User equipment (UE) and communication control method for the UE

Abstract

A UE (User Equipment) characterized by comprising a transceiver, a control unit, and a storage unit, wherein the transceiver receives allowed NSSAI (Network Slice Selection Assistance Information), and the control unit deletes, from a mapping S-NSSAI (Single Network Slice Selection Assistance Information) of the allowed NSSAI, a rejected NSSAI stored in the storage unit.

Description

Technical Field

[0001] This invention relates to a UE (User Equipment) and a communication control method for the UE. This application claims priority based on Japanese Patent Application No. 2020-111035, filed on June 29, 2020, the contents of which are incorporated herein by reference. Background Technology

[0002] In the 3GPP (3rd Generation Partnership Project), which has been conducting standardization activities for mobile communication systems in recent years, the SAE (System Architecture Evolution) has been studied as the system framework for LTE (Long Term Evolution).

[0003] Furthermore, in recent years, 3GPP has also conducted research on the next-generation communication technologies and system architectures of 5G (5th Generation) mobile communication systems, particularly standardizing 5GS (5G System) as a system for implementing 5G mobile communication systems (see Non-Patent Literature 1 and Non-Patent Literature 2). In 5GS, technical problems related to connecting various terminals to cellular networks were extracted, and solutions were standardized. Existing technical documents Non-patent literature

[0004] Non-patent document 1: 3GPP TS 23.501V16.4.0 (2020-3); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; SystemArchitecture for the 5G System; Stage 2 (Release 16) Non-patent document 2: 3GPP TS 23.502V16.4.0 (2020-3); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16) Non-patent document 3: 3GPP TS 24.501V16.4.0 (2020-3); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) Summary of the Invention The problem the invention aims to solve

[0005] In 5GS (5G System), research was conducted on 5GCN (5G Core Network) as a new core network to provide a variety of services.

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

[0007] In 3GPP, to further investigate additional functions associated with network slicing, the eNS (Enhancement of Network Slicing) was studied. As part of Phase Two of the eNS study in 3GPP, additional functions for managing the number of UEs or sessions allowed per slice or connection were investigated.

[0008] However, the practical methods for fulfilling the above requests are still unclear.

[0009] One aspect of the present invention is based on the above circumstances, providing a method for implementing the function of eNS in 5GS. Technical solution

[0010] One embodiment of the present invention, a UE (User Equipment), is characterized by comprising: a transceiver unit, a control unit, and a storage unit, wherein the transceiver unit receives allow NSSAI (Network Slice Selection Assistance Information), and the control unit deletes the mapping S-NSSAI (Single Network Slice Selection Assistance Information) of the allow NSSAI from the denial NSSAI stored in the storage unit.

[0011] One aspect of the communication control method executed by the UE (User Equipment) of the present invention is characterized by receiving an NSSAI (Network Slice Selection Assistance Information) permission and deleting the mapping S-NSSAI (Single Network Slice Selection Assistance Information) of the NSSAI permission from the NSSAI denial stored by the UE. Beneficial effects

[0012] According to one aspect of the present invention, in 5GS, eNS can be supported, and the number of UEs allowed per slice can be managed. Attached Figure Description

[0013] Figure 1 This is a diagram illustrating the general structure of a mobile communication system (EPS / 5GS). Figure 2 This is a diagram illustrating the detailed structure of a mobile communication system (EPS / 5GS). Figure 3 This is a diagram illustrating the device configuration of the UE. Figure 4 This diagram illustrates the configuration of the access network device (gNB) in 5GS. Figure 5 This diagram illustrates the configuration of the core network devices (AMF / SMF / UPF) in 5GS. Figure 6 This is a diagram illustrating the login process. Figure 7 This is a diagram illustrating the network slice-specific authentication and authorization process. Figure 8 This is a diagram illustrating the process of changing / updating UE settings. Figure 9 This is a diagram illustrating the non-login process that begins with the network. Detailed Implementation

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

[0015] first, Figure 1 This is a schematic diagram illustrating the mobile communication system 1 used in various embodiments. Figure 2 This is a diagram used to illustrate the detailed configuration of the mobile communication system 1.

[0016] exist Figure 1 The document states that the mobile communication system 1 consists of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

[0017] In the following descriptions, these devices and functions may sometimes be referred to by omitting symbols, similar to UE, Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, etc.

[0018] In addition, Figure 2 The document describes devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and N3IWF170, as well as the interfaces for interconnecting these devices and functions.

[0019] Hereinafter, symbols are sometimes omitted to describe these devices / functions, 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) of a 4G system consists of an access network_A and a core network_A, but may further include the UE and / or PDN. Similarly, the 5GS (5G System) of a 5G system consists of a UE, an access network_B, and a core network_B, but may further include the DN.

[0021] A UE is a device capable of connecting to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (also known as non-3GPP access network, non-3GPP AN). A UE can be a mobile phone, smartphone, or other terminal device capable of wireless communication, or a terminal device capable of connecting to EPS or 5GS. A UE can possess a UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that a UE can be presented as a user equipment or a terminal device.

[0022] Furthermore, Access Network A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or the wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in the E-UTRAN. It should be noted that, hereinafter, the symbol for eNB 45 is sometimes omitted, for example, eNB. Furthermore, in the case of multiple eNBs, each eNB is interconnected, for example, via an X2 interface. In addition, one or more access points are configured in the wireless LAN access network.

[0023] Furthermore, the access network _B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access networks. One or more gNBs (NR Node Bs) 122 are configured in the NG-RAN. It should be noted that, hereinafter, the symbol for gNB 122 is sometimes omitted, for example, eNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node connected to the 5GCN via an NG interface (including the N2 or N3 interface). That is, a gNB is a base station device newly designed for 5GS, with different functions than the base station device (eNB) used in the EPS as a 4G system. Furthermore, in the case of multiple gNBs, each gNB is interconnected, for example, via an Xn interface.

[0024] Furthermore, a non-3GPP access network can be either an untrusted non-3GPP access network or a trusted non-3GPP access network. An untrusted non-3GPP access network can be, for example, a public wireless LAN or other non-3GPP access network that does not undergo security management within the access network. On the other hand, a trusted non-3GPP access network can be an access network defined by 3GPP and can possess TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP gateway function).

[0025] Furthermore, E-UTRAN and NG-RAN will be referred to as 3GPP access in the following text. Additionally, wireless LAN access networks and non-3GPP ANs will be referred to as non-3GPP access. Furthermore, nodes configured in access network B are sometimes collectively referred to as NG-RAN nodes.

[0026] In addition, the devices included in Access Network_A and / or Access Network_B and / or Access Network_A and / or Access Network_B are sometimes referred to as Access Network or Access Network Devices.

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

[0028] Furthermore, the core network_B corresponds to 5GCN (5G Core Network). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN can be represented as 5GC.

[0029] In addition, the following will sometimes refer to core network_A and / or core network_B, devices included in core network_A and / or devices included in core network_B as core network or core network devices or devices within the core network.

[0030] The core network (core network_A and / or core network_B) can be an IP mobile communication network that connects the access network (access network_A and / or access network_B) with the PDN and / or DN operated by the mobile network operator (MNO). It can also be the core network used by the mobile network operator that operates and manages the mobile communication system 1. Furthermore, it can be the 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).

[0031] The core network (core network_A and / or core network_B) and access network (access network_A and / or access network_B) can vary from one mobile communication operator to another.

[0032] In addition, Figure 1 The document describes situations where PDN and DN are similar, but they can also be different. A PDN can be a DN (Data Network) that provides communication services to the UE. It should be noted that a DN can be configured as a packet data service network or configured for each service. Furthermore, a PDN can include connected communication terminals. Therefore, connecting to a PDN can be a connection to a communication terminal or server device configured for the PDN. Moreover, sending and receiving user data with the PDN can be sending and receiving user data with a communication terminal or server device configured for the PDN. It should be noted that a PDN can be represented as a DN, or a DN can be represented as a PDN.

[0033] Furthermore, hereinafter, at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one of these included devices are sometimes referred to as a network or network device. That is to say, the sending and receiving of messages and / or the execution of processes by a network and / or network device means the sending and receiving of messages and / or the execution of processes by at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one of these included devices.

[0034] Furthermore, the UE can connect to the access network. Additionally, the UE can connect to the core network via the access network. Moreover, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send and receive user data with the PDN or DN. When sending and receiving user data, it can use not only IP (Internet Protocol) communication but also non-IP communication.

[0035] Here, IP communication refers to data communication using IP, which involves sending and receiving data via IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted and received by devices / functions included in the EPS and 5GS. Furthermore, non-IP communication refers to data communication that does not use IP, but rather transmits and receives data using a structure different from IP packets. For example, non-IP communication can be data communication achieved by sending and receiving application data without an IP header, or it can use other headers such as MAC headers or Ethernet (trademarked) frame headers to send and receive user data sent and received by the UE.

[0036] Furthermore, Access Network_A, Core Network_A, Access Network_B, Core Network_B, PDN_A, and DN_A may contain elements not described herein. Figure 2The device may include, for example, an AUSF (Authentication Server Function) and an AAA (Authentication, Authorization, and Accounting) server (AAA-S) in core network_A and / or core network_B and / or PDN_A and / or DN_A. The AAA server may be configured outside the core network.

[0037] Here, AUSF is a core network device with authentication functions for both 3GPP and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP and / or non-3GPP access from the UE and performs the authentication process.

[0038] Furthermore, an AAA server is a device that connects directly to AUSF or indirectly via other network devices and possesses authentication, authorization, and accounting functions. An AAA server can be a network device within the core network. It should be noted that an AAA server can be included in the PLMN but not in core network A and / or core network B. That is, an AAA server can be a core network device or a device located outside the core network. For example, an AAA server can be a server device within the PLMN managed by a third party.

[0039] It should be noted that, in Figure 2 For the sake of simplicity, each device / function is shown as one in the diagram, but multiple identical devices / functions can be configured in the mobile communication system 1. Specifically, multiple devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150 can be configured in the mobile communication system 1. [2. Composition of each device]

[0040] Next, the configuration of the various devices (UE and / or access network device and / or core network device) used in each embodiment will be described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware built on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions possessed by each device can also be configured as physical hardware, logical hardware, or software.

[0041] It should be noted that the storage units (Storage Unit_A340, Storage Unit_A440, Storage Unit_B540, Storage Unit_A640, Storage Unit_B740) within each device and function mentioned below are, for example, composed of semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. Furthermore, each storage unit can store not only the information originally set at the factory, but also various information exchanged between the device itself and devices / functions outside the function (e.g., UE and / or access network devices and / or core network devices 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 exchanged during the various communication processes described below. Furthermore, each storage unit can store this information in each UE. Moreover, in the case of interoperability between 5GS and EPS, each storage unit can store control messages and user data exchanged between 5GS and / or devices / functions included in EPS. At this point, it can store not only data sent and received via the N26 interface, but also data not sent and received via the N26 interface. [2.1. UE Device Configuration]

[0042] First, use Figure 3 An example of the device configuration of a UE (User Equipment) will be described. The UE consists of a control unit_A300, an antenna 310, a transceiver unit_A320, and a storage unit_A340. The control unit_A300, transceiver unit_A320, and storage unit_A340 are connected via a bus. The transceiver unit_A320 is connected to the antenna 310.

[0043] The control unit_A300 is a functional unit that controls the overall operation 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.

[0044] The transceiver unit A320 is a functional unit used for wireless communication with base station devices (eNB or gNB) within the access network via an antenna. That is, the UE can use the transceiver unit A320 to send and receive user data and / or control information with access network devices and / or core network devices and / or PDN and / or DN.

[0045] When reference Figure 2In detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface using the transceiver unit (A320). Furthermore, the UE can communicate with the base station device (gNB) in the 5G AN using the transceiver unit (A320). Additionally, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit (A320). However, the N1 interface is a logical interface; therefore, communication between the UE and the AMF actually occurs via the 5G AN.

[0046] The storage unit A340 is a functional unit used to store programs, user data, control information, etc. required for various actions of the UE. [2.2. gNB Device Configuration]

[0047] Next, use Figure 4 An example of the gNB device configuration will be described. The gNB consists 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, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0048] The control unit_B500 is a functional unit that controls the overall operation 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 within the gNB.

[0049] The network connection unit_B520 is a functional unit for enabling communication between the gNB and the 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 with the AMF and / or UPF.

[0050] The transceiver unit B530 is a functional unit used for wireless communication with the UE via the antenna 510. That is, the gNB can use the transceiver unit B530 to send and receive user data and / or control information with the UE.

[0051] When reference Figure 2 In detail, the gNB located in the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface using the network connection unit_B520. Furthermore, the gNB can communicate with the UE using the transceiver unit_B530.

[0052] The storage unit B540 is a functional unit used to store programs, user data, control information, etc., required for various operations of the gNB. [2.3. AMF Device Configuration]

[0053] Next, use Figure 5 An example of the device configuration of an AMF will be described. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF can be a node that processes the control plane.

[0054] The control unit_B700 is a functional unit that controls the overall 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 within the AMF.

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

[0056] When reference Figure 2 In detail, the AMF located within the 5GCN can communicate with the gNB via the N2 interface, with the UDM via the N8 interface, with the SMF via the N11 interface, and with the PCF via the N15 interface using the network connection unit_A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit_A620. However, the N1 interface is a logical interface; therefore, communication between the UE and the AMF is actually conducted via the 5GAN. Additionally, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface using the network connection unit_A620.

[0057] The storage unit B740 is a functional unit used to store programs, user data, control information, etc. required for various operations of the AMF.

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

[0059] Furthermore, the RM state of each UE is managed within the login management system. The RM state can be synchronized between the UE and the AMF (Application Management Frame). There are two RM states: a non-login state (RM-DEREGISTERED state) and a login state (RM-REGISTERED state). In the non-login state, the UE is not logged into the network; therefore, the UE context in the AMF does not have valid location or routing information for that UE, so the AMF is in a state where it cannot reach the UE. Conversely, in the login state, the UE is logged into the network; therefore, the UE can receive services that require network login. It should be noted that the RM state can also be represented as a 5GMM state. In this case, the non-login state can also be represented as a 5GMM-DEREGISTERED state, and the login state can also be represented as a 5GMM-REGISTERED state.

[0060] In other words, 5GMM-REGISTERED can refer to either the state where each device has established a 5GMM context or the state where a PDU session context has been established. It should be noted that when each device is 5GMM-REGISTERED, UE_A10 can begin sending and receiving user data and control messages, and can also respond to paging. Furthermore, 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 used for initial login.

[0061] Furthermore, 5GMM-DEREGISTERED can indicate that the devices have not established a 5GMM context, the UE_A10's location information has not been obtained by the network, or the network cannot reach the UE_A10. It should be noted that when the devices are 5GMM-DEREGISTERED, the UE_A10 can begin the login process or establish a 5GMM context by executing the login process.

[0062] Furthermore, the CM state of each UE is managed within the connection management system. The CM state can be synchronized between the UE and the AMF. There are two CM states: an IDLE state and a CONNECTED state. In the IDLE state, the UE is logged in but does not have a NAS signaling connection established with the AMF via the N1 interface. Additionally, in the IDLE state, the UE does not have an N2 connection or an N3 connection. On the other hand, in the CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. Furthermore, in the CONNECTED state, the UE can also have an N2 connection and / or an N3 connection.

[0063] Furthermore, connection management can be divided into CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access can exist as both an IDLE state and a CONNECTED state. Similarly, the CM states in non-3GPP access can also exist as both an IDLE state and a CONNECTED state. It should be noted that the IDLE state can manifest as an idle mode, and the CONNECTED state can manifest as a connected mode.

[0064] It should be noted that the CM state can also manifest as 5GMM mode. In this case, the non-connected state can also manifest as 5GMM-IDLE mode, and the connected state can also manifest as 5GMM-CONNECTED mode. Furthermore, the non-connected state in 3GPP access can also manifest as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access can also manifest as 5GMM-CONNECTED mode over 3GPP access. Similarly, the non-connected state in non-3GPP access can also manifest as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access can also manifest as 5GMM-CONNECTED mode over non-3GPP access. It should be noted that 5GMM non-connected mode can be represented as idle mode, and 5GMM connected mode can be represented as connected mode.

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

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

[0067] Next, use Figure 5 An example of the device configuration of an SMF will be described. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF can be a node that processes the control plane.

[0068] The control unit_B700 is a functional unit that controls the overall 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 within the SMF.

[0069] The network connection unit_B720 is a functional unit for enabling the SMF to connect 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 with the AMF and / or UPF and / or PCF and / or UDM.

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

[0071] The storage unit B740 is a functional unit used to store programs, user data, control information, etc., required for various operations of the SMF.

[0072] The SMF has the following functions: session management functions such as establishing, modifying, and releasing PDU sessions; IP address allocation and management functions for UEs; UPF selection and control functions; UPF configuration functions for routing services to the appropriate destination (sending destination); SM part functions for sending and receiving NAS messages; Downlink Data Notification functions; AN-specific (each AN's) SM information sent to the AN via the N2 interface through the AMF; SSC (Session and Service Continuity mode) functions for sessions; and roaming functions, etc. [2.5. UPF Device Configuration]

[0073] Next, use Figure 5 An example of the UPF device configuration will be described. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF can be a node that processes the control plane.

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

[0075] 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 within 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 itself and the base station device (gNB) and / or SMF and / or DN within the 5G AN.

[0076] When reference Figure 2 In detail, the UPF located within the 5GCN can communicate with the gNB via the N3 interface, with the SMF via the N4 interface, with the DN via the N6 interface, and with other UPFs via the N9 interface by using the network connection unit _A620.

[0077] The storage unit B740 is a functional unit used to store the programs, user data, control information, etc. required for the various operations of the UPF.

[0078] 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 interconnection with the DN (that is, serving as a gateway between the DN and the core network_B to transmit user data); packet routing and transmission; UL CL (Uplink Classifier) ​​function for routing multiple service flows to a DN; branching point function for supporting multi-homed PDU sessions; QoS (Quality of Service) processing for the user plane; uplink service authentication function; triggering downlink packet buffering; and downlink data notification function.

[0079] Furthermore, a UPF can be a gateway for IP and / or non-IP communication. Additionally, a UPF can have the function of transmitting IP communication, or it can have the function of converting non-IP communication to IP communication. Moreover, multiple configured gateways can be gateways connecting the core network_B and a single DN. It should be noted that the UPF can have connectivity with other NFs, and can also connect to various devices via other NFs.

[0080] It should be noted that the user plane refers to the user data transmitted and received between the UE and the network. The user plane can use PDN connections or PDU sessions for transmission and reception. Furthermore, 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 transmit and receive data 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. The user plane can also be represented as a U-Plane.

[0081] Furthermore, the control plane is responsible for sending and receiving control messages for UE communication control. The control plane can use the NAS (Non-Access-Stratum) signaling connection between the UE and the MME for sending and receiving. In the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for sending and receiving. 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 sending and receiving. The control plane can also be represented as a Control Plane or a C-Plane.

[0082] Furthermore, the user plane (UP) can be a communication path for sending and receiving user data, and can be composed of multiple bearers. Similarly, the control plane (CP) can be a communication path for sending and receiving control messages, and can be composed of multiple bearers. [2.6. Description of other devices and / or functions and / or identification information in this embodiment]

[0083] Next, the identification information and messages that are transmitted, received, stored, and managed by other devices and / or functions and / or each device will be described.

[0084] A network refers to at least a portion of the access network_B, core network_B, and DN. Alternatively, it can refer to one or more devices included in at least a portion of the access network_B, core network_B, and DN as a network or network device. That is, the network performing message transmission, reception, and / or processing can mean that devices within the network (network devices and / or control devices) perform message transmission, reception, and / or processing. Conversely, the devices within the network performing message transmission, reception, and / or processing can mean that the network itself performs message transmission, reception, and / or processing.

[0085] Furthermore, SM (Session Management) messages (also known as NAS (Non-Access-Stratum) SM messages) can be NAS messages used during SM operations, or control messages exchanged between UE_A10 and SMF_A230 via AMF_A240. Moreover, SM messages can include: PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, PDU session modification request messages, PDU session modification command messages, PDU session modification complete messages, PDU session modification command reject messages, PDU session modification reject messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, and PDU session release complete messages, etc. In addition, the procedures used in SM or SM processes may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each procedure can be initiated by the UE or by the NW (network).

[0086] Furthermore, MM (Mobility Management) messages (or NAS MM messages) can be either NAS messages used in MM procedures or control messages exchanged between UE_A10 and AMF_A240. Moreover, MM messages can include: Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages, De-registration accept messages, Configuration update command messages, Configuration update complete messages, Service request messages, Service accept messages, Service reject messages, Notification messages, and Notification response messages, etc. In addition, the procedures used by MM or MM procedures may include: registration procedure, de-registration procedure, generic UE configuration update procedure, authentication and authorization procedure, service request procedure, paging procedure, and notification procedure.

[0087] Furthermore, 5GS (5G System) service can be a connectivity service provided using the core network _B190. Moreover, 5GS service can be a different service from EPS service, or it can be the same service as EPS service.

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

[0089] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, which can be IPv4, IPv6, IPv4v6, or non-IP. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying IPv4v6 indicates that either IPv4 or IPv6 is used for data transmission and reception. Specifying non-IP indicates that communication is conducted not only through IP but also through communication methods other than IP.

[0090] Furthermore, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the association between the DN providing PDU connectivity services and the UE, but it can also be a connection established between the UE and an external gateway. In 5GS, the UE establishes a PDU session through the access network_B and core network_B, thereby enabling the UE to send and receive user data with the DN. Here, the external gateway can refer to UPF, SCEF, etc. The UE can use the PDU session to perform the sending and receiving of user data with devices such as application servers configured on the DN.

[0091] It should be noted that each device (UE and / or access network device and / or core network device) can manage the establishment of more than one identification information corresponding to a PDU session. This identification information can include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and may further include other information. Furthermore, when multiple PDU sessions are established, the identification information corresponding to each PDU session can be the same or different.

[0092] Furthermore, the DNN (Data Network Name) can be identification information for identifying the core network and / or external networks such as DN. Moreover, the DNN can also be used to select gateways such as PGW_A30 / UPF_A235 that connect to the core network_B190. Additionally, the DNN can also be equivalent to the APN (Access Point Name).

[0093] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which can be IPv4, IPv6, Ethernet, or Unstructured. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying Ethernet indicates that Ethernet frames are transmitted and received. Additionally, Ethernet can indicate that communication does not use IP. Specifying Unstructured indicates that point-to-point (P2P) tunneling technology is used to send and receive data to and from application servers, etc., located in the DN. For example, UDP / IP encapsulation technology can be used as a P2P tunneling technology. It should be noted that IP can be included among the above-mentioned other PDU session types. IP can be specified if the UE can use both IPv4 and IPv6.

[0094] Furthermore, a PLMN (Public Land Mobile Network) is a communication network that provides mobile wireless communication services. A PLMN is a network managed by an operator (as a mobile) communication operator, and the operator can be identified through a PLMNID. In this article, PLMN can also mean PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) can be a Home PLMN (HPLMN). PLMN can also refer to the core network.

[0095] Furthermore, the UE can maintain a list of equivalent HPLMNs in the USIM for identifying one or more EHPLMNs. A PLMN that is different from an HPLMMN and / or an EHPLMN can be a VPLMN (Visited PLMN).

[0096] The PLMN that the UE successfully logs into can be an RPLMN (Registered PLMN). Each device can receive from the RPLMN and / or maintain and / or store in the UE's PLMN selection a list of equivalent HPLMNs that can be used to identify one or more EPLMNs (Equivalent PLMNs).

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

[0098] The requested PLMN refers to the destination network for the message sent by the UE. Specifically, it can be the PLMN selected by the UE when sending the message. The requested PLMN is the PLMN requested by the UE, and it can be the current PLMN. In addition, the PLMN requested by the UE when logged in can also be the login PLMN.

[0099] Furthermore, SNPN (Stand-alone Non-Public Network) is a network identified by an SNPN ID, which is a combination of PLMNID and NID (Network identifier), and only allows specific UEs to connect to it. SNPN can also refer to the core network. In this context, the UE allowed to connect to the SNPN can be a UE that has SNPN enabled.

[0100] Furthermore, the UE can maintain a list of equivalent SNPNs in the USIM for identifying one or more ESNPNs. SNPNs that are different from HSNPNs and / or ESNPNs can be VPLMNs (Visited PLMNs).

[0101] The SNPN that a UE successfully logs in to can be an RSNPN (Registered SNPN). Each device can receive from the RSNPN and / or maintain and / or store in the UE's PLMN selection or SNPN selection a list of equivalent SNPNs that can be used to identify one or more ESNPNs (Equivalent PLMNs).

[0102] Furthermore, a network slice (NS) refers to a logical network that provides specific network capabilities and characteristics. The UE and / or network can support network slices (NW slices; NS) in 5GS. Sometimes, network slices are simply referred to as slices.

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

[0104] Here, NST refers to a logical representation of one or more NFs associated with a resource request used to provide the requested communication service or capability. That is, NSI can refer to a collection within a core network (B190) consisting of multiple NFs. Furthermore, NSI can be a logical network configured to divide transmitted user data according to services, etc. An NS can contain more than one NF. NFs within an NS can be devices shared with other NSs or devices not shared with other NSs.

[0105] A UE and / or devices within the network can be assigned to more than one NS based on login information such as NSSAI and / or S-NSSAI and / or UE usagetype and / or more than one NSI ID and / or APN. It should be noted that UE usagetype is a parameter value included in the login information used to identify the UE's NSI. UE usagetype can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usagetype.

[0106] Furthermore, S-NSSAI (Single Network Slice Selection Assistance information) is used to identify NSs. S-NSSAI can consist solely of SST (Slice / Service Type), or it can be composed of both SST and SD (Slice Differentiator). Here, SST refers to information indicating the expected actions of the NS in terms of function and service. SD can be information that interpolates the SST when selecting an NSI from multiple NSIs shown by the SST. S-NSSAI can be information specific to each PLMN, or it can be standard information common to all PLMNs. Additionally, the network can 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, the network can provide UE-related NSs even if the UE does not send a valid S-NSSAI to the network in the login request message.

[0107] Furthermore, S-NSSAI transmitted and received between the UE and NW can also be represented as S-NSSAI IE (Information element). Moreover, the S-NSSAI IE transmitted and received between the UE and NW can consist of S-NSSAI constructed through the SST and / or SD of the PLMN and / or SST and / or SD representing the S-NSSAI of the HPLMN mapped to that S-NSSAI. One or more S-NSSAIs stored by the UE and / or NW can consist of SST and / or SD, or they can consist of S-NSSAI constructed through SST and / or SD and / or SST and / or SD representing the S-NSSAI of the HPLMN mapped to that S-NSSAI.

[0108] Furthermore, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAIs. Each S-NSSAI included in the NSSAI is information that assists in the selection of NSIs by the access network or core network. The UE can store the NSSAIs allowed by the network on a per PLMN basis. In addition, NSSAIs can be information used to select the 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 the PLMN and EPLMN.

[0109] Mapped S-NSSAI is the S-NSSAI of the HPLMN mapped to the S-NSSAI of the logged-in PLMN in a roaming scenario. The UE can store one or more configured NSSAIs and mapped S-NSSAIs included in the allowed NSSAIs for each access type. Furthermore, the UE can also store one or more mapped S-NSSAIs included in the first NSSAI and / or rejected NSSAIs and / or pending NSSAIs.

[0110] Network Slice-Specific Authentication and Authorization (NSSAA) refers to the authentication and authorization functions specific to network slices. NSAA enables UE authentication and authorization outside the core network, such as with third parties. PLMNs and network devices with NSAA capabilities can execute the NSAA procedure on a specific S-NSSAI based on the UE's login information. Furthermore, UEs with NSAA capabilities can manage, store, and send / receive pending NSSAIs and third-party denied NSSAIs. In this document, NSAA is sometimes referred to as the network slice-specific authentication and authorization process, or simply the authentication and authorization process.

[0111] An S-NSSAI requiring NSAA is an S-NSSAI that is managed by the core network and / or core network devices. Furthermore, an S-NSSAI requiring NSAA can also be an S-NSSAI that is managed by the core network and / or core network devices and is outside the HPLMN that maps the S-NSSAI.

[0112] The core network and / or core network devices can store S-NSSAI requiring NSAAA by establishing a correspondence between information indicating whether S-NSSAI and NSAAA are required. The core network and / or core network devices can also establish a correspondence between S-NSSAI requiring NSAAA and information indicating whether NSAAA has been completed or the status of NSAAA being allowed or successfully completed. The core network and / or core network devices can manage S-NSSAI requiring NSAAA as information independent of the access network.

[0113] Furthermore, the configured NSSAI is the NSSAI provided to the UE for storage. The UE can store the configured NSSAI for each PLMN. The UE can also store the configured NSSAI associated with a PLMN. It should be noted that, in this document, the configured NSSAI associated with a PLMN can be represented as the configured NSSAI for the PLMN, the configured NSSAI for the PLMN, the configured NSSAI used by the PLMN, or the configured NSSAI associated with the PLMN. In addition, the UE can also store valid configured NSSAI in all PLMNs without associating with any PLMN; such configured NSSAI can be set as the "default configured NSSAI".

[0114] NSSAI can be configured not to associate with multiple PLMNs, which can be EPLMNs.

[0115] The NSSAI configuration can be information configured by the network (or PLMN). The S-NSSAI included in the NSSAI configuration can be represented as the configured S-NSSAI. The configured S-NSSAI can be structured as including both the S-NSSAI and the mapping S-NSSAI. Alternatively, the PLMN's S-NSSAI can be represented as "configured S-NSSAI," and the mapping of this configured S-NSSAI to the HPLMN's S-NSSAI can be represented as "the mapping S-NSSAI for the PLMN's configured NSSAI."

[0116] The NSSAI setting can be updated by the NW at any time interval, or the updated NSSAI setting can be sent from the NW to the UE based on the update.

[0117] Furthermore, the requested NSSAI is the NSSAI provided by the UE to the network during the login process. During login, the S-NSSAI included in the requested NSSAI sent by the UE can be an S-NSSAI stored in the UE's allowed NSSAI list or an S-NSSAI included in the UE's configured NSSAI list. During PDU session establishment, the S-NSSAI included in the requested NSSAI sent by the UE can be an S-NSSAI included in the UE's stored allowed NSSAI list.

[0118] A request for NSSAI can represent information about a network slice requested by the UE. The S-NSSAI included in the request for NSSAI can be represented as a request for S-NSSAI. For example, a request for NSSAI can be transmitted and received within an RRC (Radio Resource Control) message, which includes NAS (Non-Access-Stratum) messages or NAS (Non-Access-Stratum) messages sent from the UE to the network, such as login request messages or PDU session establishment request messages. In roaming scenarios, the request for NSSAI can include both the VPLMN's S-NSSAI and the mapped HPLMN's S-NSSAI. In other words, the S-NSSAI included in the request for NSSAI (the request for S-NSSAI) can be composed of both S-NSSAI and mapped S-NSSAI.

[0119] Furthermore, an allowed NSSAI indicates one or more network slices that the UE is permitted to connect to. In other words, an allowed NSSAI identifies the network slices that are allowed to connect to the UE. An allowed NSSAI can be stored by the UE and / or the network controller (NW), or it can be sent from the NW to the UE.

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

[0121] Furthermore, the UE and / or NW can establish an association with a PLMN, allowing NSSAI to be stored and managed as information for the UE. NSSAI can be associated with multiple PLMNs, which can be EPLMNs.

[0122] It should be noted that in this paper, the allowed NSSAI corresponding to the PLMN and access type can be expressed as allowed NSSAI for the PLMN and access type or allowed NSSAI for the PLMN and access type. S-NSSAI included in allowed NSSAI can be expressed as allowed S-NSSAI. Allowed S-NSSAI can be configured to include both S-NSSAI and mapped S-NSSAI.

[0123] Furthermore, a rejected NSSAI indicates that the UE is not permitted access to one or more network slices. In other words, a rejected NSSAI identifies network slices that are not allowed to connect to the UE. A rejected NSSAI can be a combination of one or more S-NSSAIs and a rejection reason value.

[0124] Here, the S-NSSAI included in the rejected NSSAI can be associated with a PLMN ID or SNPN ID. It should be noted that the PLMN ID or SNPN represented by the PLMN ID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI can be the current PLMN or the current SNPN. Alternatively, the PLMN ID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI can be unrelated to the current PLMN or SNPN, but instead represent information about an HPLMN or HSNPN.

[0125] Here, the rejection reason value refers to information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and / or the network can appropriately store and manage the rejected NSSAIs based on the corresponding rejection reason values ​​established for each S-NSSAI.

[0126] Furthermore, NSSAI rejection can also be included in NAS messages sent from the network to the UE, such as login acceptance messages, configuration update commands, and login rejection messages, or in RRC messages that include NAS messages. S-NSSAI included in NSSAI rejection can also be expressed as rejected S-NSSAI.

[0127] A rejected NSSAI can be any of the first to third rejected NSSAIs, a pending NSSAI, or a first NSSAI, or a combination of these. An S-NSSAI included in a rejected NSSAI can also be expressed as a rejected S-NSSAI. A rejected S-NSSAI can be composed of both an S-NSSAI and a mapped S-NSSAI.

[0128] The UE and / or NW can associate with a PLMN to store and manage the Reject NSSAI as UE information. The Reject NSSAI may not be associated with multiple PLMNs, which can be EPLMNs.

[0129] It should be noted that in this document, a rejection NSSAI associated with a PLMN can be represented as a rejection NSSAI against the PLMN or a rejection NSSAI against the PLMN. The UE and / or NW can also store the second rejection NSSAI and / or the second rejection S-NSSAI associated with the login area. The UE and / or NW can also store the second rejection NSSAI and / or the second rejection S-NSSAI associated with the access type and / or login area.

[0130] Here, the first rejection NSSAI is a set of more than one S-NSSAI that is unavailable to the UE in the current PLMN or SNPN, which is included in the rejection NSSAI. The first rejection NSSAI can be a rejection NSSAI for the current PLMN or SNPN, a rejection S-NSSAI for the current PLMN or SNPN, or an S-NSSAI included in the rejection NSSAI of the current PLMN or SNPN. The first rejection NSSAI can be a rejection NSSAI stored by the UE or NW, or a rejection NSSAI sent from the NW to the UE.

[0131] When the first rejection NSSAI is sent from the NW to the UE, the first rejection NSSAI can be a combination of one or more S-NSSAIs and a reason value. The reason value can be "S-NSSAI not available in the current PLMN" or information indicating that the S-NSSAI corresponding to the rejection reason value is unavailable in the current PLMN or SNPN. The S-NSSAIs included in the first rejection NSSAI can be expressed as a first rejection S-NSSAI.

[0132] The First Denial NSSAI can be applied to login to the PLMN or the SNPN as a whole. The UE and / or NW can treat the First Denial NSSAI and the S-NSSAI included in the First Denial NSSAI as access type-independent information. That is, the First Denial NSSAI can be valid for both 3GPP access and non-3GPP access.

[0133] The UE can delete the first rejection NSSAI from storage when switching to a non-login state for the current PLMN via both 3GPP and non-3GPP access. In other words, if the UE switches to a non-login state for the current PLMN via one access, or successfully logs into a new PLMN via another access, or fails to log into a new PLMN via another access and switches to a non-login state, and the UE is in a state where it has not logged in via the other access (non-login state), the UE deletes the first rejection NSSAI. That is, if the UE switches to a non-login state for the current PLMN via one access and is in a state where it has logged in via the other access (login state), the UE may not delete the first rejection NSSAI.

[0134] The S-NSSAI included in the first rejection NSSAI, or the first rejection NSSAI itself, can be the S-NSSAI of the current PLMN. In other words, the S-NSSAI included in the first rejection NSSAI, or the first rejection NSSAI itself, can be stored and / or managed and / or transmitted / received only in association with the current PLMN ID or SNPNID. Alternatively, the S-NSSAI included in the first rejection NSSAI can be the S-NSSAI of the HPLMN, or it can be the S-NSSAI of the current PLMN.

[0135] The second rejection NSSAI is a set of one or more S-NSSAIs included in the requested NSSAI that are unavailable to the UE in the current registration area. The second rejection NSSAI can be a rejected NSSAI for the current registration area from the 5GS. The second rejection NSSAI can be a rejection NSSAI stored by the UE or NW, or a rejection NSSAI sent from the NW to the UE. When the second rejection NSSAI is sent from the NW to the UE, it can be information including a combination of one or more S-NSSAIs and a reason value. The reason value can be "S-NSSAI not available in the current registration area," or it can be information indicating that the S-NSSAI corresponding to the reason value is unavailable in the current registration area. The S-NSSAIs included in the second rejection NSSAI can be represented as a second rejection S-NSSAI.

[0136] The second denial NSSAI can be valid within the current login area, or it can be applied to the current login area. The UE and / or NW can treat the second denial NSSAI and the S-NSSAI included in the second denial NSSAI as information for each access type. That is, the second denial NSSAI can be information valid for 3GPP access or non-3GPP access respectively. In other words, the UE can delete the second denial NSSAI associated with a certain access from storage once it switches to a non-login state for that access.

[0137] The S-NSSAI included in the second rejection NSSAI, or the second rejection NSSAI itself, can be the S-NSSAI of the current PLMN. In other words, the S-NSSAI included in the second rejection NSSAI, or the second rejection NSSAI itself, can be stored and / or managed and / or transmitted / received only in association with the current PLMN ID or SNPNID. Alternatively, the S-NSSAI included in the second rejection NSSAI can be the S-NSSAI of the HPLMN, or it can be the S-NSSAI of the current PLMN.

[0138] The third rejection NSSAI is an S-NSSAI that requires an NSSAA, and is a set of one or more S-NSSAIs for which an NSSAA has failed or been cancelled. The third rejection NSSAI can be an NSSAI stored by the UE and / or NW, or an NSSAI transmitted and received between the NW and the UE. When a third rejection NSSAI is sent from the NW to the UE, it can be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value can be "S-NSSAI not available due to the failed or cancelled NSSAA," or it can be information indicating that an NSSAA has failed or been cancelled for an S-NSSAI corresponding to the rejection reason value. The S-NSSAIs included in the third rejection NSSAI can be represented as a third rejection S-NSSAI.

[0139] The Third Rejection NSSAI can be applied to the entire PLMN, to the PLMN and / or EPLMN, or to all PLMNs. Applying the Third Rejection NSSAI to all PLMNs can mean either that the Third Rejection NSSAI does not establish an association with any PLMN, or that the Third Rejection NSSAI establishes an association with any HPLMN.

[0140] Furthermore, the UE and / or NW can treat the Third Reject NSSAI and the Third Reject S-NSSAI as access type-independent information. That is, the Third Reject NSSAI can be valid for both 3GPP and non-3GPP access. The Third Reject NSSAI can be a different NSSAI from the Reject NSSAI. The Third Reject NSSAI can also be the First Reject NSSAI. The Third Reject NSSAI can be the Rejected NSSAI for the Failed or Revoked NSSAA of 5GS, the Rejected S-NSSAI for the Failed or Revoked NSSAA, or the S-NSSAI included in the Reject NSSAI of the Failed or Revoked NSSAA.

[0141] The third rejection NSSAI is a rejection NSSAI used by the UE to identify slices rejected by the core network due to NSSAA failure or cancellation. Specifically, while storing the third rejection NSSAI, the UE does not initiate a login request process for the S-NSSAI included in the third rejection NSSAI. The third rejection NSSAI may include identification information received from the core network that corresponds to one or more rejection reason values ​​indicating NSSAA failure.

[0142] The third rejection NSSAI is information independent of 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 either the 3GPP access or non-3GPP access parties. Alternatively, the UE may send a login request message including the S-NSSAI included in the third rejection NSSAI based on UE policy.

[0143] Alternatively, the UE can delete the third rejection NSSAI based on UE policy and transition to a state where it can send a login request message that includes the S-NSSAI contained in the third rejection NSSAI. In other words, when the UE sends a login request message that includes the S-NSSAI contained in the third rejection NSSAI based on UE policy, the UE can delete the S-NSSAI from the third rejection NSSAI.

[0144] During roaming, the S-NSSAI included in the third rejection NSSAI can be the S-NSSAI of the HPLMN. In other words, the third rejection NSSAI received by the UE from the VPLMN can include the S-NSSAI of the HPLMN.

[0145] Alternatively, during roaming, the S-NSSAI included in the third rejection NSSAI can also be the current PLMN's S-NSSAI. In other words, the S-NSSAI included in the third rejection NSSAI can be stored and / or managed and / or transmitted / received only in association with the current PLMN ID or SNPN ID.

[0146] The first NSSAI can be information including one or more S-NSSAIs that reach the maximum number of UEs per network slice. The first NSSAI can be a rejected NSSAI, an allowed NSSAI, or a pending NSSAI. The first NSSAI can be an NSSAI stored by the UE and / or the NW, or an NSSAI sent from the NW to the UE.

[0147] When the NW sends the first NSSAI to the UE, the first NSSAI may include information including one or more of the following: at least one S-NSSAI and a mapped S-NSSAI, a rejection reason value, a backoff timer value, and information indicating the validity period range of the backoff timer value. The rejection reason value can be either "the S-NSSAI that reaches the maximum number of UEs per network slice" or information indicating the maximum number of UEs allowed by the S-NSSAI corresponding to the rejection reason value.

[0148] Here, the rejection reason value can be the rejection reason value included in the rejection NSSAI, or it can be flag information, or it can be a 5GMM reason (cause). Moreover, at this time, the backoff timer value can be information indicating the following periods: prohibiting the UE from using the S-NSSAI associated with the corresponding S-NSSAI or mapped S-NSSAI, sending MM messages, and sending SM messages.

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

[0150] The first NSSAI can be applied to the entire PLMN, effective across all PLMNs, effective within the login region, and applicable to both the login PLMN and EPLMN. It can also be applied to one or more PLMNs to which a TAI belongs, as listed in the TA list (TAI list or login region). The first NSSAI applying to all PLMNs can mean either that the first NSSAI is not associated with any PLMN, or that it is associated with an HPLMN.

[0151] When the first NSSAI is valid in the entire login PLMN, or applies to all PLMNs, or applies to the login PLMN and / or EPLMN, the UE and / or NW can treat the first NSSAI and the S-NSSAI included in the first NSSAI as access type-independent information. When the first NSSAI is valid in the login area, or applies to one or more PLMNs to which a TAI belongs, as included in the TA list (TAIlist or login area), the UE and / or NW can treat the first NSSAI and the S-NSSAI included in the first NSSAI as information for each access type.

[0152] The first NSSAI can be NSSAI permission, NSSAI rejection, NSSAI pending, or other different information.

[0153] In the case where the first NSSAI is an NSSAI sent from the NW to the UE, the first NSSAI can be a set of combinations of S-NSSAI and mapped S-NSSAI.

[0154] During roaming, the S-NSSAI included in the third denial NSSAI can be the S-NSSAI of the HPLMN. In other words, the third denial NSSAI received by the UE from the VPLMN can include the S-NSSAI of the HPLMN. In this case, the third denial NSSAI can be stored and / or managed in the UE and / or NW in association with the HPLMN. Alternatively, the third denial NSSAI may not be associated with the PLMN ID, but instead be stored and / or managed in the UE and / or NW as common information across all PLMNs.

[0155] Pending NSSAIs are a set of one or more S-NSSAIs that are pending and / or unavailable for use by the UE. Pending NSSAIs require network slice-specific authentication (RSA) and can be a set of S-NSSAIs that have not completed RSA. Pending NSSAIs can be 5GS pending NSSAIs. Pending NSSAIs can be NSSAIs stored by the UE and / or NW, or NSSAIs transmitted and received between UEs and NWs.

[0156] When a pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI can be a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value can be "S-NSSAI is pending for the NSSAI," or it can indicate that the UE is prohibited or has its use of the S-NSSAI corresponding to the rejection reason value established until the NSSAI is completed.

[0157] In the case where the pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI can be a set of combinations of S-NSSAI and mapped S-NSSAI.

[0158] The pending NSSAI can be applied to the entire PLMN, or to the PLMN and one or more EPLMNs within the PLMN, or to all PLMNs. Applying the pending NSSAI to all PLMNs could mean that the pending NSSAI is not associated with any PLMN, or that the pending NSSAI is associated with the HPLMN.

[0159] The UE and / or NW can treat the S-NSSAI included in the pending NSSAI as access type-independent information. That is, the pending NSSAI can be information valid for both 3GPP and non-3GPP access. The pending NSSAI can be a different NSSAI than the rejected NSSAI. The pending NSSAI can also be the first rejected NSSAI.

[0160] A pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify a slice of the process that the UE is pending. Specifically, the UE does not initiate a login request process for the S-NSSAIs included in the pending NSSAI while storing the pending NSSAI. In other words, the UE does not use the S-NSSAIs included in the pending NSSAI during the login process until the NSSAA for the S-NSSAIs included in the pending NSSAI is completed. The pending NSSAI is information independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send login request messages including the S-NSSAIs included in the pending NSSAI to either 3GPP access or non-3GPP access parties.

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

[0162] A tracking area is one or more ranges managed by the core network that can be represented as location information for UE_A10. A tracking area can consist of multiple cells. Furthermore, a tracking area can be a range used for broadcasting control messages such as paging, or a range that UE_A10 can move within without a handover process. Moreover, a tracking area can be a routing area or a location area, as long as it is the same as these areas. Hereinafter, the tracking area can also be referred to as a TA (Tracking Area). A tracking area can be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking Area Code) and a PLMN.

[0163] A registration area is a set of one or more Tracking Areas (TAs) assigned to a UE by the AMF. It's important to note that it's preferable for UE_A10 to move within one or more TAs included in the registration area without transmitting or receiving tracking area update signals. In other words, a registration area can be a group of information representing areas where UE_A10 can move without performing a tracking area update process. Registration areas can be identified by a list of TAIs consisting of one or more TAIs.

[0164] A TAI in the TAI list can belong to one PLMN or multiple PLMNs. If multiple TAIs in the TAI list belong to different PLMNs, these PLMNs can be EPLMNs.

[0165] UE ID refers to information used to identify the UE. Specifically, for example, UE ID can be SUCI (Subscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, UE ID can also be other information configured within an application or network. Furthermore, UE ID can also be information used to identify the user.

[0166] Maximum UE count management for slice connections refers to managing the maximum number of UEs that can simultaneously register in a network slice or S-NSSAI. Here, a UE registering in a network slice or S-NSSAI can refer to an S-NSSAI representing a network slice that is included in the NSSAI storage. Devices within a network that support maximum UE count management for slice connections can store whether maximum UE count management for slice connections is required for each S-NSSAI, and can also confirm during the registration process whether the number of registered UEs has reached a constant that serves as the maximum. Furthermore, each device supporting maximum UE count management for slice connections can store a first NSSAI. In this document, the maximum UE count for slice connections is sometimes expressed as the maximum number of UEs connected to each slice, the maximum number of UEs that can register in a network slice or S-NSSAI, or the maximum number of UEs or a constant.

[0167] A backoff timer is a timer used to initiate the process of prohibiting the transmission of MM messages and / or SM messages implemented by the UE. The backoff timer is managed and executed by the UE. The backoff timer can be associated with an S-NSSAI. The UE can be in a state where, during the effective period of the backoff timer associated with the S-NSSAI, the transmission of MM messages and / or SM messages using that S-NSSAI is prohibited, restricted, or limited. These restrictions can be imposed by 5GS congestion management, or can include restrictions imposed by 5GS congestion management.

[0168] The backoff timer can be a timer that is started and / or stopped in units of S-NSSAI and / or PLMN.

[0169] Specifically, the backoff timer can correspond to S-NSSAI and can be a timer used to prohibit the transmission of MM messages and / or SM messages that use a specific S-NSSAI. In other words, it can be set so that the UE will not transmit MM messages and / or SM messages that use that specific S-NSSAI during the count of this timer.

[0170] Furthermore, it can be configured so that, based on specific conditions described later, the UE allows the transmission of MM messages and / or SM messages that were prohibited in the previous PLMN within the new PLMN during the counting of this timer. It should be noted that allowing the transmission of MM messages and / or SM messages that were prohibited in the previous PLMN can also mean allowing the transmission of MM messages and / or SM messages that use the same S-NSSAI as the corresponding S-NSSAI established with the backoff timer and / or S-NSSAI associated with the same S-NSSAI and / or S-NSSAI associated with the mapped S-NSSAI of the same S-NSSAI.

[0171] Furthermore, the backoff timer can be a timer used to prevent the transmission of MM messages that use a specific NSSAI. In other words, it can also be set so that the UE will not transmit MM messages that use NSSAIs that include that specific NSSAI and / or a specific S-NSSAI during the count of this timer.

[0172] Furthermore, it can be configured so that, based on specific conditions described later, the UE allows the transmission of MM messages that were prohibited in the previous PLMN within the new PLMN during the counting of this timer. It should be noted that allowing the transmission of MM messages that were prohibited in the previous PLMN may also mean allowing the transmission of MM messages using NSSAIs that are the same as the NSSAI corresponding to the backoff timer and / or NSSAIs that are the same as the S-NSSAI corresponding to the backoff timer. Moreover, allowing the transmission of MM messages that were prohibited in the previous PLMN may also mean allowing the transmission of MM messages using NSSAIs that are associated with the S-NSSAI corresponding to the backoff timer and / or NSSAIs associated with the mapped S-NSSAI corresponding to the backoff timer.

[0173] Furthermore, the backoff timer can also correspond to a non-NSSAI (no NSSAI) timer, used to prohibit the transmission of MM messages using non-NSSAI. In other words, UE_A10 can be configured not to transmit MM messages using no NSSAI during this timer count. Moreover, UE_A10 can also be configured to allow the transmission of MM messages prohibited in the previous PLMN in the new PLMN during this timer count, based on specific conditions described later. It should be noted that allowing the transmission of MM messages prohibited in the previous PLMN can also mean allowing the transmission of MM messages using non-NSSAI.

[0174] Furthermore, the backoff timer can be a 5GMM timer and / or an EMM (EPS mobility management) timer. Moreover, the backoff timer can be timer T3448, or a timer equivalent to timer T3448. In other words, the backoff timer can also be the same timer used to restrict communication of user data via the control plane, or the same type of timer.

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

[0176] The first identification information represents the network slice requested by the UE. The first identification information may include information from one or more S-NSSAIs corresponding to the network slice requested by the UE. It should be noted that the network slice requested by the UE can be a network slice that the UE wants to use, or a network slice that the UE requests to be allowed to use by the network. The S-NSSAI included in the first identification information may be an S-NSSAI included in the configuration NSSAI corresponding to the current PLMN, or an S-NSSAI included in the permission NSSAI corresponding to the current PLMN.

[0177] In other words, the first identification information may include one or more S-NSSAIs included in the configured NSSAI corresponding to the current PLMN, or one or more S-NSSAIs included in the permitted NSSAI corresponding to the current PLMN, or a combination of both. More specifically, the permitted NSSAI corresponding to the current PLMN may refer to a permitted NSSAI corresponding to both the current PLMN and the current access type. Furthermore, the first identification information may be a 5GS request NSSAI.

[0178] It should be noted that the S-NSSAI included in the first identification information may be an S-NSSAI not included in the rejected NSSAI associated with the current PLMN stored by the UE and / or an S-NSSAI not included in the pending NSSAI associated with the current PLMN stored by the UE, or an S-NSSAI not included in the first NSSAI associated with the current PLMN stored by the UE.

[0179] Furthermore, during roaming, if the S-NSSAI included in the pending NSSAI and / or rejected NSSAI and / or the first NSSAI is the S-NSSAI of the HPLMN, the S-NSSAI included in the first identification information may be the S-NSSAI of the current PLMN that is not mapped to the pending NSSAI and / or rejected NSSAI and / or the S-NSSAI included in the first NSSAI stored by the UE.

[0180] Furthermore, the S-NSSAI included in the first identification information may be an S-NSSAI in the UE that has been associated with the S-NSSAI or the S-NSSAI mapped to the S-NSSAI but whose backoff timer has not been executed.

[0181] The second identification information may be information indicating whether the function of managing the maximum number of UEs for UE-slice connections is supported. Alternatively, the second identification information may be information indicating whether the function of managing the maximum number of UEs for UE-slice connections is supported. The second identification information may be 5G MM capability information. The second identification information may be information indicating whether the UE can perform storage.

[0182] The tenth identification information may be information indicating that the maximum number of UEs that can log in to the network slice or S-NSSAI has been reached. The tenth identification information may include an allowed NSSAI sent from the network, a denied NSSAI sent from the network, a pending NSSAI sent from the network, or may be sent from the network as information different from these.

[0183] Furthermore, the tenth identification information can also be NSSAI. Moreover, the tenth identification information can be either allowing NSSAI or rejecting NSSAI. Furthermore, the tenth identification information can be pending NSSAI or a different NSSAI.

[0184] The tenth identification information may be a first NSSAI or an S-NSSAI included in the first NSSAI. The tenth identification information may be configured to include at least one of the eleventh to fifteenth identification information. Specifically, the tenth identification information may be configured to include at least one of the following: an S-NSSAI indicating the maximum number of UEs that can log in to the network slice or S-NSSAI; a mapped S-NSSAI of the S-NSSAI; a reason value indicating the maximum number of UEs that can log in to the network slice or S-NSSAI; a value of a backoff timer indicating the period during which UEs are prohibited from using the S-NSSAI to send login request messages; and information indicating the effective range of the backoff timer.

[0185] Furthermore, the tenth identification information may also include at least one of the following: a reason value indicating that the maximum number of UEs that can log in to the network slice has been reached; a backoff timer value indicating the period during which the transmission of login request messages using no NSSAI is prohibited; and information indicating the effective range of the backoff timer. It should be noted that the reason value indicating that the maximum number of UEs that can log in to the network slice has been reached, the backoff timer value indicating the period during which the transmission of login request messages using no NSSAI is prohibited, and the information indicating the effective range of the backoff timer may be transmitted and received separately and are not included in the tenth identification information. Here, when the tenth identification information includes rejection of NSSAI, the reason value included in the tenth identification information may be a rejection reason value.

[0186] The eleventh identification information may be information and / or a reason value indicating that the maximum number of UEs that the network allows a UE to log in to a network slice or S-NSSAI has been reached. The eleventh identification information may also be information and / or a reason value indicating that the use of S-NSSAI is denied or restricted due to reaching the maximum number of UEs connected to each slice. In other words, the eleventh identification information is information and a reason value indicating that the network denies or restricts the use of S-NSSAI for a UE because it has reached the maximum number of UEs connected to each slice.

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

[0188] Furthermore, the eleventh identification information can also be a reason value indicating restrictions and / or disallowance of connection to the slice.

[0189] Furthermore, the eleventh identification information can also be a 5GMM (5G Mobility Management) cause. Moreover, the eleventh identification information can also be a twenty-second 5GMM cause. Here, the twenty-second 5GMM cause can be a cause value indicating congestion. Furthermore, the twenty-second 5GMM cause can also be information sent to the UE due to network congestion.

[0190] Furthermore, the eleventh identification information can also be a 5GMM reason other than the twenty-second 5GMM reason. For example, the eleventh identification information can also be information sent to the UE due to network slice congestion. Moreover, the eleventh identification information can also be information sent to the UE due to insufficient resources in the network slice. Furthermore, the eleventh identification information can also be a reason value indicating that the requested service cannot be provided due to insufficient resources for a specific slice.

[0191] The twelfth identification information can be the value of a backoff timer. Specifically, the twelfth identification information can be information indicating the period during which the network prohibits the UE from using the same S-NSSAI included in the tenth identification information, the fourteenth identification information, and / or the fifteenth identification information, to begin sending an MM message or to begin sending an SM message other than a PDU connection release request message. In other words, the twelfth identification information can be information indicating the period during which the network prohibits the UE from using the same S-NSSAI included in the tenth identification information, the fourteenth identification information, and / or the fifteenth identification information, to begin sending a login request message.

[0192] The twelfth identification information may be included in the tenth identification information, or it may be associated with the S-NSSAI shown in the fourteenth identification information and / or the mapping S-NSSAI shown in the fifteenth identification information included in the same tenth identification information. The twelfth identification information may also be associated with each identification information included in the same tenth identification information.

[0193] The thirteenth identification information indicates the effective range of the backoff timer. Specifically, the thirteenth identification information may be information indicating the effective range of the backoff timer counted by the UE, using the value of the corresponding backoff timer. More specifically, the thirteenth identification information may be information indicating whether the corresponding backoff timer applies to the current PLMN (the PLMN requested by the UE or RPLMN) or applies to all PLMNs. Alternatively, the thirteenth identification information may also be information indicating that it applies to the current login area.

[0194] Furthermore, the thirteenth identification information can be information indicating the scope of the restriction, or information indicating the scope of the application restriction. It should be noted that the restriction can be a restriction implemented through congestion management. More specifically, the constraint can be a constraint restricting the transmission of MM messages by the UE. Moreover, the restriction can be implemented by a backoff timer.

[0195] The thirteenth identification information may be included in the tenth identification information. In this case, the value of the corresponding backoff timer may be the value shown by the twelfth identification information included in the same tenth identification information. In this case, the thirteenth identification information may be associated with each identification information included in the same tenth identification information.

[0196] The fourteenth identification information is information representing the S-NSSAI that represents the maximum number of UEs that can log in to each S-NSSAI. The fourteenth identification information can be an S-NSSAI included in the tenth identification information, and can be associated with the mapped S-NSSAI shown in the fifteenth identification information included in the same tenth identification information. The fourteenth identification information can be associated with each identification information included in the same tenth identification information. Furthermore, the fourteenth identification information can also be an S-NSSAI.

[0197] The fifteenth identification information is the S-NSSAI of the HPLMN associated with the corresponding S-NSSAI. Specifically, if the current PLMN (current PLMN, PLMN requested by the UE, RPLMN, or PLMN selected by the UE) is not an HPLMN, the fifteenth identification information can be the S-NSSAI of the HPLMN that represents the S-NSSAI mapped to the current PLMN. The fifteenth identification information can be a mapped S-NSSAI.

[0198] The fifteenth identification information can be the mapping S-NSSAI included in the tenth identification information, or it can be associated with the S-NSSAI shown in the fourteenth identification information included in the same tenth identification information, or in this case, it can be the mapping S-NSSAI of the S-NSSAI shown in the fourteenth identification information. The fifteenth identification information can be associated with each identification information included in the same tenth identification information. Moreover, the fifteenth identification information can also be the mapping S-NSSAI of the S-NSSAI shown in the fourteenth identification information. [3.1. Description of the processes used in each embodiment]

[0199] Next, the processes used in each embodiment will be described. It should be noted that the processes used in each embodiment include a registration procedure, a network slice-specific authentication and authorization procedure, a generic UE configuration update procedure, and a network-initiated de-registration procedure. Each procedure will be described below.

[0200] It should be noted that in each implementation method, such as Figure 2As described herein, the example given is the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software). However, the content described in this embodiment can also be applied to cases where they are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data can be transmitted and received directly between them, via the N26 interface between AMF and MME, or via UE. [3.2. Login Process]

[0201] First, use Figure 6 The registration procedure is described below. Hereinafter, this refers to the registration procedure. The registration procedure is a process initiated by the UE to register with the access network_B and / or core network_B and / or DN. If the UE is not registered with the network, it can execute this procedure at any time, such as when the power is on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (particularly the UE and AMF) can switch to a registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state can be managed on a per-device basis for each type of access. Specifically, each device can independently manage the registration state (registered state or non-registered state) for 3GPP access and the registration state for non-3GPP access.

[0202] Furthermore, the login process can be a process for updating the UE's location login information in the network and / or for periodically notifying the network of the UE's status and / or updating specific parameters related to the UE in the network.

[0203] The UE can initiate the login process while moving across a TA (Tracking Area). In other words, the UE can initiate the login process when it moves to a TA different from the TA represented by the maintained TA list (TAI list or login area). Furthermore, the UE can also initiate this process when a backoff timer or other timer expires. Moreover, the UE can also initiate the login process when the context of each device needs to be updated due to the disconnection or disabling of the PDU session. Furthermore, the UE can also initiate the login process when capability information and / or preference selection related to the establishment of the UE's PDU session changes. Furthermore, the UE can initiate the login process periodically. Moreover, the UE can initiate the login process based on the completion of the UE configuration update process, the completion of the login process, the completion of the PDU session establishment process, the completion of the PDU session management process, information received from the network during each process, or the expiration or termination of the backoff timer. It should be noted that the UE can execute the login process at any time, and is not limited to these.

[0204] It should be noted that the process used to change the state of the UE from never being logged in to being logged in to the logged-in state can be called the initial registration procedure or the registration procedure for initial registration. The registration procedure performed when the UE is already logged in to the network can be called the registration procedure for mobility and periodic registration update or the mobility and periodic registration procedure.

[0205] Figure 6 The new AMF (new AMF) 141 represents the AMF that UE_A10 has registered through this procedure, and the old AMF (old AMF) 142 represents the AMF that the UE has registered through a previous procedure. If no AMF change occurs during this procedure, no interface or process will occur between the old AMF 142 and the new AMF 141. The new AMF 141 can be the same device as the old AMF 142. In this embodiment, when referred to as AMF, it can mean the new AMF 141, the old AMF 142, or both. It should be noted that the new AMF 141 and the old AMF 142 can both be AMF 140.

[0206] First, UE_A10 initiates the login process by sending a Registration request message to the new AMF141 (S600)(S602)(S604). Specifically, the UE sends an RRC message, including the Registration request message, to the 5G AN120 (or gNB) (S600). It should be noted that the Registration request message can be a NAS message transmitted and received on the N1 interface. Furthermore, the RRC message can be a control message transmitted and received between the UE and the 5G AN120 (or gNB). The NAS message is processed at the NAS layer, and the RRC message is processed at the RRC layer. It should be noted that the NAS layer is a higher layer than the RRC layer.

[0207] Here, UE_A10 can include at least one of the first to second identification information in the login request message and / or RRC message when sending it. Furthermore, UE_A10 can include identification information indicating the type of this process in the login request message and / or RRC message when sending it. Here, the identification information indicating the type of this process can be 5GS registration type IE, or information indicating whether this process is for initial login, login information update during mobility, periodic login information update, or login in an emergency.

[0208] UE_A10 can include its capability information in the login request message to notify the network of the functions supported by the UE. Here, the UE's capability information can be the 5GS 5GMM capability.

[0209] UE_A10 can include this identification information in control messages from different control messages, such as control messages from layers lower than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer). It should be noted that UE_A10 can use this identification information to indicate that UE_A10 supports various functions, to indicate a UE request, or both. Furthermore, when sending and receiving multiple identification messages, two or more of these identification messages can constitute one or more identification messages. It should be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification message, or as different identification messages.

[0210] It should be noted that UE_A10 can select and determine whether to send the first identification information to the second 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 the context maintained by the UE.

[0211] UE_A10 can send the second identification information if it has the function of managing the maximum number of UEs for slice connection or if it requests at least one S-NSSAI that needs to be used for managing the maximum number of UEs for slice connection. UE_A10 can notify the network that it has the function of storing the first NSSAI by sending the second identification information.

[0212] Furthermore, UE_A10 can include capability information indicating NSAA functionality in its login request message, either when it has NSAA functionality or when requesting at least one S-NSSAI that identifies a slice requiring NSAA. By sending this capability information, UE_A10 can request that the UE be recognized as an NSAA-enabled UE in the network and that NSAA-based authentication and authorization processes be performed in UE-related procedures.

[0213] If the UE stores "a corresponding NSSAI is established with the PLMN requested by the UE and the access type requested by the UE" and / or stores "NSSAI is set for the requested PLMN" and / or stores "NSSAI is set by default", the UE may include the first identification information in the login request message and send it to the requested PLMN.

[0214] Alternatively, if the UE stores "a corresponding allowed NSSAI has been established with a PLMN different from the PLMN requested by the UE and the access type requested by the UE", and the TAI included in the login area associated with the allowed NSSAI or the S-NSSAI included in the allowed NSSAI belongs to the PLMN requested by the UE, the UE may include the first identification information in the login request message and send it to the requested PLMN.

[0215] UE_A10 can determine the information included in the first identification information based on one or more NSSAIs stored by the UE. The one or more NSSAIs stored by the UE may be, for example, an allowed NSSAI associated with the requested PLMN and the requested access type, and / or a setting NSSAI and / or a default setting NSSAI associated with the requested PLMN, and / or a rejected NSSAI associated with the requested PLMN. Furthermore / or, the one or more NSSAIs stored by the UE may be a pending NSSAI and / or a first NSSAI, or a rejected NSSAI not associated with the requested PLMN.

[0216] Furthermore / or, one or more NSSAIs stored by the UE may be permitted NSSAIs associated with a PLMN other than the PLMN requested by the UE and the access type and / or access type requested by the UE, and / or second denied NSSAIs associated with a PLMN other than the requested PLMN and the current login area. Moreover, UE_A10 may also store the mapping S-NSSAIs included in each NSSAI stored by the UE.

[0217] The UE can select one or more S-NSSAIs from the stored allowed NSSAIs and / or set NSSAIs, including sending them in the first identification information.

[0218] Specifically, if UE_A10 stores a permitted NSSAI associated with the requested PLMN and the requested access type, UE_A10 may include the permitted NSSAI or one or more S-NSSAIs included in the permitted NSSAI in the first identification information and send it.

[0219] Furthermore / or, if the storage establishes a configuration NSSAI associated with the PLMN requested by UE_A10, UE_A10 may include the configuration NSSAI or one or more S-NSSAIs included in the configuration NSSAI in the first identification information and send it.

[0220] Furthermore / or, if UE_A10 stores "an allowed NSSAI associated with a PLMN other than the requested PLMN and the requested access type", and if a 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, UE_A10 may include the allowed NSSAI or one or more S-NSSAIs included in the allowed NSSAI in the first identification information and send it.

[0221] In other words, UE_A10 may include in the first identification information either "S-NSSAI that is associated with a PLMN other than the requested PLMN and a login area" or "S-NSSAI that is associated with a login area and is included in a PLMN other than the requested PLMN", where at least one TAI included in the login area may belong to the first PLMN.

[0222] The first identification information may be configured to include one or more of the aforementioned S-NSSAIs. UE_A10 can control that the one or more S-NSSAIs included in the first identification information are not repeated.

[0223] Furthermore, if UE_A10 rejects NSSAI for the requested PLMN storage, UE_A10 may not include the S-NSSAI included in the rejected NSSAI in the first identification information during transmission.

[0224] Specifically, when UE_A10 stores a "first rejection NSSAI for establishing association with the requested PLMN", UE_A10 may not include the S-NSSAI included in the first rejection NSSAI in the first identification information before sending it. In other words, UE_A10 may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in the "first rejection NSSAI for establishing association with the requested PLMN" stored by the UE.

[0225] Furthermore, if UE_A10 stores at least one "Second Rejection NSSAI associated with the requested PLMN or EPLMN and the current login area", UE_A10 may not include the S-NSSAIs included in these Second Rejection NSSAIs in the first identification information before transmission. In other words, UE_A10 may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in each of the "Second Rejection NSSAIs associated with the requested PLMN or EPLMN and the current login area" stored by UE_A10.

[0226] If the information representing the current login area stored in UE_A10 includes a TAI belonging to one or more PLMNs that are different from the requested PLMN, and the different one or more PLMNs are EPLMNs of the requested PLMN, UE_A10 may also control the following: one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in each of the "Second Denied NSSAIs associated with one of the different one or more PLMNs and the current login area" stored in UE_A10.

[0227] In other words, if the information stored in UE_A10 indicating the current login area includes a TAI belonging to one or more PLMNs that are different from the requested PLMN, UE_A10 may not include the S-NSSAI included in each "Second Rejection NSSAI that establishes an association between the current login area and one of the different PLMNs" in the first identification information.

[0228] Furthermore, if UE_A10 stores a "third rejection NSSAI associated with the requested PLMN", UE_A10 may not include the S-NSSAI included in the third NSSAI in the first identification information before transmission. In other words, UE_A10 may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in the "third rejection NSSAI associated with the requested PLMN" stored by UE_A10.

[0229] Furthermore, if UE_A10 stores at least one "Third Rejection NSSAI associated with the EPLMN of the requested PLMN", UE_A10 may not include the S-NSSAI included in the third rejection NSSAI in the first identification information during transmission. In other words, UE_A10 may also control that one or more S-NSSAIs included in the first identification information are not included in the S-NSSAIs stored by UE_A10 in each of the "Third Rejection NSSAIs associated with the EPLMN of the requested PLMN".

[0230] Furthermore, if UE_A10 stores "Third Rejection NSSAIs Valid in All PLMNs", UE_A10 may not include the S-NSSAIs included in the third rejection NSSAIs, or the S-NSSAIs mapped to or associated with the S-NSSAIs, or the S-NSSAIs mapped to the S-NSSAIs, in the first identification information during transmission. In other words, UE_A10 may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in each of the "Third Rejection NSSAIs Valid in All PLMNs" stored by UE_A10, or the S-NSSAIs mapped to or associated with the S-NSSAIs, or the S-NSSAIs mapped to the S-NSSAIs. It should be noted that "Third Rejection NSSAIs Valid in All PLMNs" can mean a third rejection NSSAI not associated with a PLMN, or a third rejection NSSAI associated with an HPLMN.

[0231] Furthermore, if the UE stores "pending NSSAI for establishing association with the requested PLMN", the UE may also choose not to include the S-NSSAI included in the pending NSSAI in the first identification information before transmission. In other words, the UE may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in the "pending NSSAI for establishing association with the requested PLMN" stored by the UE.

[0232] Furthermore, if the UE stores at least one "pending NSSAI associated with the EPLMN of the requested PLMN", the UE may also omit the S-NSSAI included in the pending NSSAI from the first identification information during transmission. In other words, the UE may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in each of the "pending NSSAIs associated with the EPLMN of the requested PLMN".

[0233] Furthermore, if the UE stores "pending NSSAIs valid in all PLMNs," the UE may also exclude S-NSSAIs included in the pending NSSAIs, or S-NSSAIs mapped to or associated with the S-NSSAIs, or S-NSSAIs mapped to the S-NSSAIs, from being transmitted in the first identification information. In other words, the UE may also control that one or more S-NSSAIs included in the first identification information are not S-NSSAIs included in each of the "pending NSSAIs valid in all PLMNs," or S-NSSAIs mapped to or associated with the S-NSSAIs, or S-NSSAIs mapped to the S-NSSAIs. It should be noted that "pending NSSAIs valid in all PLMNs" can mean pending NSSAIs not associated with a PLMN, or pending NSSAIs associated with an HPLMN.

[0234] Furthermore, UE_A10 may transmit the S-NSSAI or related S-NSSAI without including it in the first identification information if the backoff timer corresponding to a certain S-NSSAI is valid (in other words, while the backoff timer is executing). Alternatively, the UE may transmit the S-NSSAI or related S-NSSAI without including it in the first identification information until the backoff timer stops. Specifically, if the S-NSSAI corresponding to the backoff timer is an S-NSSAI associated with the requested PLMN or an S-NSSAI included in the NSSAI associated with the requested PLMN, UE_A10 may also not include the S-NSSAI in the first identification information until the backoff timer is counting down, expires, or stops.

[0235] Alternatively, if the S-NSSAI corresponding to the backoff timer is associated with the HPLMN, UE_A10 may not include the S-NSSAI of the requested PLMN mapped to that S-NSSAI in the first identification information during transmission. It should be noted that associating the S-NSSAI corresponding to the backoff timer with the HPLMN can mean that the backoff timer is valid in all PLMNs, or it can mean that the backoff timer is not associated with any PLMN.

[0236] Furthermore, if the UE stores a "first NSSAI for establishing association with the requested PLMN", the UE may also omit the S-NSSAI included in the first NSSAI when sending the first identification information. In other words, the UE may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in the "first NSSAI for establishing association with the requested PLMN" stored by the UE.

[0237] Furthermore, if the UE stores at least one "first NSSAI associated with the EPLMN of the requested PLMN", the UE may also choose not to include the S-NSSAI included in the first NSSAI in the first identification information during transmission. In other words, the UE may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in each "first NSSAI associated with the EPLMN of the requested PLMN".

[0238] Furthermore, if the UE stores a "first NSSAI valid in all PLMNs," the UE may also choose not to include the S-NSSAIs included in that first NSSAI or the S-NSSAIs mapped to that S-NSSAI in the first identification information during transmission. In other words, the UE may also control that one or more S-NSSAIs included in the first identification information are not the S-NSSAIs included in each of the "first NSSAIs valid in all PLMNs" or the S-NSSAIs mapped to that S-NSSAI. It should be noted that "first NSSAI valid in all PLMNs" can mean either a first NSSAI not associated with a PLMN or a first NSSAI associated with an HPLMN.

[0239] During roaming, in the case of a rejected NSSAI and / or a pending NSSAI and / or a first NSSAI including an S-NSSAI of an HPLMN, UE_A10 may control the following: one or more S-NSSAIs included in the first identification information do not include the S-NSSAIs of rejected NSSAIs and / or pending NSSAIs and / or first NSSAIs stored by UE_A10 as mapped S-NSSAIs. In other words, UE_A10 may also control the following: not to include the S-NSSAI of the current PLMN mapped to a rejected NSSAI and / or a pending NSSAI and / or a first NSSAI in the first identification information.

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

[0241] UE_A10 may include information other than the first to second identification information in the login request message and / or the RRC message including the login request message. For example, it may include the UE ID and / or PLMN ID and / or AMF identification information in the login request message and / or the RRC message including the login request message. Here, AMF identification information may refer to information that identifies an AMF or a set of AMFs, such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0242] In addition, UE_A10 can initiate the PDU session establishment process during login by including an SM message (e.g., a PDU session establishment request message) in the login request message or by sending an SM message (e.g., a PDU session establishment request message) together with the login request message.

[0243] When the 5G AN120 (or gNB) receives an RRC message including a login request message, it selects the AMF (Application Function) for transmitting 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. Specifically, the 5G AN (or gNB) can select a new AMF 141 for the destination of the login request message based on at least one of the first to second identification information.

[0244] For example, a 5G AN120 (or gNB) can select an AMF based on first identification information. Specifically, the 5G AN (or gNB) can select an AMF included in or possessing connectivity to the network slice, as identified by S-NSSAI included in the first identification information.

[0245] Moreover, for example, a 5G AN120 (or gNB) can select an AMF that has the function of managing the maximum number of UEs for slice connection and an AMF that has the function of connecting to a network with the maximum number of UEs for slice connection based on the second identification information.

[0246] It should be noted that the method for selecting the AMF is not limited to this; the 5G AN (or gNB) can also select the AMF based on other conditions. The 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 if at least one of the first to second identification information is not included in the login request message but is included in the RRC message, the identification information included in the RRC message can be transmitted together with the login request message to the selected AMF (new AMF141) (S604).

[0247] The new AMF141 can perform a first condition check upon receiving a login request message. The first condition check determines whether the network (or the new AMF141) accepts the UE's request. If the first condition check is true, the new AMF141 executes procedures S606 to S612. Conversely, if the first condition check is false, the new AMF141 may skip procedures S606 to S608 and instead execute procedure S610.

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

[0249] It should be noted that, in this case, if the first condition is true, the control message sent and received in S610 can be a registration accept message, and if the first condition is false, the control message sent and received in S610 can be a registration reject message.

[0250] It should be noted that the first condition determination can be performed based on the receipt of the login request message and / or the various identification information and / or subscriber information and / or network capability information and / or operator policies and / or network status and / or user login information and / or the context maintained by the AMF, etc.

[0251] For example, the first condition can be determined to be true if the network allows the UE's request, and false if the network does not allow the UE's request. Alternatively, the first condition can be determined to be true if the network and / or devices within the UE's login destination support the requested function, and false if the requested function is not supported. Furthermore, the first condition can be determined to be true if the transmission and reception of identification information are allowed, and false if the transmission and reception of identification information are not allowed.

[0252] Alternatively, the first condition can be true if the S-NSSAI included in the NSSAI request received by the AMF from the UE identifies a slice requiring an NSSAA procedure, and if the NSSAA procedure for the corresponding S-NSSAI stored by the AMF for the UE is successful. Or, the first condition can be false if no S-NSSAI has been granted to the UE, and there is no future plan to allocate permission for NSSAI to the UE.

[0253] Furthermore, if the S-NSSAI included in the NSSAI request received by the AMF from the UE identifies the slice that needs to be managed by the maximum number of UEs connected to the slice, and further if the maximum number of UEs has not been reached, the first condition can be true. Alternatively, the first condition can also be true if, even without an S-NSSAI granted to the UE, it is expected that an NSSAI can be granted to the UE in the future.

[0254] If the AMF assigns the first NSSAI to the UE without the UE having allowed the S-NSSAI, the first condition can be true or false.

[0255] If the AMF identification information included in the message received by the new AMF141 from the UE indicates that the AMF is the old AMF142, then procedures S606 and S608 are executed. If the AMF identification information included in the message received by the new AMF141 from the UE_A10 indicates that the AMF is the new AMF141, then procedures S606 and S608 are not executed. In other words, if an AMF change occurs through this process, procedures S606 and S608 are executed; if no AMF change occurs, procedures S606 and S608 are skipped.

[0256] The UE context transmission process (S606, S608) is described below. The new AMF141 sends a UE context request message to the old AMF142 (S606). Based on the received UE context request message, the old AMF142 sends the UE context to the new AMF141. The new AMF141 generates the UE context based on the received UE context.

[0257] Here, the UE context sent from the new AMF141 to the old AMF142 may include the UEID and allow NSSAI. Furthermore, the UE context may also include set NSSAI and / or deny NSSAI, NSSAI and / or pending NSSAI and / or first NSSAI. Additionally, the allow NSSAI and / or set NSSAI and / or deny NSSAI and / or pending NSSAI and / or first NSSAI included in the UE context, as well as the S-NSSAI included in each NSSAI, may be associated with information regarding whether notification to the UE has been completed.

[0258] In addition, the UE context may include information about S-NSSAI that requires the NSSAA process and / or information indicating successful authentication of the UE to complete the NSSAA process and / or information indicating authentication failure.

[0259] In addition, the UE context may include S-NSSAI information that requires management of the maximum number of UEs 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.

[0260] It should be noted that information related to these S-NSSAI characteristics can be managed as a single piece of information. Specifically, the network can store information associated with each S-NSSAI, indicating whether NSAA is required, whether NSAA was successfully performed, whether management of the maximum number of UEs connected to the slice is required, and whether the maximum number of UEs connected to the slice has been reached.

[0261] The new AMF141 can send a control message to the UE based on the determination of the first condition and / or by receiving the UE context from the old AMF142 (S610). The control message can be a login acceptance message or a login rejection message.

[0262] The new AMF141 can include one or more tenth identification information entries in the control message. Alternatively, the new AMF141 can include at least one of the tenth to fifteenth identification information entries in the control message. It should be noted that the new AMF141 can indicate network support for various functions, accept UE requests, disallow requests from UEs, or combinations of these information entries by sending these identification information entries and / or control messages. Furthermore, when sending and receiving multiple identification information entries, two or more of these entries can constitute one or more identification information entries. It should be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification information or as different identification information entries.

[0263] When the new AMF141 receives first identification information and / or second identification information from the UE, it includes at least one of the tenth to fifteenth identification information in the control message and sends it.

[0264] Furthermore, the new AMF141 can send at least one of the tenth to fifteenth identification information even when there is an update to the UE's setting information.

[0265] The new AMF141 can also include setting NSSAI and / or allowing NSSAI and / or denying NSSAI and / or pending NSSAI and / or first NSSAI in the control message sent to UE_A10. It should be noted that the message sent by the new AMF141 to the UE can be based on information received from the UE. Specifically, the S-NSSAI included in the deny NSSAI sent by the new AMF141 to the UE can be the S-NSSAI included in the first identification information received from the UE.

[0266] It should be noted that the tenth to fifteenth identification information may be sent in the context of allowing NSSAI and / or denying NSSAI and / or pending NSSAI and / or the first NSSAI, or may be these NSSAIs.

[0267] The new AMF141 can include an empty value in the allowed NSSAI transmission even if the UE did not allow S-NSSAI (allow NSSAI) when the control message was sent, but there is a scheduled NSSAA procedure to be executed after this procedure is completed or in parallel with this procedure, or an NSSAA procedure is being executed between the UE and the network, or a pending NSSAI has been included in the control message to be sent.

[0268] The new AMF141 can include null values ​​in the sent control message if the UE does not allow S-NSSAI (allow NSSAI) when the control message is sent, but the tenth identification information is included in the control message. In addition, if the UE is notified of the first NSSAI before this procedure, the null value can be included in the sent NSSAI.

[0269] The new AMF141 can include the fifteenth identification information together in the control message, even if the thirteenth identification information, which indicates that it applies to all PLMNs, is included in the control message.

[0270] UE_A10 receives control messages and / or one or more of the tenth to fifteenth identification information from the network. More specifically, the UE receives control messages and / or one or more of the tenth to fifteenth identification information from the new AMF141.

[0271] UE_A10 can identify the received information based on at least one of the tenth to fifteenth identification information. Specifically, UE_A10 can identify that it is in a state where the maximum number of UEs connected to each slice has been reached, and the transmission of MM messages and / or SM messages related to the S-NSSAI shown in the tenth identification information and / or the S-NSSAI shown in the fourteenth identification information and / or the mapped S-NSSAI shown in the fifteenth identification information is temporarily prohibited. It should be noted that, here, the MM procedure can be a login request message, and the SM message can be a PDU session establishment request message.

[0272] UE_A10 may perform the following operations based on the reception of at least one of the tenth to fifteenth identification information and / or the reception of control messages, according to each tenth identification information.

[0273] UE_A10 may include the S-NSSAI associated with the S-NSSAI shown in the tenth identification information and / or the S-NSSAI shown in the fourteenth identification information and / or the mapped S-NSSAI shown in the fifteenth identification information in the appropriate first NSSAI for storage. Specifically, the UE may append the received S-NSSAI shown in the fourteenth identification information to the first NSSAI associated with the information shown in the eleventh identification information and / or the thirteenth identification information.

[0274] Alternatively, UE_A10 can append the mapping S-NSSAI shown in the received fifteenth identification information to the first NSSAI, or append the S-NSSAI related to the mapping S-NSSAI shown in the received fifteenth identification information to the first NSSAI corresponding to the current PLMN, or append it to the first NSSAI corresponding to the current PLMN and the current access type (logged-in access type, 3GPP access or non--3GPP access), or append it to the first NSSAI corresponding to the current PLMN and all access types.

[0275] Alternatively, if the S-NSSAI included in the first NSSAI stored by the UE is included in the allowed NSSAI that has been established with the PLMN, access type and other access types requested by the UE in this process, the S-NSSAI can be deleted from the allowed NSSAI.

[0276] Furthermore, UE_A10 can also, upon receiving the fifteenth identification information, store the S-NSSAI shown in the fifteenth identification information as a mapping S-NSSAI of the S-NSSAI shown in the fourteenth identification information.

[0277] If the received thirteenth identification information indicates that the information applies to all PLMNs, the UE can delete the S-NSSAI associated with the mapping S-NSSAI shown in the fifteenth identification information from the NSSAI allowed for PLMNs other than the current PLMN.

[0278] UE_A10 can identify that the S-NSSAI shown in the tenth identification information has reached the maximum number of UEs connected per slice based on the reception of the tenth identification information and / or the eleventh identification information and / or the reception of control messages. Here, the S-NSSAI shown in the tenth identification information can be the S-NSSAI shown in the fourteenth identification information and / or the mapped S-NSSAI shown in the fifteenth identification information.

[0279] UE_A10 can start counting or start a backoff timer associated with S-NSSAI based on the reception of at least one of the tenth to fifteenth identification information and / or the reception of control messages, using the received backoff timer value. It can also manage the backoff timer. Here, the backoff timer value can be the timer value shown in the tenth and / or twelfth identification information, and S-NSSAI can be the S-NSSAI shown in the first and / or tenth and / or fourteenth identification information and / or the mapped S-NSSAI shown in the fifteenth identification information.

[0280] While the backoff timer is running, UE_A10 can be a state that prohibits the sending of MM messages and SM messages using the S-NSSAI corresponding to the backoff timer, or the S-NSSAI mapped to the backoff timer (S-NSSAI of HPLMN) or the S-NSSAI associated with the S-NSSAI mapped to the backoff timer.

[0281] Furthermore, UE_A10 can also apply the backoff timer based on the valid range indicated by the thirteenth identification information when the thirteenth identification information is received.

[0282] Specifically, if the thirteenth identification information indicates information applied within the current PLMN, the UE can apply a backoff timer within the current PLMN. Specifically, with a PLMN change, UE_A10 may not stop the backoff timer counting or the backoff timer itself, but it can also remove restrictions imposed by backoff timers associated with the PLMN prior to the move. In other words, in the case of a PLMN change, the UE maintains the backoff timer, but can also remove restrictions specific to the PLMN prior to the move.

[0283] Alternatively, UE_A10 can also stop the counting of backoff timers associated with the current PLMN or the backoff timer itself when the PLMN is changed. In other words, UE_A10 can stop the backoff timer when the PLMN is changed, or it can remove the restrictions on the PLMN before the move.

[0284] Alternatively, if the thirteenth identification information indicates that it applies to all PLMNs, the UE can also apply the backoff timer to all PLMNs. In other words, even if a PLMN change occurs, UE_A10 can maintain the backoff timer without stopping it. While the backoff timer is being executed, in the event of a PLMN change, UE_A10 maintains the state that it prohibits the use of the S-NSSAI associated with the mobile destination PLMN established by the mapping S-NSSAI corresponding to the backoff timer, or the S-NSSAI of the mobile destination PLMN associated with the mapping S-NSSAI, or the MM message and SM message of the mapping S-NSSAI.

[0285] Alternatively, if the thirteenth identification information indicates information applicable to the current login area, UE_A10 can apply the backoff timer to the current login area. In other words, as UE_A10 leaves the login area, UE_A10 can stop the backoff timer counting or the backoff timer can be stopped.

[0286] Furthermore, UE_A10 can manage and / or store one or more S-NSSAIs included in the first NSSAI that are associated with the eleventh identification information and / or the thirteenth identification information.

[0287] Here, with the termination or expiration of the backoff timer, the restriction is lifted, and UE_A10 can transition to a state where it can send MM messages and SM messages that use the backoff timer to establish the corresponding S-NSSAI and / or the S-NSSAI associated with the backoff timer's mapping S-NSSAI. In other words, with the termination or expiration of the backoff timer, UE_A10 can transition to a state where it can send MM messages that use the backoff timer's corresponding S-NSSAI and / or the S-NSSAI associated with the backoff timer's mapping S-NSSAI as a request for NSSAI.

[0288] Furthermore, UE_A10 can transition to a state where it can send MM messages using the NSSAI associated with the backoff timer upon the stop or expiration of the backoff timer. In other words, UE_A10 can transition to a state where it can send MM messages using the NSSAI associated with the backoff timer as a request for NSSAI upon the stop or expiration of the backoff timer.

[0289] Furthermore, with the termination or expiration of the backoff timer, UE_A10 can delete the S-NSSAI corresponding to the backoff timer, or the mapping S-NSSAI corresponding to the backoff timer, or the S-NSSAI related to the mapping S-NSSAI corresponding to the backoff timer from the first NSSAI.

[0290] Specifically, when the backoff timer is valid for logging into the PLMN, as the backoff timer stops or expires, UE_A10 can delete the S-NSSAI associated with the backoff timer, the corresponding mapping S-NSSAI established by the backoff timer, or the S-NSSAI associated with the corresponding mapping S-NSSAI established by the backoff timer from the first NSSAI associated with the current PLMN.

[0291] Furthermore, when the backoff timer is valid for logging into the PLMN, UE_A10 can also delete the S-NSSAI associated with the backoff timer, or the corresponding mapping S-NSSAI, or the S-NSSAI associated with the mapping S-NSSAI established by the backoff timer, from the first NSSAI applied to all PLMNs as the backoff timer stops or expires.

[0292] Alternatively, when the backoff timer is valid for all PLMNs, UE_A10 can delete the S-NSSAI associated with the backoff timer, or the corresponding mapping S-NSSAI, or the S-NSSAI associated with the mapping S-NSSAI established by the backoff timer, from the first NSSAI applied to all PLMNs, along with the stopping or expiration of the backoff timer.

[0293] Furthermore, when the backoff timer is valid for all PLMNs, the S-NSSAI associated with the backoff timer, or the corresponding mapping S-NSSAI established by the backoff timer, or the S-NSSAI associated with the corresponding mapping S-NSSAI established by the backoff timer, can be deleted from the first NSSAI applied to each PLMN as the backoff timer stops or expires.

[0294] In other words, if the S-NSSAI associated with the backoff timer, or the corresponding mapped S-NSSAI established by the backoff timer, or the S-NSSAI associated with the corresponding mapped S-NSSAI established by the backoff timer is included in multiple first NSSAIs and stored by UE_A10, UE_A10 can delete the corresponding S-NSSAI from all the corresponding first NSSAIs.

[0295] Specifically, for example, if the backoff timer #1 associated with S-NSSAI#1 is managed to be valid in all PLMNs, with the termination or expiration of the backoff timer #1, the UE can remove S-NSSAI#1 from the first NSSAI#1 associated with PLMN#1, and then remove S-NSSAI#2 associated with the mapping S-NSSAI of S-NSSAI#1 from the first NSSAI#2 associated with PLMN#2.

[0296] Alternatively, if UE_A10 receives a TAI list, the received TAI list can be set to valid; if UE_A10 already stores a valid TAI list, the old TAI list can be deleted or invalidated. Hereinafter, the valid TAI list will be represented as the login area. It should be noted that if UE_A10 does not store a valid TAI list, and no TAI list is received from the core network during this process, the valid TAI list may be in an unstored state.

[0297] Furthermore, UE_A10 can appropriately store each received NSSAI. Specifically, upon receiving a setting NSSAI, UE_A10 can store the received setting NSSAI as "the setting NSSAI associated with the current PLMN". That is, UE_A10 can replace "the setting NSSAI associated with the current PLMN stored by UE_A10" with "the received setting NSSAI".

[0298] Furthermore, UE_A10 can delete the S-NSSAI mappings included in "the S-NSSAIs associated with the current PLMN stored by UE_A10" upon receiving the setting NSSAI. Moreover, if the "received setting NSSAIs" include one or more mappings S-NSSAIs, UE_A10 can store these one or more mappings S-NSSAIs.

[0299] Furthermore, UE_A10 can delete the "reject NSSAI stored in UE_A10 that is associated with the current PLMN" when it receives the NSSAI setting.

[0300] Alternatively, upon receiving the set NSSAI, UE_A10 may delete at least one of the following: "first rejection NSSAI stored by UE_A10 and associated with the current PLMN", "second rejection NSSAI stored by UE_A10 and associated with the current PLMN", and "third rejection NSSAI stored by UE_A10 and associated with the current PLMN".

[0301] Furthermore, upon receiving the set NSSAI, UE_A10 can delete "the first NSSAI stored by UE_A10" and / or "the first NSSAI stored by UE_A10 that is associated with the current PLMN" and / or one or more "the first NSSAI stored by UE_A10 that is associated with the current PLMN's EPLMN".

[0302] Furthermore, upon receiving a set NSSAI, UE_A10 can delete "pending NSSAI stored in UE_A10" and / or "pending NSSAI stored in UE_A10 that is associated with the current PLMN" and / or one or more "first pending NSSAI stored in UE_A10 that is associated with the current PLMN's EPLMN".

[0303] Furthermore, UE_A10 can, upon receiving a permitted NSSAI, store the received permitted NSSAI as "a permitted NSSAI associated with the current PLMN and the current access type". In other words, UE_A10 can replace the "permitted NSSAI associated with the current PLMN and the current access type" stored in UE_A10 with "the received permitted NSSAI".

[0304] Furthermore, if UE_A10 receives a list of TAIs and allowed NSSAIs from the new AMF141, and at least one TAI in the TAI list belongs to an EPLMN, UE_A10 can store the received allowed NSSAIs as "allowed NSSAIs associated with the EPLMN to which the TAIs in the TAI list belong and the current access type".

[0305] It should be noted that, when storing NSSAI, UE_A10 can store either the NSSAI that is allowed to be associated with the login region, or the S-NSSAI included in the NSSAI that is allowed to be associated with the login region.

[0306] Furthermore, UE_A10 can delete the mapping S-NSSAI included in either "based on received deleted allowed NSSAI" or "based on received updated old allowed NSSAI" upon receiving an allowed NSSAI. Moreover, if UE_A10 includes the mapping S-NSSAI in "received allowed NSSAI", UE_A10 can store one or more of those mappings.

[0307] In cases where an S-NSSAI included in the old allowed NSSAI is included in the pending NSSAI and is received by UE_A10, the mapped S-NSSAI of that S-NSSAI may not be deleted.

[0308] If UE_A10 receives an MM message that includes both NSSAI enabled and NSSAI pending, UE_A10 can perform control of receiving based on NSSAI pending before performing receiving based on NSSAI enabled.

[0309] Specifically, if the old allowed NSSAIs stored in UE_A10 include S-NSSAI#1, and UE_A10 receives from the network a pending NSSAI including S-NSSAI#1 and a new allowed NSSAI excluding S-NSSAI#1, UE_A10 may perform an update of the received stored NSSAIs based on the pending NSSAIs before performing an update of the received stored NSSAIs based on the allowed NSSAIs.

[0310] Similarly, when UE_A10 receives an MM message that includes both allowing NSSAI and denying NSSAI, UE_A10 can perform control based on denying NSSAI before performing control based on allowing NSSAI.

[0311] Specifically, if the old allowed NSSAIs stored in UE_A10 include S-NSSAI#1, and UE_A10 receives from the network a rejected NSSAI including S-NSSAI#2, which is a mapped S-NSSAI as S-NSSAI#1, and a new allowed NSSAI that does not include S-NSSAI#1, UE_A10 may perform an update of the stored NSSAIs received based on rejected NSSAIs before performing an update of the stored NSSAIs received based on allowed NSSAIs.

[0312] Furthermore, UE_A10 can delete the S-NSSAI that is "stored in UE_A10 and associated with the current PLMN and is denied NSSAI" if it receives an NSSAI permission.

[0313] Specifically, UE_A10 may, upon receiving an allowed NSSAI, delete the S-NSSAI included in the received allowed NSSAI and / or the mapped S-NSSAI of the received allowed NSSAI from at least one of "first denied NSSAI stored by UE_A10 and associated with the current PLMN", "second denied NSSAI stored by UE_A10 and associated with the current PLMN", "second denied NSSAI stored by UE_A10 and associated with the current PLMN and the current login area", and "third denied NSSAI stored by UE_A10 and associated with the current PLMN". Alternatively, it may delete the S-NSSAI included in the received allowed NSSAI and / or the mapped S-NSSAI of the received allowed NSSAI from all NSSAIs.

[0314] Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from the "Pending NSSAIs stored by UE_A10 that are associated with the current PLMN". Also, upon receiving an allowed NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from the "Pending NSSAIs stored by UE_A10 that are associated with all PLMNs". Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from the "Pending NSSAIs stored by UE_A10 that are associated with EPLMNs".

[0315] In a roaming scenario, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN, UE_A10 can, upon receiving an allowed NSSAI, delete the mapped S-NSSAI of the newly received allowed NSSAI from the "pending NSSAI stored in UE_A10". At this time, in the roaming scenario, the allowed NSSAI is associated with the current PLMN or the current SNPN, i.e., the PLMN ID or SNPN ID representing the RPLMN or RSNPN. On the other hand, the S-NSSAI included in the pending NSSAI can be the S-NSSAI of the HPLMN.

[0316] Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with the current PLMN stored by UE_A10". Alternatively, upon receiving an allowed NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with all PLMNs stored by UE_A10".

[0317] Furthermore, upon receiving a rejection NSSAI, UE_A10 can store the rejection reason value associated with the S-NSSAI included in the received rejection NSSAI as an appropriate rejection NSSAI. In other words, UE_A10 can append the S-NSSAI included in the received rejection NSSAI to the "rejection NSSAI" stored in UE_A10.

[0318] Specifically, when UE_A10 receives the rejection reason value "S-NSSAI is not available in the current PLMN or SNPN" and the 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.

[0319] Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI is not available in the current login area" and the 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 and the current login area".

[0320] Furthermore, when UE_A10 receives the rejection reason value "S-NSSAI unavailable due to NSSAA failure or cancellation" and a rejection S-NSSAI associated with the rejection reason value, UE_A10 can append the "received rejection S-NSSAI" to the "third rejection NSSAI". In this case, the "third rejection NSSAI" can be associated with the current PLMN or can be used in all PLMNs.

[0321] It should be noted that when UE_A10 receives a TAI list along with the rejected NSSAI, the current login area is represented by the received TAI list. Conversely, when UE_A10 does not receive a TAI list along with the rejected NSSAI, the current login area is represented by the TAI list previously received and stored by UE_A10. Furthermore, when UE_A10 receives the rejection reason value "S-NSSAI unavailable due to NSSAA failure or cancellation" and a rejected NSSAI including a rejected S-NSSAI associated with the rejection reason value, UE_A10 can append and / or store the S-NSSAI in the third rejected NSSAI. It should also be noted that when the UE stores a third rejected NSSAI associated with the current PLMN, the received S-NSSAI can be appended and / or stored in the third rejected NSSAI associated with the current PLMN.

[0322] Furthermore, if a rejected NSSAI is received, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from "Allowed NSSAIs stored in UE_A10 and associated with the current PLMN".

[0323] Here, if UE_A10 receives a rejected NSSAI that includes an S-NSSAI associated with the HPLMN, and if the mapped S-NSSAI included in "Allowed NSSAIs associated with the current PLMN stored by UE_A10" is included in the rejected NSSAI received by UE_A10, UE_A10 can delete the S-NSSAI from "Allowed NSSAIs associated with the current PLMN stored by UE_A10".

[0324] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "Pending NSSAIs Associated with the Current PLMN stored in UE_A10". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with All PLMNs stored in UE_A10". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with EPLMN stored in UE_A10".

[0325] Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with the current PLMN stored by UE_A10". Alternatively, upon receiving an allowed NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with all PLMNs stored by UE_A10".

[0326] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "Pending NSSAIs Associated with the Current PLMN stored in UE_A10". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with All PLMNs stored in UE_A10". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with EPLMN stored in UE_A10".

[0327] It should be noted that during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the HPLMN, the pending NSSAI stored by the UE is the S-NSSAI of the current PLMN (i.e., the VPLMN), the UE_A10 receives a rejected NSSAI, or the mapped S-NSSAI of a certain S-NSSAI included in "pending NSSAIs stored by UE_A10 that are associated with the current PLMN" is included in the rejected NSSAI, then the S-NSSAI can be deleted from "pending NSSAIs stored by UE_A10 that are associated with the current PLMN".

[0328] Alternatively, during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the HPLMMN, and the pending NSSAI stored by the UE is also the S-NSSAI of the HPLMMN, the UE_A10 may, upon receiving a rejected NSSAI, delete the S-NSSAI included in the received rejected NSSAI from the "pending NSSAIs stored by UE_A10 that are associated with the current PLMN".

[0329] Alternatively, during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the current PLMN (i.e., the VPLMN), the pending NSSAI stored by the UE is the S-NSSAI of the HPLMN, the UE_A10 receives a rejected NSSAI, or if an S-NSSAI included in the pending NSSAIs stored by the UE_A10 is a mapped S-NSSAI of the rejected NSSAI or a mapped S-NSSAI of the rejected NSSAI, the S-NSSAI can be deleted from the pending NSSAIs stored by the UE_A10.

[0330] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "First NSSAIs stored by UE_A10 that are associated with the current PLMN". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "First NSSAIs stored by UE_A10 that are associated with all PLMNs". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "First NSSAIs stored by UE_A10 that are associated with EPLMNs".

[0331] Furthermore, upon receiving a pending NSSAI, UE_A10 can replace the pending NSSAI stored in UE_A10 with a new pending NSSAI. Specifically, upon receiving a pending NSSAI included in the login acceptance message during the login process for the current PLMN or SNPN, UE_A10 can replace the pending NSSAI associated with the current PLMN or SNPN stored in UE_A10 with a new pending NSSAI.

[0332] Alternatively, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN, or if the pending NSSAI included in the login acceptance message during the login process for the current PLMN or SNPN received by UE_A10, the pending NSSAI stored in UE_A10 can be replaced with a new pending NSSAI.

[0333] Furthermore, when UE_A10 stores the mapping S-NSSAI of pending NSSAI, UE_A10 can delete the mapping S-NSSAI of pending NSSAI, store the mapping S-NSSAI of new pending NSSAI, and perform processing on both sides.

[0334] It should be noted that the pending NSSAI mapping S-NSSAI can be stored based on the old NSSAI-enabled mapping S-NSSAI.

[0335] It should be noted that the various processes performed by the UE based on the receipt of each identification information, as described above, can be performed during this process or after the completion of this process, or they can be performed after the completion of this process based on the completion of this process.

[0336] It should be noted that the AMF can select and determine which identification information from the tenth to the fifteenth identification information to include in the control message based on the received identification information and / or subscriber information and / or network capability information and / or operator policies and / or network status and / or user login information and / or the context maintained by the AMF.

[0337] Furthermore, AMF can include SM messages (e.g., PDU session establishment accept messages) within the login accept message when the control message is a login accept message, or send SM messages (e.g., PDU session establishment accept messages) together with the login accept message. However, this sending method can also be performed when the login request message includes SM messages (e.g., PDU session establishment request messages). Additionally, this sending method can also be performed when SM messages (e.g., PDU session establishment request messages) are sent together with the login request message. AMF can indicate that the SM process has been accepted during the login process by performing such sending methods.

[0338] In addition, the AMF can indicate that the UE's request has been 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 policies and / or network status and / or user login information and / or the context maintained by the AMF, or it can indicate that the UE's request has been rejected by sending a login rejection message.

[0339] The UE receives a control message via the 5G AN (gNB) (S608). If the control message is a login acceptance message, the UE can identify that its request based on the login request message has been accepted and the content of various identification information included in the login acceptance message by receiving the login acceptance message. Alternatively, if the control message is a login rejection message, the UE can identify that its request implemented by the login request message has been rejected and the content of various identification information included in the login rejection message by receiving the login rejection message. Furthermore, the UE can also identify that its request has been rejected if it has not received a control message after a specified period of time following the sending of the login request message.

[0340] 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 the PDU session establishment completion message or other SM messages in the login completion message when it receives PDU session establishment acceptance messages, or it can indicate the completion of the SM process by including the SM message. Here, the login completion message is a NAS message transmitted and received on the N1 interface, but it is included in the RRC message for transmission and reception between the UE and the 5G AN (gNB).

[0341] The AMF receives the login completion message via the 5G AN (gNB) (S612). Furthermore, each device completes this process based on the transmission and reception of the login acceptance message and / or login completion message.

[0342] Alternatively, each device can complete the login process based on the sending and receiving of login rejection messages.

[0343] It should be noted that each device can transition to or maintain a state where the UE is already logged into the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission and reception of login acceptance messages and / or login completion messages. Alternatively, it can transition to or maintain a state where the UE is not logged into the network relative to the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of login rejection messages. Furthermore, transitions to different states can be based on the transmission and reception of login completion messages or the completion of the login process.

[0344] Furthermore, each device can perform processing based on the information sent and received during the login process upon completion of the login process. For example, the reason for the UE's request being rejected can be identified when information indicating that part of the UE's request has been rejected is sent and received. Moreover, each device can re-enact the process based on the reason for the UE's request being rejected, and can also perform the login process on core network A or other cells.

[0345] Furthermore, the UE can store the identification information received along with the login acceptance message and / or login rejection message based on the completion of the login process, and can also identify the network.

[0346] Furthermore, the UE can delete one or more stored NSSAIs based on the completion of the login process. Specifically, based on the completion of this process, if the UE_A10 transitions to a non-login state for the current PLMN on both access methods (3GPP access and non-3GPP access), the UE_A10 can delete the stored first rejected NSSAI and / or third rejected NSSAI and / or first NSSAI.

[0347] Furthermore, based on the completion of this process, if UE_A10 transitions to a non-login state on a certain access (3GPP access and non-3GPP access) for the current PLMN, or if UE_A10 successfully completes the login process in a new login area, or if the result of UE_A10 performing the login process in a new login area is a transition to a non-login state or a login state on a certain access, UE_A10 can delete the second rejection NSSAI associated with the current PLMN, the current login area, and / or the access type.

[0348] Furthermore, each device can restart the login process based on the expiration or termination of the backoff timer.

[0349] Furthermore, each device can restart the login process based on the stored NSSAI updates.

[0350] Furthermore, each device can initiate the SM process by sending and receiving SM messages based on the transition to or maintenance of the UE's logged-in state (RM_REGISTERED state, or 5GMM-REGISTERED state). [3.3. Network Slice-Specific Authentication and Authorization Process]

[0351] Next, use Figure 7 The Network Slice Specific Authentication and Authorization (NSSAA) process is described below. Hereinafter, the NSSAA process will also be referred to as this process. This process can be a procedure used by the core network to perform authentication and authorization processes for UEs in slices requiring the NSSAA process. Here, the authentication and authorization processes can be re-authentication and re-authorization processes.

[0352] This process is executed by the PLMN and can be performed on each object that is an NSSAA process, S-NSSAI (mapped S-NSSAI), and / or UE. This process can be executed in the completed state of the login process.

[0353] This process can be initiated by AMF140. For example, AMF140 can initiate this process based on the receipt of a login request message from UE_A10. AMF140 can initiate this process without storing the result of the NSSAA procedure for at least one S-NSSAI requested by UE_A10 or a mapped S-NSSAI that requires the NSSAA procedure. Here, the result of the NSSAA procedure can be information indicating NSSAA success, information indicating NSSAA failure, or both. Moreover, the information indicating NSSAA success can be allowing the NSSAA procedure. In other words, if the S-NSSAI is stored as allowing the NSSAA procedure, AMF140 can recognize that the NSSAA procedure for the S-NSSAI has been successful and retain the result of the NSSAA procedure.

[0354] Alternatively, AMF140 may initiate this procedure based on a request from AAA-S181. For example, it is also possible that, based on the result of an already executed NSSAA procedure, AMF140 and / or NW manage a certain S-NSSAI as an NSSAI-allowed state, and AAA-S181 subsequently requests the execution of NSSAA for that S-NSSAI again, AMF may initiate this procedure based on a request from AAA-S181. In this case, this procedure can be considered an NSSAA procedure initiated by AAA-S.

[0355] The following describes this process. The AMF140 sends an EAP ID request message (S700) to UE_A10 via a 5G AN (or gNB or non-3GPP access). The EAP ID request message can be sent within an authentication request message that is a NAS message, or it can be an authentication request message that is a NAS message itself. It should be noted that the authentication request message that is a NAS message can be a 5GS network slice-specific authentication command (NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND) message. The AMF140 can include one or more S-NSSAIs corresponding to the EAP ID request message in the EAP ID request message or in an authentication request message that includes the EAP ID request message. Here, the S-NSSAI can be the HPLMN's S-NSSAI or a mapped S-NSSAI.

[0356] AMF140 requests one or more EAP IDs from UE_A10 based on the EAP ID request message as identification information for the UE used in performing NSSAA for one or more S-NSSAIs.

[0357] UE_A10 sends an EAP ID response message to AMF140 based on the receipt of an EAP ID request message and / or an S-NSSAI and / or an authentication request message (S702). The EAP ID response message can be sent as an authentication response message that is a NAS message, or it can be an authentication response message that is a NAS message. It should be noted that the authentication response message that is a NAS message can also be a 5GS network slice-specific authentication completion message. UE_A10 can include the S-NSSAI received from AMF140 in the EAP ID response message or in an authentication request message that includes the EAP ID response message. UE_A10 can also include the EAP ID, which serves as the UE's identification information corresponding to the S-NSSAI received from AMF140, in the EAP ID response message. It should be noted that UE_A10 can include multiple EAP IDs and multiple S-NSSAIs in the EAP ID response message, and each EAP ID and each S-NSSAI can be sent in an associated manner.

[0358] Based on the receipt of the EAP ID response message and / or EAP ID and / or authentication response message as a NAS message from UE_A10, AM140 sends an NSSAA authentication request message to AAA-S181 via AUSF180 (S704, S706). AM140F may send the EAP ID response message received from UE_A10 to AUSF180 and / or AAA-S181 in an NSSAA authentication request message, or it may send the EAP ID and / or S-NSSAI included in the EAP ID response message received from UE_A10 to AUSF180 and / or AAA-S181 in an NSSAA authentication request message.

[0359] It should be noted that the NSAAA authentication request message sent from AMF140 to AUSF180 and the NSAAA authentication request message sent from AUSF180 to AAA-S181 can be the same message or different messages. Specifically, AUSF180 can transmit the NSAAA authentication request message received from AMF140 to AAA-S181, or it can include the EAP ID and / or S-NSSAI included in the authentication request message received from AMF140 in the NSAAA authentication request message and send it to AAA-S181.

[0360] AAA-S181 may initiate the process of exchanging messages required for authentication between UE_A10 and AAA-S181 based on the receipt of an NSSAA authentication request message and / or at least one piece of information included in the NSSAA authentication request message (S708). It should be noted that the messages used in the message exchange process between AAA-S181 and UE_A10 may be EAP messages.

[0361] Next, AAA-S181 sends the NSAA authentication response message to AMF140 via AUSF180 as a response to the authentication request message received from AMF140 (S710, S712).

[0362] It should be noted that the NSAAA authentication response message sent from AAA-S181 to AUSF180 and the NSAAA authentication response message sent from AUSF180 to AMF140 can be the same message or different messages. Specifically, AUSF180 can transmit the NSAAA authentication response message received from AAA-S181 back to AAA-S181, or it can include the authentication result and / or S-NSSAI included in the authentication response message received from AAA-S181 in the NSAAA authentication response message and send it to AMF140.

[0363] The AUSF180 includes the authentication result and S-NSSAI in its NSSAA authentication response message. The authentication result can indicate success or failure. The S-NSSAI included in the NSSAA authentication response message can be the HPLMN's S-NSSAI or a mapped S-NSSAI.

[0364] Based on the receipt of the NSSAA authentication response message, the AMF140 sends an authentication result message (S714) to the UE_A10. The AMF140 may include the NSSAA authentication response message or the authentication result included in the NSSAA authentication response message, along with S-NSSAI, in the authentication result message.

[0365] The authentication result message can be a 5GS network slice-specific authentication result message, or it can be included in a network slice-specific authentication result message and sent.

[0366] Each device can complete this process based on the transmission and reception of authentication result messages. Each device can update the stored information based on the information transmitted and received during this process. Specifically, the AMF140 and / or NW can store the authentication result of each S-NSSAI based on the transmission and reception of authentication results. For example, if "success" is transmitted and received as an authentication result, the AMF140 and / or NW can establish an association with the S-NSSAI transmitted and received along with the authentication result, storing it as an NSAA "success" status as UE information. Similarly, if "failure" is transmitted and received as an authentication result, the AMF140 and / or NW can establish an association with the S-NSSAI transmitted and received along with the authentication result, storing it as an NSAA "failure" status as UE information.

[0367] Furthermore, in cases where this process begins based on the receipt of a login request message from UE_A10, the AMF140 can update the allowed NSSAI and / or rejected NSSAI for the UE based on the authentication result. Specifically, for example, if the authentication result is "successful," the AMF140 can include the S-NSSAI sent and received along with the authentication result in the allowed NSSAI, or store it as a mapped S-NSSAI of the S-NSSAI included in the allowed NSSAI, or it can store "allowed" in association with the received S-NSSAI. Similarly, if the authentication result is "failed," the AMF140 can store the S-NSSAI sent and received along with the authentication result as a third rejected NSSAI, or store it as a mapped S-NSSAI of the S-NSSAI included in the third rejected NSSAI, or it can store "rejected" in association with the received S-NSSAI. Furthermore, if the authentication result is "failure" or "success" of AMF transmission and reception, and the UE_A10 includes the S-NSSAI transmitted and received along with the authentication result in the pending NSSAI, or stores it as a mapped S-NSSAI of the S-NSSAI included in the pending NSSAI, the UE_A10 can delete the S-NSSAI from the pending NSSAI, or delete the S-NSSAI associated with the S-NSSAI from the pending NSSAI.

[0368] Furthermore, the UE can store the authentication result of each S-NSSAI based on the transmission and reception of authentication results. Specifically, for example, if the UE receives and receives "successfully" as the authentication result, it can associate the S-NSSAI transmitted and received along with the authentication result and store it as an NSSAA "successful" status as UE information. Similarly, if the UE receives and receives "failed" as the authentication result, it can associate the S-NSSAI transmitted and received along with the authentication result and store it as an NSSAA "failed" status as UE information.

[0369] Furthermore, each device can perform update processing based on the stored information based on the completion of this process. For example, the AFM can, based on the completion of this process, initiate a UE configuration update process or a non-login process initiated by the network if there are changes to the S-NSSAI included in the UE's allowed NSSAI and / or denied NSSAI. The AMF can use the UE configuration update process to notify the UE of the new allowed NSSAI and the new denied NSSAI. The AMF can also use a non-login process initiated by the network to notify the UE of the new denied NSSAI. [3.4. UE Setting Update Process]

[0370] Next, use Figure 8 The Generic UE configuration update procedure is described below. Hereinafter, the UE configuration update procedure will also be referred to as this procedure. This procedure is used by the core network to update the configuration information of the UE. This procedure can also be used for network-led mobility management of UEs logged into the network.

[0371] Furthermore, devices within the core network, such as the AMF, can initiate this process based on updates to network settings and / or operator policies. It should be noted that this process can be triggered by UE mobility detection, detection of changes in the UE and / or access network and / or core network state, or changes in network slice state. Moreover, this process can be triggered by receiving requests from the DN and / or the DN's application server, changes in network settings, or changes in operator policies. Furthermore, this process can also be triggered by the expiration of an ongoing timer. It should be noted that the triggering of this process for devices within the core network is not limited to these. In other words, this process can be executed at any time after the completion of the aforementioned login process and / or PDU session establishment process. Furthermore, if each device is in a state with an established 5GMM context and / or in a state of 5GMM connection mode, this process can be executed at any time.

[0372] Furthermore, each device can send and receive messages during this process, including identification information for changing UE settings and / or identification information for stopping or changing functions performed by the UE. Moreover, each device can update settings information as instructed by the network based on the completion of this process, or initiate actions as instructed by the network.

[0373] The UE can update its configuration information based on the control information sent and received through this process. Furthermore, the UE can stop an ongoing function or start a new function as its configuration information is updated. In other words, devices within the core network can lead this process, sending control messages and information to the UE to use this control information and enable the UE to update its recognizable configuration information. Moreover, devices within the core network can stop an ongoing function or start a new function by updating the UE's configuration information.

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

[0375] The AMF140 can include one or more of the NSSAIs (hereinafter, meaning Set NSSAI, Allow NSSAI, Deny NSSAI, Pending NSSAI, and First NSSAI) related to UE_A10 in the configuration update command message. It should be noted that the AMF can indicate new UE configuration information or request an update to the UE's configuration information by sending one or more of the NSSAIs. It should also be noted that information indicating support for each function and information indicating a request to use each function can be sent and received as the same identification information, or as different identification information.

[0376] Furthermore, the AMF140 can include a list of TAIs representing new login areas in the configuration update command message.

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

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

[0379] 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 policies and / or network status and / or user login information and / or the context maintained by AMF140, thereby indicating a request to update the configuration information of UE_A10.

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

[0381] Alternatively, if UE_A10 receives a TAI list, the received TAI list can be set to valid; if UE_A10 already stores a valid TAI list, the old TAI list can be deleted or invalidated. Hereinafter, the valid TAI list will be represented as the login area. It should be noted that if UE_A10 does not store a valid TAI list, and no TAI list is received from the core network during this process, the valid TAI list may be in an unstored state.

[0382] Furthermore, UE_A10 can appropriately store each received NSSAI. Specifically, upon receiving a setting NSSAI, UE_A10 can store the received setting NSSAI as "the setting NSSAI associated with the current PLMN". That is, UE_A10 can replace "the setting NSSAI associated with the current PLMN stored by UE_A10" with "the received setting NSSAI".

[0383] Furthermore, UE_A10 can delete the S-NSSAI mappings included in "the S-NSSAIs associated with the current PLMN stored by UE_A10" upon receiving the setting NSSAI. Moreover, if the "received setting NSSAIs" include one or more mappings S-NSSAIs, UE_A10 can store these one or more mappings S-NSSAIs.

[0384] Furthermore, UE_A10 can delete the "reject NSSAI stored in UE_A10 that is associated with the current PLMN" when it receives the NSSAI setting.

[0385] Alternatively, upon receiving the set NSSAI, UE_A10 may delete at least one of the following: "first rejection NSSAI stored by UE_A10 and associated with the current PLMN", "second rejection NSSAI stored by UE_A10 and associated with the current PLMN", and "third rejection NSSAI stored by UE_A10 and associated with the current PLMN".

[0386] Furthermore, upon receiving the set NSSAI, UE_A10 can delete "the first NSSAI stored by UE_A10" and / or "the first NSSAI stored by UE_A10 that is associated with the current PLMN" and / or one or more "the first NSSAI stored by UE_A10 that is associated with the current PLMN's EPLMN".

[0387] Furthermore, upon receiving a set NSSAI, UE_A10 can delete "pending NSSAI stored in UE_A10" and / or "pending NSSAI stored in UE_A10 that is associated with the current PLMN" and / or one or more "first pending NSSAI stored in UE_A10 that is associated with the current PLMN's EPLMN".

[0388] Furthermore, UE_A10 can, upon receiving a permitted NSSAI, store the received permitted NSSAI as "a permitted NSSAI associated with the current PLMN and the current access type". In other words, UE_A10 can replace the "permitted NSSAI associated with the current PLMN and the current access type" stored in UE_A10 with "the received permitted NSSAI".

[0389] Furthermore, when UE_A10 receives a TAI list and allowed NSSAIs from the new AMF141, and at least one TAI in the TAI list belongs to an EPLMN, UE_A10 can store the received allowed NSSAIs as "allowed NSSAIs associated with the EPLMN to which the TAIs in the TAI list belong and the current access type." It should be noted that when storing allowed NSSAIs, UE_A10 can store them in association with the login area, or it can store the S-NSSAIs included in the allowed NSSAIs in association with the login area.

[0390] Furthermore, UE_A10 can delete the mapping S-NSSAI included in either "based on received deleted allowed NSSAI" or "based on received updated old allowed NSSAI" upon receiving an allowed NSSAI. Moreover, if UE_A10 includes the mapping S-NSSAI in "received allowed NSSAI", UE_A10 can store one or more of those mappings.

[0391] In cases where an S-NSSAI included in the old allowed NSSAI is included in the pending NSSAI and is received by UE_A10, the mapped S-NSSAI of that S-NSSAI may not be deleted.

[0392] If UE_A10 receives an MM message that includes both NSSAI enabled and NSSAI pending, UE_A10 can perform control of receiving based on NSSAI pending before performing receiving based on NSSAI enabled.

[0393] Specifically, if the old allowed NSSAIs stored in UE_A10 include S-NSSAI#1, and UE_A10 receives from the network a pending NSSAI including S-NSSAI#1 and a new allowed NSSAI excluding S-NSSAI#1, UE_A10 may perform an update of the received stored NSSAIs based on the pending NSSAIs before performing an update of the received stored NSSAIs based on the allowed NSSAIs.

[0394] Similarly, when UE_A10 receives an MM message that includes both allowing NSSAI and denying NSSAI, UE_A10 can perform control based on denying NSSAI before performing control based on allowing NSSAI.

[0395] Specifically, if the old allowed NSSAIs stored in UE_A10 include S-NSSAI#1, and UE_A10 receives from the network a rejected NSSAI including S-NSSAI#2, which is a mapped S-NSSAI as S-NSSAI#1, and a new allowed NSSAI that does not include S-NSSAI#1, UE_A10 may perform an update of the stored NSSAIs received based on the rejected NSSAIs before performing an update of the stored NSSAIs received based on the allowed NSSAIs.

[0396] Furthermore, UE_A10 can delete the S-NSSAI that is "stored in UE_A10 and associated with the current PLMN and is denied NSSAI" if it receives an NSSAI permission.

[0397] Specifically, UE_A10 may, upon receiving an allowed NSSAI, delete the S-NSSAI included in the received allowed NSSAI and / or the mapped S-NSSAI of the received allowed NSSAI from at least one of "first denied NSSAI stored by UE_A10 and associated with the current PLMN", "second denied NSSAI stored by UE_A10 and associated with the current PLMN", "second denied NSSAI stored by UE_A10 and associated with the current PLMN and the current login area", and "third denied NSSAI stored by UE_A10 and associated with the current PLMN". Alternatively, it may delete the S-NSSAI included in the received allowed NSSAI and / or the mapped S-NSSAI of the received allowed NSSAI from all NSSAIs.

[0398] Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from the "Pending NSSAIs stored by UE_A10 that are associated with the current PLMN". Also, upon receiving an allowed NSSAI, UE_A10 can remove the mapped S-NSSAI or S-NSSAI included in the received allowed NSSAI from the "Pending NSSAIs stored by UE_A10 that are associated with all PLMNs". Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from the "Pending NSSAIs stored by UE_A10 that are associated with EPLMNs".

[0399] In a roaming scenario, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN, UE_A10 can, upon receiving an allowed NSSAI, delete the mapped S-NSSAI of the newly received allowed NSSAI from the "pending NSSAI stored in UE_A10". At this time, in the roaming scenario, the allowed NSSAI is associated with the current PLMN or the current SNPN, i.e., the PLMN ID or SNPN ID representing the RPLMN or RSNPN. On the other hand, the S-NSSAI included in the pending NSSAI can be the S-NSSAI of the HPLMN.

[0400] Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with the current PLMN stored by UE_A10". Alternatively, upon receiving an allowed NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with all PLMNs stored by UE_A10".

[0401] Furthermore, upon receiving a rejection NSSAI, UE_A10 can store the rejection reason value associated with the S-NSSAI included in the received rejection NSSAI as an appropriate rejection NSSAI. In other words, UE_A10 can append "the S-NSSAI included in the received rejection NSSAI" to the rejection NSSAI stored in UE_A10.

[0402] Specifically, when UE_A10 receives the rejection reason value "S-NSSAI is not available in the current PLMN or SNPN" and the 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.

[0403] Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI is not available in the current login area" and the 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 and the current login area".

[0404] Specifically, when UE_A10 receives the rejection reason value "S-NSSAI is 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. At this time, the "third rejection NSSAI" can be associated with the current PLMN or it can be applicable to all PLMNs.

[0405] It should be noted that when UE_A10 receives a TAI list along with the NSSAI rejection, the current login region is represented by the received TAI list. On the other hand, when UE_A10 does not receive a TAI list along with the NSSAI rejection, the current login region is represented by the TAI list previously received and stored by UE_A10.

[0406] Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI unavailable due to NSSAA failure or cancellation" and a rejection NSSAI including the 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 if the UE stores the third rejection NSSAI associated with the current PLMN, the received S-NSSAI may be appended and / or stored in the third rejection NSSAI associated with the current PLMN.

[0407] Furthermore, if a rejected NSSAI is received, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from "Allowed NSSAIs stored in UE_A10 and associated with the current PLMN".

[0408] Here, if UE_A10 receives a rejected NSSAI that includes an S-NSSAI associated with the HPLMN, and if the mapped S-NSSAI included in "Allowed NSSAIs associated with the current PLMN stored by UE_A10" is included in the rejected NSSAI received by UE_A10, UE_A10 can delete the S-NSSAI from "Allowed NSSAIs associated with the current PLMN stored by UE_A10".

[0409] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "Pending NSSAIs Associated with the Current PLMN stored in UE_A10". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with All PLMNs stored in UE_A10". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with EPLMN stored in UE_A10".

[0410] Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with the current PLMN stored by UE_A10". Alternatively, upon receiving an allowed NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with all PLMNs stored by UE_A10".

[0411] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "Pending NSSAIs Associated with the Current PLMN stored in UE_A10". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with All PLMNs stored in UE_A10". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with EPLMN stored in UE_A10".

[0412] It should be noted that during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the HPLMN, the pending NSSAI stored by the UE is the S-NSSAI of the current PLMN (i.e., the VPLMN), the UE_A10 receives a rejected NSSAI, or the mapped S-NSSAI of a certain S-NSSAI included in "pending NSSAIs stored by UE_A10 that are associated with the current PLMN" is included in the rejected NSSAI, then the S-NSSAI can be deleted from "pending NSSAIs stored by UE_A10 that are associated with the current PLMN".

[0413] Alternatively, during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the HPLMMN, and the pending NSSAI stored by the UE is also the S-NSSAI of the HPLMMN, the UE_A10 may, upon receiving a rejected NSSAI, delete the S-NSSAI included in the received rejected NSSAI from the "pending NSSAIs stored by UE_A10 that are associated with the current PLMN".

[0414] Alternatively, during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the current PLMN (i.e., the VPLMN), and the pending NSSAI stored by the UE is the S-NSSAI of the HPLMN, or if UE_A10 receives a rejected NSSAI, or if an S-NSSAI included in the pending NSSAIs stored by UE_A10 is a mapped S-NSSAI of the rejected NSSAI or a mapped S-NSSAI of an S-NSSAI included in a rejected NSSAI, then that S-NSSAI can be deleted from the pending NSSAIs stored by UE_A10. Furthermore, upon receiving a rejected NSSAI, UE_A10 can delete the S-NSSAI included in the received rejected NSSAI from the first NSSAI associated with the current PLMN stored by UE_A10. Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "first NSSAIs associated with all PLMNs stored by UE_A10". Also, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "first NSSAIs associated with EPLMNs stored by UE_A10".

[0415] Furthermore, upon receiving a pending NSSAI, UE_A10 can replace the pending NSSAI stored in UE_A10 with a new pending NSSAI. Specifically, upon receiving a pending NSSAI included in the login acceptance message during the login process for the current PLMN or SNPN, UE_A10 can replace the pending NSSAI associated with the current PLMN or SNPN stored in UE_A10 with a new pending NSSAI.

[0416] Alternatively, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN, or if the pending NSSAI included in the login acceptance message during the login process for the current PLMN or SNPN received by UE_A10, the pending NSSAI stored in UE_A10 can be replaced with a new pending NSSAI.

[0417] Furthermore, when UE_A10 stores the mapping S-NSSAI of pending NSSAI, UE_A10 can delete the mapping S-NSSAI of pending NSSAI, store the mapping S-NSSAI of new pending NSSAI, and perform processing on both sides.

[0418] It should be noted that the pending NSSAI mapping S-NSSAI can be stored based on the old NSSAI-enabled mapping S-NSSAI.

[0419] It should be noted that the processes performed by UE_A10 based on the receipt of each identification information, as described above, can be executed during this process or after the completion of this process, or they can be executed after the completion of this process. Moreover, the UE can send a configuration update complete message to AMF140 via 5G AN (gNB) as a response message to the configuration update command message (S802) based on the identification information included in the configuration update command message.

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

[0421] Furthermore, each device can perform processing based on the information sent and received during this process upon completion of this process. For example, when sending and receiving update information regarding setting information, each device can update the setting information. Moreover, when sending and receiving information indicating that a login process needs to be performed, UE_A10 can start the login process upon completion of this process.

[0422] Furthermore, UE_A10 can store the identification information received along with the configuration information command message based on the completion of this process, and can also identify the network. In addition, the UE can execute various procedures based on the stored information based on the completion of this process.

[0423] In the above process, the devices in the core network can instruct the UE to update the settings information that the UE has applied by sending and receiving settings update command messages, and can instruct the UE to stop or change the functions being performed. [3.5. Non-login process starting from the network]

[0424] Next, use Figure 9 The network-initiated de-registration procedure is described below. This procedure refers to the network-initiated de-registration process. The network-initiated de-registration procedure is used to manually de-register a UE to access network A and / or core network A, access network B and / or core network B and / or DN and / or PDN. This procedure can also be used for network-led mobility management of a UE that has logged into the network.

[0425] If the UE is in a network-registered state (RM-REGISTERED state or 5GMM-REGISTEDED state), the AMF can execute this procedure at any time. For example, the AMF can start this procedure as the UE's registration information is updated. Specifically, the AMF can start this procedure based on the completion of the NSSAA procedure, even if the UE's registration information does not allow NSSAI. In other words, the AMF can start this procedure even if there is no S-NSSAI allowed by the UE and no future plans to add S-NSSAI permission through other procedures (such as the NSSAA procedure).

[0426] First, the AMF140 can initiate this procedure by sending a De-registration request message to UE_A10 (S900). Here, the De-registration request message is a NAS message transmitted and received on the N1 interface, but it is included in the RRC message transmission and reception between the UE and the 5GAN (gNB).

[0427] AMF140 may include at least one identification information from each NSSAI (hereinafter, meaning rejected NSSAI, pending NSSAI, and first NSSAI) in the non-login request message. AMF may further include a reason value and / or information indicating the access type to be de-logged in the non-login request message and send it. Here, the reason value may be a 5GMM cause. Furthermore, if this process begins based on the result of the NSSAA process or upon completion of the NSSAA, the reason value may be a value indicating that no network slices are available. In this case, it may be the 5GS 5GMM reason value #62 "No network slices available".

[0428] It should be noted that the AMF140 can send these identification information and / or non-login messages to indicate that the network does not support certain functions, to request a transition to a non-login state, to notify the AMF140 of changes, to continue instructing the start of the login process, and to indicate a combination of these information. Furthermore, when sending and receiving multiple identification information, two or more of these identification information can constitute one or more identification information. It should also be noted that information indicating support for certain functions and information indicating a request to use certain functions can be sent and received as the same identification information, or as different identification information.

[0429] UE_A10 can identify and store the rejection of S-NSSAI and the reason for rejection, and determine the UE's action, based on the reception and / or reason value of at least one of the NSSAIs and / or the reception of other identification information and / or the UE's state.

[0430] Furthermore, upon receiving a rejection NSSAI, UE_A10 can store the rejection reason value associated with the S-NSSAI included in the received rejection NSSAI as an appropriate rejection NSSAI. In other words, UE_A10 can append "the S-NSSAI included in the received rejection NSSAI" to the rejection NSSAI stored in UE_A10.

[0431] Specifically, when UE_A10 receives the rejection reason value "S-NSSAI is not available in the current PLMN or SNPN" and the 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.

[0432] Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI is not available in the current login area" and the 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 and the current login area".

[0433] Specifically, when UE_A10 receives the rejection reason value "S-NSSAI is 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. At this time, the "third rejection NSSAI" can be associated with the current PLMN or it can be applicable to all PLMNs.

[0434] It should be noted that when UE_A10 receives a TAI list along with the NSSAI rejection, the current login region is represented by the received TAI list. On the other hand, when UE_A10 does not receive a TAI list along with the NSSAI rejection, the current login region is represented by the TAI list previously received and stored by UE_A10.

[0435] Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI unavailable due to NSSAA failure or cancellation" and a rejection NSSAI including the 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 if the UE stores the third rejection NSSAI associated with the current PLMN, the received S-NSSAI may be appended and / or stored in the third rejection NSSAI associated with the current PLMN.

[0436] Furthermore, if a rejected NSSAI is received, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from "Allowed NSSAIs stored in UE_A10 and associated with the current PLMN".

[0437] Here, if UE_A10 receives a rejected NSSAI that includes an S-NSSAI associated with the HPLMN, and if the mapped S-NSSAI included in "Allowed NSSAIs associated with the current PLMN stored by UE_A10" is included in the rejected NSSAI received by UE_A10, UE_A10 can delete the S-NSSAI from "Allowed NSSAIs associated with the current PLMN stored by UE_A10".

[0438] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "Pending NSSAIs Associated with the Current PLMN stored in UE_A10". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with All PLMNs stored in UE_A10". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with EPLMN stored in UE_A10".

[0439] Furthermore, upon receiving an allowed NSSAI, UE_A10 can remove the S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with the current PLMN stored by UE_A10". Alternatively, upon receiving an allowed NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI associated with all PLMNs stored by UE_A10".

[0440] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "Pending NSSAIs Associated with the Current PLMN stored in UE_A10". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with All PLMNs stored in UE_A10". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "Pending NSSAIs Associated with EPLMN stored in UE_A10".

[0441] It should be noted that during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the HPLMN, the pending NSSAI stored by the UE is the S-NSSAI of the current PLMN (i.e., the VPLMN), the UE_A10 receives a rejected NSSAI, or the mapped S-NSSAI of a certain S-NSSAI included in "pending NSSAIs stored by UE_A10 that are associated with the current PLMN" is included in the rejected NSSAI, then the S-NSSAI can be deleted from "pending NSSAIs stored by UE_A10 that are associated with the current PLMN".

[0442] Alternatively, during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the HPLMMN, and the pending NSSAI stored by the UE is also the S-NSSAI of the HPLMMN, the UE_A10 may, upon receiving a rejected NSSAI, delete the S-NSSAI included in the received rejected NSSAI from the "pending NSSAIs stored by UE_A10 that are associated with the current PLMN".

[0443] Alternatively, during roaming, if the S-NSSAI included in the rejected NSSAI (any of the first to third rejected NSSAIs) is the S-NSSAI of the current PLMN (i.e., the VPLMN), the pending NSSAI stored by the UE is the S-NSSAI of the HPLMN, the UE_A10 receives a rejected NSSAI, or if an S-NSSAI included in the pending NSSAIs stored by the UE_A10 is a mapped S-NSSAI of the rejected NSSAI or a mapped S-NSSAI of the rejected NSSAI, the S-NSSAI can be deleted from the pending NSSAIs stored by the UE_A10.

[0444] Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received rejected NSSAI from the "First NSSAIs stored by UE_A10 that are associated with the current PLMN". Also, upon receiving a rejected NSSAI, UE_A10 can remove the mapped S-NSSA or S-NSSAI included in the received permitted NSSAI from the "First NSSAIs stored by UE_A10 that are associated with all PLMNs". Furthermore, upon receiving a rejected NSSAI, UE_A10 can remove the S-NSSAI included in the received permitted NSSAI from the "First NSSAIs stored by UE_A10 that are associated with EPLMNs".

[0445] Furthermore, upon receiving a pending NSSAI, UE_A10 can replace the pending NSSAI stored in UE_A10 with a new pending NSSAI. Specifically, upon receiving a pending NSSAI included in the login acceptance message during the login process for the current PLMN or SNPN, UE_A10 can replace the pending NSSAI associated with the current PLMN or SNPN stored in UE_A10 with a new pending NSSAI.

[0446] Alternatively, if the S-NSSAI included in the pending NSSAI is the S-NSSAI of the HPLMN, or if the pending NSSAI included in the login acceptance message during the login process for the current PLMN or SNPN received by UE_A10, the pending NSSAI stored in UE_A10 can be replaced with a new pending NSSAI.

[0447] Furthermore, when UE_A10 stores the mapping S-NSSAI of pending NSSAI, UE_A10 can delete the mapping S-NSSAI of pending NSSAI, store the mapping S-NSSAI of new pending NSSAI, and perform processing on both sides.

[0448] It should be noted that the pending NSSAI mapping S-NSSAI can be stored based on the old NSSAI-enabled mapping S-NSSAI.

[0449] It should be noted that the processes performed by UE_A10 based on the reception of each identification information, as described above, can be performed during this process or after the completion of this process, or they can be performed after the completion of this process based on the completion of this process.

[0450] UE_A10 receives non-login request messages via 5G AN (gNB). UE_A10 can identify the various identification information included in the non-login request message by receiving it.

[0451] Upon receiving a non-login request message, UE_A10 can send a non-login acceptance message to AMF140 via the 5G AN (or gNB). It should be noted that the non-login acceptance message is a NAS message transmitted and received on the N1 interface. Furthermore, RRC messages can be control messages transmitted and received between the UE and the 5G AN (or gNB).

[0452] Each device can transition to the state where the UE is not logged into the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of login acceptance messages. Furthermore, the transitions of each device to each state can be based on the completion of this process.

[0453] Furthermore, each device can perform processing based on the information sent and received during this process based on the completion of the non-login process. For example, UE_A10 can start the login process based on the completion of the non-login process. [4. Embodiments of the present invention]

[0454] Implementations of this invention can be a combination of one or more processes described in the three sections. For example, in this embodiment, after the initial login process described in the three sections is completed, an NSSAA process can be implemented to perform a UE configuration update process. Furthermore, each device (UE and core network devices) can perform one or more mobile and periodic login processes based on the completion of the initial login process. Alternatively, after the initial login process described in the three sections is completed, an NSSAA process can be implemented to perform a non-login process initiated by the network.

[0455] The following describes an example of a specific embodiment of the present invention. It should be noted that the various devices can combine the operations of the multiple embodiments described below to implement the invention.

[0456] Specifically, the actions of each device when allowing NSSAI transmission and reception can be based on the first embodiment, and the actions when rejecting NSSAI transmission and reception can be based on the second embodiment. Alternatively, the actions of each device when allowing NSSAI transmission and reception can be based on the first embodiment, and the actions when rejecting NSSAI transmission and reception can be based on the third embodiment.

[0457] Alternatively, the actions of each device when allowing NSSAI transmission and reception can be based on the second embodiment, and the actions when rejecting NSSAI transmission and reception can be based on the first embodiment. The actions of each device when allowing NSSAI transmission and reception can be based on the second embodiment, and the actions when rejecting NSSAI transmission and reception can be based on the third embodiment.

[0458] Alternatively, the actions of each device when allowing NSSAI transmission and reception can be based on the third embodiment, and the actions when rejecting NSSAI transmission and reception can be based on the first embodiment. The actions of each device when allowing NSSAI transmission and reception can be based on the third embodiment, and the actions when rejecting NSSAI transmission and reception can be based on the second embodiment. [4.1. First Implementation Method]

[0459] The first embodiment (hereinafter, this embodiment) will be described below. In this embodiment, an example of the operation of each device in the case where, during roaming, the S-NSSAI included in the third rejected NSSAI is the S-NSSAI of the HPLMN, the pending NSSAI is the S-NSSAI of the current PLMN (RPLMN and VPLMN), and the UE manages and / or stores the mapped S-NSSAI of the pending NSSAI will be described.

[0460] Specifically, this section explains the situation where a UE receives a third rejection NSSAI from the network while the UE is in the state of stored pending NSSAI.

[0461] First, during the initial login process for the VPLMN, the UE sends the login request message containing S-NSSAI#1, which represents the VPLMN's S-NSSAI, to the VPLMN, thus initiating the login process. At this point, the UE may also include the mapping S-NSSAI#2 of S-NSSAI#1 in the login request message.

[0462] Next, the UE receives a pending NSSAI including S-NSSAI#1 from the VPLMN. The UE stores S-NSSAI#1 included in the pending NSSAI. At this time, the UE does not delete S-NSSAI#2, which is the mapped S-NSSAI of S-NSSAI#1, from storage, nor does it store S-NSSAI#2, which is the mapped S-NSSAI of S-NSSAI#1.

[0463] Next, the UE receives an MM message from the VPLMN that includes a third rejection NSSAI containing S-NSSAI#2. Based on the receipt of the third rejection NSSAI, the UE stores S-NSSAI#2 as part of the third rejection NSSAI.

[0464] Furthermore, the UE can remove S-NSSAI#1 from the pending NSSAI if S-NSSAI#1 of the VPLMN mapped to S-NSSAI#2 is included in the pending NSSAI.

[0465] It should be noted that when S-NSSAI#1 is mapped to S-NSSAI#2, that is, when multiple HPLMNs' S-NSSAIs are mapped to S-NSSAI#1, the UE can still receive S-NSSAI#2 without deleting S-NSSAI#1 from the pending NSSAIs.

[0466] The UE can remove S-NSSAI#1 from the pending NSSAI if all of the mapped S-NSSAIs in the third rejected NSSAI are included in the reception.

[0467] If the UE stores a third rejection NSSAI, it can control the MM procedure by preventing the use of the S-NSSAI included in the third rejection NSSAI.

[0468] Based on the above, in this embodiment, based on the rejection of NSSAI of S-NSSAI constituting HPLMN, the pending NSSAI of S-NSSAI of the current PLMN stored by the UE can be updated.

[0469] It should be noted that the first login process can be the login process described in Chapter 3. Furthermore, the process by which the UE receives the third rejection NSSAI can be a login process, a UE settings change process, or a non-login process initiated by the network.

[0470] Furthermore, in this embodiment, the UE receives a third rejection NSSAI, but alternatively, even if the UE receives a first rejection NSSAI or a second rejection NSSAI including an S-NSSAI of HPLMN, each device can perform the same action. [4.2. Second Implementation]

[0471] The second embodiment (hereinafter, this embodiment) will be described below. In this embodiment, an example of the operation of each device will be described in the case where, during roaming, the S-NSSAI included in the first rejected NSSAI is the S-NSSAI of the current PLMN (RPLMN and VPLMN), and the pending NSSAI is also the S-NSSAI of the HPLMMN.

[0472] Specifically, this section explains the situation where the UE receives a first rejection NSSAI from the network while the UE is in the state of stored pending NSSAI.

[0473] First, during the initial login process for the VPLMN, the UE sends the login request message containing S-NSSAI#1, which represents the VPLMN's S-NSSAI, to the VPLMN, thus initiating the login process. At this point, the UE may also include the mapping S-NSSAI#2 of S-NSSAI#1 in the login request message.

[0474] Next, the UE receives the pending NSSAI, which includes S-NSSAI#2, from the VPLMN. The UE stores S-NSSAI#2 second, which is included in the pending NSSAI, in the pending NSSAI.

[0475] Next, the UE receives an MM message from the VPLMN that includes a first rejection NSSAI containing S-NSSAI#1. Based on the receipt of the first rejection NSSAI, the UE stores S-NSSAI#1 in a third rejection NSSAI.

[0476] Furthermore, the UE can remove S-NSSAI#2 from the pending NSSAI if S-NSSAI#2, which is the mapping S-NSSAI of S-NSSAI#1, is included in the pending NSSAI.

[0477] It should be noted that when S-NSSAI#1 is mapped to more than just S-NSSAI#2, that is, when multiple HPLMNs' S-NSSAIs are mapped to S-NSSAI#1, the UE can remove multiple S-NSSAIs from the pending NSSAIs based on the reception of S-NSSAI#1.

[0478] Specifically, for example, if S-NSSAI#2 and S-NSSAI#3 of HPLMN are stored in the pending NSSAI, and S-NSSAI#2 and S-NSSAI#3 are mapped to S-NSSAI#1 of VPLMN, the UE can remove S-NSSAI#2 and S-NSSAI#3 from the pending NSSAI based on the acceptance of the rejected NSSAI including S-NSSAI#1.

[0479] The UE can control the MM process of S-NSSAI included in the first rejection NSSAI to prevent it from starting.

[0480] Based on the above, in this embodiment, the pending NSSAI of the S-NSSAI of the HPLMN that constitutes the current PLMN can be updated based on the rejection of NSSAI reception of the S-NSSAI.

[0481] It should be noted that the first login process can be the login process described in Chapter 3. Furthermore, the process by which the UE receives the third rejection NSSAI can be a login process, a UE settings change process, or a non-login process initiated by the network.

[0482] Furthermore, in this embodiment, the UE receives the first rejection NSSAI, but alternatively, even if the UE receives the second or third rejection NSSAI including the S-NSSAI of the VPLMN, each device can perform the same action. [4.3. Third Implementation]

[0483] The third embodiment (hereinafter, this embodiment) will be described below. In this embodiment, an example of the operation of each device that manages and / or stores the mapped S-NSSAI of the NSSAI that is allowed during roaming, where the S-NSSAI included in the third denied NSSAI is the S-NSSAI of the HPLMN, the NSSAI that is allowed is the S-NSSAI of the current PLMN (RPLMN and VPLMN), and the NSSAI that is allowed is the mapping S-NSSAI of the UE.

[0484] Specifically, this section explains the situation where a UE receives a third rejection NSSAI from a VPLMN while the UE is in a state where NSSAI is allowed and an association has been established between the VPLMN of the storage and roaming destination.

[0485] First, during the initial login process for the VPLMN, the UE sends the login request message containing S-NSSAI#1, which represents the VPLMN's S-NSSAI, to the VPLMN, thus initiating the login process. At this point, the UE may also include the mapping S-NSSAI#2 of S-NSSAI#1 in the login request message.

[0486] At this time, S-NSSAI#1 is included in the NSSAI allowed or NSSAI set associated with VPLMN and stored in the UE.

[0487] Next, the UE receives the allowed NSSAI including S-NSSAI#1 from the VPLMN. The UE stores S-NSSAI#1 included in the allowed NSSAI. At this time, the UE does not delete S-NSSAI#2, which is the mapped S-NSSAI of S-NSSAI#1, from storage, nor does it store S-NSSAI#2, which is the mapped S-NSSAI of S-NSSAI#1.

[0488] Next, the UE receives an MM message from the VPLMN that includes a third rejection NSSAI containing S-NSSAI#2. Based on the receipt of the third rejection NSSAI, the UE stores S-NSSAI#2 as part of the third rejection NSSAI.

[0489] Furthermore, the UE can remove S-NSSAI#1 from the allowed NSSAI if S-NSSAI#1 of the VPLMN mapped to S-NSSAI#2 is included in the allowed NSSAI.

[0490] It should be noted that if S-NSSAI#1 is mapped to S-NSSAI#2, that is, if multiple HPLMNs' S-NSSAIs are mapped to S-NSSAI#1, the UE can still receive S-NSSAI#2 without deleting S-NSSAI#1 from the allowed NSSAIs.

[0491] The UE can remove S-NSSAI#1 from the allowed NSSAI if all S-NSSAI mappings in the third rejected NSSAI are included in the reception.

[0492] Alternatively, even if the mapping S-NSSAI#1 is not just S-NSSAI#2, the UE can remove S-NSSAI#1 from the allowed NSSAI based on the reception of S-NSSAI#2.

[0493] The UE can control the MM process of S-NSSAI included in the third rejection NSSAI by preventing it from starting.

[0494] Based on the above, in this embodiment, based on the rejection of NSSAI in the S-NSSAI constituting the HPLMMN, the storage information of the allowed NSSAI and the mapping S-NSSAI of the current PLMN stored by the UE can be updated.

[0495] It should be noted that the first login process can be the login process described in Chapter 3. Furthermore, the process by which the UE receives the third rejection NSSAI can be a login process, a UE settings change process, or a non-login process initiated by the network.

[0496] Furthermore, in this embodiment, the UE receives a third rejection NSSAI, but alternatively, even if the UE receives a first rejection NSSAI or a second rejection NSSAI including an S-NSSAI of HPLMN, each device can perform the same behavior. [5. Improved Example]

[0497] The program operating in the apparatus of one embodiment of the present invention can be a program that controls a central processing unit (CPU) or similar device to enable the computer to perform its functions in a manner that implements the functions of an embodiment of the present invention. The program or the information processed by the program is temporarily stored in volatile memory such as random access memory (RAM) or non-volatile memory such as flash memory, hard disk drive (HDD), or other storage device systems.

[0498] It should be noted that programs used to implement the functions of the embodiments involved in this invention can also be recorded in a computer-readable recording medium. This can be achieved by reading the program recorded in the recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into a device, including hardware such as an operating system and peripherals. Furthermore, the "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium for short-term dynamic storage of programs, or other computer-readable recording media.

[0499] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be installed or executed by electronic circuits such as integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware components, or combinations thereof. General-purpose processors may be microprocessors, or processors, controllers, microcontrollers, or state machines of conventional types. The aforementioned electronic circuits may be constructed from digital circuits or analog circuits. Furthermore, in cases where advancements in semiconductor technology have led to the emergence of integrated circuit technologies that replace current integrated circuits, one or more embodiments of the present invention may also utilize new integrated circuits based on such technologies.

[0500] It should be noted that the present invention is not limited to the embodiments described above. While one example of the device is described in the embodiments, the present invention is not limited to this 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, and other household appliances, etc.

[0501] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the technical solutions shown, and embodiments obtained by appropriately combining technical solutions disclosed in different embodiments are also included within the technical scope of the present invention. In addition, it also includes configurations obtained by replacing elements that have the same effect as those described in the above embodiments with each other.

Claims

1. A user equipment (UE), characterized in that, have: Receiving and dispatching department, control department, and storage department. When the transceiver receives the Network Slice Selection Assistance Information (NSSAI), it indicates that the transceiver unit has received the information. The control unit removes the S-NSSAI contained in the allowed NSSAI from the rejected NSSAI for the current PLMN stored in the storage unit, which includes single network slice selection assistance information S-NSSAI that is not available in the current Public Land Mobile Network (PLMN). The control unit deletes the mapping S-NSSAI that allows NSSAI from the storage unit, which includes S-NSSAIs sent along with rejection reasons due to failure or cancellation of network slice-specific authentication and authorization NSSAA.

2. The UE according to claim 1, characterized in that, The UE is in roaming mode.

3. A communication control method executed by a user equipment (UE), characterized in that, The communication control method, upon receiving the Network Slice Selection Assistance Information (NSSAI), Remove the S-NSSAI contained in the Allow NSSAI from the UE's stored Denied NSSAI for the current PLMN, which includes Single Network Slice Selection Assistance Information (S-NSSAI) that is not available in the current Public Land Mobile Network (PLMN). Remove the mapping S-NSSAI that allows NSSAI from the UE's stored data, including S-NSSAIs sent along with rejection reasons due to network slice-specific authentication and authorization NSSAA failure or cancellation, and the rejection NSSAIs due to NSSAA failure or cancellation.

4. The communication control method according to claim 3, characterized in that, The UE is in roaming mode.

Images