UE (User Equipment) and communication control method

Abstract

To provide communication means for realizing functions regarding management of information on network slices in 5GS.SOLUTION: The present invention provides methods and communication means for procedures in an initial registration of UE and a periodic or mobility based registration, for realizing management of information on network slices in 5GS. The present invention further provides methods and communication means for a network slice-specific authentication and authorization procedure, a UE configuration update procedure and a de-registration procedure, after completion of the registration procedures.SELECTED DRAWING: Figure 6

Description

【Technical Field】 【0001】 The present invention relates to a UE (User Equipment). and communication control methods, etc. to it. 【Background Art】 【0002】 3GPP (3rd Generation Partnership Project), which conducts standardization activities for recent mobile communication systems, is studying SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution). 【0003】 In recent years, 3GPP has also been studying next-generation communication technologies and system architectures for the 5G (5th Generation) mobile communication system, which is the next-generation mobile communication system. In particular, as a system for realizing the 5G mobile communication system, the specifications of 5GS (5G System) are being developed (see Non-Patent Document 1 and Non-Patent Document 2). In 5GS, technical issues for connecting various types of terminals to a cellular network are extracted and solutions are specified. 【Prior Art Documents】 【Non-Patent Documents】 【0004】 【Non-Patent Document 1】 3GPP TS 23.501 V16.4.0 (2020-3); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16) 【Non-Patent Document 2】 3GPP TS 23.502 V16.4.0 (2020-3); 3rd GenerationPartnership Project; Technical Specification Group Services and System Aspects;Procedures for the 5G System; Stage 2 (Release 16) [Non-Patent Document 3] 3GPP TS 24.501 V16.4.0 (2020-3); 3rd GenerationPartnership Project; Technical Specification Group Core Network and Terminals;Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) [Overview of the Initiative] [Problems that the invention aims to solve] 【0005】 In order to provide a wide variety of services with 5GS (5G System), a new core network called 5GCN (5G Core Network) is being considered. 【0006】 Furthermore, 5G defines network slices, which are logical networks that provide specific network functions or characteristics for specific service types or groups. For example, a network slice may be a logical network provided for terminals with low latency capabilities, or a logical network provided for sensor terminals used in the Internet of Things (IoT). 【0007】 3GPP is also considering eNS (Enhancement of Network Slicing) to explore further features related to network slicing. As part of Phase 2 of eNS development, 3GPP is considering adding functionality to manage the number of UEs or sessions allowed per slice. 【0008】 However, a practical way to satisfy the above requirements has not yet been clearly defined. 【0009】 This invention was made in view of the above circumstances, and aims to provide a method for realizing functions for eNS in 5GS. [Means for solving the problem] 【0010】 In an embodiment of the present invention, the UE (User Equipment) comprises a transmitting / receiving unit and a storage unit, wherein the transmitting / receiving unit receives a first authorization NSSAI (Network Slice Selection Assistance Information) from the core network, and if a plurality of tracking area information included in the information indicating the registration area stored by the UE belongs to different PLMNs, the storage unit stores the received first authorization NSSAI in each authorization NSSAI associated with each PLMN. 【0011】 In an embodiment of the present invention, the UE (User Equipment) comprises a transmitting / receiving unit and a storage unit, wherein the transmitting / receiving unit receives a first authorization NSSAI (Network Slice Selection Assistance Information) from the core network, and if a plurality of tracking area information included in the information indicating the registration area stored by the UE belongs to a plurality of different PLMNs, the storage unit stores the received first authorization NSSAI in a single authorization NSSAI associated with the plurality of different PLMNs. 【0012】 In an embodiment of the present invention, the UE (User Equipment) comprises a transmitting / receiving unit, a storage unit, and a control unit, wherein the transmitting / receiving unit transmits a request NSSAI (Network Slice Selection Assistance Information) to a first PLMN, and the control unit includes in the request NSSAI an S-NSSAI included in an authorized NSSAI stored by the UE, and the authorized NSSAI is associated with a second PLMN and a registration area, and at least one tracking area included in the registration area belongs to the first PLMN. [Effects of the Invention] 【0013】 According to the present invention, eNS support becomes available in 5GS, and the number of allowed UEs per slice can be managed. [Brief explanation of the drawing] 【0014】 [Figure 1] This is a diagram illustrating the general outline of the mobile communication system (EPS / 5GS). [Figure 2] This diagram illustrates the detailed configuration of the mobile communication system (EPS / 5GS). [Figure 3] This is a diagram illustrating the equipment configuration of the UE. [Figure 4] This diagram illustrates the configuration of the access network device (gNB) in 5GS. [Figure 5] This diagram illustrates the configuration of the core network equipment (AMF / SMF / UPF) in 5GS. [Figure 6] This is a diagram explaining the registration procedure. [Figure 7] This diagram illustrates the Network Slice specific authentication and authorization procedure. [Figure 8] This diagram illustrates the procedure for changing / updating UE settings. [Figure 9] This diagram illustrates the non-registration procedure initiated by the network. 【Best Mode for Carrying Out the Invention】 【0015】 Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system when the present invention is applied will be described. 【0016】 [1. System Overview] First, FIG. 1 is a diagram for explaining the outline of the mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining the detailed configuration of the mobile communication system 1. 【0017】 As shown in FIG. 1, the mobile communication system 1 is described as being 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. 【0018】 Hereinafter, these devices / functions may be described with symbols omitted, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. 【0019】 Also, as shown in FIG. 2, devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc., and interfaces connecting these devices / functions to each other are described. 【0020】 Hereinafter, these devices / functions may be described with symbols omitted, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc. 【0021】 Furthermore, the 4G system, EPS (Evolved Packet System), consists of access network_A and core network_A, but may also include UE and / or PDN. Similarly, the 5G system, 5GS (5G System), consists of UE, access network_B and core network_B, but may also include DN. 【0022】 A UE is a device capable of connecting to network services via 3GPP access (also known as a 3GPP access network or 3GPP AN) and / or non-3GPP access (also known as a non-3GPP access network or non-3GPP AN). A UE may be a wireless communication terminal device such as a mobile phone or smartphone, and may be a terminal device capable of connecting to both EPS and 5GS. A UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). A UE may also be referred to as a user device or a terminal device. 【0023】 Furthermore, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. E-UTRAN has one or more eNBs (evolved Node B)45. Note that in the following, eNB45 may be written simply as eNB. If there are multiple eNBs, each eNB is connected to the others, for example, by an X2 interface. Furthermore, the wireless LAN access network has one or more access points. 【0024】 Furthermore, access network_B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NGRadio Access Network) and / or non-3GPP access networks. One or more gNBs (NR NodeBs)122 are placed in the NG-RAN. Note that, below, gNB122 may be written with the symbol omitted, such as eNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including the N2 interface or N3 interface). In other words, a gNB is a base station device newly designed for 5GS and has different functions from the base station device (eNB) used in the 4G system, EPS. Also, if there are multiple gNBs, each gNB is connected to the others, for example, by an Xn interface. 【0025】 Furthermore, a non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, an untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public Wi-Fi network. On the other hand, a trusted non-3GPP access network may be an access network defined by 3GPP and may be equipped with a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function). 【0026】 Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Similarly, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Additionally, nodes located in access network_B may be collectively referred to as NG-RAN nodes. 【0027】 Furthermore, in the following, access network_A and / or access network_B and / or the devices included in access network_A and / or the devices included in access network_B may be referred to as access networks or access network devices. 【0028】 Furthermore, Core Network A corresponds to EPC (Evolved Packet Core). EPC is configured with, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. 【0029】 Furthermore, Core Network B corresponds to 5GCN (5G CoreNetwork). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN may also be expressed as 5GC. 【0030】 Furthermore, in the following, Core Network A and / or Core Network B, the devices included in Core Network A and / or Core Network B may be referred to as the Core Network, Core Network devices, or devices within the Core Network. 【0031】 The core network (Core Network A and / or Core Network B) may be an IP mobile communication network operated by a Mobile Network Operator (MNO) that connects the access network (Access Network A and / or Access Network B) to the PDN and / or DN; it may be a core network for a mobile network operator that operates and manages the mobile communication system 1; or it may be a core network for a virtual mobile communication operator or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler). 【0032】 The core network (Core Network A and / or Core Network B) and the access network (Access Network A and / or Access Network B) may differ for each mobile network operator. 【0033】 Furthermore, although Figure 1 shows a case where the PDN and DN are the same, they may be different. The PDN may be a Data Network (DN) that provides communication services to the UE. The DN may be configured as a packet data service network, or it may be configured for each service. In addition, the PDN may include connected communication terminals. Therefore, connecting to the PDN may also mean connecting to communication terminals or server devices located in the PDN. Furthermore, sending and receiving user data with the PDN may also mean sending and receiving user data with communication terminals or server devices located in the PDN. Note that the PDN may be referred to as DN, and the DN may be referred to as PDN. 【0034】 Furthermore, in the following, access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein may be referred to as a network or network device. In other words, when a network and / or network device sends and receives messages and / or performs procedures, it means that access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein send and receive messages and / or perform procedures. 【0035】 Furthermore, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data with the PDN or DN. When sending and receiving user data, non-IP communication may be used in addition to IP (Internet Protocol) communication. 【0036】 Here, IP communication refers to data communication using IP, where data is sent and received via IP packets. An IP packet consists of an IP header and a payload. The payload may include data sent and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication refers to data communication that does not use IP, where data is sent and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by sending and receiving application data without an IP header, or it may be user data sent and received by the UE with other headers such as a MAC header or an Ethernet® frame header attached. 【0037】 Furthermore, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may contain devices not shown in Figure 2. For example, core network_A and / or core network_B and / or PDN_A and / or DN_A may include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S). The AAA server may be located outside the core network. 【0038】 Here, AUSF is a core network device equipped with authentication functions for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP access and / or non-3GPP access from the UE and executes the authentication procedure. 【0039】 Furthermore, the AAA server is a device equipped with authentication, authorization, and billing functions, which connects directly or indirectly to the AUSF via other network devices. The AAA server may be a network device within the core network. However, the AAA server may not be included in core network_A and / or core network_B, but may be included in PLMN. In other words, the AAA server may be a core network device or a device located outside the core network. For example, the AAA server may be a server device within PLMN managed by a third party. 【0040】 Note that in Figure 2, for the sake of simplification, only one of each device / function is shown; however, multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150. 【0041】 [2. Configuration of each device] Next, the configuration of each device (UE, and / or access network device, and / or core network device) used in each embodiment will be described with reference to a diagram. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software. 【0042】 Furthermore, each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) within each device / function described below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only the information originally set at the time of shipment, but also various information transmitted and received with devices / functions other than its own device / function (for example, UE, and / or access network devices, and / or core network devices, and / or PDN, and / or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc. contained in control messages transmitted and received within the various communication procedures described later. Furthermore, each memory unit may store this information for each UE. In addition, when interworking between 5GS and EPS occurs, each memory unit can store control messages and user data transmitted and received with devices / functions contained within 5GS and / or EPS. In this case, not only data transmitted and received via the N26 interface can be stored, but also data transmitted and received without using the N26 interface. 【0043】 [2.1. UE Equipment Configuration] First, an example of the UE (User Equipment) configuration will be explained using Figure 3. The UE consists of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, transceiver_A320, and storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310. 【0044】 The control unit_A300 is a functional unit that controls the operation and functions of the entire UE. The control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the memory unit_A340 as needed. 【0045】 The transceiver unit A320 is a functional unit for wireless communication with base station equipment (eNB or gNB) within the access network via an antenna. In other words, the UE can use the transceiver unit A320 to send and receive user data and / or control information between the access network equipment and / or core network equipment and / or PDN and / or DN. 【0046】 Referring to Figure 2, the UE can communicate with the base station equipment (eNB) in E-UTRAN via the LTE-Uu interface using the transceiver unit A320. The UE can also communicate with the base station equipment (gNB) in 5G AN using the transceiver unit A320. Furthermore, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit A320. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN. 【0047】 Memory unit A340 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UE. 【0048】 [2.2. gNB System Configuration] Next, an example of the gNB's device configuration will be explained using Figure 4. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510. 【0049】 The control unit B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit B500 implements various processes in the gNB by reading and executing various programs stored in the memory unit B540 as needed. 【0050】 The network connection unit B520 is a functional unit that allows the gNB to communicate with the AMF and / or UPF. In other words, the gNB can use the network connection unit B520 to send and receive user data and / or control information with the AMF and / or UPF. 【0051】 The transceiver unit B530 is a functional unit for wireless communication with the UE via the antenna 510. In other words, the gNB can send and receive user data and / or control information to and from the UE using the transceiver unit B530. 【0052】 Referring to Figure 2, the gNB within the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface by using the network connection unit B520. Furthermore, the gNB can communicate with the UE by using the transceiver unit B530. 【0053】 Memory unit B540 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the gNB. 【0054】 [2.3. AMF Equipment Configuration] Next, an example of the AMF's device configuration will be explained using Figure 5. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF may be a node that handles the control plane. 【0055】 The control unit B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit B700 implements various processes in the AMF by reading and executing various programs stored in the memory unit B740 as needed. 【0056】 The network connection unit_B720 is a functional unit that allows the AMF to connect to base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. In other words, the AMF can use the network connection unit_B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. 【0057】 Referring to Figure 2, the AMF within 5GCN can communicate with the gNB via the N2 interface, the UDM via the N8 interface, the SMF via the N11 interface, and the PCF via the N15 interface, using the network connection unit _A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit _A620. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN. Additionally, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface using the network connection unit _A620. 【0058】 Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the AMF. 【0059】 Furthermore, the AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and protecting the integrity of NAS messages, registration management (RM) function, connection management (CM) function, reachability management function, mobility management function for UEs, etc., forwarding SM (Session Management) messages between the UE and the SMF, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA; Security Anchor Functionality), security context management (SCM; Security Context Management) function, support for the N2 interface to the N3IWF (Non-3GPP Interworking Function), support for sending and receiving NAS signals with the UE via the N3IWF, and authentication of UEs connected via the N3IWF. 【0060】 Furthermore, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. There are two RM states: unregistered state (RM-DEREGISTERED state) and registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, so the UE context in the AMF does not have valid location or routing information for that UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered with the network, so the UE can receive services that require registration with the network. Note that the RM state may also be expressed as the 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state. 【0061】 In other words, 5GMM-REGISTERED means that each device may have established a 5GMM context or a PDU session context. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, and may respond to paging. In addition, when each device is 5GMM-REGISTERED, UE_A10 may perform registration procedures other than the registration procedure for initial registration, and / or service request procedures. 【0062】 Furthermore, 5GMM-DEREGISTERED may occur even if each device has not established a 5GMM context, or if the location information of UE_A10 is not known to the network, or if the network is unreachable to UE_A10. If each device is in a 5GMM-DEREGISTERED state, UE_A10 may initiate the registration procedure, or establish a 5GMM context by executing the registration procedure. 【0063】 Furthermore, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. There are two CM states: disconnected state (CM-IDLE state) and connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 connection or an N3 connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-CONNECTED state, the UE may have an N2 connection and / or an N3 connection. 【0064】 Furthermore, connection management may be handled separately for CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access may include an unconnected state (CM-IDLE state over 3GPP access) and a connected state (CM-CONNECTED state over 3GPP access). Furthermore, the CM states in non-3GPP access may include an unconnected state (CM-IDLE state over non-3GPP access) and a connected state (CM-CONNECTED state over non-3GPP access). Note that the unconnected state may be expressed as idle mode, and the connected state may be expressed as connected mode. 【0065】 Furthermore, the CM state may be expressed as 5GMM mode. In this case, the disconnected state may be expressed as 5GMM-IDLE mode, and the connected state may be expressed as 5GMM-CONNECTED mode. Additionally, the disconnected state in 3GPP access may be expressed as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM-CONNECTED mode over 3GPP access. Furthermore, the disconnected state in non-3GPP access may be expressed as 5GMM-IDLE mode over non-3GPPaccess, and the connected state in non-3GPP access may be expressed as 5GMM-CONNECTED mode over non-3GPP access. Note that 5GMM-IDLE mode may also be expressed as idle mode, and 5GMM-CONNECTED mode may also be expressed as connected mode. 【0066】 Furthermore, one or more AMFs may be located within core network_B. Also, an AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Additionally, an AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs. 【0067】 Furthermore, N3IWF is a device and / or function placed between the non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access. 【0068】 [2.4. SMF Equipment Configuration] Next, an example of the SMF device configuration will be explained using Figure 5. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane. 【0069】 The control unit B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit B700 implements various processes in the SMF by reading and executing various programs stored in the memory unit B740 as needed. 【0070】 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 use the network connection unit B720 to send and receive user data and / or control information with the AMF, and / or UPF, and / or PCF, and / or UDM. 【0071】 Referring to Figure 2, the SMF within 5GCN can communicate with the AMF via the N11 interface, the UPF via the N4 interface, the PCF via the N7 interface, and the UDM via the N10 interface by using the network connection unit A620. 【0072】 Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the SMF. 【0073】 SMF has functions such as session management (Session Management) including establishing, modifying, and releasing PDU sessions; IP address allocation and management for UEs; UPF selection and control; UPF configuration for routing traffic to appropriate destinations; sending and receiving the SM portion of NAS messages; Downlink Data Notification; providing AN-specific (AN-specific) SM information transmitted to ANs via the N2 interface through AMF; determining the SSC mode (Session and Service Continuity mode) for sessions; and roaming functionality. 【0074】 [2.5. UPF Equipment Configuration] Next, an example of the UPF's configuration will be explained using Figure 5. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF may be a node that handles the control plane. 【0075】 The control unit B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit B700 implements various processes in the UPF by reading and executing various programs stored in the memory unit B740 as needed. 【0076】 The network connection unit B720 is a functional unit that allows the UPF to connect with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN. 【0077】 Referring to Figure 2, the UPF within 5GCN can communicate with the gNB via the N3 interface, the SMF via the N4 interface, the DN via the N6 interface, and other UPFs via the N9 interface by using the network connection unit A620. 【0078】 Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UPF. 【0079】 UPF has functions such as acting as an anchor point for intra-RAT mobility or inter-RAT mobility, acting as an external PDU session point for interconnecting to DNs (i.e., acting as a gateway between DNs and core network B to forward user data), routing and forwarding packets, an UL CL (UplinkClassifier) ​​function that supports routing multiple traffic flows to a single DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notification. 【0080】 Furthermore, the UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have the function of forwarding IP communication, and may also have the function of converting non-IP communication to IP communication. In addition, multiple gateways may be gateways connecting the core network B to a single DN. The UPF may also have connectivity to other NFs, and may connect to each device via other NFs. 【0081】 The user plane refers to user data transmitted and received between the UE and the 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 NGRAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. Hereinafter, the user plane may be referred to as U-Plane. 【0082】 Furthermore, the control plane refers to the control messages sent and received for communication control of the UE, etc. The control plane may be sent and received using the NAS (Non-Access-Stratum) signaling connection between the UE and the MME. In addition, in the case of EPS, the control plane may be sent and received using the LTE-Uu interface and the S1-MME interface. In addition, in the case of 5GS, the control plane may be sent and received using the interface between the UE and NGRAN and the N2 interface. Hereinafter, the control plane may be referred to as the control plane or the C-Plane. 【0083】 Furthermore, the U-Plane (User Plane; UP) may also be a communication channel for sending and receiving user data, and may consist of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may also be a communication channel for sending and receiving control messages, and may consist of multiple bearers. 【0084】 [2.6. Description of other devices and / or functions and / or identification information in this embodiment] Next, other devices and / or functions and / or identification information will be described. 【0085】 The term "network" refers to at least a portion of Access Network B, Core Network B, and DN. Furthermore, one or more devices included in at least a portion of Access Network B, Core Network B, and DN may be referred to as a network or network device. In other words, the statement that a network performs message transmission and / or processing may also mean that devices within the network (network devices, and / or control devices) perform message transmission and / or processing. Conversely, the statement that devices within the network perform message transmission and / or processing may also mean that the network performs message transmission and / or processing. 【0086】 Furthermore, SM (Session Management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and may be control messages sent and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, SM messages may include PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, PDU session modification request messages, PDU session modification command messages, PDU session modification complete messages, PDU session modification command reject messages, PDU session modification reject messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, PDU session release complete messages, etc. Also, procedures for SM or SM procedures may include PDU session establishment procedures, PDU session modification procedures, and UE-requested PDU session release procedures.Each procedure may be initiated from the UE (User Environment) or from the NW (Network). 【0087】 Furthermore, MM (Mobility management) messages (also referred to as NAS MM messages) may be NAS messages used for procedures related to MM, and may be control messages sent and received between UE_A10 and AMF_A240. In addition, MM messages may include registration request messages, registration accept messages, registration reject messages, de-registration request messages, de-registration accept messages, configuration update command messages, configuration update complete messages, service request messages, service accept messages, service reject messages, notification messages, notification response messages, etc. Furthermore, procedures for or for MM may include registration procedures, deregistration procedures, generic UE configuration update procedures, authentication and authorization procedures, service request procedures, paging procedures, and notification procedures. 【0088】 Furthermore, the 5GS (5G System) service may be a connectivity service provided using the core network_B190. In addition, the 5GS service may be a different service from the EPS service, or it may be a service similar to the EPS service. 【0089】 Furthermore, non-5GS services may be any service other than 5GS services, and may include EPS services and / or non-EPS services. 【0090】 Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, it means that data will be sent and received using IPv4. If IPv6 is specified, it means that data will be sent and received using IPv6. If IPv4v6 is specified, it means that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it means that communication will be conducted using a communication method other than IP, rather than IP-based communication. 【0091】 Furthermore, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the relationship between a DN and an UE that provides PDU connectivity services, but it may also be connectivity established between the UE and an external gateway. In 5GS, the UE can send and receive user data to and from the DN using the PDU session by establishing a PDU session via access network_B and core network_B. Here, this external gateway may be UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers located on the DN. 【0092】 Furthermore, each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with each PDU session. These pieces of identification information may include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, or they may include other information. In addition, if multiple PDU sessions are established, the pieces of identification information associated with each PDU session may be the same or different. 【0093】 Furthermore, the DNN (Data Network Name) may be identification information that identifies the core network and / or external networks such as DNs. In addition, the DNN can be used as information to select gateways such as PGW_A30 / UPF_A235 to which the core network_B190 is connected. Furthermore, the DNN may be equivalent to the APN (Access Point Name). 【0094】 Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Ethernet may also indicate that communication using IP will not be performed. If Unstructured is specified, it indicates that data will be sent and received to application servers, etc., on the DN using Point-to-Point (P2P) tunneling technology. As a P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, IP may also be included as a PDU session type. IP can be specified when the UE can use both IPv4 and IPv6. 【0095】 Furthermore, 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 (mobile) telecommunications carrier, and the operator can be identified by the PLMNID. In this paper, PLMN may also mean PLMNID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). PLMN may also mean the core network. 【0096】 Furthermore, the UE may maintain an Equivalent HPLMN list in the USIM to identify one or more EHPLMNs (Equivalent HPLMNs). A PLMN that is different from an HPLMN and / or EHPLMN may be a VPLMN (Visited PLMN). 【0097】 A PLMN that a UE has successfully registered may be an RPLMN (Registered PLMN). Each device may receive, and / or retain, and / or store an Equivalent PLMN list from the RPLMN to identify one or more EPLMNs (Equivalent PLMNs) that can be used equivalently to the RPLMN in the UE's PLMN selection. 【0098】 The current PLMN may be a PLMN requested by the UE, and / or a PLMN selected by the UE, and / or an RPLMN, and / or a PLMN permitted by the network, and / or a PLMN to which a core network device sending and receiving messages belongs. 【0099】 The requested PLMN refers to the destination network for a message sent by the UE. Specifically, it may be the PLMN selected by the UE when sending a message. The requested PLMN is the PLMN requested by the UE and may be the current PLMN. Furthermore, if the UE is registered, the requested PLMN may be the registered PLMN. 【0100】 Furthermore, a network slice (NS) is a logical network that provides specific network capabilities and characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. Network slices are sometimes simply referred to as slices. 【0101】 Furthermore, a Network Slice Instance (NSI) is composed of an instance (entity) of a Network Function (NF) and a set of necessary resources, forming a network slice in which it is deployed. Here, an NF is a processing function in a network, adopted or defined by 3GPP. One or more NSIs are instances of NSs configured within core network_B. Additionally, an NSI may be composed of virtual NFs (Network Functions) generated using an NST (NetworkSlice Template). 【0102】 Here, NST is a logical representation of one or more NFs associated with resource requests to provide the required communication services and capabilities. In other words, NSI may be a collection within the core network_B190 composed of multiple NFs. Furthermore, NSI may be a logical network configured to separate user data delivered by services, etc. One or more NFs may be configured in an NS. NFs configured in an NS may be devices shared with other NSs, or they may not. 【0103】 UEs and / or devices within the network can be assigned to one or more NSs based on registration information such as NSSAI and / or S-NSSAI and / or UE usage type and / or one or more NSI IDs and / or APN. The UE usage type is a parameter value included in the UE's registration information used to identify the NSI. The UE usage type may be stored in the HSS. The AMF may select between SMF and UPF based on the UE usage type. 【0104】 Furthermore, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying an NS. S-NSSAI may consist only of SST (Slice / Service type), or it may consist of both SST and SD (Slice Differentiator). Here, SST is information that indicates the expected behavior of the NS in terms of function and service. SD may be information that complements SST when selecting one NSI from multiple NSIs indicated by SST. S-NSSAI may be information specific to each PLMN, or it may be standard information common to all PLMNs. The network may also store one or more S-NSSAIs in the UE's registration information as default S-NSSAIs. If S-NSSAI is the default S-NSSAI, and the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide NSs relevant to the UE. 【0105】 Furthermore, the S-NSSAI transmitted and received between the UE and the NW may be expressed as an S-NSSAI IE (Information element). In addition, the S-NSSAIIE transmitted and received between the UE and the NW may consist of an S-NSSAI composed of the SST and / or SD of a registered PLMN, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN to which that S-NSSAI is mapped. One or more S-NSSAIs stored by the UE and / or NW may consist of an SST and / or SD, or an S-NSSAI composed of an SST and / or SD, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN to which that S-NSSAI is mapped. 【0106】 Furthermore, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAIs. Each S-NSSAI included in NSSAI is information that assists the access network or core network in selecting an NSI. The UE may store the NSSAIs allowed by the network for each PLMN. Also, NSSAIs may be information used to select an AMF. The UE may apply each NSSAI (allowed NSSAI, and / or configured NSSAI, and / or rejected NSSAI, and / or pending NSSAI, and / or first NSSAI) to the PLMN and EPLMN. 【0107】 A mapped S-NSSAI is an HPLMN S-NSSAI mapped to the registered PLMN's S-NSSAI in a roaming scenario. The UE may store one or more mapped S-NSSAIs that are mapped to the configured NSSAI and the allowed NSSAI for each access type. Furthermore, the UE may store one or more mapped S-NSSAIs that are included in the first NSSAI and / or rejected NSSAI and / or pendingNSSAI. 【0108】 Network Slice-Specific Authentication and Authorization (NSSAA) functionality is a feature that enables authentication and authorization specific to network slices. Network slice-specific authentication and authorization allows authentication and authorization of UEs outside the core network, such as by third parties. PLMNs and network devices equipped with NSSAA functionality can execute NSSAA procedures on a given S-NSSAI based on the UE's registration information. Furthermore, UEs equipped with NSSAA functionality can manage, store, and send / receive pending NSSAIs and third rejected NSSAIs. In this paper, NSSAA may sometimes be referred to as network slice-specific authentication and authorization procedures or authentication and authorization procedures. 【0109】 An S-NSSAI requiring NSSAA is an S-NSSAI requiring NSSAA that is managed by the core network and / or core network equipment. Furthermore, an S-NSSAI requiring NSSAA may be an S-NSSAI other than HPLMN that is managed by the core network and / or core network equipment and is a mapped S-NSSAI. 【0110】 The core network and / or core network device may store S-NSSAIs that require NSSAA by associating them with information indicating whether or not NSSAA is required. The core network and / or core network device may further store S-NSSAIs that require NSSAA with information indicating whether or not NSSAA has been completed, or information indicating that NSSAA has been completed and is authorized or successful. The core network and / or core network device may manage S-NSSAIs that require NSSAA as information unrelated to the access network. 【0111】 Furthermore, a configured NSSAI is an NSSAI supplied to and stored within the UE. The UE may store a configured NSSAI for each PLMN. The UE may also store a configured NSSAI associated with a PLMN. In this paper, a configured NSSAI associated with a PLMN may be expressed as a configured NSSAI for the PLMN, or a configured NSSAI of the PLMN, or a configured NSSAI for the PLMN, or a configured NSSAI associated with the PLMN. Additionally, the UE may store a configured NSSAI that is not associated with a PLMN but is valid for all PLMNs, and such a configured NSSAI may be referred to as the "default configured NSSAI". 【0112】 A configured NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs. 【0113】 The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be expressed as configured S-NSSAI. The configured S-NSSAI may consist of an S-NSSAI and a mapped S-NSSAI. Alternatively, the S-NSSAI of a PLMN may be expressed as "configured S-NSSAI," and the S-NSSAI that is mapped to HPLMN may be expressed as "mapped S-NSSAI for configuredNSSAI for PLMN." 【0114】 Furthermore, the requested NSSAI is an NSSAI provided by the UE to the network during the registration procedure. In the registration procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be an S-NSSAI included in the allowed NSSAI or configured NSSAI stored by the UE. In the PDU session establishment procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be an S-NSSAI included in the allowed NSSAI stored by the UE. 【0115】 The requested NSSAI may be information indicating the network slice requested by the UE. The S-NSSAI included in the requested NSSAI may be expressed as the requested S-NSSAI. For example, the requested NSSAI is sent in an RRC (RadioResource Control) message that includes a NAS message or NAS (Non-Access-Stratum) message sent from the UE to the network, such as a registration request message or a PDU session establishment request message. 【0116】 Furthermore, an allowed NSSAI is information that indicates one or more network slices that the UE has allowed to connect. In other words, an allowed NSSAI identifies the network slices that the network has allowed to connect to the UE. 【0117】 The UE and / or NW may store and manage allowedNSSAI as part of the UE's information for each access (3GPP access or non-3GPP access). The UE and / or NW may further manage allowed NSSAI in association with registration areas. 【0118】 Furthermore, the UE and / or NW may store and manage the allowed NSSAI as UE information, associated with the PLMN. The allowed NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs. 【0119】 In this paper, an allowedNSSAI associated with a PLMN and an access type may also be expressed as an allowedNSSAI for a PLMN and an access type, or an allowedNSSAI for a PLMN's access type. An S-NSSAI included in an allowed NSSAI may be expressed as an allowed S-NSSAI. An allowed S-NSSAI may consist of an S-NSSAI and a mapped S-NSSAI. 【0120】 Furthermore, a rejected NSSAI is information indicating one or more network slices that the UE is not permitted to connect to. In other words, a rejected NSSAI is information that identifies network slices that the network does not allow the UE to connect to. A rejected NSSAI may also include one or more combinations of S-NSSAI and rejection reason values. 【0121】 Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network may appropriately store and manage the rejected NSSAIs based on the associated rejection reason value for each S-NSSAI. 【0122】 Furthermore, rejected NSSAIs may be included in NAS messages sent from the network to the UE, such as registration acceptance messages, configuration update commands, or registration rejection messages, or in RRC messages that contain NAS messages. S-NSSAIs included in rejected NSSAIs may be expressed as rejected S-NSSAIs. 【0123】 A rejected NSSAI may be any of the first to third rejected NSSAIs, a pending NSSAI, and the first NSSAI, or a combination thereof. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. A rejected S-NSSAI may consist of an S-NSSAI and a mapped S-NSSAI. 【0124】 The UE and / or NW may store and manage rejected NSSAIs as UE information, associated with PLMNs. A rejected NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs. 【0125】 In this paper, a rejected NSSAI associated with a PLMN may also be expressed as a rejected NSSAI for a PLMN, or a rejected NSSAI of a PLMN. The UE and / or NW may further store a second rejected NSSAI and / or a second rejected S-NSSAI in association with a registration area. The UE and / or NW may also store a second rejected NSSAI and / or a second rejected S-NSSAI in association with an access type and / or registration area. 【0126】 Here, the first rejected NSSAI is a set of one or more S-NSSAIs that the UE has included in the requested NSSAI but are unavailable in the current PLMN. The first rejected NSSAI may be the rejected NSSAI for the current PLMN in 5GS, the rejected S-NSSAI for the current PLMN, or the S-NSSAI included in the rejected NSSAI for the current PLMN. The first rejected NSSAI may be a rejected NSSAI stored by the UE or NW, or a rejected NSSAI sent from the NW to the UE. If the first rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the first rejected NSSAI may be information that includes one or more combinations of S-NSSAI and reason values. The rejection reason value at this time may be "S-NSSAI not available in the current PLMN or SNPN (S-NSSAI not available in the current PLMN)," and may be information indicating that the S-NSSAI associated with the rejection reason value is not available in the current PLMN or SNPN. The S-NSSAI included in the first rejected NSSAI may be expressed as the first rejected S-NSSAI. 【0127】 The first rejected NSSAI may apply to the entire registered PLMN. The UE and / or NW may treat the first rejected NSSAI and the S-NSSAI contained within the first rejected NSSAI as information independent of the access type. In other words, the first rejected NSSAI may be valid information for both 3GPP access and non-3GPP access. 【0128】 If the UE transitions to an unregistered state for the current PLMN via both 3GPP access and non-3GPP access, it may delete the first rejected NSSAI from its memory. In other words, if the UE transitions to an unregistered state for the current PLMN via one access, or successfully registers with a new PLMN via another access, or fails to register with a new PLMN via another access and transitions to an unregistered state, and the UE is also unregistered via the other access, the UE deletes the first rejected NSSAI. That is, if the UE transitions to an unregistered state for the current PLMN via one access, and the UE is registered with the current PLMN via the other access (registered state), the UE does not need to delete the first rejected NSSAI. 【0129】 The second rejected NSSAI is a set of one or more S-NSSAIs that the UE included in the requested NSSAI and that are unavailable within the current registration area. The second rejected NSSAI may be a 5GS rejected NSSAI for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored by the UE or NW, or a rejected NSSAI sent from the NW to the UE. If the second rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the second rejected NSSAI may be information that includes one or more combinations of S-NSSAI and reason values. The reason value in this case may be "S-NSSAI not available in the current registration area," and may be information indicating that the S-NSSAI associated with the reason value is unavailable within the current registration area. S-NSSAI included in the second rejected NSSAI may also be expressed as the second rejected S-NSSAI. 【0130】 The second rejected NSSAI may be valid within the current registration area and may apply to the current registration area. The UE and / or NW may treat the second rejected NSSAI and the S-NSSAI contained within the second rejected NSSAI as information per access type. That is, the second rejected NSSAI may be valid for 3GPP access or non-3GPP access, respectively. That is, once an access transitions to an unregistered state, the UE may delete the second rejected NSSAI associated with that access from storage. 【0131】 The third rejected NSSAI is a set of one or more S-NSSAIs that require an NSSAA, for which the NSSAA has failed or been revoked. The third rejected NSSAI may be an NSSAI stored by the UE and / or NW, or an NSSAI transmitted between the NW and the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejectedNSSAI may be information that includes one or more combinations of S-NSSAIs and rejection reasons. The rejection reason in this case may be "S-NSSAI not available due to the failed or revoked NSSAA," and may be information indicating that the NSSAA for the S-NSSAI associated with the rejection reason has failed or been revoked. The S-NSSAIs included in the third rejected NSSAI may be expressed as the third rejectedS-NSSAI. 【0132】 The third rejected NSSAI may apply to the entire registered PLMN, or to the registered PLMN and / or EPLMN, or to all PLMNs. The fact that the third rejected NSSAI applies to all PLMNs may mean that the third rejected NSSAI is not associated with a PLMN, or that the third rejected NSSAI is associated with an HPLMN. 【0133】 Furthermore, the UE and / or NW may treat the third rejectedNSSAI and the third rejected S-NSSAI as information independent of the access type. That is, the third rejected NSSAI may be information valid for 3GPP access and non-3GPP access. The third rejected NSSAI may be a different NSSAI from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI. The third rejected NSSAI may be a 5GS rejected NSSAI for the failed or revoked NSSAA, a rejected S-NSSAI for the failed or revoked NSSAA, or an S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA. 【0134】 The third rejected NSSAI is a rejected NSSAI that identifies a slice that has been rejected by the UE due to an NSSAA failure or cancellation from the core network. Specifically, while the UE stores the third rejected NSSAI, it does not initiate a registration request procedure for the S-NSSAI contained in the third rejected NSSAI. The third rejected NSSAI may be identification information containing one or more S-NSSAIs received from the core network in association with rejection reason values ​​indicating NSSAA failure. The third rejected NSSAI is access type independent information. Specifically, if the UE stores the third rejected NSSAI, the UE does not have to attempt to send a registration request message containing the S-NSSAI contained in the third rejected NSSAI for both 3GPP and non-3GPP access. Alternatively, the UE may send a registration request message containing the S-NSSAI contained in the third rejected NSSAI based on its UE policy. Alternatively, the UE may delete the third rejected NSSAI in accordance with its UE policy and transition to a state where it can send a registration request message containing the S-NSSAI included in the third rejected NSSAI. In other words, if the UE sends a registration request message containing the S-NSSAI included in the third rejected NSSAI in accordance with its UE policy, the UE may delete that S-NSSAI from the third rejected NSSAI. 【0135】 The first NSSAI is information containing one or more S-NSSAIs that have reached the maximum number of UEs per network slice. The first NSSAI may be a rejected NSSAI, an allowed NSSAI, or a pending NSSAI. The first NSSAI may be an NSSAI stored by the UE and / or the NW, or an NSSAI sent from the NW to the UE. 【0136】 When the first NSSAI is sent from the NW to the UE, the first NSSAI may include one or more pieces of information, each including at least one of the following: an S-NSSAI, a mapped S-NSSAI, a rejection reason value, a backoff timer value, and information indicating the validity period range of the backoff timer value. The rejection reason value in this case may be "an S-NSSAI that has reached the maximum number of UEs per network slice," and may be information indicating that the maximum number of UEs that can be permitted for the S-NSSAI associated with the rejection reason value has been reached. Here, the rejection reason value may be a rejection reason value included in the rejected NSSAI, flag information, or a 5GMM cause. Furthermore, the backoff timer value in this case may be information indicating the period during which the UE is prohibited from sending MM messages and SM messages using the S-NSSAI relating to the corresponding S-NSSAI or mapped S-NSSAI. 【0137】 Furthermore, the information indicating the validity period range of the backoff timer value may be information indicating whether the backoff timer value applies to the current PLMN (PublicLand Mobile Network), to all PLMNs, or is valid in the current registration area. 【0138】 The first NSSAI may apply to the entire registered PLMN, may be valid for all PLMNs, may apply to all PLMNs, may be valid within a registration area, may apply to registered PLMNs and EPLMNs, or may apply to one or more PLMNs to which TAIs included in a TA list (TAI list or registration area) belong. The fact that the first NSSAI applies to all PLMNs may mean that the first NSSAI is not associated with a PLMN, or that the first NSSAI is associated with an HPLMN. 【0139】 If the first NSSAI is valid across the entire registered PLMN, or applies to all PLMNs, or applies to the registered PLMN and / or EPLMN, the UE and / or NW may treat the first NSSAI and the S-NSSAI contained within the first NSSAI as access-type independent information. If the first NSSAI is valid within a registration area, or applies to one or more PLMNs to which TAIs contained in a TA list (TAI list or registration area) belong, the UE and / or NW may treat the first NSSAI and the S-NSSAI contained within the first NSSAI as access-type specific information. 【0140】 The first NSSAI may be an allowed NSSAI, a rejected NSSAI, a pending NSSAI, or information different from these. 【0141】 A pending NSSAI is a set of one or more S-NSSAIs that are pending and / or unavailable for use by the UE. A pending NSSAI may be a set of S-NSSAIs for which the network requires network slice specific authentication, and for which network slice specific authentication has not yet been completed. A pending NSSAI may be a 5GS pending NSSAI. A pending NSSAI may be an NSSAI stored by the UE and / or the NW, or an NSSAI sent and received between the NW and the UE. 【0142】 If the pending NSSAI is an NSSAI sent from the network to the UE, the pendingNSSAI may include information that includes one or more combinations of S-NSSAI and rejection reason values. The rejection reason value in this case may be "NSSAA is pending for the S-NSSAI" and may be information indicating that the S-NSSAI associated with the rejection reason value is prohibited or pending from being used by the UE until the NSSAA for that S-NSSAI is completed. 【0143】 If pending NSSAI is an NSSAI sent from the network to the user interface (UE), then pendingNSSAI may be a set of combinations of S-NSSAI and mapped S-NSSAI. 【0144】 A pending NSSAI may apply to the entire registered PLMN, to the registered PLMN and one or more EPLMNs of the registered PLMN, or to all PLMNs. If a pending NSSAI applies to all PLMNs, it may mean that the pending NSSAI is not associated with a PLMN, or that the pending NSSAI is associated with an HPLMN. 【0145】 The UE and / or NW may treat the S-NSSAI included in the pending NSSAI as information independent of the access type. That is, the pending NSSAI may be valid for both 3GPP access and non-3GPP access. The pending NSSAI may be a different NSSAI from the rejected NSSAI. The pending NSSAI may be the first rejected NSSAI. 【0146】 A pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that the UE identifies as a slice for which the procedure is pending. Specifically, while the UE is storing a pending NSSAI, it will not initiate a registration request procedure for the S-NSSAI contained within the pending NSSAI. In other words, the UE will not use the S-NSSAI contained within the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI contained within the pending NSSAI is completed. A pending NSSAI is access-type independent information. Specifically, if the UE is storing a pending NSSAI, it will not attempt to send a registration request message containing the S-NSSAI contained within the pending NSSAI via either 3GPP or non-3GPP access. 【0147】 A tracking area is one or more ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may consist of multiple cells. Furthermore, a tracking area may be the range to which control messages such as paging are broadcast, or the range to which UE_A10 can move without handover procedures. Furthermore, a tracking area may be a routing area, a location area, or something similar. Hereinafter, a tracking area may also be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking Area Code) and a PLMN. 【0148】 A registration area is a set of one or more TAs assigned by the AMF to a UE. UE_A10 may move within one or more TAs included in the registration area without sending or receiving signals for tracking area updates. In other words, a registration area may be a set of information indicating an area that UE_A10 can move within without performing the tracking area update procedure. A registration area may be identified by a TAIlist consisting of one or more TAIs. 【0149】 A TAI included in the TAI list may belong to one PLMN or to multiple PLMNs. If multiple TAIs included in the TAI list belong to different PLMNs, those PLMNs may be EPLMNs. 【0150】 A UE ID is information used to identify a UE (User Account). Specifically, for example, a UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, a UE ID may be other information configured within an application or network. Furthermore, a UE ID may be information used to identify a user. 【0151】 Managing the maximum number of UEs connected to a slice means managing the maximum number of UEs that can be registered to a network slice or S-NSSAI simultaneously. Here, the UEs registered to a network slice or S-NSSAI may be those that are included in the allowed NSSAI and stored, with the S-NSSAI representing the network slice being stored. Devices in the support network that support the function of managing the maximum number of UEs connected to a slice can store whether or not maximum UE management is required for each S-NSSAI, and can also check during the registration procedure whether or not the registered UEs have reached a constant, which is the maximum number. Furthermore, each device that supports the function of managing the maximum number of UEs connected to a slice may store the first NSSAI. In this paper, the maximum number of UEs connected to a slice may be expressed as the maximum number of UEs connected to each slice, the maximum number of UEs that can be registered to a network slice or S-NSSAI, the maximum number of UEs, or a constant. 【0152】 A backoff timer is a timer that prevents the UE from sending MM messages and / or initiating procedures via SM messages. The backoff timer is managed and executed by the UE. The backoff timer may be associated with S-NSSAI. While the backoff timer associated with S-NSSAI is active, the UE may be prohibited, restricted, or limited from sending MM messages and / or SM messages using that S-NSSAI. These restrictions may be restrictions imposed by 5GS congestion management, or restrictions that include restrictions imposed by 5GS congestion management. 【0153】 The backoff timer may be a timer that is started and / or stopped on an S-NSSAI and / or PLMN basis. 【0154】 Specifically, the backoff timer may be associated with an S-NSSAI and may be a timer for prohibiting the transmission of MM messages and / or SM messages using a particular S-NSSAI. In other words, the UE may be configured not to send MM messages and / or SM messages using that particular S-NSSAI while this timer is counting. 【0155】 Furthermore, during the timer count, the UE may configure the new PLMN to allow the transmission of MM messages and / or SM messages that were prohibited in the previous PLMN, based on certain conditions described later. Note that when it is stated that the transmission of MM messages and / or SM messages that were prohibited in the previous PLMN is allowed, it may also mean that the transmission of MM messages and / or SM messages using the same S-NSSAI as the S-NSSAI associated with the backoff timer, and / or S-NSSAI related to the same S-NSSAI, and / or S-NSSAI related to the mapped S-NSSAI of the same S-NSSAI is allowed. 【0156】 Furthermore, the backoff timer may be a timer for prohibiting the transmission of MM messages using a specific NSSAI. In other words, the UE may be configured not to transmit MM messages using that specific NSSAI, and / or NSSAI including a specific S-NSSAI, while this timer is counting. 【0157】 Furthermore, during this timer count, the UE may configure the new PLMN to allow the transmission of MM messages that were prohibited in the previous PLMN, based on certain conditions described later. Note that when it is stated that the transmission of MM messages that were prohibited in the previous PLMN are allowed, it may mean that the transmission of MM messages using an NSSAI that includes the same NSSAI as the NSSAI associated with the backoff timer, and / or an NSSAI that includes the same S-NSSAI as the S-NSSAI associated with the backoff timer is allowed. Furthermore, when it is stated that the transmission of MM messages that were prohibited in the previous PLMN are allowed, it may mean that the transmission of MM messages using an NSSAI that includes an S-NSSAI related to the S-NSSAI associated with the backoff timer, and / or an NSSAI that includes an S-NSSAI related to the mapped S-NSSAI of the S-NSSAI associated with the backoff timer is allowed. 【0158】 Furthermore, the backoff timer may be associated with no NSSAI and may be a timer for prohibiting the transmission of MM messages using no NSSAI. In other words, UE_A10 may be configured not to transmit MM messages using no NSSAI while this timer is counting. In addition, UE_A10 may be configured, while this timer is counting, to allow the transmission of MM messages that were prohibited in the previous PLMN based on specific conditions described later. Note that when it is stated that the transmission of MM messages that were prohibited in the previous PLMN is allowed, it may also mean that MM messages using no NSSAI are allowed. 【0159】 Furthermore, the backoff timer may be a 5GMM timer and / or an EMM (EPS mobility management) timer. Additionally, the backoff timer may be timer T3448 or an equivalent timer. In other words, the backoff timer may be the same timer as, or a similar timer to, the timer used to regulate the communication of user data via the control plane. 【0160】 Next, the identification information transmitted, received, and stored by each device in this embodiment will be described. 【0161】 The first identification information is information indicating the network slice requested by the UE. The first identification information may include one or more S-NSSAIs associated with the network slice requested by the UE. The network slice requested by the UE may be a network slice that the UE wants to use, or a network slice that the UE requests to be allowed to use from the network. The S-NSSAI included in the first identification information may be an S-NSSAI included in a configured NSSAI associated with the current PLMN, or an S-NSSAI included in an allowed NSSAI associated with the current PLMN. 【0162】 In other words, the first identification information may be an S-NSSAI contained in a configured NSSAI associated with one or more current PLMNs, or an S-NSSAI contained in an allowed NSSAI associated with one or more current PLMNs, or a combination of the above two. More specifically, the allowed NSSAI associated with a current PLMN may be an allowed NSSAI associated with a current PLMN and a current access type. Furthermore, the first identification information may be a requested NSSAI of 5GS. 【0163】 Furthermore, the S-NSSAI included in the first identification information may be an S-NSSAI that is stored by the UE and is not included in the rejected NSSAI associated with the current PLMN, and / or an S-NSSAI that is stored by the UE and is not included in the pending NSSAI associated with the current PLMN, and an S-NSSAI that is stored by the UE and is not included in the first NSSAI associated with the current PLMN. 【0164】 Furthermore, the S-NSSAI included in the first identification information may be an S-NSSAI in which the backoff timer associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI, is not running in the UE. 【0165】 The second identification information may be information indicating that the UE supports a function for managing the maximum number of UEs connected to a slice. Alternatively, the second identification information may be information indicating whether or not the UE supports a function for managing the maximum number of UEs connected to a slice. The second identification information may be 5G MM capability information. The second identification information may be information indicating that the UE is capable of storing information. 【0166】 The tenth identification information may be information indicating an S-NSSAI that has reached the maximum number of UEs that can be registered in a network slice or S-NSSAI. The tenth identification information may be included in an allowed NSSAI transmitted from the network, in a rejected NSSAI transmitted from the network, in a pendingNSSAI transmitted from the network, or transmitted from the network as information different from these. 【0167】 Furthermore, the tenth identification information may be an NSSAI. Furthermore, the tenth identification information may be an allowed NSSAI or a rejected NSSAI. Furthermore, the tenth identification information may be a pending NSSAI or a different NSSAI. 【0168】 The tenth identification information may be the first NSSAI or an S-NSSAI included in the first NSSAI. The tenth identification information may consist of at least one of the identification information items 11 to 15. Specifically, the tenth identification information may consist of at least one of the following: an S-NSSAI that has reached the maximum number of UEs that can be registered to a network slice or S-NSSAI; the mapped S-NSSAI of that S-NSSAI; a reason value indicating that the maximum number of UEs that can be registered to that network slice or S-NSSAI has been reached; a backoff timer value indicating the period during which UEs are prohibited from sending registration request messages using that S-NSSAI; and information indicating the effective range of that backoff timer. Furthermore, the tenth identification information may consist of at least one of the following: a reason value indicating that the maximum number of UEs that can be registered to a network slice has been reached; a backoff timer value indicating the period during which sending registration request messages using no NSSAI is prohibited; and information indicating the effective range of that backoff timer. Furthermore, the reason value indicating that the maximum number of UEs that can be registered for a network slice has been reached, the value of the backoff timer indicating the period during which sending registration request messages using no NSSAI is prohibited, and information indicating the valid range of the backoff timer are not included in the 10th identification information and may be sent and received separately. Here, if the 10th identification information is included in rejected NSSAI, the reason value included in the 10th identification information may be a rejection reason value. 【0169】 The 11th identifier may be information indicating that the network has reached the maximum number of UEs that can be registered with a network slice or S-NSSAI, and / or a reason value. The 11th identifier may be information indicating that the use of S-NSSAI is being rejected or restricted because the maximum number of UEs that can be connected per slice has been reached, and / or a reason value. In other words, the 11th identifier is information and a reason value indicating that the UE has been rejected or restricted from using S-NSSAI by the network because the maximum number of UEs that can be connected per slice has been reached. The 11th identifier may be included in the 10th identifier and may be associated with the S-NSSAI indicated in the 14th identifier included in the same 10th identifier, and / or the mappedS-NSSAI indicated in the 15th identifier. The 11th identifier may be associated with each identifier included in the same 10th identifier. If the 11th identifier is included in rejected NSSAI, the 11th identifier may be a rejection reason value. The 11th identifier may be flag information. 【0170】 Furthermore, the 11th identification information may be a reason value indicating that connection to the slice is restricted and / or not permitted. Furthermore, the 11th identification information may be a reason value indicating that registration to the slice is restricted and / or not permitted. 【0171】 Furthermore, the 11th identification information may be a 5GMM (5GMobility Management) cause. Furthermore, the 11th identification information may be a 22nd 5GMM cause, where the 22nd 5GMM cause may be a reason value indicating congestion. Furthermore, the 22nd 5GMM cause may be information sent to the UE due to network congestion. 【0172】 Furthermore, the 11th identifier may be a 5GMM cause other than the 22nd 5GMM cause. For example, the 11th identifier may be information sent to the UE due to network slice congestion. Furthermore, the 11th identifier may be information sent to the UE due to insufficient resources in a network slice. Furthermore, the 11th identifier may be a reason value indicating that the requested service cannot be provided due to insufficient resources for a particular slice. 【0173】 The 12th identification information may be the value of the backoff timer. Specifically, the 12th identification information may be information indicating the period during which the network prohibits the UE from sending MM messages using the S-NSSAI indicated in the 14th identification information and / or the 15th identification information, which are included in the same 10 identification information, or from sending SM messages other than PDU connection release request messages. In other words, the 12th identification information may be information indicating the period during which the network prohibits the UE from sending registration request messages using the S-NSSAI indicated in the 14th identification information and / or the 15th identification information, which are included in the same 10 identification information. 【0174】 The 12th identification information may be included in the 10th identification information and may be associated with the S-NSSAI shown in the 14th identification information included in the same 10th identification information, and / or the mapped S-NSSAI shown in the 15th identification information. The 12th identification information may also be associated with each of the identification information included in the same 10th identification information. 【0175】 The 13th identification information is information indicating the valid range of the backoff timer. Specifically, the 13th identification information may be information indicating the valid range of the backoff timer counted by the UE, using the corresponding backoff timer value. More specifically, the 13th identification information may be information indicating that the corresponding backoff timer applies to the current PLMN (the PLMN or RPLMN requested by the UE), or to all PLMNs. Alternatively, the 13th identification information may be information indicating that it applies to the current registration area. 【0176】 Furthermore, the 13th identification information may be information indicating the scope of the regulation, or information indicating the scope to which the regulation applies. The regulation may be a congestion management regulation. More specifically, the regulation may restrict the transmission of MM messages by the UE. Furthermore, the regulation may be implemented by a backoff timer. 【0177】 The 13th identification information may be included in the 10th identification information, in which case the corresponding backoff timer value may be the value indicated by the 12th identification information included in the same 10th identification information. Furthermore, in that case, the 13th identification information may be associated with each piece of identification information included in the same 10th identification information. 【0178】 The 14th identification information is information indicating an S-NSSAI that has reached the maximum number of UEs that can be registered for each S-NSSAI. The 14th identification information may be an S-NSSAI included in the 10th identification information, and may be associated with a mapped S-NSSAI indicated in the 15th identification information included in the same 10th identification information. The 14th identification information may also be associated with each other identification information included in the same 10th identification information. Furthermore, the 14th identification information may be an S-NSSAI. 【0179】 The 15th identifying information is the S-NSSAI of the HPLMN associated with the corresponding S-NSSAI. Specifically, if the current PLMN (current PLMN, or PLMN requested by the UE, or RPLMN, a PLMN selected by the UE) is not an HPLMN, the 15th identifying information may be information indicating the S-NSSAI of the HPLMN mapped to the S-NSSAI of the current PLMN. The 15th identifying information may also be the mapped S-NSSAI. 【0180】 The 15th identification information may be a mapped S-NSSAI included in the 10th identification information, and may be associated with the S-NSSAI shown in the 14th identification information included in the same 10th identification information, in which case it may be the mapped S-NSSAI of the S-NSSAI shown in the 14th identification information. The 15th identification information may be associated with each of the identification information included in the same 10th identification information. Furthermore, the 15th identification information may be the mapped S-NSSAI of the S-NSSAI shown in the 14th identification information. 【0181】 [3.1. Description of the procedures used in each embodiment] Next, the procedures used in each embodiment will be described. The procedures used in each embodiment include the registration procedure, the Network Slice-Specific Authentication and Authorization procedure, the GenericUE configuration update procedure, and the Network-initiated de-registration procedure. Each procedure will be described below. 【0182】 In each embodiment, the explanation will be based on the example where the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software), as shown in Figure 2. However, the contents described in this embodiment are also applicable when 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 them, 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. 【0183】 [3.2. Registration Procedure] First, the registration procedure will be explained using Figure 6. Hereafter, "this procedure" refers to the registration procedure. The registration procedure is a procedure in which the UE takes the lead in registering with access network_B and / or core network_B and / or DN. The UE can execute this procedure at any time, for example, when power is turned on, if it is not registered with the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (5GMM-DEREGISTERED state). In addition, each device (especially the UE and AMF) can transition to the registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. Note that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state for 3GPP access (registered state or unregistered state) and the registration state for non-3GPP access. 【0184】 Furthermore, the registration procedure may also be a procedure for updating the location registration information of the UE in the network, and / or for the UE to periodically notify the network of the status of the UE, and / or for updating specific parameters related to the UE in the network. 【0185】 A UE may initiate the registration process when it moves across a Tracking Area (TA). In other words, a UE may initiate the registration process when it moves to a TA different from the TA indicated in its TA list (TAI list or registration area). Furthermore, a UE may initiate this process when a running backoff timer or other timer expires. Furthermore, a UE may initiate the registration process when it is necessary to update the context of each device due to a PDU session disconnection or invalidation. Furthermore, a UE may initiate the registration process when there is a change in the capability information and / or preferences related to the UE's PDU session establishment. Furthermore, a UE may initiate the registration process periodically. Furthermore, a UE may initiate the registration process based on the completion of a UE configuration update procedure, or the completion of a registration procedure, or the completion of a PDU session establishment procedure, or the completion of a PDU session management procedure, or based on information received from the network in each procedure, or based on the expiration or termination of a backoff timer. Note that a UE can perform the registration process at any time, not limited to these. 【0186】 Furthermore, the procedure for transitioning the UE from a state where it is not registered with the network to a state where it is registered may be called the initial registration procedure or the registration procedure for initial registration, and the registration procedure performed when the UE is registered with the network may be called the registration procedure for mobility and periodic registration update or the mobility and periodic registration procedure. 【0187】 In Figure 6, new AMF141 refers to the AMF to which UE_A10 is registered by this procedure, and oldAMF142 refers to the AMF to which the UE was registered by a procedure prior to this procedure. If no changes to the AMF occur within this procedure, the interface between old AMF142 and new AMF141, and the procedures between old AMF142 and new AMF141 do not occur, and new AMF141 may be the same device as old AMF142. In this embodiment, when referred to as AMF, it may mean new AMF141, old AMF142, or both. Note that new AMF141 and old AMF142 may be AMF140. 【0188】 First, UE_A10 initiates the registration process by sending a Registration request message to new AMF141 (S600)(S602)(S604). Specifically, the UE sends an RRC message containing the Registration request message to the 5G AN120 (or gNB) (S600). The Registration request message is a NAS message sent and received on the N1 interface. The RRC message may be a control message sent and received between the UE and the 5GAN120 (or gNB). The NAS message is processed at the NAS layer, and the RRC message is processed at the RRC layer. The NAS layer is a higher layer than the RRC layer. 【0189】 Here, UE_A10 may include one or more of the first and second identification information in the registration request message and / or RRC message. Furthermore, UE_A10 may include identification information indicating the type of procedure in the registration request message and / or RRC message. Here, the identification information indicating the type of procedure may be 5GS registration type IE and may be information indicating that the procedure is for initial registration, or for updating registration information due to movement, or for periodic updating of registration information, or for emergency registration. 【0190】 UE_A10 may include a registration request message for UE capability information in order to notify the network of the functions that UE_A10 supports. Here, the UE capability information may be 5G MM capability for 5GS. 【0191】 UE_A10 may also transmit this identification information in a different control message, such as a control message at a lower layer than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer). Furthermore, by transmitting this identification information, UE_A10 may indicate that it supports each function, indicate a request from the UE, or both. In addition, if multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Furthermore, the information indicating support for each function and the information indicating a request for the use of each function may be transmitted and received as the same piece of identification information, or as different pieces of identification information. 【0192】 Furthermore, UE_A10 may select and decide whether or not to transmit the first and second identification information to the network based on the UE's capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, etc. 【0193】 UE_A10 may transmit a second identifier if it has the capability to manage the maximum number of UEs connected to a slice, or if it requests at least one S-NSSAI that requires management for managing the maximum number of UEs connected to a slice. By transmitting the second identifier, UE_A10 may notify the network that it has the capability to store the first NSSAI. 【0194】 Furthermore, if UE_A10 has NSSAA functionality, or requests at least one S-NSSAI that identifies slices requiring NSSAA, it may include capability information indicating support for NSSAA functionality in the registration request message. By sending capability information indicating support for NSSAA functionality, UE_A10 may request the network to treat this UE as a UE with NSSAA functionality and to perform authentication and authorization procedures using NSSAA functionality in procedures relating to the UE. 【0195】 If the UE stores "allowed NSSAI associated with the PLMN requested by the UE and the access type requested by the UE," and / or "configured NSSAI for the requested PLMN," and / or "default configured NSSAI," the UE may include the first identification information in the registration request message and send it to the requested PLMN. 【0196】 Alternatively, if the UE stores an "allowed NSSAI associated with a PLMN different from the PLMN requested by the UE and the access type requested by the UE," and the TAI in the registration area associated with that allowed NSSAI or the S-NSSAI contained in that allowed NSSAI belongs to the PLMN requested by the UE, the UE may include the first identification information in the registration request message and send it to the requested PLMN. 【0197】 UE_A10 may determine the information to be included in the first identification information based on one or more NSSAIs stored by the UE. One or more NSSAIs stored by the UE may be, for example, an allowed NSSAI associated with the requested PLMN and the requested access type, and / or a configured NSSAI associated with the requested PLMN, and / or a default configured NSSAI, and / or a rejected NSSAI associated with the requested PLMN. Furthermore / or, one or more NSSAIs stored by the UE may be a pending NSSAI and / or the first NSSAI. 【0198】 Furthermore, / or, one or more NSSAIs stored by the UE may be allowed NSSAIs associated with PLMNs other than those requested by the UE, and the access type and / or access type requested by the UE, and / or a second rejected NSSAI associated with PLMNs other than those requested, and the current registration area. Furthermore, UE_A10 may also store mapped S-NSSAIs of S-NSSAIs contained in each NSSAI stored by the UE. 【0199】 The UE may select one or more S-NSSAIs from the stored allowed NSSAIs and / or configured NSSAIs and include them in the first identification information before transmission. 【0200】 Specifically, if UE_A10 stores an allowed NSSAI associated with the requested PLMN and the requested access type, UE_A10 may transmit the first identifier including that allowed NSSAI, or one or more S-NSSAIs contained within that allowed NSSAI. 【0201】 Furthermore / or, if UE_A10 stores a configured NSSAI associated with a PLMN requested by UE_A10, UE_A10 may transmit the configured NSSAI, or one or more S-NSSAIs contained within the configured NSSAI, in the first identification information. 【0202】 Furthermore, if UE_A10 stores "allowed NSSAI associated with a PLMN other than the requested PLMN and the requested access type," and if the TAIs in the registration area (TAI list) associated with that allowed NSSAI or the S-NSSAI contained in that allowed NSSAI are associated with the requested PLMN, then UE_A10 may transmit the first identification information including that allowed NSSAI or one or more S-NSSAIs contained in that allowed NSSAI. 【0203】 In other words, UE_A10 may include in the first identification information "S-NSSAI included in the allowed NSSAI associated with a registration area and a PLMN other than the requested PLMN" or "S-NSSAI associated with a registration area, included in the allowed NSSAI associated with a PLMN other than the requested PLMN" stored by the UE, and at least one TAI included in this registration area may belong to the first PLMN. 【0204】 The first identification information may consist of one or more of the above-mentioned S-NSSAIs. However, UE_A10 may control the first identification information so that the one or more S-NSSAIs included in it do not overlap. 【0205】 Furthermore, if UE_A10 stores rejected NSSAI for a PLMN requested by UE_A10, UE_A10 may transmit the S-NSSAI included in the rejected NSSAI without including it in the first identification information. 【0206】 Specifically, if UE_A10 stores "a first rejected NSSAI associated with the requested PLMN," UE_A10 may transmit the S-NSSAI included in that first rejected NSSAI without including it in the first identification information. In other words, UE_A10 may perform a control so that one or more S-NSSAIs included in the first identification information are not S-NSSAIs included in "a first rejected NSSAI associated with the requested PLMN" stored by the UE. 【0207】 Furthermore, if UE_A10 stores at least one "second rejected NSSAI associated with the requested PLMN or EPLMN and the current registration area," UE_A10 may transmit the S-NSSAIs included in those second rejected NSSAIs without including them in the first identification information. In other words, UE_A10 may control the first identification information so that one or more S-NSSAIs included are not among the S-NSSAIs included in each "second rejected NSSAI associated with the requested PLMN or EPLMN and the current registration area" that UE_A10 stores. 【0208】 If the information indicating the current registration area stored by UE_A10 includes a TAI belonging to one or more PLMNs different from the requested PLMN, then that one or more different PLMNs are the EPLMNs of the requested PLMN, and UE_A10 may take control to ensure that one or more S-NSSAIs included in the first identification information are not S-NSSAIs included in each "second rejected NSSAI associated with one of those one or more different PLMNs and the current registration area" stored by UE_A10. 【0209】 In other words, if the information that UE_A10 stores indicating the current registration area includes TAIs belonging to one or more PLMNs different from the requested PLMN, UE_A10 does not need to include in the first identification information the S-NSSAI contained in each "second rejected NSSAI associated with one of those different PLMNs, the current registration area, and the PLMN." 【0210】 Furthermore, if UE_A10 stores a "third rejected NSSAI associated with the requested PLMN," UE_A10 may transmit the S-NSSAI included in that third rejected NSSAI without including it in the first identification information. In other words, UE_A10 may perform control such that one or more S-NSSAIs included in the first identification information are not S-NSSAIs included in the "third rejected NSSAI associated with the requested PLMN" stored by UE_A10. 【0211】 Furthermore, if UE_A10 stores at least one "third rejected NSSAI associated with the EPLMN of the requested PLMN", UE_A10 may transmit the S-NSSAI contained in that third rejected NSSAI without including it in the first identifier. In other words, UE_A10 may control the first identifier so that one or more S-NSSAIs included are not among the S-NSSAIs contained in each "third rejected NSSAI associated with the EPLMN of the requested PLMN" stored by UE_A10. 【0212】 Furthermore, if UE_A10 stores a "third rejected NSSAI valid for all PLMNs," UE_A10 may transmit the S-NSSAI contained in that third rejected NSSAI, or the S-NSSAI to which that S-NSSAI is mapped, or the S-NSSAI associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI, without including them in the first identification information. In other words, UE_A10 may perform a control such that one or more S-NSSAIs included in the first identification information are no longer S-NSSAI contained in each "third rejected NSSAI valid for all PLMNs" stored by UE_A10, or the S-NSSAI to which that S-NSSAI is mapped, or the S-NSSAI associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI. Furthermore, "a third rejected NSSAI valid for all PLMNs" may mean a third rejected NSSAI not associated with a PLMN, or a third rejected NSSAI associated with an HPLMN. 【0213】 Furthermore, if the UE stores a "pending NSSAI associated with the requested PLMN," the UE may transmit the S-NSSAI contained in that pending NSSAI without including it in the first identification information. In other words, the UE may control the first identification information so that one or more S-NSSAIs contained in it are not among the S-NSSAIs contained in the "pending associated with the requested PLMN" stored by the UE. 【0214】 Furthermore, if the UE stores at least one pending NSSAI associated with the EPLMN of the requested PLMN, the UE may transmit the S-NSSAI contained in that pending NSSAI without including it in the first identification information. In other words, the UE may control the first identification information so that one or more S-NSSAIs included in it are not S-NSSAIs included in each pending NSSAI associated with the EPLMN of the requested PLMN. 【0215】 Furthermore, if the UE stores a "pending NSSAI valid for all PLMNs," the UE may transmit the S-NSSAI contained in that pending NSSAI, or the S-NSSAI to which that S-NSSAI is mapped, or the S-NSSAI associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI, without including them in the first identification information. In other words, the UE may control the first identification information so that one or more S-NSSAIs contained in each "pending NSSAI valid for all PLMNs," or the S-NSSAI to which that S-NSSAI is mapped, or the S-NSSAI associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI. Note that "pending NSSAI valid for all PLMNs" may mean a pending NSSAI not associated with a PLMN, or a pending NSSAI associated with an HPLMN. 【0216】 Furthermore, UE_A10 may transmit an S-NSSAI, or any S-NSSAI related to that S-NSSAI, without including it in the first identification information if the backoff timer associated with a certain S-NSSAI is active, in other words, while the backoff timer is running, or until the backoff timer is stopped. Specifically, if the S-NSSAI to which the backoff timer is associated is an S-NSSAI associated with the requested PLMN, or an S-NSSAI included in an NSSAI associated with the requested PLMN, UE_A10 may transmit that S-NSSAI without including it in the first identification information while the backoff timer is counting, or until the backoff timer expires or is stopped. Alternatively, if the S-NSSAI to which the backoff timer is associated is associated with an HPLMN, UE_A10 may transmit the S-NSSAI of the requested PLMN to which that S-NSSAI is mapped, without including it in the first identification information. Furthermore, the statement that an S-NSSAI to which a backoff timer is associated is linked to an HPLMN may mean that the backoff timer is valid for all PLMNs, or it may mean that the backoff timer is not associated with any PLMN. 【0217】 Furthermore, if the UE stores a "first NSSAI associated with the requested PLMN," the UE may transmit the S-NSSAI contained in that first NSSAI without including it in the first identification information. In other words, the UE may control the first identification information so that one or more S-NSSAIs contained in it are not S-NSSAIs contained in the "first NSSAI associated with the requested PLMN" that the UE stores. 【0218】 Furthermore, if the UE stores at least one "first NSSAI associated with the EPLMN of the requested PLMN," the UE may transmit the S-NSSAI contained in that first NSSAI without including it in the first identification information. In other words, the UE may control the first identification information so that one or more S-NSSAIs contained in it are not S-NSSAIs contained in each "first NSSAI associated with the EPLMN of the requested PLMN." 【0219】 Furthermore, if the UE stores a "first NSSAI valid for all PLMNs," the UE may transmit the S-NSSAI included in that first NSSAI, or the S-NSSAI to which that S-NSSAI is mapped, without including them in the first identification information. In other words, the UE may control the first identification information so that one or more S-NSSAIs included in each "first NSSAI valid for all PLMNs," or the S-NSSAI to which that S-NSSAI is mapped, are not included in each "first NSSAI valid for all PLMNs." Note that "first NSSAI valid for all PLMNs" may mean a first NSSAI not associated with a PLMN, or a first NSSAI associated with an HPLMN. 【0220】 UE_A10 may include information other than the first and second identification information in the registration request message and / or the RRC message containing the registration request message, for example, the UE ID and / or PLMN ID and / or AMF identification information. Here, the AMF identification information may be information that identifies an AMF or a set of AMFs, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier). 【0221】 Furthermore, UE_A10 may initiate the PDU session establishment procedure during the registration procedure by including an SM message (e.g., a PDU session establishment request message) in the registration request message, or by sending an SM message (e.g., a PDU session establishment request message) together with the registration request message. 【0222】 When a 5G AN120 (or gNB) receives an RRC message containing a registration request message, it selects an AMF to forward the registration request message (S602). The 5G AN120 (or gNB) may select an AMF based on one or more pieces of identification information contained in the registration request message and / or the RRC message containing the registration request message. Specifically, the 5G AN (or gNB) may select a new AMF141 to which the registration request message should be sent based on at least one piece of identification information from the first to the second set of identification information. 【0223】 For example, a 5G AN120 (or gNB) may select an AMF based on the first identification information. Specifically, the 5G AN (or gNB) may select an AMF that is included in or has connectivity to a network slice identified by the S-NSSAI included in the first identification information. 【0224】 Furthermore, for example, the 5G AN120 (or gNB) may, based on the second identification information, select an AMF having a function for managing the maximum number of UEs connected to a slice and / or an AMF having connectivity to a network having a function for managing the maximum number of UEs connected to a slice. 【0225】 Note that the method of selecting an AMF is not limited to this, and a 5G AN (or gNB) may select an AMF based on other conditions. The 5G AN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected new AMF (S604). Note that if at least one of the first to second identification information is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message may be forwarded to the selected AMF (new AMF141) together with the registration request message (S604). 【0226】 When new AMF141 receives a registration request message, it can perform a first condition determination. The first condition determination is to determine whether the network (or newAMF141) accepts the UE's request. If the first condition determination is true, new AMF141 executes procedures S606 to S612. On the other hand, if the first condition determination is false, new AMF141 may not execute procedures S606 to S608 and instead execute procedure S610. 【0227】 Alternatively, new AMF141 may request the UE context from old AMF142 and, after receiving the UE context from old AMF142 (S606, S608), perform the first conditional determination. In that case, if the first conditional determination is true, new AMF141 may execute S610 and / or S612. On the other hand, if the first conditional determination is false, new AMF141 may execute S610. 【0228】 Furthermore, if the first condition is true, the control message transmitted and received in S610 may be a Registration accept message, and if the first condition is false, the control message transmitted and received in S610 may be a Registration reject message. 【0229】 Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or the identification information contained in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF, etc. 【0230】 For example, if the network permits the UE's request, the first conditional determination is true; if the network does not permit the UE's request, the first conditional determination may be false. Also, if the network to which the UE is registered, and / or the devices within the network, support the function requested by the UE, the first conditional determination is true; if they do not support the function requested by the UE, the first conditional determination may be false. Furthermore, if the transmitted and received identification information is permitted, the first conditional determination is true; if the transmitted and received identification information is not permitted, the first conditional determination may be false. 【0231】 Furthermore, the first condition may be true if the S-NSSAI included in the requested NSSAI received by the UE by the AMF identifies a slice that requires an NSSAA procedure, and the AMF also remembers that the NSSAA procedure for the corresponding S-NSSAI was successful. Alternatively, the first condition may be false if there is no S-NSSAI to allow the UE and there are no plans to assign an allowedNSSAI to the UE in the future. 【0232】 Furthermore, if the S-NSSAI included in the requested NSSAI received by the AMF from the UE identifies a slice that requires management of the maximum number of UEs connected to that slice, and the maximum number of UEs has not been reached, then the first condition may be true. Alternatively, even if there is no S-NSSAI to allow the UE, the first condition may be true if it is expected that an allowed NSSAI will be assigned to the UE in the future. 【0233】 If AMF assigns a first NSSAI to a UE when there is no S-NSSAI to authorize the UE, the first conditional determination may be true or false. 【0234】 If the AMF identified in the AMF identifier included in the message received by new AMF141 from UE is old AMF142, procedures S606 and S608 are executed. If the AMF identified in the AMF identifier included in the message received by new AMF141 from UE_A10 is new AMF141, procedures S606 and S608 are not executed. In other words, if an AMF change occurs as a result of this procedure, procedures S606 and S608 are executed; if no AMF change occurs, procedures S606 and S608 are skipped. 【0235】 The UE context transfer procedure (S606, S608) is described below. The new AMF141 sends a UE context request message to the old AMF142 (S606). Based on the received UE context request message, the old AMF142 sends the UE context to the new AMF141. The new AMF141 generates the UE context based on the received UE context. 【0236】 Here, the UE context sent from new AMF141 to old AMF142 may include the UE ID and allowedNSSAI. Furthermore, the UE context may include configuredNSSAI and / or rejected NSSAI, NSSAI and / or pendingNSSAI, and / or the first NSSAI. In addition, the allowed NSSAI and / or configuredNSSAI and / or rejected NSSAI and / or pending NSSAI and / or the first NSSAI included in the UE context, and the S-NSSAI included in each NSSAI, may be associated with information indicating whether or not notification to the UE has been completed. 【0237】 Furthermore, the UE context may include information about S-NSSAIs that require NSSAA procedures, and / or information indicating that authentication was successful, that the NSSAA procedures have been completed for the UE, and / or information indicating that authentication failed. 【0238】 Furthermore, the UE context may include information about S-NSSAI that requires management of the maximum number of UEs connected to a slice, and / or information indicating that the maximum number of UEs has been reached, and / or information indicating whether or not the maximum number of UEs connected to a slice has been reached. 【0239】 Furthermore, information regarding the characteristics of these S-NSSAIs may be managed as a single piece of information. Specifically, the network may store associated information for each S-NSSAI indicating whether or not NSSAA is required, whether or not NSSAA was successful, whether or not management of the maximum number of UEs connected to a slice is required, and whether or not the maximum number of UEs connected to a slice has been reached. 【0240】 The new AMF141 may send a control message to the UE based on the decision of the first condition determination and / or based on the receipt of the UE context from the old AMF142 (S610). The control message may be a registration acceptance message or a registration rejection message. 【0241】 The new AMF141 may include one or more of the 10th identification information in the control message. Alternatively, the new AMF141 may include one or more of the 10th to 15th identification information in the control message. By transmitting this identification information and / or the control message, the new AMF141 may indicate that the network supports each function, that the UE's request has been accepted, that the request from the UE has not been permitted, or a combination of these. Furthermore, if multiple identification information is transmitted and received, two or more of these identification information may be configured as one or more identification information. 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 as different identification information. 【0242】 When the new AMF141 receives the first and / or second identification information from the UE, it may include at least one of the identification information items 10 to 15 in the control message and send it. 【0243】 Furthermore, the new AMF141 may transmit at least one of the identification information from the 10th to the 15th when there is an update to the UE's configuration information. 【0244】 The new AMF141 may also send a configuredNSSAI and / or allowed NSSAI and / or rejected NSSAI and / or pending NSSAI and / or a first NSSAI to UE_A10 in the control message. 【0245】 The identification information of items 10 to 15 may be included in and transmitted in the allowed NSSAI and / or rejected NSSAI and / or pending NSSAI and / or the first NSSAI, or in these NSSAIs. 【0246】 When sending a control message, the new AMF141 does not have an S-NSSAI (allowed NSSAI) to allow the UE, but if it plans to perform an NSSAA procedure after or in parallel with this procedure, or if an NSSAA procedure is currently being performed between the UE and the network, or if it sends a pending NSSAI in the control message, it may send an empty value for allowed NSSAI. 【0247】 When sending a control message, the new AMF141 does not have an S-NSSAI (allowed NSSAI) to authorize the UE, but if it includes a 10th identification piece in the control message, or if it has already notified the UE of the first NSSAI before this procedure, it may include an empty value in the allowed NSSAI and send it. 【0248】 If the control message includes a 13th identifier indicating that the new AMF141 applies to all PLMNs, it may also include a 15th identifier in the control message. 【0249】 UE_A10 receives a control message and / or one or more pieces of identification information from the 10th to 15th from the network. More specifically, the UE receives a control message and / or one or more pieces of identification information from the 10th to 15th from newAMF141. 【0250】 UE_A10 may recognize the received information based on the receipt of at least one of the identification information from the 10th to the 15th. Specifically, UE_A10 may recognize that the transmission of MM messages and / or SM messages using S-NSSAI related to the S-NSSAI indicated by the 10th identification information and / or the S-NSSAI indicated by the 14th identification information and / or the mapped S-NSSAI indicated by the 15th identification information is temporarily prohibited because the maximum number of UEs connected per slice has been reached. Note that the MM procedure may be a registration request message, and the SM message may be a PDU session establishment request message. 【0251】 Based on the reception of at least one of the identification information items 10 to 15, and / or a control message, UE_A10 may perform the following operations for each of the 10th identification information items: 【0252】 UE_A10 may store S-NSSAIs related to the S-NSSAI indicated by the 10th identification information, and / or the S-NSSAI indicated by the 14th identification information, and / or the mapped S-NSSAI indicated by the 15th identification information, in an appropriate first NSSAI. Specifically, the UE may add the received S-NSSAI indicated by the 14th identification information to the first NSSAI associated with the information indicated by the 11th identification information, and / or the 13th identification information. 【0253】 Alternatively, UE_A10 may add the mapped S-NSSAI indicated by the received 15th identification information to the first NSSAI, or add the S-NSSAI relating to the mapped S-NSSAI indicated by the received 15th identification information to the first NSSAI associated with the current PLMN, or add it to the first NSSAI associated with the current PLMN and the current access type (registered access type, 3GPP access or non-3GPP access), or add it to the first NSSAI associated with the current PLMN and all access types. 【0254】 Furthermore, if an S-NSSAI contained in the first NSSAI stored by the UE is also contained in an allowed NSSAI stored by the UE and associated with the PLMN, access type, and other access types requested by the UE in this procedure, the S-NSSAI may be removed from the allowed NSSAI. 【0255】 Furthermore, if UE_A10 receives the 15th identification information, it may store the S-NSSAI indicated by the 15th identification information as the mapped S-NSSAI of the S-NSSAI indicated by the 14th identification information. 【0256】 If the received 13th identification information indicates that it applies to all PLMNs, the UE may remove the S-NSSAI associated with the mapped S-NSSAI indicated by the 15th identification information from the allowed NSSAI corresponding to PLMNs other than the current PLMN. 【0257】 UE_A10 may recognize, based on the reception of the 10th identification information and / or the 11th identification information and / or the reception of a control message, that the S-NSSAI indicated in the 10th identification information has reached the maximum number of UEs connected per slice. Here, the S-NSSAI indicated in the 10th identification information may be the S-NSSAI indicated in the 14th identification information and / or the mapped S-NSSAI indicated in the 15th identification information. 【0258】 UE_A10 may, based on the reception of at least one piece of identification information from the 10th to 15th pieces of information and / or the reception of a control message, use the received value of the backoff timer to count or start the backoff timer associated with the S-NSSAI, or manage the backoff timer. Here, the value of the backoff timer may be the value of the timer indicated in the 10th piece of identification information and / or the 12th piece of identification information, and the S-NSSAI may be the S-NSSAI indicated in the 1st piece of identification information and / or the 10th piece of identification information and / or the 14th piece of identification information and / or the mapped S-NSSAI indicated in the 15th piece of identification information. 【0259】 While the backoff timer is running, UE_A10 may be in a state where it is prohibited from sending MM messages and SM messages using S-NSSAI associated with the backoff timer, or mapped S-NSSAI (HPLMN S-NSSAI) associated with the backoff timer, or S-NSSAI related to mapped S-NSSAI associated with the backoff timer. 【0260】 Furthermore, if UE_A10 receives the 13th identification information, it may apply a backoff timer according to the valid range indicated in the 13th identification information. 【0261】 Specifically, if the 13th identification information indicates that it applies within the current PLMN, UE_A10 may apply the backoff timer within the current PLMN. Specifically, in the event of a PLMN change, UE_A10 does not have to count or stop the backoff timer, but the restrictions imposed by the backoff timer associated with the previous PLMN may be released. In other words, if the PLMN is changed, the UE maintains the backoff timer, but the restrictions imposed on the previous PLMN may be released. 【0262】 Alternatively, UE_A10 may, in response to a change in the PLMN, stop counting or stopping the backoff timer associated with the current PLMN. In other words, if the PLMN is changed, UE_A10 may stop the backoff timer, and any restrictions on the PLMN before the move may be released. 【0263】 Alternatively, if the 13th identification information indicates that it applies to all PLMNs, UE_A10 may apply the backoff timer to all PLMNs. In other words, UE_A10 may maintain the backoff timer even if a change occurs in the PLMN, instead of stopping it. If a change occurs in the PLMN while the backoff timer is running, UE_A10 may maintain a state where MM messages and SM messages using the S-NSSAI of the destination PLMN associated with the mapped S-NSSAI of the S-NSSAI to which the backoff timer was associated, or the S-NSSAI of the destination PLMN associated with the mapped S-NSSAI, or the mapped S-NSSAI, are prohibited. 【0264】 Alternatively, if the 13th identification information indicates that it applies in the current registration area, UE_A10 may apply the backoff timer in the current registration area. In other words, as UE_A10 leaves the registration area, UE_A10 may start counting or stop the backoff timer. 【0265】 Furthermore, UE_A10 may manage and / or store the first NSSAI or one or more S-NSSAIs contained in the first NSSAI that are associated with the 11th identification information and / or the 13th identification information. 【0266】 Here, upon the stop or expiration of the backoff timer, the restriction may be lifted, and UE_A10 may transition to a state in which it can send MM messages and SM messages using the S-NSSAI to which the backoff timer was associated, and / or the S-NSSAI related to the mapped S-NSSAI to which the backoff timer was associated, and / or the mapped S-NSSAI to which the backoff timer was associated. In other words, upon the stop or expiration of the backoff timer, UE_A10 may transition to a state in which it can send MM messages using the S-NSSAI to which the backoff timer was associated, and / or the S-NSSAI related to the mapped S-NSSAI to which the backoff timer was associated, and / or the mapped S-NSSAI to which the backoff timer was associated, as the requested NSSAI. 【0267】 Furthermore, upon the stop or expiration of the backoff timer, UE_A10 may transition to a state in which it can send MM messages using the NSSAI associated with the backoff timer. In other words, upon the stop or expiration of the backoff timer, UE_A10 may transition to a state in which it can send MM messages using the NSSAI associated with the backoff timer as the requested NSSAI. 【0268】 Furthermore, upon the termination or expiration of the backoff timer, UE_A10 may delete from the first NSSAI the S-NSSAI to which the backoff timer was associated, or the mapped S-NSSAI to which the backoff timer was associated, or the S-NSSAI associated with the mapped S-NSSAI to which the backoff timer was associated. 【0269】 Specifically, if a backoff timer is enabled for a registered PLMN, upon the termination or expiration of the backoff timer, UE_A10 may delete from the first NSSAI associated with the current PLMN the S-NSSAI to which the backoff timer was associated, or the mapped S-NSSAI to which the backoff timer was mapped, or the S-NSSAI associated with the mapped S-NSSAI to which the backoff timer was mapped. 【0270】 Furthermore, if a backoff timer is enabled for a registered PLMN, upon the termination or expiration of the backoff timer, UE_A10 may remove from the first NSSAI applicable to all PLMN the S-NSSAI to which the backoff timer was associated, or the mapped S-NSSAI to which the backoff timer was mapped, or the S-NSSAI associated with the mapped S-NSSAI to which the backoff timer was mapped. 【0271】 Alternatively, if the backoff timer is enabled for all PLMNs, upon the termination or expiration of the backoff timer, UE_A10 may remove from the first NSSAI applicable to all PLMNs the S-NSSAI to which the backoff timer was associated, or the mapped S-NSSAI to which the backoff timer was mapped, or the S-NSSAI associated with the mapped S-NSSAI to which the backoff timer was mapped. 【0272】 Furthermore, if the backoff timer is enabled for all PLMNs, upon the termination or expiration of the backoff timer, the S-NSSAI to which the backoff timer was associated, or the mapped S-NSSAI to which the backoff timer was mapped, or the S-NSSAI associated with the mapped S-NSSAI to which the backoff timer was mapped, may be deleted from the first NSSAI applied to each PLMN. 【0273】 In other words, if an S-NSSAI to which the backoff timer is associated, or a mapped S-NSSAI to which the backoff timer was associated, or an S-NSSAI associated with a mapped S-NSSAI to which the backoff timer was associated, is included in multiple first NSSAIs and stored in UE_A10, UE_A10 may delete the corresponding S-NSSAI from all of the corresponding first NSSAIs. 【0274】 Specifically, for example, if backoff timer #1 associated with S-NSSAI#1 was managed as being enabled for all PLMNs, upon the termination or expiration of backoff timer #1, the UE may remove S-NSSAI#1 from the first NSSAI#1 associated with PLMN#1, and further remove S-NSSAI#2 associated with the mapped S-NSSAI of S-NSSAI#1 from the first NSSAI#2 associated with PLMN#2. 【0275】 Furthermore, if UE_A10 receives a TAI list, it may activate the received TAI list. If UE_A10 already has a valid TAI list stored, it may delete or invalidate the old TAI list. Hereafter, a valid TAI list may be referred to as a registration area. Note that if UE_A10 does not have a valid TAI list stored and does not receive a TAI list from the core network during this procedure, a valid TAI list may not be stored. 【0276】 Furthermore, UE_A10 may appropriately store each NSSAI it receives. Specifically, when UE_A10 receives a configured NSSAI, it may store the received configured NSSAI as the "configured NSSAI associated with the current PLMN". In other words, UE_A10 may replace the "configured NSSAI associated with the current PLMN stored by UE_A10" with the "received configured NSSAI". 【0277】 Furthermore, if UE_A10 receives a configured NSSAI, it may delete the mapped S-NSSAI of the S-NSSAI included in "the configured NSSAI associated with the current PLMN stored by UE_A10". Furthermore, if "the received configured NSSAI" contains one or more mapped S-NSSAIs, UE_A10 may store those one or more mapped S-NSSAIs. 【0278】 Furthermore, if UE_A10 receives a configured NSSAI, it may delete the "rejected NSSAI that UE_A10 has stored and associated with the current PLMN." 【0279】 Alternatively, if UE_A10 receives a configured NSSAI, it may delete at least one of the following: "the first rejected NSSAI stored by UE_A10 and associated with the current PLMN", "the second rejected NSSAI stored by UE_A10 and associated with the current PLMN", and "the third rejected NSSAI stored by UE_A10 and associated with the current PLMN". 【0280】 Furthermore, when UE_A10 receives a configured NSSAI, it may delete the "first NSSAI stored by UE_A10", and / or the "first NSSAI stored by UE_A10 and associated with the current PLMN", and / or one or more "first NSSAIs stored by UE_A10 and associated with the EPLMN of the current PLMN". 【0281】 Furthermore, when UE_A10 receives a configured NSSAI, it may delete the "pending NSSAI stored by UE_A10", and / or the "pending NSSAI stored by UE_A10 and associated with the current PLMN", and / or one or more "first pending NSSAIs stored by UE_A10 and associated with the EPLMN of the current PLMN". 【0282】 Furthermore, when UE_A10 receives an allowed NSSAI, it may store the received allowed NSSAI as the "allowed NSSAI associated with the current PLMN and the current access type". That is, UE_A10 may replace the "allowed NSSAI associated with the current PLMN and the current access type" stored by UE_A10 with the "received allowed NSSAI". 【0283】 Furthermore, when UE_A10 receives a TAI list and an allowed NSSAI from new AMF141, and if at least one TAI included in the TAI list belongs to the EPLMN, UE_A10 may store the received allowed NSSAI as the "allowed NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs and the current access type". 【0284】 Alternatively, if UE_A10 does not receive a TAI list but receives an allowed NSSAI from new AMF141, and further if the TAI included in the TAI list that the UE previously received and stored belongs to an EPLMN, UE_A10 may store the received allowed NSSAI as "the allowed NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs, and the current access type". 【0285】 That is, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, and those one or more different PLMNs are EPLMNs, UE_A10 may store the "received allowed NSSAI" as "one allowed NSSAI associated with one of those one or more different PLMNs and the current access type". 【0286】 In other words, UE_A10 may store the "received allowed NSSAI" as "the allowed NSSAI associated with the PLMN to which the TAI included in the registration area stored by UE_A10 belongs and the current access type". 【0287】 Furthermore / or, if the multiple TAI included in the registration area stored by UE_A10 belong to different PLMNs respectively, UE_A10 may replace the "received allowed NSSAI" with "the allowed NSSAI associated with each PLMN to which the TAI included in each registration area stored by UE_A10 belongs and the current access type". 【0288】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "received allowed NSSAI" as "allowed NSSAI#1 associated with PLMN#1 and the current access type" and "allowed NSSAI#2 associated with PLMN#2 and the current access type". 【0289】 Alternatively, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, and those one or more PLMNs are EPLMNs, UE_A10 may store the "received allowed NSSAI" in "one allowed NSSAI associated with the one or more PLMNs to which the TAI included in the registration area belongs, the current access type, and the current access type." 【0290】 Furthermore / or, if two or more TAIs included in the registration area belong to multiple PLMNs, UE_A10 may replace the "one or more PLMNs to which the TAIs included in the registration area belong, and the current access type, and one allowed NSSAI" stored in UE_A10 with the "received allowed NSSAI". 【0291】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#1 which is an EPLMN, then UE_A10 may store the "received allowed NSSAI" in "allowed NSSAI#1 associated with PLMN#1, PLMN#2, and the current access type." 【0292】 Alternatively, if the TAIs included in the registration area stored by UE_A10 belong to one or more PLMNs different from the RPLMN, and those one or more PLMNs are EPLMNs, then UE_A10 may store the "received allowed NSSAI" only as "one allowed NSSAI associated with the RPLMN and the current access type." In other words, even if the TAIs included in the registration area stored by UE_A10 belong to one or more PLMNs different from the RPLMN, UE_A10 does not have to store the "received allowed NSSAI" as an allowed NSSAI associated with those one or more PLMNs. 【0293】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may replace the "one allowed NSSAI associated with the RPMMN and the current access type" stored in UE_A10 with the "received allowed NSSAI". 【0294】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#1 which is an EPLMN, then UE_A10 may store the "received allowed NSSAI" only in "allowed NSSAI#1 associated with PLMN#1 and the current access type." 【0295】 Furthermore, when UE_A10 stores an allowed NSSAI, it may store the allowed NSSAI in association with a registration area, or it may store the S-NSSAI included in the allowed NSSAI in association with a registration area. 【0296】 Furthermore, if UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSAI of the S-NSSAI included in the "allowed NSSAI deleted based on reception" or the "older allowed NSSAI updated based on reception". Furthermore, if the "received allowed NSSAI" includes mapped S-NSSAI, UE_A10 may store one or more of those mapped S-NSSAI. 【0297】 Furthermore, if UE_A10 receives an allowed NSSAI, it may delete any rejected NSSAIs that UE_A10 has stored and associated with the current PLMN. 【0298】 Specifically, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI contained in the received allowed NSSAI from at least one of the following: "the first rejected NSSAI stored by UE_A10 and associated with the current PLMN", "the second rejected NSSAI stored by UE_A10 and associated with the current PLMN", "the second rejected NSSAI stored by UE_A10 and associated with the current PLMN and the current registration area", and "the third rejected NSSAI stored by UE_A10 and associated with the current PLMN", or it may delete the S-NSSAI contained in the received allowed NSSAI from all NSSAI. 【0299】 Specifically, if UE_A10 receives an allowed NSSAI, it may further delete the S-NSSAI associated with the current registration area and included in the further received allowed NSSAI from "the second rejected NSSAI that UE_A10 has stored and associated with the current PLMN". 【0300】 Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMNs". Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0301】 Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Alternatively, if UE_A10 receives an allowed NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." 【0302】 Furthermore, if UE_A10 receives a rejected NSSAI, it may store the S-NSSAI contained in the received rejected NSSAI as "rejected NSSAI associated with the current PLMN" based on the rejection reason value to which the S-NSSAI is associated. In other words, UE_A10 may add "the S-NSSAI contained in the received rejected NSSAI" to "rejected NSSAI associated with the current PLMN" that UE_A10 stores. 【0303】 Specifically, when UE_A10 receives a rejection reason value of "S-NSSAI not allowed in the current PLMN or SNPN" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to the first rejected NSSAI associated with the current PLMN. 【0304】 Furthermore, when UE_A10 receives a rejection reason value of "S-NSSAI not allowed in the current registration area" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the "received rejected S-NSSAI" to the second rejected NSSAI associated with the current PLMN and the current registration area. 【0305】 Note that when UE_A10 receives a TAI list together with the rejected NSSAI, the current registration area is indicated by the received TAI list. On the other hand, when UE_A10 does not receive a TAI list together with the rejected NSSAI, the current registration area is indicated by the TAI list that UE_A10 received and remembered last time. 【0306】 If the TAI included in the current registration area remembered by UE_A10 belongs to one or more PLMNs different from the RPLMN, the one or more different PLMNs are EPLMNs, and UE_A10 may store and / or add the "rejected S-NSSAI received in association with the rejection reason value 'S-NSSAI not allowed in the current registration area'" to the second rejected NSSAI associated with one of the one or more different PLMNs and the current registration area. 【0307】 Furthermore / or, if one or more TAIs included in a registration area belong to different PLMNs, UE_A10 may store, in addition to each "second rejected NSSAI associated with each PLMN to which a TAI included in a registration area belongs, the current access type, and the "rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" for each "rejected NSSAI associated with each PLMN to which a TAI included in a registration area belongs, and the current access type" that UE_A10 stores. 【0308】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "second rejected S-NSSAI received" as "second rejected NSSAI#1 associated with PLMN#1 and the current registration area" and "second rejected NSSAI#2 associated with PLMN#2 and the current registration area". 【0309】 Alternatively, if the TAI included in the registration area belongs to one or more PLMNs different from the RPLMN, those one or more PLMNs are EPLMNs, and UE_A10 may store the "rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" in "one second rejected NSSAI associated with that one or more PLMNs and the current registration area." 【0310】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may store "a rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" in addition to "a second rejected NSSAI associated with those multiple PLMNs and the current access type" that UE_A10 stores. 【0311】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "received second rejected S-NSSAI" in "the second rejected NSSAI#1 associated with PLMN#1, PLMN#2, and the current registration area." 【0312】 Furthermore, if a TAI included in the TAI list indicating the current registration area belongs to an EPLMN, UE_A10 may store the S-NSSAI associated with the received rejection reason value "S-NSSAI that is not allowed in the current registration area" as "a second rejected NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs, and the current access type." 【0313】 Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, then that one or more PLMNs is an EPLMN, and UE_A10 may store the "received second rejected S-NSSAI" only as "one second rejected NSSAI associated with the RPLMN and the current access type." In other words, even if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, UE_A10 does not have to store the "received second rejected S-NSSAI" as a second rejected NSSAI associated with that one or more PLMNs. 【0314】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may replace the "one second rejected NSSAI associated with the RPMMN and the current access type" stored in UE_A10 with the "second rejected S-NSSAI received". 【0315】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#1 which is an EPLMN, then UE_A10 may store and / or add the "received second rejected S-NSSAI" only to "the second rejected NSSAI#1 associated with PLMN#1 and the current access type." 【0316】 Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI is not possible due to NSSAA failure or revocation" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to a third rejected NSSAI associated with the current PLMN. 【0317】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "allowed NSSAIs that UE_A10 stores and associates with the current PLMN". 【0318】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0319】 Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Alternatively, if UE_A10 receives an allowed NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." 【0320】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0321】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with EPLMN." 【0322】 Furthermore, each process performed by the UE based on the receipt of each piece of identification information as described above may be performed during or after this procedure, or after this procedure is completed, based on the completion of this procedure. 【0323】 Furthermore, AMF may select and decide which of the identification information items 10 to 15 to include in the control message based on each received identification information item, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF. 【0324】 Furthermore, if the control message is a registration acceptance message, the AMF may send the registration acceptance message with an SM message (e.g., a PDU session establishment acceptance message), or send the SM message (e.g., a PDU session establishment acceptance message) together with the registration acceptance message. However, this method of sending may be performed only if the registration request message contains an SM message (e.g., a PDU session establishment request message). This method of sending may also be performed if the SM message (e.g., a PDU session establishment request message) is sent together with the registration request message. By performing such a method of sending, the AMF can indicate that the procedure for the SM has been accepted in the registration procedure. 【0325】 Furthermore, based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF, the AMF may indicate that the UE's request has been accepted by sending an acceptance message, or it may indicate that the UE's request has been rejected by sending a rejection message. 【0326】 The UE receives a control message via the 5G AN (gNB) (S608). If the control message is an acceptance message, the UE can recognize that its request via the registration request message has been accepted and the contents of the various identification information contained in the acceptance message. Alternatively, if the control message is a rejection message, the UE can recognize that its request via the registration request message has been rejected and the contents of the various identification information contained in the rejection message. Furthermore, if the UE does not receive a control message after a predetermined period has elapsed since sending the registration request message, it may recognize that its request has been rejected. 【0327】 Furthermore, if the control message is a registration acceptance message, the UE may send a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S610). If the UE receives an SM message such as a PDU session establishment acceptance message, it may also include the SM message, such as a PDU session establishment completion message, in the registration completion message, or it may include the SM message to indicate that the procedure for the SM has been completed. Here, the registration completion message is a NAS message sent and received on the N1 interface, but it is included in the RRC message sent and received between the UE and the 5GAN (gNB). 【0328】 The AMF receives a registration completion message via 5G AN(gNB) (S612). Each device completes this procedure based on the sending and receiving of a registration acceptance message and / or registration completion message. 【0329】 Alternatively, each device may complete the registration process based on the sending and receiving of registration rejection messages. 【0330】 Furthermore, each device may transition to or maintain a state in which the UE is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of registration acceptance messages and / or registration completion messages, or may transition to or maintain a state in which the UE is not registered with the network on the access for which a registration rejection message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending and receiving of registration rejection messages. In addition, each device may transition to each state based on the sending and receiving of registration completion messages or the completion of the registration procedure. 【0331】 Furthermore, each device may perform processing based on the information sent and received during the registration process, upon completion of the registration procedure. For example, if it receives information indicating that some of the UE's requests were rejected, it may recognize the reason why the UE's requests were rejected. Furthermore, each device may perform the procedure again based on the reason why the UE's requests were rejected, or it may perform the registration procedure for core network_A or another cell. 【0332】 Furthermore, based on the completion of the registration process, the UE may store the identification information received along with the registration acceptance message and / or registration rejection message, and may recognize the network's decision. 【0333】 Furthermore, UE may delete one or more stored NSSAIs based on the completion of the registration procedure. Specifically, if UE_A10 transitions to an unregistered state on both accesses (3GPP access and non-3GPP access) to the current PLMN based on the completion of this procedure, UE_A10 may delete the first rejectedNSSAI and / or the third rejected NSSAI and / or the first NSSAI that it stores. 【0334】 Furthermore, upon completion of this procedure, if UE_A10 transitions to an unregistered state on certain access (3GPP access and non-3GPP access) to the current PLMN, or if UE_A10 successfully completes the registration procedure in a new registration area, or if UE_A10 transitions to an unregistered or registered state on certain access as a result of performing the registration procedure in a new registration area, UE_A10 may delete the second rejected NSSAI associated with the current PLMN, the current registration area, and / or its access type. 【0335】 Furthermore, each device may restart the registration process based on the expiration or termination of the backoff timer. 【0336】 Furthermore, each device may restart the registration process based on updates to its stored NSSAI. 【0337】 Furthermore, each device may initiate an SM procedure by sending or receiving an SM message based on the transition or maintenance of the UE to a state in which it is registered with the network (RM_REGISTEREDstate or 5GMM-REGISTERED state). 【0338】 [3.3. Network Slice-Specific Authentication and Authorization Procedures] Next, the Network Slice-Specific Authentication and Authorization (NSSAA) procedure will be explained using Figure 7. Hereinafter, the NSSAA procedure will also be referred to as this procedure. This procedure may be a procedure for the core network to perform authentication and authorization procedures for UEs for slices that require the NSSAA procedure. Here, the authentication procedure and authorization procedure may be a re-authentication procedure and a re-authorization procedure. 【0339】 This procedure is performed by PLMN and may be performed for each S-NSSAI (mapped S-NSSAI) and / or UE that is subject to the NSSAA procedure. This procedure may be performed after the registration procedure is complete. 【0340】 This procedure may be initiated by AMF140. For example, AMF140 may initiate this procedure based on the receipt of a registration request message from UE_A10. AMF140 may initiate this procedure if it remembers that at least one S-NSSAI or mapped S-NSSAI of an S-NSSAI requested by UE_A10 is an S-NSSAI that requires an NSSAA procedure, and further remembers the result of the NSSAA for that S-NSSAI. Here, the result of the NSSAA may be information indicating that the NSSAA was successful, information indicating that the NSSAA was unsuccessful, or both. Furthermore, information indicating that the NSSAA was successful may be an allowed NSSAI. In other words, if an S-NSSAI was remembered as an allowed NSSAI, AMF140 may recognize that the NSSAA for that S-NSSAI was successful and may retain the result of the NSSAA. 【0341】 Alternatively, AMF140 may initiate this procedure based on a request from AAA-S181. For example, if AMF140 and / or NW are managing an S-NSSAI that is an allowed NSSAI based on the results of an already executed NSSAA procedure, and AAA-S181 requests that an NSSAA be performed again on the S-NSSAI, AMF may initiate this procedure based on a request from AAA-S181. In this case, this procedure may be an NSSAA procedure initiated by AAA-S. 【0342】 The procedure is described below. The AMF140 sends an EAP ID request message to UE_A10 via 5G AN (or gNB or non-3GPP access) (S700). The EAP ID request message may be sent as part of an Authentication request message, which is a NAS message, or as an Authentication request message, which is a NAS message. Note that the Authentication request message, which is a NAS message, may also be a 5GS NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message. The AMF140 sends the EAP ID request message or the Authentication request message containing the EAP ID request message, including one or more S-NSSAIs corresponding to this EAP ID request message. Here, the S-NSSAI may be an HPLMN S-NSSAI or a mapped S-NSSAI. 【0343】 Based on the transmission of the EAP ID request message, AMF140 requests one or more EAP IDs from UE_A10 as identification information for the UE to be used to perform NSSAA on one or more S-NSSAIs. 【0344】 Based on the receipt of an EAP ID request message and / or an S-NSSAI and / or an authentication request message, UE_A10 sends an EAP ID response message to AMF140 (S702). The EAP ID response message may be sent as part of an authentication response message (which is a NAS message), or as an authentication response message (which is a NAS message). The authentication response message (which is a NAS message) may be a 5GS NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message. UE_A10 may include the S-NSSAI received from AMF140 in the EAP ID response message or the authentication request message containing the EAP ID response message. UE_A10 may include the EAP ID, which is the identification information of the UE corresponding to the S-NSSAI received from AMF140, in the EAP ID response message. Furthermore, UE_A10 may include multiple EAP IDs and multiple S-NSSAIs in the EAP ID response message, and each EAP ID and each S-NSSAI may be associated and transmitted together. 【0345】 Based on receiving an EAP ID response message and / or an authentication response message which is an EAPID and / or NAS message from UE_A10, AMF140 sends an NSSAA authentication request message to AAA-S181 via AUSF180 (S704, S706). AM140F may include the EAP ID response message received from UE_A10 in the NSSAA authentication request message and send it to AUSF180 and / or AAA-S181, or it may include the EAP ID and / or S-NSSAI contained in the EAP ID response message received from UE_A10 in the NSSAA authentication request message and send it to AUSF180 and / or AAA-S181. 【0346】 The NSSAA authentication request message sent from AMF140 to AUSF180 and the NSSAA authentication request message sent from AUSF180 to AAA-S181 may be the same message or different messages. Specifically, AUSF180 may forward the NSSAA authentication request message received from AMF140 to AAA-S181, or it may include the EAP ID and / or S-NSSAI contained in the authentication request message received from AMF140 in the NSSAA authentication request message and send it to AAA-S181. 【0347】 Based on the receipt of the NSSAA authentication request message and / or at least one piece of information contained in the NSSAA authentication request message, AAA-S181 may initiate the exchange of messages necessary for authentication between UE_A10 and AAA-S181 (S708). The messages used in the message exchange procedure between AAA-S181 and UE_A10 may be EAP messages. 【0348】 Next, AAA-S181 sends an NSSAA authentication response message to AMF140 via AUSF180 as a response to the authentication request message received from AMF140 (S710, S712). 【0349】 The NSSAA authentication response message sent from AAA-S181 to AUSF180 and the NSSAA authentication response message sent from AUSF180 to AMF140 may be the same message or different messages. Specifically, AUSF180 may forward the NSSAA authentication response message received from AAA-S181 back to AAA-S181, or it may include the authentication result and / or S-NSSAI contained in the authentication response message received from AAA-S181 in the NSSAA authentication response message and send it to AMF140. 【0350】 AUSF180 sends the authentication result and S-NSSAI in the NSSAA authentication response message. Here, the authentication result may be information indicating success or failure. Here, the S-NSSAI included in the NSSAA authentication response message may be the HPLMN S-NSSAI or the mapped S-NSSAI. Based on the receipt of the NSSAA authentication response message, AMF140 sends an authentication result message to UE_A10 (S714). AMF140 may send the authentication result message including the NSSAA authentication response message, or the authentication result and S-NSSAI included in the NSSAA authentication response message. 【0351】 The authentication result message may be a 5GS NETWORKSLICE-SPECIFIC AUTHENTICATION RESULT message, or it may be included in the NETWORKSLICE-SPECIFIC AUTHENTICATION RESULT message and sent as such. 【0352】 Each device may complete this procedure based on the sending and receiving of authentication result messages. Each device may update its stored information based on the information sent and received in this procedure based on the completion of this procedure. Specifically, the AMF140 and / or NW may store the authentication result for each S-NSSAI based on the sending and receiving of authentication results. For example, if the AMF140 and / or NW send and receive "success" as an authentication result, it may store the NSSAA in a "successful" state as UE information, associated with the S-NSSAI sent and received along with the authentication result. Similarly, if the AMF140 and / or NW send and receive "failure" as an authentication result, it may store the NSSAA in a "failed" state as UE information, associated with the S-NSSAI sent and received along with the authentication result. 【0353】 Furthermore, if this procedure is initiated based on the receipt of a registration request message from UE_A10, AMF140 may update the allowed NSSAI and / or rejected NSSAI for the UE based on the transmission and reception of the authentication results. Specifically, for example, if AMF140 sends or receives "success" as an authentication result, it may include the S-NSSAI sent or received with the authentication result in the allowed NSSAI, or store the S-NSSAI included in the allowed NSSAI as a mapped S-NSSAI, or store the received S-NSSAI associated with "allowed". Similarly, if AMF140 sends or receives "failure" as an authentication result, it may store the S-NSSAI sent or received with the authentication result as a third rejected NSSAI, or store the S-NSSAI included in the third rejected NSSAI as a mapped S-NSSAI, or store the received S-NSSAI associated with "rejected". Furthermore, if AMF sends or receives "failure" or "success" as an authentication result, and if UE_A10 has included an S-NSSAI sent or received along with the authentication result in the pending NSSAI, or has stored an S-NSSAI included in the pending NSSAI as a mapped S-NSSAI, then UE_A10 may delete that S-NSSAI from the pending NSSAI, or delete any S-NSSAI associated with that S-NSSAI from the pending NSSAI. 【0354】 Furthermore, the UE may store the authentication result for each S-NSSAI based on the transmission and reception of authentication results. Specifically, for example, if the UE sends or receives "success" as an authentication result, it may store the NSSAA in its information as a "successful" state, associated with the S-NSSAI sent or received along with the authentication result. Similarly, if the UE sends or receives "failure" as an authentication result, it may store the NSSAA in its information as a "failed" state, associated with the S-NSSAI sent or received along with the authentication result. 【0355】 Furthermore, each device may perform processing based on updates to its stored information upon completion of this procedure. For example, upon completion of this procedure, the AFM may initiate a UE configuration update procedure or a network-initiated deregistration procedure if there are changes to the S-NSSAI included in the allowed NSSAI and / or rejected NSSAI for the UE. The AMF may use the UE configuration update procedure to notify the UE of the new allowed NSSAI and the new rejected NSSAI. The AMF may also use a network-initiated deregistration procedure to notify the UE of the new rejected NSSAI. 【0356】 [3.4.UE Configuration Update Procedure] Next, the Generic UE configuration update procedure will be explained using Figure 8. Hereafter, the UE configuration update procedure will also be referred to as this procedure. This procedure is a procedure for the core network to update the UE configuration information. This procedure may be a mobility management procedure initiated by the network for UEs registered with the network. 【0357】 Furthermore, devices within the core network, such as AMF, may initiate this procedure based on network configuration updates and / or operator policy updates. The trigger for this procedure may be detection of UE mobility, detection of a state change in the UE, and / or the access network, and / or the core network, or a state change in a network slice. Additionally, the trigger for this procedure may be the receipt of a request from the DN and / or the DN's application server, a change in network configuration, or a change in operator policy. Furthermore, the trigger for this procedure may be the expiration of a running timer. However, the triggers for devices within the core network to initiate this procedure are not limited to these. In other words, this procedure may be executed at any time after the aforementioned registration procedure and / or PDU session establishment procedure is completed. Furthermore, this procedure may be executed at any time as long as each device has established a 5GMM context and / or each device is in 5GMM connection mode. 【0358】 Furthermore, during this procedure, each device may send and receive messages containing identification information for changing the UE's configuration information and / or for stopping or changing the functions that the UE is performing. In addition, based on the completion of this procedure, each device may update its configuration information to the settings instructed by the network, or initiate the behavior instructed by the network. 【0359】 The UE may update its configuration information based on the control information transmitted and received through this procedure. Furthermore, in conjunction with the update of the UE's configuration information, the UE may stop any functions it is currently running or start any new functions. In other words, a device in the core network may initiate this procedure and send control messages and control information of this procedure to the UE, thereby causing the UE to update its identifiable configuration information using this control information. Furthermore, by causing the UE to update its configuration information, a device in the core network may cause the UE to stop any functions it is currently running or cause the UE to start any new functions. 【0360】 First, the AMF140 initiates the UE configuration update procedure by sending a Configuration update command message (S800) to the UE_A10 via the 5G AN120 (or gNB). 【0361】 The AMF140 may include one or more of the NSSAIs related to UE_A10 (hereinafter, configured NSSAI, allowed NSSAI, rejected NSSAI, pending NSSAI, and the first NSSAI) in the configuration update command message. The AMF may indicate new UE configuration information or request an update to the UE configuration information by sending one or more of the NSSAIs. The information indicating support for each function and the information indicating a request for use of each function may be sent and received as the same identification information or as different identification information. 【0362】 Furthermore, the AMF140 may include a TAI list indicating the new registration area in the configuration update command message. 【0363】 Furthermore, when multiple pieces of identification information are sent and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that information indicating support for each function and information indicating a request to use each function may be sent and received as the same piece of identification information, or as different pieces of identification information. 【0364】 Furthermore, the AMF140 may select and decide whether to include each NSSAI and TAI list in the configuration update command 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 AMF140. 【0365】 Furthermore, the AMF140 may indicate a request to update the UE_A10 configuration information by sending a configuration update command 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 AMF140. 【0366】 UE_A10 receives a configuration update command message from AMF140 via 5G AN120 (or gNB) (S800). UE_A10 may update the UE's configuration information based on the configuration update command message and / or the identification information contained in the configuration update command message. 【0367】 Furthermore, if UE_A10 receives a TAI list, it may activate the received TAI list. If UE_A10 already has a valid TAI list stored, it may delete or invalidate the old TAI list. Hereafter, a valid TAI list may be referred to as a registration area. Note that if UE_A10 does not have a valid TAI list stored and does not receive a TAI list from the core network during this procedure, a valid TAI list may not be stored. 【0368】 Furthermore, UE_A10 may appropriately store each NSSAI it receives. Specifically, when UE_A10 receives a configured NSSAI, it may store the received configured NSSAI as the "configured NSSAI associated with the current PLMN". In other words, UE_A10 may replace the "configured NSSAI associated with the current PLMN stored by UE_A10" with the "received configured NSSAI". 【0369】 Furthermore, if UE_A10 receives a configured NSSAI, it may delete the mapped S-NSSAI of the S-NSSAI included in "the configured NSSAI associated with the current PLMN stored by UE_A10". Furthermore, if "the received configured NSSAI" contains one or more mapped S-NSSAIs, UE_A10 may store those one or more mapped S-NSSAIs. 【0370】 Furthermore, if UE_A10 receives a configured NSSAI, it may delete the "rejected NSSAI that UE_A10 has stored and associated with the current PLMN." 【0371】 Alternatively, if UE_A10 receives a configured NSSAI, it may delete at least one of the following: "the first rejected NSSAI stored by UE_A10 and associated with the current PLMN", "the second rejected NSSAI stored by UE_A10 and associated with the current PLMN", and "the third rejected NSSAI stored by UE_A10 and associated with the current PLMN". 【0372】 Furthermore, if UE_A10 receives a configured NSSAI, it may delete "the first NSSAI stored by UE_A10", and / or "the first NSSAI stored by UE_A10 and associated with the current PLMN", and / or one or more "the first NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN". 【0373】 Furthermore, when UE_A10 receives a configured NSSAI, it may delete the "pending NSSAI stored by UE_A10" and / or the "pending NSSAI stored by UE_A10 and associated with the current PLMN" and / or one or more "first pending NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN". 【0374】 Furthermore, if UE_A10 receives an allowed NSSAI, it may store the received allowed NSSAI as "the allowed NSSAI associated with the current PLMN and the current access type." In other words, UE_A10 may replace the "allowed NSSAI associated with the current PLMN and the current access type" that UE_A10 stores with the "received allowed NSSAI." 【0375】 Furthermore, if UE_A10 receives a TAI list and an allowed NSSAI from new AMF141, and if at least one TAI in the TAI list belongs to an EPLMN, UE_A10 may store the received allowed NSSAI as "the allowed NSSAI associated with the EPLMN to which the TAI in the TAI list belongs, the current access type, and the EPLMN to which the TAI belongs." 【0376】 Alternatively, if UE_A10 does not receive a TAI list but receives an allowed NSSAI from new AMF141, and if the TAI included in the TAI list that the UE has previously received and stored belongs to an EPLMN, then UE_A10 may store the received allowed NSSAI as "the allowed NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs, and the current access type." 【0377】 In other words, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, then those one or more PLMNs are EPLMNs, and UE_A10 may store the "received allowed NSSAI" in "one allowed NSSAI associated with one of those one or more PLMNs, the current access type, and the PLMN among them." 【0378】 In other words, UE_A10 may store the "received allowedNSSAI" in the "PLMN to which each TAI contained in the registration area stored by UE_A10 belongs, the current access type, and the allowed NSSAI associated with it." 【0379】 Furthermore / or, if multiple TAIs contained in a registration area stored by UE_A10 each belong to different PLMNs, UE_A10 may replace each "allowed NSSAI associated with each PLMN to which a TAI contained in a registration area belongs, and the current access type" stored by UE_A10 with the "received allowed NSSAI". 【0380】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "received allowed NSSAI" as "allowed NSSAI#1 associated with PLMN#1 and the current access type" and "allowed NSSAI#2 associated with PLMN#2 and the current access type". 【0381】 Alternatively, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, and those one or more PLMNs are EPLMNs, UE_A10 may store the "received allowed NSSAI" in "one allowed NSSAI associated with the one or more PLMNs to which the TAI included in the registration area belongs, the current access type, and the current access type." 【0382】 Furthermore / or, if two or more TAIs included in the registration area belong to multiple PLMNs, UE_A10 may replace the "one or more PLMNs to which the TAIs included in the registration area belong, and the current access type, and one allowed NSSAI" stored in UE_A10 with the "received allowed NSSAI". 【0383】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#1 which is an EPLMN, then UE_A10 may store the "received allowed NSSAI" in "allowed NSSAI#1 associated with PLMN#1, PLMN#2, and the current access type." 【0384】 Alternatively, if the TAIs included in the registration area stored by UE_A10 belong to one or more PLMNs different from the RPLMN, and those one or more PLMNs are EPLMNs, then UE_A10 may store the "received allowed NSSAI" only as "one allowed NSSAI associated with the RPLMN and the current access type." In other words, even if the TAIs included in the registration area stored by UE_A10 belong to one or more PLMNs different from the RPLMN, UE_A10 does not have to store the "received allowed NSSAI" as an allowed NSSAI associated with those one or more PLMNs. 【0385】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may replace the "one allowed NSSAI associated with the RPMMN and the current access type" stored in UE_A10 with the "received allowed NSSAI". 【0386】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#1 which is an EPLMN, then UE_A10 may store the "received allowed NSSAI" only in "allowed NSSAI#1 associated with PLMN#1 and the current access type." 【0387】 Furthermore, when UE_A10 stores an allowed NSSAI, it may store the allowed NSSAI in association with a registration area, or it may store the S-NSSAI included in the allowed NSSAI in association with a registration area. 【0388】 Furthermore, if UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSAI of the S-NSSAI included in the "allowed NSSAI deleted based on reception" or the "older allowed NSSAI updated based on reception". Furthermore, if the "received allowed NSSAI" includes mapped S-NSSAI, UE_A10 may store one or more of those mapped S-NSSAI. 【0389】 Furthermore, if UE_A10 receives an allowed NSSAI, it may delete any rejected NSSAIs that UE_A10 has stored and associated with the current PLMN. 【0390】 Specifically, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI contained in the received allowed NSSAI from at least one of the following: "the first rejected NSSAI stored by UE_A10 and associated with the current PLMN", "the second rejected NSSAI stored by UE_A10 and associated with the current PLMN", "the second rejected NSSAI stored by UE_A10 and associated with the current PLMN and the current registration area", and "the third rejected NSSAI stored by UE_A10 and associated with the current PLMN", or it may delete the S-NSSAI contained in the received allowed NSSAI from all NSSAI. 【0391】 Specifically, if UE_A10 receives an allowed NSSAI, it may further delete the S-NSSAI associated with the current registration area and included in the further received allowed NSSAI from "the second rejected NSSAI that UE_A10 has stored and associated with the current PLMN". 【0392】 Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMNs". Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0393】 Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Alternatively, if UE_A10 receives an allowed NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." 【0394】 Furthermore, if UE_A10 receives a rejected NSSAI, it may store the S-NSSAI contained in the received rejected NSSAI as "rejected NSSAI associated with the current PLMN" based on the rejection reason value to which the S-NSSAI is associated. In other words, UE_A10 may add "the S-NSSAI contained in the received rejected NSSAI" to "rejected NSSAI associated with the current PLMN" that UE_A10 stores. 【0395】 Specifically, if UE_A10 receives a rejection reason value "S-NSSAI that is not accepted in the current PLMN or SNPN" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to the first rejected NSSAI associated with the current PLMN. 【0396】 Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI that is not allowed in the current registration area" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the "received rejected S-NSSAI" to "a second rejected NSSAI associated with the current PLMN and the current registration area." 【0397】 If UE_A10 receives a TAI list along with a rejected NSSAI, the current registration area will be indicated by the received TAI list. On the other hand, if UE_A10 does not receive a TAI list along with a rejected NSSAI, the current registration area will be indicated by the TAI list that UE_A10 previously received and stored. 【0398】 If the TAI included in the current registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, then the one or more different PLMNs are EPLMNs, and UE_A10 may store and / or add "rejected S-NSSAI received associated with rejection reason value "S-NSSAI not allowed in the current registration area"" to each "second rejected NSSAI associated with one of those one or more different PLMNs and the current registration area." 【0399】 Furthermore / or, if one or more TAIs included in a registration area belong to different PLMNs, UE_A10 may store, in addition to each "second rejected NSSAI associated with each PLMN to which a TAI included in a registration area belongs, the current access type, and the "rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" for each "rejected NSSAI associated with each PLMN to which a TAI included in a registration area belongs, and the current access type" that UE_A10 stores. 【0400】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "second rejected S-NSSAI received" as "second rejected NSSAI#1 associated with PLMN#1 and the current registration area" and "second rejected NSSAI#2 associated with PLMN#2 and the current registration area". 【0401】 Alternatively, if the TAI included in the registration area belongs to one or more PLMNs different from the RPLMN, those one or more PLMNs are EPLMNs, and UE_A10 may store the "rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" in "one second rejected NSSAI associated with that one or more PLMNs and the current registration area." 【0402】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may store "a rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" in addition to "a second rejected NSSAI associated with those multiple PLMNs and the current access type" that UE_A10 stores. 【0403】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "received second rejected S-NSSAI" in "the second rejected NSSAI#1 associated with PLMN#1, PLMN#2, and the current registration area." 【0404】 Furthermore, if a TAI included in the TAI list indicating the current registration area belongs to an EPLMN, UE_A10 may store the S-NSSAI associated with the received rejection reason value "S-NSSAI that is not allowed in the current registration area" as "a second rejected NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs, and the current access type." 【0405】 Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, then that one or more PLMNs is an EPLMN, and UE_A10 may store the "received second rejected S-NSSAI" only as "one second rejected NSSAI associated with the RPLMN and the current access type." In other words, even if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, UE_A10 does not have to store the "received second rejected S-NSSAI" as a second rejected NSSAI associated with that one or more PLMNs. 【0406】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may replace the "one second rejected NSSAI associated with the RPMMN and the current access type" stored in UE_A10 with the "second rejected S-NSSAI received". 【0407】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#1 which is an EPLMN, then UE_A10 may store and / or add the "received second rejected S-NSSAI" only to "the second rejected NSSAI#1 associated with PLMN#1 and the current access type." 【0408】 Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI is not possible due to NSSAA failure or revocation" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to a third rejected NSSAI associated with the current PLMN. 【0409】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "allowed NSSAIs that UE_A10 stores and associates with the current PLMN". 【0410】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0411】 Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Alternatively, if UE_A10 receives an allowed NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." 【0412】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0413】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with EPLMN." 【0414】 Furthermore, each process performed by the UE based on the receipt of each of the _A10 identification pieces described above may be performed during or after this procedure, or after this procedure is completed based on its completion. In addition, the UE may send a Configuration update complete message to the AMF140 via 5GAN (gNB) as a response message to the Configuration update command message, based on the identification piece contained in the Configuration update command message (S802). 【0415】 When UE_A10 sends a configuration update completion command message, AMF140 receives the configuration update completion message via 5G AN(gNB) (S802). Each device completes this procedure based on the sending and receiving of the configuration update command message and / or the configuration update completion message. 【0416】 Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of this procedure. For example, if update information for configuration information is transmitted and received, each device may update the configuration information. Furthermore, if information indicating that a registration procedure needs to be performed is transmitted and received, UE_A10 may initiate the registration procedure upon completion of this procedure. 【0417】 Furthermore, upon completion of this procedure, UE_A10 may store the identification information received along with the configuration command message, or recognize the network decision. The UE may also execute the procedures based on the stored information upon completion of this procedure. 【0418】 In the above procedure, by sending and receiving configuration update command messages, devices within the core network can instruct the UE to update configuration information already applied by the UE, or to stop or change functions that the UE is performing. 【0419】 [3.5. Unregistered procedures initiated by the network] Next, the network-initiated de-registration procedure will be explained using Figure 9. Hereafter, this procedure refers to the network-initiated de-registration procedure. The network-initiated de-registration procedure is a procedure for the network to manually deregister from access network_A and / or core network_A, access network_B and / or core network_B and / or DN and / or PDN. This procedure may be a mobility management procedure initiated by the network for UEs registered with the network. 【0420】 The AMF can initiate this procedure at any time, provided that the UE is registered with the network (RM-REGISTERED state or 5GMM-REGISTEDED state). For example, the AMF may initiate this procedure upon updating the UE's registration information. More specifically, the AMF may initiate this procedure when, following the completion of the NSSAA procedure, there are no longer any allowed NSSAIs in the UE's registration information. In other words, the AMF may initiate this procedure if there are no S-NSSAIs to allow for the UE and there are no plans to add any S-NSSAIs to the allowed NSSAIs through other procedures (e.g., the NSSAA procedure) in the future. 【0421】 First, the AMF140 may initiate this procedure by sending a de-registration request message to UE_A10 (S900). Here, the de-registration request message is a NAS message sent and received on the N1 interface, but between the UE and the 5G AN (gNB), it is sent and received as part of an RRC message. 【0422】 AMF140 may include identification information for at least one of the NSSAIs (hereinafter, meaning rejected NSSAI, pending NSSAI, and first NSSAI) in the non-registration request message. AMF may further include a reason value and / or information indicating the access type to be unregistered in the non-registration request message, where the reason value may be 5GMMcause. Furthermore, if this procedure is initiated based on the result of an NSSAA procedure, or upon completion of an NSSAA, the reason value may be a value indicating that no network slices are available. In that case, it may be 5GS 5GMM cause value #62 “No network slices available”. 【0423】 Furthermore, by transmitting this identification information and / or unregistered messages, the AMF140 may indicate that the network does not support each function, request a transition to an unregistered state, notify a change in the AMF140, instruct the commencement of the registration procedure, or display information combining these. In addition, if multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Furthermore, 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 piece of identification information, or as different pieces of identification information. 【0424】 Based on the reception of at least one of the NSSAIs, and / or the reception of a reason value, and / or the reception of other identification information, and / or the state of the UE, UE_A10 may recognize and store the rejectedS-NSSAI and the reason for rejection, and determine the behavior of the UE. 【0425】 Furthermore, if UE_A10 receives a rejected NSSAI, it may store the S-NSSAI contained in the received rejected NSSAI as "rejected NSSAI associated with the current PLMN" based on the rejection reason value to which the S-NSSAI is associated. In other words, UE_A10 may add "the S-NSSAI contained in the received rejected NSSAI" to "rejected NSSAI associated with the current PLMN" that UE_A10 stores. 【0426】 Specifically, if UE_A10 receives a rejection reason value "S-NSSAI that is not accepted in the current PLMN or SNPN" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to the first rejected NSSAI associated with the current PLMN. 【0427】 Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI that is not allowed in the current registration area" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the "received rejected S-NSSAI" to "a second rejected NSSAI associated with the current PLMN and the current registration area." 【0428】 If UE_A10 receives a TAI list along with a rejected NSSAI, the current registration area will be indicated by the received TAI list. On the other hand, if UE_A10 does not receive a TAI list along with a rejected NSSAI, the current registration area will be indicated by the TAI list that UE_A10 previously received and stored. 【0429】 If the TAI included in the current registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, then the one or more different PLMNs are EPLMNs, and UE_A10 may store and / or add "rejected S-NSSAI received associated with rejection reason value "S-NSSAI not allowed in the current registration area"" to each "second rejected NSSAI associated with one of those one or more different PLMNs and the current registration area." 【0430】 Furthermore / or, if one or more TAIs included in a registration area belong to different PLMNs, UE_A10 may store, in addition to each "second rejected NSSAI associated with each PLMN to which a TAI included in a registration area belongs, the current access type, and the "rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" for each "rejected NSSAI associated with each PLMN to which a TAI included in a registration area belongs, and the current access type" that UE_A10 stores. 【0431】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "second rejected S-NSSAI received" as "second rejected NSSAI#1 associated with PLMN#1 and the current registration area" and "second rejected NSSAI#2 associated with PLMN#2 and the current registration area". 【0432】 Alternatively, if the TAI included in the registration area belongs to one or more PLMNs different from the RPLMN, those one or more PLMNs are EPLMNs, and UE_A10 may store the "rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" in "one second rejected NSSAI associated with that one or more PLMNs and the current registration area." 【0433】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may store "a rejected S-NSSAI received associated with the rejection reason value 'S-NSSAI that is not allowed in the current registration area'" in addition to "a second rejected NSSAI associated with those multiple PLMNs and the current access type" that UE_A10 stores. 【0434】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#2 which is an EPLMN, then UE_A10 may store the "received second rejected S-NSSAI" in "the second rejected NSSAI#1 associated with PLMN#1, PLMN#2, and the current registration area." 【0435】 Furthermore, if a TAI included in the TAI list indicating the current registration area belongs to an EPLMN, UE_A10 may store the S-NSSAI associated with the received rejection reason value "S-NSSAI that is not allowed in the current registration area" as "a second rejected NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs, and the current access type." 【0436】 Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, then that one or more PLMNs is an EPLMN, and UE_A10 may store the "received second rejected S-NSSAI" only as "one second rejected NSSAI associated with the RPLMN and the current access type." In other words, even if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, UE_A10 does not have to store the "received second rejected S-NSSAI" as a second rejected NSSAI associated with that one or more PLMNs. 【0437】 Furthermore / or, if multiple TAIs included in the registration area each belong to different PLMNs, UE_A10 may replace the "one second rejected NSSAI associated with the RPMMN and the current access type" stored in UE_A10 with the "second rejected S-NSSAI received". 【0438】 Specifically, if the registration area stored by UE_A10 includes TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1 which is an RPLMN, and TAI#2 belongs to PLMN#1 which is an EPLMN, then UE_A10 may store and / or add the "received second rejected S-NSSAI" only to "the second rejected NSSAI#1 associated with PLMN#1 and the current access type." 【0439】 Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI is not possible due to NSSAA failure or revocation" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to a third rejected NSSAI associated with the current PLMN. 【0440】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "allowed NSSAIs that UE_A10 stores and associates with the current PLMN". 【0441】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0442】 Furthermore, if UE_A10 receives an allowed NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Alternatively, if UE_A10 receives an allowed NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." 【0443】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMN". Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with EPLMN". 【0444】 Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received rejected NSSAI from "the first NSSAI that UE_A10 stores and associates with the current PLMN." Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with all PLMNs." Furthermore, if UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI contained in the received allowed NSSAI from "the first NSSAI that UE_A10 stores and associates with EPLMN." 【0445】 Furthermore, each process that the UE performs based on the receipt of each _A10 identification information as described above may be performed during or after this procedure, or after this procedure is completed based on its completion. 【0446】 UE_A10 receives unregistered request messages via 5G AN(gNB). By receiving unregistered request messages, UE_A10 can recognize the content of various identification information contained in the unregistered request messages. 【0447】 Upon receiving a deregistration request message, UE_A10 may send a deregistration acceptance message to AMF140 via the 5G AN (or gNB). The deregistration acceptance message is a NAS message sent and received on the N1 interface. The RRC message may be a control message sent and received between the UE and the 5G AN (or gNB). 【0448】 Each device may transition to a state where the UE is not registered on the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending and receiving of registration acceptance messages. Alternatively, each device may transition to any of these states based on the completion of this procedure. 【0449】 Furthermore, each device may perform processing based on the information transmitted and received in this procedure upon completion of the non-registration procedure. For example, UE_A10 may initiate the registration procedure upon completion of the non-registration procedure. 【0450】 [4. Embodiments of the present invention] Embodiments in the present invention may be combinations of one or more procedures described in Chapter 3. For example, in this embodiment, after the completion of the initial registration procedure described in Chapter 3, an NSSAA procedure may be performed and a UE configuration update procedure may be executed. Furthermore, each device (UE and core network devices) may perform one or more relocation and periodic registration procedures based on the completion of the initial registration procedure. Alternatively, after the completion of the initial registration procedure described in Chapter 3, an NSSAA procedure may be performed and a deregistration procedure that starts the network may be performed. 【0451】 The following describes an example of a specific embodiment of the present invention. Note that the behavior of the multiple embodiments described below may be combined and implemented by the respective devices. 【0452】 Specifically, each device may behave according to the first embodiment when transmitting and receiving allowed NSSAI, and according to the second embodiment when transmitting and receiving rejected NSSAI. Alternatively, each device may be behave according to the first embodiment when transmitting and receiving allowed NSSAI, and according to the third embodiment when transmitting and receiving rejected NSSAI. 【0453】 Alternatively, each device may behave according to the second embodiment when transmitting and receiving allowed NSSAI, and according to the first embodiment when transmitting and receiving a second rejected NSSAI. Each device may behave according to the second embodiment when transmitting and receiving allowed NSSAI, and according to the third embodiment when transmitting and receiving a second rejected NSSAI. 【0454】 Alternatively, each device may behave according to the third embodiment when transmitting and receiving allowed NSSAI, and according to the first embodiment when transmitting and receiving second rejected NSSAI. 【0455】 [4.1. First Embodiment] The first embodiment (hereinafter referred to as "this embodiment") will be described below. In this embodiment, an example of the behavior of each device after transmission and reception of each NSSAI, and further, the behavior of each device after a PLMN change occurs, will be described when the TAs included in the current registration area belong to different PLMNs. 【0456】 In this embodiment, the UE can store the received allowedNSSAI in multiple allowed NSSAIs based on the current registration area. Furthermore / or, in this embodiment, the UE can store or add the S-NSSAI contained in the received second rejected NSSAI in multiple second rejectedNSSAIs based on the current registration area. 【0457】 Specifically, in this embodiment, the UE initiates the first registration procedure for PLMN#1's 3GPP access by sending a first registration request message to the core network of PLMN#1 over 3GPP access. 【0458】 During the first registration procedure, the UE may receive a first registration acceptance message or a first registration rejection message from PLMN#1 (core network). 【0459】 Here, the first registration acceptance message or the first registration rejection message may include a TAI list indicating the registration area. If the UE includes a new TAI list in the first registration acceptance message or the first registration rejection message, it treats that TAI list as available (valid). If the UE receives a new TAI list and has the old TAI list in its memory, it deletes the old TAI list or treats it as unavailable. 【0460】 If the UE's first registration acceptance message or second registration rejection message does not include a TAI list indicating the registration area, it will treat an already stored TAI list as valid. Thereafter, the area indicated by the valid TAI list after receiving the registration acceptance message or registration rejection message will be treated as the current registration area. 【0461】 If the UE does not include a TAI list indicating a registration area in the first registration acceptance message or the second registration rejection message, and furthermore, does not remember a valid registration area, then the UE is in a state of not remembering a valid registration area (TAI list). 【0462】 Hereafter, the area indicated by the valid TAI list (if any) after receiving the first registration acceptance message or the first registration rejection message will be treated as the current registration area. 【0463】 For example, if a UE receives an allowed NSSAI included in the first registration acceptance message, and the current registration area also includes TAI#1 belonging to PLMN#1 and TAI#2 belonging to PLMN#2, the UE can store the received allowed NSSAI in allowedNSSAI#1 associated with PLMN#1 and allowedNSSA#2 associated with PLMN#2, respectively. 【0464】 Similarly, for example, if a UE receives a second rejectedNSSAI contained in a first registration acceptance message or a first registration rejection message, and the current registration area also contains TAI#1 belonging to PLMN#1 and TAI#2 belonging to PLMN#2, the UE can store the S-NSSAI contained in the received second rejected NSSAI in a second rejected NSSAI#1 associated with PLMN#1 and a second rejected NSSAI#2 associated with PLMN#2, respectively. 【0465】 Here, if the first registration procedure is an initial registration procedure, and the first registration rejection message does not include a TAI list indicating the registration area but does include a second rejectedNSSAI, the UE may, based on the fact that the UE does not remember a valid registration area, store the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI#3 associated with PLMN#1. 【0466】 Here, the S-NSSAI included in the second rejected NSSAI#3 does not have to be associated with and stored in a registration area, or it may be associated with dummy registration area information. Here, the dummy registration area information may be empty registration area information. 【0467】 Alternatively, if the UE does not remember the current registration area, it does not need to remember the second rejected NSSAI that the UE received from PLMN#1 during the initial registration procedure. 【0468】 Furthermore, the first registration procedure may be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and may be the behavior of the registration procedure described in Chapter 3. 【0469】 The following describes the behavior when the current registration area includes at least TAI#1 and TAI#2, and further, when TAI#1 belongs to PLMN#1 and TAI#2 belongs to PLMN#2. 【0470】 Next, a PLMN change occurs in the UE without a change in the registration area. Specifically, we will explain the case where the UE moves from TAI#1 to TAI#2. 【0471】 After a UE moves from TAI#1 to TAI#2, a transfer or periodic registration procedure occurs. The cause of this registration procedure is not specifically defined, but it could be, for example, a periodic registration procedure. 【0472】 Based on the fact that TAI#2 belongs to PLMN#2, the UE may perform a second registration procedure for 3GPP access to PLMN#2. The UE may initiate the registration procedure by sending a second registration request message to PLMN#2 (core network) that includes at least the first identification information. 【0473】 Here, the UE may include in the first identifier information an S-NSSAI contained in an allowed NSSAI#2 associated with PLMN#2. Furthermore, the UE may control the first identifier information so that it does not include an S-NSSAI contained in a second rejected NSSAI#2 associated with PLMN#2. In other words, the S-NSSAI included in the first identifier information does not need to be included in a second rejected NSSAI#2 associated with PLMN#2. 【0474】 Based on the receipt of the second registration request message, PLMN#2 (core network) may send a second registration acceptance message or a second registration rejection message to the UE. 【0475】 Based on the receipt of a second registration acceptance message or a second registration rejection message, the UE performs the same actions as in the first registration procedure. 【0476】 Furthermore, the second registration procedure may also be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and may be the behavior of the registration procedure described in Chapter 3. 【0477】 As described above, in this embodiment, each device can store the received allowed NSSAI and / or second rejected NSSAI in a plurality of allowed NSSAI and / or a plurality of second rejected NSSAI based on the current registration area. 【0478】 Although this embodiment only describes the registration procedure, it may be implemented using other procedures. Specifically, instead of a registration acceptance message or a registration rejection message, the UE may receive an allowed NSSAI and / or a second rejected NSSAI in a configuration update command message during the UE configuration update procedure described in Chapter 3, and act based on the reception of each NSSAI. 【0479】 Alternatively, instead of a registration acceptance message or a registration rejection message, the UE may receive an allowedNSSAI and / or a second rejected NSSAI in a non-registration request message during a network-initiated non-registration procedure as described in Chapter 3, and act based on the receipt of each NSSAI. 【0480】 [4.1. Second Embodiment] The second embodiment (hereinafter referred to as "this embodiment") will be described below. In this embodiment, an example of the behavior of each device after transmission and reception of each NSSAI, and further, the behavior of each device after a PLMN change occurs, will be described when the TAs included in the current registration area belong to different PLMNs. 【0481】 In the first embodiment, the received allowedNSSAI was stored in multiple allowed NSSAIs based on the current registration area, whereas in this embodiment, the UE can store the received allowed NSSAI in a single allowedNSSAI associated with multiple PLMNs based on the current registration area. 【0482】 Similarly, in the first embodiment, based on the current registration area, the S-NSSAI contained in the received second rejected NSSAI was stored in multiple second rejected NSSAIs, whereas in this embodiment, based on the current registration area, the UE can store or add the S-NSSAI contained in the received second rejected NSSAI to one second rejected NSSAI associated with multiple PLMNs. 【0483】 Specifically, in this embodiment, the UE initiates the first registration procedure for PLMN#1's 3GPP access by sending a first registration request message to the core network of PLMN#1 over 3GPP access. 【0484】 During the first registration procedure, the UE may receive a first registration acceptance message or a first registration rejection message from PLMN#1 (core network). 【0485】 Here, the first registration acceptance message or the first registration rejection message may include a TAI list indicating the registration area. If the UE includes a new TAI list in the first registration acceptance message or the first registration rejection message, it treats that TAI list as available (valid). If the UE receives a new TAI list and has the old TAI list in its memory, it deletes the old TAI list or treats it as unavailable. 【0486】 If the UE's first registration acceptance message or second registration rejection message does not include a TAI list indicating the registration area, it will treat an already stored TAI list as valid. Thereafter, the area indicated by the valid TAI list after receiving the registration acceptance message or registration rejection message will be treated as the current registration area. 【0487】 If the UE does not include a TAI list indicating a registration area in the first registration acceptance message or the second registration rejection message, and furthermore, does not remember a valid registration area, then the UE is in a state of not remembering a valid registration area (TAI list). 【0488】 Hereafter, the area indicated by the valid TAI list (if any) after receiving the first registration acceptance message or the first registration rejection message will be treated as the current registration area. 【0489】 For example, if a UE receives an allowed NSSAI included in the first registration acceptance message, and the current registration area also includes TAI#1 belonging to PLMN#1 and TAI#2 belonging to PLMN#2, the UE can store the received allowed NSSAI in allowed NSSAI#1 associated with PLMN#1 and PLMN#2. 【0490】 Similarly, if a UE receives a second rejectedNSSAI contained in a first registration acceptance message or a first registration rejection message, and the current registration area also contains TAI#1 belonging to PLMN#1 and TAI#2 belonging to PLMN#2, the UE can store the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI#1 associated with PLMN#1 and PLMN#2. 【0491】 Here, if the first registration procedure is an initial registration procedure, and the first registration rejection message does not include a TAI list indicating the registration area but does include a second rejectedNSSAI, the UE may, based on the fact that the UE does not remember a valid registration area, store the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI#3 associated with PLMN#1. 【0492】 Here, the S-NSSAI included in the second rejected NSSAI#3 does not have to be associated with and stored in a registration area, or it may be associated with dummy registration area information. Here, the dummy registration area information may be empty registration area information. 【0493】 Alternatively, if the UE does not remember the current registration area, it does not need to remember the second rejected NSSAI that the UE received from PLMN#1 during the initial registration procedure. 【0494】 Furthermore, the first registration procedure may be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and may be the behavior of the registration procedure described in Chapter 3. 【0495】 The following describes the behavior when the current registration area includes at least TAI#1 and TAI#2, and further, when TAI#1 belongs to PLMN#1 and TAI#2 belongs to PLMN#2. 【0496】 Next, a PLMN change occurs in the UE without a change in the registration area. Specifically, we will explain the case where the UE moves from TAI#1 to TAI#2. 【0497】 After a UE moves from TAI#1 to TAI#2, a transfer or periodic registration procedure occurs. The cause of this registration procedure is not specifically defined, but it could be, for example, a periodic registration procedure. 【0498】 Based on the fact that TAI#2 belongs to PLMN#2, the UE may perform a second registration procedure for 3GPP access to PLMN#2. The UE may initiate the registration procedure by sending a second registration request message to PLMN#2 (core network) that includes at least the first identification information. 【0499】 Here, the UE may include in the first identification information S-NSSAI contained in the allowed NSSAI#1 associated with PLMN#1 and PLMN#2. Furthermore, the UE may control the first identification information so that it does not include S-NSSAI contained in the second rejectedNSSAI#1 associated with PLMN#1 and PLMN#2. In other words, the S-NSSAI included in the first identification information does not need to be included in the second rejectedNSSAI#1 associated with PLMN#1 and PLMN#2. 【0500】 Based on the receipt of the second registration request message, PLMN#2 (core network) may send a second registration acceptance message or a second registration rejection message to the UE. 【0501】 Based on the receipt of a second registration acceptance message or a second registration rejection message, the UE performs the same actions as in the first registration procedure. 【0502】 Furthermore, the second registration procedure may also be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and may be the behavior of the registration procedure described in Chapter 3. 【0503】 As described above, in this embodiment, each device can store the received allowed NSSAI and / or second rejected NSSAI in one allowed NSSAI associated with a plurality of PLMNs and / or one second rejected NSSAI associated with a plurality of PLMNs, based on the current registration area. 【0504】 Although this embodiment only describes the registration procedure, it may be implemented using other procedures. Specifically, instead of a registration acceptance message or a registration rejection message, the UE may receive an allowed NSSAI and / or a second rejected NSSAI in a configuration update command message during the UE configuration update procedure described in Chapter 3, and act based on the reception of each NSSAI. 【0505】 Alternatively, instead of a registration acceptance message or a registration rejection message, the UE may receive an allowedNSSAI and / or a second rejected NSSAI in a non-registration request message during a network-initiated non-registration procedure as described in Chapter 3, and act based on the receipt of each NSSAI. 【0506】 [4.1. Third Embodiment] The third embodiment (hereinafter referred to as "this embodiment") will be described below. In this embodiment, an example of the behavior of each device after transmission and reception of each NSSAI, and further, the behavior of each device after a PLMN change occurs, will be described when the TAs included in the current registration area belong to different PLMNs. 【0507】 In the first embodiment, the received allowedNSSAI is stored in multiple allowed NSSAIs based on the current registration area, and in the second embodiment, the UE stores the received allowed NSSAI in one allowedNSSAI associated with multiple PLMNs based on the current registration area, whereas in this embodiment, the received allowed NSSAI is stored in one allowedNSSAI belonging only to the current PLMN. 【0508】 Similarly, in the first embodiment, the UE could store the S-NSSAI contained in the received second rejected NSSAI in a plurality of second rejected NSSAIs based on the current registration area, and in the second embodiment, the UE could store or add the S-NSSAI contained in the received second rejected NSSAI in a single second rejected NSSAI associated with a plurality of PLMNs based on the current registration area, whereas in this embodiment, the S-NSSAI contained in the received second rejected NSSAI is stored in a single second rejected NSSAI that belongs only to the current PLMN. 【0509】 Furthermore, in this embodiment, even if the UE is an allowed NSSAI belonging to a PLMN other than the PLMN (core network) to which the registration request message is sent, if the TAI included in the registration area to which the allowed NSSAI is associated is associated with the current PLMN (the destination PLMN), the registration request message can include the S-NSSAI included in the allowed NSSAI. 【0510】 Furthermore, in this embodiment, when the UE sends a registration request message, if at least one TAI included in the current registration area belongs to a PLMN different from the destination of the registration request message, and the UE also stores a second rejected NSSAI associated with that different PLMN, the UE may implement control to not include the S-NSSAI included in the second rejected NSSAI associated with that different PLMN in the registration request message. 【0511】 Specifically, in this embodiment, the UE initiates the first registration procedure for PLMN#1's 3GPP access by sending a first registration request message to the core network of PLMN#1 over 3GPP access. 【0512】 During the first registration procedure, the UE may receive a first registration acceptance message or a first registration rejection message from PLMN#1 (core network). 【0513】 Here, the first registration acceptance message or the first registration rejection message may include a TAI list indicating the registration area. If the UE includes a new TAI list in the first registration acceptance message or the first registration rejection message, it treats that TAI list as available (valid). If the UE receives a new TAI list and has the old TAI list in its memory, it deletes the old TAI list or treats it as unavailable. 【0514】 If the UE's first registration acceptance message or second registration rejection message does not include a TAI list indicating the registration area, it will treat an already stored TAI list as valid. Thereafter, the area indicated by the valid TAI list after receiving the registration acceptance message or registration rejection message will be treated as the current registration area. 【0515】 If the UE does not include a TAI list indicating a registration area in the first registration acceptance message or the second registration rejection message, and furthermore, does not remember a valid registration area, then the UE is in a state of not remembering a valid registration area (TAI list). 【0516】 Hereafter, the area indicated by the valid TAI list (if any) after receiving the first registration acceptance message or the first registration rejection message will be treated as the current registration area. 【0517】 For example, if a UE receives an allowed NSSAI included in the first registration acceptance message, and the current registration area also includes TAI#1 belonging to PLMN#1 and TAI#2 belonging to PLMN#2, the UE can store the received allowed NSSAI in allowed NSSAI#1 associated with PLMN#1 and PLMN#2, and in allowed NSSA#2 associated with PLMN#2, respectively. 【0518】 Similarly, for example, if a UE receives a second rejectedNSSAI contained in a first registration acceptance message or a first registration rejection message, and the current registration area also contains TAI#1 belonging to PLMN#1 and TAI#2 belonging to PLMN#2, the UE can store the S-NSSAI contained in the received second rejected NSSAI in a second rejected NSSAI#1 associated with PLMN#1 and PLMN#2, and a second rejected NSSAI#2 associated with PLMN#2, respectively. 【0519】 Here, if the first registration procedure is an initial registration procedure, and the first registration rejection message does not include a TAI list indicating the registration area but does include a second rejectedNSSAI, the UE may, based on the fact that the UE does not remember a valid registration area, store the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI#3 associated with PLMN#1. 【0520】 Here, the S-NSSAI included in the second rejected NSSAI#3 does not have to be associated with and stored in a registration area, or it may be associated with dummy registration area information. Here, the dummy registration area information may be empty registration area information. 【0521】 Alternatively, if the UE does not remember the current registration area, it does not need to remember the second rejected NSSAI that the UE received from PLMN#1 during the initial registration procedure. 【0522】 Furthermore, the first registration procedure may be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and may be the behavior of the registration procedure described in Chapter 3. 【0523】 The following describes the behavior when the current registration area includes at least TAI#1 and TAI#2, and further, when TAI#1 belongs to PLMN#1 and TAI#2 belongs to PLMN#2. 【0524】 Next, a PLMN change occurs in the UE without a change in the registration area. Specifically, we will explain the case where the UE moves from TAI#1 to TAI#2. 【0525】 After a UE moves from TAI#1 to TAI#2, a transfer or periodic registration procedure occurs. The cause of this registration procedure is not specifically defined, but it could be, for example, a periodic registration procedure. 【0526】 Based on the fact that TAI#2 belongs to PLMN#2, the UE may perform a second registration procedure for 3GPP access to PLMN#2. The UE may initiate the registration procedure by sending a second registration request message to PLMN#2 (core network) that includes at least the first identification information. 【0527】 Here, the UE may include in the first identification information S-NSSAI contained in the allowed NSSAI#12 associated with PLMN#1 and PLMN#2. Furthermore, the UE may control the first identification information so that it does not include S-NSSAI contained in the second rejectedNSSAI#12 associated with PLMN#1 and PLMN#2. In other words, the S-NSSAI included in the first identification information does not have to be included in the second rejectedNSSAI#12 associated with PLMN#1 and PLMN#2. 【0528】 Based on the receipt of the second registration request message, PLMN#2 (core network) may send a second registration acceptance message or a second registration rejection message to the UE. 【0529】 Based on the receipt of a second registration acceptance message or a second registration rejection message, the UE performs the same actions as in the first registration procedure. 【0530】 Furthermore, the second registration procedure may also be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and may be the behavior of the registration procedure described in Chapter 3. 【0531】 Accordingly, in this embodiment, each device stores the received allowed NSSAI and / or second rejected NSSAI in one allowed NSSAI and / or second rejected NSSAI associated with the current PLMN (RPLMN), regardless of the current registration area. 【0532】 Furthermore, even if an allowed NSSAI is associated with a PLMN other than the requested PLMN, the UE can use that allowed NSSAI to generate the first identification information if the TAI included in the registration area to which the allowed NSSAI is associated belongs to the current PLMN. 【0533】 Furthermore, based on the current registration area, the UE can use a second rejected NSSAI associated with a PLMN other than the one being requested, as well as a second rejected NSSAI associated with the requested PLMN, to generate the first identification information. 【0534】 Although this embodiment only describes the registration procedure, it may be implemented using other procedures. Specifically, instead of a registration acceptance message or a registration rejection message, the UE may receive an allowed NSSAI and / or a second rejected NSSAI in a configuration update command message during the UE configuration update procedure described in Chapter 3, and act based on the reception of each NSSAI. 【0535】 Alternatively, instead of a registration acceptance message or a registration rejection message, the UE may receive an allowedNSSAI and / or a second rejected NSSAI in a non-registration request message during a network-initiated non-registration procedure as described in Chapter 3, and act based on the receipt of each NSSAI. 【0536】 [5. Variant] The program that operates in the device according to the present invention may be a program that controls a Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of the embodiment according to the present invention. The program or the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, a Hard Disk Drive (HDD), or other storage system. 【0537】 Furthermore, a program for realizing the functions of the embodiments related to the present invention may be recorded on a computer-readable recording medium. This can also be realized by loading the program recorded on this recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium. 【0538】 Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuit may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of the present invention may use new integrated circuits based on such technologies. 【0539】 It should be noted that the present invention is not limited to the embodiments described above. Although one example of a device is described in the embodiments, the present invention is not limited thereto and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances. 【0540】 While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, the present invention 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 invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Explanation of symbols] 【0541】 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

Claims

[Claim 1] UE (User Equipment), It comprises a transmitting / receiving unit and a control unit, The transmitting and receiving unit receives a control message from the core network that includes a first S-NSSAI (Single-Network Slice Selection Assistance Information), a first mapped S-NSSAI, and a first allowed NSSAI (Network Slice Selection Assistance Information). When the control message is received, if the registered area includes multiple TAIs (Tracking Area Identities), and the multiple TAIs belong to different PLMNs (Public Land Mobile Networks), and furthermore, the different PLMNs are EPLMNs (Equivalent PLMNs), the control unit stores the first S-NSSAI included in the control message in each allowed NSSAI associated with each PLMN. The control unit deletes the mapped S-NSSAI of the allowed NSSAI stored in association with each of the different PLMNs, and stores the first mapped S-NSSAI. A UE characterized by the following: [Claim 2] A communication control method performed by User Equipment (UE), The aforementioned communication control method is: The steps include receiving a control message from the core network that includes a first S-NSSAI (Single-Network Slice Selection Assistance Information), a first mapped S-NSSAI, and a first allowed NSSAI (Network Slice Selection Assistance Information), When the control message is received, if the registered area includes multiple TAIs (Tracking Area Identities), and the multiple TAIs belong to different PLMNs (Public Land Mobile Networks), and furthermore, the different PLMNs are EPLMNs (Equivalent PLMNs), the first S-NSSAI included in the control message is stored in each allowed NSSAI associated with each PLMN. The steps include deleting the mapped S-NSSAI of the allowed NSSAI stored in association with each of the different PLMNs, The first step of storing the mapped S-NSSAI, Having, A communication control method performed by a UE, characterized by the above.

Images