User equipment (UE) and access and mobility management function (AMF)

Abstract

It is not clear how to control signal transmission for a UAV that does not support NTZ. In addition, since uplink transmission cannot be performed in the NTZ, it is not clear whether the UAV needs to return a response message to a request message when the UAV receives the request message from the network.SOLUTION: To reject a SM message from a UAV that does not support NTZ, the AMF receives a ULNAS Transport message from the UE and sends a DLNASS Transport message to the UE if the UE is in NTZ. Also, when the UE receives a non-registration request message including a cause value indicating that the UAS service is not allowed by the NTZ, the UE may not transmit a non-registration accept message.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] This embodiment relates to a UE (User Equipment) and an AMF (Access and Mobility Management Function). [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) is studying the system architecture of the 5G System (5GS), a fifth-generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 3). Currently, as part of the study toward the specification of Release 19, new architectures and architecture extensions for communication between UAVs (Uncrewed Aerial Vehicles) and networks or systems, as well as procedures and control information for communication and control, are being considered (see Non-Patent Document 4). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V19.0.0 (2024-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 19) [Non-patent document 2] 3GPP TS 23.502 V19.0.0 (2024-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 19) [Non-patent document 3] 3GPP TS 24.501 V18.7.0 (2024-06); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18) [Non-patent document 4] 3GPP TR 23.700-59 V1.0.0 (2024-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architecture enhancements of UAS, UAV and UAM; Phase 3 (Release 19) Summary of the Invention [Problem to be solved by the invention]

[0004] Currently, 5GS specifies communications between uncrewed aerial vehicles (UAVs) and networks. Release 19 addresses UAV behavior in no-transmit zones (NTZs), geographic areas where UAVs are not permitted to communicate or perform communication-related activities in certain frequency bands.

[0005] However, it is unclear how to control signal transmission for UAVs that do not support NTZ. Also, since uplink transmission is not possible within NTZ, it is unclear whether a UAV needs to return a response message to a request message when it receives one from the network.

[0006] This embodiment has been made in consideration of the above circumstances. This embodiment clarifies how to control signal transmission for UAVs that do not support NTZ. Furthermore, in NTZ, when a UAV receives a request message from a network, it clarifies whether it is necessary to return a response message to the request message. [Means for solving the problem]

[0007] The UE (User Equipment) of this embodiment is a UE having a transceiver unit, and the UE is a UAV (Uncrewed Aerial Vehicle) that supports NTZ (No Transmit Zone), and the transceiver unit receives a non-registration request message including first information from an AMF (Access and Mobility Management Function), and does not send a non-registration acceptance message based on the first information, where the first information is a reason value indicating that UAS service is not allowed by the NTZ.

[0008] The AMF (Access and Mobility Management Function) of this embodiment is an AMF having a transceiver unit and a control unit, wherein the transceiver unit receives a registration request message including first information from a UE, and based on the first information, the control unit recognizes that the UE is a UAV (Uncrewed Aerial Vehicle) that supports NTZ, and the transceiver unit sends a non-registration request message including second information to the UE, and when the second information is sent, the control unit does not start a first timer, wherein the first information is information indicating that the UE supports NTZ, and the second information is a reason value indicating that UAS service is not allowed by NTZ, and the first timer is T3522. [Effects of the Invention]

[0009] This embodiment clarifies how to control signal transmission for UAVs that do not support NTZ, and also clarifies whether a UAV needs to return a response message to a request message when the UAV receives the request message from the network in NTZ. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). [Figure 2] FIG. 1 is a diagram illustrating the detailed configuration of a mobile communication system (EPS / 5GS). [Figure 3] FIG. 1 is a diagram illustrating the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Figure 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 10 is a diagram illustrating a registration procedure. [Figure 7] FIG. 10 is a diagram illustrating a UE-initiated deregistration procedure. [Figure 8] FIG. 1 illustrates a network-initiated deregistration procedure. [Figure 9] A diagram explaining the PDU session establishment procedure. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, the best mode for carrying out the present embodiment will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which the present embodiment is applied will be described.

[0012] [1. System Overview] First, FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1. As shown in FIG.

[0013] FIG. 1 shows that the mobile communication system 1 is composed 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.

[0014] In the following, these devices and functions may be referred to by abbreviating the symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0015] 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 interfaces that connect these devices and functions to each other.

[0016] In the following, these devices and functions may be referred to by abbreviated symbols such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0017] The 4G system EPS (Evolved Packet System) includes an access network _A and a core network _A, but may further include a UE and / or a PDN. The 5G system 5GS (5G System) includes a UE, an access network _B, and a core network _B, but may further include a DN.

[0018] The UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, or 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, or non-3GPP AN). The UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device that can connect to both EPS and 5GS. The UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC).

[0019] Furthermore, access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are deployed in the E-UTRAN. Note that, hereinafter, the eNB 45 may be referred to by abbreviating the symbol eNB. If there are multiple eNBs, the eNBs are connected to each other, for example, via an X2 interface. Furthermore, one or more access points are deployed in the wireless LAN access network.

[0020] Furthermore, access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Note that, hereinafter, the symbol for gNB 122 may be abbreviated, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs and connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in the 4G system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

[0021] Furthermore, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the 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, the trusted non-3GPP access network may be an access network specified by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF).

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

[0023] Furthermore, in the following, access network _A, and / or access network _B, and / or devices included in access network _A, and / or devices included in access network _B may be referred to as access networks or access network devices.

[0024] The core network_A corresponds to an EPC (Evolved Packet Core), which includes, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), and an HSS (Home Subscriber Server).

[0025] Furthermore, the core network_B corresponds to a 5G Core Network (5GCN). In the 5GCN, for example, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc. are arranged. Here, the 5GCN may be expressed as a 5GC.

[0026] In addition, in the following, core network _A and / or core network _B, devices included in core network _A, and / or devices included in core network _B may be referred to as core networks, core network devices, or devices within the core network.

[0027] 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, or 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).

[0028] Also, while FIG. 1 illustrates a case where the PDN and the DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may mean connecting to a communication terminal or a server device located in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal or a server device located in the PDN. The PDN may be referred to as the DN, and the DN may be referred to as the PDN.

[0029] In addition, hereinafter, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device sends or receives a message and / or performs a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein send or receive a message and / or perform a procedure.

[0030] The UE can also connect to an access network. The UE can also connect to a core network via the access network. The UE can also connect to a PDN or DN via the access network and the core network. That is, the UE can transmit and receive (communicate) user data with the PDN or DN. When transmitting and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication can be used.

[0031] Here, IP communication refers to data communication using IP, and data is transmitted and received using IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the IP packet structure. For example, non-IP communication may be data communication achieved by transmitting and receiving application data without an IP header, or it may be user data transmitted and received by a UE with a different header, such as a MAC header or an Ethernet (registered trademark) frame header, added.

[0032] In addition, access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A may be configured with devices not shown in Fig. 2. For example, core network _A and / or core network _B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0033] Here, the AUSF is a core network device having an authentication function for 3GPP access and non-3GPP access, specifically, a network function unit that receives an authentication request for 3GPP access and / or non-3GPP access from a UE and executes the authentication procedure.

[0034] The AAA server is a device that has authentication, authorization, and accounting functions and is connected to the AUSF directly or indirectly via another network device. The AAA server may be a network device within the core network. The AAA server may not be included in the core network _A and / or core network _B, but may be included in the PLMN. In other words, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device within the PLMN managed by a third party.

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

[0036] The UPF_A235 is connected to the DN, the SMF, other UPFs, and the access network. The UPF_A235 may perform functions such as an anchor for intra-RAT mobility or inter-RAT mobility, packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows for one DN, a branching point function that supports multi-homed PDU sessions, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and a trigger function for downlink data notification. The UPF_A235 may also be a relay device that forwards user data as a gateway between the DN and the core network_B190. The UPF_A235 may also be a gateway for IP communication and / or non-IP communication. The UPF_A235 may also have a function for forwarding IP communication and a function for converting non-IP communication to IP communication. Furthermore, multiple gateways may be gateways that connect the core network _B190 to a single DN. Note that UPF_A235 may have connectivity with other NFs and may be connected to each device via other NFs.

[0037] Between UPF_A235 and the access network, UPF_C239 (also called a branching point or uplink classifier), which is a UPF different from UPF_A235, may exist as a device or NF. When UPF_C239 exists, a PDU session between the UE and the DN will be established via the access network, UPF_C239, and UPF_A235.

[0038] Furthermore, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be written with the symbols omitted, such as UPF.

[0039] [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 the drawings. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0040] Note that each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device / function mentioned below is configured with, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Furthermore, each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between devices / functions other than the device / function itself (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Furthermore, each memory unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Furthermore, each memory unit may store this information for each UE. Furthermore, when interworking between 5GS and EPS is performed, each memory unit can store control messages and user data transmitted and received between 5GS and / or devices / functions included in EPS. At this time, not only those transmitted and received via the N26 interface but also those transmitted and received without going through the N26 interface can be stored.

[0041] [2.1. UE Device Configuration] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

[0042] The control unit _A300 is a functional unit that controls the operation and functions of the entire UE.The control unit _A300 realizes various processing in the UE by reading and executing various programs stored in the memory unit _A340 as necessary.

[0043] The transceiver unit _A320 is a functional unit for wireless communication with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can use the transceiver unit _A320 to transmit and receive user data and / or control information between an access network device, and / or a core network device, and / or a PDN, and / or a DN.

[0044] Explaining in detail with reference to Figure 2, the UE can communicate with a base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit _A320. The UE can also communicate with a base station device (gNB) in the 5G AN by using the transceiver unit _A320. The UE can also transmit and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transceiver unit _A320. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN.

[0045] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

[0046] The UE in this embodiment may be a 5G ProSe-enabled UE, a UAV (Uncrewed Aerial Vehicle) or a UAV-C, or an aerial UE.

[0047] [2.2. gNB device configuration] Next, an example of the gNB device configuration will be described using Figure 4. The gNB is composed of a control unit _B500, an antenna 510, a network connection unit _B520, a transceiver unit _B530, and a memory unit _B540. The control unit _B500, the network connection unit _B520, the transceiver unit _B530, and the memory unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510.

[0048] The control unit _B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit _B500 realizes various processes in the gNB by reading and executing various programs stored in the memory unit _B540 as necessary.

[0049] 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 send and receive user data and / or control information between the AMF and / or UPF using the network connection unit _B520.

[0050] The transceiver unit _B530 is a functional unit for wireless 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.

[0051] 2, a gNB in ​​a 5G AN can communicate with an AMF via an N2 interface by using a network connection unit _B 520, and can communicate with a UPF via an N3 interface, and can communicate with a UE by using a transceiver unit _B 530.

[0052] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[0053] [2.3. AMF device configuration] Next, an example of the AMF device configuration will be explained using Figure 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0054] The control unit _B700 is a functional unit that controls the operation and functions of the entire AMF.The control unit _B700 realizes various processing in the AMF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0055] The network connection unit _B720 is a functional unit for the AMF to connect to a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN. In other words, the AMF can use the network connection unit _B720 to send and receive user data and / or control information between a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN.

[0056] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with a gNB via the N2 interface by using the network connection unit _A620, can communicate with a UDM via the N8 interface, can communicate with an SMF via the N11 interface, and can communicate with a PCF via the N15 interface. The AMF can also send and receive NAS messages with a UE via the N1 interface by using the network connection unit _A620. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via a 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with an MME via the N26 interface by using the network connection unit _A620.

[0057] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the AMF.

[0058] 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) functions, connection management (CM) functions, reachability management functions, mobility management functions for UEs, etc., transferring SM (Session Management) messages between the UE and the SMF, access authentication (Access Authorization) functions, security anchor functionality (SEA), security context management (SCM), a function to support the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function to support sending and receiving NAS signals with the UE via the N3IWF, and a function to authenticate UEs connected via the N3IWF.

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

[0060] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context or a PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, 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.

[0061] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which UE_A10's location information is not known to the network, or a state in which UE_A10 is unreachable from the network. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or may establish a 5GMM context by performing the registration procedure.

[0062] In addition, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a 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. In the CM-IDLE state, the UE does not have an N2 interface connection or an N3 interface 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. In the CM-CONNECTED state, the UE may have an N2 interface connection and / or an N3 interface connection.

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

[0064] The CM state may be expressed as a 5GMM mode. In this case, the unconnected state may be expressed as a 5GMM-IDLE mode, and the connected state may be expressed as a 5GMM-CONNECTED mode. Furthermore, the unconnected state in 3GPP access may be expressed as a 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as a 5GMM-CONNECTED mode over 3GPP access. Furthermore, the unconnected state in non-3GPP access may be expressed as 5GMM unconnected mode in non-3GPP access (5GMM-IDLE mode over non-3GPP access), and the connected state in non-3GPP access may be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). Note that the 5GMM unconnected mode may be expressed as idle mode, and the 5GMM connected mode may be expressed as connected mode.

[0065] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). In addition, the AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0066] In addition, the N3IWF is a device and / or function located between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.

[0067] [2.4. SMF device configuration] Next, an example of the SMF device configuration will be explained using Figure 5. The SMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0068] The control unit _B700 is a functional unit that controls the operation and functions of the entire SMF.The control unit _B700 realizes various processing in the SMF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0069] The network connection unit _B720 is a functional unit for the SMF to connect with the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can send and receive user data and / or control information between the AMF, and / or UPF, and / or PCF, and / or UDM using the network connection unit _B720.

[0070] Explaining in more detail with reference to Figure 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface, with the UPF via the N4 interface, with the PCF via the N7 interface, and with the UDM via the N10 interface by using the network connection unit _A620.

[0071] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the SMF.

[0072] The SMF has session management functions such as establishing, modifying, and releasing PDU sessions, IP address allocation for UEs and its management, UPF selection and control, UPF configuration for routing traffic to the appropriate destination, sending and receiving the SM portion of NAS messages, Downlink Data Notification, providing AN-specific (for each AN) SM information to be sent to the AN via the N2 interface via the AMF, determining the SSC mode (Session and Service Continuity mode) for the session, and roaming functions.

[0073] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be explained using Figure 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0074] The control unit _B700 is a functional unit that controls the operation and functions of the entire UPF.The control unit _B700 realizes various processing in the UPF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0075] The network connection unit _B720 is a functional unit for the UPF to connect to a base station device (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit _B720 to transmit and receive user data and / or control information between the base station device (gNB), and / or SMF, and / or DN within the 5G AN.

[0076] Explaining in more detail with reference to Figure 2, a UPF in a 5GCN can communicate with a gNB via the N3 interface, with an SMF via the N4 interface, with a DN via the N6 interface, and with other UPFs via the N9 interface by using the network connection unit _A620.

[0077] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UPF.

[0078] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a gateway between DNs and core network_B that forwards user data), packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows to one 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 notifications.

[0079] The UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have a function for forwarding IP communication and a function for converting non-IP communication and IP communication. Furthermore, multiple gateways may be gateways that connect the core network_B to a single DN. The UPF may also have connectivity with other NFs and may be connected to each device via other NFs.

[0080] The user plane refers to user data transmitted and received between a UE and a network. The user plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, in the case of EPS, the user plane 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. Furthermore, in the case of 5GS, the user plane 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. Hereinafter, the user plane may be referred to as the U-Plane.

[0081] Furthermore, the control plane refers to control messages transmitted and received to control UE communications, etc. The control plane may be transmitted and received using a Non-Access-Stratum (NAS) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be referred to as the control plane or the C-Plane.

[0082] Furthermore, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data and may be composed of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages and may be composed of multiple bearers.

[0083] 2.6. Description of Other Devices and / or Functions Next, other devices and / or functions will be described.

[0084] The network refers to at least a portion of the access network _B, the core network _B, and the DN. Furthermore, one or more devices included in at least a portion of the access network _B, the core network _B, and the DN may be referred to as a network or a network device.

[0085] That is, when a network transmits, receives, and / or processes messages, it may mean that devices in the network (network devices and / or control devices) transmit, receive, and / or process messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0086] The network may refer to a public land mobile network (PLMN) or a non-public network (NPN). The network may also be referred to as a NW.

[0087] A PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator, which is a communications carrier, and the operator can be identified by a PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscription Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may store an Equivalent PLMN list in its USIM to identify one or more Equivalent PLMNs (EPLMNs). A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN).

[0088] A registration area is a set of one or more TAs assigned to a UE by the AMF. Note that while UE_A10 is moving within one or more TAs included in the registration area, it may be able to move without sending or receiving signals for tracking area update. In other words, a registration area may be a group of information indicating areas in which UE_A10 can move without performing a tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0089] A tracking area (TA) is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may be composed of multiple cells. Furthermore, a tracking area may be an area in which control messages such as paging are broadcast, or an area in which UE_A10 can move without performing a handover procedure. Furthermore, a tracking area (also referred to as a TA) may be a routing area, a location area, or anything similar. A tracking area may be identified by a tracking area identity (TAI) consisting of a tracking area code (TAC) and a PLMN.

[0090] A tracking area identity (TAI) may be information that identifies a TA. The TAI may be composed of a mobile country code (MCC), a mobile network code (MNC), and a tracking area code (TAC).

[0091] A TA list is a list that includes one or more TAs assigned by the network to UE_A10. Note that UE_A10 may be able to move without performing a tracking area update procedure while moving within one or more TAs included in the TA list. In other words, UE_A10 may use the TA list as a group of information indicating areas in which UE_A10 can move without performing a tracking area update procedure. Note that the TA list may also be expressed as a TAI list consisting of one or more TAIs (Tracking area identities), and hereinafter, the TAI list may refer to the TA list.

[0092] The SM (Session Management) message may be a NAS message used in the procedure for SM. The SM message may also be referred to as a NAS (Non-Access-Stratum) SM message. The SM message may be a control message transmitted and received between the UE_A10 and the SMF_A230 via the AMF_A240. The SM message may also be referred to as a 5G SM message.

[0093] The MM (Mobility management) message may be a NAS message used in the MM procedure. The MM message may be a control message transmitted and received between the UE_A10 and the AMF_A240. The MM message may also be referred to as a NAS MM message. The MM message may also be referred to as a 5G MM message.

[0094] 5GS (5G System) service may be a connection service provided using core network _B190.

[0095] A non-5GS service may be a service other than a 5GS service.

[0096] A PDU (Protocol Data Unit) session can be defined as an association between a DN providing a PDU connectivity service and a UE, but it may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data to and from a DN by establishing a PDU session via an access network _B and a core network _B. Here, this external gateway may be a UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session. Note that each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with a PDU session. Note that this identification information may include one or more of a DNN, a QoS rule, a PDU session type, an application identification information, an NSI identification information, an access network identification information, and an SSC mode, or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with each PDU session may be the same or different.

[0097] The DNN (Data Network Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN can also be used as information for selecting a gateway such as a PGW / UPF that connects the core network B190.

[0098] An UAV (Uncrewed Aerial Vehicle) may be a flying drone. The UAV may be associated with a UAV controller. Furthermore, the UAV may be associated with the UAV controller and managed by a core network device and / or UTM (UAS Traffic Management). Furthermore, when the UAV is associated with a UAV controller (described later) and managed, it may be managed as a UAS by the core network device and / or UTM. The UAV's own information (identification information, IP address, location information, etc.) may be managed by the core network device and / or UTM. Furthermore, the UAV may be a UE. Note that the UAV may also be referred to as an aerial UE, etc.

[0099] A UAV controller (UAV-C) is a controller for operating a UAV. The UAV controller may be associated with the UAV. Furthermore, the UAV controller may be associated with the UAV and managed by a core network device and / or a UTM. Furthermore, when the UAV controller is associated with the UAV and managed, it may be managed as a UAS by the core network device and / or a UTM. The UAV controller's own information (identification information, IP address, location information, etc.) may be managed by the core network device and / or a UTM. The UAV controller may also be a UE. The UAV controller may be expressed as a UAC or a UAV-C. The UAV-C may also be a UE.

[0100] An Uncrewed Aerial System (UAS) may consist of a UAV and a UAV controller. The UAS may be managed by a core network device and / or a UTM. The UAS may consist of one UAV and one UAV controller.

[0101] Furthermore, a UAS (Uncrewed Aerial System) may be composed of a UAV and related functions. Here, the related functions may include a C2 (command and control) link. Furthermore, the C2 link may be a link between the UAV and a control device, or a link between the UAV and a network. Furthermore, the C2 link may be a link for remote identification.

[0102] A No-Transmit Zone (NTZ) may be a geographical area in which aerial UEs or UAVs are not permitted to communicate and perform communication-related operations in a specific frequency band. Furthermore, an NTZ may be defined at a national level as a geographical area in which aerial UEs or UAVs are not permitted or prohibited from communicating and performing communication-related operations in a specific frequency band based on the need for spectrum operational restrictions. The NTZ and the NTZ-related functions described in this embodiment may be referred to by other names. Furthermore, an NTZ may be a geographical area in which aerial UEs or UAVs are not permitted to communicate and perform communication-related operations in a specific frequency band and / or carrier frequency. The NTZ may be a Restricted Transmission Area (RTA). The NTZ may be mapped to an RTA.

[0103] Additionally, the UE, and / or the network, and / or each device / function of the network may or may not support NTZ. Unless otherwise specified herein, the UE, and / or the network, and / or each device of the network may support NTZ. Details regarding support for NTZ by the UE and / or each device are described in this chapter and subsequent chapters.

[0104] Here, the restriction by the NTZ may be indicated by information about the NTZ (also referred to as NTZ information), which may be information in which information about the region (also referred to as a zone or area) to which the NTZ is applied and information about frequency bands in which communication and communication-related operations are not permitted in the region are associated. In other words, for example, the NTZ information may be information in which the region restricted by the NTZ is associated with one or more frequency bands corresponding to the region. Conversely, for example, the NTZ information may be information in which one or more NTZ-restricted regions are associated with frequency bands in which communication and communication-related operations are not permitted in the NTZ. Note that the area restricted by the NTZ may be one or more entire cells, may be composed of a part of one or more cells, may be an area indicated by a tracking area (TA) or TAI, or may be indicated as a geographical area, but is not limited to these. More specifically, for example, the information about the area restricted by the NTZ may be indicated by a geographical area, a cell ID, a TA, a TAI, an RA, etc.

[0105] Furthermore, for example, when a UE or UAV that supports NTZ enters an NTZ while moving, it may recognize that communication, message transmission, etc. using a specific frequency band included in the corresponding information about the NTZ is prohibited in a specific area included in the information about the NTZ that has been received and stored or pre-stored (preconfigured) by the UE.

[0106] Note that within the NTZ, transmission by a base station device (eNB or gNB) may or may not be prohibited.

[0107] The NTZ may be information indicated by NTZ information. The NTZ information may be information consisting of a list of restricted frequency bands and / or a list of geographical areas. Here, the geographical area may indicate coordinates including longitude, latitude, and altitude restrictions. The NTZ information may also be referred to as NTZ assistance information.

[0108] The 5GMM-DEREGISTERED state is a state of a UE. The 5GMM-DEREGISTERED state may be a non-registered state. The 5GMM-DEREGISTERED state may be a state in which the UE is not registered with the network. The 5GMM-DEREGISTERED state may be 5GMM-DEREGISTERED.NORMAL-SERVICE, 5GMM-DEREGISTERED.LIMITED-SERVICE, 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION, 5GMM-DEREGISTERED.PLMN-SEARCH, 5GMM-DEREGISTERED.NO-SUPI, 5GMM-DEREGISTERED.NO-CELL-AVAILABLE, 5GMM-DEREGISTERED.eCALL-INACTIVE, and / or 5GMM-DEREGISTERED.INITIAL-REGISTRATION-NEEDED.

[0109] When a terminal device is "not served by E-UTRA" and / or "not served by NR", it may mean that the terminal device cannot communicate with the network, or it may mean that the terminal device is only available for communication over PC5.

[0110] Next, when a terminal device is "served by E-UTRA" and / or "served by NR", it may mean that the terminal device can communicate with the network, or that the terminal device can use communication on PC5 and / or communication on Uu.

[0111] Additionally, a terminal device being "not served by E-UTRA" may mean that the terminal device is unable to communicate with a base station or network using E-UTRA technology.

[0112] Additionally, a terminal device being "not served by NR" may mean that the terminal device cannot communicate with a base station or network using NR technology.

[0113] The first timer may be a timer managed by the UE. The first timer may be timer T3580. The first timer may be started using a timer value of the first timer. The first timer may be a timer started when the UE sends a PDU session establishment request message to the SMF. The first timer may be a timer managing retransmission of the PDU session establishment request message. The first timer may be a timer that runs from when the UE sends a PDU session establishment request message to the SMF until it receives a PDU session establishment accept message or a PDU session establishment reject message from the SMF. The first timer may be stopped when the UE receives a PDU session establishment accept message or a PDU session establishment reject message.

[0114] The timer value of the first timer may be 16 seconds, 24 seconds in WB-N1 / CE mode, or 21 seconds for access via a satellite NG-RAN cell.

[0115] The second timer may be a timer managed by the AMF. The second timer may be timer T3522. The second timer may be started using a timer value of the second timer. The second timer may be a timer started when the AMF sends a non-registration request message to the UE. The second timer may be a timer that manages retransmission of the non-registration request message. The second timer may be a timer that runs from when the AMF sends a non-registration request message to the UE until it receives a non-registration accept message from the UE. The second timer may be stopped when the AMF receives the non-registration accept message.

[0116] The timer value of the second timer may be 6 seconds. The timer value of the second timer may be 24 seconds in WB-N1 / CE mode, or 11 seconds for access via a satellite NG-RAN cell. The timer value of the second timer may be greater than 6 seconds, 24 seconds, and / or 11 seconds. The timer value of the second timer may be greater than 6 seconds, 24 seconds, and / or 11 seconds if the UE is a UAV that supports NTZ. The timer value of the second timer may be 24 seconds and / or 11 seconds if the UE is a UAV that supports NTZ.

[0117] The third timer may be a timer managed by the UE. The third timer may be timer T3346. The third timer may be started using a timer value of the third timer. The third timer may be a timer that is started when the UE receives identification information 13 and / or 17. The third timer may be a timer for congestion management. The third timer may be a timer that prevents the UE from communicating with the network while it is running.

[0118] The timer value of the third timer may be provided by the network in an ATTACH REJECT, ROUTING AREA UPDATE REJECT, TRACKING AREA UPDATE REJECT, REGISTRATION REJECT, DE-REGISTRATION REQUEST, or SERVICE REJECT message. The timer value of the third timer may be provided by a lower layer as an "extended wait time" value. The timer value of the third timer may be randomly selected from a default value range of 15 to 30 minutes. The timer value of the third timer may be randomly determined.

[0119] The fourth timer may be a timer managed by the SMF. The fourth timer may be started using a timer value of the fourth timer. The fourth timer may be started when releasing or deactivating user plane resources of the PDU session. The fourth timer may be a timer for managing the release of the PDU session. The fourth timer may be a timer for releasing user plane resources or releasing a deactivated PDU session.

[0120] The timer value of the fourth timer may be a specific value, may be determined by the UE and / or the SMF, or may be determined by the UAS-NF (or UTM, or USS).

[0121] The fifth timer may be a timer managed by the UE. The fifth timer may be started using a timer value of the fifth timer. The fifth timer may be started when releasing or deactivating user plane resources of the PDU session. The fifth timer may be a timer for managing the release of the PDU session. The fifth timer may be a timer for releasing user plane resources or releasing a deactivated PDU session.

[0122] The timer value of the fifth timer may be a specific value. The timer value of the fifth timer may be determined by the UE and / or the SMF. The timer value of the fifth timer may be determined by the UAS-NF (or the UTM, or the USS). The timer value of the fifth timer may be transmitted to the UE from the SMF and / or the UAS-NF.

[0123] The sixth timer may be a timer managed by the UE. The sixth timer may be timer T3510. The sixth timer may be started using a timer value of the sixth timer. The sixth timer may be started when the UE sends a registration request message to the AMF. The sixth timer may be a timer for managing retransmission of the registration request message. The sixth timer may be a timer that runs from when the UE sends a registration request message to the AMF until the UE receives a registration accept message or a registration reject message from the AMF. The sixth timer may be stopped when the UE receives the registration accept message or the registration reject message.

[0124] The timer value of the sixth timer may be 15 seconds, 85 seconds in WB-N1 / CE mode, or 27 seconds for access via a satellite NG-RAN cell.

[0125] The seventh timer may be a timer managed by the UE. The seventh timer may be timer T3521. The seventh timer may be started using a timer value of the seventh timer. The seventh timer may be started when the UE sends a non-registration request message to the AMF. The seventh timer may be a timer for managing retransmission of the non-registration request message. The seventh timer may be a timer that runs from when the UE sends a non-registration request message to the AMF until it receives a non-registration accept message from the AMF. The seventh timer may be stopped when the UE receives a non-registration accept message. The seventh timer may not be started when the UE sends a non-registration request message due to power off.

[0126] The seventh timer may have a timer value of 15 seconds, 45 seconds in WB-N1 / CE mode, or 27 seconds for access via a satellite NG-RAN cell.

[0127] The timer values ​​of the first to seventh timers may be indicated by the seventeenth identification information.

[0128] [2.7. Description of Identification Information in This Embodiment] Next, the identification information transmitted, received, stored, and / or managed by each device in this embodiment will be described.

[0129] The first identification information is capability information of the UE, and may be capability information indicating whether the UE supports NTZ or does not support it.

[0130] In this specification, support of NTZ by a UE is also referred to as NTZ-aware communication by the UE, support of NTZ communication by the UE, support of the NTZ function by the UE, etc.

[0131] Here, when a UE supports NTZ, it may mean that the UE supports sending and receiving information about NTZ, and / or recognizing and / or storing information about NTZ, and / or behaving based on information about NTZ.

[0132] The first identification information may be information included as part of the 5GMM capability, or a 5GMM capability Information Element (IE), or the 5GMM capability.

[0133] The second identification information may be a Request type, a Request type Information Element (IE), or information indicating a type of 5GSM message.

[0134] The second identification information may be a Request type IE set to "initial request."

[0135] The second identification information may be a Request type IE set to "existing PDU session", or "initial emergency request", or "existing emergency PDU session", or "modification request", or "MA PDU request", or "reserved".

[0136] The third identification information is a Payload container. The third identification information may be a Payload container Information Element (IE).

[0137] The third identification information may include the fourth identification information.

[0138] The fourth identification information is a Payload container type. The fourth identification information may be a Payload container type IE (Information Element).

[0139] The fourth identification information may be included in the third identification information.

[0140] The fourth identification information may be set to "N1 SM information."

[0141] The fourth identification information may be set to "SMS", or "LTE Positioning Protocol (LPP) message container", or "SOR transparent container", or "UE policy container", or "UE parameters update transparent container", or "Location services message container", or "CIoT user data container", or "Service-level-AA container", or "Event notification", or "User plane positioning information container", or "Multiple payloads".

[0142] The fifth identification information is a PDU session ID. The fifth identification information may be a PDU session ID IE (Information Element). The fifth identification information may be the PDU session ID of the PDU session to be established.

[0143] The sixth identification information may be information indicating a time from when the UE enters the NTZ to when it leaves the NTZ. The sixth identification information may be a timer value. The sixth identification information may be information indicating a period or time during which the UE is in the NTZ or is expected or assumed to enter the NTZ.

[0144] The sixth identity may be determined based on the NTZ information and / or the UE mobility pattern, and may be determined by the UE, the network, or each network device.

[0145] The sixth identification information may be information transmitted from the UE to the AMF or the SMF. The sixth identification information may be information transmitted from the UAS-NF (or the UTM, or the USS) to the AMF or the SMF.

[0146] The sixth identification information may be an unavailability period duration. The sixth identification information may be unavailability information or an unavailability period duration included in an unavailability configuration.

[0147] The sixth identification information may be unavailability information or an unavailability information information element (IE).

[0148] The sixth identification information may be an unavailability configuration or an unavailability configuration information element (IE).

[0149] The tenth identification information may be information indicating that the 5GSM message was not forwarded. The tenth identification information may be a Payload container IE in which information indicating that the 5GSM message was not forwarded is set. The tenth identification information may be a Payload container IE in which the 5GSM message that was not forwarded is set.

[0150] The tenth identification information may be a Payload container. The tenth identification information may be a Payload container Information Element (IE).

[0151] The tenth identification information may include the eleventh identification information.

[0152] The eleventh identification information is a Payload container type. The eleventh identification information may be a Payload container type IE (Information Element).

[0153] The eleventh identification information may be included in the tenth identification information.

[0154] The eleventh identification information may be set to "N1 SM information."

[0155] The 11th identification information may be set to "SMS", or "LTE Positioning Protocol (LPP) message container", or "SOR transparent container", or "UE policy container", or "UE parameters update transparent container", or "Location services message container", or "CIoT user data container", or "Service-level-AA container", or "Event notification", or "User plane positioning information container", or "Multiple payloads".

[0156] The twelfth identification information is a PDU session ID. The twelfth identification information may be a PDU session ID IE (Information Element). The twelfth identification information may be a PDU session ID of the PDU session to be established.

[0157] The thirteenth identification information is a reason value. The thirteenth identification information may be a reason value indicating congestion. The thirteenth identification information may be a reason value indicating that the network is congested. The thirteenth identification information may be #22 (Congestion).

[0158] The thirteenth identifier may be a reason value indicating that UAS services are not allowed. The thirteenth identifier may be #79 (UAS services not allowed).

[0159] The 13th identification information may be information contained in a 5GMM cause information element (IE).

[0160] The fourteenth identification information is a reason value. The fourteenth identification information may be a reason value indicating that communication is not permitted in the NTZ. The fourteenth identification information may be a reason value indicating that UAS service is not permitted by the NTZ. The fourteenth identification information may be a reason value indicating that UAS service is not permitted using the NTZ. The fourteenth identification information may be a reason value indicating that UAS service is not permitted in the NTZ. The fourteenth identification information may indicate that the NTZ is unavailable. The fourteenth identification information may indicate that operation cannot be performed in the NTZ or that operation is not permitted in the NTZ.

[0161] Furthermore, the fourteenth identification may indicate that operation is not possible or not permitted at the current location, where the current location may refer to the current location of the UE.

[0162] The fourteenth identification information may be indicated by the thirteenth identification information. In other words, the fourteenth identification information may be the same as the thirteenth identification information.

[0163] The 14th identification information may be information contained in a 5GMM cause IE (Information Element).

[0164] The fifteenth identification information is a reason value. The fifteenth identification information may be a reason value indicating that communication is not permitted in the NTZ. The fifteenth identification information may be a reason value indicating that UAS service is not permitted by the NTZ. The fifteenth identification information may be a reason value indicating that UAS service is not permitted using the NTZ. The fifteenth identification information may be a reason value indicating that UAS service is not permitted in the NTZ. The fifteenth identification information may indicate that the NTZ is unavailable. The fifteenth identification information may indicate that operation cannot be performed in the NTZ or that operation is not permitted in the NTZ.

[0165] Furthermore, the fifteenth identification may indicate that operation is not possible or not permitted at the current location, where the current location may refer to the current location of the UE.

[0166] The 15th identification information may be indicated by the 18th identification information. In other words, the 15th identification information may be the same as the 18th identification information.

[0167] The 15th identification information may be information contained in a 5GSM cause information element (IE).

[0168] The sixteenth identification information may be NTZ information. The sixteenth identification information may be information consisting of a list of restricted frequency bands and / or a list of geographical areas, where the geographical area may indicate coordinates including longitude, latitude, and altitude restrictions.

[0169] The sixteenth identification information may be information generated and stored by the network operator and / or each device in the network.

[0170] The 16th identification information may be information preconfigured in the UE, i.e., information that is set and stored in advance. Here, when the UE preconfigured with the 16th identification information does not receive the 16th identification information from the network, the UE may perform communication taking NTZ into consideration based on information indicated by the preconfigured 16th identification information.

[0171] Furthermore, when a UE that has received and stored or preconfigured the 16th identification information further receives a message including new 16th identification information, the UE may replace or add the preconfigured 16th identification information. Furthermore, when the 16th identification information received by the UE is null, the UE may delete the information indicated by the 16th identification information that has already been stored.

[0172] The seventeenth identification information is a timer value. The seventeenth identification information may be a timer value associated with the thirteenth and / or eighteenth identification information. The seventeenth identification information may be a backoff timer value.

[0173] The 17th identification information may be a timer value used together with the 13th identification information. The 17th identification information may be information indicating a time for restricting communication due to network congestion. The 17th identification information may be information indicating a time until the network congestion is resolved. The 17th identification information may be a random value.

[0174] The eighteenth identifier is a reason value. The eighteenth identifier may be a reason value indicating that UAS services are not allowed. The eighteenth identifier may be #86 (UAS services not allowed).

[0175] The 18th identification information may be information contained in a 5GSM cause IE (Information Element).

[0176] The 19th identification information may be information indicating the release or deactivation of user plane resources of the PDU session.

[0177] [3. Description of procedures used in each embodiment] Next, the procedures used in each embodiment will be described.

[0178] In each embodiment, as shown in FIG. 2, the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software). However, the contents described in this embodiment are also applicable to cases where these are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between these devices, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE.

[0179] 3.1. Registration Procedure First, the registration procedure will be explained using Figure 6. The registration procedure is a procedure in 5GS. In this chapter, the registration procedure may be referred to as this procedure.

[0180] This procedure is a procedure for the UE to initiate registration with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with the network, it can execute this procedure at any time, for example, when it is powered on. In other words, if the UE is in the unregistered state (RM-DEREGISTERED state), it can start this procedure at any time.

[0181] The registration procedure initiated by a UE in an unregistered state may be referred to as a registration procedure for initial registration.

[0182] Furthermore, each device (particularly the UE and the AMF) can transition to a registered state (RM-REGISTERED state) based on completion of the registration procedure. Note that the registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or unregistered state) for 3GPP access and the registration state for non-3GPP access.

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

[0184] This procedure may be performed multiple times. In other words, after this procedure is completed, it may be started again.

[0185] Furthermore, the UE that performs this procedure may be a UAV, a UAV that supports NTZ, or a UAV that does not support NTZ.

[0186] The UE may initiate this procedure after performing network selection.

[0187] The UE may initiate this procedure when it performs mobility across TAs (Tracking Areas). In other words, the UE may initiate this procedure when it moves to a TA different from the TA indicated in the TA list it holds.

[0188] Additionally, the UE may initiate this procedure periodically. Additionally, the UE may initiate this procedure based on the completion of a UE Configuration Update procedure.

[0189] However, the UE may perform the registration procedure at any timing, not limited to these.

[0190] Additionally, the UE may periodically initiate a registration procedure even when in a registered state.

[0191] The registration procedure performed based on the mobility of the UE and the registration procedure performed periodically may be referred to as a registration procedure for mobility and periodic registration update. In other words, the registration procedure for mobility and periodic registration update may be a registration procedure performed based on the mobility of the UE or a registration procedure performed periodically.

[0192] Furthermore, the registration procedures for mobility and periodic registration updates may be registration procedures performed based on a configuration update of the UE, or may be registration procedures performed to establish a communication path for transmitting and receiving user data, or may be registration procedures performed based on a request from the network.

[0193] Furthermore, the registration procedures for mobility and periodic registration updates may be registration procedures other than the registration procedure for initial registration.

[0194] The UE may perform this procedure before entering the NTZ. The UE may perform this procedure just before entering the NTZ.

[0195] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be a registration procedure for initial registration, or a registration procedure for mobility and periodic registration update.

[0196] First, the UE starts the registration procedure by transmitting a registration request message to the AMF (S800) (S802) (S804). Specifically, the UE transmits an RRC message including a registration request message to the 5G AN (or gNB) (S800). The registration request message is an NAS message. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0197] Here, the UE may transmit the first and / or sixth identification information by including it in a registration request message and / or an RRC message. More specifically, the UE may transmit the first and / or sixth identification information by including it in a registration request message and / or an RRC message, or may transmit the first and / or sixth identification information by including it in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer).

[0198] In addition, the UE may transmit a registration request message to indicate to the network the contents indicated by each piece of identification information or to indicate the UE's request.

[0199] Furthermore, the UE may transmit each piece of identification information to indicate to the network what each piece of identification information represents.

[0200] Specifically, if the UE supports NTZ, it may transmit first identification information indicating that it supports NTZ. If the UE does not support NTZ, it may transmit first identification information indicating that it does not support NTZ. If the UE does not support NTZ, it does not need to transmit first identification information.

[0201] The UE may transmit the sixth identity to indicate to the AMF the time from when the UE enters the NTZ to when it leaves the NTZ. The UE may calculate and transmit the sixth identity.

[0202] The UE may transmit the sixth identification information before entering the NTZ. The UE may transmit the sixth identification information immediately before entering the NTZ.

[0203] In addition, the UE may decide whether to transmit each identification information based on subscription information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0204] When the UE sends the registration request message, the UE may start a sixth timer, where the sixth timer may be T3510.

[0205] If the sixth timer expires, the UE may resend the registration request message, where if the UE is within the NTZ when the sixth timer expires, the UE may not resend the registration request message.

[0206] When a 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to forward the registration request message (S802). Note that the 5G AN (or gNB) may select an AMF based on information included in the registration request message and / or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S804).

[0207] Next, the AMF receives a registration request message from the UE via the 5G AN (gNB). The AMF may receive the registration request message including the first and / or sixth identification information.

[0208] Furthermore, by receiving a registration request message, the AMF may recognize the contents indicated by each identification information or may recognize the UE's request.

[0209] Furthermore, by receiving each identification information, the AMF may recognize the content indicated by each identification information and may recognize the UE's request.

[0210] Specifically, the AMF may recognize that the UE supports NTZ if it receives first identification information indicating that it supports NTZ. The AMF may recognize that the UE does not support NTZ if it receives first identification information indicating that it does not support NTZ. The AMF may recognize that the UE does not support NTZ if it does not receive the first identification information.

[0211] When the sixth identity is received, the AMF may recognize the time from when the UE enters the NTZ to when it leaves the NTZ. When the sixth identity is received, the AMF may start a timer using the sixth identity. The AMF may not send a registration accept message or a registration reject message until the timer using the sixth identity expires. When the timer using the sixth identity expires, the AMF may send a registration accept message or a registration reject message.

[0212] Furthermore, the AMF may not transmit a registration acceptance message or a registration rejection message using a frequency band restricted by the NTZ until the timer using the sixth identification information expires. In other words, the AMF may transmit a registration acceptance message or a registration rejection message using a frequency band not restricted by the NTZ until the timer using the sixth identification information expires.

[0213] When the AMF receives the registration request message, the AMF may perform a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the UE's request. If the first condition determination is true, the AMF starts the procedure of (A) in Figure 6. If the first condition determination is false, the AMF starts the procedure of (B) in Figure 6.

[0214] Furthermore, the first condition determination may be performed based on the receipt of a 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 the AMF, etc.

[0215] For example, if the network allows the UE's request, the first condition determination may be true. If the network does not allow the UE's request, the first condition determination may be false.

[0216] For example, if the network to which the UE is registered and / or a device within the network supports the function requested by the UE, the first condition determination may be true, and if the network to which the UE is registered and / or a device within the network does not support the function requested by the UE, the first condition determination may be false.

[0217] For example, if each identification is authorized, the first condition determination may be true, and if each identification is not authorized, the first condition determination may be false.

[0218] The conditions for determining whether the first condition determination is true or false do not have to be limited to the above-mentioned conditions.

[0219] First, the case where the first condition is true will be described.

[0220] In the procedure of (A) of Figure 6, as a response message to the registration request message, the AMF sends a registration accept message to the UE via the 5G AN (or gNB) (S806). Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB). Furthermore, the AMF may transmit a registration accept message including the 16th identification information.

[0221] The AMF may indicate that the UE's request has been accepted by sending a registration accept message. The AMF may determine whether to send the registration accept message based on the 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 the AMF, etc.

[0222] Specifically, when sending the 16th identification information, the AMF may indicate updated NTZ information.

[0223] The AMF may send the 16th identity when the UE's NTZ information needs to be updated. The AMF may send the 16th identity when it determines that the UE's NTZ information is outdated. Here, the AMF may receive the 16th identity from the UAS-NF, and / or the UTM, and / or the USS.

[0224] The AMF may send a registration acceptance message including information indicating that some of the UE's requests have been rejected.

[0225] Next, the UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S806). Further, the UE may receive the registration acceptance message including the 16th identification information.

[0226] Here, if the UE receives the registration accept message, it may recognize that the UE's request has been accepted.

[0227] Specifically, when receiving the 16th identification information, the UE may recognize the updated NTZ information.

[0228] When the 16th identification information is received, the UE may store the 16th identification information. When the 16th identification information is received, the UE may delete the stored 16th identification information and store the received 16th identification information.

[0229] Here, the UE does not need to transmit any signal based on the 16th identification information. More specifically, if the UE is within the NTZ indicated by the 16th identification information, the UE does not need to transmit any signal. In other words, the UE does not need to transmit uplink data or perform an MM procedure and / or an SM procedure based on the 16th identification information.

[0230] If the UE receives information indicating that some of the UE's requests have been rejected, the UE may recognize that some of the UE's requests have been rejected.

[0231] Next, the UE may or may not send a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S808). Here, the registration completion message is an NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0232] Next, the AMF may or may not receive a registration completion message via the 5G AN (gNB) (S808).

[0233] Each device may complete the procedure of FIG. 6(A) based on sending and receiving the registration acceptance message and / or the registration completion message.

[0234] Next, a case where the first condition determination is false will be described.

[0235] In the procedure of (B) of Figure 6, as a response message to the registration request message, the AMF sends a registration reject message to the UE via the 5G AN (gNB) (S810). Here, the registration reject message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message transmitted and received between the UE and the 5G AN (gNB). Furthermore, the AMF may send a registration reject message including identification information 13, and / or 14, and / or 16, and / or 17.

[0236] The AMF may indicate that the UE's request has been rejected by sending a registration rejection message. Further, the AMF may send a registration rejection message including information indicating that the UE's request has been rejected.

[0237] Specifically, when sending the 13th identification information, the AMF may indicate that the network is congested. The AMF may send the 13th identification information when it recognizes that the UE does not support NTZ and determines that the UE is in the NTZ.

[0238] Furthermore, the AMF may transmit the 17th identification information together with the 13th identification information.

[0239] When sending the 17th identification information, the AMF may indicate the time during which the UE should not perform an MM procedure and / or an SM procedure.

[0240] When sending the 14th identity, the AMF may indicate that the UAS service is not allowed due to NTZ. The AMF may send the 14th identity if it recognizes that the UE supports NTZ.

[0241] When sending the 16th identification information, the AMF may indicate updated NTZ information.

[0242] The AMF may send the 16th identity when the UE's NTZ information needs to be updated. The AMF may send the 16th identity when it determines that the UE's NTZ information is outdated. Here, the AMF may receive the 16th identity from the UAS-NF, and / or the UTM, and / or the USS.

[0243] Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). When the UE receives the registration rejection message, the UE may recognize that the UE's request has been rejected. Furthermore, the UE may receive the registration rejection message including identification information 13, and / or 14, and / or 16, and / or 17.

[0244] Specifically, when the 13th identification information is received, the UE may recognize that the network is in a congested state.

[0245] If the 13th identity is received, the UE may enter a 5GMM-DEREGISTERED state, where the UE in the 5GMM-DEREGISTERED state may not perform PLMN selection if it is within the NTZ.

[0246] If the 13th identification information is received, the UE does not need to perform PLMN selection.

[0247] Additionally, the UE may receive the 17th identification information along with the 13th identification information.

[0248] When the 17th identification information is received, the UE may know the times when it should not perform MM procedures and / or SM procedures.

[0249] If the UE receives the 13th identification information, the UE may start a third timer using the 17th identification information. If the UE receives the 13th identification information and the third timer is running, the UE may stop the third timer. Here, the third timer may be T3346 or another timer.

[0250] Here, the UE may not perform the MM procedure and / or the SM procedure if the third timer is running.

[0251] If the 14th identification information is received, the UE may recognize that UAS service is not permitted by the NTZ.

[0252] If the 14th identity is received, the UE may enter the 5GMM-DEREGISTERED state. More specifically, if the 14th identity is received, the UE may enter the 5GMM-DEREGISTERED state without sending a deregistration accept message. Here, the UE in the 5GMM-DEREGISTERED state may not perform PLMN selection if it is within the NTZ.

[0253] If the 14th identification information is received, the UE does not need to perform PLMN selection.

[0254] When the 16th identification information is received, the UE may recognize the updated NTZ information.

[0255] When the 16th identification information is received, the UE may store the 16th identification information. When the 16th identification information is received, the UE may delete the stored 16th identification information and store the received 16th identification information.

[0256] Here, the UE does not need to transmit any signal based on the 16th identification information. More specifically, if the UE is within the NTZ indicated by the 16th identification information, the UE does not need to transmit any signal. In other words, the UE does not need to transmit uplink data or perform an MM procedure and / or an SM procedure based on the 16th identification information.

[0257] Each device may complete procedure (B) in this procedure based on sending and receiving the registration rejection message.

[0258] Each device may complete this procedure based on the completion of the procedure in (A) or (B) of FIG.

[0259] Upon completion of the procedure in FIG. 6(A), the UE may transition to a state in which the UE is registered in the network (RM_REGISTERED state).

[0260] Furthermore, based on the completion of the procedure in (B) of Figure 6, the UE may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state), or may transition to a state in which the UE is not registered in the network.

[0261] Upon completion of this procedure, each device may perform processing based on the transmission and reception of each identification information.

[0262] If the UE's request is rejected, the UE may perform this procedure again or may perform network selection for a different network.

[0263] 3.2. Non-Registration Procedures Next, the de-registration procedure will be described. In this chapter, this procedure refers to the de-registration procedure. The de-registration procedure is a procedure initiated by the UE or the network to deregister the UE. In other words, the de-registration procedure may be a UE-initiated de-registration procedure or a network-initiated de-registration procedure. The de-registration procedure may also be a procedure to change the UE state to a de-registered state.

[0264] The UE and the network can execute this procedure at any time as long as the UE is registered with the network. In other words, the UE and the network can start this procedure at any time as long as the UE is registered. Furthermore, each device (especially the UE and the AMF) can transition to the unregistered state based on the completion of the unregistration procedure.

[0265] In addition, prior to this procedure, the registration procedure and / or PDU session establishment procedure may have been performed one or more times.

[0266] This procedure may be performed multiple times.

[0267] Furthermore, a device in the core network, such as the AMF, may initiate this procedure based on an update to the network configuration and / or an update to the operator policy. The trigger for this procedure may be detection of UE mobility, detection of a change in the status of the UE, the access network, and / or the core network, or a change in the status of a network slice. The trigger for this procedure may be reception of a request from the DN and / or an application server of the DN, a change in the network configuration, or a change in the operator policy. The triggers for the device in the core network to initiate this procedure are not limited to these.

[0268] Furthermore, this procedure may be performed at any time when each device has established a 5GMM context and / or when each device is in 5GMM connected mode.

[0269] During this procedure, each device may also send and receive messages containing identification information indicating the reason for the UE deregistration and / or indicating that network reselection is required. Furthermore, each device may delete the UE context or initiate network-directed behavior based on the completion of this procedure.

[0270] The UE may recognize the reason for deregistration based on the control information transmitted and received in this procedure. Furthermore, upon recognizing the reason for deregistration, the UE may delete the UE context or initiate network reselection. In other words, a device in the core network may initiate this procedure and send the control messages and control information of this procedure to the UE, thereby causing the UE to recognize the reason for deregistration. Furthermore, upon recognizing the reason for deregistration, the device in the core network may delete the UE context or initiate network reselection.

[0271] Furthermore, the UE that performs this procedure may be a UAV, a UAV that supports NTZ, or a UAV that does not support NTZ.

[0272] The non-registration procedure is classified into a UE-initiated non-registration procedure and a network-initiated non-registration procedure. The UE-initiated non-registration procedure and the network-initiated non-registration procedure will be described below.

[0273] 3.2.1. UE-initiated de-registration procedure First, the UE-initiated de-registration procedure will be explained using Figure 7. In this chapter, this procedure refers to the UE-initiated de-registration procedure. The UE-initiated de-registration procedure is a de-registration procedure initiated by the UE. Each step of this procedure will be explained below.

[0274] First, the UE starts the deregistration procedure by sending a deregistration request message to the AMF via the 5G AN (or gNB) (S1000).

[0275] The UE may also request deletion of the UE's context by sending a deregistration request message based on the received identification information, and / or subscription information, and / or UE capability information, and / or UE status, and / or user registration information, and / or context held by the UE, etc.

[0276] If the UE sends the unregistered request message, the UE may start a seventh timer, where the seventh timer may be T3521.

[0277] If the seventh timer expires, the UE may resend the non-registration request message, where if the UE is within the NTZ when the seventh timer expires, the UE may not resend the non-registration request message.

[0278] Next, the AMF receives a non-registration request message from the UE via the 5G AN (gNB) (S1000). The AMF may recognize the reason for deregistration of the UE based on the non-registration request message and / or the identification information included in the non-registration request message.

[0279] Furthermore, the AMF may send a deregistration accept message to the UE via the 5G AN (gNB) as a response message to the deregistration request message based on the identification information included in the deregistration request message (S1002).

[0280] Next, the UE may receive a non-registration acceptance message from the AMF via the 5G AN (gNB) (S1002).

[0281] Each device may complete this procedure based on sending and receiving a non-registration request message and / or a non-registration acceptance message.

[0282] Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of this procedure. For example, each device may delete the UE context when it transmits or receives update information for the configuration information.

[0283] Furthermore, if the UE transmits or receives information indicating that a network reselection and / or registration procedure needs to be performed, the UE may initiate the network reselection and / or registration procedure based on the completion of this procedure.

[0284] 3.2.2. Network-Initiated Deregistration Procedures Next, the network-initiated de-registration procedure will be explained using Figure 8. In this chapter, this procedure refers to the network-initiated de-registration procedure. The network-initiated de-registration procedure is a de-registration procedure that is initiated by the network. Each step of this procedure will be explained below.

[0285] First, the AMF initiates the deregistration procedure by sending a deregistration request message to the UE via the 5G AN (or gNB) (S1200).

[0286] The AMF may start a second timer by sending an unregister request message.

[0287] Here, the AMF may transmit a deregistration request message including identification information 13, and / or 14, and / or 16, and / or 17. By transmitting these identification information, the AMF may indicate the reason for deregistration of the UE or may indicate the need for network reselection. Furthermore, two or more of these identification information may be configured as one or more identification information. Furthermore, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

[0288] Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the non-registration request message by including each identification information in the non-registration request message and sending it.

[0289] Specifically, when sending the 13th identity, the AMF may indicate that the network is congested. If the AMF has not received a registration request message including the first identity and determines that the UE is in the NTZ, the AMF may send the 13th identity.

[0290] When transmitting the 13th identity, the AMF may not start the second timer. When transmitting the 13th identity, the AMF may set the second timer to a value longer than 6 seconds. Here, the second timer may be T3522.

[0291] More specifically, if the AMF has not received a registration request message including the first identity and sends the thirteenth identity, the AMF may not start the second timer. If the AMF has not received a registration request message including the first identity and sends the thirteenth identity, the AMF may set the second timer to a value longer than 6 seconds.

[0292] Here, if the AMF does not receive the first identification information, it may recognize that the UE is a UAV that does not support NTZ. Also, if the AMF does not receive the first identification information, it may be interpreted as if the AMF has received first identification information indicating that the UE is a UAV that does not support NTZ.

[0293] The AMF may not start the second timer if it determines that the UE is in the NTZ. The AMF may set the second timer to a value greater than 6 seconds if it determines that the UE is in the NTZ.

[0294] When sending the 13th identity, the AMF may enter the 5GMM-DEREGISTERED state. When sending the 13th identity, based on the sending of a non-registration request message, the AMF may enter the 5GMM-DEREGISTERED state.

[0295] If the AMF determines that the UE is in the NTZ, it may enter the 5GMM-DEREGISTERED state based on sending a non-registration request message. In other words, if the AMF determines that the UE is in the NTZ, it may enter the 5GMM-DEREGISTERED state without receiving a non-registration accept message.

[0296] Here, when the non-registration request message is for 3GPP access, the AMF may enter a 5GMM-DEREGISTERED state for 3GPP access. When the non-registration request message is for non-3GPP access, the AMF may enter a 5GMM-DEREGISTERED state for non-3GPP access.

[0297] When the UE sends the thirteenth identity, the AMF may not resend the non-registration request message even if the second timer expires. More specifically, when the AMF has not received a registration request message including the first identity and sends the thirteenth identity, the AMF may not resend the non-registration request message even if the second timer expires. When the AMF determines that the UE is within the NTZ, the AMF may not resend the non-registration request message even if the second timer expires.

[0298] Furthermore, the AMF may transmit the 17th identification information together with the 13th identification information.

[0299] When sending the 17th identification information, the AMF may indicate the time during which the UE should not perform an MM procedure and / or an SM procedure.

[0300] When sending the 14th identity, the AMF may indicate that the UAS service is not permitted by the NTZ. The AMF may send the 14th identity when it receives a registration request message including the first identity.

[0301] When transmitting the 14th identity, the AMF may not start the second timer. When transmitting the 14th identity, the AMF may set the second timer to a value longer than 6 seconds. Here, the second timer may be T3522.

[0302] More specifically, when receiving a registration request message including the first identity and sending a fourteenth identity, the AMF may not start the second timer. When receiving a registration request message including the first identity and sending a fourteenth identity, the AMF may set the second timer to a value longer than 6 seconds.

[0303] Here, when the AMF receives the first identification information, it may recognize that the UE is a UAV that supports NTZ. In other words, when the AMF receives a registration request message including the first identification information, it may recognize that the UE is a UAV that supports NTZ.

[0304] The AMF may not start the second timer if it determines that the UE is in the NTZ. The AMF may set the second timer to a value greater than 6 seconds if it determines that the UE is in the NTZ.

[0305] When sending the 14th identity, the AMF may enter a 5GMM-DEREGISTERED state. When sending the 14th identity, based on the sending of a non-registration request message, the AMF may enter a 5GMM-DEREGISTERED state.

[0306] If the AMF determines that the UE is in the NTZ, it may enter the 5GMM-DEREGISTERED state based on sending a non-registration request message. In other words, if the AMF determines that the UE is in the NTZ, it may enter the 5GMM-DEREGISTERED state without receiving a non-registration accept message.

[0307] Here, when the non-registration request message is for 3GPP access, the AMF may enter a 5GMM-DEREGISTERED state for 3GPP access. When the non-registration request message is for non-3GPP access, the AMF may enter a 5GMM-DEREGISTERED state for non-3GPP access.

[0308] When transmitting the fourteenth identity, the AMF may not resend the non-registration request message even if the second timer expires. More specifically, when receiving a registration request message including the first identity and transmitting the fourteenth identity, the AMF may not resend the non-registration request message even if the second timer expires. When the AMF determines that the UE is within the NTZ, the AMF may not resend the non-registration request message even if the second timer expires.

[0309] When sending the 16th identification information, the AMF may indicate updated NTZ information.

[0310] The AMF may send the 16th identity when the UE's NTZ information needs to be updated. The AMF may send the 16th identity when it determines that the UE's NTZ information is outdated. Here, the AMF may receive the 16th identity from the UAS-NF, and / or the UTM, and / or the USS.

[0311] Furthermore, the AMF may select and decide whether to include each identification information in the non-registration request 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 the AMF, etc.

[0312] The AMF may also request deletion of the UE's context by sending a deregistration request message based on the 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 the AMF, etc.

[0313] Next, the UE receives a deregistration request message from the AMF via the 5G AN (gNB) (S1200). Here, the UE may receive the deregistration request message including the 13th, and / or 14th, and / or 16th, and / or 17th identification information. The UE may recognize the reason for deregistration of the UE and may perform network reselection based on the deregistration request message and / or the identification information included in the deregistration request message.

[0314] Specifically, when the 13th identification information is received, the UE may recognize that the network is in a congested state.

[0315] When the 13th identification information is received, the UE does not need to send a non-registration acceptance message. More specifically, when the UE is a UAV that supports NTZ and when the 13th identification information is received, the UE does not need to send a non-registration acceptance message. In other words, when the UE sends the first identification information in the registration procedure and when the 13th identification information is received, the UE does not need to send a non-registration acceptance message.

[0316] Here, a UE that supports NTZ may be able to recognize whether it is within the NTZ.

[0317] If the 13th identification information is received, and the UE is a UAV that supports NTZ, and the UE is within the NTZ, the UE does not need to send a non-registration acceptance message. Also, if the 13th identification information is received, and the UE is a UAV that supports NTZ, and the UE is outside the NTZ, the UE may send a non-registration acceptance message.

[0318] If the 13th identity is received, the UE may enter the 5GMM-DEREGISTERED state. More specifically, if the 13th identity is received, the UE may enter the 5GMM-DEREGISTERED state without sending a deregistration accept message. Here, the UE in the 5GMM-DEREGISTERED state may not perform PLMN selection if it is within the NTZ.

[0319] If the 13th identification information is received, the UE does not need to perform PLMN selection.

[0320] Additionally, the UE may receive the 17th identification information along with the 13th identification information.

[0321] When the 17th identification information is received, the UE may know the times when it should not perform MM procedures and / or SM procedures.

[0322] If the UE receives the 13th identification information, the UE may start a third timer using the 17th identification information. If the UE receives the 13th identification information and the third timer is running, the UE may stop the third timer. Here, the third timer may be T3346 or another timer.

[0323] Here, the UE may not perform the MM procedure and / or the SM procedure if the third timer is running.

[0324] If the 14th identification information is received, the UE may recognize that UAS service is not permitted by the NTZ.

[0325] When the UE receives the 14th identification information, the UE does not need to send a non-registration acceptance message. More specifically, when the UE is a UAV that supports NTZ and receives the 14th identification information, the UE does not need to send a non-registration acceptance message. In other words, when the UE sends the first identification information in the registration procedure and receives the 14th identification information, the UE does not need to send a non-registration acceptance message.

[0326] Here, a UE that supports NTZ may be able to recognize whether it is within the NTZ.

[0327] If the 14th identification information is received, and the UE is a UAV that supports NTZ, and the UE is within the NTZ, the UE does not need to send a non-registration acceptance message. Also, if the 14th identification information is received, and the UE is a UAV that supports NTZ, and the UE is outside the NTZ, the UE may send a non-registration acceptance message.

[0328] If the 14th identity is received, the UE may enter the 5GMM-DEREGISTERED state. More specifically, if the 14th identity is received, the UE may enter the 5GMM-DEREGISTERED state without sending a deregistration accept message. Here, the UE in the 5GMM-DEREGISTERED state may not perform PLMN selection if it is within the NTZ.

[0329] If the 14th identification information is received, the UE does not need to perform PLMN selection.

[0330] When the 16th identification information is received, the UE may recognize the updated NTZ information.

[0331] When the 16th identification information is received, the UE may store the 16th identification information. When the 16th identification information is received, the UE may delete the stored 16th identification information and store the received 16th identification information.

[0332] Here, the UE does not need to transmit any signal based on the 16th identification information. More specifically, if the UE is within the NTZ indicated by the 16th identification information, the UE does not need to transmit any signal. In other words, the UE does not need to transmit uplink data or perform an MM procedure and / or an SM procedure based on the 16th identification information.

[0333] Furthermore, the UE may send a deregistration accept message to the AMF via the 5G AN (gNB) as a response message to the deregistration request message based on the identification information included in the deregistration request message (S1202).

[0334] Next, the AMF may receive a non-registration acceptance message via the 5G AN (gNB) (S1202). In addition, each device completes this procedure based on the transmission and reception of the non-registration request message and / or the non-registration acceptance message.

[0335] The AMF may stop the second timer if it receives a non-registration accept message. The AMF may enter a 5GMM-DEREGISTERED state if it receives a non-registration accept message. The AMF may enter a 5GMM-DEREGISTERED state for 3GPP access if it receives a non-registration accept message when the non-registration request message was for 3GPP access. The AMF may enter a 5GMM-DEREGISTERED state for non-3GPP access if it receives a non-registration accept message when the non-registration request message was for non-3GPP access.

[0336] Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of this procedure. For example, each device may delete the UE context when it transmits or receives update information for the configuration information.

[0337] Furthermore, if the UE transmits or receives information indicating that a network reselection and / or registration procedure needs to be performed, the UE may initiate the network reselection and / or registration procedure based on the completion of this procedure.

[0338] In the above procedure, by sending and receiving a non-registration request message, a device in the core network can instruct the UE to delete configuration information already applied by the UE, or to stop or change functions currently being executed by the UE.

[0339] [3.3. PDU Session Establishment Procedure] Next, the PDU session establishment procedure will be described with reference to Fig. 9. Hereinafter, the PDU session establishment procedure may be referred to as this procedure. The PDU session establishment procedure may also be an SM procedure.

[0340] Note that the registration procedure may have been performed one or more times prior to this procedure.

[0341] This procedure may be performed multiple times. In other words, after the PDU session establishment procedure is completed once, the PDU session establishment procedure may be performed again.

[0342] Furthermore, the UE that performs this procedure may be a UAV, a UAV that supports NTZ, or a UAV that does not support NTZ.

[0343] Next, each step of the PDU session establishment procedure is described.

[0344] First, the UE sends a PDU session establishment request message to the SMF (S1400) (S1402) (S1404) to start the PDU session establishment procedure.

[0345] Specifically, the UE initiates the PDU session establishment procedure by sending an uplink NAS transport (UL NAS TRANSPORT) message including a PDU session establishment request message to the AMF via the access network (S1400). The PDU session establishment request message may be included in an N1 SM container.

[0346] Here, the UE may transmit the second and / or third and / or fourth and / or fifth identification information in the PDU session establishment request message and / or the UL NAS transport message, or may transmit the second and / or third and / or fourth and / or fifth identification information together with the PDU session establishment request message and / or the UL NAS transport message.

[0347] Specifically, the UE may indicate the type of the 5GSM message by transmitting the second identification information. The UE may indicate that the Request type is "initial request" by transmitting the second identification information.

[0348] In addition, the UE may indicate that the Request type is "existing PDU session", or "initial emergency request", or "existing emergency PDU session", or "modification request", or "MA PDU request", or "reserved" by sending the second identification information.

[0349] When the UE sends a PDU session establishment request message, the UE may set the third identity to the 5GSM message. When the UE sends a 5GSM message, the UE may set the third identity to the 5GSM message.

[0350] The UE may set the fourth identification information to "N1 SM information" when sending a PDU session establishment request message, and may set the fourth identification information to "N1 SM information" when sending a 5GSM message.

[0351] By transmitting these pieces of identification information, the UE may indicate that the UE supports each function, or may indicate a request from the UE. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0352] In addition, the UE may indicate that it supports each function or indicate its request by sending a PDU session establishment request message and / or a UL NAS transport message.

[0353] In addition, the UE may select and decide whether to transmit each identification information based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0354] The UE may send a PDU session establishment request message and / or a UL NAS transport message and start a first timer, which may be timer T3580.

[0355] Next, when the AMF receives the UL NAS transport message, it may recognize what the UE is requesting and / or the contents of the information, etc. (message, container, information) contained in the UL NAS transport message.

[0356] Here, (C) of FIG. 9 will be explained.

[0357] The AMF may send a downlink NAS transport (DL NAS TRANSPORT) message to the UE via the access network (S1424) (S1426).

[0358] Here, the AMF may send a DL NAS transport message including identification information numbered 10, and / or 11, and / or 12, and / or 13, and / or 14, and / or 16, and / or 17 to the UE via the access network. The AMF may also send a DL NAS transport message together with identification information numbered 10, and / or 11, and / or 12, and / or 13, and / or 14, and / or 16, and / or 17 to the UE via the access network.

[0359] Furthermore, the AMF may transmit the 17th identification information together with the 13th identification information.

[0360] Specifically, if the AMF determines not to forward the 5GSM message to the SMF, it may send tenth identification information to the UE. If the AMF determines not to forward the 5GSM message to the SMF, it may not perform SMF selection (S1402).

[0361] If the AMF determines that the UE is in the NTZ, it may send identifications 10, 13, and / or 17. If the AMF recognizes that the UE does not support NTZ and determines that the UE is in the NTZ, it may send identifications 10, 13, and / or 17.

[0362] Here, the AMF may recognize that the UE does not support NTZ if it receives a registration request message that does not include first identification information. The AMF may recognize that the UE does not support NTZ if it receives a registration request message that includes first identification information that indicates that the UE does not support NTZ.

[0363] Here, recognizing that the UE does not support NTZ can be read as recognizing that the UE is a UAV that does not support NTZ.

[0364] The AMF may prevent the UE from transmitting signals within the NTZ by transmitting identification information numbered 10, and / or 13, and / or 17.

[0365] If the AMF determines that the UE is within the NTZ, it may transmit identification information numbered 10, and / or 11, and / or 12, and / or 13, and / or 14, and / or 16, and / or 17. In other words, if the AMF transmits identification information numbered 10 because the UE is within the NTZ, it may transmit identification information numbered 10, and / or 11, and / or 12, and / or 13, and / or 14, and / or 16, and / or 17.

[0366] Next, the UE may receive a DL NAS transport message from the AMF (S1424) (S1426). Here, the UE may receive a DL NAS transport message including identification information of 10th, and / or 11th, and / or 12th, and / or 13th, and / or 14th, and / or 16th, and / or 17th from the AMF. The UE may also receive a DL NAS transport message together with identification information of 10th, and / or 11th, and / or 12th, and / or 13th, and / or 14th, and / or 16th, and / or 17th from the AMF.

[0367] Additionally, the UE may receive the 17th identification information along with the 13th identification information.

[0368] When the UE receives the DL NAS transport message, it may recognize that the UE's request has been accepted and / or the contents of the information, etc. (message, container, information) included in the DL NAS transport message.

[0369] Specifically, when the UE receives the 13th identification information, it may pass, to the 5GSM sublayer, information indicating that the 5GSM message was not forwarded, or may pass the received 17th identification information. When the UE receives the 13th identification information, it may pass, to the 5GSM sublayer, information indicating that the 5GSM message was not forwarded due to DNN-based congestion control, or may pass the received 17th identification information. When the UE receives the 13th identification information, it may pass, to the 5GSM sublayer, information indicating that the 5GSM message was not forwarded due to S-NSSAI and DNN-based congestion control, or may pass the received 17th identification information. When the UE receives the 13th identification information, it may pass, to the 5GSM sublayer, information indicating that the 5GSM message was not forwarded due to S-NSSAI-only-based congestion control, or may pass the received 17th identification information.

[0370] If the UE receives the 13th identification information, it may stop the first timer and abort the PDU session establishment procedure.

[0371] When the UE receives information from the 5GSM sublayer indicating that a 5GSM message was not forwarded, the UE may stop the first timer and abort the PDU session establishment procedure. When the UE receives information from the 5GSM sublayer indicating that a 5GSM message was not forwarded due to DNN-based congestion control, the UE may stop the first timer and abort the PDU session establishment procedure. When the UE receives information from the 5GSM sublayer indicating that a 5GSM message was not forwarded due to S-NSSAI and DNN-based congestion control, the UE may stop the first timer and abort the PDU session establishment procedure. When the UE receives information from the 5GSM sublayer indicating that a 5GSM message was not forwarded due to S-NSSAI-only based congestion control, the UE may stop the first timer and abort the PDU session establishment procedure.

[0372] When the UE receives the seventeenth identification information from the 5GSM sublayer, the UE may start a third timer using the seventeenth identification information. If the third timer is running, the UE may stop the third timer. The third timer may be T3346 or another timer.

[0373] Here, the UE may not perform the MM procedure and / or the SM procedure if the third timer is running.

[0374] 9C is executed, the process from (S1402) onward in this procedure does not need to be executed. In other words, this procedure may be stopped after (C) in FIG.

[0375] Next, the procedure when (C) in FIG. 9 is not executed will be described.

[0376] The AMF selects an SMF as a transfer destination of information, etc. (message, container, information) included in the UL NAS transport message received from the UE (S1402). Note that the AMF may select an SMF based on information, etc. (message, container, information) included in the UL NAS transport message, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0377] Next, the AMF transmits to the SMF information (message, container, information) contained in the UL NAS transport message received from the UE (S1404). The AMF may transmit an Nsmf_PDUSession_CreateSMContext Request message to the SMF.

[0378] Next, when the SMF receives information etc. (message, container, information) sent from the AMF (S1404), it may recognize what the UE is requesting and / or the contents of the information etc. (message, container, information) sent from the AMF. When the SMF receives an Nsmf_PDUSession_CreateSMContext Request message from the AMF, it may recognize what the UE is requesting and / or the contents of the information etc. (message, container, information) sent from the AMF.

[0379] Here, the SMF may perform a second condition determination. The second condition determination may be for determining whether the network accepts the UE request. If the SMF determines that the second condition determination is true, it may start the procedure of (A) in Figure 9, and if the SMF determines that the second condition determination is false, it may start the procedure of (B) in Figure 9.

[0380] Furthermore, the second condition determination may be performed based on information received from the AMF (message, container, information), and / or subscription information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

[0381] Note that the second condition determination may be performed by an NF other than the SMF. When an NF other than the SMF performs the second condition determination, the SMF may provide the NF with information necessary for performing the second condition determination, specifically, at least a portion of the information received from the UE (S1406). Then, when the NF determines whether the second condition determination is true or false based on the information received from the SMF, it may convey information including the result of the second condition determination (i.e., true or false) to the SMF. The SMF may determine identification information and / or a control message to be transmitted to the UE based on the result of the second condition determination received from the NF.

[0382] For example, if the network permits the UE's request, the second condition determination may be determined as true, and if the network does not permit the UE's request, the second condition determination may be determined as false. Furthermore, if the network to which the UE is connected and / or a device within the network supports the function requested by the UE, the second condition determination may be determined as true, and if the function requested by the UE is not supported, the second condition determination may be determined as false. Furthermore, if the transmitted and received identification information is permitted, the second condition determination may be determined as true, and if the transmitted and received identification information is not permitted, the second condition determination may be determined as false.

[0383] The conditions for determining whether the second condition is true or false are not limited to the above-mentioned conditions.

[0384] Next, each step of the procedure in FIG. 9(A) will be explained.

[0385] The SMF may select a UPF for the PDU session to be established and send an N4 session establishment request message to the selected UPF (S1408). The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0386] Here, the SMF may select one or more UPFs based on information received from the AMF (message, container, information), and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc. Furthermore, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF.

[0387] Next, when the UPF receives the N4 session establishment request message (S1408), the UPF may recognize the content of the information received from the SMF. Furthermore, the UPF may send an N4 session establishment response message to the SMF based on the reception of the N4 session establishment request message (S1410).

[0388] Next, when the SMF receives an N4 session establishment response message as a response message to the N4 session establishment request message (S1410), it may recognize the contents of the information received from the UPF.

[0389] Next, the SMF sends a PDU session establishment accept message to the UE based on the reception of the PDU session establishment request message, and / or the selection of the UPF, and / or the reception of the N4 session establishment response message (S1412) (S1414) (S1416).

[0390] Specifically, the SMF may send an N1 SM container, N2 SM information, and / or a PDU session ID to the AMF based on receiving a PDU session establishment request message, selecting a UPF, and / or receiving an N4 session establishment response message (S1412). Here, the N1 SM container may include a PDU session establishment accept message. Furthermore, the PDU session ID may be included in the PDU session establishment accept message.

[0391] Next, the AMF that receives the N1 SM container, and / or the N2 SM information, and / or the PDU session ID may send a DL NAS transport message to the UE via the access network (S1414) (S1416).

[0392] Specifically, the AMF sends an N2 PDU session request message to the access network (S1414). The access network that receives the N2 PDU session request message may send a DL NAS transport message to the UE (S1416). Here, the N2 PDU session request message may include a DL NAS transport message and / or N2 SM information. The DL NAS transport message may also include a PDU session ID and / or an N1 SM container.

[0393] The PDU session establishment acceptance message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been accepted.

[0394] Here, the SMF may indicate that at least a portion of the UE's request in the PDU session establishment request message has been accepted by sending a PDU session establishment acceptance message.

[0395] Here, the SMF may send a PDU session establishment acceptance message including the 16th identification information.

[0396] Specifically, when sending the 16th identification information, the SMF may indicate updated NTZ information.

[0397] The SMF may send the 16th identity when the NTZ information of the UE needs to be updated. The SMF may send the 16th identity when it determines that the NTZ information of the UE is outdated. Here, the SMF may receive the 16th identity from the UAS-NF, and / or the UTM, and / or the USS.

[0398] Furthermore, the SMF may indicate that the network supports each function by sending each identification information and / or a PDU session establishment acceptance message, or may indicate that the request from the UE has been accepted.

[0399] Furthermore, the SMF may determine which identification information to include in the PDU session establishment acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0400] Next, the UE receives a PDU session establishment accept message and / or a DL NAS transport message from the SMF (S1412) (S1414) (S1416). The UE may receive the PDU session establishment accept message from the SMF, including the 16th identification information.

[0401] When the UE receives the PDU session establishment acceptance message and / or the second NAS message, it may recognize that the UE's request has been accepted and / or the contents of the information (message, container, information) contained in the DL NAS transport message.

[0402] Specifically, when receiving the 16th identification information, the UE may recognize the updated NTZ information.

[0403] When the 16th identification information is received, the UE may store the 16th identification information. When the 16th identification information is received, the UE may delete the stored 16th identification information and store the received 16th identification information.

[0404] Here, the UE does not need to transmit any signal based on the 16th identification information. More specifically, if the UE is within the NTZ indicated by the 16th identification information, the UE does not need to transmit any signal. In other words, the UE does not need to transmit uplink data or perform an MM procedure and / or an SM procedure based on the 16th identification information.

[0405] When the UE receives the PDU session establishment acceptance message and / or the DL NAS transport message, it may stop the first timer and recognize that the PDU session has been established.

[0406] Next, each step of the procedure in FIG. 9(B) will be explained.

[0407] The SMF transmits a PDU session establishment reject message to the UE (S1418) (S1420) (S1422).

[0408] Specifically, the SMF may send an N1 SM container and / or a PDU session ID to the AMF based on receiving the PDU session establishment request message (S1418). Here, the N1 SM container may include a PDU session establishment rejection message. Furthermore, the PDU session ID may be included in the PDU session establishment rejection message.

[0409] Next, the AMF may send a DL NAS transport message to the UE via the access network (S1420) (S1422), where the DL NAS transport message may include a PDU session ID and / or an N1 SM container.

[0410] The PDU session establishment rejection message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been rejected.

[0411] Here, the SMF may indicate that the UE request is rejected by sending a PDU session establishment rejection message.

[0412] In addition, the SMF may indicate that the UE request has been rejected by sending a PDU session establishment rejection message.

[0413] Here, the SMF may send a PDU session establishment rejection message including identification information 15, and / or 16, and / or 17, and / or 18.

[0414] Specifically, when sending the 15th identification information, the SMF may indicate that the UAS service is not permitted by the NTZ. If the SMF recognizes that the UE is a UAV that supports NTZ, it may send the 15th identification information.

[0415] Here, the SMF may receive information indicating that the UE is a UAV that supports NTZ from the AMF and / or the UAS-NF. If the SMF receives information indicating that the UE is a UAV that supports NTZ from the AMF and / or the UAS-NF, the SMF may recognize that the UE is a UAV that supports NTZ.

[0416] When sending the 16th identification information, the SMF may indicate updated NTZ information.

[0417] The SMF may send the 16th identity when the NTZ information of the UE needs to be updated. The SMF may send the 16th identity when it determines that the NTZ information of the UE is outdated. Here, the SMF may receive the 16th identity from the UAS-NF, and / or the UTM, and / or the USS.

[0418] When sending the 18th identification information, the SMF may indicate that there is a lack of resources or that the UAS service is not permitted. The SMF may send the 18th identification information if it recognizes that the UE is a UAV that does not support NTZ.

[0419] Additionally, the SMF may send the 18th identification information if it is notified by the UAS-NF that UAS services are not permitted.

[0420] Here, the SMF may receive information indicating that the UE is a UAV that does not support NTZ from the AMF and / or UAS-NF. If the SMF receives information indicating that the UE is a UAV that does not support NTZ from the AMF and / or UAS-NF, the SMF may recognize that the UE is a UAV that does not support NTZ.

[0421] Additionally, the SMF may transmit the 17th identification information together with the 18th identification information.

[0422] When sending the 17th identification information, the SMF may indicate the time during which the UE should not perform MM procedures and / or SM procedures.

[0423] Here, the UAS-NF may be a UTM (Uncrewed Aerial System Traffic Management) or a USS (UAS Service Supplier).

[0424] Furthermore, the SMF may determine which identification information to include in the PDU session establishment rejection message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0425] Next, the UE receives a DL NAS transport message and / or a PDU session establishment rejection message (S1418) (S1420) (S1422). Here, the UE may receive the PDU session establishment rejection message including identification information 15, and / or 16, and / or 17, and / or 18 from the SMF.

[0426] When the UE receives a PDU session establishment rejection message and / or a DL NAS transport message, it may recognize that the UE's request has been rejected and / or the contents of the information (message, container, information) contained in the DL NAS transport message.

[0427] Specifically, when the 15th identification information is received, the UE may recognize that the UAS service is not permitted by the NTZ.

[0428] Here, a UE that supports NTZ may be able to recognize whether it is within the NTZ.

[0429] If the 15th identity is received, the UE may enter a 5GMM-DEREGISTERED state, where a UE in a 5GMM-DEREGISTERED state may not perform PLMN selection if it is within the NTZ.

[0430] If the 15th identification information is received, the UE does not need to perform PLMN selection.

[0431] When the 16th identification information is received, the UE may recognize the updated NTZ information.

[0432] When the 16th identification information is received, the UE may store the 16th identification information. When the 16th identification information is received, the UE may delete the stored 16th identification information and store the received 16th identification information.

[0433] Here, the UE does not need to transmit any signal based on the 16th identification information. More specifically, if the UE is within the NTZ indicated by the 16th identification information, the UE does not need to transmit any signal. In other words, the UE does not need to transmit uplink data or perform an MM procedure and / or an SM procedure based on the 16th identification information.

[0434] If the 18th identification information is received, the UE may recognize that the network is out of resources and that UAS service is not permitted.

[0435] Additionally, the UE may receive the 17th identification information along with the 18th identification information.

[0436] When the 17th identification information is received, the UE may know the times when it should not perform MM procedures and / or SM procedures.

[0437] If the UE receives the 18th identification information, the UE may start a third timer using the 17th identification information. If the UE receives the 18th identification information and the third timer is running, the UE may stop the third timer. Here, the third timer may be T3346 or another timer.

[0438] Here, the UE may not perform the MM procedure and / or the SM procedure if the third timer is running.

[0439] If the UE receives a PDU session establishment rejection message and / or a DL NAS transport message, it may stop the first timer and recognize that the PDU session has not been established.

[0440] Each device may complete this procedure and establish a PDU session based on the sending and receiving of the PDU session establishment acceptance message. At this time, each device may transition to a state in which it can communicate with the DN using the established PDU session.

[0441] In addition, each device may complete this procedure based on sending and receiving a PDU session establishment rejection message. At this time, each device cannot establish a PDU session, so if there is no already established PDU session, it may not be able to communicate with the DN.

[0442] If the first timer expires, the UE may retransmit the PDU session establishment request message or reset and start the first timer. This retransmission may be repeated up to four times. That is, upon the fifth expiration of the first timer, the UE may abort this procedure.

[0443] Here, when the first timer expires, if the UE is within the NTZ, the UE does not need to retransmit the PDU session establishment request message.

[0444] In addition, the processes performed by the UE based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure.

[0445] Furthermore, the SMF may decide to release or deactivate user plane resources of established PDU sessions.

[0446] Specifically, when the SMF decides to release or deactivate user plane resources for a PDU session, it may send 19th identification information to the UE.

[0447] Furthermore, the SMF may start a fourth timer if it recognizes that the UE is in the NTZ. Here, the SMF may be indicated that the UE is in the NTZ by the AMF or the UAS-NF. The SMF may recognize that the UE is in the NTZ if it is indicated that the UE is in the NTZ.

[0448] If the fourth timer expires, the SMF may release the PDU session.

[0449] In addition, the UE may release or deactivate user plane resources of the established PDU session.

[0450] Specifically, the UE may receive a 19th identification from the 5G AN (or gNB). When the UE receives the 19th identification, the UE may release or deactivate user plane resources of the PDU session. The 19th identification may be transmitted from the SMF.

[0451] Furthermore, the UE may start a fifth timer if it receives the 19th identification while in the NTZ. Also, the UE may start the fifth timer if it enters the NTZ after receiving the 19th identification. In other words, the UE may start the fifth timer if it enters the NTZ while releasing or deactivating user plane resources for a PDU session.

[0452] If the fifth timer expires, the UE may release the PDU session.

[0453] 4. Variations The program that runs on the device according to this embodiment may be a program that controls a central processing unit (CPU) or the like to make a computer function so as to realize the functions of the embodiment according to this embodiment. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a non-volatile memory such as a flash memory, a hard disk drive (HDD), or other storage device system.

[0454] A program for realizing the functions of the embodiments according to the present invention may be recorded on a computer-readable recording medium. The program may be read into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may also refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0455] Additionally, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, such as an integrated circuit or multiple integrated circuits. The 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, or a conventional processor, controller, microcontroller, or state machine. The electrical circuit may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge, one or more aspects of the present embodiments may utilize new integrated circuit technologies that replace current integrated circuits.

[0456] It should be noted that this example is not limited to the above-described embodiment. In the embodiment, one example of a device is described, but this example is not limited to this 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 / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0457] Although the embodiment of this example has been described in detail above with reference to the drawings, the specific configuration is not limited to this example, and design modifications within the scope of the gist of this example are also included. Furthermore, this example can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this example. Furthermore, configurations in which elements described in each of the above embodiments are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0458] 1. Mobile communication systems 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A (E-UTRAN) 90 Core Network_A 120 Access Network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core Network_B 235 UPF_A 239 UPF_C

Claims

1. A UE (User Equipment) equipped with a transceiver unit, The UE is an Uncrewed Aerial Vehicle (UAV) that supports a No Transmit Zone (NTZ), The transmitting / receiving unit receiving a non-registration request message including first information from an access and mobility management function (AMF); not sending a non-registration acceptance message based on the first information; where: The first information is a reason value indicating that UAS service is not permitted by the NTZ; A UE characterized by:

2. An AMF (Access and Mobility Management Function) having a transceiver unit and a control unit, The transceiver unit receives a registration request message including first information from a UE; Based on the first information, the control unit recognizes that the UE is a UAV (Uncrewed Aerial Vehicle) that supports NTZ; The transceiver unit transmits, to the UE, a non-registration request message including second information; When the second information is transmitted, the control unit does not start the first timer; where: The first information is information indicating that the UE supports NTZ; The second information is a reason value indicating that UAS service is not permitted by the NTZ; The first timer is T3522. AMF is characterized by:

Images