User equipment (UE) and communication control method

Abstract

A UE (User Equipment) has a control section that, in the case of connecting to a SNPN (Stand-alone Non-Public Network) service via a PLMN (Public Land Mobile Network) using a 3GPP access, is configured to operate in SNPN access mode on a non-3GPP access.

Description

Technical Field

[0001] This invention relates to a UE (User Equipment) and a communication control method. This application claims priority based on Japanese Patent Application No. 2020-088863, filed on May 21, 2020, the contents of which are incorporated herein by reference. Background Technology

[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), as a fifth-generation (5G) mobile communication system, was studied, and discussions were held on supporting new processes and functions (see Non-Patent Literature 1-3). The concept of NPN (Non-Public Network) was introduced in Release 16, and the expansion of this function was discussed in Release 17 (see Non-Patent Literature 4).

[0003] Existing technical documents

[0004] Non-patent literature

[0005] Non-patent document 1: 3GPP TS 23.501V16.4.0 (2020-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; SystemArchitecture for the 5G System; Stage 2 (Release 16)

[0006] Non-patent document 2: 3GPP TS 23.502V16.4.0 (2020-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16)

[0007] Non-patent document 3: 3GPP TS 24.501V16.4.1 (2020-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16)

[0008] Non-patent document 4: 3GPP TR 23.700-07V0.3.0(2020-01); 3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Study on enhanced support of non-public networks (Release 17) Summary of the Invention

[0009] The problem the invention aims to solve

[0010] Non-patent literature 4 studies a method for switching between SNPN (Stand-alone NPN) and PLMN as a form of NPN, but it has not been fully discussed and no conclusions have been drawn.

[0011] One aspect of the present invention is based on the above circumstances, providing a method for efficiently switching between SNPN and PLMN.

[0012] Technical solution

[0013] One aspect of the present invention is a user equipment (UE) that includes a control unit. When using 3GPP access to connect to a public land mobile network (PLMN) and an independent non-public network (SNPN) service, the control unit is configured to operate in SNPN access mode on non-3GPP access.

[0014] Another aspect of the present invention is a communication control method executed by a user equipment (UE) that operates in SNPN access mode on non-3GPP access when using 3GPP access to connect via a public terrestrial mobile network (PLMN) and an independent non-public network (SNPN) service.

[0015] Beneficial effects

[0016] According to one aspect of the present invention, switching between SNPN and PLMN can be performed efficiently. Attached Figure Description

[0017] Figure 1 This is a diagram illustrating a mobile communication system with a direct connection to an SNPN.

[0018] Figure 2 This is a diagram illustrating the detailed configuration of a mobile communication system that is directly connected to an SNPN.

[0019] Figure 3 This is a schematic diagram illustrating a mobile communication system with both direct connection to the PLMN and connection to the SNPN via the PLMN.

[0020] Figure 4 This is a diagram illustrating the detailed configuration of a mobile communication system, showing both the case of direct connection to the PLMN and the case of connection to the SNPN via the PLMN.

[0021] Figure 5 This is a diagram illustrating the device configuration of the UE.

[0022] Figure 6 This diagram illustrates the configuration of the access network device (gNB) in 5GS.

[0023] Figure 7 This diagram illustrates the configuration of the core network devices (AMF / SMF / UPF) in 5GS.

[0024] Figure 8 This is a diagram illustrating the login process.

[0025] Figure 9 This is a diagram illustrating the PDU session establishment process.

[0026] Figure 10 This is a diagram illustrating the network-driven non-login process.

[0027] Figure 11 This is a diagram illustrating the non-login process led by the UE.

[0028] Figure 12 This is a diagram illustrating the PDU session release process. Detailed Implementation

[0029] Hereinafter, the preferred embodiment for carrying out the present invention will be described with reference to the accompanying drawings. It should be noted that, in this embodiment, an example is provided to illustrate an implementation of a mobile communication system in which the present invention is applied.

[0030] [1. System Overview]

[0031] Here, we will explain the mobile communication system.

[0032] first, Figure 1 This is a schematic diagram used to illustrate a mobile communication system with a direct connection to SNPN. Figure 2 This is a diagram used to illustrate the detailed configuration of the mobile communication system. Furthermore, Figure 3 This is a diagram illustrating the general layout of a mobile communication system that connects directly to a PLMN and the general layout of a mobile communication system that connects to an SNPN via a PLMN. Figure 4 These are diagrams used to illustrate detailed descriptions of these mobile communication systems.

[0033] Figure 1 The document describes the communication system as consisting of UE (User Equipment)_10, access network_100, core network_200, and DN (Data Network)_250. It should be noted that sometimes the reference numerals for these devices and networks are omitted in the accompanying drawings, such as UE, access network, core network, and DN. Here, Figure 1 The access network can be 3GPP access or non-3GPP access, but 3GPP access is preferred.

[0034] also, Figure 2 It records the device / network functions such as UE_10, base station device_110, AMF (Access and Mobility Management Function)_210, SMF (Session Management Function)_220, UPF (User Plane Function)_230, and DN_250, as well as the interfaces for interconnecting these device / network functions.

[0035] also, Figure 3 The document describes a communication system consisting of UE (User Equipment)_10, access network_102, core network_202, DN (Data Network)_252, core network_200, and DN (Data Network)_250. In the case of a direct connection to a PLMN, the mobile communication system can be composed of parts of UE_10, access network_102, core network_202, and DN (Data Network)_252. Figure 3 The access network _102 can be 3GPP access or non-3GPP access, preferably 3GPP access.

[0036] Furthermore, a mobile communication system connected to an SNPN via a PLMN can be composed of parts of UE_10, an access network, a core network_200, and DN (Data Network)_250. In this case, the access network between UE_10 and the core network_200 can be composed of parts of access network_102, core network_202, and DN (Data Network)_252. This access network can be a 3GPP access network or a non-3GPP access network, but a non-3GPP access network is preferred.

[0037] also, Figure 4 It describes the device / network functions of UE_10, base station device_112, AMF_210, AMF_212, SMF_220, SMF_222, UPF_230, UPF_232, N3IWF_240, DN_250, DN_252, etc., as well as the interfaces for interconnecting these device / network functions.

[0038] It should be noted that the 5GS (5G System) of a 5G system consists of a UE, an access network, and a core network, but may further include a DN.

[0039] A UE is a device capable of connecting to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (also known as non-3GPP access network, non-3GPP AN). Furthermore, a UE can be a mobile phone, smartphone, or other terminal device capable of wireless communication, or a terminal device capable of connecting to EPS (Evolved Packet System) and 5GS as 4G systems. Additionally, a UE can possess a UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that a UE can be presented as a user equipment or a terminal device.

[0040] In addition, the access network can also be called the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access network (non-3GPP AN).

[0041] In NG-RAN, one or more base station devices are configured. These base station devices can be gNBs. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is connected to the 5GC via an NG interface (including the N2 or N3 interface). That is, a gNB is a base station device newly designed for 5GS, with different functions than the base station devices (eNBs) used in EPS. Furthermore, in the case of multiple gNBs, they are interconnected, for example, via an Xn interface. It should be noted that base station device_110 and base station device_112 correspond to gNBs.

[0042] Furthermore, NG-RAN will be referred to as 3GPP access in the following text. Non-3GPP AN will be referred to as non-3GPP access. Nodes configured in the access network will also be collectively referred to as NG-RAN nodes.

[0043] In addition, the devices included in the access network and / or the devices included in the access network are sometimes referred to as access network devices.

[0044] It should be noted that Access Network_100 and Access Network_102 correspond to 3GPP access.

[0045] In addition, base station device 110 is configured in access network 100, and base station device 112 is configured in access network 102.

[0046] also, Figure 4 The N3IWF is used for untrusted non-3GPP access scenarios.

[0047] Furthermore, the core network corresponds to 5GC (5G Core Network). Within 5GC, for example, AMF, UPF, SMF, PCF, etc., are configured. Here, 5GC can also be represented as 5GCN.

[0048] In addition, the N3IWF can be configured in the access network_102 or the core network_200, but ideally it should be configured in the core network.

[0049] In addition, the core network and / or the devices included in the core network are sometimes referred to as core network devices.

[0050] The core network can be an IP mobile communication network operated by a Mobile Network Operator (MNO) that connects the access network and the DN; it can also be the core network of a mobile communication operator used to operate and manage mobile communication systems; or it can be the core network of virtual mobile communication operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).

[0051] Furthermore, a DN can also be a DN that provides communication services to the UE. Additionally, a DN can be configured as a packet data service network, or it can be configured for each service. Moreover, a DN can include connected communication terminals. Therefore, connecting to a DN can be connecting to a communication terminal or server device configured on the DN. Furthermore, sending and receiving user data with a DN can be sending and receiving user data with a communication terminal or server device configured on the DN.

[0052] Furthermore, hereinafter, at least a portion of the access network, core network, and DN, and / or more than one of these devices, may be referred to as a network or network device. That is to say, the sending and receiving of messages and / or the execution of processes by a network and / or network device can refer to the sending and receiving of messages and / or the execution of processes by at least a portion of the access network, core network, and DN, and / or more than one of these devices.

[0053] Furthermore, the UE can connect to the access network. Additionally, the UE can connect to the core network via the access network. Moreover, the UE can connect to the DN via both the access network and the core network. That is, the UE can send and receive user data with the DN. Furthermore, when sending and receiving user data, the UE can use not only IP (Internet Protocol) communication but also non-IP communication.

[0054] Here, IP communication refers to data communication using IP, which involves sending and receiving data via IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted or received by devices / functions included in the EPS and devices / functions included in the 5GS.

[0055] Furthermore, non-IP communication refers to data communication that does not use IP, but rather transmits and receives data through a structure different from IP packets. For example, non-IP communication can be achieved by transmitting and receiving application data without IP headers, or it can transmit and receive user data sent and received by the UE using other headers such as MAC headers and Ethernet (registered trademark) frame headers.

[0056] [2. Composition of each device]

[0057] Next, the configuration of the various devices (UE and / or access network device and / or core network device) used in each embodiment will be described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware built on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions possessed by each device can also be configured as physical hardware, logical hardware, or software.

[0058] It should be noted that the storage units (storage unit_340, storage unit_440, storage unit_540) within the various devices and functions mentioned below are composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. Furthermore, each storage unit can store not only the information originally set at the factory, but also various information exchanged between the device itself and other devices / functions (e.g., UE and / or access network devices and / or core network devices and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc., included in the control messages exchanged during the various communication processes described later. Furthermore, each storage unit can store this information in each UE.

[0059] [2.1. UE Device Configuration]

[0060] First, use Figure 5 An example of the device configuration of a UE (User Equipment) will be described. The UE consists of a control unit_300, an antenna_310, a transceiver unit_320, and a storage unit_340. The control unit_300, transceiver unit_320, and storage unit_340 are connected via a bus. The transceiver unit_320 is connected to the antenna_310.

[0061] The control unit 300 is a functional unit that controls the overall operation and functions of the UE. It should be noted that the control unit 300 can also handle functions not possessed by other functional units in the UE (transceiver unit 320, storage unit 340). The control unit 300 reads and executes various programs stored in the storage unit 340 as needed, thereby implementing various processes within the UE.

[0062] The transceiver unit 320 is a functional unit used for wireless communication with base station devices and the like within the access network via the antenna 310. That is, the UE can use the transceiver unit 320 to send and receive user data and / or control information with access network devices and / or core network devices and / or PDN and / or DN.

[0063] Furthermore, the UE can communicate with the base station device (gNB) within the 5G AN by using the transceiver unit_320. Additionally, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit_320.

[0064] Storage unit 340 is a functional unit used to store programs, user data, control information, etc., required for various actions of the UE. Furthermore, storage unit 340 may also have the function of storing control information transmitted and received between the UE and the access network device, core network device, and DN.

[0065] [2.2.gNB (Base Station Device_110, Base Station Device_112) Device Configuration]

[0066] Next, use Figure 6 An example of the gNB device configuration will be described. The gNB consists of a control unit_500, an antenna_510, a network connection unit_520, a transceiver unit_530, and a storage unit_540. The control unit_500, network connection unit_520, transceiver unit_530, and storage unit_540 are connected via a bus. The transceiver unit_530 is connected to the antenna_510.

[0067] The control unit 500 is a functional unit that controls the overall operation and functions of the gNB. It should be noted that the control unit 500 can also handle functions not possessed by other functional units in the base station device 110 (network connection unit 520, transceiver unit 530, and storage unit 540). The control unit 500 reads and executes various programs stored in the storage unit 540 as needed, thereby implementing various processes within the gNB.

[0068] The network connection unit 520 is a functional unit for enabling communication between the gNB and the AMF and / or UPF. That is, the gNB can use the network connection unit 520 to send and receive user data and / or control information with the AMF and / or UPF.

[0069] The transceiver unit 530 is a functional unit used for wireless communication with the UE via the antenna 510. That is, the gNB can use the transceiver unit 530 to send and receive user data and / or control information with the UE.

[0070] The gNB, located in the 5G AN, can communicate with the AMF via the N2 interface and with the UPF via the N3 interface using the network connection unit_520. Furthermore, the gNB can communicate with the UE using the transceiver unit_530.

[0071] Storage unit 540 is a functional unit used to store programs, user data, control information, etc., required for various operations of the gNB. Furthermore, storage unit 540 may also have the function of storing control information transmitted and received between the UE, other access network devices (base station devices), core network devices, and DN. [2.3. Device configuration of AMF (AMF_210, AMF_212)]

[0072] Next, use Figure 7 An example of the AMF's device configuration will be described. The AMF consists of a control unit_700, a network connection unit_720, and a storage unit_740. The control unit_700, network connection unit_720, and storage unit_740 are connected via a bus. The AMF can be a node in the processing control plane (also known as the C-plane).

[0073] The control unit 700 is a functional unit that controls the overall operation and functions of the AMF. It should be noted that the control unit 700 can also handle functions that other functional units in the AMF (network connection unit 720, storage unit 740) do not possess. The control unit 700 reads and executes various programs stored in the storage unit 740 as needed, thereby realizing various processes within the AMF.

[0074] The network connection unit 720 is a functional unit for connecting the AMF to base station devices and / or N3IWF and / or other AMFs and / or SMFs and / or PCFs and / or NSSFs (Network Slice Selection Functions) and / or UDMs (Unified Data Management) and / or SCEFs. That is, the AMF can use the network connection unit 720 to send and receive user data and / or control information between itself and base station devices and / or N3IWFs and / or other AMFs and / or SMFs and / or PCFs and / or NSSFs and / or UDMs and / or SCEFs.

[0075] Within the 5GCN, the AMF (Advanced Feature Module) can communicate with base station devices or N3IWFs via the N2 interface using the network connection unit_720, communicate with other AMFs via the N14 interface, communicate with the SMF (Supervisor Module) via the N11 interface, communicate with the PCF (Public Module Module) via the N15 interface, communicate with the NSSF (Nanjing Service Module SF) via the N22 interface, and communicate with the UDM (User Device Module) via the N8 interface. Furthermore, the AMF can send and receive NAS messages with the UE (User Equipment) via the N1 interface using the network connection unit_720. However, the N1 interface is a logical interface; therefore, communication between the UE and the AMF is actually conducted via the 5G AN (Anti-Network Module).

[0076] Storage unit 740 is a functional unit used to store programs, user data, control information, etc., required for various operations of the AMF. Furthermore, storage unit 740 may also have the function of storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0077] It should be noted that the AMF has the following functions: 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; performing registration management (RM) functions; connection management (CM) functions; reachability management functions; mobility management functions for UEs, etc.; transmitting SM (Session Management) messages between the UE and the SMF; access authentication (Access Authorization) functions; security anchor function (SEA); security context management (SCM); supporting the N2 interface for N3IWF (Non-3GPP Interworking Function); supporting the transmission and reception of NAS signals with the UE via N3IWF; and authenticating UEs connected via N3IWF.

[0078] Furthermore, the RM state of each UE is managed within the login management system. The RM state can be synchronized between the UE and the AMF (Application Management Frame). There are two RM states: a non-login state (RM-DEREGISTERED state) and a login state (RM-REGISTERED state). In the non-login state, the UE is not logged into the network; therefore, the UE context in the AMF does not have valid location or routing information for that UE, so the AMF is in a state where it cannot reach the UE. Conversely, in the login state, the UE is logged into the network; therefore, the UE can receive services that require network login. It should be noted that the RM state can also be represented as a 5GMM state. In this case, the non-login state can also be represented as a 5GMM-DEREGISTERED state, and the login state can also be represented as a 5GMM-REGISTERED state.

[0079] In other words, 5GMM-REGISTERED can refer to either the state where each device has established a 5GMM context or the state where a PDU session context has been established. It should be noted that when each device is 5GMM-REGISTERED, UE_10 can begin sending and receiving user data and control messages, and can also respond to paging. Furthermore, it should be noted that when each device is 5GMM-REGISTERED, UE_10 can perform login procedures and / or service request procedures other than the login procedure used for initial login.

[0080] Furthermore, 5GMM-DEREGISTERED can mean several things: the devices have not established a 5GMM context, the UE_10's location information has not been obtained by the network, or the network cannot reach the UE_10. It should be noted that when all devices are 5GMM-DEREGISTERED, the UE_10 can begin the login process or establish a 5GMM context by executing the login process.

[0081] Furthermore, the CM state of each UE is managed within the connection management system. The CM state can be synchronized between the UE and the AMF. There are two CM states: an IDLE state and a CONNECTED state. In the IDLE state, the UE is logged in but does not have a NAS signaling connection established with the AMF via the N1 interface. Additionally, in the IDLE state, the UE does not have an N2 connection or an N3 connection. On the other hand, in the CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. Furthermore, in the CONNECTED state, the UE can also have an N2 connection and / or an N3 connection.

[0082] Furthermore, connection management can be divided into CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access can exist as both an IDLE state and a CONNECTED state. Similarly, the CM states in non-3GPP access can also exist as both an IDLE state and a CONNECTED state. It should be noted that the IDLE state can manifest as an idle mode, and the CONNECTED state can manifest as a connected mode.

[0083] It should be noted that the CM state can also manifest as 5GMM mode. In this case, the non-connected state can also manifest as 5GMM-IDLE mode, and the connected state can also manifest as 5GMM-CONNECTED mode. Furthermore, the non-connected state in 3GPP access can also manifest as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access can also manifest as 5GMM-CONNECTED mode over 3GPP access. Similarly, the non-connected state in non-3GPP access can also manifest as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access can also manifest as 5GMM-CONNECTED mode over non-3GPP access. It should be noted that 5GMM non-connected mode can be represented as idle mode, and 5GMM connected mode can be represented as connected mode.

[0084] Furthermore, more than one AMF can be configured within the core network. Additionally, an AMF can be an NF (Network Function) that manages more than one NSI (Network Slice Instance). Furthermore, an AMF can also be a shared CP function (CCNF; Common CPNF, Control Plane Network Function) shared among multiple NSIs.

[0085] It should be noted that N3IWF is a device and / or function configured between the non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access. Ideally, N3IWF is configured in the core network.

[0086] [2.4. SMF Device Configuration]

[0087] Next, use Figure 7 An example of the device configuration of an SMF will be described. The SMF consists of a control unit_700, a network connection unit_720, and a storage unit_740. The control unit_700, network connection unit_720, and storage unit_740 are connected via a bus. The SMF can be a node that processes the control plane.

[0088] The control unit 700 is a functional unit that controls the overall operation and functions of the SMF. It should be noted that the control unit 700 can also handle functions not possessed by other functional units in the SMF (network connection unit 720, storage unit 740). The control unit 700 reads and executes various programs stored in the storage unit 740 as needed, thereby realizing various processes within the SMF.

[0089] The network connection unit 720 is a functional unit for enabling the SMF to connect with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit 720 to send and receive user data and / or control information with the AMF and / or UPF and / or PCF and / or UDM.

[0090] The SMF located within the 5GCN can communicate with the AMF via the N11 interface, with the UPF via the N4 interface, with the PCF via the N7 interface, and with the UDM via the N10 interface by using the network connection unit _720.

[0091] Storage unit 740 is a functional unit used to store programs, user data, control information, etc., required for various operations of the SMF. Furthermore, storage unit 740 may also have the function of storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0092] The SMF has the following functions: session management functions such as establishing, modifying, and releasing PDU sessions; IP address allocation and management functions for UEs; UPF selection and control functions; UPF configuration functions for routing services to the appropriate destination (sending destination); SM part functions for sending and receiving NAS messages; Downlink Data Notification functions; AN-specific (each AN's) SM information sent to the AN via the N2 interface through the AMF; SSC (Session and Service Continuity mode) functions for sessions; and roaming functions, etc.

[0093] [2.5. UPF Device Configuration]

[0094] Next, use Figure 7 An example of the UPF device configuration will be described. The UPF consists of a control unit_700, a network connection unit_720, and a storage unit_740. The control unit_700, network connection unit_720, and storage unit_740 are connected via a bus. The UPF can be a node that processes the control plane.

[0095] The control unit 700 is a functional unit that controls the overall operation and functions of the UPF. It should be noted that the control unit 700 can also handle functions not possessed by other functional units in the AMF (network connection unit 720, storage unit 740). The control unit 700 reads and executes various programs stored in the storage unit 740 as needed, thereby realizing various processes within the UPF.

[0096] The network connection unit 720 is a functional unit for connecting the UPF to the base station device (gNB) and / or SMF and / or DN within the 5G AN. That is, the UPF can use the network connection unit 720 to send and receive user data and / or control information between itself and the base station device and / or N3IWF and / or SMF and / or DN and / or other UPFs.

[0097] The UPF located within the 5GCN can communicate with the base station device or N3IWF via the N3 interface, communicate with the SMF via the N4 interface, communicate with the DN via the N6 interface, and communicate with other UPFs via the N9 interface by using the network connection unit_620.

[0098] Storage unit 740 is a functional unit used to store programs, user data, control information, etc., required for various operations of the UPF. Furthermore, storage unit 740 may also have the function of storing control information transmitted and received between the UE, access network device, other core network device, and DN.

[0099] UPF has the following functions: serving as an anchor point for intra-RAT mobility or inter-RAT mobility; serving as an external PDU session point for interconnection with the DN (that is, serving as a gateway for transmitting user data between the DN and the core network); packet routing and transmission; UL CL (Uplink Classifier) ​​function for routing multiple service flows to a DN; branching point function for supporting multi-homed PDU sessions; QoS (Quality of Service) processing for the user plane; uplink service verification function; buffering function for triggering downlink packets; and downlink data notification function.

[0100] Furthermore, a UPF can be a gateway for IP and / or non-IP communication. Additionally, a UPF can be capable of transmitting IP communication or converting between non-IP and IP communication. Moreover, multiple configured gateways can connect the core network and a single DN. It should be noted that a UPF can have connectivity with other NFs and can also connect to various devices via other NFs.

[0101] It should be noted that the user plane refers to user data transmitted and received between the UE and the network. The user plane can use PDN connections or PDU sessions for transmission and reception. Furthermore, in the case of EPS, the user plane can also use 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 for transmission and reception. Moreover, in the case of 5GS, the user plane can also be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. The user plane can also be represented as a U-Plane.

[0102] Furthermore, the control plane is responsible for sending and receiving control messages for UE communication control, etc. The control plane can use the NAS (Non-Access-Stratum) signaling connection between the UE and the MME for sending and receiving. Moreover, in the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for sending and receiving. Furthermore, in the case of 5GS, the control plane can also use the interface between the UE and the NG RAN and the N2 interface for sending and receiving. The control plane can also be represented as a Control Plane or a C-Plane.

[0103] Furthermore, the user plane (UP) can be a communication path for sending and receiving user data, and can be composed of multiple bearers. Similarly, the control plane (CP) can be a communication path for sending and receiving control messages, and can be composed of multiple bearers. [2.6. Description of other devices and / or functions and identification information of this embodiment]

[0104] Next, other devices and / or functions, as well as identification information, will be described.

[0105] A network refers to at least one of an access network, core network, and DN. Alternatively, it can refer to one or more devices included in at least one of the access network, core network, and DN as a network or network device. That is, the network performing message sending, receiving, and / or processing can mean that devices within the network (network devices and / or control devices) perform message sending, receiving, and / or processing. Conversely, the devices within the network performing message sending, receiving, and / or processing can mean that the network itself performs message sending, receiving, and / or processing.

[0106] In addition, NSSF (Network Slice Selection Function) can refer to a network function (also known as NF) that has the ability to select the network slice serving the UE.

[0107] In addition, NWDAF (Network Data Analytics Function) can refer to an NF that has the ability to collect data based on NF and application functions (also known as AF).

[0108] In addition, PCF (Policy Control Function) can refer to an NF that has the function of determining policies for controlling the behavior of the network.

[0109] Furthermore, an NRF (Network Repository Function) can refer to an NF that has service discovery capabilities. An NRF can be an NF that provides information about a discovered NF when it receives a discovery request from another NF.

[0110] Furthermore, SM (Session Management) messages (also known as NAS (Non-Access-Stratum) SM messages) can be NAS messages used during SM operations, or control messages exchanged between the UE and SMF via the AMF. Moreover, SM messages can include: PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, PDU session modification request messages, PDU session modification command messages, PDU session modification complete messages, PDU session modification command reject messages, PDU session modification reject messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, and PDU session release complete messages, etc.

[0111] In addition, the procedures used in SM or within SM procedures may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each procedure can be initiated by the UE or by the NW.

[0112] Furthermore, MM (Mobility Management) messages (also known as NAS MM messages) can be NAS messages used in MM procedures, or control messages exchanged between UE10 and AMF. Moreover, MM messages can include: Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages, De-registration accept messages, Configuration update command messages, Configuration update complete messages, Service request messages, Service accept messages, Service reject messages, Notification messages, and Notification response messages, etc.

[0113] In addition, the MM process or MM procedure may include: registration procedure, de-registration procedure, generic UE configuration update procedure, authentication / authorization procedure, service request procedure, paging procedure, and notification procedure.

[0114] Furthermore, 5GS (5G System) service can be a connectivity service provided by the core network. Moreover, 5GS service can be a different service from EPS service, or it can be the same service as EPS service.

[0115] In addition, non-5GS services can be services other than 5GS services, and can also include EPS services and / or non-EPS services.

[0116] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, which can be IPv4, IPv6, IPv4v6, or non-IP. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying IPv4v6 indicates that either IPv4 or IPv6 is used for data transmission and reception. Specifying non-IP indicates that communication is conducted not only through IP but also through communication methods other than IP.

[0117] Furthermore, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the association between the DN providing PDU connectivity services and the UE, but it can also be a connection established between the UE and an external gateway. The UE can use the PDU session to send and receive user data with the DN by establishing a PDU session in the 5GS via the access network and core network. Here, the external gateway can refer to UPF, SCEF, etc. The UE can use the PDU session to perform the sending and receiving of user data with devices such as application servers configured on the DN.

[0118] It should be noted that each device (UE and / or access network device and / or core network device) can manage the establishment of more than one identification information corresponding to a PDU session. This identification information can include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, and access network identification information, and may further include other information. Furthermore, when multiple PDU sessions are established, the identification information corresponding to each PDU session can be the same or different.

[0119] Furthermore, the DNN (Data Network Name) can be identification information for identifying the core network and / or external networks such as DN. Moreover, the DNN can also be used to select gateways such as PGW_30 / UPF_235 that connect to the core network B190. Additionally, the DNN can be equivalent to the APN (Access Point Name).

[0120] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which can be IPv4, IPv6, Ethernet, or Unstructured. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying Ethernet indicates that Ethernet frames are transmitted and received. Additionally, Ethernet can indicate that communication does not use IP. Specifying Unstructured indicates that point-to-point (P2P) tunneling technology is used to send and receive data to and from application servers, etc., located in the DN. For example, UDP / IP encapsulation technology can be used as a P2P tunneling technology. It should be noted that IP can be included among the above-mentioned other PDU session types. IP can be specified if the UE can use both IPv4 and IPv6.

[0121] Furthermore, a PLMN (Public Land Mobile Network) is a communication network that provides mobile wireless communication services. A PLMN is a network managed by an operator, and the operator can be identified through its PLMN ID. A PLMN whose MCC (Mobile Country Code) and MNC (Mobile Network Code) match the UE's IMSI (International Mobile Subscriber Identity) can be a Home PLMN (HPLMN). Moreover, the UE can maintain a list of equivalent HPLMNs in its USIM to identify one or more EPLMNs. A PLMN different from an HPLMN and / or EPLMN can be a Visited PLMN (VPLMN). The PLMN that the UE successfully logs into can be an RPLMN (Registered PLMN).

[0122] Furthermore, SNPN is a type of 5GS NPN deployed for non-public use. It operates through the NPN operator and does not rely on the NF provided by the PLMN. SNPN can be identified by a combination of PLMN ID and NID. UEs capable of using SNPN can support SNPN access mode. UEs configured to operate in SNPN access mode can choose to log in to SNPN or not. UEs configured to operate in SNPN access mode can perform the SNPN selection process or not. Even if a UE can use SNPN (SNPN enabled), UEs not configured to operate in SNPN access mode can log in to SNPN or choose the PLMN. UEs not configured to operate in SNPN access mode can skip the SNPN selection process or perform the normal PLMN selection process.

[0123] It should be noted that SNPN access modes can be applied at the access unit level. That is, they can be managed separately by 3GPP access and non-3GPP access. In other words, activating or disabling SNPN access modes for 3GPP access can be independent of activating or disabling SNPN access modes for non-3GPP access. That is, if SNPN access modes for 3GPP access are activated, SNPN access modes for non-3GPP access can also be activated or disabled. Furthermore, if SNPN access modes for 3GPP access are disabled, SNPN access modes for non-3GPP access can also be activated or disabled.

[0124] Furthermore, when the SNPN access mode is not applied on an access unit basis, the SNPN access mode connected to the SNPN via the PLMN can be defined as a new SNPN access mode (e.g., SNPN access mode via the PLMN).

[0125] Furthermore, a network slice (NS) refers to a logical network that provides specific network capabilities and characteristics. The UE and / or network can support network slices (NW slices; NS) in 5GS. Sometimes, network slices are simply referred to as slices.

[0126] Furthermore, a Network Slice Instance (NSI) refers to a network slice that is formed and configured by a collection of instances (entities) of Network Functions (NFs) and the required resources. Here, NF refers to a processing function in the network, adopted or defined in 3GPP. An NSI is an entity that constitutes more than one NS within the core network. Additionally, an NSI can be composed of virtual NFs (Network Functions) generated using an NST (Network Slice Template). Here, an NST is a logical expression of more than one NF associated with a resource request for providing the requested communication service or capability. That is, an NSI can be a collection within the core network composed of multiple NFs. Furthermore, an NSI can be a logical network configured to divide transmitted user data according to services, etc. An NS can contain more than one NF. NFs constituting an NS can be devices shared with other NSs or devices not shared with other NSs. A UE and / or devices within the network can be assigned to more than one NS based on login information such as NSSAI and / or S-NSSAI and / or UE usage type and / or more than one NSI ID and / or APN. It should be noted that the UE usage type is a parameter value included in the login information used to identify the UE's NSI. The UE usage type can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usage type.

[0127] Furthermore, S-NSSAI (Single Network Slice Selection Assistance information) is information used to identify the NS. S-NSSAI can consist solely of SST (Slice / Service type), or it can be composed of both SST and SD (Slice Differentiator). Here, SST refers to information indicating the expected actions of the NS in terms of function and service. SD can be information that interpolates the SST when selecting an NSI from multiple NSIs shown by the SST. S-NSSAI can be information specific to each PLMN, or it can be standard information common to all PLMNs. Additionally, the network can store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, the network can provide UE-related NSs even if the UE does not send a valid S-NSSAI to the network in the login request message.

[0128] Furthermore, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAIs. Each S-NSSAI included in the NSSAI is information for assisting the access network or core network in selecting the NSI. The UE can store NSSAIs allowed by the network on a per PLMN basis. In addition, NSSAIs can also be information used for selecting the AMF.

[0129] Furthermore, the configured NSSAI (also known as the set NSSAI) is the NSSAI supplied to the UE for storage. The UE can store the set NSSAI for each PLMN. The set NSSAI can be information configured by the network (or PLMN). The S-NSSAI included in the set NSSAI can also be represented as the set S-NSSAI (configured S-NSSAI). The set S-NSSAI can be configured to include both the S-NSSAI and the mapped S-NSSAI.

[0130] Furthermore, the requested NSSAI (also known as the Requested NSSAI) is the NSSAI provided by the UE to the network during the login process. The requested NSSAI can be an allowed NSSAI stored by the UE or a configured NSSAI. Specifically, the requested NSSAI can be information indicating the network slice the UE wants to access. The S-NSSAI included in the requested NSSAI can also be represented as a requested S-NSSAI. For example, the requested NSSAI may be sent within an RRC (Radio Resource Control) message, which includes NAS messages or NAS (Non-Access-Stratum) messages sent from the UE to the network, such as login request messages or PDU session establishment request messages.

[0131] Furthermore, allowed NSSAI (also known as permitted NSSAI) indicates information about one or more network slices that the UE is permitted to connect to. In other words, allowed NSSAI identifies network slices that allow the network to connect to the UE. The UE and the network store and manage allowed NSSAI for each type of access (3GPP access or non-3GPP access) as UE information. S-NSSAI included in allowed NSSAI can also be represented as allowed S-NSSAI. Allowed S-NSSAI can be configured to include both S-NSSAI and mapped S-NSSAI.

[0132] Furthermore, mapped S-NSSAI (also known as mapped S-NSSAI) is the HPLMN's S-NSSAI mapped to the S-NSSAI of the logged-in PLMN in roaming scenarios. The UE can store one or more mapped S-NSSAIs that configure NSSAIs and map them to the S-NSSAIs included in the allowed NSSAIs for each access type. Moreover, the UE can store one or more mapped S-NSSAIs that include the S-NSSAIs included in rejected NSSAIs.

[0133] Furthermore, a rejected NSSAI (also known as a denied NSSAI) indicates that one or more network slices are not permitted for the UE. In other words, a rejected NSSAI identifies network slices that are not allowed for network connection to the UE. A rejected NSSAI can be a combination of one or more S-NSSAIs and a rejection reason value. Here, the rejection reason value refers to the information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network can appropriately store and manage rejected NSSAIs based on the corresponding rejection reason values ​​established for each S-NSSAI. Moreover, rejected NSSAIs can also be included in NAS messages sent from the network to the UE, such as login acceptance messages, configuration update commands, login rejection messages, or RRC messages that include NAS messages. The S-NSSAIs included in a rejected NSSAI can also be represented as rejected S-NSSAIs. A rejected NSSAI can be any one of the first to third rejected NSSAIs and pending NSSAIs, or a combination of these. The rejection of S-NSSAI included in NSSAI can also be expressed as a rejection of S-NSSAI. Rejection of S-NSSAI can be constituted as including S-NSSAI and mapping S-NSSAI.

[0134] Here, the first rejection NSSAI is a set of more than one S-NSSAI that is unavailable in the current PLMN, included in the S-NSSAI requested by the UE as part of the NSSAI request. The first rejection NSSAI can be a rejected NSSAI for the current PLMN in the 5GS, a rejected S-NSSAI for the current PLMN, or an S-NSSAI included in the rejected NSSAI for the current PLMN. The first rejection NSSAI can be a rejection NSSAI stored by the UE or NW, or a rejection NSSAI sent from the NW to the UE. In the case where the first rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the first rejection NSSAI can be information including a combination of one or more S-NSSAIs and a reason value. The rejection reason value at this time can be "S-NSSAI is not available in the current PLMN", or it can be a message indicating that S-NSSAI is not available in the current PLMN.

[0135] Furthermore, the First Denial NSSAI is valid throughout the PLMN login process. In other words, the UE and / or NW can treat the First Denial NSSAI and the S-NSSAI included in it as access type-independent information. That is, the First Denial NSSAI can be information valid for both 3GPP access and non-3GPP access.

[0136] The UE can delete the first rejection NSSAI from storage when it transitions to a non-login state for the current PLMN via both 3GPP and non-3GPP access. In other words, the UE deletes the first rejection NSSAI when it transitions to a non-login state for the current PLMN via one access, or when it successfully logs into a new PLMN via another access, or when it fails to log into a new PLMN via another access and transitions into a non-login state, and when the UE is in a state of not logging in via the other access (non-login state).

[0137] Furthermore, the second rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current registration area, included in the S-NSSAI request by the UE. The second rejected NSSAI can be a rejected NSSAI for the current registration area from the 5GS. The second rejected NSSAI can be a rejected NSSAI stored by the UE or NW, or a rejected NSSAI sent from the NW to the UE. When the second rejected NSSAI is sent from the NW to the UE, it can be information including a combination of one or more S-NSSAIs and a reason value. The reason value can be "S-NSSAI is not available in the current registration area," or it can be information indicating that the S-NSSAI corresponding to the reason value is unavailable in the current registration area.

[0138] Furthermore, the second rejection NSSAI is valid within the current login area. That is, the UE and / or NW can treat the second rejection NSSAI and the S-NSSAI included in it as information for each access type. In other words, the second rejection NSSAI can be information valid for either 3GPP access or non-3GPP access respectively. Also, the UE can delete the second rejection NSSAI from storage once it transitions to a non-login state for a certain access type.

[0139] Furthermore, the third rejection NSSAI is an S-NSSAI that requires an NSSAA, and is a set of one or more S-NSSAIs for which an NSSAA has failed or been cancelled. The third rejection NSSAI can be an NSSAI stored by the UE and / or the NW, or it can be sent from the NW to the UE. When a third rejection NSSAI is sent from the NW to the UE, it can be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value can be "S-NSSAI is not available due to the failed or revoked network slice-specific authorization and authentication," or it can be information indicating that an NSSAA has failed or been cancelled for an S-NSSAI corresponding to the rejection reason value.

[0140] Furthermore, the Third Denial NSSAI is valid throughout the PLMN login process. In other words, the UE and / or NW can treat the Third Denial NSSAI and the S-NSSAI included within it as access type-independent information. That is, the Third Denial NSSAI can be valid for both 3GPP and non-3GPP access. The Third Denial NSSAI can be a different NSSAI from the Denial NSSAI. The Third Denial NSSAI can also be the First Denial NSSAI.

[0141] The third rejection NSSAI is a rejection NSSAI used by the UE to identify slices rejected by the core network due to NSSAA failure or cancellation. Specifically, while storing the third rejection NSSAI, the UE does not initiate a login request process for the S-NSSAI included in the third rejection NSSAI. The third rejection NSSAI may include identification information received from the core network that corresponds to one or more rejection reason values ​​indicating NSSAA failure. The third rejection NSSAI is access type-independent information. Specifically, when the UE stores the third rejection NSSAI, the UE may not attempt to send a login request message including the S-NSSAI included in the third rejection NSSAI to either 3GPP access or non-3GPP access parties. Alternatively, the UE may send a login request message including the S-NSSAI included in the third rejection NSSAI based on UE policy. Alternatively, the UE may delete the third rejection NSSAI based on UE policy and transition to a state where it can send a login request message including the S-NSSAI included in the third rejection NSSAI. In other words, if the UE sends a login request message that includes the S-NSSAI included in the third rejection NSSAI based on the UE policy, the UE can remove the S-NSSAI from the third rejection NSSAI.

[0142] Furthermore, pending NSSAI (also known as pending NSSAI) is a set of one or more S-NSSAIs that require network slice-specific authentication (NSSAA) and are unusable in the current PLMN without completing NSSSAA. Pending NSSAIs can be 5GS NSSAIs rejected due to NSSAA or pending NSSAIs. Pending NSSAIs can be NSSAIs stored by the UE or NW, or NSSAIs sent from the NW to the UE. It should be noted that pending NSSAIs are not limited to rejected NSSAIs and can also be NSSAIs different from rejected NSSAIs. When pending NSSAIs are sent from the NW to the UE, they can be information including a combination of one or more S-NSSAIs and rejection reason values. The reason for rejection at this time can be "S-NSSAI is pending for the S-NSSAI", or it can be a statement that the UE is prohibited or has its S-NSSAI established with the reason for rejection until the information for the S-NSSAI is completed.

[0143] Furthermore, the pending NSSAI is valid throughout the PLMN login process. In other words, the UE and / or NW can treat the S-NSSAI included in the third rejection NSSAI and the pending NSSAI as access type-independent information. That is, the pending NSSAI can be information valid for both 3GPP access and non-3GPP access. The pending NSSAI can be a different NSSAI from the rejection NSSAI. The pending NSSAI can also be the first rejection NSSAI.

[0144] Furthermore, a pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that the UE uses to identify the slice pending the process. Specifically, the UE does not initiate a login request process for the S-NSSAIs included in the pending NSSAI while storing the pending NSSAI. In other words, the UE does not use the S-NSSAIs included in the pending NSSAI during the login process until an NSSAA is completed for the S-NSSAIs included in the pending NSSAI. The pending NSSAI is identification information received from the core network that includes one or more S-NSSAIs corresponding to the pending rejection reason value used for the NSSAA. The pending NSSAI is access type-independent information. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send a login request message including the S-NSSAIs included in the pending NSSAI to either 3GPP access or non-3GPP access parties.

[0145] A tracking area is one or more ranges managed by the core network that can be represented as location information for UE_10. A tracking area can consist of multiple cells. Furthermore, a tracking area can be a range used for broadcasting control messages such as paging, or a range that UE_10 can move within without a handover process. Moreover, a tracking area can be a routing area or a location area, as long as it is the same as these areas. Hereinafter, the tracking area can also be referred to as a TA (Tracking Area). A tracking area can be identified by a TAI (Tracking Area Identifier) ​​composed of a TAC (Tracking Area Code) and a PLMN.

[0146] A registration area is a set of one or more Tracking Areas (TAs) assigned to a UE by the AMF. It's important to note that UE_10 should ideally be able to move without transmitting or receiving tracking area update signals while moving within one or more TAs included in the registration area. In other words, a registration area can be a group of information representing areas where UE_10 can move without performing a tracking area update process. Registration areas can be identified through a TAI list consisting of one or more TAIs.

[0147] UE ID refers to information used to identify a UE. Specifically, for example, UE ID can be SUCI (Subscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, UE ID can be other information set within an application or network. Furthermore, UE ID can also be information used to identify a user.

[0148] Network Slice-Specific Authentication and Authorization (NSSAA) refers to the authentication and authorization functions specific to network slices. NSAA enables UE authentication and authorization outside the core network, such as with third parties. PLMNs and network devices with NSAA capabilities can execute the NSAA procedure for a specific S-NSSAI based on the UE's login information. Furthermore, UEs with NSAA capabilities can manage and store pending NSSAI rejections and / or failed NSSAI rejections for NSAA purposes. In this document, NSAA is sometimes referred to as the network slice-specific authentication and authorization process, or simply the authentication and authorization process.

[0149] S-NSSAI requiring NSAAA is an S-NSSAI that is managed by the core network and / or core network devices. The core network and / or core network devices can store S-NSSAI requiring NSAAA by establishing a correspondence between information indicating whether S-NSSAI is required and NSAAA is required. The core network and / or core network devices can also store S-NSSAI requiring NSAAA by establishing a correspondence between information indicating whether NSAAA has been completed or information indicating the status of NSAAA being allowed or successfully completed. The core network and / or core network devices can manage S-NSSAI requiring NSAAA as information independent of the access network.

[0150] Next, in this embodiment, the identification information transmitted, received, stored, and managed by each device will be described.

[0151] First, the primary identification information is UE capability information. This primary identification information can be 5GMM capability. Additionally, the primary identification information can indicate whether the UE supports a certain function. Furthermore, the primary identification information can also indicate whether the UE supports handover between SNPN and PLMN.

[0152] Furthermore, the second identification information is a requested NSSAI. The second identification information can consist of one or more requested S-NSSAIs. Additionally, the second identification information can represent an S-NSSAI that can connect to the SPN. Furthermore, the second identification information can also represent an S-NSSAI that can connect to the SNPN via the PLMN.

[0153] In addition, the third identification information is the type of login requested. The third identification information can be the 5GS registration type. Furthermore, the third identification information can also indicate initial registration, mobile registration updating, periodic registration updating, emergency registration, or login to the SNPN via the PLMN.

[0154] Furthermore, the fourth identification information includes at least two of the first to third identification information.

[0155] Furthermore, the eleventh identification information is network capability information. The eleventh identification information can be 5GS network feature support. Additionally, the eleventh identification information can indicate whether the network supports a certain function. Furthermore, the eleventh identification information can also indicate whether the network supports handover between SNPN and PLMN.

[0156] In addition, the twelfth identification information is Allowed NSSAI. The twelfth identification information can consist of more than one S-NSSAI.

[0157] In addition, the thirteenth identification information is the rejected NSSAI. The thirteenth identification information can consist of more than one S-NSSAI.

[0158] In addition, the fourteenth identification information is the configured NSSAI. The fourteenth identification information can consist of more than one S-NSSAI.

[0159] In addition, the fifteenth identification information is the Pending NSSAI. The fifteenth identification information can consist of more than one S-NSSAI.

[0160] Furthermore, the sixteenth identification information is identification information that includes at least two of the eleventh to fifteenth identification information.

[0161] Furthermore, the twenty-first identification information is the PDU session ID that identifies the PDU session. Alternatively, the twenty-first identification information may be the PDU session ID that identifies the PDU session to be established.

[0162] Furthermore, the twenty-second identification information is the PDU session type, which identifies the type of PDU session. Additionally, the twenty-second identification information can be the PDU session type requested by the UE for the PDU session. Furthermore, the twenty-second identification information can represent any of IPv4, IPv6, IPv4v6, Unstructured, or Ethernet (registered trademark).

[0163] Furthermore, the twenty-third identification information is SSC mode. Additionally, the twenty-third identification information can be an SSC mode requested by the UE for a PDU session. Furthermore, the twenty-third identification information can represent any of SSC mode 1, SSC mode 2, or SSC mode 3.

[0164] In addition, the twenty-fourth identification information is UE capability information. The twenty-fourth identification information can be 5GSM capability. Furthermore, the twenty-fourth identification information can indicate whether the UE supports a certain function. Additionally, the twenty-fourth identification information can indicate whether the UE supports the function of establishing a PDU session for the SNPN via the PLMN, or whether the UE supports handover between the SNPN and the PLMN.

[0165] Furthermore, the 25th identification information is one or more S-NSSAIs. Additionally, the 25th identification information can be one or more S-NSSAIs requested by the UE for the established PDU session. Furthermore, the 25th identification information can be one or more S-NSSAIs selected from the allowed NSSAIs for the current access type. Specifically, the 25th identification information, as an allowed NSSAI included in the Registration Accept message during the registration procedure, can be one or more S-NSSAIs allowed by the network for at least one party's access (3GPP access or non-3GPP access).

[0166] Furthermore, the twenty-sixth identification information is the DNN. Alternatively, the twenty-sixth identification information can also be the DNN that identifies the DN of the connection destination for the PDU session requested by the UE.

[0167] Furthermore, the twenty-seventh identification information is the PDU session ID that identifies the PDU session. Additionally, the twenty-seventh identification information can be the PDU session ID that identifies an already established PDU session. For example, the twenty-seventh identification information can be the PDU session ID used to identify a PDU session accessed via 3GPP when such a PDU session has already been established. Furthermore, the twenty-seventh identification information can also be the PDU session ID used to identify a PDU session accessed via non-3GPP when such a PDU session has already been established. Moreover, the twenty-seventh identification information can be the PDU session ID that identifies a PDU session established in the SNPN, the PDU session ID that identifies a PDU session established in the PLMN, or the PDU session ID that identifies a PDU session established in the SNPN via the PLMN.

[0168] Furthermore, the twenty-eighth identification information is identification information that includes at least two of the twenty-first to twenty-seventh identification information.

[0169] In addition, the thirty-first identification information is the PDU session ID that identifies the PDU session. It can also be the PDU session ID that identifies a PDU session that is allowed to be established by the network.

[0170] Furthermore, the 32nd identification information is the PDU session type, which identifies the type of PDU session. Additionally, the 32nd identification information can also be information indicating the PDU session type selected by the network. Furthermore, the 32nd identification information can represent any of IPv4, IPv6, IPv4v6, unstructured, or Ethernet (registered trademark).

[0171] Furthermore, the thirty-third identification information is the SSC mode. Additionally, the thirty-third identification information can be the SSC mode selected by the network for the PDU session. Furthermore, the thirty-third identification information can represent any of SSC mode 1, SSC mode 2, or SSC mode 3.

[0172] Furthermore, the thirty-fourth identification information is network UE capability information. The thirty-fourth identification information can be 5GS network feature support (5GSM network feature support). Additionally, the thirty-fourth identification information can indicate whether the network supports a certain function. Furthermore, the thirty-fourth identification information can indicate whether the network supports the function of establishing a PDU session for the SNPN via the PLMN, or whether the network supports handover between the SNPN and the PLMN.

[0173] In addition, the 35th identification information is one or more S-NSSAI.

[0174] Furthermore, the thirty-sixth identification information is the DNN. Additionally, the thirty-sixth identification information can be the DNN that identifies the DN as the connection destination of the PDU session.

[0175] Furthermore, the thirty-seventh identification information is identification information that includes at least two of the thirty-first to thirty-sixth identification information.

[0176] Furthermore, the 41st identification information is of the de-registration type. The 41st identification information can be of the de-registration type. Additionally, the 41st identification information can indicate whether re-registration is required. Furthermore, regarding whether re-registration is required, the 41st identification information can indicate whether it is for 3GPP access, for non-3GPP access, or for both. It should be noted that the forty-first identification information indicates a re-login request. This can mean that a change from SNPN to PLMN is required, a redirection to SNPN via PLMN is required, SNPN is unavailable, direct access to SNPN is unavailable, SNPN is not allowed, direct access to SNPN is not allowed, access to SNPN via PLMN is allowed, or SNPN access mode is disabled.

[0177] In addition, the forty-first identification information indicates a re-login request, which can indicate a need to change from PLMN to SNPN, a need for redirection to SNPN, an inability to use SNPN via PLMN, an inability to access to SNPN via PLMN, an inability to allow access to SNPN via PLMN, an inability to allow direct access to SNPN, or activation of SNPN access mode.

[0178] Furthermore, the 42nd identification information is a cause value. The 42nd identification information can be a 5GMM cause. The 42nd identification information can indicate a need to change from SNPN to PLMN, a need to redirect to SNPN via PLMN (redirection to SNPN via PLMN required), an inability to use SNPN (SNPN not available), an inability to use direct access to SNPN (direct access to SNPN not available), an inability to use SNPN (SNPN not allowed), an inability to use direct access to SNPN (direct access to SNPN not allowed), an access to SNPN via PLMN allowed, or a disabled SNPN access mode.

[0179] In addition, the forty-second identification information can indicate a need to change from PLMN to SNPN, a need to redirect to SNPN (redirection to SNPN required), an inability to access to SNPN via PLMN (access to SNPN not available), an inability to access SNPN via PLMN (SNPN via PLMN not available), an inability to access SNPN via PLMN (access to SNPN not allowed), an inability to directly access SNPN (direct access to SNPN allowed), or the activation of SNPN access mode.

[0180] Furthermore, the forty-third identification information is identification information that includes at least two of the forty-first and forty-second identification information.

[0181] Furthermore, the 51st identification information is the type of de-registration. The 51st identification information can be a de-registration type. Furthermore, the 51st identification information can indicate whether it is a normal de-registration or a switch-off condition. Additionally, the 51st identification information can indicate whether the normal de-registration or switch-off condition applies to 3GPP access, non-3GPP access, or both.

[0182] Furthermore, the 52nd identification information is a cause value. The 52nd identification information can be a 5GMM cause. The 52nd identification information can indicate a need to change from SNPN to PLMN, a need to redirect to SNPN via PLMN (redirection to SNPN via PLMN required), an inability to use SNPN (SNPN not available), an inability to use direct access to SNPN (direct access to SNPN not available), an inability to use SNPN (SNPN not allowed), an inability to use direct access to SNPN (direct access to SNPN not allowed), an access to SNPN via PLMN allowed, or a disabled SNPN access mode.

[0183] In addition, the 52nd identification information can indicate a need to change from PLMN to SNPN, a need to redirect to SNPN, an inability to access SNPN via PLMN (not available), an inability to access SNPN via PLMN (not available), an inability to access SNPN via PLMN (not allowed), an inability to access SNPN directly, or the activation of SNPN access mode.

[0184] Furthermore, the 53rd identification information is identification information that includes at least two of the 51st and 52nd identification information.

[0185] Furthermore, the 62nd identification information is a reason value. The 62nd identification information can be a 5GMM reason. The 62nd identification information can indicate a need for a change from SNPN to PLMN, a need for redirection to SNPN via PLMN (redirection to SNPN via PLMN required), an inability to use SNPN (SNPN not available), an inability to use direct access to SNPN (direct access to SNPN not available), an inability to use SNPN (SNPN not allowed), an inability to use direct access to SNPN (direct access to SNPN not allowed), an inability to use access to SNPN via PLMN (access to SNPN via PLMN allowed), or a disabling of SNPN access mode.

[0186] In addition, the 62nd identification information can indicate a need to change from PLMN to SNPN, a need to redirect to SNPN (redirection to SNPN required), an inability to access to SNPN via PLMN (access to SNPN not available), an inability to access SNPN via PLMN (SNPN via PLMN not available), an inability to access SNPN via PLMN (access to SNPN not allowed), an inability to directly access SNPN (direct access to SNPN allowed), or the activation of SNPN access mode.

[0187] Furthermore, the seventy-first identification information is the PDU session ID that identifies the PDU session. Additionally, the seventy-first identification information is the PDU session ID that identifies the PDU session indicating its release.

[0188] Furthermore, the 72nd identification information is a reason value. The 72nd identification information can be a 5GSM reason. The 72nd identification information can indicate a need to change from SNPN to PLMN, a need to redirect to SNPN via PLMN (redirection to SNPN via PLMN required), an inability to use SNPN (SNPN not available), an inability to use direct access to SNPN (direct access to SNPN not available), an inability to use SNPN (SNPN not allowed), an inability to use direct access to SNPN (direct access to SNPN not allowed), an inability to use access to SNPN via PLMN (access to SNPN via PLMN allowed), or a disabling of SNPN access mode.

[0189] In addition, the 72nd identification information can indicate a need to change from PLMN to SNPN, a need to redirect to SNPN, an inability to access SNPN via PLMN (not available), an inability to access SNPN via PLMN (not available), an inability to access SNPN via PLMN (not allowed), an inability to access SNPN directly, or the activation of SNPN access mode.

[0190] In addition, the 73rd identification information is the access type. The 73rd identification information can indicate 3GPP access and / or non-3GPP access.

[0191] Furthermore, when the first PDU session for SNPN is established via 3GPP access, i.e. when the first PDU session is to be released, the 73rd identification information can represent 3GPP access.

[0192] Furthermore, in the case where a second PDU session for a PLMN is established via 3GPP access, and a third PDU session for an SNPN is also established via non-3GPP access using the second PDU session (via PLMN), i.e., when only the third PDU session is to be released, the seventy-third identification information can indicate non-3GPP access.

[0193] Furthermore, when a second PDU session for a PLMN is established via 3GPP access, and a third PDU session for an SNPN is also established via the PLMN (that is, via the established PDU session), i.e. when the second PDU session and the third PDU session are to be released, the 73rd identification information can indicate 3GPP access and non-3GPP access.

[0194] Furthermore, when a second PDU session for a PLMN is established via 3GPP access, i.e. when the second PDU session is to be released, the 73rd identification information can represent 3GPP access.

[0195] Furthermore, the 74th identification information is the PDU session ID that identifies the PDU session. Additionally, the 74th identification information can be the PDU session ID that identifies an already established PDU session. For example, the 74th identification information can be the PDU session ID that identifies a PDU session established in the SNPN, the PDU session ID that identifies a PDU session established in the PLMN, or the PDU session ID that identifies a PDU session established in the SNPN via the PLMN.

[0196] Furthermore, the 75th identification information is identification information that includes at least two of the 71st to 74th identification information.

[0197] Furthermore, the 81st identification information is the PDU session ID that identifies the PDU session. Additionally, the 81st identification information is the PDU session ID that identifies the PDU session for which a release request is being made.

[0198] [3. First Implementation Method]

[0199] In this embodiment, within the SNPN, the UE executes the registration procedure (Chapter 3.1) and the PDU session establishment procedure (Chapter 3.2) to establish a first PDU session. Then, the UE can, as needed, execute the de-registration procedure (Chapter 3.3) or the PDU session release procedure (Chapter 3.4) within the SNPN. Then, the UE executes the registration procedure (Chapter 3.5) and the PDU session establishment procedure (Chapter 3.6) within the PLMN to establish a second PDU session. Then, via the established second PDU session (i.e., via the PLMN), the UE executes the registration procedure (Chapter 3.7) and the PDU session establishment procedure (Chapter 3.8) within the SNPN to establish a third PDU session. This concludes the description. By executing these procedures, the UE can transfer the first PDU session to the third PDU session. [3.1. Registration Procedure for SNPN]

[0200] Here, use Figure 1 , Figure 2 as well as Figure 8 This document describes the SNPN registration procedure initiated by a UE in a state where the SNPN access mode is activated. It should be noted that in the case of SNPN access mode managed per access, the SNPN registration procedure can be initiated by a UE in a state where the SNPN access mode for 3GPP access is activated. In this case, the SNPN access mode for non-3GPP access can be activated or disabled, but ideally disabled. Hereinafter, the SNPN registration procedure will also be referred to as the registration procedure or this procedure. The registration procedure is a UE-initiated process for registering with Access Network_100 (hereinafter also referred to as Access Network) and / or Core Network_200 (hereinafter also referred to as Core Network) and / or DN_250 (hereinafter also referred to as DN). If the UE is in a state not registered to the network, it can execute this procedure at any time, such as when the power is on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), it can initiate this procedure at any time. Furthermore, each device (especially the UE and AMF) can transition to a logged-in state (5GMM-REGISTEDED state) based on the completion of the login process. It should be noted that each login state can be managed on a per-device basis for each type of access. Specifically, each device can independently manage the login state (logged-in or non-logged-in state) for 3GPP access and the login state for non-3GPP access.

[0201] Furthermore, the login process can be a process for updating the UE's location login information in the network and / or for periodically notifying the network of the UE's status and / or updating specific parameters related to the UE in the network.

[0202] The UE can initiate the login process while moving across TAs. In other words, the UE can initiate the login process when moving to a TA different from the TA shown in its maintained TA list. Furthermore, the UE can also initiate the login process when the context of each device needs to be updated due to the PDU session being terminated or disabled. Moreover, the UE can also initiate the login process when capability information and / or preferences related to the establishment of the UE's PDU session change. Furthermore, the UE can initiate the login process periodically. Additionally, the UE can initiate the login process based on the completion of the login process or the completion of the PDU session establishment process, or information received from the network during either process. It should be noted that the UE can execute the login process at any time, and is not limited to this.

[0203] It should be noted that the process described above for transitioning from a UE not logged into the network (non-login state) to a logged-in state (login state) can be an initial registration procedure or a registration procedure for initial registration. Furthermore, the login procedure performed while the UE is logged into the network (login state) can also be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0204] First, the UE initiates the login process by sending a Registration request message to AMF_210 (hereinafter also referred to as AMF) via 3GPP access (access network_100) (S600)(S602)(S604). Here, 3GPP access may include base station device_110 (hereinafter also referred to as base station device). That is, the UE sends an RRC message including the login request message to the base station device (also referred to as gNB) (S600). It should be noted that the login request message is a NAS message transmitted and received on the N1 interface. Furthermore, the RRC message can be a control message transmitted and received between the UE and the base station device. Additionally, the NAS message is processed at the NAS layer, and the RRC message is processed at the RRC layer, which is lower than the NAS layer.

[0205] Here, the UE can include at least one of the first to fourth identification information in the login request message and / or RRC message.

[0206] The UE can include at least one of these identification information in control messages sent with these different control messages, such as those at layers lower than the RRC layer (e.g., MAC (Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol), SDAP (Service Data Adaptation Protocol), etc.). It should be noted that the UE can use this identification information to indicate that it supports various functions, to indicate a request from the UE, or both.

[0207] It should be noted that the UE may select and determine whether to send at least one of these identification information based on the UE's capability information and / or UE policies and / or UE status and / or user login information and / or the context maintained by the UE.

[0208] The UE may include information other than these identification details in the login request message and / or the RRC message, such as the UE ID and / or PLMN ID and / or AMF identification information. Here, AMF identification information may refer to information that identifies an AMF or a set of AMFs, such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0209] When the base station receives an RRC message including a login request message, it selects the AMF (Advanced Feature Message) to transmit the login request message (S602). It should be noted that the base station can select the AMF based on the received message and / or information. It should also be noted that the base station can select the AMF based on other conditions.

[0210] The base station device extracts the login request message from the received RRC message and transmits the login request message to the selected AMF (S604). It should be noted that if at least one of the first to fourth identification information is not included in the login request message but is included in the RRC message, the identification information included in the RRC message can be input together with the login request message to the selected AMF (S604).

[0211] The AMF can perform a first condition check upon receiving a login request message. The first condition check is used to determine whether the network accepts the UE's request. If the first condition check is true, the AMF can execute procedures S610 to S612. Alternatively, the AMF can execute procedure S610 if the first condition check is false.

[0212] Furthermore, the first condition determination can also be performed by a network function other than the AMF (also known as an NF). This NF could be, for example, the NSSF (Network Slice Selection Function), NWDAF (Network Data Analytics Function), PCF (Policy Control Function), etc. When the first condition determination is performed by an NF other than the AMF, the AMF can provide that NF with the information required to perform the first condition determination, specifically providing at least a portion of the information received from the UE. Moreover, if the NF determines the truth or falsehood of the first condition determination based on the information received from the AMF, it can transmit information including the result of the first condition determination (i.e., whether it is true or false) to the AMF. The AMF can then determine the identification information and / or control messages to be sent to the UE based on the result of the first condition determination received from that NF.

[0213] It should be noted that, if the first condition is true, the control message sent and received in S610 is a Registration accept message, and if the first condition is false, the control message sent and received in S610 is a Registration reject message.

[0214] It should be noted that the first condition determination can be performed based on the receipt of the login request message and / or the various identification information and / or subscriber information and / or network capability information and / or operator policies and / or network status and / or user login information and / or the context maintained by the AMF, etc.

[0215] For example, the first condition can be determined to be true if the network allows the UE's request, and false if the network does not allow the UE's request. Alternatively, the first condition can be determined to be true if the network and / or devices within the UE's login destination support the requested function, and false if the requested function is not supported. Furthermore, the first condition can be determined to be true if the transmitted and received identification information is allowed, and false if the transmitted and received identification information is not allowed.

[0216] Here, we assume the first condition is true to continue the following explanation.

[0217] The AMF can include one or more of the first to sixteenth identification information in the control message. Furthermore, the eleventh identification information can be sent only if the first identification information is received, or it can be sent even if the first identification information is not received. It should be noted that the AMF can use these identification information and / or control messages to indicate network support for various functions, to indicate that a UE's request is accepted, to indicate that a request from the UE is not allowed, or to indicate a combination of these information. Moreover, when sending and receiving multiple identification information, two or more of these identification information can constitute one or more identification information. It should be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification information, or as different identification information.

[0218] AMF may send an empty value in the allowed NSSAI without allowing the UE when sending the control message (login acceptance message), but may do so if there is a scheduled NSSAA procedure to be performed after this procedure is completed or in parallel with this procedure, or if an NSSAA procedure is being performed between the UE and the network, or if the pending NSSAI is included in the control message.

[0219] It should be noted that the AMF can determine which of the eleventh to sixteenth identification information to include in the control 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 login information and / or the context maintained by the AMF.

[0220] In addition, the AMF can indicate that the UE's request has been accepted by sending a login 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 login information and / or the context maintained by the AMF.

[0221] The UE receives a control message (login acceptance message) via the base station device (S610). By receiving the login acceptance message, the UE can identify whether the UE's request based on the login request message has been accepted and the content of various identification information included in the login acceptance message.

[0222] The UE can further send a login completion message to the AMF via the base station device as a response message to the login acceptance message (S612). Here, the login completion message is a NAS message transmitted and received on the N1 interface, but it can also be transmitted and received between the UE and the base station device as part of an RRC message.

[0223] AMF receives the login completion message via the base station device (S612). In addition, each device completes this process based on the transmission and reception of the login acceptance message and / or login completion message.

[0224] It should be noted that each device can transition to or maintain the UE's logged-in state (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of login acceptance messages and / or login completion messages or the completion of the login process.

[0225] In addition, each device can establish corresponding storage for the information received and sent during this process.

[0226] Furthermore, after completing this process, the UE's SNPN access mode can also be in an activated state. It should be noted that when managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated, or the SNPN access mode for non-3GPP access can remain unchanged.

[0227] [3.2. PDU Session Establishment Process for SNPN]

[0228] Next, use Figure 1 , Figure 2 as well as Figure 9 This section describes the PDU session establishment procedure performed by a UE in SNPN with its SNPN access mode activated after performing the login procedure described in Chapter 3.1 more than once, in order to establish a PDU session in SNPN. It should be noted that in the case of SNPN access mode managed per access, the PDU session establishment procedure in SNPN can be initiated by a UE in SNPN with its SNPN access mode activated for 3GPP access. In this case, the SNPN access mode for non-3GPP access can be activated or disabled, but ideally it should be disabled. Hereinafter, the PDU session establishment procedure in SNPN will also be referred to as the PDU session establishment procedure or this procedure.

[0229] First, the UE initiates the PDU session establishment process by sending a NAS message (S800) containing an N1 SM container with a PDU session establishment request message to AMF_210 (hereinafter also referred to as AMF) via 3GPP access (access network_100). Here, 3GPP access may include base station device_110 (hereinafter also referred to as base station device). That is, the UE sends the NAS message to the AMF via the base station device. The NAS message, for example, is a message sent via the N1 interface and may be an uplink NAS transfer (UL NASTRANSPORT) message.

[0230] Furthermore, the UE can notify the network side of a request by sending at least one of the twenty-first to twenty-sixth and twenty-eighth identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message. Here, the twenty-first identification information represents PDU session ID#1 that identifies the first PDU session. In addition, the twenty-third identification information can represent SSC mode 1, SSC mode 2, or SSC mode 3, but here it represents SSC mode 2.

[0231] It should be noted that the UE may determine whether to send one of the twenty-first to twenty-sixth and twenty-eighth identification information to the network based on the UE's capability information and / or UE policy and / or UE status and / or user login information and / or the context maintained by the UE.

[0232] It should be noted that the UE may also include this identification information in control messages that are different from these control messages, such as control messages at layers lower than the NAS layer (e.g., RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.) or control messages at layers higher than the NAS layer (e.g., transport layer, session layer, presentation layer, application layer, etc.).

[0233] Next, the AMF can identify the content of received NAS messages, UE requests, and / or information included in NAS messages (messages, containers, information).

[0234] Next, the AMF selects the SMF as the transmission destination for at least a portion of the information (messages, containers, information) included in the NAS message received from the UE (S802). It should be noted that the AMF can select the SMF as the transmission destination based on the information (messages, containers, information) included 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 login information and / or the context maintained by the AMF. Here, SMF_220 (hereinafter also referred to as SMF) is selected.

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

[0236] Next, when receiving information (messages, containers, messages) sent from the AMF, the SMF can identify the content of the requests made by the UE and / or the information (messages, containers, messages) received from the AMF.

[0237] Here, SMF can perform a second condition check. Furthermore, the second condition check can be used to determine whether the network accepts the UE's request. SMF can begin processing if the second condition check is found to be true. Figure 9 The process of (A) begins when the second condition is determined to be false. Figure 9 The process of (B).

[0238] It should be noted that the second condition determination can also be performed by an NF other than the SMF. This NF could be, for example, the NSSF, NWDAF, PCF, or NRF. When the second condition determination is performed by an NF other than the SMF, the SMF can provide that NF with the information required for the second condition determination, specifically providing at least a portion of the information received from the UE (S806). Furthermore, if the NF determines the truth or falsehood of the second condition determination based on the information received from the SMF, it can transmit information including the result of the second condition determination (i.e., whether it is true or false) to the SMF. The SMF can then determine the identification information and / or control messages to be sent to the UE based on the result of the second condition determination received from that NF.

[0239] It should be noted that the second condition determination can be performed based on information received from the AMF (messages, containers, information) and / or subscription information and / or network capability information and / or UE policies and / or operator policies and / or network status and / or user login information and / or the context maintained by the SMF.

[0240] For example, the second condition can be determined to be true if the network allows the UE's request, and false if the network does not allow the UE's request. Alternatively, the second condition can be determined to be true if the network and / or devices within the network at the UE's connection destination support the requested function, and false if the requested function is not supported. Furthermore, the second condition can be determined to be true if the transmitted and received identification information is allowed, and false if the transmitted and received identification information is not allowed. It should be noted that the conditions for determining the truth or falsity of the second condition are not limited to the conditions described above.

[0241] Next, regarding Figure 9 The steps of process (A) will be explained.

[0242] Next, the SMF can select a UPF for the established PDU session, for example, by sending an N4 session establishment request message (S808) to the selected UPF via the N4 interface. The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0243] Here, the SMF can select one or more UPFs based on information received from the AMF (messages, containers, information) 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 login information and / or the context maintained by the SMF. Furthermore, if multiple UPFs are selected, the SMF can send an N4 session establishment request message to each UPF. Here, UPF_232 (hereinafter referred to as UPF) is selected.

[0244] Next, the UPF can identify the content of the information received from the SMF when it receives the N4 session establishment request message (S808). In addition, the UPF can also send an N4 session establishment response message to the SMF via the N4 interface based on the receipt of the N4 session establishment request message (S810).

[0245] Next, the SMF can identify the content of the information received from the UPF when receiving the N4 session establishment response message, and use it as a response message to the N4 session establishment request message.

[0246] Next, the SMF receives the PDU session establishment request message and / or selects the UPF and / or receives the N4 session establishment response message, for example, via the N11 interface, and sends the N1 SM container and / or N2 SM information and / or PDU session ID to the AMF (S812). Here, the N1 SM container may include a PDU session establishment accept message.

[0247] Next, the AMF, having received the N1 SM container and / or N2 SM information and / or PDU session ID, sends a NAS message to the UE via the base station equipment included in the access network (S814)(S816). Here, the NAS message is sent, for example, via the N1 interface. Furthermore, the NAS message can be a downlink NAS transport (DL NAS TRANSPORT) message.

[0248] Specifically, when the AMF sends an N2 PDU session request message to a base station device included in the access network (S814), the base station device receiving the N2 PDU session request message sends a NAS message to the UE (S816). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. Furthermore, the NAS message may include a PDU session ID and / or an N1 SM container.

[0249] Furthermore, a PDU session establishment acceptance message can be a response message to a PDU session establishment request. Additionally, a PDU session establishment acceptance message can indicate that the establishment of a PDU session has been accepted.

[0250] Here, the SMF and / or AMF may indicate that at least a portion of the UE's request based on the PDU session establishment request message has been accepted by sending a PDU session establishment accept message and / or an N1 SM container and / or a PDU session ID and / or a NAS message and / or an N2 SM information and / or an N2 PDU session request message.

[0251] Here, the SMF and / or AMF may send at least one of the thirty-first to thirty-seventh identification information in the PDU session establishment accept message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message. Here, the thirty-first identification information may be the same as the twenty-first identification information of this process. Furthermore, the thirty-second identification information may be the same as or different from the twenty-second identification information of this process. Furthermore, the thirty-third identification information may be the same as or different from the twenty-third identification information of this process, but here it is set to represent information indicating SC mode 2. Furthermore, the thirty-fifth identification information may be the same as the twenty-fifth identification information of this process. Furthermore, the thirty-sixth identification information may be the same as the twenty-sixth identification information of this process. Furthermore, the thirty-fourth identification information may be information sent only upon receiving the twenty-fourth identification information, or information sent even if the twenty-fourth identification information is not received.

[0252] It should be noted that the SMF can indicate network support for various functions, the acceptance of a UE's request, or the denial of a request from a UE by sending these identification information and / or PDU session establishment acceptance messages. It can also indicate a combination of these information. Furthermore, when sending and receiving multiple identification information, two or more of these identification information can constitute one or more separate identification information. It should also be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification information or as different identification information.

[0253] SMF and / or AMF can notify the UE of the contents of these identification information by sending at least one of these identification information.

[0254] It should be noted that the SMF and / or AMF may determine which identification information to include in the PDU session establishment accept message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the 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 login information and / or the context maintained by the SMF and / or AMF.

[0255] Next, the UE can, for example, when receiving a NAS message via the N1 interface (S816), identify the content of the UE's request based on the PDU session establishment request message being accepted and / or the information (message, container, information) included in the NAS message.

[0256] The UE can identify the SSC mode set for the PDU session identified by the 31st identification information based on the received 31st and 33rd identification information.

[0257] Next, regarding Figure 9 The process of (B) will be explained step by step.

[0258] First, the SMF receives a PDU session establishment request message, for example, by sending the N1 SM container and / or PDU session ID to the AMF (S818) via the N11 interface. Here, the N1 SM container may include a PDU session establishment rejection message.

[0259] Next, the AMF that receives the N1 SM container and / or PDU session ID sends a NAS message to the UE via the first base station device included in the access network (S820)(S822). Here, the NAS message is sent, for example, via the N1 interface. Furthermore, the NAS message can be a downlink NAS transport (DL NAS TRANSPORT) message. Additionally, the NAS message may include the PDU session ID and / or N1 SM container.

[0260] Furthermore, a PDU session establishment rejection message can be a response message to a PDU session establishment request. Additionally, a PDU session establishment rejection message can indicate that the establishment of a PDU session has been rejected.

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

[0262] It should be noted that SMF, by sending PDU session establishment rejection messages, can indicate that the network does not support certain functions, that the UE's request is rejected, that requests from the UE are not allowed, or a combination of these. Furthermore, when sending and receiving multiple identification messages, two or more of these identification messages can constitute one or more separate identification messages. It should also be noted that information indicating support for certain functions and information indicating a request to use certain functions can be sent and received as the same identification message, or as different identification messages.

[0263] SMF and / or AMF can notify the UE of the contents of these identification information by sending at least one of these identification information.

[0264] Next, the UE can, for example, when receiving a NAS message via the N1 interface (S822), identify the content of the UE's request based on the PDU session establishment request message being rejected and / or information included in the NAS message, such as messages, containers, or information.

[0265] Each device can complete this process by establishing and receiving message transmission and reception based on the PDU session. At this point, each device can transition to a state where it can communicate with the DN using the established PDU session.

[0266] Each device can complete this process by establishing and sending rejection messages based on a PDU session. In this case, each device cannot establish a PDU session, and therefore, without an established PDU session, it cannot communicate with the DN.

[0267] It should be noted that the various processes performed by the UE based on the receipt of each identification information, as described above, can be performed during this process or after the completion of this process, or they can be performed after the completion of this process based on the completion of this process.

[0268] In addition, each device can establish corresponding storage for the information received and sent during this process.

[0269] Furthermore, after completing this process, the UE's SNPN access mode can also be in an activated state. It should be noted that when managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated, or the SNPN access mode for non-3GPP access can remain unchanged.

[0270] The following explanation assumes that the PDU session has been established and the PDU session in SNPN has already been established, and the PDU session has been received and accepted.

[0271] [3.3. Non-login procedures in SNPN]

[0272] This procedure is executed after the procedure in Chapter 3.2. Next, the non-login procedure in SNPN executed by a UE in an SNPN access mode that is activated will be described. It should be noted that, in the case of SNPN access mode managed per access, the non-login procedure in SNPN can be initiated by a UE in an SNPN access mode activated for 3GPP access. At this time, the SNPN access mode for non-3GPP access can be activated or disabled, but ideally it should be disabled. Hereinafter, the non-login procedure in SNPN will also be referred to as the non-login procedure or this procedure. There are network-led and UE-led non-login procedures. The non-login procedure can be a procedure used to delog a UE from the network (access network and / or core network and / or DN). In other words, the UE or AMF can execute the non-login procedure while the UE is in a state already logged into the network (RM-REGISTERED state or 5GMM-REGISTEDED state). Furthermore, each device can execute the non-login procedure when it is detected that the UE has left the communicable area of ​​the SNPN. In particular, this procedure can be performed when a PDU session configured as SSC mode 2 is being established.

[0273] [3.3.1 Network-led non-login process]

[0274] First, use Figure 1 , Figure 2 as well as Figure 10 This section describes the network-driven non-login process. Hereinafter, the network-driven non-login process in SNPN will also be referred to as the non-login process or this process.

[0275] The AMF_210 (hereinafter also referred to as AMF) initiates this procedure by sending a non-login request (DEREGISTRATION REQUEST) message to the UE (S900) via 3GPP access (access network_100). Here, the non-login request message is a NAS message transmitted and received on the N1 interface, but it is actually a message sent by the AMF to the UE via the base station device_110 (hereinafter also referred to as the base station device) included in the access network_100.

[0276] Furthermore, the AMF may include at least one of the identification information from 41 to 43 in the non-login request message. It should be noted that whether the non-login request message includes any of the identification information from 41 to 43 can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the twenty-fourth identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for handover between the SNPN and PLMN, the AMF may include at least one of the identification information from 41 to 43 in the non-login request message.

[0277] In addition, the AMF can send at least one of these identification information and / or a non-login request message to request the change of the UE's login state in the SNPN to a non-login state, and / or release a PDU session established in the SNPN, and / or instruct to start a login process and / or PDU session establishment process against the PLMN, and / or instruct to start a login process and / or PDU session establishment process against the SNPN via the PLMN, and / or instruct to change from a direct connection to the SNPN to a connection to the SNPN via the PLMN, and / or instruct to change a PDU session established directly to the SNPN to a PDU session established to the SNPN via the PLMN, and / or instruct to disable the SNPN access mode.

[0278] When the UE receives a non-login request message from the AMF, it can identify the content of each identification information included in the non-login request message. Moreover, the UE can determine its actions based on the reception of the non-login request message and / or each identification information.

[0279] That is, the UE can change its login state in the SNPN to a non-login state, or release the PDU session established in the SNPN, or start the login process and / or PDU session establishment process for the PLMN, or start the login process and / or PDU session establishment process for the SNPN via the PLMN, or trigger the process to change from a direct connection to the SNPN to a connection to the SNPN via the PLMN.

[0280] Furthermore, the UE that receives the non-login request message can send a non-login acceptance (DEREGISTRATIONACCEPT) message (S902) to the AMF. Here, the non-login acceptance message is a NAS message sent and received on the N1 interface, but it is actually a message sent by the UE to the AMF via the access network.

[0281] Each device can transition to a state where the UE is not logged into the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of non-login received messages. Furthermore, this state transition implemented by each device can be based on the completion of this process.

[0282] Furthermore, each device can perform processing based on the information transmitted and received during the non-login process based on the completion of the non-login process. For example, based on the completion of the non-login process, the UE can begin the login process for the PLMN or disable the SNPN access mode. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged. It should be noted that the UE can disable the SNPN access mode based on the transmission and reception of non-login request messages and / or non-login acceptance messages and / or various identification information. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged.

[0283] [3.3.2 UE-led non-login process]

[0284] Next, use Figure 1 , Figure 2 as well as Figure 11 The UE-led non-login process will be described below. Hereinafter, the UE-led non-login process in SNPN will also be referred to as the non-login process or this process. The UE initiates this process by sending a non-login request (DEREGISTRATION REQUEST) message to AMF_210 (hereinafter also referred to as AMF) (S1000) via 3GPP access (access network_100). Here, the non-login request message is a NAS message transmitted and received on the N1 interface, but it is actually a message sent by the UE to the AMF via the base station device_110 (hereinafter also referred to as the base station device) included in access network_100.

[0285] Furthermore, the UE may include at least one of the identification information from 51 to 53 in the non-login request message. It should be noted that whether the non-login request message includes any of the identification information from 51 to 53 can be determined based on the first identification information sent during the login process performed prior to this procedure and / or the twenty-fourth identification information sent during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for handover between the SNPN and PLMN, the UE may include at least one of the identification information from 51 to 53 in the non-login request message.

[0286] When the AMF receives a non-login request message from the UE, it can determine the AMF's action based on the reception of the non-login request message and / or identification information.

[0287] For example, the AMF that receives a non-login request message can send a non-login acceptance (DEREGISTRATIONACCEPT) message (S1002) to the UE. Here, the non-login acceptance message is a NAS message sent and received on the N1 interface, but it is actually a message sent by the AMF to the UE via the access network.

[0288] Furthermore, the AMF may include the sixty-second identification information in the non-login acceptance message. It should be noted that whether the sixty-second identification information is included in the non-login acceptance message can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the twenty-fourth identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for handover between the SNPN and PLMN, the AMF may include the sixty-second identification information in the non-login acceptance message.

[0289] In addition, the AMF can send at least one of these identification messages and / or a non-login acceptance message to request to change the login state of the UE in the SNPN to a non-login state, and / or to release a PDU session established in the SNPN, and / or to instruct to start a login process and / or PDU session establishment process against the PLMN, and / or to instruct to start a login process and / or PDU session establishment process against the SNPN via the PLMN, and / or to instruct to change from a direct connection to the SNPN to a connection to the SNPN via the PLMN, and / or to instruct to change a PDU session established directly to the SNPN to a PDU session established to the SNPN via the PLMN, and / or to instruct to disable the SNPN access mode.

[0290] When the UE receives a non-login acceptance message from the AMF, it can identify the content of each identification information included in the non-login acceptance message. Moreover, the UE can determine its actions based on the reception of the non-login acceptance message and / or each identification information.

[0291] That is, the UE can change its login state in the SNPN to a non-login state, or release the PDU session established in the SNPN, or start the login process and / or PDU session establishment process for the PLMN, or start the login process and / or PDU session establishment process for the SNPN via the PLMN, or trigger a change from direct connection to the SNPN to connection to the SNPN via the PLMN.

[0292] Each device can transition to a state where the UE is not logged into the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of non-login received messages. Furthermore, this state transition implemented by each device can be based on the completion of this process.

[0293] Furthermore, each device can perform processing based on the information transmitted and received during the non-login process based on the completion of the non-login process. For example, based on the completion of the non-login process, the UE can begin the login process for the PLMN or disable the SNPN access mode. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged. It should be noted that the UE can disable the SNPN access mode based on the transmission and reception of non-login request messages and / or non-login acceptance messages and / or various identification information. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged.

[0294] [3.4. PDU Session Release Process in SNPN]

[0295] This procedure is performed after the procedure in Chapter 3.2. Next, the PDU session release procedure in the SNPN executed by a UE in an SNPN access mode that is active will be described. It should be noted that in the case of SNPN access mode managed per access, the PDU session release procedure in the SNPN can be initiated by a UE in an SNPN access mode activated for 3GPP access. At this time, the SNPN access mode for non-3GPP access can be activated or disabled, but ideally it should be disabled. Hereinafter, the PDU session release procedure in the SNPN will also be referred to as the PDU session release procedure or this procedure. There are network-led PDU session release procedures and UE-led PDU session release procedures. The PDU session release procedure can be used to release a PDU session. Furthermore, each device can execute the PDU session release procedure when it is detected that the UE has left the communicable area of ​​the SNPN. In particular, this procedure can be executed when a PDU session set to SSC mode 2 is being established.

[0296] [3.4.1 Network-led PDU session release process]

[0297] First, use Figure 1 , Figure 2 as well as Figure 12 This section describes the network-led PDU session release process. Hereinafter, the network-led PDU session release process in SNPN will also be referred to as the PDU session release process or this process. The SMF_220 (hereinafter also called SMF) initiates this process by sending a PDU session release command (PDU SESSION RELEASE COMMAND) message to the UE (S1002). Here, the PDU session release command message is a message included in the NAS messages transmitted and received on the N1 interface, but it is actually a message sent by the SMF to the UE via AMF_210 (hereinafter also called AMF) and Access Network_100 (hereinafter also called Access Network).

[0298] Furthermore, the SMF may include at least one of the identification information 71 to 73 and 75 in the PDU session release command message. It should be noted that whether the PDU session release command message includes any of the identification information 71 to 73 and 75 can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the twenty-fourth identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for switching between SNPN and PLMN, the SMF may include at least one of the identification information 71 to 73 and 75 in the PDU session release command message. It should be noted that the seventy-first identification information may represent the PDU session ID#1 that identifies the first PDU session.

[0299] In addition, the SMF can send at least one of these identification information and / or a PDU session release command message to indicate the release of a PDU session established in the SNPN, and / or the initiation of a login process and / or PDU session establishment process against the PLMN, and / or the initiation of a login process and / or PDU session establishment process against the SNPN via the PLMN, and / or the change from a direct connection to the SNPN to a connection to the SNPN via the PLMN, and / or the change from a PDU session directly established to the SNPN to a PDU session established to the SNPN via the PLMN, and / or the disabling of the SNPN access mode.

[0300] When the UE receives a PDU session release command message from the SMF, it can identify the content of each identification information included in the PDU session release command message. Moreover, the UE can determine its actions based on the reception of the non-login request message and / or each identification information.

[0301] That is, the UE can release the PDU session established in the SNPN, or start the login process and / or PDU session establishment process for the PLMN, or start the login process and / or PDU session establishment process for the SNPN via the PLMN, or determine to change from a direct connection to the SNPN to a connection to the SNPN via the PLMN, or determine to change the PDU session established directly to the SNPN to a PDU session established to the SNPN via the PLMN.

[0302] Furthermore, the UE that receives the PDU session release command can send a PDU session release complete message to the SMF. Here, the PDU session release complete message is a message included in the NAS messages sent and received by the AMF on the N1 interface, but it is actually a message sent by the UE to the SMF via the access network and the AMF.

[0303] Furthermore, each device can process the information sent and received during the PDU session release process based on its completion. For example, based on the completion of the PDU session release process, the UE can start the login process for the PLMN, disable the SNPN access mode, or leave the SNPN access mode state unchanged. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged. It should be noted that, based on the transmission and reception of the PDU session release command and / or the PDU session release completion message and / or various identification information, the UE can disable the SNPN access mode, or leave the SNPN access mode state unchanged. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged. [3.4.2 UE-led PDU session release process]

[0304] Next, use Figure 1 , Figure 2 as well as Figure 12 This section describes the UE-led PDU session release process. Hereinafter, the UE-led PDU session release process in SNPN will also be referred to as the PDU session release process or this process. The UE initiates this process by sending a PDU session release request (PDU SESSION RELEASE REQUEST) message to SMF_220 (hereinafter also referred to as SMF) (S1000). Here, the PDU session release request message is included in the NAS messages sent and received on the N1 interface, but it is actually a message sent by the UE to the SMF via Access Network_100 (hereinafter also referred to as Access Network) and AMF_210 (hereinafter also referred to as AMF).

[0305] Furthermore, the UE may include the 81st identification information in the PDU session release request message. It should be noted that whether the 81st identification information is included in the PDU session release request message can be determined based on the first identification information sent during the login process prior to this procedure and / or the 24th identification information sent during the PDU session establishment process prior to this procedure. For example, if the first identification information and / or the 24th identification information indicate support for handover between the SNPN and PLMN, the UE may include the 81st identification information in the PDU session release request message. It should be noted that the 81st identification information may represent the PDU session ID#1 that identifies the first PDU session.

[0306] When the SMF receives a PDU session release request message from the UE, it can determine the SMF's action based on the receipt of the PDU session release request message.

[0307] For example, the SMF may send the PDU session release command message including at least one of the identification information from the 71st to 73rd and 75th segments (S1002). It should be noted that whether the PDU session release command message includes any of the identification information from the 71st to 73rd and 75th segments can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the 24th identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the 24th identification information indicate support for switching between the SNPN and PLMN, the SMF may send the PDU session release command message including at least one of the identification information from the 71st to 73rd and 75th segments. It should be noted that the 71st identification information may represent the PDU session ID#1 that identifies the first PDU session.

[0308] In addition, the SMF can send at least one of these identification information and / or a PDU session release command message to indicate the release of a PDU session established in the SNPN, and / or the initiation of a login process and / or PDU session establishment process against the PLMN, and / or the initiation of a login process and / or PDU session establishment process against the SNPN via the PLMN, and / or the change from a direct connection to the SNPN to a connection to the SNPN via the PLMN, and / or the change from a PDU session directly established to the SNPN to a PDU session established to the SNPN via the PLMN, and / or the disabling of the SNPN access mode.

[0309] When the UE receives a PDU session release command message from the SMF, it can identify the content of each identification information included in the PDU session release command message. Moreover, the UE can determine its actions based on the reception of the non-login request message and / or each identification information.

[0310] That is, the UE can release the PDU session established in the SNPN, or start the login process and / or PDU session establishment process for the PLMN, or start the login process and / or PDU session establishment process for the SNPN via the PLMN, or determine to change from a direct connection to the SNPN to a connection to the SNPN via the PLMN, or determine to change the PDU session established directly to the SNPN to a PDU session established to the SNPN via the PLMN.

[0311] Furthermore, the UE that receives the PDU session release command can send a PDU session release complete message to the SMF. Here, the PDU session release complete message is a message included in the NAS messages sent and received by the AMF on the N1 interface, but it is actually a message sent by the UE to the SMF via the access network and the AMF.

[0312] Furthermore, each device can perform processing based on the information sent and received during the PDU session release process upon completion of the PDU session release process. For example, based on the completion of the PDU session release process, the UE can start the login process for the PLMN, disable the SNPN access mode, or leave the SNPN access mode state unchanged. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged. It should be noted that, based on the sending and receiving of the PDU session release command and / or the PDU session release completion message and / or various identification information, the UE can disable the SNPN access mode, or leave the SNPN access mode state unchanged. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be disabled, or the state of the SNPN access mode for non-3GPP access can remain unchanged. [3.5. Login Process for PLMN]

[0313] This procedure can be executed after the procedures in Chapters 3.1 to 3.2 have been executed. Alternatively, this procedure can be executed after the procedures in Chapters 3.1 to 3.2 have been executed, followed by the procedures in Chapters 3.3 or 3.4.

[0314] As mentioned above, a UE that has performed the non-login procedure in Chapter 3.3 or the PDU session release procedure in Chapter 3.4 in SNPN can disable SNPN access mode.

[0315] In addition, UEs that do not execute the non-login procedure in Chapter 3.3 or the PDU session release procedure in Chapter 3.4 in SNPN can disable SNPN access mode, for example, by moving, disconnecting from SNPN, or leaving the communication area of ​​SNPN.

[0316] It should be noted that when managing SNPN access mode per access point, the SNPN access mode for 3GPP access can also be disabled. In this case, the SNPN access mode for non-3GPP access can be activated or disabled, but ideally it should be disabled.

[0317] Thus, a UE whose SNPN access mode or NPN access mode for 3GPP access is disabled can perform a PLMN selection procedure to select a specific PLMN. Furthermore, it can perform a registration procedure within that PLMN. The PLMN ID corresponding to this PLMN can be, for example, possessed by the UE itself, or it can be included in system information broadcast from the PLMN's base station. The UE can use this PLMN ID to select the PLMN.

[0318] Here, use Figure 3 , Figure 4 as well as Figure 8 This document describes the registration procedure in the PLMN. Hereinafter, the registration procedure in the PLMN will also be referred to as the registration procedure or this procedure. The registration procedure is initiated by the UE to register with the access network_102 (hereinafter also referred to as the access network) and / or the core network_202 (hereinafter also referred to as the core network) and / or the DN_252 (hereinafter also referred to as the DN). If the UE is in a state of not being registered with the network, it can execute this procedure at any time, such as when the power is on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and AMF) can transition to a registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state can be managed in each device according to each type of access. Specifically, each device can independently manage the registration state (registered state or non-registered state) for 3GPP access and the registration state for non-3GPP access.

[0319] Furthermore, the login process can be a process for updating the UE's location login information in the network and / or for periodically notifying the network of the UE's status and / or updating specific parameters related to the UE in the network.

[0320] The UE can initiate the login process while moving across TAs. In other words, the UE can initiate the login process when moving to a TA different from the TA shown in its maintained TA list. Furthermore, the UE can also initiate the login process when the context of each device needs to be updated due to the PDU session being terminated or disabled. Moreover, the UE can also initiate the login process when capability information and / or preferences related to the establishment of the UE's PDU session change. Furthermore, the UE can initiate the login process periodically. Additionally, the UE can initiate the login process based on the completion of the login process or the completion of the PDU session establishment process, or information received from the network during either process. It should be noted that the UE can execute the login process at any time, and is not limited to this.

[0321] It should be noted that the process described above for transitioning from a UE not logged into the network (non-login state) to a logged-in state (login state) can be an initial registration procedure or a registration procedure for initial registration. Furthermore, the login procedure performed while the UE is logged into the network (login state) can also be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0322] First, the UE initiates the login process by sending a registration request message (S600)(S602)(S604) to the AMF_212 (hereinafter also referred to as AMF) via 3GPP access (access network_102). Here, 3GPP access may include base station device_112 (hereinafter also referred to as base station device). That is, the UE sends an RRC message including the login request message to the base station device (also referred to as gNB) (S600). It should be noted that the login request message can be a NAS message transmitted and received on the N1 interface. Furthermore, the RRC message can be a control message transmitted and received between the UE and the base station device. In addition, the NAS message is processed at the NAS layer, and the RRC message is processed at the RRC layer, which is lower than the NAS layer.

[0323] Here, the UE may include at least one of the first to fourth identification information in the login request message and / or RRC message. Here, the first to fourth identification information may be the same as or different from the first to fourth identification information in Chapter 3.1.

[0324] The UE can include at least one of these identification information in control messages sent with these different control messages, such as those at layers lower than the RRC layer (e.g., MAC (Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol), SDAP (Service Data Adaptation Protocol), etc.). It should be noted that the UE can use this identification information to indicate that it supports various functions, to indicate a request from the UE, or both.

[0325] It should be noted that the UE may select and determine whether to send at least one of these identification information based on the UE's capability information and / or UE policies and / or UE status and / or user login information and / or the context maintained by the UE.

[0326] The UE may include information other than these identification details in the login request message and / or the RRC message, such as the UE ID and / or PLMN ID and / or AMF identification information. Here, AMF identification information may refer to information that identifies an AMF or a set of AMFs, such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0327] When the base station receives an RRC message including a login request message, it selects the AMF (Advanced Feature Message) to transmit the login request message (S602). It should be noted that the base station can select the AMF based on the received message and / or information. It should also be noted that the base station can select the AMF based on other conditions.

[0328] The base station device extracts the login request message from the received RRC message and transmits the login request message to the selected AMF (S604). It should be noted that if at least one of the first to fourth identification information is not included in the login request message but is included in the RRC message, the identification information included in the RRC message can be input together with the login request message to the selected AMF (S604).

[0329] The AMF can perform a first condition check upon receiving a login request message. The first condition check is used to determine whether the network accepts the UE's request. If the first condition check is true, the AMF can execute procedures S610 to S612. Alternatively, the AMF can execute procedure S610 if the first condition check is false.

[0330] Furthermore, the first condition determination can also be performed by a network function other than the AMF (also known as an NF). This NF could be, for example, the NSSF (Network Slice Selection Function), NWDAF (Network Data Analytics Function), PCF (Policy Control Function), etc. When the first condition determination is performed by an NF other than the AMF, the AMF can provide that NF with the information required to perform the first condition determination, specifically providing at least a portion of the information received from the UE. Moreover, if the NF determines the truth or falsehood of the first condition determination based on the information received from the AMF, it can transmit information including the result of the first condition determination (i.e., whether it is true or false) to the AMF. The AMF can then determine the identification information and / or control messages to be sent to the UE based on the result of the first condition determination received from that NF.

[0331] It should be noted that, if the first condition is true, the control message sent and received in S610 is a Registration accept message, and if the first condition is false, the control message sent and received in S610 is a Registration reject message.

[0332] It should be noted that the first condition determination can be performed based on the receipt of the login request message and / or the various identification information and / or subscriber information and / or network capability information and / or operator policies and / or network status and / or user login information and / or the context maintained by the AMF, etc.

[0333] For example, the first condition can be determined to be true if the network allows the UE's request, and false if the network does not allow the UE's request. Alternatively, the first condition can be determined to be true if the network and / or devices within the UE's login destination support the requested function, and false if the requested function is not supported. Furthermore, the first condition can be determined to be true if the transmitted and received identification information is allowed, and false if the transmitted and received identification information is not allowed.

[0334] Here, we assume the first condition is true to continue the following explanation.

[0335] The AMF may include one or more of the first to sixteenth identification information in the control message. Here, the eleventh to sixteenth identification information may be the same as or different from the eleventh to sixteenth identification information in Chapter 3.1. It should be noted that the AMF can indicate network support for various functions, the acceptance of a UE's request, the denial of a request from a UE, or a combination of these information by sending these identification information and / or control messages. Furthermore, when sending and receiving multiple identification information, two or more of these identification information can constitute one or more identification information. It should be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification information or as different identification information.

[0336] AMF may send an empty value in the allowed NSSAI without allowing the UE when sending the control message (login acceptance message), but may do so if there is a scheduled NSSAA procedure to be performed after this procedure is completed or in parallel with this procedure, or if an NSSAA procedure is being performed between the UE and the network, or if the pending NSSAI is included in the control message.

[0337] It should be noted that the AMF can determine which of the eleventh to sixteenth identification information to include in the control 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 login information and / or the context maintained by the AMF.

[0338] In addition, the AMF can indicate that the UE's request has been accepted by sending a login 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 login information and / or the context maintained by the AMF.

[0339] The UE receives a control message (login acceptance message) via the base station device (S610). By receiving the login acceptance message, the UE can identify whether the UE's request based on the login request message has been accepted and the content of various identification information included in the login acceptance message.

[0340] The UE can further send a login completion message to the AMF via the base station device as a response message to the login acceptance message (S612). Here, the login completion message is a NAS message transmitted and received on the N1 interface, but it can also be transmitted and received between the UE and the base station device as part of an RRC message.

[0341] AMF receives the login completion message via the base station device (S612). In addition, each device completes this process based on the transmission and reception of the login acceptance message and / or login completion message.

[0342] It should be noted that each device can transition to or maintain the UE's logged-in state (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of login acceptance messages and / or login completion messages or the completion of the login process.

[0343] In addition, each device can establish corresponding storage for the information received and sent during this process.

[0344] Furthermore, after completing this process, the UE's SNPN access mode may also be disabled. It should be noted that when managing SNPN access modes per access point, the SNPN access mode for 3GPP access may be disabled, or the SNPN access mode for non-3GPP access may remain unchanged.

[0345] [3.6. PDU Session Establishment Process for PLMN]

[0346] Next, use Figure 3 , Figure 4 as well as Figure 9 This section describes the PDU session establishment process performed by a UE in a disabled SNPN access mode to establish a PDU session in the PLMN after performing the login process described in Chapter 3.5 more than once. It should be noted that, in the case of SNPN access mode managed per access, the PDU session establishment process in the PLMN can be initiated by a UE in a disabled SNPN access mode for 3GPP access. In this case, the SNPN access mode for non-3GPP access can be activated or disabled, but ideally disabled. Hereinafter, the PDU session establishment process in the PLMN will also be referred to as the PDU session establishment process or this process.

[0347] First, the UE initiates the PDU session establishment process by sending a NAS message (S800) containing an N1 SM container with a PDU session establishment request message to AMF_212 (hereinafter also referred to as AMF) via 3GPP access (access network_102). Here, 3GPP access may include base station device_112 (hereinafter also referred to as base station device). That is, the UE sends the NAS message to the AMF via the base station device. The NAS message, for example, is a message sent via the N1 interface and may be an uplink NAS transfer (UL NASTRANSPORT) message.

[0348] Furthermore, the UE can notify the network side of a request by sending at least one of the identification information 21 to 26, 28 in the PDU session establishment request message and / or N1 SM container and / or NAS message. Here, the identification information 21 to 26, 28 may be the same as or different from the identification information in Chapter 3.2. However, here, the identification information 21 may represent the PDU session ID#2 that identifies the second PDU session.

[0349] It should be noted that the UE may determine whether to send one of the twenty-first to twenty-sixth and twenty-eighth identification information to the network based on the UE's capability information and / or UE policy and / or UE status and / or user login information and / or the context maintained by the UE.

[0350] It should be noted that the UE may also include this identification information in control messages that are different from these control messages, such as control messages at layers lower than the NAS layer (e.g., RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.) or control messages at layers higher than the NAS layer (e.g., transport layer, session layer, presentation layer, application layer, etc.).

[0351] Next, the AMF can identify the content of received NAS messages, UE requests, and / or information included in NAS messages (messages, containers, information).

[0352] Next, the AMF selects the SMF as the transmission destination for at least a portion of the information (messages, containers, information) included in the NAS message received from the UE (S802). It should be noted that the AMF can select the SMF as the transmission destination based on the information (messages, containers, information) included 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 login information and / or the context maintained by the AMF. Here, SMF_222 (hereinafter also referred to as SMF) is selected.

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

[0354] Next, when receiving information (messages, containers, messages) sent from the AMF, the SMF can identify the content of the requests made by the UE and / or the information (messages, containers, messages) received from the AMF.

[0355] Here, SMF can perform a second condition check. Furthermore, the second condition check can be used to determine whether the network accepts the UE's request. SMF can begin processing if the second condition check is found to be true. Figure 9 The process of (A) begins when the second condition is determined to be false. Figure 9 The process of (B).

[0356] It should be noted that the second condition determination can also be performed by an NF other than the SMF. This NF could be, for example, the NSSF, NWDAF, PCF, or NRF. When the second condition determination is performed by an NF other than the SMF, the SMF can provide that NF with the information required for the second condition determination, specifically providing at least a portion of the information received from the UE (S806). Furthermore, if the NF determines the truth or falsehood of the second condition determination based on the information received from the SMF, it can transmit information including the result of the second condition determination (i.e., whether it is true or false) to the SMF. The SMF can then determine the identification information and / or control messages to be sent to the UE based on the result of the second condition determination received from that NF.

[0357] It should be noted that the second condition determination can be performed based on information received from the AMF (messages, containers, information) and / or subscription information and / or network capability information and / or UE policies and / or operator policies and / or network status and / or user login information and / or the context maintained by the SMF.

[0358] For example, the second condition can be determined to be true if the network allows the UE's request, and false if the network does not allow the UE's request. Alternatively, the second condition can be determined to be true if the network and / or devices within the network at the UE's connection destination support the requested function, and false if the requested function is not supported. Furthermore, the second condition can be determined to be true if the transmitted and received identification information is allowed, and false if the transmitted and received identification information is not allowed. It should be noted that the conditions for determining the truth or falsity of the second condition are not limited to the conditions described above.

[0359] Next, regarding Figure 9 The steps of process (A) will be explained.

[0360] Next, the SMF can select a UPF for the established PDU session, for example, by sending an N4 session establishment request message (S808) to the selected UPF via the N4 interface. The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0361] Here, the SMF can select one or more UPFs based on information received from the AMF (messages, containers, information) 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 login information and / or the context maintained by the SMF. Furthermore, if multiple UPFs are selected, the SMF can send an N4 session establishment request message to each UPF. Here, we assume that UPF_232 (hereinafter also referred to as UPF) is selected.

[0362] Next, the UPF can identify the content of the information received from the SMF when it receives the N4 session establishment request message (S808). In addition, the UPF can also send an N4 session establishment response message to the SMF via the N4 interface based on the receipt of the N4 session establishment request message (S810).

[0363] Next, the SMF can identify the content of the information received from the UPF when receiving the N4 session establishment response message, and use it as a response message to the N4 session establishment request message.

[0364] Next, the SMF receives the PDU session establishment request message and / or selects the UPF and / or receives the N4 session establishment response message, for example, via the N11 interface, and sends the N1 SM container and / or N2 SM information and / or PDU session ID to the AMF (S812). Here, the N1 SM container may include a PDU session establishment accept message.

[0365] Next, the AMF, having received the N1 SM container and / or N2 SM information and / or PDU session ID, sends a NAS message to the UE via the base station equipment included in the access network (S814)(S816). Here, the NAS message is sent, for example, via the N1 interface. Furthermore, the NAS message can be a downlink NAS transport (DL NAS TRANSPORT) message.

[0366] Specifically, when the AMF sends an N2 PDU session request message to a base station device included in the access network (S814), the base station device receiving the N2 PDU session request message sends a NAS message to the UE (S816). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. Furthermore, the NAS message may include a PDU session ID and / or an N1 SM container.

[0367] Furthermore, a PDU session establishment acceptance message can be a response message to a PDU session establishment request. Additionally, a PDU session establishment acceptance message can indicate that the establishment of a PDU session has been accepted.

[0368] Here, the SMF and / or AMF may indicate that at least a portion of the UE's request based on the PDU session establishment request message has been accepted by sending a PDU session establishment accept message and / or an N1 SM container and / or a PDU session ID and / or a NAS message and / or an N2 SM information and / or an N2 PDU session request message.

[0369] Here, the SMF and / or AMF may send at least one of the thirty-first to thirty-seventh identification information in the PDU session establishment accept message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message. Here, the thirty-first to thirty-third, thirty-fifth, and thirty-sixth identification information may be the same as or different from the twenty-first to twenty-third, twenty-fifth, and twenty-sixth identification information of this procedure. Furthermore, the thirty-fourth and thirty-seventh identification information may be the same as or different from the thirty-fourth and thirty-seventh identification information in Chapter 3.2. However, here, the thirty-first identification information is the same as the twenty-first identification information of this procedure.

[0370] It should be noted that the SMF can indicate network support for various functions, the acceptance of a UE's request, or the denial of a request from a UE by sending these identification information and / or PDU session establishment acceptance messages. It can also indicate a combination of these information. Furthermore, when sending and receiving multiple identification information, two or more of these identification information can constitute one or more separate identification information. It should also be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification information or as different identification information.

[0371] SMF and / or AMF can notify the UE of the contents of these identification information by sending at least one of these identification information.

[0372] It should be noted that the SMF and / or AMF may determine which identification information to include in the PDU session establishment accept message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the 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 login information and / or the context maintained by the SMF and / or AMF.

[0373] Next, the UE can, for example, when receiving a NAS message via the N1 interface (S816), identify the content of the UE's request based on the PDU session establishment request message being accepted and / or the information (message, container, information) included in the NAS message. For example, the UE can identify the PDU session type and SSC mode set for the PDU session identified by the 31st identification information based on the received 31st, 32nd, and 33rd identification information. In addition, the UE can identify the functions supported by the network based on the received 34th identification information.

[0374] Next, regarding Figure 9 The process of (B) will be explained step by step.

[0375] First, the SMF receives a PDU session establishment request message, for example, by sending the N1 SM container and / or PDU session ID to the AMF (S818) via the N11 interface. Here, the N1 SM container may include a PDU session establishment rejection message.

[0376] Next, the AMF that receives the N1 SM container and / or PDU session ID sends a NAS message to the UE via the first base station device included in the access network (S820)(S822). Here, the NAS message is sent, for example, via the N1 interface. Furthermore, the NAS message can be a downlink NAS transport (DL NAS TRANSPORT) message. Additionally, the NAS message may include the PDU session ID and / or N1 SM container.

[0377] Furthermore, a PDU session establishment rejection message can be a response message to a PDU session establishment request. Additionally, a PDU session establishment rejection message can indicate that the establishment of a PDU session has been rejected.

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

[0379] It should be noted that SMF, by sending PDU session establishment rejection messages, can indicate that the network does not support certain functions, that the UE's request is rejected, that requests from the UE are not allowed, or a combination of these. Furthermore, when sending and receiving multiple identification messages, two or more of these identification messages can constitute one or more separate identification messages. It should also be noted that information indicating support for certain functions and information indicating a request to use certain functions can be sent and received as the same identification message, or as different identification messages.

[0380] SMF and / or AMF can notify the UE of the contents of these identification information by sending at least one of these identification information.

[0381] Next, the UE can, for example, when receiving a NAS message via the N1 interface (S822), identify the content of the UE's request based on the PDU session establishment request message being rejected and / or information included in the NAS message, such as messages, containers, or information.

[0382] Each device can complete this process by establishing a receive message based on a PDU transmission and reception session. At this point, each device can transition to a state where it can communicate with the DN using the established PDU session.

[0383] Each device can complete this process by establishing and sending rejection messages based on a PDU session. In this case, each device cannot establish a PDU session, and therefore, cannot communicate with the DN if no PDU session has been established.

[0384] It should be noted that the various processes performed by the UE based on the receipt of each identification information, as described above, can be performed during this process or after the completion of this process, or they can be performed after the completion of this process based on the completion of this process.

[0385] In addition, each device can establish corresponding storage for the information received and sent during this process.

[0386] Furthermore, after completing this process, the UE's SNPN access mode may also be disabled. It should be noted that when managing SNPN access modes per access point, the SNPN access mode for 3GPP access may be disabled, or the SNPN access mode for non-3GPP access may remain unchanged.

[0387] The following explanation assumes that a PDU session has already been established in the PLMN and the PDU session has been received and accepted.

[0388] [3.7. (Regarding the SNPN login process via PLMN)]

[0389] Next, use Figure 3 , Figure 4 as well as Figure 8 This document describes the registration procedure via the SNPN for a UE that has completed the registration process described in Chapter 3.5 and the PDU session establishment process described in Chapter 3.6 within the PLMN. At this time, the UE's SNPN access mode can be either disabled or activated. It should be noted that in the case of SNPN access mode management per access point, the registration procedure via the PLMN's SNPN can be initiated by a UE whose SNPN access mode for non-3GPP access is activated. In this case, the SNPN access mode for 3GPP access can be activated or disabled, but ideally it should be disabled. Hereinafter, the registration procedure (via the PLMN) within the SNPN will also be referred to as the registration procedure or this procedure. Furthermore, the registration procedure (via the PLMN) within the SNPN mentioned here refers to the registration procedure performed on the SNPN using a PDU session established through the PDU session establishment process within the PLMN.

[0390] The login process in SNPN (via PLMN) can be replaced by the following substitutions, applying the login process in SNPN described in Chapter 3.1.

[0391] First, 3GPP access is replaced with non-3GPP access. Furthermore, the base station device is replaced with a base station device and / or an N3IWF. Additionally, RRC messages transmitted between the UE and the base station device are replaced with IKEv2 messages transmitted between the UE and the N3IWF. Furthermore, information and control messages included in the RRC messages are replaced with information and control messages included in the IKEv2 messages. Specifically, login request messages and / or login acceptance messages and / or login completion messages and / or login rejection messages are included in IKEv2 messages and transmitted and received via the N3IWF. Furthermore, the processing performed by the base station device is replaced with the processing performed by the N3IWF. For example, the selection of the AMF performed by the base station device can be performed by the N3IWF.

[0392] The following description focuses on the parts of the login process that differ from those in Chapter 3.1. That is to say, the parts not described below can be covered by the description in Chapter 3.1.

[0393] First, the UE initiates the login process by sending a registration request message (S600)(S602)(S604) to AMF_210 (hereinafter also called AMF) via a non-3GPP access network and N3IWF_240 (hereinafter also called N3IWF). Here, the non-3GPP access network can consist of access network_102, core network_202, and DN_252. Specifically, the UE sends an IKEv2 message including the login request message to N3IWF via the non-3GPP access network (S600). It should be noted that the login request message can be a NAS message transmitted and received on the N1 interface. Furthermore, the IKEv2 message can be a control message transmitted and received between the UE and N3IWF. Additionally, NAS messages can be processed at the NAS layer, and IKEv2 messages can be processed at a layer lower than the NAS layer.

[0394] Here, the UE can include at least one of the first to fourth identification information in the login request message and / or IKEv2 message. Here, the first to fourth identification information may be the same as or different from the first to fourth identification information in Chapter 3.1. Furthermore, the first to fourth identification information may be the same as or different from the first to fourth identification information in Chapter 3.5.

[0395] The UE may include information other than these identification information in the login request message and / or IKEv2 message, such as the UE ID and / or PLMN ID and / or AMF identification information.

[0396] When the N3IWF receives an IKEv2 message including a login request message, it selects the AMF (Application Function) for transmitting the login request message (S602). It should be noted that the N3IWF can select the AMF based on the received message and / or information. It should also be noted that the N3IWF can select the AMF based on other conditions. Here, the same AMF_210 (hereinafter also referred to as AMF) as the AMF in Chapter 3.1 is selected, but a different AMF can also be selected.

[0397] The N3IWF extracts the login request message from the received IKEv2 message and transmits the login request message to the selected AMF (S604). It should be noted that if at least one of the first to fourth identification information is not included in the login request message but is included in the IKEv2 message, the identification information included in the IKEv2 message can be input together with the login request message to the selected AMF (S604).

[0398] AMF can perform a first condition check upon receiving a login request message. The first condition check and / or the execution conditions of the first condition check and / or the criteria for determining the truth or falsehood of the first condition check and / or the actions taken when the first condition check is determined to be true or false and / or the control messages sent and received when the first condition check is determined to be true or false, etc., can be the same as in Chapter 3.1.

[0399] In addition, the first condition determination can also be performed by network functions other than AMF (also known as NF).

[0400] Here, we assume the first condition is true to continue the following explanation.

[0401] AMF may include one or more of the first to sixteenth identification information in the control message. Here, the eleventh to sixteenth identification information may be the same as or different from the eleventh to sixteenth identification information in Chapter 3.1. Furthermore, the eleventh to sixteenth identification information may be the same as or different from the eleventh to sixteenth identification information in Chapter 3.5.

[0402] The UE receives a control message (login acceptance message) via the N3IWF (S610). By receiving the login acceptance message, the UE can identify whether the UE's request based on the login request message has been accepted and the content of various identification information included in the login acceptance message.

[0403] The UE can further send the login completion message as a response message to the login acceptance message to the AMF via the N3IWF (S612). Here, the login completion message is a NAS message sent and received on the N1 interface, but it can also be included in an IKEv2 message and sent and received between the UE and the N3IWF.

[0404] The AMF receives the login completion message via the N3IWF (S612). Furthermore, each device completes this process based on the transmission and reception of the login acceptance message and / or login completion message.

[0405] It should be noted that each device can transition to or maintain the UE's logged-in state (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of login acceptance messages and / or login completion messages or the completion of the login process.

[0406] In addition, each device can establish corresponding storage for the information received and sent during this process.

[0407] Furthermore, after completing this process, the UE's SNPN access mode can be either disabled or activated. It should be noted that when managing SNPN access modes per access point, the SNPN access mode for non-3GPP access can be activated, or the SNPN access mode for 3GPP access can remain unchanged.

[0408] [3.8. (via PLMN) PDU session establishment process for SNPN]

[0409] Next, use Figure 3 , Figure 4 as well as Figure 9 This section describes the PDU session establishment process performed by a UE that has completed the login procedure described in Chapter 3.7 more than once in order to establish a PDU session in the SNPN. At this time, the UE's SNPN access mode can be either disabled or activated. It should be noted that in the case of SNPN access mode managed per access, the PDU session establishment process in the PLMN's SNPN can be initiated by a UE whose SNPN access mode for non-3GPP access is activated. In this case, the SNPN access mode for 3GPP access can be activated or disabled, but ideally it should be disabled. Hereinafter, the PDU session establishment process in the SNPN will also be referred to as the PDU session establishment process or this process.

[0410] The PDU session establishment process in SNPN can be replaced by the following substitutions, applying the PDU session establishment process in SNPN described in Chapter 3.2.

[0411] First, 3GPP access is replaced with non-3GPP access. Furthermore, the base station device is replaced with a base station device and / or an N3IWF. Additionally, RRC messages transmitted between the UE and the base station device are replaced with IKEv2 messages transmitted between the UE and the N3IWF. Moreover, information and control messages included in the RRC messages are replaced with information and control messages included in the IKEv2 messages. Specifically, PDU session establishment request messages and / or PDU session establishment accept messages and / or PDU session establishment reject messages can be included in IKEv2 messages via the N3IWF for transmission and reception.

[0412] The following description focuses on the parts that differ from the PDU session establishment process in Chapter 3.2. That is, the parts not described below can be covered by the description in Chapter 3.2.

[0413] First, the UE initiates the PDU session establishment process by sending a NAS message (S800) containing an N1 SM container with a PDU session establishment request message to AMF_210 (hereinafter also referred to as AMF) via a non-3GPP access network and N3IWF_240 (hereinafter also referred to as N3IWF). Here, the non-3GPP access network can consist of access network_102, core network_202, and DN_252. That is, the UE sends the NAS message to the AMF via N3IWF. The NAS message, for example, is a message sent via the N1 interface and can be an uplink NAS transport (UL NAS TRANSPORT) message.

[0414] Furthermore, the UE can notify the network side of a request by sending at least one of the twenty-first to twenty-eighth identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message. Here, the twenty-first to twenty-sixth and twenty-eighth identification information may be the same as or different from the twenty-first to twenty-sixth and twenty-eighth identification information in Chapter 3.6. Furthermore, the twenty-first identification information must be different from the twenty-first identification information in Chapter 3.6. Here, the twenty-first identification information represents PDU session ID #3 identifying the third PDU session. Furthermore, the twenty-second to twenty-sixth and twenty-eighth identification information may be the same as or different from the twenty-second to twenty-sixth and twenty-eighth identification information in Chapter 3.6. Furthermore, the twenty-seventh identification information must be different from the twenty-first identification information in this chapter. Furthermore, the twenty-seventh identification information may be the same as the twenty-first identification information in Chapter 3.6. That is, the twenty-seventh identification information may represent PDU session ID #2 indicating the PDU session established with the PLMN.

[0415] Next, the AMF can identify the content of received NAS messages, UE requests, and / or information included in NAS messages (messages, containers, information).

[0416] Next, the AMF selects the SMF as the transmission destination for at least a portion of the information (message, container, information) included in the NAS message received from the UE (S802). Here, the same SMF_220 (hereinafter also referred to as SMF) as the SMF in Chapter 3.2 is selected, but a different SMF may also be selected.

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

[0418] Next, when receiving information (messages, containers, messages) sent from the AMF, the SMF can identify the content of the requests made by the UE and / or the information (messages, containers, messages) received from the AMF.

[0419] Here, SMF can perform a second condition determination. The second condition determination and / or the execution conditions of the second condition determination and / or the criteria for determining the truth or falsehood of the second condition determination and / or the actions when the second condition determination is true or false and / or the control messages sent and received when the second condition determination is true or false can be the same as in Chapter 3.2.

[0420] It should be noted that the second condition check can also be performed by NFs other than SMFs.

[0421] Next, regarding Figure 9 The steps of process (A) will be explained.

[0422] Next, the SMF can select a UPF for the established PDU session, for example, by sending an N4 session establishment request message (S808) to the selected UPF via the N4 interface. Here, it is assumed that the same UPF_230 (hereinafter also referred to as UPF) as the UPF in Chapter 3.2 is selected, but a different UPF can also be selected. The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0423] Next, the UPF can identify the content of the information received from the SMF when it receives the N4 session establishment request message (S808). In addition, the UPF can also send an N4 session establishment response message to the SMF via the N4 interface based on the receipt of the N4 session establishment request message (S810).

[0424] Next, the SMF can identify the content of the information received from the UPF when receiving the N4 session establishment response message, and use it as a response message to the N4 session establishment request message.

[0425] Next, the SMF receives the PDU session establishment request message and / or selects the UPF and / or receives the N4 session establishment response message, for example, via the N11 interface, and sends the N1 SM container and / or N2 SM information and / or PDU session ID to the AMF (S812). Here, the N1 SM container may include a PDU session establishment accept message.

[0426] Next, the AMF that receives the N1 SM container and / or N2 SM information and / or PDU session ID (thirteenth identification information) sends an N2 PDU session request message to the N3IWF (S814). Here, the N2 PDU session request message may include the N2 SM information and / or the NAS message. Furthermore, the NAS message may include the PDU session ID and / or the N1 SM container.

[0427] Next, the N3IWF performs the IPsec child SA (security association) establishment process with the UE via the access network. After the IPsec child SA is established between the UE and the N3IWF, a NAS message is sent to the UE (S816).

[0428] Specifically, the N3IWF sends an IKE Create_Child_SA request message to the UE according to the IKEv2 specification described in RFC 7296 to establish an IPsec Child SA for a PDU session. Here, the IKE Create_Child_SA request message indicates that the requested IPsec Child SA will operate in Tunneling Mode. Furthermore, the IKE Create_Child_SA request message may include the PDU session ID associated with the Child SA.

[0429] Next, when the UE receives the IPsec Child SA, it sends the IKE Create_Child_SA response message to the N3IWF.

[0430] Based on the above, an IPsec Child SA is established between the UE and the N3IWF.

[0431] After establishing the IPsec Child SA, the N3IWF can send a NAS message (S816) to the UE, which includes a PDU session establishment acceptance message.

[0432] Here, the SMF and / or AMF may send at least one of the thirty-first to thirty-seventh identification information in the PDU session establishment accept message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message. Here, the thirty-first to thirty-third, thirty-fifth, and thirty-sixth identification information may be the same as or different from the twenty-first to twenty-third, twenty-fifth, and twenty-sixth identification information of this procedure. However, here, the thirty-first identification information is the same as the twenty-first identification information of this procedure. That is, the thirty-first identification information represents the PDU session ID#3 that identifies the third PDU session.

[0433] Furthermore, the identification information 31 to 37 may be the same as or different from the identification information 31 to 37 in Chapter 3.2. Also, the identification information 31 to 37 may be the same as or different from the identification information 31 to 37 in Chapter 3.6.

[0434] SMF and / or AMF can notify the UE of the contents of these identification information by sending at least one of these identification information.

[0435] Next, when receiving the NAS message (S816), it is possible to identify the content of the UE's request based on the PDU session establishment request message being accepted and / or the information (message, container, information) included in the NAS message.

[0436] The UE can identify the SSC mode set for the PDU session identified by the 31st identification information based on the received 31st and 33rd identification information.

[0437] Next, regarding Figure 9 The process of (B) will be explained step by step.

[0438] First, the SMF receives a PDU session establishment request message, for example, by sending the N1 SM container and / or PDU session ID to the AMF (S818) via the N11 interface. Here, the N1 SM container may include a PDU session establishment rejection message.

[0439] Next, the AMF that received the N1 SM container and / or N2 SM information and / or PDU session ID (thirteenth identification information) sends an N2 PDU session request message to the N3IWF (S820). Here, the N2 PDU session request message may include the N2 SM information and / or the NAS message. Furthermore, the NAS message may include the PDU session ID and / or the N1 SM container.

[0440] Next, the N3IWF performs the IPsec child SA (security association) establishment process with the UE via the access network. After the IPsec child SA is established between the UE and the N3IWF, a NAS message is sent to the UE (S822).

[0441] Specifically, the N3IWF sends an IKE Create_Child_SA request message to the UE according to the IKEv2 specification described in RFC 7296 to establish an IPsec Child SA for a PDU session. Here, the IKE Create_Child_SA request message indicates that the requested IPsec Child SA will operate in Tunneling Mode. Furthermore, the IKE Create_Child_SA request message may include the PDU session ID associated with the Child SA.

[0442] Next, when the UE receives the IPsec Child SA, it sends the IKE Create_Child_SA response message to the N3IWF.

[0443] Based on the above, an IPsec Child SA is established between the UE and the N3IWF.

[0444] After establishing the IPsec Child SA, the N3IWF can send a NAS message (S822) to the UE, which includes a PDU session establishment rejection message.

[0445] Next, when the UE receives the NAS message (S822), it can identify the content of the UE's request based on the PDU session establishment request message being rejected and / or the information (message, container, information) included in the NAS message.

[0446] Each device can complete this process by establishing a receive message based on a PDU transmission and reception session. At this point, each device can transition to a state where it can communicate with the DN using the established PDU session.

[0447] Each device can complete this process by establishing and sending rejection messages based on a PDU session. In this case, each device cannot establish a PDU session, and therefore, cannot communicate with the DN if no PDU session has been established.

[0448] It should be noted that the various processes performed by the UE based on the receipt of each identification information, as described above, can be performed during this process or after the completion of this process, or they can be performed after the completion of this process based on the completion of this process.

[0449] In addition, each device can establish corresponding storage for the information received and sent during this process.

[0450] Furthermore, after completing this process, the UE's SNPN access mode can be either disabled or activated. It should be noted that when managing SNPN access modes per access point, the SNPN access mode for non-3GPP access can be activated, or the SNPN access mode for 3GPP access can remain unchanged.

[0451] Here, we assume that the PDU session has been established and the PDU session in SNPN has been received by accepting the PDU session establishment message.

[0452] As described above, the login procedure and PDU session establishment procedure for the SNPN are performed using the PDU session established in the PLMN through the procedures in Chapter 3.6, thereby enabling the establishment of a PDU session via non-3GPP access. That is, the UE can be in a state where a PDU session in the PLMN and a PDU session in the SNPN have been established.

[0453] As described above, by executing each process, the first PDU session can be transferred to the third PDU session.

[0454] [4. Second Implementation]

[0455] In this embodiment, a method for transferring a third PDU session to a first PDU session will be described in the opposite manner to the first embodiment.

[0456] That is, the UE executes the login procedure in Chapter 4.1 and the PDU session establishment procedure in Chapter 4.2 within the PLMN to establish a second PDU session. Then, via the established second PDU session (i.e., via the PLMN), the UE executes the login procedure in Chapter 4.3 and the PDU session establishment procedure in Chapter 4.4 within the SNPN to establish a third PDU session. The UE can then, as needed, execute the non-login procedure in Chapter 3.3 or the PDU session release procedure in Chapter 3.4 within the SNPN. Then, the UE executes the login procedure in Chapter 3.1 and the PDU session establishment procedure in Chapter 3.2 within the SNPN to establish a first PDU session. This concludes the explanation. By executing these procedures, the UE can transfer the third PDU session to the first PDU session.

[0457] [4.1. Login process for PLMN]

[0458] This procedure can be directly applied to the procedure in Chapter 3.5, so please refer to Chapter 3.5. The UE can be logged into the PLMN when completing this procedure.

[0459] [4.2. PDU Session Establishment Process for PLMN]

[0460] This procedure is executed after the procedure in Chapter 4.1. This procedure can directly apply the procedure in Chapter 3.6, so please refer to Chapter 3.6. When the UE completes this procedure, it can be in a state where a second PDU session has been established in the PLMN.

[0461] [4.3. (Regarding the SNPN login process via PLMN)]

[0462] This procedure is executed after the procedure in Chapter 4.2. This procedure can directly apply the procedure in Chapter 3.7, so please refer to Chapter 3.7. Upon completion of this procedure, the UE can be in a state where it is already logged into the SNPN via the PLMN.

[0463] [4.4. PDU Session Establishment Process for SNPN (via PLMN)]

[0464] This procedure is executed after the procedure in Chapter 4.3. This procedure can directly apply the procedure in Chapter 3.8, so please refer to Chapter 3.8. Upon completion of this procedure, the UE can be in a state where a third PDU session has been established in the SNPN via the PLMN. That is, the UE can be in a state where both a second and third PDU session have been established.

[0465] [4.5. Non-login procedures in SNPN (via PLMN)]

[0466] Next, the non-login procedure in the SNPN via the PLMN executed by the UE that has completed the procedures in Chapter 4.4 will be described. At this time, the UE's SNPN access mode can be either disabled or activated. It should be noted that, in the case of SNPN access mode managed per access point, the non-login procedure in the SNPN via the PLMN can be initiated by a UE in a state where the SNPN access mode for non-3GPP access is activated. At this time, the SNPN access mode for 3GPP access can be activated or disabled, but ideally it should be disabled. Hereinafter, the non-login procedure in the SNPN via the PLMN will also be referred to as the non-login procedure or this procedure. There are network-led non-login procedures and UE-led non-login procedures. The non-login procedure can be a procedure used to de-login a UE that has logged into the network (access network and / or core network and / or DN). In other words, the UE or AMF can execute the non-login procedure while the UE is in a state already logged into the network (RM-REGISTERED state or 5GMM-REGISTEDED state). Furthermore, if the UE is detected to have entered an area where it can communicate directly with the SNPN, each device can perform a non-login procedure. In particular, this procedure can be performed when a PDU session configured as SSC mode2 is being established.

[0467] When the UE completes this process, its login status in the SNPN via the PLMN can be either non-login or the third PDU session has been released. That is, the UE can also maintain its login status in the PLMN while the second PDU session remains established. [4.5.1 Network-led Non-login Process]

[0468] First, use Figure 3 , Figure 4 as well as Figure 10 This section describes the network-driven non-login process. Hereinafter, the network-driven non-login process in the SNPN via the PLMN will also be referred to as the non-login process or this process.

[0469] The AMF_210 (hereinafter also referred to as AMF) sends a non-login request (DEREGISTRATION REQUEST) message to the UE (S900) via N3IWF_240 (hereinafter also referred to as N3IWF) and a non-3GPP access, thereby initiating this procedure. Here, the non-3GPP access can consist of access network_102, core network_202, and DN_252. The non-login request message is a NAS message transmitted and received on the N1 interface.

[0470] Furthermore, the AMF may include at least one of the identification information from 41 to 43 in the non-login request message. It should be noted that whether the non-login request message includes any of the identification information from 41 to 43 can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the twenty-fourth identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for handover between the SNPN and PLMN, the AMF may include at least one of the identification information from 41 to 43 in the non-login request message.

[0471] In addition, the AMF can send at least one of these identification information and / or a non-login request message to request the change of the UE's login state in the SNPN via the PLMN to a non-login state, and / or to request the release of a PDU session established in the SNPN via the PLMN, and / or to instruct the start of the login process and / or PDU session establishment process for the SNPN, and / or to instruct the start of the PDU session release process for releasing the PDU session established in the PLMN, and / or to instruct the change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and / or to instruct the change from a PDU session established to the SNPN via the PLMN to a PDU session directly established to the SNPN, and / or to instruct the activation of the SNPN access mode.

[0472] When the UE receives a non-login request message from the AMF, it can identify the content of each identification information included in the non-login request message. Moreover, the UE can determine its actions based on the reception of the non-login request message and / or each identification information.

[0473] That is, the UE can change the UE's login state in the SNPN via the PLMN to a non-login state, release the PDU session established in the SNPN via the PLMN, start the login process and / or PDU session establishment process for the SNPN, start the PDU session release process for releasing the PDU session established in the PLMN, and trigger the execution of the process for changing the connection from the PLMN to the SNPN to a direct connection to the SNPN.

[0474] Furthermore, the UE that receives the non-login request message can send a non-login acceptance (DEREGISTRATION ACCEPT) message (S902) to the AMF via the non-3GPP access and N3IWF. Here, the non-login acceptance message is a NAS message transmitted and received on the N1 interface.

[0475] Each device can transition to a state where the UE is not logged into the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of non-login received messages. Furthermore, this state transition implemented by each device can be based on the completion of this process.

[0476] Furthermore, each device can perform processing based on the information transmitted and received during the non-login process based on the completion of the non-login process. For example, based on the completion of the non-login process, the UE can start the login process for the PLMN, activate the SNPN access mode, or disable the SNPN access mode. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access. It should be noted that the UE can activate or disable the SNPN access mode based on the transmission and reception of non-login request messages and / or non-login accept messages and / or various identification information. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access.

[0477] [4.5.2 UE-led non-login process]

[0478] Next, use Figure 3 , Figure 4 as well as Figure 11 This section describes the UE-led non-login process. Hereinafter, the UE-led non-login process in SNPN will also be referred to as the non-login process or this process. The UE initiates this process by sending a non-login request (DEREGISTRATION REQUEST) message to AMF_210 (hereinafter also referred to as AMF) (S1000) via a non-3GPP access network and N3IWF_240 (hereinafter also referred to as N3IWF). Here, the non-3GPP access network can consist of access network_102, core network_202, and DN_252. Here, the non-login request message is a NAS message sent and received on the N1 interface.

[0479] Furthermore, the UE may include at least one of the identification information from 51 to 53 in the non-login request message. It should be noted that whether the non-login request message includes any of the identification information from 51 to 53 can be determined based on the first identification information sent during the login process performed prior to this procedure and / or the twenty-fourth identification information sent during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for handover between the SNPN and PLMN, the UE may include at least one of the identification information from 51 to 53 in the non-login request message.

[0480] When the AMF receives a non-login request message from the UE, it can determine the AMF's action based on the reception of the non-login request message and / or identification information.

[0481] For example, the AMF that receives the non-login request message can send a non-login acceptance (DEREGISTRATION ACCEPT) message (S1002) to the UE via the N3IWF and non-3GPP access. Here, the non-login acceptance message is a NAS message sent and received on the N1 interface.

[0482] Furthermore, the AMF may include the sixty-second identification information in the non-login acceptance message. It should be noted that whether the sixty-second identification information is included in the non-login acceptance message can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the twenty-fourth identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for handover between the SNPN and PLMN, the AMF may include the sixty-second identification information in the non-login acceptance message.

[0483] In addition, the AMF can send at least one of these identification messages and / or a non-login acceptance message to request to change the login state of the UE in the SNPN via the PLMN to a non-login state, and / or to request to release a PDU session established in the SNPN via the PLMN, and / or to instruct to start a login process and / or PDU session establishment process for the SNPN, and / or to instruct to start a PDU session release process for releasing a PDU session established in the PLMN, and / or to instruct to change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and / or to instruct to change a PDU session established to the SNPN via the PLMN to a PDU session established directly to the SNPN, and / or to instruct to activate the SNPN access mode.

[0484] When the UE receives a non-login acceptance message from the AMF, it can identify the content of each identification information included in the non-login acceptance message. Moreover, the UE can determine its actions based on the reception of the non-login acceptance message and / or each identification information.

[0485] That is, the UE can change the UE's login state in the SNPN via the PLMN to a non-login state, release the PDU session established in the SNPN via the PLMN, start the login process and / or PDU session establishment process for the SNPN, start the PDU session release process for releasing the PDU session established in the PLMN, and trigger the execution of the process for changing the connection from the PLMN to the SNPN to a direct connection to the SNPN.

[0486] Each device can transition to a state where the UE is not logged into the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of non-login received messages. Furthermore, this state transition implemented by each device can be based on the completion of this process.

[0487] Furthermore, each device can perform processing based on the information transmitted and received during the non-login process based on the completion of the non-login process. For example, based on the completion of the non-login process, the UE can start the login process for the PLMN, activate the SNPN access mode, or disable the SNPN access mode. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access. It should be noted that the UE can activate or disable the SNPN access mode based on the transmission and reception of non-login request messages and / or non-login accept messages and / or various identification information. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access.

[0488] [4.6. PDU Session Release Procedure in SNPN (via PLMN)]

[0489] Next, the PDU session release procedure via the PLMN's SNPN, executed by the UE following the procedures in Chapter 4.4, will be explained. At this time, the UE's SNPN access mode can be either disabled or activated. It should be noted that, in the case of SNPN access mode managed per access point, the PDU session establishment procedure via the PLMN's SNPN can be initiated by a UE in a state where the SNPN access mode for non-3GPP access is activated. At this time, the SNPN access mode for 3GPP access can be activated or disabled, but ideally disabled. Hereinafter, the PDU session release procedure via the PLMN's SNPN will also be referred to as the PDU session release procedure or this procedure. There are network-led and UE-led PDU session release procedures. The PDU session release procedure can be used to release a PDU session. Furthermore, when it is detected that the UE has left the communicable area of ​​the SNPN, each device can execute the PDU session release procedure. In particular, this procedure can be executed when a PDU session set to SSC mode 2 is being established.

[0490] When the UE completes this process, it can be in a state where the third PDU session in the SNPN via the PLMN has been released. That is, the UE can also maintain its logged-in state in the PLMN, and the second PDU session can also remain established. It should be noted that the UE can maintain its logged-in state in the SNPN via the PLMN, but can also be in a non-login state afterwards.

[0491] [4.6.1 Network-led PDU session release process]

[0492] First, use Figure 3 , Figure 4 as well as Figure 12 This document describes the network-led PDU session release procedure. Hereinafter, the network-led PDU session release procedure via the PLMN's SNPN will also be referred to as the PDU session release procedure or this procedure. The SMF_220 (hereinafter also called SMF) initiates this procedure by sending a PDU session release command (PDU SESSION RELEASE COMMAND) message to the UE (S1002) via AMF_210 (hereinafter also called AMF), N3IWF_240 (hereinafter also called N3IWF), and non-3GPP access. Here, non-3GPP access can consist of access network_102, core network_202, and DN_252. Here, the PDU session release command message is a message included in the NAS messages transmitted and received on the N1 interface.

[0493] Furthermore, the SMF may send the PDU session release command message including at least one of the identification information from 71 to 75. It should be noted that whether the PDU session release command message includes any of the identification information from 71 to 75 can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the twenty-fourth identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the twenty-fourth identification information indicate support for handover between SNPN and PLMN, the SMF may send the PDU session release command message including at least one of the identification information from 71 to 75. It should be noted that the seventy-first identification information may represent PDU session ID #3 identifying a third PDU session. Furthermore, the seventy-fourth identification information may represent PDU session ID #2 identifying a second PDU session. Additionally, if the PDU session release command message includes both the seventy-first and seventy-fourth identification information, the seventy-third identification information may represent 3GPP access and non-3GPP access corresponding to the PDU sessions indicated by the seventy-first and seventy-fourth identification information. Furthermore, if the PDU session release command message includes the 71st identification information but not the 74th identification information, the 73rd identification information can represent the non-3GPP access corresponding to the PDU session indicated by the 71st identification information.

[0494] In addition, the SMF can send at least one of these identification information and / or a PDU session release command message to instruct the release of a PDU session established in the SNPN via the PLMN, and / or to initiate a login process and / or PDU session establishment process for the SNPN, and / or to initiate a PDU session release process for releasing a PDU session established in the PLMN, and / or to change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and / or to change a PDU session established in the SNPN via the PLMN to a PDU session established directly in the SNPN, and / or to activate the SNPN access mode.

[0495] When the UE receives a PDU session release command message from the SMF, it can identify the content of each identification information included in the PDU session release command message. Moreover, the UE can determine its actions based on the reception of the non-login request message and / or each identification information.

[0496] That is, the UE can release a PDU session established in the SNPN via the PLMN, start a login process and / or PDU session establishment process for the SNPN, start a PDU session release process for releasing the PDU session established in the PLMN, determine to change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and determine to change a PDU session established in the SNPN via the PLMN to a PDU session established directly in the SNPN.

[0497] Furthermore, the UE that receives the PDU session release command can send a PDU session release complete message to the SMF via non-3GPP access, N3IWF, and AMF. Here, the PDU session release complete message is included in the NAS messages sent and received by the AMF on the N1 interface.

[0498] Furthermore, each device can process the information sent and received during the PDU session release process upon its completion. For example, upon completion of the PDU session release process, the UE can begin the PLMN login process, activate the SNPN access mode, or disable the SNPN access mode. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access. It should also be noted that the UE can activate or disable the SNPN access mode based on the transmission and reception of the PDU session release command and / or the PDU session release completion message and / or various identification information. Again, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access.

[0499] Furthermore, based on the receipt of a PDU session release command that includes the 74th identification information, or based on the receipt of a PDU session release command that includes the 74th identification information, the UE can determine to begin the procedures outlined in Chapter 4.7. Conversely, based on the receipt of a PDU session release command that does not include the 74th identification information, or based on the receipt of a PDU session release command that includes the 74th identification information, the UE can determine not to begin the procedures outlined in Chapter 4.7.

[0500] [4.6.2 UE-led PDU session release process]

[0501] Next, use Figure 3 , Figure 4 as well as Figure 12 This document describes the UE-led PDU session release procedure. Hereinafter, the UE-led PDU session release procedure via the PLMN's SNPN will also be referred to as the PDU session release procedure or this procedure. The UE initiates this procedure by sending a PDU session release request (PDU SESSION RELEASE REQUEST) message to SMF_220 (hereinafter also called SMF) (S1000) via non-3GPP access, N3IWF_240 (hereinafter also called N3IWF), and AMF_210 (hereinafter also called AMF). Here, non-3GPP access can consist of access network_102, core network_202, and DN_252. Here, the PDU session release request message is a message included in the NAS messages sent and received on the N1 interface.

[0502] Furthermore, the UE may include the 81st identification information in the PDU session release request message. It should be noted that whether the 81st identification information is included in the PDU session release request message can be determined based on the first identification information sent during the login process prior to this procedure and / or the 24th identification information sent during the PDU session establishment process prior to this procedure. For example, if the first identification information and / or the 24th identification information indicate support for handover between the SNPN and PLMN, the UE may include the 81st identification information in the PDU session release request message. It should be noted that the 81st identification information may represent the PDU session ID#3 identifying the third PDU session.

[0503] When the SMF receives a PDU session release request message from the UE, it can determine the SMF's action based on the receipt of the PDU session release request message.

[0504] For example, the SMF may send the PDU session release command message including at least one of the 71st to 75th identification information (S1002). It should be noted that whether the PDU session release command message includes any of the 71st to 75th identification information can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the 24th identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the 24th identification information indicate support for handover between the SNPN and PLMN, the SMF may send the PDU session release command message including at least one of the 71st to 75th identification information. It should be noted that the 71st identification information may represent PDU session ID #3 identifying a third PDU session. Furthermore, the 74th identification information may represent PDU session ID #2 identifying a second PDU session. Moreover, if the PDU session release command message includes both the 71st and 74th identification information, the 73rd identification information may represent 3GPP access and non-3GPP access corresponding to the PDU sessions indicated by the 71st and 74th identification information. Furthermore, if the PDU session release command message includes the 71st identification information but not the 74th identification information, the 73rd identification information can represent the non-3GPP access corresponding to the PDU session indicated by the 71st identification information.

[0505] In addition, the SMF can send at least one of these identification information and / or a PDU session release command message to instruct the release of a PDU session established in the SNPN via the PLMN, and / or to initiate a login process and / or PDU session establishment process for the SNPN, and / or to initiate a PDU session release process for releasing a PDU session established in the PLMN, and / or to change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and / or to change a PDU session established in the SNPN via the PLMN to a PDU session established directly in the SNPN, and / or to activate the SNPN access mode.

[0506] When the UE receives a PDU session release command message from the SMF, it can identify the content of each identification information included in the PDU session release command message. Moreover, the UE can determine its actions based on the reception of the non-login request message and / or each identification information.

[0507] That is, the UE can release a PDU session established in the SNPN via the PLMN, start a login process and / or PDU session establishment process for the SNPN, start a PDU session release process for releasing the PDU session established in the PLMN, determine to change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and determine to change a PDU session established in the SNPN via the PLMN to a PDU session established directly in the SNPN.

[0508] Furthermore, the UE that receives the PDU session release command can send a PDU session release complete message to the SMF via non-3GPP access, N3IWF, and AMF. Here, the PDU session release complete message is included in the NAS messages sent and received by the AMF on the N1 interface.

[0509] Furthermore, each device can process the information sent and received during the PDU session release process upon its completion. For example, upon completion of the PDU session release process, the UE can begin the PLMN login process, activate the SNPN access mode, or disable the SNPN access mode. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access. It should also be noted that the UE can activate or disable the SNPN access mode based on the transmission and reception of the PDU session release command and / or the PDU session release completion message and / or various identification information. Again, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access.

[0510] Furthermore, based on the receipt of a PDU session release command that includes the 74th identification information, or based on the receipt of a PDU session release command that includes the 74th identification information, the UE can determine to begin the procedures outlined in Chapter 4.7. Conversely, based on the receipt of a PDU session release command that does not include the 74th identification information, or based on the receipt of a PDU session release command that includes the 74th identification information, the UE can determine not to begin the procedures outlined in Chapter 4.7.

[0511] [4.7. PDU Session Release Process for PLMN]

[0512] This procedure is executed after the procedure in Chapter 4.6. Then, using... Figure 3 , Figure 4 as well as Figure 12 This section describes the UE-led PDU session release procedure. At this time, the UE's SNPN access mode may be disabled. It should be noted that, in the case of SNPN access mode managed per access point, a UE in a state where the SNPN access mode for 3GPP access is disabled can initiate a non-login procedure via the PLMN's SNPN. In this case, the SNPN access mode for non-3GPP access can be activated or disabled, but ideally it should be disabled. Hereinafter, the UE-led PDU session release procedure in the PLMN will also be referred to as the PDU session release procedure or this procedure. The UE initiates this procedure by sending a PDU session release request (PDU SESSION RELEASE REQUEST) message to SMF_222 (hereinafter also referred to as SMF) (S1000) via 3GPP access (access network_102) and AMF_212 (hereinafter also referred to as AMF). Here, the PDU session release request message is a message included in the NAS messages sent and received on the N1 interface.

[0513] Furthermore, the UE may include the 81st identification information in the PDU session release request message. It should be noted that whether the 81st identification information is included in the PDU session release request message can be determined based on the first identification information sent during the login process prior to this procedure and / or the 24th identification information sent during the PDU session establishment process prior to this procedure. For example, if the first identification information and / or the 24th identification information indicate support for handover between the SNPN and PLMN, the UE may include the 81st identification information in the PDU session release request message. It should be noted that the 81st identification information may represent the PDU session ID#2 identifying the second PDU session.

[0514] When the SMF receives a PDU session release request message from the UE, it can determine the SMF's action based on the receipt of the PDU session release request message.

[0515] For example, the SMF may send the PDU session release command message including at least one of the identification information from the 71st to 73rd and 75th segments (S1002). It should be noted that whether the PDU session release command message includes any of the identification information from the 71st to 73rd and 75th segments can be determined based on the first identification information obtained during the login process performed prior to this procedure and / or the 24th identification information obtained during the PDU session establishment process performed prior to this procedure. For example, if the first identification information and / or the 24th identification information indicate support for switching between the SNPN and PLMN, the SMF may send the PDU session release command message including at least one of the identification information from the 71st to 73rd and 75th segments. It should be noted that the 71st identification information may represent the PDU session ID#2 identifying the second PDU session.

[0516] In addition, the SMF can send at least one of these identification information and / or a PDU session release command message to indicate the release of a PDU session established in the PLMN, and / or the initiation of a login process and / or PDU session establishment process for the SNPN, and / or the change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and / or the change from a PDU session established to the SNPN via the PLMN to a PDU session established directly to the SNPN, and / or the activation of the SNPN access mode.

[0517] When the UE receives a PDU session release command message from the SMF, it can identify the content of each identification information included in the PDU session release command message. Moreover, the UE can determine its actions based on the reception of the non-login request message and / or each identification information.

[0518] That is, the UE can release the PDU session established in the PLMN, start the login process and / or PDU session establishment process for the SNPN, determine to change from a connection to the SNPN via the PLMN to a direct connection to the SNPN, and determine to change the PDU session established to the SNPN via the PLMN to a PDU session established directly to the SNPN.

[0519] Furthermore, the UE that receives the PDU session release command can send a PDU session release complete message to the SMF via non-3GPP access, N3IWF, and AMF. Here, the PDU session release complete message is included in the NAS messages sent and received by the AMF on the N1 interface.

[0520] Furthermore, each device can process the information sent and received during the PDU session release process upon its completion. For example, upon completion of the PDU session release process, the UE can begin the PLMN login process, activate the SNPN access mode, or disable the SNPN access mode. It should be noted that, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access. It should also be noted that the UE can activate or disable the SNPN access mode based on the transmission and reception of the PDU session release command and / or the PDU session release completion message and / or various identification information. Again, in the case of managing SNPN access modes per access point, the SNPN access mode for 3GPP access can be activated or disabled, as can the SNPN access mode for non-3GPP access.

[0521] When the UE completes this process, it may be in a state where the second PDU session in the PLMN has been released. It should be noted that the UE maintains its logged-in state in the PLMN, but it may also be in a non-logged-in state afterwards.

[0522] [4.8. Login process for SNPN]

[0523] This procedure can be executed after completing the procedures in Chapters 4.1 to 4.4. Alternatively, it can be executed after completing the procedures in Chapters 4.1 to 4.4, followed by the procedures in Chapters 4.5 or 4.6. Furthermore, it can be executed after completing the procedures in Chapters 4.1 to 4.4, followed by the procedures in Chapters 4.6 to 4.7. This procedure can directly apply the procedures in Chapter 3.1; therefore, please refer to Chapter 3.1. Upon completing this procedure, the UE can be in a state where it is already logged into SNPN.

[0524] [4.9. PDU Session Establishment Process for SNPN]

[0525] This procedure can be executed after the procedure in Chapter 4.8. This procedure can directly apply the procedure in Chapter 3.2, so please refer to Chapter 3.2. When the UE completes this procedure, it can be in a state where the first PDU session has been established in the SNPN.

[0526] As described above, by executing each process, the third PDU session can be transferred to the first PDU session.

[0527] [5. Improved Example]

[0528] The program operating in the apparatus of this invention can be a program that controls a central processing unit (CPU) or other computer to perform functions in order to achieve the functions of the embodiments of this invention. The program or the information processed by the program is temporarily stored in volatile memory such as random access memory (RAM) or non-volatile memory such as flash memory, hard disk drive (HDD) or other storage device systems.

[0529] It should be noted that programs used to implement the functions of the embodiments involved in this invention can also be recorded in a computer-readable recording medium. This can be achieved by reading the program recorded in the recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into a device, including hardware such as an operating system and peripherals. Furthermore, the "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium for short-term dynamic storage of programs, or other computer-readable recording media.

[0530] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be installed or executed by electronic circuits such as integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware components, or combinations thereof. General-purpose processors may be microprocessors, or processors, controllers, microcontrollers, or state machines of conventional types. The aforementioned electronic circuits may be constructed from digital circuits or analog circuits. Furthermore, in cases where advancements in semiconductor technology have led to the emergence of integrated circuit technologies that replace current integrated circuits, one or more embodiments of the present invention may also utilize new integrated circuits based on such technologies.

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

[0532] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the technical solutions shown, and embodiments obtained by appropriately combining technical solutions disclosed in different embodiments are also included within the technical scope of the present invention. In addition, it also includes configurations obtained by replacing elements that have the same effect as those described in the above embodiments with each other.

Claims

1. A user equipment (UE), characterized in that, The UE includes a control unit and a transceiver unit. When using 3GPP access and Independent Non-Public Network (SNPN) service connection, the control unit is configured so that the UE operates in SNPN access mode on the 3GPP access; during the SNPN login process, the transceiver unit sends a login request message to the SNPN via the 3GPP access. When using 3GPP access to access SNPN service via Public Land Mobile Network (PLMN), the control unit is configured to operate in the SNPN access mode when the UE is on non-3GPP access; during the login process for the SNPN, the transceiver unit sends the login request message to the SNPN via the non-3GPP access.

2. The UE according to claim 1, characterized in that, When using the 3GPP access to connect to the SNPN service via the PLMN, the control unit is configured so that the UE operates on the 3GPP access without SNPN access mode.

3. A communication control method executed by a user equipment (UE), characterized in that, When using 3GPP access and Independent Non-Public Network (SNPN) service connection, the UE operates in SNPN access mode on the 3GPP access; during the SNPN login process, it sends a login request message to the SNPN via the 3GPP access. When using 3GPP access to access SNPN services via a Public Land Mobile Network (PLMN), the UE operates in the SNPN access mode on a non-3GPP access basis; during the login process for the SNPN, the UE sends the login request message to the SNPN via the non-3GPP access.

Images