UE(User Equipment)

Abstract

Communication means are provided to realize a function relating to management of information for appropriate PLMN selection, taking into consideration network slice support for each PLMN in 5GS. Provided are a method for acquisition of information in an initial registration of UE, procedures for updating information, and PLMN selection based on information, and communication means, to realize management of information for appropriate PLMN selection, taking into consideration network slice support by a PLMN at a relocation destination of UE.

Description

[Technical field]

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

[0002] 3GPP (3rd Generation Partnership Project), which is involved in the standardization of recent 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 the 5th Generation (5G) mobile communication system, and in particular has been working on the specification of the 5GS (5G System) as a system for realizing the 5G mobile communication system (see Non-Patent Documents 1 to 4). In 5GS, technical issues for connecting a wide variety of terminals to a cellular network are being extracted and solutions are being specified. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 23.501 V16.4.0 (2020-03); 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.4.0 (2020-03); 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.4.1 (2020-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) [Non-Patent Document 4] 3GPP TS 23.122 V16.5.0 (2020-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 16) [Non-Patent Document 5] 3GPP TR 23.700-40 V0.3.0 (2020-01);3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of network slicing; Phase 2 (Release 17) Summary of the Invention [Problem to be solved by the invention]

[0005] In the 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services.

[0006] Furthermore, in 5G, network slices, which are logical networks that provide specific network functions or specific network characteristics for a specific service type or a specific group, are defined. For example, a network slice may be a logical network provided for a terminal with a low latency function, or a logical network provided for a sensor terminal used in the Internet of Things (IoT).

[0007] 3GPP is also studying Enhancement of Network Slicing (eNS) to consider further functions related to network slicing. In Phase 2 of eNS, 3GPP is considering adding a function for selecting an appropriate visited mobile network (VPLMN) in consideration of support for slices used in a home mobile network (HPLMN) at a UE's destination (see Non-Patent Document 5).

[0008] However, the realization method for satisfying the above requirements is not yet clear.

[0009] One aspect of the present invention has been made in consideration of the above circumstances, and provides a method for implementing functions for eNS in 5GS. [Means for solving the problem]

[0010] In one aspect of the present invention, a UE (User Equipment) includes a transceiver unit, a control unit, and a storage unit, and the transceiver unit receives, in a first PLMN (Public Land Mobile Network), a registration acceptance message from a core network, the registration acceptance message including a first S-NSSAI (Single Network Slice Selection Assistance Information) permitted for use in the first PLMN and a second PLMN ID indicating a second PLMN associated with the first S-NSSAI, the storage unit associates the second PLMN ID with the first S-NSSAI and stores it, and the control unit stores the second PLMN ID associated with the first S-NSSAI, and the control unit stores the second PLMN ID associated with the first S-NSSAI. the control unit transitions to a registration state based on reception of the registration acceptance message; and when the transceiver unit receives, after receiving the registration acceptance message, a configuration update command in the first PLMN, the configuration update command including a first S-NSSAI authorized for use in the first PLMN and a third PLMN ID indicating a third PLMN associated with the first S-NSSAI, the memory unit associates and stores the third PLMN ID with the first S-NSSAI, and the control unit selects the third PLMN based on the third PLMN ID associated with the first S-NSSAI. Effect of the Invention

[0011] According to one aspect of the present invention, support for eNS becomes possible in 5GS, and it becomes possible for a UE to select a visited mobile network (VPLMN) at its destination, taking into account support for slices used in the home mobile network (HPLMN). [Brief description of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). [Diagram 2] A diagram explaining the detailed configuration of a mobile communication system (EPS / 5GS). [Diagram 3] A diagram explaining the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Diagram 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 1 is a diagram illustrating a registration procedure. [Figure 7] A diagram explaining the procedure for changing / updating UE settings. [Figure 8] FIG. 1 is a diagram illustrating an embodiment of one aspect of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

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

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

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

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

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

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

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

[0023] 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 defined by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP Gateway function (TNGF).

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

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

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

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

[0028] 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 a core network.

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

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

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

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

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

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

[0035] In addition, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may include devices not shown in Fig. 2. For example, the core network_A and / or the core network_B and / or the PDN_A and / or the 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.

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

[0037] The AAA server is a device that is connected to the AUSF directly or indirectly via another network device and has authentication, authorization, and accounting functions. The AAA server may be a network device in the core network. The AAA server may not be included in the core network_A and / or the 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 in the PLMN managed by a third party.

[0038] 2, for the sake of simplicity, one of each device and function is shown, but a plurality of similar devices and functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with a plurality of 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0084] 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 by the UE or may be initiated by the NW.

[0085] Also, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in a procedure 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, and the like. 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.

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

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

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

[0089] 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 may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and the DN using a PDU session by establishing a PDU session via an access network _B and a core network _B. Here, the external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data between a device such as an application server located in a DN and the DN using a PDU session.

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

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

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

[0093] Moreover, 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) communication carrier, and the operator can be identified by a PLMN ID. In this document, PLMN may mean 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 mean a core network.

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

[0095] A PLMN to which the 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.

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

[0097] The requested PLMN means a destination network of a message when the UE sends a message. Specifically, it may be a PLMN selected by the UE when the UE sends a message. The requested PLMN is a PLMN requested by the UE, and may be a current PLMN. Also, when the UE is in a registered state, the requested PLMN may be a registered PLMN.

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

[0099] In addition, the SOR transparent container 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."

[0100] In addition, a 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, and the AMF may refer to the information including the list of preferred PLMN / access technology combinations provided to the UDM, generate a SOR transparent container information element based on this information, and send it to the UE.

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

[0102] In addition, for example, when a UE switches networks due to mobility or selects a PLMN in automatic mode when the UE powers up at a roaming destination, the combination of PLMN and access technology that has the highest priority and is available and permissible may be selected.

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

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

[0105] Here, an NST is associated with resource requirements for providing a required communication service or capability, and is a logical representation of one or more NFs. In other words, an NSI may be a collection within a core network_B190 configured with multiple NFs. 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. An NF configured in an NS may or may not be a device shared with other NSs.

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

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

[0108] 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 a registered PLMN, and / or an SST and / or SD indicating an S-NSSAI of an HPLMN to which the S-NSSAI is mapped. One or more S-NSSAIs stored by the UE and / or the 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 an S-NSSAI of an HPLMN to which the S-NSSAI is mapped.

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

[0110] A mapped S-NSSAI is an S-NSSAI of a 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. In addition, the UE may store one or more mapped S-NSSAIs of the first NSSAI, and / or the rejected NSSAI, and / or the S-NSSAI included in the pending NSSAI.

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

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

[0113] The core network and / or core network device may store an S-NSSAI that requires 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 that requires an NSSAA with information indicating whether the 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 that requires an NSSAA as information unrelated to the access network.

[0114] A configured NSSAI is an NSSAI provided and stored in a 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 a PLMN, a configured NSSAI for a PLMN, or a configured NSSAI associated with a PLMN. A UE may store a configured NSSAI that is valid for all PLMNs without being associated with a PLMN, and such a configured NSSAI may be referred to as a "default configured NSSAI."

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

[0116] 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 an S-NSSAI and a mapped S-NSSAI. Alternatively, the S-NSSAI of the PLMN may be expressed as the "configured S-NSSAI", and the S-NSSAI with the configured S-NSSAI mapped to the HPLMN may be expressed as the "mapped S-NSSAI for the configured NSSAI for the PLMN".

[0117] In addition, the requested NSSAI is an NSSAI provided from 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 the 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.

[0118] 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 registration request message, a NAS message such as a PDU session establishment request message transmitted from the UE to the network, or a Radio Resource Control (RRC) message including a Non-Access-Stratum (NAS) message.

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

[0120] The UE and / or the 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 the NW may further manage the allowed NSSAI in association with a registration area.

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

[0122] 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 the 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. The allowed S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0123] Also, 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 the S-NSSAI and a rejection reason value.

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

[0125] 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, a registration reject message, etc., or an RRC message including an NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI.

[0126] 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. The 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.

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

[0128] In this document, the rejected NSSAI associated with the PLMN may be expressed as a rejected NSSAI for the PLMN or a rejected NSSAI of the PLMN. The UE and / or NW may further store the second rejected NSSAI and / or the second rejected S-NSSAI in association with the registration area. The UE and / or NW may store the second rejected NSSAI and / or the second rejected S-NSSAI in association with the access type and / or the registration area.

[0129] Here, the first rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current PLMN among the S-NSSAIs included in the requested NSSAI by the UE. The first rejected NSSAI may be a rejected NSSAI for the current PLMN of 5GS, a rejected S-NSSAI for the current PLMN, or an S-NSSAI included in the rejected NSSAI for the current PLMN. The first rejected NSSAI may be a rejected NSSAI stored by the UE or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the first rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. The rejection reason value at this time may be "S-NSSAI not available in the current PLMN" or may be information indicating that the S-NSSAI associated with the rejection reason value is not available in the current PLMN or SNPN. The S-NSSAI included in the first rejected NSSAI may be expressed as the first rejected S-NSSAI.

[0130] The first rejected NSSAI may be applied to the entire registered PLMN. The UE and / or NW may treat the first rejected NSSAI and the S-NSSAI included in the first rejected NSSAI as information that does not depend on the access type. In other words, the first rejected NSSAI may be information that is valid for 3GPP access and non-3GPP access.

[0131] The UE may delete the first rejected NSSAI from memory when the UE transitions to an unregistered state in both 3GPP access and non-3GPP access for the current PLMN. In other words, when the UE transitions to an unregistered state for the current PLMN via an access, or when the UE successfully registers to a new PLMN via an access, or when the UE fails to register to the new PLMN via an access and transitions to an unregistered state, and when the UE is not registered via the other access (unregistered state), the UE deletes the first rejected NSSAI. In other words, when the UE transitions to an unregistered state for the current PLMN via an access, and when the UE is registered to the current PLMN via the other access (registered state), the UE does not need to delete the first rejected NSSAI.

[0132] The second rejected NSSAI is a set of one or more S-NSSAIs that are unavailable in the current registration area among the S-NSSAIs included in the requested NSSAI by the UE. The second rejected NSSAI may be a rejected NSSAI of 5GS for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored by the UE or the NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information including one or more combinations of an S-NSSAI and a reason value. In this case, the rejection reason value may be "S-NSSAI not available in the current registration area" or may be information indicating that the S-NSSAI associated with the reason value is unavailable in the current registration area. An S-NSSAI included in the second rejected NSSAI may be expressed as the second rejected S-NSSAI.

[0133] The second rejected NSSAI may be valid in the current registration area and may be applied to the current registration area. The UE and / or NW may treat the second rejected NSSAI and the S-NSSAI included in the second rejected NSSAI as information for each access type. That is, the second rejected NSSAI may be information valid for each of 3GPP access and non-3GPP access. That is, once the UE transitions to an unregistered state for an access, the UE may delete the second rejected NSSAI associated with the access from its memory.

[0134] The third rejected NSSAI is a set of one or more S-NSSAIs that require an NSSAA and for which the NSSAA for the S-NSSAI has failed or been revoked. The third rejected NSSAI may be an NSSAI stored by the UE and / or the NW, or may be an NSSAI transmitted and received between the NW and the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. The rejection reason value at this time may be "S-NSSAI not available due to the failed or revoked NSSAA" or may be information indicating that the NSSAA for the S-NSSAI associated with the rejection reason value has failed or been revoked. The S-NSSAI included in the third rejected NSSAI may be expressed as the third rejected S-NSSAI.

[0135] The third rejected NSSAI may apply to the entire registered PLMN, may apply to the registered PLMN and / or the EPLMN, or may apply to all PLMNs. The third rejected NSSAI may apply to all PLMNs, which may mean that the third rejected NSSAI is not associated with a PLMN, or may mean that the third rejected NSSAI is associated with a HPLMN.

[0136] Furthermore, the UE and / or NW may treat the third rejected NSSAI and the third rejected S-NSSAI as information independent of the access type. That is, the third rejected NSSAI may be information valid for 3GPP access and non-3GPP access. The third rejected NSSAI may be an NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI. The third rejected NSSAI may be the rejected NSSAI for the failed or revoked NSSAA of 5GS, the rejected S-NSSAI for the failed or revoked NSSAA, or the S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA.

[0137] The third rejected NSSAI is a rejected NSSAI that identifies a slice that the UE has rejected due to the failure or cancellation of the NSSAA from the core network. Specifically, while the UE stores the third rejected NSSAI, the UE does not initiate a registration request procedure for the S-NSSAI included in the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAIs received from the core network in association with a rejection reason value indicating the failure of the NSSAA. The third rejected NSSAI is information that is independent of the access type. Specifically, when the UE stores the third rejected NSSAI, the UE may not attempt to transmit a registration request message including the S-NSSAI included in the third rejected NSSAI to both 3GPP access and non-3GPP access. Alternatively, the UE may transmit a registration request message including the S-NSSAI included in the third rejected NSSAI based on a UE policy. Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which the UE can transmit a registration request message including an S-NSSAI included in the third rejected NSSAI. In other words, when the UE transmits a registration request message including an S-NSSAI included in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI.

[0138] The first NSSAI is information including one or more S-NSSAIs that have reached the maximum number of UEs per network slice. The first NSSAI may be a rejected NSSAI, an allowed NSSAI, or a pending NSSAI. The first NSSAI may be an NSSAI stored by the UE and / or the NW, or an NSSAI transmitted from the NW to the UE.

[0139] When the first NSSAI is transmitted from the NW to the UE, the first NSSAI may be information including one or more pieces of information including at least one of the S-NSSAI, the mapped S-NSSAI, the rejection reason value, the value of the back-off timer, and information indicating the validity range of the back-off timer value. The rejection reason value at this time may be "the S-NSSAI has reached the maximum number of UEs per network slice" or may be information indicating that the maximum number of UEs permitted for the S-NSSAI associated with the rejection reason value has been reached. Here, the rejection reason value may be a rejection reason value included in the rejected NSSAI, may be flag information, or may be 5GMM cause. Furthermore, at this time, the back-off timer value may be information indicating a period during which the UE is prohibited from transmitting an MM message and an SM message using the S-NSSAI related to the corresponding S-NSSAI or the mapped S-NSSAI.

[0140] Furthermore, the information indicating the validity range of the backoff timer value may be information indicating whether the backoff timer value applies to the current PLMN (Public Land Mobile Network), applies to all PLMNs, or is valid in the current registration area.

[0141] The first NSSAI may apply to the entire registered PLMN, may be valid for all PLMNs, may apply, may be valid within a registration area, may apply to the registered PLMN and the EPLMN, or may apply to one or more PLMNs to which the TAIs included in the TA list (TAI list or registration area) belong. The first NSSAI applies to all PLMNs may mean that the first NSSAI is not associated with a PLMN, or may mean that the first NSSAI is associated with a HPLMN.

[0142] If the first NSSAI is valid in the entire registered PLMN, or applies to all PLMNs, or applies to the registered PLMN and / or EPLMN, the UE and / or NW may treat the first NSSAI and the S-NSSAI included in the first NSSAI as information independent of the access type. If the first NSSAI is valid in the registration area, or applies to one or more PLMNs to which the TAIs included in the TA list (TAI list or registration area) belong, the UE and / or NW may treat the first NSSAI and the S-NSSAI included in the first NSSAI as information specific to the access type.

[0143] The first NSSAI may be an allowed NSSAI, a rejected NSSAI, a pending NSSAI, or information different from these.

[0144] A pending NSSAI is a collection of one or more S-NSSAIs that are pending and / or unavailable for use by the UE. A pending NSSAI may be a collection 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 5GS pending NSSAI. A pending NSSAI may be an NSSAI stored by the UE and / or NW, or an NSSAI sent and received between the NW and the UE.

[0145] 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 the 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.

[0146] If the pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI may be a set of a combination of the S-NSSAI and the mapped S-NSSAI.

[0147] 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. The pending NSSAI may apply to all PLMNs, which may mean that the pending NSSAI is not associated with a PLMN, or may mean that the pending NSSAI is associated with a HPLMN.

[0148] The UE and / or NW may treat the S-NSSAI included in the pending NSSAI as information independent of the access type. In other words, 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.

[0149] 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, the UE does not initiate a registration request procedure for the S-NSSAI included in the pending NSSAI while storing 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, the UE does not attempt to transmit a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0150] 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 a range in which control messages such as paging are broadcast, or a range 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 to these. Hereinafter, a tracking area may be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) composed of a TAC (Tracking area code) and a PLMN.

[0151] A registration area is a collection of one or more TAs that the AMF assigns to a UE. 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 a signal for tracking area update. In other words, a registration area may be a group of information indicating an area 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.

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

[0153] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), or a SUPI (Subscription Permanent Identifier), or a GUTI (Globally Unique Temporary Identifier), or an IMEI (International Mobile Subscriber Identity), or 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.

[0154] The management of the maximum number of UEs connected to a slice refers to managing the maximum number of UEs that can be registered in a network slice or an S-NSSAI at the same time. Here, the UE to be registered in the network slice or the S-NSSAI may be stored by including the S-NSSAI indicating the network slice in the allowed NSSAI. A device in a network that supports the function of managing the maximum number of UEs connected to a slice can store, for each S-NSSAI, whether or not the management of the maximum number of UEs connected to the slice is required, and can further check during the registration procedure whether or not the registered UEs have reached a constant number that is the maximum number. Furthermore, each device that supports the function of managing the maximum number of UEs connected to a slice may be capable of storing a first NSSAI. In this document, the maximum number of UEs connected to a slice may be expressed as the maximum number of UEs connected to each slice, or the maximum number of UEs that can be registered in the network slice or the S-NSSAI, or the maximum number of UEs, or a constant number.

[0155] The back-off timer is a timer for prohibiting the UE from transmitting an MM message and / or starting a procedure by an SM message. The back-off timer is managed and executed by the UE. The back-off timer may be associated with an S-NSSAI. The UE may be in a state in which the transmission of an MM message and / or the transmission of an SM message using the S-NSSAI is prohibited, restricted, or limited while the back-off timer associated with the S-NSSAI is valid. These restrictions may be restrictions due to 5GS congestion management or restrictions including restrictions due to 5GS congestion management.

[0156] The backoff timer may be a timer that is started and / or stopped on a per S-NSSAI and / or per PLMN basis.

[0157] Specifically, the back-off timer may be associated with an S-NSSAI and may be a timer for prohibiting transmission of MM messages and / or SM messages using a specific S-NSSAI. In other words, the UE may be configured not to transmit MM messages and / or SM messages using the specific S-NSSAI while the timer is counting.

[0158] Furthermore, the UE may configure the new PLMN to permit transmission of MM messages and / or SM messages that were prohibited in the previous PLMN during the count of this timer, based on a specific condition described below. Note that when it is expressed that transmission of MM messages and / or SM messages that were prohibited in the previous PLMN is permitted, it may mean that transmission of MM messages and / or SM messages using the same S-NSSAI as the S-NSSAI associated with the back-off timer, and / or an S-NSSAI associated with the same S-NSSAI, and / or an S-NSSAI associated with a mapped S-NSSAI of the same S-NSSAI is permitted.

[0159] Furthermore, the back-off timer may be a timer for prohibiting transmission of an MM message using a specific NSSAI, in other words, the UE may be configured not to transmit an MM message using the specific NSSAI and / or an NSSAI including a specific S-NSSAI during the countdown of the timer.

[0160] Furthermore, the UE may configure the new PLMN to permit transmission of an MM message that was prohibited in the previous PLMN during the count of this timer, based on a specific condition described later. Note that when it is expressed that transmission of an MM message that was prohibited in the previous PLMN is permitted, it may mean that transmission of an MM message using an NSSAI that is the same as the NSSAI associated with the back-off timer and / or an NSSAI that includes the same S-NSSAI as the S-NSSAI associated with the back-off timer is permitted. Furthermore, when it is expressed that transmission of an MM message that was prohibited in the previous PLMN is permitted, it may mean that transmission of an MM message using an NSSAI that includes an S-NSSAI associated with the S-NSSAI associated with the back-off timer and / or an NSSAI that includes an S-NSSAI associated with the mapped S-NSSAI of the S-NSSAI associated with the back-off timer is permitted.

[0161] Also, the back-off timer may be associated with no NSSAI and may be a timer for prohibiting transmission of an MM message using no NSSAI. In other words, UE_A10 may configure this timer not to transmit an MM message using no NSSAI while it is counting. Furthermore, UE_A10 may configure this timer to be counted while it is counting, based on specific conditions described below, so that transmission of an MM message that was prohibited in the PLMN before the change is permitted in the new PLMN. Note that when it is expressed that transmission of an MM message that was prohibited in the PLMN before the change is permitted, this may mean that an MM message using no NSSAI is permitted.

[0162] Furthermore, the back-off timer may be a 5GMM timer and / or an EMM (EPS mobility management) timer. Furthermore, the back-off timer may be timer T3448 or a timer equivalent to timer T3448. In other words, the back-off timer may be the same timer as or similar to a timer for regulating communication of user data via the control plane.

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

[0164] The first identification information in this embodiment may be capability information of UE_A10 indicating that UE_A10 supports a function of receiving, recognizing, processing, and storing from the network information that associates and combines requested and / or permitted NSSAIs (S-NSSAI(s)) and visited PLMNs (vPLMNs) or EHPLMNs that support the requested and / or permitted NSSAIs (S-NSSAI(s)). Furthermore, the first identification information may be UE capability information indicating whether UE_A10 supports the above function.

[0165] Alternatively, the first identification information may be UE_A10 capability information indicating that UE_A10 supports a function of receiving, recognizing and processing information from the core network including (only) one or more PLMNs that support only the requested and / or allowed NSSAI (S-NSSAI(s)). Further, the first identification information may be UE capability information indicating whether UE_A10 supports the above function.

[0166] Further, the first identification information may be identification information for UE_A10 to request from the core network information of a vPLMN or EHPLMN that supports information associating and combining an NSSAI requested and / or permitted by UE_A10 with a vPLMN that supports the NSSAI requested and / or permitted by UE_A10, or core network capability information indicating that UE_A10 supports a function for generating, processing and transmitting information of a vPLMN that supports the NSSAI requested and / or permitted by UE_A10.

[0167] Furthermore, the combination of NSSAI (S-NSSAI(s)) and PLMN ID that the aforementioned UE_A10 receives, recognizes, and processes from the network may be information in which one S-NSSAI is associated with one PLMN ID and combined, information in which multiple S-NSSAIs are associated with one PLMN ID and combined, or information in which one S-NSSAI is associated with multiple PLMN IDs and combined.

[0168] The first identification information may be information indicating that UE_A10 has a function of storing an extended SOR (Steering of Roaming) transparent container information element (SOR transparent container IE), or may be information indicating that UE_A10 has a function of storing an extended allowed NSSAI.

[0169] The second identification information in this embodiment may be core network capability information indicating that the core network supports a function of selecting a visited PLMN (vPLMN) of UE_A10 that supports a requested and / or permitted NSSAI (S-NSSAI(s)) by UE_A10 and further transmitting the selected PLMN information (PLMN ID) to UE_A10. Furthermore, the second identification information may be core network capability information indicating whether the core network supports the function.

[0170] Here, the PLMN information that the core network sends to UE_A10 may be information associated with and combined with the NSSAI requested by UE_A10 to the core network and / or authorized by the core network, or it may be only the aforementioned selected PLMN information (PLMN ID).

[0171] Furthermore, when the core network transmits PLMN information associated with NSSAI (slice information) as combined information, the information may be one S-NSSAI associated with one PLMN ID and combined, or multiple S-NSSAIs associated with one PLMN ID and combined, or one S-NSSAI associated with multiple PLMN IDs and combined.

[0172] The third identification information in this embodiment may be information that associates and combines information (PLMN ID) that identifies one or more PLMNs (vPLMN(s)) that UE_A10 can use as a destination network and an NSSAI (S-NSSAI(s)) supported by each PLMN, and may further be information that includes multiple such combined information.

[0173] In addition, the combination of PLMN ID and NSSAI may be information in which one S-NSSAI is associated with and combined with one PLMN ID, information in which multiple S-NSSAIs are associated with and combined with one PLMN ID, or information in which one S-NSSAI is associated with and combined with multiple PLMN IDs.

[0174] Here, the PLMN information (PLMN ID) included in the third identification information may be one or more PLMN IDs selected by the core network based on the requested and / or permitted S-NSSAI in the UE_A10's home network (home PLMN; hPLMN).

[0175] Furthermore, the third identification information may include information consisting of one or more combinations of information indicating an access technology (access technology; PLMN Access Technology Identifier) ​​further associated with the association between the PLMN ID and the S-NSSAI.

[0176] For example, the third identification information may be an information element that extends a Steering of Roaming (SOR) transparent container information element, or may be information that extends an allowed NSSAI. Here, for example, the extended SOR transparent container information element may be a combination of a PLMN ID and an access technology in a list of preferred PLMN / access technology combinations included in the SOR transparent container information element, to which an NSSAI (S-NSSAI(s)) supported by each PLMN is further added. Also, for example, the extended allowed NSSAI may be configured to include other information, in addition to a combination of a plurality of S-NSSAIs and mapped S-NSSAIs included in the allowed NSSAI, by further adding one or a plurality of PLMN IDs to which each S-NSSAI is supported.

[0177] Here, if UE_A10 does not indicate capability information for recognizing the third identification information based on the second identification information, the core network may not send the third identification information to the UE_A10, and may instead send an unextended SOR transparent container IE or an unextended allowed S-NSSAI.

[0178] The third identity may include an S-NSSAI that the core network allows the UE to use (e.g., an allowed S-NSSAI) and a list of one or more PLMNs associated with the S-NSSAI, where the core network may be a PLMN.

[0179] The fourth identification information in this embodiment may be identification information composed of information (PLMN ID) that identifies one or more networks (vPLMNs) that UE_A10 can use as destination networks.

[0180] Here, the PLMN information (PLMN ID) included in the fourth identification information may be one or more PLMN IDs selected by the core network based on the requested and / or permitted S-NSSAI in the UE_A10's home network (home PLMN; hPLMN).

[0181] Furthermore, the fourth identification information may be one or more combinations of a PLMN ID and information indicating an access technology (access technology; PLMN Access Technology Identifier) ​​associated with each other.

[0182] For example, the fourth identification information may be a SOR transparent container IE, which may include one or more PLMN(s) for which UE_A10 supports an NSSAI (S-NSSAI(s)) requested and / or allowed by the network and selected by the core network.

[0183] Furthermore, the fourth identification information may be an information element that extends a SOR transparent container information element (SOR transparent container IE), or may be information that extends an allowed NSSAI. Here, for example, the extended SOR transparent container information element may be a combination of a PLMN ID and an access technology in a list of preferred PLMN / access technology combinations included in the SOR transparent container information element, to which an NSSAI (S-NSSAI(s)) supported by each PLMN is further added. Also, for example, the extended allowed NSSAI may be configured to include other information, in addition to a combination of a plurality of S-NSSAIs and mapped S-NSSAIs included in the allowed NSSAI, by further adding one or a plurality of PLMN IDs to which each S-NSSAI is supported.

[0184] Here, if UE_A10 does not indicate capability information for recognizing the third identification information based on the second identification information, the core network may not send the third identification information to the UE_A10 and may send a conventional SOR transparent container IE that does not take into account the PLMN's S-NSSAI support.

[0185] [3. First embodiment] [3.1. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a generic UE configuration update procedure, and a PLMN selection. Each procedure will be described below.

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

[0187] [3.2. 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 for the UE to take the initiative in registering to the access network_B, and / or the core network_B, and / or the DN. If the UE is not registered to the network, it can execute this procedure at any timing, such as when the power is turned on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), it can start this procedure at any timing. Furthermore, each device (particularly the UE and the AMF) can transition to a registered state (5GMM-REGISTEDED 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 non-registered state) for 3GPP access and the registration state for non-3GPP access.

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

[0189] The UE may start the registration procedure when the UE performs mobility across TAs (tracking areas). In other words, the UE may start the registration procedure when the UE moves to a TA different from the TA indicated in the TA list (TAI list or registration area) held by the UE. Furthermore, the UE may start this procedure when a back-off timer or other timer that is being executed expires. Furthermore, the UE may start the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may start the registration procedure when a change occurs in the capability information and / or preferences regarding the establishment of a PDU session of the UE. Furthermore, the UE may start the registration procedure periodically. Furthermore, the UE may start the registration procedure based on the completion of a UE configuration update procedure, based on the completion of a registration procedure, based on the completion of a PDU session establishment procedure, based on the completion of a PDU session management procedure, based on information received from the network in each procedure, or based on the expiration or stop of a back-off timer. It should be noted that the UE can execute the registration procedure at any timing, not limited to these.

[0190] In addition, the above-mentioned 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.

[0191] 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 requested by the UE.

[0192] 6 indicates the AMF to which UE_A10 is registered by this procedure, and old AMF142 means the AMF to which the UE was registered by a procedure prior to this procedure. If no change in AMF 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 AMF is written, it may mean new AMF141, old AMF142, or both. Note that new AMF141 and old AMF142 may be AMF140.

[0193] First, the UE_A10 starts the registration procedure by transmitting a registration request message to the new AMF 141 (S600) (S602) (S604). Specifically, the UE transmits an RRC message including the registration request message to the 5G AN 120 (or gNB) (S600). The registration request message is a NAS message transmitted and received on the N1 interface. The RRC message may be a control message transmitted and received between the UE and the 5G AN 120 (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0194] Here, UE_A10 can transmit the first identification information by including it in a registration request message and / or an RRC message. 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 periodic updating of registration information, or for emergency registration.

[0195] In order to notify the network of the functions supported by UE_A10, UE_A10 may include the capability information of the UE in the registration request message, or may include the first identification information as the capability information of the UE. Here, the capability information of the UE may be the 5G MM capability of 5GS.

[0196] UE_A10 may transmit this identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, the MAC layer, the RLC layer, the PDCP layer). By transmitting these identification information, UE_A10 may indicate that UE_A10 supports each function, may indicate a UE request, or may indicate both. Furthermore, 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.

[0197] Furthermore, UE_A10 may select or decide whether to transmit the first identification information to the network based on UE capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, etc.

[0198] When UE_A10 has a function for identifying and processing combination information of PLMN ID and NSSAI (S-NSSAI) supported by PLMN included in the third identification information and / or fourth identification information used for PLMN selection after movement, UE_A10 may transmit the first identification information in a registration request message. By transmitting the first identification information, UE_A10 may indicate to the network that it has a function for processing combination information of PLMN ID and NSSAI (S-NSSAI) supported by PLMN included in the third identification information and / or fourth identification information.

[0199] Further, UE_A10 may indicate by sending the first identification information in a registration request message that it requests network capability information indicating that the network supports the function corresponding to the first identification information.

[0200] It is also assumed that UE_A10 has the capability to support the function indicated by the first identification information, and further that UE_A10 uses one or more S-NSSAIs included in the NSSAI (requested NSSAI) that it requests to use in the PLMN (HPLMN) in which it is registering through this procedure, in the VPLMN or EHPMN to which it will register and connect after UE mobility occurs, and when requested, the first identification information may be included in a registration request message or transmitted to the network.

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

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

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

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

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

[0206] Alternatively, a case in which 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 be a case in which the UE stores an allowed NSSAI associated with a PLMN other than the PLMN requested by the UE or an S-NSSAI included in the allowed NSSAI, and a PLMN list that supports the S-NSSAI, and the PLMN list includes the PLMN requested by the UE.

[0207] UE_A10 may also include an S-NSSAI contained in an allowed NSSAI associated with a PLMN other than the PLMN requested by the UE in the requested NSSAI.

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

[0209] Alternatively, in a registration request procedure with 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.

[0210] In addition, UE_A10 may initiate a PDU session establishment procedure during the registration procedure by sending a registration request message including an SM message (e.g., a PDU session establishment request message), or by sending an SM message (e.g., a PDU session establishment request message) together with the registration request message.

[0211] When the 5G AN 120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S602). The 5G AN 120 (or gNB) can select an AMF based on one or more 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 transmitted based on the first identification information.

[0212] For example, the 5G AN 120 (or gNB) may select an AMF that supports a function corresponding to the capability information indicated by the first identification information based on the first identification information. Specifically, the 5G AN (or gNB) may select an AMF that corresponds to the capability information of the UE indicated by the first identification information and has a function for generating and transmitting a PLMN ID and / or a combination of the access technology of the PLMN and an NSSAI (S-NSSAI) supported by the PLMN, which are included in the third identification information and / or the fourth identification information.

[0213] The method of 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). If the first identification information is not included in the registration request message but is 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).

[0214] When the new AMF 141 receives the registration request message, it can execute a first condition determination. The first condition determination is for determining whether or not 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.

[0215] Alternatively, the new AMF 141 may perform the first condition determination after requesting the UE context from the old AMF 142 and 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.

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

[0217] Furthermore, the first condition determination may be performed based on 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.

[0218] For example, if the network permits the UE's request, the first condition determination may be true, and if the network does not permit the UE's request, the first condition determination may be false. Also, if the network to which the UE is registered and / or a device in 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.

[0219] In addition, when 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 when the AMF stores the result of the NSSAA procedure of the corresponding S-NSSAI for the UE as successful, the first condition determination may be true. Alternatively, when there is no S-NSSAI to allow the UE and there is no plan to assign an allowed NSSAI to the UE in the future, the first condition determination may be false.

[0220] In addition, when the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information for identifying a slice that requires management of the maximum number of UEs connected to the slice, and further when the maximum number of UEs has not been reached, the first condition determination may be true. Or, even if there is no S-NSSAI permitted 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.

[0221] When the AMF assigns a first NSSAI to the UE when there is no S-NSSAI permitted for the UE, the first condition determination may be true or false.

[0222] If the AMF indicated in the AMF identification information included in the message received by the new AMF 141 from the UE is the old AMF 142, the 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 the new AMF 141 from the UE_A 10 is the new AMF 141, the 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.

[0223] The UE context transfer procedure (S606, S608) will be described. The new AMF 141 transmits a UE context request message to the old AMF 142 (S606). The old AMF 142 transmits 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.

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

[0225] The UE context may also include information of an 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.

[0226] The UE context may also include information on an S-NSSAI that requires management of the maximum number of UEs connecting 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 connecting to a slice has been reached.

[0227] 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 an NSSAA is required, whether the 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.

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

[0229] New AMF 141 may transmit a control message including at least one or more of the second to fourth identification information. By transmitting these identification information and / or the control message, new AMF 141 may indicate that the network supports each function, may indicate that the UE's request has been accepted, may indicate that the request from the UE is permitted or not supported, or may indicate a combination of these. Furthermore, when multiple identification information are transmitted and received, two or more of these identification information may be configured as one or more identification information. 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.

[0230] Here, the second identification information may be capability information indicating that the new AMF 141 and / or the core network supports a function corresponding to the capability information indicated by the first identification information received from the UE.

[0231] The new AMF 141 may also indicate that the new AMF 141 and / or the core network have the capability indicated by the second identity by including the third and / or fourth identity in the registration accept message. In other words, when the new AMF 141 includes the third and / or fourth identity in the registration accept message, the new AMF 141 may not include the second identity.

[0232] Furthermore, if the new AMF 141 does not receive the first identification information from the UE, the new AMF 141 may not transmit the third and / or fourth identification information. In other words, if the new AMF 141 does not receive the first identification information from the UE, the third and / or fourth identification information may be prohibited.

[0233] When new AMF 141 receives the first identification information from the UE, it may transmit at least one of the second to fourth identification information by including it in a control message.

[0234] Furthermore, the new AMF 141 may transmit at least one of the third identification information and / or the fourth identification information when the UE's configuration information is updated.

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

[0236] When sending the control message, new AMF141 may send an empty value in the allowed NSSAI if there is no S-NSSAI (allowed NSSAI) permitted for the UE, but if there is a plan to execute an NSSAA procedure after completion of this procedure or in parallel with this procedure, or if an NSSAA procedure is being executed between the UE and the network, or if a pending NSSAI was sent in the control message.

[0237] When transmitting a control message, new AMF141 does not permit the UE to have an S-NSSAI (allowed NSSAI), but if the 10th identification information is included in the control message, or if the UE has been notified of the first NSSAI prior to this procedure, new AMF141 may transmit an empty value in the allowed NSSAI.

[0238] When the new AMF 141 includes the 13th identification information, which indicates that the new AMF 141 applies to all PLMNs, in a control message, the new AMF 141 may also include the 15th identification information in the control message.

[0239] UE_A10 receives from the network the control message and / or one or more pieces of identification information from the 10th to the 15th. More specifically, the UE receives from the new AMF141 the control message and / or one or more pieces of identification information from the 10th to the 15th.

[0240] UE_A10 may recognize the received information based on the reception of at least one of the tenth to fifteenth identification information. Specifically, UE_A10 may recognize that the maximum number of UEs connected per slice has been reached, and therefore transmission of MM messages and / or transmission of SM messages using the S-NSSAI indicated by the tenth identification information, and / or the S-NSSAI indicated by the fourteenth identification information, and / or the S-NSSAI related to the mapped S-NSSAI indicated by the fifteenth identification information is temporarily prohibited. Note that the MM procedure here may be a registration request message, and the SM message may be a PDU session establishment request message.

[0241] UE_A10 may perform the following operations based on receiving at least one of the second to fourth identification information and / or receiving a control message.

[0242] By receiving one or more of the second to fourth identification information, UE_A10 may recognize that the network supports the function corresponding to the UE capability information indicated by the first identification information.

[0243] If UE_A10 receives a third identification information and / or a fourth identification information without receiving the second identification information, it may recognize, store and process the third identification information and / or the fourth identification information as an unextended SOR transparent container information element or an unextended allowed NSSAI.

[0244] When UE_A10 receives the third identification information and / or the fourth identification information, UE_A10 may store or update them. For example, when this procedure is an initial registration procedure, or when the UE does not store or hold the third identification information and / or the fourth identification information, UE_A10 may store them. Also, for example, when this procedure is a registration procedure for update, or when the UE has already received or stored or held information included in the third identification information and / or the fourth identification information by preconfiguration, UE_A10 may update them by overwriting or adding the third identification information and / or the fourth identification information newly received by this procedure.

[0245] Specifically, when the third identification information is an extended SOR transparent container information element, UE_A10 stores one or more pieces of information indicated in the third identification information based on receiving the third identification information. Furthermore, when UE_A10 has already stored an extended SOR transparent container information element or a non-extended SOR transparent container information element, it may delete the old SOR transparent container information element.

[0246] Alternatively, if the third identification information is an extended allowed NSSAI, UE_A10 stores one or more pieces of information indicated in the third identification information based on reception of the third identification information. Specifically, UE_A10 may update the allowed NSSAI based on reception of the third identification information. Furthermore, if UE_A10 has already stored an allowed NSSAI, it may delete the old allowed NSSAI.

[0247] More specifically, when the third identification information is an extended allowed NSSAI, UE_A10 may store the S-NSSAI included in the allowed NSSAI indicated in the third identification information in association with the current PLMN and access type based on the reception of the third identification information. Furthermore, UE_A10 may store the S-NSSAI included in the allowed NSSAI in association with the supported PLMN list.

[0248] When the fourth identification information is a SOR transparent container information element, UE_A10 may store the received SOR transparent container information element based on the reception of the fourth identification information. When the fourth identification information is an allowed NSSAI, UE_A10 may store the received allowed NSSAI based on the reception of the fourth identification information.

[0249] Here, for example, the third identification information and / or the fourth identification information may be new information generated by the AMF, UDM, SOR-AF, or other core network device that has received the first identification information from the UE, by associating with each PLMN supporting the S-NSSAI(s) included in the NSSAI (allowed NSSAI) that the UE allows based on the SOR transparent container information element, or may be information generated by extending or modifying the SOR transparent container information element. Specifically, this association may be configured as a list that extends the SOR transparent container information element or the PLMN ID and access technology list (list of preferred PLMN / access technology combinations) in which the PLMN ID and the access technology recorded in the PLMN ID and access technology list (list of preferred PLMN / access technology combinations) included in the SOR transparent container information element are associated with the allowed NSSAI or one or more S-NSSAIs included in the allowed NSSAI supported for each PLMN ID, and the PLMN ID, the access technology, and one or more NSSAIs allowed by the UE are associated as a set of information.

[0250] Also, for example, the third identification information and / or the fourth identification information may be new information generated by the AMF, UDM, or other core network device that has received the first identification information from the UE by associating, for each S-NSSAI included in the allowed NSSAI, with the PLMN IDs of one or more VPLMNs that support the S-NSSAI, or may be information generated by extending or modifying the allowed NSSAI. Specifically, the third identification information and / or the fourth identification information may be configured as a list of extended allowed NSSAIs that includes, in addition to the association between the S-NSSAI and the mapped S-NSSAI, a set of information including the PLMN IDs that support these S-NSSAIs.

[0251] Also, for example, when the third identity is included in the registration accept message, the AMF may not include the allowed NSSAI, and may include the third identity instead of the allowed NSSAI. In other words, the UE that receives the third identity may recognize the third identity as information including the allowed NSSAI, and may use the information included in the third identity as the allowed NSSAI in various subsequent processes.

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

[0253] Furthermore, when the control message is a registration acceptance message, the AMF may include an SM message (e.g., a PDU session establishment acceptance message) in the registration acceptance message and send it, or may 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.

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

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

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

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

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

[0259] 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 transmission / reception of a registration acceptance message and / or a registration completion message, and may transition to or maintain a state in which the UE is not registered in the network on the access on which the registration rejection message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on transmission / reception of a registration rejection message. Also, the transition to each state of each device may be based on transmission / reception of a registration completion message or completion of the registration procedure.

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

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

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

[0263] Further, based on completion of this procedure, UE_A10 may delete a second rejected NSSAI associated with the current PLMN, the current registration area, and / or its access type 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 registered state on an access as a result of performing the registration procedure in the new registration area.

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

[0265] Additionally, each device may re-initiate the registration procedure based on the updated NSSAI it stores.

[0266] 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 in the network (RM_REGISTERED state or 5GMM-REGISTERED state).

[0267] [3.3. Renewal Procedure] Next, the renewal procedure will be described. In this chapter, the renewal procedure will also be referred to as this procedure.

[0268] The update procedure may be a network-initiated or UE-initiated procedure for updating information (list of preferred PLMN / access technology combinations) stored by UE_A10 based on the third identification information and / or the fourth identification information received by UE_A10 in the registration procedure of Chapter 3.2. Specifically, the update procedure may be a registration procedure for periodic or arbitrary registration update, and / or a generic UE configuration update procedure, and / or a network-initiated NAS transport procedure, and / or a UE-initiated NAS transport procedure.

[0269] This registration procedure may be a procedure in which UE_A10 receives new third identity information and / or fourth identity information from the core network in the procedure described in Chapter 3.2, and updates information based on the third identity information and / or fourth identity information (list of preferred PLMN / access technology combinations) that UE_A10 has already received and stored.

[0270] In this procedure using a network-initiated or UE-initiated NAS transport procedure, the update of the third identification information and / or the fourth identification information may be a procedure in which the core network includes the third identification information and / or the fourth identification information in a DL NAS transport message and sends it to UE_A10, and UE_A10, upon receiving these, updates information based on the third identification information and / or the fourth identification information that it has already received and stored (list of preferred PLMN / access technology combinations).

[0271] Furthermore, the method of updating the third identification information and / or the fourth identification information by the UE based on receiving the third identification information and / or the fourth identification information may be the same as the registration procedure.

[0272] Here, the UE-initiated NAS transport procedure may be a procedure for the UE to provide various information to the core network. The provided information may include a transparent container information element. Furthermore, the transparent container information element may be an extended transparent container information element.

[0273] Furthermore, the UE-initiated NAS transport procedure may be a procedure that is started by the UE transmitting a UL NAS transport message to the AMF. Furthermore, the UE-initiated NAS transport procedure may be a procedure that is started by a trigger such as a change in the UE state or a change in the UE settings. Furthermore, the UE-initiated NAS transport procedure may be a procedure that is started by an instruction from a higher layer.

[0274] Furthermore, the network initiated NAS transport procedure may be a procedure for the core network to provide various information to the UE, and the provided information may include a transparent container information element, and the transparent container information element may be an extended transparent container information element.

[0275] Furthermore, the network-initiated NAS transport procedure may be a procedure that is started by the AMF transmitting a DL NAS transport message to the UE. Furthermore, the network-initiated NAS transport procedure may be a procedure that is started based on the reception of a UL NAS transport message. Conversely, the network-initiated NAS transport procedure may be a procedure that is started based on a trigger other than the reception of a UL NAS transport message. For example, the network-initiated NAS transport procedure may be a procedure that is started based on a change in network status, a change in network settings, or the like.

[0276] This procedure, which is performed via the UE configuration update procedure, is described in the next section 3.3.1.

[0277] [3.3.1. UE configuration update procedure] Next, the generic UE configuration update procedure will be described with reference to FIG. 7. Hereinafter, the generic UE configuration update procedure will also be referred to as this procedure. This procedure is a procedure for updating configuration information of a UE under the initiative of a core network. This procedure may be a procedure for mobility management that is executed under the initiative of a network for a UE registered in the network.

[0278] Furthermore, a device in a core network such as an AMF may start this procedure based on an update of a network configuration and / or an update of an operator policy. The trigger of this procedure may be detection of UE mobility, detection of a change in the state of the UE, and / or the access network, and / or the core network, or a change in the state of a network slice. The trigger of this procedure may be reception of a request from a DN and / or an application server of the DN, a change in the network configuration, or a change in an operator policy. The trigger of this procedure may be expiration of a running timer. The trigger for the device in the core network to start this procedure is not limited to these. In other words, this procedure may be executed at any timing after the above-mentioned registration procedure and / or PDU session establishment procedure are completed. Furthermore, this procedure may be executed at any timing as long as each device has established a 5GMM context and / or is in a 5GMM connected mode.

[0279] During this procedure, each device may transmit and receive a message including identification information for changing the configuration information of the UE and / or identification information for stopping or changing a function being executed by the UE. Furthermore, each device may update its configuration information to a configuration instructed by the network or start a behavior instructed by the network based on the completion of this procedure.

[0280] The UE may update the UE's configuration information based on the control information transmitted and received by this procedure. Furthermore, the UE may stop a function being executed or start a new function in accordance with the update of the UE's configuration information. In other words, the device in the core network may initiate this procedure and further transmit the control message and control information of this procedure to the UE, thereby causing the UE to update the UE's configuration information that can be identified using the control information. Furthermore, the device in the core network may stop a function being executed by the UE or cause the UE to start a new function by updating the UE's configuration information.

[0281] First, AMF140 initiates the UE configuration update procedure by sending a configuration update command message to UE_A10 via 5G AN120 (or gNB) (S700).

[0282] The AMF 140 may include the third identity and / or the fourth identity in the configuration update command message and send it. Here, the third identity and / or the fourth identity included in the configuration update command message may be new values ​​that update the third identity and / or the fourth identity that the UE has received from the AMF in the registration accept message in the registration procedure described in Chapter 3.2 and stored.

[0283] Furthermore, if AMF140 has not received a registration request message including the first identification information from the UE in the registration procedure described in Chapter 3.2, the AMF140 must not send the third identification information and / or the fourth identification information in this procedure.

[0284] AMF140 may also select and determine whether to include the third identification information and / or the fourth identification information in the configuration update command message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF140, etc.

[0285] AMF140 may also indicate a request for an update of UE_A10's configuration information by sending a configuration update command message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by AMF140, etc.

[0286] The UE may update the third identity and / or the fourth identity stored in the UE based on the third identity and / or the fourth identity. A method for updating the third identity and / or the fourth identity by the UE based on receiving the third identity and / or the fourth identity may be the same as the registration procedure.

[0287] Furthermore, the UE may transmit a configuration update complete message to the AMF 140 via the 5G AN (gNB) as a response message to the configuration update command message based on the identification information included in the configuration update command message (S702).

[0288] When UE_A10 transmits a setting update completion command message, AMF140 receives the setting update completion message via 5G AN (gNB) (S702). In addition, each device completes this procedure based on the transmission and reception of the setting update command message and / or the setting update completion message.

[0289] Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, when update information for the setting information is transmitted and received, each device may update the setting information. Furthermore, when information indicating that the registration procedure needs to be performed is transmitted and received, UE_A10 may start the registration procedure based on the completion of this procedure.

[0290] Furthermore, the UE_A10 may store the third identification information and / or the fourth identification information received together with the configuration information command message based on the completion of the procedure, or may recognize the network's decision. Also, the UE may perform each procedure based on the stored information based on the completion of the procedure.

[0291] In the above procedure, by sending and receiving a configuration update command message, a device in the core network can instruct the UE to update the configuration information that the UE has already stored or applied, or can instruct the UE to stop or change a function that the UE is executing.

[0292] 3.4. PLMN Selection Next, the process related to PLMN selection will be described.

[0293] PLMN selection may be a process performed by the UE when UE_A10 needs to switch from the PLMN to which it is currently registered and / or connected (here, the HPLMN) to another PLMN (VPLMN) due to movement (mobility), or when the UE is powered on in an area other than the HPLMN.

[0294] In addition, the PLMN selection may be performed based on the third identification information and / or the fourth identification information received and stored by UE_A10 during the registration procedure and / or the update procedure, and may be a UE process of selecting a combination of a PLMN (VPLMN) ID and / or access technology and / or NSSAI (S-NSSAI(s)) supported by the PLMN that supports a particular S-NSSAI that UE_A10 used in the HPLMN.

[0295] Here, for example, when the third identification information is an extended SOR transparent container information element, the PLMN selection may be performed in an automatic mode in which the selection is performed automatically, or in a manual mode in which the user of the UE_A10 manually selects the combination with the highest priority from among the combinations of PLMN ID and access technology and / or NSSAI (one or more S-NSSAI), and may use the combination in the registration procedure to be executed next. Here, the priority may be the order in which the combinations of PLMN and access technology and / or NSSAI (one or more S-NSSAI) are stored, and the priority of the PLMN ID included in the combination of PLMN ID and access technology and / or NSSAI (one or more S-NSSAI) stored first may be the highest.

[0296] Also, for example, when the third identification information is an extended allowed NSSAI, the PLMN selection may be a process of the UE selecting a PLMN based on the S-NSSAI that establishes a PDU session after the UE performs a registration procedure based on the PLMN selection.

[0297] In addition, the PLMN selection performed when powering on in an area other than the HPLMN may be performed based on the third identification information and / or the fourth identification information and / or information contained therein that the UE has already received and stored.

[0298] In addition, here, if the third identification information and / or the fourth identification information does not include a PLMN ID supporting one or more S-NSSAIs that the UE has connected to and used in the HPLMN, the UE may select a PLMN ID with the highest priority from the third identification information and / or the fourth identification information and perform a registration procedure based on the selected PLMN ID, or may not select a PLMN ID and perform a registration procedure based on an NSSAI (allowed NSSAI) permitted by a network other than the above-mentioned network, and the operation of the UE is not limited to these.

[0299] Furthermore, after performing the PLMN selection, the UE may perform a registration procedure with the destination PLMN selected and determined based on the PLMN selection, where the registration procedure may be a registration procedure performed by mobility or an initial registration procedure.

[0300] 4. EMBODIMENT OF THE PRESENT EMBODIMENT An embodiment of one aspect of the present invention may be a combination of one or more procedures described in Chapter 3. For example, in this embodiment, as shown in Figure 8, after completing the registration procedure (S800) described in Chapter 3, a network or UE initiated update procedure (S802) may or may not be performed.

[0301] Here, the update procedure may be initiated by the UE or the network at any time, may be performed based on a change in settings or policies in the UE or the network, or may be performed based on a change in UE subscription information stored by the network or a roaming agreement with another network (PLMN), or slicing support of another network.

[0302] Based on the completion of these procedures (S800 and / or S802), the UE and / or each device of the core network may transition to a first state (S804).

[0303] Here, the first state (S804) may be a state in which UE_A10 and each core network device are in a registered state (RM-REGISTERED state), and / or a state in which UE_A10 has received and stored third identification information and / or fourth identification information in the registration procedure (S800) and / or the update procedure (S804).Furthermore, the first state (S804) may be a state in which UE_A10 has received second identification information.

[0304] Furthermore, the third identification information may be an extended SOR transparent container information element and / or an extended allowed NSSAI, and may be based on the first identification information sent by UE_A10 to the core network during the initial registration procedure.

[0305] Next, UE_A10 in the first state may perform PLMN selection (S806) if it needs to switch to another PLMN due to mobility or if it powers on in an area other than the HPLMN. The PLMN selection may be performed based on the third identification information and / or the fourth identification information, and may be performed automatically by selecting a PLMN (VPLMN) ID that supports a specific S-NSSAI that UE_A10 used in the HPLMN, or may be performed manually by the user of UE_A10.

[0306] In addition, when two or more PLMN IDs are included in a plurality of pieces of third identification information and / or fourth identification information, a higher-ranking PLMN ID may be selected based on the priority order, etc. Here, the priority order may be the order in which the combinations of PLMN IDs and access technologies and / or one or more S-NSSAIs are stored, and the combination of PLMN IDs and access technologies and / or one or more S-NSSAIs stored first may have the highest priority order.

[0307] Next, the UE_A10 may select and determine the destination PLMN ID based on the PLMN selection, and may execute a registration procedure to the selected destination PLMN (S808), which may be a registration procedure performed by mobility or an initial registration procedure. Also, the registration procedure to the VPLM (PLMN #2 in FIG. 8) may be the same as the registration procedure described in Chapter 3, or may be a registration procedure that does not include the first identification information in the registration request message.

[0308] In addition, the embodiment described above is one in which UE_A10 receives and / or updates the third identification information and / or the fourth identification information through a registration procedure and / or an update procedure in the HPLMN. However, this is not limited to the above, and the third and / or the fourth identification information may be received and / or updated through a registration procedure and / or an update procedure in the VPLMN as well.

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

[0310] 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 implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

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

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

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

Claims

[Claim 1] A UE (User Equipment), The device includes a transmitter / receiver, a controller, and a memory unit, The transceiver unit receives, in a first PLMN (Public Land Mobile Network), a registration accept message from a core network, the registration accept message including a first S-NSSAI (Single Network Slice Selection Assistance Information) permitted for use in the first PLMN and a second PLMN ID indicating a second PLMN associated with the first S-NSSAI; The storage unit stores the second PLMN ID and the first S-NSSAI in association with each other; The control unit is capable of selecting the second PLMN based on the second PLMN ID that is associated with the first S-NSSAI and supports the first S-NSSAI; The control unit transitions to a registration state based on receipt of the registration acceptance message, When the transceiver receives a configuration update command in the first PLMN after receiving the registration accept message, the configuration update command includes a first S-NSSAI permitted for use in the first PLMN and a third PLMN ID indicating a third PLMN associated with the first S-NSSAI, The storage unit stores the third PLMN ID and the first S-NSSAI in association with each other; The control unit selects the third PLMN based on the third PLMN ID that is associated with the first S-NSSAI and supports the first S-NSSAI. The UE is characterized by:

Images