User equipment (UE)

The UE's transceiver and control unit manage authentication revocation for sensing entities, resolving integration challenges in 3GPP systems by effectively handling sensing technology.

WO2026235008A1PCT designated stage Publication Date: 2026-11-12SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/016273
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-23
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 3GPP systems lack specific solutions for integrating sensing technology, necessitating a need for addressing authentication revocation and management of sensing entities.

Method used

A UE equipped with a transceiver and control unit that receives authentication revocation information and deletes corresponding settings, managing sensing entity authentication in 3GPP systems.

Benefits of technology

Enables effective management of sensing technology integration in 3GPP systems by handling authentication revocation, thus addressing key issues and enhancing system functionality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026016273_12112026_PF_FP_ABST
    Figure JP2026016273_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present invention provides a solution to various examination problems in applying a sensing technology in a 3GPP system. This UE: receives, from an NF, an identifier of a sensing entity and a cause value indicating that the authentication of the sensing entity has been revoked; transmits, to the NF, information indicating receipt of both the identifier of the sensing entity and revocation of the authentication of the sensing entity; and deletes the stored configuration information relating to sensing.
Need to check novelty before this filing date? Find Prior Art

Description

UE (User Equipment)

[0001] One aspect of the present invention relates to a UE (User Equipment). This application claims priority based on Japanese Patent Application No. 2025-078223 filed in Japan on May 8, 2025, the content of which is incorporated herein by reference.

[0002] In 3GPP (3rd Generation Partnership Project, studies on Integrated Sensing and Communication are being conducted in Release 20 (see Non-Patent Document 1).

[0003] 3GPP TR 23.700-14 V0.1.0 (2025-04); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Integrated Sensing and Communication; Stage 2 (Release 20)

[0004] In this study, it is planned to examine how to resolve various issues to be considered when applying sensing technology in 3GPP systems, but specific solutions have not been disclosed.

[0005] One aspect of the present invention has been made in view of the circumstances as described above, and is to provide solutions to various issues to be considered when applying sensing technology in 3GPP systems.

[0006] A UE according to one aspect of the present invention is a UE comprising a transceiver, a control unit, and a storage unit, wherein the transceiver receives, from a network function, an identifier of a sensing entity and a reason value indicating that authentication of the sensing entity has been revoked, and transmits, to the network function, information indicating that the identifier of the sensing entity and the revocation of the authentication of the sensing entity have been recognized, and the control unit deletes the setting information related to sensing stored in the storage unit.

[0007] According to one aspect of the present invention, it is possible to provide solutions to various issues that need to be considered when applying sensing technology in a 3GPP system.

[0008] This is a diagram illustrating the overview of the mobile communication system (EPS / 5GS). This is a diagram illustrating the detailed configuration of the mobile communication system (EPS / 5GS). This is a diagram illustrating the equipment configuration of the UE. This is a diagram illustrating the configuration of the access network equipment. This is a diagram illustrating the configuration of the core network equipment. This is a diagram illustrating the registration procedure and / or the first procedure for approving and / or certifying the SE. This is a diagram illustrating the registration procedure and / or the second procedure for approving and / or certifying the SE. This is a diagram illustrating the third procedure for approving and / or certifying the SE. This is a diagram illustrating the first revocation procedure for revoking the approval and / or certification of the SE. This is a diagram illustrating the second revocation procedure for revoking the approval and / or certification of the SE. This is a diagram illustrating the revocation procedure for revoking the approval and / or certification of the sensing service.

[0009] The best mode for carrying out one aspect of the present invention will be described below with reference to the drawings. In this embodiment, an example of a mobile communication system to which one aspect of the present invention is applied will be described.

[0010] [1. System Overview] First, Figure 1 is a diagram illustrating the general structure of the mobile communication system 1 used in each embodiment, and Figure 2 is a diagram illustrating the detailed configuration of the mobile communication system 1.

[0011] Figure 1 shows that mobile communication system 1 consists of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

[0012] In the following, these devices and functions may be referred to using abbreviations such as UE, Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, etc.

[0013] Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and N3IWF170, as well as the interfaces that connect these devices and functions to each other.

[0014] In the following, these devices and functions may be described using abbreviations such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0015] Furthermore, the 4G system, EPS (Evolved Packet System), consists of access network_A and core network_A, but may also include UE and / or PDN. Similarly, the 5G system, 5GS (5G System), consists of UE, access network_B and core network_B, but may also include DN.

[0016] A UE is a device capable of connecting to network services via 3GPP access (also known as a 3GPP access network or 3GPP AN) and / or non-3GPP access (also known as a non-3GPP access network or non-3GPP AN). A UE may be a wireless communication terminal device such as a mobile phone or smartphone, and may be a terminal device capable of connecting to EPS and / or 5GS. A UE may be equipped with a UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). Note that a UE may also be referred to as a user device or terminal device.

[0017] Furthermore, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. E-UTRAN has one or more eNBs (evolved Node B)45. Note that in the following, eNB45 may be written simply as eNB. If there are multiple eNBs, each eNB is connected to the others, for example, by an X2 interface. Furthermore, the wireless LAN access network has one or more access points.

[0018] Furthermore, access network_B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access networks. One or more gNBs (NR NodeBs)122 are located in the NG-RAN. Note that, below, gNB122 may be written with the symbol omitted, such as gNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including the N2 interface or N3 interface). In other words, a gNB is a base station device newly designed for 5GS and has different functions from a base station device (eNB) designed for the 4G system, EPS. Also, if there are multiple gNBs, each gNB is connected to the others, for example, by an Xn interface.

[0019] Furthermore, non-3GPP access networks may include untrusted non-3GPP access networks and trusted non-3GPP access networks. Here, an untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public wireless LAN. On the other hand, a trusted non-3GPP access network may be an access network defined by 3GPP and may include a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function).

[0020] Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Similarly, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Additionally, nodes located in access network_B may be collectively referred to as NG-RAN nodes.

[0021] Furthermore, in the following, access network_A, access network_B, and the devices included in access network_A, and the devices included in access network_B may be referred to as the access network, access network devices, or devices within the access network.

[0022] Furthermore, Core Network A corresponds to EPC (Evolved Packet Core). EPC is configured with, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc.

[0023] Furthermore, Core Network B corresponds to 5GCN (5G Core Network). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN may also be expressed as 5GC.

[0024] Furthermore, in the following, Core Network A, Core Network B, and the devices included in Core Network A, and the devices included in Core Network B may be referred to as the Core Network, Core Network Devices, or Devices within the Core Network.

[0025] The core network (Core Network A and / or Core Network B) may be an IP mobile communication network operated by a Mobile Network Operator (MNO) that connects the access network (Access Network A and / or Access Network B) to the PDN and / or DN; it may be a core network for a mobile network operator that operates and manages the mobile communication system 1; or it may be a core network for a virtual mobile communication operator or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

[0026] Furthermore, although Figure 1 shows a case where the PDN and DN are the same, they may be different. The PDN may be a Data Network (DN) that provides communication services to the UE. The DN may be configured as a packet data service network, or it may be configured for each service. In addition, the PDN may include connected communication terminals. Therefore, connecting to a PDN may mean connecting to communication terminals or server devices located in the PDN. Furthermore, sending and receiving user data with a PDN may mean sending and receiving user data with communication terminals or server devices located in the PDN. Note that the PDN may be referred to as DN, and the DN may be referred to as PDN.

[0027] Furthermore, in the following, access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein may be referred to as a network (also called NW) or network device. In other words, when a network and / or network device sends and receives messages and / or performs procedures, it means that access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein send and receive messages and / or perform procedures.

[0028] Furthermore, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate with) user data to and from the PDN or DN. When sending and receiving user data, non-IP communication may be used in addition to IP (Internet Protocol) communication.

[0029] Here, IP communication refers to data communication using IP, where data is sent and received via IP packets. An IP packet consists of an IP header and a payload. The payload may include data sent and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication, on the other hand, refers to data communication that does not use IP, where data is sent and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by sending and receiving application data without an IP header, or it may be user data sent and received by the UE with other headers such as a MAC header or an Ethernet® frame header attached.

[0030] Furthermore, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may include devices not shown in Figure 2. For example, core network_A and / or core network_B may include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0031] Here, AUSF is a core network device equipped with authentication functions for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP access and / or non-3GPP access from the UE and executes the authentication procedure.

[0032] Furthermore, the AAA server is a device equipped with authentication, authorization, and billing functions, which connects directly or indirectly to the AUSF via other network devices. The AAA server may be a network device within the core network. However, the AAA server may not be included in core network_A and / or core network_B, but may be included in PLMN. In other words, the AAA server may be a core network device or a device located outside the core network. For example, the AAA server may be a server device within PLMN managed by a third party.

[0033] Note that in Figure 2, for the sake of simplification, only one of each device / function is shown; however, multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150.

[0034] [2. Configuration of Each Device] Next, the configuration of each device (UE, and / or access network device, and / or core network device) used in each embodiment will be described with reference to a diagram. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0035] Furthermore, each memory unit (memory unit_A340, memory unit_B540, memory unit_B740) within each device / function described below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only the information originally set at the time of shipment, but also various information transmitted and received with devices / functions other than its own device / function (for example, UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc., contained in control messages transmitted and received within the various communication procedures described later. Furthermore, each memory unit may store this information for each UE. In addition, when interworking between 5GS and EPS, each memory unit can store control messages and user data transmitted and received with devices / functions contained within 5GS and / or EPS. In this case, it can store not only information transmitted and received via the N26 interface, but also information transmitted and received without the N26 interface.

[0036] [2.1. UE Equipment Configuration] First, an example of the UE (User Equipment) equipment configuration will be explained using Figure 3. The UE consists of a control unit_A300, an antenna 310, a transceiver_A320, and a memory unit_A340. The control unit_A300, the transceiver_A320, and the memory unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.

[0037] The control unit_A300 is a functional unit that controls the operation and functions of the entire UE. The control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the memory unit_A340 as needed.

[0038] The transceiver unit A320 is a functional unit for wireless communication with base station equipment (eNB or gNB) within the access network via an antenna. In other words, the UE can use the transceiver unit A320 to send and receive user data and / or control information between the access network equipment and / or core network equipment and / or PDN and / or DN.

[0039] Referring to Figure 2, the UE can communicate with the base station equipment (eNB) in E-UTRAN via the LTE-Uu interface using the transceiver unit A320. The UE can also communicate with the base station equipment (gNB) in 5G AN using the transceiver unit A320. Furthermore, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit A320. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN.

[0040] Memory unit A340 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UE. Memory unit 340 may also have the function of storing control information transmitted and received between the access network device, core network device, and DN.

[0041] [2.2. Base Station Equipment Configuration] Next, an example of the base station equipment configuration will be explained using Figure 4. The base station equipment may be a gNB, or an eNB, or an en-gNB, or an ng-eNB. Here, the gNB will be used as an example of the base station equipment. That is, in the following explanation, gNB may be read as eNB, or an en-gNB, or an ng-eNB. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0042] The control unit_B500 is a functional unit that controls the overall operations and functions of the gNB. The control unit_B500 reads and executes various programs stored in the storage unit_B540 as needed, thereby realizing various processes in the gNB.

[0043] The network connection unit_B520 is a functional unit for the gNB to communicate with the AMF and / or UPF. That is, the gNB can transmit and receive user data and / or control information to and from the AMF and / or UPF using the network connection unit_B520.

[0044] The transceiver unit_B530 is a functional unit for performing radio communication with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information to and from the UE using the transceiver unit_B530.

[0045] To describe in detail with reference to FIG. 2, the gNB in the 5G AN can communicate with the AMF via the N2 interface and can communicate with the UPF via the N3 interface by using the network connection unit_B520. Further, the gNB can communicate with the UE by using the transceiver unit_B530.

[0046] The storage unit_B540 is a functional unit for storing programs, user data, control information and the like required for each operation of the gNB. In addition, the storage unit_540 may have a function of storing control information transmitted and received to and from the UE, other access network apparatuses (base station apparatuses), core network apparatuses, and DN.

[0047] Here, the base station apparatus may also be referred to as a base station, and may refer to a gNB, or an eNB, or an en-gNB, or an ng-eNB, or an access point accommodated in non-3GPP access (for example, an access point such as those used in a wireless LAN).

[0048] [2.3. Device Configuration of AMF / MME] Next, an example of the device configuration of AMF and MME, which are part of a core network device or core network function, will be described. Here, an example of the device configuration of AMF will be described using Figure 5. Although the case of AMF is described as an example here, it may be read as MME. The AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0049] The control unit_B700 is a functional unit that controls the overall operations and functions of the AMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby implementing various processes in the AMF.

[0050] The network connection unit_B720 is a functional unit for the AMF to connect with a base station apparatus (gNB) in the 5G AN, and / or SMF, and / or PCF, and / or UDM, and / or SCEF, and / or NSACF. That is, the AMF can transmit and receive user data and / or control information to and from the base station apparatus (gNB) in the 5G AN, and / or SMF, and / or PCF, and / or UDM, and / or SCEF, using the network connection unit_B720.

[0051] Referring to Figure 2, the AMF within 5GCN can communicate with the gNB via the N2 interface, the UDM via the N8 interface, the SMF via the N11 interface, and the PCF via the N15 interface, using the network connection unit _A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit _A620. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN. Additionally, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface using the network connection unit _A620.

[0052] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the AMF. Memory unit B740 may also have the function of storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0053] Furthermore, the AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and protecting the integrity of NAS messages, registration management (RM) function, connection management (CM) function, reachability management function, mobility management function for UEs, etc., forwarding SM (Session Management) messages between the UE and the SMF, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA), security context management (SCM), support for the N2 interface to the N3IWF (Non-3GPP Interworking Function), support for sending and receiving NAS signals with the UE via the N3IWF, and authentication of UEs connected via the N3IWF.

[0054] Furthermore, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. There are two RM states: unregistered state (RM-DEREGISTERED state) and registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, so the UE context in the AMF does not have valid location or routing information for that UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered with the network, so the UE can receive services that require registration with the network. Note that the RM state may also be expressed as the 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.

[0055] In other words, 5GMM-REGISTERED means that each device may have established a 5GMM context or a PDU session context. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, and may respond to paging. In addition, when each device is 5GMM-REGISTERED, UE_A10 may perform registration procedures other than the registration procedure for initial registration, and / or service request procedures.

[0056] Furthermore, 5GMM-DEREGISTERED may occur even if each device has not established a 5GMM context, or if the location information of UE_A10 is not known to the network, or if the network is unreachable to UE_A10. If each device is in a 5GMM-DEREGISTERED state, UE_A10 may initiate the registration procedure, or establish a 5GMM context by executing the registration procedure.

[0057] Furthermore, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. There are two CM states: disconnected state (CM-IDLE state) and connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 connection or an N3 connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-CONNECTED state, the UE may have an N2 connection and / or an N3 connection.

[0058] Furthermore, connection management may be handled separately for CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access may include an unconnected state (CM-IDLE state over 3GPP access) and a connected state (CM-CONNECTED state over 3GPP access). Furthermore, the CM states in non-3GPP access may include an unconnected state (CM-IDLE state over non-3GPP access) and a connected state (CM-CONNECTED state over non-3GPP access). Note that the unconnected state may be expressed as idle mode, and the connected state may be expressed as connected mode.

[0059] Furthermore, the CM state may be expressed as 5GMM mode. In this case, the disconnected state may be expressed as 5GMM-IDLE mode, and the connected state may be expressed as 5GMM-CONNECTED mode. Additionally, the disconnected state in 3GPP access may be expressed as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM-CONNECTED mode over 3GPP access. Furthermore, the disconnected state in non-3GPP access may be expressed as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access may be expressed as 5GMM-CONNECTED mode over non-3GPP access. Note that 5GMM-IDLE mode may also be expressed as idle mode, and 5GMM-CONNECTED mode may also be expressed as connected mode.

[0060] Furthermore, one or more AMFs may be located within the core network_B. Also, an AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Additionally, an AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0061] Furthermore, N3IWF is a device and / or function placed between the non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.

[0062] [2.4. SMF / PGW Device Configuration] Next, an example of the device configuration of an SMF, which is a core network device or part of the core network function, will be explained using Figure 5. Here, the example of an SMF will be used, but it may be replaced with a PGW or PGW-C. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0063] The control unit B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit B700 implements various processes in the SMF by reading and executing various programs stored in the memory unit B740 as needed.

[0064] The network connection unit B720 is a functional unit that allows the SMF to connect with the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can use the network connection unit B720 to send and receive user data and / or control information with the AMF, and / or UPF, and / or PCF, and / or UDM, and / or NSACF.

[0065] Referring to Figure 2, the SMF within 5GCN can communicate with the AMF via the N11 interface, the UPF via the N4 interface, the PCF via the N7 interface, and the UDM via the N10 interface by using the network connection unit A620.

[0066] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the SMF.

[0067] SMF has session management functions such as establishing, modifying, and releasing PDU sessions; IP address allocation and management functions for UEs; UPF selection and control functions; UPF configuration functions for routing traffic to appropriate destinations; functions for sending and receiving the SM portion of NAS messages; functions for notifying when downlink data has arrived (Downlink Data Notification); functions for providing AN-specific (AN-specific) SM information sent to ANs via the N2 interface through AMF; functions for determining the SSC mode (Session and Service Continuity mode) for sessions; and roaming functions.

[0068] Furthermore, the memory unit 740 may have a function for storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0069] [2.5. UPF / PGW / SGW Device Configuration] Next, an example of the device configuration of a UPF, which is one of the core network devices or core network functions, will be explained using Figure 5. Here, the case of a UPF will be used as an example, but it may be replaced with PGW, PGW-U, or SGW. A PGW may also combine the functions of both PGW-C and PGW-U. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0070] The control unit B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit B700 implements various processes in the UPF by reading and executing various programs stored in the memory unit B740 as needed.

[0071] The network connection unit B720 is a functional unit that allows the UPF to connect with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN.

[0072] Referring to Figure 2, the UPF within 5GCN can communicate with the gNB via the N3 interface, the SMF via the N4 interface, the DN via the N6 interface, and other UPFs via the N9 interface by using the network connection unit A620.

[0073] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UPF.

[0074] UPF has functions such as acting as an anchor point for intra-RAT mobility or inter-RAT mobility, acting as an external PDU session point for interconnecting to DNs (i.e., acting as a gateway between DNs and core network B to forward user data), routing and forwarding packets, an UL CL (Uplink Classifier) ​​function that supports routing multiple traffic flows to a single DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notification.

[0075] Furthermore, the UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have the function of forwarding IP communication, and may also have the function of converting non-IP communication to IP communication. In addition, multiple gateways may be gateways connecting the core network B to a single DN. The UPF may also have connectivity to other NFs, and may connect to each device via other NFs.

[0076] Furthermore, the memory unit 740 may have a function for storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0077] [2.6. Description of Other Devices and / or Functions and Identification Information in This Embodiment] Next, other devices and / or functions and identification information will be described.

[0078] The term "network" refers to at least a portion of Access Network B, Core Network B, and DN. Furthermore, one or more devices included in at least a portion of Access Network B, Core Network B, and DN may be referred to as a network or network device. In other words, the statement that a network performs message transmission and / or processing may also mean that devices within the network (network devices, and / or control devices) perform message transmission and / or processing. Conversely, the statement that devices within the network perform message transmission and / or processing may also mean that the network performs message transmission and / or processing.

[0079] Furthermore, the user plane (also called UP) refers to user data transmitted and received between the UE and the network. The UP may also be a communication channel for transmitting and receiving user data, and may consist of multiple bearers. In the case of 4G, the UP may be transmitted and received using a PDN connection, or in the case of 5G, using a PDU session. In the case of EPS, the UP may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. In the case of 5GS, the UP may be transmitted and received via the interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. The UP may also be expressed as U-Plane.

[0080] Furthermore, the control plane (also called CP) refers to control messages transmitted and received for communication control of the UE. The CP may also be a communication channel for transmitting and receiving control messages, and may consist of multiple bearers. The CP may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. The CP may also be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the AMF. In the case of EPS, the CP may be transmitted and received using the LTE-Uu interface and the S1-MME interface. In the case of 5GS, the CP may be transmitted and received using the interface between the UE and the NG RAN, and the N2 interface. The CP may be referred to as the control plane or the C-Plane.

[0081] Furthermore, the U-Plane (User Plane; UP) may also be a communication channel for sending and receiving user data, and may consist of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may also be a communication channel for sending and receiving control messages, and may consist of multiple bearers.

[0082] Furthermore, MM (Mobility Management) messages may be control messages sent and received between the UE and the AMF or MME during the MM procedure, and may also be NAS messages (also referred to as NAS MM messages).

[0083] Furthermore, MM procedures (also referred to as procedures for MM) may include a Registration procedure initiated by the UE, a De-registration procedure initiated by the UE or AMF (or network), a Generic UE Configuration Update procedure initiated by the AMF (or network), a Service Request procedure initiated by the UE, a Paging procedure initiated by the AMF (or network), and a Notification procedure initiated by the AMF (or network).

[0084] In this registration process, the UE may send a Registration Request message to the AMF and receive a Registration Accept or Registration Reject message from the AMF that has received it. The AMF may send a Registration Accept message if it approves the registration request from the UE, or a Registration Reject message if it does not.

[0085] In addition, in a de-registration procedure initiated by a UE, the UE may send a de-registration request message to the AMF and receive a de-registration acceptance message from the AMF that has received it.

[0086] In addition, in a deregistration procedure initiated by the AMF (or network), the AMF may send a deregistration request message to the UE and receive a deregistration acceptance message from the UE that received it.

[0087] In addition, in the generic UE configuration update procedure, the AMF may send a Configuration Update Command message to the UE and receive a Configuration Update Complete message from the UE that received the command.

[0088] Furthermore, in the service request procedure, the UE may send a Service Request message or a Control Plane Service Request message to the AMF, and receive a Service Accept message or a Service Reject message from the AMF that has received it. Here, the AMF may send a Service Accept message if it approves the request from the UE, or a Service Reject message if it does not approve it.

[0089] In addition, during the paging procedure, the AMF sends a Request Paging to the base station, the base station receives this and sends a Paging message to the UE, the UE receives this and sends a Service Request message, CP Service Request message, or Registration Request message to the AMF, which the AMF may receive.

[0090] In addition, during the notification procedure, the AMF may send a Notification message to the UE and receive a Notification Response message, or a Service Request message, or a CP Service Request message, or a Registration Request message from the UE that received the Notification Response message.

[0091] Furthermore, an SM (Session Management) message (also called a NAS (Non-Access-Stratum) SM message) may be a control message sent and received between the UE and the SMF via the AMF during an SM procedure, and may also be a NAS message (also called a NAS SM message).

[0092] Furthermore, SM procedures (also referred to as procedures for SMs) may include a PDU session establishment procedure initiated by the UE, a PDU session modification procedure initiated by the UE or SMF (or network), and a UE-requested PDU session release procedure initiated by the UE or SMF (or network).

[0093] In the PDU session establishment procedure, the UE may send a PDU Session Establishment Request message to the SMF and receive a PDU Session Establishment Accept message or a PDU Session Establishment Reject message from the SMF that received it. The SMF may send a PDU Session Establishment Accept message if it permits the UE's request to establish a PDU session, or a PDU Session Establishment Reject message if it does not permit it.

[0094] Furthermore, in a PDU session modification procedure initiated by the UE, the UE sends a PDU Session Modification Request message to the SMF, and upon receiving this, the SMF may either execute the PDU session modification procedure initiated by the SMF, or send a PDU Session Modification Reject message to the UE, which the UE may receive. Here, if the SMF approves the PDU session modification request from the UE, it may execute the PDU session modification procedure initiated by the SMF, or if it does not approve, it may send a PDU session modification reject message.

[0095] Furthermore, in a PDU session modification procedure initiated by the SMF (or network), the SMF may send a PDU Session Modification Command message to the UE, and may receive a PDU Session Modification Complete message or a PDU Session Modification Command Reject message from the UE that received it. Here, the UE may send a PDU Session Modification Complete message if it permits the PDU session modification instruction from the SMF, or a PDU Session Modification Command Reject message if it does not permit it.

[0096] Furthermore, in the PDU session release procedure initiated by the UE, the UE sends a PDU session release request message to the SMF, and upon receiving this, the SMF may either execute the PDU session release procedure initiated by the SMF, or send a PDU session release reject message to the UE, which the UE may receive. Here, if the SMF approves the PDU session release request from the UE, it may execute the PDU session release procedure initiated by the SMF, or if it does not approve, it may send a PDU session release reject message.

[0097] Additionally, in a PDU session release procedure initiated by the SMF (or network), the SMF may send a PDU Session Release Command message to the UE and receive a PDU Session Release Complete message from the UE that received the command.

[0098] Furthermore, the 5GS (5G System) service may be a connectivity service provided using the core network_B190. In addition, the 5GS service may be a different service from the EPS service, or it may be a service similar to the EPS service.

[0099] Furthermore, non-5GS services may be any service other than 5GS services, and may include EPS services and / or non-EPS services.

[0100] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, it means that data will be sent and received using IPv4. If IPv6 is specified, it means that data will be sent and received using IPv6. If IPv4v6 is specified, it means that data will be sent and received using either IPv4 or IPv6. If Non-IP is specified, it means that communication will be conducted using a communication method other than IP, rather than IP-based communication.

[0101] Furthermore, a PDU (Protocol Data Unit) session can be defined as the relationship between a DN and an UE that provides PDU connectivity services, but it may also be connectivity established between the UE and an external gateway. In 5GS, the UE can send and receive user data to and from the DN using the PDU session by establishing a PDU session via access network_B and core network_B. Here, this external gateway may be UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers located on the DN.

[0102] Furthermore, an MA PDU session may be a PDU session that provides PDU connectivity services using 3GPP access and / or non-3GPP access.

[0103] Furthermore, each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with each PDU session. These pieces of identification information may include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, and access network identification information, or they may include other information as well. In addition, if multiple PDU sessions are established, the pieces of identification information associated with each PDU session may be the same or different.

[0104] Furthermore, the DNN (Data Network Name) may be any identification information that identifies the core network and / or external networks such as DNs. In addition, the DNN can be used as information to select gateways such as PGW_A30 / UPF_A235 to which the core network B190 is connected. Furthermore, the DNN may be equivalent to the APN (Access Point Name).

[0105] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Ethernet may also indicate that communication using IP will not be performed. If Unstructured is specified, it indicates that data will be sent and received to application servers, etc., on the DN using Point-to-Point (P2P) tunneling technology. As a P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, IP may also be included as a PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0106] Furthermore, a PDN connection can be defined as the relationship between a PDN represented by an APN and a UE, but it may also be a connectivity established between a UE and an external gateway. In the EPS, the UE can send and receive user data to and from the PDN using the PDN connection by establishing a PDN connection via access network_A and core network_A. Here, this external gateway may be a PGW, SCEF, etc. The UE can use the PDN connection to send and receive user data with devices such as application servers located in the PDN.

[0107] Furthermore, a PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by a telecommunications operator, and the operator can be identified by the PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). In addition, the UE may maintain an Equivalent HPLMN list in the USIM to identify one or more EPLMNs (Equivalent HPLMNs). A PLMN that is different from the HPLMN and / or EPLMN may be a VPLMN (Visited PLMN). A PLMN that the UE has successfully registered may be an RPLMN (Registered PLMN; also called a Registered PLMN). Services provided by a PLMN may be called PLMN services, and services provided by an SNPN may be called SNPN services.

[0108] A tracking area is one or more ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may consist of multiple cells. Furthermore, a tracking area may be the range to which control messages such as paging are broadcast, or the range to which UE_A10 can move without handover procedures. In addition, a tracking area (also called a Tracking Area or TA) may be a routing area, a location area, or something similar. A tracking area may be identified by a Tracking Area Identity (TAI), which consists of a Tracking Area Code (TAC) and a Tracking Area Name Code (PLMN).

[0109] A registration area (also called a registration area) is a set of one or more TAs assigned by the AMF to the UE. UE_A10 may move within one or more TAs included in the registration area without sending or receiving signals for tracking area updates. In other words, a registration area may be a set of information indicating an area that UE_A10 can move within without performing the tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0110] A UE ID is information used to identify a UE, and is sometimes referred to as a UE identifier. Specifically, for example, a UE ID may be a SUCI (Subscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, a UE ID may be other information set within an application or network. Furthermore, a UE ID may be information used to identify a user. Note that a UE ID may also be a GUTI (which may be referred to as 6G-GUTI in the case of 6G) for 6G and later.

[0111] Furthermore, a UE in single registration mode only needs to have one active MM state. That is, a UE in single registration mode only needs to be active in either the RM state (5GMM state) in 5GC or the EMM state in EPC. Also, a UE in single registration mode may be in 5GC NAS mode when connecting to 5GC and in EPC NAS mode when connecting to EPC. Additionally, since a UE in single registration mode can only be registered with either 5GC or EPC, it may be necessary to map EPS-GUTI (also called 4G-GUTI) and 5G-GUTI when moving between EPC and 5GC.

[0112] Furthermore, a UE in dual registration mode may be able to register independently with 5GC and EPC. A UE in dual registration mode can maintain 5G-GUTI and EPS-GUTI (also referred to as 4G-GUTI) independently.

[0113] Furthermore, the registration attempt counter may be a counter used in the UE and / or network to limit the number of registration attempts (i.e., the number of times the registration procedure is executed). The initial value of the registration attempt counter may be 0. The maximum value of the registration attempt counter may be 5 or a different value. The value of the registration attempt counter may be incremented (i.e., increased by 1) each time a registration procedure is executed and a registration rejection message is received. The value of the registration attempt counter may also be incremented if it is not set to the maximum value. The value of the registration attempt counter may be reset when the UE is powered on, or when a USIM is inserted, or when a registration procedure is successfully completed, or when a registration procedure is rejected for a predetermined reason (in other words, when the UE receives a registration rejection message containing a predetermined reason), or when a network-initiated non-registration procedure is completed for a predetermined reason (in other words, when the UE receives a non-registration request message containing a predetermined reason), or when a new PLMN is selected. Here, resetting the value of the registration attempt counter may mean resetting its value to its initial value. Furthermore, in this specification, the value of the registration trial counter may be simply referred to as the registration trial counter.

[0114] Furthermore, the 5GS update status (also referred to as 5U status) may indicate the state of the UE in 5GS. The 5GS update status may also be stored in the non-volatile memory of the USIM or ME. The 5GS update status may also be updated after performing a registration procedure, a deregistration procedure initiated by the network, a service request procedure, a paging procedure, etc. The 5GS update status may also be updated when the TAI changes to one that does not belong to the current registration area while the NAS-level mobility management congestion control backoff timer (T3346) is operating.

[0115] Furthermore, there may be 5U1, 5U2, and 5U3 in the 5GS update state. Here, 5U1 may be called "5U1: UPDATED", 5U2 may be called "5U2: NOT UPDATED", and 5U3 may be called "5U3: ROAMING NOT ALLOWED".

[0116] Additionally, 5U1 may indicate that the last registration or attempt at registration was successful.

[0117] Furthermore, 5U2 may indicate that the last registration or attempt at registration was procedurally unsuccessful. For example, this may occur if the UE receives a registration rejection message from the AMF, or if the UE does not receive a response message (registration acceptance message or registration rejection message) from the AMF. Also, 5U2 may indicate that the last service request or attempt at service request procedure was procedurally unsuccessful. For example, this may occur if the UE receives a service denial message from the AMF, or if the UE does not receive a response message (service acceptance message or service denial message) from the AMF.

[0118] Furthermore, 5U3 may indicate that the last registration or registration procedure attempt was successfully performed, but the response or reply from AMF was negative due to roaming or subscription restrictions. Alternatively, 5U3 may indicate that the last service request or service request procedure attempt was successfully performed, but the response or reply from AMF was negative due to roaming or subscription restrictions.

[0119] Furthermore, 5G-GUTI is an identifier for UEs used in 5GS, and its purpose is to avoid revealing permanent identifiers for UEs and users. 5G-GUTI consists of GUAMI, an identifier that uniquely identifies the AMF to which 5G-GUTI is assigned, and 5G-TMSI, an identifier that uniquely identifies the UE within that AMF. GUAMI consists of MCC, MNC, and AMF Identifier. The AMF Identifier consists of an 8-bit AMF Region ID, a 10-bit AMF Set ID, and a 6-bit AMF Pointer. 5G-TMSI is 32 bits long.

[0120] Furthermore, the last visited registered TAI (Tracking Area Identity) may be a TAI included in the TAI list or registered area registered by the UE on the network, and may be an identifier that identifies the last TA visited by the UE.

[0121] Furthermore, a Sensing Service Consumer may be an entity that consumes, or potentially consumes, Sensing Result. A Sensing Service Consumer may also request Sensing Result. In other words, a Sensing Service Consumer may request Sensing Result and consume Sensing Result. A Sensing Service Consumer may also request Sensing Result from a network (3GPP network or non-3GPP network) and consume Sensing Result from that network.

[0122] Here, a 3GPP network may mean an access network defined by 3GPP (access network_A or access network_B), a core network defined by 3GPP (core network_A or core network_B), or a network composed of an access network and a core network defined by 3GPP. Furthermore, a non-3GPP network may mean an access network defined by non-3GPP (non-3GPP access network), or a network that includes an access network defined by non-3GPP (non-3GPP access network).

[0123] Furthermore, a Sensing Entity (SE) may be a Sensing Transmitter (ST) and / or a Sensing Receiver (SR), or may include both an ST and / or an SR. Note that a Sensing Transmitter may also be simply referred to as a Transmitter. Similarly, a Sensing Receiver may also be simply referred to as a Receiver. Furthermore, the SE and / or ST and / or SR may be located in a UE or base station. Also, for the sake of simplicity, in this specification, ST and SR may be referred to as SE. In other words, in this specification, SE may be read as ST and / or SR.

[0124] Furthermore, a sensing function (also called SF) may be a logical function related to supporting sensing services. Here, SE and SF may be different things.

[0125] Furthermore, Sensing Service may refer to the collection and / or provision of information regarding the characteristics of an object and / or the environment using wireless signals, or the ability to do so.

[0126] Furthermore, 3GPP sensing data may be data obtained from 3GPP radio signals. Also, 3GPP sensing data may be data derived from 3GPP radio signals that have been affected by objects and / or the environment for sensing purposes (e.g., reflected, and / or refracted, and / or diffracted), or data that has been processed within a 5G system. Here, 3GPP radio signals may mean radio signals defined by 3GPP, or signals transmitted and received wirelessly that are specified as 3GPP standards. Note that 3GPP sensing data may sometimes simply be referred to as sensing data.

[0127] Furthermore, 5G wireless sensing may be a function of a 5GS (5G system) that provides the ability to acquire information about the characteristics and objects in the environment (e.g., shape, size, direction, velocity, position, distance between objects, relative movement between objects, etc.) using NR (New Radio) radio frequency signals. This information may be extended by information generated by functions previously standardized in EPC and / or E-UTRAN.

[0128] Furthermore, non-3GPP sensing data may be data provided for sensing purposes by non-3GPP sensors (e.g., video, LiDAR, sonar) related to the object or environment. Note that non-3GPP sensing data may sometimes be simply referred to as sensing data.

[0129] Furthermore, sensing assistance information may be information provided to the 5G system by a trusted third party, or information used to support the derivation of sensing results. Sensing assistance information does not have to include 3GPP sensing data. Also, 3GPP sensing data does not have to include sensing assistance information. Furthermore, sensing assistance information may be different from 3GPP sensing data. Sensing assistance information may include, for example, map information, area information, UE ID associated with the sensing target, UE IDs near the sensing target, UE location information, and UE speed information.

[0130] Furthermore, sensing contextual information may be information provided to a trusted third party that provides context for the conditions for obtaining sensing results, and the results of sensing by the 5G system are provided to that third party. Sensing contextual information may also include, for example, map information, area information, capture count, UE location, ID, etc. Sensing contextual information may be required in scenarios where sensing results are combined with data from other resources outside the 5G system.

[0131] Furthermore, a sensing group (also referred to as an SG) may be a set of STs and SRs whose locations are known and which can synchronously collect sensing data.

[0132] Furthermore, a sensing receiver (SR) may be an entity that receives sensing signals used by a sensing service for its operation. A sensing receiver may also be part of a RAN node or UE. Additionally, a sensing receiver may be located in the same or a different entity as the sensing transmitter.

[0133] Furthermore, the sensing results may be processed 3GPP sensing data requested by the service consumer.

[0134] Furthermore, a sensing signal may be a signal transmitted on a 3GPP radio interface available for sensing, or a signal transmitted on a 3GPP radio interface available for sensing.

[0135] Furthermore, a sensing transmitter (ST) may be an entity that transmits sensing signals used by a sensing service for its operation. A sensing transmitter may also be part of a RAN node or UE. Additionally, a sensing transmitter may be located in the same or a different entity as a sensing receiver.

[0136] Furthermore, the Target sensing service area may be a Cartesian coordinate system area that needs to be sensed by deriving characteristics of the environment and / or characteristics of objects in the environment from affected (e.g., reflected, refracted, or diffracted) 3GPP radio signals, with a specific sensing service quality.

[0137] Furthermore, monostatic sensing may be sensing using ST and SR located on the same entity. Monostatic sensing is sometimes simply referred to as monostatic.

[0138] Furthermore, bistatic sensing may be a sensing method that uses STs and SRs placed on different entities. Bistatic sensing is sometimes simply referred to as bistatic.

[0139] Furthermore, multistatic sensing may refer to sensing using multiple STs and multiple SRs. Multistatic sensing is sometimes simply called multistatic.

[0140] Furthermore, in this specification, the sensing mode may also be expressed as the sensing type or the sensing function.

[0141] Furthermore, the first identification information may indicate whether the SE supports all sensing modes or types. For example, the first identification information may indicate whether the SE supports or does not support all sensing modes or types.

[0142] Here, SE supporting all sensing modes or types may mean that SE supports base station-based sensing, UE-based sensing, and UE-base station cooperative sensing. Furthermore, SE supporting all sensing modes or types may mean that SE supports base station monostatic, base station bistatic, UE bistatic, UE monostatic, UE-base station bistatic, and base station-UE bistatic.

[0143] Furthermore, the fact that SE does not support all sensing modes or types may mean that SE does not support base station-based sensing, UE-based sensing, and UE-base station cooperative sensing. In addition, the fact that SE does not support all sensing modes or types may mean that SE does not support base station monostatic, base station bistatic, UE bistatic, UE monostatic, UE-base station bistatic, and base station-UE bistatic.

[0144] Here, all sensing modes or types may include base station-based sensing, and / or UE-based sensing, and / or UE-based station coordinated sensing.

[0145] Furthermore, base station-based sensing may include base station monostatic and base station bistatic sensing.

[0146] Here, base station monostatic may be referred to as base station monostatic sensing, or base station-based sensing of base station monostatic, or base station-based monostatic sensing, etc.

[0147] Furthermore, base station bistatic sensing may also be referred to as base station bistatic sensing, base station-to-base station bistatic sensing, base station-to-base station bistatic sensing, base station-based bistatic sensing, or base station-based base station-to-base station bistatic sensing. Additionally, base station-to-base station sensing may be referred to as inter-base station sensing.

[0148] Furthermore, UE-based sensing may include UE monostatic and UE bistatic sensing.

[0149] Here, UE monostatic may be referred to as UE monostatic sensing, UE-based sensing of UE monostatic, or UE-based monostatic sensing, etc.

[0150] Furthermore, UE bistatic may also be referred to as UE bistatic sensing, UE-UE bistatic, UE-UE bistatic sensing, UE-based bistatic sensing, or UE-based UE-UE bistatic sensing. Also, UE-UE may be referred to as inter-UE.

[0151] Furthermore, UE-base station coordinated sensing may include UE-base station bistatic sensing and base station-UE bistatic sensing. Also, UE-base station coordinated sensing may be referred to as base station-UE coordinated sensing, coordinated sensing between the UE and the base station, or coordinated sensing between the base station and the UE.

[0152] Here, UE-base station bistatic sensing may be referred to as UE-base station bistatic sensing, UE-base station-based bistatic sensing, etc. Also, UE-base station may be referred to as UE-base station-to-base station.

[0153] Furthermore, base station-UE bistatic sensing may also be referred to as base station-UE bistatic sensing, base station-UE based bistatic sensing, etc. Also, base station-UE may be referred to as the connection between base station and UE.

[0154] Furthermore, sensing may be referred to as sensing mode, sensing type, or sensing mode. Sensing configuration information may be referred to as sensing control information and / or sensing measurement control information.

[0155] Furthermore, the first identification information may indicate the modes or types of sensing that the SE supports or does not support. Also, the first identification information may indicate all modes or types of sensing as supported modes or types of sensing. Furthermore, the first identification information may indicate all modes or types of sensing as unsupported modes or types of sensing.

[0156] Furthermore, the second identification information may indicate whether the SE supports base station-based sensing. For example, the second identification information may indicate whether the SE supports or does not support base station-based sensing. Here, the fact that the SE supports base station-based sensing may mean that the SE supports base station monostatic and base station bistatic. Conversely, the fact that the SE does not support base station-based sensing may mean that the SE does not support base station monostatic and base station bistatic.

[0157] Furthermore, the second identification information may indicate the modes or types of sensing that the SE supports or does not support. The second identification information may also indicate base station-based sensing as a mode or type of sensing that the SE supports. Furthermore, the second identification information may also indicate base station-based sensing as a mode or type of sensing that the SE does not support.

[0158] Furthermore, the third identification information may indicate whether the SE supports base station monostatic operation. For example, the third identification information may indicate whether the SE supports or does not support base station monostatic operation.

[0159] Furthermore, the third identification information may indicate the sensing modes or types that the SE supports or does not support. The third identification information may also indicate base station monostatic as a sensing mode or type supported by the SE. Furthermore, the third identification information may also indicate base station monostatic as a sensing mode or type that the SE does not support.

[0160] Furthermore, the fourth identification information may indicate whether the SE supports base station bistatics. For example, the fourth identification information may indicate whether the SE supports or does not support base station bistatics.

[0161] Furthermore, the fourth identification information may indicate a sensing mode or type that the SE supports or does not support. The fourth identification information may also indicate base station bistatic as a sensing mode or type that the SE supports. Furthermore, the fourth identification information may also indicate base station bistatic as a sensing mode or type that the SE does not support.

[0162] Furthermore, the fifth identifier may indicate whether the SE supports UE-based sensing. For example, the fifth identifier may indicate whether the SE supports or does not support UE-based sensing. Here, the SE supporting UE-based sensing may mean that the SE supports UE monostatic and UE bistatic sensing. Conversely, the SE not supporting UE-based sensing may mean that the SE does not support UE monostatic and UE bistatic sensing.

[0163] Furthermore, the fifth identification information may indicate a sensing mode or type that the SE supports or does not support. The fifth identification information may also indicate UE-based sensing as a sensing mode or type supported by the SE. Furthermore, the fifth identification information may also indicate UE-based sensing as a sensing mode or type that the SE does not support.

[0164] Furthermore, the sixth identifier may indicate whether the SE supports UE bistatics. For example, the sixth identifier may indicate whether the SE supports or does not support UE bistatics.

[0165] Furthermore, the sixth identification information may indicate a sensing mode or type that the SE supports or does not support. The sixth identification information may also indicate UE bistatic as a sensing mode or type that the SE supports. Furthermore, the sixth identification information may also indicate UE bistatic as a sensing mode or type that the SE does not support.

[0166] Furthermore, the seventh identifier may indicate whether the SE supports UE monostatic. For example, the seventh identifier may indicate whether the SE supports or does not support UE monostatic.

[0167] Furthermore, the seventh identification information may indicate a sensing mode or type that the SE supports or does not support. The seventh identification information may also indicate UE monostatic as a sensing mode or type supported by the SE. Furthermore, the seventh identification information may also indicate UE monostatic as a sensing mode or type that the SE does not support.

[0168] Furthermore, the eighth identification information may indicate whether the SE supports UE-base station coordinated sensing. For example, the eighth identification information may indicate whether the SE supports or does not support UE-base station coordinated sensing. Here, the fact that the SE supports UE-base station coordinated sensing may mean that the SE supports UE-base station bistatic and base station-UE bistatic. Conversely, the fact that the SE does not support UE-base station coordinated sensing may mean that the SE does not support UE-base station bistatic and base station-UE bistatic.

[0169] Furthermore, the eighth identification information may indicate a sensing mode or type that the SE supports or does not support. Also, the eighth identification information may indicate UE-base station cooperative sensing as a sensing mode or type that the SE supports. Also, the eighth identification information may indicate UE-base station cooperative sensing as a sensing mode or type that the SE does not support.

[0170] Furthermore, the ninth identification information may indicate whether the SE supports UE-base station bistatics. For example, the ninth identification information may indicate whether the SE supports or does not support UE-base station bistatics.

[0171] Furthermore, the ninth identification information may indicate a sensing mode or type that the SE supports or does not support. The ninth identification information may also indicate UE-base station bistatic as a sensing mode or type supported by the SE. Furthermore, the ninth identification information may also indicate UE-base station bistatic as a sensing mode or type that the SE does not support.

[0172] Furthermore, the tenth identification information may indicate whether the SE supports base station-UE bistatics. For example, the tenth identification information may indicate whether the SE supports or does not support base station-UE bistatics.

[0173] Furthermore, the tenth identification information may indicate a sensing mode or type that the SE supports or does not support. The tenth identification information may also indicate base station-UE bistatic as a sensing mode or type supported by the SE. Furthermore, the tenth identification information may also indicate base station-UE bistatic as a sensing mode or type that the SE does not support.

[0174] Furthermore, the eleventh identification information may indicate whether the SE supports a sensing mode or type. For example, the eleventh identification information may indicate whether the SE supports the transmission and / or ST and / or ST functions. For example, the eleventh identification information may indicate whether the SE supports or does not support the transmission and / or ST and / or ST functions.

[0175] Furthermore, the 11th identification information may indicate whether the SE supports the receiving and / or SR and / or SR functions. For example, the 11th identification information may indicate whether the SE supports or does not support the receiving and / or SR and / or SR functions.

[0176] Furthermore, the 11th identification information may indicate whether the SE supports transmit and receive, and / or ST or ST functions, and / or SR or SR functions. For example, the 11th identification information may indicate whether the SE supports or does not support transmit and receive, and / or ST or ST functions, and / or SR or SR functions.

[0177] Furthermore, the 11th identification information may indicate a sensing mode or type that the SE supports or does not support. Furthermore, the 11th identification information may indicate, as a sensing mode or type that the SE supports, transmit, and / or receive, and / or ST, and / or ST functions, and / or SR, and / or SR functions. Furthermore, the 11th identification information may indicate, as a sensing mode or type that the SE does not support, transmit, and / or receive, and / or ST, and / or ST functions, and / or SR, and / or SR functions.

[0178] Furthermore, the 11th identification information may consist of two or more bits and include a bit indicating whether or not it supports the transmit and / or ST and / or ST functions, and a bit indicating whether or not it supports the receive and / or SR and / or SR functions.

[0179] Furthermore, the 12th identification information may be an identifier (also called ID, Identifier, or Identity). The 12th identification information may also be the identifier of an SE (Sensing Entity) and / or an ST (Sensing Transmitter) and / or an SR (Sensing Receiver). If the SE and / or ST and / or SR are UEs, the 12th identification information may be the identifier of the UE. If the SE and / or ST and / or SR are base stations, the 12th identification information may be the identifier of the base station. Here, a base station may be a 3G base station (NB, NodeB), a 4G base station (eNB, evolved NB), a 5G base station (gNB), or a 6G or later base station. Furthermore, the 12th identification information may be information within the Service-level-AA container IE. Furthermore, the 12th identification information may be information set in the service-level device ID within the Service-level-AA container IE. Furthermore, the twelfth piece of identification information may be an identifier assigned by AF.

[0180] Furthermore, the 13th identification information may be information indicating location. Furthermore, the 13th identification information may be information indicating latitude and / or longitude and / or altitude. Furthermore, the 13th identification information may be a cell ID that identifies a cell, a Tracking Area Identifier (TAI) that identifies a tracking area (also called TA), or an RA ID that identifies a registered area (also called RA).

[0181] Furthermore, the 14th identification information may indicate a sensing area supported by the SE. Alternatively, the 14th identification information may indicate a sensing area not supported by the SE.

[0182] Furthermore, the 15th identification information may indicate the accuracy of sensing supported by the SE. Alternatively, the 15th identification information may indicate the accuracy of sensing not supported by the SE.

[0183] Furthermore, the 16th identification information may indicate the radio wave intensity supported by the SE. Alternatively, the 16th identification information may indicate the radio wave intensity not supported by the SE.

[0184] Furthermore, the 17th identification information may indicate the antenna gains supported by the SE. Alternatively, the 17th identification information may indicate antenna gains not supported by the SE.

[0185] Furthermore, the 18th piece of identification information may be an identifier for an application function (also known as an Application Function or AF).

[0186] Furthermore, the 19th piece of identification information may be the address (e.g., an IP address) of a network function (also known as NF) that performs authorization and / or authentication of the SE and / or ST and / or SR.

[0187] Furthermore, the 20th piece of identification information may be the SF address (for example, an IP address).

[0188] Furthermore, the 21st identification information may be information indicating that approval and / or certification is requested. Furthermore, the 21st identification information may be information indicating that approval and / or certification of SE or sensing service is requested.

[0189] Furthermore, the 31st identification information may be information indicating whether or not the approval and / or certification was successful. Furthermore, the 31st identification information may be information indicating whether the approval and / or certification was successful, unsuccessful, or failed. Furthermore, the 31st identification information may be information indicating whether the approval and / or certification of the SE and / or ST and / or SR or sensing service was successful, unsuccessful, or failed.

[0190] Furthermore, the 32nd identifier may be a reason value. The 32nd identifier may also be a reason value indicating that approval and / or authentication was unsuccessful or failed. Furthermore, the 32nd identifier may also be a reason value indicating that approval and / or authentication of SE and / or ST and / or SR or sensing services was unsuccessful or failed. Furthermore, the 32nd identifier may be a reason value sent when the 31st identifier indicates that approval and / or authentication was unsuccessful or failed. Furthermore, the 32nd identifier may indicate that the requested sensing accuracy cannot be met. Furthermore, the 32nd identifier may indicate that the sensing service is not permitted.

[0191] Furthermore, the 33rd identification information may be an identifier (also referred to as ID, Identifier, or Identity). The 33rd identification information may also be an identifier for an SE, and / or ST, and / or SR. If the SE, and / or ST, and / or SR is a UE, the 33rd identification information may be an identifier for the UE. If the SE, and / or ST, and / or SR is a base station, the 33rd identification information may be an identifier for the base station. The 33rd identification information may also be identical to the 12th identification information. Furthermore, the 33rd identification information may be an identifier (also referred to as an SG ID) that identifies the SG containing the SE, ST, or SR indicated by the 12th identification information. The 33rd identification information may also be a new identifier assigned when the 12th identification information indicates an old identifier.

[0192] Furthermore, the 34th identification information may be an identifier (also referred to as an ID) that associates the SE and / or ST and / or SR that requested approval and / or authentication with the success or failure of the approval and / or authentication for that SE and / or ST and / or SR at the NF that performs the approval and / or authentication of the SE and / or ST and / or SR.

[0193] Furthermore, the 35th identification information may indicate whether the NW supports a sensing mode or type. For example, the 35th identification information may indicate whether the NW supports or does not support a sensing mode or type. Here, this sensing mode or type may be all sensing modes or types, or modes or types included in all sensing modes or types. Specifically, the 35th identification information may indicate whether or not all sensing modes or types are supported. Also, the 35th identification information may indicate whether or not base station-based sensing, and / or UE-based sensing, and / or UE-base station coordinated sensing, and / or base station monostatic, and / or base station bistatic, and / or UE bistatic, and / or UE monostatic, and / or UE-base station bistatic, and / or base station-UE bistatic.

[0194] Furthermore, the 36th identification information may be information indicating whether approval and / or certification is pending. Alternatively, the 36th identification information may be information indicating that approval and / or certification for SE and / or ST and / or SR or sensing services is pending. Alternatively, the 36th identification information may be information indicating that approval and / or certification for SE and / or ST and / or SR or sensing services is not pending.

[0195] Furthermore, the 41st Identifier may be information or a reason value indicating the reason why the authorization and / or certification was revocation. The 41st Identifier may also indicate that the authorization and / or certification was revocation, or that the authorization and / or certification of the SE or sensing service was revocation, or that the timer managing the validity period of the authorization and / or certification expired, or that the SE moved, or that the SE moved out of the sensing area supported by the SF, or that the SE made a PLMN change (i.e., roamed), or that the number of sensing measurements exceeded the number requested, or that the number of sensing results generated exceeded the number requested, or that the number of sensing results reported exceeded the number requested, or that the maximum number of SEs that the SF can support was exceeded, or that the QoS request was changed, or changed to another SF, or that communication between the SE and the NF performing the authorization and / or certification was interrupted for a period of time, or that the sensing service is not permitted.

[0196] Furthermore, the 42nd identification information may be an identifier (also referred to as ID, Identifier, or Identity). The 42nd identification information may also be an identifier for SE and / or ST and / or SR. If SE and / or ST and / or SR are UEs, the 42nd identification information may be an identifier for the UE. If SE and / or ST and / or SR are base stations, the 42nd identification information may be an identifier for the base station. Furthermore, the 42nd identification information may be identical to the 12th identification information and / or the 33rd identification information.

[0197] Furthermore, the 43rd identification information may be an identifier that associates the SE and / or ST and / or SR that requested approval and / or certification with the success or failure of the approval and / or certification corresponding to that SE and / or ST and / or SR at the NF that approves and / or certifies the SE and / or ST and / or SR. Also, the 43rd identification information may be the same as the 34th identification information.

[0198] Furthermore, the 51st identification information may also be information indicating that a person has accepted that they have been revocation, or that their authorization and / or certification has been revoked, or that they have become aware that their authorization and / or certification has been revoked, or that they have become aware that their authorization and / or certification for SE or sensing services has been revoked.

[0199] The 51st identification information may also be information indicating that the UE has deleted and / or will delete information it stores (including sensing configuration information).

[0200] Furthermore, the 52nd identification information may be an identifier (also referred to as ID, Identifier, or Identity). Furthermore, the 52nd identification information may be an identifier for SE and / or ST and / or SR. Furthermore, if SE and / or ST and / or SR are UEs, the 52nd identification information may be an identifier for the UE. Furthermore, if SE and / or ST and / or SR are base stations, the 52nd identification information may be an identifier for the base station. Furthermore, the 52nd identification information may be the same as the 12th identification information and / or the 33rd identification information and / or the 42nd identification information.

[0201] Furthermore, the 53rd identification information may be an identifier that associates the SE and / or ST and / or SR that requested approval and / or certification with the success or failure of the approval and / or certification corresponding to that SE and / or ST and / or SR at the NF that approves and / or certifies the SE and / or ST and / or SR. Also, the 53rd identification information may be the same as the 34th identification information and / or the 43rd identification information.

[0202] Furthermore, the 61st identification information may be information indicating that sensing has been completed, and / or the requested sensing service has been completed, and / or the number of sensing measurements has exceeded the requested number, and / or the number of times sensing results have been generated has exceeded the requested number, and / or the number of times sensing results have been reported has exceeded the requested number.

[0203] [3. First Embodiment] The following describes each procedure in detail.

[0204] In this specification, the phrase "each device stores the information it has received and / or stores what is indicated by the received information" may be used interchangeably with "each device recognizes and / or considers the information indicated by the received information."

[0205] [3.1. First Procedure for Approving and / or Authenticating the SE] First, the first procedure for approving and / or authenticating the SE will be explained using Figure 6. This first procedure may be performed within the registration procedure initiated by the UE. Therefore, the registration procedure will be explained first. Note that the first procedure for approving and / or authenticating the SE may refer only to steps S606 to S608.

[0206] In this chapter, this registration procedure may be simply referred to as "this procedure." The registration procedure is a procedure initiated by the UE to register with access network_B and / or core network_B and / or DN. If the UE is not registered with the network, it can execute this procedure at any time, for example, when powered on. In other words, if the UE is in an unregistered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and AMF) can transition to a registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. Note that the registration status may be managed by each device for each access. Specifically, each device may independently manage the registration status for 3GPP access (registered or unregistered state) and the registration status for non-3GPP access.

[0207] Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network, and / or a procedure for periodically notifying the network of the status of the UE, and / or a procedure for updating specific parameters related to the UE in the network.

[0208] The UE may initiate the registration process when it moves to a TA outside its current registration area. In other words, the UE may initiate the registration process when it moves to a TA different from the TA indicated in its TAI list. Furthermore, the UE may initiate the registration process when it is necessary to update the context of each device due to the disconnection or invalidation of a PDU session. Furthermore, the UE may initiate the registration process if there is a change in the capability information and / or preferences regarding the establishment of the UE's PDU session. Furthermore, the UE may initiate the registration process periodically. Furthermore, the UE may initiate the registration process upon completion of an MM procedure or SM procedure, or based on information received from the network in each procedure. The UE may also initiate this procedure after performing one or more of the procedures described herein. However, the UE may perform the registration process at any time it chooses, not limited to these.

[0209] Furthermore, the procedure for a UE to transition from an unregistered state to a registered state may be an initial registration procedure or a registration procedure for initial registration. Additionally, a registration procedure performed when a UE is registered with the network may be a registration procedure for mobility and periodic registration update, or a mobility and periodic registration procedure.

[0210] The registration procedures described below are applicable to all of these.

[0211] First, the UE initiates the registration process by sending a NAS message containing a registration request message to the AMF (S600)(S602)(S604). Specifically, the UE sends an RRC message containing the registration request message to the base station equipment (also referred to as 5G AN or gNB) (S600). The registration request message is a NAS message transmitted and received on the N1 interface. The RRC message may be a control message transmitted and received between the UE and the base station equipment. The NAS message is processed at the NAS layer, and the RRC message is processed at the RRC layer. The NAS layer is a higher layer than the RRC layer.

[0212] Here, the UE may include at least one of the identification information items 1, 5 through 21 in the registration request message and / or RRC message.

[0213] Furthermore, the UE may transmit this identification information in a different control message at the RRC layer or NAS layer, or in a control message at a layer other than the RRC layer and NAS layer. The UE may also transmit this identification information to indicate that it supports each function, to indicate a request from the UE, or to indicate both.

[0214] Furthermore, the UE may select and decide which of the identification information items 1, 5 through 21 to transmit to the network based on the UE's capability information, and / or UE policies, and / or the UE's status, and / or the user's registration information, and / or the context held by the UE, and / or the identification information transmitted or received in procedures performed prior to this procedure. In addition, the UE may transmit at least one of the identification information items 1, 5 through 21 based on instructions from a higher or lower layer.

[0215] For example, when a UE supports sensing functionality, it may transmit at least one of the identification information items 1, 5 through 21. Conversely, when a UE does not support sensing functionality, it does not need to transmit at least one of the identification information items 1, 5 through 21.

[0216] Furthermore, if the UE supports all sensing functions, it may transmit a first identification information indicating that it supports all sensing modes or types. Conversely, if the UE does not support all sensing functions, it may transmit a first identification information indicating that it does not support all sensing modes or types.

[0217] Furthermore, if the UE supports UE-based sensing, it may transmit a fifth identification information indicating that it supports UE-based sensing. Also, if the UE does not support UE-based sensing, it may transmit a fifth identification information indicating that it does not support UE-based sensing.

[0218] Furthermore, if the UE supports UE bistatics, it may transmit a sixth identifier indicating that it supports UE bistatics. Also, if the UE does not support UE bistatics, it may transmit a sixth identifier indicating that it does not support UE bistatics.

[0219] Furthermore, if the UE supports UE monostatic, it may transmit a seventh identifier indicating that it supports UE monostatic. Also, if the UE does not support UE monostatic, it may transmit a seventh identifier indicating that it does not support UE monostatic.

[0220] Furthermore, if the UE supports UE-base station cooperative sensing, it may transmit an eighth identification information indicating that it supports UE-base station cooperative sensing. Furthermore, if the UE does not support UE-base station cooperative sensing, it may transmit an eighth identification information indicating that it does not support UE-base station cooperative sensing.

[0221] Furthermore, if the UE supports UE-base station bistatics, it may transmit a ninth identification code indicating that it supports UE-base station bistatics. Furthermore, if the UE does not support UE-base station bistatics, it may transmit a ninth identification code indicating that it does not support UE-base station bistatics.

[0222] Furthermore, if the UE supports base station-UE bistatic, it may transmit a 10th identification information indicating that it supports base station-UE bistatic. Furthermore, if the UE does not support base station-UE bistatic, it may transmit a 10th identification information indicating that it does not support base station-UE bistatic.

[0223] Furthermore, if the UE supports the transmit and / or ST and / or ST functions, it may transmit an eleventh identification information indicating that it supports the transmit and / or ST and / or ST functions. Furthermore, if the UE does not support the transmit and / or ST and / or ST functions, it may transmit an eleventh identification information indicating that it does not support the transmit and / or ST and / or ST functions.

[0224] Furthermore, if the UE supports the receiving and / or SR and / or SR functions, it may transmit an eleventh identification indicating that it supports the receiving and / or SR and / or SR functions. Furthermore, if the UE does not support the receiving and / or SR and / or SR functions, it may transmit an eleventh identification indicating that it does not support the receiving and / or SR and / or SR functions.

[0225] Furthermore, if the UE supports transmit and receive, and / or ST or ST functions, and / or SR or SR functions, it may transmit an eleventh identification information indicating that it supports transmit and receive, and / or ST or ST functions, and / or SR or SR functions. Furthermore, if the UE does not support transmit and receive, and / or ST or ST functions, and / or SR or SR functions, it may transmit an eleventh identification information indicating that it does not support transmit and receive, and / or ST or ST functions, and / or SR or SR functions.

[0226] Furthermore, the UE's decision on whether or not to transmit any of the identification information items 1, 5 through 21 to the network is not limited to the above conditions, and may be made by, for example, a combination of the above conditions.

[0227] Furthermore, the UE may include information other than the identification information described in items 1, 5 through 21 in the registration request message and / or RRC message, for example, the UE ID and / or PLMN ID and / or AMF identification information. Here, the AMF identification information may be information that identifies an AMF or a set of AMFs, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0228] Next, when the base station device receives an RRC message containing a registration request message, it selects an AMF to forward the registration request message (S602). The base station device may also select an AMF based on the identification information contained in the registration request message and / or the RRC message. Specifically, when the base station device receives the first, fifth to 21 identification information, it may select an AMF to which the registration request message should be sent based on the first, fifth to 21 identification information. For example, the base station device may select an AMF included in the network slice identified by the first, fifth to 21 identification information, or an AMF that has connectivity to the network slice identified by the first, fifth to 21 identification information. The method of selecting an AMF is not limited to this, and the base station device may select an AMF based on other conditions.

[0229] Furthermore, the base station device extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S604). If the identification information of items 1, 5 to 21 is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message may be forwarded to the selected AMF together with the registration request message (S604).

[0230] Next, if the AMF receives a registration request message, it may perform a first condition determination (not shown). Here, the first condition determination may be for determining whether or not the network accepts the UE's request. If the AMF determines that the first condition determination is true, it may execute the procedures from S606 to S612; if it determines that the first condition determination is false, it may execute the procedure in S610.

[0231] Furthermore, the first condition determination by AMF may be performed after receiving the response message S608. In this case, if AMF determines that the first condition determination is true, it may execute the procedures from S610 to S612, and if it determines that the first condition determination is false, it may execute the procedure in S610.

[0232] Next, if the AMF receives a registration request message and / or if the registration request message contains the first, 5 to 21 identification information, it may send a request message to the NF containing at least one of the first, 5 to 21 identification information (S606). Here, the NF may be an NF specifically prepared for the authorization and / or authentication of SEs, an NF prepared for the authorization and / or authentication of SEs and sensing services, an NEF (Network Exposure Function), an UDM (Unified Data Management), an NWDAF (Network Data Analytics Function), or another existing NF.

[0233] Furthermore, the AMF does not need to send a request message to the NF if the NW does not support the sensing mode or type. In other words, the AMF may only send a request message to the NF if the NW supports the sensing mode or type.

[0234] Next, if the NF receives a request message from the AMF, it may decide whether or not to approve and / or authenticate the UE as an SE based on the identification information contained in the request message (S607).

[0235] For example, if an NF approves and / or certifies a UE as an SE, it may store that the UE has been certified and / or authenticated as an SE. In this case, the UE may be stored in association with the fact that it has been certified and / or authenticated as an SE, or an identifier (ID) shown in the 34th identification information and / or an identifier that identifies the SG shown in the 33rd identification information may be assigned to that association and stored.

[0236] Furthermore, if the NF does not approve and / or authenticate the UE as an SE (if approval and / or authentication is unsuccessful), it may remember that the UE was authenticated and / or not authenticated as an SE. In this case, the NF may store the UE and the fact that it was authenticated and / or not authenticated as an SE in association, or it may further assign an identifier (ID) shown in the 34th Identification Information to that association and store it.

[0237] Next, NF may send AMF a response message containing at least one of the identification information from 31 to 35 (S608).

[0238] For example, if NF approves and / or certifies its UE as SE, it may transmit a 31st Identification Information indicating that the approval and / or certification of the SE was successful, and / or a 33rd Identification Information indicating the SE identifier or the SG identifier, and / or a 34th Identification Information, and / or a 35th Identification Information.

[0239] Furthermore, if the NF does not approve and / or authenticate the UE as an SE, it may transmit a 31st identification information indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 32nd identification information indicating a reason value indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 33rd identification information indicating an identifier of the SE or an identifier of the SG, and / or a 35th identification information.

[0240] Furthermore, if the NW supports the sensing mode or type, the NF may transmit a 35th identification piece indicating that it supports the sensing mode or type. Also, if the NW does not support the sensing mode or type, the NF may transmit a 35th identification piece indicating that it does not support the sensing mode or type, and may not transmit any of the 31st to 34th identification pieces.

[0241] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the AMF, that it cannot approve and / or authenticate the UE as an SE, it may transmit the 31st and / or 32nd identification pieces.

[0242] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the AMF, that it can approve and / or authenticate the UE as an SE, it may transmit at least one of the identification pieces from paragraphs 31, 33 to 35.

[0243] Next, if the AMF receives a response message (S608), it may perform the first condition determination described above.

[0244] Furthermore, the control message sent and received in S610 may be a registration accept message or a registration reject message. For example, if the first condition determination is true, the control message sent and received in S610 may be a registration accept message, and if the first condition determination is false, the control message sent and received in S610 may be a registration accept message or a registration reject message.

[0245] Furthermore, the first condition determination may be performed based on the receipt of a registration request message and / or each identification piece contained in the registration request message and / or the receipt of a response message and / or each identification piece contained in the response message and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user registration information and / or context held by AMF, etc.

[0246] For example, if the network neither allows nor rejects the UE's request, the first condition determination may be judged as true, and if the network neither allows nor rejects the UE's request, the first condition determination may be judged as false. Furthermore, if the network neither allows nor rejects only a portion of the UE's request, even if there are UE requests that are not allowed, the first condition determination may be judged as true. Also, if the network neither allows nor rejects all of the UE's requests, the first condition determination may be judged as false. In addition, if the network to which the UE is registered, and / or the devices within the network, support the functions requested by the UE, the first condition determination may be judged as true, and if they do not support the functions requested by the UE, the first condition determination may be judged as false. Furthermore, if the transmitted and received identification information is permitted, the first condition determination may be judged as true, and if the transmitted and received identification information is not permitted, the first condition determination may be judged as false.

[0247] Furthermore, the AMF may include one or more of the identification information from items 31 to 35 in the control message and transmit it to the UE via the base station equipment (S610). The AMF may also indicate by transmitting these identification information and / or the control message whether the network supports each function (including functions for sensing), whether the UE's request has been accepted or permitted, or a combination thereof.

[0248] Furthermore, the AMF may store the contents of the received identification information when it receives a registration request message from the UE that includes at least one of the identification information from the 1st, 5th to 21st. Also, the AMF may store the contents of the received identification information when it receives a response message from the NF that includes at least one of the identification information from the 31st to 35th.

[0249] Furthermore, if the AMF receives a registration request message from the UE containing at least one of the 1st, 5th to 21st identification information, and / or receives a response message from the NF containing at least one of the 31st to 35th identification information, the AMF may include at least one of the 31st to 35th identification information in a control message and send it.

[0250] Furthermore, AMF may decide whether or not to include any of the identification information from items 31 to 35 in the control message, based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF, and / or identification information sent or received in procedures performed prior to this procedure.

[0251] Furthermore, the AMF may include at least a portion of the identification information contained in the response message received from the NF directly into the control message and send it to the UE.

[0252] Furthermore, the AMF may replace the content of at least a portion of the identification information received from the NF and send it to the UE. For example, the AMF may send the UE the 32nd identification information to which the content received from the NF has been changed to something else. For example, if the 32nd identification information included in the response message received from the NF indicates a reason value indicating that the SE's approval and / or authentication was unsuccessful, the AMF may send the UE a control message containing the 32nd identification information indicating a reason value indicating that the sensing service is not permitted.

[0253] Furthermore, if AMF receives identification number 35 from NF indicating that it does not support the sensing mode or type, AMF may transmit identification number 35 and / or identification number 32 indicating that it does not support the sensing mode or type, but may not transmit identification number 31 and / or identification number 33 and / or identification number 34. Identification number 32 may indicate a reason value indicating that the sensing service is not permitted or that SE approval and / or authentication was unsuccessful.

[0254] Next, the UE receives a control message via the base station equipment (S610). If the control message is an acceptance message, the UE may recognize and store that its request via the registration request message has been accepted, and the contents of each piece of identification information included in the acceptance message. If the control message is a rejection message, the UE may recognize and store that its request via the registration request message has been rejected, and the contents of each piece of identification information included in the rejection message. The UE may also take action based on the received control message and / or identification information.

[0255] For example, upon receiving a control message, the UE may abort the procedure, reset the registration attempt counter, set the 5GS update status to 5U2 or 5U3, delete all 5G-GUTIs, delete the last visited registered TAI, delete the equivalent PLMN list, or, if performing the registration procedure again for the current PLMN, not set the 12th identification information in the registration request message, nor include the 12th identification information.

[0256] Furthermore, the UE that receives the 31st identification information may remember and / or recognize whether the SE's authorization and / or authentication was successful, unsuccessful, or failed.

[0257] Furthermore, the UE that received the 32nd identification information may remember and / or recognize that the SE's authorization and / or authentication was unsuccessful or failed.

[0258] Furthermore, a UE that receives the 33rd identification information may store and / or recognize the identifier of the SE and / or the identifier of the SG. If the UE receives the 33rd identification information which differs from the content of the 12th identification information, it may overwrite the stored 12th identification information with the identifier of the SE indicated by the 33rd identification information.

[0259] Furthermore, the UE that receives the 34th identification information may store and / or recognize the ID indicated by the 34th identification information.

[0260] Furthermore, the UE that receives the 35th identification information may store and / or recognize, based on its contents, whether the NW supports a sensing mode or type.

[0261] Furthermore, upon receiving a registration acceptance message, a UE in 5GMM-IDLE mode may transition to 5GMM-CONNECTED mode, or a UE in 5GMM-CONNECTED mode may maintain 5GMM-CONNECTED mode.

[0262] Furthermore, when a registration rejection message is received, a UE in 5GMM-IDLE mode may maintain 5GMM-IDLE mode, and a UE in 5GMM-CONNECTED mode may transition to 5GMM-IDLE mode.

[0263] Furthermore, if the control message is a registration acceptance message, the UE may send a registration completion message to the AMF via the base station equipment as a response message to the registration acceptance message (S612). Here, the registration completion message is a NAS message sent and received on the N1 interface, but it may be sent and received between the UE and the base station equipment as part of an RRC message.

[0264] The AMF receives a registration completion message via the base station equipment (S612). Each device also completes this procedure based on the sending and receiving of a registration acceptance message and / or a registration completion message.

[0265] Furthermore, each device may complete the registration procedure based on the sending and receiving of registration rejection messages.

[0266] Furthermore, each device may transition to or maintain a state in which the UE is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of registration acceptance messages and / or registration completion messages, or may transition to or maintain a state in which the UE is not registered with the network on the access for which a registration rejection message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending and receiving of registration rejection messages. In addition, each device may transition to each state based on the sending and receiving of registration completion messages or the completion of the registration procedure.

[0267] Furthermore, each device may perform processing based on the information sent and received during the registration process, upon completion of the registration procedure. For example, if it receives information indicating that some of the UE's requests were rejected, it may recognize the reason why the UE's requests were rejected. Furthermore, each device may perform the procedure again based on the reason why the UE's requests were rejected, or it may perform the registration procedure for core network_A or another cell.

[0268] Furthermore, based on the completion of the registration process, the UE may store the identification information received along with the registration acceptance message and / or registration rejection message, and may recognize the network's decision.

[0269] Furthermore, each device may store the information transmitted and received during this procedure in an associated manner.

[0270] Furthermore, each step from S606 to S608 may be sent and received as control messages in a layer different from the NAS layer. For example, these control messages may be control messages in a sensing layer specifically designed for sensing purposes and / or for exchanging control information related to sensing.

[0271] [3.2. Second Procedure for Approving and / or Certifying SEs] Next, the second procedure for approving and / or certifying SEs will be explained using Figures 6 and 7.

[0272] This second procedure is an improvement on part of the procedure in Chapter 3.1 described above. The difference from the first procedure lies in step S700 onwards. Therefore, the parts common to Chapter 3.1 (steps S600 to S604) can be applied directly to this chapter, and the following explanation will focus on the differences from the procedure in Chapter 3.1.

[0273] Furthermore, the second procedure for approving and / or certifying the SE may refer only to steps S716 to S718 and part of step S720.

[0274] In this chapter, this registration procedure may sometimes be simply referred to as "this procedure."

[0275] First, please refer to Chapter 3.1 for an explanation of each step from S600 to S604.

[0276] Next, if the AMF receives a registration request message, it may perform a first condition determination (not shown) and a second condition determination (S700). Here, the first condition determination may be for determining whether the network accepts the UE's request. If the AMF determines that the first condition determination is true, it may execute the procedures from S710 to S712; if it determines that the first condition determination is false, it may execute the procedure in S710.

[0277] Furthermore, the second conditional determination (S700) may be for determining whether or not to execute steps S716 to S718 and S720. If the AMF determines that the second conditional determination is true, it executes the procedures from S716 to S720; if it determines that the second conditional determination is false, it does not need to execute the procedures from S716 to S720. In the following explanation, the first and second conditional determinations are described as independent, but the second conditional determination may be performed within the first conditional determination.

[0278] For example, AMF may determine the second condition to be true if the network supports the sensing mode or type, or it may determine the second condition to be false if the network does not support the sensing mode or type.

[0279] Furthermore, if the AMF receives a first identification marker indicating support for all sensing modes or types, and / or a fifth identification marker indicating support for UE-based sensing, and / or a sixth identification marker indicating support for UE bistatic, and / or a seventh identification marker indicating support for UE monostatic, an eighth identification marker indicating support for UE-base station cooperative sensing, and / or a ninth identification marker indicating support for UE-base station bistatic, and / or a tenth identification marker indicating support for base station-UE bistatic, and / or an eleventh identification marker indicating support for transmit, and / or ST, and / or ST functionality, and / or eleventh identification marker indicating support for receive, and / or SR, and / or SR functionality, and / or an eleventh identification marker indicating support for transmit and receive, and / or ST or ST functionality, and / or SR or SR functionality, the second condition determination may be determined to be true.

[0280] Furthermore, if the AMF receives a first identification information indicating that it does not support any sensing mode or type, and / or a fifth identification information indicating that it does not support UE-based sensing, and / or a sixth identification information indicating that it does not support UE bistatic, and / or a seventh identification information indicating that it does not support UE monostatic, an eighth identification information indicating that it does not support UE-base station cooperative sensing, and / or a ninth identification information indicating that it does not support UE-base station bistatic, and / or a tenth identification information indicating that it does not support base station-UE bistatic, and / or an eleventh identification information indicating that it does not support transmit, and / or ST, and / or ST functions, and / or eleventh identification information indicating that it does not support receive, and / or SR, and / or SR functions, and / or an eleventh identification information indicating that it does not support transmit and receive, and / or ST or ST functions, and / or SR or SR functions, the second condition determination may be judged as false.

[0281] Furthermore, AMF may determine the second condition to be true if the SE approval and / or certification procedure is performed after the registration procedure. Conversely, AMF may determine the second condition to be false if the SE approval and / or certification procedure is not performed after the registration procedure.

[0282] Furthermore, the control message sent and received by S710 may be a registration accept message or a registration reject message. For example, if the first condition determination is true, the control message sent and received by S710 may be a registration accept message, and if the first condition determination is false, the control message sent and received by S710 may be a registration accept message or a registration reject message.

[0283] Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or the identification information contained in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF, etc.

[0284] For example, if the network neither allows nor rejects the UE's request, the first condition determination may be judged as true, and if the network neither allows nor rejects the UE's request, the first condition determination may be judged as false. Furthermore, if the network neither allows nor rejects only a portion of the UE's request, even if there are UE requests that are not allowed, the first condition determination may be judged as true. Also, if the network neither allows nor rejects all of the UE's requests, the first condition determination may be judged as false. In addition, if the network to which the UE is registered, and / or the devices within the network, support the functions requested by the UE, the first condition determination may be judged as true, and if they do not support the functions requested by the UE, the first condition determination may be judged as false. Furthermore, if the transmitted and received identification information is permitted, the first condition determination may be judged as true, and if the transmitted and received identification information is not permitted, the first condition determination may be judged as false.

[0285] Furthermore, the AMF may include at least one of the identification information items 32, 35, and 36 in the control message and transmit it to the UE via the base station equipment (S710). The AMF may also indicate by transmitting these identification information items and / or the control message whether the network supports each function (including functions for sensing), whether the UE's request has been accepted, whether the request from the UE has been permitted, or a combination of these.

[0286] Furthermore, if the AMF receives a registration request message from the UE that includes at least one of the first, fifth to 21 pieces of identification information, it may store the contents of the received identification information.

[0287] Furthermore, when the AMF receives a registration request message from the UE containing at least one of the first, 5 to 21 identification information, and / or when the second condition determination is true or false, it may include at least one of the 32, 35, and 36 identification information in a control message and send it.

[0288] Furthermore, AMF may decide whether or not to include any of the identification information described in paragraphs 32, 35, and 36 in the control message, based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by AMF, and / or identification information sent or received in procedures performed prior to this procedure.

[0289] Furthermore, if the second condition determination is true, the AMF may include a 36th piece of identification information indicating that the SE's approval and / or certification is pending.

[0290] Furthermore, if the second condition is false, the AMF may not include the 36th identification information, or it may include the 36th identification information indicating that the SE's approval and / or certification is not pending.

[0291] Furthermore, if the NW supports a sensing mode or type, the AMF may include a 35th identification in the control message indicating that the NW supports a sensing mode or type. Furthermore, if the NW does not support a sensing mode or type, the AMF may include a 35th identification in the control message indicating that the NW does not support a sensing mode or type.

[0292] Furthermore, if the second condition is false, the AMF may include a 32nd identifier in the control message indicating that the sensing service is not permitted.

[0293] Next, the UE receives a control message (registration acceptance message or registration rejection message) via the base station equipment (S710). If the control message is a registration acceptance message, the UE may recognize and store that its request via the registration request message has been accepted and the contents of each piece of identification information included in the registration acceptance message. If the control message is a registration rejection message, the UE may recognize and store that its request via the registration request message has been rejected and the contents of each piece of identification information included in the registration rejection message. The UE may also take action based on the received control message and / or identification information.

[0294] For example, upon receiving a control message, the UE may abort the procedure, reset the registration attempt counter, set the 5GS update status to 5U2 or 5U3, delete all 5G-GUTIs, delete the last visited registered TAI, delete the equivalent PLMN list, or, if performing the registration procedure again for the current PLMN, not include the 12th identification information in the registration request message.

[0295] Furthermore, the UE that receives the 32nd identification information may remember and / or recognize that the sensing service is not permitted.

[0296] Furthermore, the UE that receives the 35th identification information may store and / or recognize, based on its contents, whether the NW supports a sensing mode or type.

[0297] Furthermore, upon receiving the 36th identification information, the UE may, based on its contents, remember and / or recognize whether the SE's approval and / or certification is pending. In this case, if the UE remembers and / or recognizes that the SE's approval and / or certification is pending, it may remember and / or recognize that the second procedure will be initiated after or during the registration procedure.

[0298] Furthermore, upon receiving a registration acceptance message, a UE in 5GMM-IDLE mode may transition to 5GMM-CONNECTED mode, or a UE in 5GMM-CONNECTED mode may maintain 5GMM-CONNECTED mode.

[0299] Furthermore, when a registration rejection message is received, a UE in 5GMM-IDLE mode may maintain 5GMM-IDLE mode, and a UE in 5GMM-CONNECTED mode may transition to 5GMM-IDLE mode.

[0300] Furthermore, if the control message is a registration acceptance message, the UE may send a registration completion message to the AMF via the base station equipment as a response message to the registration acceptance message (S712). Here, the registration completion message is a NAS message sent and received on the N1 interface, but it may be sent and received between the UE and the base station equipment as part of an RRC message.

[0301] The AMF receives a registration completion message via the base station equipment (S612). Each device also completes this procedure based on the sending and receiving of a registration acceptance message and / or a registration completion message.

[0302] Furthermore, each device may complete the registration procedure based on the sending and receiving of registration rejection messages.

[0303] Furthermore, each device may transition to or maintain a state in which the UE is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of registration acceptance messages and / or registration completion messages, or may transition to or maintain a state in which the UE is not registered with the network on the access for which a registration rejection message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending and receiving of registration rejection messages. In addition, each device may transition to each state based on the sending and receiving of registration completion messages or the completion of the registration procedure.

[0304] Furthermore, each device may perform processing based on the information sent and received during the registration process, upon completion of the registration procedure. For example, if it receives information indicating that some of the UE's requests were rejected, it may recognize the reason why the UE's requests were rejected. Furthermore, each device may perform the procedure again based on the reason why the UE's requests were rejected, or it may perform the registration procedure for core network_A or another cell.

[0305] Furthermore, based on the completion of the registration process, the UE may store the identification information received along with the registration acceptance message and / or registration rejection message, and may recognize the network's decision.

[0306] Furthermore, each device may store the information transmitted and received during this procedure in an associated manner.

[0307] Next, we will describe the steps from S716 onward that are executed when AMF determines that the second condition is true.

[0308] If the AMF determines that the second condition determination is true, and / or receives a registration request message, and / or the registration request message contains the first, 5 to 21 identification information, it may send a request message to the NF containing at least one of the first, 5 to 21 identification information (S716). Here, the NF may be an NF specifically prepared for the approval and / or authentication of SEs, an NF prepared for the approval and / or authentication of SEs and sensing services, an NEF, an UDM, an NWDAF, or any other existing NF.

[0309] Next, if the NF receives a request message, it may decide whether or not to approve and / or authenticate the UE as an SE based on the identification information received from the AMF (S717).

[0310] For example, if an NF approves and / or certifies a UE as an SE, it may store that the UE has been certified and / or authenticated as an SE. In this case, the UE may be stored in association with the fact that it has been certified and / or authenticated as an SE, or an identifier (ID) shown in the 34th identification information and / or an identifier that identifies the SG shown in the 33rd identification information may be assigned to that association and stored.

[0311] Furthermore, if the NF does not approve and / or authenticate the UE as an SE (if approval and / or authentication is unsuccessful), it may remember that the UE was authenticated and / or not authenticated as an SE. In this case, the NF may store the UE and the fact that it was authenticated and / or not authenticated as an SE in association, or it may further assign an identifier (ID) shown in the 34th Identification Information to that association and store it.

[0312] Next, NF may send AMF a response message containing at least one of the identification information from 31 to 35 (S718).

[0313] For example, if NF approves and / or certifies its UE as SE, it may transmit a 31st Identification Information indicating that the approval and / or certification of the SE was successful, and / or a 33rd Identification Information indicating the SE identifier or the SG identifier, and / or a 34th Identification Information, and / or a 35th Identification Information.

[0314] Furthermore, if the NF does not approve and / or authenticate the UE as an SE, it may transmit a 31st identification information indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 32nd identification information indicating a reason value indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 33rd identification information indicating an identifier of the SE or an identifier of the SG, and / or a 35th identification information.

[0315] Furthermore, if the NW supports the sensing mode or type, the NF may transmit a 35th identification piece indicating that it supports the sensing mode or type. Also, if the NW does not support the sensing mode or type, the NF may transmit a 35th identification piece indicating that it does not support the sensing mode or type, and may not transmit any of the 31st to 34th identification pieces.

[0316] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the AMF, that it cannot approve and / or authenticate the UE as an SE, it may transmit the 31st and / or 32nd identification pieces.

[0317] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the AMF, that it can approve and / or authenticate the UE as an SE, it may transmit at least one of the identification pieces from paragraphs 31, 33 to 35.

[0318] Next, upon receiving a response message (S718), the AMF may transmit a second control message to the UE via the base station equipment, including one or more of the identification information from 31 to 35 (S720). The AMF may also indicate, by transmitting this identification information and / or the second control message, whether the network supports each function (including functions for sensing), whether the UE's request has been accepted or permitted, or a combination thereof.

[0319] Furthermore, the second control message transmitted and received by the S720 may be a configuration update command message or a DL NAS TRANSPORT message.

[0320] Furthermore, if the AMF receives a response message from the NF that includes at least one of the identification information items 31 to 35, it may store the contents of the received identification information.

[0321] Furthermore, if the AMF receives a response message from the NF that includes at least one of the identification information items 31 to 35, it may include at least one of the identification information items 31 to 35 in a second control message and send it.

[0322] Furthermore, AMF may decide whether or not to include any of the identification information from items 31 to 35 in the second control message, based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF, and / or identification information sent or received in procedures performed prior to this procedure.

[0323] Furthermore, the AMF may include at least a portion of the identification information contained in the response message received from the NF directly into the second control message and send it to the UE.

[0324] Furthermore, the AMF may replace the content of at least a portion of the identification information received from the NF and send it to the UE. For example, the AMF may send the UE the 32nd identification information to which the content received from the NF has been changed to something else. For example, if the 32nd identification information included in the response message received from the NF indicates a reason value indicating that the SE's approval and / or authentication was unsuccessful, the AMF may send the UE a control message containing the 32nd identification information indicating a reason value indicating that the sensing service is not permitted.

[0325] Furthermore, if AMF receives identification number 35 from NF indicating that it does not support the sensing mode or type, AMF may transmit identification number 35 and / or identification number 32 indicating that it does not support the sensing mode or type, but may not transmit identification number 31 and / or identification number 33 and / or identification number 34. Identification number 32 may indicate a reason value indicating that the sensing service is not permitted or that SE approval and / or authentication was unsuccessful.

[0326] Next, the UE receives a second control message via the base station equipment (S720). Upon receiving the second control message, the UE may recognize and store the contents of each identification information contained in the second control message. The UE may also perform actions based on the received second control message and / or identification information.

[0327] For example, upon receiving the second control message, the UE may abort the procedure, reset the registration attempt counter, set the 5GS update status to 5U2 or 5U3, delete all 5G-GUTIs, delete the last visited registered TAI, delete the equivalent PLMN list, or, if performing the registration procedure again for the current PLMN, not set the 12th identification information in the registration request message, nor include the 12th identification information.

[0328] Furthermore, the UE that receives the 31st identification information may remember and / or recognize whether the SE's authorization and / or authentication was successful, unsuccessful, or failed.

[0329] Furthermore, the UE that received the 32nd identification information may remember and / or recognize that the SE's authorization and / or authentication was unsuccessful or failed.

[0330] Furthermore, a UE that receives the 33rd identification information may store and / or recognize the identifier of the SE and / or the identifier of the SG. If the UE receives the 33rd identification information which differs from the content of the 12th identification information, it may overwrite the stored 12th identification information with the identifier of the SE indicated by the 33rd identification information.

[0331] Furthermore, the UE that receives the 34th identification information may store and / or recognize the ID indicated by the 34th identification information.

[0332] Furthermore, the UE that receives the 35th identification information may store and / or recognize, based on its contents, whether the NW supports a sensing mode or type.

[0333] Furthermore, if a control message containing the 32nd identification information (a registration acceptance message or a registration rejection message) has been sent, the AMF does not need to include the 32nd identification information in the second control message.

[0334] Furthermore, each step from S716 to S720 may be sent and received as control messages in a layer different from the NAS layer. For example, these control messages may be control messages in a sensing layer specifically designed for sensing purposes and / or for exchanging control information related to sensing.

[0335] [3.3. Third Procedure for Approving and / or Certifying SEs] Next, a third procedure for approving and / or certifying SEs will be explained using Figure 8. This third procedure may be a procedure conducted between the UE or base station and the NF.

[0336] First, let's explain the procedures that take place between the UE and the NF.

[0337] The UE may send a request message to the NF containing at least one of the identification information items 1, 5 to 21 (S802). At this time, the UE may be in a registered state. This NF may be an NF prepared specifically for the authorization and / or authentication of SEs, an NF prepared for the authorization and / or authentication of SEs and sensing services, an NEF, an UDM, an NWDAF, or another existing NF.

[0338] Furthermore, the UE may select and decide whether or not to transmit any of the identification information from items 1, 5 through 21 based on the UE's capability information, and / or UE policies, and / or the UE's status, and / or the user's registration information, and / or the context held by the UE, and / or the identification information sent and received in procedures performed prior to this procedure. In addition, the UE may transmit at least one of the identification information from items 1, 5 through 21 based on instructions from a higher or lower layer.

[0339] For example, when a UE supports sensing functionality, it may transmit at least one of the identification information items 1, 5 through 21. Conversely, when a UE does not support sensing functionality, it does not need to transmit at least one of the identification information items 1, 5 through 21.

[0340] Furthermore, if the UE supports all sensing functions, it may transmit a first identification information indicating that it supports all sensing modes or types. Conversely, if the UE does not support all sensing functions, it may transmit a first identification information indicating that it does not support all sensing modes or types.

[0341] Furthermore, if the UE supports UE-based sensing, it may transmit a fifth identification information indicating that it supports UE-based sensing. Also, if the UE does not support UE-based sensing, it may transmit a fifth identification information indicating that it does not support UE-based sensing.

[0342] Furthermore, if the UE supports UE bistatics, it may transmit a sixth identifier indicating that it supports UE bistatics. Also, if the UE does not support UE bistatics, it may transmit a sixth identifier indicating that it does not support UE bistatics.

[0343] Furthermore, if the UE supports UE monostatic, it may transmit a seventh identifier indicating that it supports UE monostatic. Also, if the UE does not support UE monostatic, it may transmit a seventh identifier indicating that it does not support UE monostatic.

[0344] Furthermore, if the UE supports UE-base station cooperative sensing, it may transmit an eighth identification information indicating that it supports UE-base station cooperative sensing. Furthermore, if the UE does not support UE-base station cooperative sensing, it may transmit an eighth identification information indicating that it does not support UE-base station cooperative sensing.

[0345] Furthermore, if the UE supports UE-base station bistatics, it may transmit a ninth identification code indicating that it supports UE-base station bistatics. Furthermore, if the UE does not support UE-base station bistatics, it may transmit a ninth identification code indicating that it does not support UE-base station bistatics.

[0346] Furthermore, if the UE supports base station-UE bistatic, it may transmit a 10th identification information indicating that it supports base station-UE bistatic. Furthermore, if the UE does not support base station-UE bistatic, it may transmit a 10th identification information indicating that it does not support base station-UE bistatic.

[0347] Furthermore, if the UE supports the transmit and / or ST and / or ST functions, it may transmit an eleventh identification information indicating that it supports the transmit and / or ST and / or ST functions. Furthermore, if the UE does not support the transmit and / or ST and / or ST functions, it may transmit an eleventh identification information indicating that it does not support the transmit and / or ST and / or ST functions.

[0348] Furthermore, if the UE supports the receiving and / or SR and / or SR functions, it may transmit an eleventh identification indicating that it supports the receiving and / or SR and / or SR functions. Furthermore, if the UE does not support the receiving and / or SR and / or SR functions, it may transmit an eleventh identification indicating that it does not support the receiving and / or SR and / or SR functions.

[0349] Furthermore, if the UE supports transmit and receive, and / or ST or ST functions, and / or SR or SR functions, it may transmit an eleventh identification information indicating that it supports transmit and receive, and / or ST or ST functions, and / or SR or SR functions. Furthermore, if the UE does not support transmit and receive, and / or ST or ST functions, and / or SR or SR functions, it may transmit an eleventh identification information indicating that it does not support transmit and receive, and / or ST or ST functions, and / or SR or SR functions.

[0350] Furthermore, the UE's decision on whether or not to transmit any of the identification information items 1, 5 through 21 to the network is not limited to the above conditions, and may be made by, for example, a combination of the above conditions.

[0351] Next, if the NF receives a request message (S802), it may decide whether or not to approve and / or authenticate the UE as an SE based on the identification information contained in the request message (S804).

[0352] For example, if an NF approves and / or certifies a UE as an SE, it may store that the UE has been certified and / or authenticated as an SE. In this case, the UE may be stored in association with the fact that it has been certified and / or authenticated as an SE, or an identifier (ID) shown in the 34th identification information and / or an identifier that identifies the SG shown in the 33rd identification information may be assigned to that association and stored.

[0353] Furthermore, if the NF does not approve and / or authenticate the UE as an SE (if approval and / or authentication is unsuccessful), it may remember that the UE was authenticated and / or not authenticated as an SE. In this case, the NF may store the UE and the fact that it was authenticated and / or not authenticated as an SE in association, or it may further assign an identifier (ID) shown in the 34th Identification Information to that association and store it.

[0354] Next, the NF may send a response message to the UE that includes at least one of the identification information from 31 to 35 (S806).

[0355] For example, if NF approves and / or certifies its UE as SE, it may transmit a 31st Identification Information indicating that the approval and / or certification of the SE was successful, and / or a 33rd Identification Information indicating the SE identifier or the SG identifier, and / or a 34th Identification Information, and / or a 35th Identification Information.

[0356] Furthermore, if the NF does not approve and / or authenticate the UE as an SE, it may transmit a 31st identification information indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 32nd identification information indicating a reason value indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 33rd identification information indicating an identifier of the SE or an identifier of the SG, and / or a 35th identification information.

[0357] Furthermore, if the NW supports the sensing mode or type, the NF may transmit a 35th identification piece indicating that it supports the sensing mode or type. Also, if the NW does not support the sensing mode or type, the NF may transmit a 35th identification piece indicating that it does not support the sensing mode or type, and may not transmit any of the 31st to 34th identification pieces.

[0358] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the UE, that it cannot approve and / or authenticate the UE as an SE, it may transmit the 31st and / or 32nd identification pieces.

[0359] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the UE, that it can approve and / or authenticate the UE as an SE, it may transmit at least one of the identification pieces from paragraphs 31, 33 to 35.

[0360] Furthermore, if the UE receives a response message from the NF containing at least one of the identification information items 31 to 35, it may store the contents of the received identification information. The UE may also perform actions based on the received control message and / or identification information.

[0361] For example, upon receiving a control message, the UE may cancel the procedure, set the 5GS update status to 5U2 or 5U3, delete all 5G-GUTIs, delete the last visited registered TAI, delete the equivalent PLMN list, or, if performing a registration procedure for the current PLMN, not set the 12th identification information in the registration request message, nor include the 12th identification information.

[0362] Furthermore, the UE that receives the 31st identification information may remember and / or recognize whether the SE's authorization and / or authentication was successful, unsuccessful, or failed.

[0363] Furthermore, the UE that received the 32nd identification information may remember and / or recognize that the SE's authorization and / or authentication was unsuccessful or failed.

[0364] Furthermore, a UE that receives the 33rd identification information may store and / or recognize the identifier of the SE and / or the identifier of the SG. If the UE receives the 33rd identification information which differs from the content of the 12th identification information, it may overwrite the stored 12th identification information with the identifier of the SE indicated by the 33rd identification information.

[0365] Furthermore, the UE that receives the 34th identification information may store and / or recognize the ID indicated by the 34th identification information.

[0366] Furthermore, the UE that receives the 35th identification information may store and / or recognize, based on its contents, whether the NW supports a sensing mode or type.

[0367] Although this third procedure was described as a procedure initiated by the UE, this procedure may also be initiated based on the receipt of a trigger (S800) from an NF other than the UE (including NFs different from the decision-making body in S804).

[0368] Furthermore, each step from S800 to S806 may be sent and received as control messages in a layer different from the NAS layer. For example, these control messages may be control messages in a sensing layer specifically designed for sensing purposes and / or for exchanging control information related to sensing.

[0369] Next, we will explain the procedures that take place between the base station and the NF.

[0370] The base station may send a request message to the NF containing at least one of the identification information from 1 to 4 and 8 to 21 (S802). This NF may be an NF specifically prepared for the approval and / or authentication of SEs, an NF prepared for the approval and / or authentication of SEs and sensing services, an NEF, an UDM, an NWDAF, or any other existing NF.

[0371] Furthermore, the base station may select and decide whether or not to transmit any of the identification information 1 to 4 and 8 to 21 based on the base station's capability information, and / or the base station's policy, and / or the base station's status, and / or the base station's registration information, and / or the context held by the base station, and / or the identification information transmitted or received in procedures performed prior to this procedure. In addition, the base station may transmit at least one of the identification information 1 to 4 and 8 to 21 based on instructions from a higher or lower layer.

[0372] For example, when a base station supports sensing functionality, it may transmit at least one of the identification information items 1 through 4 and 8 through 21. Conversely, when a base station does not support sensing functionality, it does not have to transmit at least one of the identification information items 1 through 4 and 8 through 21, nor does it have to perform this procedure.

[0373] Furthermore, if the base station supports all sensing functions, it may transmit a first identification information indicating that it supports all sensing modes or types. Furthermore, if the base station does not support all sensing functions, it may transmit a first identification information indicating that it does not support all sensing modes or types.

[0374] Furthermore, if the base station supports base station-based sensing, it may transmit a second identification information indicating that it supports base station-based sensing. Furthermore, if the base station does not support base station-based sensing, it may transmit a second identification information indicating that it does not support base station-based sensing.

[0375] Furthermore, if the base station supports base station monostatic, it may transmit a third identification information indicating that it supports base station monostatic. Also, if the base station does not support base station monostatic, it may transmit a third identification information indicating that it does not support base station monostatic.

[0376] Furthermore, if the base station supports base station bistatic operation, it may transmit a fourth identification information indicating that it supports base station bistatic operation. Furthermore, if the base station does not support base station bistatic operation, it may transmit a fourth identification information indicating that it does not support base station bistatic operation.

[0377] Furthermore, if the base station supports UE-base station cooperative sensing, it may transmit an eighth identification information indicating that it supports UE-base station cooperative sensing. Furthermore, if the base station does not support UE-base station cooperative sensing, it may transmit an eighth identification information indicating that it does not support UE-base station cooperative sensing.

[0378] Furthermore, if the base station supports UE-base station bistatics, it may transmit a ninth identification information indicating that it supports UE-base station bistatics. Furthermore, if the base station does not support UE-base station bistatics, it may transmit a ninth identification information indicating that it does not support UE-base station bistatics.

[0379] Furthermore, if the base station supports base station-UE bistatic, it may transmit a 10th identification information indicating that it supports base station-UE bistatic. Furthermore, if the base station does not support base station-UE bistatic, it may transmit a 10th identification information indicating that it does not support base station-UE bistatic.

[0380] Furthermore, if the base station supports the functions of transmit and / or ST and / or ST, it may transmit an eleventh identification information indicating that it supports the functions of transmit and / or ST and / or ST. Furthermore, if the base station does not support the functions of transmit and / or ST and / or ST, it may transmit an eleventh identification information indicating that it does not support the functions of transmit and / or ST and / or ST.

[0381] Furthermore, if the base station supports the functions of receiving and / or signal reinforcement (SR), it may transmit an eleventh identification information indicating that it supports the functions of receiving and / or signal reinforcement (SR). Furthermore, if the base station does not support the functions of receiving and / or signal reinforcement (SR), it may transmit an eleventh identification information indicating that it does not support the functions of receiving and / or signal reinforcement (SR).

[0382] Furthermore, if the base station supports the functions of transmit and receive and / or ST or ST, and / or SR or SR, it may transmit an eleventh identification information indicating that it supports the functions of transmit and receive and / or ST or ST, and / or SR or SR. Furthermore, if the base station does not support the functions of transmit and receive and / or ST or ST, and / or SR or SR, it may transmit an eleventh identification information indicating that it does not support the functions of transmit and receive and / or ST or ST, and / or SR or SR.

[0383] Furthermore, the decision of whether or not a base station transmits any of the identification information items 1 through 4 or 8 through 21 to the network is not limited to the above conditions, and may be made based on a combination of the above conditions.

[0384] Next, if the NF receives a request message (S802), it may decide whether or not to approve and / or authenticate the base station as an SE based on the identification information contained in the request message (S804).

[0385] For example, if NF approves and / or certifies a base station as an SE, NF may store that the base station has been certified and / or authenticated as an SE. In this case, NF may store the base station in association with the fact that it has been certified and / or authenticated as an SE, or it may further assign an identifier (ID) shown in the 34th identification information and / or an identifier that identifies the SG shown in the 33rd identification information to that association and store it.

[0386] Furthermore, if the NF does not approve and / or authenticate the base station as an SE (if approval and / or authentication is unsuccessful), it may store that the base station was authenticated and / or not authenticated as an SE. In this case, the NF may store the base station and the fact that it was authenticated and / or not authenticated as an SE in association, or it may further assign an identifier (ID) shown in the 34th identification information to that association and store it.

[0387] Next, the NF may send a response message to the base station that includes at least one of the identification information from 31 to 35 (S806).

[0388] For example, if the NF approves and / or certifies the base station as an SE, it may transmit a 31st identification information indicating that the approval and / or certification of the SE was successful, and / or a 33rd identification information indicating the identifier of the SE or the identifier of the SG, and / or a 34th identification information, and / or a 35th identification information.

[0389] Furthermore, if the NF does not approve and / or authenticate the base station as an SE, it may transmit a 31st identification information indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 32nd identification information indicating a reason value indicating that the approval and / or authentication of the SE was unsuccessful, and / or a 33rd identification information indicating the identifier of the SE or the identifier of the SG, and / or a 35th identification information.

[0390] Furthermore, if the NW supports the sensing mode or type, the NF may transmit a 35th identification piece indicating that it supports the sensing mode or type. Also, if the NW does not support the sensing mode or type, the NF may transmit a 35th identification piece indicating that it does not support the sensing mode or type, and may not transmit any of the 31st to 34th identification pieces.

[0391] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the base station, that it cannot approve and / or authenticate the UE as an SE, it may transmit the 31st and / or 32nd identification pieces.

[0392] Furthermore, if the NF determines, based on the information indicated by one or more identification pieces received from the base station, that it can approve and / or authenticate the UE as an SE, it may transmit at least one of the identification pieces from paragraphs 31, 33 to 35.

[0393] Furthermore, if the base station receives a response message from the NF that includes at least one of the identification information items 31 to 35, it may store the contents of the received identification information. The base station may also take action based on the received control message and / or identification information.

[0394] For example, a base station that receives a control message containing the 32nd identification information may abort this procedure, set the 5GS update status to 5U2 or 5U3, delete all 5G-GUTIs, delete the last visited registered TAI, delete the equivalent PLMN list, or, if performing the registration procedure for the current PLMN, not include the 12th identification information in the registration request message.

[0395] Furthermore, a base station that has received the 31st identification information may remember and / or recognize whether the SE's approval and / or authentication was successful, unsuccessful, or failed.

[0396] Furthermore, the base station that received the 32nd identification information may remember and / or recognize that the SE's approval and / or authentication was unsuccessful or failed.

[0397] Furthermore, a base station that receives the 33rd identification information may store and / or recognize the SE identifier and / or SG identifier. If the base station receives the 33rd identification information which differs from the content of the 12th identification information, it may overwrite the stored 12th identification information with the SE identifier indicated by the 33rd identification information.

[0398] Furthermore, a base station that receives the 34th identification information may store and / or recognize the ID indicated by the 34th identification information.

[0399] Furthermore, a base station that receives the 35th identification information may store and / or recognize, based on its contents, whether the NW supports a sensing mode or type.

[0400] Although this third procedure was described as a procedure initiated by the base station, this procedure may also be initiated based on the receipt of a trigger (S800) from an NF other than the base station (including NFs different from the decision-maker in S804).

[0401] Furthermore, each step from S800 to S806 may be sent and received as control messages in a layer different from the NAS layer. For example, these control messages may be control messages in a sensing layer specifically designed for sensing purposes and / or for exchanging control information related to sensing.

[0402] [3.4. First revocation procedure for revoking approval and / or certification of SE] Next, the first revocation procedure for revoking approval and / or certification of SE will be explained using Figure 9. This first revocation procedure may be a procedure conducted between the UE or base station and the NF. Furthermore, this NF may be the same as or different from the NF that granted approval and / or certification in Chapter 3.1, Chapter 3.2, or Chapter 3.3. In other words, this NF may be an NF specifically prepared for the revocation of approval and / or certification of SE, or it may be the same as the NF prepared for the approval and / or certification of SE, or it may be the same NF prepared for the approval and / or certification of SE and sensing services, or it may be an NEF, or an UDM, or an NWDAF, or it may be another existing NF.

[0403] First, let's explain the procedures that take place between the UE and the NF.

[0404] The NF may decide whether to revoke authorization and / or certification to a UE (also referred to here as SE) (S900). For example, the NF may decide to revoke authorization and / or certification to a UE if authorization and / or certification is revocation, and / or the timer governing the validity period of authorization and / or certification expires, and / or the SE moves, and / or the SE moves out of the sensing area supported by the SF, and / or the SE undergoes a PLMN change (i.e., roaming), and / or the number of sensing measurements exceeds the number requested, and / or the number of sensing results generated exceeds the number requested, and / or the number of sensing results reported exceeds the number requested, and / or the maximum number of SEs that the SF can support exceeds, and / or the QoS request is changed, and / or changed to another SF, and / or communication between the SE and the NF performing authorization and / or certification is interrupted for a period of time, and / or sensing services are not permitted.

[0405] If the NF decides to cancel, it may send a cancellation command message (also called a control message) to the UE that includes at least one of the identification information items 41 to 43 (S902). If the NF does not decide to cancel, it does not need to send a cancellation command message to the UE.

[0406] When the UE receives a cancel command message (S902), it may recognize and store the information indicated by the identification information contained in the cancel command message.

[0407] Furthermore, based on the receipt of the identification information in paragraph 41, the UE may remember and / or recognize that authorization and / or certification has been revoked, or authorization and / or certification of an SE or sensing service has been revoked, or a timer governing the validity period of authorization and / or certification has expired, or an SE has moved, or an SE has moved out of the sensing area supported by the SF, or an SE has made a PLMN change (i.e., roaming), or the number of sensing measurements has exceeded the number requested, or the number of sensing results to be generated has exceeded the number requested, or the number of sensing results to be reported has exceeded the number requested, or the maximum number of SEs that the SF can support has been exceeded, or a QoS request has been changed, or changed to another SF, or communication between the SE and the NF performing authorization and / or certification has been interrupted for a period of time, or the sensing service is not permitted.

[0408] Furthermore, based on the receipt of the identification information in section 42, the UE may recognize the identifier of the SE indicated by the identification information in section 42, and may delete information corresponding to the identifier of the SE indicated by the identification information in section 42 that was stored in the procedures of Chapter 3.1, 3.2, or 3.3 (including sensing configuration information).

[0409] Furthermore, based on the receipt of the 43rd identification information, if the information indicated by the 43rd identification information is the same as the 34th identification information received in the procedure of Chapter 3.1, Chapter 3.2, or Chapter 3.3, the UE may delete the information corresponding to the ID indicated by the 43rd identification information, which was stored in the procedure of Chapter 3.1, Chapter 3.2, or Chapter 3.3 (including sensing configuration information).

[0410] Furthermore, the UE may delete information stored in the procedures of Chapter 3.1, 3.2, or 3.3 (including sensing configuration information) based on the cancel command message and / or the identification information contained in the cancel command message.

[0411] The UE may send a response message (also referred to as a cancellation acceptance message or cancellation confirmation message) to the NF that sent the cancellation command message, which includes at least one of the identification information from 51 to 53 (S904).

[0412] When the NF receives a response message from the UE, it may recognize that the UE has acknowledged that its authorization and / or authentication has been revoked, and / or that the content of the identification information it sent to the UE has been understood. The NF may also delete any sensing control information to the UE that was obtained through the procedures in Chapter 3.1, 3.2, or 3.3.

[0413] Next, we will explain the procedures that take place between the base station and the NF.

[0414] The NF may decide whether to revoke authorization and / or certification to a base station (also referred to here as SE) (S900). For example, the NF may decide to revoke authorization and / or certification to a base station if authorization and / or certification is to be revocation, and / or if the timer governing the validity period of authorization and / or certification expires, and / or if the SE moves, and / or if the SE moves out of the sensing area supported by the SF, and / or if the number of sensing measurements exceeds the number requested, and / or if the number of sensing results generated exceeds the number requested, and / or if the number of sensing results reported exceeds the number requested, and / or if the maximum number of SEs that the SF can support exceeds, and / or if the QoS request is changed, and / or changed to another SF, and / or if communication between the SE and the NF performing authorization and / or certification is interrupted for a period of time, or if sensing services are not permitted.

[0415] If the NF decides to cancel, it may send a cancellation command message (also called a control message) to the base station that includes at least one of the identification information items 41 to 43 (S902). If the NF does not decide to cancel, it does not need to send a cancellation command message to the base station.

[0416] When the base station receives a cancellation command message (S902), it may recognize and store the information indicated by the identification information contained in the cancellation command message.

[0417] Furthermore, based on the receipt of the 41st identification information, the base station may remember and / or recognize that authorization and / or authentication has been revoked, or authorization and / or authentication of an SE or sensing service has been revoked, or a timer managing the validity period of authorization and / or authentication has expired, or an SE has moved, or an SE has moved out of the sensing area supported by the SF, or an SE has made a PLMN change (i.e., roaming), or the number of sensing measurements has exceeded the number requested, or the number of sensing results to be generated has exceeded the number requested, or the number of sensing results to be reported has exceeded the number requested, or the maximum number of SEs that the SF can support has been exceeded, or a QoS request has been changed, or changed to another SF, or communication between the SE and the NF performing authorization and / or authentication has been interrupted for a period of time, or the sensing service is not permitted.

[0418] Furthermore, based on the reception of the identification information in section 42, the base station may recognize the identifier of the SE indicated by the identification information in section 42, and may delete the information corresponding to the identifier of the SE indicated by the identification information in section 42 that was stored in the procedure of Chapter 3.3 (including sensing configuration information).

[0419] Furthermore, based on the reception of the 43rd identification information, if the information indicated by the 43rd identification information is the same as the 34th identification information received in the procedure of Chapter 3.3, the base station may delete the information corresponding to the ID indicated by the 43rd identification information, which was stored in the procedure of Chapter 3.3 (including sensing setting information).

[0420] Furthermore, the base station may delete the information stored in the procedure of Chapter 3.3 (including sensing configuration information) based on the cancellation command message and / or the identification information contained in the cancellation command message.

[0421] The base station may send a response message (also referred to as a cancellation acceptance message or cancellation confirmation message) to the NF that sent the cancellation command message, which includes at least one of the identification information from 51 to 53 (S904).

[0422] When the NF receives a response message from the base station, it may recognize that the base station has acknowledged that its authorization and / or authentication has been revoked, and / or that the content of the identification information it sent to the base station has been understood. The NF may also delete the sensing control information to the base station that was performed using the procedures in Chapter 3.3.

[0423] [3.5. Second revocation procedure for revoking approval and / or certification for SE] Next, the second revocation procedure for revoking approval and / or certification for SE will be explained using Figure 10. This second revocation procedure may be a procedure conducted between the UE and the NF via the AMF. Furthermore, this NF may be the same as or different from the NF that granted approval and / or certification in Chapter 3.1, 3.2, or 3.3. In other words, this NF may be an NF specifically prepared for revoking approval and / or certification for SE, or it may be the same as the NF prepared for the approval and / or certification of SE, or it may be the same NF prepared for the approval and / or certification of SE and sensing services, or it may be an NEF, or an UDM, or an NWDAF, or it may be another existing NF.

[0424] First, let's explain the procedures that take place between the UE and the NF.

[0425] The NF may decide whether to revoke authorization and / or certification to a UE (also referred to here as SE) (S1000). For example, the NF may decide to revoke authorization and / or certification to a UE if authorization and / or certification is revocation, and / or the timer governing the validity period of authorization and / or certification expires, and / or the SE moves, and / or the SE moves out of the sensing area supported by the SF, and / or the SE undergoes a PLMN change (i.e., roaming), and / or the number of sensing measurements exceeds the number requested, and / or the number of sensing results generated exceeds the number requested, and / or the number of sensing results reported exceeds the number requested, and / or the maximum number of SEs that the SF can support exceeds, and / or the QoS request is changed, and / or changed to another SF, and / or communication between the SE and the NF performing authorization and / or certification is interrupted for a period of time, and / or sensing services are not permitted.

[0426] If the NF decides to cancel, it may send a cancellation command message (also called a control message) to the AMF that includes at least one of the identification information items 41 to 43 (S902). If the NF does not decide to cancel, it does not need to send a cancellation command message to the AMF.

[0427] When AMF receives a cancel command message, it may recognize and store the information indicated by the identification information contained in the cancel command message.

[0428] The AMF may send a response message (also referred to as a cancellation acceptance message or cancellation confirmation message) to the NF that sent the cancellation command message, which includes at least one of the identification information from 51 to 53 (S1008).

[0429] Upon receiving a response message from the AMF, the NF may recognize that the UE has acknowledged that its authorization and / or authentication has been revoked, and / or that the content of the identification information it sent to the UE has been understood. The NF may also delete the sensing control information for the UE(SE) that was performed using the procedures in Chapter 3.1, 3.2, or 3.3.

[0430] Furthermore, the response message (S1008) sent from AMF to NF may be sent after sending a non-registration request message to UE (S1004) and receiving a non-registration acceptance message from UE (S1006).

[0431] Then, based on the receipt of a cancellation command message (S1002) or the transmission of a response message (S1008), the AMF may initiate the non-registration procedure.

[0432] AMF may send a non-registration request message to UE containing at least one of the identification information from 41 to 43 (S1004).

[0433] When the UE receives a non-registration request message, it may recognize and store the information indicated by the identification information contained in the non-registration request message.

[0434] Furthermore, the UE may delete information stored in the procedures of Chapter 3.1, 3.2, or 3.3 (including sensing configuration information) based on the cancel command message and / or the identification information contained in the cancel command message.

[0435] The UE may send the AMF an unregistered acceptance message containing at least one of the identification information from 51 to 53 (S1006).

[0436] When the AMF receives a non-registration acceptance message from the UE, it may recognize that the UE has acknowledged that its authorization and / or authentication has been revoked, and / or that the content of the identification information it sent to the UE has been understood. The AMF may also delete any control information it has stored regarding sensing to the UE, if such control information was stored in accordance with the procedures in Chapter 3.1, 3.2, or 3.3.

[0437] Furthermore, as described above, AMF may send a response message to NF after receiving an unregistered acceptance message from UE (S1008).

[0438] Upon receiving a response message from the AMF, the NF may recognize that the UE has acknowledged that its authorization and / or authentication has been revoked, and / or that the content of the identification information it sent to the UE has been understood. The NF may also delete the sensing control information for the UE(SE) that was performed using the procedures in Chapter 3.1, 3.2, or 3.3.

[0439] Next, we will explain the procedures that take place between the base station and the NF, using Figure 10.

[0440] The NF may decide whether to revoke authorization and / or certification to a base station (also referred to here as SE) (S1000). For example, the NF may decide to revoke authorization and / or certification to a base station if authorization and / or certification is to be revocation, and / or if the timer governing the validity period of authorization and / or certification expires, and / or if the SE moves, and / or if the SE moves out of the sensing area supported by the SF, and / or if the number of sensing measurements exceeds the number requested, and / or if the number of times sensing results are generated exceeds the number requested, and / or if the number of times sensing results are reported exceeds the number requested, and / or if the maximum number of SEs that the SF can support exceeds, and / or if the QoS request is changed, and / or changed to another SF, and / or if communication between the SE and the NF performing authorization and / or certification is interrupted for a certain period of time, and / or if sensing services are not permitted.

[0441] If the NF decides to cancel, it may send a cancellation command message (also called a control message) to the AMF that includes at least one of the identification information items 41 to 43 (S902). If the NF does not decide to cancel, it does not need to send a cancellation command message to the AMF.

[0442] When receiving the cancellation command message, the AMF may recognize and store the content indicated by the identification information included in the cancellation command message.

[0443] The AMF may transmit a response message (also referred to as a cancellation accept message or a cancellation confirmation message) including at least one of the 51st to 53rd pieces of identification information to the NF that has transmitted the cancellation command message (S1008).

[0444] Upon receiving the response message from the AMF, the NF may recognize that the base station has recognized that the approval and / or authentication has been canceled, and / or that the content of the identification information transmitted to the base station has been understood. Further, the NF may delete the control information related to sensing for the base station (SE), which was performed in the procedure of Chapter 3.1, Chapter 3.2, or Chapter 3.3.

[0445] Note that the response message (S1008) transmitted from the AMF to the NF may be transmitted after transmitting an N2 message (also referred to herein as a first control message) to the base station (not shown) and receiving an N2 message (also referred to herein as a second control message) from the base station (not shown).

[0446] Then, the AMF may start transmission and reception of N2 messages with the base station, based on the reception of the cancellation command message (S1002) or the transmission of the response message (S1008).

[0447] The AMF may transmit a first control message including at least one of the 41st to 43rd pieces of identification information to the base station (not shown).

[0448] When receiving the first control message, the base station may recognize and store the content indicated by the identification information included in the first control message.

[0449] Further, the base station may delete the information (including setting information related to sensing) stored in the procedure of Chapter 3.1, Chapter 3.2, or Chapter 3.3, based on the first control message and / or the identification information included in the first control message.

[0450] The base station may transmit a second control message including at least one of the 51st to 53rd pieces of identification information to the AMF (not shown).

[0451] Upon receiving the second control message from the base station, the AMF may recognize that the base station has recognized that authorization and / or authentication have been revoked, and / or that the content of the identification information transmitted to the base station has been understood. Further, when the AMF stores control information related to sensing for the base station, which was performed in the procedure of Chapter 3.1, Chapter 3.2, or Chapter 3.3, the AMF may delete such control information.

[0452] Note that, as described above, the AMF may transmit a response message to the NF after receiving the second control message from the base station (S1008).

[0453] Upon receiving the response message from the AMF, the NF may recognize that the base station has recognized that authorization and / or authentication have been revoked, and / or that the content of the identification information transmitted to the base station has been understood. Further, the NF may delete control information related to sensing for the base station (SE), which was performed in the procedure of Chapter 3.1, Chapter 3.2, or Chapter 3.3.

[0454] [3.6. Revocation Procedure for Revoking Authorization and / or Authentication for Sensing Service] Next, after describing the procedure for authorization and / or authentication for the sensing service, the revocation procedure for revoking authorization and / or authentication for the sensing service will be described with reference to Figure 11.

[0455] [3.6.1 Procedure for Authorization and / or Authentication for Sensing Service] First, the procedure for authorization and / or authentication for the sensing service will be described.

[0456] As a Sensing Service Consumer, the Application Function (AF) may send a first request message to the NF regarding the approval and / or authentication and / or registration of the sensing service in order to obtain the sensing results. This NF may be an NF specifically prepared for the approval and / or authentication of the sensing service, an NF prepared for the approval and / or authentication of the SE and the sensing service, an NEF, an UDM, an NWDAF, or any other existing NF.

[0457] The first request message may include the type of sensing service and related information. The type of sensing service may also be referred to as the mode or type of sensing. Furthermore, the type of sensing service may refer to any of the modes or types of sensing, and / or base station-based sensing, and / or base station monostatic, and / or base station bistatic, and / or UE-based sensing, and / or UE monostatic, and / or UE bistatic, and / or UE-base station cooperative sensing, and / or UE-base station bistatic, and / or base station-UE bistatic.

[0458] Next, upon receiving the first request message from the AF, the NF may grant the AF approval and / or authentication regarding the use of the sensing service.

[0459] Next, if the AF is approved and / or authenticated (i.e., the AF is approved and / or authenticated), the NF may discover and select a candidate SF. If the AF is not approved and / or authenticated (i.e., the AF is not approved and / or authenticated), the NF may not discover and select a candidate SF, or may send a control message to the AF containing control information indicating that it was not approved and / or authenticated, and control information indicating the reason for the non-approval and / or authentication, or may terminate the procedure.

[0460] Next, the NF may send a second request message to the discovered and selected SF. Here, the second request message may include the information contained in the first request message.

[0461] Next, upon receiving the second request message, the SF may further authorize and / or certify the use of the sensing service. The SF may authorize and / or certify the AF on behalf of the NF. If authorization and / or certification has been performed by the NF, the SF is not required to authorize and / or certify.

[0462] Furthermore, if approval and / or authentication fails (i.e., approval and / or authentication is not granted), the SF may not have to find and select a candidate SF, or it may send a control message via the NF to the AF containing control information indicating that approval and / or authentication was not granted, and control information indicating the reason for the lack of approval and / or authentication, or it may terminate the procedure.

[0463] Next, if the SF does not approve and / or authenticate, or if the approval and / or authentication is successful, the SF may discover and select candidate SEs. In this case, the SF may discover and select candidate SEs based on the information contained in the second request message and the capabilities supported by the SEs.

[0464] Next, the SF may send a third request message to the discovered and selected SE, which includes control information regarding the sensing measurement.

[0465] Next, upon receiving the third request message, the SE may recognize and / or store the contents of the control information regarding the sensing measurement, and may set the system to perform the measurement according to the control information regarding the sensing measurement.

[0466] Next, the SE may perform sensing measurements and acquire sensing data. Here, the sensing data may be 3GPP sensing data or non-3GPP sensing data.

[0467] Next, the SE may transmit sensing data to the SF.

[0468] Next, when the SF receives sensing data, it may generate the sensing result and send it to the NF.

[0469] Next, when the NF receives the sensing result, it may send the sensing result to the AF.

[0470] Furthermore, the AF should be able to receive the sensing results from the NF.

[0471] Furthermore, SE, and / or SF, and / or NF, and / or AF may store the various control information (including identification information) exchanged in this procedure. Also, SE, and / or SF, and / or NF, and / or AF may store the various control information (including identification information) exchanged in this procedure, each of which has an expiration date, until that expiration date expires. In this case, when the expiration date set for the various control information (including identification information) exchanged in this procedure expires, SE, and / or SF, and / or NF, and / or AF may delete the stored control information whose expiration date has expired. Furthermore, the deletion of stored control information by SE, and / or SF, and / or NF, and / or AF may be considered equivalent to the revocation of the approval and / or certification for the sensing service.

[0472] [3.6.2 Revocation Procedures for Revoke Approval and / or Certification for Sensing Services] Next, we will explain the revocation procedures for revoking approval and / or certification for sensing services.

[0473] This procedure may be initiated by the SE or AF when revoking the certification of an ongoing sensing service.

[0474] [3.6.2.1 Cancellation Procedure Initiated by SE] Next, we will explain the case in which this procedure is initiated by SE (i.e., UE or base station) using Figure 11.

[0475] SE may send a control message containing the 61st identification information to SF (S1100). Here, SE may send the 61st identification information together with the sensing data. Alternatively, SE may send the 61st identification information as part of the sensing data.

[0476] The SF then receives a control message containing sensing data and / or the 61st identification information. If the SF receives sensing data, it may generate the sensing result and send the sensing result along with the 61st identification information to the NF (S1102).

[0477] Next, when the NF receives a control message containing the sensing results and / or the 61st identification information, it may decide whether or not to revoke the authorization and / or authentication for the sensing service (S1104).

[0478] Next, if NF decides to revoke the authorization and / or certification for the sensing service, it may send a control message to AF containing control information indicating that the authorization and / or certification for the sensing service has been revoked (S1106), or it may send a control message to SF containing control information indicating that the authorization and / or certification for the sensing service has been revoked (not shown).

[0479] Upon receiving this control message, the SF may send a control message to the SE containing control information indicating that it has revoked authorization and / or authentication for the sensing service (not shown).

[0480] Furthermore, if SE sends a control message containing the 61st identification information to SF, and / or receives a control message from SF, SE may delete the control information regarding sensing measurement stored in the procedure of Chapter 3.6.1, and may cancel the settings regarding measurement in accordance with the control information regarding sensing measurement.

[0481] [3.6.2.2 Cancellation Procedure Initiated by AF] Next, we will explain the cases in which this procedure is initiated by AF.

[0482] The AF may send a fourth request message including control information indicating revocation of the authorization and / or authentication for the sensing service to the NF, in order to revoke the authorization and / or authentication for the sensing service. This NF may be the same as the NF in section 3.6.1.

[0483] Next, the NF that has received the fourth request message from the AF may determine whether to revoke the authorization and / or authentication for the sensing service.

[0484] Next, when determining to revoke the authorization and / or authentication for the sensing service, the NF may send a control message to the AF including control information indicating that the authorization and / or authentication for the sensing service has been revoked, and control information indicating the reason for revoking the authorization and / or authentication for the sensing service, or may abort this procedure.

[0485] Next, the NF may send a control message including control information indicating that the authorization and / or authentication for the sensing service has been revoked, and control information indicating the reason for revoking the authorization and / or authentication for the sensing service, to the already selected SF according to the procedure in section 3.6.1.

[0486] Next, the SF that has received this control message may send a control message including control information indicating that the authorization and / or authentication for the sensing service has been revoked, and control information indicating the reason for revoking the authorization and / or authentication for the sensing service, to one or more already selected SEs according to the procedure in section 3.6.1.

[0487] Upon receiving this control message, the SE may delete the control information related to sensing measurement stored in the procedure of section 3.6.1, or release the measurement-related configuration according to the control information related to sensing measurement.

[0488] [4. Modifications] A program that operates in a device according to one aspect of the present invention may be a program that controls a Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of the embodiment according to the present invention. The program or the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0489] Furthermore, a program for realizing the functions of an embodiment relating to one aspect of the present invention may be recorded on a computer-readable recording medium. This may also be realized by loading the program recorded on this recording medium into a computer system and executing it. Here, "computer system" refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Also, "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0490] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuit may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of the present invention may also utilize new integrated circuits based on such technologies.

[0491] It should be noted that the present invention is not limited to the embodiments described above. Although one example of a device is described in the embodiments, one aspect of the present invention is not limited thereto and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0492] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, various modifications are possible within the scope of the claims for one aspect of the present invention, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included.

Claims

1. A UE comprising a transmitting / receiving unit, a control unit, and a storage unit, wherein the transmitting / receiving unit receives from a network function an identifier of a sensing entity and a reason value indicating that the authentication of the sensing entity has been revoked, transmits to the network function the identifier of the sensing entity and information indicating that the authentication of the sensing entity has been revoked, and the control unit deletes the sensing-related setting information stored in the storage unit.