UE(user equipment)

Abstract

To clarify UE and network behavior to efficiently support network slices that are time-limited.SOLUTION: The UE transmits a registration request message including information indicating that a temporary network slice is supported, receives a registration accept message or a registration reject message including allowedNSSAI or configuredNSSAI including S-NSSAI indicating the temporary network slice and a timer value corresponding to the S-NSSAI, starts a timer using the timer value, stores the S-NSSAI in the allowedNSSAI or the configuredNSSAI in the UE, deletes the S-NSSAI from the allowedNSSAI or the configuredNSSAI in the UE when the timer expires, and stores the S-NSSAI in rejectedNSSAI in the UE.SELECTED DRAWING: Figure 6

Description

[Technical Field]

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

[0002] The 3GPP (3rd Generation Partnership Project) is studying system architecture for a fifth-generation (5G) mobile communication system (also referred to as the 5G System or 5GS) (see Non-Patent Documents 1 to 3). 3GPP is currently discussing the extension of network slicing (also referred to as NS) functionality as part of its studies toward the specification of Release 18 (see Non-Patent Document 4). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18) [Non-patent document 2] 3GPP TS 23.502 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) [Non-patent document 3] 3GPP TS 24.501 V18.0.1 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) [Non-patent document 4] 3GPP TR 23.700-41 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of network slicing; Phase 3 (Release 18) Summary of the Invention [Problem to be solved by the invention]

[0004] In Non-Patent Document 4, Release 18 considers how to support 5GS when NS is time-limited, but the detailed behavior of UE and network is still unclear.

[0005] In view of the above, one aspect of the present invention is to clarify the detailed behavior of UE and network in order to efficiently support time-constrained NS. [Means for solving the problem]

[0006] A UE of one embodiment of the present invention is a UE (User Equipment) comprising a transceiver unit, a control unit, and a memory unit, wherein the transceiver unit transmits a registration request message including information indicating support for a temporary network slice, and receives a registration acceptance message or a registration rejection message including an allowed NSSAI or configured NSSAI including an S-NSSAI indicating a temporary network slice, and a timer value corresponding to the S-NSSAI, and the control unit starts a timer using the timer value, stores the S-NSSAI in the allowed NSSAI or configured NSSAI in the memory unit, and when the timer expires, deletes the S-NSSAI from the allowed NSSAI or configured NSSAI in the memory unit, and stores the S-NSSAI in the rejected NSSAI in the memory unit. [Effects of the Invention]

[0007] The present invention allows detailed UE and network behavior to be specified in order to efficiently support time-constrained NS. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). [Figure 2] FIG. 1 is a diagram illustrating the detailed configuration of a mobile communication system (EPS / 5GS). [Figure 3] FIG. 1 is a diagram illustrating the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Figure 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 10 is a diagram illustrating a registration procedure. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

[0012] In the following, these devices and functions may be referred to by abbreviating the symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

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

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

[0015] The 4G system EPS (Evolved Packet System) includes an access network _A and a core network _A, but may further include a UE and / or a PDN. The 5G system 5GS (5G System) includes a UE, an access network _B, and a core network _B, but may further include a DN.

[0016] A UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, or 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, or non-3GPP AN). A 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. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that a UE may be referred to as a user device or a terminal device.

[0017] Furthermore, access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are deployed in the E-UTRAN. Note that, hereinafter, the eNB 45 may be referred to by abbreviating the symbol eNB. If there are multiple eNBs, the eNBs are connected to each other, for example, via an X2 interface. Furthermore, one or more access points are deployed in the wireless LAN access network.

[0018] Furthermore, 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 deployed in the NG-RAN. Note that, hereinafter, the gNB 122 may be referred to by its symbol abbreviated as eNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs and connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in the 4G EPS system. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

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

[0020] NG-RAN refers to a radio access network that connects to 5GCN, and may use NR, E-UTRA, or both. In other words, NG-RAN may be E-UTRAN.

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

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

[0023] The core network_A corresponds to an EPC (Evolved Packet Core), which includes, 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), and an HSS (Home Subscriber Server).

[0024] Furthermore, the core network_B corresponds to a 5G Core Network (5GCN). In the 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), a Unified Data Management (UDM), etc. are arranged. Here, the 5GCN may be expressed as a 5GC.

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

[0026] 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 or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

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

[0028] Also, while FIG. 1 illustrates a case where the PDN and the DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services 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 mean connecting to a communication terminal or a server device located in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal or a server device located in the PDN. The PDN may be expressed as the DN, and the DN may be expressed as the PDN.

[0029] In addition, hereinafter, 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 sends or receives a message and / or performs 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 send or receive a message and / or perform a procedure.

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

[0031] Here, IP communication refers to data communication using IP, and data is transmitted and received using IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the IP packet structure. For example, non-IP communication may be data communication achieved by transmitting and receiving application data without an IP header, or may be user data transmitted and received by a UE with a different header, such as a MAC header or an Ethernet (registered trademark) frame header, added.

[0032] In addition, access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A may include devices not shown in Fig. 2. For example, core network _A and / or core network _B and / or PDN_A and / or 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.

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

[0034] The AAA server is a device that has authentication, authorization, and accounting functions and is connected to the AUSF directly or indirectly via another network device. The AAA server may be a network device within the core network. The AAA server may not be included in the core network_A and / or core network_B, but may be included in the PLMN and / or SNPN. 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 within the PLMN and / or SNPN managed by a third party.

[0035] In this document, when we refer to NW, it may mean the core network, the access network, or both.

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

[0037] Furthermore, the mobile communication system 1 may include devices and / or functions other than those described above, such as a Network Slice Selection Function (NSSF).

[0038] [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, as logical (virtual) hardware configured on general-purpose hardware, or 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.

[0039] Note that each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device / function mentioned below is configured with, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Furthermore, 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 devices / functions other than the device / function itself (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Furthermore, each memory unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Furthermore, each memory unit may store this information for each UE. Furthermore, when interworking between 5GS and EPS is performed, each memory unit can store control messages and user data transmitted and received between 5GS and / or devices / functions included in EPS. At this time, not only those transmitted and received via the N26 interface but also those transmitted and received without going through the N26 interface can be stored.

[0040] [2.1. UE Device Configuration] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 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.

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

[0042] The transceiver unit _A320 is a functional unit for wireless communication with a base station device (eNB or gNB) in the 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.

[0043] Explaining in detail with reference to Figure 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.

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

[0045] [2.2. gNB device configuration] Next, an example of the gNB device configuration will be described using Figure 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.

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

[0047] 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 send and receive user data and / or control information between the AMF and / or UPF using the network connection unit _B520.

[0048] The transceiver unit _B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information to and from the UE using the transceiver unit _B530.

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

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

[0051] [2.3. AMF device configuration] Next, an example of the AMF device configuration will be explained using 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.

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

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

[0054] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with a gNB via the N2 interface by using the network connection unit _A620, can communicate with a UDM via the N8 interface, can communicate with an SMF via the N11 interface, and can communicate with a PCF via the N15 interface. The AMF can also send and receive NAS messages with a UE via the N1 interface by using the network connection unit _A620. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via a 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with an MME via the N26 interface by using the network connection unit _A620.

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

[0056] The AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and protecting the integrity of NAS messages, registration management (RM) functions, connection management (CM) functions, reachability management functions, mobility management functions for UEs, etc., transferring SM (Session Management) messages between the UE and the SMF, access authentication (Access Authorization) functions, security anchor functionality (SEA), security context management (SCM), a function to support the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function to support sending and receiving NAS signals with the UE via the N3IWF, and a function to authenticate UEs connected via the N3IWF.

[0057] In addition, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. The RM state includes an unregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with 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 with the network, and therefore the UE can receive services that require registration with the network. Note that the RM state may also 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.

[0058] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context or 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 perform registration procedures other than the registration procedure for initial registration, and / or service request procedures.

[0059] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which UE_A10's location information is not known to the network, or a state in which UE_A10 is unreachable from the network. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or may establish a 5GMM context by performing the registration procedure.

[0060] In addition, connection management manages the CM state for each UE. 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 an N2 interface connection or an N3 interface connection. 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 an N2 interface connection and / or an N3 interface connection.

[0061] Furthermore, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may include 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 include 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). Note that the non-connected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.

[0062] The CM state may be expressed as a 5GMM mode. In this case, the unconnected state may be expressed as a 5GMM-IDLE 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-IDLE mode over 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.

[0063] 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 among multiple NSIs.

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

[0065] [2.4. SMF device configuration] Next, an example of the SMF device configuration 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.

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

[0067] The network connection unit _B720 is a functional unit for the SMF to connect with the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can send and receive user data and / or control information between the AMF, and / or UPF, and / or PCF, and / or UDM using the network connection unit _B720.

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

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

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

[0071] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be explained using Figure 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.

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

[0073] 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 within the 5G AN. In other words, the UPF can use the network connection unit _B720 to transmit and receive user data and / or control information between the base station device (gNB), and / or SMF, and / or DN within the 5G AN.

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

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

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

[0077] 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 a function for converting non-IP communication and IP communication. Furthermore, 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.

[0078] The user plane refers to user data transmitted and received between a UE and a 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 the 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 referred to as the U-Plane.

[0079] Furthermore, the control plane refers to control messages transmitted and received to control UE communications, etc. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and 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 NG RAN and the N2 interface. Hereinafter, the control plane may be referred to as the control plane or the C-Plane.

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

[0081] [2.6. Other Devices and / or Functions and / or Terms Used in This Embodiment] Next, other devices, functions, terms, identification information sent, received, stored, and managed by each device, and / or messages will be described.

[0082] A network refers to at least a portion of an access network _B, a core network _B, and a DN. Furthermore, one or more devices included in at least a portion of an access network _B, a core network _B, and a 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 devices within the network (network devices and / or control devices) transmit, receive, receive, and / or process messages. Conversely, when a device within the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

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

[0084] 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. Note that each procedure may be initiated by the UE or the network (NW).

[0085] Furthermore, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in procedures 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, etc.

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

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

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

[0089] Furthermore, 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 via a communication method other than IP.

[0090] Furthermore, a PDU (Protocol 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 to and from a DN by establishing a PDU session via an access network _B and a core network _B. Here, this external gateway may be a UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session.

[0091] Each device (UE, and / or access network device, and / or core network device) may associate one or more pieces of identification information with a PDU session and manage them. These pieces of identification information may include one or more of the following: DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode (also referred to as SSC mode), or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with the PDU sessions may be the same or different.

[0092] Furthermore, the DNN (Data Network Name) may be identification information that identifies the core network and / or an external network such as a DN. Furthermore, the DNN can also 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).

[0093] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and can be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data will be transmitted and received using IPv4. If IPv6 is specified, it indicates that data will be transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be transmitted and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be transmitted and received to an application server or the like in the 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 also include IP. IP can be specified if the UE is capable of using both IPv4 and IPv6.

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

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

[0096] A PLMN to which a 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.

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

[0098] The requested PLMN refers to the network to which the UE sends a message when the UE sends the message. Specifically, it may be the PLMN selected by the UE when the UE sends the message. The requested PLMN is the PLMN requested by the UE, and may be the current PLMN. When the UE is in a registered state, the requested PLMN may be the registered PLMN.

[0099] An NPN (Non-public network) is a network intended for non-public specifications. There are two types of NPNs: SNPN (Stand-alone non-public network) and PNI-NPN (Public network integrated non-public network). SNPNs and PNI-NPNs may be deployed in 5GS. In this document, when referring to an NPN, it can refer to either an SNPN or a PNI-NPN, or both.

[0100] A Stand-alone Non-Public Network (SNPN) is a network operated by an NPN operator and does not rely on network functions provided by a PLMN. In other words, an SNPN is a network independent of a PLMN and can only be accessed by specific UEs. An SNPN may be identified by a PLMN ID and a Network Identifier (NID).

[0101] Here, the PLMN ID identifying the SNPN does not need to be unique, for example, one or more PLMN IDs reserved for use in private networks may be used for the NPN.

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

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

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

[0105] A PNI-NPN (Public network integrated non-public network) is an NPN deployed with the support of a PLMN, i.e., a network that uses the capabilities of a PLMN to implement non-public specifications.

[0106] Onboarding services in SNPN allow an MS (UE) to access the SNPN for onboarding using default UE credentials.

[0107] The registration procedure for onboarding services in the SNPN may be an initial registration for onboarding services in the SNPN. Additionally, or alternatively, the registration procedure for onboarding services in the SNPN may be a registration procedure for registration update due to mobility when the UE is registered for onboarding services in the SNPN. The registration procedure for onboarding services in the SNPN may also be referred to as SNPN onboarding registration.

[0108] In the registration procedure for the SNPN onboarding service, MM-based slice admission control for the S-NSSAI for the SNPN onboarding service may not be performed by the AMF or the NF in the core network.

[0109] The onboarding service in the SNPN may also allow the UE to connect to the SNPN indicating that onboarding is permitted using default UE credentials for primary authentication such that the UE is configured with one or more entries in a "list of subscriber data." Note that the onboarding service in the SNPN may be expressed as an onboarding service or as onboarding.

[0110] Furthermore, when a UE is registered for onboarding services in an SNPN, services other than the onboarding services in the SNPN may not be available, and when a UE is not registered for onboarding services in an SNPN, the onboarding services in the SNPN may not be available.

[0111] Here, when the UE performs registration for the onboarding service in the SNPN, the UE may indicate SNPN onboarding registration in the 5GS registration type information element. Note that the registration procedure for the onboarding service may also be referred to as the onboarding procedure.

[0112] Next, an onboarding network (ON) may refer to a network where onboarding is permitted. The onboarding network may also be a network that provides initial registration and / or access to a UE for onboarding. The onboarding network may also be expressed as ONN.

[0113] Here, the onboarding network may be a PLMN and may be expressed as ON-PLMN. Furthermore, the onboarding network may be an SNPN and may be expressed as ON-SNPN (onboarding SNPN).

[0114] The onboarding network may also be a PLMN or an onboarding SNPN that enables remote provisioning for registered UEs.

[0115] Next, a provisioning server is an entity that provides credentials to a UE to enable an SNPN connection.

[0116] Here, the provisioning server may exist in the onboarding network, or may exist in an external DN different from the onboarding network.

[0117] Next, a Subscription Owner SNPN (SO-SNPN) may be an SNPN that has a subscription for a UE. The SO-SNPN may also be an SNPN that provides subscription data to a UE via a provisioning server during an onboarding procedure. The ON-SNPN and the SO-SNPN may be the same SNPN or different SNPNs.

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

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

[0120] Here, an NST is a logical representation of one or more NFs associated with resource requirements for providing the required communication services and capabilities. In other words, an NSI may be a collection of multiple NFs within the core network_B190. 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. The NFs configured in an NS may or may not be devices shared with other NSs.

[0121] A UE and / or a device in the network can 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 APNs. The UE usage type is a parameter value included in the UE registration information and 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.

[0122] Furthermore, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying an NS. S-NSSAI may consist of only SST (Slice / Service type), or may consist of both SST and SD (Slice Differentiator). Here, SST is information indicating the expected behavior of an NS in terms of functions and services. Furthermore, SD may be information that interpolates SST when selecting one NSI from multiple NSIs indicated by SST. S-NSSAI may be information specific to each PLMN or SNPN, or may be standard information common to PLMNs or SNPNs.

[0123] In addition, the S-NSSAI may be transmitted and received between each device using the 5GS S-NSSAI IE, in which case the S-NSSAI may be composed of the S-NSSAI (SST and / or SD) associated with the current PLMN or SNPN, and / or the S-NSSAI (SST and / or SD) of the HPLMN (if any, for example, when the UE is roaming or when the current PLMN or SNPN is a VPLMN or SNPN).

[0124] The network may also store one or more S-NSSAIs in the registration information of the UE as default S-NSSAIs. If an S-NSSAI is a default S-NSSAI, the network may provide an NS related to the UE if the UE does not send a valid S-NSSAI to the network in the registration request message.

[0125] 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 the registered PLMN or SNPN, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN or HSNPN to which the S-NSSAI is mapped. One or more S-NSSAIs stored in the UE and / or 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 the S-NSSAI of the HPLMN to which the S-NSSAI is mapped.

[0126] Also, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAIs. 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 or SNPN. The NSSAI may also 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) to a PLMN and an EPLMN, or to an SNPN and an ESNPN.

[0127] A mapped S-NSSAI is an S-NSSAI of an 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 for the rejected NSSAI and / or the S-NSSAI included in the pending NSSAI.

[0128] If a roaming scenario of an SNPN is supported, the mapped S-NSSAI may be the S-NSSAI of the HSNPN mapped to the S-NSSAI of the registered SNPN.

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

[0130] The S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. Furthermore, during roaming, the S-NSSAI requiring an NSSAA may be an S-NSSAI other than that of an HPLMN or HSNPN, where the S-NSSAI of an HPLMN or HSNPN requiring an NSSAA that is managed by a core network and / or a core network device becomes the mapped S-NSSAI.

[0131] The core network and / or core network device may store an S-NSSAI requiring 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 requiring an NSSAA in association with information indicating whether an 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 requiring an NSSAA as information unrelated to the access network.

[0132] Also, a configured NSSAI is an NSSAI that is provisioned and stored in the UE. The UE may store a configured NSSAI for each PLMN or SNPN. The UE may store a configured NSSAI in association with a PLMN or SNPN.

[0133] In this document, a configured NSSAI associated with a PLMN may be expressed as a configured NSSAI for the PLMN, or a configured NSSAI of the PLMN, or a configured NSSAI for the PLMN, or a configured NSSAI associated with the PLMN. Similarly, a configured NSSAI associated with an SNPN may be expressed as a configured NSSAI for the SNPN, or a configured NSSAI of the SNPN, or a configured NSSAI for the SNPN, or a configured NSSAI associated with the SNPN.

[0134] Also, a UE may not be associated with a PLMN and may store a configured NSSAI that is valid for all PLMNs, and may refer to such a configured NSSAI as the "default configured NSSAI." Similarly, a UE may not be associated with an SNPN and may store a configured NSSAI that is valid for all SNPNs, and may refer to such a configured NSSAI as the "default configured NSSAI." A UE may not be associated with a PLMN or SNPN and may store a configured NSSAI that is valid for all PLMNs and SPNNs, and may refer to such a configured NSSAI as the "default configured NSSAI."

[0135] A configured NSSAI may be associated with multiple PLMNs or SNPNs, where the multiple PLMNs may be EPLMNs and the multiple SNPNs may be ESNPNs.

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

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

[0138] Furthermore, one or more S-NSSAIs of an HPLMN or HSNPN to which the configured S-NSSAI is mapped may be expressed as "one or more mapped S-NSSAIs for a configured NSSAI of a PLMN or SNPN" or "one or more mapped S-NSSAIs for a configured NSSAI of a PLMN or SNPN."

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

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

[0141] The requested NSSAI is an NSSAI provided by 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 configured NSSAI stored by the UE.

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

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

[0144] In other words, the requested NSSAI may be an S-NSSAI included in a configured NSSAI associated with one or more current PLMNs, or an S-NSSAI included in an allowed NSSAI associated with one or more current PLMNs, or a combination of the two. More specifically, the allowed NSSAI associated with the current PLMN may be an allowed NSSAI associated with the current PLMN and the current access type. Furthermore, the requested NSSAI may be a 5GS requested NSSAI.

[0145] In addition, the S-NSSAI included in the requested NSSAI may be an S-NSSAI stored by the UE and not included in the rejected NSSAI associated with the current PLMN or SNPN, and / or an S-NSSAI stored by the UE and not included in the pending NSSAI associated with the current PLMN or SNPN, or an S-NSSAI stored by the UE and not included in the fourth rejected NSSAI associated with the current PLMN or SNPN.

[0146] Furthermore, the S-NSSAI included in the requested NSSAI may be an S-NSSAI for which the back-off timer associated with that S-NSSAI and / or its mapped S-NSSAI is not running in the UE.

[0147] Also, the allowed NSSAI is information indicating one or more network slices to which the UE is allowed. In other words, the allowed NSSAI is information identifying a network slice to which the network allows the UE to connect. The allowed NSSAI may be an allowed NSSAI stored in the UE and / or the NW, or may be an allowed NSSAI transmitted from the NW to the UE. In this case, the allowed NSSAI may refer to the allowed NSSAI IE of 3GPP.

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

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

[0150] Note that a list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN and included in the allowed NSSAI IE may be referred to as the Allowed NSSAI, and a list of mapped S-NSSAIs that are S-NSSAIs of the HPLMN or HSNPN to which the S-NSSAIs of the current PLMN or SNPN are mapped may be referred to as the list of mapped S-NSSAIs of the Allowed NSSAI. Here, the list of mapped S-NSSAIs of the Allowed NSSAI may be 3GPP mapped S-NSSAI(s) for the allowed NSSAI for a PLMN. Similarly, the Allowed NSSAI may mean 3GPP allowed NSSAI for a PLMN or an SNPN.

[0151] The UE and / or 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 NW may further manage the allowed NSSAI in association with a registration area.

[0152] Furthermore, the UE and / or NW may store and manage an allowed NSSAI associated with a PLMN or an SNPN as information of the UE. An allowed NSSAI may be associated with multiple PLMNs, where the multiple PLMNs may be EPLMNs, and the multiple SNPNs may be ESNPNs.

[0153] In this document, an allowed NSSAI associated with a PLMN or SNPN and an access type may be expressed as an "allowed NSSAI for a PLMN or SNPN and an access type" or an "allowed NSSAI for an access type of a PLMN or SNPN."

[0154] An S-NSSAI included in an allowed NSSAI may be expressed as an allowed S-NSSAI. The allowed S-NSSAI may be transmitted or received using the S-NSSAI IE, in which case the allowed S-NSSAI (SST and / or SD) may be configured to include the S-NSSAI and the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any, for example, when the UE is roaming or when the associated PLMN or SNPN is a VPLMN or VSNPN).

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

[0156] Furthermore, one or more S-NSSAIs of an HPLMN or HSNPN to which the allowed S-NSSAI is mapped may be expressed as "one or more mapped S-NSSAIs for an allowed NSSAI of a PLMN or SNPN" or "one or more mapped S-NSSAIs for an allowed NSSAI of a PLMN or SNPN."

[0157] Furthermore, the rejected NSSAI is information indicating one or more network slices that the UE is not permitted to use or request. In other words, the rejected NSSAI is information identifying a network slice to which the network does not permit the UE to connect. The rejected NSSAI transmitted from the NW to the UE may be included in the rejected NSSAI IE or the extended rejected NSSAI IE.

[0158] The rejected NSSAI transmitted and received using the rejected NSSAI IE may be information including one or more combinations of the S-NSSAI (SST and / or SD) and a rejection reason value (rejected S-NSSAI).The rejected NSSAI transmitted and received using the Extended rejected NSSAI IE may be information including one or more combinations of the S-NSSAI (SST and / or SD) and the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any, for example, when the UE is roaming or when the associated PLMN or SNPN is a VPLMN or VSNPN) and a rejection reason value (rejected S-NSSAI) in the case of roaming.

[0159] The Extended rejected NSSAI IE may include one or more sets of Rejected S-NSSAs and / or NSSAIs (5GS Partial extended rejected NSSAI list), and the set of Rejected S-NSSAIs may include information indicating the type of this set.

[0160] The information indicating the type of set may be, for example, information indicating that the set includes one or more rejected S-NSSAIs (SST and / or SD) with associated back-off timer values, or information indicating that the set includes one or more rejected S-NSSAIs (SST and / or SD) without associated back-off timer values.

[0161] If the information indicating the type of set is information indicating that this set includes one or more rejected S-NSSAIs with associated back-off timer values, the set of rejected S-NSSAIs may include a back-off timer value.

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

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

[0164] 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, or a registration reject message, or in an RRC message including an NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI.

[0165] When the UE is roaming, the rejected NSSAI may be transmitted using the Rejected NSSAI IE or may be transmitted using the Extended rejected NSSAI IE. The Extended rejected NSSAI IE may include one or more rejected S-NSSAI (IEs) consisting of the S-NSSAI (SST and / or SD) of the current PLMN or SNPN, the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN), and a rejection reason value. The UE may understand that the received S-NSSAI of the current PLMN or SNPN together with the received mapped S-NSSAI has been rejected from the NW. On the other hand, the Rejected NSSAI IE may include a rejected S-NSSAI IE with the S-NSSAI of the current PLMN or SNPN and a rejection reason value, and the UE may understand that the request to the NW for the S-NSSAI associated with the received S-NSSAI of the current PLMN or SNPN, or the S-NSSAI of the HPLMN or HSNPN, has been rejected.

[0166] The rejected NSSAI may be any one of the first to fifth rejected NSSAIs, one or more mapped S-NSSAIs for the first rejected NSSAI, one or more mapped S-NSSAIs for the second rejected NSSAI, one or more mapped S-NSSAIs for the fourth rejected NSSAI, and one or more mapped S-NSSAIs for the fifth rejected NSSAI, or a combination thereof. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI. The rejected S-NSSAI may be transmitted and received between devices using the S-NSSAI IE, and the S-NSSAI IE indicating the rejected NSSAI may include the S-NSSAI and the mapped S-NSSAI.

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

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

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

[0170] When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, it includes one or more S-NSSAIs that were rejected because they are unavailable in the current PLMN or the current SNPN, among the S-NSSAIs included in the requested NSSAI transmitted by the UE to the NW. In this case, the first 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 not available in the current PLMN or SNPN" or may be information indicating that the S-NSSAI associated with the rejection reason value is unavailable in the current PLMN or SNPN. The S-NSSAI included in the first rejected NSSAI may be expressed as a first rejected S-NSSAI.

[0171] If the first rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the first rejected NSSAI may be transmitted and received in a rejected NSSAI IE or an extended rejected NSSAI IE. The rejected NSSAI IE or the extended rejected NSSAI IE may include at least one combination of the S-NSSAI of the current PLMN or SNPN and a rejection reason value. If the UE is roaming, the combination may further include a mapped S-NSSAI, which is the S-NSSAI of the HPLMN.

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

[0173] The first rejected NSSAI may apply to the entire registered PLMN or registered SNPN. The UE and / or NW may treat the first rejected NSSAI and the S-NSSAI included in the first rejected NSSAI as information independent of the access type. That is, the first rejected NSSAI may be information valid for both 3GPP access and non-3GPP access.

[0174] The UE may delete the first rejected NSSAI from its storage when it transitions to an unregistered state in both 3GPP access and non-3GPP access with respect to the current PLMN. In other words, when the UE transitions to an unregistered state with respect to the current PLMN via one access, or when it successfully registers to a new PLMN via one access, or when it fails to register to the new PLMN via one access and transitions to an unregistered state, and 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 with respect to the current PLMN via one access, and the UE is registered (registered state) with the current PLMN via the other access, the UE does not need to delete the first rejected NSSAI.

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

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

[0177] If the second rejected NSSAI is a rejected NSSAI sent from the NW to the UE, it includes one or more S-NSSAIs that the UE included in the requested NSSAI that were rejected because they are not available in the current registration area. In this case, the second rejected NSSAI may be transmitted and received in a rejected NSSAI IE or an extended rejected NSSAI IE. The rejected NSSAI IE or the extended rejected NSSAI IE may include at least one combination of the S-NSSAI of the current PLMN or SNPN and a rejection reason value. If the UE is roaming, the combination may also include a mapped S-NSSAI, which is the S-NSSAI of the HPLMN.

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

[0179] The second rejected NSSAI may be valid within the current registration area and may apply 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 that access from its memory.

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

[0181] The third rejected NSSAI is a set of one or more S-NSSAIs that require an NSSAA and for which the NSSAA for that 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. In this case, the rejection reason value 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 referred to as the third rejected S-NSSAI.

[0182] If the third rejected NSSAI is an NSSAI transmitted from the NW to the UE, the third rejected NSSAI may be transmitted or received using a rejected NSSAI IE or an extended rejected NSSAI IE.

[0183] The third rejected NSSAI may apply to the registered PLMN or the registered SNPN, or may apply to the registered PLMN and / or EPLMN, or may apply to the registered SNPN and / or ESNPN, or may apply to all PLMNs or SNPNs. The third rejected NSSAI applying to all PLMNs 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 or HSNPN.

[0184] 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 a 5GS rejected NSSAI for the failed or revoked NSSAA, a rejected S-NSSAI for the failed or revoked NSSAA, or an S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA.

[0185] The third rejected NSSAI is a rejected NSSAI that identifies a slice that the UE rejected due to an NSSAA failure or revocation 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 an NSSAA failure.

[0186] The third rejected NSSAI is information independent of the access type. Specifically, when the UE stores the third rejected NSSAI, the UE does not need to 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 can transmit a registration request message including the S-NSSAI included in the third rejected NSSAI based on a UE policy.

[0187] Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which it 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.

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

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

[0190] The fourth rejected NSSAI is information including one or more S-NSSAIs for which the maximum number of UEs per network slice has been reached. The fourth rejected NSSAI may be an NSSAI stored by the UE and / or the NW, or may be an NSSAI transmitted from the NW to the UE.

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

[0192] When the fourth rejected NSSAI is transmitted from the NW to the UE, the fourth rejected NSSAI may include one or more pieces of information including at least one of an S-NSSAI (SST and / or SD), a mapped S-NSSAI (SST and / or SD) (if any), a rejection reason value, and a back-off timer value. In this case, the rejection reason value may be "S-NSSAI not available due to maximum number of UEs reached" or may be information indicating that the S-NSSAI associated with the rejection reason value can be notified as an Allowed NSSAI or that the maximum number of allowable UEs has been reached.

[0193] The fifth rejected NSSAI may be a rejected NSSAI different from the first to fourth rejected NSSAIs. The fifth rejected NSSAI may be a rejected NSSAI referred to for a temporary network slice. For example, the fifth rejected NSSAI may be a rejected NSSAI for the temporary network slice.

[0194] Here, the rejection reason value may be a rejection reason value included in the rejected NSSAI. 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 using one or more S-NSSAIs and / or one or more mapped S-NSSAIs associated with the back-off timer value, the S-NSSAI of the current PLMN or SNPN associated with the one or more S-NSSAIs and / or the mapped S-NSSAI.

[0195] The fourth rejected NSSAI may apply to the registered PLMN and / or EPLMN, or to the registered SNPN and / or ESNPN, or to one or more PLMNs or SNPNs to which the TAIs included in the TA list (TAI list or registration area) belong.

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

[0197] If the fourth rejected NSSAI is an NSSAI transmitted from the NW to the UE, the fourth rejected NSSAI may be transmitted or received using a rejected NSSAI IE or an extended rejected NSSAI IE.

[0198] When the first to fourth rejected NSSAIs are transmitted or received using the rejected NSSAI IE or the extended rejected NSSAI IE, the rejected NSSAI IE and the extended rejected NSSAI IE may include a list of rejected S-NSSAIs.

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

[0200] When the first to fourth rejected NSSAIs are transmitted and received using an Extended rejected NSSAI IE, the list of rejected S-NSSAIs included in the Extended rejected NSSAI IE may be the 5GS Partial extended rejected NSSAI list.

[0201] The rejected S-NSSAI list includes a first type list that does not include a back-off timer value and a second type list that includes a back-off timer value that applies to all S-NSSAIs included in the rejected S-NSSAI list. The Extended rejected NSSAI IE may include one or more first type lists and / or one or more second type lists.

[0202] The first type list may include information indicating that the list is of the first type and one or more 5GS Rejected S-NSSAIs. The Rejected S-NSSAI may include the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and a corresponding rejection reason value. Furthermore, the Rejected S-NSSAI may include a mapped S-NSSAI (SST and / or SD).

[0203] The information indicating that the list is of a first type may mean that the list includes one or more S-NSSAIs without corresponding back-off timer values, in other words, the list does not include back-off timer values ​​corresponding to one or more S-NSSAIs included in the list.

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

[0205] The information indicating that this list is of the second type may be information indicating that this list includes one or more S-NSSAIs and corresponding backoff timer values, and that the backoff timer value applies to all S-NSSAIs.

[0206] In addition, the back-off timer value included in the second type list may be a value that applies to all S-NSSAIs included in the same second type list.

[0207] The pending NSSAI may be a pending NSSAI of 5GS. The pending NSSAI may be an NSSAI stored by the UE and / or the NW, or may be an NSSAI transmitted and received between the NW and the UE.

[0208] If the pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI may be sent or received using a pending NSSAI IE configured with one or more S-NSSAI IEs, and the S-NSSAI IE may include the S-NSSAI (SST and / or SD) and the mapped S-NSSAI (SST of the mapped HPLMN or HSNPN and / or SD of the mapped HPLMN or HSNPN) (if any, for example, when the UE is roaming or when the associated PLMN or SNPN is a VPLMN or VSNPN).

[0209] The pending NSSAI may apply to the entire registered PLMN or registered SNPN, or to the registered PLMN and one or more ESPMNs of the registered PLMN, or to the registered SNPN and one or more ESPMNs of the registered SNPN.

[0210] The UE and / or NW may treat the S-NSSAI included in the pending NSSAI as information independent of the access type, that is, the pending NSSAI may be information common to 3GPP access and non-3GPP access.

[0211] The pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE is pending a procedure. Specifically, while the UE stores the pending NSSAI, the UE does not initiate a registration request procedure for an S-NSSAI included in the pending NSSAI or a mapped S-NSSAI of the pending NSSAI.

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

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

[0214] In other words, a UE that stores a first pending NSSAI does not store a mapped S-NSSAI for the first pending NSSAI, and the S-NSSAI configured in the first pending NSSAI stored by the UE is the S-NSSAI of the HPLMN or HSNPN regardless of whether the UE is roaming or not.

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

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

[0217] In other words, when roaming, there may be one or more mapped S-NSSAIs for the second pending NSSAI. The S-NSSAI configured for the second pending NSSAI may be the S-NSSAI of the current PLMN or SNPN, regardless of whether roaming or not.

[0218] In this document, a reference to a pending NSSAI may mean the first pending NSSAI, the second pending NSSAI, both pending NSSAIs, or any other pending NSSAI.

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

[0220] A registration area is a collection of one or more TAs assigned to a UE by the AMF. 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 signals for tracking area update. In other words, a registration area may be a group of information indicating areas 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.

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

[0222] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), 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.

[0223] Management of the maximum number of UEs connecting to a slice refers to managing and / or controlling the maximum number of UEs that can be simultaneously registered to a network slice or S-NSSAI, or managing and / or controlling the maximum number of UEs that can simultaneously establish a PDU session using a network slice or S-NSSAI. Management of the maximum number of UEs connecting to a slice may be NSAC (network slice admission control) of 5GS. NSAC may also be expressed as slice admission control.

[0224] Management and / or control of the maximum number of UEs that can be simultaneously registered to a network slice or an S-NSSAI may be expressed as MM-based slice admission control (Mobility management based slice admission control). Management and / or control of the maximum number of UEs that can simultaneously establish a PDU session using a network slice or an S-NSSAI may be expressed as SM-based slice admission control (Session management based slice admission control). Slice admission control may refer to NSAC (Network Slice Admission Control).

[0225] Here, a UE registering to a network slice or an S-NSSAI may be stored by including an S-NSSAI indicating the network slice in an allowed NSSAI. A device in a network that supports the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can be simultaneously registered to a network slice or an S-NSSAI can store, for each S-NSSAI, whether management of the maximum number of UEs connected to a slice is required, and can further check during the registration procedure whether the number of registered UEs has reached a constant number, which is the maximum number.

[0226] Furthermore, each device that supports the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can be simultaneously registered in a network slice or S-NSSAI may be capable of storing a fourth rejected NSSAI. In this document, the maximum number of UEs connected to a slice may be expressed as the maximum number of UEs connected per slice, or the maximum number of UEs that can be registered in a network slice or S-NSSAI, or the maximum number of UEs, or a constant.

[0227] SSC (Session and Service Continuity) is a technology for maintaining a session and / or a service. Here, a session may refer to a PDU session established between a UE and a network, and a service may refer to a service provided to a UE through a PDU session established between a UE and a network. Various modes may exist.

[0228] In other words, the SSC (Session and Service Continuity) mode indicates the mode of service session continuity supported by the system and / or each device in 5GC. More specifically, it may be a mode indicating the type of service session continuity supported by the PDU session established between UE_A10 and the anchor point.

[0229] Here, the anchor point may be a UPGW or a UPF. The UPF may be a terminating user-plane function (TUPF). The TUPF is a UPF at the end of each interface and has a PDU session anchor function. In other words, the anchor point may be a PDU session anchor.

[0230] For SSC, switching the anchor point may be referred to as anchor relocation and / or PDU session anchor change. These may also be referred to as anchor relocation procedure and PDU session anchor change procedure. Furthermore, anchor relocation may be a concept that includes a change of PDU session anchor without a change of network slice and / or S-NSSAI, or may be a concept that includes a change of PDU session anchor with a change of network slice and / or S-NSSAI.

[0231] In anchor relocation, the PDU session established in the initial state may be referred to as the first PDU session, and the PDU session established after the procedure is completed may be referred to as the second PDU session.

[0232] The SSC mode may be a mode indicating the type of service session continuity set for each PDU session. In other words, the SSC mode may be associated with the PDU session.

[0233] And / or, the SSC mode may be associated with an anchor point and controlled so that it cannot be changed while the PDU session is established. The SSC mode associated with the PDU session may not be changed during the lifetime of the PDU session. Each SSC mode is described below.

[0234] SSC mode 1 is a service session continuity mode in which the same UPF is maintained as the anchor point regardless of the access technology, such as the RAT (Radio Access Technology) or cell, used by UE_A10 when connecting to the network. More specifically, SSC mode 1 may be a mode that realizes service session continuity without changing the anchor point used by the established PDU session even when UE_A10 mobility occurs.

[0235] SSC mode 2 is a service session continuation mode in which, when a PDU session includes one anchor point, the PDU session is first released and then a new PDU session is established. More specifically, when an anchor point relocation occurs, SSC mode 2 deletes the PDU session and then establishes a new PDU session.

[0236] SSC mode 2 is a service session continuity mode in which the same UPF is maintained as the anchor point only within the serving area of ​​the UPF. More specifically, SSC mode 2 may be a mode that realizes service session continuity without changing the UPF used by the established PDU session as long as UE_A10 is within the serving area of ​​the UPF. Furthermore, SSC mode 2 may be a mode that realizes service session continuity by changing the UPF used by the established PDU session when UE_A10 mobility occurs, such as moving out of the serving area of ​​the UPF.

[0237] Here, the serving area of ​​a UPF may be an area in which one UPF can provide a service session continuity function, or may be a subset of an access network such as a RAT or cell used when UE_A10 connects to a network. Furthermore, the subset of an access network may be a network consisting of one or more RATs and / or cells, or may be a TA.

[0238] In the case of session continuation in SSC mode 2, if a change in S-NSSAI is not permitted, it may be referred to as first SSC mode 2. On the other hand, in the case of session continuation in SSC mode 2, if a change in S-NSSAI is permitted, it may be referred to as second SSC mode 2. In other words, a case of session continuation in SSC mode 2 while changing the S-NSSAI or network slice may be referred to as second SSC mode 2. In further other words, a case of continuing an SSC mode 2 PDU session while changing the S-NSSAI or network slice may be referred to as second SSC mode 2. When simply referred to as SSC mode 2, it may mean first SSC mode 2 and / or second SSC mode 2.

[0239] SSC mode 3 is a service session continuity mode that allows a PDU session to be established between a new anchor point and a UE for the same DN without releasing the PDU session between the UE and the anchor point.

[0240] SSC mode 3 is a service session continuity mode that allows a new PDU session and / or communication path to be established via a new UPF for the same DN before disconnecting the PDU session and / or communication path established between UE_A10 and UPF. Furthermore, SSC mode 3 may be a service session continuity mode that allows UE_A10 to be multi-homing.

[0241] And / or, SSC mode 3 may be a mode in which service session continuity is permitted using multiple PDU sessions and / or UPFs associated with the PDU sessions. In other words, in the case of SSC mode 3, each device may realize service session continuity using multiple PDU sessions, or may realize service session continuity using multiple UPFs.

[0242] In the case of session continuation in SSC mode 3, if changing the S-NSSAI is not permitted, it may be referred to as first SSC mode 3. On the other hand, in the case of session continuation in SSC mode 3, if changing the S-NSSAI is permitted, it may be referred to as second SSC mode 3. In other words, the case of session continuation in SSC mode 3 while changing the S-NSSAI or network slice may be referred to as second SSC mode 3. In further words, the case of continuing a PDU session in SSC mode 3 while changing the S-NSSAI or network slice may be referred to as second SSC mode 3. When simply referred to as SSC mode 3, it may mean first SSC mode 3 and / or second SSC mode 3.

[0243] SSC mode 4 may be a second SSC mode 2.

[0244] In other words, SSC mode 4 is a service session continuation mode in which, when a PDU session includes one anchor point, the PDU session is first released and then established while changing the S-NSSAI or network slice. More specifically, when an anchor point relocation occurs, SSC mode 4 is a mode in which the PDU session is deleted once while changing the S-NSSAI or network slice, and then a new PDU session is established.

[0245] SSC mode 4 is a service session continuity mode in which the same UPF is maintained as the anchor point while changing the S-NSSAI or network slice only within the serving area of ​​the UPF. More specifically, SSC mode 4 may be a mode that realizes service session continuity without changing the UPF used by the established PDU session while changing the S-NSSAI or network slice as long as UE_A10 is within the serving area of ​​the UPF. Furthermore, SSC mode 4 may be a mode that realizes service session continuity by changing the UPF used by the established PDU session while changing the S-NSSAI or network slice when UE_A10 mobility occurs, such as moving out of the serving area of ​​the UPF.

[0246] Here, the serving area of ​​a UPF may be an area in which one UPF can provide a service session continuity function, or may be a subset of an access network such as a RAT or cell used when UE_A10 connects to a network. Furthermore, the subset of an access network may be a network consisting of one or more RATs and / or cells, or may be a TA.

[0247] SSC mode 5 may be the second SSC mode 3.

[0248] In other words, SSC mode 5 is a service session continuity mode that allows a PDU session to be established between a new anchor point and a UE for the same DN without releasing the PDU session between the UE and the anchor point while changing the S-NSSAI or network slice.

[0249] SSC mode 5 is a service session continuity mode that allows a new PDU session and / or communication path to be established via a new UPF for the same DN before disconnecting the PDU session and / or communication path established between UE_A10 and UPF while changing the S-NSSAI or network slice. Furthermore, SSC mode 5 may be a service session continuity mode that allows UE_A10 to be multi-homing.

[0250] In addition, SSC mode 5 may be a mode in which service session continuity is permitted using multiple PDU sessions and / or UPFs associated with the PDU sessions. In other words, in the case of SSC mode 5, each device may realize service session continuity using multiple PDU sessions, or may realize service session continuity using multiple UPFs.

[0251] The subscription information may also include restrictions on simultaneous registration of network slices. The subscription information is provided to the serving AMF (AMF serving the UE, the AMF to which the UE is connected) as a UE subscription in the form of NSSRG (Network Slice Simultaneous Registration Group) information. The subscription information may include, for each S-NSSAI, a subscribed DNN list and one default DNN, and / or information indicating whether the S-NSSAI is marked as a default subscribed S-NSSAI, and / or information indicating whether the S-NSSAI is associated with an NSSAA, and / or NSSRG information. The subscription information may be information sent by the UDM to the AMF. In other words, the UDM may be information managing the subscription information.

[0252] Furthermore, the subscription information for a UE may include NSSRG information for each S-NSSAI. The NSSRG information may be information that restricts which S-NSSAIs can be simultaneously provided to the UE in the Allowed NSSAI. If multiple S-NSSAIs have associated NSSRG information, one or more S-NSSAIs included in the allowed NSSAI may share at least one (common) NSSRG. Furthermore, if NSSRG information is present in the subscription information, each S-NSSAI included in the subscription information may be associated with at least one NSSRG. When the AMF receives subscription information for a UE that includes NSSRG information, the Allowed NSSAI for that UE can include only one or more S-NSSAIs that have a common NSSRG. Furthermore, the subscription information that includes NSSRG information may include at least one default S-NSSAI. Also, when receiving a requested NSSAI from the UE, an AMF that supports processing functions related to NSSRG and / or NSSRG information may determine whether the S-NSSAI of the HPLMN can be provided together with the allowed NSSAI based on the NSSRG information for the S-NSSAI of the HPLMN.

[0253] Furthermore, the UE may transmit information indicating whether it supports these features (subscription-based restrictions to simultaneous registration of network slices feature) by including it in a 5GMM capability IE included in a registration request message. In other words, the information indicating whether it supports the feature of subscription-based restrictions to simultaneous registration of network slices may be included as the 41st identification information. Furthermore, the NW may transmit information indicating whether it supports these features (subscription-based restrictions to simultaneous registration of network slices feature) by including it in a 5GS network feature support IE included in a registration accept message or a registration reject message. In other words, the information indicating whether it supports the feature of subscription-based restrictions to simultaneous registration of network slices may be included as the 51st identification information.

[0254] In addition, when the serving AMF provides the configured NSSAI to the UE, if the UE indicates that it supports subscription-based restrictions on concurrent network slice registrations, the AMF may provide the UE with NSSRG information for the S-NSSAI of the HPLMN that exists in the mapping information of the configured NSSAI. A UE that receives the NSSRG information may include the S-NSSAI with a common NSSRG in the requested NSSAI.

[0255] Furthermore, the first identification information may be information indicating a network slice. Furthermore, the first identification information may be information indicating a network slice requested by the UE. Furthermore, the first identification information may be a requested NSSAI.

[0256] Furthermore, the second identification information may be information indicating a capability of the UE (UE capability). Furthermore, the second identification information may be information indicated as 5GMM capability or information included in the 5GMM capability. Furthermore, the second identification information may be information indicating whether the UE supports temporary network slices. Furthermore, the second identification information may be information indicating that the UE supports temporary network slices. Furthermore, the second identification information may be information indicating that the UE does not support temporary network slices. Furthermore, the second identification information may be information indicating whether the UE has a capability to process timing information related to a network slice. Furthermore, the second identification information may be information indicating that the UE has a capability to process timing information related to a network slice. Furthermore, the second identification information may be information indicating that the UE does not have a capability to process timing information related to a network slice. Furthermore, the second identification information may be information indicating whether the UE has a capability to process information related to a time or a period when a network slice is available. Furthermore, the second identification information may be information indicating that the UE has a capability to process information related to a time or a period when a network slice is available. The second identification information may also be information indicating that the UE does not have the ability to process information regarding the time or period when the network slice is available.

[0257] Furthermore, the third identification information may be information indicating a type of registration requested. Furthermore, the third identification information may be information indicated as a 5GS registration type, or may be information included in the 5GS registration type and / or 5GS registration type. Furthermore, the third identification information may indicate an initial registration, a mobility registration updating, a periodic registration updating, an emergency registration, an SNPN onboarding registration, a disaster roaming mobility registration updating, or a disaster roaming initial registration.

[0258] The fourth identification information may be information indicating a request to update the timing information, or may be information indicating a request to transmit the updated timing information.

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

[0260] Incidentally, transmitting and receiving at least one of the first to fourth identification information may mean transmitting and receiving the fifth identification information.

[0261] Furthermore, the eleventh identification information may be information related to a network slice. Furthermore, the eleventh identification information may be information indicating a network slice transmitted from a network. The eleventh identification information may be one or more NSSAIs. The eleventh identification information may be one or more S-NSSAIs indicating a temporary network slice. Specifically, the eleventh identification information may be an allowed NSSAI, a configured NSSAI, a rejected NSSAI, an extended rejected NSSAI, and / or a pending NSSAI transmitted from the network to the UE. In other words, the eleventh identification information may be an allowed NSSAI, a configured NSSAI, a rejected NSSAI, an extended rejected NSSAI, and / or a pending NSSAI including one or more S-NSSAIs indicating a temporary network slice. Furthermore, the eleventh identification information may include a thirteenth identification information and / or a fourteenth identification information.

[0262] The 12th identification information may be information indicating a network capability (NW capability). The 12th identification information may be information indicated as 5GS network feature support or information included in 5GS network feature support. The 12th identification information may be information indicating whether the network supports temporary network slices. The 12th identification information may be information indicating that the network supports temporary network slices. The 12th identification information may be information indicating that the network does not support temporary network slices. The 12th identification information may be information indicating whether the network has the capability to process timing information related to a network slice. The 12th identification information may be information indicating that the network has the capability to process timing information related to a network slice. The 12th identification information may be information indicating that the network does not have the capability to process timing information related to a network slice. The 12th identification information may be information indicating whether the network has the capability to process information related to a time or period when a network slice is available. The 12th identification information may be information indicating that the network has the capability to process information related to a time or period when a network slice is available. The 12th identification information may also be information indicating that the network does not have the ability to process information regarding the time or period when the network slice is available.

[0263] Furthermore, the 13th identification information may be a timer value. Furthermore, the 13th identification information may be information regarding a period during which the network slice is available (which may also be referred to as a network slice availability time, network slice availability, or timing information regarding the network slice). Furthermore, the 13th identification information may be a value common to all UEs, a value common to each UE group, or a value different for each UE. Furthermore, the 13th identification information may be information included in the 11th identification information. Furthermore, the 13th identification information may be a timer value corresponding to the 11th identification information.

[0264] Furthermore, the fourteenth identification information may be information indicating whether the setting information is valid. For example, the fourteenth identification information may be information indicating whether the eleventh identification information and / or the thirteenth identification information is valid. In other words, the fourteenth identification information may be information corresponding to the eleventh identification information and / or the thirteenth identification information. Furthermore, the fourteenth identification information may be information included in the eleventh identification information and / or the thirteenth identification information.

[0265] Furthermore, the 15th identification information may be a reason value indicating that the UE request is rejected. Furthermore, the 15th identification information may be a 5GMM cause or a 5GSM cause. Furthermore, the 15th identification information may indicate that the network slice is unavailable, or that the network slice is unavailable because it is a temporary network slice, or that the network slice is permanently unavailable because it is a temporary network slice, or that the network slice is unavailable because it has been disabled, or that the network slice is unavailable because it is no longer valid, or that the network slice is unavailable because the network slice's availability time or period has passed, or that the network slice is unavailable because the network slice's availability time or period has passed and the network slice has been disabled, or that the network slice is unavailable because the network slice's availability time or period has passed and the network slice is no longer valid. The 15th identification information may also indicate that there is no network slice available, or that the network slice is not available, or that the network slice is not valid, or that the network slice is invalid, or that the network slice has timed out.

[0266] The sixteenth identification information is information that includes at least one of the eleventh to fifteenth identification information.

[0267] Incidentally, transmitting and receiving at least one of the eleventh to fifteenth identification information may mean transmitting and receiving the sixteenth identification information.

[0268] [3. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include MM procedures and SM procedures, including registration procedures, and / or setting update procedures, and / or deregistration procedures, and / or PDU session release procedures. Each procedure will be described below.

[0269] In each embodiment, as shown in FIG. 2, the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software). However, the contents described in this embodiment are also applicable to cases where these are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between these devices, 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.

[0270] 3.1. Registration Procedure Next, the registration procedure will be described with reference to FIG. 11. In this chapter, this registration procedure may be simply referred to as this procedure. The registration procedure is a procedure initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with a network, it can execute this procedure at any time, for example, when powered on. In other words, if the UE is in a deregistered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (5GMM-REGISTED 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 unregistered state) for 3GPP access and the registration state for non-3GPP access.

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

[0272] A UE may initiate a registration procedure when it moves to a TA outside its current registration area. In other words, a UE may initiate a registration procedure when it moves to a TA different from the TAs indicated in its TA list. Furthermore, a UE may initiate a registration procedure when a PDU session is disconnected or invalidated, requiring a context update for each device. Furthermore, a UE may initiate a registration procedure when a change occurs in the UE's capability information and / or preferences regarding PDU session establishment. Furthermore, a UE may initiate a registration procedure periodically. Furthermore, a UE may initiate a registration procedure based on the completion of a registration procedure, the completion of a PDU session establishment procedure, or information received from the network during each procedure. Furthermore, a UE may initiate this procedure after performing the procedures described in Chapter 3 one or more times. However, the UE may also perform the registration procedure at any timing.

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

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

[0275] Note that the UE may or may not store each NSSAI and / or S-NSSAI included in each NSSAI described in Chapter 2.6 at the time of initiating this procedure. Furthermore, the UE may initiate this procedure if it has stored each NSSAI and / or S-NSSAI included in each NSSAI described in Chapter 2.6 at the time of initiating this procedure. Furthermore, the UE may execute this procedure one or more times after storing each NSSAI and / or S-NSSAI included in each NSSAI acquired from the network by executing this procedure.

[0276] The details of the registration process described below are applicable to both.

[0277] First, the UE starts the registration procedure by transmitting an NAS message including a registration request message to the AMF (S600) (S602) (S604). Specifically, the UE transmits an RRC message including an NAS message including the registration request message to a base station device (also referred to as a 5G AN or gNB) (S600). Note that the registration request message is an NAS message transmitted and received on the N1 interface. Also, the RRC message may be a control message transmitted and received between the UE and the base station device. Also, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

[0278] Here, the UE may transmit at least one of the first to fifth identification information in the registration request message and / or the RRC message, where the first to fifth identification information may be as described in Chapter 2.6.

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

[0280] In addition, the UE may select and decide whether to send at least one of the first to fifth identification information to the network based on the UE's capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, and / or identification information sent and received in procedures performed prior to this procedure, etc.

[0281] Furthermore, when the UE supports a temporary network slice, or when the UE has the capability to process timing information related to the network slice, or when the UE has the capability to process information related to the time or period when the network slice is available, the UE may set the second identification information to indicate that the UE supports a temporary network slice, or that the UE has the capability to process timing information related to the network slice, or that the UE has the capability to process information related to the time or period when the network slice is available, and may transmit the second identification information.

[0282] Furthermore, when the UE does not support a temporary network slice, or when the UE does not have the capability to process timing information regarding the network slice, or when the UE does not have the capability to process information regarding the time or period when the network slice is available, the UE may set the second identification information to indicate that the UE does not support a temporary network slice, or when the UE does not have the capability to process timing information regarding the network slice, or when the UE does not have the capability to process information regarding the time or period when the network slice is available, and may transmit the second identification information.

[0283] Furthermore, when the UE does not support a temporary network slice, or when the UE does not have the ability to process timing information regarding the network slice, or when the UE does not have the ability to process information regarding the time or period when the network slice is available, the UE may not need to transmit second identification information regarding whether the UE supports a temporary network slice, or whether the UE has the ability to process timing information regarding the network slice, or whether the UE has the ability to process information regarding the time or period when the network slice is available.

[0284] In addition, when the UE requests an update of the timing information or requests transmission of updated timing information, the UE may set the fourth identification information to indicate that it requests an update of the timing information or that it requests transmission of updated timing information, and transmit the fourth identification information.

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

[0286] Next, when the base station device receives an RRC message including a NAS message including a registration request message, the base station device selects an AMF to forward the received RRC message, and / or the registration request message, and / or the NAS message (S602), and forwards them to the selected AMF (S604). The base station device may select an AMF based on identification information included in the registration request message, the NAS message, and / or the RRC message. Specifically, when the base station device receives at least one of the first to fifth identification information, the base station device may select an AMF based on the received identification information. For example, the base station device may select an AMF included in the network slice identified by the first identification information, or may select an AMF having connectivity to the network slice identified by the first identification information. The base station device may also select an AMF having NW functions corresponding to the UE capability information indicated by the second identification information. The AMF selection method is not limited to this, and the base station device may select an AMF based on other conditions.

[0287] Next, when the AMF receives a registration request message or the like from the base station device, the AMF can execute a first condition determination. The first condition determination is for determining whether the network accepts the UE's request. When the AMF determines that the first condition determination is true, the AMF may execute the procedures from S610 to S612. Also, when the AMF determines that the first condition determination is false, the AMF may execute the procedure of S610.

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

[0289] If the first condition determination is true, the control message transmitted and received at S610 may be a Registration accept message, and if the first condition determination is false, the control message transmitted and received at S610 may be a Registration accept message or a Registration reject message, unless otherwise specified. The control message may be transmitted in a NAS message. Furthermore, the NAS message may be transmitted in an RRC message.

[0290] Furthermore, the first condition determination may be performed based on the reception of a registration request message, etc. received from a base station device, and / or each identification information contained in the registration request message, etc., 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.

[0291] For example, if the network does not permit or reject a request from the UE, the first condition determination may be determined as true, and if the network does not permit or reject a request from the UE, the first condition determination may be determined as false. Furthermore, if the network does not permit or reject some of the UE requests, even if there is a UE request that is not permitted, the first condition determination may be determined as true. Furthermore, if the network does not permit or reject all of the UE requests, the first condition determination may be determined as false. Furthermore, if the network to which the UE is registered and / or a device within the network supports a function requested by the UE, the first condition determination may be determined as true, and if the function requested by the UE is not supported, the first condition determination may be determined as false. Furthermore, if the received identification information is permitted, the first condition determination may be determined as true, and if the received identification information is not permitted, the first condition determination may be determined as false.

[0292] Furthermore, the AMF may include at least one of the identification information items 11 to 16 in a control message and transmit the control message to the UE via the base station device. Here, the identification information items 11 to 16 may be as described in Chapter 2.6. By transmitting the identification information items and / or the control message, the AMF may indicate whether the network supports each function, whether the UE request has been accepted, or 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 permission to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0293] Furthermore, when the AMF receives at least one of the first to fifth identification information from the UE, the AMF may transmit a control message including at least one of the eleventh to sixteenth identification information. Furthermore, even when the AMF receives a registration request message or the like that does not include at least one of the first to fifth identification information from the UE, the AMF may transmit a control message including at least one of the eleventh to sixteenth identification information.

[0294] Furthermore, the AMF may determine whether to include at least one of the identification information items 11 to 16 in the control message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, and / or identification information sent and received in procedures performed prior to this procedure, etc.

[0295] The AMF may also indicate to the UE that the UE's request has been accepted by sending a registration acceptance message, or may indicate to the UE that the UE's request has been rejected by sending a registration rejection message.

[0296] In addition, based on whether the network supports temporary network slices, or whether the network has the ability to process timing information regarding network slices, or whether the network has the ability to process information regarding the time or period when the network slice is available, the AMF may determine whether to include at least one of the 11th to 16th identification information in the control message and / or the content of the 11th to 16th identification information to be transmitted.

[0297] Furthermore, the network slice that is the subject of the determination of whether to allow or disallow the use of a temporary network slice may be only the network slice identified by the S-NSSAI included in the first identification information, or it may be the network slice identified by the S-NSSAI included in the first identification information and the S-NSSAI not included in the first identification information.

[0298] Also, for example, when the network supports a temporary network slice, or when the network has the capability to process timing information regarding the network slice, or when the network has the capability to process information regarding the time or period when the network slice is available, the AMF may set the 12th identification information to indicate that the network supports a temporary network slice, or the network has the capability to process timing information regarding the network slice, or the network has the capability to process information regarding the time or period when the network slice is available, and send the 12th identification information.

[0299] In addition, when the network does not support temporary network slices, or when the network does not have the ability to process timing information regarding the network slices, or when the network does not have the ability to process information regarding the time or period when the network slice is available, the AMF may set the 12th identification information to indicate that the network does not support temporary network slices, or when the network does not have the ability to process timing information regarding the network slices, or when the network does not have the ability to process information regarding the time or period when the network slice is available, and transmit the 12th identification information.

[0300] In addition, when the network supports a temporary network slice, or when the network has the capability to process timing information regarding the network slice, or when the network has the capability to process information regarding the time or period when the network slice is available, the AMF may notify the UE that the network supports a temporary network slice, or that the network has the capability to process timing information regarding the network slice, or that the network has the capability to process information regarding the time or period when the network slice is available, by sending the 11th identification information, and / or the 13th identification information, and / or the 14th identification information.

[0301] In addition, when the network does not support temporary network slices, or when the network does not have the ability to process timing information regarding network slices, or when the network does not have the ability to process information regarding the time or period when the network slice is available, the AMF may not send the 13th identification information and / or the 14th identification information.

[0302] In addition, when the network does not support temporary network slices, or when the network does not have the ability to process timing information regarding the network slices, or when the network does not have the ability to process information regarding the time or period when the network slice is available, the AMF may notify the UE that the network does not support temporary network slices, or that the network does not have the ability to process timing information regarding the network slices, or that the network does not have the ability to process information regarding the time or period when the network slice is available, by not sending the 11th identification information and / or the 13th identification information and / or the 14th identification information.

[0303] Furthermore, when a network does not support temporary network slices, or when the network does not have the ability to process timing information regarding network slices, or when the network does not have the ability to process information regarding the time or period when a network slice is available, the network (e.g., AMF) may not be able to decide whether to allow or disallow the use of temporary network slices.

[0304] In addition, when the network does not support temporary network slices, or when the network does not have the ability to process timing information regarding network slices, or when the network does not have the ability to process information regarding the time or period when the network slice is available, the network (e.g., AMF) may discard or ignore the fourth identification information.

[0305] Furthermore, when the use of a temporary network slice is permitted, the AMF sets and stores the S-NSSAI that identifies the temporary network slice as an allowed NSSAI and / or a configured NSSAI, and the AMF may set and start a timer value indicating a period during which the network slice or S-NSSAI is available in its own timer. Note that starting this timer may be performed after the procedure is completed or may be started during the procedure. Here, if the S-NSSAI is included in the rejected NSSAI and / or pending NSSAI, the AMF may delete the S-NSSAI from the rejected NSSAI and / or pending NSSAI. Furthermore, the AMF may set the S-NSSAI that identifies the network slice to an eleventh identity, set a timer value indicating a period during which the network slice or S-NSSAI is available in a thirteenth identity, and set information indicating that these configuration information are valid in a fourteenth identity, and transmit these to the UE. In addition, the AMF may set the S-NSSAI that identifies the network slice to the 11th identification information and send it to the UE, but may not send the 13th identification information indicating the timer value indicating the period during which the network slice or S-NSSAI is available and / or the 14th identification information indicating that these setting information are valid to the UE.

[0306] Furthermore, when the use of a temporary network slice is permitted, the AMF sets and stores the S-NSSAI that identifies the temporary network slice as an allowed NSSAI and / or configured NSSAI, and the AMF may set the S-NSSAI that identifies the network slice to an eleventh identity, set a timer value indicating the period during which the network slice or S-NSSAI is available to a thirteenth identity, and set information indicating that these configuration information are valid to a fourteenth identity, and transmit the same to the UE. In this case, the AMF may not set the timer value indicating the period during which the network slice or S-NSSAI is available to its own timer or start the timer. Here, if the S-NSSAI is included in the rejected NSSAI and / or pending NSSAI, the AMF may delete the S-NSSAI from the rejected NSSAI and / or pending NSSAI.

[0307] Furthermore, when the AMF transmits the 13th identification information and also starts the AMF timer, the timer value set in the 13th identification information and the timer value set in the AMF timer may be the same value or different values. Furthermore, when the timer value set in the 13th identification information and the timer value set in the AMF timer are different values, the AMF may set the timer value set in the AMF timer to be greater than the timer value set in the 13th identification information.

[0308] Furthermore, when the use of a temporary network slice is not permitted, the AMF may set and store the S-NSSAI that identifies the temporary network slice as a rejected NSSAI, and may set the S-NSSAI that identifies the network slice to the 11th identity and send it to the UE. Here, when the S-NSSAI is included in the allowed NSSAI and / or the configured NSSAI and / or the pending NSSAI, the AMF may delete the S-NSSAI from the allowed NSSAI and / or the configured NSSAI and / or the pending NSSAI.

[0309] Furthermore, when the use of a temporary network slice is not permitted, the AMF may set and store the S-NSSAI identifying the temporary network slice as a rejected NSSAI, and may set the S-NSSAI identifying the network slice to an 11th identification and transmit it to the UE, and may set a predetermined value (e.g., 0) as a timer value indicating the period during which the network slice or S-NSSAI is available to a 13th identification, and may set information indicating that these configuration information are not valid to a 14th identification and transmit it to the UE. In this case, the AMF may stop the timer corresponding to the network slice or S-NSSAI if it is running. Here, if the S-NSSAI is included in the allowed NSSAI and / or configured NSSAI and / or pending NSSAI, the AMF may delete the S-NSSAI from the allowed NSSAI and / or configured NSSAI and / or pending NSSAI.

[0310] Furthermore, when the use of a temporary network slice is not permitted, the AMF may set and store the S-NSSAI identifying the temporary network slice as an allowed NSSAI and / or configured NSSAI, and may set the S-NSSAI identifying the network slice to an 11th identification and transmit it to the UE, and may set a predetermined value (e.g., 0) as a timer value indicating the period during which the network slice or S-NSSAI is available to a 13th identification, and may set information indicating that these configuration information are not valid to a 14th identification and transmit it to the UE. In this case, the AMF may stop the timer corresponding to the network slice or S-NSSAI if it is running. Here, when the S-NSSAI is included in the rejected NSSAI and / or pending NSSAI, the AMF may delete the S-NSSAI from the rejected NSSAI and / or pending NSSAI.

[0311] Furthermore, when the AMF receives the fourth identification information, it may transmit the eleventh identification information, and / or the thirteenth identification information, and / or the fourteenth identification information. Note that, if the AMF has already transmitted the thirteenth identification information to the UE and receives the fourth identification information, it may transmit the thirteenth identification information including an updated timer value. Furthermore, if the AMF has already transmitted the thirteenth identification information to the UE and receives the fourth identification information, the AMF may not transmit the eleventh identification information, and / or the thirteenth identification information, and / or the fourteenth identification information if the timer value has not been updated.

[0312] The AMF may also send at least one of the 11th to 16th identification information regardless of whether or not the 4th identification information has been received.

[0313] Furthermore, if the AMF has transmitted at least one of the eleventh to sixteenth identification information in this procedure, the AMF may update the configuration of the UE by transmitting at least one of the eleventh to sixteenth identification information by a control message in an MM procedure other than this procedure (for example, a configuration update command message in a configuration update procedure). In other words, the content of the identification information transmitted and received in the control message in this procedure and the content of the identification information transmitted and received in the control message in an MM procedure other than this procedure may be different or the same.

[0314] For example, the 11th identification information transmitted and received in a control message in this procedure may indicate an NSSAI (e.g., an allowed NSSAI and / or a configured NSSAI) including an S-NSSAI that identifies a temporary network slice, and the 11th identification information transmitted and received in a control message in an MM procedure different from this procedure may indicate an NSSAI (e.g., a rejected NSSAI) including an S-NSSAI that identifies a temporary network slice, thereby changing the UE's configuration information.

[0315] In addition, the 11th identification information transmitted and received in a control message in this procedure may indicate an NSSAI (e.g., a rejected NSSAI) including an S-NSSAI that identifies a temporary network slice, and the 11th identification information transmitted and received in a control message in an MM procedure different from this procedure may change the UE's configuration information by indicating an NSSAI (e.g., an allowed NSSAI and / or a configured NSSAI) including an S-NSSAI that identifies a temporary network slice.

[0316] Furthermore, the 13th identification information transmitted and received in a control message in this procedure may indicate a value other than 0 as a timer value indicating a period during which the network slice or S-NSSAI is available, and the 13th identification information transmitted and received in a control message in an MM procedure other than this procedure may indicate a value other than 0 as a timer value indicating a period during which the network slice or S-NSSAI is available, thereby changing the UE settings. Furthermore, the 13th identification information transmitted and received in a control message in this procedure may indicate a value other than 0 as a timer value indicating a period during which the network slice or S-NSSAI is available, and the 13th identification information transmitted and received in a control message in an MM procedure other than this procedure may indicate a value other than 0 as a timer value indicating a period during which the network slice or S-NSSAI is available, thereby changing the UE settings.

[0317] Furthermore, the UE settings may be changed by the 14th identification information transmitted and received in a control message in this procedure indicating that the configuration information is valid, and the 14th identification information transmitted and received in a control message in an MM procedure different from this procedure indicating that the configuration information is not valid. Furthermore, the UE settings may be changed by the 14th identification information transmitted and received in a control message in this procedure indicating that the configuration information is not valid, and the 14th identification information transmitted and received in a control message in an MM procedure different from this procedure indicating that the configuration information is valid.

[0318] In addition, when a timer started during or after the completion of this procedure expires and the S-NSSAI associated with that timer is stored in the allowed NSSAI and / or configured NSSAI and / or pending NSSAI, the AMF may delete the S-NSSAI from the stored allowed NSSAI and / or configured NSSAI and / or pending NSSAI.

[0319] In addition, when a timer started during or after the completion of this procedure expires, the AMF may store the S-NSSAI associated with that timer in the rejected NSSAI if that S-NSSAI is not stored in the rejected NSSAI.

[0320] In addition, when a timer started during or after the completion of this procedure expires and the S-NSSAI associated with that timer is stored in the allowed NSSAI and / or configured NSSAI, the AMF may continue to store the S-NSSAI together with information indicating that the S-NSSAI is not valid or invalid, without deleting it from the stored allowed NSSAI and / or configured NSSAI.

[0321] The AMF may also initiate an SM procedure (e.g., a PDU session release procedure) and / or an MM procedure (e.g., a deregistration procedure) after a timer started during or after the completion of this procedure expires.

[0322] For example, when the AMF initiates a PDU session release procedure after the timer expires, the AMF may notify the SMF of the network slice related to the expired timer and / or the S-NSSAI identifying the network slice, and / or information indicating that there is no available network slice, or that the network slice is not available, or that the network slice is not valid or invalid, or that the network slice has timed out, or that the network slice has expired. The SMF receiving this information may send a PDU session release command to the UE via the AMF using the network slice or S-NSSAI, including a PDU session ID identifying a PDU session using the network slice or S-NSSAI related to the expired timer, and / or a cause value (5GSM cause), and / or eleventh identification information. Here, the cause value (5GSM cause) may indicate that there is no available network slice, or that the network slice is not available, or that the network slice is not valid, or that the network slice is invalid, or that the network slice has timed out, or that the network slice has expired.Furthermore, the cause value (5GSM cause) may indicate operator determined barring, insufficient resources, user authentication or authorization failed, regular deactivation, network failure, reactivation requested, out of LADN service area, insufficient resources for a specific slice and DNN, or insufficient resources for a specific slice. Furthermore, the eleventh identification information may indicate an allowed NSSAI and / or a configured NSSAI and / or a rejected NSSAI.

[0323] Furthermore, when the AMF initiates a PDU session release procedure after the timer expires, the AMF may notify the SMF of the network slice related to the expired timer and / or the S-NSSAI identifying the network slice, and / or information indicating that there is no available network slice, that the network slice is not available, that the network slice is not valid or invalid, that the network slice has timed out, or that the network slice has expired. The SMF receiving this information may implicitly release one or more (or all) PDU sessions and / or resources using the network slice or S-NSSAI related to the expired timer.

[0324] Furthermore, when the AMF initiates a deregistration procedure after the timer expires, the AMF may transmit a deregistration request message to the UE, the deregistration request message including at least one of the 11th, 13th, 14th, 15th, 16th, and 18th identification information. For example, when the AMF transmits the 13th identification information, the AMF may indicate a predetermined value (e.g., 0). When the AMF transmits the 14th identification information, the AMF may indicate that the configuration information is not valid or invalid as the 14th identification information. When the AMF transmits the 11th identification information, the AMF may include a network slice or an S-NSSAI associated with the expired timer in a rejected NSSAI. The AMF may also transmit a deregistration request message to the UE, the deregistration request message including information indicating a request for re-registration. The AMF may also request the UE to transmit a requested NSSAI including an S-NSSAI indicating another network slice by transmitting a deregistration request message to the UE.

[0325] The AMF may also implicitly deregister the UE after the timer expires without initiating a deregistration procedure.

[0326] In addition, when the AMF sends the 11th identification information, and / or the 13th identification information, and / or the 14th identification information to the UE in this procedure, and starts its own timer, if the timer expires, it monitors for a predetermined time whether the UE performs a PDU session release procedure and / or a deregistration procedure, and if the UE does not initiate the PDU session release procedure and / or the deregistration procedure within the predetermined time, it may initiate the above-mentioned SM procedure (e.g., a PDU session release procedure) and / or MM procedure (e.g., a deregistration procedure).

[0327] In addition, when the AMF sends the 11th identification information, and / or the 13th identification information, and / or the 14th identification information to the UE in this procedure, and starts its own timer, if the timer expires, it monitors for a predetermined time whether the UE executes a PDU session release procedure and / or a deregistration procedure, and if the PDU session release procedure and / or a deregistration procedure is initiated by the UE within that predetermined time, it may not initiate the above-mentioned SM procedure (e.g., a PDU session release procedure) and / or MM procedure (e.g., a deregistration procedure).

[0328] In addition, when the AMF sends the 11th identification information, and / or the 13th identification information, and / or the 14th identification information to the UE in this procedure, and starts its own timer, if the timer expires, the AMF may immediately start the above-mentioned SM procedure (e.g., a PDU session release procedure) and / or MM procedure (e.g., a deregistration procedure) without monitoring whether the PDU session release procedure and / or deregistration procedure is performed by the UE.

[0329] Furthermore, when the third identification information indicates SNPN onboarding registration (onboarding registration is performed), the thirteenth identification information and / or the fourteenth identification information does not need to be transmitted.

[0330] Furthermore, when a network slice that is the target of a temporary network slice is already unavailable, and the AMF receives a registration request message from the UE including a requested NSSAI that includes an S-NSSAI that identifies the network slice, the AMF may include the 11th identification information and / or the 15th identification information in the control message and transmit the control message to the UE. Here, the 11th identification information may include the S-NSSAI. In this case, when the network slice becomes available in the future, the AMF may include in the control message date and time information indicating when the network slice will become available and / or information indicating the period until the network slice becomes available, and transmit the control message.

[0331] In addition, the network slice that is the target of the temporary network slice may not be subject to NSAC (MM-based slice admission control and / or SM-based slice admission control).

[0332] Also, when the network slice that is the target of the temporary network slice is the network slice that is the target of the NSAC, the AMF may send an S-NSSAI that identifies that network slice to the NSACF. In other words, when the AMF receives a requested NSSAI that includes an S-NSSAI that identifies a network slice that is the target of the temporary network slice and the target of the NSAC, the AMF may send that S-NSSAI to the NSACF.

[0333] Also, when the AMF receives an MM message (e.g., a registration request message or a deregistration request message) including a requested NSSAI that includes an S-NSSAI that identifies a network slice that is the target of temporary network slicing and the target of NSAC, and a timer in the AMF for that S-NSSAI or the network slice identified by that S-NSSAI has expired, the AMF may send to the NSACF that that S-NSSAI and / or the network slice identified by that S-NSSAI has become unavailable, and / or that the timer for that S-NSSAI or the network slice identified by that S-NSSAI has expired, and / or that the network slice identified by that S-NSSAI or the S-NSSAI has become unavailable due to the expiration of the timer for that S-NSSAI or the network slice identified by that S-NSSAI. Then, the NSACF that receives these control information may suspend NSAC (MM-based slice admission control) for the S-NSSAI or the network slice identified by the S-NSSAI. Then, the NSACF may transmit to the AMF that NSAC for the S-NSSAI and / or the network slice identified by the S-NSSAI has been suspended. Then, the AMF that receives these control information may transmit to the UE an MM message (e.g., a registration accept message, a registration reject message, or a deregistration accept message) including that NSAC for the S-NSSAI and / or the network slice identified by the S-NSSAI has been suspended. A UE that receives these control information may recognize the received content.

[0334] The AMF also sends a requested S-NSSAI that identifies the network slice that is the target of the temporary network slice and is the target of the NSAC. When an MM message (e.g., a registration request message or a deregistration request message) including an NSSAI is received and a timer in the AMF for the S-NSSAI or the network slice identified by the S-NSSAI has expired, the AMF may transmit an MM message (e.g., a registration accept message, a registration reject message, or a deregistration accept message) to the UE, including information that the S-NSSAI and / or the network slice identified by the S-NSSAI or the S-NSSAI has become unavailable, and / or that the timer for the S-NSSAI or the network slice identified by the S-NSSAI has expired, and / or that the network slice identified by the S-NSSAI or the S-NSSAI has become unavailable due to the expiration of the timer for the S-NSSAI or the network slice identified by the S-NSSAI, by sending a control message including the eleventh identification information and / or the fifteenth identification information, without transmitting the above to the NSACF. A UE that receives this control information may recognize the received content.

[0335] Furthermore, when the AMF receives an MM message (e.g., a registration request message or a deregistration request message) including a requested NSSAI that includes an S-NSSAI that identifies a network slice that is the target of temporary network slicing and is the target of NSAC, and a timer in the AMF for the S-NSSAI and / or the network slice identified by the S-NSSAI has expired, the AMF may perform the above-mentioned transmission to the NSACF and may also perform the above-mentioned transmission to the UE. The subsequent behaviors of the NSACF, the AMF, and the UE may be similar to those described above.

[0336] In addition, when the AMF receives an S-NSSAI that identifies a network slice that is the target of temporary network slicing and the target of NSAC, and an SM message (e.g., a PDU Session Establishment Request message or a PDU Session Release Request message), and a timer in the AMF for the S-NSSAI or the network slice identified by the S-NSSAI has expired, the AMF may send to the NSACF and / or SMF that the S-NSSAI and / or the network slice identified by the S-NSSAI has become unavailable, and / or that the timer for the S-NSSAI or the network slice identified by the S-NSSAI has expired, and / or that the S-NSSAI and / or the network slice identified by the S-NSSAI has become unavailable due to the expiration of the timer for the S-NSSAI or the network slice identified by the S-NSSAI. The AMF may also send the received SM message to the SMF. When the SMF receives this control information, the SMF may send to the NSACF that the S-NSSAI and / or the network slice identified by the S-NSSAI or the S-NSSAI has become unavailable, and / or that a timer for the S-NSSAI or the network slice identified by the S-NSSAI or the S-NSSAI has expired, and / or that the network slice identified by the S-NSSAI or the S-NSSAI has become unavailable due to the expiration of a timer for the S-NSSAI or the S-NSSAI. Then, the NSACF that receives this control information from the AMF and / or SMF may suspend NSAC (SM-based slice admission control) for the network slice identified by the S-NSSAI or the S-NSSAI. The NSACF may send to the SMF and / or AMF that NSAC for the S-NSSAI and / or the network slice identified by the S-NSSAI or the S-NSSAI has been suspended.When the SMF receives these control information, the SMF may send to the AMF that NSAC for the S-NSSAI and / or the network slice identified by the S-NSSAI or the S-NSSAI has been discontinued. The AMF that receives these control information may be able to recognize the received content. Furthermore, the SMF may send an SM message (e.g., a PDU session establishment accept message, a PDU session establishment reject message, or a PDU session release command message) including the S-NSSAI and / or the 11th identity and / or the 15th identity to the UE via the AMF. The UE that receives these control information may be able to recognize the received content.

[0337] Furthermore, when the AMF receives an S-NSSAI that identifies a network slice that is the target of temporary network slicing and the target of NSAC, and an SM message (e.g., a PDU Session Establishment Request message or a PDU Session Release Request message), and a timer in the AMF for that S-NSSAI or the network slice identified by that S-NSSAI has expired, the AMF may send a control message to the UE, without performing the above transmission to the NSACF and / or SMF, indicating that that S-NSSAI and / or the network slice identified by that S-NSSAI or the network slice identified by that S-NSSAI has become unavailable, and / or that the timer for that S-NSSAI or the network slice identified by that S-NSSAI has expired, and / or that the network slice identified by that S-NSSAI or the network slice identified by that S-NSSAI has become unavailable due to the expiration of the timer for that S-NSSAI or the network slice identified by that S-NSSAI, and / or including the 11th identification and / or the 15th identification. At this time, the control message sent from the AMF to the UE may be an MM message other than a registration acceptance message or a registration rejection message. The UE that receives this control information may be able to recognize the received content.

[0338] Furthermore, when the AMF receives an S-NSSAI that identifies a network slice that is the target of temporary network slicing and the target of NSAC, and an SM message (e.g., a PDU Session Establishment Request message or a PDU Session Release Request message), and a timer in the AMF for the S-NSSAI or the network slice identified by the S-NSSAI has expired, the AMF may perform the above-mentioned transmission to the NSACF and / or SMF, and may also perform the above-mentioned transmission to the UE. The subsequent behaviors of the NSACF, SMF, AMF, and UE may be similar to those described above.

[0339] Next, the UE receives the control message and / or the transmitted identification information (at least one of the eleventh to sixteenth identification information) via the base station device (S610). If the control message is a registration accept message, the UE may recognize, by receiving the registration accept message, that the UE's request in the registration request message has been accepted and / or the contents of the various identification information included in the registration accept message. Also, if the control message is a registration reject message, the UE may recognize, by receiving the registration reject message, that the UE's request in the registration request message has been rejected and / or the contents of the various identification information included in the registration reject message.

[0340] Furthermore, when the UE receives at least one of the 11th to 16th identification information from the core network, the UE may store the information indicated by the received identification information, or may behave based on the information indicated by the received identification information.

[0341] For example, when the 12th identification information indicates that the network supports temporary network slices, or that the network has the capability to process timing information regarding network slices, or that the network has the capability to process information regarding the time or period when the network slice is available, the UE may recognize that the network supports temporary network slices, or that the network has the capability to process timing information regarding network slices, or that the network has the capability to process information regarding the time or period when the network slice is available.

[0342] Furthermore, when the 12th identification information indicates that the network does not support temporary network slices, or that the network does not have the ability to process timing information regarding network slices, or that the network does not have the ability to process information regarding the time or period when the network slice is available, the UE may recognize the 12th identification information as indicating that the network does not support temporary network slices, or that the network does not have the ability to process timing information regarding network slices, or that the network does not have the ability to process information regarding the time or period when the network slice is available.

[0343] Furthermore, by receiving the 11th identification information, and / or the 13th identification information, and / or the 14th identification information, the UE may recognize that the network supports temporary network slices, or that the network has the ability to process timing information regarding network slices, or that the network has the ability to process information regarding the time or period when the network slice is available.

[0344] Furthermore, by not receiving the 11th identification information, and / or the 13th identification information, and / or the 14th identification information, the UE may recognize that the network does not support temporary network slices, or that the network does not have the ability to process timing information regarding network slices, or that the network does not have the ability to process information regarding the time or period when the network slice is available.

[0345] The UE may also discard or ignore the 13th identification information and / or the 14th identification information if it transmits a second identification information indicating that the UE does not support temporary network slices, or that the UE does not have the ability to process timing information regarding network slices, or that the UE does not have the ability to process information regarding the time or period when the network slice is available.

[0346] The UE may also discard or ignore the 13th identification information and / or the 14th identification information if it has not transmitted the second identification information regarding whether the UE supports temporary network slices, or whether the UE has the ability to process timing information regarding network slices, or whether the UE has the ability to process information regarding the time or period when the network slice is available.

[0347] Furthermore, when the UE receives eleventh identification information indicating an NSSAI (e.g., an allowed NSSAI and / or a configured NSSAI) including an S-NSSAI identifying a temporary network slice, and / or thirteenth identification information indicating a timer value indicating a period during which the network slice or the S-NSSAI is available, and / or fourteenth identification information indicating that these configuration information are valid, the UE may store the S-NSSAI as an allowed NSSAI and / or a configured NSSAI, and may set and start its own timer to the timer value indicated by the thirteenth identification information. Note that starting this timer may be executed after completion of this procedure or may be started during this procedure. Here, if the S-NSSAI is included in the rejected NSSAI and / or pending NSSAI, the UE may delete the S-NSSAI from the rejected NSSAI and / or pending NSSAI.

[0348] Furthermore, when the UE receives an eleventh identification indicating an NSSAI (e.g., an allowed NSSAI and / or a configured NSSAI) including an S-NSSAI that identifies a temporary network slice, but does not receive a thirteenth identification indicating a timer value indicating a period during which the network slice or S-NSSAI is available and / or a fourteenth identification indicating that these configuration information are valid, the UE stores the S-NSSAI as an allowed NSSAI and / or a configured NSSAI, but may not set or start the timer value indicated by the thirteenth identification in its own timer. Here, if the S-NSSAI is included in the rejected NSSAI and / or pending NSSAI, the UE may delete the S-NSSAI from the rejected NSSAI and / or pending NSSAI.

[0349] Furthermore, when the UE receives eleventh identification information indicating an NSSAI (e.g., a rejected NSSAI) including an S-NSSAI that identifies a temporary network slice, the UE may store the S-NSSAI as a rejected NSSAI. Here, if the S-NSSAI is included in the allowed NSSAI and / or the configured NSSAI and / or the pending NSSAI, the UE may delete the S-NSSAI from the allowed NSSAI and / or the configured NSSAI and / or the pending NSSAI.

[0350] Furthermore, when the UE receives eleventh identification information indicating an NSSAI (e.g., a rejected NSSAI) including an S-NSSAI that identifies a temporary network slice, and / or thirteenth identification information indicating a predetermined value (e.g., 0) as a timer value indicating a period during which the network slice or S-NSSAI is available, and / or fourteenth identification information indicating that these configuration information are not valid, the UE may store the S-NSSAI as a rejected NSSAI and, if a timer corresponding to the network slice or S-NSSAI is running, stop the timer. Here, if the S-NSSAI is included in an allowed NSSAI and / or a configured NSSAI and / or a pending NSSAI, the AMF may delete the S-NSSAI from the allowed NSSAI and / or the configured NSSAI and / or the pending NSSAI.

[0351] Furthermore, when the UE receives eleventh identification information indicating an NSSAI (e.g., an allowed NSSAI and / or a configured NSSAI) including an S-NSSAI that identifies a temporary network slice, and / or thirteenth identification information indicating a predetermined value (e.g., 0) as a timer value indicating a period during which the network slice or S-NSSAI is available, and / or fourteenth identification information indicating that these configuration information are not valid, the UE may stop the timer corresponding to the network slice or S-NSSAI if the timer is running. Here, if the S-NSSAI is included in a rejected NSSAI and / or a pending NSSAI, the UE may delete the S-NSSAI from the rejected NSSAI and / or the pending NSSAI.

[0352] Furthermore, when the UE transmits the fourth identification information and then receives the eleventh identification information and / or the thirteenth identification information and / or the fourteenth identification information, the UE may update the information already stored therein to the content of the received identification information. For example, after starting a timer using a timer value indicated by the already received thirteenth identification information, if the UE receives new thirteenth identification information in this procedure, the UE may reset its own timer to the timer value indicated by the new thirteenth identification information. Furthermore, after starting a timer using a timer value indicated by the already received thirteenth identification information, if the UE does not receive the eleventh identification information and / or the thirteenth identification information and / or the fourteenth identification information in this procedure, the UE may recognize that no configuration update has occurred. Furthermore, after starting a timer using a timer value indicated by the already received thirteenth identification information, the UE may transmit the fourth identification information in this procedure and then not receive the eleventh identification information and / or the thirteenth identification information and / or the fourteenth identification information, the UE may recognize that no configuration update has occurred.

[0353] In addition, if the UE has received at least one of the identification information items 11 to 16 in this procedure, and if the UE has received at least one of the identification information items 11 to 16 via a control message in an MM procedure other than this procedure (for example, a setting update command message in a setting update procedure), the UE may update its settings to the contents of the received identification information.

[0354] In addition, when a timer started during or after the completion of this procedure expires and the S-NSSAI associated with that timer is stored in the allowed NSSAI and / or configured NSSAI and / or pending NSSAI, the UE may delete the S-NSSAI from the stored allowed NSSAI and / or configured NSSAI and / or pending NSSAI.

[0355] In addition, when a timer started during or after the completion of this procedure expires, the UE may store the S-NSSAI associated with that timer in the rejected NSSAI if that S-NSSAI is not stored in the rejected NSSAI.

[0356] In addition, when a timer started during or after the completion of this procedure expires and the S-NSSAI associated with that timer is stored in the allowed NSSAI and / or configured NSSAI, the UE may continue to store the S-NSSAI together with information indicating that the S-NSSAI is not valid or invalid, without deleting it from the stored allowed NSSAI and / or configured NSSAI.

[0357] The UE may also initiate an SM procedure (e.g., a PDU session release procedure) and / or an MM procedure (e.g., a deregistration procedure) after expiration of a timer started during this procedure or after completion of this procedure.

[0358] For example, when the UE initiates a PDU session release procedure after the timer expires, the UE may send a PDU session release request message to the SMF via the AMF using the network slice or S-NSSAI, the message including a network slice related to the expired timer and / or an S-NSSAI identifying the network slice, and / or a PDU session ID identifying a PDU session using the network slice or S-NSSAI, and / or a cause value (5GSM cause). Here, the cause value (5GSM cause) may indicate that there is no network slice available, or that the network slice is not available, or that the network slice is not valid, or that the network slice is invalid, or that the network slice has timed out, or that the network slice has expired. The cause value (5GSM cause) may also indicate insufficient resources, regular deactivation, semantic errors in packet filter(s), syntactical error in packet filter(s), semantic error in the QoS operation, syntactical error in the QoS operation, invalid mandatory information.

[0359] In addition, when the UE initiates a PDU session release procedure after the timer expires, it may implicitly release one or more (or all) PDU sessions and / or resources that use the network slice or S-NSSAI associated with the expired timer.

[0360] In addition, when the UE initiates a deregistration procedure after the timer expires, it may send a deregistration request message to the network, including at least one of the identification information 11, 13 to 16, and / or information indicating that there is no network slice available, or that the network slice is not available, or that the network slice is not valid, or that the network slice is invalid, or that the network slice has timed out, or that the network slice has expired.

[0361] The UE may also implicitly deregister after the timer expires without initiating a deregistration procedure.

[0362] Furthermore, after starting the timer, if the timer expires, the UE may monitor for a predetermined time whether a PDU session release procedure and / or deregistration procedure is performed by the network, and if the PDU session release procedure and / or deregistration procedure is not initiated by the network within the predetermined time, the UE may initiate the above-mentioned SM procedure (e.g., a PDU session release procedure) and / or MM procedure (e.g., a deregistration procedure).

[0363] Furthermore, after starting the timer, if the timer expires, the UE may immediately start the above-mentioned SM procedure (e.g., a PDU session release procedure) and / or MM procedure (e.g., a deregistration procedure) without monitoring whether a PDU session release procedure and / or a deregistration procedure is performed by the network.

[0364] Furthermore, if the UE receives the 13th identification information in an MM message in another MM procedure after starting a timer using the timer value indicated by the 13th identification information and before the timer expires, the UE may reset the timer to the timer value indicated by the 13th identification information and start the timer. Furthermore, if the UE receives the 13th identification information in an MM procedure after starting a timer using the timer value indicated by the 13th identification information and before the timer expires, the UE may stop the timer that is running and set the timer to the timer value indicated by the 13th identification information and start the timer.

[0365] Furthermore, when the UE receives a 13th identification indicating a predetermined value (e.g., 0) in an MM message in another MM procedure after starting a timer using the timer value indicated by the 13th identification and before the timer expires, the UE may recognize that the S-NSSAI included in the 11th identification corresponding to the 13th identification, or the network slice identified by that S-NSSAI, is unavailable.

[0366] Furthermore, when the UE receives the thirteenth identification, the UE may recognize that the S-NSSAI included in the eleventh identification corresponding to the thirteenth identification, or the network slice identified by that S-NSSAI, is available until the timer expires. Furthermore, when the UE receives the thirteenth identification, the UE may recognize that the S-NSSAI included in the eleventh identification corresponding to the thirteenth identification, or the network slice identified by that S-NSSAI, is unavailable after the timer expires.

[0367] In addition, when the UE does not support temporary network slices, or when the UE does not have the ability to process timing information regarding network slices, or when the UE does not have the ability to process information regarding the time or period when the network slice is available, and the UE receives the 13th identification information in this procedure or in an MM message in another MM procedure, the UE may discard, ignore, or be unable to recognize the 13th identification information.

[0368] Furthermore, by receiving the 11th identification information, and / or the 13th identification information, and / or the 14th identification information, the UE may recognize that the network supports temporary network slices, or that the network has the ability to process timing information regarding network slices, or that the network has the ability to process information regarding the time or period when the network slice is available.

[0369] Furthermore, when the UE receives the eleventh identification information and / or the thirteenth identification information and / or the fourteenth identification information, the UE may store the S-NSSAI included in the NSSAI indicated by the eleventh identification information (e.g., the configured NSSAI and / or the allowed NSSAI) in the configured NSSAI and / or the allowed NSSAI until the timer value indicated by the thirteenth identification information expires. At this time, the UE may store the S-NSSAI in association with the timer value indicated by the thirteenth identification information or the timer to which that timer value is set. In other words, the UE may recognize that the setting of the S-NSSAI stored in the configured NSSAI and / or the allowed NSSAI is valid until the timer value indicated by the thirteenth identification information or the timer to which that timer value is set expires. In other words, the UE may recognize that the setting of the S-NSSAI stored in the configured NSSAI and / or the allowed NSSAI is invalid after the timer value indicated by the thirteenth identification information or the timer to which that timer value is set expires. Also, the UE may delete the S-NSSAI stored in the configured NSSAI and / or the allowed NSSAI and store the S-NSSAI as a rejected NSSAI after the timer value indicated by the thirteenth identification information or the timer to which that timer value is set expires.

[0370] Furthermore, when a network slice that is the target of a temporary network slice is already unavailable, the UE may send a registration request message including a requested NSSAI that includes an S-NSSAI that identifies the network slice to the AMF, and receive a control message including an eleventh identity and / or a fifteenth identity from the AMF, and when the S-NSSAI is included in the eleventh identity, the UE may recognize that the network slice identified in the S-NSSAI cannot be unavailable. Furthermore, when the control message includes date and time information indicating when the network slice will become available and / or information indicating the period until the network slice becomes available, the UE may recognize that the network slice will become available in the future and / or when the network slice will become available and / or the period until the network slice becomes available.

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

[0372] Next, the AMF receives a registration completion message via the base station device (S612).

[0373] Each device completes this procedure based on the transmission and reception of a registration acceptance message and / or a registration completion message. Each device may also recognize that this procedure has been successfully completed based on the transmission and reception of a registration acceptance message and / or a registration completion message.

[0374] Each device may complete the registration procedure based on the transmission or reception of a registration rejection message, or may recognize that the procedure was not completed normally or that the procedure was completed abnormally based on the transmission or reception of a registration rejection message.

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

[0376] Furthermore, each device may perform processing based on the information transmitted and received during the registration procedure based on the completion of the registration procedure. For example, if the device transmits or receives 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 core network_A or another cell.

[0377] Furthermore, 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 based on the completion of the registration procedure.

[0378] Furthermore, each device may store the information transmitted and received in this procedure in association with each other.

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

[0380] 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 loaded into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0381] Furthermore, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, such as an integrated circuit or multiple integrated circuits. The electrical 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 electrical circuit may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge that replace current integrated circuits, one or more aspects of the present invention may also utilize new integrated circuits based on that technology.

[0382] The present invention is not limited to the above-described embodiment. Although one example of a device has been described in the embodiment, the present invention is not limited to this and can be applied to terminal devices or communication devices for stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0383] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications 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 substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0384] 1. Mobile communication systems 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A (E-UTRAN) 90 Core Network_A 120 Access Network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core Network_B

Claims

[Claim 1] A UE (User Equipment) including a transceiver unit, a control unit, and a storage unit, The transmitting / receiving unit Sending a registration request message including information indicating that the network device supports temporary network slicing; receiving a registration accept message or a registration reject message including an allowed NSSAI or a configured NSSAI that includes an S-NSSAI indicating a temporary network slice and a timer value corresponding to the S-NSSAI; The control unit starting a timer using the timer value; storing the S-NSSAI in an allowed NSSAI or a configured NSSAI in the storage unit; When said timer expires, Delete the S-NSSAI from the allowed NSSAI or configured NSSAI in the storage unit; The S-NSSAI is stored in a rejected NSSAI in the storage unit. A UE characterized by:

Images