UE(User Equipment)

Abstract

To provide communication means for achieving a function related to management of information about a network slice, or a non-public network function, in 5GS.SOLUTION: Methods and communication means are provided for UE initial registration and periodic or mobility-based registration procedures for achieving management of information about a network slice, or a non-public network function, in 5GS. Furthermore, methods and communication means are provided for network slice-specific authentication / authorization procedures, UE setting update procedures, and deregistration procedures, after the registration procedures are completed.SELECTED DRAWING: Figure 6

Description

[Technical Field]

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

[0002] 3GPP (3rd Generation Partnership Project), which is currently working on standardization of 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 5G mobile communication systems (see Non-Patent Document 1). In 5GS, technical issues for connecting a wide variety of terminals to cellular networks are being identified and solutions are being specified. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 24.501 V17.3.1 (2021-06); 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 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered to provide a wide variety of services.

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

[0007] 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.

[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] However, a practical method for meeting the above requirements has not been clearly established.

[0010] The present invention has been made in consideration of the above circumstances, and aims to provide a method for realizing functions for eNS in 5GS. [Means for solving the problem]

[0011] One embodiment of the present invention relates to a UE (User Equipment) that includes a memory unit and a control unit, and the memory unit stores a configured NSSAI (Network Slice Selection Assistance Information) for a current PLMN, one or more mapped S-NSSAIs (Single Network Slice Selection Assistance Information) for the configured NSSAI, and a pending NSSAI.When the UE is roaming, the control unit includes one or more S-NSSAIs that are included in the configured NSSAI and are not associated with an S-NSSAI included in the pending NSSAI in the requested NSSAI.When the UE is not roaming, the control unit includes one or more S-NSSAIs that are included in the configured NSSAI and are not included in the pending NSSAI in the requested NSSAI. [Effects of the Invention]

[0012] According to the present invention, support for eNS and eNPN becomes possible in 5GS. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). [Figure 2] FIG. 1 is a diagram illustrating the detailed configuration of a mobile communication system (EPS / 5GS). [Figure 3] FIG. 1 is a diagram illustrating the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Figure 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 10 is a diagram illustrating a registration procedure. [Figure 7] FIG. 10 is a diagram illustrating a procedure for changing / updating UE settings. DETAILED DESCRIPTION OF THE INVENTION

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The best mode for carrying out the present invention will be described below 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.

[0015] [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.

[0016] 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.

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

[0018] 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.

[0019] 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.

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

[0021] A UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, or 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, or non-3GPP AN). A 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. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that a UE may be referred to as a user device or a terminal device.

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

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

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

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

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

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

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

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

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

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

[0032] The core network (core network_A and / or core network_B) and the access network (access network_A and / or access network_B) may differ depending on the mobile communication operator.

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

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

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

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

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

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

[0039] The AAA server is a device that has authentication, authorization, and accounting functions and is connected to the AUSF directly or indirectly via another network device. The AAA server may be a network device within the core network. The AAA server may not be included in the core network_A and / or core network_B, but may be included in the PLMN and / or 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 within the PLMN and / or SNPN managed by a third party.

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

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

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

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

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

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

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

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

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

[0049] 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.

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

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

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

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

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

[0055] 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.

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

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

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

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

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

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

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

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

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

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

[0066] 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 among multiple NSIs.

[0067] 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.

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

[0069] 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.

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

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

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

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

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

[0075] 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.

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

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

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

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

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

[0081] The user plane refers to user data transmitted and received between a UE and a network. The user plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. Hereinafter, the user plane may be referred to as the U-Plane.

[0082] Furthermore, the control plane refers to control messages transmitted and received to control UE communications, etc. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and 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 NG RAN and the N2 interface. Hereinafter, the control plane may be referred to as the control plane or the C-Plane.

[0083] Furthermore, the U-Plane (User Plane; UP) may 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.

[0084] [2.6. Other Devices and / or Functions and / or Terms Used in This Embodiment] Next, other devices, functions, terms, identification information sent, received, stored, and managed by each device, and / or messages will be described.

[0085] A network refers to at least a portion of an access network _B, a core network _B, and a DN. Furthermore, one or more devices included in at least a portion of an access network _B, a core network _B, and a 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 devices within the network (network devices and / or control devices) transmit, receive, receive, and / or process messages. Conversely, when a device within the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0086] 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. Furthermore, 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, etc.

[0087] 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 the network (NW).

[0088] Furthermore, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in procedures 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, etc.

[0089] 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.

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

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

[0092] Also, 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 via a communication method other than IP.

[0093] Furthermore, 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 it may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data to and from a DN by establishing a PDU session via an access network _B and a core network _B. Here, this external gateway may be a UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session.

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

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

[0096] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and can be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be sent and received to an application server or the like in the 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 also include IP. IP can be specified if the UE is capable of using both IPv4 and IPv6.

[0097] Also, 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 refer to the 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 also refer to a core network.

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

[0099] A PLMN to which a 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.

[0100] 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.

[0101] The requested PLMN refers to the network to which the UE sends a message when the UE sends the message. Specifically, it may be the PLMN selected by the UE when the UE sends the message. The requested PLMN is the PLMN requested by the UE, and may be the current PLMN. When the UE is in a registered state, the requested PLMN may be the registered PLMN.

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

[0103] A Stand-alone Non-Public Network (SNPN) is a network operated by an NPN operator and does not rely 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 specific UEs. An SNPN may be identified by a PLMN ID and a Network Identifier (NID).

[0104] Here, 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.

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

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

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

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

[0109] Onboarding services in SNPN allow an MS (UE) to access the SNPN for onboarding using default UE credentials.

[0110] The registration procedure for onboarding services in the SNPN may be an initial registration for onboarding services in the SNPN. Additionally, or alternatively, 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 also be referred to as SNPN onboarding registration.

[0111] 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.

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

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

[0114] Here, an NST is a logical representation of one or more NFs associated with resource requirements for providing the required communication services and capabilities. In other words, an NSI may be a collection of multiple NFs within the core network_B190. 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. The NFs configured in an NS may or may not be devices shared with other NSs.

[0115] A UE and / or a device in the network can 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 APNs. The UE usage type is a parameter value included in the UE registration information and 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.

[0116] Furthermore, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying an NS. S-NSSAI may consist of only SST (Slice / Service type), or may consist of both SST and SD (Slice Differentiator). Here, SST is information indicating the expected behavior of an NS in terms of functions and services. Furthermore, SD may be information that interpolates 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.

[0117] In addition, the S-NSSAI may 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, for example, when the UE is roaming or when the current PLMN or SNPN is a VPLMN or SNPN).

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

[0119] 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 the registered PLMN or SNPN, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN or HSNPN to which the S-NSSAI is mapped. One or more S-NSSAIs stored in the UE and / or 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 the S-NSSAI of the HPLMN to which the S-NSSAI is mapped.

[0120] Also, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAIs. Each S-NSSAI included in the NSSAI is information that assists 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 also 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.

[0121] A mapped S-NSSAI is an S-NSSAI of an 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 for the rejected NSSAI and / or the S-NSSAI included in the pending NSSAI.

[0122] 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.

[0123] The Network Slice-Specific Authentication and Authorization (NSSAA) function is a function for realizing network slice-specific authentication and authorization. Network slice-specific authentication and authorization allows UE authentication and authorization to be performed outside the core network, such as by a third party. PLMN or SNPN and network devices with NSSAA functionality can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information. Furthermore, a UE with NSSAA functionality can manage, store, and send / receive pending NSSAIs and third rejected NSSAIs. In this document, NSSAA may be referred to as the network slice-specific authentication and authorization procedure or the authentication and authorization procedure.

[0124] 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 that of an HPLMN or HSNPN, where the S-NSSAI of an HPLMN or HSNPN requiring an NSSAA that is managed by a core network and / or a core network device becomes the mapped S-NSSAI.

[0125] The core network and / or core network device may store an S-NSSAI requiring 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 requiring an NSSAA in association with information indicating whether an 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 requiring an NSSAA as information unrelated to the access network.

[0126] 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.

[0127] 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.

[0128] Also, a 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 a configured NSSAI as the "default configured NSSAI." Similarly, a UE may not be associated with an SNPN and may store a configured NSSAI that is valid for all SNPNs, and may refer to such a configured NSSAI as the "default configured NSSAI." A 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 a configured NSSAI as the "default configured NSSAI."

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

[0130] 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-NSSI IE, and in this 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, for example, when the UE is roaming or when the associated PLMN or SNPN is a VPLMN or VSNPN).

[0131] 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."

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

[0133] 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 mapped S-NSSAI(s) for the configured NSSAI.

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

[0135] The requested NSSAI is an NSSAI provided by the UE to the network during the registration procedure. In the registration procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI or configured NSSAI stored by the UE.

[0136] 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 by being included in an NAS message, such as a registration request message or a PDU session establishment request message, transmitted from the UE to the network, or an RRC (Radio Resource Control) message including a NAS (Non-Access-Stratum) 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.

[0137] 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 permission 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 may be an S-NSSAI included in an allowed NSSAI associated with the current PLMN.

[0138] 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.

[0139] 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, and / or an S-NSSAI stored by the UE and not included in the pending NSSAI associated with the current PLMN, or an S-NSSAI stored by the UE and not included in the fourth rejected NSSAI associated with the current PLMN.

[0140] Also, when roaming, if the S-NSSAI included in the pending NSSAI, and / or the rejected NSSAI, and / or the fourth rejected NSSAI is the S-NSSAI of the HPLMN, the S-NSSAI included in the requested NSSAI may be the S-NSSAI of the current PLMN, where the S-NSSAI included in the pending NSSAI, and / or the rejected NSSAI, and / or the fourth rejected NSSAI stored by the UE is not the mapped S-NSSAI.

[0141] 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 or the mapped S-NSSAI of that S-NSSAI is not running in the UE.

[0142] Also, the allowed NSSAI is information indicating one or more network slices to 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 the 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.

[0143] 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.

[0144] 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 also include a list of mapped S-NSSAIs, which are the S-NSSAIs of the HPLMN or HSNPN to which the S-NSSAIs of the current PLMN or SNPN are mapped.

[0145] Note that a list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN and included in the allowed NSSAI IE 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-NSSAIs of the current PLMN or SNPN are 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 3GPP mapped S-NSSAI(s) for the allowed NSSAI for a PLMN. Similarly, the Allowed NSSAI may mean 3GPP allowed NSSAI for a PLMN or an SNPN.

[0146] The UE and / or 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 NW may further manage the allowed NSSAI in association with a registration area.

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

[0148] 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."

[0149] An S-NSSAI included in an allowed NSSAI may be expressed as an 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 configured to include 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, for example, when the UE is roaming or when the associated PLMN or SNPN is a VPLMN or VSNPN).

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

[0151] Furthermore, one or more S-NSSAIs of an 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 for an allowed NSSAI of a PLMN or SNPN."

[0152] Furthermore, 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.

[0153] 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, for example, 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 the case of roaming.

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

[0155] The information indicating the type of set may be, for example, information indicating that the set includes one or more rejected S-NSSAIs with associated back-off timer values, or information indicating that the set includes one or more rejected S-NSSAIs without associated back-off timer values.

[0156] If the information indicating the type of set is information indicating that this set includes 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.

[0157] 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 with which the S-NSSAI included in the rejected NSSAI is associated may be the current PLMN or the current SNPN. Alternatively, the PLMN ID or SNPN ID with which the S-NSSAI included in the rejected NSSAI is associated may be information indicating an HPLMN or an HSNPN, regardless of the current PLMN or SNPN.

[0158] 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-NSSAI or the combination of the corresponding S-NSSAI and the mapped S-NSSAI.

[0159] 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, or a registration reject message, or in an RRC message including an NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI.

[0160] 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. 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 it has rejected 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.

[0161] 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 devices using the S-NSSAI IE, and the S-NSSAI IE indicating the rejected NSSAI may include the S-NSSAI and the mapped S-NSSAI.

[0162] 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.

[0163] In this document, a rejected NSSAI associated with a PLMN or an 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 a registration area. The UE and / or NW may store the second rejected NSSAI and / or the second rejected S-NSSAI in association with an access type and / or a registration area.

[0164] Here, the first rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current PLMN or current SNPN. The first rejected NSSAI may be a 5GS rejected NSSAI for the current PLMN or SNPN, a rejected S-NSSAI for the current PLMN or SNPN, an S-NSSAI included in the rejected NSSAI for the current PLMN or SNPN, 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 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.

[0165] When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, it includes one or more S-NSSAIs among the S-NSSAIs included in the requested NSSAI transmitted by the UE to the NW that were rejected because they are unavailable in the current PLMN or the current SNPN. In this case, the first rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. In this case, the rejection reason value may be "S-NSSAI not available in the current PLMN or SNPN" or may be information indicating that the S-NSSAI associated with the rejection reason value is unavailable in the current PLMN or SNPN. The S-NSSAI included in the first rejected NSSAI may be expressed as a first rejected S-NSSAI.

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

[0167] 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.

[0168] The first rejected NSSAI may apply to the entire registered PLMN or 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 independent of the access type. That is, the first rejected NSSAI may be information valid for both 3GPP access and non-3GPP access.

[0169] The UE may delete the first rejected NSSAI from its storage when it transitions to an unregistered state in both 3GPP access and non-3GPP access with respect to the current PLMN. In other words, when the UE transitions to an unregistered state with respect to the current PLMN via one access, or when it successfully registers to a new PLMN via one access, or when it fails to register to the new PLMN via one access and transitions to an unregistered state, and 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 with respect to the current PLMN via one access, and the UE is registered (registered state) with the current PLMN via the other access, the UE does not need to delete the first rejected NSSAI.

[0170] 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, managed, and / or transmitted / received. Further / alternatively, 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.

[0171] 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 5GS rejected NSSAI for the current registration area, mapped S-NSSAI(s) for a rejected NSSAI for the current registration area, or an S-NSSAI included in mapped S-NSSAI(s) for a rejected NSSAI for the current registration area. The list (set) of mapped S-NSSAIs for the second rejected NSSAI may be one or more mapped S-NSSAIs for the second rejected NSSAI, or 5GS mapped S-NSSAI(s) 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 unavailable in the current registration area. The S-NSSAI included in the second rejected NSSAI may be expressed as a second rejected S-NSSAI.

[0172] If the second rejected NSSAI is a rejected NSSAI sent from the NW to the UE, it includes one or more S-NSSAIs that the UE included in the requested NSSAI that were rejected because they are not available in the current registration area. In this case, the second rejected NSSAI may be transmitted and received in a rejected NSSAI IE. The 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 also include a mapped S-NSSAI, which is the S-NSSAI of the HPLMN.

[0173] 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.

[0174] The second rejected NSSAI may be valid within the current registration area and may apply to the current registration area. The UE and / or NW may treat the second rejected NSSAI and the S-NSSAI 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 that access from its memory.

[0175] 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 and received. Alternatively, 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.

[0176] The third rejected NSSAI is a set of one or more S-NSSAIs that require an NSSAA and for which the NSSAA for that 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. In this case, the rejection reason value 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.

[0177] The third rejected NSSAI may apply to the registered PLMN or the registered SNPN, or may apply to the registered PLMN and / or EPLMN, or may apply to the registered SNPN and / or ESNPN, or may apply to all PLMNs or SNPNs. The third rejected NSSAI applying 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.

[0178] 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 a 5GS rejected NSSAI for the failed or revoked NSSAA, a rejected S-NSSAI for the failed or revoked NSSAA, or an S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA.

[0179] The third rejected NSSAI is a rejected NSSAI that identifies a slice that the UE rejected due to an NSSAA failure or revocation 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 an NSSAA failure.

[0180] The third rejected NSSAI is information independent of the access type. Specifically, when the UE stores the third rejected NSSAI, the UE does not need to attempt to send 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 send a registration request message including the S-NSSAI included in the third rejected NSSAI based on a UE policy.

[0181] Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which it 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.

[0182] 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.

[0183] In other words, the UE and / or each device may store the "third rejected NSSAI" for 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.

[0184] The fourth rejected NSSAI is information including one or more S-NSSAIs for which the maximum number of UEs per network slice has been reached. 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.

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

[0186] 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" 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 allowable UEs has been reached.

[0187] 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 one or more S-NSSAIs and / or one or more mapped S-NSSAIs associated with the back-off timer value, the S-NSSAI of the current PLMN or SNPN associated with the one or more S-NSSAIs and / or the mapped S-NSSAI.

[0188] The fourth rejected NSSAI may apply to the entire registered PLMN, may be valid for all PLMNs, may apply, may be valid within a registration area, may apply to the registered PLMN and the EPLMN, or may apply to one or more PLMNs to which a TAI included in the TA list (TAI list or registration area) belongs. The fourth rejected NSSAI applying to all PLMNs may mean that the fourth rejected NSSAI is not associated with a PLMN, or may mean that the fourth rejected NSSAI is associated with a HPLMN.

[0189] If the fourth rejected NSSAI is valid for the entire registered PLMN, or applies to all PLMNs, or applies to the registered PLMN and / or EPLMN, the UE and / or NW may treat the fourth rejected NSSAI and the S-NSSAI included in the fourth rejected NSSAI as access type-independent information.If the fourth rejected NSSAI is valid within the registration area, or applies to one or more PLMNs to which the TAIs included in the TA list (TAI list or registration area) belong, the UE and / or NW may treat the fourth rejected NSSAI and the S-NSSAI included in the fourth rejected NSSAI as access type-specific information.

[0190] If the fourth rejected NSSAI is an NSSAI sent from the NW to the UE, the fourth rejected NSSAI may include one or more pieces of information consisting of the S-NSSAI of the current PLMN or SNPN and the mapped S-NSSAI (if any).

[0191] If the fourth rejected NSSAI is an NSSAI transmitted from the NW to the UE, the fourth rejected NSSAI may be transmitted and received using an Extended rejected NSSAI IE. If the fourth rejected NSSAI is transmitted and received using an Extended rejected NSSAI IE, the Extended rejected NSSAI IE may include information indicating that this IE includes a list of rejected S-NSSAIs with associated back-off timer values, and the back-off timer value.

[0192] Alternatively, the Extended rejected NSSAI IE containing the fourth rejected NSSAI may include information indicating that the IE contains a list of rejected S-NSSAIs without a back-off timer value associated with it, in which case the back-off timer value is not included in the Extended rejected NSSAI IE.

[0193] During roaming, the S-NSSAI included in the fourth rejected NSSAI may be the S-NSSAI of the HPLMN or the HSNPN. In other words, the fourth rejected NSSAI received by the UE from the VPLMN may include the S-NSSAI of the HPLMN or the HSNPN. In this case, the fourth rejected NSSAI may be associated with the HPLMN or the HSNPN and stored and / or managed in the UE and / or the NW.

[0194] 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.

[0195] If the pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI may be sent and received using 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 SNPN and / or SD of the mapped HPLMN or SNPN) (if any, for example, when the UE is roaming, or when the associated PLMN or SNPN is a VPLMN or VSNPN, or when the UE has the capability to store one or more mapped S-NSSAIs for the pending NSSAI).

[0196] The pending NSSAI may apply to the entire registered PLMN or registered SNPN, to the registered PLMN and one or more EPLMNs of the registered PLMN, to the registered SNPN and one or more ESNPNs of the registered SNPN, or to all PLMNs or SNPNs. A pending NSSAI that applies to all PLMNs or SNPNs may mean that the pending NSSAI is not associated with a PLMN or SNPN, or may mean that the pending NSSAI is associated with a HPLMN or HSNPN.

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

[0198] 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.

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

[0200] During roaming (roaming scenario), the S-NSSAI included in the pending NSSAI may be the S-NSSAI of the HPLMN or HSNPN. In other words, the pending NSSAI 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.

[0201] In other words, there is no mapped S-NSSAI for the first pending NSSAI, and the S-NSSAI configured in the first pending NSSAI is the S-NSSAI of the HPLMN or HSNPN regardless of whether roaming or non-roaming.

[0202] On the other hand, during roaming (roaming scenario), the S-NSSAI included in the pending NSSAI 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.

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

[0204] 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 an area in which control messages such as paging are broadcast, or an area in which UE_A10 can move without performing a handover procedure. Furthermore, a tracking area may be a routing area, a location area, or anything similar. Hereinafter, a tracking area may be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking area code) and a PLMN.

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

[0206] The TAIs included in the TAI list may belong to one PLMN or multiple PLMNs. If multiple TAIs included in the TAI list belong to different PLMNs, those PLMNs may be EPLMNs.

[0207] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, 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.

[0208] Management of the maximum number of UEs connecting to a slice refers to managing and / or controlling the maximum number of UEs that can be simultaneously registered to a network slice or S-NSSAI, or managing and / or controlling the maximum number of UEs that can simultaneously establish a PDU session using a network slice or S-NSSAI. Management of the maximum number of UEs connecting to a slice may be NSAC (network slice admission control) of 5GS. NSAC may also be expressed as slice admission control.

[0209] Management and / or control of the maximum number of UEs that can be simultaneously registered to a network slice or an S-NSSAI may be referred to as MM-based slice admission control (Mobility management based slice admission control). 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 referred to as SM-based slice admission control (Session management based slice admission control).

[0210] Here, a UE registering to a network slice or an S-NSSAI may be stored by including an S-NSSAI indicating the network slice in the allowed NSSAI. A device in a network that supports the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can be simultaneously registered to a network slice or an S-NSSAI may store, for each S-NSSAI, whether management of the maximum number of UEs connected to a slice is required, and may further check during the registration procedure whether the number of registered UEs has reached the maximum number, i.e., a constant. Furthermore, each device that supports the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can simultaneously be registered to a network slice or an S-NSSAI may store 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 to each slice, the maximum number of UEs that can be registered to a network slice or an S-NSSAI, the maximum number of UEs, or a constant.

[0211] The back-off timer is a timer for prohibiting the UE from transmitting an MM message and / or starting a procedure using an SM message. The back-off timer is managed and executed by the UE. The back-off timer may be associated with an S-NSSAI or an NSSAI. While the back-off timer associated with an S-NSSAI is valid, the UE may be in a state where transmission of an MM message and / or transmission of an SM message using that S-NSSAI is prohibited, restricted, or limited. These restrictions may be restrictions based on 5GS congestion management, restrictions that include restrictions based on 5GS congestion management, or restrictions independent of 5GS congestion management.

[0212] The backoff timer may be a timer that is started and / or stopped per S-NSSAI, and / or NSSAI, and / or PLMN, and / or SNPN.

[0213] Specifically, the back-off timer may be associated with an S-NSSAI and may be a timer for prohibiting transmission of MM messages and / or SM messages using a specific S-NSSAI. In other words, the UE may be configured not to transmit MM messages and / or SM messages using the specific S-NSSAI while the timer is counting.

[0214] Alternatively, the back-off timer may be associated with an NSSAI and may be a timer for prohibiting transmission of MM messages and / or SM messages using an S-NSSAI included in a specific NSSAI. In other words, the UE may be configured not to transmit MM messages and / or SM messages using an S-NSSAI included in the specific NSSAI while this timer is counting.

[0215] Furthermore, the UE may configure the new PLMN to allow transmission of MM messages and / or SM messages that were prohibited in the previous PLMN while this timer is counting, based on specific conditions described below. Note that the expression "allowing transmission of MM messages and / or SM messages that were prohibited in the previous PLMN" may also mean that transmission of MM messages and / or SM messages using the same S-NSSAI as the S-NSSAI mapped to the back-off timer, and / or an S-NSSAI related to the same S-NSSAI, and / or an S-NSSAI related to a mapped S-NSSAI of the same S-NSSAI is allowed.

[0216] Furthermore, the back-off timer may be a timer for prohibiting transmission of an MM message using a specific NSSAI. In other words, the UE may be configured not to transmit an MM message using the specific NSSAI and / or an NSSAI including a specific S-NSSAI while the timer is counting.

[0217] Furthermore, while this timer is counting, the UE may configure the new PLMN to permit transmission of an MM message that was prohibited in the previous PLMN based on specific conditions described below. Note that, when it is expressed that transmission of an MM message that was prohibited in the previous PLMN is permitted, it may mean that transmission of an MM message using an NSSAI that is the same as the NSSAI associated with the back-off timer and / or an NSSAI that includes the same S-NSSAI as the S-NSSAI associated with the back-off timer is permitted. Furthermore, when it is expressed that transmission of an MM message that was prohibited in the previous PLMN is permitted, it may mean that transmission of an MM message using an NSSAI that includes an S-NSSAI associated with the S-NSSAI associated with the back-off timer and / or an NSSAI that includes an S-NSSAI associated with the mapped S-NSSAI of the S-NSSAI associated with the back-off timer is permitted.

[0218] The backoff timer may also be associated with no NSSAI and may be a timer for prohibiting the transmission of MM messages using no NSSAI. In other words, UE_A10 may be configured not to transmit MM messages using no NSSAI while this timer is counting. Furthermore, UE_A10 may be configured, while this timer is counting, to allow the transmission of MM messages that were prohibited in the previous PLMN in the new PLMN based on specific conditions described below. Note that when it is expressed that the transmission of MM messages that were prohibited in the previous PLMN is allowed, it may also mean that MM messages using no NSSAI are allowed.

[0219] Furthermore, the back-off timer may be a 5GMM timer and / or an EMM (EPS mobility management) timer. Furthermore, the back-off timer may be timer T3448 or a timer equivalent to timer T3448. In other words, the back-off timer may be the same timer as or similar to a timer for regulating communication of user data via the control plane.

[0220] The 5GMM capability is information for providing the network with UE information related to interworking with 5GCN or EPS. In other words, the 5GMM capability is the MM-related capability information of the UE. The 5GMM capability may be the 5GMM capability IE of 5GS.

[0221] The UE security capability is used by the UE and the network and indicates the security algorithms supported by the UE in N1 mode for NAS security and the security algorithms supported between the NR (5G AN) and the E-UTRA (E-UTRAN) connecting to the 5GCN for AS (Access-Stratum) security. The UE security capability may be a 5GS UE security capability IE (Information Element).

[0222] When the UE is connected to 5GC, the UE and the network achieve a secure connection using the security algorithm indicated in the UE security capability.

[0223] The N1 mode is a mode of a UE that is permitted to access and / or connect to a 5GCN via a 5G AN. In other words, the N1 mode is a mode of a UE that is permitted to communicate using an N1 interface. That is, a UE in N1 mode can access and / or connect to a 5GCN via a 5G AN and / or using the N1 interface.

[0224] The last visited registered TAI is a TAI included in the registration area where the UE is registered with the network, and is information indicating the TA last accessed by the UE. The last visited registered TAI may be the last visited registered TAI IE of 5GS, or may be indicated by the 5GS tracking area identity, which is information for identifying a TA within an area covered by 5GS.

[0225] The S1 UE network capability is information for indicating the security algorithms supported by the S1 mode UE, the Iu mode UE, and the Gb mode UE. In other words, the S1 UE security capability is information for notifying the network of the security algorithms supported by the UE when the UE accesses the core network via a 3G and / or 4G access network. The security algorithms supported in S1 mode are supported for both NAS security and AS security. The S1 UE network capability may be used by the UE and the network. The S1 UE security capability may be the S1 UE security capability IE of 5GS or the UE security capability IE of EPS.

[0226] When the UE is connected to the EPC, the UE and / or the network implements a secure connection using the security algorithm indicated in the S1 UE security capability.

[0227] The S1 mode may be a mode of a UE in which the UE is permitted to communicate using the S1 interface (the interface between the E-UTRAN (or eNB) and the EPC). In other words, a UE in S1 mode can connect to the core network via the E-UTRAN.

[0228] The Iu mode is a mode in which a UE is permitted to connect to a core network via an Iu interface with a GERAN (GSM / GPRS Radio Access Network) or a UTRAN (Universal / UMTS (Mobile Telecommunications System) Terrestrial Radio Access Network).

[0229] Gb mode is a mode in which a UE is permitted to connect to the core network via the Gb interface between a GERAN BSS (Base Station System) and a SGSN (Service GPRS (General Packet Radio Services / System) Support Node).

[0230] Mobile station classmark 2 is information for notifying a network of the priority of a mobile station (MS) equipment (UE). Mobile station classmark 2 may be a Mobile station classmark 2 IE of 5GS.

[0231] Supported codecs is information for providing a network with information about voice codecs supported by a mobile device (UE). Supported codecs may be a Supported codecs IE and / or a Supported codec list IE of 5GS.

[0232] SRVCC (Single Radio Voice Call Continuity) is a voice call handover technology that maintains voice calls between LTE and 3G.

[0233] 5G-SRVCC is a voice call handover technology that maintains voice calls between 5G and 3G.

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

[0235] The first identification information is information indicating whether the UE supports a function of storing one or more mapped S-NSSAIs for a pending NSSAI. The first identification information may be information indicating that the UE can store one or more mapped S-NSSAIs for a pending NSSAI, or may be information indicating that the UE does not support a function of storing one or more mapped S-NSSAIs for a pending NSSAI. The first identification information may be 5GMM capability information and may be transmitted and received by being included in a 5GMM capability IE. The first identification information may be information indicating that the UE can store one or more mapped S-NSSAIs for a pending NSSAI. The first identification information may be information indicating that the UE cannot store one or more mapped S-NSSAIs for a pending NSSAI.

[0236] The first identification information may be information indicating whether the function for storing a second pending NSSAI is supported, or may mean that the function for storing a second pending NSSAI is supported.

[0237] The second identification information may be information indicating that the UE supports a function for managing the maximum number of UEs connecting to a slice. Alternatively, the second identification information may be information indicating whether the UE supports a function for managing the maximum number of UEs connecting to a slice. The second identification information may be 5G MM capability IE information and may be transmitted and received by being included in the 5G MM capability IE. The second identification information may be information indicating that the UE can store the fourth rejected NSSAI and / or one or more mapped S-NSSAIs for the fourth rejected NSSAI. Alternatively, the second identification information may be information indicating that the UE cannot store the fourth rejected NSSAI and / or one or more mapped S-NSSAIs for the fourth rejected NSSAI.

[0238] The tenth identification information may be information indicating whether one or more S-NSSAIs included in the pending NSSAI transmitted together are S-NSSAIs of the current PLMN or SNPN, or S-NSSAIs of the HPLMN or HSNPN. The tenth identification information may be included in the pending NSSAI IE or may be transmitted and received using an IE independent of the pending NSSAI IE.

[0239] The tenth identification information may be information indicating that one or more S-NSSAIs included in the pending NSSAI transmitted together are S-NSSAIs of the current PLMN or SNPN. The tenth identification information may be information indicating that one or more S-NSSAIs included in the pending NSSAI transmitted together are S-NSSAIs of the HPLMN or HSNPN.

[0240] The tenth identity may be information transmitted and received when the UE is roaming. If the tenth identity is transmitted and received when the UE is not roaming, the tenth identity may be information indicating that one or more S-NSSAIs included in the pending NSSAI transmitted together are S-NSSAIs of the current PLMN or SNPN, or S-NSSAIs of the HPLMN or HSNPN.

[0241] [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, a network slice-specific authentication and authorization procedure, a generic UE configuration update procedure, and a network-initiated de-registration procedure. Each procedure will be described below.

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

[0243] 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 initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with a network, it can execute this procedure at any time, for example, when it is powered on. In other words, if the UE is in a deregistered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (5GMM-REGISTED 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 unregistered state) for 3GPP access and the registration state for non-3GPP access.

[0244] 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.

[0245] A UE may initiate a registration procedure when it moves across tracking areas (TAs). In other words, a UE may initiate a registration procedure when it moves to a TA different from the TA indicated in its TA list (TAI list or registration area). Furthermore, a UE may initiate this procedure when a running backoff timer or other timer expires. Furthermore, a UE may initiate a registration procedure when a context update for each device is required due to a PDU session disconnection or invalidation. Furthermore, a UE may initiate a registration procedure when a change occurs in the UE's capability information and / or preferences related to PDU session establishment. Furthermore, a UE may initiate a registration procedure periodically. Furthermore, a UE may initiate a registration procedure based on the completion of a UE configuration update procedure, a registration procedure, a PDU session establishment procedure, a PDU session management procedure, information received from the network in each procedure, or the expiration or stopping of a backoff timer. Note that the UE may perform the registration procedure at any timing, not limited to these.

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

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

[0248] 6 indicates the AMF to which UE_A10 is registered by this procedure, and old AMF142 refers to the AMF to which the UE was registered by a procedure prior to this procedure. If no AMF change 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 referring to AMF, it may mean new AMF141, old AMF142, or both. Note that new AMF141 and old AMF142 may be AMF140.

[0249] First, UE_A10 starts the registration procedure by sending a registration request message to new AMF141 (S600) (S602) (S604). Specifically, the UE sends an RRC message including a registration request message to 5G AN120 (or gNB) (S600). Note that the registration request message is a NAS message transmitted and received on the N1 interface. Also, the RRC message may be a control message transmitted and received between the UE and 5G AN120 (or gNB). Also, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

[0250] Here, UE_A10 can transmit at least one or more of the first and second identification information in the registration request message and / or the RRC message. Furthermore, UE_A10 may transmit the registration request message and / or the RRC message including identification information indicating the type of the procedure.

[0251] 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 periodically, or for emergency registration, or for SNPN onboarding registration.

[0252] 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.

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

[0254] Here, UE_A10 may include the 5GMM capability IE in the registration request message, except when this procedure (registration procedure) is a periodic registration update procedure and / or when this procedure is a registration procedure for an SNPN onboarding service.

[0255] In other words, UE_A10 may include the 5GMM capability IE in the registration request message unless UE_A10 is performing a periodic registration updating procedure and / or UE_A10 is performing an SNPN onboarding registration procedure.

[0256] In other words, UE_A10 may include the 5GMM capability IE in the registration request message except when UE_A10 is performing a periodic registration updating procedure and / or when UE_A10 is performing a registration procedure for initial registration for onboarding services in SNPN.

[0257] In other words, UE_A10 may include a 5GMM capability IE in the registration request message unless UE_A10 performs a registration procedure using a 5GS registration type IE indicating periodic registration updating or registration for SNPN onboarding service (SNPN onboarding registration).

[0258] In other words, if this procedure (registration procedure) is a periodic registration update procedure and / or if this procedure is a registration procedure for an SNPN onboarding service, UE_A10 does not need to include the 5GMM capability IE in the registration request message.

[0259] UE_A10 may include the 5GMM capability IE in the registration request message, except when this procedure (registration procedure) is a registration procedure for an SNPN. In other words, when this procedure (registration procedure) is a registration procedure for an SNPN, UE_A10 does not need to include the 5GMM capability IE in the registration request message.

[0260] UE_A10 may include UE security capability in the registration request message to notify the security algorithm.

[0261] UE_A10 may include the UE security capability IE in the registration request message except when this procedure (registration procedure) is a periodic registration update procedure and / or when this procedure is a registration procedure for an SNPN onboarding service.

[0262] In other words, UE_A10 may include 5 UE security capability IE in the registration request message unless UE_A10 is performing a periodic registration updating procedure and / or UE_A10 is performing an SNPN onboarding registration procedure.

[0263] In other words, UE_A10 may include the UE security capability IE in the registration request message unless UE_A10 is performing a periodic registration updating procedure and / or UE_A10 is performing a registration procedure for initial registration for onboarding services in SNPN.

[0264] In other words, UE_A10 may include the UE security capability IE in the registration request message unless UE_A10 performs a registration procedure using a 5GS registration type IE indicating periodic registration updating or registration for SNPN onboarding service (SNPN onboarding registration).

[0265] In other words, if this procedure is a periodic registration update procedure and / or if this procedure is a registration procedure for an SNPN onboarding service, UE_A10 does not need to include the UE security capability IE in the registration request message.

[0266] UE_A10 may include the UE security capability IE in the registration request message, except when this procedure (registration procedure) is a registration procedure for an SNPN. In other words, when this procedure (registration procedure) is a registration procedure for an SNPN, UE_A10 does not need to include the UE security capability IE in the registration request message.

[0267] Unless this procedure is a registration procedure for an SNPN onboarding service, if UE_A10 stores a valid last visited registered TAI, UE_A10 may include the Last Visited Registered TAI IE in the registration request message.

[0268] In other words, UE_A10 may include the Last visited registered TAI IE in the registration request message unless UE_A10 performs an SNPN onboarding registration procedure.

[0269] In other words, the Last visited registered TAI IE may be included in the registration request message unless UE_A10 is performing the registration procedure for initial registration for onboarding services in SNPN.

[0270] In other words, UE_A10 may include the Last visited registered TAI IE in the registration request message unless UE_A10 performs a registration procedure using a 5GS registration type IE indicating registration for SNPN onboarding service (SNPN onboarding registration).

[0271] In other words, if this procedure is a registration procedure for an SNPN onboarding service, even if UE_A10 stores a valid last visited registered TAI, UE_A10 does not need to include the Last visited registered TAI IE in the registration request message.

[0272] If UE_A10 supports S1 mode, UE_A10 may include an S1 UE security capability IE in the registration request message to notify the EPC of the security algorithm to be used for access, except when this procedure (registration procedure) is a periodic registration update procedure and / or when this procedure is a registration procedure for an SNPN onboarding service.

[0273] In other words, UE_A10 may include 5 S1 UE security capability IE in the registration request message unless UE_A10 is performing a periodic registration updating procedure and / or UE_A10 is performing an SNPN onboarding registration procedure.

[0274] In other words, UE_A10 may include the S1 UE security capability IE in the registration request message unless UE_A10 is performing a periodic registration updating procedure and / or UE_A10 is performing a registration procedure for initial registration for onboarding services in SNPN.

[0275] In other words, UE_A10 may include the S1 UE security capability IE in the registration request message unless UE_A10 performs a registration procedure using a 5GS registration type IE indicating periodic registration updating or registration for SNPN onboarding service (SNPN onboarding registration).

[0276] In other words, UE_A10 may include the S1 UE security capability IE in the registration request message unless UE_A10 performs an SNPN onboarding registration procedure.

[0277] In other words, UE_A10 may include the S1 UE security capability IE in the registration request message unless UE_A10 is performing a registration procedure for initial registration for onboarding services in SNPN.

[0278] In other words, UE_A10 may include the S1 UE security capability IE in the registration request message unless UE_A10 performs a registration procedure using a 5GS registration type IE indicating registration for SNPN onboarding service (SNPN onboarding registration).

[0279] In other words, if this procedure is a registration procedure for an SNPN onboarding service, even if UE_A10 supports S1 mode, UE_A10 does not need to include the S1 UE security capability IE in the registration request message.

[0280] UE_A10 may include the S1 UE security capability IE in the registration request message, except when this procedure (registration procedure) is a registration procedure for an SNPN. In other words, when this procedure (registration procedure) is a registration procedure for an SNPN, UE_A10 does not need to include the S1 UE security capability IE in the registration request message.

[0281] If UE_A10 supports 5G-SRVCC from NG-RAN to UTRAN, UE_A10 may include Mobile station classmark 2 IE in the registration request message, except when this procedure is a registration procedure for an SNPN onboarding service.

[0282] In other words, UE_A10 may include the Mobile station classmark 2 IE in the registration request message unless UE_A10 performs an SNPN onboarding registration procedure.

[0283] In other words, UE_A10 may include the Mobile station classmark 2 IE in the registration request message unless UE_A10 is performing a registration procedure for initial registration for onboarding services in SNPN.

[0284] In other words, UE_A10 may include a Mobile station classmark 2 IE in the registration request message unless UE_A10 performs a registration procedure using a 5GS registration type IE indicating registration for SNPN onboarding service (SNPN onboarding registration).

[0285] In other words, if this procedure is a registration procedure for an SNPN onboarding service, UE_A10 does not need to include the Mobile station classmark 2 IE in the registration request message even if UE_A10 supports 5G-SRVCC from NG-RAN to UTRAN.

[0286] UE_A10 may include the Mobile station classmark 2 IE in the registration request message, except when this procedure (registration procedure) is a registration procedure for an SNPN. In other words, when this procedure (registration procedure) is a registration procedure for an SNPN, UE_A10 does not need to include the Mobile station classmark 2 IE in the registration request message.

[0287] If UE_A10 supports 5G-SRVCC from NG-RAN to UTRAN, UE_A10 may include the Supported codecs IE in the registration request message, except when this procedure is a registration procedure for an SNPN onboarding service.

[0288] In other words, UE_A10 may include the Supported codecs IE in the registration request message unless UE_A10 performs the SNPN onboarding registration procedure.

[0289] In other words, UE_A10 may include the Supported codecs IE in the registration request message unless UE_A10 is performing a registration procedure for initial registration for onboarding services in SNPN.

[0290] In other words, UE_A10 may include the Supported codecs IE in the registration request message unless UE_A10 performs a registration procedure using a 5GS registration type IE indicating registration for SNPN onboarding service (SNPN onboarding registration).

[0291] In other words, if this procedure is a registration procedure for an SNPN onboarding service, UE_A10 does not need to include the Supported codecs IE in the registration request message even if UE_A10 supports 5G-SRVCC from NG-RAN to UTRAN.

[0292] UE_A10 may include the Supported codecs IE in the registration request message, except when this procedure (registration procedure) is a registration procedure for an SNPN. In other words, when this procedure (registration procedure) is a registration procedure for an SNPN, UE_A10 does not need to include the Supported codecs IE in the registration request message.

[0293] In addition, the registration procedure for the SNPN onboarding service may be an initial registration procedure for the SNPN onboarding service, or a registration procedure for updating registration for mobility when the UE is registered for the SNPN onboarding service.

[0294] In addition, when this procedure is a registration procedure for the SNPN onboarding service, it may mean that the 5GS registration type IE sent and received during this procedure indicates a registration procedure for the SNPN onboarding service (SNPN onboarding registration).

[0295] In other words, if the procedure is a registration procedure for an onboarding service of an SNPN, the UE may include a 5GS registration type IE indicating the registration procedure for an onboarding service of an SNPN in a registration request message and send the registration request message to the core network.

[0296] Furthermore, when this procedure (registration procedure) is a registration procedure for an SNPN, it may mean that a PLMN ID and an NID for identifying the SNPN are transmitted and received between the core network and the UE during this procedure. In other words, when this procedure (registration procedure) is a registration procedure for an SNPN, it may mean that the UE selects an SNPN when the UE is in an SNPN access operation mode, or may further mean that the UE includes an NID IE in a registration request message.

[0297] If this procedure (registration procedure) is a registration procedure for an SNPN, and if the UE holds a valid 5G-GUTI assigned by another SNPN, and if the UE has not initiated a registration procedure for the onboarding service of the SNPN, the UE may include the 5G-GUTI in the 5GS mobile identity IE and the NID of the other SNPN in the NID IE, and include the 5GS mobile identity IE and the NID IE in the registration request message.

[0298] In other words, if the UE connects to the SNPN using the credentials of another SNPN, the UE may include the NID IE in the registration request message.

[0299] UE_A10 may transmit these identification information and / or IEs in a different control message, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer). By transmitting these identification information, UE_A10 may indicate that UE_A10 supports each function, or 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.

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

[0301] UE_A10 may send second identification information if it has a function for managing the maximum number of UEs connecting to a slice or if it requests at least one S-NSSAI that requires management for managing the maximum number of UEs connecting to a slice. UE_A10 may notify the network by sending the second identification information that it has a function for storing a fourth rejected NSSAI.

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

[0303] If the UE stores "allowed NSSAIs associated with the UE's requested PLMN or SNPN and the UE's requested access type," and / or stores "configured NSSAIs for the requested PLMN or SNPN," and / or stores "default configured NSSAIs," 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.

[0304] 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.

[0305] Note that the UE may include the requested NSSAI in the registration request message, except when this procedure is a registration procedure for the onboarding service of the SNPN.

[0306] Alternatively, if the UE stores "an allowed NSSAI associated with a PLMN different from the PLMN requested by the UE or an SNPN different from the SNPN requested by the UE, and an access type requested by the UE," and if the TAI included in the 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.

[0307] The UE_A10 may determine information to be 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-NSAIs for the allowed NSSAI, and / or a configured NSSAI associated with the requested PLMN or SNPN, and / or one or more mapped S-NSAIs for the configured NSSAI, 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-NSAIs for the rejected NSSAI. Further, the one or more NSSAIs stored by the UE may be a pending NSSAI associated with the requested PLMN or SNPN, one or more mapped S-NSAIs for the pending NSSAI, or a rejected NSSAI not associated with a PLMN.

[0308] 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 the access type requested by the UE, and / or one or more mapped S-NSAIs for that allowed NSSAI, and / or a second rejected NSSAI associated with a PLMN or SNPN other than the PLMN or SNPN requested and the current registration area, and / or one or more mapped S-NSAIs for that 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 these 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.

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

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

[0311] Further / or, if UE_A10 stores a configured NSSAI associated with the requested PLMN or SNPN, UE_A10 may include the configured NSSAI, or a portion thereof, i.e., one or more S-NSSAIs included in the configured NSSAI, in the requested NSSAI and transmit it.

[0312] 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 include in the requested NSSAI IE, and may transmit the selected mapped S-NSSAI in the requested NSSAI IE.

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

[0314] 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 if a TAI included in the 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.

[0315] 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" 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 by the UE.

[0316] 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.

[0317] Below, we will summarize the control method and / or the generation method of the requested NSSAI IE for the S-NSSAI to be included in the requested NSSAI and / or the mapped S-NSSAI to be included in "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 mean the first to fourth rejected NSSAIs associated with the requested PLMN or EPLMN, or the requested SNPN or ESNPN.

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

[0319] Specifically, when UE_A10 stores a "first rejected NSSAI associated with the requested PLMN or SNPN," UE_A10 may transmit an 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.

[0320] However, when UE_A10 also stores a list of mapped S-NSSAIs for the "first rejected NSSAI associated with the requested PLMN or SNPN," if there are one or more stored mapped S-NSSAIs that are not included in the list of mapped S-NSSAIs for the first rejected 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 that mapped S-NSSAI is mapped can be included in the requested NSSAI.

[0321] When UE_A10 stores one or more mapped S-NSSAIs for a first rejected NSSAI when roaming, and if UE_A10 also stores one or more mapped S-NSSAIs that are not included in the one or more mapped S-NSSAIs for the first rejected NSSAI stored by UE_A10 but are included in one or more mapped S-NSSAIs 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.

[0322] 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 so that one or more S-NSSAIs included in the requested NSSAI are not S-NSSAIs 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.

[0323] 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 one or more different PLMNs or 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 PLMN or SNPN among the one or more different PLMNs or SNPNs and the current registration area'' stored by UE_A10.

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

[0325] However, when UE_A10 also stores a list of mapped S-NSSAIs for the "second rejected NSSAI associated with the requested PLMN or EPLMN or SNPN or ESNPN and the current registration area," if there are one or more stored mapped S-NSSAIs that are not included in the list of mapped S-NSSAIs for the second rejected 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 that mapped S-NSSAI is mapped can be included in the requested NSSAI.

[0326] When UE_A10 stores one or more mapped S-NSSAIs for the second rejected NSSAI when roaming, and UE_A10 also 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 sent together with the mapped S-NSSAI in a registration request message.

[0327] Furthermore, when UE_A10 stores a "third rejected NSSAI associated with the requested PLMN," 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" stored by UE_A10.

[0328] Furthermore, if 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.

[0329] Furthermore, when UE_A10 stores a "third rejected NSSAI valid for all PLMNs or all SNPNs or both," UE_A10 may transmit the S-NSSAI included in the third rejected NSSAI IE, or the S-NSSAI to which the S-NSSAI is mapped, or the S-NSSAI associated with the S-NSSAI, or the mapped S-NSSAI of the S-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 the S-NSSAI included in each "third rejected NSSAI valid for all PLMNs or all SNPNs or both" stored by UE_A10, or the S-NSSAI to which the S-NSSAI is mapped, or the S-NSSAI associated with the S-NSSAI, or the mapped S-NSSAI of the S-NSSAI. Note that the "third rejected NSSAI valid for all PLMNs" may refer to a third rejected NSSAI that is not associated with a PLMN, or may refer to a third rejected NSSAI that is associated with a HPLMN.

[0330] 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.

[0331] 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.

[0332] 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 controlled by UE_A10 so that it may be included in the first rejected NSSAI or the second rejected NSSAI stored by UE_A10.

[0333] 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.

[0334] In other words, UE_A10 may control the S-NSSAI of the current PLMN and / 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, and 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 that mapped S-NSSAI is mapped may be controlled by UE_A10 so that it can be included in the registration request message.

[0335] 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.

[0336] Controlling the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI so that it can be included in the 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.

[0337] Furthermore, when UE_A10 roams, if UE_A10 stores a mapped S-NSSAI of the first rejected NSSAI and / 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, 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.

[0338] In addition, when UE_A10 roams, if UE_A10 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-NSSAIs of the first rejected NSSAI stored by UE_A10 or the list of mapped S-NSSAIs of the second rejected NSSAI stored by UE_A10.

[0339] 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 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 that mapped S-NSSAI in the registration request message.

[0340] When the UE is not roaming, the S-NSSAI included in the third rejected 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 third rejected NSSAI as a mapped S-NSSAI may not be included in the requested NSSAI.

[0341] 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.

[0342] 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.

[0343] 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 third rejected NSSAI.

[0344] 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 that is not associated with the S-NSSAI included in the third rejected NSSAI.

[0345] However, when the UE roams, if there is one or more S-NSSAIs included in one or more stored mapped S-NSSAIs for a configured NSSAI that is 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 to which the S-NSSAI is associated as the mapped S-NSSAI in a registration request message together with the mapped S-NSSAI. Specifically, in this case, the UE may construct a requested NSSAI IE using an NSSAI IE that includes the mapped S-NSSAI and an S-NSSAI IE that includes the S-NSSAI to which the mapped S-NSSAI is associated.

[0346] Furthermore, UE_A10 may transmit an S-NSSAI or an S-NSSAI related to the S-NSSAI without including it in the requested NSSAI if the backoff timer associated with the S-NSSAI is valid, in other words, if the backoff timer is running or until the backoff timer is stopped. Specifically, if the S-NSSAI associated with the backoff timer is an S-NSSAI associated with the requested PLMN or an S-NSSAI included in the NSSAI associated with the requested PLMN, UE_A10 may transmit the S-NSSAI without including it in the requested NSSAI while the backoff timer is counting or until the backoff timer expires or is stopped.

[0347] Hereinafter, if the backoff timer associated with an 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.

[0348] Furthermore, when UE_A10 stores a list of mapped S-NSSAIs for the fourth rejected NSSAI, the validity of the fourth rejected NSSAI 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.

[0349] 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.

[0350] Alternatively, if the S-NSSAI to which the backoff timer is associated is associated with the HPLMN, UE_A10 may transmit the S-NSSAI of the requested PLMN to which the S-NSSAI is mapped without including it in the requested NSSAI. Note that the S-NSSAI to which the backoff timer is associated is associated with the HPLMN may mean that the backoff timer is valid for all PLMNs, or may mean that the backoff timer is not associated with the PLMN.

[0351] Furthermore, when the UE stores the "fourth rejected NSSAI associated with the requested PLMN," the UE may transmit an S-NSSAI included in the fourth rejected NSSAI without including it in the requested NSSAI. In other words, the UE may perform control such 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" stored by the UE.

[0352] Furthermore, if the UE stores at least one "fourth rejected NSSAI associated with the EPLMN of the requesting PLMN," the UE may transmit an S-NSSAI included in the fourth rejected NSSAI without including it in the requested NSSAI. In other words, the UE may control such that one or more S-NSSAIs included in the requested NSSAI are not S-NSSAIs included in each "fourth rejected NSSAI associated with the EPLMN of the requesting PLMN."

[0353] Furthermore, when the UE stores a "fourth rejected NSSAI valid for all PLMNs," the UE may transmit an S-NSSAI included in the fourth rejected NSSAI or an S-NSSAI to which the S-NSSAI is mapped 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-NSSAI included in each "fourth rejected NSSAI valid for all PLMNs" or the S-NSSAI to which the S-NSSAI is mapped. Note that the "fourth rejected NSSAI valid for all PLMNs" may refer to a fourth rejected NSSAI that is not associated with a PLMN, or may refer to a fourth rejected NSSAI that is associated with a HPLMN.

[0354] When roaming, if the rejected NSSAI, and / or the pending NSSAI, and / or the fourth rejected NSSAI includes an S-NSSAI of the HPLMN, UE_A10 may control one or more S-NSSAIs included in the requested NSSAI not to include the S-NSSAI of the HPLMN included in the rejected NSSAI, and / or the pending NSSAI, and / or the fourth rejected NSSAI stored by UE_A10 as the mapped S-NSSAI. In other words, UE_A10 may control not to include the S-NSSAI of the current PLMN to which the S-NSSAI included in the rejected NSSAI, and / or the pending NSSAI, and / or the fourth rejected NSSAI is mapped in the requested NSSAI.

[0355] 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, and the mapped S-NSSAI of that S-NSSAI is not included in the rejected NSSAI, pending NSSAI, and / or fourth rejected NSSAI stored by UE_A10. Here, the rejected NSSAI may be at least one of the first to fourth rejected NSSAIs, and includes the S-NSSAI of the HPLMN.

[0356] 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.

[0357] 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 roams, if UE_A10 stores a list of mapped S-NSSAIs of the fourth rejected NSSAI, and if UE_A10 also stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAIs of the fourth rejected 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 that mapped S-NSSAI is mapped may be controlled so that it can be included in the registration request message.

[0358] 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.

[0359] Controlling the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI so that it can be included in the 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.

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

[0361] 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.

[0362] 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 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 each "pending NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN."

[0363] However, when UE_A10 also stores a list of mapped S-NSSAIs for the "pending NSSAI associated with the requested PLMN or EPLMN" (hereinafter referred to as the 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 that mapped S-NSSAI is mapped can be included in the requested NSSAI.

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

[0365] 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 including the pending NSSAI associated with the mapped S-NSSAI and the S-NSSAI included in the configured NSSAI together with the mapped S-NSSAI.

[0366] Furthermore, when the UE stores a "pending NSSAI valid for all PLMNs" (hereinafter referred to as the pending NSSAI), the UE may send the S-NSSAI included in that pending NSSAI, or the S-NSSAI to which that S-NSSAI is mapped, or the S-NSSAI associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI without including it in the requested NSSAI IE.

[0367] In other words, the UE may control such that one or more S-NSSAIs and / or mapped S-NSSAIs included in the requested NSSAI are no longer the S-NSSAIs included in each "pending NSSAI valid for all PLMNs", or the S-NSSAI to which that S-NSSAI is mapped, or the S-NSSAI associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI. Note that "pending NSSAI valid for all PLMNs" may mean a pending NSSAI that is not associated with a PLMN, or may mean a pending NSSAI associated with a HPLMN.

[0368] The following describes the behavior of the UE when roaming or when not roaming if the UE does not store a mapped S-NSSAI for a pending NSSAI. Note that the 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 not.

[0369] 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.

[0370] 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.

[0371] 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.

[0372] 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.

[0373] 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 that is not associated with the S-NSSAI included in the pending NSSAI.

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

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

[0376] 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.

[0377] 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 the pending 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, or in 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 or the second rejected NSSAI or the pending NSSAI.

[0378] 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 for the first rejected NSSAI, mapped S-NSSAIs for the second rejected NSSAI, or mapped S-NSSAIs for the pending NSSAI, and UE_A10 also stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAIs for the first rejected NSSAI stored by UE_A10, the list of mapped S-NSSAIs for the second rejected NSSAI stored by UE_A10, or the list of mapped S-NSSAIs for the pending NSSAI stored by UE_A10, but is included in the list of mapped S-NSSAIs for the configured NSSAI, the S-NSSAI of the current PLMN or SNPN to which that mapped S-NSSAI is mapped may be controlled so that it can be included in the registration request message.

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

[0380] Controlling the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI so that it can be included in the 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.

[0381] Furthermore, when UE_A10 roams, if UE_A10 stores a list of mapped S-NSSAIs for the first rejected NSSAI, mapped S-NSSAIs for the second rejected NSSAI, or mapped S-NSSAIs for the pending NSSAI, and if UE_A10 stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAIs for the first rejected NSSAI stored by UE_A10, the list of mapped S-NSSAIs for the second rejected NSSAI stored by UE_A10, or the list of mapped S-NSSAIs for the pending NSSAI stored by UE_A10, but is 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 mapped to that mapped S-NSSAI can be included in the registration request message together with that mapped S-NSSAI.

[0382] In addition, when UE_A10 roams, if 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-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 pending NSSAI stored by UE_A10.

[0383] The UE_A10 may include identification information other than the first and second identification information in the registration request message and / or the RRC message containing the registration request message, for example, the UE ID and / or the PLMN ID and / or the AMF identification information, and may transmit the same. Here, the AMF identification information may be information that identifies an AMF or a set of AMFs, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

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

[0385] When the 5G AN 120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to transfer the registration request message (S602). Note that the 5G AN 120 (or gNB) can select an AMF based on one or more pieces of identification information included in the registration request message and / or the RRC message including the registration request message. Specifically, the 5G AN (or gNB) may select a new AMF 141 to which to send the registration request message based on at least one piece of identification information from the first to second pieces of identification information.

[0386] 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.

[0387] Further, for example, the 5G AN120 (or gNB) may select, based on the second identification information, an AMF having functionality for managing the maximum number of UEs connecting to the slice and / or an AMF having connectivity to a network having functionality for managing the maximum number of UEs connecting to the slice.

[0388] Note that the method for 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). Note that if at least one of the first and second identification information is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message may be transferred to the selected AMF (new AMF 141) together with the registration request message (S604).

[0389] When the new AMF 141 receives a registration request message, it can execute a first condition determination. The first condition determination is for determining whether 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.

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

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

[0392] Furthermore, the first condition determination may be performed based on the 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.

[0393] 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. Furthermore, if the network to which the UE is registered and / or a device within the network supports the function requested by the UE, the first condition determination may be true, and if the 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.

[0394] Furthermore, if 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 if the AMF stores the result of the NSSAA procedure for the corresponding S-NSSAI for the UE as successful, the first condition determination may be true. Alternatively, if there is no S-NSSAI to allow for the UE and there are no plans to assign an allowed NSSAI to the UE in the future, the first condition determination may be false.

[0395] Furthermore, if the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information identifying a slice that requires management of the maximum number of UEs connected to the slice, and if the maximum number of UEs has not been reached, the first condition determination may be true. Alternatively, even if there is no S-NSSAI to allow 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.

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

[0397] If the AMF indicated in the AMF identification information included in the message received by new AMF 141 from the UE is old AMF 142, 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 new AMF 141 from UE_A10 is new AMF 141, 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.

[0398] The UE context transfer procedure (S606, S608) will be described. The new AMF 141 sends a UE context request message to the old AMF 142 (S606). The old AMF 142 sends 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.

[0399] 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.

[0400] The UE context may also include information on 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.

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

[0402] 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 NSSAA is required, whether 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.

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

[0404] The new AMF 141 may transmit one or more tenth identification information items included in a control message. By transmitting this identification information item and / or control message, the new AMF 141 may indicate that the network supports each function, that the UE's request has been accepted, that the UE's request has not been permitted, or a combination of these. Furthermore, when multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. The information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information or as different identification information.

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

[0406] When the new AMF 141 receives the first identification information from the UE, the new AMF 141 may transmit the tenth identification information.

[0407] Furthermore, when the UE's configuration information is updated, new AMF141 may include the configured NSSAI, and / or allowed NSSAI, and / or rejected NSSAI, and / or pending NSSAI in a control message and send it to UE_A10. Note that the message sent by new AMF141 to the UE may be based on information received from the UE. Specifically, the S-NSSAI included in the rejected NSSAI sent by new AMF141 to the UE may be the S-NSSAI included in the requested NSSAI received from the UE.

[0408] When sending the control message, new AMF141 does not have an allowed NSSAI (S-NSSAI) for the UE, but if it plans to perform an NSSAA procedure after completing this procedure or in parallel with this procedure, or if an NSSAA procedure is currently being performed between the UE and the network, or if it has sent a pending NSSAI in the control message, it may send an empty value in the allowed NSSAI.

[0409] When transmitting a control message, new AMF141 does not have an S-NSSAI (allowed NSSAI) permitted for the UE, but if it includes an Allowed NSSAI in the control message, or if it has notified the UE of a fourth rejected NSSAI before this procedure, it may transmit an empty value in the allowed NSSAI.

[0410] When the new AMF 141 includes the 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.

[0411] UE_A10 receives a control message and / or one or more pieces of information contained in the control message from the network. More specifically, the UE receives the control message and / or the tenth identification information from new AMF141.

[0412] 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.

[0413] Specifically, the UE may store and / or update information related to the NSSAI and start and / or stop the 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.

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

[0415] Furthermore, the AMF may select and determine whether to include the 10th identification information and / or other identification information 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.

[0416] Furthermore, when the control message is a registration acceptance message, the AMF can include an SM message (e.g., a PDU session establishment acceptance message) in the registration acceptance message and send it, or can 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.

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

[0418] The UE receives a control message via the 5G AN (gNB) (S608). If the control message is a registration acceptance message, the UE can recognize by receiving the registration acceptance message that the UE's request in the registration request message has been accepted and the contents of various identification information included in the registration acceptance message. Alternatively, if the control message is a registration rejection message, the UE can recognize by receiving a registration rejection message that the UE's request in the registration request message has been rejected and the contents of various identification information included in the registration rejection message. Furthermore, if the UE does not receive a control message even after a predetermined period has elapsed since sending the registration request message, the UE may recognize that the UE's request has been rejected.

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

[0420] 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.

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

[0422] 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 sending and receiving a registration accept message and / or a registration complete message, or may transition to or maintain a state in which the UE is not registered in the network on the access from which the registration reject message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on sending and receiving a registration reject message. Also, the transition to each state of each device may be based on sending and receiving a registration complete message or completion of the registration procedure.

[0423] Furthermore, each device may perform processing based on the information transmitted and received during the registration procedure based on the completion of the registration procedure. For example, if the device transmits or receives 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 core network_A or another cell.

[0424] Additionally, the UE may store the identification information received with the registration accept message and / or registration reject message and may recognize the network's decision based on the completion of the registration procedure.

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

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

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

[0428] Additionally, each device may initiate the registration process again based on the updated NSSAI it stores.

[0429] 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 with the network (RM_REGISTERED state or 5GMM-REGISTERED state).

[0430] [3.2. UE Configuration Update Procedure] Next, the Generic UE configuration update procedure will be described with reference to Fig. 7. Hereinafter, the UE configuration update procedure will also be referred to as this procedure. This procedure is a procedure by which the core network updates the configuration information of the UE. This procedure may be a procedure for mobility management that is initiated by the network for a UE registered in the network.

[0431] Furthermore, a device in the core network, such as the AMF, may initiate this procedure based on an update to the network configuration and / or an update to the operator policy. The trigger for this procedure may be detection of UE mobility, detection of a change in the status of the UE, the access network, and / or the core network, or a change in the status of a network slice. The trigger for this procedure may be reception of a request from the DN and / or the DN's application server, a change in the network configuration, or a change in the operator policy. The trigger for this procedure may also be expiration of a running timer. However, triggers for the device in the core network to initiate this procedure are not limited to these. In other words, this procedure may be performed at any time after the completion of the registration procedure and / or the PDU session establishment procedure. The procedure may also be performed at any time as long as each device has established a 5GMM context and / or is in 5GMM connected mode.

[0432] During this procedure, each device may also send and receive messages containing identification information for changing the UE's configuration information and / or identification information for stopping or changing a function being performed by the UE. Furthermore, each device may update its configuration information to a configuration instructed by the network or start a behavior instructed by the network based on the completion of this procedure.

[0433] The UE may update its configuration information based on the control information transmitted and received through this procedure. Furthermore, the UE may stop a function currently being executed or start a new function in response to the update of the UE's configuration information. In other words, a device in the core network may initiate this procedure and send control messages and control information of this procedure to the UE, thereby causing the UE to update its configuration information, which can be identified using this control information. Furthermore, the device in the core network may stop a function currently being executed by the UE or cause the UE to start a new function by updating the UE's configuration information.

[0434] First, AMF140 starts the UE configuration update procedure by sending a configuration update command message to UE_A10 via 5G AN120 (or gNB) (S800).

[0435] Furthermore, if there is an update to the UE's configuration information, if the configuration update command message includes a pending NSSAI, and if the UE supports the function of storing one or more mapped S-NSSAIs for the pending NSSAI, the new AMF 141 may send the 10th identification information in the configuration update command message.

[0436] UE_A10 receives a configuration update command message and / or the tenth identification information from the network. More specifically, the UE receives a configuration update command message and / or the tenth identification information from the new AMF141.

[0437] UE_A10 may recognize the received information based on receiving the tenth identification information.

[0438] AMF140 may include one or more of the NSSAIs (hereinafter, meaning configured NSSAI, allowed NSSAI, rejected NSSAI, and pending NSSAI) related to UE_A10 in the configuration update command message and send it. Note that the AMF may indicate new UE configuration information or request an update of the UE configuration information by sending one or more of the NSSAIs. Note that 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.

[0439] Furthermore, AMF 140 may send a configuration update command message including a TAI list indicating the new registration area.

[0440] Furthermore, when multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that 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.

[0441] Furthermore, AMF140 may select and decide whether to include each NSSAI and TAI list in the configuration update command message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF140, etc.

[0442] In addition, AMF140 may indicate a request for an update of UE_A10's configuration information by sending a configuration update command message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF140, etc.

[0443] UE_A10 receives a configuration update command message from AMF140 via 5G AN120 (or gNB) (S800). UE_A10 may update the UE's configuration information based on the configuration update command message and / or identification information included in the configuration update command message.

[0444] Furthermore, when UE_A10 receives a TAI list, it may make the received TAI list valid, and if UE_A10 has already stored a valid TAI list, it may delete or invalidate the old TAI list. Hereinafter, the valid TAI list may be referred to as the registration area. Note that if UE_A10 does not store a valid TAI list and does not receive a TAI list from the core network during this procedure, the valid TAI list may not be stored.

[0445] 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.

[0446] The NSSAI update and / or storage procedure in Chapter 3.3 may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure. Furthermore, the UE may transmit a configuration update complete message as a response message to the configuration update command message via the 5G AN (gNB) to the AMF 140 based on the identification information included in the configuration update command message (S802).

[0447] When UE_A10 transmits a setting update completion command message, AMF140 receives the setting update completion message via 5G AN (gNB) (S802). In addition, each device completes this procedure based on the transmission and reception of the setting update command message and / or the setting update completion message.

[0448] Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, if update information for the configuration information is transmitted and received, each device may update the configuration information. Furthermore, if information indicating that the registration procedure needs to be performed is transmitted and received, UE_A10 may start the registration procedure based on the completion of this procedure.

[0449] Furthermore, upon completion of this procedure, UE_A10 may store the identification information received with the configuration information command message, recognize the network decision, and perform each procedure based on the stored information.

[0450] In the above procedure, by sending and receiving a configuration update command message, a device in the core network can instruct the UE to update the configuration information already applied by the UE, or to stop or change the functions being executed by the UE.

[0451] 3.3. NSSAI Update 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 ().

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

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

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

[0455] 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," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN," and the "third rejected NSSAI stored by UE_A10 and associated with the current PLMN."

[0456] Furthermore, when UE_A10 receives the 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", and / or one or more "fourth rejected NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN".

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

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

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

[0460] 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.

[0461] 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 the "allowed NSSAI received by UE_A10" includes a mapped S-NSSAI, UE_A10 may store the one or more mapped S-NSSAIs.

[0462] If 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."

[0463] When UE_A10 receives an Allowed NSSAI, it may delete the S-NSSAI included in the received Allowed NSSAI from the first rejected NSSAI and / or second rejected NSSAI stored by UE_A10 if the following conditions are met. The conditions 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, when the mapped S-NSSAI of that 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, when at least one mapped S-NSSAI of that 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 that 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-NSSAIs.

[0464] 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. 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 that S-NSSAI in the list (set) of mapped S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI, and / or when it is 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.

[0465] 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.

[0466] When UE_A10 stores the mapped S-NSSAI of the first rejected NSSAI and / or the 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 that it stores, 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 that it stores.

[0467] In other words, when UE_A10 stores the mapped S-NSSAI of the first rejected NSSAI and / or the mapped S-NSSAI of the second rejected NSSAI during roaming, if it receives an Allowed NSSAI IE including a list of mapped S-NSSAIs of 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, unless there are one or more mapped S-NSSAIs that are not included in the list of mapped S-NSSAIs of the new Allowed NSSAI and are included in the list of mapped S-NSSAIs of the first rejected NSSAI and / or the list of mapped S-NSSAIs of the second rejected NSSAI that UE_A10 stores.

[0468] In other words, when UE_A10 stores the mapped S-NSSAI of the first rejected NSSAI and / or the mapped S-NSSAI of the second rejected NSSAI during roaming, if it receives an Allowed NSSAI IE including a list of mapped S-NSSAIs 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-NSSAIs of the Allowed NSSAI mapped to that S-NSSAI includes all of the S-NSSAIs included in the list of mapped S-NSSAIs of the first rejected NSSAI mapped to that S-NSSAI and / or the S-NSSAI included in the list of mapped S-NSSAIs of the second rejected NSSAI.

[0469] When UE_A10 is not roaming, or when UE_A10 is roaming and does not store the mapped S-NSSAI of the first rejected NSSAI or the 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 second rejected NSSAI that it stores.

[0470] When roaming, UE_A10 may behave such 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.

[0471] When roaming, UE_A10 may behave in such a way 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.

[0472] When UE_A10 roams and stores first information consisting of an S-NSSAI and a mapped S-NSSAI in each NSSAI, UE_A10 may delete the combination of S-NSSAI and 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-NSSAIs for the first rejected NSSAI and / or the set of mapped S-NSSAIs for the second rejected NSSAI.

[0473] 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," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN and the current registration area," and the "third rejected NSSAI stored by UE_A10 and associated with the current PLMN," or it may delete the S-NSSAI included in the received allowed NSSAI and / or the mapped S-NSSAI of the received allowed NSSAI from all NSSAIs.

[0474] 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 the "second pending NSSAI stored by UE_A10 and associated with the current PLMN". 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".

[0475] 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 the S-NSSAI is included in a new allowed NSSAI or is a mapped S-NSSAI of an allowed NSSAI.

[0476] Here, in a roaming scenario, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN, 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 is associated with the PLMN ID or SNPN ID indicating the current PLMN or current SNPN, i.e., the RPLMN or RSNPN, while the S-NSSAI included in the pending NSSAI may be the S-NSSAI of the HPLMN.

[0477] Furthermore, when UE_A10 receives an allowed 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 current PLMN." Alternatively, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSAI or S-NSSAI included in the received allowed NSSAI from the "fourth rejected NSSAI stored by UE_A10 and associated with all PLMNs."

[0478] 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 NSSAIs stored by UE_A10.

[0479] 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.

[0480] 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 current PLMN and current registration area."

[0481] Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI not possible 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 may be common to all PLMNs.

[0482] If UE_A10 receives a TAI list along with the 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 along with the rejected NSSAI, the current registration area is indicated by the TAI list that UE_A10 previously received and stored.

[0483] Furthermore, if UE_A10 receives a rejected NSSAI including a rejection reason value "S-NSSAI not possible 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 if the UE stores the third rejected NSSAI associated with the current PLMN, it may add and / or store the received S-NSSAI to the third rejected NSSAI associated with the current PLMN.

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

[0485] Here, if UE_A10 receives a rejected NSSAI that includes the S-NSSAI of the HPLMN, 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" is included in the rejected NSSAI received by UE_A10, UE_A10 may delete that S-NSSAI from the "allowed NSSAI stored by UE_A10 and associated with the current PLMN."

[0486] 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" and / or the "second pending NSSAI stored by UE_A10 and associated with the current PLMN". 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".

[0487] Furthermore, when UE_A10 receives an allowed 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 current PLMN." Alternatively, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSAI or S-NSSAI included in the received allowed NSSAI IE from the "fourth rejected NSSAI stored by UE_A10 and associated with all PLMNs."

[0488] 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 NSSAIs by including them in the set of each rejected NSSAI and / or mapped S-NSSAI for each rejected NSSAI stored by UE_A10.

[0489] More specifically, if UE_A10 receives a rejected NSSAI IE, and if the rejected S-NSSAI#1 included in the 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 S-NSSAI#1 as part of the first rejected NSSAI stored by the UE.

[0490] Similarly, if UE_A10 receives a rejected NSSAI IE, and the rejected S-NSSAI#1 included in the rejected NSSAI IE includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI that is not allowed in the current registration area," UE_A10 may store S-NSSAI#1 as part of the second rejected NSSAI stored by the UE.

[0491] Similarly, if UE_A10 receives a rejected NSSAI IE, and the rejected S-NSSAI#1 included in the rejected NSSAI IE includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI that is not acceptable due to NSSAI failure or cancellation," UE_A10 may store S-NSSAI#1 as part of the third rejected NSSAI stored by the UE.

[0492] Alternatively, if UE_A10 receives an Extended rejected NSSAI IE, and 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 that is not possible in the current PLMN or SNPN," UE_A10 may store S-NSSAI#1 as part of the first rejected NSSAI stored by the UE, and may store mapped S-NSSAI1#1 as part of the set of mapped S-NSSAIs for the first rejected NSSAI. Alternatively, under the same conditions, UE_A10 may store the combination of S-NSSAI#1 and mapped S-NSSAI1#1 as part of the first rejected NSSAI stored by the UE.

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

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

[0495] 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 included in the received rejected NSSAI from the Allowed NSSAI stored by UE_A10 if the following conditions are met. The conditions for deleting an S-NSSAI from the Allowed NSSAI stored by UE_A10 may be when UE_A10 is not roaming, when the mapped S-NSSAI of that S-NSSAI is included in the set of mapped S-NSSAI of the Allowed NSSAI and is not stored by UE_A10, when at least one mapped S-NSSAI of that 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 second rejected NSSAI received by the UE, or when the mapped S-NSSAI of that S-NSSAI is not included in the first rejected NSSAI and / or 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.

[0496] In addition, 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, this may be when UE_A10 receives the first rejected NSSAI and / or the second rejected NSSAI included in the rejected NSSAI IE, or when 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.

[0497] 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 has stored the mapped S-NSSAI of that S-NSSAI in the list (set) of mapped S-NSSAIs of the Allowed NSSAI, and / or when it is 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.

[0498] 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.

[0499] When UE_A10 receives a first rejected NSSAI or a second rejected NSSAI during roaming, if one or more mapped S-NSSAIs of an 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 remove the S-NSSAI from the Allowed NSSAI.

[0500] 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.

[0501] 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.

[0502] 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 NSSAIs and the mapped S-NSSAIs of the Allowed NSSAI.

[0503] 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.

[0504] 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-NSSAIs of the Allowed NSSAI that it stores.

[0505] When UE_A10 receives a third rejected NSSAI, and is not roaming any further, UE_A10 may delete the stored Allowed NSSAI and the S-NSSAI included in the third rejected NSSAI.

[0506] If UE_A10 receives a first rejected NSSAI and / or a second rejected NSSAI included in an Extended rejected NSSAI IE, and further when roaming, UE_A10 may remove 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 Allowed NSSAI that it stores.

[0507] 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 included 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 that S-NSSAI is included in the set of mapped S-NSSAIs of the Allowed NSSAI and is not stored by UE_A10, or when at least one mapped S-NSSAI of that S-NSSAI is stored in UE_A10 in the mapped S-NSSAI of the pending NSSAI stored in UE_A10 and further when 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 that 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-NSSAIs.

[0508] In addition, 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, this may be when UE_A10 receives the first rejected NSSAI and / or the second rejected NSSAI included in the rejected NSSAI IE, or when 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.

[0509] When UE_A10 receives a rejected NSSAI, it may not delete the first rejected NSSAI and / or the S-NSSAI included in the second rejected NSSAI included in the received rejected NSSAI from the Pending NSSAI stored by UE_A10. 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 has stored the mapped S-NSSAI of that S-NSSAI in the list (set) of mapped S-NSSAIs of the Pending NSSAI and / or when it is 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.

[0510] 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.

[0511] 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.

[0512] 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.

[0513] 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-NSSAIs of the Pending NSSAI and Allowed NSSAI.

[0514] 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.

[0515] 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-NSSAIs of the Allowed NSSAI that it stores.

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

[0517] If UE_A10 receives a first rejected NSSAI and / or a second rejected NSSAI included in an Extended rejected NSSAI IE, and further when roaming, UE_A10 may remove 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 pending NSSAIs that it stores.

[0518] 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." Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the mapped S-NSSAI or S-NSSAI included in the received allowed NSSAI from the "fourth rejected NSSAI stored by UE_A10 and associated with all PLMNs." 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."

[0519] Furthermore, if a back-off timer that restricts the use of a certain 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.

[0520] Furthermore, when UE_A10 receives a pending NSSAI, it may replace the pending NSSAI stored by UE_A10 with a new pending NSSAI. Specifically, when UE_A10 receives a pending NSSAI included in a registration accept 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 by UE_A10 with the new pending NSSAI.

[0521] Alternatively, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN, 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.

[0522] 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.

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

[0524] The UE may recognize whether the received pending NSSAI IE includes the first pending NSSAI or the second pending NSSAI based on the reception of the tenth identification information.

[0525] Specifically, when a pending NSSAI IE is received together with the tenth identification information indicating the first pending NSSAI, the UE recognizes that the S-NSSAI included in the pending NSSAI IE is the S-NSSAI of the HPLMN even when roaming, and may store or replace it.

[0526] Alternatively, if the UE receives a pending NSSAI IE together with the tenth identification information indicating the second pending NSSAI, the UE may recognize that the S-NSSAI included in the pending NSSAI IE is the S-NSSAI of the current PLMN and its mapped S-NSSAI, and may store or replace it.

[0527] Alternatively, the UE may recognize whether a pending NSSAI is the first or second pending NSSAI depending on whether the pending NSSAI IE includes a mapped S-NSSAI. Specifically, when a pending NSSAI IE including one or more mapped S-NSSAIs is received during roaming, the UE may recognize it as the second pending NSSAI and store or replace the pending NSSAI and / or one or more mapped S-NSSAIs for the pending NSSAI included in the received pending NSSAI IE.

[0528] On the other hand, when roaming, if a pending NSSAI IE that does not include a mapped S-NSSAI is received, the UE may recognize it as the first pending NSSAI and store or replace the pending NSSAI included in the received pending NSSAI IE.

[0529] 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 the S-NSSAI is included in a new pending NSSAI or is a mapped S-NSSAI of a pending NSSAI.

[0530] Furthermore, 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 the reception of one or more rejected S-NSSAI IEs, and / or Partial extended rejected NSSAI list IEs, and / or Extended rejected NSSAI IEs indicating the fourth rejected NSSAI, and / or the reception of a control message.

[0531] UE_A10 may store the S-NSSAI of the current PLMN or SNPN indicated in the fourth rejected NSSAI by including it in the 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.

[0532] 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.

[0533] 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 and access type requested by the UE in this procedure and other access types, the S-NSSAI may be deleted from the allowed NSSAI.

[0534] 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 the backoff timer using the backoff timer value, or may manage the backoff timer.

[0535] Here, if 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., if 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.

[0536] While the backoff timer is running, UE_A10 may be in a state where it is prohibited from 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) 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 associated with the backoff timer, or mapped S-NSSAIs of one or more S-NSSAIs included in the NSSAI associated with the backoff timer.

[0537] 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.

[0538] Here, upon stopping or expiration of the back-off timer, the restriction is lifted, and UE_A10 may transition to a state in which it can transmit MM messages and SM messages 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, upon stopping or expiration of the back-off timer, UE_A10 may transition to a state in which it can transmit MM messages 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.

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

[0540] Furthermore, upon stopping or expiration of the backoff timer, 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.

[0541] Specifically, upon stopping or expiration of the backoff timer, 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.

[0542] 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 it stores.

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

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

[0545] Alternatively, UE_A10 running the backoff timer may stop and / or delete the backoff timer without updating or deleting the fourth rejected NSSAI. Specific examples of conditions for deleting the fourth rejected NSSAI and / or stopping the backoff timer are shown below.

[0546] 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.

[0547] 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 which the fourth rejected NSSAI, regardless of access type, and / or the S-NSSAI included in the fourth rejected NSSAI, is valid.

[0548] 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 the access type.

[0549] When 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 stop or delete the backoff timer for which the S-NSSAI included in the fourth rejected NSSAI is valid, regardless of the access type.

[0550] 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 the access type.

[0551] 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.

[0552] If UE_A10 receives from the current PLMN or SNPN a pending NSSAI for an NSSAI or 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 mapped, UE_A10 may remove that S-NSSAI from that fourth rejected NSSAI regardless of access type.

[0553] If UE_A10 receives from the current PLMN or SNPN a pending NSSAI for an NSSAI or 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 mapped, UE_A10 may stop or delete the backoff timer for which the S-NSSAI included in the fourth rejected NSSAI is valid.

[0554] When UE_A10 transitions to an unregistered state on a certain 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.

[0555] 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.

[0556] If 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.

[0557] 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 backoff 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.

[0558] 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 backoff timer for which the fourth rejected NSSAI is valid.

[0559] In this way, the UE stores and manages information about each NSSAI. Furthermore, the UE may start and stop a back-off timer that is valid for each NSSAI or S-NSSAI for a PLMN, an SNPN, or all PLMNs.

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

[0561] Furthermore, when the UE transitions to the registered state upon completion of the initial registration procedure described in Chapter 3.1, the procedures described in Chapters 3.2 to 3.4 may be performed. During each procedure, UE_A10 may perform the NSSAI update procedure described in Chapter 3.3 based on information received from the NW and / or the UE status, and may update and / or delete information related to the stored NSSAI.

[0562] A specific example of an embodiment of the present invention will be described below.

[0563] 4.1. First embodiment The first embodiment (hereinafter referred to as the present embodiment) will be described below.

[0564] In the first embodiment, an example of a registration request procedure will be described below when, when a UE roams, the UE stores a configured NSSAI associated with a PLMN or SNPN, one or more mapped S-NSSAIs for that configured NSSAI, and a third rejected NSSAI.

[0565] Alternatively, in the first embodiment, an example of a registration request procedure will be described in a case where, when a UE roams, the UE stores a configured NSSAI associated with a PLMN or an SNPN, one or more mapped S-NSSAIs for the configured NSSAI, and a first pending NSSAI. Note that the registration request procedure may be the registration request procedure of 3.1.

[0566] First, when roaming, UE_A10 generates a registration request message to perform a registration procedure for the first PLMN (or SNPN). UE_A10 may include a 5GMM capability IE and / or a UE security capability IE in the registration request message because this procedure is neither an onboarding service for an SNPN nor a periodic registration update procedure.

[0567] Similarly, if the UE remembers a valid last visited registered TAI, it may include the Last visited registered TAI IE in the registration request message since this procedure is not a registration procedure for onboarding services for an SNPN.

[0568] Similarly, if the UE supports S1 mode, the S1 UE network capability IE may be included in the registration request message, as this procedure is neither an onboarding service for an SNPN nor a periodic registration update procedure.

[0569] Similarly, if the UE supports 5G-SRVCC from NG-RAN to UTRAN, the Mobile station classmark 2 IE and / or Supported codecs IE may be included in the registration request message, since this procedure is not a registration procedure for onboarding services for an SNPN.

[0570] Next, the UE generates a requested NSSAI IE. First, the UE generates a requested NSSAI associated with the first PLMN to be included in the requested NSSAI IE.

[0571] When the UE stores the configured NSSAI, the requested NSSAI may be the configured NSSAI stored by the UE or a part thereof. However, when roaming, the S-NSSAI included in the requested NSSAI may be controlled so that it is not an S-NSSAI associated as a mapped S-NSSAI with one or more S-NSSAIs included in the third rejected NSSAI. Furthermore, when not roaming, the S-NSSAI included in the requested NSSAI may be controlled so that it is not one or more S-NSSAIs included in the third rejected NSSAI.

[0572] However, when roaming, if one or more (mapped) S-NSSAIs that are not included in the third rejected NSSAI are included in "one or more mapped S-NSSAIs for a configured NSSAI", the S-NSSAI included in the configured NSSAI to which those one or more (mapped) S-NSSAIs are associated may be included in the requested NSSAI IE together with that (mapped) S-NSSAI, even if it is included in the third rejected NSSAI.

[0573] Similarly, when roaming, the S-NSSAI included in the requested NSSAI may be controlled so that it is not an S-NSSAI associated as a mapped S-NSSAI with one or more S-NSSAIs included in the first pending NSSAI. Furthermore, when not roaming, the S-NSSAI included in the requested NSSAI may be controlled so that it is not one or more S-NSSAIs included in the first pending NSSAI.

[0574] However, if one or more (mapped) S-NSSAIs included in "one or more mapped S-NSSAIs for a configured NSSAI" are not included in the first pending NSSAI, the S-NSSAIs included in the configured NSSAI to which those one or more (mapped) S-NSSAIs are associated may be included in the first pending NSSAI and may be included in the requested NSSAI IE together with those (mapped) S-NSSAIs.

[0575] UE_A10 may include the requested NSSAI IE configured in the above manner in a registration request message. UE_A10 sends the registration request message to the core network.

[0576] Next, from the core network, the UE receives a registration accept message including an Allowed NSSAI IE and / or a rejected NSSAI IE or an Extended rejected NSSAI IE and / or a pending NSSAI IE.

[0577] As a result, UE_A10 can select and request the appropriate S-NSSAI and mapped S-NSSAI when roaming.

[0578] [4.2. Second embodiment] The second embodiment (hereinafter referred to as the present embodiment) will be described below.

[0579] In the second embodiment, an example of a registration request procedure will be described in a case where, when a UE roams, the UE stores a configured NSSAI, one or more mapped S-NSSAIs for the configured NSSAI, a second pending NSSAI, and one or more mapped S-NSSAIs for the second pending NSSAI. Note that the registration request procedure may be the registration request procedure of 3.1.

[0580] First, when roaming, UE_A10 generates a registration request message to perform a registration procedure with the first PLMN (or SNPN). The conditions for whether to include the 5GMM capability IE, and / or the UE security capability IE, and / or the Last visited registered TAI IE, and / or the S1 UE network capability IE, and / or the Mobile station classmark 2 IE, and / or the Supported codecs IE in the registration request message may be the same as those in the first embodiment.

[0581] In addition, the 5GMM capability IE may include first identification information indicating whether or not the device has the capability to store a mapped S-NSSAI for a pending NSSAI.

[0582] Otherwise, based on the capabilities supported by the UE, the UE may include the first identity information in the registration request message or the RRC message.

[0583] In this embodiment, since the device is provided with a function for storing a second pending NSSAI, the first identification information may be information indicating that the device supports the function for storing a second pending NSSAI.

[0584] Next, the UE generates a requested NSSAI IE. First, the UE generates a requested NSSAI associated with the first PLMN to be included in the requested NSSAI IE.

[0585] If the UE stores the configured NSSAI, the requested NSSAI may be the configured NSSAI stored by the UE or a part thereof, except that the S-NSSAI included in the requested NSSAI is not the S-NSSAI included in the second pending NSSAI.

[0586] If the UE stores one or more mapped S-NSSAIs for a second pending NSSAI, and if one or more mapped S-NSSAIs included in the configured NSSAI are not included in one or more mapped S-NSSAIs for the second pending NSSAI, the S-NSSAIs included in the configured NSSAI to which the one or more mapped S-NSSAIs are associated can be included in the requested NSSAI IE together with the mapped S-NSSAIs.

[0587] UE_A10 may include the requested NSSAI IE configured in the above manner in a registration request message. UE_A10 sends the registration request message to the core network.

[0588] When the core network receives a requested NSSAI IE containing an S-NSSAI that requires an NSSAI, it generates a pending NSSAI IE and includes it in the registration accept message.

[0589] The core network generates a pending NSSAI IE based on the reception of the first identity, and the pending NSSAI IE may include one or more S-NSSAIs configured as the second pending NSSAI and the mapped S-NSSAI.

[0590] Alternatively, if the core network does not have the capability to manage a second pending NSSAI, the pending NSSAI IE may include one or more S-NSSAIs configured as the first pending NSSAI.

[0591] When the core network sends a pending NSSAI IE including one or more S-NSSAIs configured as the second pending NSSAI and a mapped S-NSSAI, the core network may include the tenth identification information in the registration accept message.

[0592] Next, the UE receives a registration accept message from the core network, the registration accept message including an Allowed NSSAI IE and / or a rejected NSSAI IE or an Extended rejected NSSAI IE and / or a pending NSSAI IE. Further, tenth identity information may be included in the registration accept message.

[0593] The UE may appropriately store the received pending NSSAI based on whether the received pending NSSAI IE includes a mapped S-NSSAI or based on the tenth identification information.

[0594] As a result, UE_A10 can select and request an appropriate S-NSSAI and mapped S-NSSAI when roaming, and further store the NSSAI appropriately.

[0595] 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.

[0596] 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 loaded into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

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

[0598] The present invention is not limited to the above-described embodiment. Although one example of a device has been described in the embodiment, 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 for AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0599] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications 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 substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0600] 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), A storage unit and a control unit are provided, The storage unit stores a configured NSSAI (Network Slice Selection Assistance Information) for a current PLMN, one or more mapped S-NSSAIs (Single Network Slice Selection Assistance Information) for the configured NSSAI, and a pending NSSAI; When the UE is roaming, the control unit Included in the configured NSSAI; and A second S-NSSAI to which the first S-NSSAI included in the pending NSSAI is mapped, The requested NSSAI will not be included as an S-NSSAI for the current PLMN or SNPN. When the UE is not roaming, the control unit Included in the configured NSSAI; and The first S-NSSAI included in the pending NSSAI, Not to be included in the requested NSSAI, The UE is characterized by:

2. If the UE is roaming, and If there are one or more first mapped S-NSSAIs included in the one or more mapped S-NSSAIs for the configured NSSAI that are not included in the pending NSSAI, The control unit Include an S-NSSAI included in the configured NSSAI associated with the first mapped S-NSSAI in the requested NSSAI together with the first mapped S-NSSAI; The UE according to claim 1 , characterized in that:

Images