User equipment (UE)

Abstract

The present invention provides a communication method for implementing a function related to management of information on a network slice or a non-public network function in a 5GS. A method of initial login of a UE, a periodic or mobile-based login procedure, and a communication method are provided for implementing management of information about a network slice or a non-public network function in a 5GS. The invention further provides a method for setting the updating process with the UE after the login process is completed and a communication method. A method of managing information about network slices accompanying each process and state transition is also provided.

Description

Technical Field

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

[0002] In 3GPP (3rd Generation Partnership Project) which is carrying out standardization activities of mobile communication systems in recent years, SAE (System Architecture Evolution) which is a system framework of LTE (Long Term Evolution) is being studied.

[0003] In addition, in recent years, 3GPP has also conducted research on the next-generation communication technology and system architecture of the 5G (5th Generation) mobile communication system, which is the next-generation mobile communication system. In particular, 5GS (5G System) has been standardized as a system for implementing the 5G mobile communication system (see Non-Patent Document 1). In 5GS, technical issues for connecting various terminals to cellular networks are extracted and solutions are standardized. Prior art literature Non-patent literature

[0004] Non-patent literature 1: 3GPP TS24.501V17.7.1 (2022-06); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) Non-patent document 2: 3GPP TR 23.700-41V0.3.0(2022-05); 3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Study on enhancement of network slicing; Phase 3(Release 18) Summary of the invention Problem that the invention aims to solve

[0005] In 5GS (5G System), in order to provide various services, research is being conducted on 5GCN (5G Core Network) as a new core network.

[0006] Moreover, in 5G, network slices are defined as logical networks that provide specific network functions and specific network characteristics for specific service types and specific groups. For example, a network slice can be a logical network provided to a terminal with a low-latency function or a logical network provided to a sensor terminal for IoT (Internet of Things).

[0007] In addition, in order to study further functions related to network slicing, 3GPP is studying eNS (Enhancement of Network Slicing). In 3GPP, as a phase 3 study of eNS, the regulation of network slicing that is valid only in a specific area and / or time is studied.

[0008] However, practical methods for meeting the above requirements are still unclear.

[0009] The present invention is completed in view of the above situation and provides a method for implementing the functions used by NS in 5GS. Technical Solution

[0010] A UE (User Equipment) according to one embodiment of the present invention is characterized in that it comprises a control unit, a transceiver unit and a storage unit, wherein the transceiver unit receives a first S-NSSAI (Single Network Slice Selection Assistance Information) and a first TA (Tracking Area) list, and in the storage unit, when the first S-NSSAI is associated with a second TA list and stored in NSSAI (Network Slice Selection Assistance Information), the control unit replaces the TA list associated with the first S-NSSAI from the second TA list to the first TA list.

[0011] A UE (User Equipment) according to an embodiment of the present invention is characterized in that it includes a control unit, a transceiver unit, and a storage unit. The UE is characterized in that: The transceiver unit receives a first S-NSSAI (Single Network Slice Selection Assistance Information) and a first TA (Tracking Area) list. In the storage unit, when the first S-NSSAI is associated with a second TA list and stored in NSSAI (Network Slice Selection Assistance Information), the control unit adds a TAI (Tracking Area Identity) included in the first TA list to the list of the second TA associated with the first S-NSSAI. Beneficial Effects

[0012] According to the present invention, the function of allowing or not allowing network slicing under specific conditions can be supported in the PLMN and SNPN of 5GS. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 This is a diagram illustrating the outline of a mobile communication system (EPS / 5GS). Figure 2 This is a diagram illustrating the detailed structure of the mobile communication system (EPS / 5GS). Figure 3 This is a diagram illustrating the device structure of UE. Figure 4 This is a diagram illustrating the structure of the access network device (gNB) in 5GS. Figure 5 This is a diagram that illustrates the structure of the core network device (AMF / SMF / UPF) in 5GS. Figure 6 This is a diagram for explaining the login process. Figure 7 This is a diagram illustrating the process of changing / updating the UE settings. DETAILED DESCRIPTION

[0014] Hereinafter, the best mode for carrying out the present invention will be described with reference to the accompanying drawings. It should be noted that in this embodiment, an embodiment of a mobile communication system in which the present invention is applied will be described as an example. [1. System Overview]

[0015] first, Figure 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment. Figure 2 It is a diagram for explaining the detailed structure of the mobile communication system 1.

[0016] exist Figure 1 It is recorded that the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network: packet data network)_A5, access network_B120, core network_B190, and DN (Data Network: data network)_A6.

[0017] In the following, these devices / functions may be recorded with omitted symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0018] In addition, Figure 2 The following devices / functions are recorded: UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170 and other devices / functions as well as interfaces connecting these devices / functions to each other.

[0019] In the following, for these devices / functions, symbols are sometimes omitted, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0020] It should be noted that the EPS (Evolved Packet System) as a 4G system is composed of an access network_A and a core network_A, but may further include UE and / or PDN. In addition, the 5GS (5G System) as a 5G system is composed of a UE, an access network_B and a core network_B, but may further include a DN.

[0021] UE is a device that can connect to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (non-3GPP access, also known as non-3GPP access network, non-3GPP AN). UE can be a terminal device that can perform wireless communication, such as a portable phone or a smart phone, or a terminal device that can connect to EPS or 5GS. UE can have UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that UE can be expressed as a user device or as a terminal device.

[0022] In addition, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in E-UTRAN. It should be noted that, in the following, eNB45 is sometimes recorded by omitting the symbol like eNB. In addition, when there are multiple eNBs, each eNB is connected to each other, for example, via an X2 interface. In addition, one or more access points are configured in the wireless LAN access network.

[0023] In addition, access network_B corresponds to the 5G access network (5G AN). 5G AN is composed of NG-RAN (NG Radio Access Network: NG wireless access network) and / or non-3GPP access network. One or more gNB (NRNodeB: NR Node B) 122 are configured in NG-RAN. It should be noted that, below, the gNB122 is sometimes recorded with omitted symbols, such as eNB. The gNB is a node that provides the NR (New Radio: New Radio) user plane and control plane to the UE, and is a node connected to the 5GCN via the NG interface (including the N2 interface or the N3 interface). That is, the gNB is a base station device redesigned for 5GS, and has different functions from the base station device (eNB) used in the EPS as a 4G system. In addition, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

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

[0025] NG-RAN refers to the radio access network connected to 5GCN, which can also use NR or E-UTRA or both. In other words, NG-RAN can also be E-UTRAN.

[0026] In addition, below, E-UTRAN and NG-RAN are sometimes referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN are sometimes referred to as non-3GPP access. In addition, nodes configured in access network_B are sometimes collectively referred to as NG-RAN nodes.

[0027] In addition, in the following, access network_A and / or access network_B and / or the device included in access network_A and / or the device included in access network_B are sometimes referred to as access networks or access network devices.

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

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

[0030] In addition, below, core network_A and / or core network_B, devices included in core network_A and / or devices included in core network_B are sometimes referred to as core networks or core network devices or devices within the core network.

[0031] The core network (core network_A and / or core network_B) can be an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator; MNO) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN, or it can be a core network used by a mobile communication operator that operates and manages the mobile communication system 1, or it can be a core network used by virtual mobile communication operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).

[0032] The core network (core network_A and / or core network_B) and the access network (access network_A and / or access network_B) may be different for each mobile communication operator.

[0033] In addition, Figure 1 The case where PDN and DN are the same is recorded in the text, but they can also be different. PDN can be a DN (Data Network) that provides communication services to UE. It should be noted that DN can be constructed as a packet data service network or for each service. Moreover, PDN can include connected communication terminals. Therefore, connection with PDN can be connection with communication terminals and server devices configured in PDN. Moreover, sending and receiving user data with PDN can also be sending and receiving user data with communication terminals and server devices configured in PDN. It should be noted that PDN can be expressed as DN, and DN can also be expressed as PDN.

[0034] In addition, hereinafter, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein are sometimes referred to as a network or a network device. That is, the network and / or network device sending and receiving messages and / or executing a process means that at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein send and receive messages and / or execute a process.

[0035] In addition, the UE can be connected to the access network. In addition, the UE can be connected to the core network via the access network. Moreover, the UE can be connected to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data between the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication can be used, but also non-IP communication can be used.

[0036] Here, IP communication refers to data communication using IP, in which data is sent and received through IP packets. An IP packet consists of an IP header and a payload portion. The payload portion may include data sent and received by devices / functions included in EPS and devices / functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, in which data is sent and received in a form different from the structure of IP packets. For example, non-IP communication may be data communication achieved by sending and receiving application data that is not assigned an IP header, or may be assigned other headers such as a MAC header, Ethernet (registered trademark) frame header, etc. to send and receive user data sent and received by the UE.

[0037] In addition, the access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may have a configuration not recorded in Figure 2 For example, the core network_A and / or the core network_B and / or the PDN_A and / or the DN_A may include an AUSF (Authentication Server Function), an AAA (Authentication, authorization, and accounting) server (AAA-S). The AAA server may be configured outside the core network.

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

[0039] In addition, the AAA server is a device that is directly connected to the AUSF or indirectly via other network devices and has authentication, authorization and billing functions. The AAA server can be a network device within the core network. It should be noted that the AAA server can be included in the PLMN and / or SNPN but not included in the core network_A and / or core network_B. That is, the AAA server can be either a core network device or a device outside the core network. For example, the AAA server can be a server device within the PLMN and / or SNPN managed by a third party (3rdParty).

[0040] In this document, when referred to as NW, it can mean a core network, an access network, or both.

[0041] It should be noted that in Figure 2In the figure, for the sake of simplicity, each device / function is described as one, but multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150 may be configured in the mobile communication system 1. [2. Configuration of each device]

[0042] Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment is described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware configured on general hardware, or as software. In addition, at least part (including all) of the functions of each device can also be configured as physical hardware, logical hardware, or software.

[0043] It should be noted that each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device and each function that appears below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit can not only store the information originally set from the factory stage, but also store various information sent and received between devices / functions other than its own device and its own function (for example, UE and / or access network device and / or core network device and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc. included in the control messages sent and received in various communication processes described later. In addition, each storage unit can also store this information for each UE. In addition, each storage unit can store control messages and user data sent and received between the devices / functions included in 5GS and / or EPS when intercommunication between 5GS and EPS is performed. At this time, not only the data sent and received via the N26 interface can be stored, but also the data not sent and received via the N26 interface can be stored. [2.1. UE device configuration]

[0044] First, use Figure 3An example of the configuration of a UE (User Equipment) is described. The UE is composed of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, the transceiver_A320, and the storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.

[0045] The control unit_A300 is a functional unit that controls the overall actions and functions of the UE. The control unit_A300 reads and executes various programs stored in the storage unit_A340 as needed, thereby realizing various processes in the UE.

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

[0047] Reference Figure 2 To explain in detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver_A320. In addition, the UE can communicate with the base station device (gNB) in the 5G AN by using the transceiver_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum: non-access layer) messages with the AMF via the N1 interface by using the transceiver_A320. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN.

[0048] The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for various actions of the UE. [2.2.gNB device configuration]

[0049] Next, use Figure 4 The following describes an example of the gNB device configuration. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, the network connection unit_B520, the transceiver unit_B530, and the storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0050] The control unit_B500 is a functional unit that controls the overall actions and functions of the gNB. The control unit_B500 reads and executes various programs stored in the storage unit_B540 as needed, thereby realizing various processes in the gNB.

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

[0052] The transceiver_B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can use the transceiver_B530 to send and receive user data and / or control information between the UE.

[0053] Reference Figure 2 To explain in detail, the gNB in ​​the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. In addition, the gNB can communicate with the UE by using the transceiver unit_B530.

[0054] Storage unit_B540 is a functional unit used to store programs, user data, control information, etc. required for various actions of gNB. [2.3.AMF device configuration]

[0055] Next, use Figure 5 The following describes an example of the device configuration of AMF. AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. AMF can be a node that operates a control plane.

[0056] The control unit_B700 is a functional unit that controls the entire operation and function of the AMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the AMF.

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

[0058] Reference Figure 2To explain in detail, the AMF in 5GCN can communicate with gNB via the N2 interface, can communicate with UDM via the N8 interface, can communicate with SMF via the N11 interface, and can communicate with PCF via the N15 interface by using the network connection unit_A620. In addition, the AMF can send and receive NAS messages with the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN. In addition, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface by using the network connection unit_A620.

[0059] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of AMF.

[0060] It should be noted that AMF has the following functions: the function of exchanging control messages with RAN using N2 interface, the function of exchanging NAS messages with UE using N1 interface, the function of encrypting and integrity protecting NAS messages, the registration management (RM) function, the connection management (CM) function, the reachability management function, the mobility management (Mobility management) function of UE, etc., the function of transmitting SM (Session Management) messages between UE and SMF, the access authentication (Access Authentication, Access Authorization) function, the security anchor function (SEA; Security Anchor Functionality), the security context management (SCM; Security Context Management) function, the function of supporting the N2 interface for N3IWF (Non-3GPP Interworking Function: non-3GPP interworking function), the function of supporting the sending and receiving of NAS signals with UE via N3IWF, the function of authenticating UE connected via N3IWF, etc.

[0061] In addition, the RM state of each UE is managed in the login management. The RM state can be synchronized between the UE and the AMF. As the RM state, there are a non-logged-in state (RM-DEREGISTERED state) and a logged-in state (RM-REGISTERED state). In the RM-DEREGISTERED state, since the UE has not logged in to the network, the UE context in the AMF does not have valid location information and routing information for the UE, so the AMF is in a state where the UE cannot be reached. In addition, in the RM-REGISTERED state, the UE has logged in to the network, so the UE can receive services that require login to the network. It should be noted that the RM state can be expressed as a 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state can be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state can be expressed as a 5GMM-REGISTERED state.

[0062] In other words, 5GMM-REGISTERED can be a state where each device has established a 5GMM context, or a state where each device has established a PDU session context. It should be noted that when each device is 5GMM-REGISTERED, UE_A10 can start sending and receiving user data and control messages, and can also respond to paging. Moreover, it should be noted that when each device is 5GMM-REGISTERED, UE_A10 can perform login procedures and / or service request procedures other than the login procedure for initial login.

[0063] Moreover, 5GMM-DEREGISTERED can be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network cannot reach UE_A10. It should be noted that when each device is 5GMM-DEREGISTERED, UE_A10 can start the login process or establish a 5GMM context by executing the login process.

[0064] In addition, the CM state of each UE is managed in the connection management. The CM state can be synchronized between the UE and the AMF. As CM states, there are 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 (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-IDLE state, the UE does not have a connection (N2connection) of the N2 interface and a connection (N3connection) of the N3 interface. On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-CONNECTED state, the UE may also have a connection (N2connection) of the N2 interface and / or a connection (N3connection) of the N3 interface.

[0065] Moreover, in connection management, it can also be divided into CM state in 3GPP access and CM state in non-3GPP access for management. In this case, as the CM state in 3GPP access, there can be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over3GPP access). Moreover, as the CM state in non-3GPP access, there can 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-CONNECTEDstate over non-3GPP access). It should be noted that the non-connected state can be expressed as an idle mode, and the connected state mode can be expressed as a connected mode.

[0066] It should be noted that the CM state can also be expressed as 5GMM mode. In this case, the non-connected state can also be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state can also be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Moreover, the non-connected state in 3GPP access can also be expressed as 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access can also be expressed as 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Moreover, the non-connected state in non-3GPP access can also be expressed as 5GMM non-connected mode in non-3GPP access (5GMM-IDLE modeover non-3GPP access), and the connected state in non-3GPP access can also be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). It should be noted that the 5GMM non-connected mode can be expressed as an idle mode, and the 5GMM connected mode can be expressed as a connected mode.

[0067] In addition, more than one AMF can be configured in the core network_B. In addition, AMF can be an NF that manages more than one NSI (Network Slice Instance). In addition, AMF can also be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.

[0068] It should be noted that N3IWF is a device and / or function configured between non-3GPP access and 5GCN when the UE is connected to 5GS via non-3GPP access. [2.4. SMF device configuration]

[0069] Next, use Figure 5 An example of the device configuration of SMF is described. SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. SMF can be a node that operates a control plane.

[0070] The control unit_B700 is a functional unit that controls the entire operation and function of the SMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the SMF.

[0071] The network connection unit_B720 is a functional unit for connecting the SMF with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit_B720 to send and receive user data and / or control information between the AMF and / or UPF and / or PCF and / or UDM.

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

[0073] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of SMF.

[0074] SMF has the following functions: session management functions such as establishment, modification, and release of PDU sessions, IP address allocation and management functions for UE, UPF selection and control functions, UPF setting functions for routing services to the appropriate destination (sending destination), functions for sending and receiving the SM part of NAS messages, functions for notifying that downlink data has arrived (Downlink Data Notification), functions for providing AN-specific (each AN's) SM information sent to AN via AMF and through the N2 interface, functions for determining the SSC mode (Session and Service Continuity mode) for the session, roaming functions, etc. [2.5. UPF device configuration]

[0075] Next, use Figure 5 The following describes an example of the device configuration of the UPF. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The UPF may be a node that operates the control plane.

[0076] The control unit_B700 is a functional unit that controls the overall operation and functions of the UPF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the UPF.

[0077] The network connection unit_B720 is a functional unit for connecting the UPF to the base station device (gNB) and / or SMF and / or DN in the 5G AN. That is, the UPF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or DN in the 5G AN.

[0078] Reference Figure 2 To explain in detail, the UPF in 5GCN can communicate with gNB via the N3 interface, communicate with SMF via the N4 interface, communicate with DN via the N6 interface, and communicate with other UPFs via the N9 interface by using the network connection unit _A620.

[0079] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of UPF.

[0080] UPF has the following functions: serving as an anchor point for intra-RAT mobility or inter-RAT mobility, serving as an external PDU session point for interconnecting with DN (that is, serving as a gateway between DN and core network_B to transmit user data), routing and transmission of packets, UL CL (Uplink Classifier) ​​function that supports routing of multiple service flows for one DN, branching point function that supports multi-homed PDU sessions, QoS (Quality of Service) processing function for user plane, verification function of uplink services, triggering buffering of downlink packets, downlink data notification function, etc.

[0081] In addition, UPF can be a gateway for IP communication and / or non-IP communication. In addition, UPF can have the function of transmitting IP communication, and can also have the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways can be gateways connecting the core network_B with a single DN. It should be noted that UPF can have connectivity with other NFs, and can also be connected to each device via other NFs.

[0082] It should be noted that the user plane is user data sent and received between the UE and the network. The user plane can use a PDN connection or a PDU session for transmission and reception. Moreover, in the case of EPS, the user plane can also use 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 for transmission and reception. Moreover, in the case of 5GS, the user plane can also be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. In the following, the user plane can also be expressed as U-Plane.

[0083] Moreover, the control plane is a control message sent and received for communication control of the UE, etc. The control plane can use the NAS (Non-Access-Stratum) signaling connection between the UE and the MME for transmission and reception. Moreover, in the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for transmission and reception. Moreover, in the case of 5GS, the control plane can also use the interface between the UE and the NG RAN and the N2 interface for transmission and reception. In the following, the control plane can be expressed as either Control Plane or C-Plane.

[0084] Furthermore, the user plane (U-Plane, User Plane; UP) may be a communication path for sending and receiving user data, and may be composed of multiple bearers. Furthermore, the control plane (C-Plane, Control Plane; CP) may be a communication path for sending and receiving control messages, and may be composed of multiple bearers. [2.6. Other devices and / or functions and / or terms in this embodiment]

[0085] Next, other devices and / or functions and / or terms and / or identification information and / or messages sent, received, stored and managed by each device are described.

[0086] The network refers to at least a part of the access network_B, the core network_B, and the DN. In addition, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may also be referred to as a network or a network device. That is, the network executing the sending, receiving, and / or processing of messages may mean that a device (network device and / or control device) in the network executes the sending, receiving, and / or processing of messages. Conversely, the device in the network executing the sending, receiving, and / or processing of messages may mean that the network executes the sending, receiving, and / or processing of messages.

[0087] In addition, the SM (session management) message (also called NAS (Non-Access-Stratum) SM message) can be a NAS message used in the process of SM, or a control message sent and received between UE_A10 and SMF_A230 via AMF_A240. Moreover, the SM message can include: PDU session establishment request message, PDU session establishment accept message, PDU session rejection message, PDU session change request message, PDU session change command message, PDU session change complete message, PDU session change command rejection message, PDU session change rejection message, PDU session release request message, PDU session release rejection message, PDU session release command message, PDU session release complete message, etc.

[0088] In addition, the process used for SM or the SM process may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each process may be a process initiated by the UE or a process initiated by the NW (network).

[0089] In addition, the MM (Mobility management) message (or also called NAS MM message) can be a NAS message used for the MM process, or a control message sent and received between UE_A10 and AMF_A240. Moreover, the MM message may include: a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc.

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

[0091] In addition, 5GS (5G System) services may be connection services provided using the core network B190. Furthermore, 5GS services may be services different from EPS services or services similar to EPS services.

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

[0093] In addition, the PDN (Packet Data Network) type indicates the type of PDN connection, which includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that IPv4 is used to send and receive data. When IPv6 is specified, it indicates that IPv6 is used to send and receive data. When IPv4v6 is specified, it indicates that IPv4 or IPv6 is used to send and receive data. When non-IP is specified, it indicates that communication is not using IP, but communication is carried out by a communication method other than IP.

[0094] In addition, a PDU (Protocol Data Unit / Packet Data Unit) session may refer to an association between a DN and a UE that can be defined as providing a PDU connectivity service, but a connectivity established between the UE and an external gateway. The UE establishes a PDU session via the access network_B and the core network_B in the 5GS, thereby being able to use the PDU session to send and receive user data with the DN. Here, the external gateway may refer to a UPF, a SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers configured in the DN.

[0095] It should be noted that each device (UE and / or access network device and / or core network device) can also establish a correspondence between one or more identification information and the PDU session for management. It should be noted that these identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode (SSCmode), and may further include other information. Moreover, in the case of establishing multiple PDU sessions, each identification information corresponding to the PDU session establishment may be the same content or different content.

[0096] In addition, DNN (Data Network Name) can be identification information for identifying external networks such as the core network and / or DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 connected to the core network_B190. Furthermore, DNN can also be equivalent to APN (Access Point Name).

[0097] In addition, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it means that IPv4 is used to send and receive data. When IPv6 is specified, it means that IPv6 is used to send and receive data. When Ethernet is specified, it means that Ethernet frames are sent and received. In addition, Ethernet can indicate that communication without using IP is performed. When Unstructured is specified, it means that Point-to-Point (P2P) tunnel technology is used to send and receive data to an application server in the DN. As a P2P tunnel technology, for example, UDP / IP encapsulation technology can also be used. It should be noted that in addition to the above, IP can also be included in the PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0098] In addition, PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator as a (mobile) communication operator, and the operator can be identified by PLMNID. In this article, PLMN can also mean PLMN ID. The PLMN that is consistent with the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) can be the Home PLMN (Home PLMN: HPLMN). PLMN can also mean the core network.

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

[0100] The PLMN to which the UE successfully logs in may be an RPLMN (Registered PLMN). Each device may receive and / or maintain and / or store from the RPLMN an equivalent HPLMN list (Equivalent HPLMN list) for identifying one or more EPLMNs (Equivalent PLMNs) that can be used equivalently to the RPLMN in the PLMN selection of the UE.

[0101] The current PLMN may be a PLMN requested by the UE, and / or a PLMN selected by the UE, and / or an RPLMN, and / or a PLMN allowed by the network, and / or a PLMN to which a core network device that sends and receives messages belongs.

[0102] The requested PLMN means the destination network of the message when the UE sends a message. Specifically, it can be the PLMN selected by the UE when the UE sends a message. The requested PLMN is the PLMN requested by the UE, which can be the current PLMN. In addition, the PLMN requested by the UE in the logged-in state can also be the logged-in PLMN.

[0103] NPN (Non-public network) refers to a network with non-public specifications as its purpose. There are two types of NPN: SNPN (Stand-alone non-public network) and PNI-NPN (Public network integrated non-public network). SNPN and PNI-NPN can be deployed to 5GS. In this article, the case shown as NPN may refer to SNPN or PNI-NPN or both.

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

[0105] Here, the PLMN ID identifying the SNPN does not need to be unique. For example, more than one PLMN ID reserved for use in a private network may also be used for the NPN.

[0106] In addition, SNPN (Stand-alone Non-Public Network) is a network identified by a SNPN ID composed of a combination of a PLMN ID and a NID (Network identifier), and only allows specific UEs to connect. SNPN can also mean a core network. Here, the UE allowed to connect to the SNPN can be a SNPN-enabled UE.

[0107] Furthermore, the UE may maintain an equivalent SNPN list (Equivalent SNPN list) for identifying one or more ESNPNs (Equivalent SNPNs) in the USIM. A SNPN different from the HSNPN and / or the ESNPN may be a VPLMN (Visited PLMN).

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

[0109] PNI-NPN (Public network integrated non-public network) refers to an NPN deployed with the support of PLMN. In other words, it is a network that uses the functions of PLMN to implement non-public specifications.

[0110] The MS (UE) can access the onboarded SNPN using the default UE credentials through the onboarding services in SNPN.

[0111] The registration process for the onboarding service of SNPN may be an initial registration for onboarding services in SNPN. Moreover, or alternatively, the registration process for the onboarding service of SNPN may also be a registration process for mobile-based registration update when the UE logs in for the onboarding service of SNPN. The registration process for the onboarding service of SNPN may also be expressed as SNPN onboarding registration.

[0112] During the login process of the loading service for SNPN, MM-based slice admission control can be performed on the S-NSSAI for the loading service for SNPN without going through the AMF or NF in the core network.

[0113] In addition, a network slice (NS) refers to a logical network that provides specific network capabilities and network characteristics. UE and / or network can support network slicing (NW slicing; NS) in 5GS. Sometimes network slicing is also referred to as slicing.

[0114] In addition, a network slice instance (NSI) refers to a network slice formed and configured by a collection of instances (entities) of network functions (NFs) and required resources. Here, NF refers to a processing function in a network, which is adopted or defined in 3GPP. NSI is an entity that constitutes one or more NSs within the core network_B. In addition, NSI can be composed of a virtual NF (Network Function) generated using NST (Network Slice Template).

[0115] Here, NST refers to a logical expression of one or more NFs associated with a resource request for providing the requested communication service or capability. That is, NSI may refer to a collection within the core network B190 composed of multiple NFs. In addition, NSI may be a logical network configured to divide the user data sent according to services, etc. More than one NF may be configured in NS. The NF configured in NS may be a device shared with other NSs, or may not be a device shared with other NSs.

[0116] The UE and / or the device in the network can be assigned to one or more NSs based on the login information such as NSSAI and / or S-NSSAI and / or UE usage type (UE usage type) and / or one or more NSI IDs and / or APN. It should be noted that the UE usage type is a parameter value included in the login information of the UE for identifying the NSI. The UE usage type can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usage type.

[0117] In addition, S-NSSAI (Single Network Slice Selection Assistance information) is information for identifying NS. S-NSSAI can be composed of only SST (Slice / Servicetype: Slice / Service type), or it can be composed of both SST and SD (Slice Differentiator: Slice Differentiator). Here, SST refers to information indicating the expected actions of NS in terms of functions and services. In addition, SD may be information that interpolates SST when selecting an NSI from multiple NSIs shown in SST. S-NSSAI may be information specific to each PLMN or SNPN, or it may be standard information common between PLMNs or SNPNs.

[0118] In addition, S-NSSAI can be sent and received between devices using the S-NSSAI IE of 5GS. In this case, the S-NSSAI can be composed of S-NSSAI (SST and / or SD) associated with the current PLMN or SNPN and / or S-NSSAI (SST and / or SD) of the HPLMN (if any. For example, when the UE is roaming or the current PLMN or SNPN is a VPLMN or SNPN).

[0119] In addition, the network may store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, when the UE does not send a valid S-NSSAI to the network in the login request message, the network may provide the NS related to the UE.

[0120] In addition, the S-NSSAI sent and received between the UE and the NW can also be expressed as an S-NSSAI IE (Information element). Moreover, the S-NSSAI IE sent and received between the UE and the NW can be composed of an S-NSSAI composed of an SST and / or SD of a logged-in PLMN or SNPN and / or an SST and / or SD representing an S-NSSAI of an HPLMN or SNPN mapped with the S-NSSAI. One or more S-NSSAIs stored by the UE and / or NW can be composed of an SST and / or SD, or can be composed of an S-NSSAI composed of an SST and / or SD and / or an SST and / or SD representing an S-NSSAI of an HPLMN mapped with the S-NSSAI.

[0121] In addition, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information for assisting the access network or core network to select NSI. The UE can store the NSSAI allowed by the network for each PLMN or SNPN. In addition, NSSAI can be information for selecting AMF. The UE can also apply each NSSAI (allowed NSSAI and / or set NSSAI and / or rejected NSSAI and / or pending NSSAI and / or first NSSAI) to PLMN and EPLMN or SNPN and ESNPN.

[0122] The mapped S-NSSAI is the S-NSSAI of the HPLMN mapped to the S-NSSAI of the logged-in PLMN in the roaming scenario. The UE may store one or more set NSSAIs and mapped S-NSSAIs mapped to the S-NSSAI included in the allowed NSSAI of each access type. Moreover, the UE may also store one or more mapped S-NSSAIs of the rejected NSSAI and / or the pending NSSAI and / or the S-NSSAI included in the first NSSAI.

[0123] In the case of a roaming scenario supporting SNPN, the mapped S-NSSAI may be the S-NSSAI of the HSNPN mapped to the S-NSSAI of the logged-in SNPN.

[0124] In this document, unless otherwise specified, when roaming, S-NSSAI may refer to the S-NSSAI and / or mapped S-NSSAI of the current PLMN and / or SNPN.

[0125] The Network Slice-Specific Authentication and Authorization (NSSAA) function refers to the function used to implement network slice-specific authentication and authorization. In the network slice-specific authentication and authorization, the UE can be authenticated and authorized outside the core network such as a third party. The PLMN or SNPN and the network device with the NSSAA function can perform the NSSAA process on a certain S-NSSAI based on the UE's login information. Moreover, the UE with the NSSAA function can manage, store, and send and receive pending NSSAI and third rejected NSSAI. In this article, NSSAA is sometimes referred to as the network slice-specific authentication and authorization process, the authentication and authorization process.

[0126] The S-NSSAI requiring NSSAA is an S-NSSAI requiring NSSAA managed by the core network and / or the core network device. Moreover, during roaming, the S-NSSAI requiring NSSAA may also be an S-NSSAI other than the HPLMN or HSNPN to which the S-NSSAI is mapped, which is an S-NSSAI of the HPLMN or HSNPN requiring NSSAA managed by the core network and / or the core network device.

[0127] The core network and / or the core network device may store the S-NSSAI that requires NSSAA by establishing a correspondence between information indicating whether S-NSSAI and NSSAA are required. The core network and / or the core network device may also establish a correspondence between the S-NSSAI that requires NSSAA and information indicating whether NSSAA has been completed or information indicating the status of allowing or successfully completing NSSAA for storage. The core network and / or the core network device may manage the S-NSSAI that requires NSSAA as information that is not related to the access network.

[0128] In addition, the configured NSSAI is the NSSAI provided to and stored in the UE. The UE may store the configured NSSAI for each PLMN or SNPN. The UE may also store the configured NSSAI in association with the PLMN or SNPN.

[0129] It should be noted that, in this article, the setting NSSAI corresponding to the PLMN can be expressed as the setting NSSAI for the PLMN or the setting NSSAI for the PLMN or the setting NSSAI for the PLMN, and the setting NSSAI associated with the PLMN. Similarly, the setting NSSAI corresponding to the SNPN can be expressed as the setting NSSAI for the SNPN or the setting NSSAI for the SNPN or the setting NSSAI for the SNPN, and the setting NSSAI associated with the SNPN.

[0130] In addition, the UE may not establish an association with the PLMN, but store the settings NSSAI that are valid for all PLMNs, and may set such settings NSSAI as the "default settings NSSAI". Similarly, the UE may not establish an association with the SNPN, but store the settings NSSAI that are valid for all SNPNs, and may set such settings NSSAI as the "default settings NSSAI". The UE may not establish an association with either the PLMN or the SNPN, but store all valid settings NSSAI for PLMNs and SNPNs, and may set such settings NSSAI as the "default settings NSSAI".

[0131] NSSAI can be set up to associate with multiple PLMNs or SNPNs. These multiple PLMNs can be EPLMNs, and multiple SNPNs can also be ESNPNs.

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

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

[0134] Moreover, one or more S-NSSAIs of the HPLMN or HSNPN mapped with the setting S-NSSAI can also be expressed as "one or more mapping S-NSSAIs of the setting NSSAI for the PLMN or SNPN" or "one or more mapping S-NSSAIs of the setting NSSAI of the PLMN or SNPN".

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

[0136] The NSSAI setting may be updated by the NW at any time, and based on the update, the updated NSSAI setting may be sent from the NW to the UE.

[0137] In addition, the requested NSSAI is the NSSAI provided by the UE to the network during the login process. During the login process, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI and / or the set NSSAI and / or the first NSSAI stored by the UE.

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

[0139] The requested NSSAI may be information including one or more S-NSSAIs corresponding to the network slices requested by the UE. It should be noted that, here, the network slice requested by the UE may refer to the network slice that the UE wants to use, or it may be the network slice that the UE requests to be allowed to use by the network. The S-NSSAI included in the requested NSSAI may be the S-NSSAI included in the set NSSAI corresponding to the current PLMN, or it may be the S-NSSAI included in the allowed NSSAI corresponding to the current PLMN.

[0140] In other words, the request NSSAI may be one or more S-NSSAIs included in the set NSSAI corresponding to the current PLMN / SNPN, one or more S-NSSAIs included in the allowed NSSAI corresponding to the current PLMN, one or more S-NSSAIs included in the first NSSAI corresponding to the current PLMN, or a combination of the above three. More specifically, the allowed NSSAI corresponding to the current PLMN may refer to the allowed NSSAI corresponding to the current PLMN and the current access type. Moreover, the request NSSAI may also be the request NSSAI of 5GS.

[0141] It should be noted that the S-NSSAI included in the requested NSSAI may be an S-NSSAI not included in the rejected NSSAI stored by the UE and associated with the current PLMN or SNPN and / or an S-NSSAI not included in the pending NSSAI stored by the UE and associated with the current PLMN or SNPN, or an S-NSSAI not included in the fourth rejected NSSAI stored by the UE and associated with the current PLMN or SNPN.

[0142] Furthermore, the S-NSSAI included in the request NSSAI may be an S-NSSAI for which a backoff timer associated with the S-NSSAI and / or a mapped S-NSSAI of the S-NSSAI in the UE is not executed.

[0143] In addition, allowed NSSAI is information indicating one or more network slices that the UE is allowed to connect to. In other words, allowed NSSAI is information identifying the network slices that the network is allowed to connect to the UE. Allowed NSSAI can be allowed NSSAI stored by the UE and / or NW, or it can be allowed NSSAI sent from the NW to the UE. In this case, allowed NSSAI can refer to the allowed NSSAI IE of 3GPP.

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

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

[0146] It should be noted that the list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN and included in the allowed NSSAI IE may also be referred to as allowed NSSAIs, and the list of mapped S-NSSAIs of the S-NSSAIs of the HPLMN or HSNPN that are mapped with the S-NSSAIs of the current PLMN or SNPN may be referred to as the list of mapped S-NSSAIs of allowed NSSAIs. Here, the list of mapped S-NSSAIs of allowed NSSAIs may be the mapped S-NSSAI(s) for the allowed NSSAI for a PLMN of 3GPP. Similarly, allowed NSSAI may also refer to the allowed NSSAI for a PLMN or an SNPN of 3GPP.

[0147] The UE and / or NW may store and manage the allowed NSSAI as UE information for each access (3GPP access or non-3GPP access). The UE and / or NW may also manage the allowed NSSAI in association with the login area.

[0148] Moreover, the UE and / or NW may establish an association with the PLMN or SNPN to store and manage the allowed NSSAI as UE information. The allowed NSSAI may also be associated with multiple PLMNs, which may be EPLMNs, and the multiple SNPNs may also be ESNPNs.

[0149] It should be noted that, in this article, the allowed NSSAI that corresponds to the PLMN or SNPN and the access type can be expressed as "the allowed NSSAI for the PLMN or SNPN and the access type" or "the allowed NSSAI for the access type of the PLMN or SNPN".

[0150] The S-NSSAI included in the allowed NSSAI can be expressed as allowed S-NSSAI (allowed S-NSSAI). Allowed S-NSSAI can be transmitted and received using the S-NSSAI IE. In this case, allowed S-NSSAI (SST and / or SD) can be constructed to include S-NSSAI and mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any. For example, when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

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

[0152] Moreover, one or more S-NSSAIs of the HPLMN or HSNPN mapped with the allowed S-NSSAI can also be expressed as "one or more mapped S-NSSAIs for the allowed NSSAIs of the PLMN or SNPN" or "one or more mapped S-NSSAIs for the allowed NSSAIs of the PLMN or SNPN".

[0153] In addition, the rejected NSSAI is information indicating one or more network slices that the UE is not allowed to use or request. In other words, the rejected NSSAI is information identifying the network slices that the network is not allowed to connect to the UE. The rejected NSSAI sent from the NW to the UE may be included in the rejected NSSAI IE or the extended rejected NSSAI IE.

[0154] The rejected NSSAI sent and received using the rejected NSSAI IE may be information including a combination of one or more S-NSSAI (SST and / or SD) and a rejection reason value (rejected S-NSSAI). The rejected NSSAI sent and received using the extended rejected NSSAI IE (Extendedrejected NSSAI IE) may be information including a combination of one or more S-NSSAI (SST and / or SD), a mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any. For example, when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN) and a rejection reason value (Rejected S-NSSAI).

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

[0156] The information indicating the type of a set may be, for example, information indicating that the set includes one or more reject S-NSSAI (SST and / or SD) together with an associated backoff timer value, or information indicating that the set does not include an associated backoff timer value but includes one or more reject S-NSSAI (SST and / or SD).

[0157] When the information indicating the type of the set is information indicating that the set includes one or more reject S-NSSAIs together with the associated backoff timer value, the set of reject S-NSSAIs may also include the backoff timer value.

[0158] Here, the S-NSSAI included in the rejected NSSAI may be associated with a PLMN ID or a SNPN ID. It should be noted that the PLMN or SNPN represented by the PLMN ID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI may be the current PLMN or the current SNPN. Alternatively, the PLMNID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI may be information representing the HPLMN or HSNPN regardless of the current PLMN or SNPN.

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

[0160] Moreover, the rejection of NSSAI may also be included in a NAS message sent from the network to the UE, such as a login acceptance message, a setting update command, a login rejection message, or an RRC message including a NAS message. The S-NSSAI included in the rejection of NSSAI may be expressed as a rejection of S-NSSAI.

[0161] The UE may use the Reject NSSAI IE to send a Reject NSSAI when roaming, or may use the Extended Reject NSSAI IE to send a Reject NSSAI. The Extended Reject NSSAI IE may include one or more Reject S-NSSAI (IE) consisting of the S-NSSAI (SST and / or SD) of the current PLMN or SNPN, the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or the SD of the mapped HPLMN or SNPN), and the Reject Reason value, which may be understood as the UE requesting the NW to request the received S-NSSAI of the current PLMN or SNPN and the received mapped S-NSSAI together and being rejected. On the other hand, the Reject NSSAI IE may also include a Reject S-NSSAI IE based on the S-NSSAI of the current PLMN or SNPN and the Reject Reason value, which may also be understood as the UE requesting the NW to receive the S-NSSAI of the current PLMN or SNPN or the S-NSSAI associated with the S-NSSAI of the HPLMN or HSNPN and being rejected.

[0162] The reject NSSAI may be any one of the first to fourth reject NSSAIs, one or more mapped S-NSSAIs for the first reject NSSAI, one or more mapped S-NSSAIs for the second reject NSSAI, and one or more mapped S-NSSAIs for the fourth reject NSSAI, or a combination of these. The S-NSSAI included in the reject NSSAI may be expressed as the reject S-NSSAI. The reject S-NSSAI may be sent and received between devices using the S-NSSAI IE, and the S-NSSAI IE indicating the reject NSSAI may be constructed to include the S-NSSAI and the mapped S-NSSAI.

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

[0164] It should be noted that, in this article, the rejection NSSAI associated with the PLMN or SNPN may also be expressed as a rejection NSSAI for the PLMN or SNPN or a rejection NSSAI for the PLMN or SNPN or a rejection NSSAI for the PLMN or SNPN. The UE and / or NW may also store the second rejection NSSAI and / or the second rejection S-NSSAI in association with the login area. The UE and / or NW may also store the second rejection NSSAI and / or the second rejection S-NSSAI in association with the access type and / or login area.

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

[0166] In the case where the first rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the S-NSSAI included in the request NSSAI sent by the UE to the NW includes one or more S-NSSAIs that are rejected due to unavailability in the current PLMN or the current SNPN. In this case, the first rejection NSSAI may be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value at this time may be "S-NSSAI not available in the current PLMN or SNPN", or it may be information indicating that the S-NSSAI corresponding to the rejection reason value is unavailable in the current PLMN or SNPN. The S-NSSAI included in the first rejection NSSAI may be expressed as the first rejection S-NSSAI.

[0167] In the case where the first rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the first rejection NSSAI may be included in a rejection NSSAI IE or an extended rejection NSSAI IE for transmission and reception. The rejection NSSAI IE or the extended rejection NSSAI IE may include a combination of the S-NSSAI of at least one current PLMN or SNPN and a rejection reason value. In the case where the UE is roaming, the above combination may also include a mapped S-NSSAI as the S-NSSAI of the HPLMN.

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

[0169] The first rejection NSSAI can be applied to the entire PLMN or SNPN. The UE and / or NW can regard the first rejection NSSAI and the S-NSSAI included in the first rejection NSSAI as information that does not depend on the access type. That is, the first rejection NSSAI can be information that is valid for 3GPP access (3GPP access) and non-3GPP access (non-3GPP access).

[0170] The UE may delete the first rejection NSSAI from the storage when the UE switches to the non-logged-in state for the current PLMN in both the 3GPP access and the non-3GPP access. In other words, when the UE switches to the non-logged-in state for the current PLMN via a certain access, or successfully logs in to a new PLMN via a certain access, or fails to log in to the new PLMN via a certain access and switches to the non-logged-in state, and when the UE is in a state (non-logged-in state) without logging in through the access of the other party, the UE deletes the first rejection NSSAI. That is, when the UE switches to the non-logged-in state for the current PLMN via a certain access, and when the UE is in a state (logged-in state) in which the UE has logged in to the current PLMN via the access of the other party, the UE may not delete the first rejection NSSAI.

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

[0172] The second rejected NSSAI is a set of one or more S-NSSAIs that are not available in the current registration area. The second rejected NSSAI can be a rejected NSSAI for the current registration area of ​​5GS, or a mapped S-NSSAI (mapped S-NSSAI(s)for rejected NSSAI for the current registration area) for the rejected NSSAI for the current registration area, or an S-NSSAI included in the mapped S-NSSAI for the rejected NSSAI for the current registration area. The list (set) of mapped S-NSSAIs for the second rejected NSSAI can be one or more mapped S-NSSAIs for the second rejected NSSAI, or a mapped S-NSSAI (mapped S-NSSAI(s)for therejected NSSAI for the current registration area) for the rejected NSSAI of 5GS for the current registration area. The second rejected NSSAI can be a rejected NSSAI stored by the UE or NW, or a rejected NSSAI sent from the NW to the UE. In the case where the second rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the second rejection NSSAI may be information including a combination of one or more S-NSSAIs and a reason value. The rejection reason value at this time may be "S-NSSAI not available in the current registration area", or it may be information indicating that the S-NSSAI corresponding to the reason value is not available in the current registration area. The S-NSSAI included in the second rejection NSSAI may be expressed as a second rejection S-NSSAI.

[0173] In the case where the second rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the S-NSSAI included in the request NSSAI by the UE includes one or more S-NSSAIs that are rejected because they are not available in the current registration area. In this case, the second rejection NSSAI may be included in the rejection NSSAI IE or the extended rejection NSSAI IE for transmission and reception. The rejection NSSAI IE or the extended rejection NSSAI IE may include a combination of the S-NSSAI of at least one current PLMN or SNPN and a rejection reason value. In the case where the UE is roaming, the above combination may also include a mapped S-NSSAI as the S-NSSAI of the HPLMN.

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

[0175] The second rejection NSSAI may be valid within the current registration area or may be applied to the current registration area. The UE and / or NW may regard the second rejection NSSAI and the S-NSSAI included in the second rejection NSSAI as information for each access type. That is, the second rejection NSSAI may be information valid for 3GPP access or non-3GPP access, respectively. That is, the UE may delete the second rejection NSSAI associated with a certain access from the storage once it switches to the non-logged-in state for the access.

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

[0177] The third rejected NSSAI is an S-NSSAI that requires NSSAA, and is a set of one or more S-NSSAIs for which the NSSAA fails or is canceled for the S-NSSAI. The third rejected NSSAI may be an NSSAI stored by the UE and / or NW, or it may be an NSSAI sent and received between the NW and the UE. In the case where the third rejected NSSAI is sent from the NW to the UE, the third rejected NSSAI may be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value at this time may be "S-NSSAI not available due to the failed or revoked NSSAI", or it may be information indicating the failure or cancellation of the NSSAI for the S-NSSAI corresponding to the rejection reason value. The S-NSSAI included in the third rejected NSSAI may be expressed as a third rejected S-NSSAI.

[0178] In the case where the third Reject NSSAI is the NSSAI sent from the NW to the UE, the third Reject NSSAI may be transmitted and received using the Reject NSSAI IE or the Extended Reject NSSAI IE.

[0179] The third rejection NSSAI can be applied to logging into a PLMN or logging into a SNPN, or can be applied to logging into a PLMN and / or an EPLMN, or can be applied to logging into a SNPN and / or an ESNPN, or can be applied to all PLMNs or SNPNs. The third rejection NSSAI being applied to all PLMNs can mean that the third rejection NSSAI is not associated with a PLMN, or can mean that the third rejection NSSAI is associated with an HPLMN or an HSNPN.

[0180] Moreover, the UE and / or NW may regard the third rejected NSSAI and the third rejected S-NSSAI as information that is independent of the access type. That is, the third rejected NSSAI may be information that is 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 also be the first rejected NSSAI. The third rejected NSSAI may be a rejected NSSAI for the failed or revoked NSSAA of the 5GS, or a rejected S-NSSAI for the failed or revoked NSSAA, or an S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA.

[0181] The third rejection NSSAI is a rejection NSSAI for the UE to identify the slices rejected by the core network due to NSSAA failure or cancellation. Specifically, while storing the third rejection NSSAI, the UE does not start the login request process for the S-NSSAI included in the third rejection NSSAI. The third rejection NSSAI may be identification information including one or more S-NSSAIs received from the core network in correspondence with the rejection reason value indicating the failure of NSSAA.

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

[0183] Alternatively, the UE may delete the third reject NSSAI based on the UE policy and transition to a state where a login request message including the S-NSSAI included in the third reject NSSAI can be sent. In other words, in the case where the UE sends a login request message including the S-NSSAI included in the third reject NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third reject NSSAI.

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

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

[0186] The fourth rejected NSSAI is information including one or more S-NSSAIs reaching the maximum number of UEs per network slice. The fourth rejected NSSAI can be the NSSAI stored by the UE and / or NW, or it can be the NSSAI sent from the NW to the UE.

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

[0188] In the case where the fourth rejection NSSAI is sent from the NW to the UE, the fourth rejection NSSAI may be information including one or more information including at least one S-NSSAI (SST and / or SD), a mapped S-NSSAI (SST and / or SD) (if present), a rejection reason value, and a backoff timer value. The rejection reason value at this time may be "S-NSSAI not available due to maximum number of UEs reached for each network slice", or it may be information indicating that the maximum number of UEs that can be notified of the S-NSSAI corresponding to the rejection reason value or allowed as the allowed NSSAI has been reached.

[0189] Here, the rejection reason value may be the rejection reason value included in the rejection NSSAI. Moreover, at this time, the value of the backoff timer may also be information indicating the period during which the UE is prohibited from sending an MM message using one or more S-NSSAIs associated with the value of the backoff timer and / or one or more mapped S-NSSAIs associated with the current PLMN or SNPN.

[0190] The fourth rejection NSSAI can be applied to the registered PLMN and / or EPLMN, and can also be applied to the registered SNPN and / or ESNPN, and can also be applied to one or more PLMNs or SNPNs described in the TAI included in the TA list (TAI list or registration area).

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

[0192] In the case where the fourth Reject NSSAI is the NSSAI sent from the NW to the UE, the fourth Reject NSSAI may be sent and received using the extended Reject NSSAI IE.

[0193] In case the first to fourth Reject NSSAIs are transmitted and received using the Reject NSSAI IE or the Extended Reject NSSAI IE, a list of rejected S-NSSAIs may be included in the Reject NSSAI IE and the Extended Reject NSSAI IE.

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

[0195] In the case where the first to fourth Reject NSSAIs are transmitted and received using the Extended Reject NSSAI IE, the list of rejected S-NSSAIs included in the Extended Reject NSSAI IE may be a partial Extended Reject NSSAI list of 5GS.

[0196] The list of rejected S-NSSAIs includes a first type of list that does not include a backoff timer value, and a second type of list that includes a backoff timer value applied to all S-NSSAIs included in the list of rejected S-NSSAIs. The extended reject NSSAI IE may be composed of one or more first type of lists and / or one or more second lists.

[0197] The first type of list may contain one or more information indicating that the list is of the first type and one or more 5GS rejection S-NSSAI. The rejection S-NSSAI may contain the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and the corresponding rejection reason value. Moreover, the rejection S-NSSAI may contain a mapping S-NSSAI (SST and / or SD).

[0198] The information indicating that the list is of the first type may mean that the list does not include one or more S-NSSAIs together with the corresponding backoff timer values. In other words, it may also mean that the list does not include backoff timer values ​​corresponding to one or more S-NSSAIs included in the list.

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

[0200] The information indicating that the list is of the second type may be information indicating that the list includes more than one S-NSSAI and the values ​​of the backoff timer corresponding thereto, and that the value of the backoff timer is applied to all S-NSSAIs.

[0201] It should be noted that the value of the backoff timer included in the second type of list may be the value included in the same second type of list and applied to all S-NSSAIs.

[0202] The pending NSSAI may be the pending NSSAI of the 5GS. The pending NSSAI may be the NSSAI stored in the UE and / or NW, or the NSSAI sent and received between the NW and the UE.

[0203] In the case where the pending NSSAI is the NSSAI sent from the NW to the UE, the pending NSSAI can be sent and received using a pending NSSAI IE that constitutes more than one S-NSSAI IE, which may include S-NSSAI (SST and / or SD) and mapped S-NSSAI (SST of the mapped HPLMN or HSNPN and / or SD of the mapped HPLMN or HSNPN) (if any. For example, when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

[0204] The pending NSSAI may be applied to the registered PLMN or the registered SNPN as a whole, may be applied in the registered PLMN and one or more EPLMNs of the registered PLMN, or may be applied in the registered SNPN and one or more ESNPNs of the registered SNPN.

[0205] The UE and / or NW may regard the S-NSSAI included in the pending NSSAI as information that does not depend on the access type. That is, the pending NSSAI may be information common to both 3GPP access and non-3GPP access.

[0206] The pending NSSAI is an NSSAI composed of one or more S-NSSAIs identifying the slice for which the UE is pending a process. Specifically, the UE does not start a login request process for the S-NSSAI included in the pending NSSAI or the mapped S-NSSAI of the pending NSSAI during storage of the pending NSSAI.

[0207] In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the login process until the NSSAA for the S-NSSAI included in the stored pending NSSAI is completed. The pending NSSAI is information that does not depend on the access type. Specifically, in the case where the UE stores the pending NSSAI, the UE does not attempt to send a login request message including the S-NSSAI included in the pending NSSAI to both the 3GPP access and the non-3GPP access.

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

[0209] In other words, for the UE storing the first pending NSSAI, the mapped S-NSSAI for the first pending NSSAI means not storing it, and the S-NSSAI constructed in the first pending NSSAI stored in the UE is the S-NSSAI of the HPLMN or HSNPN whether in roaming or non-roaming.

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

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

[0212] In other words, when roaming, there may be more than one mapped S-NSSAI for the second pending NSSAI. Whether roaming or non-roaming, the S-NSSAI constructed in the second pending NSSAI may be the S-NSSAI of the current PLMN or SNPN.

[0213] In this document, when referring to the pending NSSAI, it may mean the first pending NSSAI, the second pending NSSAI, both pending NSSAIs, or another pending NSSAI.

[0214] The tracking area is one or more ranges managed by the core network that can be represented as the location information of UE_A10. The tracking area can be composed of multiple cells. Moreover, the tracking area can be either a range for broadcasting control messages such as paging, or a range where UE_A10 can move without performing a switching process. Moreover, the tracking area can be either a routing area or a positioning area, as long as it is the same area as these areas. Hereinafter, the tracking area may also be referred to as TA (Tracking Area). The tracking area can be identified by TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.

[0215] The registration area (Registration area or login area) is a set of one or more TAs assigned to the UE by the AMF. It should be noted that it is better for UE_A10 to move without sending or receiving signals for tracking area update while moving within one or more TAs included in the registration area. In other words, the registration area can be an information group indicating the area where UE_A10 can move without performing the tracking area update process. The registration area can be identified by a TAI list (TAIlist) composed of one or more TAIs.

[0216] The TAIs included in the TAI list may belong to one PLMN or SNPN, or may belong to multiple PLMNs or SNPNs. In the case where the multiple TAIs included in the TAI list belong to different PLMNs or SNPNs, these PLMNs or SNPNs may be EPLMNs or ESNPNs.

[0217] UE ID refers to information used to identify UE. Specifically, for example, UE ID can be SUCI (SUbscription Concealed Identifier) ​​or SUPI (Subscription Permanent Identifier) ​​or GUTI (Globally Unique Temporary Identifier) ​​or IMEI (International Mobile Subscriber Identity) or IMEISV (IMEI Software Version) or TMSI (Temporary Mobile Subscriber Identity). Alternatively, UE ID can be other information set in an application or network. Moreover, UE ID can also be information used to identify a user.

[0218] The management of the maximum number of UEs connected to a slice refers to the management and / or control of the maximum number of UEs that can log in to a network slice or S-NSSAI at the same time, or the management and / or control of the maximum number of UEs that can establish a PDU session that uses a network slice or S-NSSAI at the same time. The management of the maximum number of UEs connected to a slice can be 5GS's NSAC (network slice admission control). NSAC can also be expressed as slice admission control.

[0219] The management and / or control of the maximum number of UEs that can log in to a network slice or S-NSSAI at the same time can be expressed as MM-based slice admission control (Mobility management based slice admission control). The management and / or control of the maximum number of UEs that can establish PDU sessions that use network slices or S-NSSAI at the same time can be expressed as SM-based slice admission control (Session management based slice admission control). Slice admission control (slice admission control) can mean NSAC (Network Slice Admission Control).

[0220] Here, the UE logging into the network slice or S-NSSAI may refer to the UE including the S-NSSAI representing the network slice in the storage of the allowed NSSAI. A device in a network supporting the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can simultaneously log into a network slice or S-NSSAI can store the maximum number of UEs that need to be connected to the slice for each S-NSSAI, and can confirm whether the number of logged-in UEs has reached a constant as the maximum number during the login process.

[0221] Moreover, each device that supports the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can simultaneously log in to a network slice or S-NSSAI can store the fourth rejected NSSAI. In this document, the maximum number of UEs connected to a slice is sometimes expressed as the maximum number of UEs connected to each slice or the maximum number of UEs that can log in to a network slice or S-NSSAI or the maximum number of UEs or a constant. [2.6.1. Behavior of UE and / or NW related to equivalent SNPN]

[0222] The equivalent SNPN is described below. In addition, the behavior of the UE and / or NW related to the equivalent NSSAI is described.

[0223] First, when the UE roams between SNPNs, the SNPN can be classified into a Home SNPN (also called HSNPN) and a Visited SNPN (also called VSNPN). It should be noted that when the UE does not roam between SNPNs, the SNPN can be considered the same as the Home SNPN.

[0224] In addition, the home SNPN may refer to a SNPN to which the UE can log in as a home. In addition, the home SNPN may also refer to the SNPN that the UE first selects in the SNPN selection. In addition, the home SNPN may also refer to a SNPN in which at least a portion of the information included in the SNPN identity (SNPN identity, also called SNPN ID) matches at least a portion of the information included in the IMSI of the UE. In addition, the home SNPN may also refer to a SNPN in which the MCC and MNC included in the PLMN Identity (PLMN Identity, also called PLMN ID) included in the SNPN identity (also called SNPN ID) match the MCC and MNC included in the IMSI of the UE.

[0225] In addition, a visited SNPN may refer to a SNPN that the UE can log in to other than as a home. In addition, a visited SNPN may also refer to a SNPN that the UE does not log in to as a home. In addition, a visited SNPN may also refer to a SNPN that the UE does not select first in the SNPN selection. In addition, a visited SNPN may also refer to a SNPN in which at least a portion of the information included in the SNPN identifier (also called SNPN ID) does not match at least a portion of the information included in the IMSI of the UE. In addition, a visited SNPN may also refer to a SNPN in which the MCC and MNC included in the PLMN identifier (also called PLMN ID) included in the SNPN identifier (also called SNPN ID) do not match the MCC and MNC included in the IMSI of the UE.

[0226] In addition, an equivalent HSNPN (equivalent HSNPN, also called equivalent Home SNPN, EHSNPN) may be an SNPN that is considered to be equivalent to the current SNPN (herein, the home SNPN (also called HSNPN)) in SNPN selection and / or cell selection and / or cell reselection. In addition, an equivalent HSNPN may also refer to one or more SNPNs included in an equivalent HSNPN list, and may also refer to one or more SNPNs that are not included in an equivalent VSNPN (equivalent VSNPN) list.

[0227] In addition, an equivalent VSNPN (also called equivalent Visited SNPN, EVSNPN) may refer to an SNPN that is considered to be equivalent to the current SNPN (here, a visited SNPN (also called VSNPN)) in SNPN selection and / or cell selection and / or cell reselection. In addition, an equivalent VSNPN may also refer to one or more SNPNs included in an equivalent VSNPN list, and may also refer to one or more SNPNs that are not included in an equivalent HSNPN list.

[0228] In addition, an equivalent SNPN (also referred to as ESNPN) may be a concept including an equivalent HSNPN and / or an equivalent VSNPN. That is, ESNPN may refer to an equivalent HSNPN and / or an equivalent VSNPN.

[0229] Next, the description is made about the equivalent HSNPN list (also called the EHSNPN list). In order to provide multiple HSNPN codes (HSNPN code, also called Home SNPN code, Home SNPN identity, Home SNPN ID), the SNPN code (SNPN code, also called SNPNidentity, SNPN ID) existing in the EHSNPN list can be exchanged with the HSNPN code obtained from the IMSI when selecting the SNPN or in order to select the SNPN. In addition, the EHSNPN list can be stored in the USIM. In addition, the EHSNPN list can also include the HSNPN code obtained from the IMSI. In addition, in the case that the HSNPN code obtained from the IMSI does not exist in the EHSNPN list, the HSNPN code can be regarded as the visited SNPN when selecting the SNPN or in order to select the SNPN.

[0230] Next, the description is made about the equivalent VSNPN list (also called the EVSNPN list). In order to provide multiple VSNPN codes (VSNPN code, also called Visited SNPN code, Visited SNPN identity, Visited SNPN ID), the SNPN code (SNPN code, also called SNPN identity, SNPN ID) existing in the EVSNPN list can be exchanged with the VSNPN code obtained from the IMSI when selecting the SNPN or in order to select the SNPN. In addition, the EVSNPN list can be stored in the USIM. In addition, the EVSNPN list can also include the HVNPN code obtained from the IMSI. In addition, in the case that the VSNPN code obtained from the IMSI does not exist in the EVSNPN list, the VSNPN code can be regarded as the belonging SNPN when selecting the SNPN or in order to select the SNPN.

[0231] In addition, the equivalent SNPN list (also referred to as the ESNPN list) may refer to a concept including the EHSNPN list and / or the EVSNPN list. That is, the ESNPN list may also refer to the EHSNPN list and / or the EVSNPN list.

[0232] In addition, the UE may store an equivalent SNPN list sent from the network. For example, upon receiving an MM message (e.g., a login request message or a setting update command, etc.) sent from the AMF, the UE may store the equivalent SNPN list included in the MM message.

[0233] In addition, the UE may consider the equivalent SNPN as being equivalent to the current SNPN (Home NPN or Visited SNPN) during SNPN selection and / or cell selection and / or cell reselection. In other words, when selecting an SNPN, if the home SNPN cannot be selected, the UE may give priority to selecting an equivalent SNPN (equivalent Home SNPN) that is considered equivalent to the home SNPN. In addition, when selecting a cell and / or cell reselection in the SNPN, if the home SNPN cannot be selected, the UE may give priority to selecting an equivalent SNPN (equivalent Home SNPN) that is considered equivalent to the home SNPN.

[0234] In addition, the UE may update or delete the equivalent SNPN list at the end of each login procedure.

[0235] In addition, the UE may maintain a list of equivalent SNPNs when the power is turned off. This may be for use in SNPN selection when the power is turned on later.

[0236] Furthermore, the UE may delete the equivalent SNPN list in the event that the USIM is removed from the UE or the UE logged into emergency services enters 5G MM-DEREGISTERED.

[0237] In addition, the AMF may add an equivalent SNPN list to the login acceptance message during the login process. In addition, the equivalent SNPN list may include one or more SNPN codes (also called SNPN IDs) containing a combination of a PLMN code (also called PLMN ID) and an NID. The UE may update the stored equivalent SNPN list to the received list if the equivalent SNPN list is included in the login acceptance message. In addition, the UE may delete the stored equivalent SNPN list if the equivalent SNPN list is not included in the login acceptance message.

[0238] In addition, when the UE performs a login procedure that is not performed for emergency services, the UE can delete the SNPN code (also called SNPN ID) present in the permanently forbidden SNPNs list or the temporarily forbidden SNPN list from the equivalent SNPN list.

[0239] In addition, the UE may, during the login process initiated by the UE, receive a 5GSM cause value (5GSM cause value) indicating that: an illegal UE (illegalUE) or an illegal ME (illegal ME) or 5GS services not allowed (5GS services not allowed) or a tracking area not allowed (Tracking area not allowed) or roaming not allowed in this tracking area (Roaming not allowed in this tracking area) or no suitable cells in the tracking area (No suitable cells in tracking area) or N1 mode (N1 mode not allowed) or non-3GPP access to 5GCN is not allowed (or it can also be expressed as not allowing connection from non-3GPP access to 5GCN, etc.) (Non-3GPP access to 5GCN not allowed) or temporarily not authorized for this SNPN (Temporarily not authorized for this SNPN) or permanently not authorized for this SNPN (Permanently not authorized for this SNPN) Not integrity protected (integrity protected) If a login rejection message is received during the authentication process (protection), the timer T3510 or timer T3517 in action is stopped. If the timer T3247 does not perform any action, the timer T3247 is started and the equivalent SNPN list is deleted.

[0240] In addition, the UE may, during the service request process initiated by the UE, receive a 5GSM cause value indicating that: an illegal UE or an illegal ME or 5GS services not allowed or a tracking area not allowed or roaming not allowed in this tracking area or no suitable cells in the tracking area or N1 mode not allowed or non-3GPP access to 5GCN not allowed (or it may also be expressed as not allowing connection to 5GCN from non-3GPP access, etc.) (Non-3GPP access to5GCN not allowed) or temporarily not authorized for this SNPN or permanently not authorized for this SNPN. In the case of a service rejection message for protection), the timer T3510 or timer T3517 in action is stopped. If the timer T3247 does not take action, the timer T3247 is started and the equivalent SNPN list is deleted.

[0241] In addition, in the deregistration process initiated by the network, when a deregistration request message without integrity protection is received, including a 5GSM cause value indicating: illegal UE (illegal UE) or illegal ME (illegal ME) or 5GS services not allowed (5GS services not allowed) or tracking area not allowed (Tracking area not allowed) or roaming not allowed in this tracking area (Roaming not allowed in this tracking area) or no suitable cells in the tracking area (No suitable cells in tracking area) or N1 mode not allowed (N1 mode not allowed) or non-3GPP access to 5GCN is not allowed (or it can also be expressed as not allowing connection to 5GCN from non-3GPP access, etc.) (Non-3GPP access to5GCN not allowed) or temporarily not authorized for this SNPN (Temporarily not authorized for thisSNPN) or permanently not authorized for this SNPN (Permanently not authorized for this SNPN), the equivalent SNPN list may be deleted.

[0242] In addition, the UE may include information indicating whether the UE supports an equivalent SNPN or an equivalent SNPN list in a login request message and send it. In addition, the AMF may include information indicating whether the network supports an equivalent SNPN or an equivalent SNPN list in a login acceptance message or a login rejection message and send it. Specifically, the AMF may determine whether to include information indicating whether the network supports an equivalent SNPN or an equivalent SNPN list and an equivalent SNPN list in a login acceptance message or a login rejection message sent to the UE based on the information indicating whether the UE supports an equivalent SNPN or an equivalent SNPN list included in the login request message received from the UE.

[0243] For example, when the login request message includes information indicating that the UE supports an equivalent SNPN or an equivalent SNPN list, and when the AMF supports an equivalent SNPN list and the AMF allows the login request, the AMF may send a login acceptance message to the UE including information indicating that the network supports an equivalent SNPN or an equivalent SNPN list, and including an equivalent SNPN list.

[0244] In addition, in the case where the login request message includes information indicating that the UE supports an equivalent SNPN or an equivalent SNPN list, and the AMF does not support an equivalent SNPN list and the AMF allows the login request, the AMF may send a login acceptance message to the UE that includes information indicating that the network does not support an equivalent SNPN or an equivalent SNPN list, and does not include an equivalent SNPN list.

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

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

[0247] In addition, the UE can identify whether the network supports an equivalent SNPN or an equivalent SNPN list based on the information indicating whether the network supports an equivalent SNPN or an equivalent SNPN list included in a login acceptance message or a login rejection message received from the AMF.

[0248] In addition, the UE can identify an equivalent SNPN relative to the current SNPN based on the equivalent SNPN list included in the login acceptance message or the login rejection message received from the AMF. [2.7. Description of identification information in this embodiment]

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

[0250] The first identification information is information indicating whether the UE has the ability to store the first NSSAI and / or whether the UE has the function of storing condition information associated with the S-NSSAI included in the first NSSAI, and whether the UE has the control function based on the condition information. The first identification information may also be the functional information of the UE.

[0251] The first identification information may also be information indicating that the UE has a function of storing condition information associated with the S-NSSAI and / or performing control based on the storage. It should be noted that the first identification may also exist separately for each type of condition information.

[0252] Specifically, the first identification information may be information indicating whether the device has the function of storing conditional information related to location and / or performing control based on storage that is associated with S-NSSAI, or information indicating whether the device has the function of storing conditional information related to time and / or performing control based on storage that is associated with S-NSSAI, or both.

[0253] In this case, the information indicated by the first identification information may also be represented by multiple identification information. Specifically, sending and receiving the first identification information may refer to sending and receiving the second identification information indicating whether the function of storing the conditional information related to the location associated with the S-NSSAI and / or the control based on the storage is available and / or the third identification information indicating whether the function of storing the conditional information related to the time associated with the S-NSSAI and / or the control based on the storage is available.

[0254] The tenth identification information is an NSSAI IE (Information Element) including the first NSSAI. The tenth identification information may include at least one of the eleventh to fourteenth identification information.

[0255] Specifically, one or more eleventh identification information and / or one or more twelfth identification information and / or one or more thirteenth identification information and / or one or more fourteenth identification information may be included in the tenth identification information.

[0256] The eleventh identification information may be information indicating S-NSSAI associated with identification information indicating a specific condition (condition of UE). The specific condition may be a condition indicated by the twelfth identification information and / or the thirteenth identification information.

[0257] The eleventh identification information may be an S-NSSAI IE, which may include the S-NSSAI of the current PLMN or SNPN and / or the S-NSSAI of the HPLMN or HSNPN mapped with the S-NSSAI. The S-NSSAI of the HPLMN or HSNPN mapped with the S-NSSAI of the current PLMN or SNPN may be a mapped S-NSSAI.

[0258] The S-NSSAI indicated by the eleventh identification information may be the S-NSSAI requested by the UE or other information. In other words, the eleventh identification information may be information included in the request NSSAI IE sent from the UE or information not included in the request NSSAI IE.

[0259] When the twelfth identification information is associated with the eleventh identification information, under the condition indicated by the twelfth identification information, the UE may identify the S-NSSAI indicated by the eleventh identification information as an available S-NSSAI and / or an allowed S-NSSAI. The twelfth identification information is information indicating the condition of the UE that can utilize the associated S-NSSAI. The condition that the S-NSSAI can be utilized as indicated by the twelfth identification information is expressed as the first condition.

[0260] When the condition of the UE matches the first condition, each device can identify that the UE allows the sending of a login request message and / or a PDU session establishment request message using the S-NSSAI associated with the first condition.

[0261] In other words, each device can identify that a request for login using the S-NSSAI associated with the first condition and / or a request for establishment of a PDU session using the S-NSSAI associated with the first condition is allowed when the UE is entering the first condition and / or has entered the first condition and / or the UE's condition is consistent with the first condition.

[0262] In other words, each device can identify that a request for login using the S-NSSAI associated with the first condition and / or a request for establishment of a PDU session using the S-NSSAI associated with the first condition is not allowed when the UE is not in the first condition and / or leaves the first condition and / or the UE's condition is inconsistent with the first condition.

[0263] That is, when allowing NSSAI and / or setting NSSAI to include S-NSSAI associated with the first condition, the UE may include the S-NSSAI in the login request message and send it if it matches the first condition. However, when it does not match the first condition, the S-NSSAI may not be included in the login request message and sent it.

[0264] Similarly, when the NSSAI is allowed to include an S-NSSAI associated with the first condition, the UE may send a PDU session establishment request message together with the S-NSSAI when the first condition is matched, but may not send the PDU session establishment request message together with the S-NSSAI when the second condition is not matched.

[0265] On the other hand, when the thirteenth identification information is associated with the eleventh identification information, under the condition indicated by the thirteenth identification information, the UE may identify the S-NSSAI indicated by the eleventh identification information as an unusable S-NSSAI and / or an unallowed S-NSSAI and / or a rejected S-NSSAI. The condition of not allowing the use of S-NSSAI indicated by the thirteenth identification information may be expressed as a second condition.

[0266] Each device can identify that the UE allows the sending of a login request message and / or a PDU session establishment request message using the S-NSSAI associated with the first condition when the UE's condition matches the second condition.

[0267] In other words, each device can identify that a request for login using an S-NSSAI associated with the second condition and / or a request for establishment of a PDU session using an S-NSSAI associated with the first condition is not allowed and / or is prohibited when the UE is entering the second condition and / or has entered the second condition and / or the UE's condition is consistent with the second condition.

[0268] In further words, each device can identify that a request for login using an S-NSSAI associated with the second condition and / or a request for establishment of a PDU session using an S-NSSAI associated with the first condition is allowed and / or not prohibited when the UE is not in the second condition and / or leaves the second condition and / or the UE's condition is inconsistent with the second condition.

[0269] That is, when allowing NSSAI and / or setting NSSAI to include S-NSSAI associated with the second condition, the UE cannot include the S-NSSAI in the login request message and send it when the second condition is matched. However, when it does not match the second condition, the UE can include the S-NSSAI in the login request message and send it.

[0270] Similarly, when the NSSAI is allowed to include an S-NSSAI associated with the second condition, the UE cannot send a PDU session establishment request message together with the S-NSSAI when the second condition is matched, but can send a PDU session establishment request message together with the S-NSSAI when the second condition is not matched.

[0271] The twelfth identification information includes information indicating one or more conditions under which the associated UE can utilize and / or allow the S-NSSAI represented by the one or more eleventh identification information for establishing the association. The twelfth identification information may include one or more information related to location and / or time. In other words, the conditional information included in the twelfth identification information may be information related to location and / or information related to time.

[0272] The twelfth identification information may also be expressed as conditional information. In the case where the twelfth identification information includes information indicating one or more conditions, each piece of information included in the twelfth identification information may also be expressed as conditional information. In other words, the conditional information in this specification may refer to information indicating one or more conditions.

[0273] It should be noted that, here, being able to utilize and / or allow S-NSSAI may mean allowing the sending of a login request message that includes S-NSSAI in the request NSSAI IE and / or allowing the sending of a PDU session establishment request message for establishing a PDU session that uses S-NSSAI.

[0274] Each device can identify that the UE can utilize and / or allow the S-NSSAI represented by one or more eleventh identification information for establishing an association when the condition of the UE is consistent with the first condition indicated by the twelfth identification information.

[0275] The thirteenth identification information includes information indicating one or more conditions that the associated UE cannot utilize and / or does not allow and / or rejects the S-NSSAI represented by one or more eleventh identification information for establishing the association. The thirteenth identification information may include one or more location-related information and / or time-related information. In other words, the condition information included in the thirteenth identification information may be location-related information and / or time-related information.

[0276] The thirteenth identification information may also be expressed as conditional information. In the case where the thirteenth identification information includes information indicating one or more conditions, each piece of information included in the thirteenth identification information may also be expressed as conditional information. In other words, the conditional information in this specification may refer to information indicating one or more conditions.

[0277] Each device can identify that the UE cannot utilize and / or does not allow and / or rejects the S-NSSAI represented by one or more eleventh identification information for establishing an association when the UE's condition is consistent with the condition indicated by the thirteenth identification information.

[0278] The TAI included in the TAI list included in the twelfth identification information and the thirteenth identification information may be included in the TAI list indicating the registration area or may be included in the TAI list of the registration area.

[0279] The information related to the location may be condition information related to the location, or may be a TAI list and / or area information constituting the TAI.

[0280] Area information is information that is not mapped to area information identified by a tracking area. In other words, area information is location-related information that is not associated with a TA. Area information may be information associated with a service, and may also be expressed as a service area.

[0281] The information related to time may be information indicating time-related conditions. The information related to time may be a timer value or information indicating a specific period.

[0282] In the case where the time-related information included in the twelfth identification information is a timer value, it may mean that, during the counting of the timer using the timer value, the UE can use and / or allow the S-NSSAI represented by one or more eleventh identification information associated with the twelfth identification information. The timer using the timer value included in the twelfth identification information may also be expressed as a timer that restricts the use of the S-NSSAI.

[0283] On the other hand, when the time-related information included in the thirteenth identification information is a timer value, it may mean that, during the counting of the timer using the timer value, the UE cannot use and / or does not allow and / or rejects the S-NSSAI represented by one or more eleventh identification information associated with the thirteenth identification information. The timer using the timer value included in the thirteenth identification information may also be expressed as a timer that restricts the use of the S-NSSAI.

[0284] In the case where the time-related information included in the twelfth identification information indicates a period, it may mean that during the period indicated by the twelfth identification information, the UE can utilize and / or allow the S-NSSAI represented by one or more eleventh identification information associated with the twelfth identification information.

[0285] On the other hand, in the case where the time-related information included in the thirteenth identification information represents a period, it may mean that during the period indicated by the thirteenth identification information, the UE cannot utilize and / or does not allow and / or rejects the S-NSSAI represented by one or more eleventh identification information associated with the thirteenth identification information.

[0286] When the twelfth identification information and / or the thirteenth identification information includes information indicating a plurality of conditions, it may mean that the condition indicated by each piece of identification information satisfies the condition indicated by all the information included in each piece of identification information.

[0287] Specifically, in a case including the twelfth identification information / thirteenth identification information, information related to time, and information related to location, it may be that during the period represented by the time-related information and / or during the execution of the timer, the state in which the UE is located at the position represented by the location-related information is the condition indicated by the twelfth identification information / thirteenth identification information.

[0288] In other words, in a case including the twelfth identification information / thirteenth identification information, information related to time, and information related to location, it may be that even during the period represented by the time-related information and / or during the execution of the timer, the state in which the UE is not located at the location represented by the location-related information is not the condition indicated by the twelfth identification information / thirteenth identification information.

[0289] Alternatively, in a case where the twelfth identification information and / or the thirteenth identification information includes information indicating multiple conditions, it may mean that the conditions indicated by each identification information satisfy the conditions indicated by at least one information included in each identification information.

[0290] Specifically, in the case of including the twelfth identification information / thirteenth identification information, time-related information and location-related information, it may be that as long as during the period represented by the time-related information and / or the timer is executed, even if the UE is not located at the position represented by the location-related information, the state is the condition indicated by the twelfth identification information / thirteenth identification information.

[0291] The fourteenth identification information is information indicating that the S-NSSAI indicated in the eleventh identification information is rejected according to a specific condition, and may be a rejection cause value. The S-NSSAI indicated in the eleventh identification information associated with the fourteenth identification information may be expressed as the S-NSSAI included in the first NSSAI and / or / the first S-NSSAI.

[0292] The fourteenth identification information may be sent and received between devices using the Reject NSSAI IE or the Extended Reject NSSAI IE.

[0293] The first NSSAI is an NSSAI including one or more S-NSSAIs associated with a specific condition. The specific condition may be a condition that the corresponding one or more S-NSSAIs can be used and / or allowed, or a condition that the corresponding one or more S-NSSAIs cannot be used or are not allowed to be used and / or are refused to be used. The specific condition may be represented by condition information.

[0294] In other words, the first NSSAI and / or the first S-NSSAI included in the first NSSAI may be NSSAI and / or S-NSSAI that can be used under the condition that the association is established, or may be NSSAI and / or S-NSSAI that is not allowed under the condition that the association is established.

[0295] The first NSSAI, which is a set of S-NSSAI and / or mapped S-NSSAI that can be used under the condition of establishing an association, can be expressed as the second NSSAI, and the first NSSAI, which is a set of S-NSSAI and / or mapped S-NSSAI that is not allowed under the condition of establishing an association, can be expressed as the third NSSAI. It should be noted that, unless otherwise specified in this specification, the first NSSAI can be the second NSSAI and / or the third NSSAI.

[0296] The first NSSAI may be a set NSSAI and / or an allowed NSSAI and / or a rejected NSSAI and / or a pending NSSAI, or may be any other NSSAI.

[0297] When the first NSSAI is a rejection NSSAI, the first NSSAI may be the first to fourth rejection NSSAIs, or may be any other rejection NSSAIs.

[0298] The first NSSAI IE can be used between the UE and the NW to transmit and receive the first NSSAI and / or the first S-NSSAI included in the first NSSAI. The first NSSAI IE (Information Element) can be a set NSSAI IE and / or an allow NSSAI IE and / or a reject NSSAI IE and / or an extended reject NSSAI IE and / or a pending NSSAI IE, or any other IE.

[0299] The first NSSAI IE may include an S-NSSAI IE and condition information associated with the S-NSSAI IE. The condition information may include information related to location and / or information related to time. In other words, the condition information may refer to information related to location and / or information related to time.

[0300] The information related to the location may be condition information related to the location, or may be a TAI list and / or area information constituting the TAI.

[0301] Area information is information that is not mapped to area information identified by a tracking area. In other words, area information is location-related information that is not associated with a TA. Area information may be information associated with a service, and may also be expressed as a service area.

[0302] The information related to time may be information indicating time-related conditions. The information related to time may be a timer value or information indicating a specific period. The information indicating a specific period may be composed of a start time and an end time of the period.

[0303] The first NSSAI and / or condition information associated with the first NSSAI (information indicating the first condition and / or the second condition) may be information pre-set in the UE, or may be information sent from the core network to the UE.

[0304] The UE may include the S-NSSAI of the current PLMN or SNPN in the first NSSAI for storage, and store the S-NSSAI of the HPLMN or HSNPN in the set of mapped S-NSSAIs for the first NSSAI. Alternatively, the S-NSSAI (mapped S-NSSAI) of the HPLMN or HSNPN may be stored in the first NSSAI.

[0305] Each device may control not to perform NSAC on the S-NSSAI and / or the mapped S-NSSAI included in the first NSSAI. In other words, control may be performed in the AMF and / or NSACF, etc., so that the S-NSSAI and / or the mapped S-NSSAI included in the first NSSAI do not become the object of NSAC. [3. Description of Processes Used in Each Embodiment]

[0306] Next, the procedures used in each embodiment are described. It should be noted that the procedures used in each embodiment include a registration procedure and a network-initiated de-registration procedure. Including. Each procedure is described below.

[0307] It should be noted that, in each embodiment, Figure 2As described above, the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are respectively configured as the same device (that is, the same physical hardware or the same logical hardware or the same software) is used as an example for explanation. However, the content described in this embodiment can also be applied to the case where they are configured as different devices (that is, different physical hardware, or different logical hardware or different software). For example, data can be sent and received directly between them, data can be sent and received via the N26 interface between AMF and MME, and data can be sent and received via UE. [3.1. Login process]

[0308] First, use Figure 6 The registration procedure is described. Hereinafter, this process refers to the login process. The login process is a process for the UE to log in to the access network_B and / or the core network_B and / or the DN. If the UE is not logged in to the network, this process can be performed at any time, such as when the power is turned on. In other words, if the UE is in a non-logged-in state (5GMM-DEREGISTERED state), this process can be started at any time. In addition, each device (especially the UE and the AMF) can be transformed into a logged-in state (5GMM-REGISTEDEDstate) based on the completion of the login process. It should be noted that each login state can be managed by each device for each access. Specifically, each device can independently manage the login state (logged-in state or non-logged-in state) for 3GPP access and the login state for non-3GPP access.

[0309] Moreover, the registration process may be a process for updating location registration information of the UE in the network and / or periodically notifying the network of the status of the UE from the UE and / or updating specific parameters related to the UE in the network.

[0310] The UE can start the login process when moving across a TA (tracking area). In other words, the UE can start the login process when it moves to a TA different from the TA represented by the maintained TA list (TAI list or login area). Moreover, the UE can also start this process when the backoff timer or other timer in execution expires. Moreover, the UE can also start the login process when the context of each device needs to be updated due to the disconnection or disabling of the PDU session. Moreover, the UE can also start the login process when the capability information and / or preference related to the establishment of the UE's PDU session changes. Moreover, the UE can also start the login process periodically. Moreover, the UE can start the login process based on the completion of the UE configuration update procedure (Generic UE configuration update procedure) or based on the completion of the login process or based on the completion of the PDU session establishment process or based on the completion of the PDU session management process or based on the information received from the network in each process or based on the expiration or stop of the backoff timer. It should be noted that the UE can perform the login process at any timing, and is not limited to this.

[0311] For example, when the UE enters the condition indicated by the first condition information in which an association is established with the S-NSSAI included in the first NSSAI stored by the UE and / or the UE exits from the second condition in which an association is established with the S-NSSAI included in the first NSSAI stored by the UE, UE_A10 may send a login request message and / or start a login process.

[0312] It should be noted that, when the condition information associated with the S-NSSAI included in the first NSSAI stored by the UE includes information representing multiple conditions, the UE may consider all conditions or at least one condition.

[0313] In other words, in a case where information indicating a plurality of conditions is included in the condition information, the UE can recognize a state in which the conditions indicated by the information indicating all the conditions are satisfied as the condition indicated by the condition information.

[0314] Specifically, in a case where the condition information is composed of information related to location and information related to time, on the basis that the condition represented by the information related to location matches the condition of the UE, the state in which the condition represented by the information related to time matches the condition of the UE may mean that the condition of the UE matches the condition indicated in the condition information and / or has entered the condition and / or is entering the condition.

[0315] In the case where the condition information is composed of information related to location and information related to time, the state in which at least one of the conditions represented by the information related to location and the conditions represented by the information related to time does not match the conditions of the UE may mean that the conditions of the UE do not match the conditions shown in the condition information and / or have left the conditions and / or are leaving the conditions.

[0316] In other words, in the case where the condition information includes information representing multiple conditions, and the conditions of the UE match and / or do not match the conditions indicated by all the information included in the condition information, the UE can start the login request process by including the S-NSSAI and / or NSSAI associated with the condition information in the request NSSAI IE and sending a login request message.

[0317] In the case where the condition information includes information representing multiple conditions, if any of the conditions indicated by the information included in the condition information is not matched, the UE can start the login request process by sending a login request message including one or more S-NSSAI and / or NSSAI associated with the condition information in the request NSSAI IE.

[0318] It should be noted that the process used to change the above-mentioned UE from a state of never logging in to the network to a logged-in state can be set as an initial registration procedure (initial registration procedure) or a registration procedure for initial registration (registration procedure for initial registration), and the registration procedure performed when the UE is already logged in to the network can be set as a registration procedure for mobility and periodic registration update (registration procedure for mobility and periodic registration update) or a mobility and periodic registration procedure (mobility and periodic registration procedure).

[0319] Furthermore, the registration procedure for mobility and periodic registration update may be a process independent of the registration procedure for mobility registration update and the registration procedure for periodic registration update.

[0320] Figure 6 The new AMF (new AMF) 141 indicates the AMF logged in by UE_A10 through this process, and the old AMF (old AMF) 142 indicates the AMF logged in by UE through the process before this process. When no change of AMF occurs in this process, the interface between old AMF142 and new AMF141 and the process between old AMF142 and new AMF141 will not occur, and the new AMF141 can be the same device as the old AMF142. In this embodiment, when recorded as AMF, it can mean the new AMF141, it can also mean the old AMF142, or it can mean both. It should be noted that the new AMF141 and the old AMF142 can be AMF140.

[0321] First, UE_A10 starts the registration process by sending a registration request message to the new AMF141 (S600)(S602)(S604). Specifically, the UE sends an RRC message including a registration request message to 5GAN120 (or gNB) (S600). It should be noted that the registration request message may be a NAS message sent and received on the N1 interface. In addition, the RRC message may be a control message sent and received between the UE and 5G AN120 (or gNB). In addition, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. It should be noted that the NAS layer is a higher layer than the RRC layer.

[0322] Here, UE_A10 can at least include the first identification information in the login request message and / or the RRC message for transmission. Moreover, UE_A10 can include the identification information indicating the type of this process in the login request message and / or the RRC message for transmission.

[0323] Here, the identification information indicating the type of this process may be a 5GS registration type IE (5GS registrationtype IE), or it may be information indicating that this process is a registration process for initial registration (initial registration), for updating registration information accompanying mobility (mobility registration updating), for periodic registration information updating (periodic registration updating), for emergency registration (emergency registration), or for SNPN onboarding registration.

[0324] In other words, in the case where this process is a login process for initial login, UE_A10 can send a login request message including a 5GS login type IE indicating initial registration. In the case where this process is a login process for updating login information accompanying mobility, UE_A10 can send a login request message including a 5GS login type IE indicating mobile login updating (mobility registration updating). In the case where this process is a login process for periodic login information updating, UE_A10 can send a login request message including a 5GS login type IE indicating periodic login information updating (periodic registration updating). In the case where this process is an emergency login, UE_A10 can send a login request message including a 5GS login type IE indicating emergency login (emergency registration). In the case where this process is a login process for the SNPN onboarding service, UE_A10 can send a login request message including a 5GS login type IE indicating the SNPN onboarding service (SNPN onboarding registration).

[0325] UE_A10 may include the capability information of UE_A10 in the login request message to inform the network of the functions supported by the UE. Here, the capability information of the UE may be the 5G MM capability IE (5G MM capability) of the 5GS. The first identification information may be the information included in the 5G MM capability IE of the 5GS.

[0326] UE_A10 can include these identification information and / or IE in control messages different from these, for example, control messages of layers lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer) and send them. It should be noted that UE_A10 can send these identification information to indicate that UE_A10 supports each function, or it can indicate the UE's request, or it can indicate both. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, or can be sent and received as different identification information.

[0327] UE_A10 may send capability information indicating support for the function of managing the maximum number of UEs connected to a slice when it has the function of managing the maximum number of UEs connected to a slice or requests at least one S-NSSAI that needs to be managed for the maximum number of UEs connected to a slice. UE_A10 may notify the network of the function of storing the fourth rejected NSSAI by sending capability information.

[0328] Moreover, UE_A10 may also include capability information indicating support for the NSSAA function in the login request message and send it when the UE has the NSSAA function or when at least one S-NSSAI identifying a slice requiring NSSAA and / or an S-NSSAI identifying a slice requiring NSSAA is requested to be associated as a mapped S-NSSAI. UE_A10 may request that the UE be regarded as a UE having the NSSAA function in the network and that an authentication and authorization process based on the NSSAA function be performed in a process related to the UE by sending capability information indicating support for the NSSAA function.

[0329] In the case where the UE stores "the allowed NSSAI corresponding to the PLMN or SNPN requested by the UE and the access type requested by the UE" and / or stores the "set NSSAI for the requested PLMN or SNPN" and / or stores the "default set NSSAI" and / or stores the "first NSSAI" and the first condition of establishing an association with the S-NSSAI included in the "first NSSAI" matches the UE's condition and / or stores the "first NSSAI" and the second condition of establishing an association with the S-NSSAI included in the "first NSSAI" does not match the UE's condition, the UE may include the request NSSAI IE in the login request message and send it to the requested PLMN or SNPN.

[0330] The request NSSAI IE may include a request NSSAI consisting of the S-NSSAI (SST and / or SD) of the requested PLMN or SNPN and "one or more mapped S-NSSAIs for the request NSSAI" consisting of the S-NSSAI (SST and / or SD) of the HPLMN or HSNPN.

[0331] In other words, when the UE is not roaming, the UE may include the request NSSAI in the login request message and send it; when the UE is roaming, the UE may include the request NSSAI and one or more mapping S-NSSAIs for the request NSSAI in the login request message and send it.

[0332] It should be noted that, except for the case where this process is a login process for loading services of SNPN, the UE may include the request NSSAI in the login request message.

[0333] Alternatively, in the case where the UE stores "an allowed NSSAI corresponding to a PLMN different from the PLMN requested by the UE or an SNPN different from the SNPN requested by the UE and an access type requested by the UE", and the allowed NSSAI or the TAI included in the login area associated with the S-NSSAI included in the allowed NSSAI belongs to the PLMN or SNPN requested by the UE, the UE may include the request NSSAI in the login request message and send it to the requested PLMN or SNPN.

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

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

[0336] The UE may select one or more S-NSSAIs from the stored allowed NSSAIs and / or set NSSAIs and / or first NSSAIs, including sending them in the request NSSAI IE.

[0337] Specifically, when UE_A10 stores an allowed NSSAI associated with the requested PLMN or SNPN and the requested access type, UE_A10 may include the allowed NSSAI or part thereof, that is, one or more S-NSSAIs included in the allowed NSSAI, in the allowed NSSAI IE and send it.

[0338] And / or, in the case where UE_A10 stores a set NSSAI associated with the requested PLMN or SNPN, UE_A10 may include the set NSSAI or a part thereof, that is, one or more S-NSSAIs included in the set NSSAI, in the request NSSAI and send it.

[0339] And / or, in the case where UE_A10 stores a first NSSAI associated with the requested PLMN or SNPN and / or access type, and the first condition indicated by the condition information associated with the S-NSSAI included in the first NSSAI is consistent with the condition of UE_A10, UE_A10 may include the S-NSSAI in the request NSSAI IE and send it.

[0340] And / or, in the case where UE_A10 stores a first NSSAI associated with the requested PLMN or SNPN and / or access type, and the second condition indicated by the condition information associated with the S-NSSAI included in the first NSSAI is inconsistent with the condition of UE_A10, UE_A10 may include the S-NSSAI in the request NSSAI IE for sending.

[0341] And / or, in the case where UE_A10 stores a list of mapped S-NSSAIs of allowed NSSAIs associated with the requested PLMN or SNPN and / or access type, UE_A10 may select a mapped S-NSSAI included in the list of mapped S-NSSAIs of allowed NSSAIs as a mapped S-NSSAI (SST and / or SD) of the S-NSSAI IE included in the request NSSAI IE, and include the selected mapped S-NSSAI in the request NSSAI IE for sending.

[0342] And / or, in the case where UE_A10 stores a list of mapping S-NSSAIs for setting NSSAIs associated with the requested PLMN or SNPN, UE_A10 may select a mapping S-NSSAI included in the list of mapping S-NSSAIs for setting NSSAIs as a mapping S-NSSAI (SST and / or SD) of the S-NSSAI IE included in the request NSSAI IE, and include the selected mapping S-NSSAI in the request NSSAI IE for sending.

[0343] And / or, in the case where UE_A10 stores a list of mapped S-NSSAIs of the first NSSAI associated with the requested PLMN or SNPN and / or access type, UE_A10 may select a mapped S-NSSAI included in the list of mapped S-NSSAIs of the first NSSAI as a mapped S-NSSAI (SST and / or SD) of the S-NSSAI IE included in the request NSSAI IE, and include the selected mapped S-NSSAI in the request NSSAI IE for sending.

[0344] In other words, UE_A10 may include the S-NSSAI IE consisting of the S-NSSAI of the current PLMN or SNPN and the mapped S-NSSAI of the HPLMN or HSNPN in the request NSSAI IE and send it in one or more login request messages when roaming.

[0345] And / or, in the case where UE_A10 stores "an allowed NSSAI associated with a PLMN other than the requested PLMN or an SNPN other than the requested SNPN and the requested access type", and in the case where the TAI included in the login area (TAI list) associated with the allowed NSSAI or the S-NSSAI included in the allowed NSSAI is associated with the requested PLMN or the requested SNPN, UE_A10 may include the allowed NSSAI or one or more S-NSSAIs included in the allowed NSSAI in the request NSSAI, and include the request NSSAI in the request NSSAI IE for sending.

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

[0347] The request NSSAI may be constructed to include one or more of the above-mentioned S-NSSAI. However, UE_A10 may control the one or more S-NSSAI included in the request NSSAI to be non-repeated.

[0348] Hereinafter, a control method of the S-NSSAI included in the request NSSAI included in the request NSSAI IE and / or a mapping S-NSSAI included in "one or more mapping S-NSSAI for the request NSSAI" included in the request NSSAI IE and / or a generation method of the request NSSAI IE will be summarized in the case where UE_A10 stores at least one of the first to fourth rejection NSSAIs. It should be noted that the first to fourth rejection NSSAIs here may refer to the first to fourth rejection NSSAIs associated with the requested PLMN or EPLMN or the requested SNPN or ESNPN.

[0349] In the case where UE_A10 stores a rejection NSSAI for the requested PLMN or SNPN, UE_A10 may send the request NSSAI without including the S-NSSAI included in the rejection NSSAI.

[0350] Specifically, when UE_A10 stores the "first rejection NSSAI for establishing an association with the requested PLMN or SNPN", UE_A10 may send the S-NSSAI included in the first rejection NSSAI without including it in the request NSSAI. In other words, UE_A10 may also perform the following control: one or more S-NSSAI included in the request NSSAI is not the S-NSSAI included in the "first rejection NSSAI for establishing an association with the requested PLMN or SNPN" stored by the UE.

[0351] However, in the case where UE_A10 also stores a list of mapped S-NSSAIs for the "first rejected NSSAI associated with the requested PLMN or SNPN", and in the case where one or more mapped S-NSSAIs are stored that are not included in the list of mapped S-NSSAIs for the first rejected NSSAI but are included in the list of mapped S-NSSAIs for the set NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN that maps the mapped S-NSSAI so that it can be included in the requested NSSAI.

[0352] In the case where UE_A10 stores one or more mapping S-NSSAIs for a first rejected NSSAI when roaming, and UE_A10 stores one or more mapping S-NSSAIs that are not included in the one or more mapping S-NSSAIs for the first rejected NSSAI stored by UE_A10, but are included in one or more mapping S-NSSAIs for the set NSSAI, the UE may include the S-NSSAI included in the first rejected NSSAI associated with the mapping S-NSSAI together with the mapping S-NSSAI in the login request message and send it.

[0353] Moreover, in the case where UE_A10 stores at least one "second rejected NSSAI associated with the requested PLMN or EPLMN or SNPN or ESNPN and the current login area", UE_A10 may send the S-NSSAI included in these second rejected NSSAI without including it in the request NSSAI. In other words, UE_A10 may control as follows: one or more S-NSSAI included in the request NSSAI is not the S-NSSAI included in each "second rejected NSSAI associated with the requested PLMN or EPLMN or with the requested SNPN or ESNPN and the current login area" stored by UE_A10.

[0354] In the case where the information representing the current login area stored by UE_A10 includes a TAI belonging to one or more PLMNs different from the requested PLMN or one or more SNPNs different from the requested SNPN, and the different one or more PLMNs or SNPNs are the ESNPN of the requested PLMN or the requested SNPN, UE_A10 may also perform the following control: the one or more S-NSSAIs included in the requested NSSAI are not the S-NSSAIs included in the “second rejected NSSAIs for establishing an association with one of the different one or more PLMNs or SNPNs and the current login area” stored by UE_A10.

[0355] In other words, when the information representing the current login area stored by UE_A10 includes a TAI belonging to one or more PLMNs or SNPNs different from the requested PLMN or SNPN, UE_A10 may not include the S-NSSAI included in the "second rejected NSSAI for establishing an association with one PLMN or SNPN among the different one or more PLMNs or SNPNs and the current login area" in the requested NSSAI.

[0356] However, in the case where UE_A10 also stores a list of mapped S-NSSAIs for "a second rejected NSSAI associated with the requested PLMN or EPLMN or SNPN or ESNPN and the current login area", and in the case where one or more mapped S-NSSAIs are stored that are not included in the list of mapped S-NSSAIs for the second rejected NSSAI but are included in the list of mapped S-NSSAIs for the set NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN that maps the mapped S-NSSAI so that it can be included in the requested NSSAI.

[0357] In the case where UE_A10 stores one or more mapping S-NSSAIs for the second rejected NSSAI when roaming, and UE_A10 stores one or more mapping S-NSSAIs that are not included in the one or more mapping S-NSSAIs for the second rejected NSSAI stored by UE_A10, but are included in the one or more mapping S-NSSAIs for the set NSSAI, the S-NSSAI included in the second rejected NSSAI associated with the mapping S-NSSAI can be included in the login request message and sent together with the mapping S-NSSAI.

[0358] Moreover, in the case where UE_A10 stores the "third rejection NSSAI associated with the requested PLMN or SNPN", UE_A10 may send the S-NSSAI included in the third rejection NSSAI without including it in the request NSSAI IE. In other words, UE_A10 may also perform the following control: one or more S-NSSAIs included in the request NSSAI IE are not the S-NSSAIs included in the "third rejection NSSAI associated with the requested PLMN or SNPN" stored by UE_A10.

[0359] Moreover, in the case where UE_A10 stores at least one "third rejected NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN", UE_A10 may also send the S-NSSAI included in the third rejected NSSAI without including it in the request NSSAI IE. In other words, UE_A10 may control as follows: one or more S-NSSAI included in the request NSSAI IE is not the S-NSSAI included in each "third rejected NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN" stored by UE_A10.

[0360] In the case that UE_A10 stores neither the mapped S-NSSAI of the first rejected NSSAI nor the mapped S-NSSAI of the second rejected NSSAI, UE_A10 may control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it is neither included in the first rejected NSSAI nor in the second rejected NSSAI.

[0361] In other words, when UE_A10 does not store the mapped S-NSSAI for the rejected NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it is neither included in the first rejected NSSAI nor in the second rejected NSSAI.

[0362] Moreover, when UE_A10 is roaming, when UE_A10 stores the mapping S-NSSAI of the first rejected NSSAI or the mapping S-NSSAI of the second rejected NSSAI, and when UE_A10 stores a mapping S-NSSAI that is neither included in the list of mapping S-NSSAI of the first rejected NSSAI stored by UE_A10 nor in the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10, but included in the list of mapping S-NSSAI of the set NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it can be included in the first rejected NSSAI or the second rejected NSSAI stored by UE_A10.

[0363] Moreover, regardless of whether UE_A10 stores the mapped S-NSSAI of the first rejected NSSAI or the mapped S-NSSAI of the second rejected NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it is not included in the third rejected NSSAI.

[0364] In other words, UE_A10 can control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it neither includes the first rejected NSSAI stored in UE_A10, nor the second rejected NSSAI stored in UE_A10, nor the third rejected NSSAI stored in UE_A10. However, when UE_A10 is roaming, when UE_A10 stores the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI, and when UE_A10 stores a mapping S-NSSAI that is neither included in the list of mapping S-NSSAI of the first rejected NSSAI stored by UE_A10 nor in the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10, but included in the list of mapping S-NSSAI of the set NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN that maps the mapping S-NSSAI so that it can be included in the login request message.

[0365] The S-NSSAI of the current PLMN or SNPN mapped with the mapped S-NSSAI may be the S-NSSAI pointing to the current PLMN or SNPN mapped with the mapped S-NSSAI.

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

[0367] In addition, when UE_A10 is roaming, when UE_A10 stores the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI, and when UE_A10 stores a mapping S-NSSAI that is neither included in the list of mapping S-NSSAI of the first rejected NSSAI stored by UE_A10 nor in the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10, but included in the list of mapping S-NSSAI of the set NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN mapped to the mapping S-NSSAI so that it can be included in the login request message together with the mapping S-NSSAI.

[0368] It should be noted that, when UE_A10 is roaming, if UE_A10 stores the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI, UE_A10 can control the mapping S-NSSAI included in the login request message so that it is a mapping S-NSSAI that is neither included in the list of mapping S-NSSAI of the first rejected NSSAI stored by UE_A10, nor in the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10.

[0369] In other words, when UE_A10 stores one or more mapping S-NSSAIs for rejected NSSAIs when roaming, and the mapping S-NSSAI included in one or more stored mapping S-NSSAIs for setting NSSAIs is not included in the one or more mapping S-NSSAIs for the rejected NSSAIs, the S-NSSAI included in the setting NSSAI associated with the mapping S-NSSAI can be included in the login request message together with the mapping S-NSSAI in the request NSSAI.

[0370] It may be that, when the UE is not roaming, the S-NSSAI included in the third rejected NSSAI is controlled not to be included in the requested NSSAI; when the UE is roaming, the S-NSSAI included in the third rejected NSSAI is controlled not to be included in the requested NSSAI as the S-NSSAI associated with the mapped S-NSSAI.

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

[0372] On the other hand, in the case of UE roaming, the S-NSSAI of the current PLMN or SNPN included in the request NSSAI is included in the set NSSAI for the current PLMN or SNPN, and is not associated with the S-NSSAI included in the third rejection NSSAI.

[0373] In other words, when the UE is not roaming, the UE may include one or more S-NSSAIs included in the set NSSAI for the current PLMN or SNPN and not included in the third rejected NSSAI in the requested NSSAI.

[0374] On the other hand, in the case of UE roaming, the UE may include in the request NSSAI the S-NSSAI included in the setup NSSAI for the current PLMN or SNPN and not associated with the S-NSSAI included in the third reject NSSAI.

[0375] However, when the UE is roaming, if there is one or more S-NSSAIs that are not included in the third rejected NSSAI but are included in one or more stored mapped S-NSSAIs for the set NSSAI, the UE can include the S-NSSAI as the S-NSSAI included in the set NSSAI for the current PLMN or SNPN associated with the mapped S-NSSAI in the login request message together with the mapped S-NSSAI and send it. Specifically, in this case, the UE can form a request NSSAI IE using the mapped S-NSSAI and an NSSAI IE including the S-NSSAI IE, wherein the S-NSSAI IE includes the S-NSSAI associated with the mapped S-NSSAI.

[0376] Moreover, UE_A10 may send the S-NSSAI or the S-NSSAI related to the S-NSSAI without including it in the request NSSAI when the back-off timer corresponding to a certain S-NSSAI is valid, in other words, when the back-off timer is executing or before the back-off timer stops. Specifically, when the S-NSSAI corresponding to the back-off timer is the S-NSSAI associated with the requested PLMN or SNPN or the S-NSSAI included in the NSSAI associated with the requested PLMN or SNPN, UE_A10 may also send the S-NSSAI without including it in the request NSSAI until the back-off timer counts or the back-off timer expires or stops.

[0377] Hereinafter, the situation where a corresponding backoff timer is established with a certain S-NSSAI included in the fourth rejected NSSAI and is valid and / or the backoff timer is being executed may mean that the S-NSSAI is valid and / or the fourth rejected NSSAI is valid.

[0378] Moreover, in the case where UE_A10 stores a list of mappings S-NSSAI of the fourth rejected NSSAI, the fourth rejected NSSAI being valid may also mean that the list of mappings S-NSSAI of the fourth rejected NSSAI and the mapping S-NSSAI of the fourth rejected NSSAI are valid.

[0379] In the case where the fourth rejected NSSAI and / or the list of mapped S-NSSAIs of the fourth rejected NSSAI is managed by UE_A10 regardless of whether the backoff timer is being executed, the list of valid fourth rejected NSSAIs and / or the list of mapped S-NSSAIs of the fourth rejected NSSAIs may be the fourth rejected NSSAI stored by UE_A10 and / or the list of mapped S-NSSAIs of the fourth rejected NSSAI stored by UE_A10.

[0380] Alternatively, when the S-NSSAI corresponding to the back-off timer is associated with the HPLMN or HSNPN, UE_A10 may send the S-NSSAI of the requested PLMN or SNPN mapped with the S-NSSAI without including it in the requested NSSAI.

[0381] Moreover, in the case where the UE stores the "fourth rejected NSSAI associated with the requested PLMN or SNPN", the UE may send the S-NSSAI included in the fourth rejected NSSAI without including it in the request NSSAI. In other words, the UE may also control as follows: one or more S-NSSAIs included in the request NSSAI are not the S-NSSAIs included in the "fourth rejected NSSAI associated with the requested PLMN or SNPN" stored by the UE.

[0382] Here, in this context, the requested PLMN or SNPN may be synonymous with the registered PLMN or SNPN.

[0383] Moreover, in the case where the UE stores at least one "fourth rejected NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the SNPN", the UE may also send the S-NSSAI included in the fourth rejected NSSAI without including it in the request NSSAI. In other words, the UE may also control as follows: one or more S-NSSAIs included in the request NSSAI are not the S-NSSAIs included in each "fourth rejected NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the SNPN".

[0384] When roaming, UE_A10 may control one or more S-NSSAIs included in the request NSSAI to not include the mapped S-NSSAI of the rejected NSSAI and / or the mapped S-NSSAI of the pending NSSAI and / or the S-NSSAI of the HPLMN or HSNPN included in the fourth rejected NSSAI as the mapped S-NSSAI. In other words, UE_A10 may also control as follows: not including the S-NSSAI of the current PLMN or SNPN mapped with the S-NSSAI included in the rejected NSSAI and / or the pending NSSAI and / or the fourth rejected NSSAI in the request NSSAI.

[0385] In further other words, for the S-NSSAI included in the request NSSAI generated by UE_A10, the mapping S-NSSAI of its S-NSSAI is not included in the rejection NSSAI and / or pending NSSAI and / or the fourth rejection NSSAI stored by UE_A10. Here, the rejection NSSAI can be at least any one of the first to fourth rejection NSSAIs, including the S-NSSAI of the HPLMN or HSNPN.

[0386] Moreover, when UE_A10 is roaming, in the case where UE_A10 stores a valid mapping S-NSSAI of a fourth rejected NSSAI, and in the case where UE_A10 stores a mapping S-NSSAI that is not included in a list of mapping S-NSSAI of a first rejected NSSAI stored by UE_A10, but is included in a list of mapping S-NSSAI of a set NSSAI, the S-NSSAI of the current PLMN or SNPN included in the login request message can be controlled by UE_A10 so that it can be included in the fourth rejected NSSAI.

[0387] In other words, UE_A10 can control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it is not included in the fourth rejected NSSAI. However, in the case where UE_A10 stores a list of mapped S-NSSAIs of the fourth rejected NSSAI when UE_A10 is roaming, and in the case where UE_A10 stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAIs of the fourth rejected NSSAI stored by UE_A10 but is included in the list of mapped S-NSSAIs of the set NSSAI, the S-NSSAI of the current PLMN or SNPN mapped with the mapped S-NSSAI can be controlled so that it can be included in the login request message.

[0388] The S-NSSAI of the current PLMN or SNPN mapped with the mapped S-NSSAI may be the S-NSSAI pointing to the current PLMN or SNPN mapped with the mapped S-NSSAI.

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

[0390] In addition, when UE_A10 is roaming, in the case where UE_A10 stores a list of mapped S-NSSAIs for the fourth rejected NSSAI, and in the case where UE_A10 stores a mapped S-NSSAI that is not included in the list of mapped S-NSSAIs for the fourth rejected NSSAI stored by UE_A10, but is included in the list of mapped S-NSSAIs for the set NSSAI, the S-NSSAI of the current PLMN or SNPN mapped with the mapped S-NSSAI can be controlled so that it can be included in the login request message together with the mapped S-NSSAI.

[0391] Moreover, in the case where the UE stores the "pending NSSAI associated with the requested PLMN or SNPN", the UE may also send the S-NSSAI included in the pending NSSAI without including it in the request NSSAI IE. In other words, the UE may also control as follows: one or more S-NSSAIs included in the request NSSAI IE are not the S-NSSAIs included in the "pending NSSAI associated with the requested PLMN or SNPN" stored by the UE.

[0392] Moreover, in the case where the UE stores at least one "pending NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN", the UE may also send the S-NSSAI included in the pending NSSAI without including it in the request NSSAI IE. In other words, the UE may control as follows: one or more S-NSSAIs included in the request NSSAI IE are not the S-NSSAIs included in each "pending NSSAI associated with the EPLMN of the requested PLMN or the ESNPN of the requested SNPN".

[0393] However, in the case where UE_A10 also stores a list of mapped S-NSSAIs of "pending NSSAIs associated with the requested PLMN or EPLMN or ESNPN of the requested SNPN" (hereinafter referred to as pending NSSAI), in the case where one or more mapped S-NSSAIs are stored that are not included in the list of mapped S-NSSAIs of pending NSSAIs but included in the list of mapped S-NSSAIs of set NSSAIs, UE_A10 can control the S-NSSAI of the current PLMN or SNPN that maps the mapped S-NSSAI so that it can be included in the requested NSSAI.

[0394] In other words, in the case where UE_A10 does not store the mapped S-NSSAI of the pending NSSAI but stores the pending NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN or the S-NSSAI (mapped S-NSSAI) of the HPLMN or HSNPN included in the login request message to become the S-NSSAI that is not included in the pending NSSAI stored by UE_A10.

[0395] Moreover, when UE_A10 is roaming, if UE_A10 stores the pending NSSAI together with the mapping S-NSSAI for the pending NSSAI, and if UE_A10 stores one or more mapping S-NSSAI for the pending NSSAI that is not included in the list of mapping S-NSSAI for the set NSSAI, the UE can include the pending NSSAI associated with the mapping S-NSSAI and the S-NSSAI included in the set NSSAI together with the mapping S-NSSAI in the login request message and send them.

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

[0397] It may be that, when the UE is not roaming, the S-NSSAI included in the pending NSSAI is not included in the request NSSAI, and when the UE is roaming, the S-NSSAI included in the pending NSSAI is not included in the request NSSAI as the S-NSSAI associated with the mapped S-NSSAI. The request NSSAI may be included in the request NSSAI IE.

[0398] In other words, in the case where the UE is not roaming, the S-NSSAI of the current PLMN or SNPN included in the requested NSSAI is included in the set NSSAI for the current PLMN or SNPN, and is not included in the pending NSSAI.

[0399] On the other hand, in case of UE roaming, the S-NSSAI of the current PLMN or SNPN included in the requested NSSAI is included in the set NSSAI for the current PLMN or SNPN, and is not associated with the S-NSSAI included in the pending NSSAI.

[0400] In other words, when the UE is not roaming, the UE may include one or more S-NSSAIs included in the configured NSSAI for the current PLMN or SNPN and not included in the pending rejection NSSAI in the request NSSAI.

[0401] On the other hand, in the case of UE roaming, the UE may include in the request NSSAI an S-NSSAI that is included in the setup NSSAI for the current PLMN or SNPN and is not associated with the S-NSSAI included in the pending NSSAI.

[0402] However, when the UE is roaming, if there is one or more S-NSSAIs that are not included in the pending NSSAI but are included in one or more stored mapped S-NSSAIs for the set NSSAI, the UE can include the S-NSSAI as the S-NSSAI included in the set NSSAI for the current PLMN or SNPN associated with the mapped S-NSSAI in the login request message together with the mapped S-NSSAI and send it. Specifically, in this case, the UE can form a request NSSAI IE using the mapped S-NSSAI and an NSSAI IE including the S-NSSAI IE, wherein the S-NSSAI IE includes the S-NSSAI associated with the mapped S-NSSAI.

[0403] Hereinafter, a control method of including S-NSSAI in the request NSSAI IE and / or mapping S-NSSAI and / or a method of generating the request NSSAI IE will be summarized and described when UE_A10 stores S-NSSAI in at least one of the first to fourth rejection NSSAI and pending NSSAI. It should be noted that the first to fourth rejection NSSAI and pending NSSAI here may refer to the first to fourth rejection NSSAI and pending NSSAI associated with the requested PLMN or EPLMN or the requested SNPN or ESNPN.

[0404] When UE_A10 has neither stored the mapped S-NSSAI of the first rejected NSSAI, nor the mapped S-NSSAI of the second rejected NSSAI, nor the mapped S-NSSAI of the pending NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it is neither included in the first rejected NSSAI, nor in the second rejected NSSAI, nor in the pending NSSAI.

[0405] Moreover, in the case where UE_A10 stores the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI and / or the mapping S-NSSAI of the pending NSSAI, and in the case where UE_A10 stores a mapping S-NSSAI that is neither included in the list of mapping S-NSSAI of the first rejected NSSAI stored by UE_A10, nor in the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10, nor in the list of mapping S-NSSAI of the pending NSSAI stored by UE_A10, but included in the list of mapping S-NSSAI of the set NSSAI, the S-NSSAI of the current PLMN or SNPN included in the login request message can be controlled by UE_A10 so that it can be included in the first rejected NSSAI or the second rejected NSSAI or the pending NSSAI.

[0406] In other words, UE_A10 can control the S-NSSAI of the current PLMN or SNPN included in the login request message so that it is neither included in the first rejected NSSAI, nor in the second rejected NSSAI, nor in the third rejected NSSAI, nor in the pending NSSAI. However, when UE_A10 is roaming, when UE_A10 stores a list of mapped S-NSSAI of the first rejected NSSAI or the mapped S-NSSAI of the second rejected NSSAI or the mapped S-NSSAI of the pending NSSAI, and when UE_A10 stores a mapped S-NSSAI that is neither included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10, nor in the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10, nor in the list of mapped S-NSSAI of the pending NSSAI stored by UE_A10, but included in the list of mapped S-NSSAI of the set NSSAI, the S-NSSAI of the current PLMN or SNPN mapped with the mapped S-NSSAI can be controlled so that it can be included in the login request message.

[0407] The S-NSSAI of the current PLMN or SNPN associated with the mapped S-NSSAI may be the S-NSSAI of the current PLMN or SNPN that points to the mapped S-NSSAI mapping.

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

[0409] In addition, when UE_A10 is roaming, when UE_A10 stores a list of mapped S-NSSAI of the first rejected NSSAI or the mapped S-NSSAI of the second rejected NSSAI or the mapped S-NSSAI of the pending NSSAI, and when UE_A10 stores a mapped S-NSSAI that is neither included in the list of mapped S-NSSAI of the first rejected NSSAI stored by UE_A10, nor in the list of mapped S-NSSAI of the second rejected NSSAI stored by UE_A10, nor in the list of mapped S-NSSAI of the pending NSSAI stored by UE_A10, but included in the list of mapped S-NSSAI of the set NSSAI, UE_A10 can control the S-NSSAI of the current PLMN or SNPN mapped to the mapped S-NSSAI so that it can be included in the login request message together with the mapped S-NSSAI.

[0410] It should be noted that, when UE_A10 stores the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI and / or the pending NSSAI when UE_A10 is roaming, UE_A10 can control the mapping S-NSSAI included in the login request message so that it is neither included in the list of mapping S-NSSAI of the first rejected NSSAI stored by UE_A10, nor in the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10, nor in the mapping S-NSSAI of the pending NSSAI stored by UE_A10.

[0411] As described above, control may be performed so that the S-NSSAI and / or mapped S-NSSAI included in the request NSSAI IE is not included in the rejected NSSAI and / or pending NSSAI and / or mapped S-NSSAI for the rejected NSSAI and / or mapped S-NSSAI for the pending NSSAI stored in the UE.

[0412] However, in the case where the S-NSSAI selected from the first NSSAI is included in the request NSSAI IE, the above control may not be performed. In other words, the S-NSSAI included in the first NSSAI may be controlled so that it can be included in the rejected NSSAI and / or pending NSSAI stored by the UE, and can also be included in the request NSSAI IE.

[0413] Similarly, the mapping S-NSSAI for the S-NSSAI included in the first NSSAI can also be controlled so that it can be included in the mapping S-NSSAI for the rejected NSSAI and / or the mapping S-NSSAI for the pending NSSAI stored in the UE, and can also be included in the request NSSAI IE.

[0414] UE_A10 may include information other than these identification information in a login request message and / or an RRC message including a login request message, for example, UE ID and / or PLMN ID and / or NID and / or AMF identification information may be included in a login request message and / or an RRC message including a login request message for sending. Here, AMF identification information may refer to information that identifies an AMF or a set of AMFs, for example, it may refer to 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier), GUAMI (Globally Unique AMF Identifier).

[0415] In addition, UE_A10 can start the PDU session establishment process during the login process by including an SM message (such as a PDU session establishment request message) in the login request message, or sending an SM message (such as a PDU session establishment request message) together with the login request message.

[0416] It should be noted that UE_A10 can choose and determine whether to send these identification information to the network based on the UE's capability information and / or UE policy and / or UE status and / or user login information and / or context maintained by the UE.

[0417] When receiving the RRC message including the login request message, the 5G AN120 (or gNB) selects the AMF to transmit the login request message (S602). It should be noted that the 5G AN120 (or gNB) can select the AMF based on one or more identification information included in the login request message and / or the RRC message including the login request message.

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

[0419] It should be noted that the method for selecting AMF is not limited to this, and 5G AN (or gNB) can also select AMF based on conditions other than this. 5G AN (or gNB) extracts the login request message from the received RRC message and transmits the login request message to the selected new AMF (S604). It should be noted that 5G AN (or gNB) can transmit the identification information that is not included in the login request message but included in the RRC message together with the login request message to the selected AMF (new AMF141) (S604).

[0420] The new AMF 141 can perform the first condition determination upon receiving the login request message. The first condition determination is used to determine whether the network (or the new AMF 141) accepts the UE's request. If the first condition determination is true, the new AMF 141 executes the processes of S606 to S612. On the other hand, if the first condition determination is false, the new AMF 141 may not execute the processes of S606 to S608, but execute the process of S610.

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

[0422] It should be noted that, here, when the first condition is judged to be true, the control message sent and received in S610 may be a registration accept message, and when the first condition is judged to be false, the control message sent and received in S610 may be a registration reject message.

[0423] It should be noted that the first condition judgment can be performed based on the reception of the login request message and / or the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF included in the login request message.

[0424] For example, the first condition may be true when the network allows the UE's request, and false when the network does not allow the UE's request. In addition, the first condition may be true when the network of the UE's login destination and / or the device in the network supports the function requested by the UE, and false when the function requested by the UE is not supported. Furthermore, the first condition may be true when the identification information sent and received is allowed, and false when the identification information sent and received is not allowed.

[0425] In addition, it may be that when the S-NSSAI included in the request NSSAI received by the AMF from the UE is information for identifying the slice requiring the NSSAA process, and when the result of the NSSAA process in which the AMF stores the corresponding S-NSSAI for the UE is successful, the first conditional judgment may be true. Alternatively, it may be that when there is no S-NSSAI allowed for the UE and there is no reservation for allocating the allowed NSSAI to the UE in the future, the first conditional judgment may be false.

[0426] In addition, when the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information for identifying slices that need to be managed by the maximum number of UEs connected to the slice, and when the maximum number of UEs has not been reached, the first conditional judgment may be true. Alternatively, when there is no S-NSSAI allowed for the UE, the first conditional judgment may be true if it is expected that the UE will be allocated an allowed NSSAI in the future.

[0427] In addition, when the S-NSSAI included in the request NSSAI received by the AMF from the UE is the S-NSSAI that needs to be controlled according to the condition information, NSAC can also be controlled not to be performed on the S-NSSAI.

[0428] In the case where the AMF allocates the fourth rejected NSSAI to the UE without the S-NSSAI allowed for the UE, the first conditional judgment may be true or false.

[0429] When the AMF indicated by the AMF identification information included in the message received by the new AMF141 from the UE is the old AMF142, the new AMF141 performs the procedures of S606 and S608. When the AMF indicated by the AMF identification information included in the message received by the new AMF141 from the UE_A10 is the new AMF141, the procedures of S606 and S608 are not performed. In other words, when an AMF change occurs through this procedure, the procedures of S606 and S608 are performed. When no AMF change occurs, the procedures of S606 and S608 are skipped.

[0430] The UE context transmission process (S606, S608) is described. The new AMF 141 sends a UE context request message to the old AMF 142 (S606). Based on the received UE context request message, the old AMF 142 sends the UE context to the new AMF 141. The new AMF 141 generates a UE context based on the received UE context.

[0431] Here, the UE context sent from the new AMF 141 to the old AMF 142 may include UEID and allowed NSSAI. Moreover, the UE context may also include setting NSSAI and / or rejecting NSSAI, NSSAI and / or pending NSSAI and / or fourth rejected NSSAI. In addition, the allowed NSSAI and / or setting NSSAI and / or rejecting NSSAI and / or pending NSSAI and / or fourth rejected NSSAI included in the UE context and the S-NSSAI included in each NSSAI may be associated with information on whether the notification to the UE is completed.

[0432] In addition, the UE context may also include information about the S-NSSAI that requires the NSSAA process and / or information indicating that the authentication of the UE to complete the NSSAA process is successfully performed and / or information indicating that the authentication fails.

[0433] In addition, the UE context may also include information on the S-NSSAI for managing the maximum number of UEs that need to be connected to the slice and / or information indicating that the maximum number of UEs has been reached and / or information indicating whether the maximum number of UEs connected to the slice has been reached.

[0434] It should be noted that the information related to the characteristics of these S-NSSAIs can be managed as one information. Specifically, the network can store the information indicating whether NSSAA is required, whether NSSAA is successfully performed, whether the maximum number of UEs connected to the slice needs to be managed, and whether the maximum number of UEs connected to the slice has been reached in an associated manner for each S-NSSAI.

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

[0436] In case a request NSSAI is received from the UE, and in case the S-NSSAI included in the request NSSAI requires NSSAA, the new AMF 141 may include the pending NSSAI in the control message for transmission.

[0437] Moreover, in the case where there is an update of the setting information of the UE, the new AMF141 may include the setting NSSAI and / or the allowing NSSAI and / or the rejecting NSSAI and / or the pending NSSAI in the control message and send it to UE_A10. It should be noted that the message sent by the new AMF141 to the UE may be based on the information received from the UE. Specifically, the S-NSSAI included in the rejecting NSSAI sent by the new AMF141 to the UE may be the S-NSSAI included in the requesting NSSAI received from the UE.

[0438] The new AMF 141 may send a control message without allowing S-NSSAI (allowing NSSAI) for the UE, but may include a null value in the allowed NSSAI when there is a reservation to perform the NSSAA procedure after the completion of this procedure or in parallel with this procedure, or when the NSSAA procedure is being performed between the UE and the network, or when the pending NSSAI IE is included in the control message for sending.

[0439] The new AMF 141 may include the allowed NSSAI in the control message when there is no S-NSSAI allowed for the UE (allowed NSSAI) when sending the control message, and in addition, when the fourth rejected NSSAI is notified to the UE before this process, the empty value is included in the allowed NSSAI for sending.

[0440] The new AMF 141 may include the Allowed NSSAI in the control message using the Allowed NSSAI IE. It should be noted that the Allowed NSSAI IE may include one or more S-NSSAIs of the current PLMN or SNPN. Moreover, when roaming, the Allowed NSSAI IE may include one or more mapped S-NSSAIs.

[0441] It should be noted that the S-NSSAI of the PLMN or SNPN included in the Allowed NSSAI IE may also be referred to as the Allowed S-NSSAI of the current PLMN or SNPN. In addition, more than one Allowed S-NSSAI may also be referred to as the Allowed NSSAI of the current PLMN or SNPN.

[0442] Moreover, the mapped S-NSSAI included in the Allowed NSSAI IE may also be referred to as the mapped S-NSSAI of the allowed NSSAI of the PLMN or SNPN. In addition, the mapped S-NSSAI of the allowed NSSAI of one or more current PLMNs or SNPNs may also be referred to as one or more mapped S-NSSAIs of the allowed NSSAI of the current PLMN or SNPN (mapped S-NSSAI(s) for the Allowed NSSAI: mapped S-NSSAI for the allowed NSSAI).

[0443] The new AMF 141 may include the Reject NSSAI in the control message using the Reject NSSAI IE or Extended Reject NSSAI IE. It should be noted that the Reject NSSAI IE or Extended Reject NSSAI IE may include the S-NSSAI of one or more current PLMNs or SNPNs.

[0444] The new AMF 141 may include the value of the backoff timer in the control message when the Extended Reject NSSAI IE is used to include the Reject NSSAI in the control message. Alternatively, the new AMF 141 may include the value of the backoff timer in the Extended Reject NSSAI IE and include the Extended Reject NSSAI IE in the control message for transmission. Furthermore, when roaming, one or more mapped S-NSSAIs may be included in the Extended Reject NSSAI IE.

[0445] It should be noted that the S-NSSAI of the current PLMN or SNPN included in the extended reject NSSAI IE can also be referred to as the reject S-NSSAI of the current PLMN or SNPN. In addition, more than one reject S-NSSAI can be referred to as the reject NSSAI of the current PLMN or SNPN.

[0446] The new AMF 141 may include the pending NSSAI in the control message using the pending NSSAI IE. It should be noted that the pending NSSAI IE may include one or more S-NSSAIs of the current PLMN or SNPN. And / or, when roaming, the pending NSSAI IE may include one or more mapped S-NSSAIs.

[0447] The new AMF 141 may include at least one of the tenth to fourteenth identification information in a control message and send it to the UE. The new AMF 141 may determine whether to include at least one of the tenth to fourteenth identification information in a control message for transmission and information to be transmitted based on the reception of the first identification information.

[0448] Specifically, when the first identification information is received and / or the first identification information is information indicating that the UE has the function of storing conditional information associated with the S-NSSAI and performing control based on the storage, the new AMF141 may include at least one of the tenth to fourteenth identification information in the control message and send it.

[0449] UE_A10 receives a control message and / or one or more information included in the control message from the network.

[0450] UE_A10 can identify the received information based on the reception of the control message and / or one or more information included in the control message.

[0451] Specifically, when receiving information related to NSSAI, the UE can perform storage and / or update of information related to NSSAI and start and / or stop of a timer. The details of the storage and / or update method of information related to NSSAI are described in the NSSAI update and / or storage process in Chapter 3.3.

[0452] It should be noted that the NSSAI update and / or storage process in Chapter 3.3 can be executed during this process or after this process is completed. If the NSSAI update and / or storage process in Chapter 3.3 is executed after this process is completed, it can be executed based on the completion of this process.

[0453] For example, the UE that receives the tenth to fourteenth identification information may perform the NSSAI update and / or storage procedure of Chapter 3.3 as the UE that receives the first NSSAI.

[0454] When the UE receives the twelfth identification information and / or the thirteenth identification information including the timer value, the UE may start the execution of the timer using the received timer value. The timer value included in the thirteenth identification information may be a back-off timer value, in which case the timer executed by the UE may be a back-off timer.

[0455] The UE may execute the timer in association with the S-NSSAI and / or the mapped S-NSSAI indicated in the eleventh identification information. Furthermore, the timer may be associated with the same information as the information associated with the S-NSSAI and / or the mapped S-NSSAI indicated in the eleventh identification information.

[0456] The UE may identify and / or manage the condition indicated by the timer value during the execution of the timer. The execution of the timer may refer to the period from when the timer is started to when the timer expires or when the timer is stopped.

[0457] In a case where the UE receives the twelfth identification information and / or the thirteenth identification information including the information indicating the period, the UE can recognize that the period indicated by the information indicating the period is the condition indicated by the information.

[0458] It should be noted that AMF can select and determine the identification information to be included in the control message and / or the information to be notified based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF.

[0459] In addition, when the control message is a login acceptance message, the AMF can include an SM message (e.g., a PDU session establishment acceptance message) in the login acceptance message and send it, or send the SM message (e.g., a PDU session establishment acceptance message) together with the login acceptance message. However, the sending method can also be performed when the SM message (e.g., a PDU session establishment request message) is included in the login request message. In addition, the sending method can also be performed when the SM message (e.g., a PDU session establishment request message) is sent together with the login request message. The AMF can indicate that the process used for SM in the login process is accepted by performing such a sending method.

[0460] In addition, the AMF may indicate that the UE's request is accepted by sending a login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, or may indicate that the UE's request is rejected by sending a login rejection message.

[0461] The UE receives a control message via the 5G AN (gNB) (S608). In the case where the control message is a login acceptance message, the UE can identify that the UE's request according to the login request message is accepted and the contents of various identification information included in the login acceptance message by receiving the login acceptance message. Alternatively, in the case where the control message is a login rejection message, the UE can identify that the UE's request implemented by the login request message is rejected and the contents of various identification information included in the login rejection message by receiving the login rejection message. In addition, the UE can also identify that the UE's request is rejected if it has not received a control message after a specified period of time after sending the login request message.

[0462] The UE can further send a login completion message to the AMF via the 5G AN (gNB) as a response message to the login acceptance message when the control message is a login acceptance message (S610). It should be noted that the UE can include an SM message such as a PDU session establishment completion message in the login completion message when receiving an SM message such as a PDU session establishment acceptance message, or it can include an SM message to indicate that the SM process is complete. Here, the login completion message is a NAS message sent and received on the N1 interface, but is included in the RRC message for sending and receiving between the UE and the 5G AN (gNB).

[0463] AMF receives the login completion message (S612) via 5G AN (gNB). In addition, each device completes this process based on the sending and receiving of the login acceptance message and / or the login completion message.

[0464] Alternatively, each device may complete the login process based on the sending and receiving of a login rejection message.

[0465] It should be noted that each device can transition or maintain the state in which the UE has logged in to the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of the login acceptance message and / or the login completion message, and can also transition or maintain the state in which the UE has not logged in to the network for the current PLMN or SNPN on the access receiving the login rejection message (RM_DEREGISTERED state or 5GMM-DEREGISTEREDstate) based on the sending and receiving of the login rejection message. In addition, the transition of each device to each state can also be based on the sending and receiving of the login completion message or the completion of the login process.

[0466] Moreover, each device may implement processing based on information sent and received during the login process based on the completion of the login process. For example, the reason why the UE's request was rejected may be identified when information indicating that a part of the UE's request was rejected is sent and received. Furthermore, each device may implement this process again based on the reason why the UE's request was rejected, and may also implement the login process for the core network_A and other cells.

[0467] Furthermore, the UE may store the identification information received together with the registration accept message and / or the registration reject message based on the completion of the registration procedure, and may also identify the determination of the network.

[0468] Moreover, the UE may delete one or more stored NSSAIs based on the completion of the login process. Specifically, based on the completion of this process, when the UE_A10 changes to a non-logged-in state on two accesses (3GPP access and non-3GPP access) for the current PLMN or SNPN, the UE_A10 may delete the stored first rejected NSSAI and / or the third rejected NSSAI and / or the fourth rejected NSSAI.

[0469] Moreover, based on the completion of this process, when UE_A10 changes to a non-logged-in state on a certain access (3GPP access and non-3GPP access) for the current PLMN or SNPN, or when UE_A10 successfully completes the login process in a new login area, or when UE_A10 performs a login process in a new login area, and the result is that the state changes to a non-logged-in state or a logged-in state on a certain access, UE_A10 can delete the second rejected NSSAI associated with the current PLMN or SNPN, the current login area and / or the access type.

[0470] Furthermore, each device may also restart the login process based on the expiration or stop of the back-off timer.

[0471] Furthermore, each device may restart the login process based on an update of the stored NSSAI.

[0472] Moreover, each device can start the SM process by sending and receiving SM messages based on the transition to or maintenance of the state where the UE has logged in to the network (RM_REGISTERED state, or 5GMM-REGISTERED state). [3.2.UE setting update process]

[0473] Next, use Figure 7 The UE configuration update procedure (Generic UE configuration update procedure) is described. Hereinafter, the UE configuration update procedure is also referred to as this procedure. This procedure is a process for the core network to update the setting information of the UE. This procedure can be a process for performing network-led mobility management on a UE logged in to the network.

[0474] Moreover, the devices in the core network such as AMF can start this process based on the update of network settings and / or the update of operator policies. It should be noted that the trigger of this process can be the detection of UE mobility, the detection of state changes of UE and / or access network and / or core network, or the state change of network slice. Moreover, the trigger of this process can be the reception of a request from DN and / or DN's application server, the change of network settings, or the change of operator policies. Moreover, the trigger of this process can also be the expiration of an executing timer. It should be noted that the trigger for the device in the core network to start this process is not limited to these. In other words, this process can be executed at any timing after the aforementioned registration process and / or PDU session establishment process is completed. Moreover, if the state of 5GMM context is established for each device and / or each device is in 5GMM connection mode, this process can be executed at any timing.

[0475] In addition, each device may send and receive messages including identification information for changing the setting information of the UE and / or identification information for stopping or changing the function being executed by the UE during this process. Moreover, based on the completion of this process, each device may update the setting information to the setting indicated by the network or start the behavior indicated by the network.

[0476] The UE can update the UE's setting information based on the control information sent and received through this process. Moreover, as the UE's setting information is updated, the UE can stop the function being executed or start a new function. In other words, the device in the core network can use this control information by leading this process and then sending the control message and control information of this process to the UE, so that the UE can update the identifiable UE setting information. Moreover, the device in the core network can stop the function being executed by the UE or start a new function by updating the UE's setting information.

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

[0478] Moreover, in the case where there is an update of the UE's setting information, and the setting update command message includes a pending NSSAI, and the UE supports the function of storing more than one mapped S-NSSAI of the pending NSSAI, the new AMF141 can include the tenth identification information in the setting update command message and send it.

[0479] UE_A10 receives a configuration update command message and / or the tenth identification information from the network. In more detail, the UE receives a configuration update command message and / or the tenth identification information from the new AMF141.

[0480] UE_A10 can identify the received information based on the reception of the tenth identification information.

[0481] AMF140 may include one or more of the NSSAIs related to UE_A10 (hereinafter referred to as setting NSSAI, allowing NSSAI, rejecting NSSAI, and pending NSSAI) in the setting update command message for sending. It should be noted that AMF can indicate the setting information of a new UE by sending one or more of the NSSAIs, and can also request an update of the UE's setting information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, or can be sent and received as different identification information.

[0482] Furthermore, AMF 140 may include a TAI list representing a new login area in a setting update command message and send it.

[0483] The new AMF 141 may include at least one of the tenth to fourteenth identification information in a configuration update command message and send it to the UE. The new AMF 141 may determine whether to include at least one of the tenth to fourteenth identification information in a configuration update command message for transmission and information to be transmitted based on the reception of the first identification information.

[0484] Specifically, in the case where the AMF receives the first identification information during the login process and / or the first identification information is information indicating that the UE has the function of storing conditional information associated with the S-NSSAI and performing control based on the storage, the new AMF 141 may include at least one of the tenth to fourteenth identification information in the setting update command message and send it.

[0485] UE_A10 receives one or more information included in a control message and / or a setting update command message from the network.

[0486] Furthermore, when multiple identification information is sent and received, two or more of the identification information may constitute one or more identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function may be sent and received as the same identification information or as different identification information.

[0487] It should be noted that AMF140 selects and determines whether to include each NSSAI, TAI list in the setting update command message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF140.

[0488] In addition, AMF140 can send a configuration update command message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user registration information and / or context maintained by AMF140, thereby indicating a request for an update of the setting information of UE_A10.

[0489] UE_A10 receives a setting update command message (S800) from AMF140 via 5G AN120 (or gNB). UE_A10 can update the setting information of the UE based on the setting update command message and / or the identification information included in the setting update command message.

[0490] In addition, it may also be that, when UE_A10 receives a TAI list representing a login area, the received TAI list representing the login area is set to be valid, and when UE_A10 already stores a valid TAI list representing the login area, the old TAI list representing the login area is deleted or set to be invalid. In the following, the valid TAI list representing the login area may also be expressed as the login area. It should be noted that, when UE_A10 does not store a valid TAI list representing the login area, and in the present process, the TAI list representing the login area is not received from the core network, the valid TAI list representing the login area may be in a state of not being stored.

[0491] In addition, UE_A10 can appropriately store each received NSSAI. Moreover, based on the received NSSAI, the stored information related to NSSAI of UE_A10 can be updated. Moreover, the information related to NSSAI stored by UE_A10 can be deleted and / or updated based on the state of UE_A10. The specific actions of the method for updating the storage related to NSSAI performed by UE_A10 and the conditions for the update are described in the NSSAI update and / or storage process of Chapter 3.3.

[0492] It should be noted that the NSSAI update and / or storage process in Chapter 3.3 can be executed during this process or after this process is completed, or can be executed based on the completion of this process.

[0493] In addition, in addition to the NSSAI update and / or storage process, the behavior of each device based on the sending and receiving of setting update command messages and / or identification information included in the setting update command messages may also be the behavior of each device based on the sending and receiving of control messages and / or identification information included in the control messages during the login process of this embodiment.

[0494] Based on the identification information included in the configuration update command message, the UE can send a configuration update complete message to AMF140 via the 5G AN (gNB) as a response message to the configuration update command message (S802).

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

[0496] Furthermore, each device may implement processing based on the information received and sent in this process based on the completion of this process. For example, in the case where update information for setting information is received and sent, each device may update the setting information. Furthermore, in the case where information indicating that a registration process needs to be performed is received and sent, UE_A10 may start the registration process based on the completion of this process.

[0497] Moreover, UE_A10 can store the identification information received together with the setting information command message based on the completion of this process, and can also identify the determination of the network. In addition, based on the completion of this process, the UE can execute each process based on the stored information.

[0498] In the above process, the device in the core network can instruct the UE to update the setting information that the UE has applied by sending and receiving setting update command messages, and can instruct the UE to stop or change the functions being executed. [3.3.NSSAI Update and / or Storage Process]

[0499] The following describes the update and / or storage process for each NSSAI stored in UE_A10. It should be noted that the NSSAI update process performed by the UE can be performed in the other processes described in Chapter 3, or it can be performed based on the completion of each process. In addition, it can also be performed based on other processes or other process completions. Other processes can be, for example, a deregistration procedure or a UE setting update procedure.

[0500] When receiving the setting NSSAI, UE_A10 may store the received setting NSSAI as "the setting NSSAI associated with the current PLMN or SNPN". That is, UE_A10 may replace "the setting NSSAI associated with the current PLMN or SNPN stored by UE_A10" with "the received setting NSSAI".

[0501] Moreover, when receiving the setting NSSAI, UE_A10 can delete the mapping S-NSSAI of the S-NSSAI included in the "setting NSSAI stored by UE_A10 and associated with the current PLMN or SNPN". Moreover, when one or more mapping S-NSSAI are included in the "received setting NSSAI", UE_A10 can store these one or more mapping S-NSSAI.

[0502] Moreover, upon receiving the set NSSAI, UE_A10 can delete the "rejected NSSAI stored by UE_A10 that is associated with the current PLMN or SNPN".

[0503] Alternatively, upon receiving the set NSSAI, UE_A10 may delete at least one of the "first rejection NSSAI stored in UE_A10 and associated with the current PLMN or SNPN", "the second rejection NSSAI stored in UE_A10 and associated with the current PLMN or SNPN", and "the third rejection NSSAI stored in UE_A10 and associated with the current PLMN".

[0504] Moreover, upon receiving the set NSSAI, UE_A10 may delete "the fourth rejected NSSAI stored by UE_A10" and / or "the fourth rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" and / or one or more "the fourth rejected NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN or the ESNPN of the current SNPN".

[0505] Moreover, upon receiving the set NSSAI, UE_A10 may delete "pending NSSAI stored by UE_A10" and / or "pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" and / or one or more "pending NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN or the ESNPN of the current SNPN" and / or "one or more mappings S-NSSAI for the pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" and / or one or more "one or more mappings S-NSSAI for the second pending NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN".

[0506] Moreover, upon receiving the set NSSAI, UE_A10 may delete "the first NSSAI stored by UE_A10" and / or "the first NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" and / or one or more "the first NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN or the ESNPN of the current SNPN" and / or "one or more mappings S-NSSAIs for the first NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" and / or one or more "one or more mappings S-NSSAIs for the first pending NSSAI stored by UE_A10 and associated with the EPLMN of the current PLMN".

[0507] Moreover, when receiving the allowed NSSAI, UE_A10 may store the received allowed NSSAI as "the allowed NSSAI associated with the current PLMN or SNPN and the current access type". That is, UE_A10 may replace the "allowed NSSAI associated with the current PLMN or SNPN and the current access type" stored by UE_A10 with the "received allowed NSSAI".

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

[0509] It should be noted that, when storing allowed NSSAI, UE_A10 may store the allowed NSSAI in association with the login area, or may store the S-NSSAI included in the allowed NSSAI in association with the login area.

[0510] UE_A10 may delete the mapped S-NSSAI of the S-NSSAI included in the "Allowed NSSAI deleted based on reception" or the "Old Allowed NSSAI updated based on reception" when receiving the Allowed NSSAI. Moreover, when UE_A10 includes the mapped S-NSSAI in the "Received Allowed NSSAI IE", UE_A10 may store the one or more mapped S-NSSAI.

[0511] Upon receiving the allowed NSSAI, UE_A10 may delete the S-NSSAI of "the rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN".

[0512] When receiving the allowed NSSAI, UE_A10 may delete the S-NSSAI included in the received allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10 under the following conditions. The condition for deleting S-NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored in UE_A10 may be that UE_A10 is not roaming, or that the mapping S-NSSAI of the S-NSSAI is not stored in UE_A10 as a set of mapping S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI, or that at least one UE_A10 stores the mapping S-NSSAI of the S-NSSAI in the set of mapping S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI stored in UE_A10, and all these mapping S-NSSAI are included in the allowed NSSAI received by the UE, or that the mapping S-NSSAI of the S-NSSAI is not included in the allowed NSSAI received by UE_A10, or that the S-NSSAI is not associated with multiple mapping S-NSSAIs.

[0513] When receiving the allowed NSSAI, UE_A10 may not delete the S-NSSAI included in the received allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10. The condition for not deleting the S-NSSAI from the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10 may be that UE_A10 is roaming and / or UE_A10 stores the mapped S-NSSAI of the S-NSSAI in the list (set) of mapped S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI and / or establishes an association with multiple mapped S-NSSAIs and / or all of these mapped S-NSSAIs are not included in the new allowed NSSAI and / or pending NSSAI.

[0514] It should be noted that the conditions for deleting the S-NSSAI included in the received allowed NSSAI from the fourth rejected NSSAI and / or pending NSSAI stored by UE_A10 may be the same as the conditions for deleting the S-NSSAI included in the received allowed NSSAI from the first rejected NSSAI and / or second rejected NSSAI stored by UE_A10.

[0515] When UE_A10 is roaming, if the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI is stored, in addition to the case where the allowed NSSAI IE including the new list of mapping S-NSSAI of allowed NSSAI is received, one or more mapping S-NSSAI not included in the new list of mapping S-NSSAI of allowed NSSAI are included in the list of mapping S-NSSAI of the first rejected NSSAI and / or the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10, UE_A10 deletes the S-NSSAI included in the new allowed NSSAI from the stored first rejected NSSAI and / or the second rejected NSSAI.

[0516] In other words, when UE_A10 is roaming, if it stores the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI, in addition to receiving the allowed NSSAI IE including the new list of mapping S-NSSAI of allowed NSSAI, there are one or more mapping S-NSSAIs that are not included in the new list of mapping S-NSSAI of allowed NSSAI, but included in the list of mapping S-NSSAI of the first rejected NSSAI and / or the list of mapping S-NSSAI of the second rejected NSSAI stored by UE_A10, UE_A10 deletes the S-NSSAI included in the new allowed NSSAI from the stored first rejected NSSAI and / or the second rejected NSSAI.

[0517] In other words, when UE_A10 is roaming and stores the mapping S-NSSAI of the first rejected NSSAI and / or the mapping S-NSSAI of the second rejected NSSAI, upon receiving the allowed NSSAI IE including a new list of mapping S-NSSAI of allowed NSSAI, the S-NSSAI deleted from the mapping S-NSSAI of the first rejected NSSAI and / or the second rejected NSSAI stored by UE_A10 is included in the received allowed NSSAI, and the S-NSSAI included in the list of mapping S-NSSAI of the allowed NSSAI mapped to the S-NSSAI includes all of the S-NSSAI included in the list of mapping S-NSSAI of the first rejected NSSAI and / or the list of mapping S-NSSAI of the second rejected NSSAI mapped to the S-NSSAI.

[0518] When UE_A10 is not roaming or UE_A10 is roaming, and the mapped S-NSSAI of the first rejected NSSAI and the mapped S-NSSAI of the second rejected NSSAI are not stored, when UE_A10 receives an allowed NSSAI IE including a new allowed NSSAI, UE_A10 deletes the S-NSSAI included in the new allowed NSSAI from the stored first rejected NSSAI and / or second rejected NSSAI.

[0519] UE_A10 may also act in a manner that does not delete the S-NSSAI of the current PLMN or SNPN included in the new allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI when receiving the allowed NSSAI during roaming.

[0520] UE_A10 may also take action, when receiving an allowed NSSAI during roaming, by deleting the S-NSSAI of the current PLMN or SNPN included in the new allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI.

[0521] When UE_A10 roams, when the first information consisting of S-NSSAI and mapped S-NSSAI is included in each NSSAI for storage, UE_A10 can delete the received combination of S-NSSAI and mapped S-NSSAI included in the allowed NSSAI from the first rejected NSSAI and / or the second rejected NSSAI and the set of mapped S-NSSAI of the first rejected NSSAI and / or the set of mapped S-NSSAI of the second rejected NSSAI.

[0522] Specifically, upon receiving the allowed NSSAI, UE_A10 may delete the S-NSSAI included in the received allowed NSSAI and / or the mapping S-NSSAI of the received allowed NSSAI from at least one of the “first rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN”, “the second rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN”, “the second rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN and the current login area”, and “the third rejected NSSAI stored by UE_A10 and associated with the current PLMN or SNPN”. It may also delete the S-NSSAI included in the received allowed NSSAI and / or the mapping S-NSSAI of the received allowed NSSAI from all NSSAIs.

[0523] Moreover, upon receiving the Allowed NSSAI, UE_A10 may delete the S-NSSAI included in the received Allowed NSSAI from the "first pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN (when not roaming)" or the "second pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN". Moreover, upon receiving the Allowed NSSAI, UE_A10 may delete the mapped S-NSSAI included in the received Allowed NSSAI IE from the "first pending NSSAI stored by UE_A10 (when roaming)". Moreover, upon receiving the Allowed NSSAI, UE_A10 may delete the S-NSSAI included in the received Allowed NSSAI IE from the "pending NSSAI stored by UE_A10 and associated with the EPLMN or ESNPN".

[0524] Moreover, in the case where a back-off timer for restricting the use of a certain S-NSSAI is being executed, the S-NSSAI is included in the new allowed NSSAI, or the S-NSSAI is a mapped S-NSSAI of the allowed NSSAI, the UE can stop the back-off timer.

[0525] Here, in the roaming scenario, when the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN or HSNPN, the UE_A10 can delete the mapping S-NSSAI of the S-NSSAI included in the received new allowed NSSAI from the "pending NSSAI stored by UE_A10" upon receiving the allowed NSSAI. At this time, in the roaming scenario, the allowed NSSAI can be associated with the PLMN ID or SNPN ID representing the current PLMN or the current SNPN, that is, the RPLMN or RSNPN.

[0526] Moreover, when receiving the allowed NSSAI, UE_A10 can delete the S-NSSAI included in the received allowed NSSAI from the "fourth rejected NSSAI stored by UE_A10 that is associated with the current PLMN or SNPN".

[0527] Moreover, upon receiving the Allowed NSSAI, UE_A10 may delete the S-NSSAI included in the received Allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with the current PLMN or SNPN (when not roaming)" or the "first NSSAI stored by UE_A10 and associated with the current PLMN or SNPN". Moreover, upon receiving the Allowed NSSAI, UE_A10 may delete the mapped S-NSSAI included in the received Allowed NSSAI IE from the "first NSSAI stored by UE_A10 (when roaming)". Moreover, upon receiving the Allowed NSSAI, UE_A10 may delete the S-NSSAI included in the received Allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with the EPLMN or ESNPN".

[0528] Moreover, in the case where a timer for limiting the use of the S-NSSAI included in the first NSSAI is being executed, the S-NSSAI is included in the new allowed NSSAI, or the S-NSSAI is a mapped S-NSSAI of the allowed NSSAI, the UE can stop the timer.

[0529] Here, in the roaming scenario, when the S-NSSAI included in the first NSSAI is the S-NSSAI of the HPLMN or HSNPN, UE_A10 can delete the mapping S-NSSAI of the S-NSSAI included in the received new allowed NSSAI from the "first NSSAI stored by UE_A10" when receiving the allowed NSSAI. At this time, in the roaming scenario, the allowed NSSAI can be associated with the PLMN ID or SNPN ID representing the current PLMN or the current SNPN, that is, the RPLMN or RSNPN.

[0530] Moreover, when receiving a rejection NSSAI, UE_A10 may store the S-NSSAI included in the received rejection NSSAI as an appropriate rejection NSSAI based on the rejection reason value associated with the S-NSSAI. That is, UE_A10 may append "the S-NSSAI included in the received rejection NSSAI" to the rejection NSSAI stored by UE_A10.

[0531] Specifically, when UE_A10 receives a rejection reason value "S-NSSAI not available in the current PLMN or SNPN" and a rejection S-NSSAI associated with the rejection reason value, UE_A10 can append the S-NSSAI to the first rejection NSSAI associated with the current PLMN or SNPN.

[0532] Moreover, when UE_A10 receives a rejection reason value "S-NSSAI not available in the current registration area" and a rejection S-NSSAI associated with the rejection reason value, UE_A10 can append the "received rejection S-NSSAI" to the "second rejection NSSAI associated with the current PLMN or SNPN and the current login area".

[0533] Specifically, when UE_A10 receives a rejection reason value "S-NSSAI unavailable due to failure or cancellation of NSSAA" and a rejection S-NSSAI associated with the rejection reason value, UE_A10 may append the "received rejection S-NSSAI" to the "third rejection NSSAI". At this time, the "third rejection NSSAI" may be associated with the current PLMN or SNPN.

[0534] It should be noted that, when UE_A10 receives a TAI list together with a rejection of NSSAI, the current login area is represented by the received TAI list. On the other hand, when UE_A10 does not receive a TAI list together with a rejection of NSSAI, the current login area is represented by the TAI list that UE_A10 received and stored last time.

[0535] Moreover, when UE_A10 receives a rejection reason value "S-NSSAI unavailable due to failure or cancellation of NSSAA" and a rejection NSSAI including a rejection S-NSSAI associated with the rejection reason value, UE_A10 may append and / or store the S-NSSAI in the third rejection NSSAI. It should be noted that, when the UE stores the third rejection NSSAI associated with the current PLMN or SNPN, the received S-NSSAI may be appended and / or stored in the third rejection NSSAI associated with the current PLMN or SNPN.

[0536] Moreover, when receiving the rejected NSSAI, UE_A10 can delete the S-NSSAI included in the received rejected NSSAI from the "allowed NSSAI stored by UE_A10 that is associated with the current PLMN or SNPN".

[0537] Here, in the case where UE_A10 receives a rejecting NSSAI including an S-NSSAI of a HPLMN or HSNPN, and in the case where a mapped S-NSSAI of the S-NSSAI included in the "Allowed NSSAI stored by UE_A10 and associated with the current PLMN or SNPN" is included in the rejecting NSSAI received by UE_A10, UE_A10 can delete the S-NSSAI from the "Allowed NSSAI stored by UE_A10 and associated with the current PLMN or SNPN".

[0538] Moreover, upon receiving a rejected NSSAI, UE_A10 may delete the S-NSSAI included in the received rejected NSSAI from the “first pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN (non-roaming)” and / or the “second pending NSSAI stored by UE_A10 and associated with the current PLMN or SNPN”. UE_A10 may delete the mapped S-NSSAI or S-NSSAI included in the received allowed NSSAI IE from the “first pending NSSAI stored by UE_A10” upon receiving a rejected NSSAI. Moreover, UE_A10 may delete the S-NSSAI included in the received allowed NSSAI from the “pending NSSAI stored by UE_A10 and associated with the EPLMN or ESNPN” upon receiving a rejected NSSAI.

[0539] Moreover, when receiving the allowed NSSAI, UE_A10 can delete the S-NSSAI included in the received allowed NSSAI from the "fourth rejected NSSAI stored by UE_A10 that is associated with the current PLMN or SNPN".

[0540] UE_A10 may store the S-NSSAI based on the rejection reason value associated with each S-NSSAI when receiving one or more S-NSSAI included in the rejection NSSAI. Specifically, UE_A10 may store the S-NSSAI included in the received rejection NSSAI in a set of each rejection NSSAI and / or a mapping S-NSSAI of each rejection NSSAI stored by UE_A10.

[0541] More specifically, it may be that when UE_A10 receives a Reject NSSAI IE or an Extended Reject NSSAI IE, and when the Reject S-NSSAI#1 included in the Reject NSSAI IE or the Extended Reject NSSAI IE includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI not available in the current PLMN or SNPN", UE_A10 includes S-NSSAI#1 in the first Reject NSSAI stored by the UE and stores it.

[0542] Similarly, when UE_A10 receives a Reject NSSAI IE or an Extended Reject NSSAI IE, and when the Reject S-NSSAI#1 included in the Reject NSSAI IE or the Extended Reject NSSAI IE includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI not available in the current registration area", UE_A10 includes S-NSSAI#1 in the second Reject NSSAI stored by the UE and stores it.

[0543] Similarly, when UE_A10 receives a Reject NSSAI IE or an Extended Reject NSSAI IE, and when the Reject S-NSSAI#1 included in the Reject NSSAI IE or the Extended Reject NSSAI IE includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI unavailable due to failure or cancellation of NSSAI", UE_A10 includes S-NSSAI#1 in the third Reject NSSAI stored by the UE and stores it.

[0544] Alternatively, when UE_A10 receives an extended rejection NSSAI IE, and the rejection S-NSSAI#1 included in the extended rejection NSSAI IE includes S-NSSAI#1, mapped S-NSSAI#1, and a rejection reason value indicating "S-NSSAI not available in the current PLMN or SNPN", UE_A10 includes S-NSSAI#1 in the first rejection NSSAI stored by the UE and stores the mapped S-NSSAI1#1 in the set of mapped S-NSSAIs of the first rejection NSSAI. Alternatively, under the same conditions, UE_A10 may also include the combination of S-NSSAI#1 and mapped S-NSSAI1#1 in the first rejection NSSAI stored by the UE and store it.

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

[0546] Similarly, when UE_A10 receives the Reject NSSAI IE or Extended Reject NSSAI IE, and when the Reject S-NSSAI#1 included in the Reject NSSAI IE or Extended Reject NSSAI IE includes S-NSSAI#1 and a rejection reason value indicating "S-NSSAI unavailable due to failure or cancellation of NSSAI", UE_A10 includes S-NSSAI#1 in the third Reject NSSAI stored by the UE for storage. Alternatively, under the same conditions, UE_A10 may also include the combination of S-NSSAI#1 and mapped S-NSSAI1#1 in the first Reject NSSAI stored by the UE for storage.

[0547] Upon receiving a rejection NSSAI, UE_A10 may, under the following conditions, delete the first rejection NSSAI included in the received rejection NSSAI and / or the S-NSSAI included in the second rejection NSSAI from the allowed NSSAI stored by UE_A10. The condition for deleting S-NSSAI from the allowed NSSAI stored in UE_A10 may be that UE_A10 is not roaming, or that the mapping S-NSSAI of the S-NSSAI is not included in the set of mapping S-NSSAI of allowed NSSAI for storage through UE_A10, or that at least one UE_A10 stores the mapping S-NSSAI of the S-NSSAI in the set of mapping S-NSSAI of allowed NSSAI stored in UE_A10, and all these mapping S-NSSAI are included in the first rejected NSSAI and / or the second rejected NSSAI received by the UE, or that the mapping S-NSSAI of the S-NSSAI is not included in the first rejected NSSAI and / or the second rejected NSSAI received by UE_A10, or that the S-NSSAI is not associated with multiple mapping S-NSSAIs.

[0548] It should be noted that the situation where the mapped S-NSSAI of the S-NSSAI is not included in the first reject NSSAI and / or the second reject NSSAI received by UE_A10 may be the situation where UE_A10 receives the first reject NSSAI and / or the second reject NSSAI included in the reject NSSAI IE, or the situation where UE_A10 receives the first reject NSSAI that does not include the mapped S-NSSAI but includes the reject S-NSSAI IE and / or the extended reject NSSAI IE including the second reject NSSAI.

[0549] When receiving the rejection NSSAI, UE_A10 may delete the S-NSSAI included in the first rejection NSSAI and / or the second rejection NSSAI included in the received rejection NSSAI from the allowed NSSAI stored by UE_A10. The condition for not deleting the S-NSSAI from the allowed NSSAI stored by UE_A10 may be that UE_A10 is roaming and / or UE_A10 stores the mapping S-NSSAI of the S-NSSAI in the list (set) of mapping S-NSSAI of allowed NSSAI and / or establishes an association with multiple mapping S-NSSAIs and / or all of these mapping S-NSSAIs are not included in the first rejection NSSAI and / or the second rejection NSSAI included in the extended rejection NSSAI IE received by UE_A10.

[0550] It should be noted that the condition for deleting the S-NSSAI included in the first rejection NSSAI and / or the second rejection NSSAI included in the received rejection NSSAI from the fourth rejection NSSAI stored by UE_A10 may be the same as the condition for deleting the S-NSSAI included in the first rejection NSSAI and / or the second rejection NSSAI included in the received rejection NSSAI from the allowed NSSAI stored by UE_A10.

[0551] When UE_A10 receives the first rejected NSSAI or the second rejected NSSAI during roaming, it may act in a manner not to delete the S-NSSAI from the allowed NSSAI when one or more mapping S-NSSAI of the S-NSSAI included in the allowed NSSAI are not included in the first rejected NSSAI and / or the second rejected NSSAI, while other mapping S-NSSAI or part of the mapping S-NSSAI are included in the first rejected NSSAI and / or the second rejected NSSAI associated with the S-NSSAI.

[0552] UE_A10 may also take action in a manner that does not delete the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the allowed NSSAI when receiving the first rejected NSSAI and / or the second rejected NSSAI during roaming.

[0553] UE_A10 may also delete the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the allowed NSSAI when receiving the first rejected NSSAI and / or the second rejected NSSAI during roaming.

[0554] When UE_A10 includes the first information consisting of S-NSSAI and mapped S-NSSAI in each NSSAI for storage when roaming, UE_A10 can delete the combination of S-NSSAI and mapped S-NSSAI included in the received extended reject NSSAI IE from the set of allowed NSSAI and mapped S-NSSAI of allowed NSSAI.

[0555] Upon receiving a rejected NSSAI, UE_A10 may delete the S-NSSAI included in the received rejected NSSAI from the allowed NSSAI of the current PLMN or SNPN and / or the set of mapped S-NSSAIs of the allowed NSSAI of the current PLMN or SNPN.

[0556] Specifically, when UE_A10 receives the third rejected NSSAI, and when roaming, UE_A10 may delete the S-NSSAI included in the third rejected NSSAI from the stored set of mapped S-NSSAIs of allowed NSSAIs.

[0557] When UE_A10 receives the third rejected NSSAI and is not roaming, UE_A10 may delete the S-NSSAI included in the stored allowed NSSAI and the third rejected NSSAI.

[0558] In the case where UE_A10 receives the first reject NSSAI and / or the second reject NSSAI included in the extended reject NSSAI IE, and when roaming, UE_A10 can delete the mapped S-NSSAI included in the first reject NSSAI and / or the second reject NSSAI included in the received extended reject NSSAI IE from the stored set of mapped S-NSSAIs of allowed NSSAI.

[0559] Upon receiving a rejection NSSAI, UE_A10 may, under the following conditions, delete the first rejection NSSAI included in the received rejection NSSAI and / or the S-NSSAI included in the second rejection NSSAI from the pending NSSAI stored by UE_A10. The condition for deleting S-NSSAI from the pending NSSAI stored in UE_A10 may be that UE_A10 is not roaming, or that the mapping S-NSSAI of the S-NSSAI is not included in the set of mapping S-NSSAI of allowed NSSAI for storage by UE_A10, or that at least one UE_A10 stores the mapping S-NSSAI of the S-NSSAI in the mapping S-NSSAI of pending NSSAI stored in UE_A10, and all these mapping S-NSSAI are included in the first rejected NSSAI and / or the second rejected NSSAI received by the UE, or that the mapping S-NSSAI of the S-NSSAI is not included in the first and / or second rejected NSSAI received by UE_A10, or that the S-NSSAI is not associated with multiple mapping S-NSSAIs.

[0560] It should be noted that the situation where the mapped S-NSSAI of the S-NSSAI is not included in the first reject NSSAI and / or the second reject NSSAI received by UE_A10 may be the situation where UE_A10 receives the first reject NSSAI and / or the second reject NSSAI included in the reject NSSAI IE, or the situation where UE_A10 receives the first reject NSSAI that does not include the mapped S-NSSAI but includes the reject S-NSSAI IE and / or the extended reject NSSAI IE including the second reject NSSAI.

[0561] When receiving the rejection NSSAI, UE_A10 may not delete the S-NSSAI included in the first rejection NSSAI and / or the second rejection NSSAI included in the received rejection NSSAI from the pending NSSAI stored by UE_A10. The condition for not deleting the S-NSSAI from the pending NSSAI stored by UE_A10 may be that UE_A10 is roaming and / or UE_A10 stores the mapping S-NSSAI of the S-NSSAI in the list (set) of mapping S-NSSAI of pending NSSAI and / or that an association is established with multiple mapping S-NSSAIs and / or that all these mapping S-NSSAIs are not included in the first rejection NSSAI and / or the second rejection NSSAI included in the extended rejection NSSAI IE received by UE_A10.

[0562] In other words, when UE_A10 receives the first rejected NSSAI or the second rejected NSSAI during roaming, one or more mapped S-NSSAIs of the S-NSSAI included in the pending NSSAI are not included in the first rejected NSSAI and / or the second rejected NSSAI, while other mapped S-NSSAIs or part of the mapped S-NSSAIs are included in the first rejected NSSAI and / or the second rejected NSSAI associated with the S-NSSAI, and the UE_A10 takes action in a manner not to delete the S-NSSAI from the pending NSSAI.

[0563] UE_A10 may also take action in a manner that does not delete the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the pending NSSAI when receiving the first rejected NSSAI and / or the second rejected NSSAI during roaming.

[0564] UE_A10 may also delete the S-NSSAI of the current PLMN or SNPN included in the first rejected NSSAI and / or the second rejected NSSAI from the pending NSSAI when receiving the first rejected NSSAI and / or the second rejected NSSAI during roaming.

[0565] In the case where UE_A10 includes the first information consisting of S-NSSAI and mapped S-NSSAI in each NSSAI for storage when roaming, UE_A10 can delete the combination of S-NSSAI and mapped S-NSSAI included in the received extended reject NSSAI IE from the set of pending NSSAI and mapped S-NSSAI of allowed NSSAI.

[0566] Upon receiving a rejected NSSAI, UE_A10 may delete the S-NSSAI included in the received rejected NSSAI from the allowed NSSAI of the current PLMN or SNPN and / or the set of mapped S-NSSAIs of the allowed NSSAI of the current PLMN or SNPN.

[0567] Specifically, when UE_A10 receives the third rejected NSSAI, and when roaming, UE_A10 may delete the S-NSSAI included in the third rejected NSSAI from the stored set of mapped S-NSSAIs of allowed NSSAIs.

[0568] In the case where UE_A10 receives the third rejected NSSAI and in the case of not roaming, UE_A10 may delete the stored pending NSSAI and the S-NSSAI included in the third rejected NSSAI.

[0569] In the event that UE_A10 receives the first reject NSSAI and / or the second reject NSSAI included in the extended reject NSSAI IE, and when roaming, UE_A10 may delete the mapped S-NSSAI included in the first reject NSSAI and / or the second reject NSSAI included in the received extended reject NSSAI IE from the set of mapped S-NSSAIs of stored pending NSSAIs.

[0570] Moreover, when receiving the rejection NSSAI, UE_A10 may delete the S-NSSAI included in the received rejection NSSAI from the "fourth rejection NSSAI stored by UE_A10 and associated with the current PLMN or SNPN". Moreover, when receiving the rejection NSSAI, UE_A10 may delete the S-NSSAI included in the received permission NSSAI from the "fourth rejection NSSAI stored by UE_A10 and associated with the EPLMN or ESNPN".

[0571] Moreover, in the case where a back-off timer for limiting the use of a certain S-NSSAI is being executed, and the S-NSSAI or a mapped S-NSSAI of the S-NSSAI is included in the first to third rejected NSSAIs, the UE can stop the back-off timer.

[0572] Moreover, upon receiving the pending NSSAI, UE_A10 may replace the pending NSSAI stored by UE_A10 with the new pending NSSAI. Specifically, upon receiving the pending NSSAI IE included in the login acceptance message in the login process for the current PLMN or SNPN, UE_A10 may replace the pending NSSAI associated with the current PLMN or SNPN stored by UE_A10 with the new pending NSSAI.

[0573] More specifically, in the case where UE_A10 manages the pending NSSAI as the second pending NSSAI, UE_A10 may act as described below. UE_A10 may replace the stored pending NSSAI of the current PLMN or SNPN with one or more S-NSSAIs of the current PLMN or SNPN included in the received pending NSSAI IE for storage. Moreover, when roaming, UE_A10 may replace the stored one or more mapped S-NSSAIs of the pending NSSAI of the current PLMN or SNPN with one or more current mapped S-NSSAIs included in the received pending NSSAI IE for storage.

[0574] Alternatively, in the case where the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN or HSNPN, and when UE_A10 receives the pending NSSAI included in the login acceptance message during the login process for the current PLMN or SNPN, the pending NSSAI stored by UE_A10 can be replaced with a new pending NSSAI.

[0575] Moreover, in the case where UE_A10 stores the mapping S-NSSAI of the pending NSSAI, UE_A10 can delete the mapping S-NSSAI of the pending NSSAI, store a new mapping S-NSSAI of the pending NSSAI, or perform both processing.

[0576] It should be noted that the mapping S-NSSAI of the pending NSSAI may be stored based on the mapping S-NSSAI of the old allowed NSSAI.

[0577] Moreover, in the case where a backoff timer for limiting the use of a certain S-NSSAI is being executed, the S-NSSAI is included in a new pending NSSAI, or the S-NSSAI is a mapped S-NSSAI of a pending NSSAI, the UE can stop the backoff timer.

[0578] When the UE uses explicit signaling to deregister the current PLMN or SNPN or enter the 5GMM-DEREGISTERED state for the current PLMN or SNPN, and the UE is not logged in to the current PLMN or SNPN on other access types, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case of an EPLM or ESNPN of the current PLMN or SNPN, the UE may also delete the pending NSSAI of the equivalent PLMN of the current PLMN or the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the pending NSSAI.

[0579] When the UE successfully logs in to a new PLMN or SNPN, or fails to log in to a new PLMN or SNPN and enters the 5GMM-DEREGISTERED state, and the UE has not logged in to the current PLMN or SNPN on other access types, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case of an EPLM or ESNPN of the current PLMN or SNPN, the UE may also delete the pending NSSAI of the equivalent PLMN of the current PLMN or the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the pending NSSAI.

[0580] Alternatively, in the case where the login to a new PLMN or SNPN other than the EPLMN or ESNPN fails and enters the 5GMM-DEREGISTERED state, and in the case where the UE has not logged in to the current PLMN or SNPN on other access types, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case where there is an EPLMN or ESNPN of the current PLMN or SNPN, the UE may also delete the pending NSSAI of the equivalent PLMN of the current PLMN or the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the pending NSSAI. In other words, it may be as follows.

[0581] In the case of failure to log in to a new PLMN other than the equivalent PLMN and entering the 5GMM-DEREGISTERED state, and in the case that the UE has not logged in to the current PLMN on other access types, the UE may delete the pending NSSAI associated with the current PLMN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case of the existence of the EPLMN of the current PLMN, the UE may also delete the equivalent PLMN or pending NSSAI of the current PLMN and / or the mapped S-NSSAI of the pending NSSAI.

[0582] Alternatively, in the case where the login to a new SNPN other than the equivalent SNPN fails and enters the 5GMM-DEREGISTERED state, and in the case where the UE has not logged in to the current SNPN on other access types, the UE may delete the pending NSSAI associated with the current SNPN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case where there is an ESNPN of the current SNPN, the UE may also delete the pending NSSAI of the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the pending NSSAI.

[0583] Alternatively, in the case where the login to a new PLMN or SNPN other than the EPLMN or ESNPN is successful, and in the case where the UE has not logged in to the current PLMN or SNPN on other access types, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapping S-NSSAIs of the pending NSSAI. In the case where there is an EPLM or ESNPN of the current PLMN or SNPN, the UE may also delete the pending NSSAI of the equivalent PLMN of the current PLMN or the equivalent SNPN of the current SNPN and / or the mapping S-NSSAI of the pending NSSAI. In other words, it may be as follows.

[0584] In the case of successful registration of a new PLMN other than the equivalent PLMN, and in the case that the UE has not registered to the current PLMN on other access types, the UE may delete the pending NSSAI associated with the current PLMN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case of the existence of the EPLMN of the current PLMN, the UE may also delete the equivalent PLMN or pending NSSAI of the current PLMN and / or the mapped S-NSSAI of the pending NSSAI.

[0585] Alternatively, in the case where the login to a new SNPN other than the equivalent SNPN is successful, and the UE has not logged in to the current SNPN on other access types, the UE may delete the pending NSSAI associated with the current SNPN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case where there is an ESNPN of the current SNPN, the UE may also delete the pending NSSAI of the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the pending NSSAI.

[0586] Alternatively, when the attach procedure in S1 mode or the start of the tracking area update procedure is successful, the UE operates in single registration mode, and when the UE is not logged in to the current PLMN or SNPN on other access types, the UE may delete the pending NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAIs of the pending NSSAI. In the case of an EPLM or ESNPN of the current PLMN or SNPN, the UE may also delete the pending NSSAI of the equivalent PLMN of the current PLMN or the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the pending NSSAI.

[0587] It should be noted that, when a pending NSSAI stored by the UE and associated with a certain SNPN or PLMN is deleted, the UE may delete one or more mapped S-NSSAIs of the deleted pending NSSAI.

[0588] Moreover, UE_A10 can perform the following operations according to each rejected S-NSSAI IE or according to each partially extended rejected NSSAI list or according to each extended rejected NSSAI IE based on the reception of one or more rejected S-NSSAI IEs and / or partial extended rejected NSSAI list IEs (Partial extended rejected NSSAI list IEs) and / or extended rejected NSSAI IEs indicating the fourth rejected NSSAI and / or the reception of control messages.

[0589] UE_A10 may include the S-NSSAI of the current PLMN or SNPN represented by the fourth rejection NSSAI in an appropriate fourth rejection NSSAI for storage. Specifically, the UE may append the S-NSSAI represented by the received fourth rejection NSSAI to the fourth rejection NSSAI based on the rejection reason value for establishing the association.

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

[0591] Moreover, it may be that when the S-NSSAI included in the fourth rejected NSSAI stored by the UE is included in the allowed NSSAI that has established a corresponding PLMN or SNPN, access type and other access types stored by the UE and requested by the UE in this process, the S-NSSAI is deleted from the allowed NSSAI.

[0592] UE_A10 can start counting the backoff timer associated with S-NSSAI or start the backoff timer based on the reception of the fourth rejection NSSAI and / or the reception of the control message, and can also manage the backoff timer.

[0593] Here, in the case where UE_A10 receives the fourth reject NSSAI together with the backoff timer value, and the value is neither 0 nor information indicating deactivation, the backoff timer value used for the backoff timer may be the received backoff timer value. On the other hand, in other cases, that is, when the backoff timer value is not received, the backoff timer value used for the backoff timer may be an installation-specific value.

[0594] While the back-off timer is executing, UE_A10 may be in a state of prohibiting the sending of MM messages or SM messages using one or more S-NSSAIs corresponding to the back-off timer or one or more mapped S-NSSAIs corresponding to the back-off timer (S-NSSAI of HPLMN or HSNPN), or one or more S-NSSAIs associated with one or more mapped S-NSSAIs corresponding to the back-off timer, or one or more S-NSSAIs included in the NSSAI corresponding to the back-off timer, or one or more S-NSSAIs included in the NSSAI corresponding to the back-off timer.

[0595] During the execution of the backoff timer, UE_A10 may be in a state where one or more S-NSSAIs corresponding to the backoff timer are prohibited from being included in the requested NSSAI together with the associated mapped S-NSSAI.

[0596] Here, along with the stopping or expiration of the backoff timer, the restriction is lifted, and UE_A10 can be transformed into a state where it can send MM messages and SM messages using the S-NSSAI corresponding to the backoff timer and / or the S-NSSAI related to the mapped S-NSSAI corresponding to the backoff timer and / or the mapped S-NSSAI corresponding to the backoff timer. In other words, along with the stopping or expiration of the backoff timer, UE_A10 can be transformed into a state where it can send MM messages using the S-NSSAI corresponding to the backoff timer and / or the S-NSSAI related to the mapped S-NSSAI corresponding to the backoff timer and / or the mapped S-NSSAI corresponding to the backoff timer as requesting NSSAI.

[0597] Moreover, UE_A10 can be changed to a state where it can send an MM message using the NSSAI associated with the back-off timer as the back-off timer stops or expires. In other words, UE_A10 can be changed to a state where it can send an MM message using the NSSAI associated with the back-off timer as a request for NSSAI as the back-off timer stops or expires.

[0598] Moreover, along with the stopping or expiration of the backoff timer, UE_A10 can delete the S-NSSAI corresponding to the backoff timer or the mapped S-NSSAI corresponding to the backoff timer or the S-NSSAI associated with the mapped S-NSSAI corresponding to the backoff timer from the fourth rejected NSSAI.

[0599] Specifically, with the stopping or expiration of the back-off timer, UE_A10 can delete the S-NSSAI associated with the back-off timer or the mapped S-NSSAI corresponding to the back-off timer or the S-NSSAI associated with the mapped S-NSSAI corresponding to the back-off timer from the fourth rejected NSSAI associated with the current PLMN or SNPN.

[0600] Moreover, along with the stopping or expiration of the backoff timer, UE_A10 can delete the S-NSSAI associated with the backoff timer or the S-NSSAI associated with the mapped S-NSSAI corresponding to the backoff timer from the stored fourth rejection NSSAI.

[0601] In UE_A10, when S-NSSAI is deleted from the fourth rejected NSSAI during the execution of the back-off timer in which S-NSSAI is valid, UE_A10 can stop the back-off timer.

[0602] Similarly, in UE_A10, when the backoff timer is valid or the fourth reject NSSAI is deleted during the execution of the backoff timer, UE_A10 can stop the backoff timer.

[0603] Alternatively, UE_A10 in the backoff timer execution may stop and / or delete the backoff timer regardless of the update or deletion of the fourth reject NSSAI. Specific examples of the conditions for deleting the fourth reject NSSAI and / or stopping the backoff timer are as follows.

[0604] When UE_A10 changes to a non-logged-in state on a certain access type for the current PLMN or SNPN and the access type for the other party is also in a non-logged-in state, UE_A10 can delete information that is not related to the access type, namely the fourth rejected NSSAI and / or the S-NSSAI included in the fourth rejected NSSAI.

[0605] When UE_A10 changes to a non-logged-in state on a certain access type for the current PLMN or SNPN and the access type for the other party is also in a non-logged-in state, UE_A10 can stop or delete the fourth rejected NSSAI that is not related to the access type and / or the valid back-off timer of the S-NSSAI included in the fourth rejected NSSAI.

[0606] In the case where UE_A10 receives an allowing NSSAI including the S-NSSAI included in the fourth rejecting NSSAI corresponding to the current PLMN or SNPN from the current PLMN or SNPN, UE_A10 may delete the S-NSSAI from the fourth rejecting NSSAI that is independent of the access type.

[0607] When UE_A10 receives an allowing NSSAI from the current PLMN or SNPN that includes the S-NSSAI included in the fourth rejecting NSSAI that has established a correspondence with the current PLMN or SNPN, UE_A10 may stop or delete the backoff timer that is valid for the S-NSSAI included in the fourth rejecting NSSAI that is independent of the access type.

[0608] In the case where UE_A10 receives a rejection NSSAI including an S-NSSAI included in a fourth rejection NSSAI corresponding to the current PLMN or SNPN from the current PLMN or SNPN, UE_A10 may delete the S-NSSAI from the fourth rejection NSSAI that is independent of the access type.

[0609] When UE_A10 receives a rejection NSSAI from the current PLMN or SNPN that includes the S-NSSAI included in the fourth rejection NSSAI that has established a correspondence with the current PLMN or SNPN, UE_A10 may stop or delete the backoff timer that is valid for the S-NSSAI included in the fourth rejection NSSAI that is independent of the access type.

[0610] In the case where UE_A10 receives a pending NSSAI for NSSAA or a mapped S-NSSAI of the pending NSSAI including the S-NSSAI included in the fourth rejected NSSAI corresponding to the current PLMN or SNPN from the current PLMN or SNPN, UE_A10 can delete the S-NSSAI from the fourth rejected NSSAI that is independent of the access type.

[0611] In the case where UE_A10 receives a pending NSSAI for NSSAA or a mapped S-NSSAI of the pending NSSAI including the S-NSSAI included in the fourth rejected NSSAI that has established a corresponding relationship with the current PLMN or SNPN from the current PLMN or SNPN, UE_A10 may stop or delete the backoff timer in which the S-NSSAI included in the fourth rejected NSSAI is valid.

[0612] When UE_A10 changes to a non-logged-in state for a certain access type for the current PLMN or SNPN, UE_A10 may delete the fourth rejected NSSAI corresponding to the access type and / or the S-NSSAI included in the fourth rejected NSSAI.

[0613] When UE_A10 changes to a non-logged-in state on a certain access type for the current PLMN or SNPN, UE_A10 may stop or delete the valid back-off timer of the fourth rejected NSSAI and / or the S-NSSAI included in the fourth rejected NSSAI corresponding to the access type.

[0614] In the case where UE_A10 receives an allowed NSSAI including the S-NSSAI included in the fourth rejected NSSAI from the current PLMN or SNPN via an access indicated by a certain access type, UE_A10 may delete the S-NSSAI from the fourth rejected NSSAI. At this time, the fourth rejected NSSAI and / or the S-NSSAI included in the fourth rejected NSSAI may establish a correspondence with the current PLMN or SNPN and the access type.

[0615] In the case where UE_A10 receives an allowed NSSAI including the S-NSSAI included in the fourth rejected NSSAI from the current PLMN or SNPN via an access indicated by a certain access type, UE_A10 may stop or delete the backoff timer during which the S-NSSAI included in the fourth rejected NSSAI is valid. At this time, the fourth rejected NSSAI and / or the S-NSSAI included in the fourth rejected NSSAI may establish a correspondence with the current PLMN or SNPN and the access type.

[0616] In the case where UE_A10 senses the change of AMF, UE_A10 may delete the fourth reject NSSAI. And / or, UE_A10 may stop or delete the backoff timer during which the fourth reject NSSAI is valid.

[0617] When UE_A10 enters the 5GMM-DEREGISTERED state due to a failure to log in to the current PLMN or SNPN due to a reason value other than the reason value indicating that there is no available network slice, and when it is not logged in to the current PLMN or SNPN on the access type of the other party, the UE may delete the first or third rejected NSSAI associated with the current PLMN or SNPN and / or one or more mapped S-NSSAIs of the first or third rejected NSSAI.

[0618] Here, the reason value may be a 5GMM cause of 5GS. In this case, the "reason value indicating that there is no available network slice" may be #62 "No network slice available" which is the sixty-second 5GMM cause of 5GS.

[0619] When the UE uses explicit signaling to deregister the current PLMN or SNPN or enter the 5GMM-DEREGISTERED state for the current PLMN or SNPN, and the UE has not logged in to the current PLMN or SNPN on other access types, the UE may delete the first or third rejected NSSAI and / or one or more mapped S-NSSAIs of the first or third rejected NSSAI associated with the current PLMN or SNPN. In the case where there is an EPLM or ESNPN of the current PLMN or SNPN, the UE may also delete the first or third rejected NSSAI of the equivalent PLMN of the current PLMN or the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the first or third rejected NSSAI.

[0620] When the UE successfully logs in to a new PLMN or SNPN, or fails to log in to a new PLMN or SNPN and enters the 5GMM-DEREGISTERED state, and the UE has not logged in to the current PLMN or SNPN on other access types, the UE may delete the first or third rejected NSSAI and / or one or more mapped S-NSSAIs of the first or third rejected NSSAI associated with the current PLMN or SNPN. In the case where there is an EPLM or ESNPN of the current PLMN or SNPN, the UE may also delete the first or third rejected NSSAI of the equivalent PLMN of the current PLMN or the equivalent SNPN of the current SNPN and / or the mapped S-NSSAI of the first or third rejected NSSAI.

[0621] When the UE is deregistered on the first access type, successfully logs in a new login area on the first access type, or fails in the login process on the first access type and the UE enters the 5GMM-DEREGISTERED state, the UE may delete the stored second rejected NSSAI associated with the first access type and / or the current PLMN or SNPN. Moreover, the UE may also delete one or more mapped S-NSSAIs to the deleted second rejected NSSAI associated with the current PLMN or SNPN and the first access type when roaming.

[0622] In the case where the UE is deregistered on the first access type, or the login process on the first access type fails and the UE enters the 5GMM-DEREGISTERED state, the UE may delete the stored fourth rejected NSSAI associated with the first access type and / or the current PLMN or SNPN. Moreover, the UE may also delete one or more mapped S-NSSAIs associated with the deleted fourth rejected NSSAI associated with the current PLMN or SNPN and the first access type when roaming.

[0623] It should be noted that, when the first to fourth rejected NSSAIs are deleted, the UE may delete one or more mapped S-NSSAIs of the deleted first to fourth rejected NSSAIs together.

[0624] According to the above, the UE stores and manages the information related to each NSSAI. Moreover, the UE can start and stop the back-off timer valid for the PLMN or SNPN based on the storage and update of each NSSAI.

[0625] When receiving the first NSSAI, UE_A10 may store the received first NSSAI as "the first NSSAI associated with the current PLMN or SNPN". It should be noted that the "first NSSAI associated with the current PLMN or SNPN" may also be associated with the current access type, or may be managed as information unrelated to the access type.

[0626] When receiving the first NSSAI, UE_A10 may replace the “first NSSAI stored in UE_A10” with the “first NSSAI received by UE_A10”. Alternatively, when receiving the first NSSAI, UE_A10 may include the “S-NSSAI included in the first NSSAI received by UE_A10” in the “first NSSAI stored in UE_A10” for storage.

[0627] It should be noted that, when UE_A10 receives the first NSSAI IE including the first NSSAI, it can store the received first NSSAI in association with the conditional information received together with the first NSSAI.

[0628] In other words, when UE_A10 receives the first NSSAI and condition information, the UE can store the first NSSAI in association with the condition information and / or the current PLMN or SNPN and / or access type.

[0629] It should be noted that, when UE_A10 receives the first NSSAI IE including the first NSSAI, and when the S-NSSAI included in the received first NSSAI has been stored in association with the conditional information, UE_A10 can replace the stored conditional information with the received conditional information.

[0630] In other words, when UE_A10 receives the S-NSSAI included in the first NSSAI IE and the conditional information associated with the S-NSSAI, and when UE_A10 has stored the received S-NSSAI in association with the old conditional information, UE_A10 can replace and update the conditional information stored in association with the S-NSSAI from the old conditional information to the received new conditional information.

[0631] In other words, when UE_A10 receives the S-NSSAI included in the first NSSAI IE and the condition information associated with the S-NSSAI, and when UE_A10 has stored the received S-NSSAI in association with the old condition information, UE_A10 can delete the S-NSSAI from the first NSSAI and store the received S-NSSAI in association with the received new condition information.

[0632] Specifically, when the conditional information is a TA list, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and TA list #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI in association with TA list #2 for storage, UE_A10 can replace the conditional information stored in association with S-NSSAI#1 from TA list #2 to TA list #1, and UE_A10 can also delete S-NSSAI#1 from the first NSSAI, and then store the received S-NSSAI#1 in association with TA list #1.

[0633] Similarly, when the conditional information is regional information, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and regional information #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI for storage in association with regional information #2, UE_A10 can replace the conditional information stored in association with S-NSSAI#1 from regional information #2 with regional information #1, and UE_A10 can also delete S-NSSAI#1 from the first NSSAI, and then store the received S-NSSAI#1 in association with regional information #1.

[0634] Similarly, when the conditional information is time-related information, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and time-related information #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI for storage in association with time-related information #2, UE_A10 may replace the conditional information stored in association with S-NSSAI#1 from time-related information #2 with time-related information #1, and UE_A10 may also delete S-NSSAI#1 from the first NSSAI, and then store the received S-NSSAI#1 in association with time-related information #1.

[0635] In addition, when the conditional information is time-related information, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and time-related information #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI in association with time-related information #2 for storage, and when a timer started based on time-related information #2 and associated with S-NSSAI#1 is executing, UE_A10 can stop the executing timer.

[0636] UE_A10 can start a timer based on time-related information #1 after the timer started based on time-related information #2 in execution expires or stops.

[0637] Alternatively, when UE_A10 receives a first NSSAI IE including a first NSSAI, and when the S-NSSAI included in the received first NSSAI has been stored in association with conditional information, UE_A10 may append the received conditional information to the stored conditional information.

[0638] In other words, when UE_A10 receives the S-NSSAI included in the first NSSAI IE and the condition information associated with the S-NSSAI, and UE_A10 has stored the received S-NSSAI in association with the old condition information, UE_A10 can append and update the received new condition information in the condition information stored in association with the S-NSSAI.

[0639] Specifically, when the conditional information is a TA list, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and TA list #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI in association with TA list #2 for storage, UE_A10 can append one or more TAIs included in TA list #1 to TA list #2 of the conditional information stored in association with S-NSSAI#1.

[0640] Similarly, when the conditional information is regional information, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and regional information #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI for storage in association with regional information #2, UE_A10 may append one or more regional information included in regional information #1 to regional information #2 of the conditional information stored in association with S-NSSAI#1.

[0641] Similarly, in the case where the conditional information is time-related information, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and time-related information #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI for storage in association with time-related information #2, UE_A10 may append one or more time-related information included in time-related information #1 to the time-related information #2 of the conditional information stored in association with S-NSSAI#1.

[0642] In addition, when the conditional information is time-related information, when UE_A10 receives S-NSSAI#1 included in the first NSSAI IE and time-related information #1 associated with S-NSSAI#1, and when UE_A10 has included S-NSSAI#1 in the first NSSAI for storage in association with time-related information #2, and when a timer started based on time-related information #2 and associated with S-NSSAI#1 is executing, UE_A10 can continue without stopping the executing timer.

[0643] UE_A10 may start a timer based on time-related information #1 after the timer started based on time-related information #2 in execution expires or stops. Alternatively, UE_A10 may start a timer based on time-related information #1 in parallel with the timer in execution.

[0644] Moreover, when UE_A10 receives the first NSSAI IE including the first NSSAI, it can delete the mapping S-NSSAI of the S-NSSAI included in the "first NSSAI associated with the current PLMN or SNPN stored by UE_A10". Moreover, when one or more mapping S-NSSAIs are included in the "first NSSAI IE received by UE_A10", UE_A10 can store these one or more mapping S-NSSAIs.

[0645] When the UE's conditions are inconsistent with the conditions indicated by the condition information, UE_A10 can delete the S-NSSAI and / or mapped S-NSSAI associated with the condition information from the set of the first NSSAI and / or the mapped S-NSSAI for the first NSSAI.

[0646] Specifically, when the condition information includes information related to time, the UE may delete the associated S-NSSAI and / or mapped S-NSSAI when the period indicated by the information related to time has passed.

[0647] It should be noted that when the information related to time is a timer value, the period indicated by the information related to time refers to the period from the start of the timer using the timer value to the expiration of the timer. In other words, the period indicated by the information related to time may refer to the expiration of the timer.

[0648] In the case where the condition information includes information related to the location, when the UE moves from the location indicated by the information related to the location, the UE may delete the associated S-NSSAI and / or mapped S-NSSAI.

[0649] Specifically, when the condition information includes a TAI list, when the UE leaves the TA indicated in the TAI list, the UE may delete the associated S-NSSAI and / or mapped S-NSSAI. Alternatively, when the condition information includes area information, when the UE leaves the range indicated in the area information, the UE may delete the associated S-NSSAI and / or mapped S-NSSAI.

[0650] Alternatively, even if the condition information includes location-related information, the UE may maintain the associated S-NSSAI and / or mapped S-NSSAI when the UE moves from the location indicated by the location-related information. In this case, the storage of the associated location-related information may also be maintained.

[0651] Specifically, when the condition information includes a TAI list, when the UE leaves the TA indicated in the TAI list, the UE can maintain the associated S-NSSAI and / or mapped S-NSSAI. Similarly, when the condition information includes area information, when the UE leaves the range indicated in the area information, the UE can maintain the associated S-NSSAI and / or mapped S-NSSAI.

[0652] Similarly, when the condition information includes time-related information, the UE may delete the associated S-NSSAI and / or mapped S-NSSAI when the time indicated by the time-related information has passed, that is, when the timer using the timer value has expired, or when the period indicated by the time-related information has passed.

[0653] Alternatively, when the condition information includes information related to time, the UE may maintain the associated S-NSSAI and / or mapped S-NSSAI even when the period indicated by the information related to time has passed.

[0654] When UE_A10 leaves the login area and the login process in the new login area is successful, UE_A10 can delete the first NSSAI or maintain the first NSSAI.

[0655] The UE may start a login procedure based on deleting the S-NSSAI from the first NSSAI and / or deleting the mapped S-NSSAI from the set of mapped S-NSSAIs for the first NSSAI.

[0656] For UE_A10, when the conditions of the UE are inconsistent with the conditions indicated in the condition information, the UE may maintain storage of the associated S-NSSAI and / or mapped S-NSSAI. In this case, after the timer using a specific timer value expires, the UE may delete the associated S-NSSAI and / or mapped S-NSSAI. The above-mentioned timer using a specific timer value is different from the condition information, and may be a timer indicating the period during which the S-NSSAI is controlled in association with the condition information. The timer value may be sent from the NW to the UE, and may be a value pre-set to the UE. [4. Embodiments of the present invention]

[0657] The embodiments of the present invention may be a combination of the processes described in more than one of the three sections. For example, in this embodiment, the UE may transition to a logged-in state based on the completion of the initial login process described in Section 3.1, and then implement one or more login processes for mobility and periodic login updates in Section 3.1.

[0658] In addition, each process described in Chapters 3.2 to 3.3 may also be implemented when the state is changed to the logged-in state based on the completion of the initial login process described in Chapter 3.1 or when the logged-in state is maintained. It should be noted that in each process, UE_A10 may perform the NSSAI update process described in Chapter 3.3 based on the information received from the NW and / or the state of the UE, and update and / or delete the information related to the stored NSSAI.

[0659] Alternatively, in the embodiment of the present invention, the SM process constituting the sending and receiving of the SM message may be implemented based on the completion of the login process described in Chapter 3.1.

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

[0661] Hereinafter, a first embodiment (hereinafter, this embodiment) will be described.

[0662] In the first embodiment, an example of the behavior of each device when the UE receives condition information indicating the first condition or the second condition associated with the S-NSSAI and / or one or more S-NSSAIs from the NW is described below.

[0663] The UE starts the login process by sending a login request message. It should be noted that the login process may be the login process described in Chapter 3.1.

[0664] The UE receives a login acceptance message including the tenth identification information as a response to the login request message, wherein the login acceptance message includes one or more eleventh identification information and / or one or more twelfth identification information and / or thirteenth identification information.

[0665] Specifically, the eleventh identification information may be an S-NSSAI IE, which may constitute an S-NSSAI and / or a mapped S-NSSAI of the current PLMN or SNPN. Moreover, the twelfth identification information may be sent and received in association with one or more eleventh identification information, and is information indicating the conditions under which the UE can utilize the S-NSSAI indicated by the associated eleventh identification information. On the other hand, the thirteenth identification information may be sent and received in association with one or more eleventh identification information, and is information indicating the conditions under which the UE is not allowed to utilize the S-NSSAI indicated by the associated eleventh identification information.

[0666] The twelfth identification information may include a TAI list and a timer value that can utilize the eleventh identification information. In addition, location-related information and / or time-related information that can be included in the twelfth identification information may also be included in the twelfth identification information.

[0667] The UE may store the eleventh identification information in association with the twelfth identification information and / or the current PLMN or SNPN, and the current access type.

[0668] Furthermore, when the timer value is included in the twelfth identification information and is not 0, the timer using the timer value may be executed. When the timer value is 0, the eleventh identification information may not be stored. When the timer value is 0 and / or from, the UE may recognize that the time-related information is not set from the network.

[0669] The thirteenth identification information may include a TAI list and a timer value that do not allow the eleventh identification information. In addition, location-related information and / or time-related information that can be included in the thirteenth identification information may also be included in the thirteenth identification information.

[0670] The UE may store the eleventh identification information in association with the thirteenth identification information and / or the current PLMN or SNPN, and the current access type.

[0671] The UE may include the eleventh identification information in the first NSSAI stored by the UE or store it in place of the first NSSAI stored by the UE.

[0672] Moreover, the condition information indicated by the twelfth identification information and / or the thirteenth identification information may also be stored in the storage unit of the UE. In the case where the eleventh identification information is received, when the UE replaces and stores the first NSSAI, the UE may delete the stored condition information and store the condition information included in the received twelfth identification information and / or the thirteenth identification information. In other words, if the condition information is newly received, the UE may replace the old condition information for storage.

[0673] It should be noted that, when receiving new condition information during the execution of the timer using the timer value included in the old condition information, the UE may stop and delete the executing timer. Furthermore, the UE may start counting of the timer using the newly received timer value.

[0674] In a case where the S-NSSAI represented by the eleventh identification information is associated with the conditional information and is included in the first NSSAI stored in the UE, the UE can replace the conditional information associated with the S-NSSAI represented by the eleventh identification information with the conditional information included in the received twelfth identification information and / or the thirteenth identification information.

[0675] In other words, when the UE receives the S-NSSAI included in the first NSSAI included in the tenth identification information, the UE can replace the first condition associated with the S-NSSAI with the condition information included in the twelfth identification information, and can also replace the second condition associated with the S-NSSAI with the condition information included in the thirteenth identification information.

[0676] For example, when the UE receives S-NSSAI#1 and condition information #1 associated with S-NSSAI#1, and when the UE stores S-NSSAI#1 in association with condition information #2, the UE can replace and update the condition information associated with S-NSSAI#1 from condition information #2 to condition information #1.

[0677] Alternatively, for example, when the UE receives S-NSSAI#1 and condition information #1 associated with S-NSSAI#1, and when the UE stores S-NSSAI#1 in association with condition information #2, the UE may delete S-NSSAI#1 and condition information #2, and then store S-NSSAI#1 in association with condition information #1.

[0678] Alternatively, in a case where the S-NSSAI represented by the eleventh identification information is associated with the conditional information and is included in the first NSSAI stored in the UE, the UE may append the conditional information included in the received twelfth identification information and / or thirteenth identification information to the conditional information associated with the S-NSSAI represented by the eleventh identification information.

[0679] In other words, when the UE receives the S-NSSAI included in the first NSSAI included in the tenth identification information, the UE may add the conditional information included in the twelfth identification information to the first condition associated with the S-NSSAI, or may add the conditional information included in the thirteenth identification information to the second condition associated with the S-NSSAI.

[0680] In the case of the first condition indicated by the condition information, the UE may send a login request message and / or a PDU session establishment request message using the associated S-NSSAI and / or mapped S-NSSAI.

[0681] Specifically, for example, during the execution of the timer included in the first condition information, and when the UE is in the TA indicated in the TAI list included in the first condition information, the UE may send a login request message including the S-NSSAI and / or mapped S-NSSAI indicated in the eleventh identification information and / or send a PDU session establishment request message together with the S-NSSAI and / or mapped S-NSSAI.

[0682] On the contrary, in the case of the second condition indicated by the condition information, the UE may send a login request message and / or a PDU session establishment request message using the associated S-NSSAI and / or mapped S-NSSAI.

[0683] Specifically, for example, during the execution of the timer included in the second condition information, and when the UE is in the TA shown in the TAI list included in the second condition information, the UE may be in a state where the sending of a login request message including the S-NSSAI and / or mapped S-NSSAI shown in the eleventh identification information and / or the sending of a PDU session establishment request message together with the S-NSSAI and / or mapped S-NSSAI is prohibited and / or prohibited and / or rejected.

[0684] It should be noted that, in this embodiment, the UE receives the tenth identification information during the login process, but it can also be received during the UE setting update process. That is, the UE can perform the same behavior as above based on the reception of the tenth identification information included in the setting update command. It should be noted that the UE setting update process can also be the UE setting update process described in Chapter 3.2.

[0685] Through the above, the UE can control whether to use the associated S-NSSAI in a specific state (condition) specified by the network or prohibit the use of the associated S-NSSAI in a specific state (condition) specified by the network.

[0686] Furthermore, the UE can update a specific state (condition) associated with the S-NSSAI. [5. Modifications]

[0687] The program running in the device of the present invention may be a program that controls a central processing unit (CPU) or the like to make the computer function in a manner that realizes the functions of the embodiments of the present invention. The program or the information processed by the program is temporarily stored in a volatile memory such as a random access memory (RAM) or a non-volatile memory such as a flash memory, a hard disk drive (HDD) or other storage device system.

[0688] It should be noted that the program for realizing the functions of the embodiments involved in the present invention may also be recorded in a computer-readable recording medium. This can be realized by reading the program recorded in the recording medium into a computer system and executing it. The "computer system" mentioned here refers to a computer system built into a device, and includes a computer system of hardware such as an operating system and peripherals. In addition, the "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or other computer-readable recording media.

[0689] In addition, each functional block or each feature of the device used in the above-mentioned embodiment can be installed or executed by an electronic circuit, such as an integrated circuit or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA), or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor may be a microprocessor, or it may be a processor, controller, microcontroller or state machine of the previous type. The aforementioned circuit may be composed of a digital circuit or an analog circuit. In addition, in the case where integrated circuit technology that replaces the current integrated circuit appears due to the advancement of semiconductor technology, one or more schemes of the present invention may also use new integrated circuits based on this technology.

[0690] It should be noted that the present invention is not limited to the above-mentioned embodiments. In the embodiments, an example of a device is described, but the present invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, other life equipment, and other terminal devices or communication devices.

[0691] The embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present invention. In addition, the present invention can be variously modified within the scope indicated by the claims, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other. (Cross-reference of related applications) This application claims the benefit of priority based on Japanese patent application No. 2022-139030 filed on September 1, 2022, and all the contents are incorporated into this specification by reference thereto. Description of Reference Numerals 1: Mobile communication system 10: UE_A 30: PGW-U 32: PGW-C 35: SGW 40: MME 45: eNB 50:HSS 60: PCRF 80: Access network_A (E-UTRAN) 90: Core Network_A 120: Access network_B (5G AN) 122: gNB 130: UPF 132: SMF 140:AMF 150: UDM 160: PCF 190: Core Network_B

Claims

1. A user equipment UE, the user equipment UE comprising a control unit, a transceiver unit and a storage unit, wherein the UE is characterized in that: The transceiver receives first single network slice selection assistance information S-NSSAI and a first tracking area TA list, In the storage unit, when the first S-NSSAI is associated with the second TA list and stored in the network slice selection auxiliary information NSSAI, The control unit replaces the TA list associated with the first S-NSSAI from the second TA list to the first TA list.

2. A user equipment UE, the user equipment UE comprising a control unit, a transceiver unit and a storage unit, wherein the UE is characterized in that: The transceiver receives first single network slice selection assistance information S-NSSAI and a first tracking area TA list, In the storage unit, when the first S-NSSAI is associated with the second TA list and stored in the network slice selection auxiliary information NSSAI, The control unit adds the tracking area identifier TAI included in the first TA list to the list of the second TA associated with the first S-NSSAI.

Images