Communication system

Abstract

The communication system comprises: a base station corresponding to a fifth generation wireless access system; and a communication terminal that is connected to the base station, derives a sensing-related node from at least any one of the base station and the communication terminal on the basis of information on the sensing area in response to a sensing request from an external device, and transmits the sensing-related node to the communication terminal from among the derived nodes. A sensing transmission node that transmits a sensing resource and a sensing reception node that receives the sensing resource are determined.

Description

Communication system Technical Field

[0001] This disclosure relates to wireless communication technology. Background Technology

[0002] Within the 3GPP (3rd Generation Partnership Project), the standardization organization for mobile communication systems, the fifth-generation (hereinafter sometimes referred to as "5G") radio access system (e.g., Non-Patent Document 2) is discussed as a successor to Long Term Evolution (LTE) and Long Term Evolution Advanced (LTE-A), one of the fourth-generation radio access systems (see Non-Patent Document 1). The technology for the 5G radio band is called "New Radio Access Technology" ("New Radio" is abbreviated as "NR"). The NR system is discussed based on the LTE and LTE-A systems.

[0003] For example, in Europe, the organization METIS is summarizing the requirements for 5G (see Non-Patent Document 3). In 5G wireless access systems, for LTE systems, assuming a system capacity 1000 times greater, data transmission speed 100 times greater, data processing latency 1 / 5th, and simultaneous connection capacity of communication terminals 100 times greater, further reductions in power consumption and device cost can be listed as requirements (see Non-Patent Document 3).

[0004] To meet these requirements, discussions on 5G standards are ongoing within 3GPP (see Non-Patent Literature 4-23).

[0005] As an access method for NR, the downlink direction uses OFDM (Orthogonal Frequency Division Multiplexing), while the uplink direction uses OFDM and DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM). Furthermore, similar to LTE and LTE-A, the 5G system does not include line switching; it uses only packet communication.

[0006] In NR, higher frequencies can be used compared to LTE to increase transmission speed and reduce processing latency.

[0007] In NR, which sometimes uses frequencies higher than LTE, a narrower beam-shaped transmit / receive range is formed (beamforming) and the direction of the beam is changed (beam scanning), thereby ensuring cell coverage through capability mapping.

[0008] Figure 1 is used to illustrate the decisions regarding the frame structure of NR systems in 3GPP as described in Non-Patent Document 1 (Chapter 5). Figure 1 is an explanatory diagram showing the structure of a radio frame used in an NR communication system. In Figure 1, a radio frame is 10 ms. The radio frame is divided into 10 equal-sized subframes. The NR frame structure supports one or more numberologies, i.e., one or more subcarrier spacings (SCS). In NR, a subframe is 1 ms long, and a time slot consists of 14 symbols, regardless of the subcarrier spacing. Furthermore, the number of time slots contained in a subframe is one when the subcarrier spacing is 15 kHz, and the number of time slots in other subcarrier spacings increases proportionally to the subcarrier spacing (see Non-Patent Document 11 (3GPP TS38.211)).

[0009] Non-Patent Document 2 (Chapter 5) and Non-Patent Document 11 record decisions made in 3GPP related to channel structure in NR systems.

[0010] The Physical Broadcast Channel (PBCH) is a channel used for downlink transmission from a base station (hereinafter sometimes referred to as a "base station") to a mobile terminal device (hereinafter sometimes referred to as a "mobile terminal") or other communication terminal device (hereinafter sometimes referred to as a "communication terminal" or "terminal"). The PBCH is transmitted together with the downlink synchronization signal.

[0011] In NR, the downlink synchronization signal consists of a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS). The synchronization signal is transmitted from the base station as a synchronization signal burst (hereinafter sometimes referred to as an SS burst), at a specified period for a specified duration. An SS burst consists of synchronization signal blocks (hereinafter sometimes referred to as SS blocks) for each beam of the base station.

[0012] During the duration of an SS burst, the base station changes its beam to transmit SS blocks for each beam. An SS block consists of P-SS, S-SS, and PBCH.

[0013] The Physical Downlink Control Channel (PDCCH) is the downlink transmission channel from the base station to the communication terminal. The PDCCH transmits Downlink Control Information (DCI). The DCI includes resource allocation information for the Downlink Shared Channel (DL-SCH), one of the transmission channels described later; resource allocation information for the Paging Channel (PCH), another transmission channel described later; and HARQ (Hybrid Automatic Repeat reQuest) information related to the DL-SCH. Additionally, the DCI sometimes includes Uplink Scheduling Grant. The DCI sometimes includes response signals for uplink transmissions, namely Ack (Acknowledgement) / Nack (Negative Acknowledgement). Furthermore, to allow for flexible DL / UL handover within time slots, the DCI sometimes includes Slot Format Indication (SFI). PDCCH or DCI is also known as the L1 / L2 control signal.

[0014] In NR, there are time-domain and frequency-domain regions that can serve as candidates for containing PDCCH. This region is called the Control Resource Set (CORESET). The communication terminal monitors the CORESET to acquire the PDCCH.

[0015] The Physical Downlink Shared Channel (PDSCH) is the downlink transmission channel from the base station to the communication terminal. The PDSCH maps to the Downlink Shared Channel (DL-SCH) used as the transport channel and the PCH used as the transport channel.

[0016] The Physical Uplink Control Channel (PUCCH) is the uplink transmission channel from the communication terminal to the base station. PUCCH transmits Uplink Control Information (UCI). UCI includes response signals (Ack / Nack) for downlink transmissions, CSI (Channel State Information), and Scheduling Requests (SRs). CSI is composed of RI (Rank Indicator), PMI (Precoding Matrix Indicator), and CQI (Channel Quality Indicator) reports. RI refers to the rank information of the channel matrix in MIMO (Multiple Input Multiple Output). PMI refers to the information of the precoding matrix used in MIMO. CQI is quality information indicating the quality of received data or the quality of the communication line. UCI is sometimes transmitted via PUSCH (described later). PUCCH or UCI is also referred to as L1 / L2 control signals.

[0017] The Physical Uplink Shared Channel (PUSCH) is the uplink transmission channel from the communication terminal to the base station. The PUSCH maps the Uplink Shared Channel (UL-SCH) as one of the transmission channels.

[0018] The Physical Random Access Channel (PRACH) is an uplink transmission channel from a communication terminal to a base station. PRACH transmits the random access preamble.

[0019] Downlink reference signals (RS) are symbols known in NR (Normally Injectable) communication systems. There are four types of downlink reference signals: UE-specific reference signals (DM-RS), phase tracking reference signals (PT-RS), positioning reference signals (PRS), and channel state information reference signals (CSI-RS). As physical layer measurements for communication terminals, there are measurements of the received power (RSRP) and received quality (RSRQ) of the reference signals.

[0020] The uplink reference signal is also a known symbol in NR communication systems. Three types of uplink reference signals are defined: Demodulation Reference Signal (DM-RS), Phase Tracking Reference Signal (PT-RS), and Sounding Reference Signal (SRS).

[0021] The transport channel described in Non-Patent Document 2 (Chapter 5) will be explained. The broadcast channel (BCH) in the downlink transport channel is broadcast to the entire coverage area of ​​its base station (cell). The BCH is mapped to the physical broadcast channel (PBCH).

[0022] HARQ-based retransmission control is applied to the Downlink Shared Channel (DL-SCH). The DL-SCH can broadcast to the entire coverage area of ​​the base station (cell). The DL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also known as semi-persistent scheduling. To reduce the power consumption of communication terminals, the DL-SCH supports discontinuous reception (DRX). The DL-SCH is mapped to the Physical Downlink Shared Channel (PDSCH).

[0023] The Paging Channel (PCH) supports DRX of communication terminals to reduce power consumption. The PCH is requested to broadcast over the entire coverage area of ​​the base station (cell). The PCH is mapped to physical resources such as the Physical Downlink Shared Channel (PDSCH) that can be dynamically used for traffic.

[0024] HARQ-based retransmission control is applied to the Uplink Shared Channel (UL-SCH) in the uplink transport channel. UL-SCH supports dynamic or quasi-static resource allocation. Quasi-static resource allocation is also known as Configured Grant. UL-SCH is mapped to the Physical Uplink Shared Channel (PUSCH).

[0025] The Random Access Channel (RACH) is restricted to control information. RACH is subject to collision risks. RACH is mapped to the Physical Random Access Channel (PRACH).

[0026] The following explains HARQ. HARQ is a technique that improves the communication quality of a transmission line by combining Automatic Repeat Request (ARQ) and Forward Error Correction. HARQ has the following advantages: even for transmission lines where communication quality changes, retransmission can effectively enable error correction. In particular, during retransmission, the quality can be further improved by combining the initial received result with the retransmitted result.

[0027] Here's an example illustrating the retransmission method. When the receiving side cannot correctly decode the received data—in other words, when a CRC (Cyclic Redundancy Check) error occurs (CRC=NG)—a "Nack" is sent from the receiving side to the sending side. The sending side, upon receiving the "Nack," retransmits the data. When the receiving side can correctly decode the received data—in other words, when no CRC error occurs (CRC=OK)—a "ck" is sent from the receiving side to the sending side. The sending side, upon receiving the "Ack," sends the next data.

[0028] Other examples of retransmission methods are illustrated below. If a CRC error occurs at the receiving end, a retransmission request is sent from the receiving end to the sending end. The retransmission request is made via a switch of the NDI (New Data Indicator). The sending end, upon receiving the retransmission request, retransmits the data. If no CRC error occurs at the receiving end, no retransmission request is sent. If the sending end does not receive a retransmission request within a specified time, it is assumed that no CRC error occurred at the receiving end.

[0029] The logical channel described in Non-Patent Document 1 (Chapter 6) will be explained. The Broadcast Control Channel (BCCH) is a downlink channel used to broadcast system control information. The BCCH, as a logical channel, is mapped to either the broadcast channel (BCH) as a transmission channel or the downlink shared channel (DL-SCH).

[0030] The Paging Control Channel (PCCH) is a downlink channel used to transmit paging information and system information updates. The PCCH, as a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.

[0031] The Common Control Channel (CCCH) is a channel used to transmit control information between a communication terminal and a base station. The CCCH is used when there is no RRC connection between the communication terminal and the network. In the downlink direction, the CCCH is mapped to the Downlink Shared Channel (DL-SCH) used as a transport channel. In the uplink direction, the CCCH is mapped to the Uplink Shared Channel (UL-SCH) used as a transport channel.

[0032] The Dedicated Control Channel (DCCH) is a channel used to transmit dedicated control information between a communication terminal and the network in a one-to-one manner. The DCCH is used when there is an RRC connection between the communication terminal and the network. In the uplink, the DCCH is mapped to the Uplink Shared Channel (UL-SCH), and in the downlink, it is mapped to the Downlink Shared Channel (DL-SCH).

[0033] A Dedicated Traffic Channel (DTCH) is a channel used for sending user information and conducting one-to-one communication with the communication terminal. DTCH exists in both the uplink and downlink. In the uplink, DTCH is mapped to the Uplink Shared Channel (UL-SCH), and in the downlink, it is mapped to the Downlink Shared Channel (DL-SCH).

[0034] Location tracking of a communication terminal is performed on a unit consisting of one or more cells. Location tracking is used to locate the communication terminal even in standby mode, enabling calls to the terminal; in other words, it is performed to enable calls to the communication terminal. The area used for location tracking of this communication terminal is called the Tracking Area (TA).

[0035] In NR, calls from communication terminals within a range smaller than the tracking area are supported. This range is called the RAN Notification Area (RNA). Paging of communication terminals in the RRC_INACTIVE state, as described later, occurs within this range.

[0036] In NR, to support wider transmission bandwidths, carrier aggregation (CA) has been studied, which involves combining two or more component carriers (CCs). CA is described in Non-Patent Literature 1.

[0037] In the case of a CA (Communication Terminal), the UE, as a communication terminal, has a unique RRC (Remote Reference Cell) connection with the network (NW). Within the RRC connection, a serving cell provides NAS (Non-Access Stratum) mobility information and security input. This cell is called the Primary Cell (PCell). Secondary serving cells (SCells) are formed based on the UE's capabilities, together with the PCell, to create a group of serving cells. For a single UE, a group of serving cells is formed consisting of one PCell and one or more SCells.

[0038] Furthermore, 3GPP includes dual connectivity (DC), where the UE communicates with two base stations to further increase communication capacity. DC is described in non-patent documents 1 and 22.

[0039] Sometimes, one of the base stations performing dual connectivity (DC) is called the "Master Node (MN)," and the other is called the "Secondary Node (SN)." The serving cells comprised of the Master Nodes are sometimes collectively referred to as the Master Cell Group (MCG), and the serving cells comprised of the Secondary Nodes are sometimes collectively referred to as the Secondary Cell Group (SCG). In DC, the Master Cell in the MCG or SCG is called a Special Cell (SpCell or SPCell). The Special Cell in the MCG is called a PCell, and the Special Cell in the SCG is called the Primary SCG Cell (PSCell).

[0040] In addition, in NR, the base station pre-defines a portion of the carrier frequency band for the UE (hereinafter sometimes referred to as the Bandwidth Part (BWP)). The UE transmits and receives data with the base station in this BWP, thereby reducing the power consumption in the UE.

[0041] Furthermore, 3GPP has explored services (or applications) that support sidelink (SL) communication (also known as PC5 communication) in both the EPS (Evolved Packet System) and 5G core systems (described later) (see Non-Patent Documents 1, 2, 26-28). SL communication involves communication between terminals. Examples of services using SL communication include V2X (Vehicle-to-everything) and proximity services. In SL communication, in addition to direct communication between terminals, communication between the UE and the NW via a relay has also been proposed (see Non-Patent Documents 26, 28).

[0042] The physical channel used for SL (refer to Non-Patent Documents 2, 11) is described below. The Physical Sidelink Broadcast Channel (PSBCH) transmits information related to system synchronization and is sent from the UE.

[0043] The Physical Sidelink Control Channel (PSCCH) transmits control information from the UE for sidelink communication and V2X sidelink communication.

[0044] The Physical Sidelink Shared Channel (PSSCH) transmits data from the UE for sidelink communication and V2X sidelink communication.

[0045] The Physical Sidelink Feedback Channel (PSFCH) transmits HARQ feedback from the UE that received the PSSCH to the UE that sent the PSSCH.

[0046] The transmission channel used for SL (refer to Non-Patent Document 1) will be described. The sidelink broadcast channel (SL-BCH) has a predetermined transmission format and is mapped to the PSBCH, which is the physical channel.

[0047] The Sidelink Shared Channel (SL-SCH) supports broadcast transmission. SL-SCH supports both UE autonomous resource selection and resource allocation scheduled by the base station. While UE autonomous resource selection carries a risk of conflict, there are no conflicts when the UE allocates dedicated resources through the base station. Furthermore, SL-SCH supports dynamic link adaptation by modifying transmit power, modulation, and coding. SL-SCH is mapped to the Physical Channel Sequential Channel (PSSCH).

[0048] The logical channels used for SL (refer to Non-Patent Document 2) will be described. The Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel used to broadcast sidelink system information from one UE to other UEs. The SBCCH is mapped to the SL-BCH, which serves as the transport channel.

[0049] The Sidelink Traffic Channel (STCH) is a one-to-many traffic channel used to send user information from one UE to other UEs. The STCH is used only by UEs with sidelink communication capabilities and UEs with V2X sidelink communication capabilities. One-to-one communication between two UEs with sidelink communication capabilities is also achieved through the STCH. The STCH is mapped to the SL-SCH, which serves as the transport channel.

[0050] The Sidelink Control Channel (SCCH) is a control channel used to send control information from one UE to other UEs. The SCCH is mapped to the SL-SCH, which serves as the transport channel.

[0051] In LTE, SL communication only involves broadcast. In NR, in addition to broadcast, support for unicast and groupcast has also been studied for SL communication (see Non-Patent Document 27 (3GPP TS23.287)).

[0052] In SL's unicast and multicast communications, it supports HARQ feedback (Ack / Nack), CSI reports, and more.

[0053] In addition, 3GPP is studying Integrated Access and Backhaul (IAB), which uses wireless methods to serve as both access links between UEs and base stations and backhaul links between base stations (see Non-Patent Literature 2, 20, 29).

[0054] For mobile communication systems, some new technologies have been proposed. For example, a technology that integrates sensing (detecting objects using radio waves, etc.) and communication has been proposed (see Non-Patent Literature 30, 31).

[0055] Existing technical documents

[0056] Non-patent literature

[0057] Non-patent literature 1: 3GPP TS36.300 V17.5.0

[0058] Non-patent document 2: 3GPP TS38.300 V17.5.0

[0059] Non-patent literature 3: "Scenarios, requirements and KPIs for 5G mobile and wireless system", ICT-317669-METIS / D1.1

[0060] Non-patent literature 4: 3GPP TR23.799 V14.0.0

[0061] Non-patent literature 5: 3GPP TR38.801 V14.0.0

[0062] Non-patent document 6: 3GPP TR38.802 V14.2.0

[0063] Non-patent document 7: 3GPP TR38.804 V14.0.0

[0064] Non-patent document 8: 3GPP TR38.912 V16.0.0

[0065] Non-Patent Document 9: 3GPP RP-172115

[0066] Non-patent literature 10: 3GPP TS23.501 V18.2.2

[0067] Non-patent document 11: 3GPP TS38.221 V17.5.0

[0068] Non-patent document 12: 3GPP TS38.212 V17.5.0

[0069] Non-patent document 13: 3GPP TS38.213 V17.6.0

[0070] Non-patent document 14: 3GPP TS38.214 V17.6.0

[0071] Non-patent document 15: 3GPP TS38.321 V17.5.0

[0072] Non-patent document 16: 3GPP TS38.322 V17.3.0

[0073] Non-patent document 17: 3GPP TS38.323 V17.5.0

[0074] Non-patent document 18: 3GPP TS37.324 V17.0.0

[0075] Non-patent document 19: 3GPP TS38.331 V17.5.0

[0076] Non-patent document 20: 3GPP TS38.401 V17.5.0

[0077] Non-patent document 21: 3GPP TS38.413 V17.5.0

[0078] Non-patent document 22: 3GPP TS37.340 V17.5.0

[0079] Non-patent document 23: 3GPP TS38.423 V17.5.0

[0080] Non-patent document 24: 3GPP TS38.305 V17.5.0

[0081] Non-patent document 25: 3GPP TS23.273 V18.2.0

[0082] Non-patent document 26: 3GPP TR23.703 V12.0.0

[0083] Non-patent document 27: 3GPP TS23.287 V18.0.0

[0084] Non-patent document 28: 3GPP TS23.303 V17.1.0

[0085] Non-patent document 29: 3GPP TS38.340 V17.5.0

[0086] Non-patent document 30: 3GPP TR22.837 V19.0.0

[0087] Non-patent document 31: 3GPP RWS-230250 Summary of the Invention

[0088] The technical problem that the invention aims to solve

[0089] In mobile communication systems, in addition to communication with the UE, target detection through sensing has been proposed (see Non-Patent Documents 30 and 31). Sensed targets include non-UE targets such as intruders, obstacles, or non-UE targets (targets that do not have UE functionality), such as rivers or the atmosphere. Although location management functions are introduced into mobile communication systems (see Non-Patent Documents 24 and 25), the location management object in these functions is the UE. Therefore, location management functions cannot be simply applied to sensing. The specific methods required to perform sensing in mobile communication systems are not disclosed and are unclear. This leads to the problem that sensing processing cannot be performed in mobile communication systems.

[0090] In view of the above-mentioned problems, one of the purposes of this disclosure is to realize sensing processing in a communication system in addition to communication with the UE.

[0091] Technical means for solving technical problems

[0092] The communication system disclosed herein includes: a base station corresponding to a fifth-generation wireless access system; and a communication terminal connected to the base station, which, based on a sensing request from an external device and information about a sensing area, derives sensing-related nodes from at least any one of the base station and the communication terminal, and determines, from the derived nodes, a sensing transmitting node for transmitting sensing resources and a sensing receiving node for receiving sensing resources.

[0093] Invention Effects

[0094] According to this disclosure, in the communication system, in addition to communication with the UE, sensing processing can also be realized.

[0095] The purpose, features, aspects, and advantages of this disclosure will become more apparent from the following detailed description and accompanying drawings. Attached Figure Description

[0096] Figure 1 is an explanatory diagram showing the structure of a wireless frame used in an NR communication system.

[0097] Figure 2 is a block diagram showing the overall structure of a communication system 210 using the NR method discussed in 3GPP.

[0098] Figure 3 is a structural diagram of a DC based on a base station connected to the NG core.

[0099] Figure 4 is a block diagram showing the structure of the mobile terminal 202 shown in Figure 2.

[0100] Figure 5 is a block diagram showing the structure of the base station 213 shown in Figure 2.

[0101] Figure 6 is a block diagram showing the structure of the 5GC section.

[0102] Figure 7 is a flowchart illustrating the process from cell search to standby in a communication terminal (UE) in an NR-based communication system.

[0103] Figure 8 is a diagram illustrating an example of cell structure in an NR system.

[0104] Figure 9 is a connection structure diagram showing an example of the connection structure of a terminal in SL communication.

[0105] Figure 10 is a connection structure diagram illustrating an example of a base station connection structure that supports integrated access and backhaul.

[0106] Figure 11 is a conceptual diagram of sensing when the base station acts as the transmitting node of sensing resources and the UE acts as the receiving node of sensing resources.

[0107] Figure 12 is a conceptual diagram of sensing when the base station acts as the transmitting node of sensing resources and the receiving node of sensing resources.

[0108] Figure 13 is a conceptual diagram of sensing when the UE acts as the transmitting node of sensing resources and the base station acts as the receiving node of sensing resources.

[0109] Figure 14 is a conceptual diagram of sensing when the UE acts as the transmitting node of sensing resources and the UE acts as the receiving node of sensing resources.

[0110] Figure 15 is a diagram illustrating an example sequence of sensing processing in Implementation 1.

[0111] Figure 16 is a diagram illustrating an example sequence of sensing processing in Implementation 1.

[0112] Figure 17 is a diagram illustrating other sequence examples of sensing processing in Implementation 2.

[0113] Figure 18 is a diagram illustrating other sequence examples of sensing processing in Implementation 2.

[0114] Figure 19 is a diagram illustrating other sequence examples of sensing processing in Implementation 3.

[0115] Figure 20 is a diagram illustrating other sequence examples of sensing processing in Implementation 4.

[0116] Figure 21 is a diagram illustrating other sequence examples of sensing processing in Implementation 5.

[0117] Figure 22 is a diagram illustrating other sequence examples of sensing processing in Implementation 5. Detailed Implementation

[0118] Implementation method 1.

[0119] Figure 2 is a block diagram showing the overall structure of a communication system 210 using the NR method discussed in 3GPP. Figure 2 will be explained below. The radio access network is referred to as NG-RAN (Next Generation Radio Access Network) 211. The communication terminal device, i.e., the mobile terminal device (hereinafter referred to as "user equipment" UE) 202, can wirelessly communicate with the base station device (hereinafter referred to as "NR base station (NG-RAN NodeB) gNB)" 213, and uses wireless communication to transmit and receive signals. NG-RAN 211 consists of one or more NR base stations 213.

[0120] Here, "communication terminal device" includes not only mobile terminal devices such as mobile phone terminals, but also stationary devices such as sensors. In the following description, "communication terminal device" will sometimes be abbreviated as "communication terminal".

[0121] Between UE202 and NG-RAN 211, the AS (Access Stratum) protocol is terminated. AS protocols include, for example, RRC (Radio Resource Control), SDAP (Service Data Adaptation Protocol), PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical Layer). RRC is used for the control plane (hereinafter sometimes referred to as C-plane, C-Plane, or CP), SDAP is used for the user plane (hereinafter sometimes referred to as U-plane, U-Plane, or UP), and PDCP, MAC, RLC, and PHY are used for both the C-plane and U-plane.

[0122] The Radio Resource Control (RRC) protocol between UE202 and NR base station 213 performs broadcasting, paging, and RRC connection management. The states between NR base station 213 and UE202 in RRC include RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.

[0123] During RRC_IDLE, PLMN (Public Land Mobile Network) selection, System Information (SI) broadcasting, paging, cell re-selection, and mobility operations are performed. During RRC_CONNECTED, the mobile terminal has an RRC connection and can send and receive data with the network. Additionally, during RRC_CONNECTED, handover (HO) and neighbor cell determination (measurement) are performed. During RRC_INACTIVE, the connection between the 5G core unit 214 and the NR base station 213 is maintained while simultaneously performing System Information (SI) broadcasting, paging, cell re-selection, and mobility operations.

[0124] The gNB213 connects to the 5G core (hereinafter sometimes referred to as the "5GC unit") 214, which includes Access and Mobility Management Function (AMF), Session Management Function (SMF), or User Plane Function (UPF), via the NG interface. Control information and / or user data communication occurs between the gNB213 and the 5GC unit 214. The NG interface is a collective term for the N2 interface between the gNB213 and AMF220, the N3 interface between the gNB213 and UPF221, the N11 interface between AMF220 and SMF222, and the N4 interface between UPF221 and SMF222. One gNB213 can connect to multiple 5GC units 214. The gNBs213 are connected to each other via the Xn interface, enabling communication of control information and / or user data between them.

[0125] The 5GC unit 214 is a host device, specifically a host node, that controls the connection between the NR base station 213 and the mobile terminal (UE) 202, and allocates paging signals for one or more NR base stations (gNB) 213 and / or LTE base stations (E-UTRAN NodeB: eNB). Additionally, the 5GC unit 214 performs mobility control in the idle state. The 5GC unit 214 manages the tracking area list when the mobile terminal 202 is in the idle state, and in the inactive and active states. The 5GC unit 214 initiates the paging protocol by sending paging messages to cells belonging to the registered tracking area of ​​the mobile terminal 202.

[0126] gNB213 can form one or more cells. When one gNB213 forms multiple cells, each cell is configured to communicate with UE202.

[0127] The gNB213 can be divided into a Central Unit (CU) 215 and a Distributed Unit (DU) 216. A CU 215 constitutes one unit within the gNB213. One or more DUs 216 constitute one or more cells within the gNB213. A single DU 216 constitutes one or more cells. The CU 215 connects to the DU 216 via an F1 interface, facilitating communication of control information and / or user data between the CU 215 and DU 216. The F1 interface consists of an F1-C interface and an F1-U interface. The CU 215 handles the functions of various protocols including RRC, SDAP, and PDCP, while the DU 216 handles the functions of various protocols including RLC, MAC, and PHY. One or more Transmission Reception Points (TRPs) 219 are sometimes connected to the DU 216. The TRP 219 transmits and receives radio signals with the UE.

[0128] CU215 can be divided into CU (CU-C) 217 ​​for the C-side and CU (CU-U) 218 ​​for the U-side. CU-C 217 is configured as one unit within CU215. CU-U 218 is configured as one or more units within CU215. CU-C 217 connects to CU-U 218 via an E1 interface, facilitating control information communication between CU-C 217 and CU-U 218. CU-C 217 connects to DU216 via an F1-C interface, facilitating control information communication between CU-C 217 and DU216. CU-U 218 connects to DU216 via an F1-U interface, facilitating user data communication between CU-U 218 and DU216.

[0129] The 5G communication system may include the Unified Data Management (UDM) function and Policy Control Function (PCF) described in Non-Patent Document 10 (3GPP TS23.501). The UDM and / or PCF may be included in the 5GC section 214 in Figure 2.

[0130] In a 5G communication system, a Location Management Function (LMF) as described in Non-Patent Document 24 (3GPP TS38.305) can be configured. As disclosed in Non-Patent Document 25 (3GPP TS23.273), the LMF can be connected to the base station via the AMF.

[0131] In 5G communication systems, the non-3GPP interworking function (N3IWF) described in Non-Patent Document 10 (3GPP TS23.501) may also be included. The N3IWF can terminate the access network (AN) between the user and the UE in non-3GPP access.

[0132] Figure 3 illustrates a structure based on a DC (dual connectivity) connected to the NG core. In Figure 3, solid lines represent U-Plane connections, and dashed lines represent C-Plane connections. In Figure 3, the primary base station 240-1 can be either a gNB or an eNB. Similarly, the secondary base station 240-2 can also be either a gNB or an eNB. For example, in Figure 3, the DC structure where the primary base station 240-1 is a gNB and the secondary base station 240-2 is an eNB is sometimes referred to as NG-EN-DC. Figure 3 shows an example where the U-Plane connection between the 5GC unit 214 and the secondary base station 240-2 is performed via the primary base station 240-1, but it can also be performed directly between the 5GC unit 214 and the secondary base station 240-2. Furthermore, in Figure 3, the core network connected to the LTE system or LTE-A system, namely the EPC (Evolved Packet Core), can replace the 5GC unit 214 in connecting to the primary base station 240-1. The U-Plane connection between the EPC and the auxiliary base station 240-2 can be established directly.

[0133] Figure 4 is a block diagram showing the structure of the mobile terminal 202 shown in Figure 2. The transmission processing of the mobile terminal 202 shown in Figure 4 will be described. First, control data from the control unit 310 and user data from the application unit 302 are sent to the protocol processing unit 301. Buffering of the control data and user data can be performed. This buffering can be provided in the control unit 310, the application unit 302, or the protocol processing unit 301. The protocol processing unit 301 performs protocol processing such as SDAP, PDCP, RLC, and MAC, for example, determining the transmission target base station in DC and assigning headers to various protocols. The protocol-processed data is transmitted to the encoding unit 304 for error correction and other encoding processing. Alternatively, data may be output directly from the protocol processing unit 301 to the modulation unit 305 without encoding processing. The data encoded by the encoding unit 304 is modulated in the modulation unit 305. Precoding for MIMO can also be performed in the modulation unit 305. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 306 and converted into a wireless transmission frequency. Then, the transmission signal is sent from antennas 307-1 to 307-4 to the base station 213. Figure 4 illustrates a case with four antennas, but the number of antennas is not limited to four.

[0134] Furthermore, the receiving process of the mobile terminal 202 is performed as follows: Wireless signals from the base station 213 are received via antennas 307-1 to 307-4. The received signal is converted from the wireless receiving frequency to a baseband signal by the frequency conversion unit 306, and demodulation processing is performed in the demodulation unit 308. Waiting calculations and multiplication processes can be performed in the demodulation unit 308. The demodulated data is transmitted to the decoding unit 309 for error correction and other decoding processing. The decoded data is transmitted to the protocol processing unit 301, where protocol processing such as MAC, RLC, PDCP, and SDAP is performed, including actions such as header removal in each protocol. Of the data after protocol processing, control data is transmitted to the control unit 310, and user data is transmitted to the application unit 302.

[0135] The series of processes of the mobile terminal 202 are controlled by the control unit 310. Therefore, although it is omitted in Figure 4, the control unit 310 is also connected to each of the units 302, 304 to 309.

[0136] Each part of the mobile terminal 202, such as the control unit 310, protocol processing unit 301, encoding unit 304, and decoding unit 309, is implemented, for example, by a processing circuit comprising a processor and a memory. For example, the control unit 310 is implemented by the processor executing a program describing a series of processes of the mobile terminal 202. The program describing the series of processes of the mobile terminal 202 is stored in the memory. Examples of memory are non-volatile or volatile semiconductor memories such as RAM (Random Access Memory), ROM (Read Only Memory), and flash memory. Each part of the mobile terminal 202, such as the control unit 310, protocol processing unit 301, encoding unit 304, and decoding unit 309, can be implemented by dedicated processing circuits such as FPGA (Field Programmable Gate Array), ASIC (Application Specific Integrated Circuit), and DSP (Digital Signal Processor). In Figure 4, the number of antennas used for transmitting and the number of antennas used for receiving in the mobile terminal 202 may be the same or different.

[0137] Figure 5 is a block diagram showing the structure of the base station 213 shown in Figure 2. The transmission processing of the base station 213 shown in Figure 5 will be explained. The EPC communication unit 401 transmits and receives data between the base station 213 and the EPC. The 5GC communication unit 412 transmits and receives data between the base station 213 and the 5GC (5GC unit 214, etc.). The other base station communication units 402 transmit and receive data with other base stations. The EPC communication unit 401, the 5GC communication unit 412, and the other base station communication units 402 exchange information with the protocol processing unit 403. Control data from the control unit 411, and user data and control data from the EPC communication unit 401, the 5GC communication unit 412, and the other base station communication units 402 are sent to the protocol processing unit 403. Buffering of control data and user data can be performed. The buffering of control data and user data can be provided in the control unit 411, the EPC communication unit 401, the 5GC communication unit 412, or the other base station communication units 402.

[0138] The protocol processing unit 403 performs protocol processing for SDAP, PDCP, RLC, MAC, etc., such as routing transmitted data in DC and assigning headers to various protocols. The protocol-processed data is transmitted to the encoding unit 405 for error correction and other encoding processing. Alternatively, data may be output directly from the protocol processing unit 403 to the modulation unit 406 without encoding processing. Furthermore, data can be transmitted from the protocol processing unit 403 to other base station communication units 402. For example, in DC, data transmitted from the 5GC communication unit 412 or the EPC communication unit 401 can be transmitted to other base stations, such as auxiliary base stations, via other base station communication units 402. The encoded data undergoes modulation processing in the modulation unit 406. Precoding for MIMO may also be performed in the modulation unit 406. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 407 and converted into a wireless transmission frequency. Then, using antennas 408-1 to 408-4, the transmission signal is transmitted to one or more mobile terminals 202. Figure 5 illustrates a case with four antennas, but the number of antennas is not limited to four.

[0139] Furthermore, the reception processing of base station 213 is performed as follows: Wireless signals from one or more mobile terminals 202 are received by antennas 408-1 to 408-4. The received signals are converted from the wireless receiving frequency to a baseband signal by frequency conversion unit 407, and demodulated in demodulation unit 409. The demodulated data is transmitted to decoding unit 410 for error correction and other decoding processing. The decoded data is transmitted to protocol processing unit 403, where protocol processing such as MAC, RLC, PDCP, and SDAP is performed, including actions such as header removal in each protocol. Of the data after protocol processing, control data is transmitted to control unit 411, 5GC communication unit 412, EPC communication unit 401, or other base station communication unit 402, and user data is transmitted to 5GC communication unit 412, EPC communication unit 401, or other base station communication unit 402. Data sent from other base station communication units 402 can be transmitted to 5GC communication unit 412 or EPC communication unit 401. This data could be, for example, uplink data transmitted from the DC to the 5GC communication unit 412 or the EPC communication unit 401 via other base stations.

[0140] The series of processes of base station 213 are controlled by control unit 411. Therefore, although omitted in Figure 5, control unit 411 is also connected to each of units 401, 402, 405 to 410, 412.

[0141] The various parts of base station 213, such as control unit 411, protocol processing unit 403, 5GC communication unit 412, EPC communication unit 401, other base station communication unit 402, encoding unit 405, and decoding unit 410, are implemented similarly to those of mobile terminal 202 by processing circuits comprising a processor and memory, or dedicated processing circuits such as FPGA, ASIC, and DSP. In Figure 5, the number of antennas used for transmission in base station 213 may be the same as the number of antennas used for reception, or they may be different.

[0142] As an example of the structure of CU215 shown in Figure 2, in addition to the encoding unit 405, modulation unit 406, frequency conversion unit 407, antennas 408-1 to 408-4, demodulation unit 409, and decoding unit 410 shown in Figure 5, a structure with a DU communication unit is sometimes used. The DU communication unit is connected to the protocol processing unit 403. The protocol processing unit 403 in CU215 performs protocol processing such as PDCP and SDAP.

[0143] As an example of the structure of DU216 shown in Figure 2, in addition to the EPC communication unit 401, other base station communication units 402, and 5GC communication unit 412 shown in Figure 5, a structure with a CU communication unit is sometimes used. The CU communication unit is connected to the protocol processing unit 403. The protocol processing unit 403 in DU216 performs protocol processing for PHY, MAC, RLC, etc.

[0144] Figure 6 is a block diagram showing the structure of the 5GC unit. Figure 6 shows the structure of the 5GC unit 214 shown in Figure 2 above. Figure 6 illustrates the configuration of the 5GC unit 214 shown in Figure 2, which includes an AMF, an SMF, and a UPF. In the example shown in Figure 6, the AMF may have the functions of a control plane control unit 525, the SMF may have the functions of a session management unit 527, and the UPF may have the functions of a user plane communication unit 523 and a data network communication unit 521. The data network communication unit 521 performs data transmission and reception between the 5GC unit 214 and the data network. The base station communication unit 522 performs data transmission and reception between the 5GC unit 214 and the base station 21 via the NG interface. User data sent from the data network is transmitted from the data network communication unit 521 to the base station communication unit 522 via the user plane communication unit 523, and then sent to one or more base stations 213. User data sent from base station 213 is transmitted from base station communication unit 522 to data network communication unit 521 via user plane communication unit 523, and then sent to data network.

[0145] Control data sent from base station 213 is transmitted from base station communication unit 522 to control plane control unit 525. Control plane control unit 525 can transmit control data to session management unit 527. Control data can be sent from data network. Control data sent from data network can be sent from data network communication unit 521 to session management unit 527 via user plane communication unit 523. Session management unit 527 can send control data to control plane control unit 525.

[0146] The user plane communication unit 523 includes a PDU processing unit 523-1, a mobility anchoring unit 523-2, etc., and performs overall processing for the user plane (hereinafter sometimes referred to as U-Plane). The PDU processing unit 523-1 processes data packets, such as sending and receiving packets with the data network communication unit 521 and sending and receiving packets with the base station communication unit 522. The mobility anchoring unit 523-2 is responsible for anchoring the data path when the UE moves.

[0147] The session management unit 527 manages the PDU sessions set up between the UE and the UPF. The session management unit 527 includes a PDU session control unit 527-1 and a UE IP address allocation unit 527-2. The PDU session control unit 527-1 manages the PDU sessions between the mobile terminal 202 and the 5GC unit 214. The UE IP address allocation unit 527-2 allocates IP addresses for the mobile terminal 202.

[0148] The control plane control unit 525 includes a NAS security unit 525-1, an idle state mobility management unit 525-2, etc., and performs overall processing for the control plane (hereinafter sometimes referred to as C-Plane). The NAS security unit 525-1 performs security protection for NAS (Non-Access Stratum) messages. The idle state mobility management unit 525-2 performs mobility management in standby state (idle state: RRC_IDLE state, or simply idle), generation and control of paging signals in standby state, addition, deletion, updating, retrieval of tracking areas for one or more mobile terminals 202 within the coverage area, and tracking area list management.

[0149] The series of processes in the 5GC unit 214 are controlled by the control unit 526. Therefore, although omitted in Figure 6, the control unit 526 is connected to each of the units 521-523, 525, and 527. Each unit of the 5GC unit 214, like the control unit 310 of the mobile terminal 202 described above, is implemented, for example, by a processing circuit comprising a processor and memory, or by a dedicated processing circuit such as an FPGA, ASIC, or DSP.

[0150] Next, an example of a cell search method in a communication system is shown. Figure 7 is a flowchart illustrating the general process of a communication terminal (UE) in an NR-based communication system from cell search to standby operation. If the communication terminal starts a cell search, in step ST601, the first synchronization signal (P-SS) and the second synchronization signal (S-SS) sent from surrounding base stations are used to obtain synchronization of time slot timing and frame timing.

[0151] P-SS and S-SS are collectively referred to as Synchronization Signal (SS). The Synchronization Signal (SS) contains a synchronization code that corresponds one-to-one with the PCI (Physical Cell Identifier) ​​assigned to each cell. In this discussion, the number of PCIs is set to 1008. The communication terminal uses these 1008 PCIs to achieve synchronization and detects (determines) the PCIs of synchronized cells.

[0152] In step ST602, the communication terminal receives the PBCH for the next cell to be synchronized. The BCCH on the PBCH maps to the MIB (Master Information Block), which contains cell structure information. Therefore, by receiving the PBCH and obtaining the BCCH, the MIB can be obtained. Information in the MIB includes, for example, the SFN (System Frame Number), scheduling information of SIB (System Information Block) 1, subcarrier spacing of SIB1, and DM-RS location information.

[0153] Additionally, the communication terminal obtains the SS block identifier via the PBCH. A portion of the bit string of the SS block identifier is contained in the MIB. The remaining bit string is contained in the identifier used to generate the DM-RS sequence accompanying the PBCH. The communication terminal uses the MIB contained in the PBCH and the DM-RS sequence accompanying the PBCH to obtain the SS block identifier.

[0154] Next, in step ST603, the communication terminal measures the received power of the SS block.

[0155] Next, in step ST604, the communication terminal selects the cell with the best reception quality from the more than one cell detected up to step ST603, for example, selecting the cell with the highest reception power, i.e., the optimal cell. Additionally, the communication terminal selects the beam with the best reception quality, for example, selecting the beam with the highest reception power in the SS block, i.e., the optimal beam. The selection of the optimal beam is, for example, using the reception power of the SS block identified by each SS block.

[0156] Next, in step ST605, the communication terminal receives the DL-SCH based on the scheduling information of SIB1 contained in the MIB, and obtains SIB1 (System Information Block) from the broadcast information BCCH. SIB1 contains information related to access to the cell, cell structure information, and scheduling information of other SIBs (SIBk: an integer k ≥ 2). In addition, SIB1 contains the Tracking Area Code (TAC).

[0157] Next, in step ST606, the communication terminal compares the TAC of SIB1 received in step ST605 with the TAC portion of the Tracking Area Identity (TAI) in the tracking area list already stored by the communication terminal. The tracking area list is also called the TAI list. TAI is identification information used to identify the tracking area, consisting of the MCC (Mobile Country Code), MNC (Mobile Network Code), and TAC (Tracking Area Code). MCC is the country code. MNC is the network code. TAC is the tracking area code number.

[0158] If the comparison result in step ST606 is the same as the TAC received in step ST605, and it is also included in the tracking area list, then the communication terminal enters standby mode in that cell. If the comparison shows that the TAC received in step ST605 is not included in the tracking area list, then the communication terminal requests a change of tracking area from the core network (EPC) containing the MME, etc., through that cell to perform a TAU (Tracking Area Update).

[0159] The devices constituting the core network (hereinafter sometimes referred to as core network-side devices) update the tracking area list based on the TAU request signal and the identification number (UE-ID, etc.) of the communication terminal sent from the communication terminal. The core network-side devices send the updated tracking area list to the communication terminal. The communication terminal rewrites (updates) its own TAC list based on the received tracking area list. After this, the communication terminal enters standby mode in the cell.

[0160] Next, examples of random access methods in a communication system are shown. In random access, 4-step random access and 2-step random access are used. Furthermore, for 4-step and 2-step random access, there are conflict-based random access, random access that may cause timing conflicts with other mobile terminals, and conflict-free random access.

[0161] An example of a conflict-based four-step random access method is shown. As step 1, the mobile terminal sends a random access preamble to the base station. The random access preamble can be selected by the mobile terminal from a predefined range, or it can be assigned separately to the mobile terminal and notified by the base station.

[0162] As a second step, the base station sends a random access response to the mobile terminal. The random access response includes uplink scheduling information used in the third step, and the terminal identifier used in the uplink transmission in the third step.

[0163] As step 3, the mobile terminal sends an uplink transmission to the base station. The mobile terminal uses the information obtained in step 2 in this uplink transmission. As step 4, the base station notifies the mobile terminal whether a conflict has been resolved. Mobile terminals notified of no conflict end the random access process. Mobile terminals notified of a conflict restart the process from step 1.

[0164] The conflict-free 4-step random access method differs from the conflict-based 4-step random access method in the following ways: First, before step 1, the base station pre-assigns a random access preamble and uplink scheduling to the mobile terminal. Second, notification regarding conflict resolution is not required in step 4.

[0165] An example of a collision-based two-step random access method is shown. In step 1, the mobile terminal sends a random access preamble and an uplink transmission to the base station. In step 2, the base station notifies the mobile terminal of whether a collision has occurred. Mobile terminals notified of no collision end the random access process. Mobile terminals notified of a collision restart the process from step 1.

[0166] The conflict-free two-step random access method differs from the conflict-based two-step random access method in the following way: Before step 1, the base station pre-assigns a random access preamble and uplink scheduling to the mobile terminal. Additionally, in step 2, the base station sends a random access response to the mobile terminal.

[0167] Figure 8 illustrates an example of a cell structure in NR. In an NR cell, a narrow beam is formed and its direction is changed for transmission. In the example shown in Figure 8, base station 750 uses beam 751-1 for transmission and reception with the mobile terminal at some times. At other times, base station 750 uses beam 751-2 for transmission and reception with the mobile terminal. Similarly, base station 750 uses one or more of beams 751-3 to 751-8 for transmission and reception with the mobile terminal. Thus, base station 750 constitutes a wide-range cell 752.

[0168] Figure 8 shows an example where the number of beams used by base station 750 is set to 8, but the number of beams can also be different from 8. Additionally, in the example shown in Figure 8, the number of beams used simultaneously by base station 750 is set to one, but it can also be multiple.

[0169] Beam identification uses the concept of QCL (Quasi-CoLocation) (refer to Non-Patent Document 14 (3GPP TS 38.214)). That is, it is identified by information indicating which reference signal (e.g., SS block, CSI-RS) the beam can be considered to be the same as. This information sometimes includes the type of information about the viewpoints that can be considered the same beam, such as information about Doppler shift, Doppler shift spread, average delay, average delay spread, and spatial Rx parameters (refer to Non-Patent Document 14 (3GPP TS 38.214)).

[0170] In 3GPP, sidelinks (SL) are supported for D2D (Device to Device) communication and V2V (Vehicle to Vehicle) communication (see Non-Patent Document 1 and Non-Patent Document 16). SL is specified through the PC5 interface.

[0171] In SL communication, in addition to broadcasting, support for PC5-S signaling was studied to support unicast and groupcast (see Non-Patent Document 27 (3GPP TS23.287)). For example, PC5-S signaling was implemented to establish SL, i.e., the link used to implement PC5 communication. This link is implemented in the V2X layer and is also known as a Layer 2 link.

[0172] In addition, support for RRC signaling is being researched in SL communication (see Non-Patent Document 27 (3GPP TS23.287)). RRC signaling in SL communication is also referred to as PC5 RRC signaling. For example, the ability to notify UEs of each other during PC5 communication, and the notification of AS layer settings for using PC5 communication for V2X communication, have been proposed.

[0173] Figure 9 illustrates an example of the connection structure of mobile terminals in SL communication. In the example shown in Figure 9, UE805 and UE806 exist within the coverage area 803 of base station 801. UL / DL communication 805 occurs between base station 801 and UE806. UL / DL communication 808 occurs between base station 801 and UE806. SL communication 810 occurs between UE805 and UE806. UE811 and UE812 exist outside the coverage area 803. SL communication 814 occurs between UE805 and UE811. Additionally, SL communication 816 occurs between UE811 and UE812.

[0174] As an example of communication between a UE and a NW via relay in SL communication, UE805, as shown in Figure 9, relays communication between UE811 and base station 801.

[0175] The UE performing relay sometimes uses the same structure as in Figure 4. Figure 4 is used to illustrate the relay processing in the UE. The relay processing of UE805 in communication from UE811 to base station 801 will be described. Radio signals from UE811 are received via antennas 307-1 to 307-4. The received signal is converted from the radio receiving frequency to a baseband signal by the frequency conversion unit 306, and demodulation processing is performed in the demodulation unit 308. In the demodulation unit 308, waiting calculations and multiplication processes can be performed. The demodulated data is transmitted to the decoding unit 309 for decoding processing such as error correction. The decoded data is transmitted to the protocol processing unit 301, where protocol processing for communication with UE811, such as MAC, RLC, etc., and operations such as header removal in each protocol are performed. Additionally, protocol processing for communication with base station 801, such as RLC, MAC, etc., and operations such as header assignment in each protocol are performed. In the protocol processing unit 301 of UE811, PDCP and SDAP protocol processing are sometimes also performed. The protocol-processed data is transmitted to the encoding unit 304 for error correction and other encoding processing. Alternatively, data may be output directly from the protocol processing unit 301 to the modulation unit 305 without encoding processing. The data encoded by the encoding unit 304 is modulated in the modulation unit 305. MIMO precoding may also be performed in the modulation unit 305. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 306 and converted into a radio transmission frequency. Then, the transmission signal is transmitted from antennas 307-1 to 307-4 to the base station 801.

[0176] The above content illustrates an example of UE805 relaying communication from UE811 to base station 801, but the same process is used in the relaying of communication from base station 801 to UE811.

[0177] 5G base stations can support Integrated Access and Backhaul (IAB) (see Non-Patent Documents 2, 20). An IAB-supporting base station (hereinafter sometimes referred to as an IAB base station) consists of a CU (IAB Host CU) acting as an IAB host, a DU (IAB Host DU) acting as an IAB host, and IAB nodes that connect to the IAB Host DU and the UE via radio interfaces. An F1 interface is provided between the IAB nodes and the IAB Host CU (see Non-Patent Document 2).

[0178] Figure 10 illustrates an example of IAB base station connections. IAB host CU901 is connected to IAB host DU902. IAB node 903 connects to IAB host DU902 using a radio interface. IAB node 903 also connects to IAB node 904 using a radio interface. That is, multi-level connections between IAB nodes are sometimes possible. UE905 connects to IAB node 904 using a radio interface. UE906 sometimes connects to IAB node 903 using a radio interface, and UE907 sometimes connects to IAB host DU902 using a radio interface. Multiple IAB host DU902s can connect to IAB host CU901, multiple IAB nodes 903 can connect to IAB host DU902, and multiple IAB nodes 904 can connect to IAB node 903.

[0179] In the connections between the IAB host DU and IAB nodes, and between IAB nodes, a BAP (Backhaul Adaptation Protocol) layer is set up (see Non-Patent Document 29). The BAP layer performs actions such as routing received data to the IAB host DU and / or IAB nodes, and mapping it to the RLC channel (see Non-Patent Document 29).

[0180] As an example of the structure of the IAB host CU, the same structure as CU215 is used.

[0181] As an example of the structure of the IAB host DU, it uses the same structure as DU216. In the protocol processing section of the IAB host DU, BAP layer processing is performed, such as assigning BAP headers to downlink data, routing for IAB nodes, and removing BAP headers from uplink data.

[0182] As an example of the structure of an IAB node, sometimes a structure other than the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown in Figure 5 is used.

[0183] Figures 5 and 10 are used to illustrate the transceiver processing in the IAB node. The transceiver processing of IAB node 903 in communication between IAB host CU901 and UE905 will be described. In uplink communication from UE905 to IAB host CU901, the radio signal from IAB node 904 is received through antenna 408 (part or all of antennas 408-1 to 408-4). The received signal is converted from the radio receiving frequency to a baseband signal by frequency conversion unit 407, and demodulation processing is performed in demodulation unit 409. The demodulated data is transmitted to decoding unit 410 for error correction and other decoding processing. The decoded data is transmitted to protocol processing unit 403, where protocol processing for communication with IAB node 904, such as MAC, RLC, etc., and actions such as header removal in each protocol, are performed. In addition, routing to the IAB host DU902 using the BAP header is performed, and protocol processing for communication with the IAB host DU902, such as assigning headers to each protocol, is carried out. The protocol-processed data is transmitted to the encoding unit 405 for error correction and other encoding processing. Alternatively, data may be output directly from the protocol processing unit 403 to the modulation unit 406 without encoding processing. The encoded data is modulated in the modulation unit 406. MIMO precoding may also be performed in the modulation unit 406. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 407 and converted into a radio transmission frequency. Then, the transmission signal is transmitted to the IAB host DU902 using antennas 408-1 to 408-4. The same processing is performed in downlink communication from the IAB host CU901 to the UE905.

[0184] In IAB node 904, the same send and receive processing is performed as in IAB node 903. In the protocol processing unit 403 of IAB node 903, as part of the BAP layer processing, such as assigning BAP headers in uplink communication and routing to IAB node 904, and removing BAP headers in downlink communication, etc.

[0185] In 3GPP mobile communication systems, in addition to communication with the UE, target detection via sensing has been proposed (see Non-Patent Documents 30, 31). Since the sensed targets include non-UE targets, the location management functions imported into 3GPP mobile communication systems cannot be simply applied to sensing. A specific method for performing sensing in a mobile communication system is needed.

[0186] This embodiment discloses a method for solving this problem.

[0187] Configure functions (which can also be nodes or entities) to manage sensing. For example, this could be called a Sensing Function (SF). This function manages sensing, including sensing requests, sensing settings, sensing termination, and other sensing-related processes. An SF can also function as a sensing server. By configuring functions to manage sensing, sensing processes can be managed uniformly, reducing the complexity of sensing procedures.

[0188] SF can be configured separately from other functions within NW. This reduces processing complexity and minimizes malfunctions. Alternatively, SF can be included within other functions within NW. This facilitates collaboration with other functions and reduces signaling load.

[0189] A sensing gateway function can also be configured. This sensing gateway function can be, for example, a gateway function from an external device acting as a sensing client (the entity requesting sensing) to the 3GPP mobile communication system. Furthermore, for example, the sensing gateway function can also be a routing function for sensing processing. A sensing gateway can also be configured. A sensing gateway can have a sensing gateway function. By configuring a sensing gateway function, external devices can easily perform sensing processing on the 3GPP mobile communication system.

[0190] LCS (Location Services) gateways (such as GMLC (Gateway Mobile Location Centre)) can have sensing gateway functionality. By using an LCS gateway, sensing processing and location management processing can be easily coordinated, for example. Furthermore, common gateways with other processing gateway functions can also be configured. Common gateways can also have sensing gateway functionality. Having sensing gateway functionality in a common gateway allows for easy, for example, coordination between other processing and sensing processing.

[0191] The sensing gateway can also be a PSA (PDU Session Anchor) UPF that functions as a sensing gateway. For example, it can be implemented when sensing results are sent via a UP. Sensing processing can be easily performed. Furthermore, the reliability of sensing processing can be improved.

[0192] The method for initiating sensing processing is disclosed. An external device can initiate sensing processing. The external device sends a sensing request to the SF (Sensing Component). The external device can also send a sensing request via a sensing gateway (hereinafter sometimes simply referred to as the gateway). The external device sends a sensing request to the gateway. The gateway sends a sensing request to the AMF (Agent Function). The AMF sends a sensing request to the SF. The SF can perform sensing processing upon receiving the sensing request.

[0193] The following are nine examples of information included in a sensing request.

[0194] (1) Information about the sensing target.

[0195] (2) Information about the sensing area.

[0196] (3) Information about sensing time.

[0197] (4) Information about the sensing results.

[0198] (5) Information about accuracy.

[0199] (6) Information about QoS (Quality of Service) and QoE (Quality of Experience).

[0200] (7) Determine the information of the sensing request.

[0201] (8) Information about the service.

[0202] (9) Combinations of (1) to (8).

[0203] (1) Information about the sensing target could be, for example, information about what is being sensed. The sensing target could be information about a region, such as a defined area or a defined direction. It could also be combined with information about the sensing area from (2). For example, information about the sensing target could be about an intruder, an obstacle, or a river, atmosphere, etc. For example, this information could be used in determining the sensing method in SF.

[0204] (2) Information about the sensing area may include, for example, information about a specified area, a specified direction, the vicinity of a specified base station, the vicinity of a specified UE, the relationship between a specified base station and a UE, the relationships between specified base stations, and the relationships between specified UEs. This information may be one or more. Information about the specified area may include, for example, latitude and longitude. Information about the specified area may also include altitude. Information about the specified direction may include, for example, the azimuth angle from a specified location or the azimuth from a specified location. Information about the vicinity of a specified base station may include, for example, information used to determine which base station. For example, information about the vicinity of a specified base station may include an identifier used to determine which base station. This is not limited to a base station; it may include a DU, a TRP, or a cell. Or it may include an antenna. Information about the vicinity of a specified UE may include, for example, information used to determine which UE. For example, information about the vicinity of a specified UE may include an identifier used to determine which UE. For example, this information may be used in determining which area should be sensed in the SF.

[0205] (3) Information about sensing time could include, for example, sensing start time, sensing end time, sensing period, period, etc. Information about sensing time could also be information about the predetermined sensing time. For example, the start and end of the sensing process can be determined in the SF, and this information can be used in that determination.

[0206] (4) Information about the sensing results could include, for example, information indicating the type of sensing result required. This information could include, for example, the target's 3D object detection result, 6D (3D coordinates + 3-axis direction) object detection result, the object's shape, size, position, speed, direction of movement, water level, humidity, air pressure, heart rate, etc. Information about the sensing results could also include time information. This time information could include, for example, the time the target was detected, the detection period, and the time the target could not be detected. For example, the sensing results can be exported in SF, and this information can be used in the export.

[0207] The information about accuracy in (5) can be information about the accuracy of the sensing results. The information about accuracy can be the accuracy of each precision of the sensing results disclosed in (4). For example, the sensing method can be determined in SF, and this information can be used in that determination.

[0208] (6) Information regarding QoS and QoE can be information about the QoS and QoE required for sensing. Information about QoS and QoE can include, for example, the reliability, accuracy (or precision), resolution, sensing latency, refresh rate of sensing results, missed detection rate, false alarm rate, etc. Information about QoS and QoE can also include, for example, KPIs (Key Performance Indicators) required for sensing. For example, this information can be used in determining the sensing method within SF.

[0209] (7) The information for determining the sensing request can be, for example, an identifier used to determine the sensing request. Multiple sensing requests can be executed. By setting the information for determining the sensing request, it is possible to determine which sensing request is being executed when multiple sensing requests are being executed. A maximum value can also be set for the number of sensing requests. By setting a maximum value, it is possible to avoid the sensing processing becoming complex and voluminous. For example, the information for determining the sensing request can be included in the sensing results. It is possible to determine which sensing request the sensing results are for.

[0210] (8) Information about the service could be, for example, information about the service (or application) that is being sensed. (8) Information about the service could be, for example, information used to determine the service. Information used to determine the service could be, for example, service identification information. (8) Information about the service could be, for example, information about the service that is making the sense request. For example, by receiving information about the service, SF can set the QoS and QoE applicable to the service.

[0211] It has been disclosed that external devices can also initiate sensing processing. As another method, an Application Function (AF) can also initiate sensing processing. The AF can send a sensing request to the SF. Sensing requests can also be sent via other Network Functions (NW). For example, the AF sends a sensing request to the Network Exposure Function (NEF). The NEF sends a sensing request to the AMF. The AMF sends a sensing request to the SF. The SF, upon receiving the sensing request, can perform sensing processing. Sensing processing can be initiated via the AF. For example, the AF can utilize sensing results obtained through sensing processing.

[0212] NW functions can also initiate sensing processing. An NW function could be, for example, NWDAF (Network Data Analysis Function). NWDAF can send sensing requests to SF. Sensing requests can also be sent via other NW functions. For instance, NWDAF can use sensing results obtained through sensing processing for NW data analysis.

[0213] NW functions can be, for example, RAN nodes or UEs. RAN nodes or UEs can send sensing requests to SF. Sensing requests can also be sent via other NW functions. For example, RAN nodes or UEs can use sensing results obtained through sensing processing to optimize wireless communication processing.

[0214] Management nodes can also initiate sensing processes. Management nodes can be, for example, MnS (Management Service) or OAM (Operation, Administration and Management). MnS or OAM can send sensing requests to SF. MnS or OAM can also send sensing requests to SF via other NW functions. For example, MnS or OAM can use sensing results obtained through sensing processes for NW management optimization of communication processing.

[0215] In sensing using a mobile communication system, a method for sensing a target using a UE or a base station has been proposed (refer to Non-Patent Document 31). Figures 11 to 14 are conceptual diagrams of sensing using a UE or a base station. Figure 11 shows the case where the base station acts as a transmitting node for the sensing resource (sensing resource), and the UE acts as a receiving node for the sensing resource. Figure 12 shows the case where both the base station and the sensing resource are transmitting and receiving nodes. Figure 13 shows the case where both the UE and the base station are transmitting and receiving nodes for the sensing resource. Figure 14 shows the case where both the UE and the sensing resource are transmitting and receiving nodes.

[0216] However, non-patent document 31 does not disclose any method for determining the UE or base station used for sensing. How to determine the UE or base station used for sensing becomes a problem.

[0217] Publicly disclose methods for solving this problem.

[0218] From information about the sensing area, UEs existing within the sensing area are derived. UEs located near the sensing area, UEs capable of performing sensing processes, or UEs capable of receiving sensing resources can also be derived. These UEs are referred to as sensing-related UEs (sensing-related communication terminals). Information about a specified area can be used as information about the sensing area. One or more UEs can be derived. Sensing-related UEs can also be derived as candidates for UEs receiving sensing resources (sometimes called receiving UEs).

[0219] LMF (Local Frequency Analysis) can derive sensing-related UEs from information about the sensing area. LMF identifies the UE's location information. By using LMF, sensing-related UEs can be determined. A sensing-related UE can be a UE with location information within a specified time period. A sensing-related UE can be a UE with the most recent location information. A sensing-related UE can be a UE performing location management or location measurement. Using UEs with more recent location information allows for more accurate sensing.

[0220] A node making a sensing request can send information about the sensing area to the LMF. The node making the sensing request can also request sensing-related UE information from the LMF. This request can include information about the sensing area. The request can also include information about the vicinity of the sensing area. Information about the sensing area could, for example, be its distance from a specified area. Using this information, the LMF can derive the sensing-related UE. The request can also include information about the sensing target. Using this information, for example, it can derive sensing-related UEs that are more suitable for the sensing request.

[0221] The LMF sends information about the derived sensing-related UEs to the nodes that request such information. For example, when a gateway requests sensing-related UE information, the LMF sends this information to the gateway. This information may include details such as UE identification, UE location management information (location, speed, etc.), whether the UE is within the sensing area, and the distance between the UE and the sensing area.

[0222] An interface is established between the sensing gateway and the LMF. The gateway can send a request to the LMF to provide sensing-related UE information. The gateway, upon receiving a sensing request from an external device, can also send a request to provide sensing-related UE information. The gateway has a routing function during sensing. This routing function can include the ability to select the target of the request to provide sensing-related UE information. The LMF, upon receiving the request to provide sensing-related UE information from the gateway, derives the sensing-related UE. The LMF sends information about the derived sensing-related UE to the gateway. Thus, the gateway can obtain information about the sensing-related UE.

[0223] The LMF can send information about the exported sensing-related UE to the SF. Information about the sensing-related UE can also be sent via a gateway. The gateway can have SF selection functionality (or routing functionality to the SF). Information about the sensing-related UE can also be sent via the AMF. The AMF can have SF selection functionality. The LMF sends information about the UE to the gateway. The gateway sends information about the UE to the AMF. The gateway can include this information in the sensing request sent to the AMF. The AMF sends information about the UE to the SF. The AMF can include this information in the sensing request sent to the SF.

[0224] The method disclosed describes how an LMF (Local Mesh Module) can derive and provide sensing-related UEs from information about the sensing area. However, this method is not limited to LMFs; any node possessing UE location information is acceptable. For example, when a UDM (Underlying Device Manager), GMLC (General Location Module), or location server possesses UE location information, the UDM or GMLC can derive and provide the sensing-related UEs from information about the sensing area provided by the location server. The method described above can be appropriately applied.

[0225] The gateway is disclosed to send sensing requests to the AMF (or via the AMF to the SF). However, unlike gateways used for traditional location management, the gateway cannot obtain UE information in sensing where the target is not the UE. The gateway cannot request UE information from the UDM, nor can it select the AMF to send the sensing request.

[0226] Publicly disclose methods for solving this problem.

[0227] An interface is set up between the sensing gateway and the UDM. The gateway, having received information about the sensing-related UE from the LMF, requests information about that UE from the UDM. The UDM, upon receiving the request, exports the information about the UE. This information may include, for example, the UE's subscription information and the AMF serving the UE. The UDM then sends this information to the gateway. Thus, the gateway can obtain information about the AMF serving the sensing-related UE. The gateway can then select the AMF from which the sensing request is sent. If the UDM has the UE's location information, it can simultaneously request the provision of sensing-related UE information and the request for information about the UE. Alternatively, this can be done with a single message, reducing signaling load.

[0228] The UE can send information about its sensing capabilities to the NW node. The UE can include this information in its capability information and send it to the NW node. The NW node can be an SF (Secure Serving).

[0229] The following are six examples of information regarding the sensing capabilities of this UE.

[0230] (1) Sensing resource transmission function.

[0231] (2) Sensing resource receiving function.

[0232] (3) Functions for performing measurements for sensing (sensing measurement function).

[0233] (4) Supported sensing frequency information.

[0234] (5) Sensing window supports information.

[0235] (6) Combinations of (1) to (5).

[0236] (1) For example, information may be limited to whether or not it has the function of transmitting sensing resources, or it may be information about which sensing resources can be transmitted. For example, it may be SRS or RS set for sensing.

[0237] (2) For example, information may be limited to whether or not the receiving function of the sensing resource is available, or it may be information about which sensing resource can be received. For example, PRS, CSI-RS, SSB (Synchronization Signal Block), SRS, or RS set for sensing, etc.

[0238] (3) For example, information may include, but is not limited to, whether or not a sensing measurement function is available, as well as information about which sensing measurement metrics are supported. Examples of sensing measurement metrics include RSRP, RSRQ, SIR, Doppler frequency, AOD (Angle Of Departure), TDOA (Time Difference Of Arrival), AOA (Angle Of Arrival), CIR (Channel Impulse Response), PDP (Power Delay Profile), etc. (3) Information may also include whether or not a function is available to measure the time variations of these metrics. (3) Information may also include information about sensing measurements based on LOS (Line Of Sight) or NLOS (Non Line Of Sight). (3) For example, information may include whether or not sensing measurements using LOS are supported, whether or not sensing measurements using NLOS are supported, and whether or not a function is available to export whether the path used for sensing measurements is LOS or NLOS. In addition, (3) may also be information about whether it has the function of deriving position, range, speed, acceleration, direction of movement, etc.

[0239] (4) For example, it could be information such as frequency band, frequency layer, BWP, etc. (4) For example, it could also be information about whether it has full-duplex function or sub-band full-duplex function.

[0240] A sensing window can be set up for sensing measurements. The UE performs sensing measurements in the sensing window. Communication may not be performed in the sensing window. (5) For example, information about whether there is a function to perform sensing measurements in such a sensing window.

[0241] Network nodes that receive this information about the sensing capabilities of the UE can determine, for example, which UE can be used for sensing and what kind of sensing it can perform.

[0242] The NW node can request information about sensing capabilities from the UE. Upon receiving the request, the UE sends this information back to the NW node. For example, the SF can request this information from the receiving UE. The receiving UE sends this information to the SF. The SF can consider the information about the receiving UE's sensing capabilities and configure the receiving UE accordingly. For example, the SF can request this information from a sensing-related UE. The sensing-related UE sends this information to the SF. The SF can consider the information about the sensing-related UE's sensing capabilities to determine the appropriate receiving UE.

[0243] An NW node can also be an AMF (Agency Detection and Management Detection Center). The AMF can send information received from the UE regarding its sensing capabilities to the SF (Sensing Center). For example, the SF can send a sensing request to the AMF. This sensing request may contain information about the sensing-related UE. Based on the receipt of the sensing request, the AMF can send information about the sensing capabilities of the sensing-related UE to the SF. An NW node can also be a base station. The base station can send information received from the UE regarding its sensing capabilities to the AMF.

[0244] Information about the sensing capabilities of the UE can be sent to the NW node along with information about its location management capabilities. The sensing-related UE may have location management capabilities. The NW node can, for example, use the information from the UE regarding sensing capabilities and location management capabilities to determine which UE can be used for sensing and what kind of sensing it can perform.

[0245] A method for deriving sensing-related nodes is disclosed. Sensing-related nodes can be candidate nodes for sending sensing resources for sensing. This node can be a base station. When the node is a base station, it is referred to as a sensing-related base station. The AMF derives the base station serving the sensing-related UE. This deriving can be performed using information about the sensing-related UE. For example, the deriving can be performed using information about the sensing-related UE received from a gateway. The AMF can obtain information about the sensing-related UE from the UDM and can use this information when deriving the sensing-related base station. The AMF can obtain information about the sensing-related UE from the UDM via a gateway. The AMF can obtain information about the sensing-related UE from the UDM after the gateway selects the AMF as disclosed above. This reduces processing complexity.

[0246] The AMF can initiate a service request for a sensing-related UE. This service request may include information indicating that it is for sensing purposes. The sensing-related UE is connected to the AMF. An RRC connection with the base station can be maintained. This is effective even if the sensing-related UE is not connected to either the AMF or the base station.

[0247] It has been disclosed that the AMF can send sensing requests to the SF. Information about the sensing-related base stations can be included in the sensing requests. The SF can then obtain this information about the sensing-related base stations.

[0248] There can be one or more SFs within a NW. For example, an SF can be set up for each defined sensing area. Interfaces can be set up between SFs. An SF can send sensing requests to other SFs. Other SFs can be SFs that manage the sensing areas included in the sensing requests. This SF can manage the sensing within that sensing area.

[0249] The method for determining the nodes that transmit sensing resources (sometimes called sensing transmitting nodes or simply transmitting nodes) and the nodes that receive sensing resources (sometimes called sensing receiving nodes or simply receiving nodes) is disclosed. The SF (Sensing Provider) can determine the transmitting and receiving nodes. These nodes can be either UEs (User Equipment) or base stations. The number of receiving nodes is not limited to one; there can be multiple nodes.

[0250] For example, SF can use information received from AMF about sensing-related UEs and sensing-related base stations to decide which UE to receive and which base station to transmit.

[0251] The SF can send information to the transmitting base station requesting sensing settings. This information may include information about the receiving UE, information about the sensing measurement method, information about the sensing frequency, etc. Furthermore, this information may also be included in the aforementioned sensing request.

[0252] Other methods are disclosed. The decision to receive the UE can also be made by the base station. This base station can be a transmitting base station. For example, the transmitting base station is determined by the SF, and the receiving UE is determined by that transmitting base station. This is effective when one or more receiving UEs are within the coverage area of ​​a base station. The SF can send information requesting the decision to receive the UE to the transmitting base station. This information can be included in a sensing configuration request from the SF to the transmitting base station. The base station can then decide to receive the UE based on this request.

[0253] The transmitting base station can send information about the receiving UE to the SF. For example, the base station can send the information about the receiving UE along with sensing configuration information to the SF. The SF can then obtain the information about the receiving UE. The SF can then send the sensing configuration to the receiving UE. Alternatively, the transmitting base station can directly notify the receiving UE of the sensing configuration, which can reduce signaling load.

[0254] Other methods are disclosed. The AMF can also decide which UE to receive. For example, the transmitting base station is determined by the SF, and the receiving UE is determined by the AMF. This is effective when one AMF serves one or more receiving UEs. The SF can send information to the AMF requesting the decision of which UE to receive. This request can include information about the transmitting base station. This information can be included in a sensing request from the SF to the AMF. For example, the AMF can designate one or more UEs within the coverage area of ​​the transmitting base station and surrounding base stations as receiving UEs. Not only UEs within the coverage area of ​​the transmitting base station can be designated as receiving UEs, but also surrounding UEs.

[0255] The AMF can send information about the receiving UE to the SF. The SF can obtain information about the receiving UE. The SF can send sensing settings to the receiving UE. Alternatively, the AMF can directly notify the receiving UE of the sensing settings. The AMF can also notify the receiving UE of the sensing settings via the base station serving the receiving UE. This can reduce signaling load.

[0256] The AMF can initiate a service request for the receiving UE. For example, when the AMF receives a sensing request from the SF to the receiving UE, it can initiate a service request for that receiving UE. For example, when the AMF determines the receiving UE, it can initiate a service request for that receiving UE. This service request can include information indicating that it is for sensing. The receiving UE is connected to the AMF. An RRC connection with the base station can be maintained. This is effective when the receiving UE is not connected to the AMF or the base station.

[0257] An example of a method for determining the transmitting base station and the receiving UE is disclosed. The transmitting base station and the receiving UE are determined independently. The SF determines the transmitting base station. The SF sends a sensing configuration request to the transmitting base station. The transmitting base station determines the sensing configuration. The transmitting base station sends the sensing configuration to the SF. The SF determines the receiving UE. The SF performs NW-initiated service request processing for the receiving UE. Each receiving UE can connect to a different base station. The SF sends the sensing configuration to the receiving UE via the base station connected to each receiving UE. Therefore, the sensing configuration can be shared between the transmitting base station and the receiving UE. This sensing configuration can be used to perform sensing processing.

[0258] The transmitting base station can send sensing settings to the base station to which the receiving UE is connected. This transmission can utilize an inter-base station interface. For example, the transmitting base station can use the Xn interface to send the sensing settings. The transmitting base station can send information about the receiving UE along with the sensing settings. The base station receiving this information can then send the sensing settings to receiving UEs within its coverage area. Therefore, the sensing settings can be sent to the receiving UE without going through the SF (Signal Transfer Switch), thus reducing signaling load.

[0259] Other method examples are disclosed. After determining the receiving UE, the transmitting base station is determined based on information about the determined receiving UE. The SF determines one or more receiving UEs. The SF performs NW-initiated service request processing for the receiving UE. The AMF can send information about the base stations connected to the receiving UE to the SF. The SF determines the transmitting base station from the base stations connected to the receiving UE. The SF sends a sensing configuration request to the transmitting base station. The transmitting base station determines the sensing configuration. The transmitting base station sends the sensing configuration to the SF. The SF sends the sensing configuration to the receiving UE. Thus, the sensing configuration can be shared between the transmitting base station and the receiving UE. The sensing configuration can be used to perform sensing processing.

[0260] Furthermore, the transmitting base station can send sensing settings to the base station connected to the receiving UE. The methods disclosed above can be appropriately applied.

[0261] The receiving UE can be limited to one or more UEs connected to a single base station. This single base station can be a transmitting base station. A specified number or more receiving UEs can be connected to a base station that serves as the transmitting base station. Using a single base station and the UEs connected to that base station can reduce the complexity of sensing processing.

[0262] The receiving UE can be limited to RRC_Connected UEs. Alternatively, it can not be limited to RRC_Connected UEs. The receiving UE can be either RRC_Idle or RRC_Inactive UEs. The receiving UE can receive sensing settings while in RRC_Connected state. For example, it can receive sensing settings from a SF (SF) or base station. Even after transitioning to RRC_Idle or RRC_Inactive, the receiving UE can still use the last received sensing settings. Sensing measurements can be performed even when the receiving UE is in RRC_Idle or RRC_Inactive state.

[0263] The transmitting base station transmits sensing radio waves to the target. The transmitting base station transmits resources (sensing resources) used for sensing via these sensing radio waves. The transmitting base station can use beams to transmit sensing resources. Sensing resources can be resources on the frequency-time axis. For example, sensing resources can be signals set up for sensing. For example, sensing resources can be RS transmitted on the frequency-time axis. For example, sensing resources can be RS, PRS, CSI-RS, SSB, SS, MIB, DM-RS of MIB, etc., set up for sensing.

[0264] The transmitting base station determines the beam used for sensing. The transmitting base station can use a communication beam as the sensing beam. The communication beam is not limited to the beam actually transmitting data; it can also be a beam set by the transmitting base station for the UE. For example, the base station can use the measurement result report of the RS corresponding to the communication beam at the UE to determine the sensing beam. The transmitting base station can, for example, use measurement result reports from SSB, CSI-RS, or PRS to determine the sensing beam. The transmitting base station can, for example, use information received from the SF about the receiving UE and use the communication beam between itself and the receiving UE to determine the sensing beam. For example, it can use information received from the SF about the receiving UE and use a beam transmitted to the periphery of the communication beam between itself and the receiving UE to determine the sensing beam.

[0265] The transmitting base station can select one of multiple communication beams as the sensing beam. This is effective when there are multiple receiving UEs and multiple beams used for communication with those UEs. Using a single beam for sensing simplifies the sensing process.

[0266] The transmitting base station transmits sensing resources using the determined sensing beam. Sensing resources can be, for example, RS configured for sensing. Alternatively, sensing resources can be PRS, CSI-RS, SSB, etc. The transmitting base station determines the sensing resources used for sensing.

[0267] To determine the beam, the transmitting base station can send QCL information of the sensing resources to the UE. The QCL information can indicate which RS the sensing resource is quasi-co-located with.

[0268] The transmitting base station performs sensing settings including sensing resource information, QCL information, etc. From this, sensing settings for detecting sensing targets can be derived. The transmitting base station can then send these sensing settings to the SF (Signal Power Array).

[0269] The transmitting base station can scan beams. It can transmit multiple beams in different directions. Beam scanning can be performed using multiple beams. The transmitting base station can select multiple beams from multiple communication beams as sensing beams. For example, the transmitting base station can use information received from the SF regarding the receiving UE, and use multiple communication beams between the transmitting base station and the receiving UE to determine the beams for sensing. For example, a communication beam in which a receiving UE is conducting data communication and beams in its adjacent directions can be used as sensing beams. For example, the transmitting base station can use multiple communication beams in which receiving UEs are conducting data communication as sensing beams. The transmitting base station can scan these multiple sensing beams. The transmitting base station can use the determined multiple sensing beams to transmit sensing resources set for each beam. The transmitting base station performs sensing settings including sensing resource information, QCL information, etc., for multiple beams. Thus, sensing settings for detecting sensing targets can be derived. The transmitting base station can send the sensing settings to the SF.

[0270] The method disclosed involves the UE reporting measurement results of the communication beam to the transmitting base station, which uses these measurement results to determine the sensing beam. The UE can send measurement results for multiple paths of the same beam to the base station. The UE can send measurement results for each path to the base station. The UE can send measurement results for LOS and / or NLOS to the base station. The UE can send measurement results for both LOS and NLOS for each path to the base station. The UE can send information indicating whether the measurement result is LOS or NLOS for each path's measurement results. Alternatively, information indicating whether the measurement result sent by the UE to the base station is NLOS can be included in the measurement results. The UE can include information indicating the probability or likelihood of the measurement result being NLOS in the measurement results. The UE can include information indicating whether the measurement result is LOS in the measurement results. The UE can include information indicating the probability or likelihood of the measurement result being LOS in the measurement results. LOS can be FAP (First Arriving Path). The UE can presume FAP to be LOS.

[0271] The transmitting base station can select a beam with an NLOS path as the sensing beam. During sensing, the receiving UE can measure the NLOS path from the transmitting base station. The receiving UE can receive and measure the reflected wave from the target.

[0272] The sensing configuration method is disclosed. Sensing configurations are shared between transmitting and receiving nodes. For example, sensing configurations are shared between a transmitting base station and one or more receiving UEs.

[0273] The SF sends a sensing configuration request to the base station. The base station, upon receiving the request, performs sensing configuration. The base station sends sensing configuration information to the SF. The SF sends the sensing configuration information to one or more receiving UEs. The SF can send the sensing configuration information to one or more receiving UEs via a base station serving that receiving UE. Thus, the receiving UE can obtain the sensing configuration. Sensing configuration can be shared between the transmitting base station and the receiving UE.

[0274] As a method for sending sensing configuration information from a base station to multiple receiving UEs, the multiple receiving UEs can be grouped, for example. For example, a common RNTI can be set. Multiple receiving UEs can identify sensing configuration information destined for them by detecting the PDCCH using the common RNTI. Alternatively, a group ID can be set, for example. For example, the group ID can be sent to the receiving UE along with or included in the sensing configuration information. Multiple receiving UEs can identify sensing configuration information destined for them by detecting the group ID. The common RNTI and group ID can be preset. For example, the base station can set them for the UE during the UE's service request processing. For example, the base station can notify the UE during the initial sensing configuration. The common RNTI or group ID can be used in subsequent sensing configurations. While the transmission of sensing configuration information has been disclosed, it is not limited to this; it can also be applied to the notification of sensing-related information between the base station and multiple receiving UEs. This reduces the signaling volume between the transmitting base station and multiple receiving UEs.

[0275] The SF can send sensing configuration requests to multiple base stations. The base station receiving the request performs the sensing configuration. These multiple base stations can be, for example, sensing-related base stations. The SF can use the sensing configurations of multiple base stations to select a transmitting base station. By performing the above processing before deciding on the transmitting base station, a base station that is more suitable for the QoS and QoE requirements of the sensing can be selected as the transmitting base station.

[0276] The SF can notify the selected transmitting base station that it has been selected as the transmitting base station. It can also send a sensing request. The selected base station can recognize itself as the transmitting base station. The SF sends sensing configuration information to one or more receiving UEs. Thus, the receiving UE can obtain the sensing configuration. The sensing configuration can be shared between the transmitting base station and the receiving UE.

[0277] The sensing configuration request can include information about the sensing target. Additionally, it can also include information about the receiving UE. The transmitting base station determines the beam used for sensing and derives the sensing configuration.

[0278] The following are four examples of information included in the sensor settings.

[0279] (1) Information about the settings of sensing resources.

[0280] (2) Information about the settings for sensing measurements.

[0281] (3) Information about the report of the sensing measurement results.

[0282] (4) Combinations of (1) to (3).

[0283] Here are eight examples of information regarding the settings of sensing resources in (1).

[0284] (1-1) Information about the resources used for sensing.

[0285] (1-2) Information on the allocation of sensing resources.

[0286] (1-3) Sensing resource period and offset information.

[0287] (1-4) Start time, end time, and information during the transmission of the sensing resources.

[0288] (1-5) Information about the beams used for sensing.

[0289] (1-6) QCL information of the sensing resources.

[0290] (1-7) Information about the power of the sensing resources.

[0291] Combinations of (1-8) (1-1) to (1-7).

[0292] (1-1) For example, it could be information about the frequency used for sensing. For example, (1-1) could be information about the RS used for sensing. Information about the frequency used for sensing could be, for example, information about the frequency band, frequency layer, BWP, etc. The frequency band, frequency layer, BWP, etc., used for sensing can also be set. These can be specific to sensing. By determining the frequency used for sensing, the processing complexity of nodes performing sensing processing, such as the UE or base station, can be reduced. Information about the RS used for sensing could be, for example, set as the RS, PRS, SSB, CSI-RS, etc., used for sensing. The receiving UE can identify what sensing resources can be received.

[0293] (1-2) For example, it could be time-frequency information mapping sensing resources. Time information could include symbols, time slots, radio frames, etc., mapping sensing resources. Alternatively, it could be time units such as seconds, hours, days, years, etc. Frequency information could include subcarriers, resource blocks, subbands, BWPs, carrier frequencies, sensing frequency layers, etc., mapping sensing resources.

[0294] Sensing can also be supported in SCell (or CC). Sensing can also be supported in SCG. Sensing can also be supported in PSCell. Dedicated SCells, SCGs, and PSCells can also be configured for sensing. For example, communication can be performed in PCell, and sensing can be performed in SCell, which can reduce the complexity of sensing processing during communication.

[0295] The allocation information of sensing resources in (1-2) can be information used to determine SCell, SCG, and PSCell. The receiving UE can receive the setting information of sensing resources in SCell, SCG, and PSCell.

[0296] The sensing resources can be transmitted periodically. (1-3) can be the period and offset information of the sensing resources that are transmitted periodically.

[0297] (1-4) contains information about the start time, end time, and transmission period of the sensing resource. For example, the sensing resource is transmitted periodically during this transmission period. The unit of time can be a symbol, time slot, radio frame, or seconds, hours, days, years, etc.

[0298] (1-5) contains information about the sensing beam for transmitting sensing resources. An identifier can be set for the sensing beam. The receiving UE can determine the sensing beam. For example, an identifier used for the communication beam can be used as an identifier for the sensing beam. The association with the communication beam can be indicated, and the settings of the communication beam can be used flexibly.

[0299] (1-6) is information about resources that are in a QCL relationship with the sensing resources. For example, it could be information about communication RS that are in a QCL relationship with the sensing RS. Thus, for example, measurement results about communication resources that are in a QCL relationship with the sensing resources can be used as a substitute for measurement results of the sensing resources, thereby simplifying the processing.

[0300] (1-7) contains information about the transmission power of the sensing resource. For example, this transmission power information could be the absolute value of the transmission power. Alternatively, it could be the difference between the sensing resource and other channels or other RSs. The receiving UE can identify the transmission power of the sensing resource. For example, the receiving UE can use this transmission power information to derive path loss. Path loss can be used as a sensing measurement metric.

[0301] Four examples of information regarding the settings for sensing measurements in (2) are disclosed below.

[0302] (2-1) Information about the measurement gap for sensing.

[0303] (2-1) Information about the window used for sensing measurements.

[0304] (2-3) Information about sensing measurement indicators.

[0305] Combinations of (2-4) (2-1) to (2-3).

[0306] Measurement gaps can also be set for sensing. (2-1) For example, the measurement gap period, start time, end time, etc. The unit of time can be a symbol, time slot, radio frame, or seconds, hours, days, years, etc. There is no limit to one measurement gap for sensing; multiple gaps can be set. Measurement gaps for sensing are effective, for example, when sensing is performed at a frequency different from the communication frequency. The receiving UE can switch from the communication frequency to the sensing frequency during this gap, thereby enabling sensing measurements.

[0307] A window can also be set for sensing measurements. (2-2) For example, the duration, start time, and end time of the sensing window. The unit of time can be a symbol, time slot, radio frame, or seconds, hours, days, years, etc. There is no single sensing window; multiple windows can be set. Sensing windows are effective, for example, when sensing is performed at a communication frequency. For example, a receiving UE can choose not to receive communication channels or signals during a sensing window. The receiving UE can perform sensing measurements within the sensing window.

[0308] As examples of information regarding sensing measurement indicators in (2-3), 10 are disclosed below.

[0309] (2-3-1) RSRP.

[0310] (2-3-2) RSRQ.

[0311] (2-3-3) Doppler frequency.

[0312] (2-3-4) AOA.

[0313] (2-3-5) AOD.

[0314] (2-3-6) TDOA.

[0315] (2-3-7) CIR.

[0316] (2-3-8) PDP.

[0317] (2-3-9) Sensing measurement time.

[0318] Combinations of (2-3-10) (2-3-1) to (2-3-9).

[0319] The receiving UE can be configured to measure which metric as a sensing measurement. By receiving this information, the receiving UE can identify which metric can be measured as a sensing measurement.

[0320] Furthermore, the information regarding the sensor measurement settings can include information about the sensor resources. It can also include information about the sensor resources used for the measurement. For example, if multiple sensor resources are set, it can identify which sensor resource needs to be measured.

[0321] The UE can perform sensing measurements by receiving the settings for sensing measurements.

[0322] Three examples of information regarding the report of sensing measurement results in (3) are disclosed below.

[0323] (3-1) Report triggered.

[0324] (3-2) Information about the measurement results.

[0325] Combinations of (3-3), (3-1), and (3-2).

[0326] (3-1) For example, this could be information indicating whether the timing of reporting sensing measurement results is periodic or event-triggered. When the timing of reporting sensing measurement results is periodic, this could be information such as the reporting period, start time, and end time of the measurement results. When the timing of reporting sensing measurement results is event-triggered, this could be information about the conditions for reporting sensing measurement results. This condition could be, for example, a specified threshold for the sensing measurement index. For example, a threshold for RSRP could be set. The receiving UE can report the measurement results when RSRP reaches or exceeds this threshold. This condition could be, for example, when radio wave propagation conditions or channel conditions change. For example, the measurement results can be reported when the LOS or NLOS path changes. For example, the measurement results can be reported when the FAP changes.

[0327] As another method, upon event triggering, the receiving UE can report that the event has occurred. The node receiving the report can then recognize that the event has occurred. For example, the report can be used to change sensing settings. More appropriate sensing processing can then be implemented.

[0328] (3-2) For example, it could be information about the transmitting base station, information about the measured sensing resources, information about the measured sensing beam, sensing measurement indicators, etc. (3-2) could be the identifier of the transmitting base station, the identifier of the sensing resources, or the identifier of the sensing beam. The node that receives the measurement result can determine which transmitting base station, which sensing beam, and which sensing resource it is.

[0329] The settings for sensing settings, sensing resource settings, information about sensing resource settings, sensing measurement settings, information about sensing measurement settings, sensing measurement result reporting settings, or information about sensing measurement result reporting are not limited to one; multiple settings can be configured. Information used to determine each setting or piece of information can be set for each setting or piece of information. For example, this information can serve as an identifier. For instance, SF can determine a specific sensing setting or piece of information from multiple sensing settings or pieces of information, identifying which setting and which piece of information it is. Therefore, for example, the sensing settings can be changed according to the measurement environment, enabling flexible sensing settings.

[0330] The sensing execution method is disclosed. The SF sends a sensing start request to the base station. The sensing start request can also be a sensing request. Alternatively, it can be a request to begin sending sensing resources. The base station receiving the sensing start request sends sensing resources. The sensing resources follow the sensing settings.

[0331] The SF sends a sensing start request to the UE. A sensing start request can also be a sensing request or a request to begin receiving sensing resources. The UE receiving the sensing start request receives the sensing resources. The sensing resources follow the sensing settings. The UE receiving the sensing start request performs sensing measurements. The sensing measurements are performed using the sensing settings. The receiving UE sends the sensing measurement results to the SF. The reporting of the sensing measurement results is performed using the sensing settings. Thus, the receiving UE can perform sensing measurements, and the SF can receive the sensing measurement results performed by the receiving UE.

[0332] The sensing measurement results can include measurement results for multiple paths within the same beam. It can include measurement results for each path. The sensing measurement results can include LOS and / or NLOS measurement results. It can include measurement results for each path with both LOS and NLOS. The measurement results for each path can include information indicating whether it is LOS or NLOS. It can include information indicating whether the measurement result is NLOS. It can also include information indicating the probability or likelihood of being NLOS. LOS can be FAP. SF can determine whether the sensing measurement results obtained from the receiving UE are from a LOS path or an NLOS path.

[0333] For example, if it is a LOS (Low-Input Loss) path, it can be determined that the receiving UE receives direct radio waves from the transmitting base station, rather than reflections from the target. Reflections from the target are preferably NLOS (Low-Input Loss). Measurement results from NLOS paths can be used for target sensing. Measurement results from LOS-excluded paths can be used for target sensing. Therefore, more accurate sensing results can be derived from the sensing measurement results.

[0334] The transmitting base station can change the sensing settings. The changed sensing settings can be sent to the SF. The SF then sends the changed sensing settings information to one or more receiving UEs. Thus, the receiving UEs can obtain the changed sensing settings. Sensing settings can be shared between the transmitting base station and the receiving UEs.

[0335] The SF can modify sensing settings. For example, among multiple sensing settings or information received from the transmitting base station, a different sensing setting or information can be selected. The SF sends the selected sensing setting or information as the modified sensing setting information to the transmitting base station and one or more receiving UEs. Thus, the transmitting base station and the receiving UEs can obtain the modified sensing settings. Sensing settings can be shared between the transmitting base station and the receiving UEs.

[0336] The receiving UE can request changes to sensing settings. For example, the UE can make this request to nodes that perform sensing settings, such as SF, AMF, or base stations, or nodes that perform sensing setting changes. The node receiving the request can then change the sensing settings. The sensing setting change request may include information for determining the sensing settings and information about the quality of sensing measurements. As another example, the sensing setting change request may include desired sensing setting information. This allows the receiving UE to be informed which sensing settings are preferable. The node performing the sensing settings or changing the sensing settings can use the desired sensing setting information from the UE to perform sensing settings. This enables sensing settings that are more suitable for the receiving UE's situation.

[0337] By making it possible to request sensing settings changes from the receiving UE, such as when the reception quality in the receiving UE deteriorates or when there is overlap with communication resources, this problem can be avoided or reduced.

[0338] For example, an SF that receives a sensing setting change request from a UE can send a sensing setting change request to a base station. This request may include information indicating that it is a sensing setting change request. Alternatively, the sensing setting change request can be set separately from the sensing setting request. The SF that receives the sensing setting change request from the UE can send the sensing setting change request to the base station. The base station that receives the sensing setting change request changes the sensing settings. The base station sends the changed sensing settings to the SF. The SF sends the changed sensing settings to the receiving UE. Thus, the receiving UE can obtain the changed sensing settings and use them to perform sensing measurements.

[0339] The transmitting base station can request changes to sensing settings. The transmitting base station can make this request to either a node that is setting sensing settings or a node that is changing sensing settings. The aforementioned method for the UE to request changes to sensing settings can be appropriately applied. Sensing settings can be adjusted to suit the conditions of the transmitting base station.

[0340] The AMF can request changes to sensing settings. The AMF can make this request to either the node that is setting the sensing settings or the node that is changing the sensing settings. The aforementioned method for requesting sensing setting changes by the UE can be appropriately applied. Sensing settings applicable to the AMF's conditions can be configured.

[0341] The activation / deactivation of sensing can be configured. The activation / deactivation of sensing can be set separately from the sensing start request. The activation / deactivation of sensing can include information about the sensing settings used to determine the activation / deactivation. For example, it can include identifiers of the sensing settings disclosed above. One or more preset sensing settings can be activated / deactivated. The SF sends the activation / deactivation of the sensing settings to the receiving UE. The receiving UE performs sensing measurements using the activated sensing settings. The receiving UE stops the sensing measurements using the deactivated sensing settings.

[0342] Sensing settings can be changed using the start / stop function. The process stops the change to the original sensing settings and starts the change to the new sensing settings. Therefore, when changes to sensing settings are required, the process can be performed with low latency, eliminating the need for sending the changed sensing settings and subsequent processing in the receiving UE, retransmitting sensing requests using the changed settings, and the subsequent processing in the receiving UE.

[0343] The method of initiating / stopping sensing operations via SF is disclosed, but it can also be done by AMF. AMF sends the initiation / stopping signal for sensing settings to the receiving UE. Initiation / stopping can be achieved via signaling between AMF and UE, without the need for signaling between SF and UE. This allows for earlier implementation of sensing setting changes.

[0344] The base station can initiate / stop the sensing operation. The base station sends the sensing configuration start / stop information to the receiving UE. Base station-UE signaling can be used; for example, RRC signaling can be used. Large amounts of information can be sent; for example, MAC signaling can be used. It can be sent as early as possible; for example, L1 / L2 signaling can also be used. It can be included in the DCI. It can be sent even earlier. The start / stop operation can be achieved through base station-UE signaling, without the need for SF-UE signaling. Sensing configuration changes can be implemented earlier.

[0345] SF uses sensing measurement results to derive sensing results. Examples of information included in the sensing results include: 3D object detection results with a target, six-dimensional (3D coordinates + 3-axis direction) object detection results, object shape, size, position, speed, direction of movement, water level, humidity, air pressure, heartbeat, etc. Information included in the sensing results can also be time information, such as the time the target was detected, the detection period, and the time during which the target could not be detected. Sensing results can be derived using information about the sensing results. Furthermore, the sensing results can include information indicating what kind of object the target is, such as an intruder, obstacle, river, atmosphere, etc. Sensing results can be derived using information about the target. Additionally, information included in the sensing results can include information about the sensed area, the sensed time, accuracy, QoS measurement results, and QoE measurement results. Information included in the sensing results can also include whether the target exists or has been detected. Sensing results can also be derived using information included in the sensing request.

[0346] The SF sends sensing results to the external device that initiated the sensing request, the AF, the NW node, and the management node. For example, when sending sensing results to an external device, the SF can send them via a gateway. When the SF receives a sensing request from the AMF, the SF can send the sensing results to the AMF, and the AMF can send the sensing results to the external device via a gateway.

[0347] The SF sends part or all of the sensing measurement results to the external device, AF, NW node, and management node that initiated the sensing request. It can be sent separately from the sensing results. External devices or nodes other than the SF can process the sensing measurement results. It can also be sent together with the sensing results. This reduces signaling load. For example, it is effective when it is desirable to utilize external devices to process the sensing results.

[0348] The method for ending sensing is disclosed. The SF sends a sensing termination message to the transmitting base station. A sensing termination message can also be configured. Upon receiving the sensing termination message, the transmitting base station terminates the transmission of sensing resources. Transmission of sensing resources under all sensing settings that have already begun sensing can be terminated. The transmitting base station can release sensing settings. The transmitting base station can release all sensing settings. The transmitting base station sends a sensing termination completion message to the SF. A sensing termination completion message can also be configured.

[0349] The SF sends a sensing termination message to some or all of the receiving UEs. A sensing termination message can also be configured. Upon receiving the sensing termination message, the receiving UE ends the reception of sensing resources. It can terminate the reception of sensing resources under all sensing settings that have already begun sensing. The receiving UE can release sensing settings. The receiving UE can release all sensing settings. The receiving UE sends a sensing termination completion message to the SF. A sensing termination completion message can also be configured.

[0350] An external device can initiate a sensing termination. The external device sends a sensing termination message to the SF. The external device can send a sensing termination message to the SF via a gateway. The aforementioned method for sending sensing requests can be appropriately applied. Upon receiving the sensing termination message, the SF performs the aforementioned sensing termination processing on the transmitting base station and the receiving UE. The SF, having completed the sensing termination processing, can send a sensing termination completion message to the external device. The SF can send a sensing termination completion message to the external device via a gateway. An external device that has initiated sensing can initiate a sensing termination. Furthermore, the external device can determine whether sensing has been completed.

[0351] The initiation of sensing processes for the same target can be restricted. It can be configured to prevent the initiation of multiple sensing processes for the same target. If the external device, NW node, or management node that initiated the sensing process has not received a sensing request for a particular target and the process ends, it can be configured to prevent sensing requests for the same target from being initiated. This avoids complicating the sensing process.

[0352] Alternatively, multiple sensing processes can be initiated for the same target. For example, multiple sensing processes requesting different sensing times for the same target can be initiated. Or, multiple sensing processes requesting different sensing results for the same target can be initiated. For example, the external device, NW node, or management node initiating the sensing processes can be different. Thus, multiple sensing results can be obtained for the same target, for example, enabling more flexible sensing processing.

[0353] Figures 15 and 16 are diagrams illustrating examples of sensing processing sequences. An example of initiating sensing from an external device is disclosed. Furthermore, an example of deriving sensing-related UE information from the LMF is disclosed. In step ST1501, a sensing request is generated in the external device, and sensing is initiated. In step ST1503, the external device sends a sensing request to the sensing gateway in order to send the sensing request to the NW. The sensing request may contain the information disclosed above. For example, information about the sensing area may be information representing a defined area. The sensing target may not be a UE. For example, an example where the sensing target is not a UE is disclosed.

[0354] In step ST1505, the gateway sends a request to the LMF to provide sensing-related UE information. This request may include information about the sensing area. It may also include information contained in other sensing requests. In step ST1507, the LMF exports the sensing-related UE information. Information about the sensing area can be used when exporting the sensing-related UE information. The number of sensing-related UEs is not limited to one; it can be multiple. For example, a maximum value for the number of sensing-related UEs can be set. This maximum value can be set for a mobile communication system. The LMF exports sensing-related UEs within this maximum value. By setting a maximum value, the complexity of sensing processing can be reduced.

[0355] An LMF can send information about the sensing area to other LMFs. These other LMFs may be the ones managing the sensing area. Other LMFs can use the information about the sensing area to derive sensing-related UE information. Other LMFs can also send sensing-related UE information to other LMFs. This information exchange between LMFs can utilize the LMF interface. For example, when an LMF that receives a request for sensing-related UE information from a gateway does not manage the sensing area, it can request the information from other LMFs that manage the sensing area.

[0356] In step ST1509, the LMF sends a response to the gateway requesting the provision of sensing-related UE information. This response may include the sensing-related UE information. Even if the sensing target is not a UE, the gateway can obtain information about UEs that can be used for sensing.

[0357] In step ST1511, the gateway sends a UE information request for the sensing-related UE to the UDM. This request may contain sensing-related UE information, information indicating that it is used to sense this situation, and information about what the UE information request is. Upon receiving the request, the UDM extracts the sensing-related UE information, such as the UE's registration information and the network address information of the AMF serving the UE. In step ST1513, the UDM sends the sensing-related UE information to the gateway. The gateway is able to obtain the sensing-related UE information.

[0358] In step ST1515, the gateway sends a sensing request to the AMF serving the sensing-related UE. The AMF is not limited to one, but can include multiple AMFs. The request may contain information indicating it is a sensing request, and information about the sensing-related UE served by the AMF. In step ST1517, the AMF derives information about the base station serving the sensing-related UE. This base station can be a sensing-related base station. In step ST1519, the AMF sends a sensing request to the SF. The AMF may have the ability to select the SF. The request may contain information indicating it is a sensing request, information included in the sensing request, sensing-related UE information, and sensing-related base station information. The processes from steps ST1501 to ST1519 are collectively referred to as the sensing request processing in step ST1591.

[0359] In step ST1531, the SF sends an information provision request regarding the sensing capabilities of the sensing-related UE to the sensing-related UE. The SF may send the capability information request to the sensing-related UE via the AMF or the base station. In step ST1532, the sensing-related UE sends information regarding its sensing capabilities to the SF. The sensing-related UE may send the sensing capability information to the SF via the base station or the AMF. The SF can obtain the information regarding the sensing capabilities of the sensing-related UE. The processing of steps S1531 and S1532 is collectively referred to as the sensing capability request processing in step ST1592.

[0360] In step ST1535, the SF determines the transmitting base station and the receiving UE. The receiving UE is not limited to one, but can be multiple. The SF can use information included in the sensing request to deduce the receiving UE. When deduce the receiving UE, the SF can use information about the sensing capabilities of the sensing-related UE.

[0361] In step ST1541, the SF sends a sensing configuration request to the transmitting base station. This request may include information indicating a sensing configuration request. The request may include information about the receiving UE. The request may include information about the sensing capabilities of the receiving UE. Upon receiving the sensing configuration request, the transmitting base station performs sensing configuration in step ST1542. For example, it configures settings related to sensing resources, sensing measurements, and the reporting of sensing measurement results. In step ST1543, the transmitting base station sends sensing configuration information to the SF. The SF can obtain the sensing configuration information. In step ST1544, the SF sends the sensing configuration information to the receiving UE. The receiving UE can obtain the sensing configuration information. The processes from steps ST1541 to ST1544 are collectively referred to as the sensing configuration process in step ST1593.

[0362] The transmitting base station can configure some sensing settings, while the SF can configure other sensing settings. For example, the transmitting base station can configure sensing resources, while the SF can configure sensing measurements and the reporting of sensing measurement results. The SF can configure sensing measurements and the reporting of sensing measurement results suitable for all receiving UEs.

[0363] The SF can perform sensing configuration. In this case, the sensing configuration request between the SF and the transmitting base station, as well as the transmission of the configuration, can be omitted. The transmitting base station can then avoid performing sensing configuration, reducing processing at the transmitting base station. The SF can transmit the sensing configuration to the transmitting base station and all receiving UEs. By performing sensing configuration by the SF, sensing configuration applicable to both the transmitting base station and all receiving UEs can be achieved.

[0364] The SF decides to perform a sensing measurement. In step ST1546, the SF sends a sensing request to the transmitting base station. In step ST1548, the SF sends a sensing request to the receiving UE. In step ST1550, the transmitting base station transmits sensing resources according to the sensing settings. In step ST1552, the receiving UE performs a sensing measurement according to the sensing settings. In step ST1561, the receiving UE sends the sensing measurement result to the SF according to the sensing settings. The SF can obtain the sensing measurement result from the receiving UE. The processes from steps ST1546 to ST1561 are collectively referred to as the sensing measurement process in step ST1594.

[0365] In step ST1563, the SF derives the sensing result based on the sensing measurement result received from the receiving UE. In step ST1565, the SF can determine whether the sensing was successful. The SF can derive the false alarm rate or false alarm rate of the target. In step ST1565, if the SF determines that the sensing was unsuccessful, it can attempt to sense again. For example, it can restart from step ST1593, where a sensing setting request is sent to the transmitting base station. Alternatively, the SF can reconfigure the sensing settings, starting by sending sensing settings to both the transmitting base station and the receiving UE. Alternatively, the SF can restart from sending a sensing request to both the transmitting base station and the receiving UE. When sensing is unsuccessful, it can be attempted again.

[0366] In step ST1571, the SF sends the exported sensing results to the AMF. In step ST1572, the AMF sends the sensing results to the gateway. In ST1573, the gateway sends the sensing results to the external device. The sensing results may contain not only the sensing results themselves but also an identifier of the sensing request. It is possible to identify which sensing request the sensing results pertain to. Multiple sensing requests are possible. The processing of steps ST1571 to ST1573 is collectively referred to as the sensing result reporting processing in step ST1595.

[0367] To derive the sensing results of the sensing target, the location information of the receiving UE can be used. A method for using the UE's location information in sensing processing is disclosed.

[0368] The LMF sends the location information of the sensing-related UE to the SF. The LMF can send the location information of the sensing-related UE together with, or include within, the sensing-related UE information. Thus, the SF can obtain the location information of the sensing-related UE. The SF can also obtain the location information of the receiving UE.

[0369] The SF, having acquired sensing measurement results from the receiving UE, can use the location information of the receiving UE to export the sensing results. It is capable of exporting sensing results that require the location information of the receiving UE.

[0370] The SF can request the LMF to receive the location information of the UE. For example, the SF can send this request to the LMF when it receives sensing measurement results from the receiving UE. This request may include the identification information of the receiving UE and the sensing measurement time information included in the UE's sensing measurement results. The LMF derives the location information of each receiving UE within the sensing measurement time or the time closest to that time. The LMF sends the derived location information to the SF. The LMF can send a response to the SF to this request, which may include the location information of the receiving UE. Thus, more accurate sensing results can be obtained even when the UE is moving.

[0371] The LMF can send the location information of the sensing-related base stations to the SF. The LMF can send the location information of the sensing-related base stations together with, or include within, the sensing-related base station information. Thus, the SF can obtain the location information of the sensing-related base stations. The SF can also obtain the location information of the transmitting base station.

[0372] The SF, having obtained the sensing measurement results from the receiving UE, can use the location information of the transmitting base station to derive the sensing results. It is capable of deriving sensing results that require the location information of the transmitting base station.

[0373] The SF can request the LMF to transmit the location information of the base station. For example, the SF can send this request to the LMF when it receives a sensing measurement result from the receiving UE. This request may include the identification information of the transmitting base station, the identification information of the receiving UE, and the sensing measurement time information included in the UE's sensing measurement result. The LMF derives the location information of the transmitting base station within the sensing measurement time or the time closest to that time. The LMF sends the derived location information to the SF. The LMF can send a response to the SF to this request, which may include the location information of the transmitting base station. Thus, more accurate sensing results can be obtained even when the transmitting base station is moving.

[0374] The sensing-related UE can be limited to UEs with location information. When deriving the sensing-related UE, LMF can limit the sensing-related UE to UEs with location information. Alternatively, it can limit the sensing-related UE to UEs in location information acquisition processing (UEs in location management). Therefore, the location information of the receiving UE can be used in the sensing process.

[0375] The UE can send a message to the NW node indicating whether it has location information acquisition capabilities for location management. The UE can include this information in its capability information. For example, during registration, the UE can send a message to the LMF indicating whether it has location information acquisition capabilities. The LMF can then determine that a UE with this capability is a sensing-related UE.

[0376] For example, during registration, the UE can send a message to the SF indicating whether it has location information acquisition capabilities. The UE can send this information along with sensing capability information. The SF can then determine that a UE with this capability is a receiving UE.

[0377] The LMF can initiate location information acquisition processing for the UE. Other NW nodes can also initiate this processing. Other NW nodes can send a location information acquisition processing initiation request to the LMF. For example, UE assistance positioning processing can be used as a location information acquisition process. In this case, the LMF derives the UE's location. Alternatively, UE-based positioning processing can be used. In this case, the UE derives its location management information and sends it to the LMF. This is useful, for example, when a considerable amount of time has passed since the UE's location information was acquired, to obtain the latest location information.

[0378] The SF can initiate location information acquisition processing for a UE. For example, the SF sends a location information acquisition processing initiation request to the LMF. This request can contain information related to the UE as the target. For example, the information related to the UE as the target is the UE's identifier, etc. The target UE can be, for example, a receiving UE. The LMF initiates location information acquisition processing for that UE. The LMF derives the UE's location information. The LMF can send the UE's location information to the SF. The SF can use the UE's location information to derive sensing results.

[0379] Other NW nodes can be either transmitting base stations or receiving UEs. If the transmitting base station decides to receive the UE, it can send the location information of the receiving UE to initiate the processing request.

[0380] This initiation request can occur, for example, when the sensing request is notified to the SF, or when the sensing request is sent to the transmitting base station or receiving UE. This allows for the measurement of time closer to the sensing measurement.

[0381] The SF can request location measurements from the receiving UE. For example, this request information can be included in the sensing settings. For example, the location measurement can be included in the sensing measurement metrics. The receiving UE can perform both sensing and location measurements. The receiving UE can send the location measurement results along with the sensing measurement results to the SF. The SF can send the location measurement results to the LMF. The LMF uses the location measurement results at the receiving UE to derive the receiving UE's location information. The LMF can send the receiving UE's location information to the SF. The SF can use the receiving UE's location information to derive sensing results.

[0382] The receiving UE can export location information. For example, it can use UE-based positioning (UE-based positioning) processing. The receiving UE sends the exported location information to the SF. The receiving UE can send the location measurement results along with the sensing measurement results to the SF. The SF can then send the location information to the LMF. The SF can use the receiving UE's location information to export the sensing results. Since the LMF does not need to export location information, the processing complexity and signaling volume can be reduced.

[0383] The UE can perform location measurement simultaneously with sensing measurement. For example, location measurement can be performed using sensing resources. Alternatively, sensing measurement can be performed using location measurement resources. For example, the receiving UE can use a PRS configured for location measurement to perform sensing measurement. The sensing resources and location measurement resources can be configured to be the same.

[0384] Alternatively, sensing resources and location measurement resources can be transmitted within a specified period. The receiving UE performs sensing and location measurements within the specified period. This specified period can be, for example, a sensing measurement window. Alternatively, it can be a location measurement window. The sensing measurement window and the location measurement window can be set to be the same.

[0385] The settings for sensing resources and location measurement resources can be adjusted by the SF. The LMF can send location measurement resource settings to the SF. The SF uses the received settings to configure the sensing resources. The settings for sensing measurement windows and location measurement windows can also be adjusted by the SF. The LMF can send location measurement window settings to the SF. The SF uses the received settings to configure the sensing window.

[0386] The settings for sensing resources and location measurement resources can be adjusted by the LMF. The SF can send the sensing measurement resource settings to the LMF. The LMF uses the received settings to configure the location measurement resources. The settings for the sensing measurement window and location measurement window can also be adjusted by the LMF. The SF can send the sensing measurement window settings to the LMF. The LMF uses the received settings to configure the location measurement window.

[0387] The SF can send a request to the LMF to modify the location measurement resources. This request may include information about the location measurement resources for which the modification is requested. This information may, for example, be information used to determine the location measurement resources. Upon receiving the request, the LMF can modify the location measurement resources. The information about the location measurement resources can be used. The LMF can send the modified location measurement resource settings to the SF. Only the modified location measurement resource settings can be sent. The SF can recognize the modified location measurement resource settings. For example, in the event of a conflict between location measurement resources and sensing resources, the SF can request a modification to the location measurement resources from the LMF. This can avoid the resource conflict.

[0388] The LMF can send a request to the SF to modify sensing resources. This request can include information about the sensing resources for which the modification is requested. This information may include, for example, information used to identify the sensing resources. Upon receiving the request, the SF can modify the sensing resources. The information about the sensing resources can be used. The SF can send the modified sensing resource settings to the LMF. Only the modified sensing resource settings can be sent. The LMF can recognize the modified sensing resource settings. For example, in the event of a conflict between sensing resources and location measurement resources, the LMF can request a modification to the sensing resources from the SF. This can help avoid the resource conflict.

[0389] Therefore, the receiving UE can perform position measurement processing simultaneously with sensing measurement processing. Position information can be derived using the position measurement results acquired concurrently with the sensing measurements, and this position information can be used to derive the sensing results. This allows for the export of more accurate sensing results.

[0390] When a UE performs both sensing and location measurements, sensing measurements can be performed using an NLOS path, and location measurements can be performed using a LOS path. Both sensing and location measurements can use the same beam. The same resources can be used for both sensing and location measurements. For example, the transmitting base station can use the same beam to transmit resources for both sensing and location measurements. The transmitting base station can use a beam that provides good performance on both the LOS and NLOS paths at the receiving UE.

[0391] This reduces the time for sensing and position measurement, and shortens the time until the sensing results are exported.

[0392] Once the sensing process is complete, the location information acquisition process can be terminated. For example, the SF can send a sensing termination notification to the LMF. Upon receiving this termination notification, the LMF can terminate the location information acquisition process for the sensing-related UE.

[0393] The SF can send a location acquisition processing termination request to the LMF. This transmission can be made upon completion of the sensing process. The LMF then performs the termination processing for the location acquisition process.

[0394] Location acquisition processing can end upon completion of sensing processing, or it can continue. LMF can determine whether to end location acquisition processing based on the completion of sensing processing. For example, if location acquisition processing is in progress in another service, that processing can continue.

[0395] Therefore, it is possible to obtain the location information of the receiving UE during the sensing process and use the location information of the receiving UE to derive the sensing results. For example, it can solve the following problem: if the location information of the receiving UE is unknown, it is unclear at which location the sensing measurement results were taken, thus making it impossible to derive the location of the sensing target.

[0396] The method discloses the use of UE location information in sensing processing, but location management information other than location information, such as UE speed information, can also be used. Location management information other than location information can also be used in conjunction with location information. For example, by using both UE location information and speed information, more accurate sensing results can be obtained.

[0397] By employing the method disclosed in this embodiment, target sensing can be performed using a UE and a base station. In a mobile communication system, not only communication but also sensing can be performed. Sensing services can be provided using the mobile communication system infrastructure. There is no need to build a separate infrastructure for sensing, enabling sensing services to be provided at low cost. Furthermore, sensing results can be processed within the mobile communication system. For example, obstacle sensing information can be used to select the transmission beam, control the direction, and optimize the NW (Network Width) system. Better communication performance can be obtained.

[0398] Implementation method 2.

[0399] This embodiment discloses other methods for solving the problems disclosed in Embodiment 1.

[0400] In Implementation 2, base stations existing in the sensing area are derived from information about the sensing area. Base stations located near the sensing area, base stations capable of performing sensing processes, or base stations capable of transmitting sensing resources can also be derived. Some or all of these base stations can be considered as sensing-related base stations. Information about a defined area can be used as information about the sensing area. The derived base stations can be one or more.

[0401] LMF (Local Motion Filter) can derive sensing-related base stations from information about the sensing area. LMF identifies the location information of base stations. LMF can obtain the location information of base stations from other NW (Network Node) nodes or management nodes that have this information. By using LMF, sensing-related base stations can be determined. Sensing-related base stations can be base stations with location information within a specified time period. Sensing-related base stations can be base stations with the most up-to-date location information. Sensing-related base stations can be base stations performing location management or location measurement. By using base stations with more recent location information, more accurate sensing can be achieved.

[0402] In Implementation 1, it is disclosed that a node making a sensing request can send information about the sensing area to the LMF. The node making the sensing request can request the LMF to provide sensing-related base station information. The information included in this request can appropriately utilize information included in the provision request of the sensing-related UE. Using this information, the LMF is able to deduce the sensing-related base stations.

[0403] The LMF sends information about the derived sensing-related base stations to the SF. This information includes, for example, base station identification information (e.g., base station identifier, cell identifier, etc.), base station location management information (location information, speed information, etc.), information on whether the base station is within the sensing area, and the distance between the base station and the sensing area. The transmission method can appropriately apply the method for transmitting information about sensing-related UEs and the method for transmitting information about sensing-related base stations disclosed in Implementation 1. For example, it can be transmitted via a gateway. For example, it can be transmitted via the AMF. Information about sensing-related base stations can be included in the sensing request. The SF can obtain information about sensing-related base stations. The SF can use this information to determine the transmitting base station.

[0404] The SF can send a sensing configuration request to the transmitting base station. This request may include information about the sensing area. The request may also include information already included in the sensing request. Upon receiving the request, the transmitting base station performs sensing configuration. The SF can also request sensing-related UE information from the base station. Upon receiving this request, the transmitting base station identifies the sensing-related UE. The sensing configuration request may include a request to provide sensing-related UE information. Alternatively, the request to provide sensing-related UE information may include a request to configure sensing.

[0405] The transmitting base station derives the sensing settings. The transmitting base station can derive the sensing-related UEs. As also disclosed in Embodiment 1, the sensing settings and sensing-related UEs are not limited to one, but can be multiple. The transmitting base station determines the beam directed to the sensing area. The transmitting base station can, for example, use information about the sensing area to determine the beam directed to the sensing area. The beam directed to the sensing area can be used as the beam for sensing. A communication beam can be used as the sensing beam.

[0406] The transmitting base station will derive the UE that communicates using the determined sensing beam. For example, the transmitting base station can derive the UE using measurement result reports of SSB, CSI-RS, and PRS from the UE for that beam. The transmitting base station can also derive the UE by combining information included in the sensing request. The derived UE can be used as a sensing-related UE. Thus, the transmitting base station is able to derive sensing-related UEs.

[0407] The transmitting base station can derive the UE that communicates using a beam adjacent to the determined sensing beam. For example, the transmitting base station can derive the UE using measurement result reports of SSB, CSI-RS, and PRS from the UE for that beam. This can be combined with the methods described above to derive the UE. The derived UE can be used as a sensing-related UE. Thus, the transmitting base station can derive sensing-related UEs.

[0408] The transmitting base station, having determined the sensing beam, derives the sensing settings. For example, information regarding the sensing settings can include the determined sensing beam, sensing resources within that beam, etc. The transmitting base station can use the derived sensing-related UE information. Thus, the transmitting base station can determine the sensing settings.

[0409] The transmitting base station sends information about the determined sensing settings and information about the sensing-related UE to the SF.

[0410] The transmitting base station can scan beams. The method disclosed in Embodiment 1 can be appropriately applied. For example, the transmitting base station can use a sensing beam determined using information about the sensing area and multiple beams nearby as sensing beams. These multiple sensing beams can be scanned. The transmitting base station can use the determined multiple sensing beams to transmit sensing resources set for each beam. The transmitting base station performs sensing settings including sensing resource information, QCL information, etc., for multiple beams. Thus, sensing settings for detecting sensing targets can be derived. The transmitting base station can transmit the sensing settings to the SF.

[0411] The transmitting base station will derive the UEs that communicate using the determined multiple sensing beams. This UE can be designated as a sensing-related UE. The transmitting base station can then send information about the sensing-related UEs to the SF.

[0412] In Embodiment 1, it was disclosed that the transmitting base station can select a beam with an NLOS path as a sensing beam. In this embodiment, these methods can also be appropriately applied. For example, the transmitting base station identifies UEs capable of receiving using an NLOS path with the determined sensing beam. UEs capable of receiving using an NLOS path can be designated as sensing-related UEs. Thus, an NLOS path can be used as a sensing beam for the receiving UE. The receiving UE can then receive and measure reflected waves from the target.

[0413] The SF uses information about the sensing-related UE to determine the receiving UE. The SF sends information about the determined receiving UE to the transmitting base station. The SF sends information about sensing settings to the receiving UE. The method by which the SF sends information about sensing settings to the receiving UE can appropriately employ the method disclosed in Implementation 1.

[0414] Figure 17 is a diagram illustrating other sequence examples of sensing processing. An example of deriving sensing-related base station information using LMF is disclosed. Steps common to Figures 15 and 16 are labeled with the same step numbers, and common descriptions are omitted.

[0415] In step ST1501, a sensing request is generated in the external device. In step ST1503, the external device sends the sensing request to the gateway. Then, in ST1601, the gateway sends a request to the LMF to provide sensing-related base station information. This request may include information about the sensing area. It may also include information contained in other sensing requests. In step ST1603, the LMF derives the sensing-related base station information. Information about the sensing area can be used when deriving the sensing-related base station information. The sensing-related base station is not limited to one; it can be multiple. For example, a maximum value for the number of sensing-related base stations can be set. For example, this maximum value can be set for a mobile communication system. The LMF derives the sensing-related base stations within the maximum value. By setting a maximum value, the complexity of the sensing process can be reduced.

[0416] In step ST1605, the LMF sends a response to the gateway requesting the provision of sensing-related base station information. This response may include sensing-related base station information. Even if the sensing target is not a UE, the gateway can obtain information about base station UEs that can be used for sensing.

[0417] In step ST1515, the gateway sends a sensing request to the AMF serving the sensing-related base station. The AMF is not limited to one, but can include multiple AMFs. This request may contain information indicating it is a sensing request, and information about the sensing-related base station served by the AMF. In step ST1519, the AMF sends a sensing request to the SF. This request may contain information indicating it is a sensing request, information included in the sensing request, and information about the sensing-related base station. The processing of steps ST1501 to ST1519 is collectively referred to as the sensing request processing in step ST1691.

[0418] In step ST1621, the SF determines the transmitting base station. The SF can determine a transmitting base station. The SF can deduce the transmitting base station using information contained in the sensing request.

[0419] In step ST1541, the SF sends a sensing configuration request to the transmitting base station. This request may include information indicating a sensing configuration request. Upon receiving the sensing configuration request, the transmitting base station performs sensing configuration in step ST1641. The transmitting base station identifies the sensing-related UE. In step ST1643, the transmitting base station sends sensing configuration information and sensing-related UE information to the SF. The SF can obtain the sensing configuration information and sensing-related UE information. In step ST1592, the SF and the UE perform sensing capability request processing.

[0420] In step ST1645, the SF determines the receiving UE. The SF may determine one or more receiving UEs. The SF can derive the receiving UE using sensing configuration information and sensing-related UE information received from the transmitting base station. When deriving the receiving UE, the SF can use the information contained in the sensing request received from the AMF. When deriving the receiving UE, the SF can use the sensing-related UE capability information obtained in step ST1592. In step ST1544, the SF sends the sensing configuration information to the receiving UE. The receiving UE can obtain the sensing configuration information. The processes of steps ST1541 to ST1544 are collectively referred to as the sensing configuration process of step ST1692. The processes of steps ST1594 to ST1595 following step ST1692 are the same as those in Figure 16.

[0421] As disclosed in Implementation 1, SF can perform some or all of the sensing settings.

[0422] Therefore, the UE and base station can be used to sense the target.

[0423] The AMF can determine the receiving UE. For example, the transmitting base station is determined by the SF, and the receiving UE is determined by the AMF. This method can appropriately apply the method disclosed in Implementation 1. The same effect as that disclosed in Implementation 1 can be obtained.

[0424] The transmitting base station can decide which UEs to receive. The transmitting base station will deduce the UEs that communicate using one or more of the determined sensing beams. It will then decide which part or all of the deduced UEs will be the receiving UEs. The transmitting base station can send information about the determined receiving UEs to the SF. The process of using the SF to decide which UEs to receive can be omitted.

[0425] The transmitting base station can send sensing settings to the selected receiving UE. Since the SF does not need to send sensing settings to the receiving UE, the processing can be simplified and the signaling volume reduced.

[0426] Figure 18 is a diagram illustrating other sequence examples of sensing processing. An example of deriving sensing-related base station information from the LMF is disclosed. Furthermore, an example of the transmitting base station sending sensing settings to the receiving UE is disclosed. Steps common to Figures 15, 16, and 17 are labeled with the same step numbers, and common descriptions are omitted.

[0427] In step ST1691, a sensing request is processed. After the SF determines the transmitting base station in step ST1621, in step ST1541, the SF sends a sensing configuration request to the transmitting base station. This request may include information indicating a sensing configuration request. Upon receiving the sensing configuration request, the transmitting base station sends a sensing capability request to the served UE in step ST1731. Upon receiving this request, the UE sends its sensing capability to the transmitting base station in step ST1732. In step ST1541, the transmitting base station that received the sensing configuration request exports the sensing configuration and the receiving UE in step ST1701. After exporting the sensing configuration and / or the sensing-related UE, the transmitting base station that received the sensing configuration request may request sensing capability from the sensing-related UE. The sensing-related UE may send its sensing capability to the transmitting base station. In step ST1703, the transmitting base station sends sensing configuration information and receiving UE information to the SF. The SF can then obtain the sensing configuration and receiving UE information.

[0428] In step ST1705, the transmitting base station sends a sensing setting to the receiving UE. The receiving UE can acquire the sensing setting. In step ST1707, the receiving UE can send a sensing setting completion message to the transmitting base station. The transmitting base station can recognize that the receiving UE has received the sensing setting and completed the setting. In step ST1709, the transmitting base station sends a sensing setting response to the SF. This response may contain information indicating that the sensing setting is complete at the receiving UE. This response may contain sensing setting information and information about the receiving UE. The processing in step ST1703 can be omitted, and the SF can acquire the sensing setting information and the receiving UE information through step ST1709. The processing in steps ST1541 to ST1709 is collectively referred to as the sensing setting processing in step S1791.

[0429] Therefore, the UE and base station can be used to sense the target.

[0430] By employing the method disclosed in this embodiment, the same effects as those disclosed in Embodiment 1 can be achieved. Furthermore, by first determining the transmitting base station based on information about the sensing area and information included in the sensing request, the derivation process for, for example, the sensing-related UE and the receiving UE can be simplified.

[0431] The method discloses that an LMF can derive sensing-related base stations from information about the sensing area, but is not limited to an LMF. An NW node or management node with base station location information can also derive sensing-related base stations from information about the sensing area. In the disclosed method, this NW node or management node can be used instead of the LMF to achieve the same effect.

[0432] As another method to solve the problem disclosed in Embodiment 1, the sensing-related UE and sensing-related base station can also be derived from information about the sensing area. The LMF can derive the sensing-related UE and sensing-related base station. The method of performing sensing based on the sensing-related UE information and sensing-related base station information can appropriately apply the methods disclosed in Embodiments 1 and 2. For example, in step ST1505 of FIG15, the gateway not only requests the LMF to provide sensing-related UE information, but also makes the request to provide sensing-related base station information as shown in step ST1601 of FIG17. The LMF derives the sensing-related UE information and sensing-related base station information, and sends this information to the SF via the gateway and AMF. The processing in step ST1517 can be omitted. Thus, the same effect as that disclosed in Embodiments 1 and 2 can be obtained. Furthermore, by deriving the sensing-related UE and sensing-related base station from the LMF, for example in sensing a specified area, a transmitting base station and a receiving UE suitable for that area can be selected, thereby obtaining good sensing results.

[0433] Implementation method 3.

[0434] This embodiment discloses other methods for solving the problems disclosed in Embodiment 1.

[0435] The LMF (Local Modem) derives sensing-related base stations from information about the vicinity of a specified base station. This derivation can utilize information about the vicinity of the specified base station included in the sensing request. The LMF can derive sensing-related base stations from information about the vicinity of a specified base station. For example, the LMF can derive the location information of the specified base station and derive base stations located near the derived location information. The specified base station and base stations near the specified base station can be considered as sensing-related base stations.

[0436] The method of performing sensing using sensing-related base station information can appropriately apply the method disclosed in Implementation 2.

[0437] Other methods are disclosed. Sensing-related UEs are derived from information about the vicinity of a specified base station. LMF can derive sensing-related UEs. LMF exports the location information of a specified base station and exports UEs existing near the exported location information. These UEs can be used as sensing-related UEs.

[0438] The method for performing sensing using sensing-related UE information can appropriately apply the method disclosed in Implementation 1.

[0439] Other methods are disclosed. LMF can derive the sensing-related base station and the sensing-related UE based on information about the vicinity of a specified base station. The method for performing sensing using the sensing-related base station information and the sensing-related UE information can appropriately apply the methods disclosed in Embodiments 1 and 2.

[0440] Other methods are disclosed. The node initiating the sensing request sends information about the designated base station to a node that records AMF information serving the base station. For example, this information can be sent by a gateway when an external device initiates the sensing request. The node recording AMF information serving the base station is, for example, a management node (MnS, OAM, etc.). Based on the information about the designated base station, this node derives the AMF serving that base station. Furthermore, this node can derive neighboring base stations of the designated base station. Neighboring base stations can be base stations served by the AMF serving the designated base station.

[0441] The node sends information about the derived specified base station and its neighboring base stations to the SF. This information can be used as sensing-related base station information. The node can send this information to the SF via the AMF. Alternatively, the node can send this information to the SF via the gateway. The node sends information about the AMF and sensing-related base station information to the gateway. The gateway uses the received information about the AMF to send a sensing request to the AMF. This request may include sensing-related base station information. The AMF sends a sensing request to the SF. This request may also include sensing-related base station information. Thus, a sensing request can be sent from the AMF applicable to sensing-related base stations to the SF.

[0442] The method of performing sensing using sensing-related base station information can appropriately apply the method disclosed in Implementation 2.

[0443] Figure 19 is a diagram illustrating other sequence examples of sensing processing. An example of performing sensing processing without using an LMF is disclosed. Steps common to Figures 15, 16, and 17 are labeled with the same step numbers, and common descriptions are omitted.

[0444] In step ST1501, when a sensing request is generated in the external device, in step ST1503, the external device sends the sensing request to the gateway, and the gateway receives the sensing request. The sensing request may include, for example, information about a specified base station as information about the sensing area. In step ST1801, the gateway sends a base station information request to the MnS. This request may include information about the sensing area. The request may also include information about a specified base station. Upon receiving the request, the MnS derives information about the AMF serving the specified base station, senses the relevant base station information, and sends it to the gateway as base station information in step ST1803.

[0445] As information about the sensing area, it can include information about the specified area. MnS can derive the sensing-related base station from the information about the specified area, and derive information about the AMF serving that base station.

[0446] In step ST1515, the gateway uses the received information about the AMF to send a sensing request to the AMF. In step ST1519, the AMF sends a sensing request to the SF. The AMF may include sensing-related base station information in this request. The request may include information contained in the sensing request. The processing of steps S1501 to ST1519 is collectively referred to as the sensing request processing of step ST1891. In step ST1621, the SF can determine the sending base station based on the sensing-related base station information. The processing of steps ST1594, ST1563, ST1565, and ST1595 following step ST1692 is the same as that in Figures 15-18.

[0447] Therefore, SF can obtain sensing-related base station information without using LMF.

[0448] Therefore, when a sensing request includes information such as the vicinity of a specified base station, the UE and the base station can be used to sense the target. For example, the vicinity of a specified base station can be used as the sensing target. For example, sensing can be performed with a specified base station as the transmitting base station. In a mobile communication system, not only communication can be performed, but sensing can also be carried out.

[0449] Implementation method 4.

[0450] This embodiment discloses other methods for solving the problems disclosed in Embodiment 1.

[0451] The sensing-related base station is derived from information about the vicinity of a specified UE. This derivation can utilize information about the vicinity of the specified UE included in the sensing request. The LMF can derive the sensing-related UEs from this information. For example, the LMF can derive the location information of the specified UE and UEs located near the derived location information. The specified UE and UEs near the specified UE can be considered as sensing-related UEs. "Vicinity" can be, for example, UEs within a specified distance from the specified UE. For example, it can be UEs within a specified area where the specified UE exists. The specified distance can be predetermined by standards, etc., or determined and notified to the LMF by the SF (Sensing Provider). Alternatively, it can be determined and notified to the LMF by an external device that initiates sensing processing, an NW node, or a management node.

[0452] LMF can derive sensing-related base stations from information about the vicinity of a specified UE. For example, LMF can derive the location information of a specified UE and then derive the base stations located near that location. These base stations near the specified UE can be used as sensing-related base stations.

[0453] For example, a gateway can send information about the vicinity of a specified UE, included in a sensing request, to the LMF. The LMF can then use this information to derive sensing-related UE information. Additionally, sensing-related base station information can also be derived.

[0454] The method for performing sensing using sensing-related UE information and sensing-related base station information can appropriately apply the methods disclosed in Embodiment 1 and Embodiment 2.

[0455] The gateway can request information about a specified UE from the UDM. This request may include the identifier of the specified UE. Upon receiving the request, the UDM sends the specified UE information to the gateway.

[0456] The gateway uses the AMF information serving the specified UE received from the UDM to send a sensing request to the AMF. Thus, for example, the AMF can receive the sensing request even if the gateway does not identify the AMF serving the specified UE.

[0457] The AMF can send a request to the LMF to provide sensing-related UE information. The AMF can also send a request to the LMF to provide sensing-related base station information. The AMF can send this request in a single message. This request may include information about the vicinity of a specified UE that was included in the sensing request. Additionally, the request may include information about the specified UE received from the UDM. The AMF can send this request to the LMF via the SF. The LMF can use this information to derive sensing-related UE information. Furthermore, the LMF can use this information to derive sensing-related base station information.

[0458] Figure 20 is a diagram illustrating other sequence examples of sensing processing. Examples of LMF deriving sensing-related UE information and sensing-related base station information are disclosed. Furthermore, the use of the interface between the AMF and LMF is disclosed. Steps common to Figures 15 and 16 are labeled with the same step numbers, and common descriptions are omitted.

[0459] In step ST1501, a sensing request is generated in the external device. In step ST1503, the gateway that receives the sensing request from the external device sends a UE information request to the UDM in step ST1511. In step ST1513, the gateway obtains UE information from the UDM. Then, in step ST1515, a sensing request is sent to the AMF. In step ST1901, the AMF sends a request to the LMF to provide sensing-related UE information and sensing-related base station information. This sending can use the interface between the AMF and the LMF. In step ST1903, the LMF derives the sensing-related UE information and sensing-related base station information. In step ST1905, the LMF sends the sensing-related UE information and sensing-related base station information to the AMF. In step ST1519, the AMF sends a sensing request to the SF. The processing of steps S1501 to ST1519 is collectively referred to as the sensing request processing of step ST1991.

[0460] Therefore, communication with the LMF is possible even without an interface between the gateway and the LMF. It can obtain sensing-related UE information and sensing-related base station information from the LMF. Target sensing can be performed using the UE and base station.

[0461] Other methods are disclosed. The gateway sends a sensing request to the AMF. The AMF can derive sensing-related base station information from information about the vicinity of the specified UE. The AMF derives the base stations serving the specified UE. The AMF can derive base stations adjacent to this base station. These base stations can be designated as sensing-related base stations. Furthermore, the specified UE can be designated as a sensing-related UE.

[0462] The AMF sends a sensing request to the SF. This request may include sensing-related base station information and / or sensing-related UE information. Therefore, the SF can obtain sensing-related base station information and sensing-related UE information without going through the LMF. This aims to simplify processing in the LMF and reduce signaling load.

[0463] The method for performing sensing using sensing-related UE information and sensing-related base station information can appropriately apply the methods disclosed in Embodiments 1 and 2 above.

[0464] When there is only one UE, the transmitting base station can derive the sensing related UEs. The sensing method using this method can appropriately apply the method disclosed in Implementation 2.

[0465] Therefore, when a sensing request includes information such as the vicinity of a specified UE, the UE and the base station can be used to sense the target. For example, the vicinity of a specified UE can be used as the sensing target. For example, sensing can be performed with a specified UE as the receiving UE. In mobile communication systems, not only communication can be performed, but sensing can also be carried out.

[0466] Implementation method 5.

[0467] This embodiment discloses other methods for solving the problems disclosed in Embodiment 1.

[0468] Embodiment 1 discloses a method for sending a sensing request from an external device, AF, from AMF to SF. This embodiment discloses other methods.

[0469] Sensing requests are sent to the SF without going through the AMF. A node that initiates a sensing request sends the request to the SF, in this case, without going through the AMF. For example, an external device can send a sensing request to the SF via a gateway.

[0470] The SF requests sensing-related UE information from the LMF. An interface can be set up between the SF and the LMF. This interface can be used in the transmission of signaling between the SF and the LMF. The SF can request sensing-related base station information from the LMF. Upon receiving this request from the SF, the LMF derives the sensing-related UE information and / or sensing-related base station information. The LMF then sends the derived sensing-related UE information and / or sensing-related base station information back to the SF. Thus, the SF can obtain this information from the LMF.

[0471] SF uses sensing-related UE information and sensing-related base station information to determine the receiving UE and the transmitting base station.

[0472] The SF can request information about the receiving UE from the UDM. This request may include receiving UE information determined by the SF. The UDM derives information about the UE from this UE information. The UDM can then send the derived UE information back to the SF. Thus, the SF can obtain information about the AMF serving the receiving UE. The SF can select the AMF to which it sends the sensing request. The SF can then send the sensing request to the selected AMF.

[0473] The SF can request information about the UE from the UDM. This request may include information about the sensing-related UE. The UDM extracts information about the UE from this UE information. The UDM can then send the extracted information about the UE to the SF. Thus, the SF can obtain information about the AMF serving the sensing-related UE. For example, the SF can perform this process before deciding to accept the UE. The SF can use the information about the UE received from the UDM to decide which UE to accept. The SF can use the sensing-related UE's subscription information and the AMF information serving that UE received from the UDM to decide which UE to accept. For example, a UE served by the same AMF can be selected as the accepting UE. This allows for more flexible UE selection.

[0474] The AMF can initiate a service request for a sensing-related UE. This service request can include information indicating that it is for sensing purposes. The sensing-related UE is connected to the AMF. An RRC connection with the base station can be maintained. This is effective even if the sensing-related UE is not connected to either the AMF or the base station.

[0475] Figure 21 is a diagram illustrating other sequence examples of sensing processing. An example of sending a sensing request to the SF without going through the AMF is disclosed. Furthermore, an example of the LMF deriving sensing-related UE information and sensing-related base station information is disclosed. Steps common to Figures 15 and 16 are labeled with the same step numbers, and common descriptions are omitted.

[0476] In step ST1501, a sensing request is generated in an external device. In step ST1503, the gateway that receives the sensing request sends it to the SF in step ST2001. The gateway may have an SF selection function. In step ST2003, the SF sends a request to the LMF to provide sensing-related UE information and sensing-related base station information. This transmission can use the interface between the SF and the LMF. In step ST2005, the LMF exports the sensing-related UE information and sensing-related base station information. In step ST2007, the LMF sends the sensing-related UE information and sensing-related base station information to the SF. The SF can obtain the sensing-related UE information and sensing-related base station information.

[0477] In step ST2009, the SF can send a UE information request to the UDM. This request may include sensing-related UE information. The UDM exports the UE information of the sensing-related UE and sends it to the SF in step ST2011. The SF can then obtain the UE information of the sensing-related UE from the UDM. The processes from step ST1501 to step ST2011 are collectively referred to as the sensing request processing in step ST2091.

[0478] Following the processes in steps ST1592, ST1535, ST1593, and ST1594, in step ST1563, the SF derives the sensing results using the sensing measurement results obtained from the receiving UE. After determining whether resenting is necessary in step ST1565, the SF sends the sensing results to the gateway in step ST2071. In step ST2073, the gateway sends the sensing results to external devices. The processes in steps ST2071 and ST2073 are collectively referred to as the sensing result reporting process in step ST2095.

[0479] Therefore, sensing requests can be sent to the SF without going through the AMF. Sensing results can be sent to external devices without going through the AMF. Sensing requests can be notified to the SF as early as possible. Sensing results can be provided to external devices as early as possible. Therefore, sensing processing of targets using the UE and base station can be performed with low latency.

[0480] Figure 22 is a diagram illustrating other sequence examples of sensing processing. An example of sending a sensing request to the SF without using the AMF is disclosed. Furthermore, an example of performing sensing processing without using the LMF is disclosed. Steps common to Figures 15, 16, 18, and 21 are labeled with the same step numbers, and common descriptions are omitted.

[0481] As illustrated in the example of Figure 21, when a sensing request is generated in an external device, the external device sends the sensing request to the gateway, and the gateway sends the sensing request to the SF. This does not go through the AMF. As illustrated in the example of Figure 19, the gateway receiving the sensing request can, for example, request sensing-related base station information from the MnS.

[0482] In step ST1621, the SF determines the transmitting base station. For example, if the sensing request includes information about the sensing area, and that information includes specified base station information, the SF can determine that base station as the transmitting base station. The request processing for providing sensing-related base station information to the MnS can be omitted.

[0483] In steps ST1791 and ST1594, sensing setting and sensing measurement are performed. In steps ST1563 and ST1565, it is determined whether to perform sensing again. In step ST2095, the sensing result is sent directly to the external device without going through the AMF.

[0484] Thus, the effects shown in Figure 21 can be obtained. Furthermore, sensing processing can be performed without using LMF. Sensing processing of targets using the UE and base station can be performed with lower latency.

[0485] By employing this method, sensing requests from nodes that initiate sensing requests, such as external devices, can be sent without going through the AMF. Since the SF can receive sensing requests as early as possible, sensing processing can be performed earlier. Furthermore, sensing results can be sent to external devices without going through the AMF. Nodes initiating sensing requests can obtain sensing results as early as possible. Sensing processing latency can be reduced. Additionally, it is possible to reduce the signaling load between the AMF and SF.

[0486] Implementation method 6.

[0487] As mentioned above, sensing differs from communication in that the target is not limited to the UE. If the target is the UE, information about that UE can be processed within the mobile communication system. However, if the target is not the UE, how to process the sensing results within the mobile communication system becomes a problem.

[0488] This embodiment discloses a method for processing sensing results in a mobile communication system.

[0489] Sensing results are managed within NW nodes. Target information can be managed within NW nodes. For example, sensing results can be included within target information. Sensing results can be associated with target information. NW nodes can be nodes related to sensing processing. Examples of nodes related to sensing processing include SF (Sensing Server), Sensing Server, AMF (Audio Functional Frame), and NWDAF (Non-Wide Sensor AF). SF can function as a sensing server.

[0490] To manage sensing results, it is necessary to store them. Methods for storing sensing results are disclosed.

[0491] The sensing results can be stored in association with other information. For example, they can be stored in association with information included in the sensing request. For instance, they can be stored in association with information used to determine the sensing request. This allows identification of which sensing request the sensing results pertain to.

[0492] As another method, for example, the sensing results can be stored in association with information used for communication. Ten examples of information associated with sensing results are disclosed below.

[0493] (1) Location information.

[0494] (2) Base station information.

[0495] (3) UE information.

[0496] (4) Send node information.

[0497] (5) Receive node information.

[0498] (6) AMF information for transmitting base stations.

[0499] (7) Serves to receive AMF information from UE.

[0500] (8) Send the location management information of the node.

[0501] (9) Receive the location management information of the node.

[0502] (10) Combinations of (1) to (9).

[0503] (1) For example, it could be information about the area of ​​the sensing target. Information about the sensing area is stored in association with the sensing results.

[0504] (2) For example, it could be information about the transmitting base station. This information could be an identifier. The information about the transmitting base station is stored in association with the sensing results.

[0505] (3) For example, it could be information about the receiving UE. This information could be an identifier. The information about the receiving UE is stored in association with the sensing results.

[0506] (4) Information about the transmitting node. This node may or may not be a base station. This information may be an identifier. The information about the transmitting node is stored in association with the sensing results.

[0507] (5) Information about the receiving node. This node may or may not be a UE. This information may be an identifier. The information about the receiving node is stored in association with the sensing results.

[0508] (6) Information about the AMF serving the transmitting base station. This information may be an identifier. The information about the AMF serving the transmitting base station is stored in association with the sensing results.

[0509] (7) is information about the AMF serving the receiving UE. This information may be an identifier. The information about the AMF serving the receiving UE is stored in association with the sensing results.

[0510] (8) Information concerning the location management of the transmitting node. This node may or may not be a base station. For example, this information may be location information or speed information. Any information obtained through location management is acceptable. The location management information of the transmitting node is stored in association with the sensing results.

[0511] (9) Information regarding the location management of the receiving node. This node may or may not be a UE. For example, this information may be location information or speed information. Any information obtained through location management is acceptable. The location management information of the receiving node is stored in association with the sensing results.

[0512] In this way, by associating the information used in the communication with the sensing results, the sensing results can be identified and stored in the mobile communication system.

[0513] Identification information for target identification can be set. Identification information can be assigned to targets. NW nodes can assign identification information to targets. These NW nodes can be, for example, SF, NWDAF, AMF, RAN nodes, UEs, etc. This identification information can be unique within the NW. Alternatively, the identification information can be generated using the identifiers of each node and identifiers within each node, through a combination of these. For example, it can identify which node's coverage area the target exists in, or which node sensed the target.

[0514] The identification information used to determine the target can be used as target information. The target identification information can be stored and managed in association with the sensing results.

[0515] Therefore, even when the target is not the UE, the target can be determined within the NW, and the sensing results can be managed. In mobile communication systems, sensing can be performed, and the sensing results can be managed.

[0516] Implementation method 7.

[0517] When a UE (User Equipment) communicating in a mobile communication system performs sensing, it must, for example, switch from a communication frequency band to a sensing frequency band to receive sensing resources. This switching process and sensing resource reception process must not interfere with communication. Therefore, a method is needed that allows sensing during the UE's communication process.

[0518] This embodiment discloses a method for solving this problem.

[0519] Configure the sensing measurement gap (called S-MGAP). Configure the S-MGAP for the receiving UE. The S-MGAP configuration for the receiving UE can be one or multiple. A configuration identifier can be set for the S-MGAP. The same S-MGAP can be configured for multiple UEs. The receiving UE performs sensing measurements within the S-MGAP.

[0520] The SF sets up S-MGAP. The SF can use sensing configuration information received from the transmitting base station to set up S-MGAP. The SF can set up the same S-MGAP for one or more receiving UEs. Sensing measurements can be performed using one or more receiving UEs during the same S-MGAP period. Sensing measurements are performed on one or more receiving UEs. S-MGAP can be set up for each receiving UE, or multiple receiving UEs (or a group of receiving UEs). Because it is set up individually for each receiving UE or group of receiving UEs, it can be set according to the communication status of each receiving UE or group of receiving UEs.

[0521] The following are seven examples of information about S-MGAP used for S-MGAP configuration.

[0522] (1) Gap length.

[0523] (2) Gap offset.

[0524] (3) Cycle.

[0525] (4) Switching time.

[0526] (5) Interval timing advance.

[0527] (6) Information about the service area.

[0528] (7) Combinations of (1) to (6).

[0529] (1) is information about the duration of the gap. (2) is information about the start time of the gap. (3) is information about the cycle when repeating S-MGAP. (4) is information about the RF handover time at the receiving UE. This time can be an allowed time. (5) is information about the time before the set gap start time can begin measurement. This time can be an allowed time. This information can be the period between the gap start time and the measurement start time. The information in (1) to (5) can be expressed in time (e.g., seconds or milliseconds) or in frame timing (e.g., SFN, slot number, symbol number, clock count, etc.).

[0530] (6) Information regarding the serving cell for setting up S-MGAP. For example, it could be the serving cell identifier. This information could be MCG or SCG information. This information could be PCell or PSCell information.

[0531] The SF sends information about S-MGAP to the receiving UE. The SF can include this information in a sensing request. The SF can send this information together with sensing settings, or include it within the sensing settings. The SF can also send this information as a sensing setting and include it in information about sensing measurement settings. Thus, the receiving UE can perform sensing measurements using S-MGAP.

[0532] The SF can send information about S-MGAP to the transmitting base station. The SF can also send this information about S-MGAP to the base station serving the receiving UE. The SF can send this information in association with the identifier of the receiving UE. The base station serving the receiving UE can avoid allocating communication resources to the receiving UE in the S-MGAP settings. Therefore, the receiving UE can perform sensing measurements without interfering with communication.

[0533] The base station serving the receiving UE can configure S-MGAP. The transmitting base station sends sensing settings to the SF. The SF sends the sensing settings to the base station serving the receiving UE. The SF can send the sensing settings to the receiving UE via the base station serving the receiving UE. At this time, the SF can also send the sensing settings to the base station serving the receiving UE. The base station serving the receiving UE uses the received sensing settings to configure S-MGAP. The base station serving the receiving UE can configure S-MGAP specifically for the receiving UE. The base station serving the receiving UE sends information about S-MGAP to the receiving UE. When the SF sends the sensing settings to the receiving UE via the base station serving the receiving UE, it can also send information about S-MGAP. The receiving UE performs sensing measurements in S-MGAP.

[0534] The base station serving the receiving UE can avoid allocating communication resources to the receiving UE in the S-MGAP settings. This allows the receiving UE to perform sensing measurements without interfering with communication. Furthermore, since the base station serving the receiving UE sets up an S-MGAP specifically for that UE, S-MGAPs applicable to the load of each base station and communication with the receiving UE can be configured. This allows for more efficient communication between the receiving UE and the base station, as well as sensing measurements based on the receiving UE.

[0535] When the base station serving the receiving UE is a transmitting base station, the transmitting base station can configure S-MGAP.

[0536] Other methods for configuring S-MGAP at the base station are disclosed. The base station serving the receiving UE can send the S-MGAP configured for the receiving UE to the SF. The SF can then send the S-MGAP received from the base station to the receiving UE. The SF can obtain information about the S-MGAP configured for the receiving UE. The SF can identify during which the receiving UE performs sensing measurements.

[0537] The SF can request S-MGAP configuration from the base station serving the receiving UE. This request may include sensing configuration information set by the transmitting base station. The request may also include information about the receiving UE. The base station receiving the request performs S-MGAP configuration for the receiving UE. The base station may send S-MGAP information to the receiving UE. Alternatively, the base station may send S-MGAP information to the SF. The base station may send the S-MGAP information as a response to the S-MGAP configuration request from the SF.

[0538] Therefore, SF can request S-MGAP settings. Flexible sensing control can be achieved in SF.

[0539] The receiving UE can request S-MGAP configuration from the SF. The receiving UE can request S-MGAP configuration via the base station serving the receiving UE. The request may include the UE's identifier. The request may include reason information. The reason information indicates the reason for requesting S-MGAP configuration. For example, this information could be that sensing is being performed, the sensing frequency is different from the communication frequency, or handover processing is required to receive sensing resources, etc. The request may include information about the desired S-MGAP. The SF receiving the request can configure S-MGAP using the methods disclosed above.

[0540] The receiving UE can request S-MGAP configuration from the base station. The receiving UE can request S-MGAP configuration from the base station serving the receiving UE. This request may include the UE's identifier. The request may include reason information. The request may include information about the desired S-MGAP. The base station receiving the request can configure the S-MGAP for the receiving UE.

[0541] Therefore, the receiving UE can request S-MGAP configuration. S-MGAP configuration can be performed based on the receiving UE's communication and load conditions.

[0542] The execution start / stop of S-MGAP can be configured. This can be set separately from the S-MGAP settings. The S-MGAP execution start / stop settings can include information used to determine the S-MGAP settings to start / stop. For example, it can include the identifiers of the S-MGAP settings disclosed above. The execution start / stop of one or more S-MGAP settings can be performed based on one or more pre-configured S-MGAP settings.

[0543] The SF sends an S-MGAP configuration start / stop message to the receiving UE. The receiving UE uses the S-MGAP configuration that has been started to perform sensing measurements. The receiving UE stops using the S-MGAP configuration that has been stopped to perform sensing measurements. This transmission from the SF to the receiving UE can, for example, use signaling between the SF and the UE. Alternatively, it can use signaling between the SF and the base station, as well as signaling between the base station and the UE.

[0544] Therefore, when it is necessary to change the S-MGAP settings according to the situation, the change of S-MGAP settings can be implemented with low latency without the need for the transmission time of the changed S-MGAP settings and the subsequent processing at the receiving UE.

[0545] The method for initiating / stopping S-MGAP settings is disclosed, but it can also be done by the base station. The base station serving the receiving UE sends the S-MGAP settings initiation / stopping command to the receiving UE. The initiation / stopping of S-MGAP settings can be performed using signaling between the base station and the UE, eliminating the need for signaling between the base station and the UE. This allows for earlier implementation of S-MGAP settings changes.

[0546] The method for initiating / stopping S-MGAP settings via an SF (Signal Provider Interface) is disclosed, but it can also be performed by an external device, NW (Network Controller) node, or management node. An NW node can be, for example, an AF (Automatic Front-End). The external device, NW node, or management node sends the S-MGAP settings start / stop instructions to the receiving UE. This can be done via the SF or via a base station. The method for initiating / stopping S-MGAP settings from the SF or base station can appropriately apply the methods disclosed above. Thus, for example, an external device, NW node, or management node that initiates a sensing request can request the S-MGAP settings start / stop instructions. The external device, NW node, or management node that initiates the sensing request can flexibly control the execution and cessation of sensing processing.

[0547] When S-MGAP execution start / stop settings are configured, execution can be stopped solely through the S-MGAP setting. Execution can then begin using the S-MGAP execution start setting. This allows for real-time execution start / stop functionality based on the S-MGAP settings.

[0548] The execution can be started via S-MGAP settings alone. The execution can be stopped via the S-MGAP stop settings. This reduces signaling load.

[0549] The receiving UE can request the SF to start / stop the execution of S-MGAP settings. The receiving UE can make this request via a base station serving the receiving UE. The request may include the UE's identifier, reason information, and an identifier of the S-MGAP settings for which the start / stop is requested. The SF receiving the request can use the methods disclosed above to start / stop the execution of S-MGAP settings. Therefore, for example, the S-MGAP settings can be changed according to the status of the receiving UE.

[0550] The receiving UE can request the base station to start / stop the execution of S-MGAP settings. The receiving UE can make this request to the base station serving the receiving UE. The request may include the UE's identifier, reason information, and an identifier of the S-MGAP settings for which the start / stop execution is requested. The base station receiving the request can use the methods disclosed above to start / stop the execution of S-MGAP settings. Therefore, for example, the S-MGAP settings can be changed in real time according to the status of the receiving UE.

[0551] Transmissions from the base station to the receiving UE, and vice versa, can utilize signaling between the base station and the UE. For example, RRC signaling can be used, allowing for the transmission of more information. Alternatively, MAC signaling can be used, for example, it can be included in a MAC CE (Control Element), enabling earlier transmission of information. Alternatively, L1 / L2 signaling can also be used, for example, it can be included in DCI or UCI, allowing for even earlier transmission of information.

[0552] Therefore, even when the communication band and frequency differ from those used for sensing, sensing can be performed without interfering with communication with the receiving UE by using a sensing measurement gap. In mobile communication systems, not only communication can be performed, but sensing can also be conducted.

[0553] A communication measurement gap can be used as an S-MGAP. The communication measurement gap can be configured for use with S-MGAP. The configuration method can be appropriately applied as described above. The receiving UE performs sensing measurements using the communication measurement gap configured for S-MGAP. Since the communication measurement gap is used for S-MGAP, information indicating whether it is for sensing can be included in the communication measurement gap configuration. Information indicating whether the measurement gap is for communication or sensing can be configured. The UE receiving this measurement gap configuration can identify whether the measurement gap is for communication or sensing.

[0554] Implementation method 8.

[0555] A method for sensing during the reception of UE communications is disclosed.

[0556] A sensing BWP can be configured. Sensing is performed within the sensing BWP. Sensing resources are transmitted and received within the sensing BWP. The sensing BWP can be configured to be the same as the communication BWP. Sensing can be performed within the same BWP as the communication BWP. The receiving UE does not need to perform frequency switching between communication and sensing. This reduces the complexity of sensing processing.

[0557] The sensing BWP can be configured differently from the communication BWP. Sensing can then be performed within a different BWP than the communication BWP. Because the BWPs used for communication and sensing are different, for example, erroneous operations by the receiving UE performing communication during sensing can be reduced.

[0558] The sensing BWP can be set by the SF. There can be one or more sensing BWPs. The SF can send information about the sensing BWP to the receiving UE. For example, this information could be an identifier for the sensing BWP. The SF can set the sensing BWP using sensing settings received from the transmitting base station. The SF can set the same sensing BWP for one or more receiving UEs performing sensing.

[0559] The sensing BWP can be configured by the base station serving the receiving UE. The transmitting base station sends sensing settings to the SF. The SF sends the sensing settings to the base station serving the receiving UE. The SF can send the sensing settings to the receiving UE via the base station serving the receiving UE. At this time, the SF can send the sensing settings to the base station serving the receiving UE. The base station serving the receiving UE uses the received sensing settings to configure the sensing BWP. A sensing BWP specific to the receiving UE can be configured. The base station serving the receiving UE sends information about the sensing BWP to the receiving UE. When the SF sends the sensing settings to the receiving UE via the base station serving the receiving UE, it can send information about the sensing BWP. The receiving UE performs sensing measurements in the sensing BWP.

[0560] When the base station serving the receiving UE is a transmitting base station, the transmitting base station can configure a sensing BWP.

[0561] For sensing purposes, the base station serving the receiving UE can modify the sensing BWP. The base station serving the receiving UE sends information to the receiving UE indicating the modification to the sensing BWP. This information may, for example, be an identifier of the sensing BWP. For example, RRC signaling can be used. More information can be sent. For example, it can be included in the MAC CE. Information can be sent earlier. For example, L1 / L2 signaling can also be used. For example, it can be included in the DCI. Information can be sent even earlier.

[0562] Multiple sensing BWPs can be configured for the receiving UE. Multiple sensing BWPs are pre-configured, and the information indicating changes to the sensing BWPs described above is used to indicate which of the multiple sensing BWPs to use. This allows for the early configuration of a more suitable sensing BWP.

[0563] Therefore, sensing can be performed using a sensing BWP. This reduces the complexity of sensing processing. For example, the communication frequency layer and the sensing frequency layer can be set to the same value. Different BWPs can be set for communication and sensing within the same frequency layer. This allows communication and sensing to be performed within a single frequency layer, potentially improving frequency resource utilization efficiency. Furthermore, it reduces the number of frequency layers supported by the receiving UE, thus reducing circuit complexity.

[0564] A sensing window (S-WD) can be configured. Sensing is performed within the S-WD. The transmitting base station transmits sensing resources within the S-WD. The receiving UE performs sensing measurements within the configured S-WD.

[0565] Here are 5 examples of information about S-WD.

[0566] (1) BWP.

[0567] (2) Sensing resource settings.

[0568] (3) Information about the timing of S-WD.

[0569] (4) Identification.

[0570] (5) Combinations of (1) to (4).

[0571] (1) Information about the BWP used to set up the S-WD. For example, it could be the identifier of the BWP. (2) Information about the sensor resources used in the S-WD. This could be information about the sensor resources. (2) For example, it could be information used to determine the sensor resources. (2) For example, it could be the identifier of the sensor settings. (3) For example, it could be the duration and offset of the S-WD. (3) For example, it could be the start and end times of the S-WD. (4) Information used to determine the S-WD. When setting up multiple S-WDs, this can indicate which S-WD is being used.

[0572] S-WD settings can be one or multiple. By enabling multiple settings, a more suitable S-WD setting can be used to perform sensing based on the communication status at the receiving UE.

[0573] The Sensor-Warranty (S-WD) can be set by the Sensor Provider (SF). There can be one or more S-WDs. The SF can send information about the S-WD to the receiving UE. The SF can set the S-WD using sensing settings received from the transmitting base station. The SF can set the same S-WD for one or more receiving UEs performing sensing.

[0574] The sensing data path (S-WD) can be configured by the base station serving the receiving UE. The transmitting base station sends sensing settings to the SF. The SF sends the sensing settings to the base station serving the receiving UE. The SF can send the sensing settings to the receiving UE via the base station serving the receiving UE. At this time, the SF can send the sensing settings to the base station serving the receiving UE. The base station serving the receiving UE uses the received sensing settings to configure the S-WD. An S-WD specific to the receiving UE can be configured. The base station serving the receiving UE sends information about the S-WD to the receiving UE. When the SF sends the sensing settings to the receiving UE via the base station serving the receiving UE, information about the S-WD can be sent. The receiving UE performs sensing measurements in the S-WD.

[0575] When the base station serving the receiving UE is a transmitting base station, the transmitting base station can set S-WD.

[0576] For sensing purposes, the S-WD can be changed by the base station serving the receiving UE. The base station serving the receiving UE sends information to the receiving UE indicating the change to the S-WD. This information can be, for example, an identifier of the S-WD. For example, RRC signaling can be used. More information can be sent. For example, it can be included in the MAC CE. Information can be sent earlier. For example, L1 / L2 signaling can also be used. For example, it can be included in the DCI. Information can be sent even earlier.

[0577] Multiple S-WDs can be configured for the receiving UE. Multiple S-WDs can be pre-configured, and the aforementioned information indicating S-WD changes can be used to specify which S-WD among these multiple S-WDs to use. This allows for the configuration of a more suitable S-WD as early as possible.

[0578] Therefore, sensing using S-WD can be performed. The complexity of sensing processing can be reduced. For example, the communication BWP and the sensing BWP can be set to the same value. Within the same BWP, by setting S-WD for sensing, communication and sensing can be performed within a single BWP. This can help improve the efficiency of frequency resource utilization. Furthermore, the number of BWPs supported by the receiving UE can be reduced, thus lowering circuit complexity.

[0579] Implementation method 9.

[0580] Sensing requires a different QoS than communication. This embodiment discloses a method for setting QoS for sensing.

[0581] The following are 14 examples of information regarding QoS for sensing.

[0582] (1) Horizontal accuracy of location information.

[0583] (2) Vertical accuracy of location information.

[0584] (3) Response time of location information.

[0585] (4) Information indicating whether speed is required.

[0586] (5) Speed ​​accuracy.

[0587] (6) Resolution.

[0588] (7) Range resolution.

[0589] (8) Speed ​​resolution.

[0590] (9) Delay amount.

[0591] (10) Sensing service delay.

[0592] (11) Refresh rate.

[0593] (12) Missing detection rate.

[0594] (13) False alarm rate

[0595] (14) Combinations of (1) to (13).

[0596] The method for setting QoS is disclosed. The SF receives information about the QoS required for sensing from external devices and AFs. This information can also include metrics such as KPIs required for sensing. For example, external devices and AFs can include this information or metrics in the sensing request and send it to the SF. The SF can derive information about the QoS required for sensing for use in the NW from the KPIs or other metrics required for sensing.

[0597] The SF (Sensing Node) sends QoS information to the receiving node. For example, the SF can send QoS information to the receiving UE. The SF can also send QoS information to the transmitting node. For example, the SF can send QoS information to the transmitting base station. The SF can send QoS information to the base station serving the receiving UE. The SF can also send QoS information to the AMF (Active Memory Function). The AMF can send QoS information to the transmitting base station and / or the base station serving the receiving UE. Thus, the receiving UE, the transmitting base station, the base station serving the receiving UE, and the AMF can identify the required QoS. To meet this QoS, sensing settings and sensing measurements can be implemented, for example.

[0598] Information about QoS can be included in a sensing request, a sensing configuration request, or a sensing configuration message. Including it in other messages can reduce signaling load.

[0599] The SF can send information about the QoS required for sensing to the SMF or UPF. The SF can also send QoS information via the AMF. For example, sensing measurement results can be sent using the UP (User Plane). For instance, a PDU session can be set up in the UP, and the sensing measurement results can be sent using the PDU session. The SMF and UPF, upon receiving the QoS information required for sensing, can use this information for data transmission control within the PDU session. Control can then be performed more appropriately to meet the QoS requirements for sensing.

[0600] The receiving UE can derive sensing results from its own sensing measurement results. The receiving UE can also derive sensing results using sensing measurement results from itself and other receiving UEs. The receiving UE can notify other receiving UEs of sensing measurement results. This notification can, for example, use an inter-UE interface, such as via a base station or via a signal generator (SF). Thus, the receiving UE can obtain sensing measurement results from other receiving UEs and derive sensing results using these results, resulting in more accurate sensing results.

[0601] The receiving UE can send sensing results using the UP. The receiving UE can send sensing results to the UPF. Sensing results can be sent using a PDU session. The UPF can send sensing results to external devices. The UPF can send sensing results to the DN (Data Network). The DN can send sensing results to external devices. More appropriate control can be implemented to meet the QoS requirements of the sensing.

[0602] SMF or UPF can derive QoS information required for sensing in NW from metrics such as KPIs required for sensing. This is effective, for example, when sensing measurement results are transmitted using UP. SMF or UPF can send this QoS information to the receiving UE, the transmitting base station, or the base station serving the receiving UE. It can also be transmitted via AMF. Thus, the receiving UE, the transmitting base station, and the base station serving the receiving UE can identify the QoS required for sensing. To meet this QoS, sensing measurements in UP can be transmitted, for example.

[0603] Information regarding the QoS required for sensing can be measured. This information can be partially or fully measured at the receiving UE, transmitting base station, base station, AMF, SMF, UPF, and / or SF. Alternatively, any of the nodes, such as the SF, can derive measurement results regarding the QoS required for sensing. Based on these measurement results, it can be determined whether the QoS required for sensing is met. The SF can use this determination to implement more appropriate controls to meet the QoS required for sensing, such as changing the transmitting base station or the receiving UE.

[0604] When other nodes have derived measurement results regarding the QoS requirements for sensing, this node can send a judgment result to the SF indicating whether the QoS requirements for sensing are met. This node can also request changes to desired control indicators from the SF, such as changes to the sending base station or the receiving UE. The SF can use this judgment result and the desired changes to control indicators to implement more appropriate controls to meet the QoS requirements for sensing, such as changing the sending base station or the receiving UE.

[0605] Multiple QoS requirements for sensing can be configured. These QoS requirements can be prioritized. For example, a primary QoS and a secondary QoS can be set. If the QoS required by a higher-priority sensor cannot be met, control can be implemented to satisfy the QoS required by the next higher-priority sensor. For example, if the SF determines that the primary QoS is not being met, it can be changed to a secondary QoS. Therefore, even in harsh environments where sensing capabilities degrade, switching to a lower-priority QoS can prevent sensing processing from stopping. Sensing processing can continue using a lower-priority QoS.

[0606] Therefore, the QoS required for sensing can be set. Even if the QoS required for sensing differs from the QoS required for communication, sensing processing will still be performed to meet the QoS requirements for sensing. This can satisfy the KPIs and other indicators required for sensing.

[0607] Implementation method 10.

[0608] In sensing, the target's velocity, etc., is sometimes required as a result of the sensing. Furthermore, target tracking is sometimes required as a result of sensing or its outcome. This embodiment discloses a method capable of performing such sensing.

[0609] Time information is associated with sensing measurement results. Time information can be assigned to sensing measurement results. The receiving UE associates time information with the measurement results. Time information can be the measurement time, measurement period, measurement start time, and measurement end time. The unit of time information can be year, month, day, hour, etc., or it can be symbol, time slot, subframe, radio frame, etc. Time information can be associated with sensing measurement results for each receiving UE. The time information of the sensing measurement results for each receiving UE can be obtained.

[0610] The receiving UE can send the sensing measurement results and the time information associated with those results, or the sensing measurement results with time information, to the SF. The SF can receive the time information of the sensing measurement results from each receiving UE.

[0611] When multiple sensing measurements are performed continuously or periodically, they can be presented as a series of sensing measurement results. Measurement time information, as part of this series of sensing measurement results, can be associated, for example, with the initial measurement time information and the time interval information of the sensing measurements within the series. Thus, time information can be obtained in association with sensing measurement results performed continuously or at short intervals. Compared to associating measurement time information with each measurement result in a series of sensing measurements, time information can be sent with less information.

[0612] Therefore, time information can be correlated with sensing measurement results. By using multiple acquired sensing measurement results and time information, target tracking can be performed, such as deriving the velocity of the sensed target and deriving the temporal changes in the position of the sensed target.

[0613] Implementation method 11.

[0614] The UE used for sensing may change position due to movement. In this case, the UE may be unable to receive sensing resources reflected by the target. This could result in the UE being unable to function as a receiving UE, leading to a problem where sensing cannot be performed.

[0615] This embodiment discloses a method for solving this problem.

[0616] The NW node periodically sends a request to the LMF to provide sensing-related UE information. The NW node can periodically send this request to the LMF. The NW node can be any node that sends a request to the LMF to provide sensing-related UE information as disclosed in the above embodiments. The NW node can be, for example, a gateway, AMF, SF, etc. The NW node can be, for example, a transmitting base station, a receiving UE, or a base station serving the receiving UE. These NW nodes can send the request via the AMF, SF, gateway, etc. This period can be derived by the NW node using the information contained in the sensing request.

[0617] This period can be included in the sensing request. For example, an external device can send this information in the sensing request. The NW node can use this period included in the sensing request to periodically send sensing-related UE information provision requests to the LMF.

[0618] Alternatively, a request to provide sensing-related UE information can be triggered to the LMF based on specified conditions. For example, the specified conditions could be that the RSRP of the sensing resources received by the UE is below a specified threshold (or less than a specified threshold). This is not limited to this; it could also be an indicator of other sensing measurement results, information about the sensing results, or information about the QoS required for the sensing. The specified threshold can be preset in the node that triggers the request to provide sensing-related UE information to the LMF.

[0619] This specified threshold can be included in the sensing request. For example, an external device can send the specified threshold in the sensing request. The NW node can use the specified threshold included in the sensing request to trigger a request to send sensing-related UE information to the LMF.

[0620] As a condition, for example, when the base station receiving the UE's connection changes, it can send a request to the LMF to provide sensing-related UE information. For example, the base station before the change of connection with the receiving UE could send a request to the LMF to provide sensing-related UE information, and the base station after the change of connection with the receiving UE could also send a request to the LMF to provide sensing-related UE information.

[0621] The receiving UE can periodically or under specified conditions trigger a request to the LMF to provide sensing-related UE information. These specified conditions may include, for example, when the receiving UE leaves the sensing area, when the receiving UE moves a specified distance or more, or when the receiving UE reaches a specified speed or more. For example, this can be implemented when the receiving UE exports location management information. For instance, a receiving UE with location management information can export its positional relationship with the sensing area, use this relationship to determine the specified conditions, and then notify the LMF of the request.

[0622] As a predefined condition, for example, when the base station to which the receiving UE is connected changes, a request for providing sensing-related UE information can be sent to the LMF. As a predefined condition, for example, when the receiving UE is not connected to a base station, such as during RRC_Idle or RRC_Inactive, or when the base station receiving broadcast information changes, a request for providing sensing-related UE information can be sent to the LMF. The receiving UE can send a request for providing sensing-related UE information to the LMF after establishing an RRC connection with the base station. The receiving UE can send a request for providing sensing-related UE information to the LMF when the predefined conditions are met.

[0623] The request to provide sensing-related UE information may include reason information. The reason information may be, for example, information about the specified conditions that triggered the request to provide sensing-related UE information.

[0624] Therefore, the sensing-related UE information can be updated periodically or triggered by specified conditions. The receiving UE can then be updated based on the updated sensing-related UE information.

[0625] Other methods are disclosed. The LMF determines changes in the sensing-related UE. The LMF sends the changed sensing-related UE information to the NW node. The NW node can be any node that sends a request to the LMF to provide sensing-related UE information, as disclosed in the above embodiments. For example, it can be a gateway, AMF, SF, etc. The NW node can be, for example, a transmitting base station, a receiving UE, or a base station serving the receiving UE. These NW nodes can send information via AMF, SF, gateway, etc.

[0626] The Location Management Filter (LMF) possesses the UE's location management information. This location management information includes location information, speed information, etc. For example, when one of the sensing-related UEs leaves the sensing area, the LMF removes that UE from the sensing-related UE list. When another UE enters the sensing area, it is added back to the sensing-related UE list. For example, if a UE moves more than a specified distance, it is removed from the sensing-related UE list. For example, if a UE reaches a speed exceeding a specified limit, it is removed from the sensing-related UE list. When another UE's speed falls below a specified limit, it is added back to the sensing-related UE list. In this way, the LMF can determine changes in the sensing-related UEs by using the UE's location management information.

[0627] Therefore, the LMF can update the sensing-related UE information. The receiving UE can be updated based on the updated sensing-related UE information. The LMF determines the changes in sensing-related UEs and sends the updated sensing-related UE information to the NW node, thus eliminating the need for a request for sensing-related UE information from the NW node. This reduces signaling load and streamlines the signaling transmission and processing in the NW node.

[0628] By employing the method disclosed in this embodiment, even if the UE used for sensing moves and becomes unsuitable as a receiving UE, the UE used for sensing can be updated to another UE. Sensing can continue using the updated UE.

[0629] Implementation method 11, variation 1.

[0630] The base stations used for sensing can also be mobile. Mobile base stations can be used for sensing. For example, a mobile base station can be used as a sensing-related base station. For example, a mobile base station can be used as a transmitting base station.

[0631] When using a mobile base station for sensing, the base station may be unable to transmit sensing resources to the target. This can result in the base station failing to function as a transmitting base station, leading to a failure to perform sensing operations.

[0632] Publicly disclose methods for solving this problem.

[0633] The NW node periodically sends a request to the LMF to provide sensing-related base station information. The NW node can periodically send this request to the LMF. The NW node can be any node that sends a request to the LMF to provide sensing-related base station information as disclosed in the above embodiments. The NW node can be, for example, a gateway, AMF, SF, etc. The NW node can be, for example, a transmitting base station, a receiving UE, or a base station serving the receiving UE. These NW nodes can send the request via the AMF, SF, gateway, etc. This period can be derived by the NW node using the information contained in the sensing request.

[0634] This period can be included in the sensing request. For example, an external device can send this information in the sensing request. The NW node can use this period included in the sensing request to periodically send sensing-related base station information provision requests to the LMF.

[0635] As another method, a request to provide sensing-related base station information can be sent to the LMF based on specified conditions. These specified conditions could be, for example, when the RSRP of the sensing resources received by the UE is below a specified threshold (or less than a specified threshold). However, this is not limited to these conditions; other indicators of sensing measurement results, information about sensing results, or information about the QoS required for sensing can also be used. The specified threshold can be preset in the node that triggers the request to send the sensing-related base station information to the LMF.

[0636] This specified threshold can be included in the sensing request. For example, an external device can send the specified threshold in the sensing request. The NW node can use this specified threshold included in the sensing request to trigger a request to send sensing-related base station information to the LMF.

[0637] Therefore, the sensing-related base station information can be updated periodically or triggered by specified conditions. The transmitting base station can then be updated based on the updated sensing-related base station information.

[0638] Other methods are disclosed. The LMF determines changes to the sensing-related base station. The LMF sends the changed sensing-related base station information to the NW node. The NW node can be a node that sends a request to the LMF to provide sensing-related base station information, as disclosed in the above embodiments. For example, it can be a gateway, AMF, SF, etc. The NW node can be a transmitting base station, a receiving UE, or a base station serving the receiving UE. These NW nodes can send information via AMF, SF, gateway, etc.

[0639] The Location Management Frame (LMF) possesses location management information for base stations. This location management information includes location information, speed information, etc. For example, when one of the sensing-related base stations leaves the sensing area, the LMF removes that base station from the list of sensing-related base stations. When another base station enters the sensing area, it adds that base station back to the list of sensing-related UEs. For example, if a base station moves more than a specified distance, it is removed from the list of sensing-related base stations. For example, if a base station reaches a speed exceeding a specified limit, it is removed from the list of sensing-related base stations. When another base station's speed drops below a specified limit, it is added back to the list of sensing-related base stations. In this way, the LMF can determine changes in sensing-related UEs by using the base station's location management information.

[0640] Therefore, the LMF can update the sensing-related base station information. The transmitting base station can be updated based on the updated sensing-related base station information. The LMF determines changes in sensing-related base stations and sends the updated sensing-related base station information to the NW node, thus eliminating the need for a request for sensing-related base station information from the NW node. This reduces signaling load and streamlines the signaling transmission and decision-making process within the NW node.

[0641] By employing the method disclosed in this embodiment, even if the base station used for sensing moves and becomes unsuitable for transmitting, the base station used for sensing can be updated to another base station. Sensing can continue using the updated base station.

[0642] In this specification, a node can be a function. Alternatively, a node can also be an entity.

[0643] In this specification, it is referred to as a base station, but unless otherwise specified, it may also be a RAN node. It can be a RAN node TRP or a TP (Transmission Point). A RAN node can be a CU or a DU. A RAN node can be an IAB node. A RAN node can be a DU of an IAB node.

[0644] In this specification, the UE can be an IAB node. The UE can be the MT (Mobile Termination) of the IAB node.

[0645] In the communication system disclosed herein, one gNB constitutes one or more cells. In this disclosure, it is referred to as gNB or cell, but unless otherwise specified, it can be either gNB or cell.

[0646] In this disclosure, gNB can be either MCG or SCG.

[0647] The above embodiments and their modifications are merely illustrative, and the embodiments and their modifications can be freely combined. Furthermore, any structural elements of the embodiments and their modifications can be appropriately modified or omitted.

[0648] For example, in the above embodiments and their variations, a time slot is an example of a time unit for communication in a 5G communication system. A time slot can be a scheduling unit. In the above embodiments and their variations, processing can be performed by recording in time slot units, such as TTI units, subframe units, sub-time slot units, and micro-time slot units.

[0649] For example, the methods disclosed in the above embodiments and their variations can be applied to IABs. They can be applied to communication between the IAB host and IAB nodes. They can also be applied to the processing of Uu within an IAB.

[0650] The various methods disclosed herein are summarized and recorded below as appendices.

[0651] (Appendix 1) A communication system, characterized in that it comprises: a base station corresponding to a fifth-generation wireless access system; and a communication terminal connected to the base station, which, based on a sensing request from an external device and information about a sensing area, derives sensing-related nodes from at least any one of the base station and the communication terminal, and determines, from the derived nodes, a sensing transmitting node for transmitting sensing resources and a sensing receiving node for receiving the sensing resources.

[0652] (Note 2) The communication system as described in Note 1 is characterized in that, based on the information about the sensing area, the communication terminal related to the sensing, namely the sensing-related communication terminal, is exported as the sensing-related node.

[0653] (Note 3) The communication system as described in Note 1 or 2 is characterized in that, based on the information about the sensing area, the base station related to the sensing, i.e. the sensing-related base station, is derived as the sensing-related node.

[0654] (Appendix 4) The communication system as described in Appendix 3 is characterized in that the information about the sensing area includes information for determining the base station, and based on the information about the sensing area for determining the base station included in the information about the sensing area, the determined base station and base stations near the determined base station are derived as the sensing-related base stations.

[0655] (Appendix 5) The communication system as described in Appendix 3 is characterized in that the information about the sensing area includes information for determining the communication terminal, and based on the information about the sensing area for determining the communication terminal included in the information about the sensing area, the base station near the determined communication terminal is derived as the sensing-related base station.

[0656] (Note 6) The communication system as described in any one of Notes 1 to 5 is characterized in that it further comprises: a gateway for accepting the sensing request; a sensing function for managing the sensing; and a location management function for deriving the sensing-related node.

[0657] (Note 7) The communication system as described in Note 6 is characterized in that, in the sensing function, the sensing request is received from the gateway, and the information of the sensing-related node is requested from the location management function according to the sensing request, and the sensing sending node and the sensing receiving node are determined based on the information of the sensing-related node obtained from the location management function.

[0658] (Note 8) The communication system as described in any one of Notes 1 to 7 is characterized in that the sensing results obtained by sensing using the sensing transmitting node and the sensing receiving node are stored in association with information for communication.

[0659] (Note 9) The communication system as described in any one of Notes 1 to 8 is characterized in that a sensing measurement gap is set for the sensing receiving node.

[0660] (Note 10) The communication system as described in any one of Notes 1 to 9 is characterized in that a sensing bandwidth portion is set for the sensing receiving node, and the sensing receiving node receives the sensing resources within the sensing bandwidth portion.

[0661] (Note 11) The communication system as described in any one of Notes 1 to 10 is characterized in that information about the quality of service required for sensing is derived and sent to each of the sensing transmitting node and the sensing receiving node.

[0662] (Note 12) The communication system as described in any one of Notes 1 to 11 is characterized in that the sensing receiving node associates time information with the sensing measurement results.

[0663] (Note 13) The communication system as described in any one of Notes 1 to 12 is characterized in that the information of the sensing-related nodes is updated periodically or triggered by predetermined conditions, and at least any one of the sensing-transmitting nodes and the sensing-receiving nodes is changed based on the updated information of the sensing-related nodes.

[0664] (Note 14) The communication system as described in any one of Notes 1 to 12 is characterized in that it further includes a location management function, which has the location information of the communication terminal and derives the sensing-related nodes. The location management function determines whether the sensing-related nodes have changed based on the location information of the communication terminal and the information about the sensing area, and updates the information of the sensing-related nodes when the sensing-related nodes have changed.

[0665] Label Explanation

[0666] 202 Communication terminal device (mobile terminal)

[0667] 210 Communication System

[0668] 213, 240-1, 240-2, 750 Base Station Equipment (NR Base Station, Base Station)

[0669] 214 5G Core Unit

[0670] 215 Central Unit

[0671] 216 Distributed Units

[0672] 217 Control plane central unit

[0673] 218 User-facing Central Unit

[0674] 219 TRP

[0675] 301 and 403 Protocol Processing Department

[0676] 302 Application Department

[0677] 304 and 405 coding sections

[0678] Modulation sections 305 and 406

[0679] 306, 407 Frequency Conversion Section

[0680] Antennas 307-1 to 307-4 and 408-1 to 408-4

[0681] 308, 409 De-escalation Department

[0682] Decoding sections 309 and 410

[0683] Control Departments 310, 411, and 526

[0684] 401 EPC Communications Department

[0685] 402 Other Base Station Communications Department

[0686] 412 5GC Communications Department

[0687] 521 Data Network Communications Department

[0688] 522 Base Station Communications Department

[0689] 523 User Plane Communications Department

[0690] 523-1 PDU Processing Department

[0691] 523-2 Moving Anchoring Unit

[0692] 525 Control Panel Control Unit

[0693] 525-1 NAS Security Department

[0694] 525-2 Idle Status Mobility Management Department

[0695] 527 Session Management Department

[0696] 527-1 PDU Session Control Unit

[0697] 527-2 UE IP Address Allocation Department

[0698] 751-1~751-8 Beams

[0699] 752 Community

[0700] 1100 Learning Device

[0701] Data Acquisition Departments 1110 and 1210

[0702] 1120 Model Generation Department

[0703] 1121 Compensation Calculation Department

[0704] 1122 Function Update Section

[0705] 11:30 Completed learning of the model storage department

[0706] 1200 Reasoning Device

[0707] 1220 Reasoning Department.

Claims

1. A communication system, characterized in that, It includes: a base station corresponding to a fifth-generation wireless access system; and a communication terminal connected to the base station, which, based on a sensing request from an external device and information about the sensing area, derives sensing-related nodes from at least any one of the base station and the communication terminal, and determines, from the derived nodes, a sensing transmitting node for transmitting sensing resources and a sensing receiving node for receiving the sensing resources.

2. The communication system as described in claim 1, characterized in that, Based on the information about the sensing area, the communication terminal related to the sensing, i.e., the sensing-related communication terminal, is exported as the sensing-related node.

3. The communication system as described in claim 1, characterized in that, Based on the information about the sensing area, the base station related to the sensing, i.e., the sensing-related base station, is exported as the sensing-related node.

4. The communication system as described in claim 3, characterized in that, The information about the sensing area includes information for determining the base station. Based on the information about the sensing area for determining the base station, the determined base station and base stations near the determined base station are derived as the sensing-related base stations.

5. The communication system as described in claim 3, characterized in that, The information about the sensing area includes information for determining the communication terminal. Based on the information about the sensing area for determining the communication terminal, the base stations near the determined communication terminal are derived as the sensing-related base stations.

6. The communication system as described in claim 1, characterized in that, It also includes: a gateway that accepts the sensing request; a sensing function that manages the sensing; and a location management function that exports the sensing-related nodes.

7. The communication system as described in claim 6, characterized in that, In the sensing function, the sensing request is received from the gateway, and the location management function is requested to obtain information about the sensing-related nodes based on the sensing request. Based on the information about the sensing-related nodes obtained from the location management function, the sensing sending node and the sensing receiving node are determined.

8. The communication system as described in claim 1, characterized in that, The sensing results obtained by using the sensing transmitting node and the sensing receiving node are stored in association with information used for communication.

9. The communication system as described in claim 1, characterized in that, A sensing measurement gap is set for the sensing receiving node.

10. The communication system as described in claim 1, characterized in that, A sensing bandwidth portion is set for the sensing receiving node, and the sensing receiving node receives the sensing resources within the sensing bandwidth portion.

11. The communication system as described in claim 1, characterized in that, Information regarding the quality of service required for sensing is exported and sent to each of the sensing transmitting node and the sensing receiving node.

12. The communication system as described in claim 1, characterized in that, The sensing receiving node associates time information with the sensing measurement results.

13. The communication system as described in claim 1, characterized in that, The information of the sensing-related nodes is updated periodically or triggered by specified conditions, and at least any one of the sensing-transmitting nodes and sensing-receiving nodes is changed based on the updated information of the sensing-related nodes.

14. The communication system as described in claim 1, characterized in that, It also includes a location management function, which has the location information of the communication terminal and exports the sensing-related nodes. The location management function determines whether the sensing-related nodes have changed based on the location information of the communication terminal and the information about the sensing area. When the sensing-related nodes have changed, the information of the sensing-related nodes is updated.

Images