Network node, sensing method, and base station

Abstract

A network node according to an embodiment of the present disclosure includes a control unit that controls at least one of a change in a mode of a sensing, a change in a base station for sensing, and a change in a terminal for sensing, when information based on a measurement of a signal for sensing satisfies a condition, and a transmission / reception unit that performs at least one of transmission and reception of a message for the change.

Description

Technical Field

[0001] This disclosure relates to network nodes, sensing methods, and base stations in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of further increasing data rates and reducing latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] The study also explored subsequent systems to LTE (e.g., also known as the 5th generation mobile communication system (5G), 5G+, the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 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 Summary of the Invention

[0007] The problem that the invention aims to solve

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

[0009] However, the details of wireless sensing have not been fully investigated. If the details of wireless sensing are unclear, there are concerns about a reduction in sensing / communication quality.

[0010] Therefore, one of the purposes of this disclosure is to provide network nodes, sensing methods, and base stations that improve the performance of wireless sensing.

[0011] Methods for solving problems

[0012] One aspect of this disclosure relates to a network node comprising: a control unit that controls changes to at least one of the sensing base station, the sensing terminal, and the sensing mode, based on information from measurements of the sensing signal satisfying a condition; and a transmission / reception unit that transmits and receives at least one message for the changes.

[0013] Invention Effects

[0014] According to one method of this disclosure, the performance of wireless sensing can be improved. Attached Figure Description

[0015] Figure 1A as well as Figure 1B An example of a scenario representing monostatic sensing in a BS or UE.

[0016] Figure 2A as well as Figure 2B An example of a scenario representing bistatic sensing between BS or UE.

[0017] Figure 3A as well as Figure 3B This is an example of a bistatic sensing scenario between the BS and the UE.

[0018] Figure 4 This represents an example of an NR positioning architecture.

[0019] Figure 5 An example representing a sequence of location services.

[0020] Figure 6 This is an example of how a version supports multiple location methods.

[0021] Figure 7 This represents an example of the handover process between gNBs in NR.

[0022] Figure 8 The first part of an example of the AMF / UPF intra-transfer process in NR.

[0023] Figure 9 Part 2 of an example of the AMF / UPF intra-process handover procedure in NR.

[0024] Figure 10 An example illustrating the association between option 1 and option 2 in implementation method A0.

[0025] Figure 11 This represents an example of the perception architecture involved in implementation method A1.

[0026] Figure 12 This is the first example of a process that extends NRPPa.

[0027] Figure 13 This is the second example of the process of extending NRPPa.

[0028] Figure 14 This is the third example of the process of extending NRPPa.

[0029] Figure 15 This is the fourth example of the process of extending NRPPa.

[0030] Figure 16 This represents an example of an IE used to extend NRPPa.

[0031] Figure 17 This is the first example of the process of extending LPP.

[0032] Figure 18 This is the second example illustrating the process of extending LPP.

[0033] Figure 19 This is the third example illustrating the process of extending LPP.

[0034] Figure 20 This represents the first instance of an IE used to extend LPP.

[0035] Figure 21 This represents the second example of an IE used to extend LPP.

[0036] Figure 22 This represents the third example of an IE used to extend LPP.

[0037] Figure 23 This represents an example of a perception architecture involving a combination of implementation methods A1 and A2.

[0038] Figure 24 This represents an example of the perception architecture involved in implementation method A3.

[0039] Figure 25 This represents an example of a perception architecture involved in a combination of implementation methods A1 and A3.

[0040] Figure 26 This is a flowchart illustrating an example of option 1-3-1 of implementation method B1.

[0041] Figure 27 This is a flowchart illustrating an example of option 1-3-2 of implementation method B1.

[0042] Figure 28 This is a flowchart illustrating an example of option 1-3-3 of implementation method B1.

[0043] Figure 29 This illustrates an example of the mobility process involved in implementation C2a.

[0044] Figure 30 This illustrates an example of the mobility process involved in a change to implementation C2a.

[0045] Figure 31 This represents an example of the mobility process involved in implementation C2b.

[0046] Figure 32 This represents an example of the mobility process involved in implementation C2c.

[0047] Figure 33 This represents an example of the mobility process involved in implementation C2d.

[0048] Figure 34 This is a diagram illustrating an example of the structure of an NW node (network node) according to one embodiment.

[0049] Figure 35 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0050] Figure 36 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0051] Figure 37 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0052] Figure 38 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0053] Figure 39 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

[0054] (ISAC)

[0055] The motivation behind integrated sensing and communications (ISAC) is to achieve high sensing performance and new / extended services through the use of various frequencies and cellular NW devices, and to optimize NW parameters through the analysis of real-time sensing data. Research is underway on: extended use cases for 5G systems to provide sensing services for various industries / applications addressing multiple objectives, and potential requirements for these use cases. Several use cases may also include non-3GPP type (non-wireless communication type) sensors (e.g., radar, cameras).

[0056] For example, application scenario 1 is sensing for traffic management at tourist destinations. For example, application scenario 2 is intruder detection in smart home environments.

[0057] As for ISAC, sensing-assisted communication and communication-assisted sensing are being studied. For sensing-assisted communication, sensing-assisted beam management and sensing-assisted resource allocation are being studied. For communication-assisted sensing, network sensing and coordinated sensing are being studied. To achieve these, waveforms, beamforming, artificial intelligence (AI) / deep learning (DL) operated radio access technology (RAT), frame structure, and reference signals are being studied. Furthermore, for shared spectrum, hardware, and algorithms used in ISAC, higher frequency bands, larger antenna arrays, and similar signal processing algorithms for communication and sensing are being investigated.

[0058] In ISAC, the following are the research topics: unified waveforms that simultaneously meet the requirements of communication (e.g., OFDM signals) and sensing (e.g., chirped signals); ISAC beamforming based on beamforming for communication (e.g., transmitted signals, received signals), sensing (e.g., echo signals, transmitted signals, reflected signals), and simultaneously achieving interference suppression between them; and CSI mining (CSI mining by AI) that extracts sensing information from channel information of communication (e.g., UL transmitted signals) and radar (e.g., DL radar signals) via AI / DL networks.

[0059] The study investigates three types of radar and communication systems: independent radar and communication systems, joint radar and communication systems, and integrated radar and communication systems. The following discussion will focus on ISAC systems that share hardware and bandwidth among radar and communication systems.

[0060] (Wireless Sensing)

[0061] Wireless sensing based on communication radio waves is an important means to realize the vision of 6G cyberphysical systems (CPS). ISAC can be implemented through the development of 5G-advanced (A) and 6G with higher frequencies and wider bandwidths. The design of ISAC waveforms and sensing reference signals (RS) are the main technologies used for the implementation of wireless sensing.

[0062] As for the application scenarios of ISAC, there are metaverse, high altitude platform station (HAPS) perception, crowd estimation, etc. HAPS can be an aircraft at an altitude of about 20km, or it can be used for non-terrestrial networks (NTN).

[0063] HAPS sensing, supported by communication capabilities, enables ultra-remote-distance sensing using echo signals. Considering that the sensing distance depends on the strength of the echo signal, an extremely low peak-to-average power ratio (PAPR) sensing waveform or sequence is required to improve the SNR of the echo signal at a given transmit power.

[0064] (Perception patterns / methods)

[0065] In conventional communication systems, there is communication between one BS (base station, gNB) and one UE, as well as joint transmission between multiple BSs and one UE. Similarly, conventional radar systems include: monostatic radar, where one radar transmits radar signals and receives echoes from the target object; and bistatic / multistatic radar, where one radar transmits radar signals and more than one radar receives echoes from the target object.

[0066] Independent systems use dedicated hardware and frequency bands for both radar and communications. This dedicated hardware can be located either in the same location or in a dedicated component.

[0067] Joint systems use the same hardware and dedicated frequency bands for both radar and communications.

[0068] The unified system uses the same hardware and frequency band for both radar and communications.

[0069] Sensing in the ISAC system can be achieved through any of the following sensing methods.

[0070] ◇Monostatic Sensing: Monostatic sensing utilizes the concept of monostatic radar. This sensing method requires one base station (BS) or one user equipment (UE) and senses signals via echo signals. In this method, there is no coordination between BSs, between UEs, or between BSs and UEs. Applications of this method include, for example, terahertz imaging.

[0071] ◇Bistatic / Multistatic Sensing: This method utilizes bistatic / multistatic radar for sensing. It requires at least two Base Stations (BSs) or two User Equipments (UEs) to detect signals through reflected signals. Applications of this method include, for example, localization.

[0072] ◇UE-Assisted Sensing: This concept utilizes NR positioning for UE-assisted sensing (UE-assisted sensing, sensing aided by UE). This sensing method requires both a Base Station (BS) and a UE, and sensing is achieved through communication (UL / DL) signals. It operates within the existing 5G NR framework. This method requires a UE, and both line-of-sight (LOS) and non-line-of-sight (NLOS) sensing require high computational complexity. An example application scenario for this sensing method is breath monitoring.

[0073] [Single-base sensing]

[0074] This sensing method includes BS (gNB) monobase sensing. Figure 1A ), and UE single-base perception ( Figure 1B ( ) perception methods.

[0075] Scenarios suitable for monostatic sensing have the following characteristics.

[0076] ◇The target being sensed is located near the BS / UE being sensed, requiring a high or moderate level of SNR in the echo signal.

[0077] ◇The target may also lack communication capabilities.

[0078] The requirements for monobase sensing capabilities have the following characteristics.

[0079] ◇Due to the full duplex nature of BS or UE, higher capabilities are required.

[0080] The performance of monostatic sensing has the following characteristics.

[0081] ◇Accuracy is increased by not using quantization.

[0082] ◇Accuracy is related to the SNR of the echo signal.

[0083] ◇Short delay.

[0084] [Bistatic Sensing / Multistatic Sensing]

[0085] 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 2BBistatic 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 ( ) perception methods.

[0086] The scenarios applicable to BS-BS bistatic sensing have the following characteristics.

[0087] It requires close synchronization and coordination between BSs, as well as scheduling and coordination among multiple BSs.

[0088] ◇The target may also lack communication capabilities.

[0089] The requirements for BS-BS bistatic sensing capabilities have the following characteristics.

[0090] ◇Because it is half duplex, it can be achieved even with lower power.

[0091] ◇Due to the synchronization between BS, a high level of capability is required.

[0092] The performance of BS-BS bistatic sensing has the following characteristics.

[0093] ◇Accuracy is increased by not using quantization.

[0094] ◇Accuracy is related to the SNR of the echo signal.

[0095] ◇The delay is moderate.

[0096] The scenarios applicable to UE-BS dual-base sensing, BS-UE dual-base sensing, and UE-UE dual-base sensing have the following characteristics.

[0097] ◇A communication UE is required to be present in the vicinity of the target.

[0098] The requirements for UE-BS dual-base sensing capabilities have the following characteristics.

[0099] ◇Because it is half duplex, it can be achieved even with lower power.

[0100] ◇High UE positioning accuracy is required.

[0101] The requirements for BS-UE bistatic sensing and UE-UE bistatic sensing capabilities have the following characteristics.

[0102] ◇Because it is half duplex, it can be achieved even with lower power.

[0103] ◇UE requires sufficient computing resources and high detection accuracy of reflected signals.

[0104] ◇High UE positioning accuracy is required.

[0105] The performance of UE-BS dual-base sensing, BS-UE dual-base sensing, and UE-UE dual-base sensing has the following characteristics.

[0106] ◇Through the quantification of feedback values, the accuracy becomes moderate.

[0107] ◇Accuracy is related to the configured resources and the UE location.

[0108] ◇The delay is relatively long.

[0109] In the embodiments described below, the following scenarios and ideas may also be used.

[0110] ◇In the ISAC scenario, communication and sensing functions are required.

[0111] ◇For lower complexity and backward compatibility, TDD (half-duplex) can be considered as an alternative to full-duplex in both BS and UE.

[0112] In a TDD-based ISAC system, it is preferable that the sensed signal and the reflected / echoed signal are transmitted and received in different time resources. For example, in BS-based sensing that includes monostatic BS sensing and bistatic BS1-BS2 sensing, it is preferable that the sensed signal is transmitted in the DL time resource, and the reflected / echoed signal is preferably received in the UL time resource. For example, in UE-based sensing that includes monostatic UE sensing and bistatic UE1-UE2 sensing, it is preferable that the sensed signal is transmitted in the UL time resource, and the reflected / echoed signal is preferably received in the DL time resource. In bistatic BS-UE sensing, it is preferable to use the DL time resource for sensing. In bistatic UE-DL sensing, it is preferable to use the UL time resource for sensing.

[0113] (Location Services: 5G System (5GS) Location Services (LCS) / Architecture Model and Concepts / Functional description of LCS per network function)

[0114] The following abbreviations may also be used in this disclosure.

[0115] - 5G Core Network: 5GC, 5GCN

[0116] - 5G System: 5GS

[0117] - (Radio Access Network): (R)AN

[0118] Next Generation Radio Access Network (NG-RAN)

[0119] Access and Mobility Management Function (AMF)

[0120] Location Management Function (LMF)

[0121] - Non-3GPP Interworking Function: N3IWF

[0122] - Mobile-Originated Location Request (MO-LR)

[0123] - Mobile Terminated Location Request: MT-LR

[0124] - Network Induced Location Request (NI-LR)

[0125] Gateway Mobile Location Center (GMLC)

[0126] - Network Exposure Function (NEF)

[0127] - Public Land Mobile Network (PLMN)

[0128] - Trusted Non-3GPP Access Network: TNAN

[0129] Internet Protocol (IP)

[0130] - IP Multimedia Subsystem: IMS

[0131] Unified Data Management (UDM)

[0132] - Unified Data Repository (UDR)

[0133] - Quality of Service (QoS)

[0134] The 5G system architecture includes the following service-based interfaces:

[0135] ◇Namf: Service-based interface hinted at by AMF.

[0136] ◇Nnef: Service-based interface hinted at by NEF.

[0137] The 5GS LCS architecture includes the following service-based interfaces for location services:

[0138] ◇Nlmf: Service-based interface hinted at by LMF;

[0139] ◇Ngmlc: Service-based interface hinted at by GMLC.

[0140] The 5G system architecture includes the following reference points:

[0141] ◇N1: Reference point between UE and AMF;

[0142] ◇N2: (R) The reference point between AN and AMF.

[0143] NG-RAN nodes are either gNBs or ng-eNBs. A gNB provides NR user plane and control plane termination for the UE and is connected to the 5GC via the NG interface. An ng-eNB provides E-UTRA user plane and control plane termination for the UE and is connected to the 5GC via the NG interface.

[0144] The gNB can also provide measurement information for the target UE and transmit this information to the LMF. To support NR RAT-dependent positioning, the gNB can also perform measurements of the target UE's radio signals and provide measurement results for location estimation.

[0145] The ng-eNB can also provide measurement results for location estimation and measurement information for the target UE, transmitting these measurements to the LMF. The ng-eNB performs the measurement based on a request from the LMF (either on-demand or periodically). The ng-eNB can also provide multiple TPs (Targeting Points). The ng-eNB can also broadcast auxiliary data information received from the LMF within a positioning system information message.

[0146] The UE can also perform measurements from DL signals from the NG-RAN, as well as from other sources such as E-UTRAN, various GNSS and TBS systems, WLAN access points, Bluetooth beacons, and the UE's barometric pressure and motion sensors. The measurements performed are determined by the selected positioning method. The UE may also include independent positioning capabilities (e.g., Global Positioning System (GPS)), thereby enabling it to report its location independently of NG-RAN transmissions. UEs with independent positioning capabilities can also utilize auxiliary information obtained from the network.

[0147] The Access and Mobility Management Function (AMF) is responsible for managing the location of the target UE for all types of location requests. The AMF can access the GMLC and NEF via the Namf interface, the RAN via the N2 reference point, and the UE via the N1 reference point. The functions performed by the AMF to support location services include the following:

[0148] ◇AMF ​​initiates NI-LR location request, which is used by UEs making IMS emergency calls or to know the geographic area of ​​UEs performing NE satellite access for PLMN selection verification.

[0149] ◇AMF ​​receives and manages location requests for periodic location events, triggered location events, and location events that can be used by the UE from the GMLC for 5GC-MT-LR and delayed 5GC-MT-LR.

[0150] ◇AMF ​​receives and manages location requests for 5GC-MO-LR from the UE.

[0151] ◇AMF ​​receives and manages event disclosure requests for location information from NEF.

[0152] ◇AMF ​​should be selected as LMF.

[0153] ◇AMF ​​receives the updated privacy request from UE and forwards it to UDR via UDM.

[0154] ◇AMF ​​supports the cancellation of periodic or triggered location reports for the target UE.

[0155] ◇AMF ​​supports changes to the service LMF for periodic or triggered location reports for the target UE.

[0156] ◇When auxiliary (support) data is broadcast in encrypted form via 5GS, the AMF receives the encryption key from the LMF and forwards it to the correctly subscribed UE using the mobility management process.

[0157] ◇AMF ​​stores the UE positioning capabilities received from LMF and sends these UE positioning capabilities along with the received location requests to LMF.

[0158] Location Management Function (LMF) manages the UE's location and the distribution of auxiliary data to the UE, supporting different location services for the target UE. In order to obtain UE-specific location measurements, including UL measurements acquired by the NG-RAN and DL measurements provided to the NG-RAN and acquired by the UE as part of other functions such as handover, the LMF can also interact with the serving gNB or serving eNB.

[0159] The Location Management Provider (LMF) manages the overall standby coordination and scheduling of resources required for the location of UEs registered in or accessing the 5GCN. It can also calculate or confirm final location and arbitrary speed estimates, and estimate the achieved accuracy. The LMF receives location requests for the target UE from the serving Location Management Provider (AMF) using the Nlmf interface. For the exchange of location information applicable to UE-assisted and UE-based positioning methods, the LMF interacts with the UE, and in order to obtain location information, interacts with NG-RAN, N3IWF, or TNAN.

[0160] To support location services, additional functions that may be performed by LMF include the following:

[0161] ◇LMF supports requests for a single location received from the serving AMF for the target UE.

[0162] ◇LMF supports requests for periodic or triggered locations received from the serving AMF for the target UE.

[0163] ◇LMF determines the type and number of location methods and the process based on the UE, PLMN capabilities, QoS, UE connectivity state for each access type, LCS client type, co-ordinate type, optional service type, and requirements for trustworthy UE location information.

[0164] ◇LMF reports the estimated location of the target UE directly to GMLC based on the periodic or triggered location of the target UE.

[0165] ◇LMF supports periodic or triggered location cancellation for the target UE.

[0166] ◇LMF supports the provision of broadcast auxiliary data via NG-RAN using encrypted or unencrypted forms, and the forwarding of encryption keys to subscribed UEs via AMF.

[0167] ◇LMF supports changes to the service LMF for periodic or triggered location reports for the target UE.

[0168] ◇LMF supports receiving stored UE positioning capabilities from AMF and supports providing updated UE positioning capabilities to AMF.

[0169] ◇The LMF maps the UE's location to a geographic area of ​​the PLMN that is permitted to operate based on a request from the AMF or that is not permitted to operate.

[0170] ◇LMF supports the determination of the UE's location within the scheduled location time.

[0171] ◇LMF determines whether to use the user plane or the control plane for positioning.

[0172] ◇LMF supports handling of 5GC-MT-LR, 5GC-NI-LR, 5GC-MO-LR, and delayed 5GC-MT-LR for user plane connections that span between the UE and LMF, whether periodic or triggered.

[0173] (NR Positioning Architecture: Stage 2 functional specification of UE positioning in NG-RAN / NG-RAN UE Positioning Architecture)

[0174] The following abbreviations may also be used in this disclosure.

[0175] Figure 4 This example illustrates a 5GS architecture (NR positioning architecture) applicable to the positioning of UEs using NR or E-UTRA access. As in this example, in a split gNB architecture, the gNB-DU can also include TRP functionality, which can support functions for TP, RP, or both TP and RP. A gNB-DU with TRP functionality does not need to provide cell service. NG-RAN includes ng-eNB and gNB.

[0176] The AMF receives a request for certain location services associated with a specific target UE from another entity (e.g., the GLMC or the UE), or the AMF itself determines the initiation of certain location services on behalf of the specific target UE (e.g., for an IMS emergency call from that UE). The AMF then sends the location service request to the LMF. The LMF processes the location service request to assist UE-based / UE-assisted positioning, which may sometimes include at least one of the forwarding of assisting data to the target UE and the positioning of the target UE. The LMF then returns the result of the location service (e.g., a location estimate for the UE) to the AMF.

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

[0178] The LTE-Uu interface (wireless interface) used to connect the UE to the ng-eNB via radio is used as one of several transport links for the LTE positioning protocol used by the target UE to access the NG-RAN via LTE.

[0179] The NG-C interfaces between the gNB and AMF, and between the ng-eNB and AMF, are transparent (unrecognized) to all UE location association processes. The NG-C interfaces participate in these processes only as transport links used for the NR location protocol.

[0180] The NL1 interface between the LMF and AMF is transparent to all UEs, gNBs, and ng-eNBs associated with the positioning process. The NL1 interface is used only as a transport link for LPP and NRPPa.

[0181] like Figure 5 Therefore, the entire sequence of events applied to the UE, NG-RAN, and LMF in location services follows these steps:

[0182] ◇1a.5 Certain entities within the GC (e.g., GMLC) request certain location services (e.g., location services) for the target UE from the serving AMF.

[0183] ◇1b. Alternatively, it is determined that the service AMF for the target UE requires certain location services (e.g., for the location of the UE specific to an emergency call).

[0184] ◇1c. Alternatively, the UE requests certain location services from the serving AMF at the NAS level.

[0185] ◇2. The AMF forwards the location service request to the LMF.

[0186] ◇3a. The LMF (e.g., to obtain location measurements or auxiliary data) initiates a location procedure that uses a serving ng-eNB or gNB within the NG-RAN, and, if possible, adjacent ng-eNBs or gNBs within the NG-RAN.

[0187] ◇3b. In addition to or instead of step 3a, the LMF (e.g., to obtain a location estimate or location measurement, or to forward auxiliary data to the UE) also begins a location process with the UE.

[0188] ◇4. The LMF provides a location service response to the AMF, which may include any desired results (e.g., the results may include a success or failure indication, and, if requested and obtained, a location estimate of the UE).

[0189] ◇5a. If step 1a has been performed, the AMF returns a location service response to the 5GC entity in step 1a, which may include any desired results (e.g., the UE's location estimate).

[0190] ◇5b. If step 1b has been performed, the AMF uses the location service response received in step 4 to assist the service that triggered the response in step 1b (e.g., it may also provide the GMLC with a location estimate associated with the emergency call).

[0191] ◇5c. If step 1c has been performed, the AMF returns a location service response to the UE, which may contain any desired results (e.g., the UE's location estimate).

[0192] (NR Positioning Protocol: Stage 2 functional specification of UE positioning in NG-RAN / Signalling protocols and interfaces)

[0193] The following abbreviations may also be used in this disclosure.

[0194] ◇Enhanced Cell-ID (Positioning Method): E-CID

[0195] ◇Observed Time Difference of Arrival (OTDOA)

[0196] ◇Multi-Round Trip Time (RTT)

[0197] ◇Uplink Angle of Arrival (UL-AoA)

[0198] ◇Azimuth Angle of Arrival (A-AoA)

[0199] ◇Zenith Angle of Arrival: Z-AoA

[0200] ◇Uplink Time Difference of Arrival (UL-TDOA)

[0201] ◇Downlink Time Difference of Arrival (DL-TDOA)

[0202] ◇Downlink Angle-of-Departure (DL-AoD)

[0203] ◇ Wireless Local Area Network (WLAN)

[0204] ◇Terrestrial beacon system (TBS)

[0205] ◇Metropolitan Beacon System (MBS)

[0206] ◇Positioning Reference Signal (PRS)

[0207] ◇User Plane Location Protocol (ULP)

[0208] NR Positioning Protocol A (NRPPa) transmits information between NG-RAN nodes and the LMF. It is used to support the following positioning functions:

[0209] ◇E-CID used for forwarding measurement values ​​from ng-eNB to LMF via E-UTRA.

[0210] ◇Data collection from ng-eNB or gNB supported by OTDOA for E-UTRA.

[0211] ◇Obtaining the cell ID and cell portion ID from the gNB supporting the NR cell ID positioning method.

[0212] ◇ Information exchange between LMF and NG-RAN nodes for the purpose of broadcasting auxiliary data.

[0213] ◇ NR E-CID of the measurement value is forwarded from gNB to LMF.

[0214] ◇ NR multi-RTT of measurements forwarded from gNB to LMF.

[0215] ◇ NR UL-AoA, which forwards the measurement value from gNB to LMF.

[0216] ◇ NR UL-TDOA of the measurement value forwarded from gNB to LMF.

[0217] ◇Data collection from gNBs supporting DL-TDOA, DL-AoD, Multi-RTT, UL-TDOA, and UL-AoA.

[0218] ◇Allows LMF to request the preset settings of measurement gap / PRS processing window from NG-RAN nodes, as well as the forwarding of measurement preset information to activate / deactivate.

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

[0220] The purpose of the LPP protocol is to separate the details of any particular positioning method from the details of the transmission that forms the basis of it, and to enable positioning for NR and LTE using multiple different positioning methods.

[0221] LPP procedures involve pairing requests / responses of multiple messages or one or more "not acknowledged" messages. Each procedure has a single purpose (e.g., forwarding auxiliary data, exchanging LPP association capabilities, or locating a target device in accordance with certain QoS and one or more location methods). To achieve more complex purposes (e.g., locating a target device in connection with the forwarding of auxiliary data and the exchange of LPP association capabilities), multiple procedures can be used serially or in parallel. Multiple procedures can also (e.g., to obtain a coarse location estimate using low latency and a more accurate location estimate using high latency) attempt more than one location simultaneously.

[0222] (Standard UE Positioning Methods: NG-RAN / Mainconcepts and requirements / Standard UE Positioning Methods)

[0223] The standard UE location methods supported in NG-RAN access are as follows:

[0224] ◇NW-assisted GNSS methods

[0225] ◇ OTDOA positioning based on LTE signals

[0226] ◇Extended Cell ID Method (E-CID) Based on LTE Signals

[0227] ◇WLAN positioning

[0228] ◇ Bluetooth positioning

[0229] ◇TBS Positioning

[0230] ◇ Sensor-based positioning:

[0231] —◇Barometric Pressure Sensor

[0232] ―◇ Motion Sensor

[0233] ◇NR Extended Cell ID Method Based on NR Signals (NR E-CID)

[0234] ◇Multi-RTT based on NR signals

[0235] ◇DL-AoD based on NR signal

[0236] ◇DL-TDOA based on NR signal

[0237] ◇UL-TDOA based on NR signal

[0238] ◇UL-AoA based on NR signals and including A-AoA and Z-AoA

[0239] OTDOA includes PRS-based TBS positioning. Current specifications only support LTE signal-based OTDOA. When a gNB serves a UE (being served), the E-CID includes the cell ID for the NR method. The E-CID is an extended cell ID based on LTE signals. Current specifications only support MBS signal-based TBS positioning. Figure 6 The SUPL in the value indicates whether SUPLULP supports this positioning method.

[0240] It supports hybrid positioning using multiple methods from a list of various positioning methods. It also supports independent (i.e., autonomous without network assistance) modes using more than one method from a list of various positioning methods.

[0241] These multiple positioning methods can also be supported for at least one of the following: UE-based version, UE-assisted / LMF-based version, and NG-RAN node-assisted version. Figure 6 This indicates whether the specification supports this version for multiple positioning methods.

[0242] (Switchover: Overall Description of NR and NG-RAN / Mobility and State Transitions / Intra-NR / Mobility in RRC_CONNECTED)

[0243] like Figure 7As shown, the inter-gNB handover process includes the following operations.

[0244] ◇1: The source gNB begins the handover and sends a handover request on the Xn interface.

[0245] ◇2: The target gNB performs admission control, providing new RRC settings as part of the HANDOVER REQUEST ACKNOWLEDGE.

[0246] ◇1: The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message received within the HANDOVER REQUEST ACKNOWLEDGE. This RRCReconfiguration message contains at least the cell ID and all the information required for access to the target cell, enabling the UE to access the target cell without needing to read system information. Depending on the situation, the RRCReconfiguration message may include information required for contention-based or contention-free random access. If beam-specific information exists, the access information to the target cell may also include that beam-specific information.

[0247] ◇S101: The source gNB begins the handover by sending a handover request via the Xn interface.

[0248] ◇S102x, S102: The target gNB performs admission control, providing new RRC settings as part of the handover request acknowledgment.

[0249] ◇S103, S103x: The source gNB provides RRC settings to the UE by forwarding the RRCReconfiguration message received within the HANDOVER REQUESTACKNOWLEDGE. This RRCReconfiguration message contains at least the cell ID and all the information required for access to the target cell, enabling the UE to access the target cell without needing to read system information. In some cases, the information required for contention-based and contention-free random access can be included in this RRCReconfiguration message. If beam-specific information exists, the access information to the target cell can also include that beam-specific information.

[0250] ◇S104: The UE moves the RRC connection to the target gNB and replies with RRCReconfigurationComplete.

[0251] like Figure 8 And such as Figure 9 As shown, the intra-AMF / UPF switching process includes the following operations.

[0252] ◇S200: The UE context within the source gNB contains information related to roaming and access restrictions provided during connection establishment or the last TA update.

[0253] ◇S201: The source gNB sets the measurement procedure for the UE, and the UE reports according to the measurement settings.

[0254] ◇S202: The source gNB determines the UE handover based on the MeasurementReport and RRM information.

[0255] ◇S203: The source gNB transmits a transparent RRC container containing the information required for handover preparation on the target side and sends a handover request message to the target gNB. This information includes at least the target cell ID and K. gNB* The source gNB contains the UE's C-RNTI, RRM settings including the UE's inactivity time, basic AS settings including antenna information and DL carrier frequency, the current QoS procedure provided to the UE for the DRB mapping rules, SIB1 information from the source gNB, UE capabilities for different RATs, and PDU session association information, which is included where UE report measurement information containing beam association information can be used. PDU session association information includes slicing information and QoS procedure level QoS distribution. The source gNB can also request DAPS handover for one or more DRBs. In the case of performing horizontal or vertical key distribution, K... gNB * is a key distributed by ME and gNB.

[0256] ◇S204: Admission control is sometimes performed by the target gNB. When slice information is sent to the target gNB, admission control considering the slice is performed. If associated with a slice that does not support PDU sessions, the target gNB rejects such PDU sessions.

[0257] ◇S205: The target gNB prepares for handover in L1 / L2 and sends a handover request acknowledgment (HANDOVERREQUEST ACKNOWLEDGE) to the source gNB. This handover request acknowledgment (HANDOVER REQUEST ACKNOWLEDGE) contains a transparent container sent to the UE as an RRC message used to perform the handover. The target gNB indicates whether it accepts the DAPS handover.

[0258] ◇S206: The source gNB triggers a Uu handover by sending an RRCReconfiguration message to the UE containing information required for accessing 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). Furthermore, it can also include a set of dedicated RACH resources, the association between RACH resources and SSBs, the association between RACH resources and UE-specific CSI-RS settings, shared RACH resources, and system information of the target cell.

[0259] ◇S207x: Data buffered by the source gNB distribution, and new data from more than one UPF.

[0260] ◇S207a, S207: In the absence of a DRB with DAPS set, the source gNB sends an Early Status Transformer message to the target gNB, transmitting the uplink PDCP SN receive status and downlink PDCH SN transmit status of the DRB (i.e., RLC AM) maintained by the applied PDCP status. The uplink PDCP SN receive status at least contains the PDCP SB of the initially missing UL PDCP SDU. If there are UL PDCP SDUs other than those requiring retransmission by the UE in the target cell, it may sometimes contain a bitmap of this receive status. The downlink PDCP SN transmit status indicates that the target gNB has been allocated a new PDCP SDU and does not yet have the following PDCP SBs for the PDCP SN.

[0261] ◇S207y: The target gNB buffers user data from the source gNB.

[0262] ◇S208x: The UE leaves the old cell and synchronizes with the new cell.

[0263] ◇S208: The UE synchronizes with the target cell and sends an RRCReconfigurationComplete message to the target gNB to complete the RRC handover process.

[0264] During DAPS handover, the UE will not disconnect from the source cell even if it receives an RRCReconfiguration message. If it receives an explicit release from the target node, the UE releases the source resources and settings, and stops receiving / transmitting DL / UL with the source.

[0265] ◇S208a, S208b: In the case of DAPS handover, the target gNB sends a handover success message to the source gNB to notify the UE of successful access to the target cell. In response, the source gNB sends an SN status transfer message to the multiple DRBs configured with the DAPS described in S207, and continues normal data forwarding.

[0266] ◇S209: The target gNB sends a PATH SWITCH REQUEST message to the AMF to switch the DL data path to the target gNB and triggers 5GC to establish an NG-C interface instance to the target gNB.

[0267] ◇S210: 5GC switches the DL data path to the target gNB. For each PDU session / tunnel, UPF sends one or more "end marker" packets to the source gNB toward the old path, and then releases any U-plane / TNL resources to the source gNB.

[0268] ◇S211: AMF uses PATH SWITCH REQUEST ACKNOWLEDGE to acknowledge PATH SWITCH REQUEST messages.

[0269] ◇S212: If a path switch request confirmation (PATH SWITCH REQUESTACKNOWLEDGE) is received from the AMF, the target gNB sends a UE context release (UE CONTEXTRELEASE) to notify the source gNB of the successful handover. Then, the source gNB can continue the ongoing data forwarding associated with the UE context and with radio and C-plane resources.

[0270] (argument)

[0271] Consider mobility processes for different scenarios.

[0272] For object detection and tracking, the sensing-related point (BS / UE) may change as the measured object or UE moves across different sensing modes / methods. Considering the degradation of sensing performance, the sensing mode / method may also be changed. This point can be either the point sending the sensing RS or the point measuring / reporting the sensing results.

[0273] In a surveillance environment, the points related to perception may change as the environment changes or the UE moves. Considering the degradation of perception performance, the perception mode / method may also be changed.

[0274] In motion monitoring, points related to perception may change as the person or user moves. Considering the degradation of perception performance, the perception mode / method may also change.

[0275] These processes can also be referred to as mobility processes for sensing, just as mobility processes for communication are. Mobility processes can also include changes to at least one of the BS, UE, and sensing methods / modes.

[0276] Due to the different / dedicated key performance indicators (KPIs) used for sensing and the processes involved, the coverage of sensing may differ from that of communication. The timing / conditions for triggering sensing using mobility may also differ from those for communication. The KPIs for sensing may also include at least one of the following: coverage area or distance (range) of the sensing service, resolution (distance / speed), latency, refresh rate, probability of not detected or detected, reliability level, and false detection.

[0277] Such mobility processes used for perception have not been adequately studied. If such research is insufficient, there are concerns about the degradation of perception performance.

[0278] Therefore, the inventors of this invention conceived of mobility processes for perception. In particular, they studied mobility processes for multiple different perception modes, considering the BS associated with the perception mode. The following embodiments are mainly described in relation to mobility processes for application scenarios involving object detection and tracking, but these embodiments can be applied to other application scenarios.

[0279] Therefore, the inventors of this invention have studied the mobility process during perception.

[0280] (Various rewrites, etc.)

[0281] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, each of the following embodiments (e.g., each case) may be used individually or in combination of at least two.

[0282] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0283] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0284] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) elements (MAC ControlElement (CE)), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0285] In this disclosure, 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., positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP) messages, etc. from the core network), or a combination thereof.

[0286] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0287] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0288] In this disclosure, "having the ability to..." and "the ability to support / report on..." can also be rewritten interchangeably.

[0289] In this disclosure, ceil(x), the ceiling function, and the floor function can be rewritten interchangeably. In this disclosure, floor(x), the floor function, and the floor function can be rewritten interchangeably. In this disclosure, sqrt(x) and the square root can be rewritten interchangeably. In this disclosure, x mod y, mod(x, y), the mod function, and the modulo operation can be rewritten interchangeably. In this disclosure, Σ... i=M M+N-1 f(i), Σ i=M M+N-1 f i f(i) or f(i) throughout i = M, M+1, ..., M+N-1 i The summation, f(M) + f(M+1) + ... + f(M+N-1), f M +f M+1 +...+f M+N-1 They can also be rewritten interchangeably. C(n,k) is related to the number of combinations of choosing k values ​​from n values ​​(combinatorial coefficient) and binomial coefficients. n C k C n k They can also be rewritten from each other.

[0290] In this disclosure, a b The expressions a, b, and b assigned to the lower right of a can also be rewritten. In this disclosure, a c The expressions a, a^c, and c assigned to the upper right of a can also be rewritten. In this disclosure, a b c The expressions a_b^c, where b is assigned to the lower right of a and c to the upper right, can also be rewritten. In this disclosure, x ~ It can also be represented by assigning a ~ to x, and can also be called an x-wavy line. In this disclosure, x - It can be represented by adding a hyphen (-) to x, or it can be called x-bar (bar).

[0291] In this disclosure, the frequency range corresponding to FR1 can also be 410-7125MHz. In this disclosure, FR2 can also include FR2-1 and FR2-2, the frequency range corresponding to FR2-1 can also be 24250-52600MHz, and the frequency range corresponding to FR2-1 can also be 52600-71000MHz.

[0292] The following terms / abbreviations may also be used in this disclosure.

[0293] ◇Secure User Plane Location (SUPL)

[0294] ◇SUPL Location Platform: SLP

[0295] ◇Sensing function: SF

[0296] ◇LTE Positioning Protocol (LPP)

[0297] ◇NR Positioning Protocol A (NRPPa)

[0298] ◇Terrestrial network: TN

[0299] ◇Non-terrestrial network: NTN

[0300] ◇Distribution Unit (DU)

[0301] ◇Transmission / Reception Point (TRP)

[0302] ◇Transmission Point: TP

[0303] ◇Reception Point: RP

[0304] ◇Enhanced Serving Mobile Location Centre (E-SMLC)

[0305] ◇SUPL Enabled Terminal: SET

[0306] ◇Non-Access Stratum: NAS

[0307] ◇Mobile equipment: ME

[0308] ◇Double active protocol stack (DAPS)

[0309] ◇Data Radio Bearer (DRB)

[0310] ◇User plane function: UPF

[0311] ◇Control plane interface between NG-RAN and 5GC: NG-C

[0312] The Xn interface is open. It supports the exchange of signaling information between two NG-RAN nodes and the forwarding of PDUs to various tunnel endpoints. Logically, Xn is a point-to-point interface between two NG-RAN nodes. This logical interface can be implemented even in the absence of a physical direct connection between the two NG-RAN nodes.

[0313] The F1 interface is open. It supports the exchange of signaling information between multiple endpoints and, further, data transmission to each endpoint. Logically, F1 is a point-to-point interface between two endpoints. A point-to-point logical interface can be implemented even in the absence of a physical direct connection between the two endpoints. The F1 interface supports the separation of the control plane and the user plane. It separates the radio network layer from the transport network layer. The F1 interface enables the interaction of information associated with the UE and information not associated with the UE. Designed with a future-oriented perspective, the F1 interface meets various new requirements and supports new services and functions. As a gNB or en-gNB, a set of one gNB-CU and multiple gNB-DUs can be observed from other logical nodes. 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 can also be separated into a control plane (CP) and a user plane (UP).

[0314] In this disclosure, sensing, wireless sensing, and measurement can also be rewritten in different ways.

[0315] In this disclosure, the terms location (location specific), positioning, position, location measurement, position estimation, measured value, estimated value, measurement result, perception, perceived information, quantity, measurement content, and measurement type can be interchanged.

[0316] In this disclosure, the terms "space transmit filter," "space receive filter," "space domain transmit filter," "space domain receive filter," "space domain filter," "space filter," and "beam" can be interchanged.

[0317] In this disclosure, the settings / instructions and sending settings / instructions can be overridden. In this disclosure, sending and reporting can also be overridden.

[0318] In this disclosure, the RS / data used in sensing, as well as sensing resources, can be rewritten to each other.

[0319] In this disclosure, the terms "object," "sensing object," "target," "non-UE target," "UE target," and "sensing object" can be interchanged. In this disclosure, a sensing object may or may not have communication capabilities. In this disclosure, a sensing object may also include a UE. In this disclosure, the terms "UE target," "target with communication capabilities," "target device," and "UE" can also be interchanged. In this disclosure, a non-UE target and a target without communication capabilities can also be interchanged.

[0320] In this disclosure, the first signal, communication signal, RS, radar signal, mixed signal of communication and radar, integrated signal, ISAC signal, sensing signal, and signal transmitted by the transmitter can also be rewritten in relation to each other. In this disclosure, the second signal, echo signal, impacted signal, reflected signal, refracted signal, diffracted signal, signal transmitted and received by the sensing transmitter and receiver, and signal received by the receiver can also be rewritten in relation to each other.

[0321] In this disclosure, 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, transmitting-receiving device, and object (target) can be interchanged. In this disclosure, transmit, Tx, and transmitter can also be interchanged. In this disclosure, receive, Rx, and receiver can also be interchanged. In this disclosure, transmitter, sensing transmitting station, and transmitting node can also be interchanged. In this disclosure, receiver, sensing receiving station, and receiving node can also be interchanged. In this disclosure, transmitter can also be BS / UE / wireless communication device / transmitting-receiving unit. In this disclosure, receiver can also be BS / UE / wireless communication device / transmitting-receiving unit. In this disclosure, transmitter and receiver can also be a single BS / UE / wireless communication device / transmitting-receiving unit. In this disclosure, transmitters and receivers, transceivers, integrated transceivers, BS, UE, and sensing stations located at the same location can also be rewritten.

[0322] In this disclosure, the base station (BS), NG-RAN node, gNB, ng-eNB, NG-RAN, RAN, network (NW), TRP, TP, and RP can also be rewritten.

[0323] In this 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 can also be rewritten.

[0324] In this disclosure, mobility process, mobility, handover, change / switching from source gNB to more than one target gNB, and change / switching of perception mode can also be rewritten.

[0325] In this disclosure, measurement results, processing results, processed measurement results, measurement-based processing results, reported measurement results, results, values, quantities, precision, and probabilities can also be rewritten from one another.

[0326] In this disclosure, fault, failure, performance degradation, and the establishment of conditions / events can also be rewritten.

[0327] In this disclosure, the sensing mode, sensing method, sensing type, gNB single-base sensing, gNB-UE dual-base sensing, UE-gNB dual-base sensing, gNB-gNB dual-base sensing, UE-UE dual-base sensing, and UE single-base sensing can also be rewritten to each other.

[0328] In this disclosure, the wireless communication method and the sensing method can also be rewritten in relation to each other.

[0329] (Wireless communication method)

[0330] <Implementation Method A0>

[0331] The perception pattern / method can also be defined in the specification. This pattern / method 6 can also follow at least one of the following options.

[0332] - Option 1

[0333] The sensing modes / methods can also be categorized in the same way as the NR positioning modes / methods as UE-based, UE-assisted, LMF-based, SMF-based, and NG-RAN node-assisted versions, and are supported.

[0334] - Option 2

[0335] The modes / methods of perception can also be classified and supported from at least one of the aforementioned perception methods, perception types, and perception scenarios.

[0336] Using the same definitions as NR positioning, the association between Option 1 and Option 2 can also be followed. Figure 10 .

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

[0338] According to this implementation, the UE / base station can use appropriate sensing modes / methods.

[0339] <Implementation Method A1>

[0340] Sensing can either reuse / repurpose the architecture and protocols of NR positioning, or it can be an extension of the architecture and protocols based on NR positioning.

[0341] Architecture

[0342] Figure 11This represents an example of a perception architecture. In this example, instead of the AMF in the aforementioned NR positioning architecture, an extended AMF is used, and instead of the LMF in the aforementioned NR positioning architecture, an extended LMF is used.

[0343] AMF is extended for the management of perception requests. LMF is extended for the management of coordination and the scheduling of resources required for perception.

[0344] NRPPa can also be extended between the NG-RAN node and the LMF to support sensing functionality. This sensing functionality may also include at least one of the following: 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.

[0345] Between the UE and LMF, the LPP can also be extended to support sensing functions for modes / methods of sensing related to UE assistance. Multiple pairs of request / response messages for sensing information can also be defined for different sensing methods / modes and for the forwarding of sensing capabilities.

[0346] For methods / modes of perception that are not related to the UE (e.g., where the UE is not required in the measurement of DL-aware RS and the feedback of measurement results associated with perception, or where the UE is not required in the transmission of UL-aware RS), the extension of LPP may not be necessary.

[0347] Extensions to NRPPa

[0348] In the extension of NRPPa, at least one of the following processes associated with perception may also be introduced.

[0349] - Measurement start (for a certain sensing method): This allows the LMF to request reports of measurements from the sensing method from the NG-RAN node.

[0350] - Measurement failure indication (for a specific sensing method): This is a procedure for NG-RAN nodes that notifies the LMF that the measurement start procedure was unable to report measurements for a previously requested sensing method.

[0351] - Measurement report (for a specific sensing method): This is a process for NG-RAN nodes that provides the LMF with measurements of the sensing method.

[0352] - Measurement End (for a Sensing Method): This indicates the end of periodic measurements performed by the sensing method executed by the NG-RAN node.

[0353] - Information exchange (for a certain sensing method): It allows the LMF to request the NG-RAN node to forward information about the sensing method to the LMF.

[0354] - (For a certain sensing method) Sensing information exchange: It requests sensing information from NG-RAN nodes, starting with LMF.

[0355] - (For a certain sensing method) Sensing information update: such as in sensing RS settings, application scenario, target device, environment, sensing area or new measurement, indicating to the LMF that a change has occurred, starting from the NG-RAN node.

[0356] - (For a certain sensing method) Sensing activation: It requests the NG-RAN node to activate semi-persistent sensing RS transmissions or to trigger non-periodic sensing RS transmissions, starting with LMF.

[0357] - (For a certain sensing method) Sensing deactivation: It indicates to the NG-RAN node that the sensing RS should be sent for deactivation, starting with LMF.

[0358] - (For a certain sensing method) Sensing RS setup exchange: It requests the NG-RAN node to set or update (e.g., turn off) matters sent by the sensing RS, starting with the LMF.

[0359] - (For a certain sensing method) Pre-setting of measurements for sensing: It provides the required information to the service gNB, requests the gNB to pre-set the sensing association settings, and is executed by LMF.

[0360] - (For a certain sensing method) Measurement activation for sensing: This involves requesting the NG-RAN node to activate or deactivate the pre-set sensing measurement association settings, starting with the LMF.

[0361] - Update / switch of sensing method / mode / type: It uses the same method / mode / application scenario / target device / environment as the update / activation / deactivation of measurement report, and can be updated / activated / deactivated using the possible sensing RS settings, sensing method / mode / application scenario / target device / environment, etc.

[0362] - Forwarding / controlling / feedback of auxiliary information: It exchanges certain auxiliary information used to make decisions related to the perception method / RS setting, etc.

[0363] - Forwarding / reporting / updating / interruption / failure indication (for a certain sensing method): This allows an NG-RAN node to request sensing measurements and report them to one or more TRPs within the NG-RAN node, or to notify the NG-RAN node of changes to previously configured measurements, or to interrupt ongoing measurements, or to notify the LMF of the inability to report previously requested measurements.

[0364] Some processes can be reused / repurposed from NR positioning processes, while others can be newly introduced for sensing purposes.

[0365] The phrase "for a certain sensing method" in each process can also be rewritten as "for multiple sensing methods / modes" or "for a certain sensing mode" or "for a certain application scenario / sensing area / environment / target device".

[0366] In the aforementioned processes, certain new information required for sensing can also be exchanged. This new information may include, for example, the sensing area, the measurement area used for sensing, the application scenario, the target device, the channel mode, the environment, or the measurement results described later.

[0367] Information elements (IEs) can also be defined for at least one of the following: the aforementioned processes, the measurement results of each sensing method / mode, the sensing RS setting, the measurement settings, the sensing area or the sensing measurement area, the application scenario, the target device, the channel model, and the environment. The measurement results can also be RSRP, time difference, AoA, AoD, delay, CSI, channel impulse response, power / delay / time domain distribution, measurement timing, Doppler / velocity, (measurement) missing values, probability of detection / false detection, etc.

[0368] The extension of NRPPa can be applied to any method / pattern of perception in implementation A0.

[0369] Figure 12 This represents the first example of the extended NRPPa process. This process allows the LMF to request reports from the NG-RAN node regarding 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.

[0370] Figure 13 This is the second example of the process of extending NRPPa. In this process, the NG-RAN node provides the LMF with sensing measurements for the UE. The NG-RAN node sends a measurement report of sensing method A to the LMF.

[0371] Figure 14This represents the third example of the extended NRPPa process. This process requests location information for the UE from the NG-RAN node, starting with the LMF. The LMF sends a sensing information request to the NG-RAN node. Then, the NG-RAN node sends a sensing information response to the LMF.

[0372] Figure 15 This represents the fourth example of the process for extending NRPPa. The process, which requests the NG-RAN node to set or update (e.g., disable) matters related to sensing RS measurements, is initiated by the LMF. The LMF sends a sensing RS setting request to the NG-RAN node. The NG-RAN node then sends a sensing RS setting response to the LMF.

[0373] Figure 16 This represents an example of an IE used to extend NRPPa. The example indicates the IE / group name, the presence of the IE ("M" if mandatory), and the range of the number of IEs (x, or x to y (x..y)). <maxno>This includes a description of the maximum number of elements, the type of the IE (e.g., integer, enumeration), the reference destination, and the meaning of the IE. The IE used for sensing RS configuration, i.e., the sensing RS resource set list, contains one or more sensing RS resource set items. Each sensing RS resource set item includes the sensing RS resource set ID, subcarrier spacing, sensing RS bandwidth, start PRB, period, and repetition factor.

[0374] The Extension of LPP

[0375] In the extension of LPP, at least one of the following processes associated with perception may also be introduced.

[0376] - Capability forwarding procedures for sensing (for a certain sensing method) (e.g., capability forwarding procedures, capability indication procedures, LPP request capability reception, LPP provision capability transmission): which enable the forwarding of capabilities from the UE / target to the server.

[0377] - (For a certain sensing method) the process associated with auxiliary data forwarding (e.g., auxiliary data forwarding process, periodic (P) / semi-persistent (SP) / aperiodic (AP)-auxiliary data forwarding process, P / SP / AP-auxiliary data forwarding process using update process, auxiliary data distribution process, P / SP / AP-auxiliary data distribution process, LPP request for auxiliary data transmission, LPP provision for auxiliary data reception): which enables the UE / target to request auxiliary data from a server used for assisting in sensing, and enables the server to forward auxiliary data to the UE / target.

[0378] - (For a certain sensing method) the process associated with the forwarding of sensing information (e.g., sensing information forwarding process, sensing information distribution process, reception of location information request message, and transmission of location information provision message): which makes it possible for the server to request sensing measurement data / sensing result estimates from the UE / target, and makes it possible for the UE / target to forward sensing measurement data / sensing result estimates to the server.

[0379] - Error handling procedure: This refers to the operating method of the receiving entity (UE / target or server) when it receives erroneous or unexpected data, or when it detects that specific data has not been found.

[0380] - Interruption Process: This allows the UE / target or server to interrupt an ongoing process due to some unexpected event. It can be used to stop an ongoing process.

[0381] Some processes can be reused / repurposed from NR positioning processes, while others can be newly introduced for sensing purposes.

[0382] The phrase "for a certain sensing method" in each process can also be rewritten as "for multiple sensing methods / modes" or "for a certain sensing mode" or "for a certain application scenario / sensing area / environment / target device".

[0383] Multiple IEs associated in the LPP can also be defined for a specific method / mode of perception or multiple methods / modes of perception (methods / modes related to UE, such as scenario 3, scenario 6, or the UE-based version in implementation A0).

[0384] Multiple related but separate IEs can be defined for different methods / modes of perception. Alternatively, different IEs can be defined for different versions, as in the existing LPP specifications. In the existing LPP specifications, the field NR-PositionCalculationAssistance-r16 within NR-DL-TDOA-ProvideAssistanceData or NR-DL-AoD-ProvideAssistanceData exists for UE-based NR DL-TDOA; otherwise, it does not. Similarly, a specific IE can be provided only for a particular version (e.g., UE-based) of positioning / perception.

[0385] The LPP extension is primarily used for UE-related sensing methods.

[0386] Figure 17 This represents the first example of the LPP extension process. This process is the LPP capability forwarding process. The server sends a capability request message (RequestCapabilities) to the UE / target. Then, the UE / target sends a capability provision message (ProvideCapabilities) to the server.

[0387] Figure 18 This is the second example of the extended LPP process. This process is the auxiliary data forwarding process. The UE / target sends an auxiliary data request message (RequestAssistenceData) to the server. Then, the server sends an auxiliary data provision message (ProvideAssistenceData) to the UE / target. The forwarding of the auxiliary data provision message can also occur periodically / semi-persistently / aperiodically.

[0388] Figure 19 This is the third example of the extended LPP process. This process is a sensing information forwarding process. The UE / target sends a Sensing Information Request message to the server. Then, the server sends a Sensing Information Provide message to the UE / target. The forwarding of the Sensing Information Provide message can also occur periodically / semi-persistently / aperiodically.

[0389] Figure 20 This represents the first example of an IE used to extend LPP. In this example, the IE used to sense requests for information, namely RequestSensingInformation, includes a common IE (commonIEsRequestSensingInformation) for multiple sensing methods, 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).

[0390] Figure 21 This represents a second example of an IE used to extend LPP. In this example, the IE for providing sensing information, namely ProvideSensingInformation, includes a common IE (commonIEsProvideSensingInformation) for multiple sensing methods, 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).

[0391] Figure 22 This represents the third example of an IE used to extend LPP. In this example, METHOD-A-ProvideSensingInformation can also contain METHOD-A-SignalMeasurementInformation and ecid-Error. METHOD-A-SignalMeasurementInformation can also contain primaryCellMeasuredResults and measuredResultsList.

[0392] According to this implementation, the UE / base station can use an appropriate architecture / protocol that has been extended for sensing.

[0393] <Implementation Method A2>

[0394] The new architecture and protocol for sensing differ from the architecture and protocol for NR positioning, and may also include at least one of the following features.

[0395] - Introducing a new AMF for managing awareness requests.

[0396] - Introduces new features for managing co-ordination and scheduling the resources required for sensing, namely the sensing management function (SMF).

[0397] - It is also possible to introduce new protocols (such as NRPPa or based on NRPPa) between NG-RAN nodes and new SMFs.

[0398] - It is also possible to introduce a new protocol (such as LPP or based on LPP) between the UE and the new SMF.

[0399] Alternatively, some architectures / protocols (as in implementation A1) may be reused / repurposed / extended, while some architectures / protocols (as in implementation A2) may be newly introduced. Figure 23 This illustrates an example of a sensing architecture involving a combination of implementation methods A1 and A2. In this example, instead of the AMF in the aforementioned NR positioning architecture, the extended AMF of implementation method A1 is used, and a new SMF of implementation method A2 is added and connected to the extended AMF.

[0400] The process for the new protocol and the details of the IE can also be the same as in implementation method A1.

[0401] According to this implementation, the UE / base station can use the appropriate architecture / protocol introduced for sensing.

[0402] <Implementation Method A3>

[0403] The new architecture and protocol of perception are different from those of NR positioning, but can also be connected to / operate with those of NR positioning, and include at least one of the following features.

[0404] - Introduce an additional AMF (Adaptive Context Function) to manage the relationship / adaptation between perception and location requests. For example, a perception request could trigger a location request, and the location result could be reused / repurposed for perception. Alternatively, a new interface could be introduced between the existing AMF and the additional AMF.

[0405] - Introduce additional (new) sensing management functions (SMFs) for managing co-ordination, scheduling of resources required for sensing, and relationships / adaptations between locations. For example, certain resources / settings for location (e.g., PRS), and measurements of RSRP / RSRQ / AoA / AoD / time difference can be reused / repurposed for sensing. For example, a new interface between the existing LMF and the additional AMF can also be introduced. For example, a new interface between the existing LMF and the additional SMF can also be introduced.

[0406] - It is also possible to introduce new protocols (such as NRPPa or based on NRPPa) between NG-RAN nodes and additional SMFs.

[0407] - It is also possible to introduce a new protocol (such as LPP or based on LPP) between the UE and the additional SMF.

[0408] Figure 24 This illustrates an example of the sensing architecture involved in implementation A3. In this example, the LMF and the additional SMF are connected in the aforementioned NR positioning architecture, and the AMF, the LMF, the additional SMF, and the additional AMF are connected.

[0409] Implementation methods A1, A2, and combinations of at least two of them are also possible. Different architectures / protocols can also be applied to different implementation methods.

[0410] Figure 25 This illustrates an example of a sensing architecture involving a combination of implementation methods A1 and A3. In this example, the AMF and LMF in the aforementioned NR positioning architecture are connected to an additional SMF.

[0411] According to this implementation, the UE / base station can use an appropriate architecture / protocol for location-based awareness.

[0412] <Analysis B1>

[0413] In BS (gNB)-UE dual-base sensing, the base station (e.g., gNB) transmits RS / data (DL sensing resources) used in DL sensing, for example. The UE then performs measurements on the RS / data received via the object and reports the sensing results to the NW (e.g., gNB).

[0414] Depending on the application scenario, different quantities (measurement content / measurement results) can be applied. However, it is not yet clear what quantities the UE measures and reports. Therefore, the inventors of this invention have conceived of a method for appropriately measuring / reporting sense resources.

[0415] <Implementation Method B1>

[0416] Similar to BS (gNB)-UE dual-base sensing, the UE receives sensing RS / data (DL sensing resources) transmitted from the base station (gNB) via the object and performs measurements (control measurements). The UE may also receive settings / instructions related to the measurement quantity (measurement content / measurement result) in advance from the NW (base station). For example, the measurement quantity may be at least one of the following types.

[0417] [Implementation Method B1.1]

[0418] The UE can also measure sensed resources (RS / data) and send (report) the measurement results directly to the NW (base station). The measurement results can also be at least one of the following types 1 (1-0 to 1-5).

[0419] Type 1-0: Code phase measurement (also known as pseudo range), Doppler measurement, carrier phase measurement (also known as cumulative delta range), carrier-to-noise ratio of the received signal, measurement quality parameters for each measurement, measurement information related to the additional path (non-GNSS associated 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. The data includes at least one of the following: UE receiver-transmitter time difference (ARFCN), barometric pressure sensor measurement, round-trip time, measurement characteristics, reference location, reference time, quality of each measurement, and line-of-sight (LOS) / non-line-of-sight (NLOS) information. This information may also be included in the measurement results of NR positioning used in UE-assisted positioning methods.

[0420] 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)

[0421] Types 1-2: Channel Impulse Response (CIR) and other transformations.

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

[0423] Types 1-3: Power delay profile (PDP), or delay profile (DP), or range / delay-Doppler / angle mapping.

[0424] Types 1-4: at least one of power, delay, phase, and channel response timing.

[0425] Types 1-5: Measurements of at least one of Types 1-1 to 1-4 can also be measured for each of one or more paths. For example, the X strongest paths can also be selected for reporting. "Strongest" can also mean that the values ​​of the measurements of each type are large.

[0426] In addition, various types of measurements can also be reported together with other information such as cell ID, RSID, measurement timing, timestamp, LOS / NLOS, quality / reliability of each measurement, etc.

[0427] According to implementation method B1.1, the UE can determine the appropriate reporting amount for DL-aware resources and implement appropriate measurement / reporting.

[0428] [Implementation Method B1.2]

[0429] The UE can also perform measurements corresponding to the application scenario for sensed resources (RS / data) and send (report) the measurement results. The measurement results can be, for example, at least one of the following types 2 (2-0 to 2-4).

[0430] Type 2-0: Latitude / longitude / altitude (with uncertain shape), velocity (with uncertain shape), reference time (e.g., with temporal correlation from GNSS to NG-RAN and uncertain shape), indication of the positioning / sensing method used, measured cell ID, RSID, ARFCN, measurement timing, UE location estimation (with uncertain shape), timestamp, reference location, reference time, quality of each measurement, and at least one of LOS / NLOS information. This information may also be included in the measurement results of NR positioning for UE-based positioning methods.

[0431] Type 2-1: The number of one or more detected objects.

[0432] Type 2-1': The presence or absence of the object being detected. That is, the number reported can also be 0.

[0433] Type 2-2: The scope of the object being detected. That is, not only a specific location, but also the scope corresponding to a specific location.

[0434] Type 2-2': The size of the object being detected.

[0435] Type 2-3: The state of the detected object (e.g., speed, direction of movement, path, distance to the object, angle, object recognition result, shape recognition result, posture recognition result, substance recognition result).

[0436] Types 2-4: Credibility.

[0437] The UE can also measure / report statistical values ​​of the measured quantities (e.g., the average value, cumulative distribution function (CDF) / probability density function (PDF) etc.).

[0438] In addition, various types of measurements can also be measured / reported together with other information such as cell ID, RS ID, measurement timing, timestamp, LOS / NLOS, and at least one of the quality / reliability of each measurement.

[0439] The UE can also send the supported application scenarios as UE capability information. The UE can also receive the settings / instructions for the measurement quantity to be measured in advance through higher-layer signaling / physical layer signaling for each application scenario, and perform measurement / reporting based on the settings / instructions.

[0440] According to implementation method B1.2, the UE can perform appropriate measurements / reports for DL-aware resources based on the application scenario. This enables optimal communication to be implemented for each application scenario.

[0441] [Implementation Method B1.3]

[0442] The UE may send (report) at least one direct measurement result (type 1, i.e. any type in implementation B1.1) and at least one measurement result corresponding to the application scenario (type 2, i.e. any type in implementation B1.2) separately, or it may send (report) them together.

[0443] Option 1-3-1: The UE may also measure only the measurement quantity of type 1 (any type in implementation B1.1) and send (report).

[0444] Figure 26 This is a flowchart illustrating an example of option 1-3-1. The UE measures DL sensing resources (RS / data) (S101). The UE sends (reports) the direct measurement results based on the measurements in S101 to the gNB / LMF (type 1 measurement results, e.g., associated with CSI) (S102). Based on the reported measurement results, the gNB / LMF performs calculations / processing / measurements corresponding to the application scenario to obtain the final sensing result (S103). The sensing result in S103 corresponds to a type 2 (any type in implementation B1.2) measurement result.

[0445] According to option 1-3-1, by setting the UE's measurement to only type 1, it is possible to reduce the amount of processing required by the UE.

[0446] Option 1-3-2: The UE can also obtain the measurement results of type 2 (any type in implementation B1.2) based on the measurement results of type 1 (any type in implementation B1.1) and send (report).

[0447] Figure 27 This is a flowchart illustrating an example of option 1-3-2. The UE measures DL sensing resources (RS / data) (S201). The UE obtains the direct measurement results based on the measurement in S201 (type 1 measurement results, e.g., associated with CSI) (S202). Based on the measurement results in S202, the UE performs calculations / processing / measurements corresponding to the application scenario, obtains the final sensing result, and reports it to the gNB / LMF (S203). The sensing result in S203 corresponds to the type 2 (any type in implementation B1.2) measurement result.

[0448] According to option 1-3-2, the UE also obtains the type 2 measurement results, thereby enabling rapid processing corresponding to those measurement results. Furthermore, the UE can select the content to send based on the type 2 measurement results.

[0449] Option 1-3-3: The UE may also send (report) the measurement results of type 1 (any type in implementation B1.1) and the measurement results of type 2 (any type in implementation B1.2) together.

[0450] Figure 28 This is a flowchart illustrating an example of option 1-3-3. The UE measures DL sensing resources (RS / data) (S301). The UE obtains the direct measurement results based on the measurement in S301 (type 1 measurement results, e.g., associated with CSI) (S302). Based on the measurement results in S302, the UE performs calculations / processing / measurements corresponding to the application scenario and obtains the measurement results (all or part of the measurement results) (S303). The sensing results in S303 correspond to type 2 (any type in implementation B1.2) measurement results. The UE reports the direct measurement results in S302 (all or part of the measurement results) and the measurement results corresponding to the application scenario in S303 (all or part of the measurement results) to the gNB / LMF (S304).

[0451] According to option 1-3-3, the UE can select the measurement result to be sent from the measurement results of type 1 and type 2 based on the application scenario, and send it (report).

[0452] For the method of transmitting (reporting) measurement results by the UE, the following options 1-3-4 and 1-3-5 can also be applied.

[0453] Option 1-3-4: The UE can also use PUCCH / PUSCH as a UCI (CSI or other UL control information) or MAC CE or Radio Resource Control (RRC) Information Element (IE) to send measurement results to the NW.

[0454] Option 1-3-5: The UE may also use the extended LPP protocol for sensing or the new LPP protocol for sensing, or a protocol based on the LPP protocol, for sensing extended LMF or new SMF / Sensing Function (SF) and send it. The extended LMF, new SMF, LPP protocol or LPP protocol based protocol may also correspond to the sensing architecture and protocol described in (1) and (2) above.

[0455] [change]

[0456] If the number of reports for at least one type exceeds the threshold, the UE can also send (report) that number of reports. The threshold can also be preset / indicated via higher-layer signaling / physical-layer signaling. The threshold can also vary for each object / path.

[0457] The UE can use different methods to transmit type 1 measurement results and type 2 measurement results, or it can use the same method. For example, the UE can 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 can also be different.

[0458] According to this implementation, the quantities and methods of sensing between the BS (gNB) and UE become clear. As a result, the UE can appropriately measure and report DL sensing resources, thus preventing a decrease in sensing accuracy and communication quality.

[0459] <Analysis B2>

[0460] As described in Implementation B1, when measurements and methods related to DL sensing resources are applied, it is not yet clear what settings the UE should be configured or what operations the UE should perform. For example, the settings / selections related to spatial transmit filters / spatial receive filters are not yet clear. Therefore, the inventors of this invention have conceived of a setting / operation method for appropriately receiving / measuring / reporting sensing resources.

[0461] <Implementation Method B2>

[0462] For settings related to the measurement of DL-sensing resources and the corresponding reports, the following options can also be applied. The UE can also receive from the NW (e.g., a base station) a setting / instruction indicating that the same measurement RS resource (DL-sensing resource) is repeatedly transmitted R times (R>=1) in consecutive symbols / time slots / specific time units. Then, the UE can also receive the RS resource (DL-sensing resource) repeatedly transmitted based on the setting / instruction via an object and measure it (or control the measurement).

[0463] This implementation method can also be used in combination with implementation method B1. That is, the UE can also receive downlink (DL) sensing resources repeatedly transmitted from the base station (gNB) and received via the object, and control the measurement of the repeatedly transmitted DL sensing resources.

[0464] [Implementation Method B2.1]

[0465] The same spatial transmission filter can also be used for each of the repeatedly transmitted RS resources (DL-aware resources). The UE can also receive settings / indications related to RS resources repeatedly transmitted from the NW using the same spatial transmission filter (e.g., the same TCI state / QCL-D source RS). For example, when the base station can specifically / infer the location (range) of an object, repeated transmission using the same spatial transmission filter (beam) can improve the measurement accuracy of the UE.

[0466] Option 1

[0467] The UE can also change the spatial receiving filter for each measurement. The UE can also determine the spatial receiving filter without using settings / instructions. In this case, the UE can also apply the following options 1-1 to 1-3. Furthermore, when reporting the measurement quantity (measurement result) of Implementation B1, the following options 1-1 to 1-3 can also be applied.

[0468] Option 1-1: The UE may also select / report one (optimal) measurement result for one measurement sample for the purpose of reporting. Then, the UE may further report information / concepts related to the selected spatial reception filter corresponding to the selected / reported measurement result (e.g., TCI status, RS ID of QCL resource, beam ID, RS ID of DL / UL, etc.).

[0469] Option 1-2: The UE can also select a maximum of X (optimal) measurement results / measurement RSs for reporting. Here, X <= R, and X can also be set via RRC based on the UE's transmitting capabilities. The UE can then report the selected measurement results, and further, report information / concepts related to the spatial reception filter used to receive the selected measurement RSs.

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

[0471] Option 1-2-2: When several measurements are identical for X resources, the UE can report only one measurement for each identical resource. When the measurements for X resources are different, the UE can report measurements related to those X resources. This reduces the reporting of identical measurements, thus suppressing overhead.

[0472] Options 1-3: The UE can also perform averaging / filtering of X (e.g., the optimal X) measurement results and report one of the processed measurement results. The UE can also send this X as UE capability information, and X can also be set via RRC signaling.

[0473] The selection of UE in options 1-1 and 1-2 can be based on calculations of the highest / lowest / average intensity / range / mass / probability of the measurement results, or it can be based on specific rules.

[0474] The UE may also envision that the spatial transmission filter used for RS transmission is the same as the spatial reception filter used for RS reception.

[0475] Option 2

[0476] The spatial reception filter of the UE used for each measurement can also be set by the NW. In this case, options 1-1 to 1-3 can also be applied in the same way. However, in option 2, the UE may also choose not to report information / concepts related to the spatial reception filter.

[0477] Alternatively, option 2 can also be applied only when R=1.

[0478] When a specific spatial receiving filter is applied, the UE may also not need to detect the sensing RS.

[0479] The UE can also pre-transmit the capabilities associated with the spatial receiving filter used for receiving measurements as UE capability information.

[0480] [Implementation Method B2.2]

[0481] Alternatively, a different spatial transmission filter can be used for each of the repeatedly transmitted RS resources (DL sensing resources). The UE can also receive settings / instructions from the NW for R sensing resources that are repeatedly transmitted using different spatial transmission filters (e.g., via TCI state / QCL-D RS). For example, in cases where the base station has difficulty specifying / inferring the location (range) of an object, by using different spatial transmission filters (beams), the UE can perform correct measurements regardless of the object's location.

[0482] Option 1

[0483] The UE may also use the same spatial receiving filter for each measurement. The UE may also determine the spatial receiving filter without using a setting / instruction. In this case, the UE may also apply the following options 1-1 to 1-3. Furthermore, when reporting the measurement quantity (measurement result) of Implementation B1, the following options 1-1 to 1-3 may also be applied.

[0484] Option 1-1: The UE may also select one (optimal) measurement result for a single measurement sample for reporting purposes. The UE may then further report information / concepts related to the selected spatial transmission filter corresponding to the selected / reported measurement result (e.g., TCI status, RS ID of QCL resources, beam ID, rearranged RS index, etc.). The UE may or may not report information / concepts related to the spatial reception filter.

[0485] Option 1-2: The UE may also select a maximum of X (optimal X) measurement results for reporting. Here, X <= R, and X can also be set via RRC based on the UE's transmitting capabilities. The UE may then further report information / concepts related to the selected RS / space transmission filter corresponding to the selected / reported measurement results. The UE may also choose not to report information / concepts related to the space reception filter.

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

[0487] Option 1-2-2: When several measurements are identical for X resources, the UE can report each measurement only once. When the measurements for X resources are different, the UE can report each measurement for each of the X resources separately. This reduces the reporting of identical measurements, thus suppressing overhead.

[0488] Options 1-3: The UE can also perform averaging / filtering of X (e.g., the optimal X) measurement results and report one of the processed measurement results. The UE can also send this X as UE capability information, and this X can also be set via RRC signaling, etc.

[0489] The selection of UE in options 1-1 and 1-2 can be based on calculations of the highest / lowest / average intensity / range / mass / probability of the measurement results, or it can be based on specific rules.

[0490] Option 2

[0491] The UE can also use the same spatial reception filter for each measurement. The spatial reception filter of the UE used for each measurement can also be set by the NW through higher-layer signaling / physical layer signaling, etc. The UE can also report the set reporting amount in the same way as in implementation B1. In option 2, options 1-1 to 1-3 can also be applied in the same way. However, in option 2, the UE may also not report information / concepts related to the spatial reception filter.

[0492] Option 3

[0493] The UE can also use a different spatial receiving filter for each measurement. The spatial receiving filter used by the UE for each measurement can also be determined by the UE. The UE can also report the set reporting amount in the same way as in implementation B1. In option 3, options 1-1 to 1-3 can also be applied in the same way.

[0494] Option 4

[0495] The UE can also use a different spatial reception filter for each measurement. The spatial reception filter of the UE used for each measurement can also be set by the NW through higher-layer signaling / physical layer signaling, etc. The UE can also report the set reporting amount in the same way as in implementation B1. In option 4, options 1-1 to 1-3 can also be applied in the same way. However, in option 4, the UE may not report information / concepts related to the spatial reception filter.

[0496] When a specific spatial receiving filter is applied, the UE may also not need to detect the sensing RS.

[0497] The UE can also pre-transmit the capabilities associated with the spatial receiving filter used for receiving measurements as UE capability information.

[0498] According to this implementation, the methods for setting / selecting spatial transmit filters / spatial receive filters in the sensing between the BS (gNB) and UE become clear. As a result, the UE can appropriately receive DL sensing resources (beams) and measure / report, thus preventing a decrease in sensing accuracy / communication quality.

[0499] <Analysis B3>

[0500] In UE-BS (gNB) bistatic sensing, the UE, for example, transmits RS / data (UL sensing resources) used in UL sensing. The base station (e.g., gNB) then performs measurements on the received RS / data via the object and reports the sensing results.

[0501] Depending on the application scenario, different quantities (measurement content) may be applied. However, it is unclear what quantities the gNB measures and reports. Therefore, the inventors of this invention have conceived of a method for appropriately measuring / reporting sensed resources.

[0502] <Implementation Method B3>

[0503] Similar to UE-BS (gNB) bistatic sensing, the base station (gNB) receives sensing RS / data (UL sensing resources) transmitted from the UE via the object and performs measurements. The gNB can also use the Extended NR Positioning Protocol A (NRPPa) for sensing or a protocol based on the New NRPPa for sensing to send (report) measurements (measurement results) to the UE, the Extended LMF for sensing, or the New SMF / SF for sensing. These measurements (measurement results) can, for example, be at least one of the following types.

[0504] [Implementation Method B3.1]

[0505] The base station (gNB) can also measure sensed resources (RS / data) and send (report) the direct measurement results. The measurement results can also be, for example, at least one of the following types 3 (3-0 to 3-4).

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

[0507] Type 3-1: CIR and other transformations.

[0508] Type 3-1': Radar Cross Section (RCS), and other transformations.

[0509] Type 3-2: Power Delay Distribution (PDP), or Delay Distribution (DP), or range / delay-Doppler / angle mapping.

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

[0511] Type 3-4: The measurement of at least one of Types 3-1 to 3-3 can also be measured for each of one or more paths. For example, the X strongest paths can also be selected for reporting.

[0512] In addition, various types of measurements can also be reported together with other information such as cell ID, RSID, measurement timing, timestamp, LOS / NLOS, quality / reliability of each measurement, etc.

[0513] According to implementation method B3.1, the gNB is able to determine the appropriate reporting amount for UL sensing resources and implement appropriate measurement / reporting.

[0514] [Implementation Method B3.2]

[0515] The gNB can also perform measurements appropriate to the application scenario for UL sensing resources (RS / data) and send (report) the measurement results. The measurement results can also be at least one of the following types 4 (4-1 to 4-4).

[0516] Type 4-1: The number of one or more targets detected.

[0517] Type 4-1': The presence or absence of the object being detected. That is, the number reported can also be 0.

[0518] Type 4-2: The scope of the object being detected. That is, not only a specific location, but also the scope corresponding to a specific location.

[0519] Type 4-2': The size of the object being detected.

[0520] Type 4-3: The state of the detected object (e.g., speed, direction of movement, path, distance to the object, angle, object recognition result, shape recognition result, posture recognition result, substance recognition result).

[0521] Type 4-4: Credibility.

[0522] The UE can also measure / report statistical values ​​of the measured quantities (e.g., the various types of information mentioned above), such as the mean, cumulative distribution function (CDF), probability density function (PDF), etc.

[0523] The gNB can also send (report) at least one direct measurement result (type 3, i.e. any type in implementation B3.1) and at least one measurement result corresponding to the application scenario (type 4, i.e. any type in implementation B3.2) separately, or send (report) them together.

[0524] In addition, various types of measurements can also be reported together with other information such as cell ID, RSID, measurement timing, timestamp, LOS / NLOS, quality / reliability of each measurement, etc.

[0525] The example of implementation method B1.3 can also be used in the same way with respect to implementation methods B3.1 and B3.2. That is, type 1 of implementation method B1.3 is replaced with type 3, type 2 is replaced with type 4, DL is replaced with UL, UE is replaced with gNB, and gNB / LMF (transmission destination) is replaced with LMF / SMF / SF.

[0526] The gNB can also receive in advance settings / instructions for measurements that should be measured according to each application scenario via higher-layer signaling / physical layer signaling, and perform measurements / reports based on those settings / instructions.

[0527] According to implementation method B3.2, the gNB can perform appropriate measurements / reports for UL sensing resources based on the application scenario. This enables optimal communication for each application scenario.

[0528] <Analysis B4>

[0529] As described in Implementation B3, when measurements and methods related to UL sensing resources are applied, it is not yet clear what settings the gNB should be configured for or what operations the gNB / UE should perform. For example, the settings / selections related to spatial transmit filters / spatial receive filters are not yet clear. Therefore, the inventors of this invention have conceived of a setting / operation method for appropriately receiving / measuring / reporting sensing resources.

[0530] <Implementation Method B4>

[0531] The following options can also be applied to settings related to the measurement of UL sensing resources, as well as reports corresponding to those settings and RS transmissions from the UE. The NW (base station, gNB) can also send a setting / instruction to the UE indicating that the same UL RS resource (UL sensing resource) is repeatedly transmitted R times (R>=1) in consecutive symbols / time slots / specific time units. The gNB can also receive the UL RS resource (UL sensing resource) repeatedly transmitted from the UE via the object and measure it (or control the measurement).

[0532] Option A: NW can also configure the UE to repeatedly transmit RS resources within the same spatial transmission filter. This spatial transmission filter can also be determined by the UE.

[0533] Option B: The NW can also configure the UE to repeatedly transmit RS resources in the same spatial transmission filter. This same spatial transmission filter can also be set / indicated by the NW (e.g., using TCI status ID or QCL-D source RS).

[0534] Option C: NW can also configure the UE to repeatedly transmit RS resources in different spatial transmission filters. This spatial transmission filter can also be determined by the UE.

[0535] Option D: The NW can also configure the UE to repeatedly transmit RS resources in different spatial transmission filters. This spatial transmission filter can also be determined by the NW.

[0536] In options A through D, the NW (gNB) may use the same or different spatial receiving filters. If the gNB measures the sensed resources (RS / data) and reports the measurement results in the same manner as in implementation B3, options 1 through 3 may also be applied.

[0537] Option 1: The gNB can also select one (optimal) measurement result for one measurement sample used for reporting. The gNB can also report information / concepts related to the selected RS / space transmit filter corresponding to the selected / reported measurement result (e.g., TCI status, RS ID of QCL resource, beam ID, rearranged RS index, etc.). The gNB may or may not report information / concepts related to the space receive filter.

[0538] Option 2: The gNB can also select a maximum of X (optimal X) measurements for reporting. Here, X <= R, and X can also be set via RRC based on the UE's transmission capabilities. The gNB can then further report information / concepts related to the selected RS / space transmission filter, corresponding to the selected / reported measurements.

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

[0540] Option 2-2: When several measurements are identical for X resources, gNB can report each identical measurement only once. When the measurements for X resources are different, gNB can report each measurement for each of the X resources separately. This reduces the reporting of identical measurements, thus suppressing overhead.

[0541] Option 3: The gNB can also perform averaging / filtering of X (e.g., the optimal X) measurement results and report one of the processed measurement results. X can also be set via RRC signaling, etc.

[0542] The selection of gNB in ​​options 1 and 2 can be based on calculations of the highest / lowest / average strength / range / mass / probability, etc., from the measurement results, or it can be based on specific rules.

[0543] In cases where NW configurations include UEs with different spatial transmission filters, gaps can be set to allow for repeated transmission of UL-aware resources. These gaps can be defined in the specification or transmitted by the UE as UE capability information. A gap is the time interval between transmissions of RSs using different spatial transmission filters.

[0544] According to this implementation, the methods for setting / selecting spatial transmit filters / spatial receive filters in the sensing between UE-BS (gNB) become clear. As a result, the gNB can appropriately receive UL sensing resources (beams) and measure / report, thus preventing a decrease in sensing accuracy / communication quality.

[0545] <Analysis C1>

[0546] In gNB monopolar sensing, the gNB may lose tracking of an object as it moves. Prior to this, the gNB could either trigger a mobility process to discover another gNB in ​​order to maintain continuous object sensing capabilities, or it could trigger a mobility process to switch to another sensing method with higher accuracy.

[0547] Detailed information is provided in Implementation C1 / Implementation C2 for the gNB single-base sensing method. For other sensing methods, the differences from Implementation C1 / Implementation C2 are provided.

[0548] In this disclosure, the signaling between the gNB / UE and the SMF can also follow implementation method A. In this disclosure, the signaling from the gNB to the UE can also follow signaling based on RRC IE / MAC CE / DCI.

[0549] <Implementation Method C1>

[0550] This implementation relates to a mobility process for sensing.

[0551] The definition of perceived mobility may also include changes to at least one of gNB, UE, and the method / mode of perception.

[0552] In this disclosure, the source / target gNB / UE, TRP, IAB, NCR, RIS, and network controlled access point (NCAP) can also be rewritten.

[0553] The mobility process can also be triggered by at least one of the following options.

[0554] Option 1: Extended LMF / New SMF / New AMF. In this disclosure, SMF may also refer to Extended LMF / New SMF / New AMF / SF. SMF may also trigger mobility procedures based on measurements reported from gNB or results processed in SMF.

[0555] Option 2: Source gNB. The source gNB can also trigger the mobility process based on the results measured or processed by the source gNB.

[0556] The target gNB used for mobility can also be determined by at least one node from several options. This node may or may not determine the target perception method / mode.

[0557] Option 3: SMF.

[0558] Option 4: Source gNB. More suitable than SMF for determining the method / pattern of perception.

[0559] The combination of options 1 and 4 is not preferred. In cases where the SMF determines the mobility process, the SMF can also determine more than one target gNB.

[0560] More than one target gNB can also follow at least one of the following conditions.

[0561] ◇Scenario 1: A single target gNB using gNB monobase sensing.

[0562] ◇Scenario 2: One gNB-gNB pair using gNB-gNB bistatic sensing. This pair can be two target gNBs, or one master gNB and one coordinating gNB.

[0563] ◇Scenario 3: One gNB-UE pair using gNB-UE bistatic sensing.

[0564] ◇Scenario 4: One gNB-UE pair using UE-gNB dual-base sensing.

[0565] ◇Scenario 5: Using a single target gNB for bistatic sensing between the gNB and the UE. After the mobility process, the UE can also be selected and configured via the target gNB.

[0566] ◇Scenario 6: Using a single target gNB for UE-gNB bistatic sensing. After the mobility procedure, the UE can also be selected and configured via the target gNB.

[0567] ◇In each case, multiple objectives, or multiple objectives from combinations of different situations, may also be possible.

[0568] A constraint may or may not exist between the node that determines the triggering of the mobility process (option 1 / 2) and the node that determines more than one target gNB (option 3 / 4). The constraint may also be at least one of the following examples.

[0569] ◇The node that determines the trigger of the mobility process is the same as the node that determines one or more target gNBs.

[0570] ◇When the node that triggers the mobility process is a gNB, the node that determines more than one target gNB can also be an SMF or a gNB. When the node that triggers the mobility process is an SMF, the node that determines more than one target gNB can also still be an SMF.

[0571] The conditions / events used to determine mobility / handover processes / triggering SMF / gNB can also follow at least one of the following options.

[0572] Option 1: This condition / event depends on the implementation of SMF / gNB.

[0573] Option 2: The condition / event is defined in the specification used for perception. The condition / event may also follow at least one of the following options 2-x.

[0574] Option 2-1: For a Type 3 measurement quantity associated with a directly sensed resource measurement result, the event occurs when the measurement result / value / quantity / accuracy / probability is lower or higher than a defined / set threshold, or within a defined / set range. The Type 3 measurement quantity may also follow at least one of Embodiments B1 to B4. The Type 3 measurement quantity may also be measured / calculated by the gNB.

[0575] Option 2-2: For a Type 4 measurement associated with a perception result for a specific application scenario, the event occurs when the measured result / value / quantity / accuracy / probability is lower or higher than a defined / set threshold, or within a defined / set range. The Type 4 measurement may also follow at least one of Implementation Methods B1 to B4. The Type 4 measurement may also be measured / calculated by gNB / SMF.

[0576] ―◇Change 1: An event can be a situation where the measured result / value / quantity / accuracy / probability is lower (poor) or higher (good) than a defined / set threshold, or a situation within a defined / set range that lasts for a specific period of time, or it can occur only a specific number of times. The specific time or specific number of times (threshold) can be defined in the specification or set through RRC IE.

[0577] ―◇Change 2: The event is valid only if one or more objects are considered. The number of objects can be defined in the specification or set via RRC IE.

[0578] ―◇Change 3: For different multiple measurements, either a common single condition / event can be applied, or multiple dedicated conditions / events can be applied separately.

[0579] According to this implementation method, the mobility process can be performed appropriately.

[0580] <Implementation Method C2a>

[0581] This implementation involves a combination of options 2 and 3 of implementation C1 in gNB monobase sensing (the mobility process is triggered by the source gNB and the target gNB is determined by the SMF).

[0582] like Figure 29 As in the example, if the condition / event in implementation C1 occurs in the gNB (S301), the source gNB can also send a sensing HANDOVER REQUEST message to the SMF (S302). The SMF can identify at least one of more target gNBs and at least one of their corresponding target sensing modes (S303), and forward the sensing HANDOVER REQUEST to more than one target gNB, or it can send a new sensing request with a reset of sensing association settings to more than one target gNB (S304). Then, the SMF can also send a sensing HANDOVER REQUEST ACKNOWLEDGE message to the source gNB (S306). The source gNB can either continue sensing association behavior based on information from the SMF, or it can stop (S307). This continuation can also include updates. The target gNB can also process requests from the SMF (S305).

[0583] In this disclosure, the perception association setting can also be a setting for perception mode / measurement RS / object / application scenario / measurement / report / coordinated gNB / becoming a UE.

[0584] Changes: such as Figure 30 As in the example, after S305, the SMF can also receive messages such as acknowledgments / feedbacks from more than one target gNB (S406), and then send a sensing handover request acknowledgment (SENSING HANDOVERREQUEST ACKNOWLEDGE) to the source gNB (S407). More than one target gNB can also autonomously determine the sensing association setting and send that setting to the SMF within a message such as an acknowledgment / feedback. The source gNB can either continue sensing association behavior based on information from the SMF, or it can stop (S408). This continuity can also include updates.

[0585] The mobility process of a source gNB to one or more target gNBs fails if the SMF receives a failure / fault message from one or more target gNBs within a specific time period, or if the source gNB receives a NACK from the SMF within a specific time period, or if the source gNB fails to receive any message from the SMF. This failure / fault can also be requested / managed / executed in the source gNB or the SMF. The procedure in case of a failed request (sensing handover request) can also follow at least one of the following options.

[0586] Option 1: This process depends on the implementation of NW.

[0587] Option 2: SMF retransmits the request to more than one target gNB of the same type.

[0588] Option 3: SMF re-executes the decision of more than one target gNB and sends the request to more than one new target gNB.

[0589] Option 4: The source gNB resends the request to the SMF.

[0590] A sensing handover request may also include at least one of the following pieces of information.

[0591] ◇At least one of the following: a perceived object ID, information associated with other objects, an environment ID, environment association information, a motion ID, and motion association information.

[0592] ◇ An ID associated with the sensing application scenario, and at least one of the sensing service categories.

[0593] ◇Sensing source gNB ID.

[0594] ◇At least one of the following: one or more target gNB IDs and one or more target gNBs' perception modes.

[0595] ◇ (In the source gNB) One or more IDs of the perceived pattern / method used.

[0596] ◇ (Source gNB) Perception RS settings.

[0597] ◇ (In the source gNB) Setting up the measurement / reporting of perception.

[0598] ◇ (In the source gNB) One or more object (ID) perceptual measurements.

[0599] ◇ (From gNB) Sensing measurement results for at least one of the corresponding measurement quantity and measurement timing.

[0600] ◇The history of perception measurement results and the corresponding perception patterns / methods.

[0601] ◇The ID of the condition / event that triggered it.

[0602] ◇ (From gNB) Other settings / information associated with one or more perception tasks for one or more object IDs.

[0603] ◇ Estimate information related to sensing errors. For example, errors caused by incomplete calibration between the transmit and receive antennas in a gNB.

[0604] ◇The current resolution of perception.

[0605] The Sensing Handover Request Acknowledgment (SENSING HANDOVER REQUEST ACKNOWLEDGE) may also include at least one of the following pieces of information.

[0606] ◇ An indicator for at least one of the following: release of initial perception settings, cessation of initial perception behavior, and continuation / update of initial perception behavior.

[0607] ◇At least one of the following: a perceived object ID, information associated with other objects, an environment ID, environment association information, a motion ID, and motion association information.

[0608] ◇ An ID associated with the sensing application scenario, and at least one of the sensing service categories.

[0609] ◇One or more target gNB IDs. This can include any of the following: the ID of one gNB used for monostatic sensing; two gNB IDs used for gNB-gNB bistatic sensing; or gNB IDs used for gNB-UE bistatic sensing or UE-gNB bistatic sensing, with or without a paired UE ID. The two gNB IDs can also be the ID of one primary gNB and the ID of one coordinating gNB.

[0610] ◇ (In the target gNB) One or more IDs of the perceived pattern / method used.

[0611] ◇ (In the target gNB) Perception RS settings.

[0612] ◇ (In the target gNB) Setting up the measurement / reporting of perception.

[0613] ◇ (In the target gNB) One or more object (ID) perceptual measurements.

[0614] ◇(In the target gNB) Other settings / information associated with one or more perception tasks for one or more object IDs.

[0615] ◇ Estimate information related to sensing errors. For example, the error caused by incomplete calibration between the transmit and receive antennas in the target gNB.

[0616] ◇The current resolution of perception.

[0617] According to this implementation, in gNB single-base sensing, when the mobility process is triggered by the source gNB and the target gNB is determined by the SMF, the mobility process can be appropriately executed.

[0618] <Implementation Method C2b>

[0619] This implementation relates to a combination of options 2 and 4 of implementation C1 in gNB monobase sensing (the case where the mobility process is triggered by the source gNB and the target gNB is determined by the source gNB).

[0620] like Figure 31 As in the example, the SMF can also send settings (pre-settings) for the sensing / mobility process to the source gNB (S501). If the condition / event in implementation C1 occurs in the gNB (S502), the source gNB can also determine at least one of one or more target gNBs and one or more corresponding target sensing modes (S503). This determination can also follow at least one of the following options.

[0621] Option 1: This decision depends on the implementation. For example, the decision is based on an estimate of the object's movement path.

[0622] Option 2: This decision is based on settings / instructions from the SMF. These settings / instructions may also be specific to an application scenario and at least one of an object.

[0623] The source gNB can also directly send a sensing handover request message (S504) to one or more target gNBs. One or more target gNBs can also process the sensing handover request information, continue participating in the sensing task for the indicated object ID (S505), and send a sensing handover request acknowledgment message (S506) to the source gNB. The source gNB can also continue or stop the sending / measuring of sensing measurements RS (S507). This continuation can also include updates.

[0624] The content of the sensing handover request and the sensing handover request acknowledgment can also be the same as in implementation C2a. The sensing handover request acknowledgment can include messages such as confirmation / feedback, or it can include sensing association settings from one or more target gNBs.

[0625] According to this implementation, in gNB monobase sensing, when the mobility process is triggered by the source gNB and the source gNB determines the target gNB, the mobility process can be executed appropriately.

[0626] <Implementation Method C2c>

[0627] This implementation relates to a combination of options 1 and 3 of implementation C1 in gNB single-base sensing (the case where the mobility process is triggered by the SMF and the target gNB is determined by the SMF).

[0628] like Figure 32 As in the example, the source gNB can also send a sensing measurement report to the SMF (S601). In the SMF, if the condition / event in implementation C1 occurs (S602), the SMF can determine at least one of the target gNBs and corresponding target sensing modes (S603), and send a sensing HANDOVER REQUEST message to the target gNBs, or send a new sensing request with a reset of sensing association settings to the target gNBs (S604). Then, the SMF can also send a sensing setting release (sensing HANDOVER CONFIG RELEASE) message to the source gNB (S607). The source gNB can either continue sensing association behavior based on the SMF's settings, or stop it (S608). This continuation can also include updates.

[0629] Changes: After S605, SMF can also receive messages such as acknowledgments / feedbacks from more than one target gNB (S606) and send sensing configuration (SENSING CONFIG) to the source gNB (S607).

[0630] The content of the sensing handover request can also be the same as in implementation C2a. The sensing handover request can also include sensing configuration information for one or more target gNBs. This sensing configuration information may include, for example, at least one of the following: the sensing mode / method used (for the target gNB), sensing RS settings, sensing measurement / reporting settings, one or more sensing measurements for one or more object IDs, and other settings / information associated with the sensing task for one or more object IDs (e.g., the coordinating gNB ID or the ID of the paired UE).

[0631] The content of the Sensing Configuration / Sensing Handover Configuration Release can include instructions to the source gNB regarding whether to continue / release / update the settings / behaviors associated with Sensing, or it can include Sensing configuration information for one or more target gNBs.

[0632] According to this implementation, in gNB single-base sensing, when the mobility process is triggered by the SMF and the target gNB is determined by the SMF, the mobility process can be appropriately executed.

[0633] <Implementation Method C2d>

[0634] This implementation relates to a combination of options 1 and 3 of implementation C1 in gNB single-base sensing (the case where the mobility process is triggered by the SMF and the target gNB is determined by the SMF).

[0635] like Figure 33 As in the example, the source gNB can also send a sensing measurement report to the SMF (S701). In the SMF, if the condition / event in implementation C1 occurs (S702), the SMF can also determine at least one of the target gNBs and corresponding target sensing modes (S703) and send a sensing handover configuration message to the source gNB (S704). The source gNB can also directly send a sensing handover request to one or more target gNBs (S705). Here, the source gNB can also directly forward certain information from the sensing handover configuration message via the sensing handover request. After processing the Sensing Handover Request (SENSING HANDOVER REQUEST) information, one or more target gNBs continue to participate in the sensing task for the indicated object ID (S706) and send a Sensing Handover Request Acknowledgment (SENSING HANDOVER REQUEST ACKNOWLEDGE) message to the source gNB (S707). The source gNB can also continue or stop the sending / measuring behavior of the Sensing Measurement RS based on the instruction from the Sensing Handover Configuration (SMF) (S708). This continuation can also include updates.

[0636] When the SMF determines the target gNB, it is preferable for the SMF to directly set the target gNB (implementation C2c).

[0637] The content of the sensing handover configuration can be the same as that in implementation C2c, or it can include at least one of the following pieces of information.

[0638] ◇At least one of the following: a perceived object ID, information associated with other objects, an environment ID, environment association information, a motion ID, and motion association information. The motion can also be the motion of an object.

[0639] ◇ID associated with the sensing application scenario.

[0640] ◇One or more target gNB IDs. This can include the ID of one gNB used for monostatic sensing, two gNB IDs used for gNB-gNB bistatic sensing, and any of the gNB IDs used for gNB-UE bistatic sensing or UE-gNB bistatic sensing, with or without a paired UE ID. The two gNB IDs can also be the ID of one primary gNB and the ID of one coordinating gNB.

[0641] ◇More than one ID of the perceived pattern / method used in more than one target gNB.

[0642] ◇ (In the target gNB) Perception RS settings.

[0643] ◇ (In the target gNB) Setting up the measurement / reporting of perception.

[0644] ◇ (In the target gNB) One or more object (ID) perceptual measurements.

[0645] ◇(In the target gNB) Other settings / information associated with one or more perception tasks for one or more object IDs.

[0646] ◇ Estimate information related to sensing errors. For example, the error caused by incomplete calibration between the transmit and receive antennas in the target gNB.

[0647] ◇Continue / update / stop the perception association settings for the source gNB, and update the perception association settings for the source gNB. The updated perception association settings may also include changes to the perception resolution within a specific perception service category.

[0648] ◇Perception service category.

[0649] The Sensing Handover Configuration can include either the content from the Sensing Handover Request or the content from the Sensing Handover Request Acknowledgement.

[0650] The mobility process from the source gNB to the target gNB fails if the source gNB receives a NACK / failure / malfunction from the SMF, or if the reception of any message from the SMF fails within a specific time period. This failure / malfunction can also be requested / managed / executed in the SMF or the source gNB. The process in the event of a failed request (sensing handover configuration / sensing handover request) can also follow at least one of the following options.

[0651] Option 1: This process depends on the implementation of NW.

[0652] Option 2: SMF retransmits the request to more than one target gNB of the same type.

[0653] Option 3: SMF re-executes the decision of more than one target gNB and sends the request to more than one new target gNB.

[0654] According to this implementation, in gNB single-base sensing, when the mobility process is triggered by the SMF and the target gNB is determined by the SMF, the mobility process can be appropriately executed.

[0655] <Analysis C2>

[0656] In gNB-UE bistatic sensing with object / UE movement, consider the following operations.

[0657] ◇When the UE loses tracking of an object (tracking of the object fails), consider the following scenarios.

[0658] ―◇Scenario 1: If the gNB can identify UE tracking failure through at least one of the periodic measurement reports of the UE's sensing RS, the location of the object, and the location of the UE, the gNB can set up another UE for sensing by periodically setting up the sensing of another UE.

[0659] ―◇Scenario 2: New reports related to failures / malfunctions of UE-based tracking can also be introduced (implementation C3 described later).

[0660] ◇ (When the gNB can distinguish between gNB tracking failure and UE tracking failure,) even if the gNB loses track of an object (object tracking failure), the gNB can still detect one or more target gNBs with or without a new sensing mode, and trigger a mobility procedure for continuous sensing of that object (implementation C4 described later). Even if the gNB cannot distinguish between gNB tracking failure and UE tracking failure, the condition in the UE of implementation 3 is still met, and as long as the UE reports to the gNB or the condition in the gNB of implementation C4 is met, the gNB can decide whether to trigger / how to trigger the mobility procedure.

[0661] ◇The relationship between existing handover for communication and mobility for sensing can also be defined (implementation C5 described later).

[0662] In UE-gNB bistatic sensing with object / UE movement, consider the following operations.

[0663] ◇In the event that a UE loses track of an object (object tracking fails), the gNB can identify the sensing status based on gNB-based measurements. The gNB can also configure another UE for sensing purposes through periodic sensing configurations.

[0664] ◇ (When the gNB can distinguish between gNB tracking failure and UE tracking failure,) when the gNB loses track of the object (object tracking failure), the gNB can also discover one or more target gNBs with or without a new sensing mode, triggering a mobility process for continuous sensing function for that object (implementation C4 described later).

[0665] ◇The relationship between existing handover for communication and mobility for sensing can also be defined (implementation C5 described later).

[0666] <Implementation Method C3>

[0667] This implementation relates to the process in gNB-UE bistatic sensing when UE tracking fails (resulting in sensing / tracking failure / performance degradation in the UE).

[0668] The conditions / events that may trigger at least one of the following UE-based reports may also follow at least one of the following options 3-x: perception fault, perception change, UE change, indication of failure to track the set object, and indication of reduced accuracy of perception task.

[0669] Option 3-1: For a Type 1 measurement associated with a directly perceived resource measurement result, the event occurs when the measured result / value / quantity / accuracy / probability is lower or higher than a defined / set threshold, or falls within a defined / set range. The Type 1 measurement may also follow at least one of Implementation Methods B1 to B4. The Type 1 measurement may also be measured / calculated by the UE.

[0670] Option 3-2: For a Type 2 measurement associated with a perception result for a specific application scenario, the event occurs when the measured result / value / quantity / accuracy / probability is lower or higher than a defined / set threshold, or falls within a defined / set range. The Type 2 measurement may also follow at least one of Implementation Methods B1 to B4. The Type 2 measurement may also be measured / calculated by the UE.

[0671] —◇Change 1: An event can be a situation where the measured result / value / quantity / accuracy / probability is lower (poor) or higher (good) than a defined / set threshold, or falls within a defined / set range, lasting for a specific period of time, or it can occur only a specific number of times. The specific time or the specific number of times (threshold) can be defined in the specification or set through RRC IE.

[0672] ―◇Change 2: The event is valid only if one or more objects are considered. The number of objects can be defined in the specification or set via RRC IE.

[0673] ―◇Change 3: For different multiple measurements, either a common single condition / event can be applied, or multiple dedicated conditions / events can be applied separately.

[0674] After an event is triggered, the UE may also send a new report to the gNB to indicate the possibility of a perceived fault. This report may also follow at least one of the following characteristics.

[0675] ◇This report may also contain at least one of the following information.

[0676] ―◇ Fault detection indicator.

[0677] —◇At least one of the following: a perceived object ID, information associated with other objects, an environment ID, environment association information, a motion ID, and motion association information. The motion can also be the motion of an object.

[0678] —◇At least one of the ID associated with the sensing application scenario and the sensing service category.

[0679] ―◇Sensory measurement results.

[0680] —◇ Existing L1 / L3 measurement results for communication.

[0681] ―◇Triggering event ID.

[0682] ―◇The ID of the candidate target gNB, and the measurement results of the existing L1 / L3 used for communication.

[0683] ―◇Perceptual resolution being processed.

[0684] ◇The content of the report can also be the same as the measurement / reporting behavior of the UE for the sensing RS in at least one of Implementations B1 to B4. Here, a new event can also be introduced to trigger the sensing result report.

[0685] ◇The report format can also be RRC IE / MAC CE / UCI.

[0686] According to this implementation, in gNB-UE bistatic sensing, the UE is able to appropriately report tracking failures / malfunctions.

[0687] <Implementation Method C4a>

[0688] This implementation relates to the triggering of a source gNB-based mobility process in dual-base sensing when gNB tracking fails (resulting in sensing / tracking failure / performance degradation in the UE).

[0689] The source gNB may also trigger a mobility procedure based on at least one of a UE-based report or a measurement / estimate based on that gNB. This triggering may also follow at least one of the following options.

[0690] Option 1: The source gNB uses the measurement / reporting settings for gNB-UE bistatic sensing to reset another UE within the coverage area.

[0691] Option 2: The source gNB uses the same procedure as in implementation C2a / C2b to send a sensing handover request to the SMF or one or more target gNBs. One or more target gNBs may also follow any of scenarios 1 to 6 in implementation C1. After receiving feedback / instructions from the SMF, the SMF may instruct the gNB to reset another UE used for gNB-UE bibase sensing, or it may instruct another gNB used for communicating with the same source UE.

[0692] The content of the sensing handover request can also be the same as in implementation C2a / implementation C2b. This content can also follow several of the following characteristics.

[0693] ◇In gNB-UE bistatic sensing, this content may further include at least one of the following pieces of information.

[0694] ―◇The ID of the UE performing the sensing measurement.

[0695] —◇Perception measurement reports from the UE, or processed measurement results from the source gNB.

[0696] —◇ Existing L1 / L3 measurement results for communication.

[0697] —◇Estimated perception error associated information in this case. For example, the error caused by incomplete synchronization between the gNB and the UE.

[0698] ◇In UE-gNB dual-base sensing, this content may further include at least one of the following information.

[0699] ―◇Send the UE ID of the sensing RS.

[0700] ―◇Sensing measurement results or processed measurement results based on the source gNB.

[0701] —◇Estimated perception error associated information in this case. For example, the error caused by incomplete synchronization between the gNB and the UE.

[0702] The content of the Sensing Handover Request Acknowledgment (SENSING HANDOVER REQUEST ACKNOWLEDGE) can also be the same as in Implementation C2a / Implementation C2b. The failure / malfunction process (when a NACK is received or during a specific period of standby) can also be the same as in Implementation C2a / Implementation C2b. If it is decided to maintain gNB-UE dual-base sensing, the content of the Sensing Handover Request Acknowledgment (SENSING HANDOVER REQUEST ACKNOWLEDGE) can also include at least one of the following: whether another UE using the source gNB for gNB-UE dual-base sensing has been discovered, whether a handover has been initiated (via the existing RRCReconfiguration message within the Sensing Handover Request Acknowledgment (SENSING HANDOVER REQUEST ACKNOWLEDGE) from the source gNB / UE to another target gNB, and the corresponding configuration signaling.

[0703] According to this implementation, in bistatic sensing, the source gNB can appropriately trigger a mobility process in the event of gNB tracking failure.

[0704] <Implementation Method C4b>

[0705] This implementation relates to the triggering of an SMF-based mobility process in the event of gNB tracking failure in bistatic sensing.

[0706] The SMF can also use the same process as in implementation C2c / C2d, determining the triggering of the mobility procedure based on reports from the UE or gNB, and identifying the target gNB. More than one target gNB can also follow any of scenarios 1 to 6 in implementation C1. The SMF can either decide to reset the source gNB for another UE used for gNB-UE bibase sensing, or (if it is decided to maintain gNB-UE bibase sensing) decide to cause the source gNB to perform a handover from the source gNB / UE to the target gNB.

[0707] The content of the sensing handover request can also be the same as in implementation C2c. The content of the sensing handover configuration can also be the same as in implementation C2d. The failure / malfunction process (when a NACK is received or during standby for a specific period of time) can also be the same as in implementation C2d. The content of the sensing handover request / sensing handover configuration can also further include additional information such as the ID of the participating sensing UE.

[0708] According to this implementation, in bistatic sensing, the SMF can appropriately trigger a mobility process in the event of gNB tracking failure.

[0709] <Implementation Method C5>

[0710] This implementation relates to the relationship between existing handover for communication and mobility for sensing.

[0711] In the case where a UE is configured to both communication and sensing (a UE receives both communication and sensing configurations), the UE can also be configured separately for measurement reports for communication and measurement reports for sensing.

[0712] The procedures / signaling used for communication and sensing mobility can also follow at least one of the following options.

[0713] Option 1: Different / dedicated procedures / signaling. In this case, dedicated handover signaling / procedures can also be introduced for communication and sensing based on the corresponding measurement reports.

[0714] Option 2: Common Procedures / Signaling. In this case, the gNB / UE can also perform a common handover based on a joint study of measurement reports used for communication and sensing. The gNB / UE can also perform a common handover for communication and sensing based on at least one measurement report used for communication and sensing.

[0715] Whether the gNB triggers the perceived mobility process can also follow at least one of the following options.

[0716] Option 1: Whether the gNB triggers the perceived mobility process, based on a joint study of measurement reports (conditions / events) used for communication and perception.

[0717] Option 2: Whether the gNB triggers the perceived mobility process based on the measurement report (condition / event) used for perception.

[0718] Option 3: If the existing communication mobility process is triggered by the UE, the perceived mobility process is also triggered / executed by the UE.

[0719] According to this implementation, the relationship between existing handover for communication and mobility for sensing can be clearly defined.

[0720] <Analysis C3>

[0721] In gNB-gNB bistatic sensing accompanied by object / UE movement, the gNB may lose track of the object / UE (object tracking failure). Prior to this, the gNB may also trigger a mobility procedure. This triggering may also follow at least one of the following scenarios.

[0722] ◇Scenario 1: The coordinating gNB is changed (implementation C6 described later). This can also mean that the source gNB and the gNB-gNB bistatic sensing mode are maintained.

[0723] ◇Scenario 2: At least one of the source gNB, or the source gNB, the coordinating gNB, and the sensing mode is changed (implementation C7 described later). This may not necessarily mean that the target gNB is in a gNB-gNB bistatic sensing mode.

[0724] <Implementation Method C6>

[0725] This implementation involves a mobility process based on gNB-gNB bistatic sensing.

[0726] The activation of the mobility process can also be determined by at least one of the following options.

[0727] Option 1: SMF.

[0728] Option 2: Source gNB. This decision can depend on the implementation or on the conditions / events of implementation method C1.

[0729] Option 3: Coordinate gNB. This decision may depend on the implementation or be based on the conditions / events of implementation method C1.

[0730] The methods / modes for mobility, target gNB, and target perception can also be determined by at least one of the following options.

[0731] Option 4: SMF.

[0732] Option 5: Source gNB.

[0733] Option 6: Coordinate gNB.

[0734] ◇In determining the method / mode of perception, SMF is preferred.

[0735] ◇In cases where the SMF determines the triggering of the mobility process, it is preferable that the SMF also determines the target gNB.

[0736] ◇For more than one target gNB, any one of cases 1 to 6 of implementation method C1 can be followed.

[0737] In Option 1, the SMF can also determine more than one new target coordination gNB. The SMF can also send an instruction / setting to the source gNB for the ID of more than one new target gNB for coordination with more than one gNB. This instruction / setting can also be the same as the sensing handover configuration in implementation C2d. The mobility process can also follow at least one of the following options 1-x.

[0738] Option 1-1: To establish a new sensing pair for a gNB, the source gNB can send a sensing handover request to one or more new target gNBs, or it can send a sensing association setting reset to one or more new target gNBs. This signaling / procedure can also be the same as in implementation C2d. Prior to this, the source gNB can also send a setting / instruction to the initial coordinating gNB to release the sensing settings.

[0739] ◇Options 1-2: The SMF can send a sensing handover request along with the source gNB's ID and sensing association settings from that source gNB to one or more new target gNBs, or it can send a sensing association setting reset to one or more new target gNBs. This signaling / process can also be the same as in implementation C2c.

[0740] In options 2 / 3, the same process as in implementation C2a / C2b can also be reused. The content of the sensing handover request can also further include the estimated sensing error in this case (e.g., the error of incomplete synchronization between the source gNB and the coordinating gNB).

[0741] According to this implementation, gNB-gNB bistatic sensing can appropriately perform mobility processes.

[0742] <Implementation Method C7>

[0743] This implementation relates to another approach to the mobility process of gNB-gNB bistatic sensing.

[0744] The mobility process can also be triggered by at least one of options 1 to 3 in implementation C6.

[0745] The methods / modes for mobility, target gNB, and target perception can also be determined by at least one of options 4 to 6 in implementation C6.

[0746] In Option 1, the SMF can also determine one or more new target coordination gNBs and the perception mode for the corresponding objects. The SMF can also send instructions / settings for one or more new target gNBs (with IDs) to the source gNB. These instructions / settings can also be the same as the perception handover configuration in implementation C2d. The mobility process can also follow at least one of the following options 1-x.

[0747] Option 1-1: The source gNB can also send a sensing handover request to more than one new target gNB. The source gNB can also continue / stop / update sensing association behavior after receiving a sensing handover request acknowledgment from more than one new target gNB.

[0748] ◇Options 1-2: The SMF can also send a Sensing Handover Request to more than one new target gNB. The source gNB can also continue / stop / update its sensing association behavior.

[0749] ◇One or more target gNBs can also follow any of cases 1 to 6 of implementation method C1. That is, one or more new target gNBs can be either just a new target gNB (the sensing mode can be determined as gNB monostatic sensing), or multiple new target gNBs (both a new primary gNB and a new coordinating gNB) (the sensing mode can also be maintained as gNB-gNB bistatic sensing), or a UE that is paired with the new target gNB (the sensing mode can also be determined as gNB-UE or UE-gNB bistatic sensing).

[0750] ◇In the aforementioned options 1-x, the sensing handover request or sensing handover configuration may include an indication / configuration for only the new target gNB, or an indication / configuration for multiple new target gNBs (both the new primary gNB and the new coordinating gNB), or an indication / configuration for the UE that is paired with the new target gNB.

[0751] In options 2 / 3, the same process as in implementation C2a / C2b can also be reused / reused. More than one target gNB can also follow any of scenarios 1 to 6 of implementation C1. That is, more than one new target gNB can be either a new target gNB (the sensing mode can be determined as gNB monostatic sensing), multiple new target gNBs (both a new primary gNB and a new coordinating gNB) (the sensing mode can also be maintained as gNB-gNB bistatic sensing), or a UE paired with a new target gNB (the sensing mode can also be determined as gNB-UE or UE-gNB bistatic sensing). The sensing handover request can also further include the estimated sensing error in this case (e.g., the error of incomplete synchronization between the source gNB and the coordinating gNB).

[0752] According to this implementation, gNB-gNB bistatic sensing can appropriately perform mobility processes.

[0753] <Implementation Method C8>

[0754] This implementation involves constraints on changes in perception patterns during mobility processes.

[0755] When changed to a sensing mode (target sensing mode, target mode, second mode) different from that of the source gNB, the target gNB determined by the source gNB or the SMF can also be at least one of the following options.

[0756] ◇ Option 1: One or more gNBs with (supporting / being set / using) the same sensing mode as that of the source gNB.

[0757] ◇ Option 2: One or more gNBs with (supporting / being set / using) the same or different sensing mode as that of the source gNB.

[0758] In the sensing mode during the mobility process, there can also be rules for the sensing mode of the source gNB and the sensing modes of one or more target gNBs. These rules can be defined in the specification, set / indicated, or reported as capability information. These rules can also follow at least one of the options in the following examples.

[0759] ◇ Example 1: When the sensing mode of the source gNB is gNB single - base sensing, the sensing mode of one or more target gNBs is either gNB single - base sensing or gNB - gNB double - base sensing. <*

[0760] ◇ Example 2: When the sensing mode of the source gNB is gNB - UE double - base sensing, the sensing mode of one or more target gNBs is either gNB - UE double - base sensing or UE - gNB double - base sensing.

[0761] ◇ Example 3: When the sensing mode of the source gNB is gNB single - base sensing, the sensing mode of one or more target gNBs is any one of gNB single - base sensing, gNB - gNB double - base sensing, gNB - UE double - base sensing, and UE - gNB double - base sensing.

[0762] ◇ Example 4: When the sensing mode of the source gNB is gNB - UE double - base sensing, the sensing mode of one or more target gNBs is any one of gNB - gNB double - base sensing, gNB - UE double - base sensing, UE - gNB double - base sensing, and gNB - gNB double - base sensing.

[0763] ◇ Example 5: The sensing mode of one or more target gNBs depends on the capabilities of the target gNB. This capability can also be to support gNB single - base sensing / full - duplex communication.

[0764] According to this embodiment, an appropriate sensing mode can be applied during the mobility process.

[0765] <NW node (network node)>

[0766] like Figure 34 As in the example, NW node 31 may also have a control unit 310 and a transmit / receive unit 320. The control unit 310 performs the processes / operations described in each embodiment and controls the transmit / receive unit 320. The transmit / receive unit 320 has a transmission path interface for at least one of the core network 30, base station 10, and other NW nodes 31. The hardware structure of NW node 31 may also be the same as that of base station 10 and user terminal 20 described later. NW node 31 may also include extended LMF / new SMF / new AMF / SMF / SF / base station 10 (gNB).

[0767] When information (e.g., measurement results, processing results) based on measurements of signals used for sensing (e.g., sensing RS) meets conditions (e.g., conditions / events), the control unit 310 can also control changes (e.g., mobility procedures) to at least one of the base station 10 used for sensing, the terminal 20 used for sensing, and the sensing mode (e.g., sensing mode / method). The transmission and reception unit 320 can also transmit and receive at least one of the messages for the changes (e.g., at least one of sensing handover request, sensing handover request confirmation, sensing handover setting, and sensing handover request release).

[0768] The base station 10 can also transmit and receive the signal (e.g., gNB single-base sensing). The change can also change the base station to one or more other target base stations.

[0769] Alternatively, the transmitter (e.g., gNB / UE, primary gNB / UE) transmits the signal, and the receiver (e.g., other gNB / UE, coordinating gNB / UE) receives the signal (e.g., bistatic sensing). The modification may also change at least one of the transmitters and receivers, from a source base station (e.g., source gNB) 10 to one or more other target base stations (e.g., target gNB) 10.

[0770] In the case where the base station (e.g., source gNB) 10 is changed to the target base station (e.g., target gNB) 10, the change may also be based on the constraint between the mode (e.g., the sensing mode before the change) and the second sensing mode in the target base station (e.g., the sensing mode after the change), changing the mode to the second mode.

[0771] <Supplement>

[0772] [Notification of information to the UE]

[0773] The notification of any information from the network (NW) (e.g., base station (BS)) to the UE in the above-described embodiments (in other words, the reception of any information from the BS in the UE) can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.

[0774] In the case of notification by a MAC CE, the MAC CE can also be identified by the inclusion of a new Logical Channel ID (LCID) in the MAC subheader, which is not specified in the existing standard.

[0775] In the case of notification by DCI, the notification may also be made through specific fields of DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to DCI, the format of DCI, etc.

[0776] Furthermore, the notification of any information to the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0777] [Notification from UE]

[0778] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information in the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0779] In the case of notification by a MAC CE, the MAC CE can also be identified by the inclusion of a new LCID, which is not specified in the existing standard, in the MAC subheader.

[0780] In cases where the above notification is made by the UCI, PUCCH or PUSCH can also be used to send the above notification.

[0781] Furthermore, the notification of any information from the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0782] [Regarding the application of each implementation method]

[0783] At least one of the above-described implementation methods can also be applied under certain conditions. These conditions can be specified in the specification or communicated to the UE / BS using higher-layer signaling / physical layer signaling (RRC IE / MAC CE / UCI).

[0784] The specific conditions mentioned above can also represent at least one of the following:

[0785] ◇Activation of at least one of the above-described embodiments.

[0786] At least one of the above-described implementation methods may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability.

[0787] This specific UE capability can also represent at least one of the following:

[0788] ◇The UE supports specific processes / processes / operations / controls / information related to at least one of the above-described implementation methods.

[0789] ◇Application scenarios supported by UE.

[0790] ◇Perception modes / methods supported by UE.

[0791] ◇At least one of the sensed measurement quantity supported by the UE and its corresponding accuracy.

[0792] ◇Perception measurement report settings supported by UE.

[0793] ◇The number of sensed objects supported by the UE for each application scenario (maximum number).

[0794] ◇At least one of the following: a condition / event supported by the UE for use in mobility procedures, and a report triggered by such condition / event.

[0795] ◇At least one of the following: a perception RS supported by the UE and a perception RS setting supported by the BS.

[0796] ◇Sensed RS measurement capability supported by UE.

[0797] ◇Perceptual error improvement methods supported by UE.

[0798] ◇The UE supports at least one of the mobility processes for sensing and the mobility processes supported by the BS.

[0799] UE capabilities can also be rewritten as BS capabilities. UE capabilities can also be reported to the server / LMF / SF / BS / another UE. BS capabilities can also be reported to the server / LMF / SF / UE / another BS.

[0800] This specific BS capability can also represent at least one of the following:

[0801] ◇BS supports specific processes / processes / operations / controls / information related to at least one of the above-described implementations.

[0802] ◇Application scenarios supported by BS.

[0803] ◇Perception patterns / methods supported by BS.

[0804] ◇At least one of the sensing measurement quantity supported by BS and its corresponding accuracy.

[0805] ◇Sensory measurement report settings supported by BS.

[0806] ◇ The number of perceived objects (maximum number) supported by BS for each application scenario.

[0807] ◇At least one of the following: a condition / event supported by BS for use in the mobility process, and a report triggered by that condition / event.

[0808] ◇At least one of the following: a perception RS supported by a BS and a perception RS setting supported by a BS.

[0809] ◇Sensing RS measurement capability supported by BS.

[0810] ◇Perceptual error improvement methods supported by BS.

[0811] ◇BS supports the identification of more than one target BS for mobility processes.

[0812] ◇BS supports mobility processes for perception and at least one of the mobility processes supported by BS.

[0813] Furthermore, the aforementioned specific UE capabilities can be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities that are specific to each frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), capabilities that are specific to each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities that are specific to each subcarrier spacing (SCS), or capabilities that are features (FS) or features per component carrier (FSPC).

[0814] Furthermore, the aforementioned specific UE capabilities can be either the ability to be applied across all duplex modes (commonly regardless of the duplex mode) or the capability for each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0815] Furthermore, at least one of the above-described embodiments can also be applied when the UE is set / activated / triggered by specific information associated with the above-described embodiments (or performs the operations of the above-described embodiments) via higher-layer signaling / physical layer signaling. This specific information can also represent at least one of the following:

[0816] ◇ indicates information on activating / deactivating the operation of the above-described implementation method.

[0817] ◇RRC parameters used in specific versions or specific RATs. In Rel.YY (e.g., YY is 18 or higher), the RRC parameter that activates operation XXX can also be represented as XXX_rYY (XXX-rYY).

[0818] Even if at least one of the aforementioned specific UE capabilities is not supported or the aforementioned specific information is not set, the UE may, for example, apply the operation of Rel.15 / 16.

[0819] (Postscript)

[0820] With respect to one embodiment of this disclosure, the following invention is noted.

[0821] [Postscript 1]

[0822] A network node having:

[0823] The control unit controls changes to at least one of the sensing base station, the sensing terminal, and the sensing mode, based on conditions met by information measured from the signals used for sensing; and

[0824] The sending and receiving unit performs at least one function of sending and receiving messages for the changes.

[0825] [Postscript 2]

[0826] As described in Appendix 1, the network nodes, wherein...

[0827] The base station transmits and receives the signal.

[0828] The change is to change the base station to one or more other target base stations.

[0829] [Postscript 3]

[0830] Network nodes as described in Appendix 1 or Appendix 2, wherein,

[0831] The transmitter transmits the signal, and the receiver receives the signal.

[0832] The change is to replace at least one source base station in the transmitter and the receiver with one or more other target base stations.

[0833] [Postscript 4]

[0834] As described in any one of Annexes 1 to 3, the network node, wherein,

[0835] When the base station is changed to the target base station, the change is based on the constraint between the mode and the second sensing mode in the target base station, changing the mode to the second mode.

[0836] (Postscript)

[0837] With respect to one embodiment of this disclosure, the following invention is noted.

[0838] [Postscript 1]

[0839] A terminal having:

[0840] A receiving unit receives signals for sensing; and

[0841] The control unit controls the transmission of a report of the perceived fault when the information measured based on the signal meets the conditions.

[0842] [Postscript 2]

[0843] The terminal as described in Appendix 1, wherein,

[0844] The condition is the degradation of the performance of tracking the perceived object.

[0845] [Postscript 3]

[0846] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0847] Following the report, the control unit modifies one or more base stations that transmit the sensing signals.

[0848] [Postscript 4]

[0849] The terminal as described in any one of Annexes 1 to 3, wherein,

[0850] The report includes at least one of the following: the fault, the object, the sensed environment, the object's action, the application scenario of the sensed information, the category of the sensed information, the measurement results, the measurement results of the communication signal, the conditions, candidates for base stations that transmit the signal used for sensed information, and the resolution of the sensed information.

[0851] (Postscript)

[0852] With respect to one embodiment of this disclosure, the following invention is noted.

[0853] [Postscript 1]

[0854] A terminal having:

[0855] The receiving unit receives communication and sensing settings; and

[0856] The control unit controls the transmission of a first report for the measurement used in the communication and a second report for the measurement used in the sensing.

[0857] [Postscript 2]

[0858] The terminal described in Appendix 1, wherein,

[0859] Following 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.

[0860] [Postscript 3]

[0861] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0862] The control unit performs the process of changing one or more base stations associated with the perception separately from the process of changing one or more base stations associated with the communication.

[0863] [Postscript 4]

[0864] The terminal as described in any one of Annexes 1 to 3, wherein,

[0865] The control unit performs the process of changing one or more base stations associated with the communication and the sensing.

[0866] (Wireless communication system)

[0867] The structure of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0868] Figure 35 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one implementation. The wireless communication system 1 (which may also be referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized by the Third Generation Partnership Project (3GPP).

[0869] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also 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.

[0870] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the 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.

[0871] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0872] The wireless communication system 1 may also include: a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. User terminals 20 may also be located within at least one cell. The configuration and number of each cell and user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0873] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0874] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these; for example, FR1 can also be equivalent to a frequency band higher than FR2.

[0875] In addition, in each CC, the user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

[0876] Multiple base stations 10 can also be connected via wired (e.g., fiber optic cable based on the Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

[0877] Base station 10 may also be connected to core network 30 via other base stations 10 or directly. Core network 30 may include at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0878] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, a single network node may provide multiple functions. Furthermore, communication with external networks (e.g., the Internet) can also be conducted via the DN.

[0879] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0880] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0881] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be applied in the wireless access methods of UL and DL.

[0882] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0883] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0884] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and high-level control information can also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) can be transmitted via PBCH.

[0885] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0886] Additionally, the DCI for scheduling PDSCH can also be called DL allocation, DL DCI, etc., and the DCI for scheduling PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0887] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0888] A search space can also correspond to a PDCCH candidate that matches one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. disclosed herein can be rewritten interchangeably.

[0889] Uplink control information (UCI) can also be transmitted via PUCCH, including at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). Random access preambles used for establishing a connection with the cell can also be transmitted via PRACH.

[0890] In addition, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, various channels may be described without the word "physical".

[0891] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, as DL-RS, cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS) can also be transmitted.

[0892] Synchronization signals can be, for example, at least one of the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0893] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0894] The core network 20 (servers within the core network 20) ​​can also send sensing-related requests or auxiliary data. The base station 10 can also, based on the requests, control at least one of reporting the sensing results, activating or deactivating the transmission of the reference signal used for sensing, setting or updating the reference signal, activating or deactivating the sensing measurement, and updating the sensing method. The user terminal 20 can also, based on the requested mutual assistance data, forward any one of the sensing capabilities and the sensing results.

[0895] (Base station)

[0896] Figure 36 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0897] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0898] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0899] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0900] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of a transmitter / receiver, RF circuitry, baseband circuitry, filters, phase shifters, measurement circuitry, transmitting / receiving circuitry, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0901] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0902] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0903] The transmitting / receiving unit 120 can also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 can also receive the aforementioned uplink channel, uplink reference signal, etc.

[0904] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0905] The transmitting and receiving unit 120 (transmitting processing unit 1211) may, for example, perform processing at the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer (e.g., RLC retransmission control), and Medium Access Control (MAC) layer (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 110, and generate a bit string to be transmitted.

[0906] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing, Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0907] For baseband signals, the transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc., to the wireless frequency band, and transmit the wireless frequency band signals through the transmitting and receiving antenna 130.

[0908] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, demodulate baseband signals, etc., for signals in the wireless frequency band that are received by the transmitting and receiving antenna 130.

[0909] For the acquired baseband signal, the transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to acquire user data.

[0910] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also 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 can also be output to the control unit 110.

[0911] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0912] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of the transmitting and receiving unit 120, the transmitting and receiving antenna 130 and the transmission path interface 140.

[0913] The transmitting and receiving unit 120 can also transmit and receive at least one signal for sensing (e.g., sensing RS). When the information measured based on the signal (e.g., measurement result, processing result) meets a condition (e.g., condition / event), the control unit 110 can also control the change (e.g., mobility process) of at least one of the base station for sensing, the terminal for sensing, and the sensing mode (e.g., sensing mode / method).

[0914] The transmitting and receiving unit 120 can also transmit signals for sensing (e.g., sensing RS). The control unit 110 can also control the reception of reports of the sensed faults if measurements based on the signals (e.g., measurement results, processing results) meet conditions (e.g., conditions / events).

[0915] The transmitting and receiving unit 120 can also transmit communication and sensing settings. The control unit 110 can also control the reception of a first report of the measurement used for the communication and the reception of a second report of the measurement used for sensing.

[0916] (User terminal)

[0917] Figure 37 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0918] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0919] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0920] The control unit 210 can also control signal generation, mapping, etc. The control unit 210 can also control transmission, reception, measurement, etc., using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmission / reception unit 220.

[0921] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0922] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0923] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0924] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0925] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0926] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0927] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0928] Furthermore, whether or not to apply DFT processing can be based on the transform precoding settings. For a certain channel (e.g., PUSCH), if transform precoding is activated, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0929] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0930] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0931] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to obtain user data.

[0932] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can also 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 can also be output to the control unit 210.

[0933] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZPCSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0934] Alternatively, the transmitting unit and receiving unit of the user terminal 20 in this disclosure may also be composed of at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0935] The transmitting and receiving unit 220 can also receive signals for sensing (e.g., sensing RS). When the information measured based on the signal (e.g., measurement result, processing result) meets the conditions (e.g., condition / event), the control unit 210 can also control the transmission of a report of the sensed fault (implementation C3).

[0936] The condition could also be a deterioration in the performance of tracking the perceived object.

[0937] Following the report, the control unit 210 may also change one or more base stations that transmit the signals used for sensing.

[0938] The report may also include at least one of the following: the fault, the object, the sensed environment, the object's action, the sensed application scenario, the sensed category, the measurement result, the measurement result of the communication signal, the condition, a candidate base station for transmitting the sensed signal, and the sensed resolution.

[0939] The transmitting and receiving unit 220 can also receive communication and sensing settings. The control unit 210 can also control the transmission of a first report for the measurement used for the communication and the transmission of a second report for the measurement used for sensing (Embodiment C5).

[0940] Following at least one of the first report and the second report, the control unit 210 may also change one or more base stations associated with at least one of the communication and the sensing.

[0941] The control unit 210 may also execute the process of changing one or more base stations associated with the sensing separately from the process of changing one or more base stations associated with the communication.

[0942] The control unit 210 can also perform the process of changing one or more base stations associated with the communication and the sensing.

[0943] (Hardware structure)

[0944] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0945] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. As described above, the implementation method is not particularly limited.

[0946] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 38 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0947] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0948] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0949] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading out and writing data in the memory 1002 and the storage device 1003.

[0950] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be configured as a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least some of the control unit 110 (210), the transmit / receive unit 120 (220), etc. described above may also be implemented by the processor 1001.

[0951] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated by the processor 1001; similar implementations can be made for other functional blocks.

[0952] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to one embodiment of this disclosure.

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

[0954] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmitting and receiving unit 120 (220) and transmitting and receiving antenna 130 (230) can also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) can also be implemented by physically or logically separating the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0955] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0956] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

[0957] Furthermore, the base station 10 and the user terminal 20 can also 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), and a field-programmable gate array (FPGA), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0958] (Variation example)

[0959] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, can be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) can be interchanged. Additionally, a signal can also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) can also be referred to as cell, frequency carrier, carrier frequency, etc.

[0960] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitutes a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0961] Here, the parameter set can also refer to communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0962] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

[0963] A time slot can also contain multiple mini-time slots. Each mini-time slot can also consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (PUSCH) mapping type B.

[0964] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0965] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is to say, at least one of the subframe and TTI can be a subframe in the existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0966] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0967] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0968] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0969] A TTI with a duration of 1 ms can also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0970] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

[0971] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0972] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0973] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0974] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0975] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0976] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0977] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. In addition, "cell", "carrier", etc. in this disclosure can also be rewritten as "BWP".

[0978] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0979] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0980] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0981] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0982] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher layer to lower layer, and from lower layer to higher layer. Information, signals, etc., can also be input and output via multiple network nodes.

[0983] Input and output information, signals, etc., can be stored in a specific location (e.g., memory) or managed using management tables. Input and output information, signals, etc., can be overwritten, updated, or appended. Output information, signals, etc., can also be deleted. Input information, signals, etc., can also be sent to other devices.

[0984] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0985] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0986] Furthermore, notification of specific information (e.g., a "is X" notification) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0987] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0988] Whether it is called software, firmware, middleware, microcode, hardware description language, or any other name, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, program, subprogram, software module, application, software application, software package, routine, subroutine, object, executable file, execution thread, process, function, etc.

[0989] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0990] The terms "system" and "network" as used in this disclosure are interchangeable. "Network" may also refer to devices included in a network (e.g., base stations).

[0991] In this disclosure, the terms "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 amplitude", "beam angle", "antenna", "antenna element", "panel", "UE panel", "transmitting entity", and "receiving entity" are used interchangeably.

[0992] Furthermore, in this disclosure, the antenna port and the antenna port used for any signal / channel (e.g., the DeModulation Reference Signal (DMRS) port) can be mutually modified. In this disclosure, the resources and the resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.) can also be mutually modified. Additionally, resources may also include time / frequency / symbol / space / power resources. Moreover, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0993] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0994] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET Pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0995] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0996] Furthermore, in this disclosure, "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", "specific QCL type (e.g., type A, type D)" can also be rewritten in different ways.

[0997] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0998] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" and "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc., can also be interchanged. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationship can also be interchanged.

[0999] In this disclosure, the terms "Base Station (BS)", "Wireless 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", and "Component Carrier" are used interchangeably. There are also instances where terms such as macrocell, small cell, femtocell, and picocell are used to refer to base stations.

[1000] 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 divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​the base station providing communication services within that coverage area, as well as at least one of the base station subsystems.

[1001] In this disclosure, the act of a base station sending information to a terminal and the act of the base station instructing the terminal to perform control / operation based on that information can be rewritten in turn.

[1002] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "user equipment (UE)", and "terminal" are used interchangeably.

[1003] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[1004] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[1005] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, autonomous two-wheelers, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers, rickshaws, ships (bottles and other watercraft), airplanes, rockets, artificial satellites, drones, multi-rotor aircraft, quadcopters, balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[1006] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station may include a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may also be an IoT (Internet of Things) device such as a sensor.

[1007] Figure 39 This figure illustrates an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a speed 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 gear shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[1008] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a handlebar) and to steer at least one of the front wheel 46 and the rear wheel 47 based on the operation of the steering wheel operated by the user.

[1009] The electronic control unit 49 consists of a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63). Signals from various sensors 50-58 present in the vehicle are input into the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

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

[1011] The information service unit 59 comprises various devices such as a car navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[1012] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that implement output to the outside (e.g., display, speaker, LED light, touch panel, etc.).

[1013] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning devices (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) mapping), gyroscope systems (e.g., Inertial Measurement Unit (IMU)) and Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance or autonomous driving functions.

[1014] The communication module 60 can communicate with the microprocessor 61 and the constituent elements of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) between the microprocessor 61 and the memory (ROM, RAM) 62, and various sensors 50-58 in the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, electronic control unit 49, and the vehicle 40 via the communication port 63.

[1015] The communication module 60 is controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information between external devices via wireless communication. The communication module 60 can be located either inside or outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[1016] The communication module 60 can also wirelessly transmit to an external device at least one of the signals input to the electronic control unit 49 from the various sensors 50-58, information obtained based on those signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 can also contain information based on the aforementioned inputs.

[1017] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) sent from external devices and displays it to the information service unit 59 provided by the vehicle. The information service unit 59 can also be referred to as an information output unit (e.g., outputting information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH)).

[1018] Furthermore, the communication module 60 stores various information received from external devices into a memory 62 that can be utilized by the microprocessor 61. The microprocessor 61 can also control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, and various sensors 50-58 of the vehicle 40 based on the information stored in the memory 62.

[1019] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is rewritten as communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can also be rewritten as terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[1020] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[1021] In this disclosure, actions are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. Clearly, in a network containing one or more network nodes having a base station, various operations performed for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[1022] The various methods / implementations described in this disclosure can be used individually, in combination, or switched as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, with respect to the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[1023] The various methods / implementations described in this disclosure can also be applied to 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 a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other appropriate wireless communication methods, and next-generation systems extended, modified, established, or specified based on them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[1024] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise specified. In other words, the word "based on" means both "based on only" and "based on at least".

[1025] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[1026] The term "determining" as used in this disclosure can encompass a wide variety of actions. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining.

[1027] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[1028] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". In other words, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made. In this disclosure, "judgment (decision)" and the above-mentioned operations can also be rewritten interchangeably.

[1029] Furthermore, in this disclosure, "determine / determining" can be interchanged with "assume / assuming," "expect / expecting," and "consider / considering." Additionally, in this disclosure, "not assuming to proceed..." and "assuming not to proceed..." can also be interchanged.

[1030] In this disclosure, "expect" and "be expected" can be interchanged. For example, "expect(s)......" ("..." can also be expressed using a that-clause, to-infinitive, etc.) and "be expected......" can also be interchanged. "does not expect......" and "be not expected......" can also be interchanged. Furthermore, "An apparatus A is not expected......" and "Apparatus B other than apparatus A does not expect......" can also be interchanged (for example, if apparatus A is a UE, apparatus B can also be a base station).

[1031] The term "maximum transmit power" as used in this disclosure can refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[1032] As used in this disclosure, the terms "connected," "coupled," or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually "connected" or "coupled" elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, "connected" can also be rewritten as "access."

[1033] In this disclosure, when two elements are connected, it is possible to use more than one wire, cable, printed electrical connection, etc., and to use electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region as several non-limiting and non-inclusive examples, so as to be "connected" or "combined" with each other.

[1034] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other". Additionally, the term can also mean "A and B are different from C respectively". Terms such as "separate" and "combined" can also be interpreted in the same way as "different".

[1035] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusiveness. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[1036] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[1037] In this disclosure, expressions such as "below," "less than," "above," "more," and "equal to" can be rewritten interchangeably. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "fast," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be rewritten interchangeably. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "fast," "slow," "wide," and "narrow," when used as expressions with the prefix "i" (where i is any integer), are not limited to the positive, comparative, and superlative degrees, and can be rewritten interchangeably (for example, "highest" and "i-th highest" can also be rewritten interchangeably).

[1038] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[1039] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "based on A", "B during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be appropriately rewritten as nouns, gerunds, or ordinary sentences depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately following or immediately preceding). Moreover, a time offset can be applied to the time when A occurs. For example, "A" can also be interchanged with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the notified information.

[1040] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, occasion, resource, etc., can also be rewritten to each other.

[1041] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.< / maxno>

Claims

1. A network node having: The control unit controls changes to at least one of the sensing base station, the sensing terminal, and the sensing mode, based on conditions met by information measured from the signals used for sensing; and The sending and receiving unit performs at least one function of sending and receiving messages for the changes.

2. The network node as described in claim 1, wherein, The base station transmits and receives the signal. The change is to change the base station to one or more other target base stations.

3. The network node as described in claim 1, wherein, The transmitter transmits the signal, and the receiver receives the signal. The change is to replace at least one source base station in the transmitter and the receiver with one or more other target base stations.

4. The network node as described in claim 1, wherein, When the base station is changed to the target base station, the change is based on the constraint between the mode and the second sensing mode in the target base station, changing the mode to the second mode.

5. A method for sensing network nodes, comprising: The steps include controlling changes to at least one of the sensing base station, the sensing terminal, and the sensing mode, provided that information based on measurements of the signals used for sensing meets certain conditions; and The steps involve sending and receiving messages for the changes.

6. A base station, comprising: A transmitting and receiving unit, comprising at least one for transmitting and receiving signals for sensing; and The control unit controls changes to at least one of the base station for sensing, the terminal for sensing, and the sensing mode, provided that the information measured based on the signal meets the conditions.

Images