User equipment (UE)

Abstract

The present invention clarifies UE behavior and NW behavior for when an NS or S-NSSAI identifying the NS is applied redundantly. A UE supporting a partial network slice includes S-NSSAI in requested NSSAI. If the S-NSSAI is permitted by some, but not all, TAs in the registration area, and the UE is not in the NS-AoS, then the UE receives partially allowed NSSAI not including the S-NSSAI.

Description

UE (User Equipment)

[0001] This embodiment relates to UE (User Equipment). This application claims priority to Japanese Patent Application No. 2023-164659, filed on September 27, 2023, the contents of which are incorporated herein by reference.

[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 Documents 1 to 3).

[0003] 3GPP TS 23.501 V18.2.2 (2023-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)3GPP TS 23.502 V18.2.0 (2023-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18)3GPP TS 24.501 V18.3.1 (2023-06); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18)

[0004] Discussions on expanding NS functions in Rel-18 include discussions on NS-AoS (Network Slice Area of ​​Service), discussions on temporarily available NS (temporarily available network slice), discussions on partial NS (Partial Network Slice) within a registration area, and discussions on the exchange of NS and NSI (Network Slice Instance).

[0005] However, the details of the UE behavior and network (also referred to as NW) behavior when these NSs or S-NSSAIs that identify these NSs are applied in duplicate are still not clear.

[0006] One aspect of this embodiment has been made in consideration of the above circumstances, and aims to clarify the UE behavior and NW behavior when these NSs or S-NSSAIs identifying those NSs are applied in duplicate.

[0007] A UE of one embodiment of this embodiment is a UE (User Equipment) having a transceiver unit and a control unit, the UE is a UE that supports partial network slice, the control unit includes an S-NSSAI in the requested NSSAI, the S-NSSAI is allowed in some, but not all, TAs in the registration area, and when the UE is not in NS-AoS, the transceiver unit receives a partially allowed NSSAI that does not include the S-NSSAI.

[0008] According to one aspect of this embodiment, it is possible to clarify the UE behavior and NW behavior when these NSs or S-NSSAIs identifying those NSs are applied in duplicate.

[0009] Fig. 1 is a diagram for explaining an overview of a mobile communication system (EPS / 5GS). Fig. 2 is a diagram for explaining a detailed configuration of a mobile communication system (EPS / 5GS). Fig. 3 is a diagram for explaining the device configuration of a UE. Fig. 4 is a diagram for explaining the configuration of an access network device (gNB) in 5GS. Fig. 5 is a diagram for explaining the configuration of a core network device (AMF / SMF) in 5GS.

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

[0011] [1. System Overview] First, FIG. 1 is a diagram for explaining an overview 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.

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

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

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

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

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

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

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

[0019] 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 symbol for gNB 122 may be abbreviated, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs, and is a node that 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 system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

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

[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] 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 referred to as the DN, and the DN may be referred to as the PDN.

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

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

[0030] 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 portion. The payload portion 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 it 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.

[0031] In addition, access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A may be configured with devices not shown in Fig. 2. For example, core network _A and / or core network _B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

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

[0033] 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. 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 managed by a third party.

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

[0035] Furthermore, the term "network" refers to at least a portion of the access network _B, core network _B, and DN. One or more devices included in at least a portion of the access network _B, core network _B, and DN may also 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, 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.

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

[0037] Note that each memory unit (memory unit_A340, memory unit_B540, 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. Each memory unit can store not only information originally configured at the time of shipment, but also various information transmitted and received between the device / function and itself (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each memory unit can also store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Each memory unit may also 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 the device / function included in 5GS and / or EPS. In this case, not only those transmitted and received via the N26 interface but also those transmitted and received without via the N26 interface can be stored.

[0038] [2.1. Device configuration of UE] 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.

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

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

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

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

[0043] [2.2. Device configuration of gNB] Next, an example of the device configuration of a gNB 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.

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

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

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

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

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

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

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

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

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

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

[0054] 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), supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), supporting the transmission and reception of NAS signals with the UE via the N3IWF, and authenticating the UE connected via the N3IWF.

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

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

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

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

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

[0060] The CM state may be expressed as a 5GMM mode. In this case, the unconnected state may be expressed as a 5GMM unconnected mode (5GMM-IDLE mode), and the connected state may be expressed as a 5GMM connected mode (5GMM-CONNECTED mode). Furthermore, the unconnected state in 3GPP access may be expressed as a 5GMM unconnected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access may be expressed as a 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Furthermore, the unconnected state in non-3GPP access may be expressed as a 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 a 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). In addition, the 5GMM non-connected mode may be expressed as idle mode, and the 5GMM connected mode may be expressed as connected mode.

[0061] In addition, one or more AMFs may be placed in the core network _B. In addition, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). In addition, the AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

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

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

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

[0065] 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 use the network connection unit _B720 to send and receive user data and / or control information between the AMF, and / or UPF, and / or PCF, and / or UDM, and / or NSACF.

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

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

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

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

[0070] [2.5. UPF Device Configuration] Next, an example of the UPF device configuration 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.

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

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

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

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

[0075] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a gateway between DNs and core network_B that forwards user data), packet routing and forwarding, an 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, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notifications.

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

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

[0078] [2.6. Description of Other Devices and / or Functions and Control Information in the Present Embodiment] Next, other devices or functions, technical terms, control information and control messages transmitted, received, stored and managed by each device or function, etc. will be described.

[0079] Furthermore, these control information and control messages may be information that is pre-stored by the UE, and / or base station, and / or AMF, and / or SMF, and / or core network devices / functions other than AMF and SMF (e.g., NSSF, PCF, etc.), or some of these may be pre-stored and stored in conjunction with the transmission and reception of this control information.

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

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

[0082] The user plane (also referred to as UP) refers to user data transmitted and received between a UE and a network. The UP may be a communication path for transmitting and receiving user data and may be composed of multiple bearers. The UP may be transmitted and received using a PDN connection in the case of 4G, or a PDU session in the case of 5G. In the case of EPS, the UP 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. In the case of 5GS, the UP 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. The UP may also be expressed as the U-Plane.

[0083] Furthermore, a control plane (also referred to as CP) refers to a control message transmitted and received to control communication of a UE, etc. The CP may be a communication path for transmitting and receiving control messages, and may be composed of multiple bearers. The CP may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. The CP may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the AMF. In the case of EPS, the CP may be transmitted and received using the LTE-Uu interface and the S1-MME interface. In the case of 5GS, the CP may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. The CP may be expressed as a control plane or a C-Plane.

[0084] In addition, the SM procedure (also referred to as the procedure for SM) may include a PDU session establishment procedure initiated by the UE, a PDU session modification procedure initiated by the UE or SMF (or network), and a UE-requested PDU session release procedure initiated by the UE or SMF (or network).

[0085] In the PDU session establishment procedure, the UE sends a PDU session establishment request message to the SMF, and upon receiving the PDU session establishment request message, the SMF may send a PDU session establishment accept message or a PDU session establishment reject message to the UE. If the SMF accepts the PDU session establishment request from the UE, it may send a PDU session establishment accept message, or if it rejects the PDU session establishment request, it may send a PDU session establishment reject message.

[0086] In addition, in the UE-initiated PDU session modification procedure, the UE sends a PDU session modification request message to the SMF, and upon receiving the PDU session modification request message, the SMF may either execute the SMF-initiated PDU session modification procedure or send a PDU session modification reject message to the UE. Here, if the SMF accepts the PDU session modification request from the UE, it may execute the SMF-initiated PDU session modification procedure, or if it rejects the request, it may send a PDU session modification reject message.

[0087] In addition, in a PDU session modification procedure initiated by the SMF (or the network), the SMF sends a PDU session modification command message to the UE, and the UE, upon receiving the PDU session modification command message, may send a PDU session modification complete message or a PDU session modification command reject message to the SMF. Here, the UE may send a PDU session modification complete message if it accepts the PDU session modification instruction from the SMF, or may send a PDU session modification command reject message if it does not accept the instruction.

[0088] In addition, in the UE-initiated PDU session release procedure, the UE transmits a PDU session release request message to the SMF, and upon receiving the PDU session release request message, the SMF may either execute the SMF-initiated PDU session release procedure or send a PDU session release reject message to the UE. Here, if the SMF accepts the PDU session release request from the UE, it may execute the SMF-initiated PDU session release procedure, or if it rejects the request, it may send a PDU session release reject message.

[0089] In addition, in a PDU session release procedure initiated by the SMF (or the network), the SMF sends a PDU session release command message to the UE, and the UE that receives this may send a PDU session release complete message to the SMF.

[0090] In addition, the MM (Mobility Management) message may be a control message transmitted and received between the UE and the AMF in the MM procedure, or may be an NAS message (also referred to as an NAS MM message).

[0091] In addition, an SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a control message transmitted and received between a UE and an SMF via an AMF during an SM procedure, or may be an NAS message (also referred to as a NAS SM message).

[0092] In addition, the MM procedure (also referred to as a procedure for MM) may include a registration procedure initiated by the UE, a de-registration procedure initiated by the UE or the AMF (or the network), a generic UE configuration update procedure initiated by the AMF (or the network), a service request procedure initiated by the UE, a paging procedure initiated by the AMF (or the network), and a notification procedure initiated by the AMF (or the network).

[0093] In this case, in the registration procedure, the UE sends a registration request message to the AMF, and the AMF that receives the message may send a registration accept message or a registration reject message to the UE. Here, the AMF may send a registration accept message if it accepts the registration request from the UE, or may send a registration reject message if it does not accept it.

[0094] In addition, in a deregistration procedure initiated by the UE, the UE may send a deregistration request message to the AMF, and the AMF may then send a deregistration accept message to the UE.

[0095] In addition, in a deregistration procedure initiated by the AMF (or network), the AMF may send a deregistration request message to the UE, and the UE that receives this may send a deregistration acceptance message to the AMF.

[0096] In addition, in the generic UE configuration update procedure, the AMF may send a configuration update command message to the UE, and the UE that receives this may send a configuration update complete message to the AMF.

[0097] In addition, in the service request procedure, the UE sends a service request message to the AMF, and the AMF that receives the service request may send a service accept message or a service reject message to the UE. Here, the AMF may send a service accept message when accepting the service request from the UE, or may send a service reject message when not accepting the service request.

[0098] In addition, in the paging procedure, the AMF sends a paging request (Request Paging) to the base station, and the base station that receives it sends a paging message to the UE, and the UE that receives it may send a service request message or a registration request message to the AMF.

[0099] In addition, in the notification procedure, the AMF sends a notification message to the UE, and the UE that receives this may send a notification response message to the AMF, or may send a service request message or a registration request message to the AMF.

[0100] In addition, the MM (Mobility Management) message may be a control message transmitted and received between the UE and the AMF in the MM procedure, or may be an NAS message (also referred to as an NAS MM message).

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

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

[0103] 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 it 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.

[0104] 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 DNN, QoS rule, PDU session type, application identification information, NSI identification information, and access network identification information, or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with the PDU sessions may be the same or different.

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

[0106] 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 sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be sent 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.

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

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

[0109] 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 one or more NSs configured within a core network _B. An NSI may also be composed of virtual network functions (NFs) generated using a network slice template (NST). Here, an NST is associated with resource requirements for providing required communication services and capabilities, and is a logical representation of one or more NFs. In other words, an NSI may be a collection of multiple NFs within the core network _B 190. An NSI may also be a logical network configured to separate user data delivered by services, etc. One or more NFs may be configured within an NS. The NFs configured in an NS may or may not be devices shared with other NSs. 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.

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

[0111] 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 the NSSAI authorized by the network for each PLMN. Also, the NSSAI may be information used to select an AMF.

[0112] Furthermore, the configured NSSAI (also referred to as configured NSSAI) is an NSSAI that is provided and stored in the UE. The UE may store the configured NSSAI for each PLMN. The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be expressed as configured S-NSSAI. The configured S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0113] The requested NSSAI (also referred to as the Requested NSSAI) is an NSSAI provided from the UE to the network during the registration procedure. The requested NSSAI may be an allowed NSSAI or a configured NSSAI stored by the UE. Specifically, the requested NSSAI may be information indicating a network slice that the UE wishes to access. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is transmitted in a Radio Resource Control (RRC) message including an NAS message or a Non-Access-Stratum (NAS) message, such as a registration request message or a PDU session establishment request message, transmitted from the UE to the network.

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

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

[0116] Furthermore, a rejected NSSAI (also referred to as a Rejected NSSAI) is information indicating one or more network slices to which a UE is not permitted to connect. In other words, a rejected NSSAI is information identifying a network slice to which a network does not permit a UE to connect. A rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value (hereinafter also referred to as a reason value or rejection reason). Here, a rejection reason value is information indicating a reason why a network rejects a corresponding S-NSSAI. The UE and the network may store and manage the rejected NSSAI appropriately based on the rejection reason value associated with each S-NSSAI. Furthermore, the rejected NSSAI may be included in an NAS message transmitted from the network to a 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. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. Here, the rejected NSSAI may mean either the second or fourth rejected NSSAI. Furthermore, the rejected S-NSSAI may mean a rejected S-NSSAI included in either the second or fourth rejected NSSAI. Furthermore, the second rejected S-NSSAI may be an S-NSSAI included in the second rejected NSSAI, and the fourth rejected S-NSSAI may be an S-NSSAI included in the fourth rejected NSSAI. Furthermore, the rejected NSSAI may be either the second or fourth rejected NSSAI or a pending NSSAI, or a combination of these. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0117] Here, the second rejected NSSAI may be a rejected NSSAI for the current RA. In other words, the second rejected NSSAI may be an NSSAI that cannot be used in the current RA. Furthermore, the second rejected NSSAI may be a set of one or more S-NSSAIs that are not usable in the current RA, among the S-NSSAIs included in the requested NSSAI by the UE. Furthermore, the second rejected S-NSSAI may be a rejected S-NSSAI for the current registration area. Furthermore, the second rejected NSSAI may be a rejected NSSAI stored by the UE and / or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. This reason value may indicate "S-NSSAI not available in the current registration area", which may mean that the S-NSSAI associated with the reason value is not available in the current RA.

[0118] Furthermore, the second rejected NSSAI may be valid within the current RA. That is, the UE and / or NW may treat the second rejected NSSAI and the S-NSSAI included in the second rejected NSSAI as information for each access type. That is, the second rejected NSSAI may be information valid for each of 3GPP access and non-3GPP access. That is, once the UE transitions to an unregistered state for a certain access, the UE may delete the second rejected NSSAI from its memory.

[0119] Furthermore, the S-NSSAI included in the second rejected NSSAI in the memory unit of the UE may be treated as unusable in the current RA, i.e., the UE may be in a state where the MM procedure and / or SM procedure using the S-NSSAI is prohibited in the current RA.

[0120] The fourth rejected NSSAI may also be a rejected NSSAI for the current tracking area. In other words, the fourth rejected NSSAI may be an NSSAI that is not available in the current TA.

[0121] The fourth rejected NSSAI may also be a rejected NSSAI for the current TA in the current RA (rejected NSSAI for the current tracking area in the current registration area). In other words, the fourth rejected NSSAI may be an NSSAI that is not available in the current TA in the current RA.

[0122] Furthermore, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current TA in the current RA, but can be used in other TAs in the current RA.

[0123] Furthermore, the fourth rejected NSSAI may be an NSSAI that cannot be used in the current TA in the current RA, but may be an NSSAI that can be used in other TAs in the current RA and other RAs (different from the current RA).

[0124] Furthermore, the fourth rejected NSSAI may be a set of S-NSSAIs included in the requested NSSAI by the UE, which may be S-NSSAIs that are not available in the current TA, or a set of S-NSSAIs sent by the AMF with a rejection reason indicating that the S-NSSAIs are not available in the current TA.

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

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

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

[0128] Here, the fourth rejected NSSAI not depending on the access type may mean, for example, that when a UE receives the fourth rejected NSSAI via 3GPP access, the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI cannot be used not only via 3GPP access but also via non-3GPP access. Similarly, when a UE receives the fourth rejected NSSAI via non-3GPP access, the fourth rejected NSSAI or the S-NSSAI included in the fourth rejected NSSAI cannot be used not only via 3GPP access but also via non-3GPP access. Note that when the fourth rejected NSSAI is not depending on the access type, it is desirable that the UE and / or NW not store the fourth rejected NSSAI for each access type (i.e., simply store the fourth rejected NSSAI instead of storing it separately for each access type), but this is not limited to this.

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

[0130] Additionally, if the UE does not have a valid RA and / or TA, the fourth rejected NSSAI may be applicable to the RA and / or TA for which the rejected NSSAI was received.

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

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

[0133] Furthermore, if the 5GS registration type indicates mobility registration updating, and the purpose of initiating the registration procedure is not to change the network slice to which the UE is currently registered, and the UE is in the current RA or the current TA, the UE does not need to include the requested NSSAI in the registration procedure.

[0134] In addition, the S-NSSAI included in the fourth rejected NSSAI (also referred to as the fourth rejected S-NSSAI) may be associated with one or more TAs that cannot use the rejected S-NSSAI (fourth rejected S-NSSAI).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0151] Note that this restriction may be lifted if the UE is powered off, or if the UE moves out of the current TA, or if the UICC including the USIM is removed from the UE, or if the fourth rejected NSSAI or fourth rejected S-NSSAI stored in the UE is deleted. That is, the UE may become able to perform the MM procedure and / or the SM procedure using the fourth S-NSSAI in the current TA.

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

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

[0154] Furthermore, the fourth rejected S-NSSAI may be not only a rejected S-NSSAI included in the fourth rejected NSSAI, but also a rejected S-NSSAI that is not included in the fourth rejected NSSAI. Furthermore, the above description regarding the fourth rejected NSSAI may be read as a description regarding the fourth rejected S-NSSAI.

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

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

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

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

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

[0160] Furthermore, the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the S-NSSAI included in the mapped S-NSSAI for the fourth rejected NSSAI in the memory unit of the UE may be treated as unusable in the current TA or in the current TA in the current RA. That is, the UE may be in a state where an MM procedure and / or an SM procedure using the S-NSSAI is prohibited in the current TA or in the current TA in the current RA. In other words, the UE may be in a state where an MM procedure and / or an SM procedure using the S-NSSAI is not prohibited in a TA other than the current TA or in a TA other than the current TA in the current RA.

[0161] Furthermore, a pending NSSAI (also referred to as a Pending NSSAI) is an S-NSSAI that requires network slice specific authentication by the network, and is a collection of one or more S-NSSAIs that are not usable in the current PLMN because the network slice specific authentication has not been completed. The pending NSSAI may be a 5GS Rejected NSSAI due to NSSAA or a pending NSSAI. The pending NSSAI may be an NSSAI stored by the UE or the NW, or an NSSAI transmitted from the NW to the UE. Note that the pending NSSAI is not limited to the rejected NSSAI, and may be an NSSAI independent of the rejected NSSAI. When the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. The rejection reason value in this case may be "NSSAA is pending for the S-NSSAI" and may be information indicating that the S-NSSAI associated with the rejection reason value is prohibited or pending use by the UE until the NSSAA for that S-NSSAI is completed.

[0162] Furthermore, the pending NSSAI is valid for the entire registered PLMN. In other words, the UE and / or NW may treat the S-NSSAI included in the third rejected NSSAI and the pending NSSAI as information independent of the access type. In other words, the pending NSSAI may be information valid for 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may be the second or fourth rejected NSSAI.

[0163] Furthermore, the pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE has pending procedures. Specifically, while the UE stores the pending NSSAI, it does not initiate a registration request procedure for the S-NSSAI included in the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI included in the pending NSSAI is completed. The pending NSSAI is identification information that includes one or more S-NSSAIs received from the core network in association with a rejection reason value indicating a pending NSSAA. The pending NSSAI is information that is independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0164] A tracking area (also referred to as TA) is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. A TA may be composed of multiple cells. Furthermore, a TA 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 TA may be a routing area, a location area, or anything similar. A TA may be identified by a Tracking Area Identity (TAI), which is composed of a PLMN ID (PLMN Identifier) ​​and a Tracking Area Code (TAC). Here, the PLMN ID is an identifier used to identify a PLMN and may be composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). The MCC is an identifier used to identify the country in which the UE is located, and the MNC is an identifier used to identify the Home Location Network (HPLMN) in the country in which the UE is located. The TAC is an identifier used to identify a TA in a PLMN.

[0165] A registration area (also referred to as a registration area, RA) is a collection of one or more TAs assigned to a UE by the AMF. Note that UE_A10 may be able to move without sending or receiving signals for TA update while moving within one or more TAs included in the RA. In other words, RA may be a group of information indicating areas in which UE_A10 can move without performing a TA update procedure. An RA may be identified by a TAI list consisting of one or more TAIs.

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

[0167] Network Slice-Specific Authentication and Authorization (NSSAA) 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. PLMNs and network devices with NSSAA functionality can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information. Furthermore, UEs with NSSAA functionality can manage and store rejected NSSAIs for pending NSSAA and / or rejected NSSAIs for failed NSSAA. In this document, NSSAA may be referred to as the network slice-specific authentication and authorization procedure or the authentication and authorization procedure.

[0168] An S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. The core network and / or core network device may store 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 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.

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

[0170] In addition, a UE in dual registration mode may be able to independently register with 5GC and EPC. A UE in dual registration mode can independently maintain 5G-GUTI and EPS-GUTI (also referred to as 4G-GUTI).

[0171] 3. First Embodiment First, a first embodiment will be described. In this embodiment, control information transmitted, received, stored, and / or managed by each device / function will be described.

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

[0173] Furthermore, if the UE supports functionality using temporarily available NS (also referred to as temporarily available NS) and / or functionality using S-NSSAI time validity information (also referred to as S-NSSAI time validity information) and / or functionality using validity time (also referred to as validity time), the UE may indicate in the registration request message that it supports temporarily available NS and / or S-NSSAI time validity information and / or validity time. Furthermore, S-NSSAI time validity information may be read as S-NSSAI time availability information or validity time.

[0174] The AMF may also include one or more S-NSSAIs and / or validity times (also referred to as validity times or validity periods) for one or more S-NSSAIs in the configured NSSAI in the registration acceptance message and / or configuration update command and send them to the UE.

[0175] In addition, in the case of roaming, the AMF may send the configured NSSAI to the UE, including the S-NSSAI and / or the validity time for the S-NSSAI, based on the limited use of the VPLMN S-NSSAI or the HPLMN mapped S-NSSAI.

[0176] Also, if the validity time is changed or if the validity time for an S-NSSAI in the configured NSSAI is determined, the PLMN may provide that S-NSSAI and / or the validity time for that S-NSSAI in the configured NSSAI to UEs that support the temporarily available NS function.

[0177] Also, for a UE that supports temporarily available NS and / or S-NSSAI time validity information and / or validity time, if a validity time for the S-NSSAI is configured, the UE may include the S-NSSAI in the requested NSSAI included in the registration request message if the validity time indicates that the S-NSSAI is available. Also, if the S-NSSAI is included in the allowed NSSAI or partially allowed NSSAI, the UE may establish a PDU session related to the S-NSSAI.

[0178] Also, for a UE that supports temporarily available NS, and / or S-NSSAI time validity information, and / or validity time, if a validity time for the S-NSSAI is configured, the UE may not include the S-NSSAI in the requested NSSAI if the validity time indicates that the S-NSSAI is unavailable.

[0179] Also, for a UE that supports temporarily available NS and / or S-NSSAI time validity information and / or validity time, if a validity time is set for the S-NSSAI, and if the validity time indicates that the S-NSSAI is unavailable, and if the S-NSSAI is part of an allowed NSSAI or partially allowed NSSAI, the UE may delete the S-NSSAI from the stored allowed NSSAI or partially allowed NSSAI, or may release the PDU session associated with the S-NSSAI.

[0180] Additionally, for a UE that supports temporarily available NS, and / or S-NSSAI time validity information, and / or validity time, if a validity time is configured for the S-NSSAI and if the validity time indicates that the S-NSSAI is unavailable and / or that the S-NSSAI is unavailable again, the UE may delete the S-NSSAI from the configured NSSAIs that it stores.

[0181] Also, for a UE that supports temporarily available NS, and / or S-NSSAI time validity information, and / or validity time, if a validity time is applied to an S-NSSAI (e.g., S-NSSAI#1), an AMF that supports temporarily available NS may, if S-NSSAI#1 is provided in the requested NSSAI included in the registration request message by the UE, send a configured NSSAI including the validity time of S-NSSAI#1 and / or S-NSSAI#1 to the UE in the registration accept message if the validity time indicates that the S-NSSAI (or S-NSSAI#1) is unavailable and / or will become available again.

[0182] Also, for a UE that supports temporarily available NS, and / or S-NSSAI time validity information, and / or validity time, if a validity time is applied to an S-NSSAI (e.g., S-NSSAI#1), an AMF that supports temporarily available NS may, if S-NSSAI#1 is provided in the requested NSSAI included in the registration request message by the UE, exclude S-NSSAI#1 from the configured NSSAI and send it to the UE if the validity time indicates that the S-NSSAI (or S-NSSAI#1) is unavailable and / or will not be available again.

[0183] Furthermore, for a UE that supports temporarily available NS and / or S-NSSAI time validity information and / or validity time, if a validity time is applied to an S-NSSAI (e.g., S-NSSAI#1), an AMF that supports temporarily available NS may delete S-NSSAI#1 from the allowed NSSAI or partially allowed NSSAI without sending a control signal to the UE if S-NSSAI#1 is included in the UE's allowed NSSAI or partially allowed NSSAI and the validity time indicates that the S-NSSAI (or S-NSSAI#1) is unavailable. At this time, if a PDU session related to S-NSSAI#1 is established, the AMF may request the SMF to release the PDU session.

[0184] Furthermore, for a UE that does not support temporarily available NS, and / or S-NSSAI time validity information, and / or validity time, if a validity time is applied to an S-NSSAI (e.g., S-NSSAI#1), an AMF that supports temporarily available NS may allow or partially allow the NS corresponding to that S-NSSAI#1 if the validity time indicates that the S-NSSAI (or S-NSSAI#1) is available, or may allow the establishment of a PDU session using that S-NSSAI#1.

[0185] Furthermore, for a UE that does not support temporarily available NS and / or S-NSSAI time validity information and / or validity time, if a validity time is applied to an S-NSSAI (e.g., S-NSSAI#1), an AMF that supports temporarily available NS may reject registration and / or delete S-NSSAI#1 from the configured NSSAI by providing an updated configured NSSAI in a registration accept message if the validity time indicates that the S-NSSAI (or S-NSSAI#1) is unavailable when S-NSSAI#1 is provided in the requested NSSAI included in the registration request message by the UE. In other words, the UE may delete S-NSSAI#1 from the configured NSSAI stored in the UE by receiving from the AMF a configured NSSAI with S-NSSAI#1 deleted.

[0186] Furthermore, for a UE that does not support temporarily available NS and / or S-NSSAI time validity information and / or validity time, if a validity time is applied to an S-NSSAI (e.g., S-NSSAI#1), an AMF that supports temporarily available NS may delete S-NSSAI#1 from the configured NSSAI and / or allowed NSSAI and / or partially allowed NSSAI by a configuration update procedure if the S-NSSAI is included in the UE's allowed NSSAI or partially allowed NSSAI and the validity time indicates that the S-NSSAI (or S-NSSAI#1) is unavailable. At this time, if a PDU session for S-NSSAI#1 is established, the AMF may request the SMF to release the PDU session.

[0187] Furthermore, for a UE that does not support temporarily available NS, and / or S-NSSAI time validity information, and / or validity time, when a validity time is applied to an S-NSSAI (e.g., S-NSSAI#1), an AMF that supports temporarily available NS may, when it detects that the S-NSSAI (or S-NSSAI#1) is available again based on the validity time of S-NSSAI#1, update the UE's configured NSSAI by including S-NSSAI#1 in the configured NSSAI and sending it to the UE.

[0188] Furthermore, the S-NSSAI time validity information may be configured to include one or more time windows, and each time window may be configured to include a start date and time, an end date and time, a recurrence pattern, and a recurrence end date and time. Here, the start date and time may indicate the date and time when the NS identified by the S-NSSAI becomes available. The end date and time may indicate the date and time when the NS identified by the S-NSSAI becomes unavailable. The recurrence pattern may indicate how often the time window is repeated. The recurrence end date and time may indicate the date and time when the recurrence of the time window ends. Here, the date and time may be configured as a year, month, day, and / or time.

[0189] In addition, the S-NSSAI time validity information may be transmitted and received within a registration accept message and / or a configuration update command sent from the AMF to the UE.

[0190] Furthermore, the UE may recognize whether the S-NSSAI is available or unavailable at the current date and time based on the S-NSSAI time validity information transmitted from the AMF. Specifically, the UE may recognize whether the S-NSSAI is available or unavailable based on information within a time window included in the S-NSSAI time validity information.

[0191] In addition, an NS-AoS (Network Slice Area of ​​Service, also referred to as an NS service area) may be an area in which zero or more resources are allocated to an NS in an NG-RAN cell, so that a UE can access and receive service from a specific NS.

[0192] Additionally, NS-AoS may include a TA in which NS is not available in some cells of the TA.

[0193] The AMF may also configure the UE using S-NSSAI location availability information (also referred to as S-NSSAI location availability information).

[0194] Furthermore, S-NSSAI location availability information may be referred to as S-NSSAI location availability information for configured NSSAI, or as S-NSSAI location validity information, or as S-NSSAI location validity information for configured NSSAI. Furthermore, S-NSSAI location availability information may be read as S-NSSAI location validity information or as NS-AoS.

[0195] Furthermore, the S-NSSAI included in the S-NSSAI location availability information may be referred to as an NS-AoS S-NSSAI or an NS-AoS target S-NSSAI. Furthermore, the cell included in the S-NSSAI location availability information may be referred to as an NS-AoS cell or an NS-AoS target cell or area. Furthermore, the location information included in the S-NSSAI location availability information may be referred to as information indicating an NS-AoS cell or information indicating an NS-AoS target cell or area.

[0196] The AMF may also be configured for each S-NSSAI as to whether or not to send S-NSSAI location availability information to the UE.

[0197] In addition, the S-NSSAI location availability information sent to the UE may be configured to include, for each available S-NSSAI of the configured NSSAI, location information (e.g., a cell ID) indicating the cell of the TA within the RA in which the S-NSSAI is available if the S-NSSAI is not available in all cells of the TA.

[0198] Also, if the UE indicates that it supports S-NSSAI location availability information and / or NS-AoS capability and / or NS-AoS-related capabilities, the AMF may configure the S-NSSAI location availability information in the UE by including it in a Registration Accept message or a Configuration Update Command message when allocating an RA where the NS availability does not match the entire TA (i.e., the NS is not available throughout the TA). A UE that receives the S-NSSAI location availability information may apply the information as follows: If the S-NSSAI is rejected in the RA, or if the S-NSSAI is partially rejected in the RA, or if the S-NSSAI is rejected with a cause code for re-registration, the UE may request the S-NSSAI only if the S-NSSAI location availability information indicates that the S-NSSAI is available in the cell where the UE is camped. - If the S-NSSAI is included in the partially allowed NSSAI or the allowed NSSAI, when the UE is in a cell within the RA but outside the location information of the S-NSSAI (i.e., the cell indicated by the location information included in the S-NSSAI location availability information), the UE may not activate UP for an already established PDU session, and the UE may not transmit an NAS message and / or user data as the payload of an NAS message on the uplink (UL). - If the S-NSSAI is included in the partially allowed NSSAI or the allowed NSSAI, when a UE in CM-CONNECTED state moves from a cell within NS-AoS to a cell outside NS-AoS, the NG-RAN (i.e., the base station) may deactivate UP resources for a PDU session for that S-NSSAI if they are activated.

[0199] Furthermore, when the UE leaves NS-AoS, or is in a cell within RA but leaves the cell indicated by the location information included in the S-NSSAI location availability information, the UE and / or NW may keep the S-NSSAI in the S-NSSAI location availability information included in the allowed NSSAI, may keep it included in the configured NSSAI, or may remove it from the configured NSSAI.

[0200] In addition, when the S-NSSAI included in the S-NSSAI location availability information is subject to NSAC, the S-NSSAI may be counted towards NSAC even if the UE is outside the NS-AoS.

[0201] Additionally, cells outside the NS-AoS may be configured not to allocate Radio Resource Management (RRM) resources for the S-NSSAI.

[0202] The NW may also enforce NS-AoS for the S-NSSAI (for example, S-NSSAI#1) as follows: The NW may monitor the validity of S-NSSAI#1 for a UE in the CM-CONNECTED state. That is, the AMF may register an AoI (Area of ​​Interest) using the location information in the S-NSSAI location availability information. Furthermore, if a UE that does not support NS-AoS or S-NSSAI location availability information makes a PDU session establishment request using S-NSSAI#1 that is not valid (i.e., invalid) according to the S-NSSAI location availability information, the AMF may reject the NAS transport message using a back-off timer using S-NSSAI-based congestion control. In other words, in this case, if the AMF rejects a UL NAS message including a PDU session establishment request message received from the UE without forwarding it to the SMF, it may send a DL NAS message including a back-off timer to the UE. - Also, if the AMF determines that a UE in CM-CONNECTED state has moved outside of NS-AoS, the AMF may execute the following logic (a) to (c).

[0203] (a) If a UE that does not support NS-AoS or S-NSSAI location availability information has another S-NSSAI (i.e., an S-NSSAI different from S-NSSAI#1) in the allowed NSSAI, the AMF may update the UE configuration by removing the S-NSSAI from the allowed NSSAI and / or configured NSSAI and sending a configuration update command including them to the UE. Upon receiving such an allowed NSSAI and / or configured NSSAI, the UE may release the PDU session using that S-NSSAI. The AMF may then request the SMF to locally release or release all PDU sessions using that S-NSSAI.

[0204] (b) If a UE that does not support NS-AoS or S-NSSAI location availability information does not have another S-NSSAI (i.e., an S-NSSAI different from S-NSSAI#1) in the allowed NSSAI, the AMF may update the UE configuration by removing the S-NSSAI from the allowed NSSAI and / or configured NSSAI, including the default S-NSSAI or default configured NSSAI in the allowed NSSAI, and sending a configuration update command including them to the UE. Upon receiving such an allowed NSSAI and / or configured NSSAI, the UE may release the PDU session using that S-NSSAI. The AMF may then request the SMF to locally release or release all PDU sessions using that S-NSSAI. (c) If a UE that does not support NS-AoS or S-NSSAI location availability information does not have any other S-NSSAIs (i.e., S-NSSAIs different from S-NSSAI#1) in the allowed NSSAIs and configured NSSAIs, the AMF may indicate to the SMF to release the PDU session.

[0205] - If the AMF determines that S-NSSAI#1 becomes valid, for example, when the UE moves into NS-AoS, the AMF may update the UE configuration by sending a configuration update command to the UE that includes S-NSSAI#1 in the configured NSSAI. - If the AMF determines that the S-NSSAI of a PDU session is restricted to NS-AoS in the PDU session, the AMF may indicate to the SMF that the PDU session is subject to the area restriction of the S-NSSAI.

[0206] Furthermore, a partial network slice (also referred to as a partial NS), or a partial NS in an RA, may be an NS supported by one or more TAs in a PLMN or SNPN, or an NS supported by one or more TAs in an RA in a PLMN or SNPN, or an NS that is not supported by all TAs but is supported by one or more TAs in an RA in a PLMN or SNPN.

[0207] Furthermore, supporting partial NS or supporting partial NS in an RA may mean that the network configures a partially allowed NSSAI and / or a partially rejected NSSAI (also referred to as S-NSSAI rejected partially in the RA) for the UE, or that the network and / or UE supports a partially allowed NSSAI and / or a partially rejected NSSAI, or that the network and / or UE supports a function based on a partially allowed NSSAI and / or a partially rejected NSSAI.

[0208] A partially allowed NSSAI may indicate one or more S-NSSAI values ​​that are available for use by a UE in a network (e.g., serving PLMN or SNPN) in some TAs in the current RA. A partially allowed NSSAI may also indicate one or more S-NSSAI values ​​that are available for use by a UE in a network (e.g., serving PLMN or SNPN) in some, but not all, TAs in the current RA. Each S-NSSAI in the partially allowed NSSAI may be associated with a list of TAs that support or can use that S-NSSAI.

[0209] Also, an S-NSSAI of an allowed NSSAI may be supported by all TAs of the RA, but an S-NSSAI of a partially allowed NSSAI may only be supported by TAs that correspond to or are included in the list of TAs associated with that S-NSSAI.

[0210] In addition, if the UE supports partial NS in RA, the AMF may provide the UE with a partially allowed NSSAI or a partially rejected NSSAI in a registration accept message or a configuration update command message, taking into account whether the S-NSSAI of the requested NSSAI received from the UE is supported in the current TA and neighboring TAs.

[0211] If one or more required S-NSSAIs are supported in a subset of TAs in the registration area, the AMF may include such S-NSSAIs in the partially allowed NSSAIs and provide the UE with mapping information of the S-NSSAIs of the partially allowed NSSAIs to the S-NSSAIs of the HPLMN. For each S-NSSAI of the partially allowed NSSAIs, the AMF may provide the UE with a list of TAs that support that S-NSSAI. The UE may be considered to be registered across RAs using that S-NSSAI. The AMF may also provide the partially allowed NSSAIs along with the UE context to the NG-RAN and / or base station.

[0212] The AMF may also reject the S-NSSAI with a rejection reason indicating that it is part of the RA, and for each S-NSSAI of the partially rejected NSSAI (S-NSSAI rejected partially in the RA), the AMF may provide the UE with a list of TAs that support the S-NSSAI and / or a list of TAs that do not support the S-NSSAI.

[0213] Furthermore, if a UE requests an S-NSSAI in a cell of a TA whose NS-AoS of the S-NSSAI does not match the deployed TA, that is, if the S-NSSAI is included in the requested NSSAI and sent, the AMF may include the S-NSSAI in the allowed NSSAI or partially allowed NSSAI and send it to the UE.

[0214] Also, if the UE stores a partially allowed NSSAI, the UE may be considered to have registered using the S-NSSAI of the partially allowed NSSAI throughout the RA, and the UE may not perform the registration procedure even when moving between a TA that supports the S-NSSAI and a TA that does not support the S-NSSAI within the RA.

[0215] Also, if the UE stores a partially allowed NSSAI, the UE may initiate a PDU session establishment procedure for that S-NSSAI only if the UE is in a TA where the S-NSSAI is supported.

[0216] Additionally, if the AMF determines that a PDU session is associated with an S-NSSAI included in a partially allowed NSSAI, the AMF may indicate to the SMF that the PDU session is subject to the area restrictions of the S-NSSAI.

[0217] Furthermore, if the UE stores a partially allowed NSSAI, and if the UE has already established a PDU session using an S-NSSAI included in the partially allowed NSSAI, the UE may activate the UP resources of the PDU session only when the UE is in a TA that is part of the TA list associated with the S-NSSAI. Here, activating the UP resources may mean making the UP resources available, or maintaining the available state of the UP resources, or not deactivating the UP resources, or not making the UP resources unavailable.

[0218] Furthermore, if a UE stores a partially allowed NSSAI, and the UP resources of a PDU session using an S-NSSAI included in the partially allowed NSSAI are activated, and the UE moves to a TA that is not part of the list of TAs associated with that S-NSSAI, or moves outside the TA associated with that S-NSSAI, or moves outside a TA that supports that S-NSSAI, or moves to a TA that does not support that S-NSSAI, the UP resources of the PDU session may be deactivated, and the PDU session context (which may also be referred to as configuration information related to the PDU session) in the UE and the SMF may not be released.

[0219] Also, when the UE stores a list of partially rejected NSSAIs and / or mapped S-NSSAIs for partially rejected NSSAIs and / or their associated TAs, the UE may initiate a registration request procedure to request registration using that S-NSSAI only if it is in a TA that supports that S-NSSAI.

[0220] In addition, for a UE in CM-CONNECTED state, if a PDU session is established and UP resources are activated in an S-NSSAI included in a partially allowed NSSAI, and the UE moves to a TA that does not support that S-NSSAI, the NG-RAN may deactivate the UP resources.

[0221] Furthermore, the partially allowed NSSAI and the mapped S-NSSAI for the partially allowed NSSAI may be applied only to 3GPP access, only to non-3GPP access, or to both accesses (i.e., 3GPP access and non-3GPP access). Furthermore, the partially allowed NSSAI and the mapped S-NSSAI for the partially allowed NSSAI may be applied to a PLMN and / or an SNPN.

[0222] A partially rejected NSSAI may indicate an S-NSSAI that is rejected by the network (which may be, for example, a serving PLMN or SNPN) in some, but not all, TAs in the current RA. A partially rejected NSSAI may indicate that an S-NSSAI is rejected by the network (which may be, for example, a serving PLMN or SNPN) in some, but not all, TAs in the current RA. An S-NSSAI in a partially rejected NSSAI may be associated with a list of TAs that reject or do not support the S-NSSAI, respectively. A partially rejected NSSAI or an S-NSSAI included in a partially rejected NSSAI may be referred to as an S-NSSAI rejected partially in the RA.

[0223] Furthermore, the partially rejected NSSAI and the mapped S-NSSAI for the partially rejected NSSAI may be applied only to 3GPP access, only to non-3GPP access, or to both accesses (i.e., 3GPP access and non-3GPP access). Furthermore, the partially rejected NSSAI and the mapped S-NSSAI for the partially rejected NSSAI may be applied to the PLMN and / or SNPN.

[0224] Furthermore, when the UE receives a partially rejected NSSAI and / or a mapped S-NSSAI for the partially rejected NSSAI, it may store them, and when they are stored, when the UE is in a TA that does not support that S-NSSAI, it may not include that S-NSSAI in the requested NSSAI or establish a PDU session using that S-NSSAI.

[0225] In addition, NSR (NS Replacement) may refer to replacing an S-NSSAI with an alternative S-NSSAI when the S-NSSAI becomes unavailable or becomes congested.

[0226] The AMF may also determine to replace the S-NSSAI with an alternative S-NSSAI. The AMF may also determine an alternative S-NSSAI for the UE that is registering using the S-NSSAI. The alternative S-NSSAI may be supported in the RA.

[0227] In addition, when the UE supports NSR or the NSR function, and / or NSI replacement or the NSI replacement function, the UE may send a registration request message including support for NSR or the NSR function, and / or NSI replacement or the NSI replacement function in the registration procedure.

[0228] Furthermore, when establishing a PDU session related to an S-NSSAI that needs to be exchanged, the AMF may provide the UE with an alternative S-NSSAI for that S-NSSAI in the allowed NSSAI and configured NSSAI, or may provide mapping information between the S-NSSAI and the alternative S-NSSAi for that UE.

[0229] Furthermore, the alternative NSSAI (also referred to as an alternative NSSAI) may be a list of mapping information between the S-NSSAI to be exchanged and the alternative S-NSSAI. Furthermore, the S-NSSAI included in the alternative NSSAI may be the alternative S-NSSAI.

[0230] In addition, an alternative S-NSSAI (also referred to as an alternative S-NSSAI) may indicate a compatible S-NSSAI for the S-NSSAI included in the allowed NSSAI that the AMF uses to replace the S-NSSAI when the S-NSSAI is not available or when the S-NSSAI is congested.

[0231] Furthermore, the UE and / or the NW may store the alternative NSSAI separately for 3GPP access and non-3GPP access. Furthermore, the alternative NSSAI may be applicable to the PLMN and / or the SNPN.

[0232] Furthermore, the UE is a UE that supports a temporarily available network slice, the UE is configured with a validity time or S-NSSAI time validity information for the S-NSSAI, and the validity time indicates that the S-NSSAI is available, and the UE requests the S-NSSAI in a requested NSSAI in the registration request message, and if the S-NSSAI is included in a rejected NSSAI or a partially rejected NSSAI, the UE may not establish a PDU session associated with the S-NSSAI.

[0233] Furthermore, if the UE is a UE that supports a temporarily available network slice, the UE is configured with a validity time or S-NSSAI time validity information for the S-NSSAI, where the validity time indicates that the S-NSSAI is available, the UE requests the S-NSSAI in the requested NSSAI in the registration request message, the S-NSSAI is included in the partially rejected NSSAI, and the UE moves to a TA within the RA that supports the S-NSSAI, or if the UE moves outside a TA included in the TA list that does not support the S-NSSAI, or if the UE moves to a TA not included in the TA list associated with the S-NSSAI, the UE may establish a PDU session associated with the S-NSSAI.

[0234] Furthermore, if the UE is a UE that supports a temporarily available network slice, the UE is configured with a validity time or S-NSSAI time validity information for the S-NSSAI, where the validity time indicates that the S-NSSAI is available, the UE requests the S-NSSAI in the requested NSSAI in the registration request message, the S-NSSAI is included in the rejected NSSAI, and the UE moves outside the RA that supports the S-NSSAI, or if the UE moves outside a TA or RA included in the TA list that supports the S-NSSAI, or if the UE moves to a TA or RA not included in the TA list associated with the S-NSSAI, the UE may establish a PDU session associated with the S-NSSAI.

[0235] Furthermore, if the UE is a UE that supports a temporarily available network slice, the UE is configured with a validity time or S-NSSAI time validity information for the S-NSSAI, and the validity time indicates that the S-NSSAI is available, the UE requests the S-NSSAI in a requested NSSAI in the registration request message, and the S-NSSAI is included in an allowed NSSAI or partially allowed NSSAI, the UE may establish a PDU session associated with the S-NSSAI.

[0236] Furthermore, if the UE is a UE that supports a temporarily available network slice, the UE is configured with a validity time or S-NSSAI time validity information for the S-NSSAI, where the validity time indicates that the S-NSSAI is available, the UE requests the S-NSSAI in the requested NSSAI in the registration request message, the S-NSSAI is included in the partially allowed NSSAI, and the UE moves outside a TA that supports the S-NSSAI, or if the UE moves outside a TA in the RA that supports the S-NSSAI, or if the UE moves outside a TA in the RA that is included in the list of TAs that support the S-NSSAI, or if the UE moves to a TA in the RA that is not included in the list of TAs associated with the S-NSSAI, the UE may not establish a PDU session associated with the S-NSSAI.

[0237] Furthermore, if the UE is a UE that supports a temporarily available network slice, the UE is configured with a validity time or S-NSSAI time validity information for the S-NSSAI, where the validity time indicates that the S-NSSAI is available, the UE requests the S-NSSAI in the requested NSSAI in the registration request message, the S-NSSAI is included in the allowed NSSAI, and the UE moves outside the RA that supports the S-NSSAI, or if the UE moves outside a TA or RA included in the TA list that supports the S-NSSAI, or if the UE moves to a TA or RA not included in the TA list associated with the S-NSSAI, the UE may not establish a PDU session associated with the S-NSSAI.

[0238] Furthermore, if the UE is a UE that supports a temporarily available network slice, the UE is configured with a validity time or S-NSSAI time validity information for the S-NSSAI, and the validity time indicates that the S-NSSAI is not available, the UE requests the S-NSSAI in a requested NSSAI in the registration request message, and the S-NSSAI is included in a partially allowed NSSAI, the UE may not establish a PDU session associated with the S-NSSAI.

[0239] Furthermore, if the UE receives a partially allowed NSSAI that includes S-NSSAI#1 and the validity time for S-NSSAI#1, and the UE is in a TA that supports S-NSSAI#1 (i.e., a TA that is the target of the partially allowed NSSAI), and the validity time indicates that the S-NSSAI is available, the UE may establish a PDU session associated with that S-NSSAI.

[0240] Also, for example, if a UE receives a partially allowed NSSAI including S-NSSAI#1 and a validity time for S-NSSAI#1, and the UE is in a TA that supports S-NSSAI#1 (i.e., a TA that is the target of the partially allowed NSSAI), but the validity time indicates that the S-NSSAI is not available, the UE may not establish a PDU session related to that S-NSSAI.

[0241] Also, for example, when a UE receives a partially allowed NSSAI including S-NSSAI#1 and a validity time for S-NSSAI#1, and the UE is in a TA that does not support S-NSSAI#1 (i.e., outside the TA covered by the partially allowed NSSAI), the UE may not establish a PDU session related to the S-NSSAI, even if the validity time indicates that the S-NSSAI is available, or even if the validity time indicates that the S-NSSAI is not available.

[0242] Also, for example, if a UE receives a partially rejected NSSAI including S-NSSAI#1 and a validity time for S-NSSAI#1, and the UE is in a TA that supports S-NSSAI#1 (i.e., outside the TA covered by the partially rejected NSSAI), but the validity time indicates that the S-NSSAI is available, the UE may establish a PDU session associated with that S-NSSAI.

[0243] Also, for example, if a UE receives a partially rejected NSSAI including S-NSSAI#1 and a validity time for S-NSSAI#1, and the UE is in a TA that supports S-NSSAI#1 (i.e., outside the TA covered by the partially rejected NSSAI), but the validity time indicates that the S-NSSAI is not available, the UE may not establish a PDU session associated with that S-NSSAI.

[0244] Also, for example, when a UE receives a partially rejected NSSAI including S-NSSAI#1 and a validity time for S-NSSAI#1, and the UE is in a TA that does not support S-NSSAI#1 (i.e., the TA that is the target of the partially rejected NSSAI), the UE may not establish a PDU session related to the S-NSSAI, even if the validity time indicates that the S-NSSAI is available, or even if the validity time indicates that the S-NSSAI is not available.

[0245] Furthermore, if the UE is a UE that supports partial network slicing, and the UE includes an S-NSSAI in the requested NSSAI, and the S-NSSAI is rejected in some but not all TAs of the RA, and the UE does not support S-NSSAI location validity information, and the S-NSSAI is subject to NS-AoS, and when the UE is not in NS-AoS or it is determined by the AMF that the UE is not in NS-AoS, the UE may receive and store a partially rejected NSSAI including the S-NSSAI sent from the AMF.

[0246] Furthermore, if the UE is a UE that supports partial network slice, and the UE includes an S-NSSAI in the requested NSSAI, and / or the S-NSSAI is rejected in some but not all TAs of the RA, and / or the UE does not support S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is not in NS-AoS or the AMF determines that the UE is not in NS-AoS, the AMF may send a partially rejected NSSAI including the S-NSSAI to the UE, and the UE may receive and store it.

[0247] Furthermore, if the UE is a UE that supports partial network slice, and the UE includes an S-NSSAI in the requested NSSAI, and / or the S-NSSAI is rejected in some but not all TAs of the RA, and / or the UE supports S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is not in NS-AoS or the AMF determines that the UE is not in NS-AoS, the AMF may send the partially rejected NSSAI to the UE with or without the S-NSSAI, and the UE may receive and store it.

[0248] Furthermore, if the UE is a UE that supports partial network slice, and the UE includes an S-NSSAI in the requested NSSAI, and / or the S-NSSAI is rejected in some but not all TAs of the RA, and / or the UE does not support S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is in NS-AoS or the AMF determines that the UE is in NS-AoS, the AMF may send the partially rejected NSSAI to the UE with or without the S-NSSAI, and the UE may receive and store it.

[0249] Furthermore, if the UE is a UE that supports partial network slice, and the UE includes an S-NSSAI in the requested NSSAI, and / or the S-NSSAI is rejected in some but not all TAs of the RA, and / or the UE supports S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is in NS-AoS or the AMF determines that the UE is in NS-AoS, the AMF may send the partially rejected NSSAI to the UE with or without the S-NSSAI, and the UE may receive and store it.

[0250] Furthermore, if the UE is a UE that supports partial network slice, and the UE includes the S-NSSAI in the requested NSSAI, and / or the S-NSSAI is allowed in some but not all TAs of the RA, and / or the UE does not support the S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is not in NS-AoS or the AMF determines that the UE is not in NS-AoS, the AMF may send the partially allowed NSSAI to the UE without including the S-NSSAI, and the UE may receive and store it.

[0251] Furthermore, if the UE is a UE that supports partial network slicing, and the UE includes the S-NSSAI in the requested NSSAI, and / or the S-NSSAI is allowed in some but not all TAs of the RA, and / or the UE supports the S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is not in NS-AoS or the AMF determines that the UE is not in NS-AoS, the AMF may send the partially allowed NSSAI to the UE without including the S-NSSAI, and the UE may receive and store it. Here, the AMF sends the S-NSSAI to the UE within the partially allowed NSSAI, and when the UE receives it, it may ignore the partially allowed NSSAI and / or the S-NSSAI included in the partially allowed NSSAI, or it may not store the received partially allowed NSSAI and / or the S-NSSAI included in the partially allowed NSSAI, or it may discard the received partially allowed NSSAI, or it may delete the received S-NSSAI if it is included in a partially allowed NSSAI that it has already stored.

[0252] Furthermore, if the UE is a UE that supports partial network slice, and the UE includes the S-NSSAI in the requested NSSAI, and / or the S-NSSAI is allowed in some but not all TAs of the RA, and / or the UE does not support the S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is in NS-AoS or the AMF determines that the UE is in NS-AoS, the AMF may include the S-NSSAI in the partially allowed NSSAI and send it to the UE, and the UE may receive and store it.

[0253] Furthermore, if the UE is a UE that supports partial network slice, and the UE includes the S-NSSAI in the requested NSSAI, and / or the S-NSSAI is allowed in some but not all TAs of the RA, and / or the UE supports the S-NSSAI location validity information, and / or the S-NSSAI is subject to NS-AoS, and / or when the UE is in NS-AoS or the AMF determines that the UE is in NS-AoS, the AMF may include the S-NSSAI in the partially allowed NSSAI and send it to the UE, and the UE may receive and store it.

[0254] Furthermore, if an S-NSSAI is the subject of S-NSSAI time validity information and the S-NSSAI time validity information indicates that the S-NSSAI is available for use, then when an alternative S-NSSAI is the subject of S-NSSAI time validity information, the S-NSSAI time validity information of the alternative S-NSSAI may indicate that the S-NSSAI is available for use. In other words, if a certain S-NSSAI (e.g., S-NSSAI#1) and an alternative S-NSSAI for that S-NSSAI (S-NSSAI#1) are the subject of temporarily available NS and / or S-NSSAI time validity information, and the validity time for that S-NSSAI (S-NSSAI#1) indicates that the S-NSSAI (or S-NSSAI#1) is available, the validity time for an alternative S-NSSAI for that S-NSSAI (S-NSSAI#1) may indicate that the S-NSSAI (or S-NSSAI#1) is available.

[0255] Furthermore, a partially allowed NSSAI (also referred to as a partially allowed NSSAI IE) may be an NSSAI that includes one or more S-NSSAIs that the UE can use in some TAs in the current RA. Furthermore, a partially allowed NSSAI may be managed as part of an allowed NSSAI or separately from an allowed NSSAI. Furthermore, a partially allowed NSSAI may be managed as a rejected NSSAI or separately from a rejected NSSAI. Furthermore, a partially allowed NSSAI may be managed in association with an S-NSSAI rejected partially in the current RA. That is, an S-NSSAI included in a partially allowed NSSAI may be managed so as not to be included in an S-NSSAI rejected partially in the current RA, and an S-NSSAI included in an S-NSSAI rejected partially in the current RA may be managed so as not to be included in a partially allowed NSSAI.

[0256] Furthermore, an S-NSSAI included in a partially allowed NSSAI may be associated with a list of TAs that support the S-NSSAI. In other words, when a partially allowed NSSAI includes one or more S-NSSAIs, a list of TAs that support (can be used for) the S-NSSAI may be associated with each S-NSSAI. In other words, when a network (e.g., an AMF or SMF) transmits a partially allowed NSSAI that includes one or more S-NSSAIs to a UE, the network may transmit, for each S-NSSAI, a list of TAs that support (can be used for) the S-NSSAI. In this case, the TA list may be transmitted by being included in the partially allowed NSSAI, or may be transmitted as information separate from the partially allowed NSSAI. Furthermore, when the UE is roaming, the network (e.g., AMF or SMF) may also send to the UE a mapped NSSAI (an NSSAI that includes one or more mapped S-NSSAIs) or a mapped S-NSSAI (an S-NSSAI of the HPLMN) corresponding to a partially allowed NSSAI or an S-NSSAI included in a partially allowed NSSAI.

[0257] Furthermore, the S-NSSAI rejected partially in the current RA (also referred to as an S-NSSAI partially rejected in the current RA) may be an S-NSSAI that the UE cannot use in some TAs in the current RA. This may be the second or fourth rejected S-NSSAI, or the second or fourth rejected NSSAI itself. The S-NSSAI rejected partially in the current RA may be an S-NSSAI included in a partially rejected NSSAI. The S-NSSAI rejected partially in the current RA may be referred to as an S-NSSAI rejected partially in the RA, or an S-NSSAI partially rejected in the RA by the AMF or the network.

[0258] Furthermore, an S-NSSAI rejected partially in the current RA may be associated with a list of TAs that support the S-NSSAI. In other words, when an S-NSSAI rejected partially in the current RA includes one or more S-NSSAIs, a list of TAs that support (can be used for) the S-NSSAI may be associated with each S-NSSAI. In other words, when a network (e.g., an AMF or SMF) transmits an S-NSSAI rejected partially in the current RA that includes one or more S-NSSAIs to a UE, the network may transmit, for each S-NSSAI, a list of TAs that support (can be used for) the S-NSSAI. In this case, the list of TAs may be transmitted by being included in the S-NSSAI rejected partially in the current RA, or may be transmitted as information separate from the S-NSSAI rejected partially in the current RA.

[0259] Furthermore, when the UE has stored a partially allowed NSSAI and receives an NSSAI (allowed NSSAI, pending NSSAI, rejected NSSAI, configured NSSAI, default configured NSSAI) that includes an S-NSSAI included in the partially allowed NSSAI, the UE may delete the S-NSSAI from the partially allowed NSSAIs it has stored, or may store the S-NSSAI in the corresponding NSSAI (allowed NSSAI, pending NSSAI, rejected NSSAI, configured NSSAI, default configured NSSAI) based on the received NSSAI (allowed NSSAI, pending NSSAI, rejected NSSAI, configured NSSAI, default configured NSSAI).

[0260] Furthermore, when the UE has stored a partially allowed NSSAI and receives an S-NSSAI rejected partially in the current RA including an S-NSSAI included in the partially allowed NSSAI, the UE may delete the S-NSSAI from the partially allowed NSSAI or store it in the second or fourth rejected NSSAI.

[0261] In addition, when the UE stores an S-NSSAI rejected partially in the current RA and receives an NSSAI (allowed NSSAI, pending NSSAI, rejected NSSAI, configured NSSAI, default configured NSSAI) that includes the S-NSSAI included in the S-NSSAI rejected partially in the current RA, the UE may delete the S-NSSAI from the S-NSSAI rejected partially in the current RA.

[0262] In addition, when the UE stores an S-NSSAI rejected partially in the current RA and receives a partially allowed NSSAI that includes an S-NSSAI included in the S-NSSAI rejected partially in the current RA, the UE may delete the S-NSSAI from the S-NSSAI rejected partially in the current RA.

[0263] Also, when a UE has (memorizes) a partially allowed NSSAI and is in a TA that supports the S-NSSAI included in that partially allowed NSSAI, the UE may include that S-NSSAI in the requested NSSAI in the registration request message and send it.

[0264] Also, when the UE does not have (does not remember) an allowed NSSAI, and / or a configured NSSAI, and / or a default configured NSSAI for the current PLMN or SNPN, but the UE has (memorizes) a partially allowed NSSAI and is in a TA that supports the S-NSSAI included in the partially allowed NSSAI, the UE may include the S-NSSAI in the requested NSSAI in the registration request message and send it.

[0265] Also, when the UE has (memorizes) an S-NSSAI rejected partially in the current RA and the UE is in a TA that supports that S-NSSAI, the UE may include that S-NSSAI in the requested NSSAI in the registration request message and send it.

[0266] Also, when the UE does not have (does not remember) an allowed NSSAI, and / or a configured NSSAI, and / or a default configured NSSAI for the current PLMN or SNPN, the UE has (memorizes) an S-NSSAI rejected partially in the current RA, and the UE is in a TA that supports the S-NSSAI, the UE may include the S-NSSAI in the requested NSSAI in the registration request message and send it.

[0267] In addition, when the UE includes an S-NSSAI included in a partially allowed NSSAI in the requested NSSAI in a registration request message, the UE may include information in the registration request message and / or the requested NSSAI indicating that the requested NSSAI was created from the partially allowed NSSAI.

[0268] In addition, when the UE includes an S-NSSAI rejected partially in the current RA or an S-NSSAI included in an S-NSSAI rejected partially in the current RA in the requested NSSAI in the registration request message, the UE may include information in the registration request message and / or requested NSSAI indicating that the requested NSSAI was created from the S-NSSAI rejected partially in the current RA.

[0269] Also, if the UE does not have (or memorizes) an allowed NSSAI, and / or a configured NSSAI, and / or a default configured NSSAI, and / or a partially allowed NSSAI, and / or an S-NSSAI rejected partially in the current RA for the current PLMN or SNPN, the UE may not include the requested NSSAI in the registration request message.

[0270] Also, when the UE does not have (does not remember) an allowed NSSAI, and / or a configured NSSAI, and / or a default configured NSSAI for the current PLMN or SNPN, and has (memorizes) a partially allowed NSSAI and / or an S-NSSAI rejected partially in the current RA, but the UE is not in a TA that supports the S-NSSAI, the UE may not include the requested NSSAI in the registration request message.

[0271] Furthermore, when the UE does not have (does not remember) an allowed NSSAI, and / or a configured NSSAI, and / or a partially allowed NSSAI, and / or an S-NSSAI rejected partially in the current RA for the current PLMN or SNPN, but has (memorizes) a default configured NSSAI, the UE may include the S-NSSAI included in the default configured NSSAI in the requested NSSAI in the registration request message.

[0272] In addition, the S-NSSAI included in the partially allowed NSSAI may or may not be subject to session management-based network slice admission control (NSAC). In other words, the network may determine whether to apply session management-based NSAC to each S-NSSAI included in the partially allowed NSSAI.

[0273] Furthermore, when a UE transmits a NAS message including a PDU session establishment request message using an S-NSSAI included in a partially allowed NSSAI in a TA that does not support the S-NSSAI, if the AMF receives the NAS message including the PDU session establishment request message and detects that the S-NSSAI is not supported in the TA and / or that the S-NSSAI is partially unavailable in the current RA, the AMF may forward the PDU session establishment request message to the SMF and notify it that the S-NSSAI and / or the S-NSSAI are not supported in the TA. Here, the AMF may detect that the S-NSSAI is not supported in the TA by itself or may obtain this from another NF (e.g., NSSF or PCF). Then, the SMF that receives these may transmit a PDU session establishment rejection message to the UE via the AMF. At this time, the SMF may include the S-NSSAI and / or the cause value in the PDU session establishment rejection message. Here, the reason value may indicate unavailability in the current TA and / or partial unavailability in the current RA.

[0274] Furthermore, when the UE transmits an NAS message including a PDU Session Establishment Request message using an S-NSSAI included in a partially allowed NSSAI in a TA that does not support the S-NSSAI, and the SMF receives the PDU Session Establishment Request message via the AMF, the SMF may transmit a PDU Session Establishment Rejection message to the UE via the AMF. In this case, the SMF may include the S-NSSAI and / or a reason value in the PDU Session Establishment Rejection message. Here, the reason value may indicate that the S-NSSAI is unavailable in the current TA and / or that it is partially unavailable in the current RA.

[0275] [4. Modifications] A program running on an apparatus according to one aspect of this embodiment may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to this embodiment. 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 another storage device system.

[0276] A program for realizing the functions of an embodiment according to one aspect of this example may be recorded on a computer-readable recording medium. The program may be read 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.

[0277] Additionally, 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, one or more aspects of the present embodiments may utilize new integrated circuit technologies that replace current integrated circuits.

[0278] It should be noted that the present embodiment is not limited to the above-described embodiment. In the embodiment, one example of a device is described, but one aspect of the present embodiment is not limited to this, and can be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, for example, AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0279] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design modifications within the scope of this embodiment are also included. Furthermore, various modifications of one aspect of this embodiment are possible 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 this embodiment. Furthermore, configurations in which elements described in each of the above embodiments are substituted with elements that achieve the same effect are also included.

Claims

1. A UE (User Equipment) having a transceiver unit and a control unit, the UE being a UE that supports partial network slices, the control unit including an S-NSSAI in a requested NSSAI, the S-NSSAI being allowed in some but not all TAs in a registration area, and when the UE is not in an NS-AoS, the transceiver unit receiving a partially allowed NSSAI that does not include the S-NSSAI.

Images