UE (User Equipment) and communication control method

Abstract

When a UE (user equipment) moves between PLMNs (Public Land Mobile Networks) and / or NPNs (Non-Public Networks) in a 5GS (5G System), the control processing of the UE and the control processing of a control device in a core network are unclear. The present invention provides a communication means for transitioning the UE state to a new state when a UE moves between PLMNs, moves between NPNs or moves between a PLMN and an NPN in a 5GS. Furthermore, the present invention provides a communication means for removing the limitation on the UE imposed by the control device in the core network when the UE moves between PLMNs, between NPNs or between a PLMN and an NPN in a 5GS.

Description

[Technical field]

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

[0002] The 3GPP (3rd Generation Partnership Project) has begun studying the system architecture of 5GS (5G System), the next-generation, or fifth-generation (5G), mobile communications system, and is discussing support for new procedures and new functions (see Non-Patent Documents 1, 2, 3, and 4).

[0003] For example, requirements include the optimization and diversification of communication procedures to support continuous mobile communication services in response to a wide variety of services, and the optimization of system architecture to match the optimization and diversification of communication procedures. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 23.501 v16.4.0 (2020-03); Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16) [Non-Patent Document 2] 3GPP TS 23.502 v16.4.0 (2020-03); Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16) [Non-Patent Document 3] 3GPP TS 24.501 v16.4.1 (2020-03); Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) [Non-Patent Document 4] 3GPP TR 23.700-07 v0.3.0 (2020-01); Technical Specification Group Services and System Aspects; Study on enhanced support of non-public networks (Release 17) Summary of the Invention [Problem to be solved by the invention]

[0005] In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered to provide a wide variety of services. In addition, in 5GS, the provision of a private network that can be used by specific users for specific purposes, such as NPN (Non-Public Network), which is defined separately from PLMN (Public Land Mobile Network), a public network, and the function to realize a private network are also being considered.

[0006] However, when a UE (User Equipment) is registered with the NPN, the processing by the core network control device and the processing by the UE are not clear.

[0007] One aspect of the present invention has been made in consideration of the above-mentioned circumstances, and its purpose is to provide a method for implementing processing by a core network control device and processing by a UE in 5GS when a UE is registered in an NPN. [Means for solving the problem]

[0008] One embodiment of the present invention relates to a UE (User Equipment; terminal device), which includes a transceiver unit and a control unit that transmits a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to a control device, and receives a PDU session establishment acceptance message including a reason value from the control device, wherein the PDU session type is set to IPv4v6, the reason value is a 50th 5GSM (5G Session Management) reason value indicating that only IPv4 PDU session types are allowed, and further, when the UE is registered in an SNPN (Stand-alone Non-Public Network), the control unit configures the transceiver unit so that a UE-requested PDU session establishment procedure for a PDU session type for which the DNN, the S-NSSAI, and IPv6 are set is not initiated until the UE is registered in a PLMN (Public land mobile network).Furthermore, a UE (User Equipment; terminal device) of one embodiment of the present invention is characterized in that it comprises a transceiver unit and a control unit that transmit a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to a control device, and receives a PDU session establishment acceptance message including a reason value from the control device, wherein the PDU session type is set to IPv4v6, the reason value is a 51st 5GSM (5G Session Management) reason value indicating that only IPv6 PDU session types are allowed, and further, when the UE is registered in an SNPN (Stand-alone Non-Public Network), the control unit configures the transceiver unit so that a PDU session establishment procedure requested by the UE for a PDU session type for which the DNN, the S-NSSAI, and IPv4 are set is not initiated until the UE is registered in a PLMN (Public land mobile network).

[0009] A communication control method for a UE (User Equipment; terminal device) according to one embodiment of the present invention includes the steps of: transmitting a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to a control device; and receiving a PDU session establishment accept message including a reason value from the control device, wherein the PDU session type is set to IPv4v6, the reason value is a 50th 5GSM (5G Session Management) reason value indicating that only IPv4 PDU session types are allowed, and further, when the UE is registered in an SNPN (Stand-alone Non-Public Network), the UE is configured so that a UE-requested PDU session establishment procedure for a PDU session type for which the DNN, the S-NSSAI, and IPv6 are set is not initiated until the UE is registered in a PLMN (Public land mobile network).Furthermore, a communication control method for a UE (User Equipment; terminal device) of one embodiment of the present invention includes a step of sending a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to a control device, and a step of receiving a PDU session establishment acceptance message including a reason value from the control device, wherein the PDU session type is set to IPv4v6, the reason value is a 51st 5GSM (5G Session Management) reason value indicating that only IPv6 PDU session types are allowed, and further, when the UE is registered in an SNPN (Stand-alone Non-Public Network), the UE is configured so that a UE-requested PDU session establishment procedure for a PDU session type for which the DNN, the S-NSSAI, and IPv4 are set is not initiated until the UE is registered in a PLMN (Public land mobile network). Effect of the Invention

[0010] According to one aspect of the present invention, in 5GS, it is possible to realize the control process of the control device in the core network and the control process of the UE when the UE moves between PLMNs or NPNs. Furthermore, in 5GS, it is also possible to realize the control process of the control device in the core network and the control process of the UE when the UE moves between PLMNs and SNPNs. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). [Diagram 2] A diagram explaining the detailed configuration of a mobile communication system (EPS / 5GS). [Diagram 3] A diagram explaining the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Diagram 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 1 is a diagram for explaining procedures 1 to 4. [Figure 7] FIG. 1 is a diagram illustrating a registration procedure. [Figure 8] A diagram explaining the PDU session establishment procedure. [Figure 9] FIG. 1 is a diagram explaining an RRC connection release procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS With reference to the drawings, a best mode for carrying out one embodiment of the present invention will be described.

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

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

[0015] In the following, these devices and functions may be described with abbreviated symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

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

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

[0018] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

[0019] The UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, non-3GPP AN). The UE may be a terminal device capable of wireless communication such as a mobile phone or a smartphone, and may be a terminal device that can connect to both EPS and 5GS. The UE may include a Universal Integrated Circuit Card (UICC) or an Embedded UICC (eUICC). The UE may be expressed as a user device or a terminal device.

[0020] Moreover, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. In the E-UTRAN, one or more eNBs (evolved Node B) 45 are arranged. In the following, the eNB 45 may be written with the symbol omitted, such as eNB. In addition, when there are multiple eNBs, the eNBs are connected to each other, for example, by an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.

[0021] Moreover, the access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are arranged in the NG-RAN. In the following, the gNB 122 may be described with the symbol omitted, such as eNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, the gNB is a base station device newly designed for the 5GS, and has a different function from the base station device (eNB) used in the EPS, which is a 4G system. In addition, when there are multiple gNBs, each gNB is connected to each other, for example, by an Xn interface.

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

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

[0024] Moreover, the core network_A corresponds to an EPC (Evolved Packet Core). In the EPC, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), an HSS (Home Subscriber Server), etc. are arranged.

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

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

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

[0028] Also, in FIG. 1, the PDN and the DN are the same, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a communication terminal connected thereto. Therefore, connecting to the PDN may be connecting to a communication terminal or a server device arranged in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may be transmitting and receiving user data to and from a communication terminal or a server device arranged in the PDN. The PDN may be expressed as the DN, and the DN may be expressed as the PDN.

[0029] In addition, in the following, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device transmits or receives a message and / or executes a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein transmits or receives a message and / or executes a procedure.

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

[0031] Here, IP communication refers to data communication using IP, and data is transmitted and received by IP packets. The IP packet is composed of an IP header and a payload section. The payload section may include data transmitted and received by devices and functions included in EPS and devices and functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by transmitting and receiving application data to which an IP header is not attached, or may be user data transmitted and received by a UE with another header such as a MAC header or an Ethernet (registered trademark) frame header attached.

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

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

[0034] [2.1. UE device configuration] First, an example of the device configuration of UE (User Equipment) will be described with reference to Fig. 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

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

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

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

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

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

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

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

[0042] The transceiver unit _B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information between the UE and the transceiver unit _B530.

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

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

[0045] [2.3. AMF device configuration] Next, an example of the device configuration of the AMF will be described with reference to Figure 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The AMF may be a node that handles the control plane.

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

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

[0048] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, the AMF can transmit and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN. In addition, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

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

[0050] In addition, the AMF has a function of exchanging control messages with the RAN using the N2 interface, a function of exchanging NAS messages with the UE using the N1 interface, a function of encrypting and protecting the integrity of NAS messages, a registration management (RM) function, a connection management (CM) function, a reachability management function, a mobility management function for UEs, etc., a function of transferring SM (Session Management) messages between the UE and the SMF, an access authentication (access authorization) function, a security anchor functionality (SEA), a security context management (SCM) function, a function of supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function of supporting the transmission and reception of NAS signals with the UE via the N3IWF, and a function of authenticating UEs connected via the N3IWF.

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

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

[0053] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which the location information of UE_A10 is not known to the network, or a state in which the network cannot reach UE_A10. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or establish a 5GMM context by executing the registration procedure.

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

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

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

[0057] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be an NF that manages one or more NSIs (Network Slice Instances). In addition, the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared between multiple NSIs.

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

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

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

[0061] The network connection unit _B720 is a functional unit for connecting the SMF to the AMF, and / or the UPF, and / or the PCF, and / or the UDM. In other words, the SMF can use the network connection unit _B720 to transmit and receive user data and / or control information between the AMF, and / or the UPF, and / or the PCF, and / or the UDM.

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

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

[0064] The SMF has a session management function such as establishing, modifying, and releasing PDU sessions, an IP address allocation for UEs and its management function, a UPF selection and control function, a UPF setting function for routing traffic to the appropriate destination (destination), a function for sending and receiving the SM part of NAS messages, a function for notifying that downlink data has arrived (Downlink Data Notification), a function for providing AN-specific (for each AN) SM information that is sent to the AN via the N2 interface via the AMF, a function for determining the SSC mode (Session and Service Continuity mode) for the session, and a roaming function.

[0065] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be described with reference to Fig. 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

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

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

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

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

[0070] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a function for forwarding user data as a gateway between DN and core network_B), a packet routing and forwarding function, a UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows for one DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, a downlink packet buffering function, and a function for triggering downlink data notification.

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

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

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

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

[0075] [2.6. Description of other equipment and / or functions] Next, other devices and / or functions will be described.

[0076] The PCF has a function of providing policy rules.

[0077] The UDM also has an authentication credential processing function, a user identification processing function, an access authentication function, a registration / mobility management function, a subscription management function, and the like.

[0078] The PCRF is connected to the PGW and / or the PDN and has a function of managing QoS for data delivery. For example, the PCRF manages the QoS of the communication path between the UE_A10 and the PDN. The PCRF may also be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when transmitting and receiving user data.

[0079] The HSS is connected to the MME and / or the SCEF and has a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, when controlling access to the MME. Furthermore, the HSS may be connected to a location management device different from the MME.

[0080] The SCEF is connected to the DN and / or PDN, the MME, and the HSS, and has a function as a relay device that transfers user data as a gateway connecting the DN and / or PDN with the core network_A. The SCEF may be a gateway for non-IP communication. The SCEF may also have a function of converting between non-IP communication and IP communication. A plurality of such gateways may be arranged in the core network_A. The SCEF may be configured outside or inside the core network.

[0081] [3. Explanation of terms, identification information, and procedures used in each embodiment] At least one term, identification information, and procedure used in each embodiment will be explained in advance.

[0082] [3.1. Explanation of terms and identification information used in each embodiment] First, highly specialized terms used in each embodiment and identification information used in the procedures will be explained in advance.

[0083] The network refers to at least a part of the access network _B, the core network _B, and the DN. Furthermore, one or more devices included in at least a part of the access network _B, the core network _B, and the DN may be referred to as a network or a network device. In other words, when a network transmits, receives, and / or processes messages, it may mean that a device in the network (a network device and / or a control device) transmits, receives, and / or processes messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, and / or processes messages.

[0084] Furthermore, the network may refer to a PLMN (Public Land Mobile Network) or an NPN, which will be described later. Furthermore, when it is expressed that the UE performs network selection, it may indicate that the UE performs PLMN selection or that the UE performs SNPN selection.

[0085] Moreover, a registered PLMN refers to a PLMN in which a UE is registered.

[0086] An equivalent PLMN is a PLMN that is treated by a network as if it were the same PLMN as any other PLMN. For example, an equivalent PLMN may be one or more PLMNs that are treated the same as a registered PLMN.

[0087] Furthermore, an SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in a procedure for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session completion message, a PDU session rejection message, a PDU session change request message, a PDU session change acceptance message, a PDU session change response message, etc. Furthermore, the procedure for SM may include a PDU session establishment procedure.

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

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

[0090] In addition, single registration mode is a mode in which UE_A10 maintains a common registration state for 5GMM state and EMM state when N1 mode and S1 mode are available.

[0091] In addition, the dual registration mode is a mode in which UE_A10 maintains the registration state of 5GMM state and EMM state independently when N1 mode and S1 mode are available. In addition, in the case of the dual registration mode, UE_A10 may be registered in the network only in N1 mode (i.e., registered only in 5GC), may be registered in the network only in S1 mode (registered only in EPC), or may be registered in the network in both N1 mode and S1 mode (registered in both 5GC and EPC).

[0092] In addition, to interwork with 5GS and EPC, a UE that supports both 5GC and EPC NAS can operate in single registration mode or dual registration mode.

[0093] The S1 mode is a mode that allows the UE_A10 to access the EPC via the E-UTRAN. In other words, the S1 mode may be a mode in which messages are sent and received using the S1 interface. The S1 interface may be composed of an S1-MME interface and an S1-U interface.

[0094] In addition, the N1 mode is a mode in which the UE_A10 is permitted to access the 5GC via the 5G access network. In other words, the N1 mode may be a mode in which messages are transmitted and received using the N1 interface.

[0095] In addition, the APN (Access Point Name) may be identification information for identifying a core network and / or an external network such as a PDN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network A_90.

[0096] Additionally, the PDN (Packet Data Network) type indicates the type of PDN connection, and can be IPv4, IPv6, IPv4v6, or non-IP. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If IPv4v6 is specified, it indicates that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it indicates that communication will not be via IP, but rather via a communication method other than IP.

[0097] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN providing a PDU connectivity service and a UE, but may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and the DN using a PDU session by establishing a PDU session via an access network _B and a core network _B. Here, the external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data between a device such as an application server located in a DN and the DN using a PDU session.

[0098] Each device (UE, and / or access network device, and / or core network device) may manage one or more identification information in association with a PDU session. The identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and may further include other information. Furthermore, when multiple PDU sessions are established, each identification information associated with a PDU session may be the same or different.

[0099] Furthermore, the DNN (Data Network Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN may be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0100] Also, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of the PDU session, and may be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data is transmitted and received using IPv4. If IPv6 is specified, it indicates that data is transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames are transmitted and received. Also, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data is transmitted and received to an application server or the like in a DN using Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, the PDU session type may include IP. IP can be specified when the UE is capable of using both IPv4 and IPv6.

[0101] A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. A UE and / or a network can support network slices (NW slices; NS) in 5GS.

[0102] A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be deployed. Here, an NF is a processing function in a network, which is adopted or defined by 3GPP. An NSI is an entity of an NS, one or more of which are configured in a core network _B. An NSI may also be composed of a virtual network function (NF) generated using a network slice template (NST). Here, an NST is associated with a resource requirement for providing a required communication service or capability, and is a logical expression of one or more NFs. In other words, an NSI may be a collection in a core network _B 190 composed of multiple NFs. An NSI may also be a logical network configured to separate user data delivered by a service or the like. An NS may be configured with one or more NFs. An NF configured in an NS may or may not be a device shared with other NSs. A UE and / or a device in the network may be assigned to one or more NSs based on registration information such as an NSSAI, an S-NSSAI, an UE usage type, an NSI ID, or one or more NSI IDs, and / or an APN. The UE usage type is a parameter value included in the registration information of the UE that is used to identify the NSI. The UE usage type may be stored in the HSS. The AMF may select an SMF and a UPF based on the UE usage type.

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

[0104] In addition, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information that assists the access network or core network in selecting an NSI. The UE may store the NSSAI authorized by the network for each PLMN. In addition, the NSSAI may be information used to select an AMF.

[0105] Moreover, the SSC (Session and Service Continuity) mode indicates a session service continuity mode supported by the system and / or each device in a 5G system (5GS). More specifically, it may be a mode indicating a type of session service continuity supported by a PDU session established between UE_A10 and UPF. The SSC mode may be a mode indicating a type of session service continuity set for each PDU session. Furthermore, the SSC mode may be composed of three modes, SSC mode 1, SSC mode 2, and SSC mode 3. The SSC mode associated with a PDU session may not be changed while the PDU session exists.

[0106] Furthermore, an RRC (Radio Resource Control) connection is a connection established between a UE and a base station device in an access network. More specifically, an RRC connection is a connection established at a Uu reference point between a UE and a base station device in an access network. An RRC connection may be configured with a radio bearer. Furthermore, an RRC connection may be a connection established in a 3GPP access. Furthermore, an RRC connection may be a connection established in an RRC layer below a NAS layer. Furthermore, an RRC connection may be a connection established and / or released by transmitting and receiving an RRC message in the RRC layer. Furthermore, an RRC connection may be a connection suspended by transmitting and receiving an RRC message in the RRC layer.

[0107] Also, the 5GMM-CONNECTED mode with RRC inactive indication is a state indicating that the state of the NAS layer is a connected state even though the RRC layer is in an inactive state. In other words, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the radio bearer is released while maintaining the NAS signaling connection and / or the context of the NAS signaling connection.

[0108] Furthermore, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the RRC connection is suspended. More specifically, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the state of the NAS layer is a connected state, but the RRC connection is suspended. In other words, the 5GMM-CONNECTED mode with RRC inactive indication may be a state in which the RRC connection is suspended while maintaining the NAS signaling connection and / or the context of the NAS signaling connection.

[0109] Here, the UE may transition from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on reception of information indicating that the RRC connection is suspended from a lower layer. Furthermore, the UE may transition only the state for 3GPP access from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on reception of information indicating that the RRC connection is suspended from a lower layer. Note that the information indicating that the RRC connection is suspended may be an indication indicating that the RRC connection is suspended.

[0110] Also, support of 5GMM-CONNECTED mode with RRC inactive indication may mean that maintaining the state of the NAS layer in a connected state is supported even when a notification indicating that the RRC layer has been deactivated is received from a lower layer. Furthermore, use of 5GMM-CONNECTED mode with RRC inactive indication may mean maintaining the state of the NAS layer in a connected state even when a notification indicating that the RRC layer has been deactivated is received from a lower layer.

[0111] Moreover, the PDU session with suspended user-plane resources is a PDU session in which user plane resources are established or re-established and the radio bearer is suspended. Here, the timing at which the radio bearer is suspended may be the timing at which the UE transitions to 5GMM-CONNECTED mode with RRC inactive indication. Furthermore, the radio bearer may be a data radio bearer.

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

[0113] The TA list is a list including one or more TAs assigned by the network to UE_A10. Note that UE_A10 may be able to move without performing a tracking area update procedure while moving within one or more TAs included in the TA list. In other words, UE_A10 may be able to move within the TA or TAs included in the TA list without performing a tracking area update procedure. Note that the TA list may be expressed as a TAI list consisting of one or more TAIs (Tracking area identities), and hereinafter, the TAI list may refer to the TA list.

[0114] A Local Area Data Network (LADN) is a DN that a UE can connect to only in a specific location and provides connectivity to a specific DNN (i.e., a LADN DNN). A LADN may be a DN that can be connected to in a specific location by using a PDU session associated with a specific DNN. Furthermore, a LADN may be a DN that can be connected to in a specific location by using a PDU session associated with a combination of a specific DNN and a specific S-NSSAI.

[0115] The LADN information is information related to the LADN. The LADN information may be information indicating a specific LADN available to the UE. The LADN information may include a LADN DNN and LADN service area information. More specifically, the LADN information may include information present for one or more LADNs (hereinafter referred to as information indicating the LADN). Furthermore, the information indicating the LADN may include a LADN DNN and LADN service area information. Here, the LADN DNN may be information identifying the LADN, may be information identifying a DN treated as the LADN, or may be a DNN used when establishing a PDU session for the LADN.

[0116] In addition, when the LADN information is conventional LADN information, the LADN information may be information having the configuration described above. Specifically, when the LADN information is conventional LADN information, the LADN service area may be the conventional LADN service area.

[0117] Conversely, when the LADN information is extended LADN information, the LADN information may be information in which a part of the configuration described above is extended. Specifically, when the LADN information is extended LADN information, the LADN service area may be an extended LADN service area. Furthermore, when the LADN information is extended LADN information, the information indicating the LADN may further include information indicating a period during which the LADN service area is valid and / or information indicating the granularity of the LADN service area. Furthermore, when the LADN information is extended LADN information, the information indicating the LADN may further include an S-NSSAI.

[0118] An LADN service area is an area in which a PDU session to an LADN can be established. The LADN service area may be an area in which a connection to the LADN is possible. Furthermore, the LADN service area may be an area indicated by LADN service area information. Here, the LADN service area information may be information that identifies the LADN service area, and may be provided as a set of tracking areas or as a TAI (Tracking Area Identity) list.

[0119] In addition, when the LADN service area is a conventional LADN service area, the LADN service area may be an area formed by a tracking area belonging to the registration area to which the UE is currently connected. In other words, when the LADN service area is a conventional LADN service area, the LADN service area may be an area formed by one or more tracking areas. Conversely, when the LADN service area is an extended LADN service area, the LADN service area may be an area formed by the tracking area, or an area covered by some base stations in the tracking area. Furthermore, when the LADN service area is an extended LADN service area, the LADN service area may be an area of ​​a size other than the area formed by the tracking area, or may be an area independent of the tracking area. In other words, when the LADN service area is an extended LADN service area, the LADN service area may be an area formed by one or more tracking areas, or may be an area different from the area formed by one or more tracking areas.

[0120] Furthermore, when the LADN service area is an area constituted by one or more tracking areas, the LADN service area information may be a tracking area ID list constituted by one or more tracking area IDs. Conversely, when the LADN service area is an area different from the area constituted by one or more tracking areas, the LADN service area information may be information that requires assistance from a RAN (Radio Access Network) or may be information that does not require assistance from the RAN. Here, the information that requires assistance from the RAN may be cell information or base station information. Furthermore, the information that requires assistance from the RAN may be a cell ID or a base station ID. Furthermore, the information that requires assistance from the RAN is not limited to these, and may be information defined by the RAN. Furthermore, the information that does not require assistance from the RAN may be physical location information or location information that can be obtained by an application. Furthermore, the information that does not require assistance from the RAN is not limited to these, and may be information that can be obtained by a source other than the RAN. Here, the RAN may be expressed as an access network. Conversely, the access network may be referred to as a RAN.

[0121] An extension of an LADN service area may mean using an LADN service area with a different granularity than a conventional LADN service area. Further, an extension of an LADN service area may mean using extended LADN information that is different from conventional LADN information. Further, an extension of an LADN service area may mean connecting to an extended LADN that is different from a conventional LADN.

[0122] That is, if each device supports the extension of the LADN service area, in addition to the conventional LADN service area, an extended LADN service area different from the conventional LADN service area may be applicable. Furthermore, if each device supports the extension of the LADN service area, in addition to the conventional LADN information, extended LADN information different from the conventional LADN information may be usable. Furthermore, if each device supports the extension of the LADN service area, in addition to the conventional LADN, it may be possible to connect to an extended LADN different from the conventional LADN.

[0123] Conversely, if some of the devices do not support the extension of the LADN service area, the extended LADN service area may not be applicable, and only the conventional LADN service area may be applicable. Furthermore, if some of the devices do not support the extension of the LADN service area, the use of extended LADN information may not be possible, and only the conventional LADN information may be usable. Furthermore, if some of the devices do not support the extension of the LADN service area, connection to the extended LADN may not be possible, and only connection to the conventional LADN may be possible.

[0124] Also, if each device supports usage restrictions on the extension of the LADN service area, the extended LADN service area may not be adaptable, and only the conventional LADN service area may be adaptable. Furthermore, if each device supports usage restrictions on the extension of the LADN service area, the use of extended LADN information may not be possible, and only the conventional LADN information may be usable. Furthermore, if each device supports usage restrictions on the extension of the LADN service area, connection to the extended LADN may not be possible, and only connection to the conventional LADN may be possible.

[0125] Conversely, if each device does not support the use restriction of the extended LADN service area, the extended LADN service area may also be applicable. Furthermore, if each device does not support the use restriction of the extended LADN service area, the extended LADN information may also be usable. Furthermore, if each device does not support the use restriction of the extended LADN service area, the device may be able to connect to the extended LADN.

[0126] A PDU session for LADN is a PDU session associated with a DNN associated with the LADN. The PDU session for LADN may be a PDU session established for the LADN. In other words, it may be a PDU session established between a UE and an LADN, or may be a PDU session used for user data communication between a UE and an LADN. The PDU session for LADN may be a PDU session that can be established only in an LADN service area. In other words, the UE may be able to establish a PDU session for the LADN by using a specific DNN in a specific location. In other words, the UE may be able to establish a PDU session for the LADN by using a combination of a specific DNN and a specific S-NSSAI in a specific location.

[0127] A Non-Public Network (NPN) is a private network that is not intended for general use, but is used by specific users for specific purposes, such as for private use by companies. There are two types of NPNs: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. Note that when NPN is written below, it can mean both SNPN and Public network integrated NPN.

[0128] The SNPN is a network operated by an NPN operator and is not affected by the functions provided by the PLMN. In other words, the SNPN is a network dedicated to the NPN, independent of the publicly available PLMN. The SNPN may be a network identified by an SNPN identity (SNPN ID). The SNPN ID may be information that combines a PLMN ID and a Network identifier (NID). The PLMN ID used in the SNPN ID may be information reserved for a private network, for example, the MCC included in the PLMN ID may be 999. Furthermore, when a UE is registered in an SNPN, the registered SNPN may be called a registered SNPN or an RSNPN (registered SNPN).

[0129] NID (Network Identifier) ​​is information that identifies a network. An SNPN may be identified by a combination of PLMN ID and NID. NID may be unique within an SNPN or may be globally unique.

[0130] The Public network integrated NPN is a network realized by utilizing the functional units of the PLMN. In other words, the Public network integrated NPN is an NPN that is virtually realized within the PLMN. Furthermore, the Public network integrated NPN is an NPN that can be created via the PLMN. The Public network integrated NPN may be realized by using the function of a network slice. Specifically, the Public network integrated NPN may be a network that can be realized by using a network slice allocated for the NPN. In this case, the Public network integrated NPN may be identified by the S-NSSAI or by a combination of the S-NSSAI and the CAG ID.

[0131] Furthermore, the public network integrated NPN may be realized using a DN. Specifically, the public network integrated NPN may be a network that can be realized by using a DN for an NPN. In this case, the public network integrated NPN may be identified by the DNN or by a combination of the DNN and a CAG ID.

[0132] A CAG (Closed Access Groups) ID is information that identifies a group of subscribers that are permitted to connect to one or more cells associated with the CAG. A CAG may be a group identified by a CAG ID. A CAG is a group used when implementing a public network integrated NPN in a network slice. A CAG may be used to prevent a UE that is not permitted for an NPN from attempting to access a network slice allocated for the NPN. Furthermore, a CAG ID is unique information within a PLMN.

[0133] An SNPN enabled UE is a UE configured to use an SNPN. An SNPN enabled UE may store at least one piece of information related to an SNPN. In other words, the configuration information of an SNPN enabled UE may include information indicating that the use of an SNPN is possible. Furthermore, an SNPN enabled UE may support an SNPN access mode. In other words, an SNPN enabled UE may operate in an SNPN access mode.

[0134] The SNPN access mode is a mode in which the SNPN is selected. The SNPN access mode may be a mode in which the UE is registered to the SNPN. Furthermore, the SNPN access mode may be a mode in which the UE is connected to the SNPN. In other words, a UE operating in the SNPN access mode may select only the SNPN during network selection. More specifically, a UE operating in the SNPN access mode may select only the SNPN via the Uu interface during network selection. In other words, a UE operating in the SNPN access mode may select the SNPN without selecting a PLMN during network selection. Here, a UE operating in the SNPN access mode may be expressed as a UE in the SNPN access mode. Furthermore, a UE in the SNPN access mode may be a UE in which the SNPN is enabled.

[0135] An equivalent SNPN (equivalent PLMN) may be an SNPN that is treated the same as any SNPN. For example, an equivalent SNPN may be one or more SNPNs that are treated the same as the registration SNPN.

[0136] Additionally, an equivalent SNPN may be a PLMN that is treated the same as any SNPN. For example, an equivalent SNPN may be one or more PLMNs that are treated the same as the registration SNPN.

[0137] Further, the equivalent SNPN may be one or more SNPNs or a PLMN identified with the same PLMN ID as any SNPN. For example, the equivalent SNPN may be one or more SNPNs or a PLMN identified with the same PLMN ID as the registration SNPN. Further, the equivalent SNPN may be a PLMN identified with the same PLMN ID as the registration SNPN, and an equivalent PLMN of said PLMN.

[0138] The first identification information is information indicating suspension of an RRC connection. The first identification information may be a suspend configuration information element. Furthermore, the first identification information may be a suspend indication. Furthermore, the first identification information may be identification information indicating that an RRC connection is suspended. Furthermore, the first identification information may be identification information indicating that an RRC connection is suspended.

[0139] Furthermore, the first identification information may be information for transitioning the state of the RRC connection to an RRC_INACTIVE state. In other words, the first identification information may be information indicating that the RRC layer transitions to a deactivated state.

[0140] Furthermore, the first identification information may be information selected and determined by the network based on the received identification information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, etc. Furthermore, the first identification information may be information selected and determined based on other identification information selected by the network in this procedure.

[0141] The eleventh identification information is information indicating a PDU session type. The eleventh identification information may be information indicating a PDU session type requested by the UE. More specifically, the eleventh identification information may be information indicating a PDU session type requested by the UE and associated with the PDU session established in this procedure. Furthermore, the eleventh identification information may be information selected or determined based on a UE configuration, and / or a UE state, and / or a user policy, and / or an application request.

[0142] Here, the PDU session type selected by the UE may be set in the eleventh identification information. Specifically, IPv4 or IPv6 may be set as the PDU session type in the eleventh identification information. Furthermore, IPv4v6 may be set as the PDU session type in the eleventh identification information. Furthermore, Unstructured or Ethernet may be set as the PDU session type in the eleventh identification information. Note that the PDU session type set in the eleventh identification information is not limited to these.

[0143] The twelfth identification information is information indicating a DNN. The twelfth identification information may be information indicating a DNN requested by the UE. More specifically, the twelfth identification information may be information indicating a DNN associated with a PDU session to be established in this procedure, requested by the UE. Furthermore, the twelfth identification information may be information selected or determined based on a UE configuration, and / or a UE state, and / or a user policy, and / or an application request.

[0144] The thirteenth identification information is information indicating an S-NSSAI. The thirteenth identification information may be information indicating an S-NSSAI requested by the UE. More specifically, the thirteenth identification information may be information indicating an S-NSSAI requested by the UE and associated with a PDU session established in this procedure. Furthermore, the thirteenth identification information may be information selected or determined based on a UE configuration, a UE state, a user policy, and / or an application request. Furthermore, the thirteenth identification information may be an S-NSSAI included in an NSSAI transmitted or received in the registration procedure, or an S-NSSAI stored by the UE.

[0145] The 21st identification information is information indicating a PDU session type. The 21st identification information may be information indicating a PDU session type selected by the network. More specifically, the 21st identification information may be information indicating a PDU session type selected by the network to be associated with the PDU session established in this procedure.

[0146] Furthermore, the 21st identification information may be information selected and determined by the network based on the received identification information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, etc. Furthermore, the 21st identification information may be information selected and determined based on other identification information selected by the network in this procedure.

[0147] Here, the 21st identification information may be set with a PDU session type selected by the network. Specifically, the 21st identification information may be set with IPv4 or with IPv6 as the PDU session type. Furthermore, the 21st identification information may be set with IPv4v6 as the PDU session type. Furthermore, the 21st identification information may be set with Unstructured or with Ethernet as the PDU session type. Note that the PDU session type set in the 21st identification information is not limited to these.

[0148] Furthermore, the PDU session type set in the 21st identification information may be the same PDU session type as the PDU session type set in the received 11th identification information, or may be a PDU session type different from the PDU session type set in the received 11th identification information.

[0149] The 22nd identification information is information indicating a DNN. The 22nd identification information may be information indicating a DNN selected by a network. More specifically, the 22nd identification information may be information indicating a DNN selected by a network and associated with a PDU session established in this procedure.

[0150] Furthermore, the 22nd identification information may be information selected and determined by the network based on the received identification information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, etc. Furthermore, the 22nd identification information may be information selected and determined based on other identification information selected by the network in this procedure.

[0151] The 23rd identification information is information indicating an S-NSSAI. The 23rd identification information may be information indicating an S-NSSAI selected by the network. More specifically, the 23rd identification information may be information indicating an S-NSSAI selected by the network and associated with a PDU session established in this procedure.

[0152] Furthermore, the 23rd identification information may be information selected or determined by the network based on the received identification information, and / or information associated with the NSI, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, etc. Furthermore, the 23rd identification information may be information selected or determined based on other identification information selected by the network in this procedure.

[0153] The 24th identification information is a reason value indicating why the UE request is not permitted. The 24th identification information may be a 5GSM (5GS Session Management) reason value. Furthermore, the 24th identification information may be information indicating that the PDU session type requested by the UE is not permitted. In other words, the 24th identification information may be information indicating that a PDU session type other than the PDU session type requested by the UE is permitted.

[0154] Furthermore, the 24th identification information may be information selected or determined by the network based on identification information received from the UE, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or the area to which the UE currently belongs, etc.

[0155] Furthermore, the 24th identification may be a 50th 5GSM cause value indicating that only IPv4 is allowed as a PDU session type. In other words, the 24th identification may be 5GSM cause #50 "PDU session type IPv4 only allowed". Note that 5GSM cause #50 "PDU session type IPv4 only allowed" may be a cause value indicating that only IPv4 is allowed as a PDU session type for the requested IP connectivity.

[0156] Furthermore, the 24th identification may be a 51st 5GSM cause value indicating that only IPv6 is allowed as a PDU session type. In other words, the 24th identification may be 5GSM cause #51 "PDU session type IPv6 only allowed". Note that 5GSM cause #51 "PDU session type IPv6 only allowed" may be a cause value indicating that only IPv6 is allowed as a PDU session type for the requested IP connectivity.

[0157] Furthermore, the 24th identification information may be information indicating that IPv4v6 is not permitted as a PDU session type. The 24th identification information may be information indicating that IPv4 is not permitted as a PDU session type. The 24th identification information may be information indicating that IPv6 is not permitted as a PDU session type.

[0158] Furthermore, the 24th identification information may be information indicating that a PDU session whose PDU session type is IPv4 cannot be established using the same DNN and / or the same S-NSSAI. Further, the 24th identification information may be information indicating that a PDU session whose PDU session type is IPv6 cannot be established using the same DNN and / or the same S-NSSAI.

[0159] [3.2. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a PDU session establishment procedure, and a generic UE configuration update procedure. Each procedure will be described below.

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

[0161] [3.2.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 7. The registration procedure is a procedure in 5GS. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering to the access network_B and / or the core network_B and / or the DN. If the UE is not registered in the network, it can execute this procedure at any time, such as when the power is turned on. In other words, if the UE is in a deregistered state (RM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure.

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

[0163] The UE may start the registration procedure when mobility across TAs is performed. In other words, the UE may start the registration procedure when the UE moves to a TA different from the TA indicated in the TA list held by the UE. Furthermore, the UE may start this procedure when an executing timer expires. Furthermore, the UE may start the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may start the registration procedure when there is a change in capability information and / or preferences regarding the establishment of a PDU session of the UE. Furthermore, the UE may start the registration procedure periodically. Furthermore, the UE may start the registration procedure based on the completion of a UE configuration update procedure. It should be noted that the UE can execute the registration procedure at any timing, not limited to the above.

[0164] Furthermore, the UE may periodically start the registration procedure even in a registered state. In other words, the UE may start the registration procedure based on the expiration of a timer. Furthermore, the UE may start the registration procedure in a state in which the UE stores LADN information. Furthermore, the UE may start the registration procedure in a state in which a PDU session is established. The PDU session may be a PDU session associated with LADN information or a PDU session for LADN. Furthermore, the PDU session may be a PDU session associated with an NSSAI.

[0165] In addition, the registration procedure executed based on the mobility of the UE and the registration procedure executed periodically may be expressed as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure executed based on the mobility of the UE, or may be a registration procedure executed periodically. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed based on a setting update of the UE. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration update may be a registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration update may be expressed as this procedure.

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

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

[0168] Here, the UE can transmit one or more pieces of identification information in a registration request message and / or an RRC message, but may also transmit the identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer). By transmitting the identification information, the UE may indicate that the UE supports each function, or may indicate a request of the UE. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. The information indicating support of each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0169] The UE may also initiate a PDU session establishment procedure during the registration procedure by sending a SM message (e.g., a PDU session establishment request message) included in the registration request message, or by sending an SM message (e.g., a PDU session establishment request message) together with the registration request message.

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

[0171] When the AMF receives the registration request message, the AMF can execute a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the request of the UE. When the first condition determination is true, the AMF starts the procedure of (A) in Fig. 7, whereas when the first condition determination is false, the AMF starts the procedure of (B) in Fig. 7.

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

[0173] First, a case where the first condition determination is true will be described. In the procedure of (A) in Fig. 7, the AMF can first execute the fourth condition determination. The fourth condition determination is for determining whether the AMF transmits and receives an SM message between the AMF and the SMF.

[0174] In addition, the fourth condition determination may be performed based on whether the AMF has received an SM message. In addition, the fourth condition determination may be performed based on whether the registration request message includes an SM message. For example, if the AMF has received an SM message and / or if the registration request message includes an SM message, the fourth condition determination may be true, and if the AMF has not received an SM message and / or if the registration request message does not include an SM message, the fourth condition determination may be false. In addition, the conditions that determine the truth or falsehood of the fourth condition determination may not be limited to the above-mentioned conditions.

[0175] If the fourth condition decision is true, the AMF selects an SMF and transmits and receives SM messages with the selected SMF, whereas if the fourth condition decision is false, the AMF does not perform these operations (S806). In addition, even if the fourth condition decision is true, the AMF may discontinue the procedure in (A) of Figure 7 if it receives an SM message indicating rejection from the SMF. In this case, the AMF can start the procedure in (B) of Figure 7.

[0176] In addition, in S806, when transmitting and receiving an SM message with the SMF, the AMF can notify the SMF of the identification information received in the registration request message. The SMF can obtain the identification information received from the AMF by transmitting and receiving an SM message with the AMF.

[0177] Next, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message based on the reception of the registration request message and / or the completion of the transmission and reception of the SM message with the SMF (S808). For example, when the fourth condition determination is false, the AMF may transmit a registration accept message based on the reception of the registration request message from the UE. Also, when the fourth condition determination is true, the AMF may transmit a registration accept message based on the completion of the transmission and reception of the SM message with the SMF. Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0178] The AMF may transmit one or more identification information in the registration acceptance message. By transmitting these identification information, the AMF may indicate that the network supports each function, or may indicate that the UE's request has been accepted. Furthermore, when multiple identification information are transmitted and received, two or more of these identification information may be configured as one or more identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0179] Furthermore, the AMF may select and determine which identification information to include in the registration acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0180] Furthermore, the AMF may include and send an SM message (e.g., a PDU session establishment accept message) in the registration acceptance message, or may send an SM message (e.g., a PDU session establishment accept message) together with the registration acceptance message. However, this sending method may be executed when an SM message (e.g., a PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Also, this sending method may be executed when an SM message (e.g., a PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure.

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

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

[0183] The UE receives a registration acceptance message via the 5G AN (gNB) (S808). By receiving the registration acceptance message, the UE can recognize that the UE's request by the registration request message has been accepted and the contents of various identification information included in the registration acceptance message.

[0184] The UE may further transmit a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S810). When the UE receives an SM message such as a PDU session establishment acceptance message, the UE may transmit an SM message such as a PDU session establishment completion message in the registration completion message, or may indicate that the procedure for SM has been completed by including the SM message. Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is transmitted and received in an RRC message between the UE and the 5G AN (gNB).

[0185] The AMF receives a registration completion message via the 5G AN (gNB) (S810). In addition, each device completes the procedure of (A) in FIG. 7 based on the transmission and reception of the registration acceptance message and / or the registration completion message.

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

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

[0188] The UE receives a registration rejection message via the 5G AN (gNB) (S812). By receiving the registration rejection message, the UE can recognize that the UE's request by the registration request message has been rejected and the contents of various identification information included in the registration rejection message. In addition, if the UE does not receive a registration rejection message even after a predetermined period has elapsed after transmitting the registration request message, the UE may recognize that the UE's request has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the registration rejection message.

[0189] In addition, the procedure of Fig. 7 (B) may be started when the procedure of Fig. 7 (A) is stopped. In the procedure of Fig. 7 (A), if the fourth condition determination is true, the AMF may transmit an SM message indicating a rejection such as a PDU session establishment rejection message in the registration rejection message, or may indicate that the procedure for SM has been rejected by including an SM message indicating a rejection such as a PDU session establishment rejection message. In this case, the UE may further receive an SM message indicating a rejection such as a PDU session establishment rejection message, or may recognize that the procedure for SM has been rejected.

[0190] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Fig. 7. Each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in Fig. 7, and may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) or transition to a state in which the UE is not registered in the network based on the completion of the procedure of (B) in Fig. 7. Furthermore, the transition of each device to each state may be performed based on the completion of the registration procedure or the establishment of a PDU session.

[0191] Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure based on the completion of the registration procedure. For example, when transmitting and receiving information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's request has been rejected, or may perform the registration procedure for the core network_B or another cell.

[0192] Further, the UE may store the identification information received with the registration accept message and / or the registration reject message and may recognize the network's decision upon completion of the registration procedure.

[0193] [3.2.2. PDU Session Establishment Procedure] Next, an overview of the PDU session establishment procedure performed to establish a PDU session for a DN will be described with reference to FIG. 8. The PDU session establishment procedure is a procedure in 5GS. Hereinafter, this procedure refers to the PDU session establishment procedure. The PDU session establishment procedure is a procedure for each device to establish a PDU session. Each device can start the PDU session establishment procedure at any timing when the registration procedure is completed and the device is in a registered state. Each device may also be able to execute the PDU session establishment procedure during the registration procedure. Each device may also establish a PDU session based on the completion of the PDU session establishment procedure.

[0194] In addition, the PDU session establishment procedure may be a procedure initiated by the UE or may be a procedure initiated by the UE. In other words, the PDU session establishment procedure may be a UE-requested PDU session establishment procedure. Each device can establish multiple PDU sessions by performing the PDU session establishment procedure multiple times.

[0195] Here, when the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for the LADN, each device may establish a PDU session for the LADN based on completion of the PDU session establishment procedure. In other words, when the PDU session establishment procedure is a PDU session establishment procedure using the LADN DNN, each device may establish a PDU session for the LADN based on completion of the PDU session establishment procedure.

[0196] Furthermore, the UE may initiate a PDU session establishment procedure to establish a PDU session for the LADN when it is located in an area where connectivity to the LADN is possible and / or when it is located in an LADN service area. Conversely, the UE may be prohibited from performing a PDU session establishment procedure to establish a PDU session for the LADN when it is located outside the LADN service area.

[0197] In other words, each device may perform a PDU session establishment procedure to establish a PDU session for the LADN if the UE is located in an area where connection to the LADN is possible and / or if the UE is located in an LADN service area. Conversely, the network device may reject a request for a PDU session establishment procedure to establish a PDU session for the LADN if the UE is located outside the LADN service area.

[0198] First, the UE initiates a PDU session establishment procedure by sending a NAS message including a PDU session establishment request message to the SMF via a 5G AN (gNB) and an AMF (S900) (S902) (S904).

[0199] Specifically, the UE transmits a NAS message including a PDU session establishment request message to the AMF via the N1 interface and via the 5G AN (gNB) (S900). The NAS message including the PDU session establishment request message may be an MM message. Furthermore, the MM message may be an uplink NAS transport (UL NAS TRANSPORT) message. Here, when it is expressed that the identification information and / or value are included in the PDU session establishment request message, it may mean that the identification information and / or value are included in the MM message including the PDU session establishment request message.

[0200] Here, the UE may transmit one or more of at least the eleventh to thirteenth identification information in a PDU session establishment request message and / or a NAS message, but may also transmit the identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, or a PDCP layer). The identification information may indicate a request of the UE by being included in these messages. Furthermore, when multiple identification information are transmitted and received, two or more of the identification information may be configured as one or more identification information.

[0201] Specifically, the UE may include the eleventh identification information in a PDU session establishment request message. Furthermore, the UE may include the twelfth identification information and / or the thirteenth identification information in an uplink NAS transport message together with the PDU session establishment request message including at least the eleventh identification information. Furthermore, the UE may transmit the uplink NAS transport message to the AMF (S900). In other words, the UE may transmit the twelfth identification information and / or the thirteenth identification information to the AMF together with the PDU session establishment request message including the eleventh identification information. In yet another word, the UE may transmit the PDU session establishment request message including the eleventh identification information together with the twelfth identification information and / or the thirteenth identification information to the AMF.

[0202] Furthermore, the UE may indicate a request for establishment of a PDU session establishment request message of a PDU session type indicated by the eleventh identification information by transmitting the eleventh identification information. Furthermore, the UE may indicate a PDU session type requested by the UE by transmitting the eleventh identification information.

[0203] Furthermore, the UE may indicate a request for establishing a PDU session corresponding to a DNN indicated by the twelfth identification information by transmitting the twelfth identification information. Furthermore, the UE may indicate a DNN requested by the UE by transmitting the twelfth identification information. The twelfth identification information may be a DNN that identifies a DN supporting one or more functions indicated by the identification information transmitted and received together with the twelfth identification information. Furthermore, the twelfth identification information may be a DNN received in the registration procedure, or may be a LADN DNN.

[0204] Furthermore, the UE may indicate a request for establishment of a PDU session corresponding to an S-NSSAI indicated by the 13th identification information by transmitting a 13th identification information. Furthermore, the UE may indicate an S-NSSAI requested by the UE by transmitting a 13th identification information. Note that the 13th identification information may be an S-NSSAI that identifies an NS supporting one or more functions indicated by an identification information transmitted and received together with the 13th identification information.

[0205] When the AMF receives a NAS message including a PDU session establishment request message (S900), it extracts the PDU session establishment request message from the NAS message and selects an SMF as a transfer destination of the PDU session establishment request message (S902). The AMF may select the transfer destination SMF based on each identification information included in the PDU session establishment request message and / or the NAS message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0206] The AMF forwards the PDU session establishment request message to the selected SMF via the N11 interface (S904).

[0207] When the SMF receives the PDU session establishment request message (S904), it recognizes various identification information included in the PDU session establishment request message. Then, the SMF executes a third condition determination. The third condition determination is for the SMF to determine whether or not to accept the UE request. In the third condition determination, the SMF determines whether the third condition determination is true or false. If the third condition determination is true, the SMF starts the procedure of (A) in Figure 8, and if the third condition determination is false, the SMF starts the procedure of (B) in Figure 8.

[0208] The third condition determination may be performed based on the PDU session establishment request message, and / or each identification information included in the PDU session establishment request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or a context held by the SMF. For example, if the network permits the request of the UE, the third condition determination may be true. If the network does not permit the request of the UE, the third condition determination may be false. Furthermore, if the network to which the UE is connected and / or a device in the network supports the function requested by the UE, the third condition determination may be true, and if the function requested by the UE is not supported, the third condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the third condition determination may be true, and if the identification information to be transmitted and received is not permitted, the third condition determination may be false. The conditions for determining whether the third condition determination is true or false may not be limited to the above-mentioned conditions.

[0209] Next, the steps when the third condition determination is true, that is, each step of the procedure in (A) of Fig. 8 will be described. The SMF selects a UPF to establish a PDU session, and transmits a session establishment request message to the selected UPF via the N4 interface (S906), thereby starting the procedure in (A) of Fig. 8.

[0210] Here, the SMF may select one or more UPFs based on each identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc., acquired based on receiving the PDU session establishment request message. In addition, when multiple UPFs are selected, the SMF may send a session establishment request message to each UPF.

[0211] The UPF receives a session establishment request message from the SMF via the N4 interface (S906) and creates a context for the PDU session. Furthermore, the UPF sends a session establishment response message to the SMF via the N4 interface based on the reception of the session establishment request message and / or the creation of the context for the PDU session (S908).

[0212] The SMF receives a session establishment response message from the UPF via the N4 interface as a response message to the session establishment request message (S908). The SMF may perform address allocation of an address to be assigned to the UE based on the reception of the PDU session establishment request message, and / or the selection of the UPF, and / or the reception of the session establishment response message.

[0213] The SMF sends a PDU session establishment accept message to the UE via the AMF based on reception of a PDU session establishment request message, and / or selection of a UPF, and / or reception of a session establishment response message, and / or completion of address allocation of an address to be assigned to the UE (S910) (S912).

[0214] Specifically, when the SMF transmits a PDU session establishment acceptance message to the AMF via the N11 interface (S910), the AMF that receives the PDU session establishment request message transmits a NAS message including the PDU session establishment acceptance message to the UE via the N1 interface (S912). The PDU session establishment acceptance message is a NAS message and may be a response message to the PDU session establishment request. Furthermore, the PDU session establishment acceptance message may be included in an MM message and transmitted through the N1 interface. Furthermore, the MM message may be a NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, when it is expressed that the identification information and / or value are included in the PDU session establishment acceptance message, it may mean that they are included in the MM message including the PDU session establishment acceptance message. Furthermore, the PDU session establishment acceptance message may indicate that the establishment of the PDU session has been accepted.

[0215] Here, the SMF and AMF may indicate that the UE's request for PDU session establishment has been accepted by sending a PDU session establishment acceptance message.

[0216] The SMF and AMF may transmit the PDU session establishment acceptance message including one or more of at least the 21st to 24th identification information. By transmitting these identification information, the SMF and AMF may indicate that the network supports each function, or may indicate that the UE's request has been accepted. Furthermore, when multiple identification information are transmitted and received, two or more of these identification information may be configured as one or more identification information. Furthermore, the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0217] Furthermore, the SMF and AMF may indicate acceptance of a PDU session establishment request of the PDU session type indicated by the 21st identification information by sending the 21st identification information, or may indicate that the PDU session is established. Furthermore, the SMF and AMF may indicate a PDU session type selected or determined by the network by sending the 21st identification information. Note that the PDU session type indicated by the 21st identification information may be the same PDU session type as the received 11th identification information, or may be a PDU session type different from the received 11th identification information.

[0218] Furthermore, the SMF and AMF may indicate acceptance of a request to establish a PDU session corresponding to the DNN indicated by the 22nd identification information, or may indicate that the PDU session is established, by transmitting the 22nd identification information. Furthermore, the SMF and AMF may indicate a DNN selected or determined by the network by transmitting the 22nd identification information. The 22nd identification information may be a DNN that identifies a DN supporting one or more functions indicated by the identification information transmitted and received together with the 22nd identification information. Furthermore, the 22nd identification information may be a DNN transmitted in the registration procedure, or may be a LADN DNN.

[0219] Furthermore, the SMF and AMF may, by transmitting the 23rd identification information, indicate acceptance of a request to establish a PDU session corresponding to the S-NSSAI indicated by the 23rd identification information, or may indicate that the PDU session is established. Furthermore, the SMF and AMF may, by transmitting the 23rd identification information, indicate an S-NSSAI selected or determined by the network. Note that the 23rd identification information may be an S-NSSAI that identifies an NS that supports one or more functions indicated by the identification information transmitted and received together with the 23rd identification information. Furthermore, the 23rd identification information may be an S-NSSAI transmitted in the registration procedure.

[0220] Furthermore, the SMF and / or AMF may indicate that some of the UE requests are not allowed by sending the 24th identity. Specifically, the SMF and / or AMF may indicate that the UE requested PDU session type is not allowed by sending the 24th identity.

[0221] Furthermore, the SMF and / or AMF may indicate that only PDU session types different from the PDU session type requested by the UE are allowed by transmitting the 24th identification information. Furthermore, the SMF and / or AMF may indicate that a PDU session type different from the PDU session type indicated by the received 11th identification information is set to the 21st identification information by transmitting the 24th identification information.

[0222] Specifically, when the PDU session type indicated by the 11th identification information is IPv4v6 or IPv6, and the permitted PDU session type is IPv4, the SMF and / or AMF may set IPv4 as the PDU session type in the 21st identification information. Furthermore, in this case, the SMF and / or AMF may set a reason value indicating that only IPv4 is permitted in the 24th identification information. Furthermore, in this case, the SMF and / or AMF may indicate that only IPv4 is permitted as the PDU session type by transmitting the 24th identification information. Furthermore, in this case, the SMF and / or AMF may indicate that IPv6 and / or IPv4v6 are not permitted as the PDU session type by transmitting the 24th identification information.

[0223] Here, the reason value indicating that only IPv4 is allowed may be the 50th 5GSM reason value. Furthermore, the reason value indicating that only IPv4 is allowed may be a reason value indicating that only IPv4 is allowed as a PDU session type. In other words, the reason value indicating that only IPv4 is allowed may be a reason value indicating that only IPv4 PDU session types are allowed.

[0224] Furthermore, when the PDU session type indicated by the eleventh identification information is IPv4v6 or IPv4, and the permitted PDU session type is IPv6, the SMF and / or AMF may set the PDU session type to IPv6 in the twenty-first identification information. Furthermore, in this case, the SMF and / or AMF may set a reason value indicating that only IPv6 is permitted in the twenty-fourth identification information. Furthermore, in this case, the SMF and / or AMF may indicate that only IPv6 is permitted as the PDU session type by transmitting the twenty-fourth identification information. Furthermore, in this case, the SMF and / or AMF may indicate that IPv4 and / or IPv4v6 are not permitted as the PDU session type by transmitting the twenty-fourth identification information.

[0225] Here, the reason value indicating that only IPv6 is allowed may be the 51st 5GSM reason value. Furthermore, the reason value indicating that only IPv6 is allowed may be a reason value indicating that only IPv6 is allowed as a PDU session type. In other words, the reason value indicating that only IPv6 is allowed may be a reason value indicating that only IPv6 PDU session types are allowed.

[0226] Furthermore, the SMF and AMF may select and decide whether to include one or more of at least the identification information 21 to 24 in the PDU session establishment acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0227] The SMF and AMF can also include the selected and / or permitted PDU session ID in the PDU session establishment accept message. The SMF and AMF can also specify a PDU session type indicating the type of the selected and / or permitted PDU session. As the PDU session type, any of IPv4, IPv6, IPv4v6, Ethernet, and Unstructured can be specified as described above. The SMF and AMF can also include the SSC mode of the selected and / or permitted PDU session in the PDU session establishment accept message.

[0228] Furthermore, the SMF and AMF may include the approved QoS rule set in the PDU session establishment acceptance message. The approved QoS rule set may include one or more QoS rules. Furthermore, if multiple QoS flows and / or user plane radio bearers are established in this procedure, the approved QoS rule set may include multiple QoS rules. Conversely, if only one QoS flow and / or user plane radio bearer is established in this procedure, the approved QoS rule set may include one QoS rule.

[0229] Furthermore, the SMF may include information indicating that some of the UE requests have been rejected in the PDU session establishment acceptance message and transmit the information indicating that some of the UE requests have been rejected, and may indicate the reason why some of the UE requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE requests have been rejected by receiving the information indicating that some of the UE requests have been rejected. The reason for the rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

[0230] The UE receives a PDU session establishment acceptance message from the SMF (S910) (S912). Specifically, after the PDU session establishment acceptance message is sent from the SMF to the AMF (S910), the UE receives a NAS message including the PDU session establishment acceptance message from the AMF via the N1 interface (S912). Based on receiving the PDU session establishment acceptance message and / or the NAS message including the PDU session establishment acceptance message, the UE may send a PDU session establishment complete message to the SMF via the AMF (S914) (S916). By receiving the PDU session establishment acceptance message, the UE can detect that the UE's request for the PDU session establishment request has been accepted.

[0231] Specifically, the UE sends a PDU session establishment completion message to the AMF via the N1 interface (S914). When the AMF receives the PDU session establishment completion message from the UE, it sends a PDU session establishment completion message to the SMF via the N11 interface (S916).

[0232] In addition, the PDU session establishment completion message sent by the AMF to the SMF may be a response message to the PDU session establishment acceptance message sent from the SMF to the AMF in S910. In addition, the PDU session establishment completion message may be a NAS message. In addition, the PDU session establishment completion message may be any message indicating that the PDU session establishment procedure is completed.

[0233] When the SMF receives a PDU session establishment completion message from the AMF via the N11 interface (S916), it can perform a second condition determination. The second condition determination is for determining the type of message on the N4 interface to be transmitted and received. When the second condition determination is true, the SMF sends a session change request message to the UPF via the N4 interface (S918), and receives a session change accept message sent from the UPF as a response message (S920). When the second condition determination is false, the SMF sends a session establishment request message to the UPF via the N4 interface (S918), and receives a session change accept message sent from the UPF as a response message (S920).

[0234] The second condition determination may be performed based on whether a session on the N4 interface for the PDU session is established. For example, if a session on the N4 interface for the PDU session is established, the second condition determination may be true, and if a session on the N4 interface for the PDU session is not established, the second condition determination may be false. The conditions for determining whether the second condition determination is true or false are not limited to the above-mentioned conditions.

[0235] Each device completes the procedure (A) during the PDU session establishment procedure based on the transmission and reception of a PDU session establishment completion message, and / or the transmission and reception of a session change response message, and / or the transmission and reception of a session establishment response message. When the procedure (A) during this procedure is completed, the UE is in a state in which a PDU session for the DN is established. Here, if the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for the LADN, each device may establish a PDU session for the LADN based on the completion of the procedure (A) during this procedure.

[0236] Next, each step of the procedure (B) during the PDU session establishment procedure will be described. The SMF transmits a PDU session establishment reject message to the UE via the AMF (S922) (S924). Specifically, the SMF transmits a PDU session establishment reject message to the AMF via the N11 interface (S922). When the AMF receives a PDU session establishment request message from the SMF via the N11 interface (S922), it transmits a PDU session establishment reject message to the UE using the N1 interface (S924).

[0237] The PDU session establishment rejection message may be a NAS message or an SM message transmitted from the SMF to the UE. The PDU session establishment rejection message may be any message indicating that the establishment of the PDU session has been rejected. The PDU session establishment rejection message may be transmitted and received via the N1 interface in an MM message. The MM message may be a NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, when it is expressed that the PDU session establishment rejection message includes identification information and / or a value, this may mean that the identification information and / or a value are included in an MM message including the PDU session establishment rejection message.

[0238] Here, the SMF may indicate that the UE's request by the PDU session establishment request has been rejected by transmitting a PDU session establishment rejection message. Furthermore, the SMF may include information indicating the reason for the rejection in the PDU session establishment rejection message and transmit it, or may indicate the reason for the rejection by transmitting the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

[0239] The SMF and / or AMF may send the PDU session establishment rejection message including at least the 24th identification information and / or the back-off timer value, and may indicate that the UE request has been rejected by sending the 24th identification information and / or the back-off timer value, or may indicate the reason why the UE request has been rejected.

[0240] Further, the SMF and / or AMF may indicate that the UE's request is not allowed by sending the 24th identity. Specifically, the SMF and / or AMF may indicate that the UE's requested PDU session type is not allowed by sending the 24th identity.

[0241] Specifically, when the PDU session type indicated by the 11th identification information is IPv4v6 or IPv6 and the permitted PDU session type is IPv4, the SMF and / or AMF may set a reason value indicating that only IPv4 is permitted in the 24th identification information. Furthermore, in this case, the SMF and / or AMF may indicate that only IPv4 is permitted as the PDU session type by transmitting the 24th identification information. Furthermore, in this case, the SMF and / or AMF may indicate that IPv6 and / or IPv4v6 are not permitted as the PDU session type by transmitting the 24th identification information.

[0242] Here, the reason value indicating that only IPv4 is allowed may be the 50th 5GSM reason value. Furthermore, the reason value indicating that only IPv4 is allowed may be a reason value indicating that only IPv4 is allowed as a PDU session type. In other words, the reason value indicating that only IPv4 is allowed may be a reason value indicating that only IPv4 PDU session types are allowed.

[0243] Furthermore, when the PDU session type indicated by the 11th identification information is IPv4v6 or IPv4, and the permitted PDU session type is IPv6, the SMF and / or AMF may set a reason value indicating that only IPv6 is permitted in the 24th identification information. Furthermore, in this case, the SMF and / or AMF may indicate that only IPv6 is permitted as a PDU session type by transmitting the 24th identification information. Furthermore, in this case, the SMF and / or AMF may indicate that IPv4 and / or IPv4v6 are not permitted as a PDU session type by transmitting the 24th identification information.

[0244] Here, the reason value indicating that only IPv6 is allowed may be the 51st 5GSM reason value. Furthermore, the reason value indicating that only IPv6 is allowed may be a reason value indicating that only IPv6 is allowed as a PDU session type. In other words, the reason value indicating that only IPv6 is allowed may be a reason value indicating that only IPv6 PDU session types are allowed.

[0245] Furthermore, the SMF and / or AMF may transmit a back-off timer value to instruct the UE to set the back-off timer value to the transmitted value, or may instruct the UE to start the back-off timer with the transmitted value set.

[0246] Furthermore, the SMF and / or AMF may select and decide whether to include at least the 24th identification information in the PDU session establishment rejection message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0247] By receiving the PDU session establishment rejection message, the UE can recognize that the UE's PDU session establishment request has been rejected, and the contents of the various identification information contained in the PDU session establishment rejection message.

[0248] Each device completes the PDU session establishment procedure based on the completion of the procedure of (A) or (B) in Figure 8. Each device may transition to a state in which the PDU session is established based on the completion of the procedure of (A) in Figure 8, or may recognize that the PDU session establishment procedure has been rejected based on the completion of the procedure of (B) in Figure 8, and may transition to a state in which the PDU session is not established. Furthermore, by completing the procedure of (A) in Figure 8, the UE can communicate with the DN using the established PDU session.

[0249] Furthermore, each device may perform processing based on the information transmitted and received in the PDU session establishment procedure based on the completion of the PDU session establishment procedure. For example, when each device transmits and receives information indicating that some of the UE's requests have been rejected, it may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again or perform the PDU session establishment procedure for another cell based on the reason why the UE's requests have been rejected.

[0250] Further, the UE may store the identification information received along with the PDU session establishment accept message and / or the PDU session establishment reject message and may recognize the network's decision based on the completion of the PDU session establishment procedure.

[0251] For example, when each device transmits and receives the 21st identification information, it may establish a PDU session of the PDU session type indicated by the 21st identification information. Furthermore, when the UE receives the 21st identification information, it may recognize that a PDU session of the PDU session type indicated by the 21st identification information will be established. Furthermore, when the UE receives the 21st identification information, it may recognize the PDU session type selected and determined by the network.

[0252] Furthermore, when each device transmits and receives the 22nd identification information, it may establish a PDU session corresponding to the DNN indicated by the 22nd identification information. Furthermore, when the UE receives the 22nd identification information, it may recognize that a PDU session corresponding to the DNN indicated by the 22nd identification information is established. Furthermore, when the UE receives the 22nd identification information, it may recognize a DNN selected and determined by the network. Note that the 22nd identification information may be a DNN that identifies a DN supporting one or more functions indicated by the identification information transmitted and received together with the 22nd identification information. Furthermore, the 22nd identification information may be a DNN received in the registration procedure, or may be a LADN DNN.

[0253] Furthermore, when each device transmits and receives the 23rd identification information, it may establish a PDU session corresponding to the S-NSSAI indicated by the 23rd identification information. Furthermore, when the UE receives the 23rd identification information, it may recognize that a PDU session corresponding to the S-NSSAI indicated by the 23rd identification information is established. Furthermore, when the UE receives the 23rd identification information, it may recognize the S-NSSAI selected and determined by the network. Note that the 23rd identification information may be an S-NSSAI that identifies an NS supporting one or more functions indicated by the identification information transmitted and received together with the 23rd identification information. Furthermore, the 23rd identification information may be an S-NSSAI received in the registration procedure, or may be an S-NSSAI.

[0254] Furthermore, the UE may recognize that a part of the UE's request is not permitted when the 24th identification information is received. Specifically, the UE may recognize that a PDU session type requested by the UE is not permitted when the 24th identification information is received. In other words, the UE may recognize that a PDU session of a PDU session type other than the PDU session type requested by the UE is established when the 24th identification information is received.

[0255] Furthermore, if the UE receives the 24th identification information with a cause value indicating that only IPv4 is allowed, the UE may recognize that only IPv4 is allowed as a PDU session type. Furthermore, in this case, the UE may indicate that IPv6 and / or IPv4v6 are not allowed as PDU session types.

[0256] Here, the reason value indicating that only IPv4 is allowed may be the 50th 5GSM reason value. Furthermore, the reason value indicating that only IPv4 is allowed may be a reason value indicating that only IPv4 is allowed as a PDU session type. In other words, the reason value indicating that only IPv4 is allowed may be a reason value indicating that only IPv4 PDU session types are allowed.

[0257] Furthermore, if a 24th identification information is received with a cause value indicating that only IPv4 is allowed, the UE may implement behavior A. More specifically, if an 11th identification information is transmitted with IPv4v6 configured, and a 21st identification information is received with IPv4 configured, and a 24th identification information is received with a cause value indicating that only IPv4 is allowed, the UE may implement behavior A. In other words, if a PDU session type of IPv4v6 is requested, and a 24th identification information is received with a PDU session type of IPv4 configured and a cause value indicating that only IPv4 is allowed, the UE may implement behavior A.

[0258] In addition, behavior A may be a behavior of recognizing that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is prohibited. Furthermore, behavior A may be a behavior of setting so that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is prohibited. Furthermore, behavior A may be a behavior of setting so that a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is not started. Furthermore, behavior A may be a behavior of transitioning to a state in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is prohibited.

[0259] Furthermore, the UE may be prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 configured while performing behavior A. Furthermore, the UE may be configured to prohibit the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 configured while performing behavior A. Furthermore, the UE may be in a state in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 configured is prohibited while performing behavior A.

[0260] Furthermore, behavior A may be performed until the UE is registered in a new PLMN, or may be performed until the UE is registered in a new SNPN. More specifically, when the UE is registered in a PLMN, behavior A may be performed until the UE is registered in a PLMN other than an even PLMN, or may be performed until the UE is registered in an SNPN. Furthermore, when the UE is registered in an SNPN, behavior A may be performed until the UE is registered in an SNPN other than an even SNPN, or may be performed until the UE is registered in a PLMN.

[0261] In other words, if the UE is not operating in the SNPN access mode, behavior A may be implemented until the UE registers with a PLMN other than an even-numbered PLMN, or until the UE registers with an SNPN. Furthermore, if the UE is operating in the SNPN access mode, behavior A may be implemented until the UE registers with an SNPN other than an even-numbered SNPN, or until the UE registers with a PLMN.

[0262] Furthermore, behavior A may be implemented until the PDU session type is changed, and may be implemented until the UE is switched off or the USIM is removed.

[0263] In addition, a PLMN other than an equal PLMN may be a PLMN that is not in the list of equal PLMNs. In other words, a UE being registered in a PLMN other than an equal PLMN may indicate that the UE is registered in a new PLMN that is not in the list of equal PLMNs.

[0264] Furthermore, a PLMN other than an equivalent PLMN may be a PLMN that is not included in the list of equivalent PLMNs. In other words, a UE being registered in a PLMN other than an equivalent PLMN may indicate that the UE is registered in a new PLMN that is not included in the list of equivalent PLMNs.

[0265] Furthermore, an SNPN other than the equivalent SNPN may be an SNPN that is not in the list of equivalent SNPNs. In other words, a UE registering with an SNPN other than the equivalent SNPN may indicate that the UE registers with a new SNPN that is not in the list of equivalent SNPNs.

[0266] Furthermore, an SNPN other than the equal-value SNPN may be an SNPN that is not included in the list of equal-value SNPNs. In other words, a UE registering with an SNPN other than the equal-value SNPN may indicate that the UE registers with a new SNPN that is not included in the list of equal-value SNPNs.

[0267] Here, the same DNN may be the same DNN included in the 12th identification information and transmitted and received in this procedure, or may be the same DNN included in the 22nd identification information and transmitted and received. Furthermore, the same S-NSSAI may be the same S-NSSAI included in the 13th identification information and transmitted and received in this procedure, or may be the same S-NSSAI included in the 23rd identification information and transmitted and received.

[0268] Furthermore, the new PDU session establishment procedure may be a PDU session establishment procedure other than this procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after completion of this procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after completion of this procedure.

[0269] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6.

[0270] Furthermore, if the UE receives the 24th identification information with a cause value indicating that only IPv6 is allowed, the UE may recognize that only IPv6 is allowed as a PDU session type. Furthermore, in this case, the UE may indicate that IPv4 and / or IPv4v6 are not allowed as PDU session types.

[0271] Here, the reason value indicating that only IPv6 is allowed may be the 51st 5GSM reason value. Furthermore, the reason value indicating that only IPv6 is allowed may be a reason value indicating that only IPv6 is allowed as a PDU session type. In other words, the reason value indicating that only IPv6 is allowed may be a reason value indicating that only IPv6 PDU session types are allowed.

[0272] Furthermore, if a 24th identification information is received with a cause value indicating that only IPv6 is allowed, the UE may implement behavior B. More specifically, if an 11th identification information is transmitted with IPv4v6 configured, and a 21st identification information is received with IPv6 configured, and a 24th identification information is received with a cause value indicating that only IPv6 is allowed, the UE may implement behavior B. In other words, if a PDU session type of IPv4v6 is requested, and a 24th identification information is received with a PDU session type with IPv6 configured and a cause value indicating that only IPv6 is allowed, the UE may implement behavior B.

[0273] In addition, behavior B may be a behavior of recognizing that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type set to IPv4 is prohibited. Furthermore, behavior B may be a behavior of setting so that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type set to IPv4 is prohibited. Furthermore, behavior B may be a behavior of setting so that a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type set to IPv4 is not started. Furthermore, behavior B may be a behavior of transitioning to a state in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type set to IPv4 is prohibited.

[0274] Furthermore, the UE may be prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 configured while performing behavior B. Furthermore, the UE may be configured to prohibit the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 configured while performing behavior B. Furthermore, the UE may be in a state in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 configured is prohibited while performing behavior B.

[0275] Furthermore, behavior B may be performed until the UE is registered in a new PLMN, or may be performed until the UE is registered in a new SNPN. More specifically, when the UE is registered in a PLMN, behavior B may be performed until the UE is registered in a PLMN other than an even PLMN, or may be performed until the UE is registered in an SNPN. Furthermore, when the UE is registered in an SNPN, behavior B may be performed until the UE is registered in an SNPN other than an even SNPN, or may be performed until the UE is registered in a PLMN.

[0276] In other words, if the UE is not operating in the SNPN access mode, behavior B may be performed until the UE is registered in a PLMN other than an even-numbered PLMN, or until the UE is registered in an SNPN. Furthermore, if the UE is operating in the SNPN access mode, behavior B may be performed until the UE is registered in an SNPN other than an even-numbered SNPN, or until the UE is registered in a PLMN.

[0277] Furthermore, behavior B may be implemented until the PDU session type is changed, and may be implemented until the UE is switched off or the USIM is removed.

[0278] In addition, a PLMN other than an equal PLMN may be a PLMN that is not in the list of equal PLMNs. In other words, a UE being registered in a PLMN other than an equal PLMN may indicate that the UE is registered in a new PLMN that is not in the list of equal PLMNs.

[0279] Furthermore, a PLMN other than an equivalent PLMN may be a PLMN that is not included in the list of equivalent PLMNs. In other words, a UE being registered in a PLMN other than an equivalent PLMN may indicate that the UE is registered in a new PLMN that is not included in the list of equivalent PLMNs.

[0280] Furthermore, an SNPN other than the equivalent SNPN may be an SNPN that is not in the list of equivalent SNPNs. In other words, a UE registering with an SNPN other than the equivalent SNPN may indicate that the UE registers with a new SNPN that is not in the list of equivalent SNPNs.

[0281] Furthermore, an SNPN other than the equal-value SNPN may be an SNPN that is not included in the list of equal-value SNPNs. In other words, a UE registering with an SNPN other than the equal-value SNPN may indicate that the UE registers with a new SNPN that is not included in the list of equal-value SNPNs.

[0282] Here, the same DNN may be the same DNN included in the 12th identification information and transmitted and received in this procedure, or may be the same DNN included in the 22nd identification information and transmitted and received. Furthermore, the same S-NSSAI may be the same S-NSSAI included in the 13th identification information and transmitted and received in this procedure, or may be the same S-NSSAI included in the 23rd identification information and transmitted and received.

[0283] Furthermore, the new PDU session establishment procedure may be a PDU session establishment procedure other than this procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after completion of this procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after completion of this procedure.

[0284] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4.

[0285] Furthermore, when the UE receives a back-off timer value, the UE may set the back-off timer to the back-off timer value, or may start the back-off timer set to the received back-off timer value. Here, even when the UE receives a back-off timer value, if the UE receives 24th identification information, the UE may ignore the received back-off timer value and may not start the back-off timer. Conversely, even when the UE receives a back-off timer value and 24th identification information, the UE may set the back-off timer to the received back-off timer value, or may start the back-off timer set to the received back-off timer value.

[0286] Furthermore, if the UE receives the 24th identification information, after completing this procedure, the UE may start the PDU session establishment procedure under other conditions based on the completion of this procedure and / or the reception of the 24th identification information. Note that, if the UE is running a back timer, the UE may start the PDU session establishment procedure under other conditions after the back-off timer expires.

[0287] Here, the UE initiating the PDU session establishment procedure under other conditions may mean, for example, initiating the PDU session establishment procedure by setting a DNN different from the DNN previously transmitted by the UE in a DNN information element and transmitting the DNN information element to the network.Furthermore, the UE initiating the PDU session establishment procedure under other conditions may mean initiating the PDU session establishment procedure by setting an S-NSSAI different from the S-NSSAI previously transmitted by the UE in an S-NSSAI information element and transmitting the S-NSSAI information element to the network.

[0288] Furthermore, the UE initiating the PDU session establishment procedure under another condition may mean initiating the PDU session establishment procedure by setting a PDU session type different from the previously transmitted PDU session type in a PDU session type information element and transmitting the PDU session type information element to the network. Furthermore, the UE initiating the PDU session establishment procedure under another condition may mean initiating the PDU session establishment procedure by changing the area in which the UE is located and then transmitting a PDU session establishment request message.

[0289] Furthermore, the UE initiating a PDU session establishment procedure under other conditions may mean that the UE initiates a PDU session establishment procedure without using a DNN. Furthermore, the UE initiating a PDU session establishment procedure under other conditions may mean that the UE initiates a PDU session establishment procedure without using an S-NSSAI.

[0290] When the UE receives the 24th identification information, after completing this procedure, the PDU session establishment procedure using the DNN and / or S-NSSAI and / or PDU session type requested by the UE may transition to a state in which the PDU session establishment procedure is not started, stopped, or prohibited. Here, the PDU session establishment procedure using the DNN and / or S-NSSAI and / or PDU session type requested by the UE may refer to a PDU session establishment procedure that is started by the UE transmitting a PDU session establishment request message including the DNN and / or S-NSSAI and / or PDU session type previously requested. In other words, when the UE receives the 24th identification information, the PDU session establishment procedure using the same DNN and / or the same S-NSSAI and / or the same PDU session type may be prohibited, or the UE may be prohibited from transmitting a PDU session establishment request message including the same PDU session type together with the same DNN and / or the same S-NSSAI.

[0291] When the UE receives the 24th identification information, the UE may transition to a state in which a PDU session establishment procedure using the same DNN and / or the same S-NSSAI and / or the same PDU session type is prohibited for a certain period of time after the completion of this procedure. Furthermore, when the UE receives the 24th identification information, the UE may transition to a state in which transmission of a PDU session establishment request message including the same PDU session type with the same DNN and / or the same S-NSSAI is prohibited for a certain period of time after the completion of this procedure. Here, the certain period may be a period set by a back-off timer value, or may be a period set by the network or the UE.

[0292] [3.2.3. RRC Connection Release Procedure] Next, an overview of the RRC connection release procedure performed to release or suspend the RRC connection will be described with reference to FIG. 9. The RRC connection release procedure is a procedure in 5GS. Hereinafter, this procedure refers to the RRC connection release procedure. The RRC connection release procedure is a procedure for each device to release or suspend the RRC connection. Note that a base station device in an access network can start the RRC connection release procedure at any timing when the registration procedure is completed and the device is in a registered state. Also, each device may release or suspend the RRC connection based on the completion of the RRC connection release procedure.

[0293] The RRC connection release procedure may be initiated by a base station device in an access network or may be initiated by a core network device. Furthermore, the RRC connection release procedure may be initiated by being triggered by the transmission of an RRC message from the UE.

[0294] For example, the base station device and / or the core network device in the access network may start the RRC connection release procedure based on a change in the state of the UE, or may start the RRC connection release procedure based on a change in the subscriber information of the UE. Furthermore, the base station device and / or the core network device in the access network may start the RRC connection release procedure based on a change in the network setting, or may start the RRC connection release procedure based on a change in the state of the network. Furthermore, the base station device and / or the core network device in the access network may start the RRC connection release procedure based on detection that the user data transmission / reception unit is no longer present, or may start the RRC connection release procedure based on detection that the RRC connection is no longer necessary. Note that the trigger for the base station device and / or the core network device in the access network to start the RRC connection release procedure is not limited to these.

[0295] First, a base station device (gNB) in an access network starts an RRC connection release procedure by sending an RRC release message to the UE (S1000).

[0296] Specifically, the gNB transmits an RRC release message to the UE via the Uu interface (S1000). Note that the RRC release message may be an RRC message.

[0297] Here, the gNB may transmit at least the first identification information in an RRC release message, which may indicate the request of the gNB by being included in the message.

[0298] Furthermore, the gNB may indicate that the RRC connection is suspended by transmitting the first identification information. In other words, the gNB may deactivate the state of the RRC connection by transmitting the first identification information, or may suspend the state of the RRC connection.

[0299] Furthermore, the gNB may instruct the UE to suspend the RRC connection by transmitting the first identification information. Furthermore, the gNB may instruct the UE to deactivate the state of the RRC connection or to suspend the state of the RRC connection by transmitting the first identification information.

[0300] Here, suspending the RRC connection may mean putting the RRC connection in a deactivated state. Furthermore, deactivating the state of the RRC connection may mean putting the state of the RRC layer in a deactivated state. Furthermore, suspending the state of the RRC connection may mean putting the state of the RRC layer in a suspended state.

[0301] Furthermore, the gNB may transition to the RRC_INACTIVE state by transmitting the first identification information. Furthermore, the gNB may instruct the UE to transition to the RRC_INACTIVE state by transmitting the first identification information.

[0302] The UE receives an RRC release message (S900). Based on the reception of the RRC release message, the UE may recognize and store identification information included in the RRC release message.

[0303] Furthermore, the UE_R may release the RRC connection or suspend the RRC connection based on the reception of the RRC release message, and may deactivate the state of the RRC connection or suspend the state of the RRC connection based on the reception of the RRC release message.

[0304] Furthermore, the UE_R may transmit information indicating that the RRC connection has been suspended to an upper layer based on the reception of the RRC release message, and may transition to an RRC_INACTIVE state based on the reception of the RRC release message.

[0305] Here, the UE_R may be a functional unit that performs the function of the RRC layer of the UE. Furthermore, the higher layer may be a NAS layer. Furthermore, the information indicating that the RRC connection is suspended may be an indication indicating that the RRC connection is suspended. Furthermore, the information indicating that the RRC connection is suspended may be first identification information.

[0306] Furthermore, the UE_N may receive information indicating that the RRC connection has been suspended from the lower layer. Furthermore, the UE_N may transition to a 5GMM-CONNECTED mode with RRC inactive indication based on receiving information indicating that the RRC connection has been suspended from the lower layer. More specifically, the UE_N may transition from the 5GMM-CONNECTED mode to a 5GMM-CONNECTED mode with RRC inactive indication based on receiving information indicating that the RRC connection has been suspended from the lower layer.

[0307] Here, the UE_N may transition only the 3GPP access state from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on receiving information indicating that the RRC connection is suspended from a lower layer. In other words, even if the UE_N receives information indicating that the RRC connection is suspended from a lower layer, the UE_N may not transition the non-3GPP access state to 5GMM-CONNECTED mode with RRC inactive indication.

[0308] Here, the UE_N may be a functional unit that performs the function of the NAS layer of the UE. In other words, the UE_N may be a transceiver that performs the function of the NAS layer of the UE, or may be a functional unit that performs the function of the NAS layer of the UE. Furthermore, the lower layer may be an RRC layer. Furthermore, the information indicating that the RRC connection is suspended may be an indication that the RRC connection is suspended. Furthermore, the information indicating that the RRC connection is suspended may be first identification information.

[0309] Each device completes the RRC connection release procedure based on the transmission / reception of the RRC release and / or the transition to each state. Each device may release the RRC connection or suspend the RRC connection based on the completion of this procedure. Furthermore, each device may transition to a state in which the RRC connection is suspended or a state in which the RRC connection is deactivated based on the completion of this procedure. Furthermore, each device may transition to an RRC_INACTIVE state based on the completion of this procedure.

[0310] Further, each device may transition to 5GMM-CONNECTED mode with RRC inactive indication based on completion of the procedure. More specifically, each device may transition from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on completion of the procedure.

[0311] [4. First embodiment] Next, a first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In this embodiment, the UE selects one or more procedures from among the first to fourth procedures and executes them.

[0312] In addition, the UE may determine which of the first to fourth procedures to perform based on the UE's configuration information, and / or information received from the network, and / or the UE's mode, and / or the UE's capability information.

[0313] [4.1. First Procedure] Next, the first procedure will be described with reference to FIG. 6. Hereinafter, the first procedure will be referred to as this procedure. In the first procedure, first, the UE selects a first network (S600). Next, based on the first network selection, the UE connects to the selected network and starts a registration procedure (S602). Next, each device performs a registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing a PDU session establishment procedure initiated by the UE (S604), and transitions to a state in which communication using the PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session.

[0314] Next, each device may perform an RRC connection release procedure at any timing (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

[0315] Next, the UE selects a second network at any timing (S608). Next, based on the second network selection, the UE connects to the selected network and starts a registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device performs a registration procedure and / or a PDU session establishment procedure initiated by the UE (S610) (S612). Next, based on the completion of the registration procedure and / or the PDU session establishment procedure, each device transitions to a state in which communication using a PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session. With the above, the first procedure is completed.

[0316] Here, the UE may execute the second network selection based on a change in the state of the UE, or may execute the second network selection based on a change in the configured subscriber information of the UE. Furthermore, the UE may execute the second network selection based on a change in the configuration of the UE, or may execute the second network selection based on the movement of the UE. Furthermore, the UE may execute the second network selection based on receiving a control message from the network, or may execute the second network selection based on an instruction from the network. Here, the control message may be a NAS message or a control message other than a NAS message. Specifically, the control message may be a non-registration request message or a registration rejection message. Note that the trigger for the UE to execute the second network selection is not limited to these.

[0317] In addition, in the first procedure, the UE may perform PLMN selection in the first network selection to select a PLMN. More specifically, the UE may select a PLMN in the first network selection based on UE configuration information, and / or information received from the network, and / or UE mode, and / or UE capability information. Specifically, if the UE is not operating in an SNPN access mode, the UE may perform PLMN selection in the first network selection to select a PLMN.

[0318] Further, in the first procedure, the UE may be registered in the PLMN based on the first network selection. In other words, the UE may transition to a state registered in the PLMN based on the first network selection. Further, in the first procedure, the UE may be registered in the PLMN after completion of the first network selection. In other words, the UE may be in a state registered in the PLMN.

[0319] Further, in the first procedure, the UE may perform PLMN selection in the second network selection and select a PLMN. More specifically, the UE may select a PLMN in the second network selection based on UE configuration information, and / or information received from the network, and / or a mode of the UE, and / or a capability information of the UE. Further, the UE may select a PLMN in the second network selection based on a change in UE configuration information, and / or information received from the network, and / or a change in UE mode, and / or a change in UE capability information. Specifically, the UE may perform PLMN selection in the second network selection and select a PLMN if it is not operating in the SNPN access mode.

[0320] In addition, the UE may transition to a state in which the SNPN access mode is not activated if the UE selects a PLMN in the first network selection, and may transition to a state in which the SNPN access mode is not activated if the UE selects a PLMN in the second network selection.

[0321] Further, the UE may select a PLMN, connect to the selected PLMN, or both, based on the first network selection, and may transition to a state in which the PLMN is selected or a state in which the UE is registered with the PLMN, based on the first network selection.

[0322] Further, the UE may select a new PLMN, or may move from the current PLMN to the new PLMN, or both, based on the second network selection, and further, the UE may transition to a state where the new PLMN is selected, or may transition from a state where it is registered in the current PLMN to a state where it is registered in the new PLMN, based on the second network selection.

[0323] Further, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode, or may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode, based on the second network selection.

[0324] Specifically, the UE may transition to 5GMM-IDLE mode based on the selection of a PLMN other than uniform PLMN. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of a PLMN other than uniform PLMN. More specifically, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of a PLMN other than uniform PLMN if it is registered in the PLMN. Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of a PLMN other than uniform PLMN if it is not operating in SNPN access mode.

[0325] Furthermore, the UE may transition only the 3GPP access state from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of a PLMN other than uniform PLMN.

[0326] Conversely, the UE may not transition to 5GMM-IDLE mode based on the selection of a PLMN that is an even PLMN. In other words, the UE may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of a PLMN that is an even PLMN. More specifically, the UE may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of a PLMN that is an even PLMN if the UE is registered in the PLMN. Furthermore, the UE may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of a PLMN that is an even PLMN if the UE is not operating in the SNPN access mode.

[0327] In addition, the selection of a PLMN other than an even PLMN may indicate that a PLMN other than an even PLMN with respect to the registered PLMN is selected as a new PLMN. Furthermore, the selection of a PLMN other than an even PLMN may indicate that a PLMN other than an even PLMN with respect to the registered PLMN is selected as a new PLMN, and the UE enters the selected new PLMN.

[0328] Furthermore, the selection of a PLMN that is an even PLMN may indicate that a PLMN in the list of even PLMNs is selected as a new PLMN. Furthermore, the selection of a PLMN that is an even PLMN may indicate that a PLMN in the list of even PLMNs is selected as a new PLMN, and the UE enters the selected new PLMN. In other words, the selection of a PLMN that is an even PLMN may indicate that a PLMN included in the list of even PLMNs is selected as a new PLMN, and the UE enters the selected new PLMN.

[0329] Further, the UE may implement behavior C or continue behavior A based on the second network registration.

[0330] Specifically, the UE may implement behavior C based on the registration of a PLMN other than the uniform PLMN. In other words, when the UE is implementing behavior A, the UE may implement behavior C based on the registration of a PLMN other than the uniform PLMN.

[0331] Conversely, the UE may continue behavior A based on the registration of the PLMN that is the equivalent PLMN. In other words, if the UE is implementing behavior A, the UE may continue behavior A based on the registration of the PLMN that is the equivalent PLMN.

[0332] Here, behavior A may be the same as behavior A during a PDU session establishment procedure. Furthermore, behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set. Furthermore, behavior C may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted.

[0333] Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted.

[0334] Further, the UE may implement behavior D or continue behavior B based on the second network registration.

[0335] Specifically, the UE may implement behavior D based on the registration of a PLMN other than the uniform PLMN. In other words, when the UE is implementing behavior B, the UE may implement behavior D based on the registration of a PLMN other than the uniform PLMN.

[0336] Conversely, the UE may continue behavior B based on the registration of the PLMN that is the equivalent PLMN. In other words, if the UE is implementing behavior B, the UE may continue behavior B based on the registration of the PLMN that is the equivalent PLMN.

[0337] Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Furthermore, behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set. Furthermore, behavior D may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted.

[0338] Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted.

[0339] In addition, the registration of a PLMN other than an even-numbered PLMN may refer to the registration of a new PLMN that is not an even-numbered PLMN for the registered PLMN. Furthermore, the registration of a PLMN that is an even-numbered PLMN may refer to the registration of a new PLMN that is in the list of even-numbered PLMNs.

[0340] Furthermore, the same DNN may be the same DNN as the DNN transmitted and received in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN as the DNN included in the 12th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same DNN as the DNN included in the 22nd identification information and transmitted and received in the previously performed PDU session establishment procedure. Furthermore, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted and received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI included in the 13th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same S-NSSAI as the S-NSSAI included in the 23rd identification information and transmitted and received in the previously performed PDU session establishment procedure.

[0341] Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure.

[0342] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6.

[0343] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4.

[0344] Furthermore, if the request for the PDU session establishment procedure is rejected, each device may not establish a PDU session. In this case, each device may perform processing based on information included in the PDU session establishment rejection message after completing the PDU session establishment procedure, or may complete the first procedure by performing processing based on information included in the PDU session establishment rejection message.

[0345] [4.2. Second Procedure] Next, the second procedure will be described with reference to FIG. 6. Hereinafter, the second procedure will be referred to as the main procedure. In the second procedure, first, the UE selects a first network (S600). Next, based on the first network selection, the UE connects to the selected network and starts a registration procedure (S602). Next, each device performs a registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing a PDU session establishment procedure initiated by the UE (S604), and transitions to a state in which communication using the PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session.

[0346] Next, each device may perform an RRC connection release procedure at any timing (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

[0347] Next, the UE selects a second network at any timing (S608). Next, based on the second network selection, the UE connects to the selected network and starts a registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device performs a registration procedure and / or a PDU session establishment procedure initiated by the UE (S610) (S612). Next, based on the completion of the registration procedure and / or the PDU session establishment procedure, each device transitions to a state in which communication using a PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session. With the above, the second procedure is completed.

[0348] Here, the UE may execute the second network selection based on a change in the state of the UE, or may execute the second network selection based on a change in the configured subscriber information of the UE. Furthermore, the UE may execute the second network selection based on a change in the configuration of the UE, or may execute the second network selection based on the movement of the UE. Furthermore, the UE may execute the second network selection based on receiving a control message from the network, or may execute the second network selection based on an instruction from the network. Here, the control message may be a NAS message or a control message other than a NAS message. Specifically, the control message may be a non-registration request message or a registration rejection message. Note that the trigger for the UE to execute the second network selection is not limited to these.

[0349] In addition, in the second procedure, the UE may perform PLMN selection in the first network selection to select a PLMN. More specifically, the UE may select a PLMN in the first network selection based on UE configuration information, and / or information received from the network, and / or UE mode, and / or UE capability information. Specifically, if the UE is not operating in an SNPN access mode, the UE may perform PLMN selection in the first network selection to select a PLMN.

[0350] Furthermore, in the second procedure, the UE may be registered in the PLMN based on the first network selection. In other words, the UE may transition to a state registered in the PLMN based on the first network selection. Furthermore, in the second procedure, the UE may be registered in the PLMN after the first network selection is completed. In other words, the UE may be in a state registered in the PLMN.

[0351] Furthermore, in the second procedure, the UE may perform SNPN selection and select an SNPN in the second network selection. More specifically, the UE may select an SNPN in the second network selection based on UE configuration information, and / or information received from the network, and / or a mode of the UE, and / or a capability information of the UE. Furthermore, the UE may select an SNPN in the second network selection based on a change in UE configuration information, and / or information received from the network, and / or a change in UE mode, and / or a change in UE capability information. Specifically, when the UE is operating in an SNPN access mode, the UE may perform SNPN selection and select an SNPN instead of a PLMN selection in the second network selection.

[0352] In addition, if the UE selects a PLMN in the first network selection, the UE may transition to a state in which the SNPN access mode is not activated, and if the UE selects an SNPN in the second network selection, the UE may transition to a state in which the SNPN access mode is activated.

[0353] Further, the UE may select a PLMN, connect to the selected PLMN, or both, based on the first network selection, and may transition to a state in which the PLMN is selected or a state in which the UE is registered with the PLMN, based on the first network selection.

[0354] Further, the UE may select an SNPN, or may move from a PLMN to an SNPN, or both, based on the second network selection, and further, the UE may transition to a state where an SNPN is selected, or may transition from a state registered in a PLMN to a state registered in an SNPN, based on the second network selection.

[0355] Further, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the second network selection.

[0356] Specifically, the UE may transition to 5GMM-IDLE mode based on the selection of the SNPN. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of the SNPN. More specifically, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of the SNPN if it is registered in a PLMN. Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of the SNPN if it is not operating in the SNPN access mode.

[0357] Furthermore, the UE may transition only the 3GPP access state from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of the SNPN.

[0358] In addition, the selection of the SNPN may indicate that a new SNPN is selected. Furthermore, the selection of the SNPN may indicate that a new SNPN is selected and the UE enters the selected new SNPN.

[0359] Further, the UE may perform behavior C based on the second network registration.

[0360] Specifically, the UE may perform behavior C based on the registration to the new SNPN. In other words, if the UE is performing behavior A, the UE may perform behavior C based on the registration to the new SNPN.

[0361] Here, behavior A may be the same as behavior A during a PDU session establishment procedure. Furthermore, behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set. Furthermore, behavior C may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted.

[0362] Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted.

[0363] Further, the UE may implement behavior D based on the second network registration.

[0364] Specifically, the UE may implement behavior D based on the registration to the new SNPN. In other words, if the UE is implementing behavior B, the UE may implement behavior D based on the registration to the new SNPN.

[0365] Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Furthermore, behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set. Furthermore, behavior D may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted.

[0366] Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted.

[0367] In addition, registration to a new SNPN may refer to registration to a new SNPN.

[0368] Furthermore, the same DNN may be the same DNN as the DNN transmitted and received in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN as the DNN included in the 12th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same DNN as the DNN included in the 22nd identification information and transmitted and received in the previously performed PDU session establishment procedure. Furthermore, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted and received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI included in the 13th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same S-NSSAI as the S-NSSAI included in the 23rd identification information and transmitted and received in the previously performed PDU session establishment procedure.

[0369] Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure.

[0370] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6.

[0371] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4.

[0372] Furthermore, if the request for the PDU session establishment procedure is rejected, each device may not establish a PDU session. In this case, each device may perform processing based on information included in the PDU session establishment rejection message after completing the PDU session establishment procedure, or may complete the second procedure by performing processing based on information included in the PDU session establishment rejection message.

[0373] [4.3. Third Procedure] Next, the third procedure will be described with reference to FIG. 6. Hereinafter, the third procedure will be referred to as this procedure. In the third procedure, first, the UE selects a first network (S600). Next, based on the first network selection, the UE connects to the selected network and starts a registration procedure (S602). Next, each device performs a registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing a PDU session establishment procedure initiated by the UE (S604), and transitions to a state in which communication using the PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session.

[0374] Next, each device may perform an RRC connection release procedure at any timing (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

[0375] Next, the UE selects a second network at any timing (S608). Next, based on the second network selection, the UE connects to the selected network and starts a registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device performs a registration procedure and / or a PDU session establishment procedure initiated by the UE (S610) (S612). Next, based on the completion of the registration procedure and / or the PDU session establishment procedure, each device transitions to a state in which communication using a PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session. With the above, the third procedure is completed.

[0376] Here, the UE may execute the second network selection based on a change in the state of the UE, or may execute the second network selection based on a change in the configured subscriber information of the UE. Furthermore, the UE may execute the second network selection based on a change in the configuration of the UE, or may execute the second network selection based on the movement of the UE. Furthermore, the UE may execute the second network selection based on receiving a control message from the network, or may execute the second network selection based on an instruction from the network. Here, the control message may be a NAS message or a control message other than a NAS message. Specifically, the control message may be a non-registration request message or a registration rejection message. Note that the trigger for the UE to execute the second network selection is not limited to these.

[0377] In addition, in the third procedure, the UE may perform SNPN selection in the first network selection and select an SNPN. More specifically, the UE may select an SNPN in the first network selection based on UE configuration information, and / or information received from the network, and / or UE mode, and / or UE capability information. Specifically, when the UE is operating in an SNPN access mode, the UE may perform SNPN selection in the first network selection instead of PLMN selection and select an SNPN.

[0378] Furthermore, in the third procedure, the UE may be registered with the SNPN based on the first network selection. In other words, the UE may transition to a state registered with the SNPN based on the first network selection. Furthermore, in the third procedure, the UE may be registered with the SNPN after the first network selection is completed. In other words, the UE may be in a state registered with the SNPN.

[0379] Furthermore, in the third procedure, the UE may perform PLMN selection in the second network selection and select a PLMN. More specifically, the UE may select a PLMN in the second network selection based on UE configuration information, and / or information received from the network, and / or a mode of the UE, and / or a capability information of the UE. Furthermore, the UE may select a PLMN in the second network selection based on a change in UE configuration information, and / or information received from the network, and / or a change in UE mode, and / or a change in UE capability information. Specifically, the UE may perform PLMN selection in the second network selection and select a PLMN if it is not operating in the SNPN access mode.

[0380] In addition, if the UE selects an SNPN in the first network selection, the UE may transition to a state in which the SNPN access mode is activated, and if the UE selects a PLMN in the second network selection, the UE may transition to a state in which the SNPN access mode is not activated.

[0381] Further, the UE may select an SNPN, connect to the selected SNPN, or both based on the first network selection, and may transition to a state in which the SNPN is selected or a state in which the UE is registered to the SNPN based on the first network selection.

[0382] Further, the UE may select a PLMN, or may move from the SNPN to the PLMN, or both, based on the second network selection, and further, the UE may transition to a state where the PLMN is selected, or may transition from a state registered in the SNPN to a state registered in the PLMN, based on the second network selection.

[0383] Further, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the second network selection.

[0384] Specifically, the UE may transition to 5GMM-IDLE mode based on the PLMN selection. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the PLMN selection. More specifically, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the PLMN selection when registered in an SNPN. Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the PLMN selection when operating in an SNPN access mode.

[0385] Furthermore, the UE may transition only the 3GPP access state from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the PLMN selection.

[0386] In addition, the selection of the PLMN may indicate that a new PLMN is selected. Furthermore, the selection of the PLMN may indicate that a new PLMN is selected and the UE enters the selected new PLMN.

[0387] Further, the UE may perform behavior C based on the second network registration.

[0388] Specifically, the UE may, upon registration with the new PLMN, implement behavior C. In other words, if the UE is implementing behavior A, the UE may, upon registration with the new PLMN, implement behavior C.

[0389] Here, behavior A may be the same as behavior A during a PDU session establishment procedure. Furthermore, behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set. Furthermore, behavior C may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted.

[0390] Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted.

[0391] Further, the UE may implement behavior D based on the second network registration.

[0392] Specifically, the UE may implement behavior D upon registration with the new PLMN. In other words, if the UE is implementing behavior B, the UE may implement behavior D upon registration with the new PLMN.

[0393] Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Furthermore, behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set. Furthermore, behavior D may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted.

[0394] Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted.

[0395] In addition, registration to a new PLMN may refer to registration to a new PLMN.

[0396] Furthermore, the same DNN may be the same DNN as the DNN transmitted and received in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN as the DNN included in the 12th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same DNN as the DNN included in the 22nd identification information and transmitted and received in the previously performed PDU session establishment procedure. Furthermore, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted and received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI included in the 13th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same S-NSSAI as the S-NSSAI included in the 23rd identification information and transmitted and received in the previously performed PDU session establishment procedure.

[0397] Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure.

[0398] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6.

[0399] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4.

[0400] Furthermore, if the request for the PDU session establishment procedure is rejected, each device may not establish a PDU session. In this case, each device may perform processing based on information included in the PDU session establishment rejection message after completing the PDU session establishment procedure, or may complete the third procedure by performing processing based on information included in the PDU session establishment rejection message.

[0401] [4.4. Fourth Procedure] Next, the fourth procedure will be described with reference to FIG. 6. Hereinafter, the fourth procedure will be referred to as the present procedure. In the fourth procedure, first, the UE selects a first network (S600). Next, based on the first network selection, the UE connects to the selected network and starts a registration procedure (S602). Next, each device performs a registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing a PDU session establishment procedure initiated by the UE (S604), and transitions to a state in which communication using the PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session.

[0402] Next, each device may perform an RRC connection release procedure at any timing (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

[0403] Next, the UE selects a second network at any timing (S608). Next, based on the second network selection, the UE connects to the selected network and starts a registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device performs a registration procedure and / or a PDU session establishment procedure initiated by the UE (S610) (S612). Next, based on the completion of the registration procedure and / or the PDU session establishment procedure, each device transitions to a state in which communication using a PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session. With the above, the fourth procedure is completed.

[0404] Here, the UE may execute the second network selection based on a change in the state of the UE, or may execute the second network selection based on a change in the configured subscriber information of the UE. Furthermore, the UE may execute the second network selection based on a change in the configuration of the UE, or may execute the second network selection based on the movement of the UE. Furthermore, the UE may execute the second network selection based on receiving a control message from the network, or may execute the second network selection based on an instruction from the network. Here, the control message may be a NAS message or a control message other than a NAS message. Specifically, the control message may be a non-registration request message or a registration rejection message. Note that the trigger for the UE to execute the second network selection is not limited to these.

[0405] In addition, in the fourth procedure, the UE may perform SNPN selection in the first network selection and select an SNPN. More specifically, the UE may select an SNPN in the first network selection based on UE configuration information, and / or information received from the network, and / or UE mode, and / or UE capability information. Specifically, when the UE is operating in an SNPN access mode, the UE may perform SNPN selection in the first network selection instead of PLMN selection and select an SNPN.

[0406] Furthermore, in the fourth procedure, the UE may be registered with the SNPN based on the first network selection. In other words, the UE may transition to a state registered with the SNPN based on the first network selection. Furthermore, in the fourth procedure, the UE may be registered with the SNPN after the first network selection is completed. In other words, the UE may be in a state registered with the SNPN.

[0407] Furthermore, in the fourth procedure, the UE may perform SNPN selection and select an SNPN in the second network selection. More specifically, the UE may select an SNPN in the second network selection based on UE configuration information, and / or information received from the network, and / or a mode of the UE, and / or a capability information of the UE. Furthermore, the UE may select an SNPN in the second network selection based on a change in UE configuration information, and / or information received from the network, and / or a change in UE mode, and / or a change in UE capability information. Specifically, when the UE is operating in an SNPN access mode, the UE may perform SNPN selection and select an SNPN in the second network selection instead of a PLMN selection.

[0408] In addition, the UE may transition to a state in which the SNPN access mode is activated if the UE selects an SNPN in the first network selection, and may transition to a state in which the SNPN access mode is activated if the UE selects an SNPN in the second network selection.

[0409] Further, the UE may select an SNPN, connect to the selected SNPN, or both based on the first network selection, and may transition to a state in which the SNPN is selected or a state in which the UE is registered to the SNPN based on the first network selection.

[0410] Further, the UE may select a new SNPN, or may move from a current SNPN to a new SNPN, or may do both, based on the second network selection. Further, the UE may transition to a state where a new SNPN is selected, or may transition from a state where the UE is registered to the current SNPN to a state where the UE is registered to the new SNPN, based on the second network selection.

[0411] Further, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode, or may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode, based on the second network selection.

[0412] Specifically, the UE may transition to 5GMM-IDLE mode based on the selection of an SNPN other than the equal SNPN. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of an SNPN other than the equal SNPN. More specifically, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of an SNPN other than the equal SNPN if it is registered in an SNPN. Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of an SNPN other than the equal SNPN if it is operating in an SNPN access mode.

[0413] Furthermore, the UE may transition only the 3GPP access state from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of an SNPN other than an equal SNPN.

[0414] Conversely, the UE may not transition to 5GMM-IDLE mode based on the selection of an SNPN that is an equal SNPN. In other words, the UE may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of an SNPN that is an equal SNPN. More specifically, the UE may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of an SNPN that is an equal SNPN if the UE is registered in an SNPN. Furthermore, the UE may not transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of an SNPN that is an equal SNPN if operating in an SNPN access mode.

[0415] In addition, the selection of an SNPN other than the equal SNPN may indicate that an SNPN other than the equal SNPN for the registered SNPN is selected as a new SNPN. Furthermore, the selection of an SNPN other than the equal SNPN may indicate that an SNPN other than the equal SNPN for the registered SNPN is selected as a new SNPN, and the UE enters the selected new SNPN.

[0416] Furthermore, the selection of an SNPN that is an equal SNPN may indicate that an SNPN in the list of equal SNPNs is selected as a new SNPN. Furthermore, the selection of an SNPN that is an equal SNPN may indicate that an SNPN in the list of equal SNPNs is selected as a new SNPN, and the UE enters the selected new SNPN. In other words, the selection of an SNPN that is an equal SNPN may indicate that an SNPN included in the list of equal SNPNs is selected as a new SNPN, and the UE enters the selected new SNPN.

[0417] Further, the UE may implement behavior C or continue behavior A based on the second network registration.

[0418] Specifically, the UE may implement behavior C based on the registration of an SNPN other than the equal SNPN. In other words, when the UE is implementing behavior A, the UE may implement behavior C based on the registration of an SNPN other than the equal SNPN.

[0419] Conversely, the UE may continue behavior A based on the registration of an SNPN that is an equivalent SNPN. In other words, if the UE is implementing behavior A, the UE may continue behavior A based on the registration of an SNPN that is an equivalent SNPN.

[0420] Here, behavior A may be the same as behavior A during a PDU session establishment procedure. Furthermore, behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set. Furthermore, behavior C may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted. Furthermore, behavior C may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv6 set is lifted.

[0421] Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted. Furthermore, behavior C may be a behavior in which the initiation of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is configured is permitted.

[0422] Further, the UE may implement behavior D or continue behavior B based on the second network registration.

[0423] Specifically, the UE may implement behavior D based on the registration of an SNPN other than the equal SNPN. In other words, when the UE is implementing behavior B, the UE may implement behavior D based on the registration of an SNPN other than the equal SNPN.

[0424] Conversely, the UE may continue behavior B based on the registration of an SNPN that is an equivalent SNPN. In other words, if the UE is implementing behavior B, the UE may continue behavior B based on the registration of an SNPN that is an equivalent SNPN.

[0425] Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Furthermore, behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set. Furthermore, behavior D may be a behavior that recognizes that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that sets that the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted. Furthermore, behavior D may be a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is lifted.

[0426] Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted. Furthermore, behavior D may be a behavior in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type with IPv4 set is permitted.

[0427] In addition, registration of an SNPN other than an equal-value SNPN may refer to registration with a new SNPN that is not an equal-value SNPN for the registered SNPN. Furthermore, registration of an equal-value SNPN may refer to registration with a new SNPN that is in the list of equal-value SNPNs.

[0428] Furthermore, the same DNN may be the same DNN as the DNN transmitted and received in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN as the DNN included in the 12th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same DNN as the DNN included in the 22nd identification information and transmitted and received in the previously performed PDU session establishment procedure. Furthermore, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted and received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI included in the 13th identification information and transmitted and received in the previously performed PDU session establishment procedure, or the same S-NSSAI as the S-NSSAI included in the 23rd identification information and transmitted and received in the previously performed PDU session establishment procedure.

[0429] Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure that is performed after the completion of a previously performed PDU session establishment procedure.

[0430] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv6.

[0431] Furthermore, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a new PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4 may be a UE requested PDU session establishment procedure for the same DNN and / or the same S-NSSAI and a PDU session type configured with IPv4.

[0432] Furthermore, if the request for the PDU session establishment procedure is rejected, each device may not establish a PDU session. In this case, each device may perform processing based on information included in the PDU session establishment rejection message after completing the PDU session establishment procedure, or may complete the fourth procedure by performing processing based on information included in the PDU session establishment rejection message.

[0433] 5. Variations The program that runs on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of the embodiments according to the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0434] A program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium. The program may be read into a computer system and executed to implement the functions. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0435] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when a technology for integrated circuitization that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit based on that technology.

[0436] The present invention is not limited to the above-mentioned embodiment. In the embodiment, one example of the device is described, but the present invention is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV equipment, kitchen equipment, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0437] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included.

Claims

1. A UE (User Equipment), Send a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to the control device; receiving a PDU session establishment accept message from the control device, the PDU session establishment accept message including a cause value; A transmitter / receiver and a controller are provided. When the PDU session type is set to IPv4v6, the reason value is a 50th 5GSM (5G Session Management) reason value indicating that only IPv4 PDU session types are permitted, and the UE is registered in an SNPN (Stand-alone Non-Public Network), the control unit configures the transceiver unit so that a PDU session establishment procedure requested by the UE for a PDU session type in which the DNN, the S-NSSAI, and IPv6 are set is not initiated until the UE is registered in a PLMN (Public land mobile network). The UE is characterized by:

2. If the PDU session type is set to IPv4v6, the cause value is the 50th 5GSM cause value, and the UE is registered to the SNPN, the control unit configures the transceiver unit so that a PDU session establishment procedure requested by the UE for the PDU session type for which the DNN, the S-NSSAI, and IPv6 are set is not initiated until the UE is registered to a new SNPN that is not included in the list of equal SNPNs. The UE according to claim 1,

3. A UE (User Equipment), Send a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to the control device; receiving a PDU session establishment accept message from the control device, the PDU session establishment accept message including a cause value; A transmitter / receiver and a controller are provided. When the PDU session type is set to IPv4v6, the reason value is a 51st 5GSM (5G Session Management) reason value indicating that only IPv6 PDU session types are permitted, and the UE is registered in an SNPN (Stand-alone Non-Public Network), the control unit configures the transceiver unit so that a PDU session establishment procedure requested by the UE for a PDU session type in which the DNN, the S-NSSAI, and IPv4 are set is not initiated until the UE is registered in a PLMN (Public land mobile network). The UE is characterized by:

4. If the PDU session type is set to IPv4v6, the reason value is the 51st 5GSM reason value, and the UE is registered to the SNPN, the control unit configures the transceiver unit so that a PDU session establishment procedure requested by the UE for the PDU session type for which the DNN, the S-NSSAI, and IPv4 are set is not initiated until the UE is registered to a new SNPN that is not included in the list of equal SNPNs.

4. The UE according to claim 3,

5. A communication control method for a UE (User Equipment), comprising: sending a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to the control device; receiving a PDU session establishment accept message from the control device, the PDU session establishment accept message including a cause value; The PDU session type is set to IPv4v6, the cause value is a 50th 5GSM (5G Session Management) cause value indicating that only IPv4 PDU session types are allowed, and further, if the UE is registered in an SNPN (Stand-alone Non-Public Network), the UE is configured to not initiate a UE-requested PDU session establishment procedure for a PDU session type in which the DNN, the S-NSSAI, and IPv6 are set until the UE is registered in a PLMN (Public land mobile network); A UE communication control method comprising:

6. If the PDU session type is set to IPv4v6, the cause value is the 50th 5GSM cause value, and the UE is registered to the SNPN, the UE is configured to not initiate a UE-requested PDU session establishment procedure for a PDU session type for which the DNN, the S-NSSAI, and IPv6 are set, until the UE is registered to a new SNPN that is not included in the list of equal SNPNs.

6. The UE communication control method according to claim 5,

7. A communication control method for a UE (User Equipment), comprising: sending a PDU session establishment request message including a PDU (Protocol Data Unit) session type together with a DNN (Data Network Name) and an S-NSSAI (Single Network Slice Selection Assistance information) to the control device; receiving a PDU session establishment accept message from the control device, the PDU session establishment accept message including a cause value; The PDU session type is set to IPv4v6, the cause value is a 51st 5GSM (5G Session Management) cause value indicating that only IPv6 PDU session types are allowed, and further, when the UE is registered in an SNPN (Stand-alone Non-Public Network), the UE is configured to not initiate a UE-requested PDU session establishment procedure for a PDU session type in which the DNN, the S-NSSAI, and IPv4 are set until the UE is registered in a PLMN (Public land mobile network); A UE communication control method comprising:

8. If the PDU session type is set to IPv4v6, the cause value is the 51st 5GSM cause value, and the UE is registered to the SNPN, the UE is configured to not initiate a UE-requested PDU session establishment procedure for a PDU session type for which the DNN, the S-NSSAI, and IPv4 are set, until the UE is registered to a new SNPN that is not included in the list of equal SNPNs. The communication control method for a UE according to claim 7.

Images