UE (user equipment)

Abstract

To provide communication means for achieving, in 5GS, a function that pertains to management of information pertaining to network slicing or a non-public network function.SOLUTION: Provided are communication means and a method for procedures for UE initial registration and periodic or movement-based registration for achieving, in 5GS, management of information pertaining to network slicing or a non-public network function. Further provided are communication means and a method for a procedure after completion of a registration procedure and for a de-registration procedure. Further provided is a method for managing information pertaining to network slicing in association with each procedure and the transition of a state.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to User Equipment (UE). [Background technology]

[0002] 3GPP (3rd Generation Partnership Project), which is involved in the standardization of recent mobile communication systems, is currently 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 5G (5th Generation) mobile communication systems, and in particular has been working on the specification of 5GS (5G System) as a system for realizing the 5G mobile communication system (see Non-Patent Document 1). In 5GS, technical issues for connecting a wide variety of terminals to a cellular network are being extracted and solutions are being specified. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 24.501 V17.4.1 (2021-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) Summary of the Invention [Problem to be solved by the invention]

[0005] In the 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services.

[0006] Furthermore, in 5G, network slices, which are logical networks that provide specific network functions or specific network characteristics for a specific service type or a specific group, are defined. For example, a network slice may be a logical network provided for a terminal with a low latency function, or a logical network provided for a sensor terminal used in the Internet of Things (IoT).

[0007] Furthermore, 3GPP is studying Enhancement of Network Slicing (eNS) to consider further functions related to network slicing. In Phase 2 of eNS, 3GPP is considering adding a function for managing the number of UEs permitted per slice or the number of sessions to be connected (Network Slice Admission Control (NSAC)).

[0008] Furthermore, we are studying eNPN (enhanced NPN) as a work item to enhance NPN (Non-Public Network), and are considering adding an onboarding service function for NPN.

[0009] In addition, 3GPP is also considering supporting the functions of NSSAA and NSAC in a stand-alone non-public network (SNPN), which is one type of NPN.

[0010] However, a practical method for meeting the above requirements is not clear.

[0011] The present invention has been made in consideration of the above circumstances, and aims to provide a method for implementing functions for NS and / or SNPN in 5GS. [Means for solving the problem]

[0012] One embodiment of the present invention relates to a UE (User Equipment), which includes a transceiver unit, a control unit, and a memory unit, and the transceiver unit receives a pending NSSAI (Network Slice Selection Assistance Information) IE from a core network, and when the UE is roaming, the control unit replaces the pending NSSAI in the memory unit with one or more mapped S-NSSAI (Single Network Slice Selection Assistance Information) included in the pending NSSAI IE and stores it, and ignores one or more S-NSSAIs of current PLMNs included in the pending NSSAI IE.

[0013] One embodiment of the UE (User Equipment) of the present invention comprises a control unit, a memory unit, and a transceiver unit, wherein the transceiver unit receives a registration acceptance message including a Pending NSSAI1 (Network Slice Selection Assistance Information) IE including one or more first mapped S-NSSAIs (Single Network Slice Selection Assistance Information), and the control unit replaces one or more mapped S-NSSAIs for the Pending NSSAI in the memory unit with the first mapped S-NSSAI. Effect of the Invention

[0014] According to the present invention, it becomes possible to support network slice functions in 5GS SNPN. [Brief description of the drawings]

[0015] [Figure 1]1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). [Diagram 2] A diagram explaining the detailed configuration of a mobile communication system (EPS / 5GS). [Diagram 3] A diagram explaining the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Diagram 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 1 is a diagram illustrating a registration procedure. [Figure 7] FIG. 1 illustrates a network initiated de-registration procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The best mode for carrying out the present invention will now be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which the present invention is applied will be described.

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

[0018] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network _A80, core network _A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6.

[0019] In the following, these devices and functions may be described with abbreviated symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

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

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

[0022] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

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

[0024] Moreover, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. In the E-UTRAN, one or more eNBs (evolved Node B) 45 are arranged. In the following, the eNB 45 may be written with the symbol omitted, such as eNB. In addition, when there are multiple eNBs, the eNBs are connected to each other, for example, by an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.

[0025] Moreover, the access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are arranged in the NG-RAN. In the following, the gNB 122 may be described with the symbol omitted, such as eNB. The 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 an N2 interface or an N3 interface). That is, the gNB is a base station device newly designed for the 5GS, and has a different function from the base station device (eNB) used in the EPS, which is a 4G system. In addition, when there are multiple gNBs, each gNB is connected to each other, for example, by an Xn interface.

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

[0027] NG-RAN refers to a radio access network that connects to a 5GCN, and NR or E-UTRA or both may be used. In other words, NG-RAN may be E-UTRAN.

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

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

[0030] Moreover, the core network_A corresponds to an EPC (Evolved Packet Core). In the EPC, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), an HSS (Home Subscriber Server), etc. are arranged.

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

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

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

[0034] 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 depending on the mobile communication operator.

[0035] Also, in FIG. 1, the PDN and the DN are the same, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a communication terminal connected thereto. Therefore, connecting to the PDN may be connecting to a communication terminal or a server device arranged in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may be transmitting and receiving user data to and from a communication terminal or a server device arranged in the PDN. The PDN may be expressed as the DN, and the DN may be expressed as the PDN.

[0036] In addition, in the following, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device transmits or receives a message and / or executes a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein transmits or receives a message and / or executes a procedure.

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

[0038] Here, IP communication refers to data communication using IP, and data is transmitted and received by IP packets. The IP packet is composed of an IP header and a payload section. The payload section may include data transmitted and received by devices and functions included in EPS and devices and functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by transmitting and receiving application data to which an IP header is not attached, or may be user data transmitted and received by a UE with another header such as a MAC header or an Ethernet (registered trademark) frame header attached.

[0039] In addition, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may include devices not shown in Fig. 2. For example, the core network_A and / or the core network_B and / or the PDN_A and / or the DN_A may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S). The AAA server may be located outside the core network.

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

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

[0042] In this document, when we refer to NW, it can mean either the core network or the access network, or both.

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

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

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

[0046] [2.1. UE device configuration] First, an example of the device configuration of UE (User Equipment) will be described with reference to Fig. 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

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

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

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

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

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

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

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

[0054] The transceiver unit _B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information between the UE and the transceiver unit _B530.

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

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

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

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

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

[0060] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, the AMF can transmit and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN. In addition, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

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

[0062] In addition, the AMF has a function of exchanging control messages with the RAN using the N2 interface, a function of exchanging NAS messages with the UE using the N1 interface, a function of encrypting and protecting the integrity of NAS messages, a registration management (RM) function, a connection management (CM) function, a reachability management function, a mobility management function for UEs, etc., a function of transferring SM (Session Management) messages between the UE and the SMF, an access authentication (access authorization) function, a security anchor functionality (SEA), a security context management (SCM) function, a function of supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function of supporting the transmission and reception of NAS signals with the UE via the N3IWF, and a function of authenticating UEs connected via the N3IWF.

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

[0064] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context, or may be a state in which each device has established a PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration, and / or a service request procedure.

[0065] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which the location information of UE_A10 is not known to the network, or a state in which the network cannot reach UE_A10. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or establish a 5GMM context by executing the registration procedure.

[0066] In addition, in the connection management, the CM state of each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have a NAS signaling connection established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have a connection (N2 connection) of the N2 interface and a connection (N3 connection) of the N3 interface. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have a connection (N2 connection) of the N2 interface and / or a connection (N3 connection) of the N3 interface.

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

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

[0069] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be an NF that manages one or more NSIs (Network Slice Instances). In addition, the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared between multiple NSIs.

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

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

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

[0073] The network connection unit _B720 is a functional unit for connecting the SMF to the AMF, and / or the UPF, and / or the PCF, and / or the UDM. In other words, the SMF can use the network connection unit _B720 to transmit and receive user data and / or control information between the AMF, and / or the UPF, and / or the PCF, and / or the UDM.

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

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

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

[0077] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be described with reference to Fig. 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

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

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

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

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

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

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

[0084] 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 an interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. Hereinafter, the user plane may be expressed as U-Plane.

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

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

[0087] [2.6. Other devices and / or functions and / or terms in this embodiment] Next, other devices, functions, terms, and / or identification information and / or messages transmitted, received, stored, and managed by each device will be described.

[0088] The network refers to at least a part of the access network _B, the core network _B, and the DN. Furthermore, one or more devices included in at least a part of the access network _B, the core network _B, and the DN may be referred to as a network or a network device. In other words, when a network transmits, receives, and / or processes messages, it may mean that a device in the network (a network device and / or a control device) transmits, receives, and / or processes messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, and / or processes messages.

[0089] In addition, the SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Further, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, and the like.

[0090] Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure. Each procedure may be initiated by the UE or may be initiated by the NW (network).

[0091] Also, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in a procedure for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, and the like.

[0092] In addition, the procedures for MM or MM procedures may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

[0093] In addition, the 5GS (5G System) service may be a connection service provided using the core network_B 190. Furthermore, the 5GS service may be a service different from the EPS service or may be a service similar to the EPS service.

[0094] In addition, non-5GS services may be services other than 5GS services, and may include EPS services and / or non-EPS services.

[0095] Additionally, the PDN (Packet Data Network) type indicates the type of PDN connection, and can be IPv4, IPv6, IPv4v6, or non-IP. 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 IPv4v6 is specified, it indicates that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it indicates that communication will not be via IP, but rather via a communication method other than IP.

[0096] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN that provides a PDU connectivity service and a UE, but may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and the DN using a PDU session by establishing a PDU session via an access network _B and a core network _B. Here, the external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data between a device such as an application server located in a DN and the DN using a PDU session.

[0097] Each device (UE, and / or access network device, and / or core network device) may manage one or more identification information in association with a PDU session. The identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and may further include other information. Furthermore, when multiple PDU sessions are established, each identification information associated with a PDU session may be the same or different.

[0098] Furthermore, the DNN (Data Network Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN may be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network_B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0099] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of the PDU session, and may be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data is transmitted and received using IPv4. If IPv6 is specified, it indicates that data is transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames are transmitted and received. Also, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data is transmitted and received to an application server or the like in a DN using Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, the PDU session type may include IP. IP can be specified when the UE is capable of using both IPv4 and IPv6.

[0100] Moreover, a PLMN (Public Land Mobile Network) is a communication network that provides mobile wireless communication services. A PLMN is a network managed by an operator, which is a (mobile) communications carrier, and the operator can be identified by a PLMN ID. In this document, PLMN may mean PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). PLMN may mean a core network.

[0101] Furthermore, the UE may store an Equivalent HPLMN list in the USIM to identify one or more EHPLMNs (Equivalent HPLMNs). A PLMN different from the HPLMN and / or the EHPLMN may be a Visited PLMN (VPLMN).

[0102] A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN). Each device may receive, maintain, and / or store an Equivalent PLMN list from the RPLMN to identify one or more Equivalent PLMNs (EPLMNS) that can be used equivalently to the RPLMN in the UE's PLMN selection.

[0103] The current PLMN may be the PLMN requested by the UE, and / or the PLMN selected by the UE, and / or the RPLMN, and / or the PLMN allowed by the network, and / or the PLMN to which the core network device sending or receiving the message belongs.

[0104] The requested PLMN means a destination network of a message when the UE sends a message. Specifically, it may be a PLMN selected by the UE when the UE sends a message. The requested PLMN is a PLMN requested by the UE, and may be a current PLMN. Also, when the UE is in a registered state, the requested PLMN may be a registered PLMN.

[0105] NPN (Non-public network) is a network for non-public specifications. There are two types of NPN: SNPN (Stand-alone non-public network) and PNI-NPN (Public network integrated non-public network). SNPN and PNI-NPN may be deployed in 5GS. In this document, when referring to NPN, it may mean SNPN, PNI-NPN, or both.

[0106] A Stand-alone non-public network (SNPN) is a network operated by an NPN operator and does not depend on network functions provided by a PLMN. In other words, an SNPN is a network independent of a PLMN and can only be accessed by a specific UE. An SNPN may be identified by a PLMN ID and a Network identifier (NID).

[0107] Note that the PLMN ID identifying the SNPN does not need to be unique, for example one or more PLMN IDs reserved for use in private networks may be used for the NPN.

[0108] Also, a Stand-alone Non-Public Network (SNPN) is a network that is identified by an SNPN ID consisting of a combination of a PLMN ID and a Network Identifier (NID) and that only certain UEs are permitted to connect to. The SNPN may also refer to a core network. Here, a UE permitted to connect to the SNPN may be an SNPN enabled UE.

[0109] Furthermore, the UE may store an Equivalent SNPN list in the USIM to identify one or more ESNPNs (Equivalent SNPNs). An SNPN different from the HSNPN and / or the ESNPN may be a Visited PLMN (VPLMN).

[0110] The SNPN to which the UE successfully registers may be the Registered SNPN (RSNPN). Each device may receive from the RSNPN and / or maintain and / or store an Equivalent SNPN list to identify one or more ESNPNs (Equivalent PLMNs) that can be used equivalently to the RSNPN in the UE's PLMN selection or SNPN selection.

[0111] A PNI-NPN (Public network integrated non-public network) is an NPN deployed with the support of a PLMN, in other words, a network that uses the capabilities of a PLMN to implement non-public specifications.

[0112] Onboarding services in SNPN allow an MS (UE) to access an SNPN indicating onboarding using default UE credentials.

[0113] The registration procedure for onboarding services in the SNPN may be an initial registration for onboarding services in the SNPN. Additionally, or the registration procedure for onboarding services in the SNPN may be a registration procedure for registration update due to mobility when the UE is registered for onboarding services in the SNPN. The registration procedure for onboarding services in the SNPN may be expressed as SNPN onboarding registration.

[0114] In the registration procedure for the SNPN onboarding service, MM-based slice admission control for the S-NSSAI for the SNPN onboarding service may not be performed by the AMF or the NF in the core network.

[0115] A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. A UE and / or a network can support a network slice (NW slice; NS) in 5GS. A network slice may also be simply referred to as a slice.

[0116] A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a deployed network slice. Here, an NF is a processing function in a network, which is adopted or defined by 3GPP. An NSI is an entity of an NS, of which one or more are configured in a core network_B. An NSI may also be composed of a virtual network function (NF) generated using a network slice template (NST).

[0117] Here, an NST is associated with resource requirements for providing a required communication service or capability, and is a logical representation of one or more NFs. In other words, an NSI may be a collection within a core network_B190 configured with multiple NFs. An NSI may also be a logical network configured to separate user data delivered by services, etc. An NS may be configured with one or more NFs. An NF configured in an NS may or may not be a device shared with other NSs.

[0118] A UE and / or a device in the network may be assigned to one or more NSs based on registration information such as an NSSAI, an S-NSSAI, an UE usage type, an NSI ID, or one or more NSI IDs, and / or an APN. The UE usage type is a parameter value included in the registration information of the UE that is used to identify the NSI. The UE usage type may be stored in the HSS. The AMF may select an SMF and a UPF based on the UE usage type.

[0119] Also, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying an NS. S-NSSAI may be composed of only SST (Slice / Service type) or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating the expected operation of an NS in terms of functions and services. Also, SD may be information for interpolating SST when selecting one NSI from multiple NSIs indicated by SST. S-NSSAI may be information specific to each PLMN or SNPN, or may be standard information common to PLMNs or SNPNs.

[0120] The S-NSSAI may also be transmitted and received between each device using the 5GS S-NSSAI IE, in which case the S-NSSAI may be composed of the S-NSSAI (SST and / or SD) associated with the current PLMN or SNPN, and / or the S-NSSAI (SST and / or SD) of the HPLMN (if any, e.g., when the UE is roaming or the current PLMN or SNPN is a VPLMN or SNPN).

[0121] The network may also store one or more S-NSSAIs in the registration information of the UE as default S-NSSAIs, and if the S-NSSAI is the default S-NSSAI, the network may provide the NS related to the UE when the UE does not send a valid S-NSSAI to the network in the registration request message.

[0122] Furthermore, the S-NSSAI transmitted and received between the UE and the NW may be expressed as an S-NSSAI IE (Information element). Furthermore, the S-NSSAI IE transmitted and received between the UE and the NW may be configured with an S-NSSAI configured with an SST and / or SD of a registered PLMN or SNPN, and / or an SST and / or SD indicating an S-NSSAI of an HPLMN or HSNPN to which the S-NSSAI is mapped. One or more S-NSSAIs stored by the UE and / or the NW may be configured with an SST and / or SD, or may be configured with an S-NSSAI configured with an SST and / or SD, and / or an SST and / or SD indicating an S-NSSAI of an HPLMN to which the S-NSSAI is mapped.

[0123] Moreover, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information to assist the access network or core network in selecting an NSI. The UE may store an NSSAI allowed by the network for each PLMN or SNPN. The NSSAI 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) to a PLMN and an EPLMN, or to an SNPN and an ESNPN.

[0124] A mapped S-NSSAI is an S-NSSAI of a HPLMN that is mapped to an S-NSSAI of a registered PLMN in a roaming scenario. The UE may store one or more mapped S-NSSAIs that are mapped to the configured NSSAI and the S-NSSAI included in the allowed NSSAI for each access type. In addition, the UE may store one or more mapped S-NSSAIs of the rejected NSSAI and / or the S-NSSAI included in the pending NSSAI.

[0125] If a roaming scenario of an SNPN is supported, the mapped S-NSSAI may be the S-NSSAI of the HSNPN mapped to the S-NSSAI of the registered SNPN.

[0126] The Network Slice-Specific Authentication and Authorization (NSSAA) function is a function for realizing authentication and authorization specific to a network slice. With network slice-specific authentication and authorization, authentication and authorization of a UE can be performed outside the core network, such as by a 3rd party. A PLMN or SNPN and a network device equipped with the NSSAA function can perform an NSSAA procedure for a certain S-NSSAI based on the registration information of the UE. Furthermore, a UE equipped with the NSSAA function can manage, store, and transmit / receive a pending NSSAI and a third rejected NSSAI. In this document, NSSAA may be referred to as a network slice-specific authentication and authorization procedure or an authentication and authorization procedure.

[0127] The S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. Furthermore, during roaming, the S-NSSAI requiring an NSSAA may be an S-NSSAI other than the HPLMN or HSNPN, where the S-NSSAI of the HPLMN or HSNPN requiring an NSSAA that is managed by the core network and / or a core network device becomes the mapped S-NSSAI.

[0128] The core network and / or core network device may store an S-NSSAI that requires an NSSAA by associating the S-NSSAI with information indicating whether an NSSAA is required. The core network and / or core network device may further store an S-NSSAI that requires an NSSAA with information indicating whether the NSSAA has been completed, or information indicating that the NSSAA has been completed and is permitted or successful. The core network and / or core network device may manage an S-NSSAI that requires an NSSAA as information unrelated to the access network.

[0129] Also, a configured NSSAI is an NSSAI that is provisioned and stored in the UE. The UE may store a configured NSSAI for each PLMN or SNPN. The UE may store a configured NSSAI in association with a PLMN or SNPN.

[0130] In this document, 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. Similarly, a configured NSSAI associated with an SNPN may be expressed as a configured NSSAI for the SNPN, or a configured NSSAI of the SNPN, or a configured NSSAI for the SNPN, or a configured NSSAI associated with the SNPN.

[0131] Also, the UE may not be associated with a PLMN and may store a configured NSSAI that is valid for all PLMNs, and may refer to such configured NSSAI as the "default configured NSSAI." Similarly, the UE may not be associated with a SNPN and may store a configured NSSAI that is valid for all SNPNs, and may refer to such configured NSSAI as the "default configured NSSAI." The UE may not be associated with a PLMN or SNPN and may store a configured NSSAI that is valid for all PLMNs and SPNNs, and may refer to such configured NSSAI as the "default configured NSSAI."

[0132] The configured NSSAI may be associated with multiple PLMNs or SNPNs, where the multiple PLMNs may be EPLMNs and the multiple SNPNs may be ESNPNs.

[0133] The configured NSSAI may be information configured by the network (or PLMN or SNPN). The S-NSSAI included in the configured NSSAI may be expressed as the configured S-NSSAI. The configured S-NSSAI may be transmitted or received using the S-NSSAI IE, in which case the configured S-NSSAI may be configured to include the S-NSSAI (SST and / or SD) and the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any, e.g., when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

[0134] Alternatively, the S-NSSAI (SST and / or SD) of the PLMN or SNPN and the S-NSSAI (SST and / or SD) of the HPLMN or SNPN may be treated independently. Specifically, the configured S-NSSAI of the PLMN or SNPN may be expressed as a "configured S-NSSAI for the PLMN or SNPN" or a "configured S-NSSAI of the PLMN or SNPN" or a "configured S-NSSAI for the PLMN or SNPN."

[0135] Furthermore, the one or more S-NSSAIs of the HPLMN or HSNPN to which the configured S-NSSAI is mapped may be expressed as "one or more mapped S-NSSAIs for the configured NSSAI of the PLMN or SNPN" or "one or more mapped S-NSSAIs of the configured NSSAI of the PLMN or SNPN."

[0136] In other words, the UE may store a "configured NSSAI of the current PLMN or SNPN" in which the S-NSSAI of the current PLMN or SNPN is configured, and may also store "one or more mapped S-NSSAIs for the configured NSSAI of the current PLMN or SNPN" when roaming. The one or more mapped S-NSSAIs for the configured NSSAI may be 3GPP's mapped S-NSSAI(s) for the configured NSSAI.

[0137] The configured NSSAI may be updated by the NW at any time, and the updated configured NSSAI may be transmitted from the NW to the UE based on the update.

[0138] In addition, the requested NSSAI is an NSSAI provided from 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 the S-NSSAI included in the allowed NSSAI or the configured NSSAI stored by the UE.

[0139] The requested NSSAI may be information indicating a network slice requested by the UE. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is transmitted and received in a NAS message or a Radio Resource Control (RRC) message including a Non-Access-Stratum (NAS) message transmitted from the UE to the network, such as a registration request message or a PDU session establishment request message. Here, in a roaming case, the requested NSSAI may include the S-NSSAI of the VPLMN and the S-NSSAI of the mapped HPLMN. In other words, the S-NSSAI (requested S-NSSAI) included in the requested NSSAI may be composed of the S-NSSAI and the mapped S-NSSAI.

[0140] The requested NSSAI may be information including one or more S-NSSAIs associated with a network slice requested by the UE. Note that 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 requested NSSAI 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.

[0141] In other words, the requested NSSAI may be an S-NSSAI included in a configured NSSAI associated with one or more current PLMNs, or an S-NSSAI included in an allowed NSSAI associated with one or more current PLMNs, or a combination of the two. More specifically, the allowed NSSAI associated with the current PLMN may be an allowed NSSAI associated with the current PLMN and the current access type. Furthermore, the requested NSSAI may be a 5GS requested NSSAI.

[0142] In addition, the S-NSSAI included in the requested NSSAI may be an S-NSSAI stored by the UE and not included in the rejected NSSAI associated with the current PLMN or SNPN, and / or an S-NSSAI stored by the UE and not included in the pending NSSAI associated with the current PLMN or SNPN, or an S-NSSAI stored by the UE and not included in the fourth rejected NSSAI associated with the current PLMN or SNPN.

[0143] Furthermore, the S-NSSAI included in the requested NSSAI may be an S-NSSAI for which the back-off timer associated with that S-NSSAI and / or the mapped S-NSSAI of that S-NSSAI is not running in the UE.

[0144] Also, the allowed NSSAI is information indicating one or more network slices for which the UE is allowed. In other words, the allowed NSSAI is information identifying a network slice to which the network allows the UE to connect. The allowed NSSAI may be an allowed NSSAI stored in the UE and / or NW, or may be an allowed NSSAI transmitted from the NW to the UE. In this case, the allowed NSSAI may refer to the allowed NSSAI IE of 3GPP.

[0145] The allowed NSSAI IE sent from the NW to the UE may include a list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN when not roaming.

[0146] When roaming, the allowed NSSAI IE sent from the NW to the UE may include a list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN, and may further include a list of mapped S-NSSAIs, which are the S-NSSAIs of the HPLMN or HSNPN to which the S-NSSAI of the current PLMN or SNPN is mapped.

[0147] In addition, a list of S-NSSAIs of the current PLMN or SNPN that are included in the allowed NSSAI IE and are valid for the current PLMN or SNPN may be referred to as the Allowed NSSAI, and a list of mapped S-NSSAIs that are S-NSSAIs of the HPLMN or HSNPN to which the S-NSSAI of the current PLMN or SNPN is mapped may be referred to as the list of mapped S-NSSAIs of the Allowed NSSAI. Here, the list of mapped S-NSSAIs of the Allowed NSSAI may be the mapped S-NSSAI(s) for the allowed NSSAI for a PLMN of 3GPP. Similarly, the Allowed NSSAI may mean the allowed NSSAI for a PLMN or an SNPN of 3GPP.

[0148] The UE and / or the NW may store and manage the allowed NSSAI for each access (3GPP access or non-3GPP access) as information of the UE. The UE and / or the NW may further manage the allowed NSSAI in association with a registration area.

[0149] Furthermore, the UE and / or NW may store and manage an allowed NSSAI in association with a PLMN or an SNPN as information of the UE. The allowed NSSAI may be associated with multiple PLMNs, where the multiple PLMNs may be EPLMNs, and the multiple SNPNs may be ESNPNs.

[0150] In this document, an allowed NSSAI associated with a PLMN or SNPN and an access type may be expressed as an "allowed NSSAI for a PLMN or SNPN and an access type" or an "allowed NSSAI for an access type of a PLMN or SNPN."

[0151] The S-NSSAI included in the allowed NSSAI may be expressed as the allowed S-NSSAI. The allowed S-NSSAI may be transmitted or received using the S-NSSAI IE, in which case the allowed S-NSSAI (SST and / or SD) may be comprised of the S-NSSAI and the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any, e.g., when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

[0152] Alternatively, the S-NSSAI (SST and / or SD) of the PLMN or SNPN and the S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) of the HPLMN or SNPN may be treated independently. Specifically, the Allowed S-NSSAI of the PLMN or SNPN may be expressed as "allowed S-NSSAI for the PLMN or SNPN" or "allowed S-NSSAI of the PLMN or SNPN" or "allowed S-NSSAI for the PLMN or SNPN."

[0153] Furthermore, one or more S-NSSAIs of the HPLMN or HSNPN to which the allowed S-NSSAI is mapped may be expressed as "one or more mapped S-NSSAIs for an allowed NSSAI of a PLMN or SNPN" or "one or more mapped S-NSSAIs of an allowed NSSAI of a PLMN or SNPN."

[0154] Also, the rejected NSSAI is information indicating one or more network slices that the UE is not permitted to use or request. In other words, the rejected NSSAI is information identifying a network slice to which the network does not permit the UE to connect. The rejected NSSAI transmitted from the NW to the UE may be included in the rejected NSSAI IE or the extended rejected NSSAI IE.

[0155] The rejected NSSAI transmitted and received using the rejected NSSAI IE may be information including one or more combinations of the S-NSSAI (SST and / or SD) and a rejection reason value (rejected S-NSSAI). The rejected NSSAI transmitted and received using the Extended rejected NSSAI IE may be information including one or more combinations of the S-NSSAI (SST and / or SD) and the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any, e.g., when the UE is roaming or when the associated PLMN or SNPN is a VPLMN or VSNPN) and a rejection reason value (rejected S-NSSAI) in roaming.

[0156] The Extended rejected NSSAI IE may include one or more Rejected S-NSSAs and / or NSSAI sets (5GS Partial extended rejected NSSAI list), and the Rejected S-NSSAI set may include information indicating the type of the set.

[0157] The information indicating the type of the set may be, for example, information indicating that the set includes one or more rejected S-NSSAIs (SST and / or SD) with associated back-off timer values, or information indicating that the set includes one or more rejected S-NSSAIs (SST and / or SD) without associated back-off timer values.

[0158] If the information indicating the type of the set is information indicating that the set contains one or more rejected S-NSSAIs with associated back-off timer values, the set of rejected S-NSSAIs may include a back-off timer value.

[0159] Here, the S-NSSAI included in the rejected NSSAI may be associated with a PLMN ID or an SNPN ID. Note that the PLMN or SNPN indicated by the PLMN ID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI may be the current PLMN or the current SNPN. Alternatively, the PLMN ID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI may be information indicating an HPLMN or an HSNPN, regardless of the current PLMN or SNPN.

[0160] Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI or the combination of the corresponding S-NSSAI and the mapped S-NSSAI (if any). The UE and / or the network may store and manage each S-NSSAI and / or the mapped S-NSSAI (if any) as an appropriate rejected NSSAI and / or the mapped S-NSSAI of the rejected NSSAI based on the rejection reason value associated with each S-NSSA or the combination of the corresponding S-NSSAI and the mapped S-NSSAI.

[0161] Furthermore, the rejected NSSAI may be included in an NAS message transmitted from the network to the UE, such as a registration accept message, a configuration update command, a registration reject message, etc., or an RRC message including an NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI.

[0162] The rejected NSSAI may be transmitted using the Rejected NSSAI IE when the UE is roaming, or may be transmitted using the Extended rejected NSSAI IE. The Extended rejected NSSAI IE may include one or more rejected S-NSSAI (IEs) consisting of the S-NSSAI (SST and / or SD) of the current PLMN or SNPN, the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) and a rejection reason value, and the UE may understand that the request to the NW for the received S-NSSAI of the current PLMN or SNPN together with the received mapped S-NSSAI has been rejected. On the other hand, the Rejected NSSAI IE may include a rejected S-NSSAI IE with the S-NSSAI of the current PLMN or SNPN and a rejection reason value, and the UE may understand that the request to the NW for the S-NSSAI associated with the received S-NSSAI of the current PLMN or SNPN, or the S-NSSAI of the HPLMN or HSNPN, has been rejected.

[0163] The rejected NSSAI may be any one of the first to fourth rejected NSSAIs, one or more mapped S-NSSAIs for the first rejected NSSAI, one or more mapped S-NSSAIs for the second rejected NSSAI, and one or more mapped S-NSSAIs for the fourth rejected NSSAI, or a combination thereof. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI. The rejected S-NSSAI may be transmitted and received between each device using the S-NSSAI IE, and the S-NSSAI IE indicating the rejected NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI.

[0164] The UE and / or NW may store and manage the rejected NSSAI associated with the PLMN or SNPN as information of the UE. The rejected NSSAI may be further associated with one or more other PLMNs or SNPNs, where the one or more other PLMNs may be EPLMNs and the one or more other SNPNs may be ESNPNs.

[0165] In this document, the rejected NSSAI associated with the PLMN or SNPN may be expressed as a rejected NSSAI for the PLMN or SNPN, a rejected NSSAI of the PLMN or SNPN, or a rejected NSSAI for the PLMN or SNPN. The UE and / or NW may further store the second rejected NSSAI and / or the second rejected S-NSSAI in association with the registration area. The UE and / or NW may store the second rejected NSSAI and / or the second rejected S-NSSAI in association with the access type and / or the registration area.

[0166] Here, the first rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current PLMN or the current SNPN. The first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN of 5GS, a rejected S-NSSAI for the current PLMN or SNPN, an S-NSSAI included in the rejected NSSAI for the current PLMN or SNPN, a mapped S-NSSAI(s) for rejected S-NSSAI for the current PLMN or SNPN, or an S-NSSAI included in the mapped S-NSSAI(s) for rejected S-NSSAI for the current PLMN or SNPN. The list (set) of mapped S-NSSAIs for the first rejected NSSAI may be one or more mapped S-NSSAIs for the first rejected NSSAI, or may be the 5GS mapped S-NSSAI(s) for the rejected NSSAI for the current PLMN or SNPN. The first rejected NSSAI may be a rejected NSSAI stored by the UE or NW, or may be a rejected NSSAI transmitted from the NW to the UE.

[0167] When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, it includes one or more S-NSSAIs that are rejected because they are not available in the current PLMN or the current SNPN among the S-NSSAIs included in the requested NSSAI transmitted by the UE to the NW. In this case, the first rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. The rejection reason value at this time may be "S-NSSAI not available in the current PLMN or SNPN" 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 a first rejected S-NSSAI.

[0168] If the first rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the first rejected NSSAI may be transmitted and received in a rejected NSSAI IE or an extended rejected NSSAI IE. The rejected NSSAI IE or the extended rejected NSSAI IE may include at least one combination of the S-NSSAI of the current PLMN or SNPN and a rejection reason value. If the UE is roaming, the combination may further include a mapped S-NSSAI, which is the S-NSSAI of the HPLMN.

[0169] In other words, in a roaming case, the first rejected NSSAI sent from the NW to the UE may include at least one combination of the S-NSSAI of the current PLMN or SNPN, the mapped S-NSSAI, and a rejection reason value.

[0170] The first rejected NSSAI may be applied to the entire registered PLMN or the entire registered SNPN. The UE and / or NW may treat the first rejected NSSAI and the S-NSSAI included in the first rejected NSSAI as information that does not depend on the access type. In other words, the first rejected NSSAI may be information that is valid for 3GPP access and non-3GPP access.

[0171] The UE may delete the first rejected NSSAI from memory when the UE transitions to an unregistered state in both 3GPP access and non-3GPP access for the current PLMN. In other words, when the UE transitions to an unregistered state for the current PLMN via an access, or when the UE successfully registers to a new PLMN via an access, or when the UE fails to register to the new PLMN via an access and transitions to an unregistered state, and when the UE is not registered via the other access (unregistered state), the UE deletes the first rejected NSSAI. In other words, when the UE transitions to an unregistered state for the current PLMN via an access, and when the UE is registered to the current PLMN via the other access (registered state), the UE does not need to delete the first rejected NSSAI.

[0172] The S-NSSAI or the first rejected NSSAI included in the first rejected NSSAI may be the S-NSSAI of the current PLMN. In other words, the S-NSSAI or the first rejected NSSAI included in the first rejected NSSAI may be associated with only the current PLMN ID or SNPN ID and may be stored and / or managed and / or transmitted and received. Further / or, the S-NSSAI included in the first rejected NSSAI may be the S-NSSAI of the HPLMN or the S-NSSAI of the current PLMN.

[0173] The second rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current registration area. The second rejected NSSAI may be a rejected NSSAI of 5GS for the current registration area, may be a mapped S-NSSAI(s) for rejected NSSAI for the current registration area, or may be an S-NSSAI included in the mapped S-NSSAI(s) for rejected NSSAI for the current registration area. The list (set) of mapped S-NSSAI of the second rejected NSSAI may be one or more mapped S-NSSAIs for the second rejected NSSAI, or may be the mapped S-NSSAI(s) of 5GS for the rejected NSSAI for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored by the UE or NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. In this case, the rejection reason value 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 not available in the current registration area. The S-NSSAI included in the second rejected NSSAI may be expressed as a second rejected S-NSSAI.

[0174] If the second rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the UE includes one or more S-NSSAIs that were rejected because they are not available in the current registration area among the S-NSSAIs included in the requested NSSAI by the UE. In this case, the second rejected NSSAI may be transmitted and received in a rejected NSSAI IE or an extended rejected NSSAI IE. The rejected NSSAI IE or the extended rejected NSSAI IE may include at least one combination of the S-NSSAI of the current PLMN or SNPN and a rejection reason value. If the UE is roaming, the combination may further include a mapped S-NSSAI, which is the S-NSSAI of the HPLMN.

[0175] In other words, in a roaming case, the second rejected NSSAI sent from the NW to the UE may include at least one combination of the S-NSSAI of the current PLMN or SNPN, the mapped S-NSSAI, and a rejection reason value.

[0176] The second rejected NSSAI may be valid in the current registration area and may be applied to the current registration area. The UE and / or NW may treat the second rejected NSSAI and the S-NSSAI included in the second rejected NSSAI as information for each access type. That is, the second rejected NSSAI may be information valid for each of 3GPP access and non-3GPP access. That is, once the UE transitions to an unregistered state for an access, the UE may delete the second rejected NSSAI associated with the access from memory.

[0177] The S-NSSAI or the second rejected NSSAI included in the second rejected NSSAI may be the S-NSSAI of the current PLMN. In other words, the S-NSSAI or the second rejected NSSAI included in the second rejected NSSAI may be associated with only the current PLMN ID or SNPN ID and may be stored and / or managed and / or transmitted / received. Or, the S-NSSAI included in the second rejected NSSAI may be the S-NSSAI of the HPLMN or the S-NSSAI of the current PLMN.

[0178] The third rejected NSSAI is a set of one or more S-NSSAIs that require an NSSAA and for which the NSSAA for the S-NSSAI has failed or been revoked. The third rejected NSSAI may be an NSSAI stored by the UE and / or the NW, or may be an NSSAI transmitted and received between the NW and the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. The rejection reason value at this time may be "S-NSSAI not available due to the failed or revoked NSSAA" or may be information indicating that the NSSAA for the S-NSSAI associated with the rejection reason value has failed or been revoked. The S-NSSAI included in the third rejected NSSAI may be expressed as the third rejected S-NSSAI.

[0179] If the third rejected NSSAI is an NSSAI sent from the NW to the UE, the third rejected NSSAI may be transmitted or received using a rejected NSSAI IE or an extended rejected NSSAI IE.

[0180] The third rejected NSSAI may apply to a registered PLMN or a registered SNPN, or may apply to a registered PLMN and / or EPLMN, or may apply to a registered SNPN and / or ESNPN, or may apply to all PLMNs or SNPNs. The third rejected NSSAI applies to all PLMNs may mean that the third rejected NSSAI is not associated with a PLMN, or may mean that the third rejected NSSAI is associated with a HPLMN or HSNPN.

[0181] Furthermore, the UE and / or NW may treat the third rejected NSSAI 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 an NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI. The third rejected NSSAI may be the rejected NSSAI for the failed or revoked NSSAA of 5GS, the rejected S-NSSAI for the failed or revoked NSSAA, or the S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA.

[0182] The third rejected NSSAI is a rejected NSSAI that identifies a slice that the UE has rejected due to a failure or revocation of the NSSAA from the core network. Specifically, while the UE stores the third rejected NSSAI, the UE does not initiate a registration request procedure for the S-NSSAI included in the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAIs received from the core network in association with a rejection reason value indicating a failure of the NSSAA.

[0183] The third rejected NSSAI is information that does not depend on the access type. Specifically, when the UE stores the third rejected NSSAI, the UE does not need to attempt to transmit a registration request message including the S-NSSAI included in the third rejected NSSAI to both 3GPP access and non-3GPP access. Alternatively, the UE can transmit a registration request message including the S-NSSAI included in the third rejected NSSAI based on a UE policy.

[0184] Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which the UE can transmit a registration request message including an S-NSSAI included in the third rejected NSSAI. In other words, when the UE transmits a registration request message including an S-NSSAI included in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI.

[0185] During roaming, the S-NSSAI included in the third rejected NSSAI may be the S-NSSAI of the HPLMN. In other words, the third rejected NSSAI received by the UE from the VPLMN or VSNPN may include the S-NSSAI of the HPLMN or HSNPN.

[0186] In other words, the UE and / or each device may store the "third rejected NSSAI" in which the S-NSSAI of the HPLMN or HSNPN is configured. That is, even during roaming, the "third rejected NSSAI" may be stored without being associated with the mapped S-NSSAI.

[0187] The fourth rejected NSSAI is information including one or more S-NSSAIs that have reached the maximum number of UEs per network slice. The fourth rejected NSSAI may be an NSSAI stored by the UE and / or the NW, or may be an NSSAI transmitted from the NW to the UE.

[0188] The fourth rejected NSSAI may be a 5GS rejected NSSAI for the maximum number of UEs reached, may be a rejected S-NSSAI for the maximum number of UEs reached, may be an S-NSSAI included in the rejected NSSAI for the maximum number of UEs reached, may be a mapped S-NSSAI(s) for the maximum number of UEs reached, or may be an S-NSSAI included in the mapped S-NSSAI(s) for the maximum number of UEs reached. The list (set) of mapped S-NSSAI for the fourth rejected NSSAI may be one or more mapped S-NSSAI for the fourth rejected NSSAI, or may be a 5GS mapped S-NSSAI(s) for the maximum number of UEs reached.

[0189] When the fourth rejected NSSAI is transmitted from the NW to the UE, the fourth rejected NSSAI may include one or more pieces of information including at least one of an S-NSSAI (SST and / or SD), a mapped S-NSSAI (SST and / or SD) (if any), a rejection reason value, and a back-off timer value. In this case, the rejection reason value may be "S-NSSAI not available due to maximum number of UEs reached per network slice" or may be information indicating that the S-NSSAI associated with the rejection reason value can be notified as an Allowed NSSAI or that the maximum number of allowed UEs has been reached.

[0190] Here, the rejection reason value may be a rejection reason value included in the rejected NSSAI. Furthermore, at this time, the back-off timer value may be information indicating a period during which the UE is prohibited from transmitting an MM message using the S-NSSAI of the current PLMN or SNPN associated with one or more S-NSSAIs and / or one or more mapped S-NSSAIs associated with the back-off timer value.

[0191] The fourth rejected NSSAI may apply to a registered PLMN and / or EPLMN, or may apply to a registered SNPN and / or ESNPN, or may apply to one or more PLMNs or SNPNs to which a TAI included in the TA list (TAI list or registration area) belongs.

[0192] The UE and / or NW may treat the fourth rejected NSSAI and the S-NSSAI included in the fourth rejected NSSAI as information for each access type.

[0193] When the fourth rejected NSSAI is an NSSAI transmitted from the NW to the UE, the fourth rejected NSSAI may be transmitted or received using a rejected NSSAI IE or an extended rejected NSSAI IE.

[0194] When the first to fourth rejected NSSAIs are transmitted or received using the rejected NSSAI IE or the extended rejected NSSAI IE, the rejected NSSAI IE and the extended rejected NSSAI IE may include a list of rejected S-NSSAIs.

[0195] When the first to fourth rejected NSSAIs are transmitted and received using the rejected NSSAI IE, the list of rejected S-NSSAIs included in the rejected NSSAI IE may be one or more 5GS Rejected S-NSSAIs. The Rejected S-NSSAI may be configured with the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and the corresponding rejection reason value.

[0196] When the first to fourth rejected NSSAIs are transmitted and received using an Extended rejected NSSAI IE, the list of rejected S-NSSAIs included in the Extended rejected NSSAI IE may be a 5GS Partial extended rejected NSSAI list.

[0197] The rejected S-NSSAI list includes a first type list that does not include a back-off timer value and a second type list that includes a back-off timer value that applies to all S-NSSAIs included in the rejected S-NSSAI list. One or more first type lists and / or one or more second type lists may be configured in the Extended rejected NSSAI IE.

[0198] The first type list may include information indicating that the list is the first type and one or more 5GS Rejected S-NSSAIs. The Rejected S-NSSAI may include the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and a corresponding rejection reason value. Furthermore, the Rejected S-NSSAI may include a mapped S-NSSAI (SST and / or SD).

[0199] The information indicating that the list is of a first type may mean that the list includes one or more S-NSSAIs not with corresponding back-off timer values, in other words, that the list does not include back-off timer values ​​corresponding to one or more S-NSSAIs included in the list.

[0200] The second type list may include information indicating that the list is of the second type, a back-off timer value, and one or more 5GS Rejected S-NSSAIs. The Rejected S-NSSAI may include the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and a corresponding rejection reason value. Furthermore, the Rejected S-NSSAI may include a mapped S-NSSAI (SST and / or SD).

[0201] The information indicating that the list is of the second type may be information indicating that the list contains one or more S-NSSAIs and corresponding back-off timer values, and that the back-off timer value applies to all S-NSSAIs.

[0202] In addition, the back-off timer value included in the second type list may be a value that is applied to all S-NSSAIs included in the same second type list.

[0203] The pending NSSAI may be a pending NSSAI of 5GS. The pending NSSAI may be an NSSAI stored by the UE and / or the NW, or may be an NSSAI transmitted and received between the NW and the UE.

[0204] If the pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI may be sent or received using a pending NSSAI IE configured with one or more S-NSSAI IEs, which may include the S-NSSAI (SST and / or SD) and the mapped S-NSSAI (SST of the mapped HPLMN or HSNPN and / or SD of the mapped HPLMN or HSNPN) (if any, e.g., when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

[0205] The pending NSSAI may apply to the entire registered PLMN or registered SNPN, or may apply to the registered PLMN and one or more EPLMNs of the registered PLMN, or may apply to the registered SNPN and one or more ESNPNs of the registered SNPN.

[0206] 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 common information for 3GPP access and non-3GPP access.

[0207] The pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE is pending a procedure. Specifically, while the UE stores the pending NSSAI, the UE does not initiate a registration request procedure for an S-NSSAI included in the pending NSSAI or a mapped S-NSSAI of the pending NSSAI.

[0208] In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI included in the stored pending NSSAI is completed. The pending NSSAI is information independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to transmit a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0209] During roaming (roaming scenario), the S-NSSAI included in the pending NSSAI stored by the UE may be the S-NSSAI of the HPLMN or HSNPN. In other words, the pending NSSAI IE received by the UE from the VPLMN or VSNPN may include the S-NSSAI of the HPLMN or SNPN. Such a pending NSSAI may be referred to as a first pending NSSAI.

[0210] In other words, a UE that stores a first pending NSSAI does not store a mapped S-NSSAI for the first pending NSSAI, and the S-NSSAI configured in the first pending NSSAI stored by the UE is the S-NSSAI of the HPLMN or HSNPN regardless of whether the UE is roaming or not.

[0211] However, when the first pending NSSAI is sent from the NW to the UE, in other words, when the UE receives a pending NSSAI from the NW, the pending NSSAI IE including the pending NSSAI may include the mapped S-NSSAI of the current S-NSSAI or may include only the mapped S-NSSAI.

[0212] On the other hand, during roaming (roaming scenario), the S-NSSAI included in the pending NSSAI stored by the UE may be the S-NSSAI of the current PLMN (VPLMN) or SNPN (VSNPN). In other words, the pending NSSAI received by the UE from the VPLMN or VSNPN may include the S-NSSAI of the VPLMN or VSNPN. Such a pending NSSAI may be referred to as a second pending NSSAI.

[0213] In other words, when roaming, there may be one or more mapped S-NSSAIs for the second pending NSSAI. The S-NSSAI configured in the second pending NSSAI may be the S-NSSAI of the current PLMN or SNPN regardless of whether roaming or not.

[0214] In this document, a reference to a pending NSSAI may mean the first pending NSSAI, the second pending NSSAI, both pending NSSAIs, or any other pending NSSAI.

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

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

[0217] The TAIs 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.

[0218] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), or a SUPI (Subscription Permanent Identifier), or a GUTI (Globally Unique Temporary Identifier), or an IMEI (International Mobile Subscriber Identity), or an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in an application or a network. Furthermore, the UE ID may be information for identifying a user.

[0219] The management of the maximum number of UEs connected to a slice refers to managing and / or controlling the maximum number of UEs that can be registered in a network slice or an S-NSSAI at the same time, or managing and / or controlling the maximum number of UEs that can establish a PDU session using a network slice or an S-NSSAI at the same time. The management of the maximum number of UEs connected to a slice may be NSAC (network slice admission control) of 5GS. NSAC may be expressed as slice admission control.

[0220] The management and / or control of the maximum number of UEs that can be simultaneously registered in a network slice or an S-NSSAI may be expressed as MM-based slice admission control (Mobility management based slice admission control). The management and / or control of the maximum number of UEs that can simultaneously establish a PDU session using a network slice or an S-NSSAI may be expressed as SM-based slice admission control (Session management based slice admission control). Slice admission control may mean NSAC (Network Slice Admission Control).

[0221] Here, a UE to be registered in a network slice or an S-NSSAI may be stored by including an S-NSSAI indicating a network slice in an allowed NSSAI. A device in a network that supports a function of managing the maximum number of UEs connected to a slice or a function of managing and / or controlling the maximum number of UEs that can be simultaneously registered in a network slice or an S-NSSAI may store, for each S-NSSAI, whether or not management of the maximum number of UEs connected to a slice is required, and may further check whether or not the number of registered UEs has reached a constant, which is the maximum number, during a registration procedure.

[0222] Further, each device that supports a function of managing the maximum number of UEs connected to a slice, or a function of managing and / or controlling the maximum number of UEs that can be simultaneously registered in a network slice or an S-NSSAI, may be capable of storing a fourth rejected NSSAI. In this document, the maximum number of UEs connected to a slice may be expressed as the maximum number of UEs connected per slice, or the maximum number of UEs that can be registered in a network slice or an S-NSSAI, or the maximum number of UEs, or a constant.

[0223] [2.6.1. UE and / or NW behavior regarding equivalent SNPN] The following describes the equivalent SNPN and the behavior of the UE and / or NW with respect to the equivalent NSSAI.

[0224] First, when a UE roams between SNPNs, the SNPN may be classified into a Home SNPN (also referred to as an HSNPN) and a Visited SNPN (also referred to as a VSNPN). In addition, when a UE does not roam between SNPNs, the SNPN may be treated as the same as the Home SNPN.

[0225] The Home SNPN may be an SNPN that the UE can register as its home. The Home SNPN may be an SNPN that the UE first selects in SNPN selection. The Home SNPN may be an SNPN in which at least a portion of information included in an SNPN identity (also referred to as an SNPN ID) matches at least a portion of information included in the IMSI of the UE. The Home SNPN may be an SNPN in which the MCC and MNC included in a PLMN identity (also referred to as a PLMN ID) included in the SNPN identity (also referred to as an SNPN ID) match the MCC and MNC included in the IMSI of the UE.

[0226] The visited SNPN may be an SNPN that the UE can register as a SNPN other than the home. The visited SNPN may be an SNPN that the UE does not register as the home. The visited SNPN may be an SNPN that the UE does not initially select in SNPN selection. The visited SNPN may be an SNPN in which at least a part of information included in the SNPN identity (also referred to as SNPN ID) does not match at least a part of information included in the IMSI of the UE. The visited SNPN may be an SNPN in which the MCC and MNC included in the PLMN identity (also referred to as PLMN ID) included in the SNPN identity (also referred to as SNPN ID) do not match the MCC and MNC included in the IMSI of the UE.

[0227] Furthermore, an equivalent HSNPN (also referred to as equivalent Home SNPN, EHSNPN) may be an SNPN that is regarded as equivalent to a current SNPN (herein also referred to as Home SNPN (HSNPN)) in SNPN selection and / or cell selection and / or cell reselection. Furthermore, an equivalent HSNPN may be one or more SNPNs included in the equivalent HSNPN list, or one or more SNPNs not included in the equivalent VSNPN list.

[0228] Furthermore, an equivalent VSNPN (also referred to as equivalent Visited SNPN, EVSNPN) may be an SNPN that is regarded as equivalent to a current SNPN (herein also referred to as Visited SNPN (VSNPN)) in SNPN selection and / or cell selection and / or cell reselection. Furthermore, an equivalent VSNPN may be one or more SNPNs included in the equivalent VSNPN list, or one or more SNPNs not included in the equivalent HSNPN list.

[0229] Furthermore, the equivalent SNPN (also referred to as ESNPN) may be a concept that includes the equivalent HSNPN and / or the equivalent VSNPN. In other words, the ESNPN may refer to the equivalent HSNPN and / or the equivalent VSNPN.

[0230] Next, an equivalent HSNPN list (also referred to as an EHSNPN list) will be described. In order to provide a plurality of HSNPN codes (also referred to as a Home SNPN code, a Home SNPN identity, or a Home SNPN ID), an SNPN code (also referred to as an SNPN identity or an SNPN ID) present in the EHSNPN list may be replaced with an HSNPN code obtained from an IMSI during or for SNPN selection. The EHSNPN list may be stored in a USIM. The EHSNPN list may include an HSNPN code obtained from an IMSI. If an HSNPN code obtained from an IMSI does not exist in the EHSNPN list, the HSNPN code may be treated as a Visited SNPN during or for SNPN selection.

[0231] Next, an equivalent VSNPN list (also referred to as an EVSNPN list) will be described. In order to provide a plurality of VSNPN codes (also referred to as a Visited SNPN code, a Visited SNPN identity, or a Visited SNPN ID), an SNPN code (also referred to as an SNPN identity or an SNPN ID) present in the EVSNPN list may be replaced with a VSNPN code obtained from an IMSI during or for SNPN selection. The EVSNPN list may be stored in a USIM. The EVSNPN list may include a HVSNPN code obtained from an IMSI. If a VSNPN code obtained from an IMSI does not exist in the EVSNPN list, the VSNPN code may be treated as a Home SNPN during or for SNPN selection.

[0232] In addition, the equivalent SNPN list (also referred to as the ESNPN list) may be a concept that includes the EHSNPN list and / or the EVSNPN list. In other words, the ESNPN list may refer to the EHSNPN list and / or the EVSNPN list.

[0233] In addition, the UE may store an equivalent SNPN list sent from the network. For example, when the UE receives an MM message (e.g., a registration request message or a configuration update command) sent from the AMF, the UE may store the equivalent SNPN list included in the MM message.

[0234] Furthermore, the UE may treat the equivalent SNPN as being equivalent to the current SNPN (Home SNPN or Visited SNPN) during SNPN selection and / or cell selection and / or cell reselection. In other words, when the UE is unable to select the Home SNPN during SNPN selection, the UE may preferentially select an equivalent SNPN (equivalent Home SNPN) that is treated as being equivalent to the Home SNPN. Furthermore, when the UE is unable to select the Home SNPN during cell selection and / or cell reselection in the SNPN, the UE may preferentially select an equivalent SNPN (equivalent Home SNPN) that is treated as being equivalent to the Home SNPN.

[0235] The UE may also update or delete the equivalent SNPN list each time a registration procedure is completed.

[0236] The UE may also maintain an equivalent SNPN list when it is powered off, so that it can be used for SNPN selection upon subsequent power-on.

[0237] The UE may also delete the equivalent SNPN list when the USIM is removed from the UE or when a UE registered for emergency services enters 5GMM-DEREGISTERED.

[0238] The AMF may also include an equivalent SNPN list in a registration accept message in the registration procedure. The equivalent SNPN list may include one or more SNPN codes (also referred to as SNPN IDs), including a combination of a PLMN code (also referred to as PLMN ID) and an NID. If the equivalent SNPN list is included in the registration accept message, the UE may update the equivalent SNPN list stored therein to the received list. If the equivalent SNPN list is not included in the registration accept message, the UE may delete the equivalent SNPN list stored therein.

[0239] In addition, if the UE performs a registration procedure and the procedure is not performed for emergency services, the UE may remove an SNPN code (also referred to as an SNPN ID) that is present in the permanently forbidden SNPNs list or the temporarily forbidden SNPNs list from the equivalent SNPN list.

[0240] The UE may also receive a 5GMM cause value indicating that the UE is an illegal UE, or an illegal ME, or 5GS services not allowed, or Tracking area not allowed, or Roaming not allowed in this tracking area, or No suitable cells in tracking area, or N1 mode not allowed, or Non-3GPP access to 5GCN not allowed (or may be expressed as Non-3GPP access to 5GCN not allowed, etc.), during a registration procedure initiated by the UE. If a registration rejection message is received that does not have the registration rejection protection, the timer T3510 or the timer T3517 that is running may be stopped, and if the timer T3247 is not running, the timer T3247 may be started to delete the equivalent SNPN list.

[0241] The UE may also receive, in a service request procedure initiated by the UE, a 5GSM cause value indicating: illegal UE, or illegal ME, or 5GS services not allowed, or Tracking area not allowed, or Roaming not allowed in this tracking area, or No suitable cells in tracking area, or N1 mode not allowed, or non-3GPP access to 5GCN not allowed (or may be expressed as non-3GPP access to 5GCN not allowed, etc.), or Temporarily not authorized for this SNPN, or Permanently not authorized for this SNPN. When a service refusal message is received for which the SNPN is not protected against the SNPN protection, the SNPN may stop any running timer T3510 or timer T3517, and, if timer T3247 is not running, may start timer T3247 to delete the equivalent SNPN list.

[0242] Also, in a deregistration procedure initiated by the network, if a deregistration request message is received that does not have integrity protection and includes a 5GSM cause value indicating an illegal UE, or an illegal ME, or 5GS services not allowed, or Tracking area not allowed, or Roaming not allowed in this tracking area, or No suitable cells in tracking area, or N1 mode not allowed, or Non-3GPP access to 5GCN not allowed (or may be expressed as Non-3GPP access to 5GCN not allowed, etc.), or Temporarily not authorized for this SNPN, or Permanently not authorized for this SNPN, the equivalent You may delete the SNPN list.

[0243] Furthermore, the UE may include information indicating whether the UE supports an equivalent SNPN or an equivalent SNPN list in a registration request message and transmit the same. Furthermore, the AMF may include information indicating whether the network supports an equivalent SNPN or an equivalent SNPN list in a registration accept message or a registration reject message and transmit the same. Specifically, the AMF may determine whether to include information indicating whether the network supports an equivalent SNPN or an equivalent SNPN list, and the equivalent SNPN list, in a registration accept message or a registration reject message to be transmitted to the UE, based on information indicating whether the UE supports an equivalent SNPN or an equivalent SNPN list, which is included in the registration request message received from the UE.

[0244] For example, if the registration request message includes information indicating that the UE supports an equivalent SNPN or an equivalent SNPN list, and if the AMF supports the equivalent SNPN list and the AMF authorizes the registration request, the AMF may send a registration accept message to the UE including information indicating that the network supports an equivalent SNPN or an equivalent SNPN list and including the equivalent SNPN list.

[0245] In addition, if the registration request message includes information indicating that the UE supports an equivalent SNPN or an equivalent SNPN list, and if the AMF does not support the equivalent SNPN list and the AMF permits the registration request, the AMF may send to the UE a registration accept message including information indicating that the network does not support an equivalent SNPN or an equivalent SNPN list and not including the equivalent SNPN list.

[0246] In addition, if the registration request message includes information indicating that the UE supports an equivalent SNPN or an equivalent SNPN list, and if the AMF supports the equivalent SNPN list and the AMF does not allow the registration request, the AMF may send a registration rejection message to the UE including information indicating that the network supports an equivalent SNPN or an equivalent SNPN list and including the equivalent SNPN list.

[0247] In addition, if the registration request message includes information indicating that the UE supports an equivalent SNPN or an equivalent SNPN list, but the AMF does not support the equivalent SNPN list and does not allow the registration request, the AMF may send to the UE a registration rejection message including information indicating that the network does not support the equivalent SNPN or the equivalent SNPN list and not including the equivalent SNPN list.

[0248] In addition, the UE may recognize whether the network supports the equivalent SNPN or the equivalent SNPN list based on information indicating whether the network supports the equivalent SNPN or the equivalent SNPN list included in the registration accept message or the registration reject message received from the AMF.

[0249] The UE may also recognize an equivalent SNPN for the current SNPN based on the equivalent SNPN list included in the registration accept message or registration reject message received from the AMF.

[0250] [3. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure and a network-initiated de-registration procedure. Each procedure will be described below.

[0251] In each embodiment, as shown in FIG. 2, the case where the HSS and UDM, the PCF and PCRF, the SMF and PGW-C, and the UPF and PGW-U are configured as the same device (i.e., the same physical hardware, or the same logical hardware, or the same software) will be described as an example. However, the contents described in this embodiment are also applicable to the case where these are configured as different devices (i.e., different physical hardware, or different logical hardware, or different software). For example, data may be transmitted and received directly between these, 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.

[0252] [3.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 6. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering to the access network_B, and / or the core network_B, and / or the DN. If the UE is not registered to the network, it can execute this procedure at any timing, such as when the power is turned on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), it can start this procedure at any timing. Furthermore, each device (particularly the UE and the AMF) can transition to a 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 (registered state or non-registered state) for 3GPP access and the registration state for non-3GPP access.

[0253] Furthermore, the registration procedure may 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 certain parameters related to the UE in the network.

[0254] The UE may start the registration procedure when the UE performs mobility across TAs (tracking areas). In other words, the UE may start the registration procedure when the UE moves to a TA different from the TA indicated in the TA list (TAI list or registration area) held by the UE. Furthermore, the UE may start this procedure when a back-off timer or other timer that is being executed expires. Furthermore, the UE may start the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may start the registration procedure when a change occurs in the capability information and / or preferences related to the establishment of a PDU session of the UE. Furthermore, the UE may start the registration procedure periodically. Furthermore, the UE may start the registration procedure based on the completion of a UE configuration update procedure (Generic UE configuration update procedure), or based on the completion of a registration procedure, or based on the completion of a PDU session establishment procedure, or based on 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 stop of a back-off timer. The UE may execute the registration procedure at any timing, not limited to these.

[0255] In addition, the above-mentioned procedure for the UE to transition from a state where it is not registered in the network to a state where it is registered may be referred to as an initial registration procedure or a registration procedure for initial registration, and the registration procedure performed when the UE is registered in the network may be referred to as a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0256] Furthermore, the registration procedure for mobility and periodic registration update may be separate procedures: the registration procedure for mobility registration update and the registration procedure for periodic registration update.

[0257] 6 indicates the AMF to which UE_A10 is registered by this procedure, and old AMF142 means the AMF to which the UE was registered by a procedure prior to this procedure. If no change in AMF occurs in this procedure, the interface between old AMF142 and new AMF141 and the procedure between old AMF142 and new AMF141 do not occur, and new AMF141 may be the same device as old AMF142. In this embodiment, when AMF is written, it may mean new AMF141, old AMF142, or both. Note that new AMF141 and old AMF142 may be AMF140.

[0258] First, the UE_A10 starts the registration procedure by transmitting a registration request message to the new AMF 141 (S600) (S602) (S604). Specifically, the UE transmits an RRC message including the registration request message to the 5G AN 120 (or gNB) (S600). The registration request message is a NAS message transmitted and received on the N1 interface. The RRC message may be a control message transmitted and received between the UE and the 5G AN 120 (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0259] Here, UE_A10 may send a registration request message and / or an RRC message including identification information indicating the type of the procedure.

[0260] Here, the identification information indicating the type of this procedure may be a 5GS registration type IE, and may be information indicating that this procedure is a registration procedure for initial registration, or for updating registration information due to mobility, or for updating registration information due to periodic registration, or for emergency registration, or for SNPN onboarding registration.

[0261] In other words, if this procedure is a registration procedure for initial registration, UE_A10 may send a registration request message including a 5GS registration type IE indicating initial registration. If this procedure is a registration procedure for updating registration information due to mobility, UE_A10 may send a registration request message including a 5GS registration type IE indicating mobility registration updating. If this procedure is a registration procedure for updating registration information periodic, UE_A10 may send a registration request message including a 5GS registration type IE indicating periodic registration updating. If this procedure is an emergency registration, UE_A10 may send a registration request message including a 5GS registration type IE indicating emergency registration. If this procedure is a registration procedure for an SNPN onboarding service, UE_A10 may send a registration request message including a 5GS registration type IE indicating SNPN onboarding registration.

[0262] The UE_A10 may include UE capability information in the registration request message to notify the network of the functions supported by the UE_A10. Here, the UE capability information may be a 5G MM capability IE of 5GS.

[0263] UE_A10 may transmit these identification information and / or IEs in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, the MAC layer, the RLC layer, the PDCP layer). By transmitting these identification information, UE_A10 may indicate that UE_A10 supports each function, may indicate a UE request, or may indicate both. Furthermore, when multiple identification information are transmitted and received, two or more of these identification information may be configured as one or more identification information. Furthermore, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0264] When UE_A10 has a function for managing the maximum number of UEs connecting to a slice or when UE_A10 requests at least one S-NSSAI that requires management for managing the maximum number of UEs connecting to a slice, UE_A10 may transmit capability information indicating that it supports the function for managing the maximum number of UEs connecting to a slice. UE_A10 may notify the network that it has a function for storing a fourth rejected NSSAI by transmitting the capability information.

[0265] Furthermore, if UE_A10 has an NSSAA function or if it requests at least one S-NSSAI that identifies a slice that requires NSSAA and / or an S-NSSAI that identifies a slice that requires NSSAA and is associated with the S-NSSAI as a mapped S-NSSAI, it may send capability information indicating that it supports the NSSAA function in the registration request message. By sending capability information indicating that it supports the NSSAA function, UE_A10 may request the network to treat this UE as a UE with an NSSAA function and to perform authentication and authorization procedures using the NSSAA function in procedures related to the UE.

[0266] If the UE stores an "allowed NSSAI associated with the UE requested PLMN or SNPN and the UE requested access type" and / or stores a "configured NSSAI for the requested PLMN or SNPN" and / or stores a "default configured NSSAI", the UE may send the requested NSSAI IE in a registration request message to the requesting PLMN or SNPN. The requested NSSAI IE may include the requested NSSAI configured in the S-NSSAI (SST and / or SD) of the requested PLMN or SNPN and one or more mapped S-NSSAIs for the requested NSSAI configured in the S-NSSAI (SST and / or SD) of the HPLMN or HSNPN.

[0267] In other words, when the UE is not roaming, the UE may send the requested NSSAI in a registration request message, and when the UE is roaming, the UE may send the requested NSSAI and one or more mapped S-NSSAIs for the requested NSSAI in a registration request message.

[0268] In addition, except when this procedure is a registration procedure for an onboarding service of an SNPN, the UE may include the requested NSSAI in the registration request message.

[0269] Alternatively, when the UE stores "an allowed NSSAI associated with a PLMN other than the PLMN requested by the UE or an SNPN other than the SNPN requested by the UE, and an access type requested by the UE," if a TAI included in a registration area to which the allowed NSSAI or the S-NSSAI included in the allowed NSSAI is associated belongs to the PLMN or SNPN requested by the UE, the UE may include the requested NSSAI in a registration request message and send it to the requested PLMN or SNPN.

[0270] The UE_A10 may determine information included in the requested NSSAI based on one or more NSSAIs stored by the UE. The one or more NSSAIs stored by the UE may be, for example, an allowed NSSAI associated with the requested PLMN or SNPN and the requested access type, and / or one or more mapped S-NSSAIs for the allowed NSSAI, and / or a configured NSSAI associated with the requested PLMN or SNPN, and / or one or more mapped S-NSSAIs for the configured, and / or a default configured NSSAI, and / or a rejected NSSAI associated with the requested PLMN or SNPN, and / or one or more mapped S-NSSAIs for the rejected NSSAI. Furthermore, the one or more NSSAIs stored by the UE may be a pending NSSAI associated with the requested PLMN or SNPN, or one or more mapped S-NSSAIs for the pending NSSAI.

[0271] Further / or, the one or more NSSAIs stored by the UE may be an allowed NSSAI associated with a PLMN or SNPN other than the PLMN or SNPN requested by the UE and an access type requested by the UE, and / or one or more mapped S-NSSAIs for the allowed NSSAI, and / or a second rejected NSSAI associated with a PLMN or SNPN other than the PLMN or SNPN requested and a current registration area, and / or one or more mapped S-NSSAIs for the second rejected NSSAI. Furthermore, the UE_A10 may also store a mapped S-NSSAI for an S-NSSAI included in each NSSAI stored by the UE. The set of the mapped S-NSSAIs may be expressed as one or more mapped S-NSSAIs for each NSSAI, or may be expressed as a list of mapped S-NSSAIs for each NSSAI.

[0272] The UE may select one or more S-NSSAIs from the allowed NSSAIs and / or configured NSSAIs it stores and send them in the requested NSSAI.

[0273] Specifically, if UE_A10 stores an allowed NSSAI associated with the requested PLMN or SNPN and the requested access type, UE_A10 may send the requested NSSAI including the allowed NSSAI, or a part of it, i.e., one or more S-NSSAIs included in the allowed NSSAI.

[0274] Further / or, if UE_A10 stores a configured NSSAI associated with the requested PLMN or SNPN, UE_A10 may send the requested NSSAI including the configured NSSAI, or a portion of it, i.e., one or more S-NSSAIs included in the configured NSSAI.

[0275] Furthermore, if UE_A10 stores a list of mapped S-NSSAIs for the configured NSSAI associated with the requested PLMN or SNPN, UE_A10 may select a mapped S-NSSAI included in the list of mapped S-NSSAIs for the configured NSSAI as the mapped S-NSSAI (SST and / or SD) of the S-NSSAI IE to be included in the requested NSSAI IE, and may send the selected mapped S-NSSAI in the requested NSSAI IE.

[0276] In other words, when roaming, UE_A10 may send one or more S-NSSAI IEs in a registration request message, the S-NSSAI IE being composed of the S-NSSAI of the current PLMN or SNPN and the mapped S-NSSAI of the HPLMN or HSNPN.

[0277] Further / or, if UE_A10 stores "an allowed NSSAI associated with a PLMN other than the requested PLMN or an SNPN other than the requested SNPN and the requested access type", and further, if a TAI included in a registration area (TAI list) associated with that allowed NSSAI or an S-NSSAI included in that allowed NSSAI is associated with the requested PLMN or the requested SNPN, UE_A10 may include that allowed NSSAI or one or more S-NSSAIs included in that allowed NSSAI in the requested NSSAI and send the requested NSSAI in the requested NSSAI IE.

[0278] In other words, UE_A10 may include in the requested NSSAI an "S-NSSAI included in an allowed NSSAI associated with a PLMN other than the requested PLMN or an SNPN other than the requested SNPN and a registration area" stored by the UE, or an "S-NSSAI associated with a registration area included in an allowed NSSAI associated with a PLMN other than the requested PLMN or an SNPN other than the requested SNPN" stored in the UE.

[0279] The requested NSSAI may be configured to include one or more of the above S-NSSAIs. However, UE_A10 may control the one or more S-NSSAIs included in the requested NSSAI so that they do not overlap.

[0280] Below, a general description will be given of a method for controlling the S-NSSAI to be included in the requested NSSAI to be included in the requested NSSAI IE and / or a method for generating the requested NSSAI IE to be included in the "one or more mapped S-NSSAI for the requested NSSAI" to be included in the requested NSSAI IE when UE_A10 stores at least one of the first to fourth rejected NSSAIs. Note that the first to fourth rejected NSSAIs here may refer to the first to fourth rejected NSSAIs associated with the requested PLMN or EPLMN, or the requested SNPN or ESNPN.

[0281] When UE_A10 stores a rejected NSSAI for the requested PLMN or SNPN, UE_A10 may transmit the S-NSSAI contained in the rejected NSSAI without including it in the requested NSSAI IE.

[0282] Specifically, when UE_A10 stores a "first rejected NSSAI associated with the requested PLMN or SNPN," UE_A10 may transmit the S-NSSAI included in the first rejected NSSAI without including it in the requested NSSAI. In other words, UE_A10 may control one or more S-NSSAIs included in the requested NSSAI to be different from the S-NSSAIs included in the "first rejected NSSAI associated with the requested PLMN or SNPN" stored by the UE.

[0283] However, when UE_A10 also stores a list of mapped S-NSSAI for the "first rejected NSSAI associated with the requested PLMN or SNPN," if there is one or more stored mapped S-NSSAIs that are not included in the list of mapped S-NSSAI for the first rejected NSSAI and are included in the list of mapped S-NSSAI for the configured NSSAI, UE_A10 may control so that the S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped can be included in the requested NSSAI.

[0284] When UE_A10 stores one or more mapped S-NSSAI for a first rejected NSSAI when roaming, if UE_A10 further stores one or more mapped S-NSSAI that is not included in the one or more mapped S-NSSAI for the first rejected NSSAI stored by UE_A10 but is included in one or more mapped S-NSSAI for the configured NSSAI, the UE may send the S-NSSAI included in the first rejected NSSAI to which the mapped S-NSSAI is associated together with the mapped S-NSSAI in a registration request message.

[0285] Furthermore, if UE_A10 stores at least one "second rejected NSSAI associated with the requested PLMN or EPLMN or SNPN or ESNPN and the current registration area," UE_A10 may transmit the S-NSSAI included in those second rejected NSSAIs without including it in the requested NSSAI. In other words, UE_A10 may control one or more S-NSSAIs included in the requested NSSAI to be no longer an S-NSSAI included in each "second rejected NSSAI associated with the requested PLMN or EPLMN, or the requested SNPN or ESNPN and the current registration area" stored by UE_A10.

[0286] If the information indicating the current registration area stored by UE_A10 includes a TAI belonging to one or more PLMNs other than the requested PLMN or one or more SNPNs other than the requested SNPN, the different PLMN or one or more SNPNs are the EPLMN of the requested PLMN or the ESNPN of the requested SNPN, and UE_A10 may perform control so that one or more S-NSSAIs included in the requested NSSAI are not S-NSSAIs included in each "second rejected NSSAI associated with one of the different PLMN or SNPNs and the current registration area" stored by UE_A10.

[0287] In other words, if the information indicating the current registration area stored by UE_A10 includes a TAI belonging to one or more PLMNs or SNPNs different from the requested PLMN or SNPN, UE_A10 does not need to include in the requested NSSAI the S-NSSAI included in each "second rejected NSSAI associated with one of the different PLMNs or SNPNs and the current registration area."

[0288] However, when UE_A10 also stores a list of mapped S-NSSAI for the "second rejected NSSAI associated with the requested PLMN or EPLMN, or SNPN or ESNPN and the current registration area," if there is one or more mapped S-NSSAIs stored that are not included in the list of mapped S-NSSAI for the second rejected NSSAI and are included in the list of mapped S-NSSAI for the configured NSSAI, UE_A10 may control so that the S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped can be included in the requested NSSAI.

[0289] When UE_A10 stores one or more mapped S-NSSAIs for a second rejected NSSAI when roaming, if UE_A10 further stores one or more mapped S-NSSAIs that are not included in the one or more mapped S-NSSAIs for the second rejected NSSAI stored by UE_A10 but are included in one or more mapped S-NSSAIs for the configured NSSAI, the S-NSSAI included in the second rejected NSSAI to which the mapped S-NSSAI is associated may be included in and transmitted in a registration request message together with the mapped S-NSSAI.

[0290] Furthermore, when UE_A10 stores a "third rejected NSSAI associated with the requested PLMN or SNPN", UE_A10 may transmit the S-NSSAI included in the third rejected NSSAI without including it in the requested NSSAI IE. In other words, UE_A10 may control one or more S-NSSAIs included in the requested NSSAI IE to be no longer S-NSSAIs included in the "third rejected NSSAI associated with the requested PLMN or SNPN" stored by UE_A10.

[0291] Furthermore, when UE_A10 stores at least one "third rejected NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN," UE_A10 may transmit the S-NSSAI included in the third rejected NSSAI without including it in the requested NSSAI IE. In other words, UE_A10 may control so that one or more S-NSSAIs included in the requested NSSAI IE are not S-NSSAIs included in each "third rejected NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN" stored by UE_A10.

[0292] If UE_A10 does not store either the mapped S-NSSAI of the first rejected NSSAI or the mapped S-NSSAI of the second rejected NSSAI, UE_A10 may control the S-NSSAI of the current PLMN or SNPN to be included in the registration request message so that it is not included in either the first rejected NSSAI or the second rejected NSSAI.

[0293] In other words, if UE_A10 does not store a mapped S-NSSAI for a rejected NSSAI, UE_A10 may control the S-NSSAI of the current PLMN or SNPN to be included in the registration request message so that it is not included in either the first rejected NSSAI or the second rejected NSSAI.

[0294] Furthermore, when UE_A10 roams, if UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI or a mapped S-NSSAI of the second rejected NSSAI, and if UE_A10 stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10 or the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10 but is included in the list of mapped S-NSSAI of the configured NSSAI, the S-NSSAI of the current PLMN or SNPN to be included in the registration request message may be included in the first rejected NSSAI or the second rejected NSSAI stored by UE_A10, the S-NSSAI of the current PLMN or SNPN to be included in the registration request message may be controlled by UE_A10 so that it may be included in the first rejected NSSAI or the second rejected NSSAI stored by UE_A10.

[0295] Furthermore, regardless of whether UE_A10 stores the mapped S-NSSAI of the first rejected NSSAI or the mapped S-NSSAI of the second rejected NSSAI, the S-NSSAI of the current PLMN or SNPN to be included in the registration request message may be controlled by UE_A10 so that it is not included in the third rejected NSSAI.

[0296] In other words, UE_A10 may control the S-NSSAI of the current PLMN or SNPN to be included in the registration request message so that it is not included in the first rejected NSSAI stored by UE_A10, the second rejected NSSAI stored by UE_A10, or the third rejected NSSAI stored by UE_A10. However, when UE_A10 roams, and UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI of the second rejected NSSAI, if UE_A10 also stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10 or the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10 but is included in the list of mapped S-NSSAI of the configured NSSAI, the S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped may be controlled by UE_A10 so that it can be included in the registration request message.

[0297] The S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped may mean the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI.

[0298] Controlling the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI so that it can be included in a registration request message means storing and / or managing the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI as an available S-NSSAI.

[0299] In addition, when UE_A10 roams, when UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI of the second rejected NSSAI, and further when UE_A10 stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10 or the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10 but is included in the list of mapped S-NSSAI of the configured NSSAI, the S-NSSAI of the current PLMN or SNPN mapped to that mapped S-NSSAI may be included in the registration request message together with that mapped S-NSSAI.

[0300] In addition, when UE_A10 roams and stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI of the second rejected NSSAI, the mapped S-NSSAI to be included in the registration request message may be controlled by UE_A10 so that it is a mapped S-NSSAI that is not included in either the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10 or the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10.

[0301] In other words, when UE_A10 roams, if it stores one or more mapped S-NSSAIs for a rejected NSSAI, and if a mapped S-NSSAI included in the one or more stored mapped S-NSSAIs for a configured NSSAI is not included in the one or more mapped S-NSSAIs for the rejected NSSAI, the S-NSSAI included in the configured NSSAI associated with that mapped S-NSSAI can be included in the requested NSSAI together with the mapped S-NSSAI in the registration request message.

[0302] When the UE is not roaming, the S-NSSAI included in the third rejected NSSAI is controlled so as not to be included in the requested NSSAI, and when the UE is roaming, the S-NSSAI associated with the S-NSSAI included in the third rejected NSSAI as a mapped S-NSSAI may not be included in the requested NSSAI.

[0303] In other words, if the UE is not roaming, the S-NSSAI of the current PLMN or SNPN included in the requested NSSAI is included in the configured NSSAI for the current PLMN or SNPN and is not included in the third rejected NSSAI.

[0304] On the other hand, if the UE is roaming, the S-NSSAI of the current PLMN or SNPN included in the requested NSSAI is included in the configured NSSAI for the current PLMN or SNPN, and the S-NSSAI included in the third rejected NSSAI is not associated.

[0305] In further other words, if the UE is not roaming, the UE may include in the requested NSSAI one or more S-NSSAIs that are included in the configured NSSAI for the current PLMN or SNPN and that are not included in the third rejected NSSAI.

[0306] On the other hand, if the UE is roaming, the UE may include in the requested NSSAI an S-NSSAI that is included in the configured NSSAI for the current PLMN or SNPN and is not associated with the S-NSSAI included in the third rejected NSSAI.

[0307] However, when the UE roams, if there is one or more S-NSSAIs included in one or more stored mapped S-NSSAIs for the configured NSSAI that are not included in the third rejected NSSAI, the UE may send the S-NSSAI included in the configured NSSAI for the current PLMN or SNPN with which the S-NSSAI is associated as the mapped S-NSSAI in the registration request message together with the mapped S-NSSAI. Specifically, in that case, the UE may configure the requested NSSAI IE with an NSSAI IE that includes the mapped S-NSSAI and an S-NSSAI with which the mapped S-NSSAI is associated.

[0308] Furthermore, when a back-off timer associated with a certain S-NSSAI is valid, in other words, when the back-off timer is running, or until the back-off timer is stopped, UE_A10 may transmit the S-NSSAI or an S-NSSAI related to the S-NSSAI without including it in the requested NSSAI. Specifically, when the S-NSSAI to which the back-off timer is associated is an S-NSSAI associated with the requested PLMN or SNPN, or an S-NSSAI included in the NSSAI associated with the requested PLMN or SNPN, UE_A10 may transmit the S-NSSAI without including it in the requested NSSAI while the back-off timer is counting, or until the back-off timer expires or is stopped.

[0309] Hereinafter, if the backoff timer corresponding to a certain S-NSSAI included in the fourth rejected NSSAI is valid and / or the backoff timer is running, it may mean that the S-NSSAI is valid and / or the fourth rejected NSSAI is valid.

[0310] Furthermore, when UE_A10 stores a list of mapped S-NSSAIs for the fourth rejected NSSAI, the fourth rejected NSSAI being valid may also mean that the list of mapped S-NSSAIs for the fourth rejected NSSAI, the mapped S-NSSAI for the fourth rejected NSSAI is valid.

[0311] When the list of the fourth rejected NSSAI and / or the mapped S-NSSAI of the fourth rejected NSSAI is managed by UE_A10 regardless of whether the backoff timer is running or not, the list of the valid fourth rejected NSSAI and / or the mapped S-NSSAI of the valid fourth rejected NSSAI may be the fourth rejected NSSAI stored by UE_A10 and / or the list of the mapped S-NSSAI of the fourth rejected NSSAI stored by UE_A10.

[0312] Alternatively, if the S-NSSAI to which the backoff timer is associated is associated with an HPLMN or HSNPN, UE_A10 may send the S-NSSAI of the requested PLMN or SNPN to which the S-NSSAI is mapped without including it in the requested NSSAI.

[0313] Furthermore, when the UE stores the "fourth rejected NSSAI associated with the requested PLMN or SNPN", the UE may transmit the S-NSSAI included in the fourth rejected NSSAI without including it in the requested NSSAI. In other words, the UE may control so that one or more S-NSSAIs included in the requested NSSAI are not S-NSSAIs included in the "fourth rejected NSSAI associated with the requested PLMN or SNPN" stored by the UE.

[0314] Here, in this document, the requested PLMN or SNPN may be the same as the registered PLMN or SNPN.

[0315] Furthermore, if the UE stores at least one "fourth rejected NSSAI associated with the EPLMN of the requesting PLMN or the ESNPN of the SNPN," the UE may transmit the S-NSSAI included in the fourth rejected NSSAI without including it in the requested NSSAI. In other words, the UE may control one or more S-NSSAIs included in the requested NSSAI to be different from the S-NSSAIs included in each "fourth rejected NSSAI associated with the EPLMN of the requesting PLMN or the ESNPN of the SNPN."

[0316] During roaming, UE_A10 may control one or more S-NSSAIs included in the requested NSSAI not to include the mapped S-NSSAI(s) of the rejected NSSAI stored by UE_A10, and / or the mapped S-NSSAI(s) of the pending NSSAI, and / or the S-NSSAI of the HPLMN or HSNPN included in the fourth rejected NSSAI as the mapped S-NSSAI. In other words, UE_A10 may control not to include the S-NSSAI of the current PLMN or SNPN to which the rejected NSSAI, and / or the pending NSSAI, and / or the S-NSSAI included in the fourth rejected NSSAI is mapped in the requested NSSAI.

[0317] In other words, the S-NSSAI included in the requested NSSAI generated by UE_A10 is not included in the rejected NSSAI, pending NSSAI, and / or fourth rejected NSSAI stored by UE_A10 for the mapped S-NSSAI of the S-NSSAI. Here, the rejected NSSAI may be at least one of the first to fourth rejected NSSAIs, and includes the S-NSSAI of the HPLMN or HSNPN.

[0318] Furthermore, when UE_A10 roams, if UE_A10 stores a mapped S-NSSAI of a valid fourth rejected NSSAI, and if UE_A10 stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10 but is included in the list of mapped S-NSSAI of the configured NSSAI, UE_A10 may control so that the S-NSSAI of the current PLMN or SNPN to be included in the registration request message may be included in the fourth rejected NSSAI.

[0319] In other words, UE_A10 may control so that the S-NSSAI of the current PLMN or SNPN to be included in the registration request message is not included in the fourth rejected NSSAI. However, when UE_A10 stores a list of mapped S-NSSAI of the fourth rejected NSSAI when UE_A10 roams, if UE_A10 further stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAI of the fourth rejected NSSAI stored by UE_A10 but is included in the list of mapped S-NSSAI of the configured NSSAI, the S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped may be controlled so as to be included in the registration request message.

[0320] The S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped may mean the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI.

[0321] Controlling the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI so that it can be included in a registration request message means storing and / or managing the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI as an available S-NSSAI.

[0322] In addition, when UE_A10 roams, if UE_A10 stores a list of mapped S-NSSAI for the fourth rejected NSSAI, and UE_A10 further stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAI for the fourth rejected NSSAI stored by UE_A10 but is included in the list of mapped S-NSSAI for the configured NSSAI, it may be controlled so that the S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped can be included in the registration request message together with the mapped S-NSSAI.

[0323] Furthermore, when the UE stores a "pending NSSAI associated with the requested PLMN or SNPN", the UE may transmit an S-NSSAI included in the pending NSSAI without including it in the requested NSSAI IE. In other words, the UE may control such that one or more S-NSSAIs included in the requested NSSAI IE are not S-NSSAIs included in the "pending NSSAI associated with the requested PLMN or SNPN" stored by the UE.

[0324] Furthermore, if the UE stores at least one "pending NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN", the UE may transmit the S-NSSAI included in the pending NSSAI without including it in the requested NSSAI IE. In other words, the UE may control one or more S-NSSAIs included in the requested NSSAI IE to be not S-NSSAIs included in each "pending NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN".

[0325] However, when UE_A10 also stores a list of mapped S-NSSAIs for the "pending NSSAI associated with the requested PLMN or EPLMN or ESNPN of the requested SNPN" (hereinafter referred to as pending NSSAI), if there are one or more mapped S-NSSAIs stored that are not included in the list of mapped S-NSSAIs for the pending NSSAI but are included in the list of mapped S-NSSAIs for the configured NSSAI, UE_A10 may control so that the S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped can be included in the requested NSSAI.

[0326] In other words, if UE_A10 does not store a mapped S-NSSAI of a pending NSSAI but stores a pending NSSAI, the S-NSSAI of the current PLMN or SNPN or the S-NSSAI of the HPLMN or HSNPN (mapped S-NSSAI) to be included in the registration request message may be controlled by UE_A10 to be an S-NSSAI that is not included in the pending NSSAI stored by UE_A10.

[0327] Furthermore, when UE_A10 roams, if UE_A10 stores a pending NSSAI together with a mapped S-NSSAI for the pending NSSAI, and if UE_A10 also stores one or more mapped S-NSSAIs that are not included in the mapped S-NSSAI for the pending NSSAI stored by UE_A10 but are included in the list of mapped S-NSSAIs for the configured NSSAI, the UE may send a registration request message together with the pending NSSAI associated with the mapped S-NSSAI and the S-NSSAI included in the configured NSSAI.

[0328] The following describes the behavior of the UE when roaming or non-roaming in a case where the UE does not store a mapped S-NSSAI for a pending NSSAI. Note that a case where the UE does not store a mapped S-NSSAI for a pending NSSAI may mean that the S-NSSAI included in the pending NSSAI stored by the UE is the S-NSSAI of the HPLMN or HSNPN regardless of whether the UE is roaming or non-roaming.

[0329] When the UE is not roaming, the S-NSSAI included in the pending NSSAI is controlled not to be included in the requested NSSAI, and when the UE is roaming, the S-NSSAI associated with the S-NSSAI included in the pending NSSAI as the mapped S-NSSAI may not be included in the requested NSSAI. The requested NSSAI may be included in the requested NSSAI IE.

[0330] In other words, if the UE is not roaming, the S-NSSAI of the current PLMN or SNPN included in the requested NSSAI is included in the configured NSSAI for the current PLMN or SNPN and is not included in the pending NSSAI.

[0331] On the other hand, if the UE is roaming, the S-NSSAI of the current PLMN or SNPN included in the requested NSSAI is included in the configured NSSAI for the current PLMN or SNPN, and the S-NSSAI included in the pending NSSAI is not associated.

[0332] In other words, if the UE is not roaming, the UE may include in the requested NSSAI one or more S-NSSAIs that are included in the configured NSSAI for the current PLMN or SNPN and that are not included in the pending NSSAI.

[0333] On the other hand, if the UE is roaming, the UE may include an S-NSSAI in the requested NSSAI that is included in the configured NSSAI for the current PLMN or SNPN and that is not associated with an S-NSSAI included in the pending NSSAI.

[0334] However, when the UE is roaming, if there is one or more S-NSSAIs included in one or more stored mapped S-NSSAIs for the configured NSSAI that are not included in the pending NSSAI, the UE may send the S-NSSAI included in the configured NSSAI for the current PLMN or SNPN with which the S-NSSAI is associated as the mapped S-NSSAI in the registration request message together with the mapped S-NSSAI. Specifically, in that case, the UE may configure the requested NSSAI IE with an NSSAI IE that includes the mapped S-NSSAI and an S-NSSAI with which the mapped S-NSSAI is associated.

[0335] Hereinafter, a method for controlling the S-NSSAI and / or the mapped S-NSSAI to be included in the requested NSSAI IE and / or a method for generating the requested NSSAI IE when UE_A10 stores the S-NSSAI in at least one of the first to fourth rejected NSSAIs and the pending NSSAI will be generally described. Note that the first to fourth rejected NSSAIs and the pending NSSAI here may mean the first to fourth rejected NSSAIs and the pending NSSAIs associated with the requested PLMN or EPLMN or the requested SNPN or ESNPN.

[0336] If UE_A10 does not store the mapped S-NSSAI of the first rejected NSSAI, the mapped S-NSSAI of the second rejected NSSAI, or the mapped S-NSSAI of the pending NSSAI, UE_A10 may control the S-NSSAI of the current PLMN or SNPN to be included in the registration request message so that it is not included in the first rejected NSSAI, the second rejected NSSAI, or the pending NSSAI.

[0337] Furthermore, when UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI of the second rejected NSSAI and / or a mapped S-NSSAI of a pending NSSAI, if UE_A10 stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10 or the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10, or the list of mapped S-NSSAI of the pending NSSAI stored by UE_A10, but is included in the list of mapped S-NSSAI of the configured NSSAI, UE_A10 may control so that the S-NSSAI of the current PLMN or SNPN to be included in the registration request message may be included in the first rejected NSSAI, the second rejected NSSAI, or the pending NSSAI.

[0338] In other words, UE_A10 may control the S-NSSAI of the current PLMN or SNPN to be included in the registration request message so that it is not included in the first rejected NSSAI, the second rejected NSSAI, the third rejected NSSAI, or the pending NSSAI. However, when UE_A10 roams, and UE_A10 stores a list of mapped S-NSSAIs of the first rejected NSSAI, or a list of mapped S-NSSAIs of the second rejected NSSAI, or a list of mapped S-NSSAIs of a pending NSSAI, if UE_A10 further stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAIs of the first rejected NSSAI stored by UE_A10, the list of mapped S-NSSAIs of the second rejected NSSAI stored by UE_A10, or the list of mapped S-NSSAIs of the pending NSSAI stored by UE_A10, but is included in the list of mapped S-NSSAIs of the configured NSSAI, the S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is mapped may be controlled so that it can be included in the registration request message.

[0339] The S-NSSAI of the current PLMN or SNPN to which the mapped S-NSSAI is associated may mean the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI.

[0340] Controlling the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI so that it can be included in a registration request message means storing and / or managing the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI as an available S-NSSAI.

[0341] In addition, when UE_A10 roams, if UE_A10 stores a list of mapped S-NSSAIs of the first rejected NSSAI, or a list of mapped S-NSSAIs of the second rejected NSSAI, or a list of mapped S-NSSAIs of a pending NSSAI, and UE_A10 further stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAIs of the first rejected NSSAI stored by UE_A10, the list of mapped S-NSSAIs of the second rejected NSSAI stored by UE_A10, or the list of mapped S-NSSAIs of the pending NSSAI stored by UE_A10, but is included in the list of mapped S-NSSAIs of the configured NSSAI, the UE_A10 may control so that the S-NSSAI of the current PLMN or SNPN mapped to that mapped S-NSSAI can be included in the registration request message together with that mapped S-NSSAI.

[0342] In addition, when UE_A10 roams, when UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI and / or a pending NSSAI of the second rejected NSSAI, the mapped S-NSSAI to be included in the registration request message may be controlled by UE_A10 so that it is a mapped S-NSSAI that is not included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10, the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10, or the pending NSSAI stored by UE_A10.

[0343] The UE_A10 may include other identification information in the registration request message and / or the RRC message including the registration request message, for example, the UE ID and / or the PLMN ID and / or the NID and / or the AMF identification information. Here, the AMF identification information may be information for identifying an AMF or a set of AMFs, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0344] In addition, UE_A10 may initiate a PDU session establishment procedure during the registration procedure by sending a registration request message including an SM message (e.g., a PDU session establishment request message), or by sending an SM message (e.g., a PDU session establishment request message) together with the registration request message.

[0345] Furthermore, UE_A10 may select and decide whether to transmit these identification information to the network based on UE capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, etc.

[0346] When the 5G AN120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S602). In addition, the 5G AN120 (or gNB) can select the AMF based on one or more identification information included in the registration request message and / or the RRC message including the registration request message.

[0347] For example, the 5G AN 120 (or gNB) may select an AMF based on the requested NSSAI. Specifically, the 5G AN (or gNB) may select an AMF that is included in or has connectivity to a network slice identified by an S-NSSAI included in the requested NSSAI.

[0348] The method of selecting an AMF is not limited to this, and the 5G AN (or gNB) may select an AMF based on other conditions. The 5G AN (or gNB) extracts a registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). The 5G AN (or gNB) may transfer identification information that is not included in the registration request message but is included in the RRC message to the selected AMF (new AMF 141) together with the registration request message (S604).

[0349] When the new AMF 141 receives the registration request message, it can execute a first condition determination. The first condition determination is for determining whether or not the network (or the new AMF 141) accepts the UE's request. When the first condition determination is true, the new AMF 141 executes the procedures from S606 to S612. On the other hand, when the first condition determination is false, the new AMF 141 may execute the procedure of S610 without executing the procedures from S606 to S608.

[0350] Alternatively, the new AMF 141 may perform the first condition determination after requesting the UE context from the old AMF 142 and receiving the UE context from the old AMF 142 (S606, S608). In this case, the new AMF 141 may execute S610 and / or S612 when the first condition determination is true. On the other hand, the new AMF 141 may execute S610 when the first condition determination is false.

[0351] Here, if the first condition determination is true, the control message transmitted and received in S610 may be a Registration accept message, and if the first condition determination is false, the control message transmitted and received in S610 may be a Registration reject message.

[0352] Furthermore, the first condition determination may be performed based on receipt of a registration request message, and / or each 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 the AMF, etc.

[0353] For example, if the network permits the UE's request, the first condition determination may be true, and if the network does not permit the UE's request, the first condition determination may be false. Also, if the network to which the UE is registered and / or a device in the network supports the function requested by the UE, the first condition determination may be true, and if the function requested by the UE is not supported, the first condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be false.

[0354] In addition, when the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information identifying a slice requiring an NSSAA procedure, and when the AMF stores the result of the NSSAA procedure of the corresponding S-NSSAI for the UE as successful, the first condition determination may be true. Alternatively, when there is no S-NSSAI to allow the UE and there is no plan to assign an allowed NSSAI to the UE in the future, the first condition determination may be false.

[0355] In addition, when the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information for identifying a slice that requires management of the maximum number of UEs connected to the slice, and further when the maximum number of UEs has not been reached, the first condition determination may be true. Or, even if there is no S-NSSAI permitted for the UE, if it is expected that an allowed NSSAI will be assigned to the UE in the future, the first condition determination may be true.

[0356] When the AMF assigns a fourth rejected NSSAI to the UE when there is no S-NSSAI to permit the UE, the first condition determination may be true or false.

[0357] If the AMF indicated in the AMF identification information included in the message received by the new AMF 141 from the UE is the old AMF 142, the new AMF 141 executes the procedures of S606 and S608, and if the AMF indicated in the AMF identification information included in the message received by the new AMF 141 from the UE_A 10 is the new AMF 141, the new AMF 141 does not execute the procedures of S606 and S608. In other words, if an AMF change occurs due to this procedure, the procedures of S606 and S608 are executed, and if no AMF change occurs, the procedures of S606 and S608 are skipped.

[0358] The UE context transfer procedure (S606, S608) will be described. The new AMF 141 transmits a UE context request message to the old AMF 142 (S606). The old AMF 142 transmits the UE context to the new AMF 141 based on the received UE context request message. The new AMF 141 generates a UE context based on the received UE context.

[0359] Here, the UE context transmitted from new AMF 141 to old AMF 142 may include a UE ID and an allowed NSSAI. Furthermore, the UE context may include a configured NSSAI and / or a rejected NSSAI, an NSSAI and / or a pending NSSAI, and / or a fourth rejected NSSAI. Furthermore, the allowed NSSAI, and / or the configured NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the fourth rejected NSSAI included in the UE context, and the S-NSSAI included in each NSSAI may be linked to information on whether notification to the UE has been completed.

[0360] The UE context may also include information of an S-NSSAI that requires an NSSAA procedure, and / or information indicating that the NSSAA procedure has been completed for the UE, that authentication has been successful, and / or information indicating that authentication has failed.

[0361] The UE context may also include information on an S-NSSAI that requires management of the maximum number of UEs connecting to a slice, and / or information indicating that the maximum number of UEs has been reached, and / or information indicating whether the maximum number of UEs connecting to a slice has been reached.

[0362] In addition, information regarding the characteristics of these S-NSSAIs may be managed as a single piece of information. Specifically, the network may associate and store, for each S-NSSAI, information indicating whether an NSSAA is required, whether the NSSAA was successful, whether management of the maximum number of UEs connecting to the slice is required, and whether the maximum number of UEs connecting to the slice has been reached.

[0363] The new AMF 141 may send a control message to the UE based on the determination of the first condition determination and / or based on receiving the UE context from the old AMF 142 (S610). The control message may be a registration accept message or a registration reject message.

[0364] When new AMF 141 receives a requested NSSAI from the UE, and if the S-NSSAI included in the requested NSSAI requires an NSSAA, it may send the pending NSSAI in a control message.

[0365] Furthermore, when the configuration information of the UE is updated, the new AMF 141 may include the configured NSSAI, and / or the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI in a control message and transmit it to the UE_A10. Note that the message that the new AMF 141 transmits to the UE may be based on information received from the UE. Specifically, the S-NSSAI included in the rejected NSSAI that the new AMF 141 transmits to the UE may be the S-NSSAI included in the requested NSSAI received from the UE.

[0366] When sending a control message, new AMF 141 does not have an S-NSSAI (allowed NSSAI) permitted for the UE, but if there is a plan to execute an NSSAA procedure after completion of this procedure or in parallel with this procedure, or if an NSSAA procedure is being executed between the UE and the network, or if a pending NSSAI IE is sent in the control message, new AMF 141 may send an empty value in the allowed NSSAI.

[0367] When transmitting a control message, new AMF 141 does not have an S-NSSAI (allowed NSSAI) permitted for the UE, but if an Allowed NSSAI is to be included in the control message, or if a fourth rejected NSSAI has been notified to the UE prior to this procedure, new AMF 141 may transmit an empty value in the allowed NSSAI.

[0368] The new AMF 141 may include the Allowed NSSAI in the control message using the Allowed NSSAI IE. Note that the Allowed NSSAI IE may include one or more S-NSSAIs of the current PLMN or SNPN. Furthermore, during roaming, the Allowed NSSAI IE may include one or more mapped S-NSSAIs.

[0369] In addition, the S-NSSAI of a PLMN or SNPN included in the Allowed NSSAI IE may be referred to as the Allowed S-NSSAI of the current PLMN or SNPN. Furthermore, one or more Allowed S-NSSAIs may be referred to as the Allowed NSSAI of the current PLMN or SNPN.

[0370] Furthermore, the mapped S-NSSAI included in the Allowed NSSAI IE may be referred to as the mapped S-NSSAI for the Allowed NSSAI of the PLMN or SNPN, and the mapped S-NSSAI for one or more Allowed NSSAIs of the current PLMN or SNPN may be referred to as one or more mapped S-NSSAI(s) for the Allowed NSSAI of the current PLMN or SNPN.

[0371] The new AMF 141 may include the rejected NSSAI in the control message using the rejected NSSAI IE or the extended rejected NSSAI IE. Note that the rejected NSSAI IE or the extended rejected NSSAI IE may include one or more S-NSSAIs of the current PLMN or SNPN.

[0372] When the new AMF 141 includes a rejected NSSAI in a control message using the Extended rejected NSSAI IE, the new AMF 141 may include the value of the back-off timer in the control message. Alternatively, the new AMF 141 may include the value of the back-off timer in the Extended rejected NSSAI IE and further include the Extended rejected NSSAI IE in the control message and transmit it. Furthermore, during roaming, the Extended rejected NSSAI IE may include one or more mapped S-NSSAIs.

[0373] In addition, the S-NSSAI of the current PLMN or SNPN included in the Extended rejected NSSAI IE may be referred to as the rejected S-NSSAI of the current PLMN or SNPN, and one or more rejected S-NSSAIs may be referred to as the rejected NSSAI of the current PLMN or SNPN. The new AMF 141 may include the pending NSSAI in the control message using the pending NSSAI IE. In addition, the pending NSSAI IE may include one or more S-NSSAIs of the current PLMN or SNPN. Furthermore / or, when roaming, the pending NSSAI IE may include one or more mapped S-NSSAIs.

[0374] UE_A10 receives a control message and / or one or more pieces of information contained in the control message from the network.

[0375] UE_A10 may recognize the received information based on receiving the control message and / or one or more pieces of information contained in the control message.

[0376] Specifically, the UE may store and / or update information related to the NSSAI and start and / or stop a back-off timer, and details of how to store and / or update information related to the NSSAI are described in the NSSAI update and / or storage procedure in Chapter 3.3.

[0377] Note that the NSSAI updating and / or memorization procedures in Section 3.3 may be performed during this procedure or after completion of this procedure. If the NSSAI updating and / or memorization procedures in Section 3.3 are performed after completion of this procedure, they may be performed based on the completion of this procedure.

[0378] Furthermore, the AMF may select or determine the identification information to be included in the control message and / or the information to be notified based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0379] Furthermore, when the control message is a registration acceptance message, the AMF may include an SM message (e.g., a PDU session establishment acceptance message) in the registration acceptance message and send it, or may send an SM message (e.g., a PDU session establishment acceptance message) together with the registration acceptance message. However, this sending method may also be performed when an SM message (e.g., a PDU session establishment request message) is included in the registration request message. Also, this sending method may be performed when an SM message (e.g., a PDU session establishment request message) is sent together with the registration request message. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure.

[0380] In addition, the AMF may indicate that the UE's request has been accepted by sending a registration acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc., or may indicate that the UE's request has been rejected by sending a registration rejection message.

[0381] The UE receives a control message via the 5G AN (gNB) (S608). When the control message is a registration acceptance message, the UE can recognize that the UE's request by the registration request message has been accepted and the contents of various identification information included in the registration acceptance message by receiving the registration acceptance message. Or, when the control message is a registration rejection message, the UE can recognize that the UE's request by the registration request message has been rejected and the contents of various identification information included in the registration rejection message by receiving the registration rejection message. In addition, when the UE does not receive the control message even after a predetermined period has elapsed after transmitting the registration request message, the UE may recognize that the UE's request has been rejected.

[0382] If the control message is a registration acceptance message, the UE may further transmit a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S610). In addition, when the UE receives an SM message such as a PDU session establishment acceptance message, the UE may transmit an SM message such as a PDU session establishment completion message in the registration completion message, or may indicate that the procedure for SM has been completed by including the SM message. Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is transmitted and received in an RRC message between the UE and the 5G AN (gNB).

[0383] The AMF receives a registration completion message via the 5G AN (gNB) (S612). In addition, each device completes this procedure based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0384] Alternatively, each device may complete the registration procedure based on sending or receiving a registration rejection message.

[0385] Each device may transition to or maintain a state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on transmission / reception of a registration acceptance message and / or a registration completion message, and may transition to or maintain a state in which the UE is not registered in the network on the access on which the registration rejection message was received for the current PLMN or SNPN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on transmission / reception of a registration rejection message. Also, the transition to each state of each device may be based on transmission / reception of a registration completion message or completion of the registration procedure.

[0386] Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure based on the completion of the registration procedure. For example, when transmitting and receiving information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's requests have been rejected, or may perform the registration procedure for the core network_A or another cell.

[0387] Further, the UE may store the identification information received with the registration accept message and / or the registration reject message and may recognize the network's decision upon completion of the registration procedure.

[0388] Furthermore, the UE may delete one or more stored NSSAIs based on the completion of the registration procedure. Specifically, based on the completion of the procedure, if UE_A10 transitions to an unregistered state on both accesses (3GPP access and non-3GPP access) for the current PLMN or SNPN, UE_A10 may delete the first rejected NSSAI and / or the third rejected NSSAI and / or the fourth rejected NSSAI stored by UE_A10.

[0389] Further, based on completion of this procedure, UE_A10 may delete a second rejected NSSAI associated with the current PLMN or SNPN, the current registration area, and / or its access type if UE_A10 transitions to an unregistered state on an access (3GPP access and non-3GPP access) for the current PLMN or SNPN, or if UE_A10 successfully completes the registration procedure in the new registration area, or if UE_A10 transitions to an unregistered state or registered state on an access as a result of performing the registration procedure in the new registration area.

[0390] Furthermore, each device may initiate the registration procedure again upon expiration or stopping of the back-off timer.

[0391] Additionally, each device may re-initiate the registration procedure based on the updated NSSAI it stores.

[0392] Furthermore, each device may initiate an SM procedure by sending or receiving an SM message based on the UE transitioning to or maintaining a state in which it is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state).

[0393] [3.2. Network-initiated Deregistration Procedure] Next, a network-initiated de-registration procedure will be described with reference to Fig. 7. Hereinafter, this procedure refers to the network-initiated de-registration procedure. The network-initiated de-registration procedure is a procedure in which the network manually cancels registration with 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 procedure for mobility management that is initiated by the network for a UE registered in the network.

[0394] The AMF may execute this procedure at any time as long as the UE is registered in the network (RM-REGISTERED state or 5GMM-REGISTED state). For example, the AMF may initiate this procedure in response to an update of the UE's registration information. More specifically, the AMF may initiate this procedure when the UE's registration information no longer contains an allowed NSSAI based on the completion of the NSSAA procedure. In other words, the AMF may initiate this procedure when there is no S-NSSAI permitted for the UE and there are no plans to add the S-NSSAI to the allowed NSSAI through other procedures (e.g., the NSSAA procedure) in the future.

[0395] First, the AMF 140 may start this procedure by transmitting a de-registration request message to the UE_A10 (S900). Here, the de-registration request message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0396] The AMF 140 may transmit a non-registration request message including at least one identification information of each NSSAI (hereinafter, meaning rejected NSSAI and pending NSSAI). The AMF may transmit the non-registration request message further including a cause value and / or information indicating the access type to be deregistered. Here, the cause value may be a 5GMM cause. Furthermore, if this procedure is initiated based on the result of an NSSAA procedure or due to completion of the NSSAA, the cause value may be a value indicating that there are no available network slices. In that case, the cause value may be 5GS 5GMM cause value #62 "No network slices available".

[0397] By transmitting these identification information and / or non-registration messages, AMF 140 may indicate that the network does not support each function, may request a transition to a non-registered state, may notify a change in AMF 140, may subsequently instruct the start of a registration procedure, or may indicate a combination of these. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0398] UE_A10 may recognize and store the rejected S-NSSAI and the reason for rejection and determine the UE behavior based on receiving at least one of each NSSAI, and / or receiving the reason value, and / or receiving other identification information, and / or the status of the UE.

[0399] Furthermore, if the UE's configuration information is updated, the new AMF 141 may send at least one of the allowed NSSAI IE, and / or the rejected NSSAI IE, or the extended rejected NSSAI IE, and / or the pending NSSAI IE in the non-registration request message.

[0400] The UE_A10 receives a control message and / or one or more identification information from the network. More specifically, the UE receives a control message and / or one or more identification information from the new AMF141.

[0401] UE_A10 may recognize the received information based on the reception of the control message and / or one or more identification information. Specifically, the UE may store and / or update information related to the NSSAI and start and / or stop the back-off timer, as described in detail in the NSSAI update and / or storage procedure in Chapter 3.3.

[0402] Furthermore, UE_A10 may appropriately store each received NSSAI. Furthermore, UE_A10 may update its stored information regarding the NSSAI based on the received NSSAI. Furthermore, information regarding the NSSAI stored by UE_A10 may be deleted and / or updated based on the state of UE_A10. The specific behavior of how UE_A10 updates its memory regarding the NSSAI and the conditions for updating are described in the NSSAI update and / or storage procedure in Chapter 3.3.

[0403] In addition, the NSSAI update and / or memorization procedures in Chapter 3.3 may be performed during this procedure, or after completion of this procedure, or may be performed based on the completion of this procedure after completion of this procedure.

[0404] UE_A10 receives a non-registration request message via 5G AN (gNB). By receiving the non-registration request message, UE_A10 can recognize the contents of various identification information included in the non-registration request message.

[0405] Upon receiving the deregistration request message, the UE_A10 may transmit a deregistration accept message to the AMF140 via the 5G AN (or gNB) (S902). The deregistration accept message is a NAS message transmitted and received on the N1 interface. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB).

[0406] Each device may transition to a state in which the UE is not registered in the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of the registration acceptance message. In addition, the transition of each device to each state may be performed based on the completion of this procedure.

[0407] Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of the non-registration procedure. For example, UE_A10 may initiate a registration procedure for an SNPN or / PLMN and 3GPP access / or non-3GPP access based on the completion of the non-registration procedure.

[0408] [3.3. NSSAI Updates and / or Memory Procedures] The following describes the procedures for updating and / or storing each NSSAI stored by UE_A10. Note that the NSSAI update procedure by the UE may be performed during each of the other procedures described in Chapter 3, or may be performed based on the completion of each procedure. It may also be performed during other procedures or based on the completion of other procedures. The other procedures may be, for example, a deregistration procedure or a UE configuration update procedure.

[0409] When UE_A10 receives the configured NSSAI, it may store the received configured NSSAI as the "configured NSSAI associated with the current PLMN or SNPN." In other words, UE_A10 may replace the "configured NSSAI associated with the current PLMN or SNPN stored by UE_A10" with the "received configured NSSAI."

[0410] Furthermore, when 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 or SNPN stored by UE_A10." Furthermore, when the "received configured NSSAI" includes one or more mapped S-NSSAIs, UE_A10 may store the one or more mapped S-NSSAIs.

[0411] Furthermore, when UE_A10 receives a configured NSSAI, it may delete the "rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN."

[0412] Alternatively, when UE_A10 receives a configured NSSAI, it may delete at least one of the "first rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN," and the "third rejected NSSAI stored by UE_A10 and associated with the current PLMN."

[0413] Further, when UE_A10 receives a configured NSSAI, it may delete the "fourth rejected NSSAI stored by UE_A10" and / or the "fourth rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" and / or one or more "fourth rejected NSSAIs stored by UE_A10 and associated with the EPLMN of the current PLMN or the ESNPN of the current SNPN".

[0414] Furthermore, when UE_A10 receives the 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 or SNPN", and / or one or more "pending NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN or the ESNPN of the current SNPN" and / or "one or more mapped S-NSSAI for the pending NSSAI stored by UE_A10 and associated with the current PLMN or the SNPN" and / or one or more "one or more mapped S-NSSAI for a second pending NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN or the ESNPN of the current SNPN".

[0415] Furthermore, when UE_A10 receives an allowed NSSAI, it may store the received allowed NSSAI as "the allowed NSSAI associated with the current PLMN or SNPN, the current access type, and." In other words, UE_A10 may replace the "allowed NSSAI associated with the current PLMN or SNPN, the current access type, and" stored by UE_A10 with the "received allowed NSSAI."

[0416] Furthermore, when UE_A10 receives a TAI list and allowed NSSAI from new AMF141, if at least one TAI included in the TAI list belongs to an EPLMN or ESNPN, UE_A10 may replace the "allowed NSSAI associated with the EPLMN or ESNPN to which the TAI included in the TAI list belongs and the current access type" with the received allowed NSSAI.

[0417] In addition, when UE_A10 stores the allowed NSSAI, it may store the allowed NSSAI in association with the registration area, or it may store the S-NSSAI included in the allowed NSSAI in association with the registration area.

[0418] When 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 "old allowed NSSAI updated based on reception". Furthermore, when a mapped S-NSSAI is included in the "received allowed NSSAI IE" by UE_A10, UE_A10 may store the one or more mapped S-NSSAIs.

[0419] When UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI of the "rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN."

[0420] When UE_A10 receives an Allowed NSSAI, it may delete the S-NSSAI contained in the received Allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10 if the following conditions are met. The condition for deleting an S-NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10 may be when UE_A10 is not roaming, or when the mapped S-NSSAI of the S-NSSAI is not stored in UE_A10 as a set of mapped S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI, or when at least one mapped S-NSSAI of the S-NSSAI is stored in UE_A10 in the set of mapped S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI stored in UE_A10 and further when all of those mapped S-NSSAIs are included in the Allowed NSSAI received by the UE, or when the mapped S-NSSAI of the S-NSSAI is included in the Allowed NSSAI received by UE_A10. It may be the case that the S-NSSAI is not included in the NSSAI, or that the S-NSSAI is not associated with multiple mapped S-NSSAI.

[0421] When UE_A10 receives an Allowed NSSAI, it may not delete the S-NSSAI included in the received Allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10. The conditions for not deleting the S-NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10 may be when UE_A10 is roaming, and / or when UE_A10 has stored the mapped S-NSSAI of the S-NSSAI in the list (set) of mapped S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI, and / or when associated with multiple mapped S-NSSAIs, and / or when all of those mapped S-NSSAIs are not included in the new Allowed NSSAI and / or pending NSSAI.

[0422] In addition, the conditions for deleting the S-NSSAI included in the received Allowed NSSAI from the fourth rejected NSSAI and / or pending NSSAI stored by UE_A10 may be similar to the conditions for deleting the S-NSSAI included in the received Allowed NSSAI from the first rejected NSSAI and / or second rejected NSSAI stored by UE_A10.

[0423] When UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI of the second rejected NSSAI during roaming, if UE_A10 receives an Allowed NSSAI IE including a list of mapped S-NSSAI of the new Allowed NSSAI, UE_A10 deletes the S-NSSAI included in the new Allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored, except when UE_A10 stores one or more mapped S-NSSAIs that are not included in the list of mapped S-NSSAI of the new Allowed NSSAI in the list of mapped S-NSSAI of the first rejected NSSAI and / or the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10.

[0424] In other words, when UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI of the second rejected NSSAI during roaming, when it receives an Allowed NSSAI IE including a list of mapped S-NSSAI of the new Allowed NSSAI, UE_A10 deletes the S-NSSAI included in the new Allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored, except when there are one or more mapped S-NSSAIs that are not included in the list of mapped S-NSSAI of the new Allowed NSSAI and are included in the list of mapped S-NSSAI of the first rejected NSSAI and / or the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10.

[0425] In other words, when UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / or a mapped S-NSSAI of the second rejected NSSAI during roaming, when it receives an Allowed NSSAI IE including a list of mapped S-NSSAI of a new Allowed NSSAI, the S-NSSAI to be deleted from the mapped S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10 is included in the received Allowed NSSAI, and further, the S-NSSAI included in the list of mapped S-NSSAI of the Allowed NSSAI mapped to that S-NSSAI includes all of the S-NSSAI included in the list of mapped S-NSSAI of the first rejected NSSAI mapped to that S-NSSAI and / or the S-NSSAI included in the list of mapped S-NSSAI of the second rejected NSSAI.

[0426] When UE_A10 is not roaming, or when UE_A10 is roaming and does not store a mapped S-NSSAI of the first rejected NSSAI or a mapped S-NSSAI of the second rejected NSSAI, if UE_A10 receives an Allowed NSSAI IE including a new Allowed NSSAI, UE_A10 deletes the S-NSSAI included in the new Allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI that it stores.

[0427] When roaming, UE_A10 may behave in such a way that when it receives an Allowed NSSAI, it does not remove the S-NSSAI of the current PLMN or SNPN included in the new Allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI.

[0428] When roaming, UE_A10 may behave such that when it receives an Allowed NSSAI, it removes the S-NSSAI of the current PLMN or SNPN included in the new Allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI.

[0429] When UE_A10 roams and stores the first information consisting of an S-NSSAI and a mapped S-NSSAI in each NSSAI, UE_A10 may delete the combination of the S-NSSAI and the mapped S-NSSAI included in the received Allowed NSSAI IE from the first rejected NSSAI and / or the second rejected NSSAI and the set of mapped S-NSSAI of the first rejected NSSAI and / or the set of mapped S-NSSAI of the second rejected NSSAI.

[0430] Specifically, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI and / or the mapped S-NSSAI of the received allowed NSSAI from at least one of the "first rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN and the current registration area," and the "third rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN," or it may delete the S-NSSAI included in the received allowed NSSAI and / or the mapped S-NSSAI of the received allowed NSSAI from all NSSAIs.

[0431] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "the first pending NSSAI (when not roaming) stored by UE_A10 and associated with the current PLMN or SNPN" or "the second pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN". Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSAI included in the received allowed NSSAI IE from "the first pending NSSAI stored by UE_A10 (when roaming)". Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "the pending NSSAI stored by UE_A10 and associated with the EPLMN or ESNPN".

[0432] Additionally, if a back-off timer that restricts the use of an S-NSSAI is running, the UE may stop the back-off timer if the S-NSSAI is included in the new allowed NSSAI or is a mapped S-NSSAI of an allowed NSSAI.

[0433] Here, in a roaming scenario, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN or HSNPN, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSAI of the S-NSSAI included in the received new allowed NSSAI from the "pending NSSAI stored by UE_A10". At this time, in a roaming scenario, the allowed NSSAI may be associated with a PLMN ID or SNPN ID indicating the current PLMN or current SNPN, i.e., the RPLMN or RSNPN.

[0434] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI contained in the received allowed NSSAI from the "fourth rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN."

[0435] Furthermore, when UE_A10 receives a rejected NSSAI, it may store the S-NSSAI included in the received rejected NSSAI as an appropriate rejected NSSAI based on the rejection reason value associated with the S-NSSAI. In other words, UE_A10 may add "the S-NSSAI included in the received rejected NSSAI" to the rejected NSSAI stored by UE_A10.

[0436] Specifically, when UE_A10 receives a rejection reason value "S-NSSAI not possible in 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 or SNPN.

[0437] Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI not allowed in 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 or SNPN and the current registration area."

[0438] Furthermore, when UE_A10 receives a rejection reason value "S-NSSAI not allowed due to NSSAA failure or cancellation" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the "received rejected S-NSSAI" to the "third rejected NSSAI". In this case, the "third rejected NSSAI" may be associated with the current PLMN or SNPN.

[0439] In addition, if UE_A10 receives a TAI list together with a rejected NSSAI, the current registration area is indicated by the received TAI list. On the other hand, if UE_A10 does not receive a TAI list together with a rejected NSSAI, the current registration area is indicated by the TAI list that UE_A10 previously received and stored.

[0440] Furthermore, when UE_A10 receives a rejected NSSAI including a rejection reason value "S-NSSAI not allowed due to NSSAA failure or cancellation" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add and / or store the S-NSSAI to the third rejected NSSAI. Note that, when the UE stores a third rejected NSSAI associated with the current PLMN or SNPN, it may add and / or store the received S-NSSAI to the third rejected NSSAI associated with the current PLMN or SNPN.

[0441] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI contained in the received rejected NSSAI from the "allowed NSSAI stored by UE_A10 and associated with the current PLMN or SNPN."

[0442] Here, if UE_A10 receives a rejected NSSAI that includes an S-NSSAI of an HPLMN or HSNPN, and if the mapped S-NSSAI of an S-NSSAI included in the "allowed NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" is included in the rejected NSSAI received by UE_A10, UE_A10 may delete the S-NSSAI from the "allowed NSSAI stored by UE_A10 and associated with the current PLMN or SNPN".

[0443] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from the "first pending NSSAI (when not roaming) stored by UE_A10 and associated with the current PLMN or SNPN" and / or the "second pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN". When UE_A10 receives a rejected NSSAI, it may further delete the mapped S-NSSAI or S-NSSAI included in the received allowed NSSAI IE from the "first pending NSSAI stored by UE_A10". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "pending NSSAI stored by UE_A10 and associated with the EPLMN or ESNPN".

[0444] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI contained in the received allowed NSSAI from the "fourth rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN."

[0445] When UE_A10 receives one or more S-NSSAIs included in a rejected NSSAI, it may store the S-NSSAIs based on the rejection reason value associated with each S-NSSAI. Specifically, UE_A10 may store the S-NSSAIs included in the received rejected NSSAI in the set of each rejected NSSAI and / or the set of mapped S-NSSAIs for each rejected NSSAI stored by UE_A10.

[0446] More specifically, if UE_A10 receives a rejected NSSAI IE or an Extended rejected NSSAI IE, and if the rejected S-NSSAI#1 included in the rejected NSSAI IE or Extended rejected NSSAI IE includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI that is not possible in the current PLMN or SNPN," UE_A10 may store the S-NSSAI#1 in the first rejected NSSAI stored by the UE.

[0447] Similarly, if UE_A10 receives a rejected NSSAI IE or an Extended rejected NSSAI IE, and the rejected S-NSSAI#1 included in the rejected NSSAI IE or Extended rejected NSSAI IE further includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI is not possible in the current registration area," UE_A10 may store the S-NSSAI#1 in the second rejected NSSAI stored by the UE.

[0448] Similarly, if UE_A10 receives a rejected NSSAI IE or an Extended rejected NSSAI IE, and the rejected S-NSSAI#1 included in the rejected NSSAI IE or Extended rejected NSSAI IE further includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI that is not possible due to NSSAA failure or cancellation," UE_A10 may store the S-NSSAI#1 in the third rejected NSSAI stored by the UE.

[0449] Alternatively, when UE_A10 receives an Extended rejected NSSAI IE, and further, when the rejected S-NSSAI#1 included in the Extended rejected NSSAI IE includes S-NSSAI#1, mapped S-NSSAI#1, and a rejection reason value indicating "S-NSSAI not allowed in the current PLMN or SNPN", UE_A10 may store S-NSSAI#1 in the first rejected NSSAI stored by the UE, and may store mapped S-NSSAI1#1 in the set of mapped S-NSSAI of the first rejected NSSAI. Alternatively, under the same conditions, UE_A10 may store a combination of S-NSSAI#1 and mapped S-NSSAI1#1 in the first rejected NSSAI stored by the UE.

[0450] Similarly, when UE_A10 receives a rejected NSSAI IE or an Extended rejected NSSAI IE, and further when the rejected S-NSSAI#1 included in the rejected NSSAI IE or Extended rejected NSSAI IE includes the S-NSSAI#1 and a rejection reason value indicating "S-NSSAI not allowed in the current registration area", UE_A10 may include and store the S-NSSAI#1 in the second rejected NSSAI stored by the UE. Alternatively, under the same conditions, UE_A10 may include and store the combination of the S-NSSAI#1 and the mapped S-NSSAI1#1 in the first rejected NSSAI stored by the UE.

[0451] Similarly, when UE_A10 receives a rejected NSSAI IE or an Extended rejected NSSAI IE, and further when the rejected S-NSSAI#1 included in the rejected NSSAI IE or Extended rejected NSSAI IE includes the S-NSSAI#1 and a rejection reason value indicating "S-NSSAI not possible due to NSSAA failure or cancellation", UE_A10 may store the S-NSSAI#1 in the third rejected NSSAI stored by the UE. Alternatively, under the same conditions, UE_A10 may store the combination of the S-NSSAI#1 and the mapped S-NSSAI1#1 in the first rejected NSSAI stored by the UE.

[0452] When UE_A10 receives a rejected NSSAI, it may delete the first rejected NSSAI and / or the S-NSSAI included in the second rejected NSSAI contained in the received rejected NSSAI from the Allowed NSSAI stored by UE_A10 if the following conditions are met. The condition for deleting an S-NSSAI from the Allowed NSSAI stored by UE_A10 may be when UE_A10 is not roaming, or when the mapped S-NSSAI of the S-NSSAI is included in the set of mapped S-NSSAI of the Allowed NSSAI and is not stored by UE_A10, or when at least one mapped S-NSSAI of the S-NSSAI is stored in UE_A10 in the set of mapped S-NSSAI of the Allowed NSSAI stored in UE_A10 and further when all of those mapped S-NSSAIs are included in the first rejected NSSAI and / or the second rejected NSSAI received by the UE, or when the mapped S-NSSAI of the S-NSSAI is not included in the first rejected NSSAI and / or the second rejected NSSAI received by UE_A10, or when the S-NSSAI is included in multiple mapped S-NSSAIs. It may not be associated with the S-NSSAI.

[0453] In addition, a case where the mapped S-NSSAI of the S-NSSAI is not included in the first rejected NSSAI and / or the second rejected NSSAI received by UE_A10 may be a case where UE_A10 receives the first rejected NSSAI and / or the second rejected NSSAI included in the rejected NSSAI IE, or a case where UE_A10 receives an Extended rejected NSSAI IE that does not include a mapped S-NSSAI, includes a rejected S-NSSAI IE, or includes the first rejected NSSAI and / or the second rejected NSSAI.

[0454] When UE_A10 receives a rejected NSSAI, it may not delete the S-NSSAI included in the first rejected NSSAI and / or the second rejected NSSAI included in the received rejected NSSAI from the Allowed NSSAI stored by UE_A10. The conditions for not deleting the S-NSSAI from the Allowed NSSAI stored by UE_A10 may be when UE_A10 is roaming, and / or when UE_A10 stores the mapped S-NSSAI of the S-NSSAI in a list (set) of mapped S-NSSAI of the Allowed NSSAI, and / or when associated with multiple mapped S-NSSAIs, and / or when all of those mapped S-NSSAIs are not included in the first rejected NSSAI and / or the second rejected NSSAI included in the Extended rejected NSSAI IE received by UE_A10.

[0455] In addition, the conditions for deleting the S-NSSAI included in the first rejected NSSAI and / or the second rejected NSSAI included in the received rejected NSSAI from the fourth rejected NSSAI stored by UE_A10 may be similar to the conditions for deleting the S-NSSAI included in the first rejected NSSAI and / or the second rejected NSSAI included in the received rejected NSSAI from the Allowed NSSAI stored by UE_A10.

[0456] When UE_A10 receives a first rejected NSSAI or a second rejected NSSAI during roaming, if one or more mapped S-NSSAIs of the S-NSSAI included in the Allowed NSSAI are not all included in the first rejected NSSAI and / or the second rejected NSSAI, and other mapped S-NSSAIs or some mapped S-NSSAIs are associated with the S-NSSAI and included in the first rejected NSSAI and / or the second rejected NSSAI, the UE_A10 may behave in such a way as not to delete the S-NSSAI from the Allowed NSSAI.

[0457] When roaming, UE_A10 may behave in such a way that when it receives a first rejected NSSAI and / or a second rejected NSSAI, it does not remove the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the Allowed NSSAI.

[0458] When UE_A10 receives a first rejected NSSAI and / or a second rejected NSSAI during roaming, it may remove the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the Allowed NSSAI.

[0459] When UE_A10 roams and stores the first information consisting of an S-NSSAI and a mapped S-NSSAI in each NSSAI, UE_A10 may delete the combination of the S-NSSAI and the mapped S-NSSAI included in the received Extended rejected NSSAIIE from the set of Allowed NSSAI and the mapped S-NSSAI of the Allowed NSSAI.

[0460] When UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI included in the received rejected NSSAI from the set of Allowed NSSAIs of the current PLMN or SNPN and / or the set of mapped S-NSSAIs of the Allowed NSSAIs of the current PLMN or SNPN.

[0461] Specifically, when UE_A10 receives a third rejected NSSAI, and further when roaming, UE_A10 may delete the S-NSSAI included in the third rejected NSSAI from the set of mapped S-NSSAI of the Allowed NSSAI that it stores.

[0462] If UE_A10 receives a third rejected NSSAI and is not roaming, UE_A10 may delete the stored Allowed NSSAI and the S-NSSAI included in the third rejected NSSAI.

[0463] If UE_A10 receives a first rejected NSSAI and / or a second rejected NSSAI included in the Extended rejected NSSAI IE, and further when roaming, UE_A10 may delete the mapped S-NSSAI included in the first rejected NSSAI and / or the second rejected NSSAI included in the received Extended rejected NSSAI IE from the set of mapped S-NSSAI of the Allowed NSSAI that it stores.

[0464] When UE_A10 receives a rejected NSSAI, it may delete the first rejected NSSAI and / or the S-NSSAI included in the second rejected NSSAI contained in the received rejected NSSAI from the pending NSSAI stored by UE_A10 if the following conditions are met. The conditions for deleting an S-NSSAI from the pending NSSAI stored by UE_A10 may be when UE_A10 is not roaming, or when the mapped S-NSSAI of the S-NSSAI is included in the set of mapped S-NSSAI of the Allowed NSSAI and is not stored by UE_A10, or when at least one mapped S-NSSAI of the S-NSSAI is stored in UE_A10 in the mapped S-NSSAI of the pending NSSAI stored in UE_A10 and all of those mapped S-NSSAIs are included in the first rejected NSSAI and / or second rejected NSSAI received by the UE, or when the mapped S-NSSAI of the S-NSSAI is not included in the and / or second rejected NSSAI received by UE_A10, or when the S-NSSAI is not associated with multiple mapped S-NSSAI.

[0465] In addition, a case where the mapped S-NSSAI of the S-NSSAI is not included in the first rejected NSSAI and / or the second rejected NSSAI received by UE_A10 may be a case where UE_A10 receives the first rejected NSSAI and / or the second rejected NSSAI included in the rejected NSSAI IE, or a case where UE_A10 receives an Extended rejected NSSAI IE that does not include a mapped S-NSSAI, includes a rejected S-NSSAI IE, or includes the first rejected NSSAI and / or the second rejected NSSAI.

[0466] When UE_A10 receives a rejected NSSAI, it may not delete the S-NSSAI included in the first rejected NSSAI and / or the second rejected NSSAI included in the received rejected NSSAI from the Pending NSSAI stored by UE_A10. The conditions for not deleting the S-NSSAI from the Pending NSSAI stored by UE_A10 may be when UE_A10 is roaming, and / or when UE_A10 stores the mapped S-NSSAI of the S-NSSAI in a list (set) of mapped S-NSSAI of the Pending NSSAI, and / or when associated with multiple mapped S-NSSAIs, and / or when all of those mapped S-NSSAIs are not included in the first rejected NSSAI and / or the second rejected NSSAI included in the Extended rejected NSSAI IE received by UE_A10.

[0467] In other words, when UE_A10 receives a first rejected NSSAI or a second rejected NSSAI during roaming, if one or more mapped S-NSSAIs of the S-NSSAI included in the Pending NSSAI are not all included in the first rejected NSSAI and / or the second rejected NSSAI, and other mapped S-NSSAIs or some mapped S-NSSAIs are associated with the S-NSSAI and included in the first rejected NSSAI and / or the second rejected NSSAI, the UE_A10 may behave in such a way as not to delete the S-NSSAI from the Pending NSSAI.

[0468] When roaming, UE_A10 may behave in such a way that when it receives a first rejected NSSAI and / or a second rejected NSSAI, it does not delete the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the pending NSSAI.

[0469] When UE_A10 receives a first rejected NSSAI and / or a second rejected NSSAI during roaming, it may delete the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the Pending NSSAI.

[0470] When UE_A10 roams and stores the first information consisting of an S-NSSAI and a mapped S-NSSAI in each NSSAI, UE_A10 may delete the combination of the S-NSSAI and the mapped S-NSSAI included in the received Extended rejected NSSAIIE from the set of mapped S-NSSAI of the Pending NSSAI and Allowed NSSAI.

[0471] When UE_A10 receives a rejected NSSAI, it may remove the S-NSSAI included in the received rejected NSSAI from the set of Allowed NSSAIs of the current PLMN or SNPN and / or the set of mapped S-NSSAIs of the Allowed NSSAIs of the current PLMN or SNPN.

[0472] Specifically, when UE_A10 receives a third rejected NSSAI, and further when roaming, UE_A10 may delete the S-NSSAI included in the third rejected NSSAI from the set of mapped S-NSSAI of the Allowed NSSAI that it stores.

[0473] When UE_A10 receives a third rejected NSSAI, and is not roaming any further, UE_A10 may delete the pending NSSAI it stores and the S-NSSAI included in the third rejected NSSAI.

[0474] If UE_A10 receives a first rejected NSSAI and / or a second rejected NSSAI included in the Extended rejected NSSAI IE, and further when roaming, UE_A10 may delete the mapped S-NSSAI included in the first rejected NSSAI and / or the second rejected NSSAI included in the received Extended rejected NSSAI IE from the set of mapped S-NSSAIs of the pending NSSAI it stores.

[0475] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from the "fourth rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN." Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "fourth rejected NSSAI stored by UE_A10 and associated with the EPLMN or ESNPN."

[0476] Furthermore, if a back-off timer that restricts the use of an S-NSSAI is running, the UE may stop the back-off timer if that S-NSSAI or its mapped S-NSSAI is included in the first to third rejected NSSAIs.

[0477] Furthermore, when UE_A10 receives a pending NSSAI, it may replace the pending NSSAI stored in UE_A10 with a new pending NSSAI. Specifically, when UE_A10 receives a pending NSSAI IE included in a registration acceptance message during the registration procedure for the current PLMN or SNPN, it may replace the pending NSSAI associated with the current PLMN or SNPN stored in UE_A10 with the new pending NSSAI.

[0478] More specifically, when UE_A10 manages the pending NSSAI as a second pending NSSAI, UE_A10 may operate as follows: UE_A10 may replace the pending NSSAI of the current PLMN or SNPN it stores with one or more S-NSSAI(s) of the current PLMN or SNPN included in the received pending NSSAI IE and store it. Furthermore, when roaming, UE_A10 may replace one or more mapped S-NSSAI(s) of the pending NSSAI of the current PLMN or SNPN it stores with one or more current mapped S-NSSAI(s) included in the received pending NSSAI IE and store it.

[0479] Alternatively, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of an HPLMN or HSNPN, when UE_A10 receives the pending NSSAI included in a registration acceptance message during the registration procedure for the current PLMN or SNPN, it may replace the pending NSSAI stored by UE_A10 with a new pending NSSAI.

[0480] Furthermore, when UE_A10 stores a mapped S-NSSAI for a pending NSSAI, UE_A10 may delete the mapped S-NSSAI for the pending NSSAI, may store a mapped S-NSSAI for a new pending NSSAI, or may perform both processes.

[0481] In addition, the mapped S-NSSAI of the pending NSSAI may be stored based on the mapped S-NSSAI of the old allowed NSSAI.

[0482] Additionally, if a back-off timer that restricts the use of an S-NSSAI is running, the UE may stop the back-off timer if the S-NSSAI is included in a new pending NSSAI or is a mapped S-NSSAI of a pending NSSAI.

[0483] If the UE deregisters or enters 5GMM-DEREGISTERED state for the current PLMN or SNPN using explicit signaling, and if the UE is not registered with the current PLMN or SNPN on another access type, the UE may delete the pending NSSAI and / or one or more mapped S-NSSAI(s) for that pending NSSAI associated with the current PLMN or SNPN. If an EPLM or ESNPN exists for the current PLMN or SNPN, the UE may also delete the pending NSSAI and / or the mapped S-NSSAI(s) for that pending NSSAI for the equivalent PLMN(s) of the current PLMN or the equivalent SNPN(s) of the current SNPN.

[0484] If the UE successfully registers to the new PLMN or SNPN, or if registration to the new PLMN or SNPN fails and enters the 5GMM-DEREGISTERED state, and if the UE is not registered to the current PLMN or SNPN on another access type, the UE may delete the pending NSSAI and / or one or more mapped S-NSSAI(s) of that pending NSSAI associated with the current PLMN or SNPN. If an EPLM or ESNPN exists for the current PLMN or SNPN, the UE may also delete the pending NSSAI and / or the mapped S-NSSAI(s) of that pending NSSAI for the equivalent PLMN(s) of the current PLMN or the equivalent SNPN(s) of the current SNPN.

[0485] Or, if registration to a new PLMN or SNPN other than the EPLMN or ESNPN fails and the UE enters the 5GMM-DEREGISTERED state, and if the UE is not registered to the current PLMN or SNPN on another access type, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAI(s) of that pending NSSAI. If an EPLMN or ESNPN of the current PLMN or SNPN exists, the UE may further delete the pending NSSAI of the equivalent PLMN(s) of the current PLMN or the equivalent SNPN(s) of the current SNPN and / or the mapped S-NSSAI(s) of that pending NSSAI. In other words, it may be the following:

[0486] If the registration to a new PLMN other than the equivalent PLMN fails and the 5GMM-DEREGISTERED state is entered, and if the UE is not registered to the current PLMN on another access type, the UE may delete the pending NSSAI(s) associated with the current PLMN and / or one or more mapped S-NSSAI(s) of that pending NSSAI(s). If an EPLMN exists for the current PLMN, the UE may also delete the pending NSSAI(s) of the equivalent PLMN(s) of the current PLMN and / or the mapped S-NSSAI(s) of that pending NSSAI(s).

[0487] If registration to a new SNPN other than an equivalent SNPN fails and 5GMM-DEREGISTERED state is entered, and if the UE is not registered to the current SNPN on another access type, the UE may delete the pending NSSAI(s) associated with the current SNPN and / or one or more mapped S-NSSAI(s) of that pending NSSAI(s). If an ESNPN exists for the current SNPN, the UE may also delete the pending NSSAI(s) of the equivalent SNPN(s) of the current SNPN and / or the mapped S-NSSAI(s) of that pending NSSAI(s).

[0488] Or, if the registration to a new PLMN or SNPN other than the EPLMN or ESNPN is successful, and if the UE is not registered to the current PLMN or SNPN on another access type, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAI(s) of that pending NSSAI. If an EPLMN or ESNPN exists for the current PLMN or SNPN, the UE may further delete the pending NSSAI and / or the mapped S-NSSAI(s) of that pending NSSAI for the equivalent PLMN(s) of the current PLMN or the equivalent SNPN(s) of the current SNPN. In other words, it may be the following:

[0489] If the registration to a new PLMN other than the equivalent PLMN is successful and the UE is not registered to the current PLMN on another access type, the UE may delete the pending NSSAI and / or one or more mapped S-NSSAI(s) of that pending NSSAI associated with the current PLMN. If an EPLMN of the current PLMN exists, the UE may also delete the pending NSSAI and / or the mapped S-NSSAI(s) of that pending NSSAI of the equivalent PLMN(s) of the current PLMN.

[0490] If the registration to a new SNPN other than the equivalent SNPN is successful and the UE is not registered to the current SNPN on another access type, the UE may delete the pending NSSAI associated with the current SNPN and / or one or more mapped S-NSSAI(s) for that pending NSSAI. If an ESNPN for the current SNPN exists, the UE may also delete the pending NSSAI of the equivalent SNPN(s) of the current SNPN and / or the mapped S-NSSAI(s) for that pending NSSAI.

[0491] Or when the Attach procedure or the Tracking Area Update procedure in S1 mode is successfully initiated and the UE operates in single registration mode, and if the UE is not registered to the current PLMN or SNPN on another access type, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAI(s) of that pending NSSAI. If an EPLM or ESNPN exists for the current PLMN or SNPN, the UE may further delete the pending NSSAI of the equivalent PLMN(s) of the current PLMN or the equivalent SNPN(s) of the current SNPN and / or the mapped S-NSSAI(s) of that pending NSSAI.

[0492] In addition, when a pending NSSAI associated with a certain SNPN or PLMN stored in the UE is deleted, the UE may also delete one or more mapped S-NSSAI(s) of the deleted pending NSSAI.

[0493] Further, UE_A10 may perform the following operations for each rejected S-NSSAI IE, or for each Partial extended rejected NSSAI list IE, or for each Extended rejected NSSAI IE, based on reception of one or more rejected S-NSSAI IEs, and / or Partial extended rejected NSSAI list IEs, and / or Extended rejected NSSAI IEs indicating a fourth rejected NSSAI, and / or reception of a control message:

[0494] The UE_A10 may store the S-NSSAI of the current PLMN or SNPN indicated in the fourth rejected NSSAI in an appropriate fourth rejected NSSAI. Specifically, the UE may add the S-NSSAI indicated in the received fourth rejected NSSAI to the fourth rejected NSSAI based on the associated rejection reason value.

[0495] Alternatively, UE_A10 may add the mapped S-NSSAI for the received fourth rejected NSSAI to one or more mapped S-NSSAI for the fourth rejected NSSAI.

[0496] Furthermore, if the S-NSSAI included in the fourth rejected NSSAI stored by the UE is included in the allowed NSSAI stored by the UE and associated with the PLMN or SNPN and access type requested by the UE in this procedure and other access types, the S-NSSAI may be deleted from the allowed NSSAI.

[0497] Based on receipt of the fourth rejected NSSAI and / or receipt of a control message, UE_A10 may start counting the backoff timer associated with the S-NSSAI or may manage the backoff timer using the backoff timer value.

[0498] Here, when UE_A10 receives a fourth rejected NSSAI together with a back-off timer value, and if the value is neither 0 nor information indicating deactivation, the back-off timer value used for the back-off timer may be the received back-off timer value. On the other hand, in other cases, i.e., when a back-off timer value is not received, the back-off timer value used for the back-off timer may be an implementation-specific value.

[0499] While the backoff timer is running, UE_A10 may be in a state where sending MM messages or SM messages using one or more S-NSSAIs associated with the backoff timer, or one or more mapped S-NSSAIs (S-NSSAIs of HPLMN or HSNPN) associated with the backoff timer, or one or more S-NSSAIs related to one or more mapped S-NSSAIs associated with the backoff timer, or one or more S-NSSAIs included in the NSSAI to which the backoff timer is associated, or one or more mapped S-NSSAIs included in the NSSAI to which the backoff timer is associated.

[0500] While the backoff timer is running, UE_A10 may be prohibited from including one or more S-NSSAIs associated with the backoff timer in the requested NSSAI along with the associated mapped S-NSSAI.

[0501] Here, when the back-off timer stops or expires, the restriction is lifted, and UE_A10 may transition to a state in which it can transmit an MM message or an SM message using the S-NSSAI to which the back-off timer was associated, and / or the S-NSSAI related to the mapped S-NSSAI to which the back-off timer was associated, and / or the mapped S-NSSAI to which the back-off timer was associated. In other words, when the back-off timer stops or expires, UE_A10 may transition to a state in which it can transmit an MM message using the S-NSSAI to which the back-off timer was associated, and / or the S-NSSAI related to the mapped S-NSSAI to which the back-off timer was associated, and / or the mapped S-NSSAI to which the back-off timer was associated as the requested NSSAI.

[0502] Furthermore, UE_A10 may transition to a state in which it can transmit an MM message using the NSSAI associated with the back-off timer when the back-off timer stops or expires. In other words, UE_A10 may transition to a state in which it can transmit an MM message using the NSSAI associated with the back-off timer as the requested NSSAI when the back-off timer stops or expires.

[0503] Furthermore, upon the backoff timer stopping or expiring, UE_A10 may delete from the fourth rejected 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 related to the mapped S-NSSAI to which the backoff timer was associated.

[0504] Specifically, when the backoff timer stops or expires, UE_A10 may delete 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 related to the mapped S-NSSAI to which the backoff timer was associated, from the fourth rejected NSSAI associated with the current PLMN or SNPN.

[0505] Furthermore, upon the backoff timer stopping or expiring, UE_A10 may delete the S-NSSAI to which the backoff timer was associated, or the S-NSSAI related to the mapped S-NSSAI to which the backoff timer was mapped, from the fourth rejected NSSAI stored.

[0506] In UE_A10, if the S-NSSAI is removed from the fourth rejected NSSAI while a valid backoff timer for the S-NSSAI is running, UE_A10 may stop the backoff timer.

[0507] Similarly, in UE_A10, if the backoff timer is active or if the fourth rejected NSSAI is deleted while the backoff timer is running, UE_A10 may stop the backoff timer.

[0508] Alternatively, UE_A10 with the back-off timer running may stop and / or delete the back-off timer regardless of updating or deleting the fourth rejected NSSAI. Specific examples of conditions for deleting the fourth rejected NSSAI and / or stopping the back-off timer are shown below.

[0509] If UE_A10 transitions to an unregistered state on one access type for the current PLMN or SNPN and is also unregistered for the other access type, UE_A10 may delete the fourth rejected NSSAI, which is information independent of access type, and / or the S-NSSAI included in the fourth rejected NSSAI.

[0510] If UE_A10 transitions to an unregistered state on one access type for the current PLMN or SNPN and is also unregistered for the other access type, UE_A10 may stop or delete the backoff timer for the fourth rejected NSSAI regardless of access type and / or the S-NSSAI included in the fourth rejected NSSAI.

[0511] If UE_A10 receives an Allowed NSSAI from the current PLMN or SNPN that includes an S-NSSAI included in the fourth rejected NSSAI associated with the current PLMN or SNPN, UE_A10 may remove the S-NSSAI from the fourth rejected NSSAI regardless of access type.

[0512] When UE_A10 receives from the current PLMN or SNPN an Allowed NSSAI including an S-NSSAI included in a fourth rejected NSSAI to which the current PLMN or SNPN is associated, UE_A10 may stop or delete the backoff timer for which the S-NSSAI included in the fourth rejected NSSAI is valid, regardless of the access type.

[0513] If UE_A10 receives a Rejected NSSAI from the current PLMN or SNPN that includes an S-NSSAI included in the fourth rejected NSSAI associated with the current PLMN or SNPN, UE_A10 may delete the S-NSSAI from the fourth rejected NSSAI regardless of access type.

[0514] When UE_A10 receives a Rejected NSSAI from the current PLMN or SNPN that includes an S-NSSAI included in the fourth rejected NSSAI associated with the current PLMN or SNPN, UE_A10 may stop or delete the backoff timer for which the S-NSSAI included in the fourth rejected NSSAI is valid, regardless of the access type.

[0515] If UE_A10 receives a pending NSSAI for an NSSAA or a mapped S-NSSAI(s) for a pending NSSAI from the current PLMN or SNPN that includes an S-NSSAI included in the fourth rejected NSSAI associated with the current PLMN or SNPN, UE_A10 may remove the S-NSSAI from the fourth rejected NSSAI regardless of access type.

[0516] When UE_A10 receives from the current PLMN or SNPN a pending NSSAI for an NSSAA or a mapped S-NSSAI(s) for a pending NSSAI that includes an S-NSSAI included in the fourth rejected NSSAI to which the current PLMN or SNPN is associated, UE_A10 may stop or delete the backoff timer for which the S-NSSAI included in the fourth rejected NSSAI is valid.

[0517] When UE_A10 transitions to an unregistered state on an access type for the current PLMN or SNPN, UE_A10 may delete the fourth rejected NSSAI associated with that access type and / or the S-NSSAI included in the fourth rejected NSSAI.

[0518] When UE_A10 transitions to an unregistered state on an access type for the current PLMN or SNPN, UE_A10 may stop or delete the backoff timer for which the fourth rejected NSSAI associated with that access type and / or the S-NSSAI included in the fourth rejected NSSAI is valid.

[0519] When UE_A10 receives an Allowed NSSAI including an S-NSSAI included in the fourth rejected NSSAI from the current PLMN or SNPN via an access indicated by a certain access type, UE_A10 may delete the S-NSSAI from the fourth rejected NSSAI. In this case, the fourth rejected NSSAI and / or the S-NSSAI included in the fourth rejected NSSAI may correspond to the current PLMN or SNPN and its access type.

[0520] When UE_A10 receives an Allowed NSSAI including an S-NSSAI included in a fourth rejected NSSAI from the current PLMN or SNPN via an access indicated by a certain access type, UE_A10 may stop or delete the back-off timer for which the S-NSSAI included in the fourth rejected NSSAI is valid. In this case, the fourth rejected NSSAI and / or the S-NSSAI included in the fourth rejected NSSAI may correspond to the current PLMN or SNPN and its access type.

[0521] When UE_A10 detects a change in AMF, UE_A10 may delete the fourth rejected NSSAI, and / or UE_A10 may stop or delete the back-off timer for which the fourth rejected NSSAI is valid.

[0522] If UE_A10 fails registration to the current PLMN or SNPN due to a reason value other than a reason value indicating that there is no available network slice and enters the 5GMM-DEREGISTERED state, and is not registered to the current PLMN or SNPN on the other access type, the UE may delete the first or third rejected NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI.

[0523] Here, the reason value may be a 5GMM cause of 5GS. Furthermore, in this case, the "reason value indicating that there are no available network slices" may be #62 "No network slices available", which is the 62nd 5GMM cause of 5GS.

[0524] If the UE deregisters or enters 5GMM-DEREGISTERED state for the current PLMN or SNPN using explicit signaling and if the UE is not registered with the current PLMN or SNPN on another access type, the UE may delete the first or third rejected NSSAI and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI associated with the current PLMN or SNPN. If an EPLM or ESNPN exists for the current PLMN or SNPN, the UE may further delete the first or third rejected NSSAI and / or the mapped S-NSSAI(s) of the first or third rejected NSSAI of the equivalent PLMN(s) of the current PLMN or the equivalent SNPN(s) of the current SNPN.

[0525] If the UE successfully registers to the new PLMN or SNPN, or if registration to the new PLMN or SNPN fails and enters the 5GMM-DEREGISTERED state, and if the UE is not registered to the current PLMN or SNPN on another access type, the UE may delete the first or third rejected NSSAI and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI associated with the current PLMN or SNPN. If an EPLM or ESNPN of the current PLMN or SNPN exists, the UE may further delete the first or third rejected NSSAI and / or the mapped S-NSSAI(s) of the first or third rejected NSSAI of the equivalent PLMN(s) of the current PLMN or the equivalent SNPN(s) of the current SNPN.

[0526] The UE may delete the stored second rejected NSSAI associated with the first access type and / or current PLMN or SNPN when the UE deregisters on the first access type, when the registration is successful in a new registration area on the first access type, or when the registration procedure on the first access type fails and the UE enters 5GMM-DEREGISTERED state. The UE may also delete one or more mapped S-NSSAI(s) of the second rejected NSSAI associated with the deleted current PLMN or SNPN and the first access type when roaming.

[0527] If the UE deregisters on the first access type, or if the registration procedure on the first access type fails and the UE enters 5GMM-DEREGISTERED state, the UE may delete the stored fourth rejected NSSAI associated with the first access type and / or the current PLMN or SNPN. The UE may also delete one or more mapped S-NSSAI(s) of the fourth rejected NSSAI associated with the deleted current PLMN or SNPN and the first access type when roaming.

[0528] In addition, when the first to fourth rejected NSSAIs are deleted, the UE may delete one or more mapped S-NSSAI(s) for the deleted first to fourth rejected NSSAIs.

[0529] In this manner, the UE stores and manages information about each NSSAI. Furthermore, the UE may start and stop a back-off timer that is valid for a PLMN or SNPN based on the storage and update of each NSSAI.

[0530] 4. EMBODIMENTS OF THE PRESENT ART An embodiment of the present invention may be a combination of one or more of the procedures described in Chapter 3. For example, in this embodiment, upon completion of the initial registration procedure described in Chapter 3.1, the UE may transition to a registered state, and further the registration procedures for mobility and periodic registration update of Chapter 3.1 may be performed one or more times.

[0531] In addition, when the UE_A10 transitions to a registered state based on completion of the registration procedure described in Chapter 3.1 or maintains the registered state, each procedure described in Chapters 3.2 to 3.3 may be performed. During each procedure, the UE_A10 may execute the NSSAI update procedure described in Chapter 3.3 based on information received from the NW and / or the state of the UE, and may update and / or delete information related to the stored NSSAI.

[0532] Alternatively, in an embodiment of the present invention, an SM procedure may be implemented in which the sending and receiving of SM messages is configured based on the completion of the registration procedure described in Chapter 3.1.

[0533] Hereinafter, a specific example of an embodiment of the present invention will be described.

[0534] [4.1. First embodiment] The first embodiment (hereinafter, this embodiment) will be described below.

[0535] In the first embodiment, a procedure for updating information related to the NSSAI stored by the UE when a UE that does not have a function for storing one or more mapped S-NSSAI(s) of a pending NSSAI receives a pending NSSAI IE including a new mapped S-NSSAI while not roaming, and a procedure for updating information related to the NSSAI stored by the UE when a pending NSSAI IE that does not include a mapped S-NSSAI is received while roaming will be described below. Furthermore, the behavior of the UE after updating information related to the NSSAI stored by the UE will also be described.

[0536] In the initial state, the UE stores the first pending NSSAI. The first pending NSSAI may be stored based on the reception of the first pending NSSAI IE included in the first registration acceptance message during the initial registration procedure.

[0537] Next, the UE receives a second pending NSSAI IE from the NW. Note that the second pending NSSAI IE may be transmitted and received in a second registration accept message, for example, during the mobility and periodic registration procedure.

[0538] When not roaming, the second pending NSSAI IE may include one or more S-NSSAIs of the current PLMN. When roaming, the second pending NSSAI IE may include one or more S-NSSAIs of the HPLMN as one or more mapped S-NSSAI(s).

[0539] When the UE is roaming, the UE replaces the first pending NSSAI it stores with one or more S-NSSAIs included in the second pending NSSAI IE.

[0540] On the other hand, when the UE is roaming, the UE replaces the first pending NSSAI it stores with one or more mapped S-NSSAI(s) included in the second pending NSSAI IE and stores the replaced first pending NSSAI.

[0541] Additionally / or, if the UE is roaming, and the received second pending NSSAI IE further includes one or more S-NSSAI(S) of the current PLMN, the UE may ignore the one or more S-NSSAI(S) of the current PLMN included in the second pending NSSAI IE.

[0542] As a result, a UE that does not have the function of storing one or more mapped S-NSSAI(s) of a pending NSSAI can appropriately control the storage of a pending NSSAI received when non-roaming and when roaming.

[0543] Furthermore, the UE is able to properly perform MM and SM procedures, such as registration procedures and PDU session establishment procedures, based on the stored information regarding the updated NSSAI.

[0544] [4.2. Second embodiment] The second embodiment (hereinafter, this embodiment) will be described below.

[0545] In the second embodiment, a procedure for updating the first or third rejected NSSAI stored by the UE when a UE that was registered with an SNPN transitions from the current SNPN to an unregistered state will be described.

[0546] In an initial state, the UE is registered for the current SNPN and may store the first or third rejected NSSAI associated with the current SNPN and / or one or more mapped S-NSSAI(s) for the first or third rejected NSSAI.

[0547] The first or third rejected NSSAI and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI may be information stored based on, for example, receipt of a rejected NSSAI IE or an extended rejected NSSAI IE included in a registration accept message or a registration reject message in a registration procedure, or a configuration update command message in a generic UE configuration update procedure.

[0548] If the UE fails registration to the current SNPN due to a cause value other than a cause value indicating no network slice is available and enters the 5GMM-DEREGISTERED state, the UE may delete the first or third rejected NSSAI associated with the current SNPN and / or one or more mapped S-NSSAI(s) for the first or third rejected NSSAI. If an ESNPN for the current SNPN exists, the UE may further delete the first or third rejected NSSAI of the equivalent SNPN(s) of the current SNPN and / or the mapped S-NSSAI(s) for the first or third rejected NSSAI.

[0549] When the UE deregisters to the current SNPN using explicit signaling or enters 5GMM-DEREGISTERED state for the current SNPN, the UE may delete the first or third rejected NSSAI associated with the current SNPN and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI. If an ESNPN exists for the current SNPN, the UE may further delete the first or third rejected NSSAI of the equivalent SNPN(s) of the current SNPN and / or the mapped S-NSSAI(s) of the first or third rejected NSSAI.

[0550] Also, if inter-SNPN or inter-PLMN and SNPN mobility in connected mode is supported, the UE may also delete the first or third rejected NSSAI and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI associated with the current SNPN if the UE successfully registers to a new PLMN or SNPN or fails to register to a new PLMN or SNPN and enters 5GMM-DEREGISTERED state. If an ESNPN of the current SNPN exists, the UE may further delete the first or third rejected NSSAI and / or the mapped S-NSSAI(s) of the first or third rejected NSSAI of the equivalent SNPN(s) of the current SNPN.

[0551] In addition to the above conditions, the above behavior may be controlled only when the other access type of the current SNPN is not registered. Note that this condition may be added when connection to the SNPN via a non-3GPP access is supported. Specifically, for example, the following control may be executed.

[0552] If the UE fails registration to the current SNPN due to a reason value other than a reason value indicating that there is no available network slice and enters the 5GMM-DEREGISTERED state, and is not registered to the current SNPN on another access type, the UE may delete the first or third rejected NSSAI associated with the current SNPN and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI.

[0553] If the UE deregisters to the current SNPN or enters 5GMM-DEREGISTERED state for the current SNPN using explicit signaling and if the UE is not registered to the current SNPN on another access type, the UE may delete the first or third rejected NSSAI and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI associated with the current SNPN. If an ESNPN exists for the current SNPN, the UE may also delete the first or third rejected NSSAI and / or the mapped S-NSSAI(s) of the first or third rejected NSSAI of the equivalent SNPN(s) of the current SNPN.

[0554] If the UE successfully registers to the new PLMN or SNPN, or if registration to the new PLMN or SNPN fails and enters 5GMM-DEREGISTERED state, and if the UE is not registered to the current SNPN on another access type, the UE may delete the first or third rejected NSSAI and / or one or more mapped S-NSSAI(s) of the first or third rejected NSSAI associated with the current SNPN. If an ESNPN of the current SNPN exists, the UE may also delete the first or third rejected NSSAI and / or the mapped S-NSSAI(s) of the first or third rejected NSSAI of the equivalent SNPN(s) of the current SNPN.

[0555] When the first or third rejected NSSAI is deleted, the UE may also delete one or more mapped S-NSSAI(s) for the deleted first or third rejected NSSAI.

[0556] As a result, a UE that was registered with an SNPN can appropriately control information related to the stored NSSAI when it transitions to an unregistered state.

[0557] Furthermore, the UE can appropriately perform MM and SM procedures such as the registration procedure and the PDU session establishment procedure based on the updated stored information on the NSSAI. The registration procedure after the stored information on the NSSAI may use the registration procedure in Chapter 3.1.

[0558] [4.3. Third embodiment] The third embodiment (hereinafter, this embodiment) will be described below.

[0559] In the third embodiment, a procedure for updating a pending NSSAI stored in a UE when a UE that was registered with an SNPN transitions from the current SNPN to an unregistered state will be described.

[0560] In an initial state, the UE is registered for the current SNPN and may store a second pending NSSAI associated with the current SNPN and / or one or more mapped S-NSSAI(s) for the second pending NSSAI.

[0561] The second pending NSSAI and / or one or more mapped S-NSSAI(s) of the second pending NSSAI may be information stored based on, for example, receipt of a pending NSSAI IE included in a registration accept message during the registration procedure.

[0562] If the UE deregisters from the current SNPN or enters 5GMM-DEREGISTERED state for the current SNPN using explicit signaling and is not registered for the other access type of the current SNPN, the UE may delete the second pending NSSAI and / or one or more mapped S-NSSAI(s) of the second pending NSSAI associated with the current SNPN. If an ESNPN exists for the current SNPN, the UE may also delete the second pending NSSAI and / or the mapped S-NSSAI(s) of the second pending NSSAI of the equivalent SNPN(s) of the current SNPN.

[0563] Also, if inter-SNPN or inter-PLMN and SNPN mobility in connected mode is supported, if the UE successfully registers to a new PLMN or SNPN, or if registration to a new PLMN or SNPN fails and enters 5GMM-DEREGISTERED state, and is not registered to the other access type of the current SNPN, the UE may also delete the second pending NSSAI and / or one or more mapped S-NSSAI(s) of the second pending NSSAI associated with the current SNPN. Similarly, if an ESNPN exists for the current SNPN, the UE may also delete the second pending NSSAI and / or the mapped S-NSSAI(s) of the second pending NSSAI of the equivalent SNPN(s) of the current SNPN.

[0564] In addition to the above conditions, the above behavior may be controlled only when the other access type of the current SNPN is not registered. Note that this condition may be added when connection to the SNPN via a non-3GPP access is supported. Specifically, for example, the following control may be executed.

[0565] If the UE deregisters from the current SNPN or enters 5GMM-DEREGISTERED state for the current SNPN using explicit signaling and if the UE is not registered with the current SNPN on another access type, the UE may delete the second pending NSSAI and / or one or more mapped S-NSSAI(s) of the second pending NSSAI associated with the current SNPN. If an ESNPN exists for the current SNPN, the UE may also delete the second pending NSSAI and / or the mapped S-NSSAI(s) of the second pending NSSAI of the equivalent SNPN(s) of the current SNPN.

[0566] When a second pending NSSAI is deleted, the UE may also delete one or more mapped S-NSSAI(s) of the deleted second pending NSSAI.

[0567] As a result, a UE that was registered with an SNPN can appropriately control information related to the stored NSSAI when it transitions to an unregistered state.

[0568] Furthermore, the UE can appropriately perform MM and SM procedures such as the registration procedure and the PDU session establishment procedure based on the updated stored information on the NSSAI. The registration procedure after the stored information on the NSSAI may use the registration procedure in Chapter 3.1.

[0569] [4.4. Fourth embodiment] The fourth embodiment (hereinafter, this embodiment) will be described below.

[0570] In the fourth embodiment, a procedure for updating information related to the NSSAI stored in the UE when the UE deregisters from a certain access type will be described.

[0571] In an initial state, the UE is registered for the first access type and stores the fourth rejected NSSAI and / or one or more mapped S-NSSAI(s) of the fourth rejected NSSAI associated with the current PLMN or SNPN and the first access type.

[0572] The fourth rejected NSSAI and / or one or more mapped S-NSSAI(s) of the fourth rejected NSSAI may be information stored based on, for example, receipt of a rejected NSSAI IE or an extended rejected NSSAI IE included in a registration accept message or a registration reject message in a registration procedure, or a configuration update command message in a generic UE configuration update procedure.

[0573] It should be noted that the first access type may be a 3GPP access type or a non-3GPP access type.

[0574] If the UE deregisters on the first access type, or if the registration procedure on the first access type fails and the UE enters 5GMM-DEREGISTERED state, the UE may delete the stored fourth rejected NSSAI associated with the first access type and / or the current PLMN or SNPN. The UE may also delete one or more mapped S-NSSAI(s) of the fourth rejected NSSAI associated with the deleted current PLMN or SNPN and the first access type when roaming.

[0575] As a result, a UE that was registered for 3GPP access or non-3GPP access can appropriately control information related to the stored NSSAI when the UE transitions to a non-registered state for that access.

[0576] Furthermore, the UE can appropriately perform MM and SM procedures such as the registration procedure and the PDU session establishment procedure based on the updated stored information on the NSSAI. The registration procedure after the stored information on the NSSAI may use the registration procedure in Chapter 3.1.

[0577] 5. Variations The program that runs on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of the embodiments according to the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0578] A program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium. The program may be read into a computer system and executed to implement the functions. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to 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.

[0579] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when an integrated circuit technology that replaces the current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit according to the technology.

[0580] The present invention is not limited to the above-mentioned embodiment. In the embodiment, one example of the device is described, but the present invention is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV equipment, kitchen equipment, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0581] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present 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 the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0582] 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

1. A UE (User Equipment), The device includes a transmitter / receiver, a controller, and a memory unit, The transmitting / receiving unit is Receives a pending NSSAI IE from the core network, When the UE is roaming, the control unit replacing the pending NSSAI (Network Slice Selection Assistance Information) of the storage unit with one or more mapped S-NSSAI (Single Network Slice Selection Assistance Information) included in the pending NSSAI IE; Ignoring the S-NSSAI(s) of the current PLMN(s) included in the pending NSSAI IE; The UE is characterized by:

2. When the UE is not roaming, the control unit replacing the pending NSSAI in the storage unit with one or more S-NSSAIs of the current PLMN included in the pending NSSAI IE; The UE according to claim 1, characterized in that

3. A UE (User Equipment), The device includes a control unit, a storage unit, and a transmission / reception unit, The transceiver unit receives a registration acceptance message including a Pending NSSAI (Network Slice Selection Assistance Information) IE including one or more first mapped S-NSSAI (Single Network Slice Selection Assistance Information), The control unit replaces one or more mapped S-NSSAIs for the Pending NSSAI in the storage unit with the first mapped S-NSSAI. The UE is characterized by:

Images