User equipment (UE), and access and mobility management function (AMF)

Abstract

A slice non-registration inactivity timer is started when S-NSSAI is not used by a PDU session on a corresponding access type except when the PDU session is an MA PDU session. The slice non-registration inactivity timer is stopped and reset when an MA PDU session associated with on-demand S-NSSAI is successfully established on a 3GPP access and / or a non-3GPP access. This makes it possible to clearly define start, stop, and reset conditions for the slice non-registration inactivity timer in the MA PDU session.

Description

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

[0001] This embodiment relates to UE (User Equipment) and AMF (Access and Mobility Management Function). This application is based on Japanese Patent Application No. 2023-111181 filed on July 6, 2023, and the contents of this application 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 and 2). 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 3).

[0003] 3GPP TS 24.501 V18.2.1 (2023-03); 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.2.0 (2023-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)3GPP 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 manage NSs with a timer so that NSs that have not been used for a certain period of time will be deleted from the UE. However, there are some unclear aspects regarding the method for managing the timer, such as the timing to start the timer for an MA PDU session.

[0005] This embodiment has been made in view of the above circumstances. In this embodiment, the conditions for starting, stopping, and resetting the slice non-registration inactivity timer in an MA PDU session are clarified.

[0006] The UE of this embodiment is User Equipment (UE) having a transceiver unit and a control unit, and in a PDU session establishment procedure for establishing a PDU session, the transceiver unit receives a PDU session establishment accept message, and if the UE supports network slice usage control, and further, if the PDU session is an MA PDU session and the MA PDU session is successfully established over 3GPP access and / or non-3GPP access, the control unit stops and resets a slice non-registration inactivity timer for an on-demand S-NSSAI, and the slice non-registration inactivity timer is stopped and reset when the MA PDU session related to the on-demand S-NSSAI is successfully established over 3GPP access and / or non-3GPP access.

[0007] The UE of this embodiment is User Equipment (UE) having a transceiver unit and a control unit, and in a PDU session establishment procedure for establishing a PDU session, the transceiver unit receives a PDU session establishment accept message, and if the UE supports network slice usage control, and if the PDU session is an MA PDU session and user plane resources of the MA PDU session are successfully established over 3GPP access or non-3GPP access, the control unit stops and resets a slice non-registration inactivity timer for an on-demand S-NSSAI, and the slice non-registration inactivity timer is stopped and reset when user plane resources of the MA PDU session related to the on-demand S-NSSAI are successfully established over 3GPP access or non-3GPP access.

[0008] According to this embodiment, it is possible to clarify the conditions for starting, stopping, and resetting the slice non-registration inactivity timer in an MA PDU session.

[0009] 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. FIG. 9 is a diagram illustrating a network-initiated session management procedure. FIG. 10 is a diagram illustrating a UE-initiated session management procedure.

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

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

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

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

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

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

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

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

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

[0019] Furthermore, access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Note that, hereinafter, the symbol for gNB 122 may be abbreviated, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs and connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in the 4G system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

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

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

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

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

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

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

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

[0027] Also, while FIG. 1 illustrates a case where the PDN and the DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may mean connecting to a communication terminal or a server device located in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal or a server device located in the PDN. The PDN may be referred to as the DN, and the DN may be referred to as the PDN.

[0028] In addition, hereinafter, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device sends or receives a message and / or performs a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein send or receive a message and / or perform a procedure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] In addition, one or more AMFs may be placed in the core network _B. In addition, the AMF may be 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0076] The UPF has functions 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.

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

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

[0079] Furthermore, the control plane refers to control messages transmitted and received to control UE communications, etc. The control plane may be transmitted and received using a 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0104] 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."

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

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

[0107] 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."

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

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

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

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

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

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

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

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

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

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

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

[0119] 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."

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

[0121] 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."

[0122] Next, ATSSS (Access Traffic Steering, Switching and Splitting) may be a function that enables a multi-access PDU connection service. ATSSS may be a function supported by the UE and / or the network. ATSSS may be a function supported by the UE and / or the network to establish an MA PDU session.

[0123] Next, a Multi-Access PDU (MA PDU) session may be a PDU session that can have user plane resources in two access networks. Here, the two access networks may be a combination of 3GPP access and non-3GPP access, a combination of 3GPP access and 3GPP access, or a combination of non-3GPP access and non-3GPP access. In other words, the MA PDU session may be capable of exchanging PDUs between a UE and a DN by simultaneously using both 3GPP access and non-3GPP access, or by simultaneously using both 3GPP access and 3GPP access, or by simultaneously using both non-3GPP access and non-3GPP access. In other words, an MA PDU session is a PDU session that provides a PDU connection service, and at a given time, it may be possible to use one access network, or it may be possible to use one 3GPP access network and one non-3GPP access network at the same time, or it may be possible to use two 3GPP access networks at the same time, or it may be possible to use two non-3GPP access networks at the same time.

[0124] Furthermore, a Multi-Access PDU (MA PDU) session may be a PDU session that can have user plane resources in two networks. Here, the two access networks may be a combination of PLMN and NPN, a combination of PLMN and PLMN, or a combination of NPN and NPN. In other words, the MA PDU session may be capable of exchanging PDUs between a UE and a DN by simultaneously using both PLMN and NPN, by simultaneously using both PLMN and PLMN, or by simultaneously using both NPN and NPN.

[0125] Alternatively, the MA PDU session may be a PDU session that can have one or more user plane resources for each RAT type. Alternatively, the MA PDU session may be a PDU session that can have one or more user plane resources for each satellite NG-RAN RAT type. Alternatively, the MA PDU session may be a PDU session that can have one or more user plane resources for one terrestrial NG-RAN RAT type and one satellite NG-RAN RAT type. In this case, the MA PDU session may be named differently, for example, it may be named MA PDU session for RAT type.

[0126] It also explains how to handle MA PDU sessions when the deregistration procedure is completed.

[0127] First, the case where the UE-initiated de-registration procedure for 5GS services over 3GPP access is completed, and the case where the network-initiated de-registration procedure is completed and the de-registration request is for 3GPP access will be described. First, if there is an MA PDU session with user plane resources established in both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the AMF triggers the SMF to perform release of user plane resources in 3GPP access, and the UE recognizes that the user plane resources of 3GPP access have been released. Next, if there is an MA PDU session with user plane resources established only in 3GPP access, the AMF triggers the SMF to locally release the MA PDU session, and the UE locally releases the MA PDU session.

[0128] Next, the case where the UE-initiated de-registration procedure for 5GS services over non-3GPP access is completed, and the case where the network-initiated de-registration procedure is completed and the de-registration request is for non-3GPP access will be described. First, if there is an MA PDU session with user plane resources established in both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the AMF triggers the SMF to perform release of user plane resources in non-3GPP access, and the UE recognizes that the user plane resources of non-3GPP access have been released. Next, if there is an MA PDU session with user plane resources established only in non-3GPP access, the AMF triggers the SMF to locally release the MA PDU session, and the UE locally releases the MA PDU session.

[0129] Furthermore, the MA PDU session may be a PDU session using user plane resources via satellite and / or user plane resources via non-satellite (terrestrial). Here, the user plane resources via satellite may be user plane resources via 3GPP access, user plane resources via non-3GPP access, or user plane resources in a RAT type of satellite NG-RAN. Furthermore, the user plane resources via non-satellite (terrestrial) may be user plane resources via 3GPP access, user plane resources via non-3GPP access, or user plane resources different from a RAT type of satellite NG-RAN.

[0130] In addition, an MA PDU session using two 3GPP access networks and an MA PDU session using two non-3GPP access networks may be referred to as a PDU session different from an MA PDU session.

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

[0132] The satellite NG-RAN Radio Access Technology (RAT) type may be information used to identify or distinguish different types of satellite NG-RAN access in satellite NG-RAN access. The satellite NG-RAN RAT type may include, for example, "NR (LEO)," "NR (MEO)," "NR (GEO)," and "NR (OTHERSAT)." Here, "LEO" may mean a low earth orbit satellite, "MEO" may mean a medium earth orbit satellite, "GEO" may mean a geostationary earth orbit satellite, and "OTHERSAT" may mean other satellites. The satellite NG-RAN RAT type may be a RAT type.

[0133] Next, network slice usage control may be control by a network to restrict a network slice for a UE. In the network slice usage control, a network-controlled slice usage policy may be configured for the UE. In the network slice usage control, a PDU sessions inactivity timer and a network slice deregistration inactivity timer may be configured.

[0134] A network-controlled slice usage policy may be a policy for realizing network slice usage control.

[0135] Next, the on-demand S-NSSAI may be an S-NSSAI that is allowed to be registered in the network only when the UE establishes a PDU session for user data transmission and reception.

[0136] An on-demand S-NSSAI may be one or more S-NSSAIs in a configured NSSAI. An on-demand S-NSSAI may be one or more S-NSSAIs in an allowed NSSAI. An on-demand S-NSSAI may be one or more S-NSSAIs in an on-demand NSSAI.

[0137] The on-demand S-NSSAI may be an S-NSSAI for realizing network slice usage control. The on-demand S-NSSAI may simply be read as an S-NSSAI.

[0138] Next, the slice deregistration inactivity timer may be a timer that causes the UE to deregister the network slice for all on-demand S-NSSAIs of the HPLMN in the configured NSSAI after the PDU sessions associated with that S-NSSAI are released.

[0139] The slice non-registration inactivity timer may be started and / or stopped by the UE and / or AMF for each access type. The slice non-registration inactivity timer may be started and / or stopped by the UE and / or AMF for an MA PDU session regardless of the access type.

[0140] The slice non-registration inactivity timer may be started in the UE and / or the AMF for each access type when a PDU session associated with the S-NSSAI is released. The slice non-registration inactivity timer may be started in the UE and / or the AMF for each access type when the network is included in the allowed NSSAI and no PDU session is established.

[0141] The slice non-registration inactivity timer may be stopped and reset when a PDU session is established. The slice non-registration inactivity timer may be stopped and reset when an S-NSSAI is removed from the allowed NSSAIs.

[0142] The conditions for starting and stopping the slice non-registration inactivity timer are not limited to these. Here, the S-NSSAI may be an on-demand S-NSSAI.

[0143] When the slice non-registration inactivity timer expires, the AMF and / or the UE may locally remove the S-NSSAI from the allowed NSSAI. The AMF may send a UE Configuration Update Command message to remove the slice from the allowed NSSAI.

[0144] The slice non-registration inactivity timer may be a timer for realizing network slice usage control.

[0145] The slice non-registration inactivity timer for on-demand S-NSSAI may be simply expressed as a slice non-registration inactivity timer.

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

[0147] The first identification information may be information indicating whether network slice usage control is supported. The first identification information may be information indicating that network slice usage control is supported. The first identification information may be information indicating that network slice usage control is not supported. The first identification information may be information within the 5GMM capability.

[0148] The second identification information may be a request type information element. The request type information element may simply be expressed as a request type. The second identification information may be a request type information element with "MA PDU request" set. The request type information element may be set to "MA PDU request" when the UE requests an MA PDU session.

[0149] The second identification information may be a request type information element set to initial request, or existing PDU session, or initial emergency request, or existing emergency PDU session, or modification request, or reserved.

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

[0151] The tenth identity may be an S-NSSAI that is allowed to be registered in the network only when the UE establishes a PDU session for user data transmission and reception.

[0152] The tenth identity may be an on-demand S-NSSAI. The tenth identity may be one or more S-NSSAIs in a configured NSSAI. The tenth identity may be one or more S-NSSAIs in an allowed NSSAI.

[0153] The tenth identification information may be associated with the eleventh identification information and / or the fourteenth identification information. The tenth identification information may be determined based on the fourteenth identification information.

[0154] The eleventh identification information may be a timer value. The eleventh identification information may be a timer value of a slice non-registration inactivity timer.

[0155] The eleventh identification information may be a slice non-registration inactivity timer. The eleventh identification information may be a slice non-registration inactivity timer with a timer value set.

[0156] The eleventh identification information may be information pre-configured in the UE and / or the network.

[0157] The eleventh identity may be associated with the tenth identity. The eleventh identity may be included in the tenth identity. The eleventh identity may be associated with the on-demand S-NSSAI. The eleventh identity may be a timer value within the on-demand S-NSSAI. The eleventh identity may be a timer value for the on-demand S-NSSAI.

[0158] The twelfth identification information may be an access type information element (Access type IE), and may be information indicating 3GPP access or non-3GPP access.

[0159] The thirteenth identification information may be a network-controlled slice usage policy. The thirteenth identification information may include the tenth, eleventh, and fourteenth identification information.

[0160] The fourteenth identification information may be information indicating whether the UE registers with the network slice only when an application in the UE requires data transmission in the network slice for one or more S-NSSAIs of the HPLMN in the configured NSSAI. The fourteenth identification information may be information indicating that one or more S-NSSAIs in the configured NSSAI are on-demand S-NSSAIs. The fourteenth identification information may be an on-demand S-NSSAI indication.

[0161] The fifteenth identification information may be information indicating that the network supports ATSSS (Access Traffic Steering, Switching and Splitting). The fifteenth identification information may be information indicating that the network does not support ATSSS. The fifteenth identification information may be information indicating whether the network supports ATSSS.

[0162] The fifteenth identification information may be 5GS network feature support. The fifteenth identification information may be information indicating whether ATSSS is supported within the 5GS network feature support. The information indicating whether ATSSS is supported may be included in the 5GS network feature support.

[0163] The sixteenth identity may be a configured NSSAI. The sixteenth identity may be one or more S-NSSAIs within the configured NSSAI. The sixteenth identity may be a configured NSSAI that includes the tenth identity. The sixteenth identity may be a configured NSSAI associated with the tenth, and / or thirteenth, and / or fourteenth identities. The sixteenth identity may be one or more S-NSSAIs within the configured NSSAI associated with the tenth, and / or thirteenth, and / or fourteenth identities.

[0164] The seventeenth identity may be an allowed NSSAI. The seventeenth identity may be one or more S-NSSAIs within the allowed NSSAI. The seventeenth identity may be an allowed NSSAI that includes the tenth identity. The seventeenth identity may be an allowed NSSAI associated with the tenth, and / or thirteenth, and / or fourteenth identities. The seventeenth identity may be one or more S-NSSAIs within the allowed NSSAI associated with the tenth, and / or thirteenth, and / or fourteenth identities.

[0165] The 18th identification information may be information indicating a RAT type. The 18th identification information may be information indicating a RAT type of a terrestrial NG-RAN, or may be information indicating a RAT type of a satellite NG-RAN. The 18th identification information may be information including information indicating a RAT type of a terrestrial NG-RAN and information indicating a RAT type of a satellite NG-RAN. The 18th identification information may be information combining information indicating a RAT type of a terrestrial NG-RAN and information indicating a RAT type of a satellite NG-RAN.

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

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

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

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

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

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

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

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

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

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

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

[0177] Here, the UE may transmit one or more of the first and third identification information by including them in a registration request message and / or an RRC message. More specifically, the UE may transmit one or more of the first and third identification information by including them in a registration request message and / or an RRC message, or may transmit one or more of the first and third identification information by including them 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).

[0178] Specifically, if the UE supports network slice usage control, the UE may transmit first identification information indicating that the UE supports network slice usage control. If the UE does not support network slice usage control, the UE may transmit first identification information indicating that the UE does not support network slice usage control.

[0179] The UE may send the requested network slice as a requested NSSAI. In other words, the UE may send the third identity when requesting a network slice.

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

[0181] Furthermore, the UE may include one or more of the first and third identification information in a registration request message and transmit the message, thereby indicating to the network the contents indicated by the identification information included in the registration request message.

[0182] In addition, the UE may select and decide whether to include one or more of the first and third identification information 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.

[0183] The UE may also transmit identification information other than the first and third identification information in the registration request message.

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

[0185] Specifically, when the network receives the first identification information, the network may recognize that the UE supports network slice usage control. When the network receives the first identification information, the network may recognize that the UE does not support network slice usage control.

[0186] When the network receives the third identification information, it may recognize the network slice requested by the UE.

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

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

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

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

[0191] Furthermore, the AMF may indicate to the UE the contents indicated by one or more of the identification information 10 to 11 and 13 to 17 by including the identification information in the registration acceptance message and sending it.

[0192] Furthermore, the AMF may select and decide whether to include one or more of the identification information 10 to 11 and 13 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.

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

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

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

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

[0197] Specifically, when the UE receives the tenth identification information, the UE may store the tenth identification information as an on-demand S-NSSAI. When the UE receives the tenth identification information, the UE may recognize that the received S-NSSAI is an on-demand S-NSSAI. When the UE receives the tenth identification information, the UE may store the tenth identification information in the configured NSSAI or the allowed NSSAI.

[0198] When the UE receives the eleventh identification information, the UE may start a slice non-registration inactivity timer using the eleventh identification information. When the UE receives the eleventh identification information, the UE may stop and reset a slice non-registration inactivity timer using the eleventh identification information. When the UE receives the eleventh identification information, the UE may associate the tenth identification information with the eleventh identification information and store them. That is, when the UE receives the eleventh identification information, the UE may store the eleventh identification information for a certain on-demand S-NSSAI.

[0199] When the UE receives the thirteenth identification information, the UE may recognize and store the network-controlled slice usage policy. When the UE receives the thirteenth identification information, the UE may use the thirteenth identification information to determine the tenth and eleventh identification information.

[0200] When the UE receives the fourteenth identification information, it may recognize that one or more S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize which S-NSSAIs among the one or more S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize that all S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize that one or more S-NSSAIs included in the configured NSSAI are not on-demand S-NSSAIs.

[0201] If the UE receives the 15th identification information, it may recognize that the network supports ATSSS.

[0202] When the UE receives the 16th identification information, the UE may store the received configured NSSAI. When the UE receives the 16th identification information, the UE may store the received S-NSSAI as the configured NSSAI. When the UE receives the 16th identification information, the UE may store the received 16th identification information as the configured NSSAI. Furthermore, when the UE already has a configured NSSAI stored, the UE may update the received 16th identification information as the configured NSSAI.

[0203] When the UE receives the 17th identification information, it may store the received allowed NSSAI. When the UE receives the 17th identification information, it may store the received S-NSSAI as an allowed NSSAI. When the UE receives the 17th identification information, it may store the received 17th identification information as an allowed NSSAI. Furthermore, when the UE already has an allowed NSSAI stored, it may update the received 17th identification information as a new allowed NSSAI.

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

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

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

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

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

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

[0210] 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 10 to 11 and 13 to 17 in the registration rejection message and sending it.

[0211] Furthermore, the AMF may select and decide whether to include one or more of the identification information 10 to 11 and 13 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.

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

[0213] Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). The UE may also receive from the AMF a registration rejection message including one or more of the identification information items 10 to 11 and 13 to 17. 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.

[0214] Specifically, when the UE receives the tenth identification information, the UE may store the tenth identification information as an on-demand S-NSSAI. When the UE receives the tenth identification information, the UE may recognize that the received S-NSSAI is an on-demand S-NSSAI. When the UE receives the tenth identification information, the UE may store the tenth identification information in the configured NSSAI or the allowed NSSAI.

[0215] When the UE receives the eleventh identification information, the UE may start a slice non-registration inactivity timer using the eleventh identification information. When the UE receives the eleventh identification information, the UE may stop and reset a slice non-registration inactivity timer using the eleventh identification information. When the UE receives the eleventh identification information, the UE may associate the tenth identification information with the eleventh identification information and store them. That is, when the UE receives the eleventh identification information, the UE may store the eleventh identification information for a certain on-demand S-NSSAI.

[0216] When the UE receives the thirteenth identification information, the UE may recognize and store the network-controlled slice usage policy. When the UE receives the thirteenth identification information, the UE may use the thirteenth identification information to determine the tenth and eleventh identification information.

[0217] When the UE receives the fourteenth identification information, it may recognize that one or more S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize which S-NSSAIs among the one or more S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize that all S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize that one or more S-NSSAIs included in the configured NSSAI are not on-demand S-NSSAIs.

[0218] If the UE receives the 15th identification information, it may recognize that the network supports ATSSS.

[0219] When the UE receives the 16th identification information, the UE may store the received configured NSSAI. When the UE receives the 16th identification information, the UE may store the received S-NSSAI as the configured NSSAI. When the UE receives the 16th identification information, the UE may store the received 16th identification information as the configured NSSAI. Furthermore, when the UE already has a configured NSSAI stored, the UE may update the received 16th identification information as the configured NSSAI.

[0220] When the UE receives the 17th identification information, it may store the received allowed NSSAI. When the UE receives the 17th identification information, it may store the received S-NSSAI as an allowed NSSAI. When the UE receives the 17th identification information, it may store the received 17th identification information as an allowed NSSAI. Furthermore, when the UE already has an allowed NSSAI stored, it may update the received 17th identification information as a new allowed NSSAI.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0236] The UE may recognize or store the received information based on receiving at least one of the identification information items 10 to 11 and 13 to 17.

[0237] Specifically, when the UE receives the tenth identification information, the UE may store the tenth identification information as an on-demand S-NSSAI. When the UE receives the tenth identification information, the UE may recognize that the received S-NSSAI is an on-demand S-NSSAI. When the UE receives the tenth identification information, the UE may store the tenth identification information in the configured NSSAI or the allowed NSSAI.

[0238] When the UE receives the eleventh identification information, the UE may start a slice non-registration inactivity timer using the eleventh identification information. When the UE receives the eleventh identification information, the UE may stop and reset a slice non-registration inactivity timer using the eleventh identification information. When the UE receives the eleventh identification information, the UE may associate the tenth identification information with the eleventh identification information and store them. That is, when the UE receives the eleventh identification information, the UE may store the eleventh identification information for a certain on-demand S-NSSAI.

[0239] When the UE receives the thirteenth identification information, the UE may recognize and store the network-controlled slice usage policy. When the UE receives the thirteenth identification information, the UE may use the thirteenth identification information to determine the tenth and eleventh identification information.

[0240] When the UE receives the fourteenth identification information, it may recognize that one or more S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize which S-NSSAIs among the one or more S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize that all S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the fourteenth identification information, it may recognize that one or more S-NSSAIs included in the configured NSSAI are not on-demand S-NSSAIs.

[0241] If the UE receives the 15th identification information, it may recognize that the network supports ATSSS.

[0242] When the UE receives the 16th identification information, the UE may store the received configured NSSAI. When the UE receives the 16th identification information, the UE may store the received S-NSSAI as the configured NSSAI. When the UE receives the 16th identification information, the UE may store the received 16th identification information as the configured NSSAI. Furthermore, when the UE already has a configured NSSAI stored, the UE may update the received 16th identification information as the configured NSSAI.

[0243] When the UE receives the 17th identification information, it may store the received allowed NSSAI. When the UE receives the 17th identification information, it may store the received S-NSSAI as an allowed NSSAI. When the UE receives the 17th identification information, it may store the received 17th identification information as an allowed NSSAI. Furthermore, when the UE already has an allowed NSSAI stored, it may update the received 17th identification information as a new allowed NSSAI.

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

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

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

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

[0248] The UE may perform the above behavior after receiving a configuration update command message, or after receiving one or more of the identification information items 10 to 11 and 13 to 17.

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

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

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

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

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

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

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

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

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

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

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

[0260] Here, the UE may transmit one or more of the first to third identification information in a PDU session establishment request message or a NAS message, and may transmit the second identification information in a UL NAS transport message.

[0261] Specifically, if the UE supports network slice usage control, the UE may transmit first identification information indicating that the UE supports network slice usage control. If the UE does not support network slice usage control, the UE may transmit first identification information indicating that the UE does not support network slice usage control.

[0262] If the network supports ATSSS, the UE may send the second identification information. In other words, if the network supports ATSSS, the UE may request to establish an MA PDU session.

[0263] The UE may send the requested network slice as a requested NSSAI. In other words, the UE may send the third identification information when requesting a network slice.

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

[0265] 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 NAS message.

[0266] Furthermore, the UE may select and decide whether to include one or more of the first to third 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.

[0267] In addition, the UE may also include identification information other than the first to third identification information in the PDU session establishment request message and send it.

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

[0269] Specifically, when the network receives the first identification information, the network may recognize that the UE supports network slice usage control. When the network receives the first identification information, the network may recognize that the UE does not support network slice usage control.

[0270] If the network receives the second identification information, it may recognize that the UE requests to establish an MA PDU session.

[0271] When the network receives the third identification information, it may recognize the network slice requested by the UE.

[0272] Next, the AMF selects an SMF as a transfer destination for at least part of the information, etc. (message, container, information) included in the 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 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0288] 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 an NAS message to the UE (S1216). Here, the N2 PDU session request message may include an NAS message and / or N2 SM information. The NAS message may also include a PDU session ID and / or an N1 SM container.

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

[0290] 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 an NAS message, and / or N2 SM information, and / or an N2 PDU session request message.

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

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

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

[0294] Next, the UE receives a PDU session establishment acceptance message and / or a NAS message from the SMF (S1212) (S1214) (S1216). The UE may also receive the PDU session establishment acceptance message and / or the NAS message including the eleventh identification information from the SMF. When the UE receives the PDU session establishment acceptance message and / or the 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 NAS message.

[0295] Specifically, when the UE receives the 11th identification information, the UE may start a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may stop and reset a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may associate the 10th identification information with the 11th identification information and store them. That is, when the UE receives the 11th identification information, the UE may store the 11th identification information for a certain on-demand S-NSSAI.

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

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

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

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

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

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

[0302] 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 an NAS message.

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

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

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

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

[0307] Next, the UE receives an 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 NAS message including the eleventh identification information from the SMF. When the UE receives the PDU session establishment rejection message and / or the 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 NAS message.

[0308] Specifically, when the UE receives the 11th identification information, the UE may start a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may stop and reset a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may associate the 10th identification information with the 11th identification information and store them. That is, when the UE receives the 11th identification information, the UE may store the 11th identification information for a certain on-demand S-NSSAI.

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

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

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

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

[0313] In addition, when the UE receives a PDU session accept message or a PDU session reject message, it may perform the following processing.

[0314] If the UE supports network slice usage control, it may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI.

[0315] Here, the slice non-registration inactivity timer may be stopped and reset when a PDU session associated with the on-demand S-NSSAI is successfully established on 3GPP access and / or non-3GPP access.

[0316] Here, the on-demand S-NSSAI may simply be the S-NSSAI.

[0317] [3.4. Overview of Network-Initiated Session Management Procedure] Next, we will explain the overview of the network-initiated session management procedure. Hereinafter, the network-initiated session management procedure will also be referred to as this procedure. This procedure is a procedure for session management that is initiated by the network for an established PDU session.

[0318] In addition, this procedure may be a network-requested PDU session modification procedure and / or a network-requested PDU session release procedure, or may involve the execution of a network-initiated session management procedure, including but not limited to these.

[0319] If this procedure is a network-initiated PDU session modification procedure, the session management request message in this procedure may be a PDU session modification command (PDU SESSION MODIFICATION COMMAND) message.If this procedure is a network-initiated PDU session release procedure, the session management request message in this procedure may be a PDU session release command (PDU SESSION RELEASE COMMAND) message.

[0320] Note that the network-initiated session management request message in this procedure may simply be referred to as a session management request message, and the network-initiated session management completion message in this procedure may simply be referred to as a session management completion message.

[0321] If this procedure is a network-initiated PDU session modification procedure, the session management completion message in this procedure may be a PDU session modification complete (PDU SESSION MODIFICATION COMPLETE) message.If this procedure is a network-initiated PDU session release procedure, the session management completion message in this procedure may be a PDU session release complete (PDU SESSION RELEASE COMPLETE) message.

[0322] [3.4.1. Example of Network-Initiated Session Management Procedure] Next, an example of a network-initiated session management procedure will be explained using Figure 9. Hereinafter, this procedure refers to the network-initiated session management procedure. Each step of this procedure will be explained.

[0323] Based on the completion of the registration procedure and / or PDU session establishment procedure, the UE and each device in the core network _B190 initiate a network-initiated session management procedure at any time.

[0324] Specifically, a device in core network _B190 may initiate this procedure based on receiving a PDU session change request message from the UE, or may initiate this procedure based on receiving a PDU session release request message from the UE.

[0325] Furthermore, a device within Core Network _B190 may initiate this procedure based on a request from a device in the DN or another device within the core network.

[0326] Here, the device in the core network _B 190 that initiates this procedure may be an SMF and / or an AMF, and the UE may send and receive messages in this procedure via the AMF and / or the access network _B. Furthermore, the device in the DN may be an AF (Application Function) in the DN.

[0327] An apparatus within core network _B190 sends a network-initiated session management request message to the UE (S1602) to start network-initiated session management. Further, the UE receives a network-initiated session management request message from an apparatus within core network _B190.

[0328] Here, the device in core network _B190 may include at least one of the 11th, 12th, and 18th identification information in the network-initiated session management request message, or may indicate a request from core network _B190 by including these identification information. Further, the device in core network _B190 may include a PDU session ID in the network-initiated session management request message, or may request a change to be made to the PDU session identified by the PDU session ID by including the PDU session ID.

[0329] Furthermore, an apparatus within core network _B190 may send a network-initiated session management request message to the UE together with at least one of identification information 11, 12, and 18. Furthermore, the UE may receive a network-initiated session management request message from an apparatus within core network _B190 together with at least one of identification information 11, 12, and 18.

[0330] The PDU session ID included in the PDU session change request message may be the PDU session ID of the established PDU session. Furthermore, if this procedure is performed based on a UE-initiated session management procedure, the PDU session ID included in the PDU session change request message may be the same as the PDU session ID included in the PDU session change request message or the PDU session release request message.

[0331] The behavior of the UE when receiving each identification information may be based on receiving a PDU session modification command message or a PDU session release command message, or may be performed after receiving a PDU session modification command message or a PDU session release command message.

[0332] Specifically, when the UE receives the 11th identification information, the UE may start a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may stop and reset a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may associate the 10th identification information with the 11th identification information and store them. That is, when the UE receives the 11th identification information, the UE may store the 11th identification information for a certain on-demand S-NSSAI.

[0333] When the UE receives the twelfth identification information, the UE may recognize the access type specified by the network. When the UE receives the twelfth identification information, the UE may perform processing for the access type indicated by the twelfth identification information. For example, when the UE receives the twelfth identification information indicating 3GPP access, the UE may establish, modify, or release a PDU session for the 3GPP access. When the UE receives the twelfth identification information that does not indicate 3GPP access or non-3GPP access, the UE may establish, modify, or release a PDU session for both 3GPP access and non-3GPP access.

[0334] When the UE receives the 18th identification information, the UE may recognize the RAT type designated by the network. When the UE receives the 18th identification information, the UE may perform processing for the RAT type indicated by the 18th identification information.

[0335] Next, the UE that has received the network-initiated session management request message sends a network-initiated session management complete message (S1604). Furthermore, the UE may perform a first process based on at least one of the 11th, 12th, and 18th identification information received from the core network_B190 (S1606) to complete this procedure. The UE may also perform the first process based on the completion of this procedure.

[0336] Here, the UE may include a PDU session ID in the network initiated session management complete message, which may be the same as the PDU session ID included in the network initiated session management request message.

[0337] An example of the first process will be described below.

[0338] The first process may be a process in which the UE recognizes something indicated by the core network _B 190, or a process in which the UE recognizes a request from the core network _B 190. Furthermore, the first process may be a process in which the UE stores the received identification information as context, or a process in which the UE forwards the received identification information to a higher layer and / or a lower layer.

[0339] Furthermore, the UE may execute the behavior when receiving each of the above-described pieces of identification information as the first process.

[0340] Furthermore, each device may perform a process based on the identification information transmitted and received in this procedure based on completion of this procedure. In other words, the UE may perform a first process based on completion of this procedure, or may complete this procedure after completing the first process.

[0341] Furthermore, each device completes the network-initiated session management procedure based on the completion of the above-mentioned processing and / or the sending and receiving of a network-initiated session management request message and / or a network-initiated session management completion message.

[0342] Furthermore, each device may modify an existing PDU session or release an existing PDU session based on the completion of the network-initiated session management procedure. In other words, each device may modify an existing PDU session based on the completion of the PDU session modification procedure. In other words, each device may release an existing PDU session based on the completion of the PDU session release procedure.

[0343] The UE may also start a slice non-registration inactivity timer when it receives a PDU session release command message.

[0344] Here, the slice non-registration inactivity timer may be started when the S-NSSAI is not used by a PDU session on the corresponding access type.

[0345] [3.5. Overview of UE-initiated session management procedure] Next, an overview of the UE-initiated session management procedure will be explained. Hereinafter, the UE-initiated session management procedure will also be referred to as this procedure. This procedure is a procedure for session management that is initiated by the UE for an established PDU session.

[0346] This procedure may be a UE-requested PDU session modification procedure and / or a UE-requested PDU session release procedure, or may be any UE-initiated session management procedure, including but not limited to these.

[0347] If this procedure is a UE-initiated PDU session modification procedure, the session management request message in this procedure may be a PDU session modification request (PDU SESSION MODIFICATION REQUEST) message.If this procedure is a UE-initiated PDU session release procedure, the session management request message in this procedure may be a PDU session release request (PDU SESSION RELEASE REQUEST) message.

[0348] If the procedure is a UE-initiated PDU session modification procedure, the session management reject message in the procedure may be a PDU session modification reject (PDU SESSION MODIFICATION REJECT) message.If the procedure is a UE-initiated PDU session release procedure, the session management reject message in the procedure may be a PDU session release reject (PDU SESSION RELEASE REJECT) message.

[0349] Note that the UE-initiated session management request message in this procedure may simply be referred to as a session management request message, and the UE-initiated session management reject message in this procedure may simply be referred to as a session management reject message.

[0350] [3.5.1. Example of UE-Initiated Session Management Procedure] Next, each step of this procedure will be described with reference to FIG.

[0351] Based on the completion of the registration procedure and / or the PDU session establishment procedure, the UE can initiate a UE-initiated session management procedure at any time. In other words, the UE may initiate a UE-initiated session management procedure for the established PDU session at any time. In other words, the UE may initiate a UE-initiated session management procedure using the same PDU session ID as the established PDU session at any time.

[0352] First, the UE initiates a UE-initiated session management procedure by sending a UE-initiated session management request message to the SMF (S1802). Here, the UE may include a PDU session ID in the UE-initiated session management request message, or may include the PDU session ID to request modification or release of the PDU session identified by the PDU session ID.

[0353] Here, the UE may include the second identification information in the session management request message, and may send the second identification information to the SMF together with the session management request message.

[0354] Specifically, if the network supports ATSSS, the UE may send the second identification information. In other words, if the network supports ATSSS, the UE may request to establish an MA PDU session.

[0355] Furthermore, the PDU session ID included in the session management request message may be the PDU session ID of an established PDU session.

[0356] Next, the SMF receives the session management request message sent by the UE. If the SMF accepts the UE request, it starts a network-initiated session management procedure (S1804). In this case, each device may complete this procedure upon completion of the network-initiated session management procedure.

[0357] Specifically, if the network receives the second identification information, it may recognize that the UE requests to establish an MA PDU session.

[0358] Conversely, if the SMF rejects the UE request, it sends a UE-initiated session management rejection message to the UE (S1806). Hereinafter, a case where the SMF rejects the UE request will be described.

[0359] Upon receiving the UE-initiated session management request message, the SMF sends a session management reject message to the UE (S1806).

[0360] Here, the SMF may include at least one of the 11th, 12th, and 18th identities in the session management reject message. Also, the SMF may send at least one of the 11th, 12th, and 18th identities to the UE together with the session management reject message.

[0361] Here, the PDU session ID included in the session management reject message may be the same as the PDU session ID included in the session management request message, i.e., the PDU session ID included in the session management reject message may be the same as the PDU session ID provided by the UE during this procedure.

[0362] The UE receives a session management reject message from the SMF. Further, each device may complete this procedure based on the sending and receiving of the session management reject message.

[0363] Specifically, when the UE receives the 11th identification information, the UE may start a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may stop and reset a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may associate the 10th identification information with the 11th identification information and store them. That is, when the UE receives the 11th identification information, the UE may store the 11th identification information for a certain on-demand S-NSSAI.

[0364] When the UE receives the twelfth identification information, the UE may recognize the access type specified by the network. When the UE receives the twelfth identification information, the UE may perform processing for the access type indicated by the twelfth identification information. For example, when the UE receives the twelfth identification information indicating 3GPP access, the UE may establish, modify, or release a PDU session for the 3GPP access. When the UE receives the twelfth identification information that does not indicate 3GPP access or non-3GPP access, the UE may establish, modify, or release a PDU session for both 3GPP access and non-3GPP access.

[0365] When the UE receives the 18th identification information, the UE may recognize the RAT type designated by the network. When the UE receives the 18th identification information, the UE may perform processing for the RAT type indicated by the 18th identification information.

[0366] Here, the UE may recognize that the UE request has been rejected based on the reception of the session management reject message. Furthermore, the UE may perform a second process based on the reception of the session management reject message (S1808). Note that the second process may be performed based on the completion of this procedure.

[0367] Here, the second process may be a process in which the UE recognizes the matter indicated by the SMF. Furthermore, the second process may be a process in which the UE stores the received identification information as context, or may be a process in which the UE forwards the received identification information to a higher layer and / or a lower layer. Furthermore, the second process may be a process in which the UE recognizes that the request for this procedure has been rejected.

[0368] Furthermore, a PDU session change procedure and / or a PDU session release procedure for the same PDU session may refer to a PDU session change procedure and / or a PDU session release procedure using the same PDU session ID.

[0369] [4. Embodiments] Next, each embodiment will be described.

[0370] [4.1. First embodiment] First, a first embodiment will be described. In this chapter, the first embodiment may be referred to as the present embodiment.

[0371] In this embodiment, a network initiated session management procedure and / or a non-registration procedure may be performed, or other procedures may be performed, and the procedures may be procedures for MA PDU sessions.

[0372] Furthermore, before this embodiment, a registration procedure, a UE configuration update procedure, a PDU session establishment procedure, a network-initiated session management procedure, and / or a UE-initiated session management procedure may be performed. Furthermore, this embodiment may be performed after these procedures have been performed multiple times. Furthermore, these procedures may be procedures for an MA PDU session.

[0373] This embodiment may also be performed multiple times.

[0374] In this embodiment, the first control message may be a PDU session release command message, or a DL NAS transport message, or a non-registration request message.

[0375] In this embodiment, the UE may retain a pre-configured eleventh identification information.

[0376] Each step of this embodiment will be described below.

[0377] First, the network may send a first control message to the UE. The network may also send the first control message to the UE, including one or more of the 11th, 12th, and 18th identifications. The network may also send the one or more of the 11th, 12th, and 18th identifications together with the first control message to the UE.

[0378] Here, the network may transmit one or more of the eleventh, twelfth, and eighteenth identification information to indicate to the UE what each identification information indicates.

[0379] Specifically, when notifying the UE of the slice non-registration inactivity timer, the network may send an eleventh identification information. When the network sends the eleventh identification information, the network may start, stop, and reset the slice non-registration inactivity timer using the eleventh identification information.

[0380] The network may send the 12th identification information to the UE when specifying the access type.

[0381] The network may send the 18th identification information when notifying the UE of the RAT type.

[0382] In addition, the network may select and decide whether to include one or more of the identification information 11, 12, and 18 in the first control message based on the state of the UE and / or information received from other NFs, etc.

[0383] The network may also determine whether to send the first control message and / or each identification information based on the state of the UE and / or information received from other NFs, etc.

[0384] The UE may then receive a first control message from the network. The UE may also receive from the network the first control message including one or more of the 11th, 12th, and 18th identities. The UE may also receive from the network the one or more of the 11th, 12th, and 18th identities together with the first control message.

[0385] Specifically, when the UE receives the 11th identification information, the UE may start a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may stop and reset a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may associate the 10th identification information with the 11th identification information and store them. That is, when the UE receives the 11th identification information, the UE may store the 11th identification information for a certain on-demand S-NSSAI.

[0386] When the UE receives the twelfth identification information, the UE may recognize the access type specified by the network. When the UE receives the twelfth identification information, the UE may perform processing for the access type indicated by the twelfth identification information. For example, when the UE receives the twelfth identification information indicating 3GPP access, the UE may establish, modify, or release a PDU session for the 3GPP access. When the UE receives the twelfth identification information that does not indicate 3GPP access or non-3GPP access, the UE may establish, modify, or release a PDU session for both 3GPP access and non-3GPP access.

[0387] When the UE receives the 18th identification information, the UE may recognize the RAT type designated by the network. When the UE receives the 18th identification information, the UE may perform processing for the RAT type indicated by the 18th identification information.

[0388] Furthermore, the UE may store the received identification information or recognize the network's decision based on receiving the first control message, and the UE may recognize the content of the received identification information based on receiving the first control message.

[0389] For an MA PDU session, the behavior of the UE when it receives the first control message is as follows.

[0390] First, the following describes when the slice non-registration inactivity timer is started and stopped when the S-NSSAI is used by a PDU session on the corresponding access type.

[0391] If the first control message includes the 12th identification and the MA PDU session has user plane resources established in both 3GPP access and non-3GPP access, the UE may not start the slice non-registration inactivity timer.

[0392] In other words, if the first control message includes the 12th identity and the MA PDU session has user plane resources established in both 3GPP and non-3GPP accesses, the UE may not start the slice non-registration inactivity timer for the on-demand S-NSSAI in the access indicated by the 12th identity.

[0393] In other words, when the UE is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established user plane resources via 3GPP access and user plane resources via non-3GPP access, and the access indicated by the twelfth identity indicates only 3GPP access or only non-3GPP access, the UE may not start the slice deregistration inactivity timer applicable to the MA PDU session. Also, when the UE is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established user plane resources via 3GPP access and user plane resources via non-3GPP access, and the access indicated by the twelfth identity indicates 3GPP access and non-3GPP access, the UE may start the slice deregistration inactivity timer applicable to the MA PDU session.

[0394] If the first control message includes the 12th identity and the MA PDU session has user plane resources established only for the access indicated by the 12th identity, the UE may start a slice non-registration inactivity timer.

[0395] In other words, if the first control message includes the 12th identity and the MA PDU session has user plane resources established only on the access indicated by the 12th identity, the UE may start a slice non-registration inactivity timer for the on-demand S-NSSAI on the access indicated by the 12th identity.

[0396] In other words, if the UE is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established only user plane resources via 3GPP access or only user plane resources via non-3GPP access, and the access indicated by the 12th identification information indicates the access (3GPP access or non-3GPP access) corresponding to the established user plane resources, the UE may start the slice non-registration inactivity timer applied to the MA PDU session.

[0397] Furthermore, if the UE is registered to 3GPP access or non-3GPP access in the same PLMN and / or a different PLMN and has established only user plane resources via the established access (3GPP access or non-3GPP access), and the access indicated by the 12th identification information indicates the access (3GPP access or non-3GPP access) corresponding to the established user plane resources, the UE may start a slice non-registration inactivity timer applied to the MA PDU session.

[0398] If the first control message does not include the twelfth identification information, the UE may start a slice non-registration inactivity timer.

[0399] In other words, if the first control message does not include the 12th identity, the UE may start a slice non-registration inactivity timer for on-demand S-NSSAI in both 3GPP access and non-3GPP access.

[0400] In other words, if the UE is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established only user plane resources via 3GPP access or only user plane resources via non-3GPP access, when the UE receives a first control message that does not include the 12th identification, the UE may start a slice non-registration inactivity timer applicable to the MA PDU session.

[0401] Furthermore, if the UE is registered with 3GPP access or non-3GPP access in the same PLMN and / or a different PLMN and has established only user plane resources via the established access (3GPP access or non-3GPP access), when the UE receives a first control message that does not include the 12th identification, the UE may start a slice non-registration inactivity timer that applies to the MA PDU session.

[0402] Here, the slice non-registration inactivity timer may be started when the S-NSSAI is not used by a PDU session on the corresponding access type.

[0403] Furthermore, the slice inactivity timer may be started when the S-NSSAI is not used by a PDU session on the corresponding access type, except when the PDU session is an MA PDU session. In other words, the slice inactivity timer may be started when the S-NSSAI is not used by a PDU session on both 3GPP and non-3GPP accesses when the PDU session is an MA PDU session. In yet another way, the slice inactivity timer may be started when the S-NSSAI is not used by user plane resources of an MA PDU session on both 3GPP and non-3GPP accesses when the PDU session is an MA PDU session.

[0404] The above PLMN may be read as SNPN. That is, the same PLMN may be read as the same SNPN. Also, different PLMNs may be read as different SNPNs.

[0405] As described above, the slice non-registration inactivity timer may be a timer applied to the MA PDU session. In other words, the slice non-registration inactivity timer may be a timer managed in the MA PDU session (a timer managed for the entire MA PDU session), and may not be managed for each user plane resource and / or each access in the MA PDU session.

[0406] Next, the following describes when the slice non-registration inactivity timer is started and stopped when the S-NSSAI is used by user plane resources of a PDU session on the corresponding access type.

[0407] If the first control message includes the 12th identification and the MA PDU session has user plane resources established in both 3GPP access and non-3GPP access, the UE may start a slice non-registration inactivity timer.

[0408] In other words, if the first control message includes the 12th identity and the MA PDU session has user plane resources established in both 3GPP and non-3GPP accesses, the UE may start a slice non-registration inactivity timer for the on-demand S-NSSAI in the access indicated by the 12th identity.

[0409] In other words, if the first control message includes the 12th identity and the MA PDU session has user plane resources established in both 3GPP and non-3GPP accesses, the UE may start a slice non-registration inactivity timer for the on-demand S-NSSAI in the user plane resources of the MA PDU session in the access indicated by the 12th identity.

[0410] In other words, when the UE has registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established user plane resources via 3GPP access and user plane resources via non-3GPP access, and when the access indicated by the twelfth identity indicates only 3GPP access or only non-3GPP access, the UE may start a slice inactivity timer applicable to the access indicated by the twelfth identity, which is applicable to the user plane resources in the MA PDU session. Also, when the UE has registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established user plane resources via 3GPP access and user plane resources via non-3GPP access, and when the access indicated by the twelfth identity indicates 3GPP access and non-3GPP access, the UE may start a slice inactivity timer applicable to the access indicated by the twelfth identity, which is applicable to the user plane resources in the MA PDU session.

[0411] If the first control message includes the 12th identity and the MA PDU session has user plane resources established only for the access indicated by the 12th identity, the UE may start a slice non-registration inactivity timer.

[0412] In other words, if the first control message includes the 12th identity and the MA PDU session has user plane resources established only on the access indicated by the 12th identity, the UE may start a slice non-registration inactivity timer for the on-demand S-NSSAI on the access indicated by the 12th identity.

[0413] In other words, if the first control message includes a 12th identity and the MA PDU session has user plane resources established only on the access indicated by the 12th identity, the UE may start a slice non-registration inactivity timer for the on-demand S-NSSAI on the user plane resources of the MA PDU session on the access indicated by the 12th identity.

[0414] In other words, when the UE is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established only user plane resources via 3GPP access or only user plane resources via non-3GPP access, and the access indicated by the 12th identification information indicates the access (3GPP access or non-3GPP access) corresponding to the established user plane resources, the UE may start a slice deregistration inactivity timer that applies to the access indicated by the 12th identification information and that applies to the user plane resources in the MA PDU session.

[0415] In addition, if the UE is registered to 3GPP access or non-3GPP access in the same PLMN and / or a different PLMN and has established only user plane resources via the established access (3GPP access or non-3GPP access), and the access indicated by the 12th identification information indicates the access (3GPP access or non-3GPP access) corresponding to the established user plane resources, the UE may start a slice deregistration inactivity timer that applies to the access indicated by the 12th identification information and that applies to the user plane resources in the MA PDU session.

[0416] If the first control message does not include the twelfth identification information, the UE may start a slice non-registration inactivity timer.

[0417] In other words, if the first control message does not include the 12th identity, the UE may start a slice non-registration inactivity timer for on-demand S-NSSAI in both 3GPP access and non-3GPP access.

[0418] In other words, when the UE is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs and has established user plane resources via 3GPP access or only user plane resources via non-3GPP access, upon receiving the first control message not including the 12th identification, the UE may start a slice inactivity timer applicable to the user plane resources in the MA PDU session. That is, the UE may start a slice inactivity timer applicable to 3GPP access that is applicable to the user plane resources in the MA PDU session, and may also start a slice inactivity timer applicable to non-3GPP access that is applicable to the user plane resources in the MA PDU session.

[0419] Furthermore, when the UE is registered with 3GPP access or non-3GPP access in the same PLMN and / or a different PLMN and has established only user plane resources via the established access (3GPP access or non-3GPP access), and when the UE receives a first control message that does not include the 12th identification, the UE may start a slice inactivity timer that is applied to the user plane resources in the MA PDU session. That is, the UE may start a slice inactivity timer that is applied to the 3GPP access and is applied to the user plane resources in the MA PDU session, and may also start a slice inactivity timer that is applied to the non-3GPP access and is applied to the user plane resources in the MA PDU session.

[0420] Here, the slice non-registration inactivity timer may be started when the S-NSSAI is not used by a PDU session on the corresponding access type.

[0421] Additionally, the slice non-registration inactivity timer may be started when the S-NSSAI is not used by user plane resources of an MA PDU session on the corresponding access type, or the slice non-registration inactivity timer may be started when the S-NSSAI is not used by user plane resources of a PDU session on the corresponding access type.

[0422] In other words, if the PDU session is an MA PDU session, the slice non-registration inactivity timer may be started if the S-NSSAI is not used by the user plane resources of the MA PDU session on the corresponding access type.

[0423] The above PLMN may be read as SNPN. That is, the same PLMN may be read as the same SNPN. Also, different PLMNs may be read as different SNPNs.

[0424] As described above, the slice non-registration inactivity timer may be a timer applied to user plane resources in an MA PDU session. In other words, the slice non-registration inactivity timer may be a timer managed for each user plane resource and / or each access in an MA PDU session, but not managed in the MA PDU session (a timer not managed for the entire MA PDU session).

[0425] The UE may perform the behavior after receiving the first control message, or after receiving one or more of the 11th, 12th, and 18th identification information.

[0426] Furthermore, when the UE receives the first control message, the UE may perform the behavior that occurs when it receives each piece of identification information included in the first control message.

[0427] [4.2. Second embodiment] Next, a second embodiment will be described. In this chapter, the second embodiment may be referred to as the present embodiment.

[0428] In this embodiment, the PDU session establishment procedure may be performed, or another procedure may be performed. Also, this procedure may be a procedure for an MA PDU session.

[0429] Furthermore, before this embodiment, a registration procedure, a UE configuration update procedure, a PDU session establishment procedure, a network-initiated session management procedure, and / or a UE-initiated session management procedure may be performed. Furthermore, this embodiment may be performed after these procedures are performed multiple times. Furthermore, these procedures may be procedures for an MA PDU session.

[0430] This embodiment may also be performed multiple times.

[0431] In this embodiment, the first control message may be a PDU session establishment request message or a UL NAS transport message.

[0432] Also, in this embodiment, the second control message may be a PDU session establishment acceptance message, or a PDU session establishment rejection message, or a DL NAS transport message.

[0433] In this embodiment, the UE may retain a pre-configured eleventh identification information.

[0434] Each step of this embodiment will be described below.

[0435] First, the UE may send a first control message to the network, and the UE may also send the first control message including second identification information to the network, and the UE may also send the first control message together with the second identification information to the network.

[0436] Specifically, if the network supports ATSSS, the UE may send the second identification information. In other words, if the network supports ATSSS, the UE may request to establish an MA PDU session.

[0437] Here, the UE may include the second identification information in the first control message and transmit the message, thereby indicating to the network the content indicated by the identification information included in the first control message.

[0438] The UE may select and determine whether to include the second identification information in the first control message based on the state of the UE and / or each piece of received identification information, etc.

[0439] The network may then receive a first control message from the UE, and may receive the first control message from the UE including the second identification information, and may receive the first control message with the second identification information from the UE.

[0440] Further, based on receiving the first control message, the network may store the received identification information, may recognize the content of the received identification information, or may recognize the decision of the UE.

[0441] Specifically, if the network receives the second identification information, it may recognize that the UE requests to establish an MA PDU session.

[0442] The network behavior may be implemented after receiving the first control message, or after receiving the second identification information.

[0443] Furthermore, when the network receives the first control message, the network may perform a behavior upon receiving each piece of identification information included in the first control message.

[0444] The network may also forward each received identification information to other NFs.

[0445] Next, the network sends a second control message to the UE, where the network may include one or more of the 11th, 12th, and 18th identities in the second control message. The network may also send the second control message together with one or more of the 11th, 12th, and 18th identities.

[0446] Here, the network may indicate to the UE the contents indicated by the identification information included in the second control message by including one or more of the identification information 11, 12, and 18 in the second control message and transmitting the message.

[0447] Specifically, when notifying the UE of the slice non-registration inactivity timer, the network may send an eleventh identification information. When the network sends the eleventh identification information, the network may start, stop, and reset the slice non-registration inactivity timer using the eleventh identification information.

[0448] The network may send the 12th identification information to the UE when specifying the access type.

[0449] The network may send the 18th identification information when notifying the UE of the RAT type.

[0450] In addition, the network may select and decide whether to include one or more of the identification information 11, 12, and 18 in the second control message based on the state of the UE and / or information received from other NFs, etc.

[0451] The network may also determine whether to send the second control message and / or each identification information based on the state of the UE and / or information received from other NFs, etc.

[0452] The UE then receives a second control message from the network. The UE may also receive from the network the second control message including one or more of the 11th, 12th, and 18th identities. The UE may also receive from the network the second control message together with one or more of the 11th, 12th, and 18th identities.

[0453] Specifically, when the UE receives the 11th identification information, the UE may start a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may stop and reset a slice non-registration inactivity timer using the 11th identification information. When the UE receives the 11th identification information, the UE may associate the 10th identification information with the 11th identification information and store them. That is, when the UE receives the 11th identification information, the UE may store the 11th identification information for a certain on-demand S-NSSAI.

[0454] When the UE receives the twelfth identification information, the UE may recognize the access type specified by the network. When the UE receives the twelfth identification information, the UE may perform processing for the access type indicated by the twelfth identification information. For example, when the UE receives the twelfth identification information indicating 3GPP access, the UE may establish, modify, or release a PDU session for the 3GPP access. When the UE receives the twelfth identification information that does not indicate 3GPP access or non-3GPP access, the UE may establish, modify, or release a PDU session for both 3GPP access and non-3GPP access.

[0455] When the UE receives the 18th identification information, the UE may recognize the RAT type designated by the network. When the UE receives the 18th identification information, the UE may perform processing for the RAT type indicated by the 18th identification information.

[0456] Further, based on receiving the second control message, the UE may store the received identification information, may recognize the content of the received identification information, or may recognize the network's decision.

[0457] The UE may perform the above-mentioned behavior after receiving the second control message, or after receiving one or more of the 11th, 12th, and 18th identification information.

[0458] Furthermore, when the UE receives the second control message, the UE may perform the behavior that occurs when it receives each piece of identification information included in the second control message.

[0459] In addition, when the UE receives the second control message, it may perform the following processing.

[0460] First, the following describes when the slice non-registration inactivity timer is started and stopped when the S-NSSAI is used by a PDU session on the corresponding access type.

[0461] If the UE supports network slice usage control, it may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI.

[0462] If the UE supports network slice usage control, and if the PDU session is an MA PDU session and the MA PDU session is successfully established over 3GPP access and / or non-3GPP access, the UE may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI.

[0463] In other words, if the UE supports network slice usage control, and is further registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs, and has successfully established user plane resources via 3GPP access and user plane resources via non-3GPP access, the UE may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI. Also, if the UE supports network slice usage control, and is further registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs, and has successfully established only user plane resources via 3GPP access or only user plane resources via non-3GPP access, the UE may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI.

[0464] Furthermore, if the UE supports network slice usage control, and is registered with 3GPP access and / or non-3GPP access in the same PLMN and / or a different PLMN, and if the MA PDU session is successfully established, the UE may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI.

[0465] Here, the slice non-registration inactivity timer may be stopped and reset if an MA PDU session associated with the on-demand S-NSSAI is successfully established over 3GPP access and / or non-3GPP access.

[0466] As described above, the slice non-registration inactivity timer may be a timer applied to the MA PDU session. In other words, the slice non-registration inactivity timer may be a timer managed in the MA PDU session, but not managed for each user plane resource and / or each access in the MA PDU session.

[0467] Next, the following describes when the slice non-registration inactivity timer is started and stopped when the S-NSSAI is used by user plane resources of a PDU session on the corresponding access type.

[0468] If the UE supports network slice usage control, it may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI.

[0469] If the UE supports network slice usage control, and if the PDU session is an MA PDU session and the user plane resources of the MA PDU session are successfully established over 3GPP access or non-3GPP access, the UE may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI.

[0470] In other words, if the UE supports network slice usage control, and is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs, and has successfully established only user plane resources via 3GPP access or only user plane resources via non-3GPP access, the UE may stop and reset the slice non-registration inactivity timer for the on-demand S-NSSAI, i.e., the slice non-registration inactivity timer applicable to 3GPP access or non-3GPP access, but applicable to user plane resources in the MA PDU session.

[0471] Furthermore, if the UE supports network slice usage control, and is registered with 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs, and has successfully established user plane resources via 3GPP access and user plane resources via non-3GPP access, the UE may stop and reset the slice inactivity timer for the on-demand S-NSSAI, i.e., the UE may stop and reset the slice inactivity timer applicable to 3GPP access and applicable to user plane resources in the MA PDU session, and may stop and reset the slice inactivity timer applicable to non-3GPP access and applicable to user plane resources in the MA PDU session.

[0472] Here, the slice non-registration inactivity timer may be stopped and reset when the user plane resources of the MA PDU session associated with the on-demand S-NSSAI are successfully established over 3GPP access or non-3GPP access.

[0473] As described above, the slice non-registration inactivity timer may be a timer applied to user plane resources in an MA PDU session. In other words, the slice non-registration inactivity timer may be a timer managed for each user plane resource and / or each access in an MA PDU session, but may not be managed in the MA PDU session.

[0474] Here, the on-demand S-NSSAI may simply be the S-NSSAI.

[0475] [5. 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 make a computer 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.

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

[0477] 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, and integrated circuit technologies that replace current integrated circuits emerge, the present embodiments may also use new integrated circuits based on those technologies.

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

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

[0480] 1 Mobile communication system 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access network_A (E-UTRAN) 90 Core network_A 120 Access network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core network_B 235 UPF_A 239 UPF_C

Claims

1. A User Equipment (UE) having a control unit, wherein the control unit supports network slice usage control, and when a Multi-Access (MA) PDU session for an on-demand S-NSSAI is successfully established, the UE stops and resets a slice non-registration inactivity timer for the on-demand S-NSSAI for both 3GPP access and non-3GPP access.

2. The UE of claim 1, characterized in that the slice non-registration inactivity timer is a timer that causes the UE to deregister from its network slice after a PDU session associated with the on-demand S-NSSAI is released.

3. An Access and Mobility Management Function (AMF) having a control unit, wherein the control unit, when an MA PDU session related to an on-demand S-NSSAI is successfully established for both 3GPP access and non-3GPP access, stops and resets a slice non-registration inactivity timer for the on-demand S-NSSAI for the 3GPP access, and stops and resets a slice non-registration inactivity timer for the on-demand S-NSSAI for the non-3GPP access.

Images