UE(User Equipment)

Abstract

This UE provides a means in the 5GS for establishing a communication path for a specific 5G VN group selected from a plurality of 5G VN groups associated with a single DNN. The UE, in a procedure in the 5GS for the UE to establish a communication path to a 5G VN group when a plurality of 5G VN groups are associated with a single DNN, provides: appropriate information for identifying the 5G VN group to connect to; and a means for transmitting and receiving the information to and from a core network.

Description

[Technical Field]

[0001] One aspect of the present invention relates to a UE (User Equipment). This application claims priority to Japanese Patent Application No. 2020-133696, filed on August 6, 2020, the contents of which are incorporated herein by reference. [Background technology]

[0002] 3GPP (3rd Generation Partnership Project), which is currently working on standardization of mobile communication systems, is currently studying SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution).

[0003] In recent years, 3GPP has also been studying next-generation communication technologies and system architectures for 5G (5th Generation) mobile communication systems, and in particular has been working on the specification of 5GS (5G System) as a system for realizing 5G mobile communication systems (see Non-Patent Documents 1 to 4). 5GS identifies technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 23.501 V16.5.0 (2020-07); 3rd Generation Partnership Project; 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.5.0 (2020-07); 3rd Generation Partnership Project; 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.5.1 (2020-07); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) 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.

[0006] Furthermore, in 5G, a LAN-type service (5G LAN-type service) that realizes private communication in a 5G VN group, which is a group consisting of multiple terminals (User Equipment: UE) in a virtual network (VN) configured on 5GS, is being studied and specified (see Non-Patent Document 1, Non-Patent Document 2, and Non-Patent Document 3).

[0007] 3GPP is also conducting a study on enhancement of support for 5G LAN-type service (FS_5GLAN_enh), which aims to enhance the management of 5G VN Groups by establishing a one-to-many correspondence between DNNs (Data Network Names) and 5G VN Groups, instead of the conventional one-to-one correspondence.

[0008] However, the behavior of a UE when establishing a communication path for a specific 5G VN Group to which it will connect, selected from multiple 5G VN Groups associated with a single DNN, is unclear.

[0009] One aspect of the present invention has been made in consideration of the above circumstances, and aims to provide a method for implementing functional extensions related to 5G VN Group in 5GS. [Means for solving the problem]

[0010] In one aspect of the present invention, a UE (User Equipment) includes a transceiver unit, and in a PDU (Protocol Data Unit) session establishment procedure for connecting to a 5G VN (Virtual Network) group, the transceiver unit transmits a request message including a DNN (Data Network Name) and first identification information to a core network, the first identification information being information for identifying one of a plurality of 5G VN groups associated with the DNN, receives an acceptance message from the core network, and, based on receipt of the acceptance message, recognizes that it has been connected to the 5G VN group identified by the combination of the DNN and the first identification information.

[0011] In one aspect of the present invention, a UE (User Equipment) is provided with a transceiver unit, and in a PDU (Protocol Data Unit) session establishment procedure for connecting to a 5G VN (Virtual Network) group, the transceiver unit transmits a PDU session establishment request message including a DNN (Data Network Name) to a network, the DNN being a DNN associated with multiple 5G VN Groups, and receives a rejection message from the core network including second identification information, the second identification information being a reason value indicating that one of the multiple 5G VN groups associated with the DNN cannot be identified.

[0012] In one aspect of the present invention, a UE (User Equipment) includes a transceiver unit, and in a PDU (Protocol Data Unit) session establishment procedure, the transceiver unit transmits a request message to a core network and receives an acceptance message from the core network including a default DNN (Data Network Name) and third identification information, the third identification information being information for identifying a 5G VN (Virtual Network) group, and based on receiving the acceptance message, recognizes that it has been connected to the 5G VN group identified by the combination of the default DNN and the third identification information. [Effects of the Invention]

[0013] According to one aspect of the present invention, when a UE connects to a specific 5G VN Group, the UE indicates to the network the specific 5G VN Group to which it wishes to connect, selected from multiple 5G VN Groups associated with a DNN, thereby enabling the establishment of a PDU session for communication in that 5G VN Group. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). [Figure 2] FIG. 1 is a diagram illustrating the detailed configuration of a mobile communication system (EPS / 5GS). [Figure 3] FIG. 1 is a diagram illustrating the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Figure 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 10 is a diagram illustrating a registration procedure. [Figure 7] A diagram explaining the PDU session establishment procedure. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

[0022] A UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, or 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, or non-3GPP AN). A 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. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that a UE may be referred to as a user device or a terminal device.

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

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

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

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

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

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

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

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

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

[0032] The core network (core network_A and / or core network_B) and the access network (access network_A and / or access network_B) may differ depending on the mobile communication operator.

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

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

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

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

[0037] In addition, access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A may include devices not shown in Fig. 2. For example, core network _A and / or core network _B and / or PDN_A and / or DN_A may include an AUSF (Authentication Server Function) and an AAA (Authentication, Authorization, and Accounting) server (AAA-S). The AAA server may be located outside the core network.

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

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

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

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

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

[0043] [2.1. UE Device Configuration] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0066] 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 among multiple NSIs.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] Furthermore, the control plane refers to control messages transmitted and received to control UE communications, etc. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and 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 NG RAN and the N2 interface. Hereinafter, the control plane may be referred to as the control plane or the C-Plane.

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

[0084] [2.6. Description of other devices and / or functions and / or identification information in this embodiment] Next, other devices and / or functions and / or identification information will be described.

[0085] A network refers to at least a portion of an access network _B, a core network _B, and a DN. Furthermore, one or more devices included in at least a portion of an access network _B, a core network _B, and a 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 devices within the network (network devices and / or control devices) transmit, receive, receive, and / or process messages. Conversely, when a device within the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0086] In addition, the SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures 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 accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure.Each procedure may be initiated from the UE or from the NW.

[0087] Furthermore, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in procedures for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc. In addition, the procedures for MM or MM procedures may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

[0088] In addition, the 5GS (5G System) service may be a connection service provided using the core network_B190. 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] Also, 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 via a communication method other than IP.

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

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

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

[0094] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and can be IPv4, IPv6, IPv4v6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data will be transmitted and received using IPv4. If IPv6 is specified, it indicates that data will be transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be transmitted and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be transmitted and received to an application server or the like in the 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 also include IP. IP can be specified if the UE is capable of using both IPv4 and IPv6.

[0095] Also, a PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator, which is a (mobile) communications carrier, and the operator can be identified by a PLMN ID. In this document, PLMN may refer to a PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). A Visited PLMN (VPLMN) may be a PLMN different from the HPLMN or the HEPLMN (Home Equivalent PLMN). PLMN may also refer to a core network.

[0096] Furthermore, the UE may maintain an Equivalent HPLMN list in the USIM to identify one or more Equivalent HPLMNs (EHPLMNs). A PLMN different from the HPLMN and / or EHPLMN may be a Visited PLMN (VPLMN or vPLMN).

[0097] A PLMN to which a UE has successfully registered may be a Registered PLMN (RPLMN). Each device may receive, maintain, and / or store an Equivalent PLMN list from the RPLMN to identify one or more Equivalent PLMNs (EPLMNs) that can be used equivalently to the RPLMN in the UE's PLMN selection.

[0098] The current PLMN may be the PLMN requested by the UE, and / or the PLMN selected by the UE, and / or the RPLMN, and / or the PLMN allowed by the network, and / or the PLMN to which the core network device sending or receiving the message belongs.

[0099] The requested PLMN refers to the network to which the UE sends a message when the UE sends the message. Specifically, it may be the PLMN selected by the UE when the UE sends the message. The requested PLMN is the PLMN requested by the UE, and may be the current PLMN. Also, when the UE is in a registered state, the requested PLMN may be the registered PLMN.

[0100] Furthermore, the SOR (Steering of Roaming) transparent container IE may include information for the HPLMN and / or VPLMN to indicate the optimal roaming destination network to the roaming UE. Specifically, the SOR transparent information element may include a list of preferred PLMN / access technology combinations.

[0101] In addition, the SOR transparency information element and / or list of preferred PLMN / access technology combinations may be included in a "Secured packet" encrypted by the PLMN (HPLMN) using security functions, and may also be referred to as a "Secured packet."

[0102] In addition, the Steering of Roaming application function (SOR-AF), which is one of the entities in the core network, may provide information including a list of preferred PLMN / access technology combinations to the UDM, or the AMF may refer to the information including the list of preferred PLMN / access technology combinations provided to the UDM, generate a SOR transparency information element based on this information, and send it to the UE.

[0103] Here, the list of preferred PLMN / access technology combinations may be a list consisting of combinations of PLMNs (preferred PLMNs) and access technologies, and each combination may be arranged in descending order of priority.

[0104] Furthermore, for example, when a UE switches networks due to mobility or selects a PLMN in automatic mode when powering on at a roaming destination, the highest priority, usable, and allowable combination of PLMN and access technology may be selected.

[0105] A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. A network slice may also be simply referred to as a slice.

[0106] A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of required resources, forming a deployed network slice. Here, an NF is a processing function in a network, adopted or defined by 3GPP. An NSI is an entity of an NS, of which one or more are configured within a core network_B. An NSI may also be composed of a virtual network function (NF) generated using a network slice template (NST).

[0107] Here, an NST is a logical representation of one or more NFs associated with resource requirements for providing the required communication services and capabilities. In other words, an NSI may be a collection of multiple NFs within the core network_B190. An NSI may also be a logical network configured to separate user data delivered by services, etc. An NS may be configured with one or more NFs. The NFs configured in an NS may or may not be devices shared with other NSs.

[0108] A UE and / or a device in the network can be assigned to one or more NSs based on registration information such as an NSSAI, an S-NSSAI, an UE usage type, an NSI ID, or one or more APNs. The UE usage type is a parameter value included in the UE registration information and used to identify the NSI. The UE usage type may be stored in the HSS. The AMF may select an SMF and a UPF based on the UE usage type.

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

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

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

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

[0113] The Network Slice-Specific Authentication and Authorization (NSSAA) function is a function for realizing network slice-specific authentication and authorization. Network slice-specific authentication and authorization allows UE authentication and authorization to be performed outside the core network, such as by a third party. PLMNs and network devices with NSSAA functionality can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information. Furthermore, UEs with NSSAA functionality can manage, store, and send / receive pending NSSAIs and third rejected NSSAIs. In this document, NSSAA may be referred to as the network slice-specific authentication and authorization procedure or the authentication and authorization procedure.

[0114] The S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. Furthermore, the S-NSSAI requiring an NSSAA may be an S-NSSAI other than the HPLMN, where the S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device becomes a mapped S-NSSAI.

[0115] The core network and / or core network device may store an S-NSSAI requiring an NSSAA by associating the S-NSSAI with information indicating whether an NSSAA is required. The core network and / or core network device may further store an S-NSSAI requiring an NSSAA in association with information indicating whether an NSSAA has been completed, or information indicating that the NSSAA has been completed and is permitted or successful. The core network and / or core network device may manage an S-NSSAI requiring an NSSAA as information unrelated to the access network.

[0116] Also, a configured NSSAI is an NSSAI provided and stored in the UE. The UE may store a configured NSSAI for each PLMN. The UE may store a configured NSSAI in association with a PLMN. In this document, a configured NSSAI associated with a PLMN may be expressed as a configured NSSAI for the PLMN, a configured NSSAI of the PLMN, a configured NSSAI for the PLMN, or a configured NSSAI associated with the PLMN. Also, a UE may not be associated with a PLMN and may store a configured NSSAI that is valid for all PLMNs, and such a configured NSSAI may be referred to as a "default configured NSSAI."

[0117] The configured NSSAI may be associated with multiple PLMNs, which may be EPLMNs.

[0118] The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be expressed as the configured S-NSSAI. The configured S-NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI. Alternatively, the S-NSSAI of the PLMN may be expressed as the "configured S-NSSAI", and the S-NSSAI to which the configured S-NSSAI is mapped to the HPLMN may be expressed as the "mapped S-NSSAI to the configured NSSAI for the PLMN".

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

[0120] The requested NSSAI may be information indicating a network slice requested by the UE. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is transmitted in a NAS message, such as a registration request message or a PDU session establishment request message, transmitted from the UE to the network, or in a Radio Resource Control (RRC) message including a Non-Access-Stratum (NAS) message.

[0121] Also, the allowed NSSAI is information indicating one or more network slices to which the UE is permitted. In other words, the allowed NSSAI is information identifying a network slice to which the network permits the UE to connect.

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

[0123] Furthermore, the UE and / or NW may store and manage an allowed NSSAI associated with a PLMN as information of the UE. The allowed NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0124] In this document, an allowed NSSAI associated with a PLMN and an access type may be expressed as an allowed NSSAI for the PLMN and access type, or an allowed NSSAI for the access type of the PLMN. An S-NSSAI included in an allowed NSSAI may be expressed as an allowed S-NSSAI. An allowed S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0125] Furthermore, the rejected NSSAI is information indicating one or more network slices to which the UE is not permitted. In other words, the rejected NSSAI is information identifying a network slice to which the network does not permit the UE to connect. The rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value.

[0126] Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network may store and manage the rejected NSSAI appropriately based on the rejection reason value associated with each S-NSSAI.

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

[0128] The rejected NSSAI may be any one of the first to third rejected NSSAIs, the pending NSSAI, and the first NSSAI, or a combination of these. An S-NSSAI included in the rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0129] The UE and / or NW may store and manage the rejected NSSAI associated with the PLMN as information of the UE. The rejected NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0130] A pending NSSAI is a set of one or more S-NSSAIs that are pending and / or unavailable for use by the UE. A pending NSSAI may be a set of S-NSSAIs for which the network requires network slice specific authentication and for which network slice specific authentication has not been completed. A pending NSSAI may be a pending NSSAI for 5GS. A pending NSSAI may be an NSSAI stored by the UE and / or NW, or an NSSAI transmitted and received between the NW and the UE.

[0131] When the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. In this case, the rejection reason value may be "NSSAA is pending for the S-NSSAI" and may be information indicating that the S-NSSAI associated with the rejection reason value is prohibited or pending from being used by the UE until the NSSAA for that S-NSSAI is completed.

[0132] If the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be a set of combinations of the S-NSSAI and the mapped S-NSSAI.

[0133] The pending NSSAI may apply to the entire registered PLMN, to the registered PLMN and one or more EPLMNs of the registered PLMN, or to all PLMNs. A pending NSSAI that applies to all PLMNs may mean that the pending NSSAI is not associated with a PLMN, or may mean that the pending NSSAI is associated with a HPLMN.

[0134] The UE and / or NW may treat the S-NSSAI included in the pending NSSAI as information independent of the access type. That is, the pending NSSAI may be information valid for 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may be the first rejected NSSAI.

[0135] Furthermore, the pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE is pending a procedure. Specifically, while the UE stores the pending NSSAI, it does not initiate a registration request procedure for the S-NSSAI included in the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI included in the pending NSSAI is completed. The pending NSSAI is information that is independent of the access type. Specifically, when the UE stores the pending NSSAI, it does not attempt to send a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0136] 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). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking area code) and a PLMN.

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

[0138] The TAIs included in the TAI list may belong to one PLMN or multiple PLMNs. If multiple TAIs included in the TAI list belong to different PLMNs, those PLMNs may be EPLMNs.

[0139] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in an application or a network. Furthermore, the UE ID may be information for identifying a user.

[0140] A 5G LAN-type service is a service that provides private communications over 5G LTE by IP or non-IP type communications, where the IP type communications may be, for example, either IPv4, IPv6 or IPv4v6 type, and the non-IP type communications may be, for example, Ethernet type.

[0141] In addition, the 5G VN group and / or 5G VN group communication described below may be used for 5G LAN-Type services.

[0142] 5G VN (Virtual Network) is a virtual network on 5GS that supports 5G LAN-type services.

[0143] A 5G Virtual Network (VN) Group (also referred to as a 5G VN Group) is a group consisting of multiple UEs used for private communication for 5G LAN-type services.

[0144] Furthermore, User Plane (UP) communication for a 5G VN group may use any of three types of data transfer methods, where the three types of data transfer methods for User Plane communication may be any of N6-based, N19-based, and local switch.

[0145] Each of these will be explained below. First, N6-based User Plane data transfer is data transfer via DN. Next, N19-based data transfer is a state in which multiple UEs participating in a 5G VN group establish PDU sessions with different PSAs (PDU Session Anchors; UPFs that serve as the endpoints of PDU sessions), and transfers UP data using an N19 tunnel via an N19 interface that directly connects multiple PSAs used in 5G VN group communication.

[0146] When using the N19 base, the N19 tunnels may be configured in a full mesh between multiple PSAs. Local switching data transfer involves UEs participating in a 5G VN group establishing a PDU session with the same PSA (UPF) and transferring UP data locally (inside) the PSA (UPF). One or more SMFs may control the communication paths for transferring these User Plane data.

[0147] The information about the 5G VN group may include a 5G VN group ID, a 5G VN group membership, and 5G VN group data, and the 5GS uses this information to support management of the 5G VN group. Here, the 5G VN group ID may be an External Group ID and an Internal Group ID used to identify the 5G VN group. For the 5G VN group membership, a Generic Public Subscription Identifier (GPSI) may be used to uniquely identify UEs that are 5G VN group members. The 5G VN group data may include information such as a PDU session type, a DNN and S-NSSAI, and an application descriptor. In other words, the 5G VN group may be associated with the DNN and / or S-NSSAI, and the 5G VN group may be identified and specified by a combination of information including these pieces of information.

[0148] Here, the 5G VN group may be one-to-one mapped to one DNN and / or S-NSSAI, or one DNN and / or S-NSSAI may be one-to-many mapped to multiple 5G VN groups (1:N mapping), or one 5G VN group may be one-to-many mapped to one DNN and multiple S-NSSAIs, for example, when the DNN and 5G VN are one-to-one mapped, a specific 5G VN group may be specified by a specific DNN. More specifically, in a PDU session establishment procedure, the UE may include a DNN in an NAS message requesting PDU session establishment, so that each device in the core network can identify the 5G VN group and establish a PDU session for the 5G VN group.

[0149] Furthermore, for example, when a DNN and a 5G VN group are associated one-to-many, a specific DNN may be specified by a combination of identification information (information for identifying 5G VN groups) indicating one or more of the multiple 5G VN groups associated with the DNN. More specifically, in a PDU session establishment procedure, a UE may include information for identifying the DNN and the 5G VN group in an NAS message requesting PDU session establishment, and each device in the core network may identify the 5G VN group and establish a PDU session for the 5G VN group by combining this information.

[0150] Here, the identification information indicating one or more of the multiple 5G VN groups associated with the DNN may be, for example, the first identification information described below, a 5G VN Group ID (also referred to as a 5G VN group ID), an S-NSSAI, or other IDs (such as a VLAN (Virtual LAN) ID), or may be any one of these or a combination of these, and may be information that can uniquely specify a 5G VN group. In this document, identification information indicating one or more of the multiple 5G VN groups may also be referred to as information identifying a 5G VN group, a 5G VN Group ID, information specifying a 5G VN group, information identifying a group, information specifying a group, or first identification information.

[0151] Furthermore, regardless of the above, if the UE does not provide the core network with any or all of the DNN, information identifying the 5G VN group, and S-NSSAI in the PDU session establishment procedure for a 5G VN group, the core network may establish a PDU session for the UE to a default DNN and a default 5G VN group associated with the default DNN, or may not be able to establish a PDU session because it cannot identify the 5G VN group to which the UE connects, and these may be determined based on subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, etc., as will be described in more detail below.

[0152] Here, the S-NSSAI that the UE provides to the core network in the PDU session establishment procedure for the 5G VN group may be the S-NSSAI included in the allowed NSSAI that the UE received from the core network in the registration procedure, or may further be the S-NSSAI associated with the 5G VN group.

[0153] Furthermore, a 5G VN group may or may not be associated with an S-NSSAI in addition to a DNN and a 5G VN group ID. For example, a specific 5G VN group may be identified and specified by a combination of a DNN, a 5G VN group ID (information for identifying a 5G VN group), and an S-NSSAI, or may be identified by only a DNN and a 5G VN group ID. Furthermore, for example, a combination of a DNN and an S-NSSAI may enable specification of multiple 5G VN groups associated with this combination of information, and further specifying a 5G VN group ID may enable specification of one of the multiple 5G VN groups.

[0154] More specifically, in a PDU session establishment procedure for a 5G VN group, the UE may request establishment of a PDU session to a 5G VN group identified by a combination of information identifying the DNN and the 5G VN group by providing an S-NSSAI to the core network, or a PDU session to a 5G VN group identified by a combination of information identifying the DNN and the 5G VN group may be established via the S-NSSAI indicated by the UE.

[0155] Each 5G VN group may be configured as a network of a different segment. Specifically, for example, a different IPv6 prefix or an IPv4 address of a different segment may be configured for each 5G VN group, and the IPv6 prefix and / or IPv4 address configured for each 5G VN group may be assigned to a UE connecting to the 5G NV group. In other words, when the UE establishes a PDU session, the IP address assigned to the UE may be determined based on the 5G VN group provided to the network. This may enable communication within the 5G VN group to be closed to the 5G VN group. Furthermore, multiple 5G VN groups associated with one DNN may be configured as different network segments.

[0156] A PDU session for a 5G VN group is a PDU session by a DNN associated with a 5G VN group, and may be a PDU session for performing communication for the 5G VN group. The PDU session for a 5G VN group may be a PDU session established by a DNN associated with a 5G VN group in order for UE_A10 to connect to (access or join) the 5G VN group. In other words, UE_A10 connecting to a 5G VN group may be UE_A10 establishing a PDU session for the 5G VN group.

[0157] In addition, a UE that has established a PDU session for a 5G VN group may be able to perform user data communication using the PDU session for the 5G VN group with other member UEs that are accessing the same 5G VN group.

[0158] Here, for example, when establishing a PDU session for a 5G VN group, the UE may establish a PDU session for a specific 5G VN group by including a DNN in a request message. Also, for example, the UE may establish a PDU session for a specific 5G VN group by including, in addition to the DNN, identification information (e.g., first identification information described below) that specifies one or more 5G VN groups among multiple 5G VN groups associated with the DNN in the request message.

[0159] The PDU session type of the PDU session for the 5G VN group may be an IP type or a non-IP type, and the IP type may be, for example, IPv4, IPv6, or IPv4v6, and the non-IP type may be, for example, Ethernet. Furthermore, any mode for session service continuity (SSC mode 1, SSC mode 2, or SSC mode 3) may be set.

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

[0161] The first identification information in this embodiment is an allowed NSSAI that includes an S-NSSAI associated with a 5G VN group. Here, any or all of the S-NSSAIs included in the first identification information may be associated with a 5G VN group. In this document, an allowed NSSAI that does not include an S-NSSAI associated with a 5G VN group is also simply referred to as an "allowed NSSAI."

[0162] Furthermore, in the registration procedure, the UE that has received the second identification information may recognize that it is possible to execute a procedure for establishing a PDU session using an S-NSSAI associated with the 5G VN group included in the first identification information, and may execute a procedure for establishing a PDU session for the 5G VN group. Conversely, in the registration procedure, if the UE has not received the first identification information (received an allowed S-NNSAI), it may recognize that it is not possible to execute a procedure for establishing a PDU session for the 5G VN group, and must not execute a procedure for establishing a PDU session for the 5G VN group.

[0163] Furthermore, each device in the AMF or core network framework may select an S-NSSAI to be permitted for the UE to include in the first identification information based on a requested NSSAI and / or user subscription information including one or more S-NSSAs associated with a 5G VN group included by the UE in the registration request message and / or NAS message requesting registration, or network settings, or network policies, etc.

[0164] The tenth identification information in this embodiment is information for identifying a 5G VN group. Here, the tenth identification information may be information for identifying one or more of a plurality of 5G VN groups associated with one DNN (Data Network Name). In other words, a specific one or more 5G VN groups among a plurality of 5G VN groups associated with one DNN may be specified by information combining a specific DNN and the tenth identification information.

[0165] UE_A10 may transmit / provide the DNN and / or the tenth identification information to the network in a PDU session establishment procedure to access the 5G VN group. More specifically, UE_A10 may transmit a PDU session establishment request message and / or an NAS message for requesting PDU session establishment, including the DNN and / or the tenth identification information, and receive a PDU session establishment acceptance message based on the DNN and / or the tenth identification information from the core network, thereby establishing a PDU session for the 5G VN group.

[0166] Here, if UE_A10 sends a NAS message to request PDU session establishment during a PDU session establishment procedure without including a DNN and / or the 10th identification information, the AMF receiving the NAS message may establish a PDU session for a 5G VN group by using a DNN and / or the 10th identification information selected for the requested PDU session based on user subscription information, network settings, network policies, etc., and the selected DNN and / or the 10th identification information may be, for example, a default DNN and / or a default 5G NV group.

[0167] Furthermore, the 10th identification information may be identification information that can identify a specific 5G VN when combined with a DNN, or may be identification information that can identify a specific 5G VN group using only the 10th identification information.

[0168] The 15th identification information in this embodiment is a default DNN. The 15th identification information may be a DNN included in a PDU session establishment accept message received by the UE from the core network when the UE does not include a DNN in a PDU session establishment request message for requesting the establishment of a PDU session and / or a NAS message for requesting the establishment of a PDU session in the PDU session establishment procedure, and may be a DNN associated with one or more 5G VN groups.

[0169] Furthermore, the 15th identification information may be a DNN selected for the requested PDU session by the AMF that receives a PDU session establishment request message and / or a NAS message for requesting PDU session establishment during the PDU session establishment procedure based on user subscription information, network settings, network policies, etc., and a PDU session for a 5G VN group may be established using the DNN indicated by the 15th identification information and / or the 16th identification information described below.

[0170] In this embodiment, the sixteenth identification information is information for identifying a default 5G VN group. When the UE does not include the tenth identification information in the PDU session establishment request message and / or the NAS message for requesting the establishment of a PDU session in the PDU session establishment procedure, the sixteenth identification information may be information for identifying a 5G VN group included in the PDU session establishment acceptance message, the N1 SM container, the NAS message, the N2 SM information, and / or the N2 PDU session request message indicating the PDU session establishment acceptance received by the UE from the core network.

[0171] Furthermore, the 16th identification information may be information for identifying a 5G VN group selected for the requested PDU session by each device of the AMF or core network that receives a PDU session establishment request message, and / or an N1 SM container, and / or a NAS message to request the establishment of a PDU session during a PDU session establishment procedure, based on user subscription information, network settings, network policies, etc., and a PDU session for the 5G VN group may be established using the DNN indicated by the 15th identification information and / or the 16th identification information.

[0172] Furthermore, regardless of whether the UE transmits the first identification information and / or DNN in a PDU session establishment request message, an N1 SM container, and / or an NAS message for requesting establishment of a PDU session in the PDU session establishment procedure, the AMF may transmit the 16th identification information to the UE by including it in a PDU session establishment accept message, an N1 SM container, an NAS message, and / or N2 SM information and / or an N2 PDU session request message indicating acceptance of the PDU session establishment. Furthermore, whether to include the 16th identification information in the PDU session establishment accept message, an N1 SM container, an NAS message, and / or N2 SM information and / or an N2 PDU session request message may be determined by the AMF and / or each core network device based on user subscription information, a network configuration, a network policy, etc.

[0173] In this embodiment, the 17th identification information is a reason value indicating that one or more 5G VN groups among the multiple 5G VN groups associated with the DNN cannot be identified, and / or a reason value indicating that a 5G VN group cannot be identified, and / or a reason value indicating that there is no 5G VN group. Here, the 5G VN group may be one or more 5G VN groups identified by a combination of one or more identification information included in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message. In addition, here, the inability to identify a 5G VN group may mean, for example, that the UE includes a DNN associated with multiple 5G VN groups in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message, but does not include identification information for identifying one or more 5G VN groups from the multiple 5G VN groups, so that the core network and each device cannot identify the 5G VN group to which the UE is requested to connect.

[0174] Furthermore, the 17th identification information may be identification information included in a PDU session establishment rejection message sent from the core network to the UE in a PDU session establishment procedure for a 5G VN group.

[0175] Furthermore, the 17th identification information may be identification information that the core network indicates to the UE when, during a PDU session establishment procedure for a 5G VN group, the UE is unable to identify the 5G VN group based on information and / or user subscription information that the UE indicates to the core network, or network settings, or network policies, etc., and a PDU session for the 5G VN group cannot be established, and a UE that receives the 17th identification information may recognize that the PDU session establishment procedure for the 5G VN group has failed and a communication path for the 5G VN group cannot be established.

[0176] 3. First Embodiment In this embodiment, the UE establishes a PDU session for a 5G VN group by performing a registration procedure (Chapter 3.1) and a PDU session establishment procedure (Chapter 3.2).

[0177] Below, we will explain the registration procedure and PDU session establishment procedure used in this embodiment.

[0178] 3.1. Registration Procedure First, the registration procedure will be described with reference to FIG. 6. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with a network, it can execute this procedure at any time, for example, when it is powered on. In other words, if the UE is in a deregistered state (5GMM-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 (5GMM-REGISTED state) based on the completion of the registration procedure. Note that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or unregistered state) for 3GPP access and the registration state for non-3GPP access.

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

[0180] A UE may initiate a registration procedure when it moves across tracking areas (TAs). In other words, a UE may initiate a registration procedure when it moves to a TA different from the TA indicated in its TA list (TAI list or registration area). Furthermore, a UE may initiate this procedure when a running backoff timer or other timer expires. Furthermore, a UE may initiate a registration procedure when a context update for each device is required due to a PDU session disconnection or invalidation. Furthermore, a UE may initiate a registration procedure when a change occurs in the UE's capability information and / or preferences related to PDU session establishment. Furthermore, a UE may initiate a registration procedure periodically. Furthermore, a UE may initiate a registration procedure based on the completion of a UE configuration update procedure, a registration procedure, a PDU session establishment procedure, a PDU session management procedure, information received from the network in each procedure, or the expiration or stopping of a backoff timer. Note that the UE may perform the registration procedure at any timing, not limited to these.

[0181] The procedure for the UE to transition from a state where it is not registered in the network to a state where it is registered may be referred to as an initial registration procedure or a registration procedure for initial registration, and the registration procedure performed when the UE is registered in the network may be referred to as a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0182] In addition, the UE may perform PLMN selection before the registration procedure or in the initial state of the registration procedure to select and determine the PLMN required by the UE.

[0183] 6 indicates the AMF to which UE_A10 is registered by this procedure, and old AMF142 refers to the AMF to which the UE was registered by a procedure prior to this procedure. If no AMF change occurs in this procedure, the interface between old AMF142 and new AMF141 and the procedure between old AMF142 and new AMF141 do not occur, and new AMF141 may be the same device as old AMF142. In this embodiment, when referring to AMF, it may mean new AMF141, old AMF142, or both. Note that new AMF141 and old AMF142 may be AMF140.

[0184] First, UE_A10 starts the registration procedure by sending a registration request message to new AMF141 (S600) (S602) (S604). Specifically, the UE sends an RRC message including a registration request message to 5G AN120 (or gNB) (S600). Note that the registration request message is a NAS message transmitted and received on the N1 interface. Also, the RRC message may be a control message transmitted and received between the UE and 5G AN120 (or gNB). Also, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

[0185] Here, UE_A10 can transmit the requested NSSAI by including it in a registration request message and / or an RRC message. Here, the requested NSSAI transmitted by the US in the registration request message and / or the RRC message may include one or more S-NSSAIs associated with the 5G VN group. Furthermore, UE_A10 may transmit the registration request message and / or the RRC message by including identification information indicating the type of this procedure. Here, the identification information indicating the type of this procedure may be a 5GS registration type IE, and may be information indicating that this procedure is a registration procedure for initial registration, for updating registration information due to movement, for updating registration information periodically, or for emergency registration.

[0186] UE_A10 may include UE capability information in the registration request message to notify the network of the functions supported by UE_A10, where the UE capability information may be 5G MM capability of 5GS.

[0187] UE_A10 may transmit this identification information in a different control message, for example, a control message of a layer lower than the RRC layer (for example, the MAC layer, RLC layer, or PDCP layer).By transmitting this identification information, UE_A10 may indicate that UE_A10 supports each function, or may indicate a UE request, or may indicate both.In addition, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0188] Furthermore, UE_A10 may select and decide whether to send these identification information to the network based on the UE's capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, etc.

[0189] UE_A10 may include other identification information in the registration request message and / or the RRC message containing the registration request message, for example, the UE ID and / or PLMN ID and / or AMF identification information and / or requested NSSAI.

[0190] Here, the AMF identification information may be information that identifies an AMF or a set of AMFs, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0191] If UE_A10 stores "an allowed NSSAI associated with the PLMN requested by the UE and the access type requested by the UE," and / or stores "a configured NSSAI for the requested PLMN," and / or stores "a default configured NSSAI," the UE may include the requested NSSAI in a registration request message and send it to the requested PLMN.

[0192] Alternatively, if the UE stores an "allowed NSSAI associated with a PLMN other than the PLMN requested by the UE and the access type requested by the UE," and if that allowed NSSAI or an S-NSSAI included in the allowed NSSAI is further associated with the requested PLMN, UE_A10 may include the requested NSSAI in a registration request message and send it to the requested PLMN.

[0193] Here, the case where an allowed NSSAI associated with a PLMN other than the PLMN requested by the UE or an S-NSSAI included in the allowed NSSAI is associated with the requested PLMN may mean, for example, that UE_A10 stores the allowed NSSAI in association with multiple PLMNs (the requested PLMN and other PLMNs).

[0194] Alternatively, a case where an allowed NSSAI associated with a PLMN different from the PLMN requested by the UE or an S-NSSAI included in the allowed NSSAI is associated with the requested PLMN may be a case where the UE stores an allowed NSSAI associated with a PLMN different from the PLMN requested by the UE or an S-NSSAI included in the allowed NSSAI, and a PLMN list that supports that S-NSSAI, and the PLMN requested by the UE is included in that PLMN list.

[0195] UE_A10 may also include in the requested NSSAI an S-NSSAI included in an allowed NSSAI associated with a PLMN different from the PLMN requested by the UE.

[0196] Alternatively, UE_A10 may include the mapped S-NSSAI of an S-NSSAI included in an allowed NSSAI associated with a PLMN different from the PLMN requested by the UE in the 5GS Requested mapped NSSAI.

[0197] Alternatively, in the registration request procedure to the VPLMN, UE_A10 may include the S-NSSAI contained in the allowed NSSAI associated with the HPLMN in the 5GS Requested mapped NSSAI and send it to the network.

[0198] In addition, UE_A10 may initiate a PDU session establishment procedure during the registration procedure by sending an 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.

[0199] When the 5G AN 120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to forward the registration request message (S602). Note that the 5G AN 120 (or gNB) can select an AMF based on one or more pieces of identification information included in the registration request message and / or the RRC message including the registration request message. Specifically, the 5G AN (or gNB) may select the new AMF 141 to which the registration request message is to be sent based on the requested NSSAI, or may select the new AMF 141 to which the registration request message is to be sent based on the requested NSSAI including an S-NSSAI associated with a 5G VN group.

[0200] For example, the 5G AN120 (or gNB) may select an AMF that supports functionality for 5G VN group communication based on the requested NSSAI including an S-NSSAI associated with the 5G VN group.

[0201] Note that the method for selecting an AMF is not limited to this, and the 5G AN (or gNB) may select an AMF based on other conditions. The 5G AN (or gNB) extracts a registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). Note that if these identification information items are not included in the registration request message but are included in the RRC message, the identification information included in the RRC message may be transferred to the selected AMF (new AMF 141) together with the registration request message (S604).

[0202] When the new AMF 141 receives a registration request message, it can execute a first condition determination. The first condition determination is for determining whether the network (or the new AMF 141) accepts the UE's request. When the first condition determination is true, the new AMF 141 executes the procedures from S606 to S612. On the other hand, when the first condition determination is false, the new AMF 141 may execute the procedure of S610 without executing the procedures from S606 to S608.

[0203] Alternatively, the new AMF 141 may request the UE context from the old AMF 142 and perform the first condition determination after receiving the UE context from the old AMF 142 (S606, S608). In this case, the new AMF 141 may execute S610 and / or S612 if the first condition determination is true. On the other hand, the new AMF 141 may execute S610 if the first condition determination is false.

[0204] Here, if the first condition determination is true, the control message sent and received in S610 may be a Registration accept message, and if the first condition determination is false, the control message sent and received in S610 may be a Registration reject message.

[0205] Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or each identification information contained 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 context held by the AMF, etc.

[0206] For example, if the network permits the UE's request, the first condition determination may be true, and if the network does not permit the UE's request, the first condition determination may be false. Furthermore, if the network to which the UE is registered and / or a device within the network supports the function requested by the UE, the first condition determination may be true, and if the function requested by the UE is not supported, 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.

[0207] Furthermore, if the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information identifying a slice requiring an NSSAA procedure, and if the AMF stores the result of the NSSAA procedure for the corresponding S-NSSAI for the UE as successful, the first condition determination may be true. Alternatively, if there is no S-NSSAI to allow for the UE and there are no plans to assign an allowed NSSAI to the UE in the future, the first condition determination may be false.

[0208] Furthermore, if the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information identifying a slice that requires management of the maximum number of UEs connected to the slice, and if the maximum number of UEs has not been reached, the first condition determination may be true. Alternatively, even if there is no S-NSSAI to allow for the UE, if it is expected that an allowed NSSAI will be assigned to the UE in the future, the first condition determination may be true.

[0209] When the AMF allocates the first NSSAI to the UE when there is no S-NSSAI to grant to the UE, the first condition determination may be true or false.

[0210] If the AMF indicated in the AMF identification information included in the message received by new AMF 141 from the UE is old AMF 142, new AMF 141 executes the procedures of S606 and S608, and if the AMF indicated in the AMF identification information included in the message received by new AMF 141 from UE_A10 is new AMF 141, new AMF 141 does not execute the procedures of S606 and S608. In other words, if an AMF change occurs due to this procedure, the procedures of S606 and S608 are executed, and if no AMF change occurs, the procedures of S606 and S608 are skipped.

[0211] The UE context transfer procedure (S606, S608) will be described. The new AMF 141 sends a UE context request message to the old AMF 142 (S606). The old AMF 142 sends the UE context to the new AMF 141 based on the received UE context request message. The new AMF 141 generates a UE context based on the received UE context.

[0212] Here, the UE context transmitted from new AMF 141 to old AMF 142 may include a UE ID and an allowed NSSAI. Furthermore, the UE context may include a configured NSSAI and / or a rejected NSSAI, an NSSAI and / or a pending NSSAI, and / or a first NSSAI. Furthermore, the allowed NSSAI, and / or the configured NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first NSSAI included in the UE context, and the S-NSSAI included in each NSSAI may be linked to information on whether notification to the UE has been completed.

[0213] The UE context may also include information on S-NSSAI that requires an NSSAA procedure, and / or information indicating that the NSSAA procedure has been completed for the UE, that authentication has been successful, and / or information indicating that authentication has failed.

[0214] The UE context may also include information on S-NSSAI, which requires management of the maximum number of UEs connected to a slice, and / or information indicating that the maximum number of UEs has been reached, and / or information indicating whether the maximum number of UEs connected to a slice has been reached.

[0215] In addition, information regarding the characteristics of these S-NSSAIs may be managed as a single piece of information. Specifically, the network may associate and store, for each S-NSSAI, information indicating whether NSSAA is required, whether NSSAA was successful, whether management of the maximum number of UEs connecting to the slice is required, and whether the maximum number of UEs connecting to the slice has been reached.

[0216] The new AMF 141 may send a control message to the UE based on the determination of the first condition determination and / or based on receiving the UE context from the old AMF 142 (S610). The control message may be a registration accept message or a registration reject message. The following describes the case where the control message sent to the UE is a registration accept message.

[0217] The new AMF 141 may transmit a control message including one or more pieces of identification information. By transmitting one or more pieces of identification information and / or a control message, the new AMF 141 may indicate that the network supports each function, may indicate that a request from the UE has been accepted, may indicate that a request from the UE is permitted or not supported, or may indicate a combination of these. 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 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.

[0218] The new AMF141 may further include the configured NSSAI, and / or the allowed NSSAI, and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first NSSAI in a control message and send it to UE_A10.

[0219] Here, the allowed NSSAI transmitted by the new AMF 141 may be first identification information. Here, by transmitting identification information and / or a control message including the first identification information, the new AMF 141 may indicate that the network supports each function related to the 5G VN group, may indicate that the UE is permitted to use one or more S-NSSAIs associated with the 5G VN group, may indicate that the UE's request has been accepted, may indicate that the request from the UE is not permitted or supported, or may indicate a combination of these. Based on receiving the first identification information, the UE may recognize that a PDU session for the 5G VN group can be established using the S-NSSAI associated with the 5G VN group included in the first identification information, may perform a PDU session establishment procedure for the 5G VN group, or may simply recognize that a PDU session for the 5G VN group can be established.

[0220] Conversely, if the allowed NSSAI sent by new AMF141 is not the first identification information, it may recognize that the S-NSSAI associated with the 5G VN group is not allowed, or that a PDU session cannot be established for the 5G VN group, and may not perform a PDU session establishment procedure for the 5G VN group.

[0221] In addition, when new AMF141 sends the control message, regardless of whether it is associated with a 5G VN group, there is no S-NSSAI (allowed NSSAI) to allow the UE, but if there are plans to perform an NSSAA procedure after completion of this procedure or in parallel with this procedure, or if an NSSAA procedure is being performed between the UE and the network, or if a pending NSSAI is sent in the control message, new AMF141 may send an empty value in the allowed NSSAI or first identification information.

[0222] Furthermore, when the control message is a registration acceptance message, the AMF can include an SM message (e.g., a PDU session establishment acceptance message) in the registration acceptance message and send it, or can send an SM message (e.g., a PDU session establishment acceptance message) together with the registration acceptance message. However, this sending method may also be performed when an SM message (e.g., a PDU session establishment request message) is included in the registration request message. Also, this sending method may be performed when an SM message (e.g., a PDU session establishment request message) is sent together with the registration request message. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure.

[0223] In addition, the AMF may indicate that the UE's request has been accepted by sending a registration acceptance message, or may indicate that the UE's request has been rejected by sending a registration rejection message, based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0224] The UE receives a control message via the 5G AN (gNB) (S608). If the control message is a registration acceptance message, the UE can recognize by receiving the registration acceptance message that the UE's request in the registration request message has been accepted and the contents of various identification information included in the registration acceptance message. Alternatively, if the control message is a registration rejection message, the UE can recognize by receiving a registration rejection message that the UE's request in the registration request message has been rejected and the contents of various identification information included in the registration rejection message. Furthermore, if the UE does not receive a control message even after a predetermined period has elapsed since sending the registration request message, the UE may recognize that the UE's request has been rejected.

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

[0226] The AMF receives a registration completion message via the 5G AN (gNB) (S612). In addition, each device completes this procedure based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0227] Alternatively, each device may complete the registration procedure based on sending and receiving a registration rejection message.

[0228] Each device may transition to or maintain a state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on sending and receiving a registration accept message and / or a registration complete message, or may transition to or maintain a state in which the UE is not registered in the network on the access from which the registration reject message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on sending and receiving a registration reject message. Also, the transition to each state of each device may be based on sending and receiving a registration complete message or completion of the registration procedure.

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

[0230] Furthermore, 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 based on the completion of the registration procedure.

[0231] Furthermore, the UE may delete one or more stored NSSAIs based on the completion of the registration procedure. Specifically, based on the completion of this procedure, if UE_A10 transitions to an unregistered state on both accesses (3GPP access and non-3GPP access) for the current PLMN, UE_A10 may delete the first rejected NSSAI and / or the third rejected NSSAI and / or the first NSSAI that it stores.

[0232] Furthermore, based on the completion of this procedure, if UE_A10 transitions to an unregistered state on an access (3GPP access and non-3GPP access) for the current PLMN, or if UE_A10 successfully completes the registration procedure in the new registration area, or if UE_A10 transitions to an unregistered state or a registered state on an access as a result of performing the registration procedure in the new registration area, UE_A10 may delete the second rejected NSSAI associated with the current PLMN, the current registration area, and / or its access type.

[0233] Furthermore, each device may initiate the registration procedure again upon expiration or stopping of the back-off timer.

[0234] Additionally, each device may initiate the registration process again based on the updated NSSAI it stores.

[0235] Furthermore, each device may initiate an SM procedure by sending or receiving an SM message based on the UE transitioning to or maintaining a state in which it is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state).

[0236] [3.2. PDU Session Establishment Procedure] Next, the PDU session establishment procedure that a UE executes to establish a PDU session after executing the registration procedure in Chapter 3.1 one or more times will be described using Figures 1, 2, and 7. Here, we will describe the execution of a procedure to establish a PDU session for a specific 5G VN group indicated by the UE when multiple 5G VN groups are associated with one DNN. Hereinafter, the PDU session establishment procedure will also be referred to as the PDU session establishment procedure, the PDU session establishment procedure for a 5G VN group, the PDU session establishment procedure for connecting to a 5G VN GROUP, or this procedure.

[0237] Furthermore, each device may execute this procedure after completing the registration procedure, or may execute it during the registration procedure. Also, each device may start this procedure while in the registration state, or may start this procedure at any time after the registration procedure. On the other hand, if a registration acceptance message that does not include first identification information is received during the registration procedure described in Chapter 3.1, this procedure described below may not be executed, and a normal PDU session establishment procedure may be executed.

[0238] In addition, each device may establish a PDU session based on the completion of the PDU session establishment procedure. Furthermore, each device may establish multiple PDU sessions by performing this procedure multiple times.

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

[0240] In addition, the UE can notify the network side of its request by sending a PDU session establishment request message, and / or an N1 SM container, and / or an NAS message including a DNN and 10 identification information associated with one or more 5G VN groups.

[0241] Here, the UE may request establishment of a PDU session for one or more 5G VN groups to which the UE requests connection by transmitting and receiving a DNN and tenth identification information associated with the multiple 5G VN groups. Also, by transmitting a DNN and tenth identification information associated with the multiple 5G VN groups, each device in the core network may be able to identify one 5G VN group from the multiple 5G VN groups associated with one DNN.

[0242] Furthermore, the UE may include a PDU session type in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message. The PDU session type for accessing a 5G VN group may be an IP type or an Ethernet type, and the PDU session type included in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message may be IPv4, IPv6, IPv4v6, or Ethernet. It may be a PDU session type usable for 5G VN group communication, or may be a PDU session type determined for each 5G VN group based on user subscription information, network settings, network policies, 5G VN policies, and / or 5G VN group settings, etc.

[0243] Furthermore, the UE may include one or more S-NSSAIs in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message, and may request establishment of a PDU session for a 5G VN group identified by a combination of the following information: For example, the 5G VN group may be identified and specified by a combination of the DNN, the tenth identification information, and the S-NSSAI, or may be identified by the DNN and the tenth identification information alone. Also, for example, the combination of the DNN and the S-NSSAI may enable specification of multiple 5G VN groups associated with this combination of information, and further specifying a 5G VN group ID may enable specification of one 5G VN group from among these multiple 5G VN groups.

[0244] Furthermore, the UE may determine the DNN, the tenth identification information, and / or the PDU session type associated with one or more 5G VN groups to be sent to the network based on information preconfigured in the UE, and / or the UE's terminal settings, and / or the user of the UE or an application running on the UE, and / or the UE's capability information, and / or the UE policy, and / or the UE's status, and / or the user's registration information, and / or the context held by the UE, etc.

[0245] In addition, the UE may transmit this identification information in a control message other than the above, such as a control message of a layer lower than the NAS layer (e.g., RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.) or a control message of a layer higher than the NAS layer (e.g., transport layer, session layer, presentation layer, application layer, etc.).

[0246] Conversely, the UE may transmit a PDU session establishment request message, an N1 SM container, and / or an NAS message without including a DNN and tenth identification information associated with one or more 5G VN groups. In this case, as described below, a PDU session may be established based on information (5G VN ID) identifying a DNN and / or a 5G VN group, for example, a default value, determined based on user subscription information, network settings, network policy, etc. Furthermore, the information identifying a DNN and / or default 5G VN group determined based on user subscription information, network settings, network policy, etc. may be a default DNN or a default 5G VN group ID (default 5G VN ID).

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

[0248] Next, the AMF selects an SMF as a transfer destination for at least part of the information (message, container, information) contained in the NAS message received from the UE (S802). The AMF may select the transfer destination SMF based on the information (message, container, information) contained in the NAS message, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc. Here, it is assumed that SMF_220 (hereinafter also referred to as SMF) is selected.

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

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

[0251] Note that the selected SMF may take the initiative to execute a secondary authentication / authorization procedure during this procedure, as necessary. The secondary authentication / authorization procedure may be manually executed by the SMF when the UE transmits a PDU session establishment request message, and / or an N1 SM container, and / or an NAS message, including an SM PDU DN request container information element. Furthermore, the DN-AAA server that performs authentication / authorization in the secondary authentication / authorization procedure may be associated with the 5G VN group to which the UE connects in this procedure, and may be used to authenticate / authorize a PDU session for the 5G VN group. Here, the IP address of the UE when the secondary authentication / authorization procedure is executed and successful may be assigned by the DN-AAA server, not by the SMF (described later), and may be associated with each 5G VN group and usable for communication for each 5G VN group. Specifically, for example, a different IPv6 prefix may be assigned for each 5G VN group.

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

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

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

[0255] For example, if the network permits the UE's request, the determination of the second condition may be true, and if the network does not permit the UE's request, the determination of the second condition may be false. Furthermore, if the network to which the UE is connected and / or a device within the network supports the function requested by the UE, the determination of the second condition may be true, and if the function requested by the UE is not supported, the determination of the second condition may be false. Furthermore, if the transmitted and received identification information is permitted, the determination of the second condition may be true, and if the transmitted and received identification information is not permitted, the determination of the second condition may be false. The conditions for determining whether the second condition is true or false are not limited to the above-described conditions.

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

[0257] Next, if the PDU session type included by the UE in the PDU session establishment request message, the N1 SM container, and / or the NAS message is an IP type (IPv4, IPv6, or IPv4v6), the SMF assigns an IP address and / or prefix to the UE. Here, the IP address and / or prefix assigned to the UE may be associated with the 5G VN group provided by the UE to the network and may be usable for 5G VN group communication. Furthermore, the IP address and / or prefix assigned to the UE may be included in a PDU Address Information Element (IE) included in the PDU session establishment accept message, the N1 SM container, the NAS message, the N2 SM information, and / or the N2 PDU session request message, and transmitted to the UE. If an IP address or prefix has been assigned by the DN-AAA server in the secondary authentication / authorization procedure, the SMF does not need to assign it, and the IP address and / or prefix assigned to the UE by the DN-AAA server may be included in a PDU Address Information Element (IE) included in a PDU session establishment accept message, and / or an N1 SM container, and / or an NAS message, and / or an N2 SM information, and / or an N2 PDU session request message, and transmitted to the UE. Also, if the PDU session type transmitted by the UE to the core network is an Ethernet type, the SMF does not assign a MAC address (Media Access Control address).

[0258] Next, the SMF selects a UPF for the PDU session to be established. Here, the UPF may be selected based on information (such as a 5G VN Group ID) for identifying one or more 5G VNs identified by the DNNs associated with multiple 5G VN groups and the first identification information, which the UE includes in any of various messages for requesting establishment of a PDU session. More specifically, for example, when establishing two PDU sessions for 5G VN Group #1 and 5G VN Group #2 using the same combination of DNN and / or S-NSSAI, UPF #1 may be selected as the PDU session anchor (PSA) for 5G VN Group #1, and UPF #2 may be selected as the PSA for the PDU session for 5G VN Group #2.

[0259] Next, the UE may send an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S808). The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

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

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

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

[0263] Next, the SMF sends an N1 SM container, N2 SM information, and / or PDU session ID to the AMF, for example, via the N11 interface, based on the reception of the PDU session establishment request message, and / or the selection of the UPF, and / or the reception of the N4 session establishment response message (S812), where the N1 SM container may include a PDU session establishment accept message.

[0264] Next, the AMF that has received the N1 SM container, and / or the N2 SM information, and / or the PDU session ID, transmits a NAS message to the UE via a base station device included in the access network (S814) (S816). Here, the NAS message is transmitted, for example, via the N1 interface. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

[0265] Specifically, the AMF transmits an N2 PDU session request message to a base station device included in the access network (S814). The base station device that receives the N2 PDU session request message transmits an NAS message to the UE (S816). Here, the N2 PDU session request message may include an NAS message and / or N2 SM information. The NAS message may also include a PDU session ID and / or an N1 SM container.

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

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

[0268] Here, when the UE includes the DNN and / or the tenth identification information in a PDU session establishment request message, and / or an N1 SM container, and / or an NAS message and sends it to the core network, the SMF and / or AMF may include the DNN and / or the tenth identification information in part or all of a PDU session establishment request message, and / or an N1 SM container, and / or an NAS message, and / or an N2 SM information, and / or an N2 PDU session request message. In this case, the UE may recognize that a PDU session for the 5G VN group requested by the UE has been established.

[0269] In addition, here, if the UE does not include the DNN and / or the tenth identification information in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message, the SMF and / or the AMF may include at least one of the fifteenth and / or sixteenth identification information in the PDU session establishment accept message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message and send it to the UE. In this case, the UE may recognize that a PDU session for the 5G VN group indicated by the fifteenth and / or sixteenth identification information has been established.

[0270] In addition, the 15th identification information and / or the 16th identification information may be identification information determined based on user subscription information, network settings, network policies, etc., or may be default values.

[0271] In addition, the 15th identification information may be associated with the 16th identification information, and the 15th identification information and / or the 16th identification information may be associated with one or more S-NSSAIs included in the first identification information received in the registration acceptance message during the registration procedure described in Chapter 3.1.

[0272] Furthermore, the UE may store information on the 5G VN group identified by the received 15th identification information and / or 16th identification information together with these identification information. In other words, the UE may store information on the 5G VN group in association with information identifying the DNN and / or the 5G VN group and / or S-NSSAI.

[0273] By transmitting these identification information and / or the PDU session establishment acceptance message, the SMF may indicate that the network supports each function, that the UE request has been accepted, that the UE request has not been permitted, or a combination of these. Furthermore, when multiple identification information is 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 of each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

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

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

[0276] Next, when the UE receives the NAS message (S816), for example, via the N1 interface, it can recognize that the UE's request in the PDU session establishment request message has been accepted and / or the contents of the information (message, container, information) included in the NAS message. For example, the UE may recognize that a PDU session for the 5G VN group has been established based on the received DNN and / or tenth identification information and / or fifteenth identification information and / or sixteenth identification information. The UE may also recognize information identifying the 5G VN group indicated by the tenth identification information and / or sixteenth identification information (5G VN group ID).

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

[0278] First, based on receiving the PDU session establishment request message, the SMF sends an N1 SM container and / or a PDU session ID to the AMF, for example, via the N11 interface (S818), where the N1 SM container may include a PDU session establishment rejection message.

[0279] Next, the AMF that has received the N1 SM container and / or the PDU session ID transmits a NAS message to the UE via a first base station device included in the access network (S820) (S822). Here, the NAS message is transmitted, for example, via an N1 interface. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may include the PDU session ID and / or the N1 SM container.

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

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

[0282] By sending a PDU session establishment rejection message, the SMF may indicate that the network does not support each function, that the UE request has been rejected, that the UE request has not been authorized, or a combination of these. Furthermore, when multiple identification information is 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 of each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

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

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

[0285] Furthermore, here, the 17th identification information may be identification information to be included when the AMF and / or SMF and / or core network device cannot identify the 5G VN group when the UE transmits a PDU session establishment request message, an N1 SM container, and / or a NAS message including only one of the DNN and the tenth identification information associated with one or more 5G VN groups in the PDU session establishment procedure for connecting to a 5G VN group. Furthermore, the 17th identification information may be identification information to be included when the AMF and / or SMF and / or core network device recognizes that the 5G VN group identified by the combination of the DNN and / or the tenth identification information is unavailable or has become unavailable. Furthermore, the 17th identification information may be identification information to be included when the AMF and / or SMF and / or core network device recognizes that there is no 5G VN group to which the UE is connected by default, as indicated by the 15th and / or 16th identification information.

[0286] Furthermore, when the UE includes the DNN and / or the 10th identification information in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message, the UE that receives the 17th identification information may recognize that the establishment of the PDU session for the 5G VN group has failed, may recognize that there is an error in the combination of the DNN and / or the 10th identification information that the UE sent to the core network, or may recognize that the 5G VN group identified by the combination of the DNN and / or the 10th identification information is unavailable or has become unavailable.

[0287] Furthermore, if the UE does not include the DNN and / or the 10th identification information in the PDU session establishment request message, and / or the N1 SM container, and / or the NAS message, a UE that receives the 17th identification information may recognize that the establishment of a PDU session for the 5G VN group has failed, or may recognize that there is no 5G VN group to which the UE is connected by default, as indicated by the 15th and / or 16th identification information.

[0288] The 17th identification information may be identification information determined based on user subscription information, network settings, network policies, or the like.

[0289] Next, when the UE receives the NAS message (S822), for example via the N1 interface, it can recognize that the UE's request via the PDU session establishment request message has been rejected and / or the contents of the information, etc. (message, container, information) contained in the NAS message.

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

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

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

[0293] Furthermore, each device may store the information transmitted and received in this procedure in association with each other.

[0294] 5. Variations A program running on an apparatus according to the present invention may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment 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 another storage device system.

[0295] 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. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may also refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0296] Additionally, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, such as an integrated circuit or multiple integrated circuits. The electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electrical circuit may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge that replace current integrated circuits, one or more aspects of the present invention may utilize new integrated circuits based on that technology.

[0297] The present invention is not limited to the above-described embodiment. Although one example of a device has been described in the embodiment, 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 for AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0298] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications 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 substituted with elements that achieve the same effect are also included.

Claims

1. A UE (User Equipment), A transmitter / receiver and a controller are provided, In a PDU (Protocol Data Unit) session establishment procedure for connecting to a 5G VN (Virtual Network) group, the transceiver unit: Sending a request message to the core network, the request message including a DNN (Data Network Name) and first identification information; The first identification information is information different from the DNN for identifying one of a plurality of 5G VN groups associated with the DNN, The first identification information is further information indicating a default 5G VN group, receiving an acceptance message from the core network; The control unit recognizes that it has been connected to the 5G VN group identified by the combination of the DNN and the first identification information based on the reception of the acceptance message. A UE characterized by:

2. The 5G VN group is further identified by a combination of the DNN, the first identification information, and S-NSSAI (Single Network Slice Selection Assistance Information), 2. The UE of claim 1 .

Images