UE (User Equipment) and communication control method

Abstract

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

Description

[Technical field]

[0001] The present invention relates to a UE (User Equipment) and communication control methods, etc. Regarding. [Background technology]

[0002] 3GPP (3rd Generation Partnership Project), which is involved in the standardization of recent mobile communication systems, is currently studying SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution).

[0003] In recent years, 3GPP has also been studying next-generation communication technologies and system architectures for 5G (5th Generation) mobile communication systems, and in particular has been working on the specification of 5GS (5G System) as a system for realizing the 5G mobile communication system (see Non-Patent Documents 1 and 2). In 5GS, technical issues for connecting a wide variety of terminals to a cellular network are being extracted and solutions are being specified. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 24.501 V17.0.0 (2020-9); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) [Non-Patent Document 2] 3GPP TR 23.700-40 V1.1.0 (2020-10); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of network slicing; Phase 2 (Release 17) Summary of the Invention [Problem to be solved by the invention]

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

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

[0007] 3GPP is also 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] However, a practical method for meeting the above requirements is not clear.

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

[0010] In one embodiment of the present invention, a UE (User Equipment) includes a transceiver unit and a storage unit, and the transceiver unit receives a first rejected NSSAI (Network Slice Selection Assistance Information) from a core network, and the storage unit stores an S-NSSAI included in the first rejected NSSAI in a list of a second rejected NSSAI or a list of a mapped S-NSSAI of the rejected NSSAI based on a reason value associated with the S-NSSAI, and stores the S-NSSAI in a list of a second rejected NSSAI or a mapped S-NSSAI of the rejected NSSAI based on a reason value associated with the S-NSSAI, and when the UE is not roaming, or when a mapped S-NSSAI of the S-NSSAI included in a Pending NSSAI stored by the UE is not stored in the UE, or when one or more mapped S-NSSAIs of the S-NSSAI included in a Pending NSSAI stored by the UE are stored in the UE and all of the mapped S-NSSAIs are included in the list of mapped S-NSSAI of the rejected NSSAI, or when a mapped S-NSSAI of the rejected NSSAI is not stored in the UE, When the list of S-NSSAI is not stored, the S-NSSAI is deleted from the stored Pending NSSAI.

[0011] In one embodiment of the present invention, a UE (User Equipment) is provided with a transceiver unit and a memory unit, and the transceiver unit receives a first rejected NSSAI (Network Slice Selection Assistance Information) from a core network, and the memory unit stores an S-NSSAI and a mapped S-NSSAI included in the first rejected NSSAI as part of a second rejected NSSAI based on a reason value associated with the S-NSSAI, and deletes the combination of the S-NSSAI and the mapped S-NSSAI from the stored Pending NSSAI. Effect of the Invention

[0012] According to the present invention, it becomes possible to support eNS in 5GS and to manage the number of UEs allowed for each slice. [Brief description of the drawings]

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

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

[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 described with abbreviated 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] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

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

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

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

[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 defined by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP Gateway function (TNGF).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0108] Also, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying an NS. S-NSSAI may be composed of only SST (Slice / Service type) or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating an expected operation of an NS in terms of functions and services. SD may be information for interpolating SST when selecting one NSI from multiple NSIs indicated by SST. S-NSSAI may be information specific to each PLMN or may be standard information common among PLMNs. Also, the network may store one or more S-NSSAIs as a default S-NSSAI in the registration information of the UE. Note that when S-NSSAI is the default S-NSSAI, if the UE does not transmit a valid S-NSSAI to the network in a registration request message, the network may provide an NS related to the UE.

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

[0110] Moreover, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. 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. The NSSAI may be information used to select an AMF. The UE may apply each NSSAI (allowed NSSAI, and / or configured NSSAI, and / or rejected NSSAI, and / or pending NSSAI, and / or first NSSAI) to the PLMN and the EPLMN.

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

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

[0113] The S-NSSAI that requires an NSSAA is an S-NSSAI that requires an NSSAA managed by a core network and / or a core network device. Furthermore, the S-NSSAI that requires an NSSAA may be an S-NSSAI other than the HPLMN, where the S-NSSAI that requires an NSSAA managed by a core network and / or a core network device is a mapped S-NSSAI.

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

[0115] A configured NSSAI is an NSSAI provided and stored in a UE. The UE may store a configured NSSAI for each PLMN. The UE may store a configured NSSAI in association with a PLMN. In this document, a configured NSSAI associated with a PLMN may be expressed as a configured NSSAI for the PLMN, a configured NSSAI of a PLMN, a configured NSSAI for a PLMN, or a configured NSSAI associated with a PLMN. A UE may store a configured NSSAI that is valid for all PLMNs without being associated with a PLMN, and such a configured NSSAI may be referred to as a "default configured NSSAI."

[0116] The configured NSSAI may be associated with multiple PLMNs, which may be EPLMNs.

[0117] The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be expressed as the configured S-NSSAI. The configured S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI. Alternatively, the S-NSSAI of the PLMN may be expressed as the "configured S-NSSAI", and the S-NSSAI with the configured S-NSSAI mapped to the HPLMN may be expressed as the "mapped S-NSSAI for the configured NSSAI for the PLMN".

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

[0119] In addition, the requested NSSAI is an NSSAI provided from the UE to the network during the registration procedure. In the registration procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI or the configured NSSAI stored by the UE. In the PDU session establishment procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI stored by the UE.

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

[0121] Also, the allowed NSSAI is information indicating one or more network slices to which the UE is permitted. In other words, the allowed NSSAI is information identifying a network slice to which the network permits the UE to connect. The allowed NSSAI may be an allowed NSSAI stored by the UE and / or the NW, or may be an allowed NSSAI transmitted from the NW to the UE.

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

[0123] Furthermore, the UE and / or NW may store and manage an allowed NSSAI associated with a PLMN as information of the UE. The allowed NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0124] In this document, an allowed NSSAI associated with a PLMN and an access type may be expressed as an allowed NSSAI for the PLMN and the access type, or an allowed NSSAI for the access type of the PLMN. An S-NSSAI included in an allowed NSSAI may be expressed as an allowed S-NSSAI. The allowed S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0125] Further, 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. The rejected NSSAI transmitted and received using the rejected NSSAI IE may be information including one or more combinations of the S-NSSAI and a rejection reason value. The rejected NSSAI transmitted and received using the extended rejected NSSAI IE may be information including one or more combinations of the S-NSSAI, the mapped S-NSSAI, and a rejection reason value during roaming.

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

[0127] Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and / or the network may store and manage the rejected NSSAI appropriately based on the rejection reason value associated with each S-NSSAI.

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

[0129] 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 a rejected S-NSSAI IE with the S-NSSAI of the current PLMN or SNPN, the mapped S-NSSAI, and a rejection reason value, and the UE may understand that the S-NSSAI of the received current PLMN or SNPN together with the received mapped S-NSSAI is rejected to be requested to the NW. On the other hand, the Rejected NSSAI IE may include a rejected S-NSSAI IE with the S-NSSAI of the current PLMN or SNPN and a rejection reason value, and the UE may understand that the S-NSSAI of the received current PLMN or SNPN is rejected to be requested to the NW.

[0130] The rejected NSSAI may be any one of the first to third rejected NSSAIs, a pending NSSAI, the first NSSAI, a list (set) of mapped S-NSSAIs of the first rejected NSSAI, a list (set) of mapped S-NSSAIs of the second rejected NSSAI, a set (list) of pending mapped S-NSSAIs, and a set (list) of mapped S-NSSAIs of the first NSSAI, or a combination thereof. The S-NSSAI included in the rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0131] The UE and / or NW may store and manage the rejected NSSAI associated with the PLMN as information of the UE. The rejected NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

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

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

[0134] When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the first 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 PLMN" and may be information indicating that the S-NSSAI associated with the rejection reason value is not available in the current PLMN or SNPN. The S-NSSAI included in the first rejected NSSAI may be expressed as the first rejected S-NSSAI.

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

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

[0137] The S-NSSAI or the first rejected NSSAI included in the first rejected NSSAI may be the S-NSSAI of the current PLMN. In other words, the S-NSSAI or the first rejected NSSAI included in the first rejected NSSAI may be associated with only the current PLMN ID or SNPN ID and may be stored and / or managed and / or transmitted / received. 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.

[0138] The second rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current registration area among the S-NSSAIs included in the requested NSSAI by the UE. The second rejected NSSAI may be a rejected NSSAI for the current registration area of ​​the 5GS, may be a mapped S-NSSAI(s) for rejected NSSAI for the current registration area, or may be an S-NSSAI included in the mapped S-NSSAI(s) for rejected NSSAI for the current registration area. The list (set) of mapped S-NSSAI of the second rejected NSSAI may be the mapped S-NSSAI(s) for rejected NSSAI for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored by the UE or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. In this case, the rejection reason value may be "S-NSSAI not available in the current registration area" and may be information indicating that the S-NSSAI associated with the reason value is not available in the current registration area. The S-NSSAI included in the second rejected NSSAI may be expressed as a second rejected S-NSSAI.

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

[0140] The S-NSSAI or the second rejected NSSAI included in the second rejected NSSAI may be the S-NSSAI of the current PLMN. In other words, the S-NSSAI or the second rejected NSSAI included in the second rejected NSSAI may be associated with only the current PLMN ID or SNPN ID and may be stored and / or managed and / or transmitted / received. 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.

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

[0142] The third rejected NSSAI may apply to the entire registered PLMN, may apply to the registered PLMN and / or the EPLMN, or may apply to all PLMNs. The third rejected NSSAI may apply to all PLMNs, which 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.

[0143] Furthermore, the UE and / or NW may treat the third rejected NSSAI and the third rejected S-NSSAI as information independent of the access type. That is, the third rejected NSSAI may be information valid for 3GPP access and non-3GPP access. The third rejected NSSAI may be an NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI. The third rejected NSSAI may be the rejected NSSAI for the failed or revoked NSSAA of 5GS, the rejected S-NSSAI for the failed or revoked NSSAA, or the S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA.

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

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

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

[0147] 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 may include the S-NSSAI of the HPLMN.

[0148] Or, even during roaming, the S-NSSAI included in the third rejected NSSAI may be the S-NSSAI of the current PLMN. In other words, the S-NSSAI included in the third 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.

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

[0150] When the first NSSAI is transmitted from the NW to the UE, the first NSSAI may be information including one or more pieces of information including at least one of an S-NSSAI, a mapped S-NSSAI, a rejection reason value, a back-off timer value, and information indicating the validity range of the back-off timer value. In this case, the rejection reason value may be "the S-NSSAI has reached the maximum number of UEs per network slice" or may be information indicating that the maximum number of UEs allowed for the S-NSSAI associated with the rejection reason value has been reached.

[0151] Here, the rejection reason value may be a rejection reason value included in the rejected NSSAI, may be flag information, or may be 5GMM cause. 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 and an SM message using the corresponding S-NSSAI or an S-NSSAI related to the mapped S-NSSAI.

[0152] Furthermore, the information indicating the validity range of the backoff timer value may be information indicating whether the backoff timer value applies to the current PLMN (Public Land Mobile Network), applies to all PLMNs, or is valid in the current registration area.

[0153] The first 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 the TAIs included in the TA list (TAI list or registration area) belong. The first NSSAI applies to all PLMNs may mean that the first NSSAI is not associated with a PLMN, or may mean that the first NSSAI is associated with a HPLMN.

[0154] If the first NSSAI is valid in the entire registered PLMN, or applies to all PLMNs, or applies to the registered PLMN and / or EPLMN, the UE and / or NW may treat the first NSSAI and the S-NSSAI included in the first NSSAI as information independent of the access type. If the first NSSAI is valid in 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 first NSSAI and the S-NSSAI included in the first NSSAI as information specific to the access type.

[0155] The first NSSAI may be an allowed NSSAI, a rejected NSSAI, a pending NSSAI, or information different from these.

[0156] When the first NSSAI is an NSSAI transmitted from the NW to the UE, the first NSSAI may be a set of a combination of the S-NSSAI and the mapped S-NSSAI.

[0157] 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 may include the S-NSSAI of the HPLMN. In this case, the third rejected NSSAI may be associated with the HPLMN and stored and / or managed in the UE and / or NW. Alternatively, the third rejected NSSAI may not be associated with a PLMN ID and may be stored and / or managed in the UE and / or NW as information common to all PLMNs.

[0158] A pending NSSAI is a collection of one or more S-NSSAIs that are pending and / or unavailable for use by the UE. A pending NSSAI may be a collection of S-NSSAIs for which the network requires network slice specific authentication and for which network slice specific authentication has not been completed.

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

[0160] When the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be information including one or more combinations of the S-NSSAI and a rejection reason value. In this case, the rejection reason value may be "NSSAA is pending for the S-NSSAI" and may be information indicating that the S-NSSAI associated with the rejection reason value is prohibited or pending from being used by the UE until the NSSAA for that S-NSSAI is completed.

[0161] If the pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI may be a set of a combination of the S-NSSAI and the mapped S-NSSAI.

[0162] The pending NSSAI may apply to the entire registered PLMN, to the registered PLMN and one or more EPLMNs of the registered PLMN, or to all PLMNs. The pending NSSAI may apply to all PLMNs, which may mean that the pending NSSAI is not associated with a PLMN, or may mean that the pending NSSAI is associated with a HPLMN.

[0163] The UE and / or NW may treat the S-NSSAI included in the pending NSSAI as information independent of the access type. In other words, the pending NSSAI may be information valid for 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may be the first rejected NSSAI.

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

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

[0166] During roaming (roaming scenario), the S-NSSAI included in the pending NSSAI may be the S-NSSAI of the HPLMN. In other words, the pending NSSAI received by the UE from the VPLMN may include the S-NSSAI of the HPLMN.

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

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

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

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

[0171] The management of the maximum number of UEs connected to a slice refers to managing the maximum number of UEs that can be registered in a network slice or an S-NSSAI at the same time. Here, the UE to be registered in the network slice or the S-NSSAI may be stored by including the 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 can store, for each S-NSSAI, whether or not the management of the maximum number of UEs connected to the slice is required, and can further check during the registration procedure whether or not the registered UEs have reached a constant number that is the maximum number. Furthermore, each device that supports the function of managing the maximum number of UEs connected to a slice may be capable of storing a first 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, or the maximum number of UEs that can be registered in the network slice or the S-NSSAI, or the maximum number of UEs, or a constant number.

[0172] The back-off timer is a timer for prohibiting the UE from transmitting an MM message and / or starting a procedure by 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 may be associated with an NSSAI. While the back-off timer associated with an S-NSSAI is valid, the UE may be in a state in which the transmission of an MM message and / or the transmission of an SM message using the S-NSSAI is prohibited, restricted, or limited. These restrictions may be restrictions based on 5GS congestion management, may include restrictions based on 5GS congestion management, or may be restrictions independent of 5GS congestion management.

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

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

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

[0176] Furthermore, the UE may configure the new PLMN to permit transmission of MM messages and / or SM messages that were prohibited in the previous PLMN during the count of this timer, based on a specific condition described below. Note that when it is expressed that transmission of MM messages and / or SM messages that were prohibited in the previous PLMN is permitted, it may mean that transmission of MM messages and / or SM messages using the same S-NSSAI as the S-NSSAI associated with the back-off timer, and / or an S-NSSAI associated with the same S-NSSAI, and / or an S-NSSAI associated with a mapped S-NSSAI of the same S-NSSAI is permitted.

[0177] 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 during the countdown of the timer.

[0178] Furthermore, the UE may configure the new PLMN to permit transmission of an MM message that was prohibited in the previous PLMN during the count of this timer, based on a specific condition described later. 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.

[0179] Also, the back-off timer may be associated with no NSSAI and may be a timer for prohibiting transmission of an MM message using no NSSAI. In other words, UE_A10 may configure this timer not to transmit an MM message using no NSSAI while it is counting. Furthermore, UE_A10 may configure this timer to be counted while it is counting, based on specific conditions described below, so that transmission of an MM message that was prohibited in the PLMN before the change is permitted in the new PLMN. Note that when it is expressed that transmission of an MM message that was prohibited in the PLMN before the change is permitted, this may mean that an MM message using no NSSAI is permitted.

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

[0181] Next, the identification information transmitted, received, stored, and managed by each device in this embodiment will be described.

[0182] The first identification information is information indicating a network slice requested by the UE. The first identification information may be information including one or more S-NSSAIs associated with the network slice requested by the UE. Note that the network slice requested by the UE may be a network slice that the UE wishes to use, or a network slice that the UE requests to be allowed to use from the network. The S-NSSAI included in the first identification information may be an S-NSSAI included in a configured NSSAI associated with the current PLMN, or an S-NSSAI included in an allowed NSSAI associated with the current PLMN.

[0183] In other words, the first identity 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 first identity may be a requested NSSAI of 5GS.

[0184] In addition, the S-NSSAI included in the first identification information may be an S-NSSAI stored by the UE and not included in a rejected NSSAI associated with the current PLMN, and / or an S-NSSAI stored by the UE and not included in a pending NSSAI associated with the current PLMN, or an S-NSSAI stored by the UE and not included in a first NSSAI associated with the current PLMN.

[0185] Also, when roaming, when the pending NSSAI, and / or the rejected NSSAI, and / or the S-NSSAI included in the first NSSAI is the S-NSSAI of the HPLMN, the S-NSSAI included in the first identification information may be the S-NSSAI of the current PLMN, where the pending NSSAI stored by the UE, and / or the rejected NSSAI, and / or the S-NSSAI included in the first NSSAI is not the mapped S-NSSAI.

[0186] Furthermore, the S-NSSAI included in the first identification information may be an S-NSSAI for which a back-off timer associated with that S-NSSAI or the mapped S-NSSAI of that S-NSSAI is not running in the UE.

[0187] The second identification information may be information indicating that the UE supports a function for managing the maximum number of UEs connected to a slice. Alternatively, the second identification information may be information indicating whether the UE supports a function for managing the maximum number of UEs connected to a slice. The second identification information may be 5G MM capability information. The second identification information may be information indicating that the UE can store.

[0188] The tenth identification information may be information indicating that the S-NSSAI has reached the maximum number of UEs that can be registered in the network slice or the S-NSSAI. The tenth identification information may be included in an allowed NSSAI transmitted from the network, may be included in a rejected NSSAI transmitted from the network, may be included in a pending NSSAI transmitted from the network, or may be transmitted from the network as information different from these.

[0189] Furthermore, the tenth identification information may be an NSSAI. Furthermore, the tenth identification information may be an allowed NSSAI or a rejected NSSAI. Furthermore, the tenth identification information may be a pending NSSAI or an NSSAI different from these.

[0190] The tenth identification information may be the first NSSAI or an S-NSSAI included in the first NSSAI. The tenth identification information may be configured to include at least one of the eleventh to sixteenth identification information. Specifically, the tenth identification information may include at least one of an S-NSSAI that has reached the maximum number of UEs that can be registered in the network slice or the S-NSSAI, a mapped S-NSSAI of the S-NSSAI, a reason value indicating that the maximum number of UEs that can be registered in the network slice or the S-NSSAI has been reached, a value of a back-off timer indicating a period during which the UE is prohibited from transmitting a registration request message using the S-NSSAI, and information indicating a valid range of the back-off timer.

[0191] Furthermore, the tenth identification information may be configured to include at least one or more pieces of information among a reason value indicating that the maximum number of UEs that can be registered in the network slice has been reached, a back-off timer value indicating a period during which transmission of a registration request message using no NSSAI is prohibited, and information indicating a valid range of the back-off timer. Note that the reason value indicating that the maximum number of UEs that can be registered in the network slice has been reached, the back-off timer value indicating a period during which transmission of a registration request message using no NSSAI is prohibited, and information indicating a valid range of the back-off timer may not be included in the tenth identification information and may be transmitted and received separately. Here, when the tenth identification information is included in the rejected NSSAI, the reason value included in the tenth identification information may be a rejection reason value.

[0192] The eleventh identification information may be information and / or a reason value indicating from the network to the UE that the maximum number of UEs that can be registered in the network slice or the S-NSSAI has been reached. The eleventh identification information may be information and / or a reason value indicating that the use of the S-NSSAI is rejected or restricted because the maximum number of UEs connected per slice has been reached. In other words, the eleventh identification information is information and a reason value indicating that the UE has been rejected or restricted from using the S-NSSAI by the network because the maximum number of UEs connected per slice has been reached.

[0193] The eleventh identification information may be included in the tenth identification information, and may be associated with the S-NSSAI indicated in the fourteenth identification information and / or the mapped S-NSSAI indicated in the fifteenth identification information included in the same tenth identification information. The eleventh identification information may be associated with each identification information included in the same tenth identification information. When the eleventh identification information is included in the rejected NSSAI, the eleventh identification information may be a rejection reason value. The eleventh identification information may be flag information.

[0194] Furthermore, the eleventh identification information may be a reason value indicating that connection to the slice is restricted and / or not permitted. Further, the eleventh identification information may be a reason value indicating that registration to the slice is restricted and / or not permitted.

[0195] Furthermore, the eleventh identification information may be a 5G Mobility Management (5GMM) cause. Furthermore, the eleventh identification information may be a 22nd 5GMM cause. Here, the 22nd 5GMM cause may be a reason value indicating congestion. Furthermore, the 22nd 5GMM cause may be information transmitted to the UE due to network congestion.

[0196] Furthermore, the 11th identification information may be a 5GMM cause other than the 22nd 5GMM cause. For example, the 11th identification information may be information transmitted to the UE due to congestion in a network slice. Furthermore, the 11th identification information may be information transmitted to the UE due to a lack of resources in a network slice. Furthermore, the 11th identification information may be a reason value indicating that the requested service cannot be provided due to insufficient resources for a particular slice.

[0197] The twelfth identification information may be a value of a back-off timer. Specifically, the twelfth identification information may be information indicating a period during which the network prohibits the UE from transmitting an MM message using the S-NSSAI indicated in the fourteenth identification information and / or the fifteenth identification information included in the same ten identification information, or from transmitting an SM message other than a PDU connection release request message. In other words, the twelfth identification information may be information indicating a period during which the network prohibits the UE from transmitting a registration request message using the S-NSSAI indicated in the fourteenth identification information and / or the fifteenth identification information included in the same ten identification information.

[0198] The 12th identity may be included in the 10th identity and may be associated with the S-NSSAI indicated in the 14th identity included in the same 10th identity and / or the mapped S-NSSAI indicated in the 15th identity. The 12th identity may be associated with each identity included in the same 10th identity.

[0199] The twelfth identification information may be information included in the MM message, independent of the tenth identification information. The twelfth identification information may be associated with multiple S-NSSAIs. Specifically, when multiple tenth identification information are included in the same MM message including the twelfth identification information, the value of the back-off timer included in the twelfth identification information may be associated with each S-NSSAI included in the multiple tenth identification information.

[0200] The thirteenth identification information is information indicating a valid range of a back-off timer. Specifically, the thirteenth identification information may be information indicating a valid range of a back-off timer counted by the UE using a value of the corresponding back-off timer. More specifically, the thirteenth identification information may be information indicating that the corresponding back-off timer applies to a current PLMN (a PLMN requested by the UE or an RPLMN) or applies to all PLMNs. Additionally, or the thirteenth identification information may be information indicating that the corresponding back-off timer applies to a current registration area.

[0201] The thirteenth identification information may be information indicating a restriction range, or information indicating a range to which the restriction is applied. The restriction may be a restriction based on congestion management. More specifically, the restriction may limit transmission of an MM message by the UE. Furthermore, the restriction may be realized by a back-off timer.

[0202] The thirteenth identity may be information indicating whether the S-NSSAI included in the same ten identities is an S-NSSAI of the HPLMN or an S-NSSAI of the current PLMN. Specifically, the thirteenth identity may be information indicating that the same ten identities include a fourteenth identity, or may be information indicating that the same ten identities include a fifteenth identity. The thirteenth identity may be included in the tenth identity, and in that case, the value of the corresponding back-off timer may be a value indicated by the twelfth identity included in the same tenth identity. Furthermore, in that case, the thirteenth identity may be associated with each identity included in the same tenth identity.

[0203] The fourteenth identification information is information indicating an S-NSSAI that has reached the maximum number of UEs that can be registered per S-NSSAI. The fourteenth identification information may be an S-NSSAI included in the tenth identification information, and may be associated with a mapped S-NSSAI indicated in a fifteenth identification information included in the same tenth identification information. The fourteenth identification information may be associated with each identification information included in the same tenth identification information. Furthermore, the fourteenth identification information may be an S-NSSAI.

[0204] The 15th identity is the S-NSSAI of the HPLMN associated with the corresponding S-NSSAI. Specifically, when the current PLMN (current PLMN, or the PLMN requested by the UE, or the RPLMN, the PLMN selected by the UE) is not the HPLMN, the 15th identity may be information indicating the S-NSSAI of the HPLMN mapped to the S-NSSAI of the current PLMN. The 15th identity may be the mapped S-NSSAI.

[0205] The 15th identification information may be a mapped S-NSSAI included in the 10th identification information, and may be associated with an S-NSSAI indicated in a 14th identification information included in the same 10th identification information, in which case it may be a mapped S-NSSAI of the S-NSSAI indicated in the 14th identification information. The 15th identification information may be associated with each identification information included in the same 10th identification information. Furthermore, the 15th identification information may be a mapped S-NSSAI of the S-NSSAI indicated by the 14th identification information.

[0206] The 16th identification information is information indicating the validity range of the S-NSSAI and the mapped S-NSSAI of the current PLMN included in the rejected S-NSSAI included in the rejected NSSAI. Specifically, the 16th identification information may indicate that the entire S-NSSAI of the current PLMN of the related rejected S-NSSAI has been rejected, may indicate that only the combination of the S-NSSAI of the current PLMN of the related rejected S-NSSAI and the mapped S-NSSAI has been rejected, or may indicate that the entire mapped S-NSSAI of the related rejected S-NSSAI has been rejected.

[0207] In other words, when the UE receives the 16th identification information associated with the combination of S-NSSAI#1 and mapped S-NSSAI#a included in the Extended rejected NSSAI IE and "indicates that the entire S-NSSAI of the current PLMN of the associated rejected S-NSSAI has been rejected," it may be understood that the S-NSSAI#1 of the current PLMN has been rejected even in combination with other mapped S-NSSAIs.

[0208] Alternatively, the 16th identification information may be information instructing the relevant S-NSSAI to be deleted from the Allowed NSSAI, Pending NSSAI, or Rejected NSSAI, or information instructing not to delete it.

[0209] Similarly, when the UE receives the 16th identification information associated with the combination of S-NSSAI#1 and mapped S-NSSAI#a included in the Extended rejected NSSAI IE and "indicates that the entire mapped S-NSSAI of the associated rejected S-NSSAI has been rejected," it may be understood that the combination of S-NSSAI#1 and mapped S-NSSAI#a has been rejected. In other words, it may be understood that the UE has not been rejected from using S-NSSAI(s) other than the combination of S-NSSAI#1 and mapped S-NSSAI#a.

[0210] Similarly, when the UE receives a 16th identification information associated with the combination of S-NSSAI#1 and mapped S-NSSAI#a included in the Extended rejected NSSAI IE and "indicates that the entire mapped S-NSSAI of the associated rejected S-NSSAI has been rejected," it may be understood that the mapped S-NSSAI#a has been rejected.

[0211] The 16th identification information may be included in the Extended rejected NSSAI IE. Alternatively, a specific S-NSSAI or a mapped S-NSSAI may be transmitted in the rejected S-NSSAI IE included in the Extended rejected NSSAI IE to indicate that the entire S-NSSAI of the current PLMN or SNPN is rejected, or that the entire mapped S-NSSAI is rejected. Specifically, the 16th identification information may be a first indication for the NW to restrict the deletion of an Allowed NSSAI based on a rejected NSSAI or to cause the UE to restrict the deletion of a rejected NSSAI based on an Allowed NSSAI, or a second indication for the NW to cause the UE to delete an Allowed NSSAI based on a rejected NSSAI or to delete a rejected NSSAI based on an Allowed NSSAI.

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

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

[0214] [3.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 6. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering to the access network_B, and / or the core network_B, and / or the DN. If the UE is not registered to the network, it can execute this procedure at any timing, such as when the power is turned on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), it can start this procedure at any timing. Furthermore, each device (particularly the UE and the AMF) can transition to a registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. Note that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or non-registered state) for 3GPP access and the registration state for non-3GPP access.

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

[0216] The UE may start the registration procedure when the UE performs mobility across TAs (tracking areas). In other words, the UE may start the registration procedure when the UE moves to a TA different from the TA indicated in the TA list (TAI list or registration area) held by the UE. Furthermore, the UE may start this procedure when a back-off timer or other timer that is being executed expires. Furthermore, the UE may start the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may start the registration procedure when a change occurs in the capability information and / or preferences regarding the establishment of a PDU session of the UE. Furthermore, the UE may start the registration procedure periodically. Furthermore, the UE may start the registration procedure based on the completion of a UE configuration update procedure, based on the completion of a registration procedure, based on the completion of a PDU session establishment procedure, based on the completion of a PDU session management procedure, based on information received from the network in each procedure, or based on the expiration or stop of a back-off timer. It should be noted that the UE can execute the registration procedure at any timing, not limited to these.

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

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

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

[0220] Here, UE_A10 can transmit at least one or more of the first and second identification information in a registration request message and / or an RRC message. Furthermore, UE_A10 can transmit the registration request message and / or the RRC message including identification information indicating the type of the procedure. Here, the identification information indicating the type of the procedure may be a 5GS registration type IE, and may be information indicating that the procedure is a registration procedure for initial registration, for updating registration information associated with movement, for periodic updating of registration information, or for emergency registration.

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

[0222] UE_A10 may transmit these identification information 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, 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 to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

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

[0224] UE_A10 may transmit the second identification information when it has a function for managing the maximum number of UEs connecting to the slice or when it requests at least one S-NSSAI that requires management for managing the maximum number of UEs connecting to the slice. UE_A10 may notify the network that it has a function for storing the first NSSAI by transmitting the second identification information.

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

[0226] If the UE stores an "allowed NSSAI associated with the UE requested PLMN and the UE requested access type" and / or stores a "configured NSSAI for the requested PLMN" and / or stores a "default configured NSSAI", the UE may include the first identification information in a registration request message and send it to the requested PLMN.

[0227] Alternatively, when the UE stores "an allowed NSSAI associated with a PLMN other than the PLMN requested by the UE and an access type requested by the UE," 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 requested by the UE, the UE may include the first identification information in a registration request message and send it to the requested PLMN.

[0228] The UE_A10 may determine information included in the first identity 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 and the requested access type, and / or a configured NSSAI associated with the requested PLMN, and / or a default configured NSSAI, and / or a rejected NSSAI associated with the requested PLMN. Further / or, the one or more NSSAIs stored by the UE may be a pending NSSAI, and / or a first NSSAI, or a rejected NSSAI not associated with the requested PLMN.

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

[0230] The UE may select one or more S-NSSAIs from the allowed NSSAIs and / or configured NSSAIs it stores, and transmit them in the first identification information.

[0231] Specifically, if UE_A10 stores an allowed NSSAI associated with the requested PLMN and the requested access type, UE_A10 may transmit the first identification information including that allowed NSSAI or one or more S-NSSAIs included in that allowed NSSAI.

[0232] Further / or, if UE_A10 stores a configured NSSAI associated with the requested PLMN, UE_A10 may send the first identification information including that configured NSSAI or one or more S-NSSAIs included in that configured NSSAI.

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

[0234] In other words, UE_A10 may include in the first identification information an "S-NSSAI included in an allowed NSSAI associated with a PLMN other than the requested PLMN and a registration area" stored by the UE or an "S-NSSAI associated with a registration area included in an allowed NSSAI associated with a PLMN other than the requested PLMN," and at least one TAI included in this registration area may belong to the first PLMN.

[0235] The first identification information 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 first identification information so that they do not overlap.

[0236] Furthermore, when UE_A10 stores a rejected NSSAI for the requested PLMN, UE_A10 may transmit the S-NSSAI included in the rejected NSSAI without including it in the first identification information.

[0237] Specifically, when UE_A10 stores a "first rejected NSSAI associated with the requested PLMN," UE_A10 may transmit the S-NSSAI included in the first rejected NSSAI without including it in the first identification information. In other words, UE_A10 may perform control such that one or more S-NSSAIs included in the first identification information are no longer S-NSSAIs included in the "first rejected NSSAI associated with the requested PLMN" stored by the UE.

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

[0239] 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, the one or more different PLMNs are EPLMNs of the requested PLMN, and UE_A10 may perform control so that one or more S-NSSAIs included in the first identification information are not S-NSSAIs included in each of the "second rejected NSSAIs associated with one of the one or more different PLMNs and the current registration area" stored by UE_A10.

[0240] In other words, 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, UE_A10 does not need to include an S-NSSAI included in each "second rejected NSSAI associated with one of the different PLMN or PLMNs and the current registration area" in the first identification information.

[0241] 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 first identification information. In other words, UE_A10 may control one or more S-NSSAIs included in the first identification information to be no longer the S-NSSAIs included in the "third rejected NSSAI associated with the requested PLMN" stored by UE_A10.

[0242] Furthermore, when UE_A10 stores at least one "third rejected NSSAI associated with the EPLMN of the requested PLMN," UE_A10 may transmit the S-NSSAI included in the third rejected NSSAI without including it in the first identification information. In other words, UE_A10 may control one or more S-NSSAIs included in the first identification information to be no longer an S-NSSAI included in each "third rejected NSSAI associated with the EPLMN of the requested PLMN" stored by UE_A10.

[0243] Furthermore, when UE_A10 stores a "third rejected NSSAI valid for all PLMNs", UE_A10 may transmit an S-NSSAI included in the third rejected NSSAI, or an S-NSSAI to which the S-NSSAI is mapped, or an S-NSSAI associated with the S-NSSAI, or a mapped S-NSSAI of the S-NSSAI without including it in the first identification information. In other words, UE_A10 may control one or more S-NSSAIs included in the first identification information to be no longer an S-NSSAI included in each "third rejected NSSAI valid for all PLMNs" stored by UE_A10, or an S-NSSAI to which the S-NSSAI is mapped, or an S-NSSAI associated with the S-NSSAI, or a mapped S-NSSAI of the S-NSSAI. In addition, the "third rejected NSSAI valid for all PLMNs" may mean a third rejected NSSAI that is not associated with a PLMN, or may mean a third rejected NSSAI that is associated with a HPLMN.

[0244] Furthermore, when the UE stores a "pending NSSAI associated with the requested PLMN", the UE may transmit an S-NSSAI included in the pending NSSAI without including it in the first identification information. In other words, the UE may control one or more S-NSSAIs included in the first identification information to be different from the S-NSSAIs included in the "pending NSSAI associated with the requested PLMN" stored by the UE.

[0245] Furthermore, when the UE stores at least one "pending NSSAI associated with the EPLMN of the requesting PLMN," the UE may transmit an S-NSSAI included in the pending NSSAI without including it in the first identification information. In other words, the UE may control one or more S-NSSAIs included in the first identification information to be not S-NSSAIs included in each "pending NSSAI associated with the EPLMN of the requesting PLMN."

[0246] Furthermore, when the UE stores a "pending NSSAI valid for all PLMNs", the UE may transmit an S-NSSAI included in the pending NSSAI, an S-NSSAI to which the S-NSSAI is mapped, an S-NSSAI associated with the S-NSSAI, or a mapped S-NSSAI of the S-NSSAI without including it in the first identification information. In other words, the UE may control one or more S-NSSAIs included in the first identification information to be not an S-NSSAI included in each "pending NSSAI valid for all PLMNs", an S-NSSAI to which the S-NSSAI is mapped, an S-NSSAI associated with the S-NSSAI, or a mapped S-NSSAI of the S-NSSAI. Note that the "pending NSSAI valid for all PLMNs" may mean a pending NSSAI not associated with a PLMN, or a pending NSSAI associated with a HPLMN.

[0247] Furthermore, when a back-off timer associated with a certain S-NSSAI is valid, in other words, when the back-off timer is running or until the back-off timer is stopped, UE_A10 may transmit the S-NSSAI or an S-NSSAI related to the S-NSSAI without including it in the first identification information. Specifically, when the S-NSSAI to which the back-off timer is associated 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 first identification information while the back-off timer is counting or until the back-off timer expires or is stopped.

[0248] Alternatively, if the S-NSSAI to which the back-off 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 first identification information. Note that the S-NSSAI to which the back-off timer is associated is associated with the HPLMN may mean that the back-off timer is valid for all PLMNs, or may mean that the back-off timer is not associated with the PLMN.

[0249] Furthermore, when the UE stores a "first NSSAI associated with the requested PLMN", the UE may transmit an S-NSSAI included in the first NSSAI without including it in the first identification information. In other words, the UE may control one or more S-NSSAIs included in the first identification information to be different from the S-NSSAIs included in the "first NSSAI associated with the requested PLMN" stored by the UE.

[0250] Furthermore, when the UE stores at least one "first NSSAI associated with the EPLMN of the requesting PLMN," the UE may transmit the S-NSSAI included in the first NSSAI without including it in the first identification information. In other words, the UE may control one or more S-NSSAIs included in the first identification information to be different from the S-NSSAIs included in each "first NSSAI associated with the EPLMN of the requesting PLMN."

[0251] Furthermore, when the UE stores a "first NSSAI valid for all PLMNs", the UE may transmit an S-NSSAI included in the first NSSAI or an S-NSSAI to which the S-NSSAI is mapped without including it in the first identification information. In other words, the UE may control one or more S-NSSAIs included in the first identification information to be different from the S-NSSAI included in each "first NSSAI valid for all PLMNs" or the S-NSSAI to which the S-NSSAI is mapped. Note that the "first NSSAI valid for all PLMNs" may mean a first NSSAI that is not associated with a PLMN, or may mean a first NSSAI that is associated with a HPLMN.

[0252] During roaming, when the rejected NSSAI and / or pending NSSAI and / or first NSSAI include the S-NSSAI of the HPLMN, UE_A10 may control one or more S-NSSAIs included in the first identification information not to include the rejected NSSAI and / or pending NSSAI and / or the S-NSSAI of the HPLMN included in the first NSSAI stored by UE_A10 as a mapped S-NSSAI. In other words, UE_A10 may control not to include the S-NSSAI of the current PLMN to which the rejected NSSAI and / or pending NSSAI and / or the S-NSSAI included in the first NSSAI are mapped in the first identification information.

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

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

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

[0256] When the 5G AN 120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S602). 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 the new AMF 141 to which the registration request message is to be transmitted based on at least one of the first and second identification information.

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

[0258] 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 a slice and / or an AMF having connectivity to a network having functionality for managing the maximum number of UEs connecting to a slice.

[0259] The method of selecting an AMF is not limited to this, and the 5G AN (or gNB) may select an AMF based on other conditions. The 5G AN (or gNB) extracts a registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). 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).

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

[0261] Alternatively, the new AMF 141 may perform the first condition determination after requesting the UE context from the old AMF 142 and receiving the UE context from the old AMF 142 (S606, S608). In this case, the new AMF 141 may execute S610 and / or S612 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.

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

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

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

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

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

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

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

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

[0270] 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 first NSSAI. Furthermore, the allowed NSSAI, and / or the configured NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first 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.

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

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

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

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

[0275] The new AMF 141 may include one or more tenth identification information in a control message and transmit the same. Alternatively, the new AMF 141 may include one or more of the tenth to sixteenth identification information in a control message and transmit the same. By transmitting the identification information and / or the control message, the new AMF 141 may indicate that the network supports each function, may indicate that the UE's request has been accepted, may indicate that the request from the UE has not been permitted, or may indicate a combination of these. 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. 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.

[0276] When new AMF 141 receives the first identification information and / or the second identification information from the UE, it may transmit at least one of the tenth to sixteenth identification information in a control message.

[0277] Furthermore, the new AMF 141 may transmit at least one of the tenth to sixteenth identification information when the UE's configuration information is updated.

[0278] The new AMF 141 may further include the configured NSSAI, and / or the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first NSSAI in a control message and transmit it to UE_A10. Note that the message transmitted by the new AMF 141 to the UE may be based on information received from the UE. Specifically, the S-NSSAI included in the rejected NSSAI transmitted by the new AMF 141 to the UE may be the S-NSSAI included in the first identification information received from the UE.

[0279] In addition, the tenth to sixteenth identification information may be included in the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first NSSAI and transmitted, or may be these NSSAIs.

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

[0281] When transmitting a control message, new AMF141 does not permit the UE to have an S-NSSAI (allowed NSSAI), but if the 10th identification information is included in the control message, or if the UE has been notified of the first NSSAI prior to this procedure, new AMF141 may transmit an empty value in the allowed NSSAI.

[0282] When the new AMF 141 includes the 13th identification information, which indicates that the new AMF 141 applies to all PLMNs, in a control message, the new AMF 141 may also include the 15th identification information in the control message.

[0283] When the new AMF 141 includes the rejected NSSAI in the control message using the Extended rejected NSSAI IE, the new AMF 141 may include the 16th identity information in the control message and transmit it. Alternatively, the new AMF 141 may include the 16th identity information in the Extended rejected NSSAI IE and transmit it.

[0284] UE_A10 receives the control message and / or one or more pieces of information among the 10th to 16th identification information from the network. More specifically, the UE receives the control message and / or one or more pieces of information among the 10th to 16th identification information from the new AMF141.

[0285] UE_A10 may recognize the received information based on receiving at least one of identification information 10 to 16. Specifically, the UE may store and / or update information related to the NSSAI and start and / or stop a back-off timer, as described in detail in the NSSAI update procedure in Chapter 3.5.

[0286] UE_A10 may recognize that the maximum number of UEs connected per slice has been reached, and therefore transmission of MM messages and / or transmission of SM messages using the S-NSSAI indicated by the 10th identification information, and / or the S-NSSAI indicated by the 14th identification information, and / or the S-NSSAI related to the mapped S-NSSAI indicated by the 16th identification information is temporarily prohibited. Note that here, the MM procedure may be a registration request message, and the SM message may be a PDU session establishment request message.

[0287] 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 procedure in Chapter 3.5.

[0288] In addition, the NSSAI update procedure in Chapter 3.5 may be performed during this procedure, or after completion of this procedure, or after completion of this procedure, based on the completion of this procedure.

[0289] Furthermore, the AMF may select and determine which of the 10th to 16th identification information to include in the control message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0304] [3.2. Network Slice-Specific Authentication and Authorization Procedures] Next, the Network Slice-Specific Authentication and Authorization (NSSAA) procedure will be described with reference to FIG. 7. Hereinafter, the NSSAA procedure will also be referred to as this procedure. This procedure may be a procedure in which the core network executes authentication and authorization procedures of the UE for a slice that requires the NSSAA procedure. Here, the authentication procedure and authorization procedure may be a re-authentication procedure and a re-authorization procedure.

[0305] This procedure is a procedure performed by the PLMN and may be performed for each S-NSSAI (mapped S-NSSAI) and / or for each UE that is the subject of the NSSAA procedure. This procedure may be performed after the registration procedure is completed.

[0306] This procedure may be initiated by AMF140. For example, AMF140 may initiate this procedure based on receiving a registration request message from UE_A10. AMF140 may initiate this procedure when it stores at least one S-NSSAI or a mapped S-NSSAI of the S-NSSAI requested by UE_A10 as an S-NSSAI requiring an NSSAA procedure, and does not store the result of the NSSAA of the S-NSSAI. Here, the result of the NSSAA may be information indicating that the NSSAA is successful, information indicating that the NSSAA is unsuccessful, or both. Furthermore, the information indicating that the NSSAA is successful may be an allowed NSSAI. In other words, when the S-NSSAI is stored as an allowed NSSAI, AMF140 may recognize that the NSSAA of the S-NSSAI is successful, and may retain the result of the NSSAA.

[0307] Alternatively, AMF 140 may initiate this procedure based on a request from AAA-S 181. For example, when AMF 140 and / or NW manage a certain S-NSSAI as an allowed NSSAI based on the result of an already executed NSSAA procedure, and AAA-S 181 requests execution of NSSAA for the S-NSSAI again, AMF may initiate this procedure based on a request from AAA-S 181. In this case, this procedure may be an NSSAA procedure initiated by the AAA-S.

[0308] This procedure will be described below. The AMF 140 transmits an EAP ID request message to the UE_A10 via a 5G AN (or a gNB or a non-3GPP access) (S700). The EAP ID request message may be transmitted in an authentication request message that is a NAS message, or may be an authentication request message that is a NAS message. The authentication request message that is a NAS message may be a NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message of 5GS. The AMF 140 transmits the EAP ID request message or an authentication request message that includes the EAP ID request message, including one or more S-NSSAIs corresponding to the EAP ID request message. Here, the S-NSSAI may be an S-NSSAI of the HPLMN or a mapped S-NSSAI.

[0309] Based on the transmission of the EAP ID request message, AMF140 requests from UE_A10 one or more EAP IDs as UE identification information to be used for performing NSSAA for one or more S-NSSAIs.

[0310] Based on the reception of the EAP ID request message, and / or the reception of the S-NSSAI, and / or the reception of the authentication request message, the UE_A10 transmits an EAP ID response message to the AMF140 (S702). The EAP ID response message may be transmitted by being included in an authentication response message, which is a NAS message, or may be an authentication response message, which is a NAS message. The authentication response message, which is a NAS message, may be a 5GS NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message. The UE_A10 may transmit the EAP ID response message or the authentication request message including the EAP ID response message by including the S-NSSAI received from the AMF140. The UE_A10 may transmit the EAP ID response message by including the EAP ID, which is the identification information of the UE corresponding to the S-NSSAI received from the AMF140. In addition, UE_A10 may include multiple EAP IDs and multiple S-NSSAIs in the EAP ID response message, and each EAP ID and each S-NSSAI may be associated and transmitted.

[0311] Based on receiving an authentication response message, which is an EAP ID response message and / or an EAP ID and / or a NAS message, from UE_A10, AMF140 transmits an NSSAA authentication request message to AAA-S181 via AUSF180 (S704, S706). AM140F may include the EAP ID response message received from UE_A10 in an NSSAA authentication request message and transmit it to AUSF180 and / or AAA-S181, or may include the EAP ID and / or S-NSSAI included in the EAP ID response message received from UE_A10 in an NSSAA authentication request message and transmit it to AUSF180 and / or AAA-S181.

[0312] Note that the NSSAA authentication request message transmitted from the AMF 140 to the AUSF 180 and the NSSAA authentication request message transmitted from the AUSF 180 to the AAA-S 181 may be the same message or different messages. Specifically, the AUSF 180 may transfer the NSSAA authentication request message received from the AMF 140 to the AAA-S 181, or may include the EAP ID and / or S-NSSAI included in the authentication request message received from the AMF 140 in the NSSAA authentication request message and transmit it to the AAA-S 181.

[0313] Based on receiving the NSSAA authentication request message and / or at least one piece of information included in the NSSAA authentication request message, the AAA-S181 may start a procedure for exchanging messages required for authentication between the UE_A10 and the AAA-S181 (S708). Note that the message used in the message exchange procedure between the AAA-S181 and the UE_A10 may be an EAP message.

[0314] Next, the AAA-S 181 transmits an NSSAA authentication response message to the AMF 140 via the AUSF 180 in response to the authentication request message received from the AMF 140 (S710, S712).

[0315] In addition, the NSSAA authentication response message transmitted from the AAA-S 181 to the AUSF 180 and the NSSAA authentication response message transmitted from the AUSF 180 to the AMF 140 may be the same message or may be different messages. Specifically, the AUSF 180 may transfer the NSSAA authentication response message received from the AAA-S 181 to the AAA-S 181, or may include the message in the NSSAA authentication response message and transmit it to the AMF 140 based on the authentication result and / or S-NSSAI included in the authentication response message received from the AAA-S 181.

[0316] The AUSF 180 transmits an NSSAA authentication response message including the authentication result and the S-NSSAI. Here, the authentication result may be information indicating success or failure. Here, the S-NSSAI included in the NSSAA authentication response message may be the S-NSSAI of the HPLMN or the mapped S-NSSAI.

[0317] Based on the reception of the NSSAA authentication response message, AMF 140 transmits an authentication result message to UE_A 10 (S714). AMF 140 may transmit the authentication result message including the NSSAA authentication response message or the authentication result and S-NSSAI contained in the NSSAA authentication response message.

[0318] The authentication result message may be a 5GS NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message or may be transmitted in a NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message.

[0319] Each device may complete this procedure based on the transmission and reception of the authentication result message. Each device may update the stored information based on the information transmitted and received in this procedure based on the completion of this procedure. Specifically, the AMF 140 and / or the NW may store the authentication result for each S-NSSAI based on the transmission and reception of the authentication result. For example, when the AMF 140 and / or the NW transmits and receives "success" as the authentication result, the AMF 140 and / or the NW may store the authentication result as information of the UE in which the NSSAA is "successful" in association with the S-NSSAI transmitted and received together with the authentication result. Similarly, when the AMF 140 and / or the NW transmits and receives "failure" as the authentication result, the AMF 140 and / or the NW may store the authentication result as information of the UE in which the NSSAA is "failed" in association with the S-NSSAI transmitted and received together with the authentication result.

[0320] Also, when this procedure is initiated based on receiving a registration request message from UE_A10, AMF140 may update the allowed NSSAI and / or rejected NSSAI for the UE based on transmitting and receiving the authentication result. Specifically, for example, when AMF140 transmits or receives "success" as the authentication result, AMF140 may include the S-NSSAI transmitted or received together with the authentication result in the allowed NSSAI, or may store it as a mapped S-NSSAI of the S-NSSAI included in the allowed NSSAI, or may associate "allowed" with the received S-NSSAI and store it. Similarly, when AMF140 transmits or receives "failure" as the authentication result, AMF140 may store the S-NSSAI transmitted or received together with the authentication result as a third rejected NSSAI, or may store it as a mapped S-NSSAI of the S-NSSAI included in the third rejected NSSAI, or may associate "rejected" with the received S-NSSAI and store it. Furthermore, if the AMF sends or receives "Failure" or "Success" as the authentication result, and if UE_A10 has included the S-NSSAI sent or received along with the authentication result in the pending NSSAI or stored it as a mapped S-NSSAI of the S-NSSAI included in the pending NSSAI, UE_A10 may delete the S-NSSAI from the pending NSSAI or delete the S-NSSAI associated with the S-NSSAI from the pending NSSAI.

[0321] Furthermore, the UE may store the authentication result for each S-NSSAI based on the transmission and reception of the authentication result. Specifically, for example, when the UE transmits or receives "success" as the authentication result, the UE may associate the authentication result with the S-NSSAI transmitted or received together with the authentication result and store the result as information about the UE indicating that the NSSAA is "successful." Similarly, when the UE transmits or receives "failure" as the authentication result, the UE may associate the authentication result with the S-NSSAI transmitted or received together with the authentication result and store the result as information about the UE indicating that the NSSAA is "failed."

[0322] Furthermore, each device may perform processing based on updating stored information based on completion of this procedure. For example, the AFM may initiate a UE configuration update procedure or a network-initiated de-registration procedure when there is a change in the S-NSSAI included in the allowed NSSAI and / or rejected NSSAI for the UE based on completion of this procedure. The AMF may notify the UE of the new allowed NSSAI and the new rejected NSSAI using the UE configuration update procedure. The AMF may notify the UE of the new rejected NSSAI using the network-initiated de-registration procedure.

[0323] [3.3. UE configuration update procedure] Next, the generic UE configuration update procedure will be described with reference to FIG. 8. Hereinafter, the generic UE configuration update procedure will also be referred to as this procedure. This procedure is a procedure for a core network to update configuration information of a UE. This procedure may be a procedure for mobility management that is initiated by the network for a UE registered in the network.

[0324] Furthermore, a device in a core network such as an AMF may start this procedure based on an update of a network configuration and / or an update of an operator policy. The trigger of this procedure may be detection of UE mobility, detection of a change in the state of the UE, and / or the access network, and / or the core network, or a change in the state of a network slice. The trigger of this procedure may be reception of a request from a DN and / or an application server of the DN, a change in the network configuration, or a change in an operator policy. The trigger of this procedure may be expiration of a running timer. The trigger for the device in the core network to start this procedure is not limited to these. In other words, this procedure may be executed at any timing after the above-mentioned registration procedure and / or PDU session establishment procedure are completed. Furthermore, this procedure may be executed at any timing as long as each device has established a 5GMM context and / or is in a 5GMM connected mode.

[0325] During this procedure, each device may transmit and receive a message including identification information for changing the configuration information of the UE and / or identification information for stopping or changing a function being executed 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.

[0326] The UE may update the UE's configuration information based on the control information transmitted and received by this procedure. Furthermore, the UE may stop a function being executed or start a new function in accordance with the update of the UE's configuration information. In other words, the device in the core network may initiate this procedure and further transmit the control message and control information of this procedure to the UE, thereby causing the UE to update the UE's configuration information that can be identified using the control information. Furthermore, the device in the core network may stop a function being executed by the UE or cause the UE to start a new function by updating the UE's configuration information.

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

[0328] Furthermore, when the UE's configuration information is updated, the new AMF 141 may transmit at least one of the tenth to sixteenth identification information in a configuration update command message.

[0329] UE_A10 receives a configuration update command message and / or one or more pieces of identification information from the network, such as the 10th to 16th identification information. More specifically, the UE receives a configuration update command message and / or one or more pieces of identification information from the new AMF141.

[0330] UE_A10 may recognize the received information based on receiving at least one of identification information 10 to 16. Specifically, the UE may store and / or update information related to the NSSAI and start and / or stop a back-off timer, as described in detail in the NSSAI update procedure in Chapter 3.5.

[0331] UE_A10 may recognize that the maximum number of UEs connected per slice has been reached, and therefore transmission of MM messages and / or transmission of SM messages using the S-NSSAI indicated by the 10th identification information, and / or the S-NSSAI indicated by the 14th identification information, and / or the S-NSSAI related to the mapped S-NSSAI indicated by the 15th identification information is temporarily prohibited. Note that here, the MM procedure may be a registration request message, and the SM message may be a PDU session establishment request message.

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

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

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

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

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

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

[0338] 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 expressed as a 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.

[0339] When the new AMF 141 includes the rejected NSSAI in the control message using the Extended rejected NSSAI IE, the new AMF 141 may include the 16th identity information in the control message and transmit it. Alternatively, the new AMF 141 may include the 16th identity information in the Extended rejected NSSAI IE and transmit it.

[0340] The new AMF 141 may indicate the range in which the S-NSSAI included in the Allowed NSSAI and / or Extended rejected NSSAI IE is valid by sending the 16th identification information.

[0341] 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 procedure in Chapter 3.5.

[0342] In addition, the NSSAI update procedure in Chapter 3.5 may be executed during this procedure or after completion of this procedure, or may be executed based on the completion of this procedure after completion of this procedure. Furthermore, the UE may transmit a configuration update complete message as a response message to the configuration update command message to the AMF 140 via the 5G AN (gNB) based on the identification information included in the configuration update command message (S802).

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

[0344] 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, when update information for the setting information is transmitted and received, each device may update the setting information. Furthermore, when 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.

[0345] Furthermore, the UE_A10 may store the identification information received together with the configuration information command message based on the completion of the procedure, and may recognize the network decision. Also, the UE may execute each procedure based on the stored information based on the completion of the procedure.

[0346] 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 can instruct the UE to stop or change a function being executed by the UE.

[0347] 3.4. Network-initiated Deregistration Procedure Next, a network-initiated de-registration procedure will be described with reference to Fig. 9. Hereinafter, this procedure refers to the network-initiated de-registration procedure. The network-initiated de-registration procedure is a procedure in which the network manually cancels registration with access network_A, and / or core network_A, access network_B, and / or core network_B, and / or DN, and / or PDN. This procedure may be a procedure for mobility management that is initiated by the network for a UE registered in the network.

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

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

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

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

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

[0353] Furthermore, when the UE's configuration information is updated, the new AMF 141 may include at least one of the tenth to sixteenth identification information in the non-registration request message and send it.

[0354] In addition, the tenth to sixteenth identification information may be included in the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first NSSAI and transmitted, or may be these NSSAIs.

[0355] When the new AMF 141 includes the 13th identification information, which indicates that the new AMF 141 applies to all PLMNs, in a control message, the new AMF 141 may also include the 15th identification information in the control message.

[0356] UE_A10 receives the control message and / or one or more pieces of information among the 10th to 16th identification information from the network. More specifically, the UE receives the control message and / or one or more pieces of information among the 10th to 16th identification information from the new AMF141.

[0357] UE_A10 may recognize the received information based on receiving at least one of identification information 10 to 16. Specifically, the UE may store and / or update information related to the NSSAI and start and / or stop a back-off timer, as described in detail in the NSSAI update procedure in Chapter 3.5.

[0358] UE_A10 may recognize that the maximum number of UEs connected per slice has been reached, and therefore transmission of MM messages and / or transmission of SM messages using the S-NSSAI indicated by the 10th identification information, and / or the S-NSSAI indicated by the 14th identification information, and / or the S-NSSAI related to the mapped S-NSSAI indicated by the 15th identification information is temporarily prohibited. Note that here, the MM procedure may be a registration request message, and the SM message may be a PDU session establishment request message.

[0359] 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 procedure in Chapter 3.5.

[0360] In addition, the NSSAI update procedure in Chapter 3.5 may be performed during this procedure, or after completion of this procedure, or after completion of this procedure, based on the completion of this procedure.

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

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

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

[0364] Furthermore, each device may perform processing based on the information transmitted and received in the non-registration procedure based on the completion of the non-registration procedure. For example, UE_A10 may start the registration procedure based on the completion of the non-registration procedure.

[0365] [3.5.NSSAI Renewal Procedure] The following describes the update procedures of each NSSAI stored in UE_A10. Note that the NSSAI update procedures 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.

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

[0367] 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 the one or more mapped S-NSSAIs.

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

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

[0370] Further, when UE_A10 receives the configured NSSAI, it may delete the "first NSSAI stored by UE_A10" and / or the "first NSSAI stored by UE_A10 and associated with the current PLMN" and / or one or more "first NSSAIs stored by UE_A10 and associated with the EPLMN of the current PLMN".

[0371] Further, 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 "first pending NSSAIs stored by UE_A10 and associated with the EPLMN of the current PLMN".

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

[0373] Furthermore, when UE_A10 receives a TAI list and an allowed NSSAI from new AMF141, and if at least one TAI included in the TAI list belongs to 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."

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

[0375] When UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSAI of the S-NSSAI included in the "allowed NSSAI deleted based on reception" or the "old allowed NSSAI updated based on reception". Furthermore, when a mapped S-NSSAI is included in the "allowed NSSAI received by UE_A10", UE_A10 may store the one or more mapped S-NSSAIs.

[0376] However, if UE_A10 receives an S-NSSAI included in an old allowed NSSAI included in a pending NSSAI, the mapped S-NSSAI for that S-NSSAI does not need to be deleted.

[0377] When UE_A10 receives an MM message including an allowed NSSAI and a pending NSSAI, UE_A10 may perform control based on receipt of the pending NSSAI before control based on receipt of the allowed NSSAI.

[0378] Specifically, if the old allowed NSSAI stored by UE_A10 includes S-NSSAI#1, and UE_A10 receives from the network a pending NSSAI that includes S-NSSAI#1 and a new allowed NSSAI that does not include S-NSSAI#1, UE_A10 may update each stored NSSAI based on the reception of the pending NSSAI before updating each stored NSSAI based on the reception of the allowed NSSAI.

[0379] Similarly, when UE_A10 receives an MM message including an allowed NSSAI and a rejected NSSAI, UE_A10 may perform control based on receipt of the rejected NSSAI before control based on receipt of the allowed NSSAI.

[0380] Specifically, if the old allowed NSSAI stored by UE_A10 includes S-NSSAI#1, and UE_A10 receives from the network a rejected NSSAI that includes S-NSSAI#2, which is the mapped S-NSSAI of S-NSSAI#1, and a new allowed NSSAI that does not include S-NSSAI#1, UE_A10 may update each stored NSSAI based on the reception of the rejected NSSAI before updating each stored NSSAI based on the reception of the allowed NSSAI.

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

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

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

[0384] In addition, the conditions for deleting the S-NSSAI included in the received Allowed NSSAI from the first 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.

[0385] When UE_A10 is roaming, when it receives an Allowed NSSAI, if one or more mapped S-NSSAIs of the S-NSSAI included in the first rejected NSSAI and / or the second rejected NSSAI are not all included in the Allowed NSSAI and / or pending NSSAI, and at least one mapped S-NSSAI is associated with the S-NSSAI and included in the Allowed NSSAI, it may behave in such a way that the S-NSSAI is not deleted from the Allowed NSSAI.

[0386] When roaming, UE_A10 may behave in such a way that when it receives the first indication and the 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.

[0387] When roaming, UE_A10 may behave such that, when it receives a second indication and 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.

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

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

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

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

[0392] 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 a 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.

[0393] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "first 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 "first NSSAI stored by UE_A10 and associated with all PLMNs".

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

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

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

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

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

[0399] Furthermore, when 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, when the UE stores a 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.

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

[0401] Here, if UE_A10 receives a rejected NSSAI that includes the S-NSSAI of the HPLMN, and if the mapped S-NSSAI of the 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 the S-NSSAI from the "allowed NSSAI stored by UE_A10 and associated with the current PLMN".

[0402] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from "pending NSSAIs 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 "pending NSSAIs 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 "pending NSSAIs stored by UE_A10 and associated with the EPLMN".

[0403] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "first 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 "first NSSAI stored by UE_A10 and associated with all PLMNs".

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

[0405] More specifically, when UE_A10 receives a rejected NSSAI IE, and the rejected S-NSSAI#1 included in the rejected NSSAI IE further 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 in the first rejected NSSAI stored by the UE.

[0406] 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 is not possible in the current registration area," UE_A10 may store S-NSSAI#1 in the second rejected NSSAI stored by the UE.

[0407] 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 NSSAA failure or cancellation," UE_A10 may store S-NSSAI#1 in the third rejected NSSAI stored by the UE.

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

[0409] Similarly, when UE_A10 receives a rejected NSSAI IE, and further when 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 the S-NSSAI#1 in 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 in the first rejected NSSAI stored by the UE.

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

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

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

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

[0414] 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 first 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.

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

[0416] When roaming, UE_A10 may behave in such a way that when it receives the first indication and the first rejected NSSAI and / or the 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.

[0417] When UE_A10 receives the second indication and the first rejected NSSAI and / or the 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.

[0418] In addition, the second indication may be information indicating that the entire S-NSSAI of the current PLMN of the associated rejected S-NSSAI has been rejected, as indicated by the 16th identification information.

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

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

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

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

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

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

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

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

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

[0428] When roaming, UE_A10 may behave in such a way that when it receives the first indication and the first rejected NSSAI and / or the 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.

[0429] When UE_A10 receives the second indication and the first rejected NSSAI and / or the 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.

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

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

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

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

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

[0435] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from the "first 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 "first 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 "first NSSAI stored by UE_A10 and associated with the EPLMN".

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

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

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

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

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

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

[0442] Further, UE_A10 may perform the following operations for each tenth identification information based on receiving at least one or more of the tenth to sixteenth identification information and / or receiving a control message:

[0443] UE_A10 may include the S-NSSAI indicated by the tenth identity and / or the S-NSSAI indicated by the fourteenth identity and / or the S-NSSAI related to the mapped S-NSSAI indicated by the fifteenth identity in an appropriate first NSSAI and store it. Specifically, the UE may add the S-NSSAI indicated by the received fourteenth identity to the first NSSAI associated with the information indicated by the eleventh identity and / or the thirteenth identity.

[0444] Alternatively, UE_A10 may add the mapped S-NSSAI indicated in the received 15th identification information to the first NSSAI, or may add the S-NSSAI related to the mapped S-NSSAI indicated in the received 15th identification information to the first NSSAI associated with the current PLMN, or may add it to the first NSSAI associated with the current PLMN and the current access type (registered access type, 3GPP access or non-3GPP access), or may add it to the first NSSAI associated with the current PLMN and all access types.

[0445] In a roaming case, the UE may recognize whether the information indicated in the 13th identity is the S-NSSAI of the HPLMN or the S-NSSAI of the current PLMN (VPLMN) based on the information indicated in the 13th identity. Specifically, if the 13th identity is valid for the current PLMN, the UE may determine that the S-NSSAI included in the 10th identity is the S-NSSAI of the VPLMN. Or, specifically, if the 13th identity is valid for all current PLMNs, the UE may determine that the S-NSSAI included in the 10th identity is the S-NSSAI of the HPLMN.

[0446] In a roaming case, the UE may determine the S-NSSAI to which the back-off timer applies based on the information indicated in the thirteenth identity. Specifically, if the thirteenth identity is valid for the current PLMN, the UE may enable the back-off timer for the S-NSSAI of the current PLMN, and while the back-off timer is running, the initiation of an MM procedure using the S-NSSAI of the current PLMN may be restricted for the current PLMN.

[0447] Or, specifically, if the 13th identity is valid for all current PLMNs, the UE may enable a back-off timer for the S-NSSAI of the HPLMN, and while the back-off timer is running, the initiation of an MM procedure using the S-NSSAI of the HPLMN may be restricted for all PLMNs. Here, the MM procedure using the S-NSSAI of the HPLMN also includes a case where the S-NSSAI managed by the S-NSSAI of the HPLMN as the mapped S-NSSAI is included in the requested NSSAI.

[0448] In other words, while a backoff timer valid for all PLMNs is running, in all PLMNs, the UE may transition to a state in which it is restricted from sending the corresponding S-NSSAI in the requested NSSAI and from sending the corresponding S-NSSAI as a mapped S-NSSAI of the requested NSSAI.

[0449] Furthermore, if the S-NSSAI included in the first 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.

[0450] Furthermore, when UE_A10 receives the 15th identification information, it may store the S-NSSAI indicated by the 15th identification information as a mapped S-NSSAI of the S-NSSAI indicated by the 14th identification information.

[0451] If the received 13th identification information indicates that the information applies to all PLMNs, the UE may delete the S-NSSAI associated with the mapped S-NSSAI indicated in the 15th identification information from the allowed NSSAI corresponding to PLMNs other than the current PLMN.

[0452] UE_A10 may recognize that the S-NSSAI indicated in the tenth identification information has reached the maximum number of UEs connected per slice based on reception of the tenth identification information and / or the eleventh identification information and / or reception of the control message. Here, the S-NSSAI indicated in the tenth identification information may be the S-NSSAI indicated in the fourteenth identification information and / or the mapped S-NSSAI indicated in the fifteenth identification information.

[0453] UE_A10 may start counting a back-off timer associated with the S-NSSAI or may manage the back-off timer using the received back-off timer value based on receiving at least one of the tenth to sixteenth identification information and / or receiving a control message, where the back-off timer value may be the timer value indicated in the tenth identification information and / or the twelfth identification information, and the S-NSSAI may be the S-NSSAI indicated in the first identification information and / or the tenth identification information and / or the fourteenth identification information and / or the mapped S-NSSAI indicated in the fifteenth identification information.

[0454] While the backoff timer is running, UE_A10 may be prohibited from sending MM messages or SM messages using the S-NSSAI associated with the backoff timer, or the mapped S-NSSAI (S-NSSAI of the HPLMN) associated with the backoff timer, or the S-NSSAI related to the mapped S-NSSAI associated with the backoff timer, or the S-NSSAI included in the NSSAI to which the backoff timer is associated, or the mapped S-NSSAI of the S-NSSAI included in the NSSAI to which the backoff timer is associated.

[0455] Furthermore, when UE_A10 receives the 13th identification information, it may apply a backoff timer according to the validity range indicated in the 13th identification information.

[0456] Specifically, when the 13th identification information is information indicating that the back-off timer is applied in the current PLMN, UE_A10 may apply the back-off timer in the current PLMN. Specifically, when the PLMN is changed, UE_A10 may not stop the count of the back-off timer or the back-off timer, but the restriction by the back-off timer associated with the PLMN before the movement may be lifted. In other words, when the PLMN is changed, the UE maintains the back-off timer, but the restriction on the PLMN before the movement may be lifted.

[0457] Alternatively, UE_A10 may stop counting the backoff timer associated with the current PLMN or the backoff timer when the PLMN is changed. In other words, UE_A10 may stop the backoff timer when the PLMN is changed, or the restriction on the PLMN before the movement may be lifted.

[0458] Alternatively, if the 13th identification information is information indicating that the backoff timer is applied to all PLMNs, UE_A10 may apply the backoff timer to all PLMNs. In other words, UE_A10 may maintain the backoff timer without stopping it even if a PLMN change occurs. If a PLMN change occurs while the backoff timer is running, UE_A10 may maintain a state in which MM messages and SM messages are prohibited using the S-NSSAI of the target PLMN associated with the mapped S-NSSAI of the S-NSSAI to which the backoff timer was associated, or the S-NSSAI of the target PLMN associated with the mapped S-NSSAI, or the mapped S-NSSAI.

[0459] Alternatively, if the 13th identification information is information indicating that the backoff timer is applied in the current registration area, UE_A10 may apply the backoff timer in the current registration area. In other words, when UE_A10 leaves the registration area, UE_A10 may stop counting the backoff timer or the backoff timer.

[0460] Further, UE_A10 may manage and / or store a first NSSAI associated with the 11th identity and / or the 13th identity or one or more S-NSSAIs included in the first NSSAI.

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

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

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

[0464] Specifically, when a backoff timer is valid for a registered PLMN, 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 first NSSAI associated with the current PLMN.

[0465] Furthermore, when a backoff timer is valid for a registered PLMN, 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 first NSSAI applied to all PLMNs.

[0466] Alternatively, when the backoff timer is valid for all PLMNs, 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 first NSSAI that applies to all PLMNs.

[0467] Furthermore, when a backoff timer is valid for all PLMNs, upon stopping or expiration of the backoff timer, the S-NSSAI to which the backoff timer was associated, or the mapped S-NSSAI to which the backoff timer was associated, or the S-NSSAI related to the mapped S-NSSAI to which the backoff timer was associated may be deleted from the first NSSAI applied to each PLMN.

[0468] In other words, if UE_A10 stores an S-NSSAI to which the back-off timer is associated, or a mapped S-NSSAI to which the back-off timer was associated, or an S-NSSAI related to the mapped S-NSSAI to which the back-off timer was associated, included in multiple first NSSAIs, UE_A10 may delete the corresponding S-NSSAI from all corresponding first NSSAIs.

[0469] Specifically, for example, if backoff timer #1 associated with S-NSSAI #1 is managed as valid in all PLMNs, when backoff timer #1 stops or expires, the UE may delete S-NSSAI #1 from the first NSSAI #1 associated with PLMN #1, and further delete S-NSSAI #2 associated with the mapped S-NSSAI of S-NSSAI #1 from the first NSSAI #2 associated with PLMN #2.

[0470] 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 expressed as a 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.

[0471] In UE_A10, if the S-NSSAI is deleted from the first NSSAI while a valid backoff timer for the S-NSSAI is running, UE_A10 may stop the backoff timer.

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

[0473] Alternatively, UE_A10 that is running the back-off timer may stop and / or delete the back-off timer without updating or deleting the first NSSAI. Specific examples of conditions for deleting the first NSSAI and / or stopping the back-off timer are shown below.

[0474] When 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 first NSSAI, which is information independent of access type, and / or the S-NSSAI included in the first NSSAI.

[0475] When 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 that is valid for the first NSSAI regardless of access type and / or the S-NSSAI included in the first NSSAI.

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

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

[0478] If UE_A10 receives a Rejected NSSAI from the current PLMN or SNPN, including an S-NSSAI included in the first NSSAI associated with the current PLMN or SNPN, UE_A10 may delete the S-NSSAI from the first NSSAI regardless of the access type.

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

[0480] If UE_A10 receives a pending NSSAI for an NSSAA or a mapped S-NSSAI(s) for a pending NSSAI from the current PLMN or SNPN that includes an S-NSSAI included in the first NSSAI to which the current PLMN or SNPN is associated, UE_A10 may delete the S-NSSAI from that first NSSAI regardless of access type.

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

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

[0483] 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 valid for the first NSSAI associated with that access type and / or the S-NSSAI included in the first NSSAI.

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

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

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

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

[0488] 4. EMBODIMENTS OF THE PRESENT ART An embodiment of the present invention may be a combination of one or more of the procedures described in Chapter 3. For example, in this embodiment, based on the completion of the initial registration procedure described in Chapter 3.1, the UE may transition to a registered state, and further perform registration procedures for movement and periodic registration update in Chapter 3.1. During each procedure, the UE_A10 may perform an NSSAI update procedure described in Chapter 3.5 based on information received from the NW and / or the state of the UE, and may update and / or delete information related to the stored NSSAI.

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

[0490] [4.1. First embodiment] Hereinafter, a first embodiment (hereinafter, this embodiment) will be described. In this embodiment, a form will be described in which UE_A10 updates the Allowed NSSAI and / or Pending NSSAI stored based on reception of a non-registration request message including a Rejected NSSAI.

[0491] When roaming, the UEA_10 initiates the registration procedure by sending a registration request message to the current PLMN or SNPN (NW).

[0492] Specifically, UE_A10 sends a registration request message including a requested NSSAI that includes S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#b, S-NSSAI IE#3 consisting of S-NSSAI#1 and mapped S-NSSAI#c, and S-NSSAI IE#4 consisting of S-NSSAI#1 and mapped S-NSSAI#d, based on the set of Allowed NSSAI and mapped S-NSSAI of the Allowed NSSAI associated with the current PLMN or SNPN stored by UE_A10.

[0493] Furthermore, UE_A10 receives a registration acceptance message from the NW. Specifically, UE_A10 receives an Allowed NSSAI including S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#b, and a pending NSSAI including S-NSSAI IE#3 consisting of S-NSSAI#1 and mapped S-NSSAI#c, and S-NSSAI IE#4 consisting of S-NSSAI#1 and mapped S-NSSAI#d.

[0494] Based on receiving the Allowed NSSAI and pending NSSAI, UE_A10 updates the stored Allowed NSSAI, the set of mapped S-NSSAI for the Allowed NSSAI, the pending NSSAI, and the set of mapped S-NSSAI for the pending NSSAI by replacing them with the received ones.

[0495] Specifically, UE_A10 may store S-NSSAI#1 in the Allowed NSSAI, mapped S-NSSAI#a and mapped S-NSSAI#b in the set of mapped S-NSSAI of the Allowed NSSAI, S-NSSAI#1 in the pending NSSAI, and mapped S-NSSAI#c and mapped S-NSSAI#d in the set of mapped S-NSSAI of the pending NSSAI.

[0496] Furthermore, UE_A10 receives a non-registration request message from the NW. UE_A10 updates the stored information based on the rejected NSSAI included in the non-registration request message.

[0497] For example, if UE_A10 receives an extended rejected NSSAI IE including rejected S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, and rejected S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#b, UE_A10 removes S-NSSAI#1 from the Allowed NSSAI and removes S-NSSAI#a and S-NSSAI#b from the set of mapped S-NSSAI of the Allowed NSSAI.

[0498] Or, for example, when UE_A10 receives an Extended rejected NSSAI IE including a rejected S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, UE_A10 does not remove S-NSSAI#1 from the Allowed NSSAI, but removes S-NSSAI#a from the set of mapped S-NSSAI of the Allowed NSSAI.

[0499] Or, for example, when UE_A10 receives an Extended rejected NSSAI IE including a rejected S-NSSAI IE#3 consisting of S-NSSAI#1 and mapped S-NSSAI#c, and a rejected S-NSSAI IE#4 consisting of S-NSSAI#1 and mapped S-NSSAI#d, UE_A10 deletes S-NSSAI#1 from the Pending NSSAI, and deletes S-NSSAI#c and S-NSSAI#d from the set of mapped S-NSSAIs for the Pending NSSAI.

[0500] Or, for example, when UE_A10 receives an Extended rejected NSSAI IE including a rejected S-NSSAI IE#3 consisting of S-NSSAI#1 and mapped S-NSSAI#c, UE_A10 does not delete S-NSSAI#1 from the Pending NSSAI, but deletes S-NSSAI#c from the set of mapped S-NSSAI for the Pending NSSAI.

[0501] As described above, UE_A10 can update the stored information of one or more NSSAIs based on the received NSSAI.

[0502] [4.2. Second embodiment] The second embodiment (hereinafter, the present embodiment) will be described below. In the present embodiment, a form will be described in which UE_A10 updates the first rejected NSSAI and / or the second rejected NSSAI stored based on reception of a configuration update command message including an Allowed NSSAI.

[0503] When roaming, the UEA_10 initiates the registration procedure by sending a registration request message to the current PLMN or SNPN (NW).

[0504] Specifically, UE_A10 sends a registration request message including a requested NSSAI that includes S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#b, S-NSSAI IE#3 consisting of S-NSSAI#1 and mapped S-NSSAI#c, S-NSSAI IE#4 consisting of S-NSSAI#1 and mapped S-NSSAI#d, and S-NSSAI IE#5 consisting of S-NSSAI#1 and mapped S-NSSAI#e, based on the set of Allowed NSSAI and mapped S-NSSAI of the Allowed NSSAI associated with the current PLMN or SNPN stored by UE_A10.

[0505] Further, UE_A10 receives a registration acceptance message from the NW. Specifically, the Allowed NSSAI includes S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, rejected S-NSSAI IE#1 consisting of S-NSSAI#1, mapped S-NSSAI#b, and a rejection reason value indicating "S-NSSAI not allowed in the current PLMN or SNPN", rejected S-NSSAI IE#2 consisting of S-NSSAI#1, mapped S-NSSAI#c, and a rejection reason value indicating "S-NSSAI not allowed in the current PLMN or SNPN", rejected S-NSSAI IE#3 consisting of S-NSSAI#1, mapped S-NSSAI#d, and a rejection reason value indicating "S-NSSAI not allowed in the current registration area", and rejected S-NSSAI IE#4 consisting of S-NSSAI#1, mapped S-NSSAI#e, and a rejection reason value indicating "S-NSSAI not allowed in the current registration area". The UE receives an Extended rejected NSSAI IE including S-NSSAI IE#4.

[0506] Based on receiving the Allowed NSSAI and rejected NSSAI, UE_A10 updates the stored Allowed NSSAI, the set of mapped S-NSSAI for the Allowed NSSAI, the rejected NSSAI, and the set of mapped S-NSSAI for the rejected NSSAI by replacing them with the received ones.

[0507] Specifically, UE_A10 may store S-NSSAI#1 as an Allowed NSSAI, mapped S-NSSAI#a in the set of mapped S-NSSAIs of the Allowed NSSAI, S-NSSAI#1 as the first rejected NSSAI, mapped S-NSSAI#b and mapped S-NSSAI#c in the set of mapped S-NSSAIs of the first rejected NSSAI, S-NSSAI#1 as the second rejected NSSAI, and mapped S-NSSAI#d and mapped S-NSSAI#e in the set of mapped S-NSSAIs of the second rejected NSSAI.

[0508] Furthermore, UE_A10 receives a setting update command message from the NW. UE_A10 updates the stored information based on the Allowed NSSAI included in the setting update command message.

[0509] For example, when UE_A10 receives an Allowed NSSAI IE including S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#b, and S-NSSAI IE#3 consisting of S-NSSAI#1 and mapped S-NSSAI#c, UE_A10 stores S-NSSAI#1 in the Allowed NSSAI, stores mapped S-NSSAI#a, #b, and #c as the mapped S-NSSAIs of the Allowed NSSAI, deletes S-NSSAI#1 from the first rejected NSSAI, and deletes mapped S-NSSAI#b and #c from the mapped S-NSSAI of the first rejected NSSAI.

[0510] For example, if UE_A10 receives an Allowed NSSAI IE that includes S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, and S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#b, UE_A10 stores S-NSSAI#1 in the Allowed NSSAI, stores mapped S-NSSAI#a and #b as the mapped S-NSSAIs of the Allowed NSSAI, does not delete S-NSSAI#1 from the first rejected NSSAI, and deletes mapped S-NSSAI#b from the mapped S-NSSAI of the first rejected NSSAI.

[0511] For example, when UE_A10 receives an Allowed NSSAI IE including S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#d, and S-NSSAI IE#3 consisting of S-NSSAI#1 and mapped S-NSSAI#e, UE_A10 stores S-NSSAI#1 in the Allowed NSSAI, stores mapped S-NSSAI#a, #d, and #e as the mapped S-NSSAIs of the Allowed NSSAI, deletes S-NSSAI#1 from the second rejected NSSAI, and deletes mapped S-NSSAI#d and #e from the mapped S-NSSAI of the first rejected NSSAI.

[0512] For example, when UE_A10 receives an Allowed NSSAI IE including S-NSSAI IE#1 consisting of S-NSSAI#1 and mapped S-NSSAI#a, and S-NSSAI IE#2 consisting of S-NSSAI#1 and mapped S-NSSAI#d, UE_A10 stores S-NSSAI#1 in the Allowed NSSAI, stores mapped S-NSSAI#a and #d as the mapped S-NSSAI of the Allowed NSSAI, does not delete S-NSSAI#1 from the second rejected NSSAI, and deletes mapped S-NSSAI#d from the mapped S-NSSAI of the first rejected NSSAI.

[0513] As described above, UE_A10 can update the stored information of one or more NSSAIs based on the received NSSAI.

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

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

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

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

[0518] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0519] 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) including a transceiver unit and a storage unit, The transceiver receives an S-NSSAI (Single Network Slice Selection Assistance Information) included in a rejected NSSAI (Extended rejected NSSAI (Network Slice Selection Assistance Information) IE), and One or more mapped S-NSSAIs of the S-NSSAI included in the pending NSSAI are stored in the storage unit, and If all the mapped S-NSSAIs are included in the Extended rejected NSSAI IE, The S-NSSAI is deleted from the pending NSSAI stored in the storage unit, Here, the rejected NSSAI is a rejected NSSAI for a current PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network), or a rejected NSSAI for a current registration area, The UE is characterized by:

2. the Extended rejected NSSAI IE includes a rejection reason value associated with the S-NSSAI; Based on the rejection reason value, one or more mapped S-NSSAIs of the rejected NSSAI are stored in the storage unit. The UE according to claim 1 .

3. The transceiver receives the S-NSSAI included in the rejected NSSAI included in the Extended rejected NSSAI IE, and One or more of the mapped S-NSSAIs included in the pending NSSAI are stored in the storage unit; and If all of the mapped S-NSSAIs are not included in the Extended rejected NSSAI IE, The S-NSSAI is not deleted from the pending NSSAI stored in the storage unit. The UE according to claim 1 .

4. A communication control method executed by a UE (User Equipment), comprising: The UE receives a Single Network Slice Selection Assistance Information (S-NSSAI) included in a rejected NSSAI included in an Extended rejected NSSAI (Network Slice Selection Assistance Information) IE, and One or more mapped S-NSSAIs of the S-NSSAI included in the pending NSSAI are stored in the UE; and If all the mapped S-NSSAIs are included in the Extended rejected NSSAI IE, deleting the S-NSSAI from the pending NSSAI stored by the UE; Here, the rejected NSSAI is a rejected NSSAI for a current PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network), or a rejected NSSAI for a current registration area, A communication control method executed by a UE.

Images