UE(user equipment)

Abstract

To clarify how to handle a rejected S-NSSAI that is rejected in a tracking area of a registration area but can be used in another tracking area of the registration area, and the behavior of the UE and network with respect to the rejected S-NSSAI.SOLUTION: In user equipment, when an S-NSSAI that cannot be used in a current tracking area in a current registration area but can be used in other tracking areas in the current registration area is stored in the rejected NSSAI for the current tracking area, and the UE receives a new allowed NSSAI for the current PLMN or SNPN, the UE deletes the S-NSSAI included in the allowed NSSAI from the rejected NSSAI for the current tracking area.SELECTED DRAWING: Figure 6

Description

[Technical field]

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

[0002] The 3GPP (3rd Generation Partnership Project) is studying the system architecture of the 5GS (5G System), a fifth-generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 3). The concept of network slices (NS) was introduced in Release 15, the initial release of the 5G standard, and then, in Release 16 and Release 17, functional extensions of the network slices have been discussed (see Non-Patent Documents 1 to 3). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V17.2.0 (2021-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17) [Non-Patent Document 2] 3GPP TS 23.502 V17.2.1 (2021-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) [Non-Patent Document 3] 3GPP TS 24.501 V17.4.1 (2021-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 17) [Non-Patent Document 4] TSG SA Meeting #SP-94E; SP-211320; 14 - 20 December 2021, Electronic meeting Summary of the Invention [Problem to be solved by the invention]

[0004] In Release 18, further functional enhancements to network slicing are being considered. There is a possibility that consideration will be given to handling rejected S-NSSAIs that are rejected in a tracking area of ​​a registration area but can be used in another tracking area of ​​that registration area, but no concrete discussions have begun yet (Non-Patent Document 4).

[0005] One aspect of the present invention has been made in consideration of the above-mentioned circumstances, and aims to clarify how to handle a rejected S-NSSAI that is rejected in a tracking area of ​​a registration area but can be used in another tracking area of ​​that registration area, and the behavior of the UE and NW regarding that rejected S-NSSAI. [Means for solving the problem]

[0006] A UE of one embodiment of the present invention is a UE (User Equipment) having a transceiver unit, a control unit, and a memory unit, wherein in the memory unit, an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area is stored among the rejected NSSAIs for the current tracking area, and when the transceiver unit receives a new allowed NSSAI for the current PLMN or SNPN, the control unit deletes the S-NSSAI included in the allowed NSSAI from the rejected NSSAI for the current tracking area in the memory unit. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to clarify how to handle a rejected S-NSSAI that is rejected in a tracking area of ​​a registration area but can be used in another tracking area of ​​that registration area, as well as the behavior of the UE and NW regarding that rejected S-NSSAI. [Brief description of the drawings]

[0008] [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. 11 is a diagram illustrating a setting update procedure. [Figure 8] FIG. 13 is a diagram illustrating a non-registration procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

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

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

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

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

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

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

[0018] 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 written with the symbol omitted, such as gNB. 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.

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

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

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

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

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

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

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

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

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

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

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

[0030] 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 be configured with devices not shown in Fig. 2. For example, the core network_A and / or the core network_B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

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

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

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

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

[0035] Each storage unit (storage unit_A340, storage unit_B540, storage 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 storage unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between devices / functions other than the device / function itself (for example, UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each storage unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described later. Each storage unit may store this information for each UE. In addition, when interworking is performed between 5GS and EPS, each storage unit can store control messages and user data transmitted and received between devices / functions included in 5GS and / or 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.

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

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

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

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

[0040] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE. The memory unit _340 may also have a function of storing control information transmitted and received between an access network device, a core network device, and a DN.

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

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

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

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

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

[0046] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB. In addition, the memory unit _540 may have a function of storing control information transmitted and received between the UE, other access network devices (base station devices), core network devices, and DN.

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

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

[0049] 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, and / or an NSACF in a 5G AN. That is, the AMF can 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 using the network connection unit _B720.

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

[0051] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the AMF. The memory unit _740 may also have a function of storing control information transmitted and received between the UE, the access network device, other core network devices, and the DN.

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

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

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

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

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

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

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

[0059] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be a network function (NF) that manages one or more network slice instances (NSIs). In addition, the AMF may be a common control plane network function (CCNF) shared between multiple NSIs.

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

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

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

[0063] 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, and / or the NSACF.

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

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

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

[0067] In addition, the memory unit_740 may have a function of storing control information transmitted and received between the UE, access network devices, other core network devices, and the DN.

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

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

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

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

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

[0073] 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, downlink packet buffering, and a function for triggering downlink data notification.

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

[0075] In addition, the memory unit_740 may have a function of storing control information transmitted and received between the UE, access network devices, other core network devices, and DN.

[0076] The user plane (also referred to as UP) 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 in the case of 4G, or a PDU session in the case of 5G. 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.

[0077] Furthermore, the control plane (also referred to as CP) refers to a control message transmitted and received to perform communication control 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. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the AMF. 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.

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

[0079] [2.6. Description of other devices and / or functions and identification information in this embodiment] Next, other devices and / or functions and identification information will be described.

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

[0081] In addition, NSSF (Network Slice Selection Function) may be a network function (also referred to as NF) that has the function of selecting a network slice to serve a UE.

[0082] Furthermore, a Network Data Analytics Function (NWDAF) may be an NF having a function of collecting data from NFs and application functions (also referred to as AFs).

[0083] Furthermore, a PCF (Policy Control Function) may be an NF having a function of determining a policy for controlling the behavior of a network.

[0084] Furthermore, an NRF (Network Repository Function) may be an NF having a service discovery function. The NRF may be an NF having a function of providing information of a discovered NF when receiving a discovery request for another NF from an NF.

[0085] A Network Slice Admission Control Function (NSAC) may monitor and control the number of registered UEs per NS and / or the number of PDU sessions per NS for a network slice (NS) associated with a Network Slice Admission Control (NSAC). The NSACF may be configured with a maximum number of permitted UEs per NS and / or a maximum number of permitted PDU sessions per NS for each NS associated with the NSAC. The NSACF may increase or decrease the number of UEs registered with an NS so as not to exceed the maximum number of permitted UEs for registration with the NS. The NSACF may maintain a list of UE IDs registered with an NS associated with an NSAC. When the number of UEs registered with an NS increases (e.g., when a UE sends a new registration request message to the NS), the NSACF may check whether the ID of the UE is already included in the list of UE IDs registered with the NS, and if the ID of the UE is not included in the list, further check whether the maximum number of UEs per NS has been reached for the NS. In addition, when the registration status of a UE for an NS associated with an NSAC changes during a registration procedure, and / or a deregistration procedure, and / or an NSSAA procedure, etc., the AMF may make a request to the NSACF regarding the maximum number of UEs per NS. The NSACF may also have a function to increase or decrease the number of PDU sessions for an NS so as not to exceed the maximum number of PDU sessions permitted by that NS. In addition, when the number of PDU sessions using an NS increases (e.g., when a UE sends a PDU session establishment request message to that NS), the NSACF may have a function to check whether the maximum number of UEs per NS has been reached for that NS. In addition, the SMF may make a request to the NSACF regarding the maximum number of PDU sessions per NS during a PDU session establishment procedure and / or a PDU session release procedure.

[0086] In addition, the SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. 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.

[0087] The SM procedure (also referred to as a procedure for SM) 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.

[0088] Also, an MM (Mobility management) message (also referred to as a NAS MM message) may be a 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.

[0089] In addition, the MM procedure (also referred to as the procedure for MM) may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

[0090] In addition, the 5GS (5G System) service may be a connection service provided using the core network_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.

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

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

[0093] A PDU (Protocol Data Unit) session can be defined as an association between a DN providing 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.

[0094] 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, and access network identification information, or 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.

[0095] 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).

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

[0097] A PLMN (Public Land Mobile Network) is a communication network that provides a mobile radio communication service. A PLMN is a network managed by an operator, which is a communication carrier, and the operator can be identified by a PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may hold an Equivalent HPLMN list for identifying one or more EPLMNs (Equivalent HPLMNs) in the USIM. A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN). A service provided by a PLMN may be called a PLMN service, and a service provided by a SNPN may be called an SNPN service.

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

[0099] 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 network slice to be deployed. 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, one or more of which 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). Here, an NST is associated with a resource requirement for providing a required communication service or capability, and is a logical expression of one or more NFs. In other words, an NSI may be a collection in a core network _B 190 composed of multiple NFs. An NSI may also be a logical network configured to separate user data delivered by a service or the like. 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. 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.

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

[0101] In addition, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information that assists an access network or a core network in selecting an NSI. The UE may store an NSSAI authorized by the network for each PLMN. In addition, the NSSAI may be information used to select an AMF.

[0102] Furthermore, the configured NSSAI (also referred to as configured NSSAI) is an NSSAI that is provided and stored in the UE. The UE may store the configured NSSAI for each PLMN. 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 the S-NSSAI and the mapped S-NSSAI.

[0103] In addition, the requested NSSAI (also referred to as the Requested NSSAI) is an NSSAI provided from the UE to the network during the registration procedure. The requested NSSAI may be an allowed NSSAI or a configured NSSAI stored by the UE. Specifically, the requested NSSAI may be information indicating a network slice that the UE wishes to access. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is transmitted in a Radio Resource Control (RRC) message including a NAS message or 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.

[0104] In addition, the allowed NSSAI (also referred to as the Allowed NSSAI) is information indicating one or more network slices for which the UE is permitted. In other words, the allowed NSSAI is information that identifies a network slice to which the network permits the UE to connect. The UE and the network each store and manage the allowed NSSAI for each access (3GPP access or non-3GPP access) as information of the UE. The S-NSSAI included in the allowed NSSAI may be expressed as the allowed S-NSSAI. The allowed S-NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI.

[0105] Furthermore, the mapped S-NSSAI (also referred to as the mapped S-NSSAI) may be the S-NSSAI of the HPLMN mapped to the S-NSSAI of the registered PLMN in a roaming scenario. Furthermore, the mapped S-NSSAI may basically be the S-NSSAI used when the UE is roaming, or may be the S-NSSAI not used when the UE is not roaming (also referred to as non-roaming). Furthermore, the UE may store one or more mapped S-NSSAIs mapped to the configured NSSAI and the S-NSSAI included in the Allowed NSSAI of each access type. Furthermore, the UE may store one or more mapped S-NSSAIs included in the rejected NSSAI, or mapped S-NSSAIs corresponding to the S-NSSAI included in the rejected NSSAI.

[0106] Further, the rejected NSSAI (also referred to as rejected NSSAI) is information indicating one or more network slices to which the UE is not permitted. 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 may be information including one or more combinations of an S-NSSAI and a rejection reason value (hereinafter also referred to as a reason value or rejection reason). Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network may store and manage the rejected NSSAI appropriately, based on the rejection reason value associated with each S-NSSAI. Furthermore, the rejected NSSAI may be included in an NAS message transmitted from the network to the UE, such as a registration acceptance message, a configuration update command, or a registration rejection message, or an RRC message including a NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as rejected S-NSSAI. Here, the rejected NSSAI may mean any one of the first to fourth rejected NSSAI. Furthermore, the rejected S-NSSAI may mean a rejected S-NSSAI included in any one of the first to fourth rejected NSSAI. Furthermore, the rejected NSSAI may be any one of the first to fourth rejected NSSAI and a pending NSSAI, or a combination of these. 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.

[0107] Here, the first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN. In other words, the first rejected NSSAI may be an NSSAI that cannot be used in the current PLMN or SNPN. Also, the first rejected NSSAI may be a set of one or more S-NSSAIs that are not available in the current PLMN or 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. Also, the first rejected S-NSSAI may be a rejected S-NSSAI for the current PLMN or SNPN, or may be an S-NSSAI included in the rejected NSSAI for the current PLMN or SNPN. Also, the first rejected NSSAI may be a rejected NSSAI stored by the UE and / or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. 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. The rejection reason value may indicate "S-NSSAI not available in the current PLMN or SNPN" and may mean that the S-NSSAI associated with the rejection reason value is not available in the current PLMN or SNPN.

[0108] In addition, the first rejected NSSAI may be valid for the entire registered PLMN or registered SNPN. In other words, 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.

[0109] 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 or SNPN. In other words, the UE may delete the first rejected NSSAI when the UE transitions to an unregistered state for the current PLMN or SNPN via an access, or when the UE successfully registers to a new PLMN or SNPN via an access, or when the UE fails to register to a new PLMN via an access and transitions to an unregistered state, and the UE is not registered via the other access (unregistered state).

[0110] In addition, the S-NSSAI included in the first rejected NSSAI in the memory unit of the UE may be treated as being unavailable in the current PLMN or the entire SNPN, that is, the UE may be in a state in which the MM procedure and / or SM procedure using the S-NSSAI is prohibited in the current PLMN or the entire SNPN.

[0111] The second rejected NSSAI may be a rejected NSSAI for the current registration area (also referred to as a registration area). In other words, the second rejected NSSAI may be an NSSAI that cannot be used in the current registration area. The second rejected NSSAI may be a collection of one or more S-NSSAIs that are not available 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 of 5GS for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored by the UE and / 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. This reason value may indicate "S-NSSAI not available in the current registration area," which may mean that the S-NSSAI associated with the reason value is not available in the current registration area.

[0112] Furthermore, the second rejected NSSAI may be valid in the current registration area. That is, 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 a certain access, the UE may delete the second rejected NSSAI from memory.

[0113] In addition, the S-NSSAI included in the second rejected NSSAI in the memory unit of the UE may be treated as unavailable in the current registration area, i.e., the UE may be in a state in which the MM procedure and / or SM procedure using the S-NSSAI is prohibited in the current registration area.

[0114] Furthermore, the third rejected NSSAI is a set of one or more S-NSSAIs that are S-NSSAIs requiring 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 transmitted from the NW to the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. In this case, the rejection reason value may be "S-NSSAI is not available due to the failed or revoked network slice-specific authorization and authentication" or may be information indicating that the NSSAA for the S-NSSAI associated with the rejection reason value has failed or been revoked.

[0115] Furthermore, the third rejected NSSAI is valid in the entire registered PLMN. In other words, the UE and / or NW may treat the third rejected NSSAI and the S-NSSAI included in the third rejected NSSAI as information independent of the access type. In other words, 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.

[0116] The third rejected NSSAI is a rejected NSSAI that identifies a slice that the UE has rejected due to the failure or cancellation 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 the failure of the NSSAA. The third rejected NSSAI is information that is independent of 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. 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.

[0117] In addition, the S-NSSAI included in the third rejected NSSAI in the memory unit of the UE may be treated as unavailable in the entire current PLMN or SNPN, that is, the UE may be in a state where the MM procedure and / or SM procedure using the S-NSSAI is prohibited in the current registration area.

[0118] Also, the fourth rejected NSSAI may be a rejected NSSAI for the current tracking area. In other words, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area.

[0119] Also, the fourth rejected NSSAI may be a rejected NSSAI for the current tracking area in the current registration area. In other words, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area in the current registration area.

[0120] Furthermore, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area in the current registration area, but can be used in other tracking areas in the current registration area.

[0121] Furthermore, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current tracking area in the current registration area, but may be an NSSAI that can be used in other tracking areas in the current registration area and other registration areas (different from the current registration area).

[0122] In addition, the fourth rejected NSSAI may be a set of S-NSSAIs included in the requested NSSAI by the UE, which may be an S-NSSAI that is not available in the current tracking area, or a set of S-NSSAIs sent by the AMF with a rejection reason indicating that the S-NSSAI is not available in the current tracking area.

[0123] Also, in a roaming scenario (while roaming), the fourth rejected NSSAI may include one or more S-NSSAIs for the current PLMN and may include a set of mapped S-NSSAIs if available.

[0124] Furthermore, the fourth rejected NSSAI may be a rejected NSSAI stored by the UE and / or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. If the fourth rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the fourth rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. The reason value may be the 12th identification information.

[0125] Also, the fourth rejected NSSAI may be valid for 3GPP access and / or non-3GPP access. In other words, the UE and / or NW may treat the fourth rejected NSSAI as independent of the access type, or may treat the fourth rejected NSSAI as dependent on the access type. In other words, the UE and / or NW may manage and / or store the fourth rejected NSSAI for each access type, or may not manage and / or store the fourth rejected NSSAI for each access type.

[0126] Here, the fourth rejected NSSAI does not depend on the access type, for example, when the UE receives the fourth rejected NSSAI via 3GPP access, the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI may not only be available via 3GPP access, but also be available via non-3GPP access. Similarly, when the UE receives the fourth rejected NSSAI via non-3GPP access, the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI may not only be available via 3GPP access, but also be available via non-3GPP access. Note that, when the fourth rejected NSSAI does not depend on the access type, it is preferable that the UE and / or NW does not store the fourth rejected NSSAI for each access type (i.e., simply stores the fourth rejected NSSAI instead of storing it separately for each access type), but this is not limited thereto.

[0127] In addition, the case where the fourth rejected NSSAI depends on the access type may mean, for example, that when the UE receives the fourth rejected NSSAI via 3GPP access, the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI cannot be used via 3GPP access, but does not mean that it cannot be used via non-3GPP access. In other words, it may mean that the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI is not restricted from use in non-3GPP access. Similarly, when the UE receives the fourth rejected NSSAI via non-3GPP access, it may mean that the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI cannot be used via non-3GPP access, but does not mean that it cannot be used via 3GPP access. That is, it may mean that the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI is not restricted from use in 3GPP access. Note that, when the fourth rejected NSSAI depends on the access type, it is preferable that the UE and / or NW store the fourth rejected NSSAI for each access type (i.e., store the fourth rejected NSSAI for each access type), but this is not limited thereto.

[0128] Additionally, if the UE does not have a valid registration area and / or tracking area, the fourth rejected NSSAI may be applicable to the registration area and / or tracking area in which the rejected NSSAI was received.

[0129] In addition, if the current registration area or the current tracking area in the current registration area includes a TAI (Tracking Area Identity) belonging to a PLMN or SNPN different from the current PLMN or SNPN, and the current PLMN or SNPN and the different PLMN or SNPN are in a relationship of equivalent PLMN or equivalent SNPN, the fourth rejected NSSAI may be applied to these PLMNs or SNPNs in the current registration area and / or the current tracking area. In other words, in the current registration area or the current tracking area, the fourth rejected NSSAI may be applied not only to the current PLMN or SNPN, but also to the equivalent PLMN or equivalent SNPN.

[0130] In addition, if the S-NSSAI included in the requested NSSAI by the UE is the fourth rejected NSSAI, the AMF may reject the registration request message.

[0131] In addition, if the 5GS registration type indicates mobility registration updating, and the purpose of initiating the registration procedure is not to change the network slice to which the UE is currently registered, and the UE is in the current registration area or the current tracking area, the UE does not need to include a requested NSSAI in the registration procedure.

[0132] In addition, the S-NSSAI included in the fourth rejected NSSAI (also referred to as the fourth rejected S-NSSAI) may be associated with one or more tracking areas in which the rejected S-NSSAI (fourth rejected S-NSSAI) cannot be used.

[0133] Furthermore, when the UE is provided with a new configured NSSAI for the current PLMN or SNPN, the UE may replace the stored configured NSSAI with the new configured NSSAI. In this case, the UE may further delete the mapped S-NSSAI for the stored configured NSSAI and store the mapped S-NSSAI for the new configured NSSAI, may delete the stored fourth rejected NSSAI, or may delete the S-NSSAI included in the mapped S-NSSAI for the new configured NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0134] Furthermore, when the UE receives a new allowed NSSAI for the current PLMN or SNPN, the UE may delete the S-NSSAI included in the new allowed NSSAI from the stored fourth rejected NSSAI. In this case, the UE may further delete the S-NSSAI included in the mapped S-NSSAI for the new allowed NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0135] In addition, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration acceptance message, or a registration rejection message, or a non-registration request message, or a configuration update command message, based on the reason for rejection, the UE may store the received fourth rejected S-NSSAI in the rejected NSSAI and the mapped S-NSSAI for the rejected NSSAI, or may store the fourth rejected NSSAI and the mapped S-NSSAI for the fourth rejected NSSAI.

[0136] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration rejection message, or a non-registration request message, or a configuration update command message, and the S-NSSAI is included in the Rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0137] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration rejection message, or a non-registration request message, or a configuration update command message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0138] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration reject message, or a non-registration request message, or a configuration update command message during roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0139] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration rejection message, or a non-registration request message, or a configuration update command message while not roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0140] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration rejection message, or a non-registration request message, or a configuration update command message during roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the allowed NSSAI stored by the UE.

[0141] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration rejection message, or a non-registration request message, or a configuration update command message, and the S-NSSAI is included in the Rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0142] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration rejection message, or a non-registration request message, or a configuration update command message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0143] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration reject message, or a non-registration request message, or a configuration update command message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0144] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a registration accept message, or a registration rejection message, or a non-registration request message, or a configuration update command message during roaming, and the S-NSSAI is included in an Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the pending NSSAI stored by the UE.

[0145] In addition, when the UE deregisters via the access for which it received the fourth rejected NSSAI or the fourth rejected S-NSSAI, in other words, when the UE completes the deregistration procedure via that access, it may delete the fourth rejected NSSAI and / or its access type stored by the UE.

[0146] In addition, when the UE moves from the tracking area in which it received the fourth rejected NSSAI or the fourth rejected S-NSSAI to another tracking area, it may delete the fourth rejected NSSAI and / or its access type stored by the UE.

[0147] In addition, when the UE transitions from the 5GMM-REGISTERED state to the 5GMM-DEREGISTERED state, or from the 5GMM-DEREGISTERED state to the 5GMM-REGISTERED state, the UE may delete the fourth rejected NSSAI and / or its access type stored in the UE.

[0148] Furthermore, a UE that has received a fourth rejected NSSAI included in a registration accept message, a registration reject message, a configuration update command message, or a non-registration request message may perform an operation based on a rejection reason included in a rejected S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI. Specifically, if the rejection reason included in the rejected S-NSSAI indicates "S-NSSAI not available in the current tracking area" and / or "S-NSSAI not available in the current tracking area in the current registration area" and / or "No network slices available," the UE may be prohibited from using the fourth S-NSSAI in the current tracking area. That is, the UE may be in a state in which an MM procedure and / or an SM procedure using the fourth S-NSSAI is prohibited in the current tracking area.

[0149] In addition, when the UE is powered off, or when the UE moves out of the current tracking area, or when the UICC including the USIM is removed from the UE, or when the fourth rejected NSSAI or the fourth rejected S-NSSAI stored in the UE is deleted, this restriction may be lifted. In other words, the UE may be able to perform the MM procedure and / or the SM procedure using the fourth S-NSSAI in the current tracking area.

[0150] In addition, when the UE sends a registration request message including a requested NSSAI, it may select an S-NSSAI included in the requested NSSAI from among the S-NSSAIs other than the S-NSSAI included in the fourth rejected NSSAI (fourth rejected S-NSSAI) and / or the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI that it has stored.

[0151] In addition, if the UE sends a registration request message including capability information indicating that it does not support the NSSAA and a requested NSSAI, if the S-NSSAI included in the requested NSSAI is an S-NSSAI related to the NSSAA, the AMF may send a registration acceptance message including the S-NSSAI and a rejected NSSAI including a rejection reason indicating "S-NSSAI not available in the current tracking area" and / or "S-NSSAI not available in the current tracking area in the current registration area" and / or "No network slices available".

[0152] In addition, the fourth rejected S-NSSAI may be not only a rejected S-NSSAI included in the fourth rejected NSSAI, but also a rejected S-NSSAI not included in the fourth rejected NSSAI. In addition, the above description of the fourth rejected NSSAI may be read as a description of the fourth rejected S-NSSAI.

[0153] In addition, the fourth rejected NSSAI and the fourth rejected S-NSSAI may be included as LADN information contained in a registration accept message or a configuration update command and notified to the UE from the core network side.

[0154] Also, the mapped S-NSSAI for the fourth rejected NSSAI may be a mapped S-NSSAI corresponding to the fourth rejected NSSAI. In other words, the mapped S-NSSAI for the fourth rejected NSSAI may be an S-NSSAI of the HPLMN that is mapped to an S-NSSAI of the registered PLMN (i.e., an S-NSSAI included in the fourth rejected NSSAI, or the fourth rejected S-NSSAI) in a roaming scenario.

[0155] Also, the mapped S-NSSAI for the fourth rejected NSSAI may be valid for 3GPP access and / or non-3GPP access. In other words, the UE and / or NW may treat the mapped S-NSSAI for the fourth rejected NSSAI as independent of the access type, or may treat the mapped S-NSSAI for the fourth rejected NSSAI as dependent on the access type. In other words, the UE and / or NW may manage and / or store the mapped S-NSSAI for the fourth rejected NSSAI for each access type, or may not manage and / or store it for each access type.

[0156] Here, the fact that the mapped S-NSSAI for the fourth rejected NSSAI does not depend on the access type may mean, for example, that when the UE receives the mapped S-NSSAI for the fourth rejected NSSAI via 3GPP access, the mapped S-NSSAI for the fourth rejected NSSAI is not only unavailable via 3GPP access, but also unavailable via non-3GPP access. Similarly, when the UE receives the mapped S-NSSAI for the fourth rejected NSSAI via non-3GPP access, the mapped S-NSSAI for the fourth rejected NSSAI is not only unavailable via 3GPP access, but also unavailable via non-3GPP access. Furthermore, when the mapped S-NSSAI for the fourth rejected NSSAI does not depend on the access type, it is desirable for the UE and / or NW not to store the mapped S-NSSAI for the fourth rejected NSSAI for each access type (i.e., simply store the fourth rejected NSSAI rather than storing it separately for each access type), but this is not limited to this.

[0157] In addition, the case where the mapped S-NSSAI for the fourth rejected NSSAI depends on the access type may mean, for example, that when the UE receives the mapped S-NSSAI for the fourth rejected NSSAI via 3GPP access, the mapped S-NSSAI for the fourth rejected NSSAI cannot be used via 3GPP access, but does not mean that it cannot be used via non-3GPP access. In other words, it may mean that the use of the mapped S-NSSAI for the fourth rejected NSSAI in non-3GPP access is not restricted. Similarly, when the UE receives the mapped S-NSSAI for the fourth rejected NSSAI via non-3GPP access, the mapped S-NSSAI for the fourth rejected NSSAI may be used via non-3GPP access, but does not mean that it cannot be used via 3GPP access. In other words, it may mean that the use of the mapped S-NSSAI for the fourth rejected NSSAI in 3GPP access is not restricted. Furthermore, when the mapped S-NSSAI for the fourth rejected NSSAI depends on the access type, it is desirable for the UE and / or NW to store the mapped S-NSSAI for the fourth rejected NSSAI for each access type (i.e., store the fourth rejected NSSAI for each access type), but this is not limited to the above.

[0158] Furthermore, the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI in the memory unit of the UE may be treated as unavailable in the current tracking area or in the current tracking area in the current registration area. That is, the UE may be in a state in which the MM procedure and / or the SM procedure using the S-NSSAI is prohibited in the current tracking area or in the current tracking area in the current registration area. In other words, the UE may be in a state in which the MM procedure and / or the SM procedure using the S-NSSAI is not prohibited in tracking areas other than the current tracking area or in tracking areas other than the current tracking area in the current registration area.

[0159] In addition, a pending NSSAI (also referred to as a Pending NSSAI) is an S-NSSAI for which the network requires network slice specific authentication, and is a collection of one or more S-NSSAIs for which network slice specific authentication has not been completed and which cannot be used in the current PLMN. The pending NSSAI may be a Rejected NSSAI due to NSSAA or a pending NSSAI in 5GS. The pending NSSAI may be an NSSAI stored by the UE or the NW, or an NSSAI transmitted from the NW to the UE. Note that the pending NSSAI is not limited to the rejected NSSAI, and may be an NSSAI independent of the rejected NSSAI. 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 an S-NSSAI and a rejection reason value. The rejection reason value in this case may be "NSSAA is pending for the S-NSSAI" and may be information indicating that the S-NSSAI associated with the rejection reason value is prohibited or pending use by the UE until the NSSAA for that S-NSSAI is completed.

[0160] Furthermore, the pending NSSAI is valid in the entire registered PLMN. In other words, the UE and / or NW may treat the third rejected NSSAI and 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.

[0161] Moreover, 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, the UE does not initiate a registration request procedure for the S-NSSAI included in the pending NSSAI while storing the pending NSSAI. 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 identification information that includes one or more S-NSSAIs received from the core network in association with a rejection reason value indicating pending for the NSSAA. The pending NSSAI is information that is independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to transmit a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0162] A tracking area is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may be composed of multiple cells. Furthermore, a tracking area may be an area in which control messages such as paging are broadcast, or an area in which UE_A10 can move without performing a handover procedure. Furthermore, a tracking area may be a routing area, a location area, or anything similar 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.

[0163] A registration area (also called 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.

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

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

[0166] The S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. The core network and / or core network device may store the S-NSSAI requiring an NSSAA by associating the S-NSSAI with information indicating whether or not an NSSAA is required. The core network and / or core network device may further store the S-NSSAI requiring an NSSAA with information indicating whether or not the NSSAA has been completed, or information indicating that the NSSAA has been completed and is permitted or successful, in association with each other. The core network and / or core network device may manage the S-NSSAI requiring an NSSAA as information unrelated to the access network.

[0167] Also, a UE in single registration mode has only one active MM state. That is, a UE in single registration mode is only active in either the RM state (5GMM state) in 5GC or the EMM state in EPC. Also, a UE in single registration mode is in 5GC NAS mode when connecting to 5GC, and is in EPC NAS mode when connecting to EPC. Also, since a UE in single registration mode can only register to either 5GC or EPC, it is necessary to map EPS-GUTI (also called 4G-GUTI) and 5G-GUTI when moving between EPC and 5GC.

[0168] In addition, a UE in dual registration mode may be in a state where it can register independently with respect to the 5GC and the EPC. A UE in dual registration mode can independently maintain a 5G-GUTI and an EPS-GUTI (also referred to as a 4G-GUTI).

[0169] Also, the SNPN is a type of NPN that is a 5GS deployed for non-public use, and is an NPN that is operated by an NPN operator and does not depend on the NF provided by the PLMN. Also, the SNPN is identified by a combination of a PLMN ID and an NID (Network Identifier). Also, a UE that can use the SNPN may support an SNPN access mode (also referred to as an SNPN access operation mode). Also, a UE configured to operate in the SNPN access mode may be able to select an SNPN and register in the SNPN, but may not be able to select a PLMN. Also, a UE configured to operate in the SNPN access mode may be able to perform an SNPN selection procedure, but may not be able to perform a PLMN selection procedure. Also, even if a UE is available for SNPN (SNPN enabled), a UE that is not configured to operate in the SNPN access mode may not be able to select an SNPN and register in the SNPN, but may be able to select a PLMN. Also, a UE that is not configured to operate in the SNPN access mode may not be able to perform an SNPN selection procedure, but may be able to perform a PLMN selection procedure.

[0170] Also, a UE operating in the SNPN access mode may be able to select an SNPN via Uu (3GPP access). Also, a UE operating in the SNPN access mode may be able to select an SNPN via Uu or NWu established via a PDU session provided by a PLMN selected via Uu or NWu (non-3GPP access). Also, a UE not operating in the SNPN access mode may be able to select a PLMN via Uu or NWu established via a PDU session provided by a SNPN selected via Uu or NWu (non-3GPP access).

[0171] The SNPN access mode may be managed and / or applied on an access basis. That is, the SNPN access mode may be managed and / or applied separately for 3GPP access and non-3GPP access. In other words, activation or deactivation of the SNPN access mode for 3GPP access and activation or deactivation of the SNPN access mode for non-3GPP access may be independent. That is, when the SNPN access mode for 3GPP access is activated, the SNPN access mode for non-3GPP access may be activated or deactivated. Also, when the SNPN access mode for 3GPP access is deactivated, the SNPN access mode for non-3GPP access may be activated or deactivated.

[0172] Here, the SNPN access mode for 3GPP access may also be referred to as an SNPN access mode over 3GPP access or an SNPN access mode via 3GPP access.

[0173] In addition, the SNPN access mode for non-3GPP access may also be referred to as the SNPN access mode over non-3GPP access or the SNPN access mode via non-3GPP access.

[0174] Moreover, "activation" may be read as "operation", and "deactivation" may be read as "not operation". In other words, an SNPN access mode for 3GPP access being activated may mean operation in the SNPN access mode for 3GPP access. Moreover, an SNPN access mode for 3GPP access being deactivated may mean not operation in the SNPN access mode for 3GPP access. Moreover, an SNPN access mode for non-3GPP access being activated may mean operation in the SNPN access mode for non-3GPP access. Moreover, an SNPN access mode for non-3GPP access being deactivated may mean not operation in the SNPN access mode for non-3GPP access.

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

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

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

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

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

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

[0181] In addition, the SNPN to which the UE has successfully registered may be an RSNPN (Registered SNPN).

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

[0183] First, the first identification information is information indicating a network slice in which the UE wishes to register. The first identification information may be a Requested NSSAI (also referred to as a Requested NSSAI IE), which may be an NSSAI provided by the UE to the PLMN when registering to the network. The first identification information may include one or more S-NSSAIs. 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. In other words, the first identification information 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 above 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.

[0184] In addition, the S-NSSAI included in the first identification information may be an S-NSSAI that is not included in the rejected NSSAI and / or the pending NSSAI, and may be an S-NSSAI with an associated back-off timer not running.

[0185] In addition, the first identification information may not be the Requested NSSAI, but may be an S-NSSAI (requested S-NSSAI) included in the Requested NSSAI. In this case, the Requested NSSAI may be configured by one or more pieces of first identification information.

[0186] The first identification information may be configured to include at least one of the second and third identification information.

[0187] Moreover, the second identification information is UE capability information. Moreover, the second identification information may be 5GMM capability. Moreover, the second identification information may be information indicating whether or not the UE supports Extended rejected NSSAI (also referred to as Extended rejected NSSAI IE). Moreover, the second identification information may be information indicating whether or not the UE has a function of a fourth rejected NSSAI, and / or a fourth rejected S-NSSAI, and / or a mapped S-NSSAI for the fourth rejected NSSAI. Moreover, the second identification information may be information indicating whether or not the UE supports NSSAA.

[0188] The second identification information may include at least one of the first and third identification information.

[0189] Moreover, the third identification information is information indicating a request of the UE. Moreover, the third identification information may be information indicating whether or not to use the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the function of the mapped S-NSSAI for the fourth rejected NSSAI. Moreover, the third identification information may be information indicating a request for provision of information regarding whether or not there are available tracking areas and unavailable tracking areas in the current registration area.

[0190] The third identification information may be configured to include at least one of the first and second identification information.

[0191] The fourth identification information is information that includes at least one of the first to third identification information.

[0192] Furthermore, the eleventh identification information may be information indicating a network slice. Furthermore, the eleventh identification information may be an S-NSSAI. Furthermore, the eleventh identification information may be included in an allowed NSSAI, and / or a rejected NSSAI, and / or a pending NSSAI, and / or a configured NSSAI transmitted from the network, or may be transmitted from the network as information different from these.

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

[0194] Furthermore, the eleventh identification information may be the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI. Furthermore, if the eleventh identification information is the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI, it may be included in the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the configured NSSAI.

[0195] The eleventh identification information may be configured to include at least one of the twelfth and thirteenth identification information.

[0196] Also, the twelfth identification information may be a cause value. Also, the twelfth identification information may indicate one or more S-NSSAIs that are not available in the current tracking area. Also, the twelfth identification information may indicate that one or more S-NSSAIs are not available in the current tracking area in the current registration area. Also, the twelfth identification information may indicate that one or more S-NSSAIs are not available in the current tracking area in the current registration area. Also, the twelfth identification information may indicate that one or more S-NSSAIs are not available in the current tracking area in the current registration area, but are available in another tracking area in the current registration area. Also, the twelfth identification information may indicate that one or more S-NSSAIs are not available in the current tracking area in the current registration area, but are available in another tracking area in the current registration area. In addition, the one or more S-NSSAIs may be one or more S-NSSAIs indicated by the 11th identification information, or one or more S-NSSAIs included in the NSSAI indicated by the 11th identification information. In other words, the 11th identification information and the 12th identification information may correspond to each other.

[0197] Also, the 12th identification information may indicate an NSSAI that cannot be used in the current tracking area. Also, the 12th identification information may indicate that the NSSAI cannot be used in the current tracking area. Also, the 12th identification information may indicate an NSSAI that cannot be used in the current tracking area in the current registration area. Also, the 12th identification information may indicate that the NSSAI cannot be used in the current tracking area in the current registration area. Also, the 12th identification information may indicate an NSSAI that cannot be used in the current tracking area in the current registration area but can be used in another tracking area in the current registration area. Also, the 12th identification information may indicate that the NSSAI cannot be used in the current tracking area in the current registration area but can be used in another tracking area in the current registration area. Incidentally, the NSSAI may be an NSSAI indicated by the 11th identification information. In other words, the 11th identification information and the 12th identification information may correspond to each other.

[0198] In addition, the 12th identification information may indicate that there are no network slices (NS) available, or that the tracking area is not allowed, or that the tracking area is not available.

[0199] In addition, the 12th identification information may be included in a 5GMM (5G Mobility Management) cause (also referred to as a 5GMM reason value or a 5GMM rejection reason), or may be included in a cause (rejection reason; also referred to as a rejection cause) different from the 5GMM cause. In addition, the 12th identification information may be included in a rejected NSSAI (also referred to as a rejected NSSAI IE) and / or an extended rejected NSSAI IE.

[0200] The twelfth identification information may be configured to include at least one of the eleventh and thirteenth identification information.

[0201] Furthermore, the 13th identification information may be information indicating a network slice. Furthermore, the 13th identification information may be an S-NSSAI. Furthermore, the 13th identification information may be included in an allowed NSSAI, and / or a rejected NSSAI, and / or a pending NSSAI, and / or a configured NSSAI transmitted from the network, or may be transmitted from the network as information different from these. Furthermore, the 13th identification information may include a mapped S-NSSAI for the configured NSSAI.

[0202] The thirteenth identity information may be an NSSAI. The thirteenth identity information may be an allowed NSSAI, a rejected NSSAI, a pending NSSAI, a configured NSSAI, or an NSSAI different from these.

[0203] Furthermore, the thirteenth identification information may be the first to third rejected NSSAIs, and / or the first to third rejected S-NSSAIs, and / or a mapped S-NSSAI for the first to third rejected NSSAIs. Furthermore, if the thirteenth identification information is the first to third rejected S-NSSAIs, and / or a mapped S-NSSAI for the first to third rejected NSSAIs, it may be included in the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the configured NSSAI.

[0204] The thirteenth identification information may be configured to include at least one of the eleventh and twelfth identification information.

[0205] The fourteenth identification information is information that includes at least one of the eleventh to thirteenth identification information.

[0206] Furthermore, the first to fourth identification information and the eleventh to fourteenth identification information may be information that is pre-stored in the UE, and / or the base station, and / or the AMF, and / or a core network device other than the AMF, or some of these may be pre-stored and stored in conjunction with the transmission and reception of these identification information.

[0207] [3. First embodiment] First, procedures used in the first embodiment will be described. The procedures used in the first embodiment include a registration procedure, a configuration update procedure, a de-registration procedure, etc. Each procedure will be described below.

[0208] In the first 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 / function (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 / functions (i.e., different physical hardware, or different logical hardware, or different software). For example, data may be transmitted and received directly between them, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE.

[0209] [3.1. Registration Procedure] Next, the registration procedure will be described with reference to FIG. 6. In this chapter, this registration procedure may simply be referred to as this 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.

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

[0211] The UE may initiate the registration procedure when it moves to a TA outside the current registration area. In other words, the UE may initiate the registration procedure when it moves to a TA different from the TA indicated in the TA list held by the UE. Furthermore, the UE may initiate the registration procedure when the context of each device needs to be updated due to disconnection or invalidation of a PDU session. Furthermore, the UE may initiate the registration procedure when a change occurs in the capability information and / or preferences of the UE regarding the establishment of a PDU session. Furthermore, the UE may initiate the registration procedure periodically. Furthermore, the UE may initiate the registration procedure based on the completion of the registration procedure, the completion of the PDU session establishment procedure, or information received from the network in each procedure. Furthermore, the UE may initiate this procedure after performing the procedures in Chapters 3.1 to 3.3 one or more times. It should be noted that the UE may execute the registration procedure at any timing, not limited to these.

[0212] This procedure may also be performed in a PLMN (HPLMN or VPLMN), or an equivalent PLMN, or an SNPN, or an equivalent SNPN.

[0213] The above-mentioned procedure for the UE to transition from a state where it is not registered in the network (unregistered state) to a state where it is registered (registered state) may be an initial registration procedure or a registration procedure for initial registration. Also, the registration procedure executed when the UE is registered in the network (registered state) may be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0214] At the time of starting this procedure, the UE may or may not store each S-NSSAI and / or S-NSSAI described in Chapter 2.6. For example, the UE may or may not store the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI, and / or the configured NSSAI, and / or the mapped S-NSSAI for the configured NSSAI, and / or the mapped S-NSSAI for the allowed NSSAI, and / or the mapped S-NSSAI for the pending NSSAI, etc.

[0215] The details of the registration procedure described below are applicable to either of these.

[0216] First, the UE starts the registration procedure by transmitting a NAS message including a registration request message to the AMF (S600) (S602) (S604). Specifically, the UE transmits an RRC message including a registration request message to a base station device (also referred to as a 5G AN 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 base station device. 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.

[0217] Here, the UE can transmit the first to fourth identification information by including it in the registration request message and / or the RRC message. Here, the first to fourth identification information may be as described in Chapter 2.6. Furthermore, the UE may transmit the registration request message and / or the RRC message by including it in the identification information indicating the type of this procedure. Here, the identification information indicating the type of this procedure may be a 5GS registration type IE (Information Element). The 5GS registration type IE is information for indicating the type of registration requested, and may indicate initial registration, mobility registration updating, periodic registration updating, or emergency registration.

[0218] The UE may transmit these identification information by including them in a control message different from the above, for example, a control message of a layer lower than the RRC layer (for example, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Service Data Adaptation Protocol (SDAP) layer, etc.) Note that, by transmitting these identification information, the UE may indicate that the UE supports each function, may indicate a request of the UE, or may indicate both of these.

[0219] In addition, the UE may select or decide whether to transmit the first to fourth identification information to the network based on the UE's capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, and / or identification information transmitted or received in procedures performed prior to this procedure, etc.

[0220] The UE may store the allowed NSSAI, the configured NSSAI, the rejected NSSAI, and the mapped S-NSSAI.

[0221] The UE may also send at least one of the first to fourth identification information when it wants to indicate whether it has the capability of the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI.

[0222] The UE may include information other than the first to fourth identification information in the registration request message and / or the RRC 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).

[0223] In addition, if the 5GS registration type indicates mobility registration updating, and the purpose of initiating the registration procedure is not to change the network slice to which the UE is currently registered, and the UE is in the current registration area or the current tracking area, the UE does not need to include a requested NSSAI in the registration procedure.

[0224] In addition, when the UE sends a registration request message including a requested NSSAI, it may select an S-NSSAI included in the requested NSSAI from among the S-NSSAIs other than the S-NSSAI included in the fourth rejected NSSAI (fourth rejected S-NSSAI) and / or the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI that it has stored.

[0225] In addition, if the UE stores the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI, the UE may be prohibited from transmitting a registration request message and / or an RRC message including the S-NSSAI included in the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI in the current tracking area in the current registration area.

[0226] When the base station device 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 base station device may select an AMF based on identification information included in the registration request message and / or the RRC message. Specifically, when the base station device receives first to fourth identification information, the base station device may select an AMF to which the registration request message is to be transmitted based on the first to fourth identification information. Specifically, the base station device may select an AMF included in a network slice identified by the first to fourth identification information, or an AMF having connectivity to a network slice identified by the first to fourth identification information.

[0227] Note that the method of selecting AMF is not limited to this, and the base station device may select AMF based on other conditions.

[0228] The base station device extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S604). Note that, if the first to fourth 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 together with the registration request message (S604).

[0229] When the AMF receives the registration request message, the AMF may execute a first condition determination. The first condition determination is for determining whether the network accepts the request of the UE. When the AMF determines that the first condition determination is true, the AMF may execute the procedure from S610 to S612. Also, when the AMF determines that the first condition determination is false, the AMF may execute the procedure of S610.

[0230] In addition, the first condition determination may be performed by a network function (also referred to as NF) other than the AMF. When an NF other than the AMF performs the first condition determination, the AMF may provide the NF with information necessary to perform the first condition determination, specifically, at least a portion of the information received from the UE (S606). Then, when the NF determines whether the first condition determination is true or false based on the information received from the AMF, it may convey information including the result of the first condition determination (i.e., true or false) to the AMF. The AMF may determine the identification information and / or the control message to be transmitted to the UE based on the result of the first condition determination received from the NF.

[0231] In addition, 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 accept message or a Registration reject message.

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

[0233] For example, if the network does not permit or reject the request of the UE, the first condition determination may be determined as true, and if the network does not permit or reject the request of the UE, the first condition determination may be determined as false. If the network does not permit or reject some of the requests of the UE, even if there is a request of the UE that is not permitted, the first condition determination may be determined as true. If the network does not permit or reject all of the requests of the UE, the first condition determination may be determined as false. 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 determined as true, and if the network does not support the function requested by the UE, the first condition determination may be determined as false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be determined as true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be determined as false.

[0234] Furthermore, when there is an S-NSSAI that cannot be used in the current tracking area among one or more S-NSSAIs included in the requested NSSAI received from the UE, or when there is a current tracking area S-NSSAI in the current registration area, or when there is an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in another tracking area in the current registration area, the first condition determination may be determined to be false. However, even in such cases, the first condition determination may be determined to be true.

[0235] Also, when there is no available network slice (NS), or when the tracking area is not permitted, or when the tracking area is not available, the first condition determination may be determined as false. However, even in such cases, the first condition determination may be determined as true.

[0236] The AMF may transmit one or more of the identification information items 11 to 14 in the control message. Here, the identification information items 11 to 14 may be as described in Chapter 2.6. By transmitting these identification information items and / or the control message, the AMF 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 items are transmitted and received, two or more of these identification information items may be configured as one or more identification information items. Note that the information indicating the support of 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.

[0237] When the AMF receives a registration request message including the first to fourth identification information from the UE, it may send at least one of the eleventh to fourteenth identification information in a control message.

[0238] In addition, even if the AMF receives a registration request message from the UE that does not include identification information 1 to 4, the AMF may include at least one of the identification information 11 to 14 in the control message and send it.

[0239] The AMF may further include the configured NSSAI, and / or the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI in the control message and transmit it. Note that the eleventh to fourteenth identification information may be included in the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI and transmitted, or may be transmitted as information different from these.

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

[0241] In addition, the AMF may determine which of the identification information 11 to 14 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, and / or identification information sent and received in procedures performed prior to this procedure, etc.

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

[0243] In addition, when the AMF receives a registration request message from the UE including at least a part of the first to fourth identification information, and among one or more S-NSSAIs included in the first identification information, there is an S-NSSAI that cannot be used in the current tracking area, or there is a current tracking area S-NSSAI in the current registration area, or there is an S-NSSAI that cannot be used in the current tracking area in the current registration area but is available in other tracking areas in the current registration area, or there is no available network slice (NS), or the tracking area is not permitted, or the tracking area is not available, the AMF may send at least one of the eleventh to fourteenth identification information in a control message.

[0244] In addition, when the UE transmits a registration request message including capability information indicating that the UE does not support the NSSAA and a requested NSSAI, if the S-NSSAI included in the requested NSSAI is an S-NSSAI related to the NSSAA, the AMF may transmit at least one of the eleventh to fourteenth identities in a control message. Here, the S-NSSAI may be included in the eleventh identity, the thirteenth identity, or the fourteenth identity.

[0245] The UE receives the control message (registration acceptance message or registration rejection message) and / or the transmitted identification information items 11 to 14 via the base station device (S610). If the control message is a registration acceptance message, the UE can recognize, by receiving the registration acceptance message, that the UE's request in the registration request message has been accepted and the contents of the various identification information included in the registration acceptance message. If the control message is a registration rejection message, the UE can recognize, by receiving the registration rejection message, that the UE's request in the registration request message has been rejected and the contents of the various identification information included in the registration rejection message.

[0246] In addition, when the UE receives at least some of the 11th to 14th identification information from the core network (for example, when the 11th identification information and the 12th identification information are received), and the 11th identification information includes an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area, the UE may store the S-NSSAI included in the rejected NSSAI among the rejected NSSAI for the current tracking area in the memory unit of the UE. Furthermore, when the UE receives at least a part of the eleventh to fourteenth identification information from the core network (for example, when the eleventh identification information and the twelfth identification information are received), and the eleventh identification information includes an S-NSSAI that cannot be used in the current tracking area in the current registration area and can be used in other tracking areas in the current registration area, the UE may store the S-NSSAI included in the rejected NSSAI for the current tracking area in a memory unit of the UE based on a reason value indicated by the twelfth identification information. Then, while the S-NSSAI is stored in the rejected NSSAI for the current tracking area in the memory unit of the UE, use of the S-NSSAI in the current tracking area may be prohibited.

[0247] In addition, if the rejected NSSAI for the current tracking area in the UE's memory stores an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area, the UE may include an S-NSSAI other than that S-NSSAI in the requested NSSAI and send a registration request message including the requested NSSAI.

[0248] In addition, when an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area is stored among the rejected NSSAIs for the current tracking area in the memory unit of the UE, if the UE receives 11th identification information indicating a new allowed NSSAI for the current PLMN or SNPN, the S-NSSAI included in the new allowed NSSAI may be deleted from the rejected NSSAI for the current tracking area in the memory unit of the UE.

[0249] In addition, when the UE receives the 11th identification information and / or the 13th identification information, and the 11th identification information and / or the 13th identification information are allowed NSSAIs, the UE may recognize that the use of the S-NSSAI included in the allowed NSSAI is permitted, and / or that registration to the network is permitted, and / or that the UE's request is permitted.

[0250] Furthermore, when the UE receives at least a part of the 11th to 14th identification information (for example, when the 11th identification information and the 12th identification information are received), the UE may recognize that the 12th identification information corresponds to the 11th identification information. In other words, the UE may recognize that the fourth rejected NSSAI, the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI indicated by the 11th identification information is unavailable in the current tracking area, and / or unavailable in the current tracking area in the current registration area, and / or unavailable in the current tracking area in the current registration area but available in another tracking area in the current registration area, and / or there is no available network slice (NS), and / or the UE is an unauthorized tracking area, and / or the UE is an unavailable tracking area.

[0251] In addition, when the UE receives at least some of the 11th to 14th identification information (for example, when the 11th identification information and the 13th identification information are received), and the 11th identification information and / or the 13th identification information are the first rejected NSSAI, and / or the first rejected S-NSSAI, and / or the mapped S-NSSAI for the first rejected NSSAI, the UE may recognize that use of the first rejected NSSAI is prohibited in the current PLMN or SNPN.

[0252] Furthermore, when the UE receives at least some of the 11th to 14th identities (for example, when the 11th identity and the 13th identity are received), and the 11th identity and / or the 13th identity are the second rejected NSSAI, and / or the second rejected S-NSSAI, and / or the mapped S-NSSAI for the second rejected NSSAI, the UE may recognize that the use of the second rejected NSSAI, and / or the second rejected S-NSSAI, and / or the mapped S-NSSAI for the second rejected NSSAI is prohibited in the current registration area for the access for which the 11th identity and / or the 13th identity were received.

[0253] In addition, when the UE receives at least some of the 11th to 14th identities (e.g., when the 11th identity and the 13th identity are received), and the 11th identity and / or the 13th identity are the third rejected NSSAI and / or the third rejected S-NSSAI, the UE may recognize that the use of the third rejected NSSAI is prohibited because the NSSAA has failed or been revoked.

[0254] Furthermore, when the UE receives at least a portion of the eleventh to fourteenth identification information, where the eleventh identification information is the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI, and the thirteenth identification information is the first to third rejected NSSAI and / or the first to third rejected S-NSSAI and / or the mapped S-NSSAI for the first to third rejected NSSAI, the UE may The S-NSSAI and the S-NSSAI may be managed and / or stored separately.

[0255] In addition, when storing the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI, the UE may manage and / or store the 11th identification information only for the access for which it received the 11th identification information.

[0256] Furthermore, when the UE is provided with a new configured NSSAI for the current PLMN or SNPN, the UE may replace the stored configured NSSAI with the new configured NSSAI. In this case, the UE may further delete the mapped S-NSSAI for the stored configured NSSAI and store the mapped S-NSSAI for the new configured NSSAI, may delete the stored fourth rejected NSSAI, or may delete the S-NSSAI included in the mapped S-NSSAI for the new configured NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0257] Furthermore, when the UE receives a new allowed NSSAI for the current PLMN or SNPN, the UE may delete the S-NSSAI included in the new allowed NSSAI from the stored fourth rejected NSSAI. In this case, the UE may further delete the S-NSSAI included in the mapped S-NSSAI for the new allowed NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0258] In addition, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message, based on the reason for rejection, the UE may store the received fourth rejected S-NSSAI in the rejected NSSAI and the mapped S-NSSAI for the rejected NSSAI, or may store the fourth rejected NSSAI and the mapped S-NSSAI for the fourth rejected NSSAI.

[0259] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message, and the S-NSSAI is included in a rejected NSSAI IE (also referred to as a rejected NSSAI), the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0260] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message when not roaming, and the S-NSSAI is included in an Extended rejected NSSAI IE (also referred to as an Extended rejected NSSAI), the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0261] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message during roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0262] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message when not roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0263] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message during roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the allowed NSSAI stored by the UE.

[0264] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message and the S-NSSAI is included in the Rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0265] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0266] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0267] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a control message during roaming, and the S-NSSAI is included in an Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the pending NSSAI stored by the UE.

[0268] In addition, when the UE moves from the tracking area in which it received the fourth rejected NSSAI or the fourth rejected S-NSSAI to another tracking area, it may delete the fourth rejected NSSAI and / or its access type stored by the UE.

[0269] In addition, when the UE transitions from the 5GMM-DEREGISTERED state to the 5GMM-REGISTERED state, the UE may delete the fourth rejected NSSAI and / or its access type stored in the UE.

[0270] Furthermore, the UE that has received the fourth rejected NSSAI included in the control message may perform an operation based on the rejection reason included in the rejected S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI. For example, the UE may be prohibited from using the fourth S-NSSAI in the current tracking area. That is, the UE may be in a state in which the MM procedure and / or the SM procedure using the fourth S-NSSAI is prohibited in the current tracking area.

[0271] Furthermore, when the UE receives a first rejected NSSAI, it may store the received first rejected NSSAI in a first rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives a second rejected NSSAI, it may store the received second rejected NSSAI in a second rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives a third rejected NSSAI, it may store the received third rejected NSSAI in a third rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI, the UE may store the received fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI in the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI in the storage unit of the UE. In other words, the first rejected NSSAI and / or the second rejected NSSAI and / or the third rejected NSSAI and / or the fourth rejected NSSAI may be managed and / or stored separately.

[0272] In addition, when the UE receives a fourth rejected NSSAI and / or a fourth rejected S-NSSAI and / or a mapped S-NSSAI for the fourth rejected NSSAI, it may store them in the first rejected NSSAI and / or the second rejected NSSAI and / or the third rejected NSSAI in the memory unit of the UE, and may manage and / or store them together with information indicating that the received fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI are not available in the current tracking area, or in the current tracking area in the current registration area, or in the current tracking area in the current registration area but can be used in another tracking area in the current registration area.

[0273] The UE may also determine, based on the received twelfth identification information, where to store the received fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI in the UE's memory among the first rejected NSSAI, and / or the second rejected NSSAI, and / or the third rejected NSSAI, and / or the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI.

[0274] If the control message is a registration accept message, the UE can further transmit a registration completion message to the AMF via the base station device as a response message to the registration accept message (S612). Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but may be included in an RRC message and transmitted and received between the UE and the base station device.

[0275] The AMF receives a registration completion message via the base station device (S612). Furthermore, each device completes this procedure based on the transmission and reception of the registration acceptance message and / or the registration completion message.

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

[0277] 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 performed based on transmission / reception of a registration completion message or completion of the registration procedure.

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

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

[0280] In addition, each device may store the information transmitted and received in this procedure in association with each other.

[0281] [3.2. Setting Update Procedure] Next, the configuration update procedure (also referred to as generic UE configuration update procedure) will be described with reference to FIG. 7. In the procedure of Chapter 3.1, when each device including the UE transmits and receives a registration acceptance message and / or a NAS message, and the UE is registered in the network, this procedure (configuration update procedure) may be initiated when the AMF wishes to change the configuration of the UE. Note that this procedure may be executed via the same access as the access that executed the procedure of Chapter 3.1. The UE may also initiate this procedure after executing the procedures of Chapters 3.1 to 3.2 one or more times. The AMF may also initiate this procedure when there is a change in the state of the NSSAI, and / or S-NSSAI, and / or mapped S-NSSAI, etc., that have already been notified to the UE.

[0282] This procedure may also be performed in a PLMN (HPLMN or VPLMN), or an equivalent PLMN, or an SNPN, or an equivalent SNPN.

[0283] At the time of starting this procedure, the UE may or may not store each S-NSSAI and / or S-NSSAI described in Chapter 2.6. For example, the UE may or may not store the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI, and / or the configured NSSAI, and / or the mapped S-NSSAI for the configured NSSAI, and / or the mapped S-NSSAI for the allowed NSSAI, and / or the mapped S-NSSAI for the pending NSSAI, etc.

[0284] This procedure is started by the AMF sending a configuration update command to the UE through the access network (S800 in FIG. 7). Note that the configuration update command may include at least one of the eleventh to fourteenth identification information.

[0285] Furthermore, the AMF may determine which of the identification information 11 to 14 to include in the configuration update command 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, and / or identification information sent and received in procedures performed prior to this procedure, etc.

[0286] For example, the AMF may include at least one of the 11th to 14th identification information when there is a change in the status of the NSSAI, and / or the S-NSSAI, and / or the mapped S-NSSAI, etc., that have already been notified to the UE.

[0287] The AMF may cause the UE to update its configuration by sending a configuration update command to the UE via the access network, the configuration update command including at least a portion of the eleventh to fourteenth identification information.

[0288] The UE can also update the UE's configuration by receiving a configuration update command from the AMF that includes at least a portion of the 11th to 14th identification information.

[0289] In addition, when the UE receives a configuration update command from the AMF, the UE can recognize the contents of each identification information included in the configuration update command. Then, the UE may determine the behavior of the UE based on the reception of the configuration update command and / or each identification information.

[0290] In addition, when the UE receives at least some of the 11th to 14th identification information from the core network (for example, when the 11th identification information and the 12th identification information are received), and the 11th identification information includes an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area, the UE may store the S-NSSAI included in the rejected NSSAI among the rejected NSSAI for the current tracking area in the memory unit of the UE. Furthermore, when the UE receives at least a part of the eleventh to fourteenth identification information from the core network (for example, when the eleventh identification information and the twelfth identification information are received), and the eleventh identification information includes an S-NSSAI that cannot be used in the current tracking area in the current registration area and can be used in other tracking areas in the current registration area, the UE may store the S-NSSAI included in the rejected NSSAI for the current tracking area in a memory unit of the UE based on a reason value indicated by the twelfth identification information. Then, while the S-NSSAI is stored in the rejected NSSAI for the current tracking area in the memory unit of the UE, use of the S-NSSAI in the current tracking area may be prohibited.

[0291] In addition, if the rejected NSSAI for the current tracking area in the UE's memory stores an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area, the UE may include an S-NSSAI other than that S-NSSAI in the requested NSSAI and send a registration request message including the requested NSSAI.

[0292] In addition, in the rejected NSSAI for the current tracking area in the memory unit of the UE, an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area is stored, and when the UE receives a new allowed NSSAI for the current PLMN or SNPN, the S-NSSAI included in the new allowed NSSAI may be deleted from the rejected NSSAI for the current tracking area in the memory unit of the UE.

[0293] Furthermore, when the UE is provided with a new configured NSSAI for the current PLMN or SNPN, the UE may replace the stored configured NSSAI with the new configured NSSAI. In this case, the UE may further delete the mapped S-NSSAI for the stored configured NSSAI and store the mapped S-NSSAI for the new configured NSSAI, may delete the stored fourth rejected NSSAI, or may delete the S-NSSAI included in the mapped S-NSSAI for the new configured NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0294] Furthermore, when the UE receives a new allowed NSSAI for the current PLMN or SNPN, the UE may delete the S-NSSAI included in the new allowed NSSAI from the stored fourth rejected NSSAI. In this case, the UE may further delete the S-NSSAI included in the mapped S-NSSAI for the new allowed NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0295] In addition, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message, based on the reason for rejection, the UE may store the received fourth rejected S-NSSAI in the rejected NSSAI and the mapped S-NSSAI for the rejected NSSAI, or may store the fourth rejected NSSAI and the mapped S-NSSAI for the fourth rejected NSSAI.

[0296] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message and the S-NSSAI is included in the Rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0297] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0298] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message during roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0299] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message when not roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0300] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message during roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the allowed NSSAI stored by the UE.

[0301] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message and the S-NSSAI is included in the Rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0302] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0303] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0304] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a configuration update command message during roaming, and the S-NSSAI is included in an Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the pending NSSAI stored by the UE.

[0305] In addition, when the UE moves from the tracking area in which it received the fourth rejected NSSAI or the fourth rejected S-NSSAI to another tracking area, it may delete the fourth rejected NSSAI and / or its access type stored by the UE.

[0306] Furthermore, the UE that has received the fourth rejected NSSAI included in the configuration update command message may perform an operation based on the rejection reason included in the rejected S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI. For example, the UE may be prohibited from using the fourth S-NSSAI in the current tracking area. That is, the UE may be in a state in which the MM procedure and / or the SM procedure using the fourth S-NSSAI is prohibited in the current tracking area.

[0307] Furthermore, when the UE receives a first rejected NSSAI, it may store the received first rejected NSSAI in a first rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives a second rejected NSSAI, it may store the received second rejected NSSAI in a second rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives a third rejected NSSAI, it may store the received third rejected NSSAI in a third rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI, the UE may store the received fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI in the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI in the storage unit of the UE. In other words, the first rejected NSSAI and / or the second rejected NSSAI and / or the third rejected NSSAI and / or the fourth rejected NSSAI may be managed and / or stored separately.

[0308] In addition, when the UE receives a fourth rejected NSSAI and / or a fourth rejected S-NSSAI and / or a mapped S-NSSAI for the fourth rejected NSSAI, it may store them in the first rejected NSSAI and / or the second rejected NSSAI and / or the third rejected NSSAI in the memory unit of the UE, and may manage and / or store them together with information indicating that the received fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI are not available in the current tracking area, or in the current tracking area in the current registration area, or in the current tracking area in the current registration area but can be used in another tracking area in the current registration area.

[0309] The UE may also determine, based on the received twelfth identification information, where to store the received fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI in the UE's memory among the first rejected NSSAI, and / or the second rejected NSSAI, and / or the third rejected NSSAI, and / or the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI.

[0310] In addition, each device may store the information transmitted and received in this procedure in association with each other.

[0311] The UE may also complete this procedure by receiving a configuration update command from the AMF.

[0312] [3.3. Non-registration Procedures] Next, the network-initiated deregistration procedure will be described with reference to FIG. 8. Hereinafter, the network-initiated deregistration procedure will also be referred to as this procedure. The deregistration procedure may be a procedure for deregistering a UE registered in a network (access network, and / or core network, and / or DN). In other words, the AMF may execute the deregistration procedure when the UE is in a state registered in the network (RM-REGISTERED state or 5GMM-REGISTEDED state). In addition, this procedure may be started after the procedures in Chapters 3.1 and 3.2 are executed one or more times. Here, a case will be described in which the deregistration procedure is executed via the same access as the access that executed the procedures in Chapters 3.1 and 3.2. In addition, the AMF may start this procedure when there is a change in the state of the NSSAI, and / or S-NSSAI, and / or mapped S-NSSAI, etc., that have already been notified to the UE.

[0313] This procedure may also be performed in a PLMN (HPLMN or VPLMN), or an equivalent PLMN, or an SNPN, or an equivalent SNPN.

[0314] At the time of starting this procedure, the UE may or may not store each S-NSSAI and / or S-NSSAI described in Chapter 2.6. For example, the UE may or may not store the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI, and / or the configured NSSAI, and / or the mapped S-NSSAI for the configured NSSAI, and / or the mapped S-NSSAI for the allowed NSSAI, and / or the mapped S-NSSAI for the pending NSSAI, etc.

[0315] The AMF starts this procedure by sending a deregistration request message to the UE via an access network (3GPP access or non-3GPP access) (S900). Here, the deregistration request message is a NAS message transmitted and received on the N1 interface, but is actually a message that the AMF sends to the UE via a base station device included in the access network.

[0316] The AMF may also send the non-registration request message including at least one of the 11th to 14th identification information.

[0317] Furthermore, the AMF may determine which of the identification information 11 to 14 to include in the non-registration request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, and / or identification information sent and received in procedures performed prior to this procedure, etc.

[0318] For example, the AMF may include at least one of the 11th to 14th identification information when there is a change in the status of the NSSAI, and / or the S-NSSAI, and / or the mapped S-NSSAI, etc., that have already been notified to the UE.

[0319] When the UE receives a non-registration request message from the AMF, the UE may recognize the contents of each identification information included in the non-registration request message. Then, the UE may determine the behavior of the UE based on the reception of the non-registration request message and / or each identification information.

[0320] That is, the UE may transition its registration state to an unregistered state and / or release the PDU sessions established in the PLMN, either during or after the procedure is completed.

[0321] In addition, when the UE receives at least some of the 11th to 14th identification information from the core network (for example, when the 11th identification information and the 12th identification information are received), and the 11th identification information includes an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area, the UE may store the S-NSSAI included in the rejected NSSAI among the rejected NSSAI for the current tracking area in the memory unit of the UE. Furthermore, when the UE receives at least a part of the eleventh to fourteenth identification information from the core network (for example, when the eleventh identification information and the twelfth identification information are received), and the eleventh identification information includes an S-NSSAI that cannot be used in the current tracking area in the current registration area and can be used in other tracking areas in the current registration area, the UE may store the S-NSSAI included in the rejected NSSAI for the current tracking area in a memory unit of the UE based on a reason value indicated by the twelfth identification information. Then, while the S-NSSAI is stored in the rejected NSSAI for the current tracking area in the memory unit of the UE, use of the S-NSSAI in the current tracking area may be prohibited.

[0322] In addition, if the rejected NSSAI for the current tracking area in the UE's memory stores an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area, the UE may include an S-NSSAI other than that S-NSSAI in the requested NSSAI and send a registration request message including the requested NSSAI.

[0323] In addition, in the rejected NSSAI for the current tracking area in the memory unit of the UE, an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area is stored, and when the UE receives a new allowed NSSAI for the current PLMN or SNPN, the S-NSSAI included in the new allowed NSSAI may be deleted from the rejected NSSAI for the current tracking area in the memory unit of the UE.

[0324] Furthermore, when the UE is provided with a new configured NSSAI for the current PLMN or SNPN, the UE may replace the stored configured NSSAI with the new configured NSSAI. In this case, the UE may further delete the mapped S-NSSAI for the stored configured NSSAI and store the mapped S-NSSAI for the new configured NSSAI, may delete the stored fourth rejected NSSAI, or may delete the S-NSSAI included in the mapped S-NSSAI for the new configured NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0325] Furthermore, when the UE receives a new allowed NSSAI for the current PLMN or SNPN, the UE may delete the S-NSSAI included in the new allowed NSSAI from the stored fourth rejected NSSAI. In this case, the UE may further delete the S-NSSAI included in the mapped S-NSSAI for the new allowed NSSAI for the current PLMN or SNPN from the mapped S-NSSAI for the stored fourth rejected NSSAI.

[0326] In addition, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message, based on the reason for rejection, the UE may store the received fourth rejected S-NSSAI in the rejected NSSAI and the mapped S-NSSAI for the rejected NSSAI, or may store it in the fourth rejected NSSAI and the mapped S-NSSAI for the fourth rejected NSSAI.

[0327] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message and the S-NSSAI is included in the Rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0328] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0329] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message during roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0330] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message when not roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the allowed NSSAIs for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN stored by the UE.

[0331] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message during roaming, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the allowed NSSAI stored by the UE.

[0332] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message and the S-NSSAI is included in the Rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0333] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0334] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message when not roaming, and the S-NSSAI is included in the Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the pending NSSAIs for the current PLMN or SNPN and its equivalent PLMN or SNPN stored by the UE.

[0335] Furthermore, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) included in a rejected NSSAI (fourth rejected NSSAI) included in a non-registration request message during roaming, and the S-NSSAI is included in an Extended rejected NSSAI IE, the UE may delete the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI associated with the same access type from the mapped S-NSSAI for the pending NSSAI stored by the UE.

[0336] In addition, when the UE deregisters via the access for which it received the fourth rejected NSSAI or the fourth rejected S-NSSAI, in other words, when the UE completes the deregistration procedure via that access, it may delete the fourth rejected NSSAI and / or its access type stored by the UE.

[0337] In addition, when the UE moves from the tracking area in which it received the fourth rejected NSSAI or the fourth rejected S-NSSAI to another tracking area, it may delete the fourth rejected NSSAI and / or its access type stored by the UE.

[0338] In addition, when the UE transitions from the 5GMM-REGISTERED state to the 5GMM-DEREGISTERED state, the UE may delete the fourth rejected NSSAI and / or its access type stored in the UE.

[0339] Furthermore, the UE that has received the fourth rejected NSSAI included in the non-registration request message may perform an operation based on the reason for rejection included in the rejected S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI. For example, the UE may be prohibited from using the fourth S-NSSAI in the current tracking area. That is, the UE may be in a state in which the MM procedure and / or the SM procedure using the fourth S-NSSAI is prohibited in the current tracking area.

[0340] Furthermore, when the UE receives a first rejected NSSAI, it may store the received first rejected NSSAI in a first rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives a second rejected NSSAI, it may store the received second rejected NSSAI in a second rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives a third rejected NSSAI, it may store the received third rejected NSSAI in a third rejected NSSAI in a storage unit of the UE. Furthermore, when the UE receives the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI, the UE may store the received fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI in the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI in the storage unit of the UE. In other words, the first rejected NSSAI and / or the second rejected NSSAI and / or the third rejected NSSAI and / or the fourth rejected NSSAI may be managed and / or stored separately.

[0341] In addition, when the UE receives a fourth rejected NSSAI and / or a fourth rejected S-NSSAI and / or a mapped S-NSSAI for the fourth rejected NSSAI, it may store them in the first rejected NSSAI and / or the second rejected NSSAI and / or the third rejected NSSAI in the memory unit of the UE, and may manage and / or store them together with information indicating that the received fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapped S-NSSAI for the fourth rejected NSSAI are not available in the current tracking area, or in the current tracking area in the current registration area, or in the current tracking area in the current registration area but can be used in another tracking area in the current registration area.

[0342] The UE may also determine, based on the received twelfth identification information, where to store the received fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI in the UE's memory among the first rejected NSSAI, and / or the second rejected NSSAI, and / or the third rejected NSSAI, and / or the fourth rejected NSSAI, and / or the fourth rejected S-NSSAI, and / or the mapped S-NSSAI for the fourth rejected NSSAI.

[0343] Then, the UE that has received the deregistration request message may send a deregistration accept message to the AMF (S902). Here, the deregistration accept message is a NAS message transmitted and received on the N1 interface, but is actually a message that the UE sends to the AMF via the access network.

[0344] 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 deregistration acceptance message. In other words, each device may transition to a state in which the UE is not registered in the network for the access in which the deregistration acceptance message is transmitted or received.

[0345] Each device may also complete this procedure based on sending and receiving a non-registration acceptance message.

[0346] In addition, the state transition in each device may be performed based on the completion of this procedure. That is, based on the completion of the deregistration procedure, each device may transition to a state in which the UE is not registered in the network. In other words, each device may transition to a state in which the UE is not registered in the network for the access that has executed the deregistration procedure.

[0347] In addition, each device may store the information transmitted and received in this procedure in association with each other.

[0348] In addition, a UE in an unregistered state may perform the procedures in Chapter 3.1 for the same access or a different access for which it performed the unregistration procedure or sent or received a unregistration acceptance message.

[0349] [4. Modifications] A program that operates on an apparatus according to one aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment 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.

[0350] A program for implementing the functions of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. 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 be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that can be read by a computer.

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

[0352] The present invention is not limited to the above-mentioned embodiment. In the embodiment, one example of the device is described, but one aspect of 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.

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

[0354] 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 170 N3IWF 190 Core Network_B

Claims

[Claim 1] A UE (User Equipment) including a transceiver unit, a control unit, and a storage unit, In the storage unit, an S-NSSAI that cannot be used in the current tracking area in the current registration area but can be used in other tracking areas in the current registration area is stored in the rejected NSSAI for the current tracking area, When the transceiver receives a new allowed NSSAI for a current PLMN or SNPN, The control unit deletes an S-NSSAI included in the allowed NSSAI from a rejected NSSAI for the current tracking area in the storage unit. The UE is characterized by:

Images