User equipment (UE)

Abstract

Currently, in 5 GS, it is being contemplated to restrict the use of a network slice (NS) by a UE located outside an area-of-service (AoS) by managing, in AoS units, the area in which the NS can be used. However, the UE behavior when the UE is indicated to be outside the AoS has not been clarified. Further, handling of allowed NSSAI or partially allowed NSSAI when the UE is outside the AoS has also been not clarified. When the UE is indicated to be outside the AoS, the UE clarifies that the PDU session establishment procedure is aborted. When the UE is outside the AoS, it is clarified that S-NSSAI in allowed NSSAI or partially allowed NSSAI cannot be requested.

Description

UE (User Equipment)

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

[0002] The 3GPP (3rd Generation Partnership Project) is studying the system architecture of the 5G System (5GS), a fifth-generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 3). Currently, as part of the study toward the specification of Release 18, discussions are underway regarding the extension of network slicing (also referred to as NS) functions (see Non-Patent Document 4).

[0003] 3GPP TS 24.501 V18.4.0 (2023-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 18)3GPP TS 23.501 V18.3.0 (2023-09); 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.3.0 (2023-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18)3GPP TR 23.700-41 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of network slicing; Phase 3 (Release 18)

[0004] Currently, in 5GS, it is being considered to restrict the use of network slices (NS) by managing the area where NS can be used in units called Area of ​​Service (AoS). It is also specified that the network must indicate to the UE that it is outside the AoS. However, it is not clear how the UE should behave when it indicates that it is outside the AoS. It is also not clear how allowed or partially allowed NSSAI should be handled when the UE is outside the AoS.

[0005] This embodiment has been made in consideration of the above circumstances. This embodiment clarifies that if the UE indicates that it is outside the AoS, the UE aborts the PDU session establishment procedure. This embodiment also clarifies that if the UE is outside the AoS, it cannot request an S-NSSAI in the allowed NSSAI or partially allowed NSSAI.

[0006] The UE (User Equipment) of this embodiment is a UE having a control unit, and based on receiving first information, the control unit stops a first timer and aborts the PDU session establishment procedure, and the first information indicates that a UE that does not support the S-NSSAI location validity information requested the transfer of a 5GSM message having a request type IE set to "initial request" when it was not in the Network slice area of ​​service (NS-AoS) of the associated Single Network Slice Selection Assistance Information (S-NSSAI), and therefore the 5GSM message was not transferred along with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE.

[0007] This embodiment clarifies that if the UE indicates that it is outside the AoS, the UE aborts the PDU session establishment procedure. This embodiment also clarifies that if the UE is outside the AoS, it cannot request an S-NSSAI in the allowed NSSAI or partially allowed NSSAI.

[0008] FIG. 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS / 5GS). FIG. 3 is a diagram illustrating a device configuration of a UE. FIG. 4 is a diagram illustrating a configuration of an access network device (gNB) in 5GS. FIG. 5 is a diagram illustrating a configuration of a core network device (AMF / SMF / UPF) in 5GS. FIG. 6 is a diagram illustrating a registration procedure. FIG. 7 is a diagram illustrating a UE setting update procedure. FIG. 8 is a diagram illustrating a PDU session establishment procedure.

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

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

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

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

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

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

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

[0016] The 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). The UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device that can connect to both EPS and 5GS. The UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC).

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

[0018] Furthermore, access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Note that, hereinafter, the 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 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] The UPF_A235 is connected to the DN, the SMF, other UPFs, and the access network. The UPF_A235 may perform functions such as an anchor for intra-RAT mobility or inter-RAT mobility, packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows for one DN, a branching point function that supports multi-homed PDU sessions, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and a trigger function for downlink data notification. The UPF_A235 may also be a relay device that forwards user data as a gateway between the DN and the core network_B190. The UPF_A235 may also be a gateway for IP communication and / or non-IP communication. The UPF_A235 may also have a function for forwarding IP communication and a function for converting non-IP communication to IP communication. Furthermore, multiple gateways may be gateways that connect the core network _B190 to a single DN. Note that UPF_A235 may have connectivity with other NFs and may be connected to each device via other NFs.

[0035] Between UPF_A235 and the access network, UPF_C239 (also called a branching point or uplink classifier), which is a UPF different from UPF_A235, may exist as a device or NF. When UPF_C239 exists, a PDU session between the UE and the DN will be established via the access network, UPF_C239, and UPF_A235.

[0036] Furthermore, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be written with the symbols omitted, such as UPF.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0080] [2.6. Description of Other Devices and / or Functions] Next, other devices and / or functions will be described.

[0081] Next, the network refers to at least a part of the access network _B, the core network _B, and the DN. Furthermore, one or more devices included in at least a part of the access network _B, the core network _B, and the DN may be referred to as a network or a network device.

[0082] That is, when a network transmits, receives, and / or processes messages, it may mean that devices in the network (network devices and / or control devices) transmit, receive, and / or process messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0083] Furthermore, the network may refer to a public land mobile network (PLMN) or a non-public network (NPN). The network may also be referred to as a NW.

[0084] Next, 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 communication service provider, 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 Subscription Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may store an Equivalent PLMN list in its USIM to identify one or more Equivalent PLMNs (EPLMNs). A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN).

[0085] Next, PLMN selection may be a procedure for a UE to select a PLMN.

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

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

[0088] The TA list is a list that includes one or more TAs that the network has assigned to UE_A10. Note that UE_A10 may be able to move without performing a tracking area update procedure while moving within one or more TAs included in the TA list. In other words, UE_A10 may use the TA list as a group of information indicating areas that UE_A10 can move into without performing a tracking area update procedure. Note that the TA list may also be expressed as a TAI list consisting of one or more TAIs (Tracking area identities), and hereinafter, the TAI list may refer to the TA list.

[0089] Next, an NPN (Non-Public Network) is a private network used by specific users for specific purposes. There are two types of NPNs: SNPN (Stand-alone Non-Public Network) and PNI-NPN (Public Network Integrated NPN). Note that the term NPN may refer to either an SNPN or a PNI-NPN, or both.

[0090] Next, an SNPN is a network operated by an NPN operator and is not affected by functional units provided by a PLMN. In other words, an SNPN is a network dedicated to NPNs, independent of publicly available PLMNs. An SNPN may be a network identified by an SNPN identity (SNPN ID). The SNPN ID may be information that combines a PLMN ID and a Network Identifier (NID). The PLMN ID used in the SNPN ID may be information reserved for private networks. For example, the MCC included in the PLMN ID may be 999. Furthermore, when a UE is registered to an SNPN, the registered SNPN may be referred to as a registered SNPN or an RSNPN (registered SNPN).

[0091] Next, the NID is information that identifies a network. An SNPN may be identified by information that combines a PLMN ID and an NID. The NID may be information that is unique within the SNPN, or may be information that is unique worldwide.

[0092] Next, an SM (Session Management) message may be a NAS message used in a procedure for SM. The SM message may also be referred to as a NAS (Non-Access-Stratum) SM message. The SM message may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240.

[0093] Next, an MM (Mobility management) message may be a NAS message used in procedures for MM. The MM message may be a control message transmitted and received between UE_A10 and AMF_A240. Note that the MM message may also be referred to as a NAS MM message.

[0094] Next, a 5GS (5G System) service may be a connectivity service provided using the core network _B190.

[0095] Next, a non-5GS service may be a service other than a 5GS service.

[0096] Next, a PDU (Protocol Data Unit) session can be defined as an association between a DN providing 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. Note that each device (UE, and / or access network device, and / or core network device) may manage one or more pieces of identification information associated with a PDU session. Note that this identification information may include one or more of a DNN, a QoS rule, a PDU session type, an application identification information, an NSI identification information, an access network identification information, and an SSC mode, or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with each PDU session may be the same or different.

[0097] Next, 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 a PGW / UPF that connects the core network B190.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0115] The requested NSSAI is an NSSAI provided by the UE to the network during the registration procedure. In the registration procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI or configured NSSAI stored by the UE.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0157] The third rejected NSSAI may apply to the registered PLMN or the registered SNPN, or may apply to the registered PLMN and / or EPLMN, or may apply to the registered SNPN and / or ESNPN, or may apply to all PLMNs or SNPNs. The third rejected NSSAI applying to all PLMNs may mean that the third rejected NSSAI is not associated with a PLMN, or may mean that the third rejected NSSAI is associated with a HPLMN or HSNPN.

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

[0159] The third rejected NSSAI is a rejected NSSAI that identifies a slice that the UE rejected due to an NSSAA failure or revocation from the core network. Specifically, while the UE stores the third rejected NSSAI, the UE does not initiate a registration request procedure for the S-NSSAI included in the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAIs received from the core network in association with a rejection reason value indicating an NSSAA failure.

[0160] The third rejected NSSAI is information independent of the access type. Specifically, when the UE stores the third rejected NSSAI, the UE does not need to attempt to transmit a registration request message including the S-NSSAI included in the third rejected NSSAI to both 3GPP access and non-3GPP access. Alternatively, the UE can transmit a registration request message including the S-NSSAI included in the third rejected NSSAI based on a UE policy.

[0161] Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which it can transmit a registration request message including an S-NSSAI included in the third rejected NSSAI. In other words, when the UE transmits a registration request message including an S-NSSAI included in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI.

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

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

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

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

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

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

[0168] Here, the rejection reason value may be a rejection reason value included in the rejected NSSAI. Furthermore, at this time, the back-off timer value may be information indicating a period during which the UE is prohibited from transmitting an MM message using one or more S-NSSAIs and / or one or more mapped S-NSSAIs associated with the back-off timer value, the S-NSSAI of the current PLMN or SNPN associated with the one or more S-NSSAIs and / or the mapped S-NSSAI.

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

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

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

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

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

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

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

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

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

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

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

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

[0181] The RAT type identifies the transport technology used in the access network for 3GPP access and non-3GPP access. For example, the RAT type may be NR, NB-IOT, Untrusted Non-3GPP, Trusted Non-3GPP, Trusted IEEE 802.11 Non-3GPP access, Wireline, Wireline-Cable, or Wireline-BBF. Here, the RAT type may be the RAT type of the terrestrial NG-RAN or the RAT type of the satellite NG-RAN. The RAT type of the terrestrial NG-RAN may be a different RAT type from that of the satellite NG-RAN.

[0182] The partially allowed NSSAI may indicate the S-NSSAI values ​​that the UE can use in the Serving PLMN or SNPN in some of the TAs within the current registration area. Each S-NSSAI in the partially allowed NSSAI may be associated with a list of TAs in which the S-NSSAI is supported.

[0183] A partially allowed NSSAI may be sent and received as a Partial NSSAI.

[0184] A partially rejected NSSAI may indicate that the S-NSSAI has been rejected by the network in some, but not all, TAs in the registration area. Each partially rejected NSSAI may be associated with a list of TAs where the S-NSSAI has been rejected.

[0185] A partially rejected NSSAI may be sent and received as a Partial NSSAI.

[0186] The S-NSSAI location validity information may be a restriction on the use of the S-NSSAI in a TA where the availability of the network slice does not coincide with the TA boundary. For each S-NSSAI, the AMF may configure whether to send the S-NSSAI location validity information to supporting UEs.

[0187] The S-NSSAI location validity information may consist of one S-NSSAI for each relevant S-NSSAI in the configured NSSAI, and a list of cell IDs of Tracking Areas (TAs) belonging to a Registration Area (RA) that represent the NS-AoS of the S-NSSAI, where a Registration Area may be an area where one or more associated S-NSSAIs are available in some, but not all, cells of one or more TAs.

[0188] If the S-NSSAI is rejected in the RA, or partially rejected in the RA, or if the registration of the S-NSSAI is rejected with a cause code that allows for reattempts, the UE may request the S-NSSAI only if the S-NSSAI location validity information indicates that the S-NSSAI is available in the cell on which the UE is camped.

[0189] 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, the UE may not activate the user plane of an already established PDU session of the S-NSSAI. The UE and / or the SMF may not exchange user data as the payload of NAS messages in both uplink and downlink directions.

[0190] If an S-NSSAI is included in a partially allowed NSSAI or an allowed NSSAI, and a UE in CM-IDLE mode moves to a cell outside the location information of the S-NSSAI, and the UE has established a PDU session for the S-NSSAI, the PDU session may be maintained.

[0191] The S-NSSAI location validity information may also be referred to as S-NSSAI location availability information.

[0192] For an S-NSSAI in S-NSSAI location validity information, even if the S-NSSAI is included in a rejected NSSAI and / or a partially rejected NSSAI, a UE may be permitted to request the S-NSSAI if it determines that the UE is within the NS-AoS of the S-NSSAI. In other words, for an S-NSSAI in S-NSSAI location validity information, even if the S-NSSAI is included in a rejected NSSAI and / or a partially rejected NSSAI with a rejection reason value set to "S-NSSAI not available in the current registration area", a UE may be permitted to request the S-NSSAI if it determines that the UE is within the NS-AoS of the S-NSSAI.

[0193] For an S-NSSAI in the S-NSSAI location validity information, even if the S-NSSAI is included in an allowed NSSAI and / or a partially allowed NSSAI, the UE may not be allowed to request the S-NSSAI if it determines that the UE is outside the NS-AoS of the S-NSSAI.

[0194] When a UE that does not support S-NSSAI location validity information requests PDU session establishment for S-NSSAI restricted by NS-AoS and the UE is not within NS-AoS, the AMF may start performing S-NSSAI-based congestion control.

[0195] A network slice area of ​​service (NS-AoS) may be an area where a UE can access a particular network slice to receive services, and a network slice within an NG-RAN cell may have zero or more resources allocated to it.

[0196] The NS-AoS may be the location information of the S-NSSAI.

[0197] If the cell ID of the current serving cell matches any ID in the S-NSSAI location validity information, the UE may determine that it is inside the NS-AoS, otherwise, the UE may determine that it is outside the NS-AoS.

[0198] The S-NSSAI time validity information may be information indicating that the S-NSSAI is available for use. The S-NSSAI time validity information may be information indicating that the S-NSSAI is not available for use. The S-NSSAI time validity information may be information indicating whether the S-NSSAI is available for use.

[0199] The S-NSSAI time validity information may indicate the period during which the S-NSSAI is available for use. The S-NSSAI time validity information may indicate the time during which the S-NSSAI becomes available for use. The S-NSSAI time validity information may consist of the start time during which the S-NSSAI becomes available for use and the end time during which the S-NSSAI becomes unavailable.

[0200] If the UE is inside the NS-AoS of an S-NSSAI, the UE and / or SMF may attempt to establish user plane resources for a PDU session or establish a PDU session related to the S-NSSAI and / or mapped S-NSSAI(s), and in this case, the UE and / or SMF may not remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of an allowed NSSAI.

[0201] If the UE is outside the NS-AoS of an S-NSSAI, the UE and / or SMF may not attempt to establish user plane resources for or establish a PDU session related to the S-NSSAI and / or mapped S-NSSAI(s), and in this case, the UE and / or SMF may remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of the allowed NSSAI.

[0202] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is available, the UE and / or SMF may attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or establish a PDU session, and in this case, the UE and / or SMF may not remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of an allowed NSSAI.

[0203] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is unavailable, the UE and / or SMF may not attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or to establish a PDU session, and in this case, the UE and / or SMF may remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of an allowed NSSAI.

[0204] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is available and the UE is inside the NS-AoS of the S-NSSAI, the UE and / or SMF may attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or establish a PDU session, and in this case, the UE and / or SMF may not remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of an allowed NSSAI.

[0205] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is available but the UE is outside the NS-AoS of the S-NSSAI, the UE and / or SMF may not attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or to establish a PDU session, and in this case, the UE and / or SMF may remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of an allowed NSSAI.

[0206] Furthermore, if the UE is outside the NS-AoS of the S-NSSAI and the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is available, the UE and / or SMF may not attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or to establish a PDU session, and in this case, the UE and / or SMF may remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of the allowed NSSAIs.

[0207] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is unavailable and the UE is inside the NS-AoS of the S-NSSAI, the UE and / or SMF may not attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or to establish a PDU session, and in this case, the UE and / or SMF may remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of an allowed NSSAI.

[0208] Also, if the UE is inside the NS-AoS of the S-NSSAI but the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is unavailable, the UE and / or SMF may not attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or to establish a PDU session, and in this case, the UE and / or SMF may remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of the allowed NSSAIs.

[0209] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is unavailable and the UE is outside the NS-AoS of the S-NSSAI, the UE and / or SMF may not attempt to establish user plane resources for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s) or to establish a PDU session, and in this case, the UE and / or SMF may remove the S-NSSAI and / or mapped S-NSSAI(s) from the list of allowed NSSAIs and / or mapped S-NSSAIs of an allowed NSSAI.

[0210] The S-NSSAI time validity information may be referred to as validity time. Furthermore, when a UE supports the S-NSSAI time validity information, it may be expressed as the UE supporting NS-AoS. In other words, when a UE does not support the S-NSSAI time validity information, it may be expressed as the UE not supporting NS-AoS.

[0211] Timer T3580 may be started when a PDU session establishment request message and / or a NAS message is sent by the UE.

[0212] Additionally, timer T3580 may be stopped when a PDU session establishment accept message and / or a NAS message is received by the UE.

[0213] This section describes the UE behavior when timer T3580 expires. In other words, this section describes the UE behavior when, after the UE transmits a PDU session establishment request message and starts timer T3580, it does not receive a PDU session establishment acceptance message, a PDU session establishment rejection message, or an NAS message before timer T3580 expires.

[0214] The UE may retransmit the PDU Session Establishment Request message and the PDU session information sent with the initial transmission of the PDU Session Establishment Request message, and may reset and start timer T3580. This retransmission may be repeated up to four times.

[0215] If a PDU session establishment request message is sent with the fourth identification set to "initial emergency request" or "existing emergency PDU session", the UE may inform upper layers of the failure of this procedure. If a PDU session establishment request message is sent with the fourth identification set to "initial emergency request" or "existing emergency PDU session", the UE may locally de-register and attempt initial registration for emergency services.

[0216] Also, when the UE sends a PDU session establishment request message to perform a handover of an existing emergency PDU session between 3GPP access and non-3GPP access, the UE may recognize that the emergency PDU session is associated with the source access type.

[0217] [2.7. Description of Identification Information in This Embodiment] Next, the identification information transmitted, received, stored, and / or managed by each device in this embodiment will be described.

[0218] The first identification information may be information indicating whether the UE supports S-NSSAI location validity information. The first identification information may be information indicating that the UE supports S-NSSAI location validity information. The first identification information may be information indicating that the UE does not support S-NSSAI location validity information. The first identification information may be information in 5GMM capability.

[0219] The first identification information may be information indicating whether the UE supports NS-AoS. The first identification information may be information indicating that the UE supports NS-AoS. The first identification information may be information indicating that the UE does not support NS-AoS.

[0220] The second identification information may be information indicating whether the UE supports S-NSSAI time validity information. The first identification information may be information indicating that the UE supports S-NSSAI time validity information. The first identification information may be information indicating that the UE does not support S-NSSAI time validity information. The first identification information may be information in 5GMM capability.

[0221] The second identification information may be information indicating whether the UE supports a temporarily available network slice. The second identification information may be information indicating that the UE supports a temporarily available network slice. The second identification information may be information indicating that the UE does not support a temporarily available network slice. Here, the temporarily available network slice may be a network slice that is available at the time indicated by the S-NSSAI time validity information.

[0222] The third identity may be information indicating a network slice requested by the UE. The third identity may be a requested NSSAI. The third identity may be a requested NSSAI including one or more S-NSSAIs.

[0223] Here, one or more S-NSSAIs included in the requested NSSAI may be selected from one or more S-NSSAIs of the configured NSSAI, the allowed NSSAI, and / or the default configured NSSAI stored by the UE. Also, one or more S-NSSAIs included in the requested NSSAI may include one or more S-NSSAIs of the configured NSSAI, the allowed NSSAI, and / or the default configured NSSAI stored by the UE. Also, the requested NSSAI may be generated from the configured NSSAI, the allowed NSSAI, and / or the default configured NSSAI stored by the UE.

[0224] The fourth identification information may be a Request type, a Request type Information Element (IE), or information indicating a type of a 5GSM message.

[0225] The fourth identification information may be a Request type IE set to "initial request", or may be a Request type IE set to "existing PDU session", or "initial emergency request", or "existing emergency PDU session", or "modification request", or "MA PDU request", or "reserved".

[0226] The fifth identification information may be a Payload container. The fifth identification information may be a Payload container Information Element (IE). The fifth identification information may include sixth identification information.

[0227] The sixth identification information may be a Payload container type. The sixth identification information may be a Payload container type Information Element (IE). The sixth identification information may be included in the fifth identification information.

[0228] The sixth identification information may be set to "N1 SM information", and may also be set to "SMS", "LTE Positioning Protocol (LPP) message container", "SOR transparent container", "UE policy container", "UE parameters update transparent container", "Location services message container", "CIoT user data container", "Service-level-AA container", "Event notification", "User plane positioning information container", or "Multiple payloads".

[0229] The tenth identification information may be information indicating that the 5GSM message was not forwarded. The tenth identification information may be information indicating that the 5GSM message was not forwarded with a PDU Session Establishment Request message having a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE. The tenth identification information may be information indicating that the 5GSM message was not forwarded because a UE that does not support S-NSSAI location validity information requested the forwarding of the 5GSM message with a request type IE set to "initial request" when not in the NS-AoS of the associated S-NSSAI.

[0230] In other words, the tenth identification information may be information indicating that a UE that does not support S-NSSAI location validity information requested the transfer of a 5GSM message having a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI, and therefore the 5GSM message was not transferred along with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE.

[0231] The UE may stop the first timer and abort the PDU session establishment procedure based on receiving the tenth identification information, where the first timer may be timer T3580.

[0232] In addition, based on receiving the 10th identification information, the UE may stop timer T3581 and abort the PDU session modification procedure.

[0233] The eleventh identity information may be S-NSSAI location validity information. The eleventh identity information may be an S-NSSAI location validity information information element (IE).

[0234] The twelfth identity information may be S-NSSAI time validity information. The twelfth identity information may be an S-NSSAI time validity information information element (IE).

[0235] The thirteenth identity may be a configured NSSAI. The thirteenth identity may be a configured NSSAI information element (IE). The thirteenth identity may be one or more S-NSSAIs within the configured NSSAI.

[0236] The fourteenth identity may be an allowed NSSAI. The fourteenth identity may be an allowed NSSAI information element (IE). The fourteenth identity may be one or more S-NSSAIs within the allowed NSSAI.

[0237] The fifteenth identity may be a rejected NSSAI. The fifteenth identity may be a rejected NSSAI information element (IE). The fifteenth identity may be one or more S-NSSAIs within the rejected NSSAI.

[0238] The sixteenth identity may be a partially allowed NSSAI. The sixteenth identity may be a partially allowed NSSAI information element (IE). The sixteenth identity may be one or more S-NSSAIs within the partially allowed NSSAI.

[0239] The seventeenth identity may be a partially rejected NSSAI. The seventeenth identity may be a partially rejected NSSAI information element (IE). The seventeenth identity may be one or more S-NSSAIs within the partially rejected NSSAI.

[0240] [3. Description of Procedures Used in Each Embodiment] Next, procedures used in each embodiment will be described.

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

[0242] [3.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 6. The registration procedure is a procedure in 5GS. In this chapter, this procedure refers to the registration procedure. The registration procedure is a procedure initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with the network, it can execute this procedure at any time, for example, when powered on. In other words, if the UE is in the deregistered state (RM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure. Note that the registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or unregistered state) for 3GPP access and the registration state for non-3GPP access.

[0243] The registration procedure may also be a registration procedure for initial registration, a registration procedure for mobility and periodic registration update, or simply referred to as registration.

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

[0245] This procedure may be performed multiple times. In other words, after the registration procedure is completed once, the registration procedure may be performed again.

[0246] In addition, the UE may perform a registration procedure after performing SNPN selection or PLMN selection.

[0247] The UE may initiate the registration procedure when performing mobility across TAs. In other words, the UE may initiate the registration procedure when it moves to a TA different from the TA indicated in the TA list it holds. Furthermore, the UE may initiate the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may initiate the registration procedure when there is a change in the capability information and / or preferences related to the establishment of the UE's PDU session. Furthermore, the UE may initiate the registration procedure periodically. Furthermore, the UE may initiate the registration procedure based on the completion of a UE configuration update procedure. However, the UE is not limited to these, and may perform the registration procedure at any timing.

[0248] Additionally, the UE may periodically initiate a registration procedure even when in a registered state.

[0249] Note that a registration procedure performed based on the mobility of the UE and a registration procedure performed periodically may be referred to as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure performed based on the mobility of the UE, or may be a registration procedure performed periodically. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a configuration update of the UE. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration update may be a registration procedure other than the registration procedure for initial registration.

[0250] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be a registration procedure for initial registration, or a registration procedure for mobility and registration update.

[0251] First, the UE starts the registration procedure by transmitting a registration request message to the AMF (S800) (S802) (S804). Specifically, the UE transmits an RRC message including a registration request message to the 5G AN (or gNB) (S800). The registration request message is an NAS message. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0252] Here, the UE may transmit one or more of the identification information 1 to 3, 5, and 6 in a registration request message and / or an RRC message. More specifically, the UE may transmit one or more of the identification information 1 to 3, 5, and 6 in a registration request message and / or an RRC message, or may transmit one or more of the identification information 1 to 3, 5, and 6 in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer).

[0253] Specifically, if the UE supports S-NSSAI location validity information, it may send first identification information indicating that it supports S-NSSAI location validity information. If the UE does not support S-NSSAI location validity information, it may send first identification information indicating that it does not support S-NSSAI location validity information.

[0254] If the UE supports the S-NSSAI time validity information, it may send second identification information indicating that it supports the S-NSSAI time validity information. If the UE does not support the S-NSSAI time validity information, it may send second identification information indicating that it does not support the S-NSSAI time validity information.

[0255] The UE may send the requested network slice as a requested NSSAI. In other words, when requesting a network slice, the UE may send the third identity. In other words, when requesting a network slice, the UE may send a requested NSSAI including one or more requested S-NSSAIs.

[0256] The UE may also send the S-NSSAI of the stored configured NSSAI, and / or allowed NSSAI, and / or default configured NSSAI as third identification information.

[0257] The UE may also send a subset of the configured NSSAI as the third identity, where the subset of the configured NSSAI may include one or more S-NSSAIs of the configured NSSAI.

[0258] Here, the one or more S-NSSAIs included in the subset of the configured NSSAI may not be included in the rejected NSSAI or may not be related to an S-NSSAI in the rejected NSSAI. If the UE is within the NS-AoS of an S-NSSAI in the rejected NSSAI, the S-NSSAI may be included in the third identity. In other words, if the UE is within the NS-AoS of an S-NSSAI in the rejected NSSAI with a rejection reason value set to "S-NSSAI not available in the current registration area," the S-NSSAI may be included in the third identity.

[0259] Furthermore, one or more S-NSSAIs included in the subset of configured NSSAIs may be included in partially rejected NSSAIs. Furthermore, the current TAI may be included in a list of TAs where the S-NSSAI is not rejected. If the UE is inside the NS-AoS of an S-NSSAI in a partially rejected NSSAI and the current TAI is included in a list of TAs where the S-NSSAI is rejected, the S-NSSAI may be included in the third identity.

[0260] The UE may also send a subset of the allowed NSSAIs as third identity information, where the subset of the allowed NSSAIs may include one or more S-NSSAIs of the allowed NSSAIs.

[0261] Here, if the UE is outside the NS-AoS of an S-NSSAI in the allowed NSSAI, the S-NSSAI may not be included in the third identity information.

[0262] Furthermore, the one or more S-NSSAIs included in the subset of allowed NSSAIs may be included in partially allowed NSSAIs. Furthermore, the current TAI may be included in a list of TAs for which the S-NSSAI is not rejected. If the UE is outside the NS-AoS of the S-NSSAI in the partially rejected NSSAI and the current TAI is included in a list of TAs for which the S-NSSAI is not rejected, the S-NSSAI may not be included in the third identity. In other words, if the UE is outside the NS-AoS of the S-NSSAI in the partially rejected NSSAI and the current TAI is included in a list of allowed TAs for the S-NSSAI, the S-NSSAI may not be included in the third identity.

[0263] If the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is available and the UE is within the NS-AoS of the S-NSSAI, the UE may include the S-NSSAI in the third identification information.

[0264] If the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is available but the UE is outside the NS-AoS of the S-NSSAI, the UE may not include the S-NSSAI in the third identification information.

[0265] Also, if the UE is outside the NS-AoS of the S-NSSAI and the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is available, the UE does not need to include the S-NSSAI in the third identification information.

[0266] If the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is not available and the UE is inside the NS-AoS of the S-NSSAI, the UE may not include the S-NSSAI in the third identification information.

[0267] Also, if the UE is within the NS-AoS of the S-NSSAI but the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is not available, the UE may not include the S-NSSAI in the third identification information.

[0268] If the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is not available and the UE is outside the NS-AoS of the S-NSSAI, the UE may not include the S-NSSAI in the third identification information.

[0269] Note that the UE may send a registration request message to indicate to the network that the UE supports each function, or to indicate the UE's request.

[0270] Furthermore, the UE may indicate to the network the contents indicated by the identification information included in the registration request message by including one or more of the identification information 1 to 3, 5, and 6 in the registration request message and sending it.

[0271] In addition, the UE may select and decide whether to include one or more of the identification information 1 to 3, 5, and 6 in the registration request message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0272] The UE may also transmit identification information other than the first to third, fifth, and sixth identification information in the registration request message.

[0273] When a 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to forward the registration request message (S802). The 5G AN (or gNB) can select an AMF based on information included in the registration request message and / or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S804).

[0274] In addition, when the AMF receives the first identification information, it may recognize that the UE supports S-NSSAI location validity information, or may recognize that the UE does not support S-NSSAI location validity information.

[0275] In addition, when the AMF receives the second identification information, it may recognize that the UE supports S-NSSAI time validity information, or may recognize that the UE does not support S-NSSAI time validity information.

[0276] When the AMF receives the third identification information, the AMF may recognize the network slice requested by the UE. In other words, when the AMF receives the third identification information, the AMF may recognize the S-NSSAI requested by the UE.

[0277] When the AMF receives the registration request message, the AMF can perform a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the UE's request. If the first condition determination is true, the AMF starts the procedure of (A) in Figure 6, while if the first condition determination is false, the AMF starts the procedure of (B) in Figure 6.

[0278] The first condition determination may be performed based on the reception of a registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or a context held by the AMF. For example, if the network permits the UE's request, the first condition determination may be true, and if the network does not permit the UE's request, the first condition determination may be false. Furthermore, if the network to which the UE is registered and / or a device within the network supports a function requested by the UE, the first condition determination may be true, and if the network does not support the function requested by the UE, the first condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be false. The conditions for determining whether the first condition determination is true or false are not limited to the above-described conditions.

[0279] First, a case where the first condition determination is true will be described. In the procedure of (A) in Fig. 6, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message (S806). Note that the registration accept message is an NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) as part of an RRC message.

[0280] The AMF may also send a registration acceptance message including one or more of the 11th to 17th identification information. By sending these identification information, the AMF may indicate that the network supports each function or that the UE's request has been accepted.

[0281] Furthermore, the AMF may indicate to the UE what one or more of the 11th to 17th identities indicate by including them in the registration acceptance message and sending them.

[0282] Specifically, when the AMF needs to update the S-NSSAI location validity information for a UE that supports S-NSSAI location validity information, the AMF may send the 11th identification information.

[0283] If the registration request message includes a requested NSSAI that includes one S-NSSAI and the S-NSSAI time validity information indicates that the S-NSSAI is not available, the AMF may send a 13th identification information.

[0284] At this time, if the second identity indicates that S-NSSAI time validity information is supported and the S-NSSAI time validity information indicates that the S-NSSAI will be available again, the AMF may send a 12th identity. Also, if the second identity indicates that S-NSSAI time validity information is supported and the S-NSSAI time validity information indicates that the S-NSSAI will not be available again, the AMF may not include the S-NSSAI in the 13th identity. Also, if the second identity indicates that S-NSSAI time validity information is not supported and the AMF sends a 13th identity, the AMF may not include the S-NSSAI in the 13th identity.

[0285] In addition, if the UE supports S-NSSAI time validity information and the AMF needs to update the S-NSSAI time validity information, the AMF may send the 12th identification information.

[0286] The AMF may send the 13th identity information when the configured NSSAI in the UE needs to be updated.

[0287] The AMF may send the fourteenth identity when it needs to update the allowed NSSAI in the UE. In addition, when the AMF allows one or more S-NSSAIs included in the third identity, the AMF may send the one or more S-NSSAIs to be allowed by including them in the fourteenth identity.

[0288] The AMF may send the fifteenth identity when it needs to update the rejected NSSAI in the UE. In addition, when the AMF rejects one or more S-NSSAIs included in the third identity, the AMF may send the one or more rejected S-NSSAIs included in the fifteenth identity.

[0289] The AMF may send the 16th identity when it needs to update the partially allowed NSSAI in the UE.

[0290] The AMF may send the 17th identity information when it needs to update the partially rejected NSSAI in the UE.

[0291] Furthermore, the AMF may select and decide whether to include one or more of the identification information 11 to 17 in the registration acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0292] The AMF may also indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscription information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0293] Furthermore, the AMF may include information indicating that some of the UE's requests have been rejected in the registration acceptance message and send it, or may indicate the reason why some of the UE's requests have been rejected by sending the information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE's requests have been rejected by receiving the information indicating that some of the UE's requests have been rejected. Note that the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0294] Next, the UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S806). The UE may also receive the registration acceptance message from the AMF, including one or more of the 11th to 17th identification information.

[0295] Here, by receiving the registration accept message, the UE may recognize that the UE's request in the registration request message has been accepted, and the contents of the various identification information included in the registration accept message.

[0296] Specifically, when the UE receives the thirteenth identification information, the UE may store the content of the thirteenth identification information. Furthermore, when the UE receives the eleventh identification information, the UE may store the content of the eleventh identification information.

[0297] In addition, if the UE receives the 13th identification information but does not receive the 11th identification information, it may delete the stored S-NSSAI location validity information.

[0298] When the UE receives the thirteenth identification information, the UE may store the content of the thirteenth identification information. Furthermore, when the UE receives the twelfth identification information, the UE may store the content of the twelfth identification information.

[0299] In addition, if the UE receives the 13th identification information but does not receive the 12th identification information, it may delete the stored S-NSSAI time validity information.

[0300] When the UE receives the thirteenth identification information, the UE may store the thirteenth identification information.

[0301] Furthermore, when the UE receives the thirteenth identification information, the UE may replace the stored thirteenth identification information with the received thirteenth identification information.

[0302] Furthermore, when the UE receives the 13th identification information, it may delete the 14th and / or 16th identification information that it has stored.

[0303] Furthermore, when the UE receives the 13th identification information, it may delete the 15th and / or 17th identification information that it has stored.

[0304] When the UE receives the fourteenth identification information, the UE may store the fourteenth identification information.

[0305] Furthermore, when the UE receives the 14th identification information, the UE may replace the stored 14th identification information with the received 14th identification information.

[0306] Furthermore, when the UE receives the 14th identification information, it may delete the S-NSSAI included in the 14th identification information from the 15th and / or 17th identification information that it stores.

[0307] When the UE receives the 15th identification information, the UE may store the 15th identification information.

[0308] Furthermore, when the UE receives the 15th identification information, it may store the S-NSSAI included in the received 15th identification information in the 15th identification information that it has stored.

[0309] Furthermore, when the UE receives the 15th identification information, it may delete the S-NSSAI included in the 15th identification information from the 14th and / or 16th identification information that it stores.

[0310] Furthermore, when the UE receives the 15th identification information, the UE may delete the 15th identification information that it has stored.

[0311] When the UE receives the 16th identification information, the UE may store the 16th identification information.

[0312] Furthermore, when the UE receives the 16th identification information, the UE may replace the stored 16th identification information with the received 16th identification information.

[0313] When the UE receives the 17th identification information, the UE may store the 17th identification information.

[0314] Furthermore, when the UE receives the 17th identification information, the UE may replace the stored 17th identification information with the received 17th identification information.

[0315] Next, the UE may or may not send a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S808). Here, the registration completion message is an NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0316] Next, the AMF may or may not receive a registration completion message via the 5G AN (gNB) (S808).

[0317] Each device completes the procedure in FIG. 6(A) based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0318] The UE may also perform SNPN selection or PLMN selection based on receiving a registration accept message, or may perform SNPN selection or PLMN selection based on sending a registration complete message.

[0319] Next, a case where the first condition determination is false will be described. In the procedure of (B) of Fig. 6, the AMF transmits a registration reject message to the UE via the 5G AN (gNB) as a response message to the registration request message (S810). Here, the registration reject message is an NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) as an RRC message.

[0320] The AMF may also send a registration rejection message including one or more of the identification information from the 15th to 17th identification information. Furthermore, by sending these identification information, the AMF may indicate that the UE request has been rejected and may indicate the reason why the UE request has been rejected.

[0321] Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the registration rejection message by including one or more of the identification information from the 15th to 17th identification information in the registration rejection message and sending it.

[0322] Specifically, the AMF may send the fifteenth identity when it needs to update the rejected NSSAI in the UE. Also, when the AMF rejects one or more S-NSSAIs included in the third identity, the AMF may send the one or more rejected S-NSSAIs included in the fifteenth identity.

[0323] The AMF may send the 16th identity when it needs to update the partially allowed NSSAI in the UE.

[0324] The AMF may send the 17th identity information when it needs to update the partially rejected NSSAI in the UE.

[0325] Furthermore, the AMF may select and decide whether to include one or more of the identification information from items 15 to 17 in the registration rejection message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0326] Furthermore, the AMF may indicate that the UE's request via the registration request message has been rejected by sending a registration rejection message. Furthermore, the AMF may include information indicating the reason for the rejection in the registration rejection message and send it, or may indicate the reason for the rejection by sending the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. Note that the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0327] Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). The UE may also receive a registration rejection message from the AMF, including one or more pieces of identification information among the 15th to 17th pieces of identification information. By receiving the registration rejection message, the UE may recognize that the UE's request via the registration request message has been rejected and the contents of the various identification information included in the registration rejection message.

[0328] Specifically, when the UE receives the 15th identification information, the UE may store the 15th identification information.

[0329] Furthermore, when the UE receives the 15th identification information, it may store the S-NSSAI included in the received 15th identification information in the 15th identification information that it has stored.

[0330] Furthermore, when the UE receives the 15th identification information, it may delete the S-NSSAI included in the 15th identification information from the 14th and / or 16th identification information that it stores.

[0331] Furthermore, when the UE receives the 15th identification information, the UE may delete the 15th identification information that it has stored.

[0332] When the UE receives the 16th identification information, the UE may store the 16th identification information.

[0333] Furthermore, when the UE receives the 16th identification information, the UE may replace the stored 16th identification information with the received 16th identification information.

[0334] When the UE receives the 17th identification information, the UE may store the 17th identification information.

[0335] Furthermore, when the UE receives the 17th identification information, the UE may replace the stored 17th identification information with the received 17th identification information.

[0336] Here, if the UE receives the registration rejection message, it may perform SNPN selection or PLMN selection.

[0337] Furthermore, if the UE does not receive a registration rejection message within a predetermined period of time after sending the registration request message, the UE may recognize that the UE's request has been rejected.

[0338] Based on the sending and receiving of the registration rejection message, each device completes step (B) of this procedure.

[0339] The procedure in FIG. 6(B) may be started when the procedure in FIG. 6(A) is stopped.

[0340] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Figure 6. Note that each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in Figure 6. Also, each device may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) based on the completion of the procedure of (B) in Figure 6, or may transition to a state in which the UE is not registered in the network.

[0341] Furthermore, each device may perform processing based on the information transmitted and received during the registration procedure based on the completion of the registration procedure. For example, if the device transmits or receives information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's requests have been rejected, or may perform the registration procedure for the core network_B or another cell.

[0342] Furthermore, the UE may store the identification information received with the registration accept message or registration reject message and may recognize the network's decision based on the completion of the registration procedure.

[0343] Furthermore, the UE may perform SNPN selection or PLMN selection based on the completion of the registration procedure.

[0344] [3.2. UE Configuration Update Procedure] Next, the UE configuration update procedure (Generic UE configuration update procedure) will be described with reference to FIG. 7. Hereinafter, the UE configuration update procedure will also be referred to as this procedure. This procedure is a procedure by which the core network updates the configuration information of a UE. This procedure may be a procedure for mobility management that is initiated by the network for a UE registered in the network. The UE configuration update procedure may also be an MM procedure.

[0345] Note that the registration procedure may have been performed one or more times prior to this procedure.

[0346] This procedure may be performed multiple times. In other words, after the UE configuration update procedure is completed once, the UE configuration update procedure may be performed again.

[0347] Furthermore, a device in the core network, such as the AMF, may initiate this procedure based on an update to the network configuration and / or an update to the operator policy. The trigger for this procedure may be detection of UE mobility, detection of a change in the status of the UE, the access network, and / or the core network, or a change in the status of a network slice. The trigger for this procedure may be reception of a request from the DN and / or the DN's application server, a change in the network configuration, or a change in the operator policy. The trigger for this procedure may also be expiration of a running timer. The triggers for the device in the core network to initiate this procedure are not limited to these. In other words, this procedure may be performed at any time after the completion of the registration procedure and / or the PDU session establishment procedure. The procedure may also be performed at any time as long as each device has established a 5GMM context and / or is in 5GMM connected mode.

[0348] During this procedure, each device may also send and receive messages containing identification information for changing the UE's configuration information and / or identification information for stopping or changing a function being performed by the UE. Furthermore, each device may update its configuration information to a configuration instructed by the network or start a behavior instructed by the network based on the completion of this procedure.

[0349] The UE may update its configuration information based on the control information transmitted and received through this procedure. Furthermore, the UE may stop a function currently being executed or start a new function in response to the update of the UE's configuration information. In other words, a device in the core network may initiate this procedure and send control messages and control information of this procedure to the UE, thereby causing the UE to update its configuration information, which can be identified using this control information. Furthermore, the device in the core network may stop a function currently being executed by the UE or cause the UE to start a new function by updating the UE's configuration information.

[0350] First, the AMF starts the UE configuration update procedure by sending a configuration update command message to the UE via the 5G AN (gNB) (S1000).

[0351] Furthermore, when the UE's configuration information is updated, the AMF may send at least one of the identification information items 11 to 17 in a configuration update command message.

[0352] Specifically, when the AMF needs to update the S-NSSAI location validity information for a UE that supports S-NSSAI location validity information, the AMF may send the 11th identification information.

[0353] If the registration request message includes a requested NSSAI that includes one S-NSSAI and the S-NSSAI time validity information indicates that the S-NSSAI is not available, the AMF may send a 13th identification information.

[0354] At this time, if the second identity indicates that S-NSSAI time validity information is supported and the S-NSSAI time validity information indicates that the S-NSSAI will be available again, the AMF may send a 12th identity. Also, if the second identity indicates that S-NSSAI time validity information is supported and the S-NSSAI time validity information indicates that the S-NSSAI will not be available again, the AMF may not include the S-NSSAI in the 13th identity. Also, if the second identity indicates that S-NSSAI time validity information is not supported and the AMF sends a 13th identity, the AMF may not include the S-NSSAI in the 13th identity.

[0355] In addition, if the UE supports S-NSSAI time validity information and the AMF needs to update the S-NSSAI time validity information, the AMF may send the 12th identification information.

[0356] The AMF may send the 13th identity information when the configured NSSAI in the UE needs to be updated.

[0357] The AMF may send the fourteenth identity when it needs to update the allowed NSSAI in the UE. In addition, when the AMF allows one or more S-NSSAIs included in the third identity, the AMF may send the one or more S-NSSAIs to be allowed by including them in the fourteenth identity.

[0358] The AMF may send the fifteenth identity when it needs to update the rejected NSSAI in the UE. In addition, when the AMF rejects one or more S-NSSAIs included in the third identity, the AMF may send the one or more rejected S-NSSAIs included in the fifteenth identity.

[0359] The AMF may send the 16th identity when it needs to update the partially allowed NSSAI in the UE.

[0360] The AMF may send the 17th identity information when it needs to update the partially rejected NSSAI in the UE.

[0361] Next, the UE receives a configuration update command message and / or one or more pieces of information among the 11th to 17th identities from the network. More specifically, the UE receives a configuration update command message and / or one or more pieces of information among the 11th to 17th identities from the AMF.

[0362] The UE may recognize or store the received information based on receiving at least one of the eleventh to seventeenth identification information.

[0363] Specifically, when the UE receives the thirteenth identification information, the UE may store the content of the thirteenth identification information. Furthermore, when the UE receives the eleventh identification information, the UE may store the content of the eleventh identification information.

[0364] In addition, if the UE receives the 13th identification information but does not receive the 11th identification information, it may delete the stored S-NSSAI location validity information.

[0365] When the UE receives the thirteenth identification information, the UE may store the content of the thirteenth identification information. Furthermore, when the UE receives the twelfth identification information, the UE may store the content of the twelfth identification information.

[0366] In addition, if the UE receives the 13th identification information but does not receive the 12th identification information, it may delete the stored S-NSSAI time validity information.

[0367] When the UE receives the thirteenth identification information, the UE may store the thirteenth identification information.

[0368] Furthermore, when the UE receives the thirteenth identification information, the UE may replace the stored thirteenth identification information with the received thirteenth identification information.

[0369] Furthermore, when the UE receives the 13th identification information, it may delete the 14th and / or 16th identification information that it has stored.

[0370] Furthermore, when the UE receives the 13th identification information, it may delete the 15th and / or 17th identification information that it has stored.

[0371] When the UE receives the fourteenth identification information, the UE may store the fourteenth identification information.

[0372] Furthermore, when the UE receives the 14th identification information, the UE may replace the stored 14th identification information with the received 14th identification information.

[0373] Furthermore, when the UE receives the 14th identification information, it may delete the S-NSSAI included in the 14th identification information from the 15th and / or 17th identification information that it stores.

[0374] When the UE receives the 15th identification information, the UE may store the 15th identification information.

[0375] Furthermore, when the UE receives the 15th identification information, it may store the S-NSSAI included in the received 15th identification information in the 15th identification information that it has stored.

[0376] Furthermore, when the UE receives the 15th identification information, it may delete the S-NSSAI included in the 15th identification information from the 14th and / or 16th identification information that it stores.

[0377] Furthermore, when the UE receives the 15th identification information, the UE may delete the 15th identification information that it has stored.

[0378] When the UE receives the 16th identification information, the UE may store the 16th identification information.

[0379] Furthermore, when the UE receives the 16th identification information, the UE may replace the stored 16th identification information with the received 16th identification information.

[0380] When the UE receives the 17th identification information, the UE may store the 17th identification information.

[0381] Furthermore, when the UE receives the 17th identification information, the UE may replace the stored 17th identification information with the received 17th identification information.

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

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

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

[0385] The UE receives a configuration update command message from the AMF via the 5G AN (gNB) (S1000). The UE may update the configuration information of the UE based on the configuration update command message and / or the identification information included in the configuration update command message.

[0386] The UE may perform the above behavior after receiving a configuration update command message, or after receiving one or more of the 11th to 17th identification information.

[0387] Furthermore, when the UE receives a setting update command message, the UE may perform the behavior it performs when it receives each piece of identification information included in the setting update command message.

[0388] Furthermore, the UE may transmit a configuration update complete message to the AMF via the 5G AN (gNB) as a response message to the configuration update command message based on the identification information included in the configuration update command message (S1002).

[0389] When the UE transmits the setting update complete command message, the AMF receives the setting update complete message via the 5G AN (gNB) (S1002). In addition, each device completes this procedure based on the transmission and reception of the setting update command message and / or the setting update complete message.

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

[0391] Furthermore, the UE may store the identification information received with the configuration information command message and recognize the network's decision based on the completion of this procedure, and may perform procedures based on the stored information based on the completion of this procedure.

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

[0393] [3.3. PDU Session Establishment Procedure] Next, the PDU session establishment procedure will be described with reference to Fig. 8. Hereinafter, the PDU session establishment procedure may be referred to as this procedure. The PDU session establishment procedure may also be an SM procedure.

[0394] Note that the registration procedure may have been performed one or more times prior to this procedure.

[0395] This procedure may be performed multiple times. In other words, after the PDU session establishment procedure is completed once, the PDU session establishment procedure may be performed again.

[0396] Next, each step of the PDU session establishment procedure is described.

[0397] First, the UE transmits a PDU session establishment request message to the SMF (S1200, S1202, S1204) to start the PDU session establishment procedure. Then, the SMF receives the PDU session establishment request message from the UE.

[0398] Specifically, the UE initiates the PDU session establishment procedure by sending a first NAS message including an N1 SM container including a PDU session establishment request message to the AMF via the access network (S1200). The first NAS message is, for example, a message sent via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message.

[0399] Here, the UE may transmit one or more of the fourth to sixth identification information in the PDU session establishment request message and / or the first NAS message. The UE may also transmit one or more of the fourth to sixth identification information together with the PDU session establishment request message and / or the first NAS message. The UE may also transmit a PDU session ID of the PDU session to be established together with the PDU session establishment request message. The UE may also transmit the PDU session ID in the first NAS message.

[0400] Specifically, the UE may indicate the type of the 5GSM message by transmitting the fourth identification information. The UE may indicate that the Request type is "initial request" by transmitting the fourth identification information. Furthermore, the UE may indicate that the Request type is "existing PDU session", "initial emergency request", "existing emergency PDU session", "modification request", "MA PDU request", or "reserved" by transmitting the fourth identification information.

[0401] The UE may set the sixth identification information to "N1 SM information" when sending a PDU session establishment request message, and may set the sixth identification information to "N1 SM information" when sending a 5GSM message.

[0402] When the UE sends a PDU session establishment request message, the UE may set the fifth identification information to the 5GSM message. When the UE sends a 5GSM message, the UE may set the fifth identification information to the 5GSM message.

[0403] The UE may include the PDU session ID in the first NAS message if the sixth identification information is set to "N1 SM information" or "CIoT user data container".

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

[0405] In addition, the UE may indicate that it supports each function or indicate a request from the UE by sending a PDU session establishment request message or a first NAS message.

[0406] Furthermore, the UE may select and decide whether to include one or more of the fourth to sixth identification information in the PDU session establishment request message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0407] In addition, the UE may also include identification information other than one or more of the fourth to sixth identification information in the PDU session establishment request message and transmit it.

[0408] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is available and the UE is within the NS-AoS of the S-NSSAI, the UE may send a PDU session establishment request message for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s).

[0409] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is available but the UE is outside the NS-AoS of the S-NSSAI, the UE may not send a PDU session establishment request message for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s).

[0410] Also, if the UE is outside the NS-AoS of the S-NSSAI and the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is available, the UE may not send a PDU session establishment request message for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s).

[0411] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is not available and the UE is inside the NS-AoS of the S-NSSAI, the UE may not send a PDU session establishment request message for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s).

[0412] Also, if the UE is inside the NS-AoS of the S-NSSAI but the S-NSSAI time validity information of the S-NSSAI indicates that the S-NSSAI is not available, the UE may not send a PDU session establishment request message for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s).

[0413] If the S-NSSAI time validity information of an S-NSSAI indicates that the S-NSSAI is not available and the UE is outside the NS-AoS of the S-NSSAI, the UE may not send a PDU session establishment request message for a PDU session associated with the S-NSSAI and / or mapped S-NSSAI(s).

[0414] The UE may also send a PDU session establishment request message and / or a first NAS message and start a timer T3580. The timer T3580 may also be referred to as a first timer.

[0415] Next, when the AMF receives the first NAS message, it can recognize what the UE is requesting and / or the contents of the information, etc. (message, container, information) contained in the first NAS message.

[0416] Here, the procedure in FIG. 8(C) will be explained.

[0417] The AMF may send a second NAS message to the UE via the access network (S1224) (S1226), where the second NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

[0418] The AMF may also send a second NAS message including the tenth identity to the UE via the access network. The AMF may also send the second NAS message with the tenth identity to the UE via the access network. The AMF may also send the tenth identity and / or the second NAS message to the UE via the access network.

[0419] The AMF may determine not to forward the 5GSM message to the SMF. If the AMF determines not to forward the 5GSM message to the SMF, it may send the tenth identification information and / or the second NAS message to the UE (S1224) (S1226).

[0420] Specifically, the AMF may send the tenth identification information when indicating that the 5GSM message was not forwarded. The AMF may send the tenth identification information when indicating that the 5GSM message was not forwarded together with a PDU Session Establishment Request message with a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE.

[0421] The AMF may also send the tenth identification information if it indicates that the 5GSM message was not forwarded because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it is not in the NS-AoS of the associated S-NSSAI. In other words, the AMF may send the tenth identification information if the UE does not support S-NSSAI location validity information and if the UE requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it is not in the NS-AoS of the associated S-NSSAI.

[0422] In other words, the AMF may send the tenth identification information when it indicates that the 5GSM message was not forwarded with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message having a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0423] Furthermore, based on the reception of the uplink NAS transport message, the AMF may send a tenth identity to the UE if the sixth identity is set to "N1 SM information", the fourth identity is set to "initial request", the UE does not support S-NSSAI location validity information, the S-NSSAI is subject to NS-AoS, and the AMF determines that the UE is not in NS-AoS. At this time, the AMF may include a cause value or a back-off timer in the downlink NAS transport message. Here, the cause value may be a cause value indicating insufficient resources for a specific slice or may be 5GMM cause #69 "insufficient resources for specific slice".

[0424] Next, the UE may receive a second NAS message from the AMF (S1224) (S1226). The UE may also receive the second NAS message including the tenth identification information from the AMF. The UE may also receive the second NAS message together with the tenth identification information from the AMF. The UE may also receive the tenth identification information and / or the second NAS message from the AMF.

[0425] When the UE receives the second NAS message, it may recognize that the UE's request has been accepted and / or the contents of the information, etc. (message, container, information) contained in the second NAS message.

[0426] Specifically, when the UE receives the tenth identification information, the UE may stop the first timer and abort the PDU session establishment procedure, where the first timer may be timer T3580.

[0427] In addition, based on receiving the 10th identification information, the UE may stop timer T3581 and abort the PDU session modification procedure.

[0428] The UE may also receive the tenth identification information when the 5GSM message is indicated not to be transferred. The UE may receive the tenth identification information when the 5GSM message is indicated not to be transferred along with a PDU Session Establishment Request message having a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE.

[0429] The UE may also receive the tenth identification information when it is indicated that the 5GSM message was not forwarded because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI. In other words, the UE may receive the tenth identification information when the UE does not support S-NSSAI location validity information and when the UE requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0430] In other words, the UE may receive the tenth identification information when it is indicated that the 5GSM message was not forwarded with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message having a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0431] When the procedure in FIG. 8C is performed, the process in this procedure from (S1202) onward in FIG. 8 does not need to be performed.

[0432] Next, the AMF selects an SMF as a transfer destination for at least a portion of the information, etc. (message, container, information) included in the first NAS message received from the UE (S1202). The AMF may select the transfer destination SMF based on the information, etc. (message, container, information) included in the first NAS message, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0433] Next, the AMF sends at least a portion of the information (message, container, information) contained in the first NAS message received from the UE to the selected SMF, for example via the N11 interface (S1204).

[0434] Next, when the SMF receives information (messages, containers, information) sent from the AMF, it can recognize what the UE is requesting and / or the content of the information (messages, containers, information) received from the AMF.

[0435] Specifically, when the AMF and / or SMF receive the fourth identification information, they may recognize the type of the 5GSM message. When the AMF and / or SMF receive the fourth identification information, they may recognize that the Request type is "initial request". Furthermore, when the AMF and / or SMF receive the fourth identification information, they may recognize that the Request type is "existing PDU session", or "initial emergency request", or "existing emergency PDU session", or "modification request", or "MA PDU request", or "reserved".

[0436] Here, the SMF may perform a second condition determination. The second condition determination may be for determining whether the network accepts the UE request. If the SMF determines that the second condition determination is true, it may start the procedure of (A) in Figure 8, and if the SMF determines that the second condition determination is false, it may start the procedure of (B) in Figure 8.

[0437] Note that the second condition determination may be performed by an NF other than the SMF. When an NF other than the SMF performs the second condition determination, the SMF may provide the NF with information necessary for performing the second condition determination, specifically, at least a portion of the information received from the UE (S1206). Then, when the NF determines whether the second condition determination is true or false based on the information received from the SMF, it may convey information including the result of the second condition determination (i.e., true or false) to the SMF. The SMF may determine identification information and / or a control message to be transmitted to the UE based on the result of the second condition determination received from the NF.

[0438] Furthermore, the second condition determination may be performed based on information received from the AMF (message, container, information), and / or subscription information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

[0439] For example, if the network permits the UE's request, the second condition determination may be determined as true, and if the network does not permit the UE's request, the second condition determination may be determined as false. Furthermore, if the network to which the UE is connected and / or a device within the network supports the function requested by the UE, the second condition determination may be determined as true, and if the function requested by the UE is not supported, the second condition determination may be determined as false. Furthermore, if the transmitted and received identification information is permitted, the second condition determination may be determined as true, and if the transmitted and received identification information is not permitted, the second condition determination may be determined as false.

[0440] The conditions for determining whether the second condition is true or false are not limited to the above-mentioned conditions.

[0441] Next, each step of the procedure in FIG. 8(A) will be explained.

[0442] The SMF may select a UPF for the PDU session to be established and may send an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S1208). The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0443] Here, the SMF may select one or more UPFs based on information received from the AMF (message, container, information), and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc. If multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that a UPF is selected.

[0444] Next, when the UPF receives the N4 session establishment request message (S1208), it can recognize the content of the information received from the SMF. Furthermore, based on the reception of the N4 session establishment request message, the UPF may send an N4 session establishment response message to the SMF, for example, via the N4 interface (S1210).

[0445] Next, when the SMF receives an N4 session establishment response message as a response message to the N4 session establishment request message, it can recognize the contents of the information received from the UPF.

[0446] Next, the SMF sends a PDU session establishment accept message to the UE based on the reception of the PDU session establishment request message, and / or the selection of the UPF, and / or the reception of the N4 session establishment response message (S1212) (S1214) (S1216).

[0447] Specifically, the SMF sends an N1 SM container, N2 SM information, and / or a PDU session ID to the AMF, for example, via the N11 interface, based on receiving a PDU session establishment request message, selecting a UPF, and / or receiving an N4 session establishment response message (S1212). Here, the N1 SM container may include a PDU session establishment accept message. Furthermore, the PDU session ID may be included in the PDU session establishment accept message.

[0448] Next, the AMF that receives the N1 SM container, and / or the N2 SM information, and / or the PDU session ID, sends a second NAS message to the UE via the access network (S1214) (S1216). Here, the second NAS message is sent, for example, via the N1 interface. Also, the second NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

[0449] Specifically, the AMF sends an N2 PDU session request message to the access network (S1214). The access network that receives the N2 PDU session request message sends a second NAS message to the UE (S1216). Here, the N2 PDU session request message may include a second NAS message and / or N2 SM information. The second NAS message may also include a PDU session ID and / or an N1 SM container.

[0450] The PDU session establishment acceptance message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been accepted.

[0451] Here, the SMF and / or AMF may indicate that at least part of the UE's request in the PDU session establishment request message has been accepted by sending a PDU session establishment acceptance message, and / or an N1 SM container, and / or a PDU session ID, and / or a second NAS message, and / or N2 SM information, and / or an N2 PDU session request message.

[0452] Here, the SMF and / or AMF may include the 10th identification information in and send the PDU session establishment acceptance message, and / or the N1 SM container, and / or the second NAS message, and / or the N2 SM information, and / or the N2 PDU session request message.

[0453] Specifically, the AMF and / or SMF may send the tenth identification information when indicating that the 5GSM message was not forwarded. The AMF and / or SMF may send the tenth identification information when indicating that the 5GSM message was not forwarded together with a PDU Session Establishment Request message with a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE.

[0454] The AMF and / or SMF may also send the tenth identification information if it indicates that the 5GSM message was not forwarded because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI. In other words, the AMF and / or SMF may send the tenth identification information if the UE does not support S-NSSAI location validity information and if the UE requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0455] In other words, the AMF and / or SMF may send the tenth identification information when it is indicated that the 5GSM message was not forwarded with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0456] Furthermore, by sending this identification information and / or a PDU session establishment acceptance message, the SMF may indicate that the network supports each function, may indicate that the UE request has been accepted, may indicate that the request from the UE has not been permitted, or may indicate a combination of these.

[0457] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment acceptance message, and / or the N1 SM container, and / or the second NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0458] Next, the UE receives a PDU session establishment acceptance message and / or a second NAS message from the SMF (S1212) (S1214) (S1216). The UE may also receive the PDU session establishment acceptance message and / or the second NAS message including the tenth identification information from the SMF. When the UE receives the PDU session establishment acceptance message and / or the second NAS message, the UE may recognize that the UE's request in the PDU session establishment request message has been accepted and / or the contents of the information, etc. (message, container, information) included in the second NAS message.

[0459] Specifically, when the UE receives the tenth identification information, the UE may stop the first timer and abort the PDU session establishment procedure, where the first timer may be timer T3580.

[0460] In addition, based on receiving the 10th identification information, the UE may stop timer T3581 and abort the PDU session modification procedure.

[0461] The UE may also receive the tenth identification information when the 5GSM message is indicated not to be transferred. The UE may receive the tenth identification information when the 5GSM message is indicated not to be transferred along with a PDU Session Establishment Request message having a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE.

[0462] The UE may also receive the tenth identification information when it is indicated that the 5GSM message was not forwarded because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI. In other words, the UE may receive the tenth identification information when the UE does not support S-NSSAI location validity information and when the UE requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0463] In other words, the UE may receive the tenth identification information when it is indicated that the 5GSM message was not forwarded with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message having a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0464] In addition, when the UE receives a PDU session establishment acceptance message and / or a second NAS message, it may perform the behavior upon receiving each identification information included in the PDU session establishment acceptance message and / or the second NAS message.

[0465] Furthermore, when the UE receives a PDU session establishment acceptance message and / or a second NAS message, it may stop timer T3580 and recognize that the PDU session has been established.

[0466] Next, each step of the procedure in FIG. 8(B) will be explained.

[0467] First, the SMF sends a PDU session establishment reject message to the UE (S1218) (S1220) (S1222).

[0468] Specifically, based on receiving the PDU session establishment request message, the SMF sends an N1 SM container and / or a PDU session ID to the AMF, for example, via the N11 interface (S1218). Here, the N1 SM container may include a PDU session establishment rejection message. Furthermore, the PDU session ID may be included in the PDU session establishment rejection message.

[0469] Next, the AMF that has received the N1 SM container and / or the PDU session ID sends a second NAS message to the UE via the access network (S1220) (S1222). Here, the second NAS message is sent, for example, via the N1 interface. The second NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The second NAS message may include the PDU session ID and / or the N1 SM container.

[0470] The PDU session establishment rejection message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been rejected.

[0471] Here, the SMF and / or AMF may indicate that the UE's request via the PDU session establishment request message has been rejected by sending a PDU session establishment rejection message, and / or an N1 SM container, and / or a PDU session ID, and / or a second NAS message.

[0472] Furthermore, by sending a PDU session establishment rejection message, the SMF may indicate that the UE request has been rejected, or that the request from the UE has not been permitted, or may indicate a combination of these.

[0473] Here, the SMF and / or AMF may include the 10th identification information in and send the PDU session establishment rejection message, and / or the N1 SM container, and / or the second NAS message, and / or the N2 SM information, and / or the N2 PDU session request message.

[0474] Specifically, the AMF and / or SMF may send the tenth identification information when indicating that the 5GSM message was not forwarded. The AMF and / or SMF may send the tenth identification information when indicating that the 5GSM message was not forwarded together with a PDU Session Establishment Request message with a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE.

[0475] The AMF and / or SMF may also send the tenth identification information if it indicates that the 5GSM message was not forwarded because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI. In other words, the AMF and / or SMF may send the tenth identification information if the UE does not support S-NSSAI location validity information and if the UE requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0476] In other words, the AMF and / or SMF may send the tenth identification information when it is indicated that the 5GSM message was not forwarded with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0477] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment rejection message, and / or the N1 SM container, and / or the second NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0478] Furthermore, the SMF and / or AMF may include information indicating that the UE request has been rejected in the PDU session establishment rejection message, and / or the N1 SM container, and / or the second NAS message, and / or the N2 SM information, and / or the N2 PDU session request message, and may transmit the information indicating that the UE request has been rejected, and may indicate the reason why the UE request has been rejected. Furthermore, the UE may recognize the reason why the UE request has been rejected by receiving the information indicating that the UE request has been rejected. Note that the reason for the rejection may be information indicating that the content indicated by the identification information received by the SMF and / or AMF is not permitted and / or unavailable.

[0479] Next, the UE receives a second NAS message and / or a PDU session establishment rejection message (S1218) (S1220) (S1222). The UE may also receive the PDU session establishment rejection message and / or the second NAS message including the tenth identification information from the SMF. When the UE receives the PDU session establishment rejection message and / or the second NAS message, the UE may recognize that the UE's request via the PDU session establishment request message has been rejected and / or the contents of the information, etc. (message, container, information) included in the second NAS message.

[0480] Specifically, when the UE receives the tenth identification information, the UE may stop the first timer and abort the PDU session establishment procedure, where the first timer may be timer T3580.

[0481] In addition, based on receiving the 10th identification information, the UE may stop timer T3581 and abort the PDU session modification procedure.

[0482] The UE may also receive the tenth identification information when the 5GSM message is indicated not to be transferred. The UE may receive the tenth identification information when the 5GSM message is indicated not to be transferred along with a PDU Session Establishment Request message having a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE.

[0483] The UE may also receive the tenth identification information when it is indicated that the 5GSM message was not forwarded because a UE that does not support S-NSSAI location validity information requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI. In other words, the UE may receive the tenth identification information when the UE does not support S-NSSAI location validity information and when the UE requested the forwarding of a 5GSM message with a request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0484] In other words, the UE may receive the tenth identification information when it is indicated that the 5GSM message was not forwarded with a PDU session establishment request message having a PDU session ID IE set to the same value as the PDU session ID sent by the UE because the UE, which does not support S-NSSAI location validity information, requested the forwarding of the 5GSM message with the request type IE set to "initial request" when it was not in the NS-AoS of the associated S-NSSAI.

[0485] In addition, when the UE receives a PDU session establishment rejection message and / or a second NAS message, it may perform the behavior upon receiving each identification information included in the PDU session establishment rejection message and / or the second NAS message.

[0486] Furthermore, if the UE receives a PDU session establishment rejection message and / or a second NAS message, it may stop timer T3580 and recognize that the PDU session has not been established.

[0487] Each device may complete this procedure based on sending and receiving a PDU session establishment acceptance message. Each device may also establish a PDU session based on the completion of this procedure. At this time, each device may transition to a state in which it can communicate with the DN using the established PDU session.

[0488] Alternatively, each device may complete this procedure based on sending and receiving a PDU session establishment rejection message. In this case, each device cannot establish a PDU session, and therefore cannot communicate with the DN if there is no already established PDU session.

[0489] Next, the UE behavior when timer T3580 expires will be described. In other words, the UE behavior when, after transmitting a PDU session establishment request message and starting timer T3580, the UE does not receive a PDU session establishment accept message, a PDU session establishment reject message, or a second NAS message before timer T3580 expires will be described.

[0490] The UE may retransmit the PDU Session Establishment Request message and the PDU session information sent with the initial transmission of the PDU Session Establishment Request message, and may reset and start timer T3580. This retransmission may be repeated up to four times.

[0491] If a PDU session establishment request message is sent with the fourth identification set to "initial emergency request" or "existing emergency PDU session", the UE may inform upper layers of the failure of this procedure. If a PDU session establishment request message is sent with the fourth identification set to "initial emergency request" or "existing emergency PDU session", the UE may locally de-register and attempt initial registration for emergency services.

[0492] Also, when the UE sends a PDU session establishment request message to perform a handover of an existing emergency PDU session between 3GPP access and non-3GPP access, the UE may recognize that the emergency PDU session is associated with the source access type.

[0493] Next, the UE behavior and / or network behavior when the current NS-AoS is changed will be described. In other words, the UE behavior and / or network behavior when the UE moves outside the NS-AoS during this procedure will be described. In other words, the UE behavior and / or network behavior when the UE is performing this procedure inside the NS-AoS and moves outside the NS-AoS before this procedure is completed will be described. Here, the network may be an AMF or an SMF.

[0494] If the UE moves outside of NS-AoS before the procedure is completed, the procedure may be aborted and immediately restarted by the UE and / or the network.

[0495] Also, if the UE moves out of the NS-AoS before this procedure is completed, the UE may remove the associated S-NSSAI from the allowed NSSAI. In other words, if the UE moves out of the NS-AoS before this procedure is completed, the UE may remove the S-NSSAI associated with the PDU session in this procedure from the allowed NSSAI.

[0496] In addition, each of the processes performed by the UE based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0497] [4. Modifications] The program that runs on the device according to 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 the 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 other storage device system.

[0498] A program for realizing the functions of the embodiments according to the present invention 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 also 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.

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

[0500] It should be noted that this example is not limited to the above-described embodiment. In the embodiment, one example of a device is described, but this example 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.

[0501] Although the embodiment of this example has been described in detail above with reference to the drawings, the specific configuration is not limited to this example, and design modifications within the scope of the gist of this example are also included. Furthermore, this example can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this example. 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 User Equipment (UE) having a control unit, characterized in that, based on receipt of first information, the control unit stops a first timer and aborts a PDU session establishment procedure, the first information indicating that the 5GSM message was not forwarded with a PDU session establishment request message having a PDU Session ID IE set to the same value as the PDU Session ID sent by the UE because a UE that does not support the S-NSSAI location validity information requested forwarding of a 5GSM message having a request type IE set to "initial request" when not in a Network slice area of ​​service (NS-AoS) of an associated Single Network Slice Selection Assistance Information (S-NSSAI).

Images