UE (User Equipment) and AMF (Access and Mobility Management Function)

Abstract

Provided is a communication means for realizing a function relating to management of information for providing, to a UE, a network slicing service corresponding to an area, in 5GS. Provided are a communication means and a method for initial registration and periodic or movement-based registration updating procedures, for the purpose of realizing management of information relating to a UE and a service area for each network slice, in 5GS. Additionally provided are a communication means and a method for: network slice-specific authentication / approval procedures after completion of registration procedures; UE setting updating procedures; and non-registration procedures.

Description

[Technical field]

[0001] One aspect of the present invention relates to a User Equipment (UE), a core network device, an Access and Mobility Management Function (AMF), and a Session Management Function (SMF). This application claims priority to Japanese Patent Application No. 2020-093907 filed in Japan on May 29, 2020, the contents of which are incorporated herein by reference. [Background technology]

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

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

[0004] [Non-Patent Document 1] 3GPP TS 23.501 V16.4.0 (2020-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16) [Non-Patent Document 2] 3GPP TS 23.502 V16.4.0 (2020-03); 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.501 V16.4.1 (2020-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) [Non-Patent Document 4] 3GPP TR 23.700-40 V0.3.0 (2020-01);3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of network slicing; Phase 2 (Release 17) [Non-Patent Document 5] GSM Association Official Document NG.116 - Generic Network Slice Template Version 2.0 16 October 2019 Summary of the Invention [Problem to be solved by the invention]

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

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

[0007] 3GPP is also studying Enhancement of Network Slicing (eNS) to consider further functions related to network slicing. In Phase 2 of eNS, 3GPP is considering adding a function to define a service area (area of ​​service) accessible by UE for each network slice and provide a service to the UE according to the area (see Non-Patent Documents 4 and 5).

[0008] However, the method for satisfying the above requirements is not clear.

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

[0010] According to one embodiment of the present invention, a UE (User Equipment) having a control unit and a transceiver unit is characterized in that the transceiver unit receives a control message including first identification information from a control device, and if the control message is a registration acceptance message or a configuration update command, the first identification information is Allowed NSSAI (Network Slice Selection Assistance Information) or Rejected NSSAI, and if the control message is a registration rejection message or a non-registration request message, the first identification information is Rejected NSSAI, and the first identification information includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information, and the control unit stores the S-NSSAI and the area information in correspondence with each other based on the reception of the first identification information, and if the first identification information is Rejected NSSAI, the S-NSSAI includes a reason value, and the reason value indicates that the UE is not in a location where it can connect to the S-NSSAI, and based on the reception of the first identification information, further recognizes that the S-NSSAI is unavailable in the area to which it is connected.

[0011] In one embodiment of the present invention, a core network device comprises a control unit and a transceiver unit, wherein the transceiver unit receives a registration request message from a UE (User Equipment), the registration request message including UE capability information, and transmits a registration acceptance message including first identification information to the UE, the first identification information being an Allowed NSSAI (Network Slice Selection Assistance Information), a Rejected NSSAI, or a Pending NSSAI, the first identification information including an S-NSSAI (Single Network Slice Selection Assistance Information), and if the UE capability information indicates that the UE supports an area of ​​service, the first identification information further includes area information associated with the S-NSSAI.

[0012] In one embodiment of the present invention, a UE (User Equipment) comprises a control unit and a transceiver unit, wherein the transceiver unit receives a control message from a control device, the control message including a first identification information and network capability information, and when the network capability information indicates that the network supports an area of ​​service, the first identification information includes an S-NSSAI (Single Network Slice Selection Assistance Information) and area information, and the control unit corresponds and stores the S-NSSAI and the area information based on the reception of the first identification information.

[0013] In one embodiment of the present invention, a UE (User Equipment) comprises a memory unit, a control unit, and a transceiver unit, wherein the memory unit stores S-NSSAI (Single Network Slice Selection Assistance Information) in association with area information, the control unit establishes a PDU (Protocol Data Unit) session associated with the S-NSSAI, and when the UE moves from within an area indicated by the area information to outside the area indicated by the area information, the transceiver unit performs a PDU session release procedure to release the PDU session, and the control unit deletes the S-NSSAI from an allowed NSSAI and stores it in a rejected NSSAI, and configures the transceiver unit so that initiation of a PDU session establishment procedure and a PDU session modification procedure using the S-NSSAI is prohibited.

[0014] One embodiment of the present invention relates to a UE (User Equipment) that includes a memory unit, a control unit, and a transceiver unit, and the memory unit stores S-NSSAI (Single Network Slice Selection Assistance Information) in association with area information, and when the UE moves from outside the area indicated by the area information to within the area indicated by the area information, the control unit deletes the S-NSSAI from rejected NSSAI (Network Slice Selection Assistance Information) and stores the S-NSSAI in an allowed NSSAI, and configures the transceiver unit so that start of a PDU session establishment procedure and a PDU session modification procedure using the S-NSSAI is permitted.

[0015] According to one embodiment of the present invention, a UE (User Equipment) comprises a control unit and a transceiver unit, wherein the transceiver unit receives a registration acceptance message including a Pending NSSAI (Network Slice Selection Assistance Information) from a control device, the Pending NSSAI including an S-NSSAI (Single Network Slice Selection Assistance Information) and area information, and the transceiver unit performs a network slice authentication approval procedure using the S-NSSAI based on the reception of the Pending NSSAI, and the control unit deletes the S-NSSAI and the area information from the Pending NSSAI when the UE moves outside the area indicated by the area information during the execution of the network slice authentication approval procedure.

[0016] In one embodiment of the present invention, a core network device comprises a control unit and a transceiver unit, wherein the transceiver unit transmits a registration acceptance message including a Pending NSSAI (Network Slice Selection Assistance Information) to a UE (User Equipment), the Pending NSSAI including an S-NSSAI (Single Network Slice Selection Assistance Information) and area information, and the transceiver unit performs a network slice authentication approval procedure using the S-NSSAI when the UE is located within an area indicated by the area information, and when the UE moves from within the area indicated by the area information to outside the area indicated by the area information during the network slice authentication approval procedure using the S-NSSAI, the transceiver unit aborts the network slice authentication approval procedure.

[0017] According to one embodiment of the present invention, an AMF (Access and Mobility Management Function) comprises a transceiver unit, a memory unit, and a control unit, wherein the transceiver unit receives a requested NSSAI (Network Slice Selection Assistance Information) including an S-NSSAI (Single Network Slice Selection Assistance Information) from a UE (User Equipment) via a first area, the memory unit stores the S-NSSAI and area information associated with the S-NSSAI, and the control unit checks the area information based on the reception of the S-NSSAI, and if the area information includes the first area, determines that the UE is in the area indicated by the area information, and if the area information does not include the first area, determines that the UE is not in the area indicated by the area information.

[0018] According to one embodiment of the present invention, an AMF (Access and Mobility Management Function) comprises a transceiver unit, a memory unit, and a control unit, wherein the transceiver unit receives a registration request message from a UE (User Equipment) via a first area, the memory unit stores an S-NSSAI (Single Network Slice Selection Assistance Information) set in the UE and area information associated with the S-NSSAI, and the control unit determines that the UE is in an area indicated by the area information if the area information includes the first area when a requested NSSAI (Network Slice Selection Assistance Information) is not included in the registration request message, and determines that the UE is not in the area indicated by the area information if the area information does not include the first area.

[0019] In one embodiment of the present invention, an SMF (Session Management Function) comprises a control unit and a transceiver unit, the transceiver unit executes a PDU session establishment procedure for establishing a PDU (Protocol Data Unit) session, the control unit manages the PDU session in association with area information, the transceiver unit receives first identification information from an AMF (Access and Mobility Management Function) indicating that a UE (User Equipment) has moved from within an area indicated by the area information to outside the area indicated by the area information, and the control unit releases the PDU session or releases user plane resources associated with the PDU session based on the reception of the first identification information. Effect of the Invention

[0020] According to one aspect of the present invention, in 5GS, support for eNS is enabled, enabling the provision of network sliced ​​services based on the area accessed by the UE. [Brief description of the drawings]

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

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

[0023] [1. System Overview] First, FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1. As shown in FIG.

[0024] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network _A80, core network _A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6.

[0025] In the following, these devices and functions may be described with abbreviated symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0026] Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and N3IWF170, as well as interfaces that connect these devices and functions to each other.

[0027] In the following, these devices and functions may be referred to by abbreviated symbols, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0028] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0093] In addition, the SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure.Each procedure may be initiated by the UE or may be initiated by the NW.

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

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

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

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

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

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

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

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

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

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

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

[0105] The current PLMN may be the PLMN requested by the UE, and / or the PLMN selected by the UE, and / or the RPLMN, and / or the PLMN allowed by the network, and / or the PLMN to which the core network device sending or receiving the message belongs.

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

[0107] In addition, the SOR (Steering of Roaming) transparent container information element may include information for the HPLMN and / or VPLMN to indicate the optimal roaming destination network to the roaming UE. Specifically, the SOR transparent container information element may include a list of preferred PLMN / access technology combinations.

[0108] In addition, the SOR transparent container information element and / or list of preferred PLMN / access technology combinations may be included in a "Secured packet" encrypted by the PLMN (HPLMN) using security functions, and may also be referred to as a "Secured packet."

[0109] In addition, a Steering of Roaming application function (SOR-AF), which is one of the entities in the core network, may provide information including a list of preferred PLMN / access technology combinations to the UDM, and the AMF may refer to the information including the list of preferred PLMN / access technology combinations provided to the UDM, generate a SOR transparent container information element based on this information, and send it to the UE.

[0110] Here, the list of preferred PLMN / access technology combinations may be a list consisting of combinations of PLMNs (preferred PLMNs) and access technologies, and each combination may be arranged in order of priority.

[0111] In addition, for example, when a UE switches networks due to mobility or selects a PLMN in automatic mode when the UE powers up at a roaming destination, the combination of PLMN and access technology that has the highest priority and is available and permissible may be selected.

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

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

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

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

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

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

[0118] Moreover, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in the NSSAI is information that assists the access network or core network in selecting an NSI. The UE may store an NSSAI allowed by the network for each PLMN. The NSSAI may be information used to select an AMF. The UE may apply each NSSAI (allowed NSSAI, and / or configured NSSAI, and / or rejected NSSAI, and / or pending NSSAI, and / or first NSSAI) to the PLMN and the EPLMN.

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

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

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

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

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

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

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

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

[0127] The requested NSSAI may be information indicating a network slice requested by the UE. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is transmitted in a registration request message, a NAS message such as a PDU session establishment request message transmitted from the UE to the network, or a Radio Resource Control (RRC) message including a Non-Access-Stratum (NAS) message.

[0128] Also, the allowed NSSAI is information indicating one or more network slices to which the UE is permitted. In other words, the allowed NSSAI is information identifying a network slice to which the network permits the UE to connect.

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

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

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

[0132] Also, the rejected NSSAI is information indicating one or more network slices to which the UE is not permitted. In other words, the rejected NSSAI is information identifying a network slice to which the network does not permit the UE to connect. The rejected NSSAI may be information including one or more combinations of the S-NSSAI and a rejection reason value.

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

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

[0135] The rejected NSSAI may be any one of the first to fourth rejected NSSAIs, the pending NSSAI, and the first NSSAI, or a combination of these. The S-NSSAI included in the rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

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

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

[0138] Here, the first rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current PLMN among the S-NSSAIs included in the requested NSSAI by the UE. The first rejected NSSAI may be a rejected NSSAI for the current PLMN of 5GS, a rejected S-NSSAI for the current PLMN, or an S-NSSAI included in the rejected NSSAI for the current PLMN. The first rejected NSSAI may be a rejected NSSAI stored by the UE or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the first rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. The rejection reason value at this time may be "S-NSSAI not available in the current PLMN" or may be information indicating that the S-NSSAI associated with the rejection reason value is not available in the current PLMN or SNPN. The S-NSSAI included in the first rejected NSSAI may be expressed as the first rejected S-NSSAI.

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

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

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

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

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

[0144] The third rejected NSSAI may apply to the entire registered PLMN, may apply to the registered PLMN and / or the EPLMN, or may apply to all PLMNs. The third rejected NSSAI may apply to all PLMNs, which may mean that the third rejected NSSAI is not associated with a PLMN, or may mean that the third rejected NSSAI is associated with a HPLMN.

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

[0146] The third rejected NSSAI is a rejected NSSAI that identifies a slice that the UE has rejected due to the failure or cancellation of the NSSAA from the core network. Specifically, while the UE stores the third rejected NSSAI, the UE does not initiate a registration request procedure for the S-NSSAI included in the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAIs received from the core network in association with a rejection reason value indicating the failure of the NSSAA. The third rejected NSSAI is information that is independent of the access type. Specifically, when the UE stores the third rejected NSSAI, the UE may not attempt to transmit a registration request message including the S-NSSAI included in the third rejected NSSAI to both 3GPP access and non-3GPP access. Alternatively, the UE may transmit a registration request message including the S-NSSAI included in the third rejected NSSAI based on a UE policy. Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which the UE can transmit a registration request message including an S-NSSAI included in the third rejected NSSAI. In other words, when the UE transmits a registration request message including an S-NSSAI included in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI.

[0147] The fourth rejected NSSAI is a collection of one or more S-NSSAIs that are rejected by the network because the S-NSSAI requires area restriction based on the area of ​​service and the UE is not in an area where the S-NSSAI is permitted. The fourth rejected NSSAI may be an NSSAI stored by the UE and / or the NW, or may be an NSSAI transmitted and received between the NW and the UE.

[0148] When the fourth rejected NSSAI is transmitted from the NW to the UE, the fourth rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. In this case, the rejection reason value may be "S-NSSAI that is not possible because it is outside the area where the service of the S-NSSAI is provided" or may be information indicating that it is not possible because the UE is outside the area where the service of the S-NSSAI associated with the rejection reason value is provided. The S-NSSAI included in the fourth rejected NSSAI may be expressed as a fourth rejected S-NSSAI.

[0149] The fourth rejected NSSAI may further include information that includes one or more combinations of an S-NSSAI and area information.

[0150] The fourth rejected NSSAI may apply to the entire registered PLMN, may be valid for all PLMNs, may apply, may be valid within an area indicated by the area information associated with the fourth rejected S-NSSAI, may apply to the registered PLMN and the EPLMN. The fourth rejected NSSAI applies to all PLMNs may mean that the fourth rejected NSSAI is not associated with a PLMN, or may mean that the fourth rejected NSSAI is associated with a HPLMN.

[0151] If the fourth rejected NSSAI is valid across all registered PLMNs, or applies to all PLMNs, or applies to the registered PLMNs and / or EPLMNs, the UE and / or NW may treat the fourth rejected NSSAI and the S-NSSAI contained in the fourth rejected NSSAI as information independent of access type.

[0152] If the fourth rejected NSSAI is valid in the area indicated by the associated area information, the UE and / or NW may treat the fourth rejected NSSAI and the S-NSSAI included in the fourth rejected NSSAI as independent information for each access type.

[0153] The fourth rejected NSSAI may be a pending NSSAI, may be the first NSSAI, or may be information different from these.

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

[0155] When the first NSSAI is transmitted from the NW to the UE, the first NSSAI may be information including one or more pieces of information including at least one of the S-NSSAI, the mapped S-NSSAI, the rejection reason value, the value of the back-off timer, and information indicating the validity range of the back-off timer value. The rejection reason value at this time may be "the S-NSSAI has reached the maximum number of UEs per network slice" or may be information indicating that the maximum number of UEs permitted for the S-NSSAI associated with the rejection reason value has been reached. Here, the rejection reason value may be a rejection reason value included in the rejected NSSAI, may be flag information, or may be 5GMM cause. Furthermore, at this time, the back-off timer value may be information indicating a period during which the UE is prohibited from transmitting an MM message and an SM message using the S-NSSAI related to the corresponding S-NSSAI or the mapped S-NSSAI.

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

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

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

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

[0160] A pending NSSAI is a collection of one or more S-NSSAIs that are pending and / or unavailable for use by the UE. A pending NSSAI may be a collection of S-NSSAIs for which the network requires network slice specific authentication and for which network slice specific authentication has not been completed. A pending NSSAI may be a 5GS pending NSSAI. A pending NSSAI may be an NSSAI stored by the UE and / or NW, or an NSSAI sent and received between the NW and the UE.

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

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

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

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

[0165] The pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE is pending a procedure. Specifically, the UE does not initiate a registration request procedure for the S-NSSAI included in the pending NSSAI while storing the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI included in the pending NSSAI is completed. The pending NSSAI is information that is independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to transmit a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0166] In addition, the area of ​​service may be attribute information indicating an area in which a UE can access a specific network slice, in other words, the area of ​​service may be information composed of one or more elements to indicate an area in which a UE can establish a PDU session for a specific S-NSSAI.

[0167] Here, the area or information on the area indicated (specified) by the area of ​​service may be a Tracking Area (TA), may be a registration area, may be information (indicating a service area for each S-NSSAI) composed of one or more TAs, may be composed of one or more cells (eNB and / or gNB coverage), or may be an area based on geolocation information. Here, the area based on geolocation information may be composed of one or more eNB and / or gNB coverage mapped to geolocation information, or may be composed of one or more TAs mapped to geolocation information.

[0168] The area of ​​service may be composed of one or more entries, and each entry may include information indicating a country and / or region. Specifically, the area of ​​service may include one or more entries including information indicating a country and / or region in which the service of the network slice is provided based on a roaming agreement between the HPLM and the VPLMN.

[0169] Furthermore, a state in which the UE is within an area of ​​service may be a state in which the UE is present within the aforementioned area associated with the S-NSSAI to which the UE is connected or to which it is attempting to connect, and a state in which the UE is outside the area of ​​service may be a state in which the UE is not present within the aforementioned area associated with the S-NSSAI to which the UE is attempting to connect.

[0170] In addition, the area indicated by the area of ​​service may be determined by a Network Slice Provider (NSP) providing the network slice service, or may be determined based on a network policy, but is not limited to these.

[0171] In addition, the area in which the S-NSSAI service is provided based on the area of ​​service is also referred to as the service area.

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

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

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

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

[0176] The management of the maximum number of UEs connected to a slice refers to managing the maximum number of UEs that can be registered in a network slice or an S-NSSAI at the same time. Here, the UE to be registered in the network slice or the S-NSSAI may be stored by including the S-NSSAI indicating the network slice in the allowed NSSAI. A device in a network that supports the function of managing the maximum number of UEs connected to a slice can store, for each S-NSSAI, whether or not the management of the maximum number of UEs connected to the slice is required, and can further check during the registration procedure whether or not the registered UEs have reached a constant number that is the maximum number. Furthermore, each device that supports the function of managing the maximum number of UEs connected to a slice may be capable of storing a first NSSAI. In this document, the maximum number of UEs connected to a slice may be expressed as the maximum number of UEs connected to each slice, or the maximum number of UEs that can be registered in the network slice or the S-NSSAI, or the maximum number of UEs, or a constant number.

[0177] The back-off timer is a timer for prohibiting the UE from transmitting an MM message and / or starting a procedure by an SM message. The back-off timer is managed and executed by the UE. The back-off timer may be associated with an S-NSSAI. The UE may be in a state in which the transmission of an MM message and / or the transmission of an SM message using the S-NSSAI is prohibited, restricted, or limited while the back-off timer associated with the S-NSSAI is valid. These restrictions may be restrictions due to 5GS congestion management or restrictions including restrictions due to 5GS congestion management.

[0178] The backoff timer may be a timer that is started and / or stopped on a per S-NSSAI and / or per PLMN basis.

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

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

[0181] Furthermore, the back-off timer may be a timer for prohibiting transmission of an MM message using a specific NSSAI, in other words, the UE may be configured not to transmit an MM message using the specific NSSAI and / or an NSSAI including a specific S-NSSAI during the countdown of the timer.

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

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

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

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

[0186] The first identification information in this embodiment may be a capability information of the UE, which indicates that the UE supports an area of ​​service.

[0187] More specifically, the first identity may be capability information indicating that the UE has the capability to transmit, receive, recognize, store, and process information including area information and / or a cause value associated with a network slice (S-NSSAI) requested and / or granted from the core network to the core network. Furthermore, by transmitting the first identity to the core network, the UE may indicate that it supports the capability to receive, recognize, and process information related to an area of ​​service from the core network.

[0188] Here, a UE supporting the area of ​​service may have a function of transmitting and receiving information related to the provided area of ​​service between the core network, recognizing, storing, and processing the information, and a function of executing a UE-initiated or network-initiated procedure for the area of ​​service. Specifically, for example, a UE supporting the area of ​​service may have a function of recognizing, storing, and processing information related to the area associated with the S-NSSAI received from the core network, and may have a function of recognizing, storing, and processing a cause value related to the area of ​​service associated with the S-NSSAI.

[0189] Furthermore, the first identification information may be identification information for UE_A10 to request core network capability information indicating that the area of ​​service is supported from the core network.

[0190] Here, the information indicating the area may be third identification information, which will be described later.

[0191] Alternatively, the first identification information may be capability information of the UE, which indicates whether the UE supports the area of ​​service or not.

[0192] The second identification information in this embodiment is the capability information of the core network, which indicates that the core network supports an area of ​​service.

[0193] More specifically, the second identification information may be capability information indicating that the UE has the ability to transmit, receive, recognize, store, and process information regarding the area of ​​service, including area information and / or reason values ​​associated with a network slice (S-NSSAI) requested from the UE and / or granted to the UE.

[0194] Furthermore, the core network may send second identification information to the UE to indicate that the core network supports the function of receiving, recognizing, and processing information related to the area of ​​service from the UE.

[0195] Here, a UE supporting the area of ​​service may have a function of transmitting and receiving information related to the provided area of ​​service between the core network, recognizing, storing, and processing the information, and a function of executing a UE-initiated or network-initiated procedure for the area of ​​service. Specifically, for example, a UE supporting the area of ​​service may have a function of recognizing, storing, and processing information related to the area associated with the S-NSSAI received from the core network, and may have a function of recognizing, storing, and processing a cause value related to the area of ​​service associated with the S-NSSAI.

[0196] Furthermore, the second identification information may be identification information to be transmitted to UE_A10 based on the first identification information received from the UE.

[0197] Here, the information indicating the area may be third identification information, which will be described later.

[0198] The third identification information in this embodiment may be information indicating the area in which the S-NSSAI service is provided.

[0199] Here, the area indicated by the third identification information may be an area or information regarding the area indicated (specified) by the above-mentioned area of ​​service, may be a Tracking Area (TA), may be a registration area, may be information (indicating a service area for each S-NSSAI) composed of one or more TAs, may be composed of one or more cells (coverage of eNB and / or gNB), or may be an area based on geolocation information.

[0200] Furthermore, when the third identification information is an area based on geolocation information, it may be identification information composed of the coverage of one or more eNBs and / or gNBs mapped to the geolocation information, or it may be identification information composed of one or more TAs mapped to the geolocation information.

[0201] The third identification information may be area information included in the fourth rejected NSSAI.

[0202] The fourth identification information in this embodiment may be a cause value indicating that the UE is outside the area where the service of the network slice (S-NSSAI) to which the UE is connected or to which the UE is attempting to connect is provided. The fourth identification information may also be a cause value indicating that the UE has moved outside the area. The fourth identification information may also be a cause value indicating that the UE is not in a location where it can connect to the S-NSSAI.

[0203] Here, the fourth identification information may be a cause value included in the rejected NSSAI information element (IE), or may be another identification information associated with the S-NSSAI.

[0204] [3.1. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a network slice-specific authentication and authorization procedure, a generic UE configuration update procedure, and a network-initiated de-registration procedure. Each procedure will be described below.

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

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

[0207] Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network and / or for the UE to periodically notify the network of the status of the UE and / or for updating certain parameters related to the UE in the network.

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

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

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

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

[0212] Here, UE_A10 can transmit the first identification information and / or requested NSSAI (Network Slice Selection Assistance Information) in a registration request message and / or an RRC message. Furthermore, UE_A10 may transmit the registration request message and / or the RRC message including identification information indicating the type of the procedure. Here, the identification information indicating the type of the procedure may be a 5GS registration type IE, and may be information indicating that the procedure is a registration procedure for initial registration, for updating registration information associated with movement, for periodic updating of registration information, or for emergency registration.

[0213] In order to notify the network of the functions supported by UE_A10, UE_A10 may include the capability information of the UE in the registration request message, and may include the first identification information as the capability information of the UE. Here, the capability information of the UE may be the 5G MM capability of 5GS.

[0214] UE_A10 may transmit this identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, the MAC layer, the RLC layer, the PDCP layer). By transmitting these identification information, UE_A10 may indicate that UE_A10 supports each function, may indicate a UE request, or may indicate both. Furthermore, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0215] Furthermore, UE_A10 may include the S-NSSAI (NSSAA is pending for the S-NSSAI) requested by UE_A10 in the requested NSSAI. Furthermore, UE_A10 may indicate a request for the S-NSSAI by including the S-NSSAI in the requested NSSAI.

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

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

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

[0219] When the 5G AN 120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S602). The 5G AN 120 (or gNB) can select an AMF based on one or more identification information included in the registration request message and / or the RRC message including the registration request message. Specifically, the 5G AN (or gNB) may select the new AMF 141 to which the registration request message is to be transmitted based on the first identification information.

[0220] For example, the 5G AN 120 (or gNB) may select an AMF that supports a function corresponding to the capability information indicated by the first identification information based on the first identification information and / or the requested NSSAI. Specifically, the 5G AN (or gNB) may select an AMF that corresponds to the capability information of the UE indicated by the first identification information and is included in a network slice based on an area of ​​service or has connectivity to the network slice.

[0221] The method of selecting an AMF is not limited to this, and the 5G AN (or gNB) may select an AMF based on other conditions. The 5G AN (or gNB) extracts a registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). If at least one of the first and second identification information is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message may be transferred to the selected AMF (new AMF 141) together with the registration request message (S604).

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

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

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

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

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

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

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

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

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

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

[0232] Here, the UE context transmitted from new AMF 141 to old AMF 142 may include a UE ID and an allowed NSSAI. Furthermore, the UE context may include a configured NSSAI and / or a rejected NSSAI, an NSSAI and / or a pending NSSAI, and / or a first NSSAI. Furthermore, the allowed NSSAI, and / or the configured NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first NSSAI included in the UE context, and the S-NSSAI included in each NSSAI may be linked to information on whether notification to the UE has been completed.

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

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

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

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

[0237] The new AMF 141 may transmit one or more of the second to fourth identification information included in the control message. Here, the third identification information may be transmitted in one or more pieces in association with each S-NSSAI included in the allowed NSSAI and / or rejected NSSAI, and the fourth identification information may be transmitted in one or more pieces in association with each S-NSSAI included in the rejected NSSAI. By transmitting these identification information and / or the control message, the new AMF 141 may indicate that the network supports each function including the function related to the area of ​​service, may indicate that the request from the UE has been accepted, may indicate that the request from the UE has not been permitted, or may indicate a combination of these. Furthermore, when multiple identification information are transmitted and received, two or more of these identification information may be configured as one or more identification information. The information indicating support of each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0238] In addition, based on receiving the first identification information from the UE, the new AMF 141 may transmit a control message (a registration acceptance message or a registration rejection message) including one or more of the second to fourth identification information.

[0239] In other words, when the first identification information received from the UE indicates that the UE supports an area of ​​service, the new AMF 141 may transmit to the UE area information corresponding to one or more S-NSSAIs included in the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI transmitted by the new AMF 141.

[0240] Alternatively, when the core network supports the area of ​​service, the new AMF 141 may transmit the second identification information, the S-NSSAI, and the area information associated with the S-NSSAI to the UE. Note that the S-NSSAI and the area information at this time may be one or more S-NSSAI and area information included in the Allowed NSSAI, the Rejected NSSAI, or the Pending NSSAI.

[0241] In addition, the area information associated with the S-NSSAI may be included in the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI sent from the new AMF 141 to the UE, or may be information independent of the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI.

[0242] In other words, if the new AMF141 does not receive first identification information from the UE, or if the new AMF141 receives first identification information from the UE indicating that the UE does not support an area of ​​service, the new AMF141 may perform control not to transmit area information associated with the S-NSSAI included in the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI transmitted by the new AMF141 to the UE.

[0243] Specifically, if new AMF 141 detects that the UE does not support area of ​​service, new AMF 141 does not need to send area information corresponding to the S-NSSAI requested by the UE, even if the S-NSSAI is an S-NSSAI that requires an area of ​​service, and may send an Allowed NSSAI, Rejected NSSAI, or Pending NSSAI that does not include area information to the UE.

[0244] In addition, the area information associated with the S-NSSAI may be included in the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI sent from the new AMF 141 to the UE, or may be information independent of the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI.

[0245] Furthermore, new AMF141 may associate information on the service area for each S-NSSAI included in the requested NSSAI sent by UE_A10 in the registration request message as third identification information, include it in a control message, and send it to the UE. Here, the information on the service area for each S-NSSAI may be held by each AMF supporting an area of ​​service in the core network, or may be requested and obtained by the AMF from a device in or outside the core network that manages the service area for each S-NSSAI.

[0246] Furthermore, based on information about the area to which UE_A10 is connected and information about the service area for each S-NSSAI included in the requested NSSAI sent by UE_A10 in the registration request message, it may determine whether the UE is inside or outside the service area of ​​the S-NSSAI, determine a fourth identification information, associate it with each S-NSSAI, and send it to the UE by including it in a control message.

[0247] Also, for example, if UE_A10 does not include a requested NSSAI in the registration request message, the third and / or fourth identification information may be determined taking into account the area information for each S-NSSAI included in the configured NSSAI and the area information or location information to which the UE is connected, and may be included in a control message and transmitted to the UE.

[0248] Here, for example, if the registration accept message does not include the second identification information but includes the third and / or fourth identification information, UE_A10 may recognize that the core network supports the area of ​​service.

[0249] Also, for example, if the core network or AMF does not support the area of ​​service, the registration acceptance message or the registration rejection message may not include the second to fourth identification information and may be sent to UE_A10. In other words, since the registration acceptance message or the registration rejection message does not include the second to fourth identification information, UE_A10 may recognize that the core network does not support the area of ​​service.

[0250] Also, for example, here, if the control message sent to the UE is a registration acceptance message, the message may include one or more third and / or fourth identification information associated with each S-NSSAI included in the allowed NSSAI and / or rejected NSSAI.

[0251] Also, for example, if the control message sent to the UE is a registration rejection message, the message may include one or more third and / or fourth identification information associated with each S-NSSAI included in the rejected NSSAI.

[0252] In addition, each process that the UE performs based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0253] Here, it has been explained that the third and / or fourth identification information is associated with the S-NSSAI included in the allowed NSSAI and / or rejected NSSAI and is included in a control message and transmitted to the UE, but it may also be associated with the S-NSSAI included in the Pending NSSAI and included in a control message and transmitted to the UE, for example.

[0254] Also, the Allowed NSSAI and / or Rejected NSSAI included in the registration acceptance message may include an S-NSSAI and a third identification. Then, based on receiving the Rejected NSSAI, the UE may store the S-NSSAI in association with the third identification. Also, the S-NSSAI may include a fourth identification, which may indicate, for example, that the UE is not in a location where the S-NSSAI can be connected. Also, based on receiving the Rejected NSSAI, the UE may recognize that the S-NSSAI cannot be used in the area to which the UE is connected.

[0255] Furthermore, the Rejected NSSAI included in the registration rejection message may include an S-NSSAI and a third identification. Then, based on receiving the Rejected NSSAI, the UE may store the S-NSSAI and the third identification in association with each other. Furthermore, the S-NSSAI may include a fourth identification, which may indicate, for example, that the UE is not in a location where the S-NSSAI can be connected. Furthermore, based on receiving the Rejected NSSAI, the UE may recognize that the S-NSSAI is not available in the area to which the UE is connected.

[0256] Based on receiving second identification information, an S-NSSAI, and area information to which the S-NSSAI is associated from the AMF, the UE may store the received S-NSSAI in association with the area information.

[0257] Specifically, when a UE receives a second identification information, an Allowed NSSAI, and area information, and this area information is information associated with an S-NSSAI included in the Allowed NSSAI, the UE may associate the received S-NSSAI with the area information and store it as an Allowed NSSAI.

[0258] Similarly, when the UE receives a second identification information, a Rejected NSSAI and area information, and this area information is information associated with an S-NSSAI included in the Rejected NSSAI, or is a fourth rejected S-NSSAI, the UE may associate the received S-NSSAI with the area information and store it as a rejected NSSAI.

[0259] Similarly, when the UE receives second identification information, a Pending NSSAI and area information, and this area information is information associated with the S-NSSAI included in the Pending NSSAI, the UE may associate the received S-NSSAI with the area information and store it as a Pending NSSAI.

[0260] In other words, if the control message is a registration accept message, the control message may include an Allowed NSSAI and / or a Rejected NSSAI. Conversely, if the control message is a registration reject message, the control message may include a Rejected NSSAI.

[0261] Here, the Allowed NSSAI may include an S-NSSAI and a third identification information. Furthermore, the S-NSSAI and the third identification information may be associated with each other. Furthermore, the Allowed NSSAI may include identification information in which the S-NSSAI and the third identification information are combined.

[0262] Furthermore, the Rejected NSSAI may include an S-NSSAI, a third identification information, and a fourth identification information. Furthermore, the S-NSSAI, the third identification information, and the fourth identification information may be associated with each other. Furthermore, the Allowed NSSAI may include identification information that combines the S-NSSAI, the third identification information, and the fourth identification information.

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

[0264] Here, the AMF may determine whether the UE is located within the service area of ​​a specific S-NSSAI (S-NSSAI#1-1) based on the received S-NSSAI and the area information stored by the AMF. In other words, when a Requested NSSAI is provided from the UE, the AMF may determine whether the UE is located within the service area of ​​a specific S-NSSAI (S-NSSAI#1-1) based on the S-NSSAI included in the Requested NSSAI and the area information stored by the AMF.

[0265] Specifically, the AMF may determine that the UE is located within the service area of ​​S-NSSAI#1-1 if the area information associated with S-NSSAI#1-1 includes the area in which the UE is currently located. Conversely, the AMF may determine that the UE is located outside the service area of ​​S-NSSAI#1-1 if the area information associated with S-NSSAI#1-1 does not include the area in which the UE is currently located. Note that the area information may be information obtained by the AMF from another device such as a UDM, or may be information set in the AMF.

[0266] In addition, the AMF may determine whether the UE is located within the service area of ​​S-NSSAI#1-1 based on the S-NSSAI (S-NSSAI#1-1) provided to the UE and the area information stored by the AMF. In other words, when a Requested NSSAI is not provided from the UE, the AMF may determine whether the UE is located within the service area of ​​S-NSSAI#1-1 based on the S-NSSAI (S-NSSAI#1-1) provided to the UE and the area information stored by the AMF.

[0267] Specifically, the AMF may determine that the UE is located within the service area of ​​S-NSSAI#1-1 if the area information associated with S-NSSAI#1-1 includes the area in which the UE is currently located. Conversely, the AMF may determine that the UE is located outside the service area of ​​S-NSSAI#1-1 if the area information associated with S-NSSAI#1-1 does not include the area in which the UE is currently located. Note that the area information may be information obtained by the AMF from another device such as a UDM, or may be information set in the AMF.

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

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

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

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

[0272] The AMF receives a registration completion message via the 5G AN (gNB) (S612). In addition, each device completes this procedure based on the transmission and reception of the registration acceptance message and / or the registration completion message.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0294] AUSF180 transmits an NSSAA authentication response message including the authentication result and S-NSSAI. Here, the authentication result may be information indicating success or failure. Here, the S-NSSAI included in the NSSAA authentication response message may be the S-NSSAI of the HPLMN or the mapped S-NSSAI. Based on receiving the NSSAA authentication response message, AMF140 transmits an authentication result message to UE_A10 (S714). AMF140 may transmit the authentication result message including the NSSAA authentication response message, or the authentication result and S-NSSAI included in the NSSAA authentication response message.

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

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

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

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

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

[0300] In addition, if the UE moves out of the service area of ​​the S-NSSAI during the execution of this procedure, the UE and / or each device of the core network may abort this procedure, and the UE may delete information on the S-NSSAI and / or the area associated with the S-NSSAI from the Pending NSSAI. Here, the information on the area associated with the S-NSSAI may be the third identification information received by the UE in the registration procedure.

[0301] Furthermore, the core network shall not perform this procedure if the UE is outside the service area of ​​S-NSSAI.

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

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

[0304] During this procedure, each device may transmit and receive a message including identification information for changing the configuration information of the UE and / or identification information for stopping or changing a function being executed by the UE. Furthermore, each device may update its configuration information to a configuration instructed by the network or start a behavior instructed by the network based on the completion of this procedure.

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

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

[0307] AMF140 may include one or more of each NSSAI (hereinafter, meaning configured NSSAI, allowed NSSAI, rejected NSSAI, pending NSSAI, and first NSSAI) related to UE_A10 in the configuration update command message and transmit it. Note that the AMF may indicate new UE configuration information or request an update of the UE configuration information by transmitting one or more of each NSSAI. Note that the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

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

[0309] Furthermore, when multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

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

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

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

[0313] Furthermore, the Allowed NSSAI and / or Rejected NSSAI included in the configuration update command message may have the S-NSSAI associated with third and / or fourth identification information, similar to the Allowed NSSAI and / or Rejected NSSAI in the registration procedure in Chapter 3.2.

[0314] In addition, the Allowed NSSAI included in the configuration update command message may include the S-NSSAI and third identification information.

[0315] Furthermore, the Rejected NSSAI included in the configuration update command message may include an S-NSSAI and a third identification. Then, based on receiving the Rejected NSSAI, the UE may store the S-NSSAI and the third identification in association with each other. Also, the S-NSSAI may include a fourth identification, which may indicate, for example, that the UE is not in a location where the S-NSSAI can be connected. Also, based on receiving the Rejected NSSAI, the UE may recognize that the S-NSSAI is not available in the area to which the UE is connected.

[0316] In addition, when this procedure is executed when the UE moves outside the service area indicated by the third identification information received in the procedure of Chapter 3.2 or Chapter 3.3, the configuration update command message may further include information indicating that the S-NSSAI is unavailable in the current area.

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

[0318] Furthermore, UE_A10 may appropriately store each received NSSAI. Specifically, when UE_A10 receives a configured NSSAI, UE_A10 may store the received configured NSSAI as a "configured NSSAI associated with the current PLMN." In other words, UE_A10 may replace the "configured NSSAI associated with the current PLMN stored by UE_A10" with the "received configured NSSAI."

[0319] Furthermore, when UE_A10 receives a configured NSSAI, it may delete the mapped S-NSSAI of the S-NSSAI included in the "configured NSSAI associated with the current PLMN stored by UE_A10". Furthermore, when the "received configured NSSAI" includes one or more mapped S-NSSAIs, UE_A10 may store the one or more mapped S-NSSAIs.

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

[0321] Alternatively, when UE_A10 receives a configured NSSAI, it may delete at least one of the "first rejected NSSAI stored by UE_A10 and associated with the current PLMN," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN," and the "third rejected NSSAI stored by UE_A10 and associated with the current PLMN."

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

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

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

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

[0326] Alternatively, if UE_A10 does not receive a TAI list but receives an allowed NSSAI from new AMF141, and if the TAI included in the TAI list that the UE has previously received and stored belongs to an EPLMN, UE_A10 may store the received allowed NSSAI as "the allowed NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs and the current access type."

[0327] In other words, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store the "received allowed NSSAI" in each "one allowed NSSAI associated with one of the different PLMNs and the current access type."

[0328] In other words, UE_A10 may store the "received allowed NSSAI" in each "allowed NSSAI associated with the PLMN to which the TAI included in the registration area stored by UE_A10 belongs and the current access type."

[0329] Further / or, if multiple TAIs included in a registration area stored by UE_A10 belong to different PLMNs, UE_A10 may replace each "allowed NSSAI associated with each PLMN to which a TAI included in a registration area belongs and the current access type" stored by UE_A10 with the "received allowed NSSAI."

[0330] Specifically, when TAI#1 and TAI#2 are included in the registration area stored by UE_A10, if TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#2, which is an EPLMN, UE_A10 may store the "received allowed NSSAI" as "allowed NSSAI#1 associated with PLMN#1 and the current access type" and "allowed NSSAI#2 associated with PLMN#2 and the current access type."

[0331] Alternatively, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store the "received allowed NSSAI" in "one allowed NSSAI associated with the different PLMN or PLMNs to which the TAI included in the registration area belongs and the current access type."

[0332] Further / or, if two or more TAIs included in the registration area belong to multiple PLMNs, UE_A10 may replace the "one allowed NSSAI associated with one or more PLMNs to which the TAIs included in the registration area belong and the current access type" stored in UE_A10 with the "received allowed NSSAI."

[0333] Specifically, when TAI#1 and TAI#2 are included in the registration area stored by UE_A10, and TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#1, which is an EPLMN, UE_A10 may store the "received allowed NSSAI" in "allowed NSSAI#1 associated with PLMN#1, PLMN#2, and the current access type."

[0334] Alternatively, if a TAI included in a registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store the "received allowed NSSAI" only in "one allowed NSSAI associated with the RPLMN and the current access type." In other words, even if a TAI included in a registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, UE_A10 may not store the "received allowed NSSAI" as an allowed NSSAI associated with the different PLMN or PLMNs.

[0335] Further / or, if multiple TAIs included in the registration area belong to different PLMNs, UE_A10 may replace the "one allowed NSSAI associated with the RPLMN and the current access type" stored by UE_A10 with the "received allowed NSSAI."

[0336] Specifically, when the registration area stored by UE_A10 includes TAI#1 and TAI#2, if TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#1, which is an EPLMN, UE_A10 may store the "received allowed NSSAI" only in "allowed NSSAI#1 associated with PLMN#1 and the current access type."

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

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

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

[0340] Specifically, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from at least one of the "first rejected NSSAI stored by UE_A10 and associated with the current PLMN," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN," the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN and the current registration area," and the "third rejected NSSAI stored by UE_A10 and associated with the current PLMN," or it may delete the S-NSSAI included in the received allowed NSSAI from all NSSAIs.

[0341] Specifically, when UE_A10 receives an allowed NSSAI, it may further delete the S-NSSAI associated with the current registration area and included in the received allowed NSSAI from the "second rejected NSSAI stored by UE_A10 and associated with the current PLMN."

[0342] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with all PLMNs". Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "pending NSSAI stored by UE_A10 and associated with the EPLMN".

[0343] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with all PLMNs".

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

[0345] Specifically, when UE_A10 receives a rejection reason value "S-NSSAI not possible in current PLMN or SNPN" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to the first rejected NSSAI associated with the current PLMN.

[0346] Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI not allowed in current registration area" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the "received rejected S-NSSAI" to the "second rejected NSSAI associated with current PLMN and current registration area".

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

[0348] If the TAI included in the current registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store and / or add the "rejected S-NSSAI received associated with the rejection reason value "S-NSSAI not allowed in current registration area" to each "second rejected NSSAI associated with one PLMN among the different PLMN or PLMNs and the current registration area."

[0349] Further / or, if one or more TAIs included in the registration area belong to different PLMNs, UE_A10 may add a "rejected S-NSSAI received associated with the rejection reason value "S-NSSAI not allowed in current registration area" to each "second rejected NSSAI associated with each PLMN to which the TAIs included in the registration area belong and the current access type" stored by UE_A10 and store it.

[0350] Specifically, when the registration areas stored by UE_A10 include TAI#1 and TAI#2, if TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#2, which is an EPLMN, UE_A10 may store the "received second rejected S-NSSAI" as "second rejected NSSAI#1 associated with PLMN#1 and the current registration area" and "second rejected NSSAI#2 associated with PLMN#2 and the current registration area."

[0351] Alternatively, if the TAI included in the registration area belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store the "rejected S-NSSAI received in association with the rejection reason value "S-NSSAI not allowed in the current registration area" in "a second rejected NSSAI associated with the different PLMN or PLMNs and the current registration area."

[0352] Further / or, if multiple TAIs included in the registration area belong to different PLMNs, UE_A10 may add and store the "rejected S-NSSAI received associated with the rejection reason value "S-NSSAI not allowed in current registration area"" to the "one second rejected NSSAI associated with those multiple PLMNs and the current access type" stored by UE_A10.

[0353] Specifically, when the registration areas stored by UE_A10 include TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#2, which is an EPLMN, UE_A10 may store the "received second rejected S-NSSAI" in "second rejected NSSAI#1 associated with PLMN#1, PLMN#2, and the current registration area."

[0354] Furthermore, if a TAI included in the TAI list indicating the current registration area belongs to an EPLMN, UE_A10 may store the S-NSSAI associated with the received rejection reason value "S-NSSAI not allowed in the current registration area" as "a second rejected NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs and the current access type."

[0355] Alternatively, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store the "received second rejected S-NSSAI" only in "one second rejected NSSAI associated with the RPLMN and the current access type." In other words, even if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, UE_A10 may not store the "received second rejected S-NSSAI" as a second rejected NSSAI associated with the different PLMN or PLMNs.

[0356] Further / or, if multiple TAIs included in the registration area belong to different PLMNs, UE_A10 may replace the "one second rejected NSSAI associated with the RPLMN and the current access type" stored by UE_A10 with the "received second rejected S-NSSAI."

[0357] Specifically, when the registration area stored by UE_A10 includes TAI#1 and TAI#2, if TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#1, which is an EPLMN, UE_A10 may store and / or add the "received second rejected S-NSSAI" only to the "second rejected NSSAI#1 associated with PLMN#1 and the current access type."

[0358] Further, if UE_A10 receives a rejection reason value "S-NSSAI not possible due to NSSAA failure or cancellation" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to the third rejected NSSAI associated with the current PLMN.

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

[0360] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from "pending NSSAIs stored by UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with all PLMNs". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with the EPLMN".

[0361] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with all PLMNs".

[0362] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from "pending NSSAIs stored by UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with all PLMNs". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with the EPLMN".

[0363] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from the "first NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with all PLMNs". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with the EPLMN".

[0364] In addition, each process that the UE performs based on the reception of each identification information _A10 shown above may be performed during this procedure or after completion of this procedure, or may be performed based on the completion of this procedure after completion of this procedure. Furthermore, the UE may transmit a configuration update complete message to the AMF 140 via the 5G AN (gNB) as a response message to the configuration update command message based on the identification information included in the configuration update command message (S802).

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

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

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

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

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

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

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

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

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

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

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

[0376] Specifically, when UE_A10 receives a rejection reason value "S-NSSAI not possible in current PLMN or SNPN" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to the first rejected NSSAI associated with the current PLMN.

[0377] Furthermore, if UE_A10 receives a rejection reason value "S-NSSAI not allowed in current registration area" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the "received rejected S-NSSAI" to the "second rejected NSSAI associated with current PLMN and current registration area".

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

[0379] If the TAI included in the current registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store and / or add the "rejected S-NSSAI received associated with the rejection reason value "S-NSSAI not allowed in current registration area" to each "second rejected NSSAI associated with one PLMN among the different PLMN or PLMNs and the current registration area."

[0380] Further / or, if one or more TAIs included in the registration area belong to different PLMNs, UE_A10 may add a "rejected S-NSSAI received associated with the rejection reason value "S-NSSAI not allowed in current registration area" to each "second rejected NSSAI associated with each PLMN to which the TAIs included in the registration area belong and the current access type" stored by UE_A10 and store it.

[0381] Specifically, when the registration areas stored by UE_A10 include TAI#1 and TAI#2, if TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#2, which is an EPLMN, UE_A10 may store the "received second rejected S-NSSAI" as "second rejected NSSAI#1 associated with PLMN#1 and the current registration area" and "second rejected NSSAI#2 associated with PLMN#2 and the current registration area."

[0382] Alternatively, if the TAI included in the registration area belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store the "rejected S-NSSAI received in association with the rejection reason value "S-NSSAI not allowed in the current registration area" in "a second rejected NSSAI associated with the different PLMN or PLMNs and the current registration area."

[0383] Further / or, if multiple TAIs included in the registration area belong to different PLMNs, UE_A10 may add and store the "rejected S-NSSAI received associated with the rejection reason value "S-NSSAI not allowed in current registration area"" to the "one second rejected NSSAI associated with those multiple PLMNs and the current access type" stored by UE_A10.

[0384] Specifically, when the registration areas stored by UE_A10 include TAI#1 and TAI#2, and TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#2, which is an EPLMN, UE_A10 may store the "received second rejected S-NSSAI" in "second rejected NSSAI#1 associated with PLMN#1, PLMN#2, and the current registration area."

[0385] Furthermore, if a TAI included in the TAI list indicating the current registration area belongs to an EPLMN, UE_A10 may store the S-NSSAI associated with the received rejection reason value "S-NSSAI not allowed in the current registration area" as "a second rejected NSSAI associated with the EPLMN to which the TAI included in the TAI list belongs and the current access type."

[0386] Alternatively, if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different PLMN or PLMNs are EPLMNs, and UE_A10 may store the "received second rejected S-NSSAI" only in "one second rejected NSSAI associated with the RPLMN and the current access type." In other words, even if the TAI included in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, UE_A10 may not store the "received second rejected S-NSSAI" as a second rejected NSSAI associated with the different PLMN or PLMNs.

[0387] Further / or, if multiple TAIs included in the registration area belong to different PLMNs, UE_A10 may replace the "one second rejected NSSAI associated with the RPLMN and the current access type" stored by UE_A10 with the "received second rejected S-NSSAI."

[0388] Specifically, when the registration area stored by UE_A10 includes TAI#1 and TAI#2, if TAI#1 belongs to PLMN#1, which is an RPLMN, and TAI#2 belongs to PLMN#1, which is an EPLMN, UE_A10 may store and / or add the "received second rejected S-NSSAI" only to the "second rejected NSSAI#1 associated with PLMN#1 and the current access type."

[0389] Further, if UE_A10 receives a rejection reason value "S-NSSAI not possible due to NSSAA failure or cancellation" and a rejected S-NSSAI associated with the rejection reason value, UE_A10 may add the S-NSSAI to the third rejected NSSAI associated with the current PLMN.

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

[0391] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from "pending NSSAIs stored by UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with all PLMNs". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with the EPLMN".

[0392] Furthermore, when UE_A10 receives an allowed NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with all PLMNs".

[0393] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from "pending NSSAIs stored by UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with all PLMNs". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from "pending NSSAIs stored by UE_A10 and associated with the EPLMN".

[0394] Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received rejected NSSAI from the "first NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with all PLMNs". Furthermore, when UE_A10 receives a rejected NSSAI, it may delete the S-NSSAI included in the received allowed NSSAI from the "first NSSAI stored by UE_A10 and associated with the EPLMN".

[0395] In addition, each process that the UE performs based on receiving each identification information _A10 shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

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

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

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

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

[0400] In addition, the Rejected NSSAI included in the non-registration request message may have an S-NSSAI associated with third and / or fourth identification information, similar to the Rejected NSSAI in the registration procedure in Chapter 3.2.

[0401] Furthermore, the Rejected NSSAI included in the non-registration request message may include an S-NSSAI and a third identification. Then, based on receiving the Rejected NSSAI, the UE may store the S-NSSAI and the third identification in association with each other. Also, the S-NSSAI may include a fourth identification, which may indicate, for example, that the UE is not in a location where the S-NSSAI can be connected. Also, based on receiving the Rejected NSSAI, the UE may recognize that the S-NSSAI is not available in the area to which the UE is connected.

[0402] In addition, when this procedure is executed when the UE moves outside the service area indicated by the third identification information received in the procedures of Chapters 3.2 to 3.4, the configuration update command message may further include information indicating that the S-NSSAI is unavailable in the current area.

[0403] 4. EMBODIMENT OF THE PRESENT EMBODIMENT An embodiment of one aspect of the present invention may be a combination of one or more of the procedures described in Chapter 3. For example, in this embodiment, after the initial registration procedure described in Chapter 3 is completed, an NSSAA procedure may be performed and a UE configuration update procedure may be executed.

[0404] Furthermore, one or more of mobility and periodic registration procedures may be performed based on the completion of the initial registration procedure by each device (UE and device in the core network). Alternatively, after the completion of the initial registration procedure described in Chapter 3, an NSSAA procedure may be performed and a network-initiated non-registration procedure may be performed.

[0405] An example of a specific embodiment of one aspect of the present invention will be described below. Note that the behaviors of multiple embodiments described below may be combined and implemented by each device.

[0406] In the following, the next section will describe the case where the UE moves from inside to outside the service area of ​​S-NSSAI, and the case where the UE moves from inside to outside the service area of ​​S-NSSAI.

[0407] [4.1. First embodiment] A first embodiment (hereinafter, this embodiment) will be described below. In this embodiment, an example of the behavior of the UE and each device when the UE moves from inside to outside the service area of ​​S-NSSAI will be described.

[0408] In the registration procedure of Chapter 3.2, the UE may receive a registration accept message including the second identity and / or the third identity associated with each S-NSSAI included in the allowed NSSAI or Pending NSSSAI, where each S-NSSAI included in the allowed NSSAI or Pending NSSSAI may not be associated with the fourth identity, the UE may be in a service area of ​​the S-NSSAI included in the allowed NSSAI or Pending NSSSAI, and the UE and each device may recognize this.

[0409] Next, for example, the AMF may perform the NSSAA procedure in Chapter 3.3 for a specific S-NSSAI (S-NSSAI#1-1) included in the Pending NSSAI. If the UE moves out of the service area of ​​the S-NSSAI while performing the NSSAA, the UE and / or each device of the core network may abort this procedure, and the UE may delete information on the S-NSSAI and / or the area associated with the S-NSSAI from the pending NSSAI. Here, the information on the area associated with the S-NSSAI may be the third identity received by the UE in the registration procedure.

[0410] This may cause the UE to recognize that it has moved outside the service area of ​​S-NSSAI#1-1 and that S-NSSAI#1-1 is unavailable.

[0411] Also, for example, the UE may establish a PDU session to a specific S-NSSAI (S-NSSAI#1-2) included in the allowed NSSAI. Here, if the UE moves out of the service area of ​​S-NSSAI#1-2, it may receive a non-registration request message including a rejected NSSAI as described in Chapter 3.5. Here, the rejected NSSAI in the non-registration request message may include S-NSSAI#1-2, and further, a third and / or fourth identification information may be associated with S-NSSAI#1-2.

[0412] This may cause the UE to move outside the service area of ​​S-NSSAI#1-2 and realize that S-NSSAI#1-2 is unavailable.

[0413] Furthermore, the UE may move from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1 at any time.

[0414] Furthermore, the UE may be permitted to initiate a PDU session establishment procedure and / or a PDU session modification procedure using the S-NSSAI#1-1 when the UE is located within the service area of ​​the S-NSSAI#1-1. Furthermore, the UE may initiate a PDU session establishment procedure and / or a PDU session modification procedure using the S-NSSAI#1-1 when the UE is located within the service area of ​​the S-NSSAI#1-1.

[0415] Furthermore, the UE may be configured such that when the UE is located within the service area of ​​S-NSSAI#1-1, initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 is permitted. In other words, the UE may be configured such that when the UE is located within the service area of ​​S-NSSAI#1-1, initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 is possible.

[0416] Furthermore, if the UE is located outside the service area of ​​S-NSSAI#1-1, the UE may be prohibited from initiating a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1.

[0417] Furthermore, the UE may be configured to prohibit initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 when the UE is located outside the service area of ​​S-NSSAI#1-1.Furthermore, the UE may be configured to prevent initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 when the UE is located outside the service area of ​​S-NSSAI#1-1.

[0418] Furthermore, the UE and / or the network may initiate a procedure for releasing a PDU session associated with S-NSSAI#1-1 and / or user plane resources associated with the PDU session based on the UE's movement from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1. Here, the procedure for releasing the PDU session associated with S-NSSAI#1-1 may be a PDU session release procedure. Furthermore, the network may be a device within the network. Specifically, the network may refer to the AMF or the SMF.

[0419] Furthermore, the UE may delete S-NSSAI#1-1 from the Allowed NSSAI stored by the UE based on movement from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1. Furthermore, the UE may store S-NSSAI#1-1 in a Rejected NSSAI based on movement from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1. Note that the Rejected NSSAI may be a Rejected NSSAI for managing S-NSSAIs that cannot be used in the current area.

[0420] Furthermore, the UE may delete S-NSSAI#1-1 from the Pending NSSAI stored by the UE based on movement from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1. Furthermore, the UE may store S-NSSAI#1-1 as included in a Rejected NSSAI based on movement from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1. Note that the Rejected NSSAI may be a Rejected NSSAI for managing S-NSSAIs that cannot be used in the current area.

[0421] Further, the UE and / or the network may discontinue execution of an NSSAA procedure using S-NSSAI#1-1 based on the UE moving from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1.

[0422] Furthermore, the UE and / or network may be configured to not execute an NSSAA procedure using S-NSSAI#1-1 based on the UE's movement from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1.Furthermore, the UE and / or network may be configured to prohibit execution of an NSSAA procedure using S-NSSAI#1-1 based on the UE's movement from within the service area of ​​S-NSSAI#1-1 to outside the service area of ​​S-NSSAI#1-1.

[0423] [4.1. Second embodiment] The second embodiment (hereinafter, the present embodiment) will be described below. In the present embodiment, an example of the behavior of each device when a UE that has performed a registration procedure outside the service area of ​​a specific S-NSSAI (S-NSSAI#2) moves into the service area of ​​the S-NSSAI#2 will be described.

[0424] A UE that performs a registration procedure outside the service area of ​​S-NSSAI#2 and receives a control message including a rejected NSSAI and third and / or fourth identification information from the core network stores the service area of ​​S-NSSAI#2 indicated by the third identification information.

[0425] Specifically, the UE may receive a registration acceptance message or a registration rejection message including the third and / or fourth identity information associated with each S-NSSAI included in the rejected NSSAI in the registration procedure of Chapter 3.2. Here, the UE may be in a service area of ​​the S-NSSAI included in the rejected NSSAI, and the UE and each device may recognize this.

[0426] Next, when the UE recognizes that it has moved into the service area of ​​the S-NSSAI, if the UE has moved into the service area of ​​any S-NSSAI included in the rejected NSSAI, the UE may delete the S-NSSAI from the rejected NSSAI and further store the S-NSSAI in the allowed NSSAI. For example, if the UE has moved into the service area of ​​S-NSSAI#2 included in the rejected NSSAI, the UE may delete S-NSSAI#2 from the rejected NSSAI and add S-NSSAI#2 to the allowed NSSAI.

[0427] Furthermore, the UE may transition to a state in which it is permitted or possible to start executing a PDU session establishment procedure and a PDU session modification procedure using S-NSSAI#2, and may perform a PDU session establishment procedure to S-NSSAI#2.

[0428] Furthermore, the UE may move from outside the service area of ​​S-NSSAI#1-1 to inside the service area of ​​S-NSSAI#1-1 at any time.

[0429] Furthermore, the UE may be permitted to initiate a PDU session establishment procedure and / or a PDU session modification procedure using the S-NSSAI#1-1 when the UE is located within the service area of ​​the S-NSSAI#1-1. Furthermore, the UE may initiate a PDU session establishment procedure and / or a PDU session modification procedure using the S-NSSAI#1-1 when the UE is located within the service area of ​​the S-NSSAI#1-1.

[0430] Furthermore, the UE may be configured such that when the UE is located within the service area of ​​S-NSSAI#1-1, initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 is permitted. In other words, the UE may be configured such that when the UE is located within the service area of ​​S-NSSAI#1-1, initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 is possible.

[0431] Furthermore, if the UE is located outside the service area of ​​S-NSSAI#1-1, the UE may be prohibited from initiating a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1.

[0432] Furthermore, the UE may be configured to prohibit initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 when the UE is located outside the service area of ​​S-NSSAI#1-1.Furthermore, the UE may be configured to prevent initiation of a PDU session establishment procedure and / or a PDU session modification procedure using S-NSSAI#1-1 when the UE is located outside the service area of ​​S-NSSAI#1-1.

[0433] Furthermore, the UE and / or the network may initiate a procedure to re-establish a PDU session associated with S-NSSAI#1-1 and / or user plane resources associated with the PDU session based on the UE's movement from outside the service area of ​​S-NSSAI#1-1 to inside the service area of ​​S-NSSAI#1-1. Here, the procedure to re-establish a PDU session associated with S-NSSAI#1-1 may be a PDU session establishment procedure using S-NSSAI#1-1. Furthermore, the network may be a device within the network. Specifically, the network may refer to the AMF or the SMF.

[0434] Furthermore, the UE may delete S-NSSAI#1-1 from the Rejected NSSAI stored by the UE based on movement from outside the service area of ​​S-NSSAI#1-1 to inside the service area of ​​S-NSSAI#1-1. Furthermore, the UE may store S-NSSAI#1-1 in the Allowed NSSAI based on movement from outside the service area of ​​S-NSSAI#1-1 to inside the service area of ​​S-NSSAI#1-1. Note that the Rejected NSSAI may be a Rejected NSSAI for managing S-NSSAIs that cannot be used in the current area.

[0435] Further, the UE and / or the network may initiate an NSSAA procedure using S-NSSAI#1-1 based on the UE moving from outside the service area of ​​S-NSSAI#1-1 to within the service area of ​​S-NSSAI#1-1.

[0436] Further, the UE and / or network may configure that an NSSAA procedure using S-NSSAI#1-1 is executed based on the UE's movement from outside the service area of ​​S-NSSAI#1-1 to inside the service area of ​​S-NSSAI#1-1.Further, the UE and / or network may configure that an NSSAA procedure using S-NSSAI#1-1 is permitted to be executed based on the UE's movement from outside the service area of ​​S-NSSAI#1-1 to inside the service area of ​​S-NSSAI#1-1.

[0437] Furthermore, the network may initiate a UE configuration update procedure or a de-registration procedure using at least the S-NSSAI#1-1 and the fourth identification information based on the UE moving from outside the service area of ​​the S-NSSAI#1-1 to inside the service area of ​​the S-NSSAI#1-1. In other words, the network may further send a configuration update command message or a de-registration request message including at least the S-NSSAI#1-1 and the fourth identification information to the UE based on the UE moving from outside the service area of ​​the S-NSSAI#1-1 to inside the service area of ​​the S-NSSAI#1-1. In this case, the fourth identification information may be information indicating that the S-NSSAI#1-1 is unavailable in the current area.

[0438] 5. Variations The program that runs on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of the embodiments according to the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

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

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

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

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

Claims

1. A UE (User Equipment) including a transceiver unit, a control unit, and a storage unit, The transmitting / receiving unit is Send a registration request message including UE capability information indicating that the UE supports a function related to a network slice service area; Receive a registration acceptance message including a single network slice selection assistance information (S-NSSAI) and information of a cell associated with the S-NSSAI; The control unit is storing the S-NSSAI and information of a cell associated with the S-NSSAI in the storage unit; When the S-NSSAI is included in an allowed NSSAI and the UE is outside a cell associated with the S-NSSAI, the control unit initiates a PDU session release procedure for an established PDU (Protocol Data Unit) session. The UE is characterized by:

2. The S-NSSAI is also associated with a configured NSSAI. The UE according to claim 1,

3. When the UE is outside the cell associated with the S-NSSAI, the PDU session establishment procedure for the S-NSSAI is not performed. The UE according to claim 1,

4. The PDU session is a PDU session for the S-NSSAI. The UE according to claim 1,

5. An AMF (Access and Mobility Management Function) having a transceiver, The transmitting / receiving unit is When updating S-NSSAI (Single Network Slice Selection Assistance Information) and information on a cell associated with the S-NSSAI for a UE including UE (User Equipment) capability information indicating that the UE supports a function related to a network slice service area in a registration request message, The configuration update command includes a new S-NSSAI and information about the cell associated with the S-NSSAI. AMF characterized by:

Images