Base station and network node

Abstract

This network node comprises: a reception unit that receives, from a plurality of base stations, first messages each including a list of sensing ranges to be supported and requesting interface setups; a control unit that sets up a union of the lists received from the plurality of base stations as a second list of sensing ranges that the own device can handle; and a transmission unit that transmits, to a first network node, a second message including the second list and requesting registration of the own device.

Description

Base Stations and Network Nodes

[0001] The present invention relates to base stations and network nodes in communication systems.

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. Various wireless technologies are being studied for 5G to meet the requirements of achieving a throughput of 10 Gbps or more while keeping latency in wireless sections to 1 ms or less.

[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the network architecture of LTE, is being considered (for example, Non-Patent Document 1).

[0004] Furthermore, in 3GPP Rel-19, seven sensing service categories and requirements for each category are being considered for three scenarios of sensing using 5G networks: object detection and tracking, environment monitoring, and motion monitoring (see, for example, Non-Patent Document 2).

[0005] 3GPP TS 23.501 V18.4.0 (2023-12) 3GPP TS 22.137 V19.0.0 (2023-12) 3GPP TS 29.510 V18.5.0 (2023-12) 3GPP TS 29.520 V18.4.0 (2023-12) 3GPP TS 29.554 V18.2.0 (2023-12) 3GPP TS 38.455 V18.0.0 (2023-12) 3GPP TS 29.518 V18.4.0 (2023-12)

[0006] In 3GPP Rel-19, seven sensing service categories and requirements for each category are being considered for three scenarios of sensing using 5G networks: object detection and tracking, environment monitoring, and motion monitoring (see, for example, Non-Patent Document 2).

[0007] However, no method has been studied for providing a sensing service that satisfies these requirements.

[0008] The present invention has been made in view of the above points, and has as its object to provide a sensing service in a wireless communication system.

[0009] According to the disclosed technology, a network node is provided that has a receiving unit that receives a first message requesting interface configuration from a plurality of base stations, the first message including a list of supported sensing ranges; a control unit that sets the union of the lists received from the plurality of base stations as a second list of sensing ranges that the device can handle; and a transmitting unit that transmits a second message to a first network node, the second message including the second list, requesting registration of the device.

[0010] According to the disclosed technology, it is possible to provide a sensing service in a wireless communication system.

[0011] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. FIG. 3 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. FIG. 4 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of a sixth sequence diagram in an embodiment of the present invention. FIG. 1 is a diagram showing an example of a functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 2 is a diagram showing an example of a functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 3 is a diagram showing an example of a hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG. 4 is a diagram showing an example of a configuration of a vehicle 2001 in an embodiment of the present invention.

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0013] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced, and systems subsequent to LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0014] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.

[0015] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0016] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0017] The AMF is connected to the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are mutually connected via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0018] The SMF is a network node 30 having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that stores the data.

[0019] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0020] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0021] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0022] The SMF is a network node 30 having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is a SEPP in the visited network, and the hSEPP is a SEPP in the home network.

[0023] As shown in Figure 2, a UE is in a roaming environment connected to a RAN and an AMF in a Visited PLMN (VPLMN). The VPLMN and a Home PLMN (HPLMN) are connected via a vSEPP and an hSEPP. The UE can communicate with a UDM in the HPLMN via the AMF in the VPLMN, for example.

[0024] Furthermore, in 3GPP Rel-19, seven sensing service categories and requirements for each category are being considered for three scenarios of sensing using 5G networks: object detection and tracking, environment monitoring, and motion monitoring (see, for example, Non-Patent Document 2).

[0025] (Example) In this example, a procedure for providing a sensing service in a wireless communication system will be described. In this example, an AF (Application Function) 30 uses information related to sensing service quality (Quality of Service, QoS) to request sensing from a PCF (SS-PCF) for SS (Sensing) via an NEF. The SS-PCF transmits a policy control update notification to a Sensing Function (SF). Furthermore, the SF discovers (multiple) AMFs that cover the sensing range. The SF transmits a sensing request to a base station 10 under the AMF. The SS-PCF converts external parameters related to sensing input from the AF via the NEF into internal parameters used within the network.

[0026] When sensing (measurement) by the base station is initiated, the SF receives sensing data from the base station. Furthermore, the SF generates sensing results using an inference model. Here, the base station may transmit a notification indicating that the sensing quality cannot be satisfied to the SF. Furthermore, if the SF determines that the overall sensing quality cannot be satisfied but that the proxy sensing quality can be satisfied, it transmits a proxy sensing quality of service (QoS) to the base station.

[0027] The following describes the details of this embodiment using sequence diagrams to explain the processes executed by the base station 10, AMF 30A, SF 30B, (SS-)PCF 30C, UDM 30D, UDR 30E, NWDAF 30F, ADRF 30G, CHF 30H, NRF 30J, NEF 30K, and AF 30L, as well as the messages transmitted and received. Here, the NWDAF (Network Data Analytics Function) 30F includes an MTLF (Model Training Logical Function) that trains an estimation model used in sensing. The ADRF (Analytics Data Repository Function) 30G holds an inference model used in sensing. The CHF (Charging Function) 30H handles charging related to sensing.

[0028] 3 is a diagram showing an example of a first sequence diagram according to an embodiment of the present invention. The processing of each step in FIG. 3 will now be described.

[0029] S101: The base station 10 sends a request message (NG Setup request) to the AMF 30A requesting interface configuration. The request message includes a list of supported sensing ranges (Sensing Area list, SSA-list). This list is a list of sensing ranges supported by the base station 10 that conforms to the list of tracking ranges (TA (Tracking Area) list) supported by the base station 10. The AMF 30A also receives the lists from multiple base stations, generates a second list that is the union of all the received sensing range lists, and sets the second list as a list of sensing ranges that the AMF 30A can handle.

[0030] S102: The AMF 30A transmits to the base station 10 a response message (NG Setup response) in response to the request message received in S101.

[0031] S103: AMF 30A sends to NRF 30J a request message (Nnrf_NFManagement_NFRegister request, see sections 5.2.2.2.2, 6.1.6.2.2, and 6.1.6.2.11 of Non-Patent Document 3) requesting registration of its own device, including the second list generated in S101. The request message is expressed, for example, as Nnrf_NFManagement_NFRegister request (NFProfile(amfInfo(SSA-list))).

[0032] S104: The NRF 30J sends a response message (Nnrf_NFManagement_NFRegister response) to the request message received in S103 to the AMF 30A.

[0033] S105: The SF 30B transmits a request message (Npcf_SSPolicyControl_Create request) to the (SS-)PCF 30C, requesting cooperation in sensing policy control.

[0034] S106: The (SS-)PCF 30C establishes cooperation for sensing policy control based on the request message received in S105.

[0035] S107: The (SS-)PCF 30C transmits to the SF 30B a response message (Npcf_SSPolicyControl_Create response) in response to the request message received in S105.

[0036] S108: The AF 30L sends a request message (Nnef_Sensing request) to the NEF 30K to request sensing. The request message includes multiple external parameters related to sensing quality of service (QoS), an AF identifier, an AF service identifier, and a subscription request for the requested sensing. The external parameters include a sensing range reference parameter, a sensing target reference parameter, a sensing quality reference parameter, an individual sensing quality parameter, and a proxy sensing quality parameter.

[0037] The sensing range reference parameter contains information about the sensing range.

[0038] The sensing target reference parameter contains information about the sensing target.

[0039] The sensing quality reference parameter contains information about the quality of the sensing.

[0040] The sensing quality individual parameters include information about the values ​​of the individual parameters (eg, period, delay, and jitter) that override the individual parameters specified in the sensing quality reference parameters, and are also used as internal parameters.

[0041] The substitute sensing quality parameter includes information about a quality to be met as a substitute when the quality specified by the sensing quality reference parameter cannot be met.

[0042] S109: The NEF 30K sends to the (SS-)PCF 30C a request message (Npcf_PolicyAuthorization_Create request) requesting sensing, including the external parameters, AF identifier, AF service identifier, and subscription request received in S108. The subscription request includes the notification identifier assigned by the NEF 30K.

[0043] S110: The (SS-)PCF 30C sends to the NEF 30K a response message (Npcf_PolicyAuthorization_Create response) in response to the request message received in S109.

[0044] S111: The NEF 30K sends to the AF 30L a response message (Nnef_Sensing response) in response to the request message received in S108. The response message includes an external notification identifier assigned by the NEF 30K to be included in the notification to the AF 30L in response to the subscription request received in S108.

[0045] S112: The (SS-)PCF 30C converts the external parameters received in S109 into internal parameters. For example, the (SS-)PCF 30C converts the sensing range reference parameter into a sensing range list (SSA-list), the sensing target reference parameter into a sensing target (SStarget), and the sensing quality reference parameter into a sensing quality identifier (SSQI).

[0046] Furthermore, the (SS-)PCF30C derives inter-sensing priority information (SenSing Allocation and Retention Priority, SSARP) and inter-communication service priority information (Allocation and Retention Priority, ARP) from the AF identifier and AF service identifier based on a mapping table appropriately defined by the telecommunications carrier. Here, SSARP indicates the priority among sensing, and ARP indicates the priority among all communication services. Furthermore, in addition to information indicating the high priority, SSARP and ARP may also include information indicating pre-emption allowance (pre-emption vulnerable, i.e., allowing reserved network resources to be released when other high-priority communications or sensing require them) and information indicating pre-emption capability (pre-emption capability, i.e., the ability to release reserved network resources for other low-priority communications or sensing to reserve the network resources).

[0047] The (SS-)PCF 30C also converts the sensing quality reference parameters included in the proxy sensing quality parameters into SSQIs.

[0048] S113: The (SS-)PCF 30C sends a request message (Nudr_DM_Create request) to the UDR 30E to request registration of sensing-related information. The request message includes the internal parameters converted in S112 (SSA-list, SStarget, SSQI, sensing quality individual parameters, proxy sensing quality parameters, SSARP, and ARP).

[0049] S114: The UDR 30E transmits to the (SS-)PCF 30C a response message (Nudr_DM_Create response) in response to the request message received in S113.

[0050] S115: The (SS-)PCF 30C sends a request message (Npcf_SSPolicyControl_UpdateNotify request) to the SF 30B requesting an update of the sensing policy control. The request message includes the internal parameters (SSA-list, SStarget, SSQI, sensing quality individual parameters, proxy sensing quality parameters, SSARP, and ARP) received in S114 and a notification identifier.

[0051] S116: The SF 30B transmits to the (SS-)PCF 30C a response message (Npcf_SSPolicyControl_UpdateNotify response) in response to the request message received in S115.

[0052] S117: The SF 30B performs sensing based on the request from the AF 30L. Furthermore, the SF 30B may perform sensing to improve the inference model of the abnormal situation (ABNORMAL_SCENE).

[0053] Next, the process following S117 will be described. Fig. 4 is a diagram showing an example of a second sequence diagram according to an embodiment of the present invention. The process of each step in Fig. 4 will be described below.

[0054] S201: The SF30B sends a request message (Nnwdaf_MLModelProvision_Subscribe request) to the NWDAF30F requesting subscription to an inference model to satisfy the requested sensing quality of service (QoS). The request message includes the internal parameters converted in S112 of FIG. 3 (see sections 4.5.2.2, 5.4.6.2.2, 5.4.6.2.3, 5.1.6.3.4, 5.4.6.2.13, and 5.2.6.2.3 of Non-Patent Document 4, and 5.6.2.8 of Non-Patent Document 5). For example, for an abnormal state (ABNORMAL_SCENE) event, the request message includes an SSA-list as an event filter and an SSQI and individual sensing quality parameters as model extension information. For object detection (OBJECT_DETECTION) events, SStaget is included as an event filter, and SSQI and individual sensing quality parameters are included as model extension information.For object movement (OBJECT_MOBILITY) events, SStaget is included as an event filter, and SSQI and individual sensing quality parameters are included as model extension information. Furthermore, for example, the request message is expressed as follows: Nnwdaf_MLModelProvision_Subscribe request (NwdafMLModelProvSubsc (mLEventSubscs ([mLEvent(ABNORMAL_SCENE), mLEventFilter (networkArea(SSA-list=aa)), modelProvExt (SSQI, sensing quality individual parameters)],[mLEvent(OBJECT_DETECTION), mLEventFilter(targetObject(SStarget=bb)), modelProvExt(SSQI, sensing quality individual parameters)],[mLEvent(OBJECT_MOBILITY), mLEventFilter(targetObject(SStarget=bb)), modelProvExt(SSQI, sensing quality individual parameters)]), eventReq(immRep))).Here, eventReq(immRep) indicates that an immediate response is required.

[0055] S202: NWDAF30F sends a request message (Nadrf_MLModelManagement_Retrieval request) to ADRF30G requesting the inference model for which subscription was requested in S201.

[0056] S203: The ADRF 30G transmits to the NWDAF 30F a response message (Nadrf_MLModelManagement_Retrieval response) in response to the request message received in S202.

[0057] S204: The NWDAF 30F sends a response message (Nnwdaf_MLModelProvision_Subscribe response) to the SF 30B in response to the request message received in S201. The response message includes information related to the abnormal state (ABNORMAL_SCENE) file and ADRF, information related to the object detection (OBJECT_DETECTION) file and ADRF, and information related to the object movement (OBJECT_MOBILITY) file and ADRF in the requested inference model (see Section 5.4.6.2.6 of Non-Patent Document 4).

[0058] S205: The SF 30B sends a request message (Nadrf_MLModelManagement_Retrieval Request) to the ADRF 30G to request an inference model to satisfy the requested sensing quality of service (QoS). The request message includes an address specifying a file of the requested inference model related to an abnormal situation (ABNORMAL_SCENE).

[0059] S206: The ADRF 30G sends a response message (Nadrf_MLModelManagement_Retrieval response) to the request message received in S205 to the SF 30B. The response message includes an inference model related to the requested abnormal situation (ABNORMAL_SCENE).

[0060] S207: The SF 30B sends a request message (Nadrf_MLModelManagement_Retrieval Request) to the ADRF 30G to request an inference model to satisfy the requested sensing quality of service (QoS). The request message includes an address specifying a file of the requested inference model related to object detection (OBJECT_DETECTION).

[0061] S208: The ADRF 30G sends a response message (Nadrf_MLModelManagement_Retrieval response) to the request message received in S207 to the SF 30B. The response message includes an inference model related to the requested object detection (OBJECT_DETECTION).

[0062] S209: The SF 30B sends a request message (Nadrf_MLModelManagement_Retrieval Request) to the ADRF 30G to request an inference model to satisfy the requested sensing quality of service (QoS). The request message includes an address specifying a file of the requested inference model related to object mobility (OBJECT_MOBILITY).

[0063] S210: The ADRF 30G sends a response message (Nadrf_MLModelManagement_Retrieval response) to the request message received in S209 to the SF 30B. The response message includes an inference model related to the requested object movement (OBJECT_MOBILITY).

[0064] S211: The SF 30B sends a request message (Nnrf_NFDiscovery request) to the NRF 30J to request address information of the AMF that accommodates the base station located in the sensing range of the requested sensing. The request message includes information specifying the AMF as a network node and a list of sensing ranges (SSA-list).

[0065] S212: The NRF 30J sends a response message (Nnrf_NFDiscovery response) to the request message received in S209 to the SF 30B. The response message includes information (AMF instance) including the address information of the requested AMF.

[0066] S213: SF30B decides to implement a protocol similar to NRPPA (NR (New Radio) Positioning Protocol A, see Non-Patent Document 6) (for example, NRSSP (NR Sensing Protocol)) and perform sensing. That is, information is transmitted and received between SF30B and base station 10 based on the protocol related to sensing.

[0067] S214: Based on the information received in S212, SF30B transmits a request message (Namf_Communication_NonUeN2MessageTransfer request, see sections 6.1.3.8.4.2.2, 6.1.6.2.9, and 6.1.6.2.15 of Non-Patent Document 7) to AMF30A accommodating a base station located within its sensing range, requesting the transmission of a sensing measurement initiation request addressed to the base station. The request message includes a list of sensing ranges and information indicating a sensing measurement initiation request. The request message is expressed, for example, as Namf_Communication_NonUeN2MessageTransfer request (N2InformationTransferReqData(SSA-list=aa, n2Information(nrsspInfo (Measurement Initiation request)))). Moreover, since the request message is a message requesting the base station 10 to perform sensing measurement, it is a terminal-independent (Non-UE) message.

[0068] S215: The AMF 30A sends to the SF 30B a response message (Namf_Communication_NonUeN2MessageTransfer response) in response to the request message received in S209.

[0069] S216: The SF 30B sends a request message (Namf_Communication_NonUeN2InfoSubscribe request) to the AMF 30A requesting subscription to receive sensing notifications.

[0070] S217: AMF 30A sends a response message (Namf_Communication_NonUeN2InfoSubscribe response) to the request message received in S216 to SF 30B.

[0071] S218: AMF 30A sends a message requesting the execution of sensing to all base stations that support at least one range included in the sensing range list (SSA-list) received in S214.

[0072] S219: The AMF 30A stores a context including information (SF-routing info) about the route required to forward the sensing measurement report received from the base station to the SF. The information is, for example, address information of the SF.

[0073] Next, the process following S219 will be described. Fig. 5 is a diagram showing an example of a third sequence diagram according to an embodiment of the present invention. The process of each step in Fig. 5 will be described below.

[0074] S301: The AMF 30A transmits a transport message (Downlink Non-UE-Associated NRSSP Transport) that transfers route information to the SF (SF-routing info) and a sensing measurement initiation request to the base station 10. The sensing measurement initiation request includes information related to sensing quality of service (QoS). The transport message is expressed as, for example, Downlink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU (Measurement Initiation request)).

[0075] S302: The base station 10 transmits to the AMF 30A a transport message (Uplink Non-UE-Associated NRSSP Transport) for transporting the route information (SF-routing info) to the SF received in S301 and a response to the sensing measurement initiation request received in S301. The response message is expressed as, for example, Uplink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU (Measurement Initiation response)).

[0076] S303: The base station 10 performs sensing using the allocated radio resources according to the information on sensing quality of service (QoS) received in S301, and generates a sensing measurement report.

[0077] S304: The AMF 30A transmits to the SF 30B a request message (Namf_Communication_NonUeN2InfoNotify request) for notification of information including a response to the sensing measurement initiation request received in S302. The request message is expressed, for example, as Namf_Communication_NonUeN2InfoNotify request (N2InformationNotification(n2InfoContainer(nrsspInfo(Measurement Initiation response)))).

[0078] S305: The SF 30B transmits to the AMF 30A a response message (Namf_Communication_NonUeN2InfoNotify response) in response to the request message received in S304.

[0079] S306: The base station 10 transmits a transport message (Uplink Non-UE-Associated NRSSP Transport) for transporting route information to the SF (SF-routing info) and a sensing measurement report to the AMF 30A. The transport message is expressed as, for example, Uplink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU(Measurement report)).

[0080] S307: The AMF 30A transmits a request message (Namf_Communication_NonUeN2InfoNotify request) related to notification of information including the sensing measurement report received in S306 to the SF 30B. The request message is expressed, for example, as Namf_Communication_NonUeN2InfoNotify request (N2InformationNotification(n2InfoContainer(nrsspInfo(Measurement report)))).

[0081] S308: The SF 30B sends a response message (Namf_Communication_NonUeN2InfoNotify response) to the request message received in S304 to the AMF 30A.

[0082] S309: SF30B collects sensing measurement reports from multiple base stations and generates sensing results based on the collected reports. For example, SF30B generates an inference result of whether or not an abnormality exists using an inference model of an abnormal state (ABNORMAL_SCENE). If an abnormality exists, SF30B generates an object identification result by inferring the presence or absence of a target object using an inference model of object detection (OBJECT_DETECTION). Furthermore, SF30B generates an object tracking result for the identified object using an inference model of object mobility (OBJECT_MOBILITY).

[0083] S310: The SF30B sends a request message (Nudm_UECM_Registration request) to the UDM30D requesting registration of the sensing result received in S309. The request message includes information indicating the sensing target (SS target) and the sensing result. The sensing result includes, for example, information regarding the position of the detected object.

[0084] S311: The UDM 30D transmits to the UDR 30E a request message (Nudr_DM_Create request) requesting registration of the sensing result received in S309.

[0085] S312: The UDR 30E transmits to the UDM 30D a response message (Nudr_DM_Create request) in response to the request message received in S311.

[0086] S313: The UDM 30D transmits to the SF 30B a response message (Nudm_UECM_Registration response) in response to the request message received in S310.

[0087] S314: The SF 30B sends a request message (Nsf_EventExposure_Notify request) to the NEF 30K requesting notification of the sensing result. The request message includes the sensing result and a notification identifier.

[0088] S315: The NEF 30K sends a request message (Nnef_Sensing_Notify request) to the AF 30L requesting notification of the sensing result. The request message includes the sensing result received in S314 and an external identifier corresponding to the notification identifier received in S314.

[0089] S316: The AF 30L transmits to the NEF 30K a response message (Nnef_Sensing_Notify response) to the request message received in S315.

[0090] S317: The NEF 30K sends to the SF 30B a response message (Nsf_EventExposure_Notify response) to the request message received in S314.

[0091] S318: The SF 30B transmits a request message (Charging Data Request) to the CHF 30H requesting transmission of charging information related to sensing. The request message includes information related to the sensing event as information related to the charging information related to sensing.

[0092] S319: The CHF 30H transmits to the SF 30B a response message (Charging Data response) to the request message received in S318.

[0093] S320: The SF30B may perform improvements to the ABNORMAL_SCENE inference model, the OBJECT_DETECTION inference model, and the OBJECT_MOBILITY inference model, if possible.

[0094] S321: The SF30B sends a request message (Nadrf_Nadrf_MLModelManagement_Storage request) to the ADRF30G to request the registration of an improved inference model. The request message includes at least one improved inference model for the abnormal situation (ABNORMAL_SCENE) inference model, the object detection (OBJECT_DETECTION) inference model, and the object mobility (OBJECT_MOBILITY) inference model.

[0095] S322: The ADRF 30G transmits to the SF 30B a response message (Nadrf_Nadrf_MLModelManagement_Storage response) in response to the request message received in S321.

[0096] By the above procedure, sensing services can be provided in a wireless communication system.

[0097] Next, a procedure for using the proxy sensing quality parameter in the execution of sensing will be described. Fig. 6 is a diagram showing an example of a fourth sequence diagram according to an embodiment of the present invention. The processing of each step in Fig. 6 will be described below.

[0098] S401: The base station 10 may determine that the requested sensing cannot be performed, for example, due to the following factors: Here, it is assumed that the base station 10 has received a sensing start request other than the sensing measurement start request received in S301 of Fig. 5, or a communication start request for a communication service other than sensing.

[0099] (Example of first cause) When there is a request for wireless communication resource allocation from another communication service, and the inter-communication service priority information (first ARP) in the quality of service (QoS) information of the requested sensing includes information indicating preemption permission, and the inter-communication service priority information (second ARP) of the other communication service has preemption capability, and the priority of the second ARP is higher than the priority of the first ARP.

[0100] (Second example of cause) When there is a request for wireless communication resource allocation by another sensing (i.e., when another sensing measurement start request is received), and the inter-sensing priority information (first SSARP) in the quality of service (QoS) information of the requested sensing includes information indicating preemption is allowed, and the inter-sensing priority information (second SSARP) of the other sensing has preemption capability, and the priority of the second SSARP is higher than the priority of the first SSARP.

[0101] (Example of third cause) When sensing cannot be performed to meet the required quality of service (QoS) due to deterioration of wireless conditions, etc.

[0102] S402: The base station 10 sends to the AMF 30A a transport message (Uplink Non-UE-Associated NRSSP Transport) that transports route information to the SF (SF-routing info) and information indicating that the requested sensing cannot be performed.

[0103] S403: The AMF 30A transmits to the SF 30B a request message (Namf_Communication_NonUeN2InfoNotify request) for notification of information indicating that the requested sensing cannot be performed.

[0104] S404: The SF 30B transmits to the AMF 30A a response message (Namf_Communication_NonUeN2InfoNotify response) in response to the request message received in S403.

[0105] S405: SF30B collects sensing measurement reports from multiple base stations and determines, based on the collected reports, that it is not possible to generate sensing results with the sensing service quality currently being processed, but that it is possible to generate sensing results with proxy sensing quality parameters.

[0106] S406: SF30B, if necessary, executes the same procedures as S201 to S212 in FIG. 2 to obtain an inference model for performing sensing using the proxy sensing quality parameters.

[0107] S407: The SF 30B sends a request message (Npcf_SSPolicyControl_Update request) to the (SS-)PCF 30C to request an update of the sensing policy control. The request message includes the proxy sensing quality parameters to be used.

[0108] S408: The (SS-)PCF 30C sends a request message (Nudr_DM_Update request) to the UDR 30E to request an update of sensing information. The request message includes the proxy sensing quality parameters to be used.

[0109] S409: The UDR 30E transmits to the (SS-)PCF 30C a response message (Nudr_DM_Update response) in response to the request message received in S408.

[0110] S410: The (SS-)PCF 30C transmits to the SF 30B a response message (Npcf_SSPolicyControl_Update response) in response to the request message received in S407.

[0111] S411: The SF 30B transmits a request message (Namf_Communication_NonUeN2MessageTransfer request) to the AMF 30A accommodating a base station located in its sensing range, requesting that the AMF 30A transmit a sensing measurement start request addressed to the base station. The request message includes a list of sensing ranges and information indicating the sensing measurement start request, and is expressed as, for example, Namf_Communication_NonUeN2MessageTransfer request (N2InformationTransferReqData (SSA-list=aa, n2Information(nrsspInfo(Measurement Modification request)))).

[0112] S412: The AMF 30A sends to the SF 30B a response message (Namf_Communication_NonUeN2MessageTransfer response) in response to the request message received in S411.

[0113] S413: The AMF 30A sends a transport message (Downlink Non-UE-Associated NRSSP Transport) to the base station 10, which transports route information to the SF (SF-routing info) and a sensing measurement modification request. The sensing measurement modification request includes information on the proxy sensing quality parameters to be used. The transport message is expressed as, for example, Downlink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU (Measurement Modification request)). In other words, the transport message requests the base station 10 to perform sensing using the proxy sensing quality parameters.

[0114] S414: The base station 10 transmits to the AMF 30A a transport message (Uplink Non-UE-Associated NRSSP Transport) that transports the route information (SF-routing info) to the SF received in S413 and a response to the sensing measurement modification request received in S413. The transport message is expressed as, for example, Uplink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU (Measurement Modification response)).

[0115] S415: The base station 10 performs sensing based on the information about the proxy sensing quality parameters received in S413.

[0116] S416: The AMF 30A sends to the SF 30B a request message (Namf_Communication_NonUeN2InfoNotify request) for notification of information including a response to the sensing measurement modification request received in S414. The request message is expressed, for example, as Namf_Communication_NonUeN2InfoNotify request (N2InformationNotification(n2InfoContainer(nrsspInfo(Measurement Modification response)))).

[0117] S417: The SF 30B sends a response message (Namf_Communication_NonUeN2InfoNotify response) to the request message received in S416 to the AMF 30A.

[0118] As described above, by following the procedure shown in the fourth sequence diagram in FIG. 6, sensing can be performed using the proxy sensing quality parameters.

[0119] Next, a procedure for pre-confirming the service provision conditions related to sensing between the AF and the 5GC will be described. FIG. 7 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. In this sequence diagram, the SF30B has two functions: an SF and an NWDAF having an AnLF (Analytics Logical Function). The processing of each step in FIG. 7 will be described below.

[0120] S501: The AF 30L sends a request message (Nnef_PSSQ (Planned Sensing with QoS Requirements) PolicyNegotiation_Create request) to the NEF 30K to request negotiation of a sensing policy. The request message includes a sensing range reference parameter, a sensing target reference parameter, and a sensing quality reference parameter.

[0121] S502: The NEF 30K sends a request message (Npcf_PSSQPolicyControl_Create request) to the (SS-)PCF 30C to request negotiation of a sensing policy. The request message includes multiple external parameters related to sensing quality of service (QoS) (sensing range reference parameter, sensing target reference parameter, and sensing quality reference parameter).

[0122] S503: The (SS-)PCF 30C converts the external parameters received in S502 into internal parameters, i.e., converts the sensing range reference parameter into a sensing range list (SSA-list), the sensing target reference parameter into a sensing target (SStarget), and the sensing quality reference parameter into a sensing quality identifier (SSQI).

[0123] S504: (SS-)PCF30C decides to obtain from UDR30E a list of currently available sensing policies (PSSQ Policies) that match the information on sensing service quality (QoS) sent by AF30L (i.e., the external parameters received in S502 and the parameters converted in S503).

[0124] S505: The (SS-)PCF 30C transmits to the UDR 30E a request message (Nudr_DM_Query request) requesting a list of available sensing policies that were determined to be acquired in S504.

[0125] S506: The UDR 30E transmits a response message (Nudr_DM_Query response) to the request message received in S505 to the (SS-)PCF 30C. The response message includes a list of available sensing policies.

[0126] S507: The (SS-)PCF 30C transmits a request message (Nnwdaf_AnalyticsInfo request) to the SF 30B requesting the sensing performance analysis results (Sensing Performance Analytics).

[0127] S508: SF30B generates sensing performance analysis results (Sensing Performance Analytics), such as an analysis of the load status related to sensing processing at the base station, using information that the SF30B has or information obtained from OAM (Orchestration and Management).

[0128] S509: The SF 30B transmits a response message (Nnwdaf_AnalyticsInfo response) to the request message received in S507 to the (SS-)PCF 30C. The response message includes the sensing performance analysis results (Sensing Performance Analytics).

[0129] S510: Based on the sensing performance analysis results received in S509, (SS-)PCF30C determines at least one proposed sensing policy (PSSQ policy) to send to AF30L for proposal, taking into consideration the load situation at the base station.

[0130] S511: The (SS-)PCF 30C sends to the NEF 30K a response message (Npcf_PSSQPolicyControl_Create response) in response to the request message received in S502. The response message includes a list having the identifier (policy reference ID) of the proposed sensing policy determined in S510 and information about the contents of the proposed sensing policy.

[0131] S512: The NEF 30K sends a response message (Nnef_PSSQPolicyNegotiation_Create response) to the request message received in S501 to the AF 30L. The response message includes a list containing the identifier (policy reference ID) of the proposed sensing policy determined in S510 and the contents of the sensing policy.

[0132] S513: The AF 30L sends a request message (Nnef_PSSQPolicyNegotiation_Update request) to the NEF 30K requesting an update of the sensing policy. The request message includes the identifier (PSSQ policy reference ID) of the sensing policy that the AF 30L selected from the list received in S510.

[0133] S514: The NEF 30K sends a request message (Npcf_PSSQPolicyControl_Update request) to the (SS-)PCF 30C requesting an update of the sensing policy. The request message includes the identifier (PSSQ policy reference ID) of the sensing policy selected by the AF 30L from the list received in S510.

[0134] S515: The (SS-)PCF 30C sends to the NEF 30K a response message (Npcf_PSSQPolicyControl_Update response) in response to the request message received in S514.

[0135] S516: The NEF 30K sends the AF 30L a response message (Nnef_PSSQPolicyNegotiation_Update response) to the request message received in S513.

[0136] S517: The (SS-)PCF 30C updates the usage status of the sensing policy (PSSQ policy).

[0137] S518: The (SS-)PCF 30C transmits a request message (Nudr_DM_Update request) to the UDR 30E to request an update of the sensing policy.

[0138] S519: The UDR 30E transmits to the (SS-)PCF 30C a response message (Nudr_DM_Update response) in response to the request message received in S518.

[0139] Furthermore, the (SS-)PCF30C may receive from the AF30L a message requesting the start of sensing measurement, which includes the identifier (PSSQ policy reference ID) of the sensing policy selected in S513. Furthermore, the (SS-)PCF30C may convert the identifier (PSSQ policy reference ID) of the sensing policy included in the request message into the content of the policy and sensing quality of service (QoS) information to be used within the network, and transmit the converted sensing quality of service (QoS) information to the SF30B.

[0140] As described above, the procedure shown in the fifth sequence diagram in Figure 7 allows for prior confirmation of service provision conditions related to sensing between the AF and 5GC.

[0141] Next, the procedure when object movement is detected in sensing will be described. Fig. 8 is a diagram showing an example of a sixth sequence diagram according to an embodiment of the present invention. The processing of each step in Fig. 8 will be described below.

[0142] S601: The source SF 30N estimates that the sensing target is moving outside the sensing range of its own device (object movement) based on analysis of the object mobility (OBJECT_MOBILITY) inference model. The source SF 30N determines to switch SFs and determine the destination SF to track the sensing target.

[0143] S602: The source SF 30N transmits to the source AMF 30M a request message (Namf_Communication_NonUeN2MessageTransfer request) requesting transmission of a sensing measurement (and report) interruption request addressed to the base station. The request message includes a sensing range list and information indicating the sensing measurement interruption request. The request message is expressed, for example, as Namf_Communication_NonUeN2MessageTransfer request (N2InformationTransferReqData (SSA-list=aa, n2Information(nrsspInfo(Measurement Termination command)))).

[0144] S603: The source AMF 30M sends a response message (Namf_Communication_NonUeN2MessageTransfer response) to the source SF 30N in response to the request message received in S602.

[0145] S604: The source AMF 30M transmits a transfer message (Downlink Non-UE-Associated NRSSP Transport) for transferring route information to the SF (SF-routing info) and a sensing measurement interruption request to the source base station 10A. The transfer message is expressed as, for example, Downlink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU (Measurement Termination command)).

[0146] S605: The source base station 10A starts a timer (sensing interruption timer) that measures the time until the sensing measurement is interrupted. Furthermore, if the source base station 10A does not receive a sensing measurement start request message before the sensing interruption timer expires, the source base station 10A interrupts (stops) the sensing measurement.

[0147] S606: The source SF 30N transmits a request message (Nsf_Sensing_Context request) to the destination SF 30Q, requesting switching of sensing, including a context required for sensing (e.g., a sensing range). The request message includes, as the context required for sensing, an improved inference model for an abnormal state (ABNORMAL_SCENE), an improved inference model for object detection (OBJECT_DETECTION), and an improved inference model for object movement (OBJECT_MOBILITY).

[0148] S607: The movement destination SF 30Q sends a response message (Nsf_Sensing_Context response) to the request message received in S602 to the movement source SF 30N.

[0149] S608: The destination SF30Q acquires an abnormal state (ABNORMAL_SCENE) inference model corresponding to the list of sensing ranges (SSA-list) at the destination from the ADRF30G using the same procedures as S201 to S206 in Figure 2.

[0150] S609: Based on the difference between the improved inference model for the abnormal state (ABNORMAL_SCENE) obtained in S606 and the inference model for the abnormal state (ABNORMAL_SCENE) obtained in S608, the destination SF30Q further improves the improved inference model for object detection (OBJECT_DETECTION) and the improved inference model for object movement (OBJECT_MOBILITY) obtained in S606, and uses them in the object detection estimation and object movement estimation performed by its own device.

[0151] S610: The destination SF 30Q transmits a request message (Namf_Communication_NonUeN2MessageTransfer request) to the AMF 30P that accommodates a base station located in the destination sensing range, requesting that the AMF 30P transmit a sensing measurement start request addressed to the base station. The request message includes a list of sensing ranges and information indicating the sensing measurement start request, and is expressed as, for example, Namf_Communication_NonUeN2MessageTransfer request (N2InformationTransferReqData (SSA-list=aax, n2Information(nrsspInfo(Measurement Modification request)))).

[0152] S611: The destination AMF 30P sends a response message (Namf_Communication_NonUeN2MessageTransfer response) to the destination SF 30Q in response to the request message received in S610.

[0153] S612: The target AMF 30P transmits a transfer message (Downlink Non-UE-Associated NRSSP Transport) for transferring route information to the SF (SF-routing info) and a sensing measurement initiation request to the target base station 10B. The transfer message is expressed as, for example, Downlink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU (Measurement Initiation request)).

[0154] S613: The target base station 10B transmits, to the target AMF 30P, a transport message (Uplink Non-UE-Associated NRSSP Transport) for transporting route information to the SF (SF-routing info) and a response to the sensing measurement initiation request received in S612. The response message is expressed, for example, as Uplink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU (Measurement Initiation response)).

[0155] S614: The movement-destination base station 10B starts sensing in response to the sensing measurement start request received in S612.

[0156] S615: The destination AMF 30P transmits a request message (Namf_Communication_NonUeN2InfoNotify request) related to notification of information including a response to the sensing measurement initiation request to the destination SF 30Q. The request message is expressed, for example, as Namf_Communication_NonUeN2InfoNotify request (N2InformationNotification(n2InfoContainer(nrsspInfo(Measurement Initiation response)))).

[0157] S616: The destination SF 30Q sends a response message (Namf_Communication_NonUeN2InfoNotify response) to the request message received in S615 to the destination AMF 30P.

[0158] S617: The destination SF 30Q sends a request message (Npcf_SSPolicyControl_Update request) to the (SS-)PCF 30C to request an update of the sensing policy control. The request message includes information notifying that switching of the sensing function (SF) has occurred.

[0159] S618: The (SS-)PCF 30C transmits to the destination SF 30Q a response message (Npcf_SSPolicyControl_Update response) in response to the request message received in S617.

[0160] S619: The target base station 10B transmits a transfer message (Uplink Non-UE-Associated NRSSP Transport) for transferring the sensing measurement report to the target AMF 30P. The request message is expressed as, for example, Uplink Non-UE-Associated NRSSP Transport (SF-routing info, NRSSP-PDU(Measurement report)).

[0161] S620: The destination AMF 30P sends a transfer message (Namf_Communication_NonUeN2InfoNotify request) for transferring the sensing measurement report to the destination SF 30Q. This is expressed as follows: Namf_Communication_NonUeN2InfoNotify request (N2InformationNotification (n2InfoContainer(nrsspInfo(Measurement report)))).

[0162] S621: The destination SF 30Q sends a response message (Namf_Communication_NonUeN2InfoNotify response) to the request message received in S620 to the destination AMF 30P.

[0163] S622: The destination SF 30Q sends a request message (Nudm_UECM_Registration request) to the UDM 30D requesting registration of the sensing result received in S620. The request message includes information indicating the sensing target (SS target) and the sensing result. The sensing result includes, for example, information regarding the position of the detected object.

[0164] S623: The UDM 30D transmits to the UDR 30E a request message (Nudr_DM_Create request) requesting registration of the sensing result received in S622.

[0165] S624: The UDR 30E transmits to the UDM 30D a response message (Nudr_DM_Create response) in response to the request message received in S623.

[0166] S625: The UDM 30D transmits a response message (Nudm_UECM_Registration response) to the request message received in S622 to the destination SF 30Q. Thereafter, the UDM 30D reports the sensing results in the same manner as in S314 to S317 in FIG.

[0167] As described above, by the procedure shown in the sixth sequence diagram in FIG. 8, it is possible to follow the movement of an object in sensing.

[0168] As described above, the above-described embodiment makes it possible to provide a sensing service in a wireless communication system.

[0169] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0170] <Base Station 10 and Network Node 30> Fig. 9 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 9, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 9 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0171] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

[0172] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out from the storage device as needed. The content of the setting information is, for example, information related to a communication path in the IMS data channel network.

[0173] As described in the embodiments, the control unit 140 performs processing related to the sensing service, etc. The control unit 140 also performs processing related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0174] <Terminal 20> Fig. 10 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 10, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 10 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.

[0175] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving control signals, reference signals, etc. transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0176] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 in a storage device and reads them from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to communication paths in the IMS network.

[0177] As described in the embodiments, the control unit 240 performs processing related to the sensing service, etc. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

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

[0179] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

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

[0181] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0182] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0183] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0184] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0185] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0186] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

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

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

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

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

[0191] Fig. 12 shows an example configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

[0193] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0194] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0195] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0196] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0197] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0198] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

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

[0200] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0201] <Additional Notes> (Additional Note 1) A network node comprising: a receiver that receives, from a plurality of base stations, a first message requesting interface configuration, the first message including a list of supported sensing ranges, a controller that sets a union of the lists received from the plurality of base stations as a second list of sensing ranges that the network node can handle, and a transmitter that transmits, to a first network node, a second message requesting registration of the network node, the second list being included in the list. (Additional Note 2) A network node comprising: a receiver that receives, from the first network node, a second message including a list of sensing ranges and a terminal-independent first message to be transmitted to a base station, a transmitter that transmits the first message to at least one base station whose sensing range includes at least one of the sensing ranges included in the list of sensing ranges, and a controller that stores, in the first network node, information required for forwarding sensing measurement reports received from the base stations. (Supplementary Item 3) A base station comprising: a receiving unit that receives, from a first network node, a first message requesting a start of first sensing measurement, the first message including first sensing service quality information; a control unit that performs sensing using wireless communication resources allocated based on the first sensing service quality information and generates a sensing measurement report; and a transmitting unit that transmits the sensing measurement report to the first network node. (Supplementary Item 4) The base station according to Supplementary Item 3, wherein the receiving unit receives a second message requesting a start of second sensing measurement, the second message including second sensing service quality information; the control unit allocates wireless resources to the second sensing when it has confirmed that first inter-sensing priority information of the first sensing service quality information includes information indicating preemption permission, that the second inter-sensing priority information of the second sensing service quality information has preemption capability, and that the priority of the second inter-sensing priority information is higher than the priority of the first inter-sensing priority information.(Supplementary Item 5) The base station according to Supplementary Item 3, wherein the receiving unit receives a second message requesting allocation of wireless communication resources by another communication service; the control unit allocates wireless resources to the other communication service when it confirms that the first inter-communication service priority information of the first sensing service quality information includes information indicating preemption permission, that the second inter-communication service priority information of the other communication service has preemption capability, and that the priority of the second inter-communication service priority information is higher than the priority of the first inter-communication service priority information; and the transmitting unit transmits a third message to the first network node indicating that first sensing cannot be performed.

[0202] Any of Supplementary Items 1 to 5 makes it possible to provide a sensing service in a wireless communication system.

[0203] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

[0205] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0206] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0207] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0208] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

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

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

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

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

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

[0214] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0215] As used in this disclosure, the terms "system" and "network" are used interchangeably.

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

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

[0218] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

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

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

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

[0222] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0223] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

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

[0226] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0227] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0228] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

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

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

[0231] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

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

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

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

[0235] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0236] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0237] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A network node having: a receiver that receives a first message from multiple base stations requesting interface configuration, the message including a list of supported sensing ranges; a controller that sets the union of the lists received from the multiple base stations as a second list of sensing ranges that the device can handle; and a transmitter that transmits a second message to a first network node, the second message including the second list, requesting registration of the device.

2. A network node having: a receiving unit that receives a second message from a first network node, the second message including a list of sensing ranges and a terminal-independent first message to be transmitted to a base station; a transmitting unit that transmits the first message to at least one base station whose sensing range is at least one of the sensing ranges included in the list of sensing ranges; and a control unit that stores information necessary for forwarding sensing measurement reports received from the base station to the first network node.

3. A base station having: a receiving unit that receives a first message from a first network node, the first message including first sensing service quality information, requesting the start of first sensing measurement; a control unit that performs sensing using wireless communication resources allocated based on the first sensing service quality information, and generates a sensing measurement report; and a transmitting unit that transmits the sensing measurement report to the first network node.

4. The base station according to claim 3, wherein the receiving unit receives a second message including second sensing service quality information requesting the start of second sensing measurement; the control unit allocates radio resources to the second sensing when it confirms that the first inter-sensing priority information of the first sensing service quality information includes information indicating pre-emption permission, that the second inter-sensing priority information of the second sensing service quality information has pre-emption capability, and that the priority of the second inter-sensing priority information is higher than the priority of the first inter-sensing priority information; and the transmitting unit transmits a third message to the first network node indicating that first sensing cannot be performed.

5. The base station according to claim 3, wherein the receiving unit receives a second message requesting allocation of wireless communication resources by another communication service, and the control unit allocates wireless resources to the other communication service when it confirms that the first inter-communication service priority information of the first sensing service quality information includes information indicating preemption permission, that the second inter-communication service priority information of the other communication service has preemption capability, and that the priority of the second inter-communication service priority information is higher than the priority of the first inter-communication service priority information,

Images