UE(User Equipment)

Abstract

This provides a UE (User Interface) that clarifies the start, stop, and reset conditions for the slice unregistered inactive timer in MA PDU (Multi-Access PDU) sessions. [Solution] In a mobile communication system, a slice unregistered inactive timer, which is set for the UE to limit network slices, is started when S-NSSAI (Single Network Slice Selection Assistance Information) is not used by a PDU session on the corresponding access type, except when the PDU (Protocol Data Unit) session is an MA PDU session, and is stopped and reset when an MA PDU session associated with on-demand S-NSSAI is successfully established on 3GPP access and / or non-3GPP access.

Description

Technical Field

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

Background Art

[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), which is a fifth-generation (5G) mobile communication system, is under consideration, and discussions are being held to support new procedures and new functions (see Non-Patent Documents 1 and 2). Currently, as one of the considerations towards the specification of Release 18, discussions regarding the expansion of the network slice (also referred to as NS) function are being held (see Non-Patent Document 3).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

[0004] Currently, 5GS is considering using a timer to manage NSs (Network Servers) and remove NSs that have not been used for a certain period of time from the UE (User Environment). However, there are still unclear aspects regarding how to manage this timer, such as the timing for starting the timer in the case of MA PDU sessions.

[0005] One aspect of the present invention has been made in view of the above circumstances. In this invention, the start, stop, and reset conditions for the slice unregistered inactive timer in the MA PDU session are clarified. [Means for solving the problem]

[0006] One aspect of the present invention is a User Equipment (UE) comprising a transmitting / receiving unit and a control unit, wherein in a PDU session establishment procedure for establishing a PDU session, the transmitting / receiving unit receives a PDU session establishment acceptance 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 the slice unregistered deactivation timer for on-demand S-NSSAI, and the slice unregistered deactivation timer is stopped and reset when the MA PDU session associated with the on-demand S-NSSAI is successfully established over 3GPP access and / or non-3GPP access.

[0007] One aspect of the present invention is a User Equipment (UE) comprising a transmitting / receiving unit and a control unit, wherein in a PDU session establishment procedure for establishing a PDU session, the transmitting / receiving unit receives a PDU session establishment acceptance message, and if the UE supports network slice usage control, and further 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 control unit stops and resets the slice unregistered deactivation timer for on-demand S-NSSAI, and the slice unregistered deactivation timer is 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. [Effects of the Invention]

[0008] According to one aspect of the present invention, the start, stop, and reset conditions for the slice unregistered inactive timer in an MA PDU session can be clearly defined. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating the general outline of the mobile communication system (EPS / 5GS). [Figure 2] This diagram illustrates the detailed configuration of the mobile communication system (EPS / 5GS). [Figure 3] This is a diagram illustrating the equipment configuration of the UE. [Figure 4] This diagram illustrates the configuration of the access network device (gNB) in 5GS. [Figure 5] This diagram illustrates the configuration of the core network equipment (AMF / SMF / UPF) in 5GS. [Figure 6] This is a diagram explaining the registration procedure. [Figure 7] This is a diagram illustrating the procedure for updating UE settings. [Figure 8] This diagram illustrates the procedure for establishing a PDU session. [Figure 9] This diagram illustrates network-driven session management procedures. [Figure 10] This diagram illustrates the UE-led session management procedure. [Modes for carrying out the invention]

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

[0011] [1. System Overview] First, Figure 1 is a diagram illustrating the general structure of the mobile communication system 1 used in each embodiment, and Figure 2 is a diagram illustrating the detailed configuration of the mobile communication system 1.

[0012] FIG. 1 depicts 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 described by omitting symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0014] Also, FIG. 2 depicts devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc., and interfaces connecting these devices and functions to each other.

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

[0016] Note that the EPS (Evolved Packet System), which is a 4G system, is composed of access network_A and core network_A, but may further include UE and / or PDN. Also, the 5GS (5G System), which is a 5G system, is composed of UE, access network_B, and core network_B, but may further include DN.

[0017] A UE is a device capable of connecting to network services via 3GPP access (also known as a 3GPP access network or 3GPP AN) and / or non-3GPP access (also known as a non-3GPP access network or non-3GPP AN). A UE may be a wireless communication terminal device such as a mobile phone or smartphone, and may be a terminal device capable of connecting to both EPS and 5GS. A UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC).

[0018] Furthermore, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. E-UTRAN has one or more eNBs (evolved Node B)45. Note that in the following, eNB45 may be written simply as eNB. If there are multiple eNBs, each eNB is connected to the others, for example, by an X2 interface. Furthermore, the wireless LAN access network has one or more access points.

[0019] Furthermore, access network_B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access networks. One or more gNBs (NR NodeBs)122 are located in the NG-RAN. Note that, below, gNB122 may be written with the symbol omitted, such as gNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including the N2 interface or N3 interface). In other words, a 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. Also, if there are multiple gNBs, each gNB is connected to the others, for example, by an Xn interface.

[0020] Furthermore, a non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, an 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 Wi-Fi network. On the other hand, a trusted non-3GPP access network may be an access network defined by 3GPP and may be equipped with a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function).

[0021] Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Similarly, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Additionally, 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 the devices included in access network_A and / or the devices included in access network_B may be referred to as access networks or access network devices.

[0023] Furthermore, Core Network A corresponds to EPC (Evolved Packet Core). EPC is configured with, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc.

[0024] Furthermore, Core Network B corresponds to 5GCN (5G Core Network). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN may also be expressed as 5GC.

[0025] Furthermore, in the following, Core Network A and / or Core Network B, the devices included in Core Network A and / or Core Network B may be referred to as the Core Network, 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; 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] Furthermore, although Figure 1 shows a case where the PDN and DN are the same, they may be different. The PDN may be a Data Network (DN) that provides communication services to the UE. The DN may be configured as a packet data service network, or it may be configured for each service. In addition, the PDN may include connected communication terminals. Therefore, connecting to the PDN may also mean connecting to communication terminals or server devices located in the PDN. Furthermore, sending and receiving user data with the PDN may also mean sending and receiving user data with communication terminals or server devices located in the PDN. Note that the PDN may be referred to as DN, and the DN may be referred to as PDN.

[0028] Furthermore, in the following, access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein may be referred to as a network or network device. In other words, when a network and / or network device sends and receives messages and / or performs procedures, it means that access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein send and receive messages and / or perform procedures.

[0029] Furthermore, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data with the PDN or DN. When sending and receiving user data, non-IP communication may be used in addition to IP (Internet Protocol) communication.

[0030] Here, IP communication refers to data communication using IP, where data is sent and received via IP packets. An IP packet consists of an IP header and a payload. The payload may include data sent 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, where data is sent and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by sending and receiving application data without an IP header, or it may be user data sent and received by the UE with other headers such as a MAC header or an Ethernet® frame header attached.

[0031] Furthermore, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may include devices not shown in Figure 2. For example, core network_A and / or core network_B may include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0032] Here, AUSF is a core network device equipped with authentication functions for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP access and / or non-3GPP access from the UE and executes the authentication procedure.

[0033] Furthermore, the AAA server is a device equipped with authentication, authorization, and billing functions, which connects directly or indirectly to the AUSF via other network devices. The AAA server may be a network device within the core network. However, the AAA server may not be included in core network_A and / or core network_B, but may be included in PLMN. In other words, the AAA server may be a core network device or a device located outside the core network. For example, the AAA server may be a server device within PLMN managed by a third party.

[0034] Note that in Figure 2, for the sake of simplification, only one of each device / function is shown; however, multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with multiple devices / 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] UPF_A235 connects to DN, SMF, other UPFs, and access networks. UPF_A235 may also perform roles such as anchoring to intra-RAT mobility or inter-RAT mobility, packet routing and forwarding, UL CL (Uplink Classifier) ​​functionality supporting routing of multiple traffic flows to a single DN, branching point functionality supporting multi-homed PDU sessions, QoS processing for user planes, verification of uplink traffic, buffering of downlink packets, and triggering of downlink data notifications. Furthermore, UPF_A235 may also act as a relay device for transferring user data, serving as a gateway between the DN and the core network_B190. In addition, UPF_A235 may also act as a gateway for IP communication and / or non-IP communication. Moreover, UPF_A235 may have the functionality to forward IP communication and the functionality to convert between non-IP and IP communication. Furthermore, the multiple gateways that are deployed may also be gateways that connect the core network_B190 to a single DN. Note that UPF_A235 may have connectivity to other NFs and may connect to each device via other NFs.

[0036] Furthermore, a different UPF, UPF_C239 (also referred to as branching point or uplink classifier), may exist as a device or NF between UPF_A235 and the access network. If UPF_C239 exists, the PDU session between the UE and DN will be established via the access network, UPF_C239, and UPF_A235.

[0037] Furthermore, UPF130 may be the same device as UPF_A235. Note that UPF130 and UPF_A235 may be written with the symbols omitted, like 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 a diagram. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0039] Furthermore, each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) within each device / function described below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only the information originally set at the time of shipment, but also various information transmitted and received with devices / functions other than its own device / function (for example, UE, and / or access network devices, and / or core network devices, and / or PDN, and / or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc. contained in control messages transmitted and received within the various communication procedures described later. Furthermore, each memory unit may store this information for each UE. In addition, when interworking between 5GS and EPS occurs, each memory unit can store control messages and user data transmitted and received with devices / functions contained within 5GS and / or EPS. In this case, not only data transmitted and received via the N26 interface can be stored, but also data transmitted and received without using the N26 interface.

[0040] [2.1. UE Equipment Configuration] First, an example of the UE (User Equipment) configuration will be explained using Figure 3. The UE consists of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, transceiver_A320, and storage unit_A340 are connected via a bus. The transceiver_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 processes in the UE by reading and executing various programs stored in the memory unit_A340 as needed.

[0042] The transceiver unit A320 is a functional unit for wireless communication with base station equipment (eNB or gNB) within the access network via an antenna. In other words, the UE can use the transceiver unit A320 to send and receive user data and / or control information between the access network equipment and / or core network equipment and / or PDN and / or DN.

[0043] Referring to Figure 2, the UE can communicate with the base station equipment (eNB) in E-UTRAN via the LTE-Uu interface using the transceiver unit A320. The UE can also communicate with the base station equipment (gNB) in 5G AN using the transceiver unit A320. Furthermore, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit A320. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN.

[0044] 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 System Configuration] Next, an example of the gNB's device configuration will be explained using Figure 4. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transceiver unit_B530, and storage 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 implements various processes in the gNB by reading and executing various programs stored in the memory unit B540 as needed.

[0047] The network connection unit B520 is a functional unit that allows the gNB to communicate with the AMF and / or UPF. In other words, the gNB can use the network connection unit B520 to send and receive user data and / or control information with the AMF and / or UPF.

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

[0049] Referring to Figure 2, the gNB within the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface by using the network connection unit B520. Furthermore, the gNB can communicate with the UE by using the transceiver unit B530.

[0050] 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 Equipment Configuration] Next, an example of the AMF's device configuration will be explained using Figure 5. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage 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 implements various processes 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 that allows the AMF to connect to base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. In other words, the AMF can use the network connection unit_B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN.

[0054] Referring to Figure 2, the AMF within 5GCN can communicate with the gNB via the N2 interface, the UDM via the N8 interface, the SMF via the N11 interface, and the PCF via the N15 interface, using the network connection unit _A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit _A620. However, since the N1 interface is logical, actual communication between the UE and the AMF takes place via the 5G AN. Additionally, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface using the network connection unit _A620.

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

[0056] Furthermore, 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) function, connection management (CM) function, reachability management function, mobility management function for UEs, etc., forwarding SM (Session Management) messages between the UE and the SMF, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA), security context management (SCM), support for the N2 interface to the N3IWF (Non-3GPP Interworking Function), support for sending and receiving NAS signals with the UE via the N3IWF, and authentication of UEs connected via the N3IWF.

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

[0058] In other words, 5GMM-REGISTERED means that each device may have established a 5GMM context or a PDU session context. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, and may respond to paging. In addition, 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 occur even if each device has not established a 5GMM context, or if the location information of UE_A10 is not known to the network, or if the network is unreachable to UE_A10. If each device is in a 5GMM-DEREGISTERED state, UE_A10 may initiate the registration procedure, or establish a 5GMM context by executing the registration procedure.

[0060] Furthermore, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. There are two CM states: disconnected state (CM-IDLE state) and 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. Also, in the CM-IDLE state, the UE does not have an N2 connection or an N3 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. Also, in the CM-CONNECTED state, the UE may have an N2 connection and / or an N3 connection.

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

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

[0063] Furthermore, one or more AMFs may be placed within core network_B. Also, an AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Additionally, an AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

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

[0065] [2.4. SMF Equipment Configuration] Next, an example of the SMF device configuration will be explained using Figure 5. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage 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 implements various processes 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 use the network connection unit B720 to send and receive user data and / or control information with the AMF, and / or UPF, and / or PCF, and / or UDM.

[0068] Referring to Figure 2, the SMF within 5GCN can communicate with the AMF via the N11 interface, the UPF via the N4 interface, the PCF via the N7 interface, and the UDM via the N10 interface by using the network connection unit A620.

[0069] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the SMF.

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

[0071] [2.5. UPF Equipment Configuration] Next, an example of the UPF's configuration will be explained using Figure 5. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage 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 implements various processes in the UPF by reading and executing various programs stored in the memory unit B740 as needed.

[0073] The network connection unit B720 is a functional unit that allows the UPF to connect with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit B720 to send and receive user data and / or control information with base station equipment (gNB), and / or SMF, and / or DN within the 5G AN.

[0074] Referring to Figure 2, the UPF within 5GCN can communicate with the gNB via the N3 interface, the SMF via the N4 interface, the DN via the N6 interface, and other UPFs via the N9 interface by using the network connection unit A620.

[0075] Memory unit B740 is a functional unit for storing programs, user data, control information, etc., necessary for each operation of the UPF.

[0076] UPF has functions such as acting as an anchor point for intra-RAT mobility or inter-RAT mobility, acting as an external PDU session point for interconnecting to DNs (i.e., acting as a gateway between DNs and core network B to forward user data), routing and forwarding packets, an UL CL (Uplink Classifier) ​​function that supports routing multiple traffic flows to a single 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 notification.

[0077] Furthermore, the UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have the function of forwarding IP communication, and may also have the function of converting non-IP communication to IP communication. In addition, multiple gateways may be gateways connecting the core network B to a single DN. The UPF may also have connectivity to other NFs, and may connect to each device via other NFs.

[0078] Furthermore, the user plane refers to user data transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. In addition, 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 U-Plane.

[0079] Furthermore, the control plane refers to the control messages transmitted and received for communication control of the UE, etc. The control plane may be transmitted and received using the NAS (Non-Access-Stratum) signaling connection between the UE and the MME. In addition, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. In addition, 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 also be a communication channel for sending and receiving user data, and may consist of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may also be a communication channel for sending and receiving control messages, and may consist of multiple bearers.

[0081] [2.6. Description of other devices and / or functions] Next, we will describe the other devices and / or functions.

[0082] Next, "network" refers to at least a portion of Access Network B, Core Network B, and DN. Furthermore, one or more devices included in at least a portion of Access Network B, Core Network B, and DN may be referred to as a network or network device.

[0083] In other words, when a network sends, receives, and / or processes messages, it may mean that devices within the network (network devices and / or control devices) send, receive, and / or process messages. Conversely, when devices within a network send, receive, and / or process messages, it may mean that the network sends, receives, and / or processes messages.

[0084] Furthermore, the term "network" may refer to either a PLMN (Public Land Mobile Network) or an NPN (Non-Public Network). The term "network" may also be abbreviated as "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 a telecommunications operator, and the operator can be identified by the PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscription Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may maintain an Equivalent PLMN list in the USIM to identify one or more EPLMNs (Equivalent PLMNs). A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN that has been successfully registered by the UE may be a Registered PLMN (RPLMN).

[0086] Next, PLMN selection may also refer to a procedure for the 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 SNPN, PNI-NPN, or both.

[0088] Next, an SNPN is a network operated by an NPN operator and unaffected by the functional units provided by a PLMN. In other words, an SNPN is a dedicated NPN network independent of the publicly accessible PLMN. An SNPN may be a network identified by an SNPN ID (SNPN identity). The SNPN ID may be a combination of the PLMN ID and the NID (Network identifier). 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, if a UE is registered with an SNPN, the registered SNPN may be referred to as a registered SNPN or RSNPN (registered SNPN).

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

[0090] Next, an SM (Session Management) message may be a NAS message used in the procedures for SM. An SM message may also be called a NAS (Non-Access-Stratum) SM message. An SM message may be a control message sent and received between UE_A10 and SMF_A230 via AMF_A240.

[0091] Next, the MM (Mobility Management) message may be a NAS message used for MM procedures. The MM message may be a control message sent and received between UE_A10 and AMF_A240. The MM message may also be called a NAS MM message.

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

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

[0094] Next, a PDU (Protocol Data Unit) session can be defined as the relationship between a DN and an UE that provides PDU connectivity services, but it may also be connectivity established between the UE and an external gateway. In 5GS, the UE can send and receive user data to and from the DN using the PDU session by establishing a PDU session via access network_B and core network_B. Here, this external gateway may be UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers located on the DN. Furthermore, each device (UE, and / or access network device, and / or core network device) may manage by associating one or more pieces of identification information with each PDU session. These pieces of identification information may include one or more of the following: DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, or other information may be included. Furthermore, when multiple PDU sessions are established, the pieces of identification information associated with each PDU session may be the same or different.

[0095] Next, the DNN (Data Network Name) may be identification information that identifies the core network and / or external networks such as DNs. Furthermore, the DNN can also be used as information to select gateways such as PGW / UPFs that connect to the core network B190.

[0096] Furthermore, a network slice (NS) is a logical network that provides specific network capabilities and characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. Network slices are sometimes simply referred to as slices.

[0097] UEs and / or devices within the network can be assigned to one or more NSs based on registration information such as NSSAI and / or S-NSSAI and / or UE usage type and / or one or more NSI IDs and / or APN. The UE usage type is a parameter value included in the UE's registration information used to identify the NSI. The UE usage type may be stored in the HSS. The AMF may select between SMF and UPF based on the UE usage type.

[0098] Furthermore, S-NSSAI (Single Network Slice Selection Assistance Information) is information used to identify an NS. S-NSSAI may consist only of SST (Slice / Service type), or it may consist of SST and SD (Slice Differentiator). Here, SST is information that indicates the expected behavior of the NS in terms of function and service. SD may be information that complements SST when selecting one NSI from multiple NSIs indicated by SST. S-NSSAI may be information specific to each PLMN or SNPN, or it may be standard information common to PLMNs or SNPNs.

[0099] Furthermore, S-NSSAI may be transmitted and received between devices using a 5GS S-NSSAI IE, in which case S-NSSAI may consist of an S-NSSAI (SST and / or SD) associated with the current PLMN or SNPN, and / or an HPLMN S-NSSAI (SST and / or SD) (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). In addition, the S-NSSAI IE transmitted and received between the UE and the NW may consist of an S-NSSAI composed of an SST and / or SD of a registered PLMN or SNPN, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN or HSNPN to which that S-NSSAI is mapped. One or more S-NSSAIs stored by the UE and / or NW may consist of an SST and / or SD, or an S-NSSAI composed of an SST and / or SD, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN to which that S-NSSAI is mapped.

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

[0102] Furthermore, a configured NSSAI is an NSSAI supplied to and stored within the UE. The UE may store a configured NSSAI for each PLMN or SNPN. The UE may also store a configured NSSAI associated with a PLMN or SNPN.

[0103] In this paper, a configured NSSAI associated with PLMN may also be expressed as a configured NSSAI for PLMN, or a configured NSSAI of PLMN, or a configured NSSAI for PLMN, or a configured NSSAI associated with PLMN. Similarly, a configured NSSAI associated with SNPN may be expressed as a configured NSSAI for SNPN, or a configured NSSAI of SNPN, or a configured NSSAI for SNPN, or a configured NSSAI associated with SNPN.

[0104] Furthermore, the UE may store a configured NSSAI that is not associated with a PLMN but is valid for all PLMNs, and may designate such a configured NSSAI as the "default configured NSSAI". Similarly, the UE may store a configured NSSAI that is not associated with an SNPN but is valid for all SNPNs, and may designate such a configured NSSAI as the "default configured NSSAI". The UE may store a configured NSSAI that is not associated with either a PLMN or an SNPN but is valid for all PLMNs and SPNNs, and may designate such a configured NSSAI as the "default configured NSSAI".

[0105] A configured NSSAI may be associated with multiple PLMNs or SNPNs, where these 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 configured S-NSSAI. The configured S-NSSAI may be sent and received using an S-NSSAI IE, in which case the configured S-NSSAI may consist of an S-NSSAI (SST and / or SD) and a 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) for PLMN or SNPN and the S-NSSAI (SST and / or SD) for HPLMN or SNPN may be treated independently. Specifically, the configured S-NSSAI for PLMN or SNPN may be expressed as "configured S-NSSAI for PLMN or SNPN", "configured S-NSSAI for PLMN or SNPN", or "configured S-NSSAI for PLMN or SNPN".

[0108] The configured NSSAI may be updated by the network at any time, and the updated configured NSSAI may be sent from the network to the user entity based on the update.

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

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

[0111] The requested NSSAI may be information containing one or more S-NSSAIs associated with network slices requested by the UE. 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 to be allowed 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 an S-NSSAI included in an allowed NSSAI associated with the current PLMN.

[0112] In other words, a 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 above two. More specifically, an allowed NSSAI associated with a current PLMN may be an allowed NSSAI associated with a current PLMN and a current access type. Furthermore, a requested NSSAI may be a 5GS requested NSSAI.

[0113] Furthermore, the S-NSSAI included in the requested NSSAI may be an S-NSSAI that the UE stores and is not included in the rejected NSSAI associated with the current PLMN or SNPN, and / or an S-NSSAI that the UE stores and is not included in the pending NSSAI associated with the current PLMN or SNPN.

[0114] Furthermore, an allowed NSSAI is information that indicates one or more network slices that the UE has been allowed to connect to. In other words, an allowed NSSAI is information that identifies the network slices that the network has allowed the UE to connect to. An allowed NSSAI may be an allowed NSSAI stored by the UE and / or the network, or an allowed NSSAI sent from the network to the UE. In that case, an allowed NSSAI may mean a 3GPP allowed NSSAI IE.

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

[0116] Furthermore, the list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN and are included in the allowed NSSAI IE may be referred to as the Allowed NSSAI, and the list of mapped S-NSSAIs, which are the S-NSSAIs of the HPLMN or HSNPN to which the current PLMN or SNPN's S-NSSAI is 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 also be the 3GPP's mapped S-NSSAI(s) for the allowed NSSAI for a PLMN. Similarly, Allowed NSSAI may mean the 3GPP's allowed NSSAI for a PLMN or an SNPN.

[0117] The UE and / or NW may store and manage allowed NSSAIs as part of the UE's information for each access (3GPP access or non-3GPP access). The UE and / or NW may further manage allowed NSSAIs in association with registration areas.

[0118] Furthermore, the UE and / or NW may store and manage allowed NSSAIs as UE information, associated with PLMNs or SNPNs. An allowed NSSAI may be associated with multiple PLMNs, which may be EPLMNs, and which may be ESNPNs.

[0119] In this paper, allowed NSSAI associated with PLMN or SNPN and access types may be expressed as "allowed NSSAI for PLMN or SNPN and access type," or "allowed NSSAI for the access type of PLMN or SNPN."

[0120] An S-NSSAI included in an allowed NSSAI may also be expressed as an allowed S-NSSAI. An allowed S-NSSAI may be sent and received using an S-NSSAI IE, in which case the allowed S-NSSAI (SST and / or SD) may consist of an S-NSSAI and a mapped S-NSSAI (the mapped HPLMN or SNPN SST and / or the mapped HPLMN or SNPN SD) (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) for PLMN or SNPN and the S-NSSAI for HPLMN or SNPN (mapped HPLMN or SNPN SST and / or mapped HPLMN or SNPN SD) may be treated independently. Specifically, the Allowed S-NSSAI for PLMN or SNPN may be expressed as "allowed S-NSSAI for PLMN or SNPN", "allowed S-NSSAI of PLMN or SNPN", or "allowed S-NSSAI for PLMN or SNPN".

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

[0123] Next, an MA PDU (Multi-Access PDU) session may be a PDU session that can have user plane resources on 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, an MA PDU session may exchange PDUs between the UE and 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. To put it another way, an MA PDU session is a PDU session that provides PDU connectivity services and at any given time may use one access network, or simultaneously use one 3GPP access network and one non-3GPP access network, or simultaneously use two 3GPP access networks, or simultaneously use two non-3GPP access networks.

[0124] Furthermore, an MA PDU (Multi-Access PDU) session may be a PDU session that can have user plane resources on 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, an MA PDU session may exchange PDUs between the UE and DN by using both PLMN and NPN simultaneously, by using both PLMN and PLMN simultaneously, or by using both NPN and NPN simultaneously.

[0125] Furthermore, an MA PDU session may be a PDU session that can have one or more user plane resources for each RAT type. Alternatively, an MA PDU session may be a PDU session that can have one or more user plane resources for each RAT type of a satellite NG-RAN. Furthermore, an MA PDU session may be a PDU session that can have one or more user plane resources for one RAT type of a ground NG-RAN and one RAT type of a satellite NG-RAN. In this case, the MA PDU session may have a different name, for example, "MA PDU session for RAT type".

[0126] We will also explain how MA PDU sessions will be handled once the non-registration process is complete.

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

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

[0129] Furthermore, an MA PDU session may be a PDU session using user plane resources via satellite and / or user plane resources via non-satellite (ground) access. Here, 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 the RAT type of satellite NG-RAN. Also, user plane resources via non-satellite (ground) access may be user plane resources via 3GPP access, user plane resources via non-3GPP access, or user plane resources different from the RAT type of satellite NG-RAN.

[0130] Furthermore, MA PDU sessions that use two 3GPP access networks, or MA PDU sessions that use two non-3GPP access networks, may be referred to as PDU sessions distinct from MA PDU sessions.

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

[0132] The Radio Access Technology (RAT) type of a satellite NG-RAN may be information used to identify or distinguish different types of satellite NG-RAN access in satellite NG-RAN access. For example, the RAT types of a satellite NG-RAN may include "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 another satellite. The RAT type of a satellite NG-RAN may be any RAT type.

[0133] Next, network slice usage control may be a control that the network imposes on the UE to restrict network slices. Network slice usage control may involve setting a network-controlled slice usage policy on the UE. Network slice usage control may also involve setting a PDU sessions inactivity timer and a network slice deregistration inactivity timer.

[0134] A network-controlled slice usage policy can be any policy used to implement network slice usage control.

[0135] Next, an on-demand S-NSSAI may be an S-NSSAI that is permitted to register with the network. An on-demand S-NSSAI may be an S-NSSAI that is permitted to register with the network only when the UE establishes a PDU session for sending and receiving user data.

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

[0137] On-demand S-NSSAI may be an S-NSSAI for implementing network slice usage control. On-demand S-NSSAI may simply be interpreted as S-NSSAI.

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

[0139] The slice unregistered deactivation timer may be started and / or stopped by the UE and / or AMF for each access type. In MA PDU sessions, the slice unregistered deactivation timer may be started and / or stopped by the UE and / or AMF regardless of the access type.

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

[0141] The slice unregistered inactive timer may be stopped and reset when a PDU session is established. The slice unregistered inactive timer may be stopped and reset when an S-NSSAI is removed from an allowed NSSAI.

[0142] The start and stop conditions for the slice unregistered inactive timer are not limited to these. Here, S-NSSAI may be on-demand S-NSSAI.

[0143] When the slice unregistered deactivation timer expires, the AMF and / or 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] A slice unregistered inactive timer may be a timer for implementing network slice usage control.

[0145] The slice unregistered inactive timer for on-demand S-NSSAI can simply be referred to as the slice unregistered inactive timer.

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

[0147] The first identification information may be information indicating whether or not 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 identifier may be a request type information element. The request type information element may simply be expressed as "request type". The second identifier may be a request type information element set to MA PDU request. 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, existing PDU session, initial emergency request, existing emergency PDU session, modification request, or reserved.

[0150] The third identifier may be information indicating a network slice requested by the UE. The third identifier may be a requested NSSAI. The third identifier may be a requested NSSAI containing one or more S-NSSAIs.

[0151] The tenth identification information may be an S-NSSAI that is permitted to register on the network. The tenth identification information may be an S-NSSAI that is permitted to register on the network only when the UE establishes a PDU session for sending and receiving user data.

[0152] The tenth identification information may be an on-demand S-NSSAI. The tenth identification information may be one or more S-NSSAIs within a configured NSSAI. The tenth identification information may be one or more S-NSSAIs within 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 11th identification information may be a timer value. The 11th identification information may be the timer value of a slice unregistered inactive timer.

[0155] The 11th identification information may be a slice-unregistered, inactive timer. The 11th identification information may be a slice-unregistered, inactive timer with a timer value set.

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

[0157] The 11th identification information may be associated with the 10th identification information. The 11th identification information may be included in the 10th identification information. The 11th identification information may be associated with on-demand S-NSSAI. The 11th identification information may be a timer value within on-demand S-NSSAI. The 11th identification information may be a timer value for on-demand S-NSSAI.

[0158] The 12th identifying information may be an Access type information element (Access type IE). The 12th identifying information may be information indicating 3GPP access or non-3GPP access.

[0159] The 13th identification information may be a network-controlled slice usage policy. The 13th identification information may include the 10th, 11th, and 14th identification information.

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

[0161] The 15th identification information may indicate that the network supports ATSSS (Access Traffic Steering, Switching and Splitting). The 15th identification information may indicate that the network does not support ATSSS. The 15th identification information may indicate whether or not the network supports ATSSS.

[0162] The 15th identification information may be 5GS network feature support. The 15th identification information may be information indicating whether or not ATSSS is supported within 5GS network feature support. Information indicating whether or not ATSSS is supported may be included in 5GS network feature support.

[0163] The 16th identification information may be a configured NSSAI. The 16th identification information may be one or more S-NSSAIs within a configured NSSAI. The 16th identification information may be a configured NSSAI that includes the 10th identification information. The 16th identification information may be a configured NSSAI associated with the 10th, and / or 13th, and / or 14th identification information. The 16th identification information may be one or more S-NSSAIs within a configured NSSAI associated with the 10th, and / or 13th, and / or 14th identification information.

[0164] The 17th identification information may be an allowed NSSAI. The 17th identification information may be one or more S-NSSAIs within an allowed NSSAI. The 17th identification information may be an allowed NSSAI that includes the 10th identification information. The 17th identification information may be an allowed NSSAI associated with the 10th, and / or 13th, and / or 14th identification information. The 17th identification information may be one or more S-NSSAIs within an allowed NSSAI associated with the 10th, and / or 13th, and / or 14th identification information.

[0165] The 18th identification information may be information indicating the RAT type. The 18th identification information may be information indicating the RAT type of a ground-based NG-RAN, or information indicating the RAT type of a satellite-based NG-RAN. The 18th identification information may be information that includes information indicating the RAT type of a ground-based NG-RAN and information indicating the RAT type of a satellite-based NG-RAN. The 18th identification information may be information that combines information indicating the RAT type of a ground-based NG-RAN and information indicating the RAT type of a satellite-based NG-RAN.

[0166] [3. Description of the procedures used in each embodiment] Next, the procedures used in each embodiment will be described.

[0167] In each embodiment, the explanation will be based on the example where the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software), as shown in Figure 2. However, the contents described in this embodiment are also applicable when 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 them, 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 explained using Figure 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 in which the UE takes the lead in registering with access network_B and / or core network_B and / or DN. If the UE is not registered with the network, it can execute this procedure at any time, for example, when the power is turned on. In other words, if the UE is in the unregistered state (RM-DEREGISTERED state), it can start this procedure at any time. In addition, each device (especially the UE and 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 for 3GPP access (registered state or unregistered state) and the registration state for non-3GPP access.

[0169] Furthermore, the registration procedure may be a registration procedure for initial registration. It may also be a registration procedure for mobility and periodic registration update. Furthermore, the registration procedure may be referred to simply as registration.

[0170] Furthermore, the registration procedure may also 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 specific parameters related to the UE in the network.

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

[0172] A UE may initiate the registration process when it moves across TAs. In other words, a UE may initiate the registration process when it moves to a TA different from the one indicated in its TA list. Furthermore, a UE may initiate the registration process when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, a UE may initiate the registration process when there is a change in the capability information and / or preferences related to the establishment of the UE's PDU session. Furthermore, a UE may initiate the registration process periodically. Furthermore, a UE may initiate the registration process based on the completion of the UE configuration update procedure. Note that a UE can perform the registration process at any time it chooses, not limited to these.

[0173] Furthermore, even if a UE is already registered, it may initiate the registration process periodically.

[0174] Furthermore, registration procedures performed based on UE mobility and registration procedures performed periodically may be referred to as registration procedures for mobility and registration renewal. In other words, registration procedures for mobility and registration renewal may be registration procedures performed based on UE mobility, or registration procedures performed periodically. Moreover, registration procedures for mobility and registration renewal may be registration procedures performed based on UE configuration updates. Furthermore, registration procedures for mobility and registration renewal may be registration procedures performed to establish a communication channel for sending and receiving user data. Furthermore, registration procedures for mobility and registration renewal may be registration procedures performed based on requests from the network. In other words, registration procedures for mobility and registration renewal may be registration procedures other than registration procedures for initial registration.

[0175] Next, we will explain each step of the registration procedure. Note that the registration procedure described below may be for initial registration or for mobility and registration renewal.

[0176] First, the UE initiates the registration process by sending a Registration request message to the AMF (S800)(S802)(S804). Specifically, the UE sends an RRC message containing the Registration request message to the 5G AN (or gNB) (S800). The Registration request message is a NAS message. The RRC message may be a control message sent and received between the UE and the 5G AN (or gNB). The NAS message is processed at the NAS layer, and the RRC message is processed at the RRC layer. The NAS layer is a higher layer than the RRC layer.

[0177] Here, the UE may include one or more of the first and third pieces of identification information in the registration request message and / or RRC message. More specifically, the UE may include one or more of the first and third pieces of identification information in the registration request message and / or RRC message, or it may include them in a different control message, for example, a control message at a lower layer than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer).

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

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

[0180] Furthermore, the UE may indicate to the network that it supports each function, or indicate the UE's request, by sending a registration request message.

[0181] Furthermore, the UE may include one or more of the first and third types of identification information in the registration request message and send it, thereby indicating to the network what the identification information included in the registration request message represents.

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

[0183] Furthermore, the UE may include identification information other than the first and third types of identification information in the registration request message.

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

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

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

[0187] When the AMF receives a registration request message, it can perform a first conditional determination. This first conditional determination determines whether the network (or the AMF) will accept the UE's request. If the first conditional determination is true, the AMF initiates the procedure shown in Figure 6(A); if the first conditional determination is false, it initiates the procedure shown in Figure 6(B).

[0188] Furthermore, the first condition determination may be performed based on the receipt 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 context held by AMF, etc. For example, if the network permits the UE's request, the first condition determination may be true, and if the network does not permit the UE's request, the first condition determination may be false. Also, if the network to which the UE is registered, and / or the devices within the network, support the function requested by the UE, the first condition determination may be true, and if they do not support the function requested by the UE, the first condition determination may be false. In addition, if the transmitted and received identification information is permitted, the first condition determination may be true, and if the transmitted and received identification information is not permitted, the first condition determination may be false. Furthermore, the conditions that determine the truth or falsity of the first condition determination are not limited to those described above.

[0189] First, let's explain the case where the first condition is true. In the procedure shown in Figure 6(A), the AMF sends a Registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message (S806). The Registration accept message is a NAS message sent and received on the N1 interface, but it is included in the RRC message sent and received between the UE and the 5G AN (gNB).

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

[0191] Furthermore, AMF may indicate to the UE what these identifications represent by including one or more of the identifications from items 10 to 11 and 13 to 17 in the registration acceptance message.

[0192] Furthermore, AMF may select and decide whether to include one or more of the identification information from items 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 policies, and / or network status, and / or user registration information, and / or context held by AMF.

[0193] Furthermore, the AMF may indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF.

[0194] Furthermore, the AMF may include information in the registration acceptance message indicating that some of the UE's requests have been rejected, or may indicate the reason why some of the UE's requests have been rejected by sending information indicating that some of the UE's requests have been rejected. Furthermore, the UE may become aware of the reason why some of its requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may also be information indicating that the content of the identification information received by the AMF is not permitted.

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

[0196] Here, upon receiving the registration acceptance message, the UE may recognize that its request in the registration request message has been accepted, and may also recognize the content of various identification information contained in the registration acceptance message.

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

[0198] When the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

[0199] When the UE receives the 13th identification, it may recognize and remember the network control slice usage policy. When the UE receives the 13th identification, it may use the 13th identification to determine the 10th and 11th identifications.

[0200] When the UE receives the 14th 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 14th identification information, it may recognize which of the one or more S-NSSAIs included in the configured NSSAI is an on-demand S-NSSAI. When the UE receives the 14th identification information, it may recognize that all S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the 14th 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 piece of identification information, it may recognize that the network supports ATSSS.

[0202] If the UE receives the 16th identification information, it may store the received configured NSSAI. If the UE receives the 16th identification information, it may store the received S-NSSAI as a configured NSSAI. If the UE receives the 16th identification information, it may store the received 16th identification information as a configured NSSAI. Also, if the UE already has a configured NSSAI stored, it may update the received 16th identification information as a configured NSSAI.

[0203] If the UE receives the 17th identification information, it may store the received allowed NSSAI. If the UE receives the 17th identification information, it may store the received S-NSSAI as an allowed NSSAI. If the UE receives the 17th identification information, it may store the received 17th identification information as an allowed NSSAI. Also, if the UE already has an allowed NSSAI stored, it may update the received 17th identification information as an 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 a NAS message sent and received on the N1 interface, but it is included in the RRC message sent 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 Figure 6(A) based on the sending and receiving of registration acceptance messages and / or registration completion messages.

[0207] Furthermore, the UE may perform SNPN selection or PLMN selection based on the receipt of a registration acceptance message. The UE may also perform SNPN selection or PLMN selection based on the sending of a registration completion message.

[0208] Next, we will explain the case where the first condition determination is false. In the procedure shown in Figure 6(B), the AMF sends a registration rejection message to the UE via the 5G AN(gNB) as a response message to the registration request message (S810). Here, the registration rejection message is a NAS message that is sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and the 5G AN(gNB).

[0209] Furthermore, the AMF may send a registration rejection message that includes one or more of the identification information from items 10 to 11 and 13 to 17. In addition, the AMF may send these identification information to indicate that the UE's request has been rejected and to indicate the reason for the rejection.

[0210] Furthermore, AMF may indicate to the UE what the identification information included in the registration rejection message represents by including one or more of the identification information from the 10th to 11th and 13th to 17th identification information in the registration rejection message.

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

[0212] Furthermore, the AMF may indicate that the UE's request in the registration request message has been rejected by sending a registration rejection message. The AMF may also include information indicating the reason for the rejection in the registration rejection message, or may indicate the reason for the rejection by sending the reason for the rejection separately. Furthermore, the UE may recognize the reason for the rejection of its request by receiving information indicating the reason for the rejection of its request. The reason for the rejection may also be information indicating that the content of 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 a registration rejection message from the AMF that includes one or more of the identification information from items 10 to 11 and 13 to 17. Upon receiving the registration rejection message, the UE may recognize that its request in 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, it may store the tenth identification information as an on-demand S-NSSAI. When the UE receives the tenth identification information, it may recognize that the received S-NSSAI is an on-demand S-NSSAI. When the UE receives the tenth identification information, it may store the tenth identification information in a configured NSSAI or an allowed NSSAI.

[0215] When the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

[0216] When the UE receives the 13th identification, it may recognize and remember the network control slice usage policy. When the UE receives the 13th identification, it may use the 13th identification to determine the 10th and 11th identifications.

[0217] When the UE receives the 14th 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 14th identification information, it may recognize which of the one or more S-NSSAIs included in the configured NSSAI is an on-demand S-NSSAI. When the UE receives the 14th identification information, it may recognize that all S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the 14th 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 piece of identification information, it may recognize that the network supports ATSSS.

[0219] If the UE receives the 16th identification information, it may store the received configured NSSAI. If the UE receives the 16th identification information, it may store the received S-NSSAI as a configured NSSAI. If the UE receives the 16th identification information, it may store the received 16th identification information as a configured NSSAI. Also, if the UE already has a configured NSSAI stored, it may update the received 16th identification information as a configured NSSAI.

[0220] If the UE receives the 17th identification information, it may store the received allowed NSSAI. If the UE receives the 17th identification information, it may store the received S-NSSAI as an allowed NSSAI. If the UE receives the 17th identification information, it may store the received 17th identification information as an allowed NSSAI. Also, if the UE already has an allowed NSSAI stored, it may update the received 17th identification information as an allowed NSSAI.

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

[0222] Furthermore, if a UE does not receive a registration rejection message after a predetermined period has elapsed since sending a registration request message, the UE may recognize that its request has been rejected.

[0223] Each device completes procedure (B) in this procedure based on the sending and receiving of registration rejection messages.

[0224] Furthermore, the procedure in Figure 6(B) may be initiated if the procedure in Figure 6(A) is canceled.

[0225] Each device completes the registration procedure based on the completion of either procedure (A) or (B) in Figure 6. Alternatively, each device may transition to the state where the UE is registered with the network (RM_REGISTERED state) based on the completion of procedure (A) in Figure 6. Furthermore, each device may maintain the state where the UE is not registered with the network (RM_DEREGISTERED state) or transition to the state where the UE is not registered with the network based on the completion of procedure (B) in Figure 6.

[0226] Furthermore, each device may perform processing based on the information sent and received during the registration process, upon completion of the registration procedure. For example, if it receives information indicating that some of the UE's requests were rejected, it may recognize the reason why the UE's requests were rejected. Furthermore, each device may perform the procedure again based on the reason why the UE's requests were rejected, or it may perform the registration procedure for core network_B or another cell.

[0227] Furthermore, based on the completion of the registration process, the UE may store the identification information received along with the registration acceptance message or registration rejection message, and may recognize the network's decision.

[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 Generic UE configuration update procedure will be explained using Figure 7. Hereafter, the UE configuration update procedure will also be referred to as "this procedure." This procedure is a procedure for the core network to update the configuration information of the UE. This procedure may be a mobility management procedure initiated by the network for UEs registered with the network. Furthermore, the UE configuration update procedure may also be an MM procedure.

[0230] Furthermore, devices within the core network, such as AMF, may initiate this procedure based on network configuration updates and / or operator policy updates. The trigger for this procedure may be detection of UE mobility, detection of a state change in the UE, and / or the access network, and / or the core network, or a state change in a network slice. Furthermore, the trigger for this procedure may be the receipt of a request from the DN and / or the DN's application server, a change in network configuration, or a change in operator policy. Furthermore, the trigger for this procedure may be the expiration of a running timer. However, the triggers for devices within the core network to initiate this procedure are not limited to these. In other words, this procedure may be executed at any time after the aforementioned registration procedure and / or PDU session establishment procedure is completed. Furthermore, this procedure may be executed at any time as long as each device has established a 5GMM context and / or each device is in 5GMM connection mode.

[0231] Furthermore, during this procedure, each device may send and receive messages containing identification information for changing the UE's configuration information and / or for stopping or changing the functions that the UE is performing. In addition, based on the completion of this procedure, each device may update its configuration information to the settings instructed by the network, or initiate the behavior instructed by the network.

[0232] The UE may update its configuration information based on the control information transmitted and received through this procedure. Furthermore, in conjunction with the update of the UE's configuration information, the UE may stop any functions it is currently running or start any new functions. 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 identifiable configuration information using this control information. Furthermore, by causing the UE to update its configuration information, a device in the core network may cause the UE to stop any functions it is currently running or cause the UE to start any new functions.

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

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

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

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

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

[0238] When the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

[0239] When the UE receives the 13th identification, it may recognize and remember the network control slice usage policy. When the UE receives the 13th identification, it may use the 13th identification to determine the 10th and 11th identifications.

[0240] When the UE receives the 14th 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 14th identification information, it may recognize which of the one or more S-NSSAIs included in the configured NSSAI is an on-demand S-NSSAI. When the UE receives the 14th identification information, it may recognize that all S-NSSAIs included in the configured NSSAI are on-demand S-NSSAIs. When the UE receives the 14th 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 piece of identification information, it may recognize that the network supports ATSSS.

[0242] If the UE receives the 16th identification information, it may store the received configured NSSAI. If the UE receives the 16th identification information, it may store the received S-NSSAI as a configured NSSAI. If the UE receives the 16th identification information, it may store the received 16th identification information as a configured NSSAI. Also, if the UE already has a configured NSSAI stored, it may update the received 16th identification information as a configured NSSAI.

[0243] If the UE receives the 17th identification information, it may store the received allowed NSSAI. If the UE receives the 17th identification information, it may store the received S-NSSAI as an allowed NSSAI. If the UE receives the 17th identification information, it may store the received 17th identification information as an allowed NSSAI. Also, if the UE already has an allowed NSSAI stored, it may update the received 17th identification information as an allowed NSSAI.

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

[0245] Furthermore, AMF may select and decide whether to include each identification piece of information in the configuration update command message based on the received identification piece of 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 AMF.

[0246] Furthermore, the AMF may indicate a request to update 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 policies, and / or network status, and / or user registration information, and / or context held by the AMF.

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

[0248] Furthermore, the above behavior of the UE may be performed after receiving a configuration update command message. Also, the above behavior of the UE may be performed after receiving one or more of the identification information from numbers 10 to 11 and 13 to 17.

[0249] Furthermore, when the UE receives a configuration update command message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the configuration update command message.

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

[0251] When the UE sends a configuration update completion command message, the AMF receives the configuration update completion message via the 5G AN (gNB) (S1002). Each device completes this procedure based on the sending and receiving of the configuration update command message and / or the configuration update completion message.

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

[0253] Furthermore, based on the completion of this procedure, the UE may store the identification information received along with the configuration command message, and may recognize the network decision. Also, based on the completion of this procedure, the UE may perform each procedure based on the stored information.

[0254] In the above procedure, by sending and receiving configuration update command messages, devices within the core network can instruct the UE to update configuration information already applied by the UE, or to stop or change functions that the UE is performing.

[0255] [3.3. PDU Session Establishment Procedure] Next, the PDU session establishment procedure will be explained using Figure 8. Hereafter, the PDU session establishment procedure may be referred to as "this procedure." The PDU session establishment procedure may also be an SM procedure.

[0256] Please note that the registration process may have been performed at least once prior to this procedure.

[0257] Next, we will explain each step of the PDU session establishment procedure.

[0258] First, the UE sends a PDU session establishment request message to the SMF (S1200), (S1202), (S1204) to initiate the PDU session establishment procedure. The SMF then 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 containing an N1 SM container with 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 include one or more of the first to third pieces of identification information in the PDU session establishment request message or the NAS message. The UE may include the second piece of identification information in the UL NAS transport message.

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

[0262] If the network supports ATSSS, the UE may send a second set of 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, when the UE requests a network slice, it may send a third identifier.

[0264] Furthermore, by transmitting this identification information, the UE may indicate that it supports each function or that it has a request for it. In addition, if multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be combined into one or more pieces of identification information. Furthermore, the information indicating support for each function and the information indicating a request for the use of each function may be transmitted and received with the same identification information or with different identification information.

[0265] Furthermore, 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 types of 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.

[0267] Furthermore, the UE may include identification information other than the first to third types of identification information in the PDU session establishment request message.

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

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

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

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

[0272] Next, the AMF selects an SMF as the destination for at least some of the information (message, container, information) contained in the NAS message received from the UE (S1202). The AMF may also select the destination SMF based on the information (message, container, information) contained in the NAS message, and / or subscriber information, and / or network capability information, and / or UE policies, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF.

[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 conditional determination. This second conditional determination may be for determining whether the network accepts the UE's request. If the SMF determines that the second conditional determination is true, it may initiate the procedure shown in Figure 8(A); if it determines that the second conditional determination is false, it may initiate the procedure shown in Figure 8(B).

[0276] Furthermore, 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 to that NF the information necessary for performing the second condition determination, specifically, at least a part of the information received from the UE (S1206). And when that NF determines the truth or falsehood of the second condition determination based on the information received from the SMF, it may convey to the SMF the information including the result of the second condition determination (that is, true or false). The SMF may determine the identification information and / or control message to be transmitted to the UE based on the result of the second condition determination received from that NF.

[0277] Furthermore, the second condition determination may be performed based on information etc. (messages, containers, information) received from the AMF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network state, and / or user registration information, and / or context etc. held by the SMF.

[0278] For example, when the network permits the UE's request, the second condition determination may be determined to be true, and when the network does not permit the UE's request, the second condition determination may be determined to be false. Also, when the network to which the UE is connected and / or the device in the network supports the function requested by the UE, the second condition determination may be determined to be true, and when it does not support the function requested by the UE, the second condition determination may be determined to be false. Also, when the transmitted and received identification information is permitted, the second condition determination may be determined to be true, and when the transmitted and received identification information is not permitted, the second condition determination may be determined to be false.

[0279] Furthermore, the conditions for determining the truth or falsehood of the second condition determination may not be limited to the conditions described above.

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

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

[0282] Here, the SMF may select one or more UPFs based on information such as messages, containers, and information received from the AMF, and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policies, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the SMF, etc. Also, when multiple UPFs are selected, the SMF may send a N4 session establishment request message to each UPF. Here, it is assumed that a UPF has been selected.

[0283] [[ID=!]]

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

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

[0286] It should be noted that there seems to be a formatting issue in the original text where the tag is not properly separated in the English translation. It might be a formatting error in the original text that needs to be corrected in the source material for a more seamless translation flow.Specifically, based on the receipt of a PDU session establishment request message and / or selection of a UPF and / or receipt of an N4 session establishment response message, the SMF sends the N1 SM container, and / or N2 SM information, and / or PDU session ID to the AMF, for example, via the N11 interface (S1212). Here, the N1 SM container may contain a PDU session establishment acceptance message. Furthermore, the PDU session ID may be included in the PDU session establishment acceptance message.

[0287] Next, having received the N1 SM container and / or N2 SM information and / or PDU session ID, the AMF 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 also be a downlink NAS transport (DL NAS TRANSPORT) message.

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

[0289] Furthermore, the PDU session establishment acceptance message may be a response message to a PDU session establishment request. Also, the PDU session establishment acceptance message 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 N1 SM container and / or PDU session ID and / or NAS message and / or N2 SM information and / or N2 PDU session request message.

[0291] Here, the SMF and / or AMF may include the 11th identification information in the PDU session establishment acceptance message and / or N1 SM container and / or NAS message and / or N2 SM information and / or 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, that the UE's request has been accepted, that it has not authorized the request from the UE, or a combination of these.

[0293] Furthermore, the SMF and / or AMF may decide which identification information to include in the PDU session establishment acceptance message, and / or N1 SM container, and / or NAS message, and / or N2 SM information, and / or 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.

[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 a PDU session establishment acceptance message and / or a NAS message from the SMF that includes the 11th identification information. When the UE receives a PDU session establishment acceptance message and / or a NAS message, it may recognize that the UE's request by the PDU session establishment request message has been accepted and / or the contents of the information (message, container, information) contained in the NAS message.

[0295] Specifically, when the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

[0296] Furthermore, if the UE receives a PDU session establishment acceptance message and / or a NAS message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the PDU session establishment acceptance message and / or NAS message.

[0297] Next, we will explain each step of the procedure in Figure 8(B).

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

[0299] Specifically, based on the reception of a PDU session establishment request message, the SMF transmits, for example, an N1 SM container and / or a PDU session ID to the AMF via, for example, the N11 interface (S1218). Here, the N1 SM container may include a PDU session establishment rejection message. Further, 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. Also, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. Further, the NAS message may include a PDU session ID and / or an N1 SM container.

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

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

[0303] In addition, the SMF may indicate that the UE's request has been rejected by transmitting the PDU session establishment rejection message, or may indicate that the request from the UE has not been permitted, or may indicate information combining these.

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

[0305] Furthermore, the SMF and / or AMF may decide which identification information to include in the PDU session establishment rejection message, and / or N1 SM container, and / or NAS message, and / or N2 SM information, and / or 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.

[0306] Furthermore, the SMF and / or AMF may include information indicating that the UE's request has been rejected in the PDU session establishment rejection message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message, or may indicate the reason for the rejection of the UE's request by sending information indicating that the UE's request has been rejected. Furthermore, the UE may recognize the reason for the rejection of its request by receiving information indicating that the UE's request has been rejected. The reason for 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 is unavailable.

[0307] Next, the UE receives a NAS message and / or a PDU session establishment rejection message (S1218)(S1220)(S1222). The UE may also receive a PDU session establishment rejection message and / or a NAS message from the SMF, which includes the 11th identification information. When the UE receives a PDU session establishment rejection message and / or a NAS message, it may recognize that the UE's request by the PDU session establishment request message has been rejected and / or the contents of the information (message, container, information) contained in the NAS message.

[0308] Specifically, when the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

[0309] Furthermore, if the UE receives a PDU session establishment rejection message and / or a NAS message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the PDU session establishment rejection message and / or NAS message.

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

[0311] Furthermore, each device may complete this procedure based on the sending and receiving of 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 are no already established PDU sessions.

[0312] Furthermore, each process performed by the UE based on the receipt of each piece of identification information as described above may be performed during or after this procedure, or after this procedure is completed, based on the completion of this procedure.

[0313] Furthermore, if the UE receives a PDU session acceptance message or a PDU session rejection message, it may perform the following actions:

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

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

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

[0317] [3.4. Overview of Network-Driven Session Management Procedures] Next, we will describe the outline of the network-led session management procedure. Hereafter, the network-led session management procedure will also be referred to as "this procedure." This procedure is a session management procedure that the network takes the lead in executing for established PDU sessions.

[0318] Furthermore, this procedure may be a network-requested PDU session modification procedure and / or a network-requested PDU session release procedure, or any other network-requested session management procedure.

[0319] Furthermore, 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 message. Also, 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 message.

[0320] Furthermore, the network-initiated session management request message in this procedure may simply be referred to as the session management request message. Similarly, the network-initiated session management completion message in this procedure may simply be referred to as the session management completion message.

[0321] Furthermore, 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 message. Also, 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 message.

[0322] [3.4.1. Examples of Network-Driven Session Management Procedures] Next, using Figure 9, we will explain an example of a network-driven session management procedure. Hereafter, "this procedure" refers to the network-driven session management procedure. We will now explain each step of this procedure.

[0323] Upon completion of the registration and / or PDU session establishment procedures, the UE and each device within the core network_B190 will initiate network-driven session management procedures at any time.

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

[0325] Furthermore, devices within core network_B190 may initiate this procedure upon request from devices in DN or other devices within the core network.

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

[0327] The device within core network_B190 sends a network-initiated session management request message to the UE (S1602) and initiates network-initiated session management. Furthermore, the UE receives a network-initiated session management request message from the device within core network_B190.

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

[0329] Furthermore, devices within core network_B190 may send network-initiated session management request messages to the UE along with at least one of the identification information items 11, 12, and 18. In addition, the UE may receive network-initiated session management request messages from devices within core network_B190 along with at least one of the identification information items 11, 12, and 18.

[0330] Furthermore, the PDU session ID included in the PDU session change request message may be the PDU session ID of an established PDU session. In addition, if this procedure is performed based on a UE-led 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 UE's behavior upon receiving each piece of identification information may be based on the receipt of a PDU session change command message or a PDU session release command message. Alternatively, the UE's behavior upon receiving each piece of identification information may be performed after the receipt of a PDU session change command message or a PDU session release command message.

[0332] Specifically, when the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

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

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

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

[0336] Here, the UE may include the PDU session ID in the network-initiated session management completion message. The PDU session ID included in the network-initiated session management completion message may be the same as the PDU session ID included in the network-initiated session management request message.

[0337] The following describes an example of the first process.

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

[0339] Furthermore, the UE may perform the actions to be taken when it receives each of the aforementioned identification pieces of information as the first process.

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

[0341] Furthermore, each device completes the network-driven session management procedure based on the completion of the above-described processes and / or the sending and receiving of network-driven session management request messages and / or network-driven session management completion messages.

[0342] Furthermore, each device may modify existing PDU sessions or release existing PDU sessions based on the completion of network-driven session management procedures. In other words, each device may modify existing PDU sessions based on the completion of PDU session modification procedures. Similarly, each device may release existing PDU sessions based on the completion of PDU session release procedures.

[0343] Furthermore, if the UE receives a PDU session release command message, it may start a slice de-registration deactivation timer.

[0344] Here, the slice deregistration deactivation timer may be started if S-NSSAI is not used by a PDU session on the corresponding access type.

[0345] [3.5. Overview of UE-led session management procedures] Next, we will describe the UE-led session management procedure. Hereafter, the UE-led session management procedure will also be referred to as "this procedure." This procedure is a session management procedure that the UE takes the lead in executing for established PDU sessions.

[0346] Furthermore, this procedure may be a UE-requested PDU session modification procedure and / or a UE-requested PDU session release procedure, or any other UE-requested session management procedure not limited to these.

[0347] Furthermore, if this procedure is a UE-led PDU session modification procedure, the session management request message in this procedure may be a PDU session modification request message. Also, if this procedure is a UE-led PDU session release procedure, the session management request message in this procedure may be a PDU session release request message.

[0348] Furthermore, if this procedure is a UE-led PDU session modification procedure, the session management rejection message in this procedure may be a PDU session modification rejection message. Also, if this procedure is a UE-led PDU session release procedure, the session management rejection message in this procedure may be a PDU session release rejection message.

[0349] Furthermore, UE-initiated session management request messages in this procedure may simply be referred to as "session management request messages." Similarly, UE-initiated session management rejection messages in this procedure may simply be referred to as "session management rejection messages."

[0350] [3.5.1. Example of UE-led session management procedure] Next, we will explain each step of this procedure using Figure 10.

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

[0352] First, the UE initiates the 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 by including a PDU session ID, it may request that a modification or release be made to the PDU session identified by the PDU session ID.

[0353] Here, the UE may include a second identifier in the session management request message. Alternatively, the UE may send the second identifier to the SMF along with the session management request message.

[0354] Specifically, if the network supports ATSSS, the UE may send a second identification. 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 a session management request message sent by the UE. If the SMF accepts the UE's request, it initiates 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, when the network receives the second identification information, it can recognize that the UE is requesting to establish an MA PDU session.

[0358] Conversely, if the SMF rejects the UE's request, it sends a UE-initiated session management rejection message to the UE (S1806). The following describes what happens when the SMF rejects the UE's request.

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

[0360] Here, the SMF may include at least one of the identifiers 11, 12, and 18 in the session management rejection message. The SMF may also send at least one of the identifiers 11, 12, and 18 to the UE along with the session management rejection message.

[0361] Here, the PDU session ID included in the session management rejection message may be the same as the PDU session ID included in the session management request message. In other words, the PDU session ID included in the session management rejection message may be the same as the PDU session ID provided by the UE during this procedure.

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

[0363] Specifically, when the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

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

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

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

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

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

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

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

[0371] In this embodiment, network-driven session management procedures and / or non-registration procedures may be performed, or other procedures may be performed. Furthermore, these procedures may be procedures for MA PDU sessions.

[0372] Furthermore, prior to this embodiment, registration procedures and / or UE configuration update procedures and / or PDU session establishment procedures and / or network-driven session management procedures and / or UE-driven session management procedures may be performed. Also, this embodiment may be performed after these procedures have been performed multiple times. Furthermore, these procedures may be procedures for MA PDU sessions.

[0373] Furthermore, this embodiment may be carried out multiple times.

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

[0375] In this embodiment, the UE may hold a pre-configured 11th identification information.

[0376] The following describes each step of this embodiment.

[0377] First, the network may send a first control message to the UE. The network may also send a first control message to the UE that includes one or more of the identification information from the 11th, 12th, and 18th identification information sets. The network may also send one or more of the identification information from the 11th, 12th, and 18th identification information sets to the UE along with the first control message.

[0378] Here, the network may transmit one or more of the identification information from the 11th, 12th, and 18th identification information to the UE, thereby indicating the content of each identification information.

[0379] Specifically, the network may transmit an 11th identification information to the UE when notifying it of a slice unregistered inactive timer. If the network transmits the 11th identification information, it may start, stop, and reset the slice unregistered inactive timer using the 11th identification information.

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

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

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

[0383] The network may also determine whether or not to transmit the first control message and / or each piece of identification information based on the status of the UE and / or information received from other NFs.

[0384] Next, the UE may receive a first control message from the network. The UE may also receive a first control message from the network that includes one or more of the identification information from the 11th, 12th, and 18th identification information. The UE may also receive one or more of the identification information from the 11th, 12th, and 18th identification information from the network along with the first control message.

[0385] Specifically, when the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

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

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

[0388] Furthermore, based on the reception of the first control message, the UE may store the received identification information or recognize the network decision. The UE may also recognize the content of the received identification information based on the reception of the first control message.

[0389] The behavior of the UE when it receives the first control message for an MA PDU session is described below.

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

[0391] If the first control message contains the twelfth identification information and the MA PDU session has user plane resources established for both 3GPP and non-3GPP access, the UE does not need to start the slice unregistered deactivation timer.

[0392] In other words, if the first control message includes the 12th identification information and the MA PDU session holds user plane resources established for both 3GPP and non-3GPP access, the UE does not need to start a slice deregistration deactivation timer for on-demand S-NSSAI for the access indicated by the 12th identification information.

[0393] In other words, if a UE is registered for 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 12th identification information indicates either 3GPP access only or non-3GPP access only, then the UE does not need to start the slice unregistered deactivation timer applied to the MA PDU session. Also, if a UE is registered for 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 12th identification information indicates either 3GPP access or non-3GPP access, then the UE may start the slice unregistered deactivation timer applied to the MA PDU session.

[0394] If the first control message includes a twelfth identification, and the MA PDU session holds a user plane resource established only for access indicated by the twelfth identification, the UE may start a slice unregistered deactivation timer.

[0395] In other words, if the first control message includes a twelfth identifier, and the MA PDU session holds a user plane resource established only for access indicated by the twelfth identifier, the UE may start a slice deregistration deactivation timer for on-demand S-NSSAI for access indicated by the twelfth identifier.

[0396] To put it another way, if a UE is registered for 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs, and has established user plane resources only via 3GPP access or only via non-3GPP access, and the access indicated by the 12th identification information indicates access (3GPP access or non-3GPP access) corresponding to the established user plane resources, then the slice de-registration deactivation timer applied to the MA PDU session may be started.

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

[0398] If the first control message does not contain the twelfth identification information, the UE may start the slice unregistered deactivation timer.

[0399] In other words, if the first control message does not contain the twelfth identification information, the UE may start a slice deregistration deactivation timer for on-demand S-NSSAI in both 3GPP access and non-3GPP access.

[0400] In other words, if a UE is registered for 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 user plane resources via non-3GPP access, and receives a first control message that does not contain the 12th identification information, it may start a slice de-registration deactivation timer applied to the MA PDU session.

[0401] Furthermore, if a UE is registered for 3GPP access or non-3GPP access in the same PLMN and / or different PLMNs, and has established user plane resources only through established access (3GPP access or non-3GPP access), and receives a first control message that does not contain the 12th identification information, it may start a slice unregistered deactivation timer applied to the MA PDU session.

[0402] Here, the slice deregistration deactivation timer may be started if S-NSSAI is not used by a PDU session on the corresponding access type.

[0403] Furthermore, the slice unregistered deactivation timer may be started if 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 unregistered deactivation timer may be started if the PDU session is an MA PDU session, and S-NSSAI is not used by a PDU session with both 3GPP access and non-3GPP access. In other words, the slice unregistered deactivation timer may be started if the PDU session is an MA PDU session, and S-NSSAI is not used by a user plane resource of an MA PDU session with both 3GPP access and non-3GPP access.

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

[0405] As described above, the slice unregistered inactive timer may be a timer applied to the MA PDU session. In other words, the slice unregistered inactive timer may be a timer managed within the MA PDU session (a timer managed for the MA PDU session as a whole) and not a timer managed for each user plane resource and / or access within the MA PDU session.

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

[0407] If the first control message contains the twelfth identification information and the MA PDU session has user plane resources established for both 3GPP access and non-3GPP access, the UE may start the slice unregistered deactivation timer.

[0408] In other words, if the first control message includes the 12th identification information and the MA PDU session holds user plane resources established for both 3GPP and non-3GPP access, the UE may start a slice deregistration deactivation timer for on-demand S-NSSAI for the access indicated by the 12th identification information.

[0409] To put it another way, if the first control message includes a twelfth identification, and the MA PDU session holds user plane resources established for both 3GPP and non-3GPP access, the UE may start a slice deregistration deactivation timer for on-demand S-NSSAI on the user plane resources of the MA PDU session in the access indicated by the twelfth identification.

[0410] To put it another way, if a UE is registered for 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 12th identification information indicates either 3GPP access only or non-3GPP access only, then a slice unregistered deactivation timer applied to the access indicated by the 12th identification information, which is also applied to user plane resources in an MA PDU session, may be started.

[0411] If the first control message includes a twelfth identification, and the MA PDU session holds a user plane resource established only for access indicated by the twelfth identification, the UE may start a slice unregistered deactivation timer.

[0412] In other words, if the first control message includes a twelfth identifier, and the MA PDU session holds a user plane resource established only for access indicated by the twelfth identifier, the UE may start a slice deregistration deactivation timer for on-demand S-NSSAI for access indicated by the twelfth identifier.

[0413] To put it another way, if the first control message includes a twelfth identifier, and the MA PDU session holds a user plane resource established only for access indicated by the twelfth identifier, the UE may start a slice deregistration deactivation timer for on-demand S-NSSAI in the MA PDU session's user plane resource for access indicated by the twelfth identifier.

[0414] To put it another way, if a UE is registered for 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 access (3GPP access or non-3GPP access) corresponding to the established user plane resources, then a slice unregistered deactivation timer applied to the access indicated by the 12th identification information, which is applied to user plane resources in an MA PDU session, may be started.

[0415] Furthermore, if a UE is registered for 3GPP access or non-3GPP access in the same PLMN and / or different PLMNs, and has established user plane resources only through established access (3GPP access or non-3GPP access), and the access indicated by the 12th identification information indicates access (3GPP access or non-3GPP access) corresponding to an established user plane resource, the UE may start a slice unregistered deactivation timer applied to the access indicated by the 12th identification information, which is a slice unregistered deactivation timer applied to user plane resources in an MA PDU session.

[0416] If the first control message does not contain the twelfth identification information, the UE may start the slice unregistered deactivation timer.

[0417] In other words, if the first control message does not contain the twelfth identification information, the UE may start a slice deregistration deactivation timer for on-demand S-NSSAI in both 3GPP access and non-3GPP access.

[0418] To put it another way, if a UE is registered for 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 user plane resources via non-3GPP access, and receives a first control message that does not contain the 12th identification information, it may start a slice unregistered deactivation timer applied to user plane resources in an MA PDU session. In other words, it may start a slice unregistered deactivation timer applied to 3GPP access, which is a slice unregistered deactivation timer applied to user plane resources in an MA PDU session, and also start a slice unregistered deactivation timer applied to non-3GPP access, which is a slice unregistered deactivation timer applied to user plane resources in an MA PDU session.

[0419] Furthermore, if the UE is registered for 3GPP access or non-3GPP access in the same PLMN and / or different PLMNs, and has established user plane resources only through established access (3GPP access or non-3GPP access), and receives a first control message that does not contain the 12th identification information, it may start a slice unregistered deactivation timer applied to user plane resources in the MA PDU session. In other words, it may start a slice unregistered deactivation timer applied to 3GPP access, which is applied to user plane resources in the MA PDU session, and also start a slice unregistered deactivation timer applied to non-3GPP access, which is applied to user plane resources in the MA PDU session.

[0420] Here, the slice deregistration deactivation timer may be started if S-NSSAI is not used by a PDU session on the corresponding access type.

[0421] Furthermore, the slice unregistered deactivation timer may be started if S-NSSAI is not used by user plane resources of MA PDU sessions on the corresponding access type. Alternatively, the slice unregistered deactivation timer may be started if S-NSSAI is not used by user plane resources of PDU sessions on the corresponding access type.

[0422] In other words, if the PDU session is an MA PDU session, the slice deregistration deactivation 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] Furthermore, the above PLMN may be interpreted as SNPN. That is, the same PLMN may be interpreted as the same SNPN. Also, different PLMNs may be interpreted as different SNPNs.

[0424] As described above, the slice unregistered deactivation timer may be a timer applied to user plane resources in an MA PDU session. In other words, the slice unregistered deactivation timer may be a timer managed per user plane resource and / or per access in an MA PDU session, and may not be a timer managed in the MA PDU session (a timer not managed in the MA PDU session as a whole).

[0425] Furthermore, the above behavior of the UE may be performed after receiving the first control message. Also, the above behavior of the UE may be performed after receiving one or more of the identification information from the 11th, 12th, and 18th identification information.

[0426] Furthermore, if the UE receives the first control message, it may perform the actions that would occur upon receiving each piece of identification information contained 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 this embodiment.

[0428] In this embodiment, a PDU session establishment procedure may be performed, or other procedures may be performed. Furthermore, this procedure may be a procedure for an MA PDU session.

[0429] Furthermore, prior to this embodiment, registration procedures and / or UE configuration update procedures and / or PDU session establishment procedures and / or network-driven session management procedures and / or UE-driven session management procedures may be performed. Also, this embodiment may be performed after these procedures have been performed multiple times. Furthermore, these procedures may be procedures for MA PDU sessions.

[0430] Furthermore, this embodiment may be carried out 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] Furthermore, in this embodiment, the second control message may be a PDU session establishment acceptance message, a PDU session establishment rejection message, or a DL NAS transport message.

[0433] In this embodiment, the UE may hold a pre-configured 11th identification information.

[0434] The following describes each step of this embodiment.

[0435] First, the UE may send a first control message to the network. Alternatively, the UE may send a first control message to the network that includes a second identification information. Furthermore, the UE may send a first control message to the network along with the second identification information.

[0436] Specifically, if the network supports ATSSS, the UE may send a second identification. 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 send it, thereby indicating to the network what the identification information included in the first control message represents.

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

[0439] Next, the network may receive a first control message from the UE. The network may also receive a first control message from the UE that includes a second identification piece. The network may also receive a first control message from the UE along with the second identification piece.

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

[0441] Specifically, when the network receives the second identification information, it can recognize that the UE is requesting to establish an MA PDU session.

[0442] Furthermore, the above network behavior may be performed after receiving the first control message. Also, the above network behavior may be performed after receiving the second identification information.

[0443] Furthermore, when the network receives the first control message, it may perform the actions it would have taken upon receiving each piece of identification information contained in the first control message.

[0444] Furthermore, the network may forward each received identification piece of information to other Network Functions (NFs).

[0445] Next, the network sends a second control message to the UE. Here, the network may include one or more of the identification information from the 11th, 12th, and 18th identification information in the second control message. Alternatively, the network may send the second control message along with one or more of the identification information from the 11th, 12th, and 18th identification information.

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

[0447] Specifically, the network may transmit an 11th identification information to the UE when notifying it of a slice unregistered inactive timer. If the network transmits the 11th identification information, it may start, stop, and reset the slice unregistered inactive timer using the 11th identification information.

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

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

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

[0451] The network may also decide whether or not to send a second control message and / or each piece of identification information based on the status of the UE and / or information received from other NFs.

[0452] Next, the UE receives a second control message from the network. The UE may also receive a second control message from the network that includes one or more of the identification information from the 11th, 12th, and 18th identification information. The UE may also receive a second control message from the network that includes one or more of the identification information from the 11th, 12th, and 18th identification information.

[0453] Specifically, when the UE receives the 11th identification information, it may start a slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may stop and reset the slice unregistered deactivation timer using the 11th identification information. When the UE receives the 11th identification information, it may store the 10th identification information and the 11th identification information in association. That is, when the UE receives the 11th identification information, it may store the 11th identification information for a certain on-demand S-NSSAI.

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

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

[0456] Furthermore, based on the reception of the second control message, the UE may store the received identification information, recognize the content of the received identification information, or recognize a network decision.

[0457] Furthermore, the above behavior of the UE may be performed after receiving the second control message. Also, the above behavior of the UE may be performed after receiving one or more of the identification information from the 11th, 12th, and 18th identification information.

[0458] Furthermore, if the UE receives a second control message, it may perform the actions that occurred when it received each piece of identification information contained in the second control message.

[0459] Furthermore, if the UE receives the second control message, it may perform the following actions.

[0460] First, the following describes how the slice de-registered deactivation timer is started and stopped when 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 unregistered deactivation timer for on-demand S-NSSAI.

[0462] 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 UE may stop and reset the slice unregistered deactivation timer for on-demand S-NSSAI.

[0463] In other words, if the UE supports network slice usage control, and is registered for both 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 unregistered deactivation timer for on-demand S-NSSAI. Furthermore, if the UE supports network slice usage control, and is registered for both 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 unregistered deactivation timer for on-demand S-NSSAI.

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

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

[0466] As described above, the slice unregistered inactive timer may be a timer applied to an MA PDU session. In other words, the slice unregistered inactive timer may be a timer managed within an MA PDU session, but not a timer managed per user plane resource and / or per access within an MA PDU session.

[0467] Next, the following describes how the slice de-registration deactivation timer is started and stopped when S-NSSAI is used by a user plane resource 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 unregistered deactivation timer for on-demand S-NSSAI.

[0469] If the UE supports network slice usage control, and further 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 unregistered deactivation timer for on-demand S-NSSAI.

[0470] In other words, if the UE supports network slice usage control, and is registered for both 3GPP access and non-3GPP access in the same PLMN and / or different PLMNs, and has successfully established user plane resources only via 3GPP access or user plane resources only via non-3GPP access, the UE may stop and reset the slice unregistered deactivation timer for on-demand S-NSSAI. That is, the slice unregistered deactivation timer applied to 3GPP access or non-3GPP access may be stopped and reset, and the slice unregistered deactivation timer applied to user plane resources in MA PDU sessions may also be stopped and reset.

[0471] Furthermore, if the UE supports network slice usage control, and is registered for 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 unregistered deactivation timer for on-demand S-NSSAI. That is, it may stop and reset the slice unregistered deactivation timer applied to 3GPP access, which is applied to user plane resources in MA PDU sessions, and it may also stop and reset the slice unregistered deactivation timer applied to non-3GPP access, which is applied to user plane resources in MA PDU sessions.

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

[0473] As described above, the slice unregistered deactivation timer may be a timer applied to user plane resources in an MA PDU session. In other words, the slice unregistered deactivation timer may be a timer managed per user plane resource and / or per access in an MA PDU session, or a timer that is not managed in an MA PDU session.

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

[0475] [5. Variant] A program that operates in a device according to one aspect of the present invention may be a program that controls a Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of an embodiment according to one aspect of the present invention. The program or the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0476] Furthermore, a program for realizing the functions of an embodiment relating to one aspect of the present invention may be recorded on a computer-readable recording medium. This can also be realized by loading the program recorded on this recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into a device, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0477] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An 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, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuit may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of the present invention may use new integrated circuits based on such technologies.

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

[0479] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Explanation of Symbols]

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

Claims

1. User Equipment (UE) comprising a transmitting / receiving unit and a control unit, In the PDU session establishment procedure for establishing a PDU session, The aforementioned transmitting / receiving unit receives a PDU session establishment acceptance message, 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 the slice unregistered deactivation timer for on-demand S-NSSAI. The slice unregistered deactivation timer is stopped and reset when the MA PDU session associated with the on-demand S-NSSAI is successfully established over 3GPP access and / or non-3GPP access. A UE characterized by the following:

2. User Equipment (UE) comprising a transmitting / receiving unit and a control unit, In the PDU session establishment procedure for establishing a PDU session, The aforementioned transmitting / receiving unit receives a PDU session establishment acceptance message, If the UE supports network slice usage control, and further 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 control unit stops and resets the slice unregistered deactivation timer for on-demand S-NSSAI. The slice unregistered deactivation timer is stopped and reset when the user plane resource of the MA PDU session associated with the on-demand S-NSSAI is successfully established over 3GPP access or non-3GPP access. A UE characterized by the following:

Images