UE (User Equipment)

Abstract

The present invention provides a procedure and a communication unit for implementing management of maximum number of UEs connected per slice in 5GS, initial registration of UE, periodic or mobility based registration. Also, a communication unit for implementing functions related to management of maximum number of UEs connected per slice in 5GS is provided by providing a management method of timer executed after completion of registration procedure, a registration procedure method of UE in which timer is being executed and timer is not being executed, and a communication unit.

Description

Technical Field

[0001] This application relates to UE (User Equipment). This application claims priority to Japanese Patent Application No. 2019-236466, filed on December 26, 2019, the entire contents of which are incorporated herein by reference. Background Technology

[0002] In the 3GPP (3rd Generation Partnership Project), which has been conducting standardization activities for mobile communication systems in recent years, research has been carried out on SAE (System Architecture Evolution) as the system framework for LTE (Long Term Evolution).

[0003] Furthermore, in recent years, 3GPP has also conducted research on next-generation communication technologies and system frameworks for 5G (5th Generation) mobile communication systems, particularly on the standardization of 5GS (5G System) as a system for implementing 5G mobile communication systems (see Non-Patent Literature 1 and Non-Patent Literature 2). Technical problems related to connecting various terminals to cellular networks in 5GS were extracted and solutions were standardized.

[0004] Existing technical documents

[0005] Non-patent literature

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

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

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

[0009] Non-patent document 4: 3GPP TR 23.700-40V0.2.0 (2019-11); 3rd Generation Partnership Project; Technical Specification Group Services and SystemAspects; Study on Enhancement of Network Slicing Phase 2 (Release 17) Summary of the Invention

[0010] The problem the invention aims to solve

[0011] In 5GS (5G System), 5GCN (5G Core Network) was studied as a new core network in order to provide a variety of services.

[0012] Furthermore, in 5G, network slices, which provide specific network functions and characteristics, are defined as logical networks for specific service types and specific groups. For example, a network slice can be a logical network provided for terminals with low latency capabilities, or it can be a logical network provided for sensor terminals used in IoT (Internet of Things).

[0013] In 3GPP, research was conducted on eNS (Enhancement of Network Slicing) to investigate further functionalities related to network slicing. Furthermore, as Phase Two of the eNS research, 3GPP investigated the addition of functionality for managing the number of allowed UEs per slice. However, the implementation method to meet these requirements remains unclear.

[0014] The present invention was made in view of the above facts, and is an invention that provides a method for implementing the function of eNS in 5GS.

[0015] Technical solution

[0016] The UE (User Equipment) of the present invention is characterized in that it comprises: a transceiver unit for receiving control messages from a control device; and a control unit, wherein the control messages include one or more first pieces of information, the first pieces of information including a first S-NSSAI (Single Network Slice Selection Assistance information), second information, third information, fourth information, and a second S-NSSAI representing a mapped S-NSSAI to the first S-NSSAI, the second information being information indicating the reason for the S-NSSAI being rejected, the third information being information indicating the value of a backoff timer, and the fourth information being information indicating whether the backoff timer is applicable to all PLMNs, the control unit appending the first S-NSSAI to the first NSSAI (Network Slice Selection Assistance information) associated with the second and fourth information according to the received control messages. The information (network slice selection auxiliary information) deletes the first S-NSSAI included in the first NSSAI from the second NSSAI, and deletes the third S-NSSAI associated with the second S-NSSAI from the third NSSAI based on the fourth information. A backoff timer associated with the first S-NSSAI or the second S-NSSAI is started using the value represented by the third information, and the backoff timer is adapted to the range represented by the fourth information. The UE (User Equipment) of the present invention is characterized by comprising: a transceiver unit that sends a registration request message to a control device; a storage unit that stores the first NSSAI and the second S-NSSAI mapped to the first S-NSSAI included in the first NSSAI; and a control unit that includes the first S-NSSAI in the registration request message, wherein the backoff timer associated with the first S-NSSAI or the second S-NSSAI is not executed.The UE (User Equipment) of the present invention is characterized in that it comprises: a transceiver unit that receives control messages from a control device; and a control unit, wherein the control messages include one or more first pieces of information, the first pieces of information including S-NSSAI (Single Network Slice Selection Assistance information), second information, third information, and fourth information, the second information being information indicating the reason for the rejection of S-NSSAI, the third information being information indicating the value of a backoff timer, and the fourth information being information indicating whether the backoff timer applies to the current PLMN (Public Land Mobile Network) or to all PLMNs; the control unit, based on the receipt of the control messages, appends S-NSSAI to the NSSAI (Network Slice Selection Assistance information) associated with the second and fourth pieces of information according to each piece of first information, starts a backoff timer associated with S-NSSAI based on the value indicated by the third information, adapts the backoff timer to the range indicated by the fourth information, and deletes S-NSSAI from the NSSAI if the backoff timer expires.

[0017] Beneficial effects

[0018] According to one aspect of the present invention, in 5GS, eNS can be supported, and the number of allowed UEs can be managed per slice. Attached Figure Description

[0019] Figure 1 This is a diagram that provides an overview of the mobile communication system (EPS / 5GS).

[0020] Figure 2 This diagram illustrates the detailed structure of a mobile communication system (EPS / 5GS).

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

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

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

[0024] Figure 6 This is a diagram illustrating the registration process. Detailed Implementation

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

[0026] [1. System Overview]

[0027] first, Figure 1 This is a schematic diagram illustrating the mobile communication system 1 used in various embodiments. Figure 2 This is a diagram used to illustrate the detailed configuration of the mobile communication system 1.

[0028] exist Figure 1 The document states that the mobile communication system 1 consists 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.

[0029] In the following descriptions, the symbols for these devices and functions will sometimes be omitted, similar to those for UE, Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, etc.

[0030] In addition, Figure 2 The document describes 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 the interfaces for interconnecting these devices and functions.

[0031] In the following descriptions, for these devices and functions, symbols may be omitted, similar to those used for UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0032] It should be noted that the EPS (Evolved Packet System) of a 4G system consists of an access network_A and a core network_A, but may further include the UE and / or PDN. Similarly, the 5GS (5G System) of a 5G system consists of a UE, an access network_B, and a core network_B, but may further include the DN.

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

[0034] Furthermore, Access Network A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or the wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in the E-UTRAN. It should be noted that, hereinafter, the symbol for eNB 45 may sometimes be omitted, similar to eNBs. Furthermore, in the case of multiple eNBs, they are interconnected, for example, via X2 interfaces. Additionally, one or more access points are configured in the wireless LAN access network.

[0035] Furthermore, the access network _B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access networks. One or more gNBs (NRNodeBs) 122 are configured in the NG-RAN. It should be noted that, hereinafter, the symbol for gNB 122 may sometimes be omitted, similar to eNBs. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is connected to the 5GCN via an NG interface (including the N2 or N3 interface). That is, a gNB is a base station device redesigned for 5GS, with different functions than the base station device (eNB) used in the EPS as a 4G system. Furthermore, in the case of multiple gNBs, each gNB is interconnected, for example, via an Xn interface.

[0036] Furthermore, a non-3GPP access network can be either an untrusted non-3GPP access network or a trusted non-3GPP access network. An untrusted non-3GPP access network can be, for example, a public wireless LAN, a non-3GPP access network that is not subject to security management within the access network. On the other hand, a trusted non-3GPP access network can be an access network defined by 3GPP and can possess TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP gateway function).

[0037] Furthermore, E-UTRAN and NG-RAN are sometimes referred to as 3GPP access. Additionally, wireless LAN access networks and non-3GPP ANs are sometimes referred to as non-3GPP access. Furthermore, nodes configured in access network B are sometimes collectively referred to as NG-RAN nodes.

[0038] In addition, the devices included in Access Network_A and / or Access Network_B and / or Access Network_A and / or Access Network_B are sometimes referred to as Access Network or Access Network Devices.

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

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

[0041] In addition, the following will sometimes refer to core network_A and / or core network_B, devices included in core network_A and / or devices included in core network_B as core network or core network devices or devices within the core network.

[0042] The core network (core network_A and / or core network_B) can be an IP mobile communication network that connects the access network (access network_A and / or access network_B) with the PDN and / or DN operated by the mobile network operator (MNO). It can also be the core network used by the mobile network operator that operates and manages the mobile communication system 1. Furthermore, it can be the core network used by virtual mobile communication operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).

[0043] In addition, Figure 1 The document describes situations where PDN and DN are similar, but they can also be different. A PDN can be a DN (Data Network) that provides communication services to the UE. It should be noted that a DN can be configured as a packet data service network or as a separate network for each service. Furthermore, a PDN can include connected communication terminals. Therefore, connecting to a PDN can also mean connecting to a communication terminal or server device configured on the PDN. Moreover, sending and receiving user data with a PDN can also mean sending and receiving user data with a communication terminal or server device configured on the PDN. It should be noted that a PDN can be expressed as a DN, and vice versa.

[0044] Furthermore, hereinafter, at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one of these included devices are sometimes referred to as a network or network device. That is to say, the sending and receiving of messages and / or the execution of processes by a network and / or network device means the sending and receiving of messages and / or the execution of processes by at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one of these included devices.

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

[0046] Here, IP communication refers to data communication using IP, which involves sending and receiving data via IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted or received by devices and functions included in the EPS (Electronic Power Supply) or 5GS (Power Controller System). Furthermore, non-IP communication refers to data communication that does not use IP, but rather transmits and receives data using a different structure than IP packets. For example, non-IP communication can be data communication achieved by transmitting and receiving application data without an IP header, or it can use other headers such as MAC headers or Ethernet frame headers to transmit and receive user data sent and received by the UE.

[0047] In addition, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may also be composed of elements not described in the text. Figure 2 The device. For example, an AUSF (Authentication Server Function) and an AAA (Authentication, Authorization, and Accounting) server (AAA-S) may be included in core network A and / or core network B.

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

[0049] Furthermore, an AAA server is a device that connects directly to AUSF or indirectly via other network devices and possesses authentication, authorization, and accounting functions. An AAA server can be a network device within the core network. It should be noted that an AAA server can be located within the PLMN but not within Core Network A and / or Core Network B. That is, an AAA server can be a core network device or a device located outside the core network. For example, an AAA server can be a server device within the PLMN managed by a 3rd Party (third party).

[0050] It should be noted that, in Figure 2 For the sake of simplicity in the accompanying drawings, only one example of each device and function is described. However, multiple identical devices and functions can be configured in the mobile communication system 1. Specifically, multiple devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150 can be configured in the mobile communication system 1.

[0051] [2. Composition of each device]

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

[0053] It should be noted that the storage units (Storage Unit_A340, Storage Unit_A440, Storage Unit_B540, Storage Unit_A640, Storage Unit_B740) within each device and function mentioned below are, for example, composed of semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. Furthermore, each storage unit can store not only information originally set at the factory, but also various information exchanged with devices and functions other than its own device and function (e.g., UE and / or access network devices and / or core network devices and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc., included in control messages exchanged during the various communication processes described later. Furthermore, each storage unit can also store this information per UE. Moreover, when interoperability between 5GS and EPS is performed, each storage unit can store control messages and user data exchanged with devices and functions included in 5GS and / or EPS. At this point, it can store not only information sent and received through the N26 interface, but also information not sent and received through the N26 interface.

[0054] [2.1. UE Device Configuration]

[0055] First, use Figure 3 An example of the device configuration of a UE (User Equipment) will be described. The UE consists of a control unit_A300, an antenna 310, a transceiver unit_A320, and a storage unit_A340. The control unit_A300, the transceiver unit_A320, and the storage unit_A340 are connected via a bus. The transceiver unit_A320 is connected to the antenna 310.

[0056] The control unit_A300 is a functional unit that controls the overall operation and functions of the UE. The control unit_A300 reads and executes various programs stored in the storage unit_A340 as needed, thereby realizing various processes in the UE.

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

[0058] When reference Figure 2In detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface using the transceiver unit (A320). Furthermore, the UE can communicate with the base station device (gNB) in the 5G AN using the transceiver unit (A320). Additionally, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit (A320). Since the N1 interface is a logical interface, the actual communication between the UE and the AMF is conducted through the 5G AN.

[0059] The storage unit A340 is a functional unit used to store programs, user data, control information, etc. required for various actions of the UE.

[0060] [2.2. gNB Device Configuration]

[0061] Next, use Figure 4 An example of the gNB device configuration will be described. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0062] The control unit_B500 is a functional unit that controls the overall operation and functions of the gNB. The control unit_B500 reads and executes various programs stored in the storage unit_B540 as needed, thereby realizing various processes within the gNB.

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

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

[0065] When reference Figure 2 In detail, the gNB located in the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface using the network connection unit_B520. Furthermore, the gNB can communicate with the UE using the transceiver unit_B530.

[0066] The storage unit B540 is a functional unit used to store programs, user data, control information, etc., required for various operations of the gNB.

[0067] [2.3. AMF Device Configuration]

[0068] Next, use Figure 5 An example of the device configuration of an AMF will be described. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF can be a node in the operation control plane.

[0069] The control unit_B700 is a functional unit that controls the overall operation and function of the AMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes within the AMF.

[0070] The network connection unit_B720 is a functional unit for connecting the AMF to base station devices (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF within the 5G AN. That is, the AMF can use the network connection unit_B720 to send and receive user data and / or control information with the base station devices (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF within the 5G AN.

[0071] When reference Figure 2 In detail, the AMF (Active Network Module) within the 5GCN can communicate with the gNB via the N2 interface, with the UDM via the N8 interface, with the SMF via the N11 interface, and with the PCF via the N15 interface using the network connection unit_A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit_A620. Since the N1 interface is a logical interface, communication between the UE and AMF is actually conducted via the 5G AN (Active Network Module). Additionally, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface using the network connection unit_A620.

[0072] The storage unit_B740 is a functional unit used to store programs, user data, control information, etc. required for various operations of the AMF.

[0073] It should be noted that the AMF has the following functions: exchanging control messages with the RAN using the N2 interface; exchanging NAS messages with the UE using the N1 interface; encrypting and protecting the integrity of NAS messages; registration management (RM); connection management (CM); reachability management; mobility management for UEs, etc.; transmitting SM (Session Management) messages between the UE and the SMF; access authentication (Access Authorization); security anchor function (SEA); security context management (SCM); supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function); supporting the transmission and reception of NAS signals between the UE and the N3IWF via the N3IWF; and authenticating UEs connected via the N3IWF.

[0074] Furthermore, registration management manages the RM state of each UE. The RM state can be synchronized between the UE and the AMF. There are two RM states: unregistered (RM-DEREGISTERED state) and registered (RM-REGISTERED state). In the RM-DEREGISTERED state, because the UE is not registered with the network, the UE context in the AMF lacks valid location and routing information for that UE; therefore, the AMF cannot reach the UE. Conversely, in the RM-REGISTERED state, the UE is registered with the network, and therefore, the UE can receive services requiring network registration. It should be noted that the RM state can also be represented as a 5GMM state. In this case, the RM-DEREGISTERED state can be represented as 5GMM-DEREGISTERED state, and the RM-REGISTERED state can be represented as 5GMM-REGISTERED state.

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

[0076] Furthermore, 5GMM-DEREGISTERED can be a state where the devices have not established a 5GMM context, a state where the location information of UE_A10 has not been obtained by the network, or a state where the network cannot reach UE_A10. It should be noted that when the devices are 5GMM-DEREGISTERED, UE_A10 can start the registration process or establish a 5GMM context by executing the registration process.

[0077] Furthermore, in connection management, the CM state of each UE is managed. The CM state can be synchronized between the UE and the AMF. There are two CM states: a disconnected 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. Furthermore, in the CM-IDLE state, the UE does not have a connection via the N2 interface (N2connection) or the N3 interface (N3connection). On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection established with the AMF via the N1 interface. Additionally, in the CM-CONNECTED state, the UE may also have a connection via the N2 interface (N2connection) and / or the N3 interface (N3connection).

[0078] Furthermore, connection management can be divided into CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access can be either an idle state (CM-IDLE state over 3GPP access) or a connected state (CM-CONNECTED state over 3GPP access). Similarly, the CM states in non-3GPP access can be either an idle state (CM-IDLE state over non-3GPP access) or a connected state (CM-CONNECTED state over non-3GPP access). It should be noted that the idle state can be expressed as an idle mode, and the connected state can be expressed as a connected mode.

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

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

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

[0082] [2.4. SMF Device Configuration]

[0083] Next, use Figure 5 An example of the device configuration of an SMF will be described. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF can be a node in the operation control plane.

[0084] The control unit_B700 is a functional unit that controls the overall operation and function of the SMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes within the SMF.

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

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

[0087] The storage unit B740 is a functional unit used to store programs, user data, control information, etc., required for various operations of the SMF.

[0088] The SMF has the following functions: session management functions such as PDU session establishment, modification, and release; IP address allocation and management functions for UE; UPF selection and control functions; UPF setting functions for routing services to the appropriate destination (sending destination); functions for sending and receiving NAS messages (SM part); functions for notifying downlink data that has arrived (Downlink Data Notification); functions for providing AN-specific (each AN's) SM information sent to the AN via the AMF and via the N2 interface; functions for determining the SSC mode (Session and Service Continuity mode) for the session; roaming functions, etc.

[0089] [2.5. UPF Device Configuration]

[0090] Next, use Figure 5 An example of the UPF device configuration will be described. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF can be a node in the control plane.

[0091] The control unit_B700 is a functional unit that controls the overall operation and function of the UPF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes within the UPF.

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

[0093] When reference Figure 2 In detail, the UPF located within the 5GCN can communicate with the gNB via the N3 interface, with the SMF via the N4 interface, with the DN via the N6 interface, and with other UPFs via the N9 interface by using the network connection unit _A620.

[0094] The storage unit B740 is a functional unit used to store the programs, user data, control information, etc. required for the various operations of the UPF.

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

[0096] Furthermore, a UPF can be a gateway for IP and / or non-IP communication. Additionally, a UPF can function as both a transmitter of IP communication and a converter between IP and non-IP communication. Moreover, multiple configured gateways can connect the core network (B) and a single DN. It should be noted that a UPF can have connectivity with other NFs and can also connect to various devices through other NFs.

[0097] It should be noted that the user plane refers to the user data transmitted and received between the UE and the network. The user plane can use PDN connections or PDU sessions for transmission and reception. Furthermore, in the case of EPS, the user plane can use the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface for transmission and reception. Moreover, in the case of 5GS, the user plane can be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. Hereinafter, the user plane can be referred to as U-Plane.

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

[0099] Furthermore, a U-Plane (User Plane; UP) can be a communication path for sending and receiving user data, and can consist of multiple bearers. Similarly, a C-Plane (Control Plane; CP) can be a communication path for sending and receiving control messages, and can also consist of multiple bearers.

[0100] [2.6. Description of other devices and / or functions and / or identification information in this embodiment]

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

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

[0103] Furthermore, SM (Session Management) messages (also known as NAS (Non-Access-Stratum) SM messages) can be NAS messages used during SM operations, or control messages exchanged between UE_A10 and SMF_A230 via AMF_A240. Moreover, SM messages can include: PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, PDU session modification request messages, PDU session modification command messages, PDU session modification complete messages, PDU session modification command reject messages, PDU session modification reject messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, and PDU session release complete messages, etc. In addition, the procedures used in SM or SM processes may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each procedure can start from the UE or from the NW.

[0104] Furthermore, MM (Mobility Management) messages (or NAS MM messages) can be either NAS messages used in MM procedures or control messages exchanged between UE_A10 and AMF_A240. Moreover, MM messages can include: Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages, De-registration accept messages, Configuration update command messages, Configuration update complete messages, Service request messages, Service accept messages, Service reject messages, Notification messages, and Notification response messages, etc. In addition, the processes used by MM or MM procedures may include: registration procedure, de-registration procedure, generic UE configuration update procedure, authentication and authorization procedure, service request procedure, paging procedure, and notification procedure.

[0105] Furthermore, 5GS (5G System) service can be a connectivity service provided using the core network _B190. Moreover, 5GS service can be either a different service from EPS service or the same service as EPS service.

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

[0107] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, which can be IPv4, IPv6, IPv4v6, or non-IP. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying IPv4v6 indicates that either IPv4 or IPv6 is used for data transmission and reception. Specifying non-IP indicates that communication is conducted using a method other than IP, rather than using IP.

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

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

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

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

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

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

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

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

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

[0117] Furthermore, the configured NSSAI is the NSSAI supplied to the UE and stored. The UE can store the configured NSSAI per PLMN. The configured NSSAI can be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI can be expressed as the configured S-NSSAI. The configured S-NSSAI can be structured to include both the S-NSSAI and the mapped S-NSSAI.

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

[0119] Furthermore, an allowed NSSAI (Allowed NSSAI) is information indicating one or more network slices that are permitted for the UE. In other words, an allowed NSSAI identifies the network slice that allows the network to connect to the UE. The UE and the network store and manage the allowed NSSAI as UE information on a per-access basis (3GPP access or non-3GPP access). The S-NSSAI included in the allowed NSSAI can be expressed as allowed S-NSSAI. Allowed S-NSSAI can be configured to include both the S-NSSAI and the mapped S-NSSAI.

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

[0121] Furthermore, a rejected NSSAI indicates that one or more network slices are not allowed for the UE. In other words, a rejected NSSAI identifies network slices that the network is not allowed to connect to the UE. A rejected NSSAI can be a combination of one or more S-NSSAIs and a rejection reason value. Here, the rejection reason value refers to the information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network can appropriately store and manage rejected NSSAIs based on establishing corresponding rejection reason values ​​for each S-NSSAI. Moreover, rejected NSSAIs can be included in registration acceptance messages, configuration update commands, registration rejection messages, NAS messages sent from the network to the UE, or RRC messages that include NAS messages. The S-NSSAIs included in a rejected NSSAI can be expressed as rejected S-NSSAIs. A rejected NSSAI can be any one of the first rejected NSSAIs to the third rejected NSSAIs, a pending NSSAI, or the first NSSAI, or a combination thereof. The S-NSSAI included in the rejected S-NSSAI can be expressed as a rejected S-NSSAI. The rejected S-NSSAI can be constructed as including the S-NSSAI and the mapped S-NSSAI.

[0122] Here, the first rejected NSSAI is a set of more than one S-NSSAIs included in the S-NSSAI of the requested NSSAI that are unavailable to the UE in the current PLMN. The first rejected NSSAI can be a 5GS rejected NSSAI for the current PLMN, a rejected S-NSSAI for the current PLMN, or an S-NSSAI included in a rejected NSSAI for the current PLMN. The first rejected NSSAI can be a rejected NSSAI stored by the UE or NW, or a rejected NSSAI sent from the NW to the UE. When the first rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the first rejected NSSAI can be a combination of one or more S-NSSAIs and a reason value. The rejection reason value at this time can be either "S-NSSAI is not available in the current PLMN" or information indicating that the S-NSSAI corresponding to the rejection reason value is not available in the current PLMN.

[0123] The first rejection NSSAI is valid throughout the entire registered PLMN. In other words, the UE and / or NW can operate the first rejection NSSAI and the S-NSSAI included in the first rejection NSSAI as access type-independent information. That is, the first rejection NSSAI can be information valid for both 3GPP access and non-3GPP access.

[0124] The UE can delete the first-rejected NSSAI from storage if it becomes unregistered relative to the current PLMN, through access via both 3GPP and non-3GPP access. In other words, the UE can delete the first-rejected NSSAI if it becomes unregistered relative to the current PLMN through an access, or if it successfully registers with a new PLMN through an access, or if it fails to register with a new PLMN through an access and becomes unregistered, or if it becomes unregistered through access via another access.

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

[0126] The second rejected NSSAI is valid within the current registration area. That is, the UE and / or NW can operate the second rejected NSSAI and the S-NSSAI included in it as information for each access type. In other words, the second rejected NSSAI can be information valid for both 3GPP access and non-3GPP access. Furthermore, the UE can delete the second rejected NSSAI from storage once it transitions to a non-registered state relative to a certain access type.

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

[0128] The third rejection NSSAI is valid throughout the registered PLMN. In other words, the UE and / or NW can operate the third rejection NSSAI and the S-NSSAI included in the third rejection NSSAI as access type-independent information. That is, the third rejection NSSAI can be information valid for both 3GPP and non-3GPP access. The third rejection NSSAI can be a different NSSAI from the initial rejection NSSAI. The third rejection NSSAI can be the first rejection NSSAI.

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

[0130] The first NSSAI can include information on one or more S-NSSAIs that reach the maximum number of UEs per network slice. The first NSSAI can be a rejected NSSAI, an allowed NSSAI, or a pending NSSAI. The first NSSAI can be an NSSAI stored by the UE and / or the NW, or an NSSAI sent from the NW to the UE.

[0131] When sending a first NSSAI from the NW to the UE, the first NSSAI may include information including one or more of the following: at least one S-NSSAI and a mapped S-NSSAI, a reason value, a backoff timer value, and information indicating the validity period of the backoff timer value. The reason value can be either "the S-NSSAI that reaches the maximum number of UEs per network slice" or information indicating the maximum number of UEs allowed by the S-NSSAI corresponding to the rejection reason value. Here, the reason value can be either the rejection reason value included in the rejection NSSAI or flag information. Furthermore, the backoff timer value may indicate the following periods: prohibition of UEs from using the S-NSSAI associated with the corresponding S-NSSAI or the mapped S-NSSAI, the start of sending MM messages, and the start of sending SM messages.

[0132] Furthermore, the information indicating the validity period of the backoff timer value indicates whether the backoff timer value is applicable to the current PLMN (Public Land Mobile Network), whether it is applicable to all PLMNs, and whether it is valid in the current registration area.

[0133] The first NSSAI can be valid throughout the entire registered PLMN, across all PLMNs, or within the registered area. When the first NSSAI is valid throughout the registered PLMN or across all PLMNs, the UE and / or NW can operate with the first NSSAI and its included S-NSSAI as access type-independent information. When the first NSSAI is valid within the registered area, the UE and / or NW can operate with the first NSSAI and its included S-NSSAI as information for each access type.

[0134] The first NSSAI can be an allowed NSSAI, a rejected NSSAI, a pending NSSAI, or a different type of information.

[0135] Pending NSSAIs are S-NSSAIs that require specific network slice authentication for the network. They are a collection of one or more S-NSSAIs that cannot be used in the current PLMN if the specific network slice authentication is not completed. Pending NSSAIs can be NSSAIs rejected by 5GS due to specific network slice authentication and authorization, or pending NSSAIs. Pending NSSAIs can be NSSAIs stored by the UE or NW, or NSSAIs sent from the NW to the UE. It should be noted that pending NSSAIs can be NSSAIs independent of rejected NSSAIs, and are not limited to rejected NSSAIs. When a pending NSSAI is an NSSAI sent from the NW to the UE, the pending NSSAI can be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value at this time can be "S-NSSAI pending due to specific network slice authentication and authorization (S-NSSAI specific network slice authentication and authorization pending)", or it can be information indicating that the UE is prohibited or pending from using the S-NSSAI corresponding to the rejection reason value until the specific network slice authentication and authorization for that S-NSSAI is completed.

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

[0137] A pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify the slice for which the UE has pending the process. Specifically, the UE will not initiate a registration request process for the S-NSSAIs included in the pending NSSAI while storing the pending NSSAI. In other words, the UE will not use the S-NSSAIs included in the pending NSSAI during the registration process until the specific network slice authentication and authorization for the S-NSSAIs included in the pending NSSAI are completed. A pending NSSAI is identification information received from the core network that includes one or more S-NSSAIs corresponding to a rejection reason value indicating pending authentication and authorization for a specific network slice. Pending NSSAIs are access type-independent information. Specifically, when the UE stores pending NSSAIs, the UE will not attempt to send a registration request message including the S-NSSAIs included in the pending NSSAI to either 3GPP access or non-3GPP access parties.

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

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

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

[0141] Network slice-specific authentication and authorization (BSA) functions refer to the authentication and authorization functions specific to network slices. These functions enable UE authentication and authorization outside the core network, such as the 3rd Party, through network slice-specific authentication and authorization. PLMNs and network devices equipped with BSA functions can perform BSA authentication and authorization procedures for a specific S-NSSAI based on the UE's registration information. Furthermore, UEs equipped with BSA functions can manage and store NSSAIs pending rejection due to BSA authentication and authorization failures and / or rejections due to BSA authentication and authorization failures. In this document, BSA authentication and authorization may sometimes be referred to as network slice-specific authentication and authorization procedures or authentication and authorization procedures.

[0142] S-NSSAIs requiring specific network slice authentication and authorization are S-NSSAIs managed by the core network and / or core network devices. The core network and / or core network devices establish and store a mapping between S-NSSAIs and information indicating whether specific network slice authentication and authorization are required. Thus, S-NSSAIs requiring specific network slice authentication and authorization can be stored. The core network and / or core network devices can further establish and store a mapping between S-NSSAIs requiring specific network slice authentication and authorization and information indicating whether the specific network slice authentication and authorization is completed, or information indicating a state of completion that allows or succeeds. The core network and / or core network devices can manage S-NSSAIs requiring specific network slice authentication and authorization as information independent of the access network.

[0143] Maximum UE number management for slice connections refers to managing the maximum number of UEs that can be registered simultaneously in a network slice or S-NSSAI. Here, a UE registered in a network slice or S-NSSAI refers to a network slice represented by an S-NSSAI, which is included in and stored in the allowed NSSAIs. Devices within a network supporting maximum UE number management for slice connections can store whether maximum UE number management for slice connections is required for each S-NSSAI, and can also confirm during the registration process whether the number of registered UEs has reached a constant that serves as the maximum. Furthermore, it is preferable that each device supporting maximum UE number management for slice connections stores a first NSSAI. In this document, the maximum UE number for slice connections is sometimes expressed as the maximum number of UEs connected to each slice, the maximum number of UEs that can be registered in a network slice or S-NSSAI, or the maximum number of UEs or a constant.

[0144] A backoff timer is a timer used to initiate the process of prohibiting the transmission of MM messages and / or SM messages implemented by the UE. The backoff timer is managed and executed by the UE. The backoff timer can be associated with S-NSSAI. During the period when the backoff timer associated with S-NSSAI is valid, the UE may be in a state where the transmission of MM messages and / or SM messages using S-NSSAI is prohibited, constrained, or limited. These constraints can be either restrictions implemented by 5GS congestion management or constraints that include constraints implemented by 5GS congestion management.

[0145] The backoff timer can be a timer that is started and / or stopped by S-NSSAI and / or PLMN units.

[0146] Specifically, the backoff timer can correspond to the S-NSSAI and can be a timer used to prohibit the transmission of MM messages and / or SM messages using a specific S-NSSAI. In other words, the UE can be configured not to transmit MM messages and / or SM messages using that specific S-NSSAI during the timer count.

[0147] Furthermore, the UE can also be configured to allow the transmission of MM messages and / or SM messages that were prohibited in the previous PLMN within the timer count, based on specific conditions described later. It should be noted that, when expressed as allowing the transmission of MM messages and / or SM messages that were prohibited in the previous PLMN, it can mean allowing the transmission of MM messages and / or SM messages using the same S-NSSAI as the S-NSSAI corresponding to the backoff timer and / or S-NSSAI associated with the same S-NSSAI and / or S-NSSAI mapped to the same S-NSSAI.

[0148] Furthermore, the backoff timer can be a timer used to prohibit the transmission of MM messages using a specific NSSAI. In other words, the UE can be configured not to transmit MM messages using NSSAIs that include that specific NSSAI and / or a specific S-NSSAI while the timer is counting.

[0149] Furthermore, the UE can also be configured to allow the transmission of MM messages that were prohibited in the previous PLMN within the new PLMN, based on specific conditions described later, during this timer count. It should be noted that, when expressed as allowing the transmission of MM messages prohibited in the previous PLMN, it can mean allowing the transmission of MM messages using the same NSSAI as the NSSAI corresponding to the backoff timer establishment and / or including an NSSAI with the same S-NSSAI as the S-NSSAI corresponding to the backoff timer establishment. Moreover, when expressed as allowing the transmission of MM messages prohibited in the previous PLMN, it can also mean allowing the transmission of MM messages using an NSSAI that includes an S-NSSAI associated with the S-NSSAI corresponding to the backoff timer establishment and / or including an NSSAI associated with a mapping of the S-NSSAI corresponding to the backoff timer establishment.

[0150] Furthermore, the backoff timer can be a timer used to prohibit the transmission of MM messages that correspond to no NSSAI and use no NSSAI. In other words, UE_A10 can be configured not to transmit MM messages using no NSSAI during this timer count. Moreover, UE_A10 can also be configured to allow the transmission of MM messages that were prohibited in the previous PLMN in the new PLMN during this timer count, based on specific conditions described later. It should be noted that when expressed as allowing the transmission of MM messages that were prohibited in the previous PLMN, it can mean allowing MM messages using no NSSAI.

[0151] Furthermore, the backoff timer can also be a 5GMM timer and / or an EMM (EPS mobility management) timer. Moreover, the backoff timer can be timer T3448, or a timer equivalent to timer T3448. In other words, the backoff timer can be the same timer used to constrain communication of user data via the Control Plane, or it can be the same timer as the timer used for this purpose.

[0152] Next, in this embodiment, the identification information transmitted, received, stored, and managed through each device will be explained.

[0153] The first identification information represents the network slice the UE wishes to register for. The first identification information may include information from one or more S-NSSAIs corresponding to the network slice the UE wishes to register for. The S-NSSAIs included in the first identification information can be either S-NSSAIs included in the configured NSSAIs corresponding to the current PLMN establishment, or S-NSSAIs included in the permitted NSSAIs corresponding to the current PLMN establishment. In other words, the first identification information can be one or more S-NSSAIs included in the configured NSSAIs corresponding to the current PLMN establishment, or one or more S-NSSAIs included in the permitted NSSAIs corresponding to the current PLMN establishment, or a combination of both. More specifically, the permitted NSSAIs corresponding to the current PLMN establishment can refer to the permitted NSSAIs corresponding to the current PLMN and the current access type establishment. Furthermore, the first identification information may be the NSSAI requested by 5GS.

[0154] It should be noted that the S-NSSAI included in the first identification information may be an S-NSSAI that is not included in the rejected NSSAI and / or pending NSSAI and / or the first NSSAI. Moreover, the S-NSSAI included in the first identification information may be an S-NSSAI whose backoff timer has not been executed and is associated with that S-NSSAI or the S-NSSAI mapped to that S-NSSAI.

[0155] The second identification information may be information indicating whether the function of managing the maximum number of UEs for UE-slice connections is supported. Alternatively, the second identification information may be information indicating whether the function of managing the maximum number of UEs for UE-slice connections is supported. The second identification information may be 5G MM capability information. The second identification information may be information indicating whether the UE can perform storage.

[0156] The tenth identification information may be information indicating that the maximum number of UEs that can be registered in a network slice or S-NSSAI has been reached. The tenth identification information may be included in an allowed NSSAI sent from the network, a rejected NSSAI sent from the network, a pending NSSAI sent from the network, or may be sent from the network as different information from these.

[0157] Furthermore, the tenth identification information can be an NSSAI. Moreover, the tenth identification information can be either an allowed NSSAI or a rejected NSSAI. Furthermore, the tenth identification information can be either a pending NSSAI or a different NSSAI.

[0158] The tenth identification information may be a first NSSAI or an S-NSSAI included in the first NSSAI. The tenth identification information may be configured to include at least one of the eleventh to fifteenth identification information. Specifically, the tenth identification information may be configured to include at least one of the following: an S-NSSAI that represents the maximum number of UEs that can register in a network slice or S-NSSAI; an S-NSSAI that maps to the S-NSSAI; a reason value indicating that the maximum number of UEs that can register in the network slice or S-NSSAI has been reached; a backoff timer value indicating the period during which UEs are prohibited from sending registration request messages using the S-NSSAI; and information indicating the effective range of the backoff timer.

[0159] Furthermore, the tenth identification information may also include at least one of the following: a reason value indicating that the maximum number of UEs that can register with the network slice has been reached; a backoff timer value indicating the period during which the transmission of registration request messages using no NSSAI is prohibited; and information indicating the effective range of the backoff timer. It should be noted that the reason value indicating that the maximum number of UEs that can register with the network slice has been reached, the backoff timer value indicating the period during which the transmission of registration request messages using no NSSAI is prohibited, and the information indicating the effective range of the backoff timer may be transmitted and received separately and are not included in the tenth identification information. Here, in the case where the tenth identification information includes a rejected NSSAI, the reason value included in the tenth identification information may be a rejection reason value.

[0160] The eleventh identification information may be information and / or a reason value indicating that the maximum number of UEs that the network allows a UE to register in a network slice or S-NSSAI has been reached. The eleventh identification information may also be information and / or a reason value indicating that the use of S-NSSAI is rejected or restricted due to reaching the maximum number of UEs connected to each slice. In other words, the eleventh identification information is information and a reason value indicating that the network rejects or restricts the use of S-NSSAI for a UE because it has reached the maximum number of UEs connected to each slice. The eleventh identification information may be included in the tenth identification information, or it may be associated with the S-NSSAI shown in the fourteenth identification information and / or the mapped S-NSSAI shown in the fifteenth identification information included in the same tenth identification information. The eleventh identification information may be associated with each of the identification information included in the same tenth identification information. In the case where the eleventh identification information is included in the rejected NSSAI, the eleventh identification information may be a rejection reason value. The eleventh identification information may also be flag information.

[0161] Furthermore, the eleventh identification information can be a reason value indicating that connections to the slice are restricted and / or not allowed. Also, the eleventh identification information can be a reason value indicating that registration to the slice is restricted and / or not allowed.

[0162] Furthermore, the eleventh identification information can be a 5GMM (5G Mobility Management) cause. Also, the eleventh identification information can be a twenty-second 5GMM cause. Here, the twenty-second 5GMM cause can be a cause value indicating congestion. Moreover, the twenty-second 5GMM cause can also be information sent to the UE due to network congestion.

[0163] Furthermore, the eleventh identification information can be a 5GMM cause other than the twenty-second 5GMM cause. For example, the eleventh identification information can be information sent to the UE due to network slice congestion. Also, the eleventh identification information can be information sent to the UE due to insufficient resources in the network slice. Moreover, the eleventh identification information can also be a reason value indicating that the requested service cannot be provided due to insufficient resources for a specific slice.

[0164] The twelfth identification information may be the value of a backoff timer. Specifically, the twelfth identification information may be information indicating the period during which the network prohibits the UE from using the same S-NSSAI included in the tenth identification information, the fourteenth identification information, and / or the fifteenth identification information, to begin sending an MM message or to begin sending an SM message other than a PDU connection release request message. In other words, the twelfth identification information may be information indicating the period during which the network prohibits the UE from using the same S-NSSAI included in the tenth identification information, the fourteenth identification information, and / or the fifteenth identification information, to begin sending a registration request message.

[0165] The twelfth identification information may be included in the tenth identification information, or it may be associated with the S-NSSAI shown in the fourteenth identification information and / or the S-NSSAI mapped in the fifteenth identification information included in the same tenth identification information. The twelfth identification information may also be associated with each of the identification information included in the same tenth identification information.

[0166] The thirteenth identification information is information indicating the effective range of the backoff timer. Specifically, the thirteenth identification information may be information indicating the effective range of the backoff timer counted by the UE, using the corresponding backoff timer value. More specifically, the thirteenth identification information may be information indicating whether the corresponding backoff timer applies to the current PLMN or to all PLMNs. Alternatively, the thirteenth identification information may also be information indicating whether it applies to the current registration region.

[0167] Furthermore, the thirteenth identification information can be either information indicating the scope of the constraint or information indicating the scope to which the constraint applies. It should be noted that the constraint can be a constraint implemented by congestion management. More specifically, the constraint can be a constraint restricting the transmission of MM messages by the UE. Moreover, the constraint can be a constraint implemented by a backoff timer.

[0168] The thirteenth identification information may be included in the tenth identification information. In this case, the value of the corresponding backoff timer may be the value shown by the twelfth identification information included in the same tenth identification information. Moreover, in this case, the thirteenth identification information may be associated with each of the identification information included in the same tenth identification information.

[0169] The fourteenth identification information is information representing the S-NSSAI that represents the maximum number of UEs that can be registered in each S-NSSAI. The fourteenth identification information can be an S-NSSAI included in the tenth identification information, or it can be associated with an S-NSSAI mapped to the fifteenth identification information included in the same tenth identification information. The fourteenth identification information can be associated with each identification information included in the same tenth identification information. Furthermore, the fourteenth identification information can be an S-NSSAI.

[0170] The fifteenth identification information is the S-NSSAI of the HPLMN associated with the corresponding S-NSSAI. Specifically, if the current PLMN is not an HPLMN, the fifteenth identification information can be the S-NSSAI of the HPLMN that represents the S-NSSAI mapped to the current PLMN.

[0171] The fifteenth identification information can be the S-NSSAI mapped by the tenth identification information, or it can be associated with the S-NSSAI shown by the fourteenth identification information included in the same tenth identification information, or in this case, it can be the S-NSSAI mapped by the S-NSSAI shown by the fourteenth identification information. The fifteenth identification information can be associated with each identification information included by the same tenth identification information. Moreover, the fifteenth identification information can be the S-NSSAI mapped by the S-NSSAI represented by the fourteenth identification information.

[0172] [3.1. Description of the processes used in each embodiment]

[0173] Next, the processes used in each embodiment will be described. It should be noted that the processes used in each embodiment include a registration procedure. These procedures will be described below.

[0174] It should be noted that in each implementation method, such as Figure 2As described herein, the example given is a case where the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device (i.e., the same physical hardware, the same logical hardware, or the same software). However, the content described in this embodiment can also be applied to cases where these are configured as different devices (i.e., different physical hardware, different logical hardware, or different software). For example, data can be transmitted and received directly between these devices, through the N26 interface between the AMF and MME, or through the UE.

[0175] [3.2. Registration Process]

[0176] First, use Figure 6 The registration procedure is described below. Hereinafter, this refers to the registration procedure. The registration procedure is initiated by the UE to register with the access network_B and / or core network_B and / or DN. If the UE is not registered in the network, this procedure can be executed at any time, such as when power is applied. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), this procedure can begin at any time. Furthermore, each device (especially the UE and AMF) can transition to a registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state can be managed by each device on a per-access basis. Specifically, each device can independently manage the registration state (registered state or non-registered state) for 3GPP access and the registration state for non-3GPP access.

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

[0178] The UE can initiate the registration process during cross-TA mobility. In other words, the UE can initiate the registration process when moving to a TA different from the TA shown in its maintained TA list. Furthermore, the UE can also initiate this process when a running backoff timer or other timer expires. Moreover, the UE can also initiate the registration process when the context of each device needs to be updated due to the disconnection or disabling of the PDU session. Furthermore, the UE can also initiate the registration process when capability information and / or preference selection related to the establishment of the UE's PDU session changes. Furthermore, the UE can initiate the registration process periodically. Moreover, the UE can initiate the registration process based on the completion of the UE configuration update process, the completion of the registration process, the completion of the PDU session establishment process, the completion of the PDU session management process, information received from the network during each process, or the expiration or termination of the backoff timer. It should be noted that the UE can execute the registration process at any time, and is not limited to these.

[0179] It should be noted that the process used to change the state of a UE from never registered in the network to a registered state can be called the initial registration procedure or the registration procedure for initial registration. The registration procedure performed when the UE is already registered in the network can be called the registration procedure for mobility and periodic registration update or the mobility and periodic registration procedure.

[0180] Figure 6 The "new AMF" refers to the UE's AMF registered through this process, while the "old AMF" means the UE's AMF was registered through a process preceding this one. During this process, if no changes to the AMF occur, no interface or process exists between the old and new AMFs. The new AMF can be the same device as the old AMF. In this embodiment, when referred to as "AMF," it can mean either "new AMF," "old AMF," or both.

[0181] First, the UE initiates the registration process (S600)(S602)(S604) by sending a registration request message to the new AMF. Specifically, the UE sends an RRC message (S600) containing the registration request message to the 5G AN (or gNB). It should be noted that the registration request message is a NAS message transmitted and received on the N1 interface. Furthermore, the RRC message can be a control message transmitted and received between the UE and the 5G AN (or gNB). Additionally, NAS messages are processed by the NAS layer, and RRC messages are processed by the RRC layer. It should be noted that the NAS layer is a higher-level layer than the RRC layer.

[0182] Here, the UE can include at least one of the first to second identification information in the registration request message and / or RRC message. Furthermore, the UE can also include identification information indicating the type of this process in the registration request message and / or RRC message. Here, the identification information indicating the type of this process can be 5GS registration type IE, or information indicating that this process is for initial registration, for registration information updates accompanying mobility, for periodic registration information updates, or for registration in emergency situations.

[0183] The UE may include its capability information in the registration request message to notify the network of the functions it supports. Here, the UE's capability information may be the 5G MM capability of the 5GS.

[0184] The UE can include this identification information in control messages from different layers, such as control messages from layers lower than the RRC layer (e.g., MAC layer, RLC layer, PDCP layer). It should be noted that by sending this identification information, the UE can indicate support for various functions, make a request, or represent both. Furthermore, when sending and receiving multiple identification messages, two or more of these identification messages can constitute one or more separate identification messages. It should also be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification message or as different identification messages.

[0185] It should be noted that the UE may select and determine whether to send the first identification information to the second identification information to the network based on the UE's capability information and / or UE policy and / or UE status and / or user registration information and / or the context maintained by the UE.

[0186] The UE can send the second identification information if it has the function of managing the maximum number of UEs for slice connection or if it requests at least one S-NSSAI that needs to be used for managing the maximum number of UEs for slice connection. The UE can notify the network that it has the function of storing the first NSSAI by sending the second identification information.

[0187] Furthermore, the UE can include this capability information in the registration request message when it has specific Network Slice Authentication and Authorization (NSSAA) functionality or requests at least one S-NSSAI identifying a slice requiring NSSAA. The UE can use this capability information to request the network to operate the UE as an NSSAA-enabled UE and to execute the authentication and authorization processes implemented by the NSSAA functionality in UE-related processes.

[0188] The UE may store permitted NSSAIs relative to the requested PLMN and the requested access, and / or configured NSSAIs and denied NSSAIs relative to the requested PLMN. Furthermore, the UE may also store the S-NSSAIs mapped to each NSSAI.

[0189] The UE can send the second identification information if it stores allowed NSSAIs and / or maintains configured NSSAIs relative to the requested PLMN and the requested access. The UE can select one or more S-NSSAIs from the stored allowed and / or configured NSSAIs and include them in the first identification information before sending them. Furthermore, if the UE stores rejected NSSAIs, the S-NSSAIs included in the rejected NSSAIs can be sent without being included in the first identification information. Moreover, if the backoff timer corresponding to a particular S-NSSAI is active (i.e., while the backoff timer is running), the UE can send the S-NSSAI or related S-NSSAIs without including them in the first identification information; or, the UE can send the S-NSSAI or related S-NSSAIs without including them in the first identification information until the backoff timer stops. Specifically, if the S-NSSAI corresponding to the backoff timer is the S-NSSAI of the requested PLMN, the S-NSSAI can be sent without including it in the first identification information while the backoff timer is active.

[0190] The UE may include information other than the first to second identification information in the registration request message and / or the RRC message including the registration request message. For example, the UE ID and / or PLMN ID and / or AMF identification information may be included in the registration request message and / or the RRC message including the registration request message. Here, AMF identification information may refer to information that identifies an AMF or a set of AMFs, such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0191] In addition, the UE can initiate the PDU session establishment process during registration by sending an SM message (e.g., a PDU session establishment request message) in the registration request message or by sending an SM message (e.g., a PDU session establishment request message) together with the registration request message.

[0192] When the 5G AN (or gNB) receives an RRC message including a registration request message, it selects the AMF (Application Facilitator) for transmitting the registration request message (S602). It should be noted that the 5G AN (or gNB) can select the 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) can select the new AMF of the destination of the registration request message based on at least one of the first to second identification information.

[0193] For example, a 5G AN (or gNB) can select an AMF based on first identification information. Specifically, the 5G AN (or gNB) can select an AMF that is included in the network slice identified by S-NSSAI as included in the first identification information, or that has connectivity to the network slice.

[0194] Moreover, for example, a 5G AN (or gNB) can select an AMF that has the function of managing the maximum number of UEs for slice connection and an AMF that has the function of connectivity to a network that has the function of managing the maximum number of UEs for slice connection based on the second identification information.

[0195] It should be noted that the selection method for the AMF is not limited to this; the 5G AN (or gNB) can also select the AMF based on other conditions. The 5G AN (or gNB) extracts the registration request message from the received RRC message and transmits the registration request message to the selected new AMF (S604). It should be noted that if at least one of the first to second identification information is included in the RRC message but not in the registration request message, the identification information included in the RRC message can be transmitted together with the registration request message to the selected AMF (S604).

[0196] The new AMF can perform a first condition check upon receiving a registration request message. The first condition check is used to determine whether the network (or the new AMF) accepts the UE's request. If the first condition check is true, the new AMF executes procedures S606 to S612. On the other hand, if the first condition check is false, the new AMF executes procedure S610 instead of procedures S606 to S608.

[0197] Alternatively, the new AMF can perform a first condition check after requesting the UE context from the old AMF and receiving the UE context from the old AMF (S606, S608). In this case, if the new AMF determines the first condition to be true, it executes S610 and S612. On the other hand, the new AMF can execute S610 if the first condition is false.

[0198] It should be noted that, in this case, if the first condition is true, the control message sent and received in S610 can be a registration accept message, and if the first condition is false, the control message sent and received in S610 can be a registration reject message.

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

[0200] For example, it is preferable that: if the network allows the UE's request, the first condition is determined to be true; if the network does not allow the UE's request, the first condition is determined to be false. Furthermore, it is preferable that: if the network and / or devices within the network of the UE's registration destination support the function requested by the UE, the first condition is determined to be true; if the network and / or devices within the network of the UE's registration destination do not support the function requested by the UE, the first condition is determined to be false. Moreover, it is preferable that: if the transmission and reception of identification information are permitted, the first condition is determined to be true; if the transmission and reception of identification information are not permitted, the first condition is determined to be false.

[0201] Furthermore, if the S-NSSAI included in the requested NSSAI received by the AMF from the UE identifies a slice requiring a specific network slice authentication and authorization process, and further if the AMF stores the result of the specific network slice authentication and authorization process corresponding to the UE's S-NSSAI as successful, then the first condition can be true. Alternatively, if the UE does not have an authorized S-NSSAI and there is no plan to allocate an authorized NSSAI to the UE in the future, then the first condition can be false.

[0202] Furthermore, if the S-NSSAI included in the NSSAI request received by the AMF from the UE identifies the slice managed by the maximum number of UEs required to connect to the slice, and further if the maximum number of UEs has not been reached, the first condition can be true. Alternatively, if it is expected that an allowed NSSAI can be assigned to the UE in the future, even if the UE does not have an allowed S-NSSAI, the first condition can be true.

[0203] In the case where the UE does not have an authorized S-NSSAI and the first NSSAI is assigned to the UE, the first condition can be either true or false.

[0204] If the new AMF differs from the AMF identified in the message received from the UE by the new AMF, procedures S606 and S608 are executed; if the new AMF is the same as the AMF identified in the message received from the UE by the new AMF, procedures S606 and S608 are not executed. In other words, if the AMF changes through this procedure, procedures S606 and S608 are executed; if the AMF does not change, procedures S606 and S608 are skipped.

[0205] The UE context transmission process (S606, S608) is described. The new AMF identifies the AMF shown in the AMF identification information as the old AMF and sends a UE context request message to the old AMF (S606). The old AMF sends the UE context to the new AMF based on the received UE context request message. The new AMF generates the UE context based on the received UE context.

[0206] Here, the UE context sent from the new AMF to the old AMF may include the UE ID and allowed NSSAIs. Furthermore, the UE context may include configured NSSAIs and / or rejected NSSAIs, NSSAIs and / or pending NSSAIs and / or first NSSAIs. Additionally, the allowed NSSAIs and / or configured NSSAIs and / or rejected NSSAIs and / or pending NSSAIs and / or first NSSAIs included in the UE context, as well as the S-NSSAIs included in each NSSAI, can be associated with information indicating whether the notification to the UE is complete.

[0207] In addition, the UE context may also include S-NSSAI information that requires a specific network slice authentication and authorization process and / or information indicating successful authentication and / or failed authentication for the UE to complete a specific network slice authentication and authorization process.

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

[0209] It should be noted that information related to these S-NSSAI characteristics can be managed as a single piece of information. Specifically, the network can associate and store information indicating whether NSAA is needed, whether NSAA is successful, whether the maximum number of UEs connected to the slice needs to be managed, and whether the maximum number of UEs connected to the slice has been reached for each S-NSSAI.

[0210] The new AMF sends a control message to the UE based on a first condition determination and / or based on receiving the UE context from the old AMF (S610). The control message can be either a registration acceptance message or a registration rejection message.

[0211] The new AMF can include one or more tenth identification information pieces in a control message for transmission. Alternatively, the new AMF can include at least one of the tenth to fifteenth identification information pieces in a control message for transmission. It should be noted that the AMF can use these identification information pieces and / or control messages to indicate network support for various functions, to indicate that a UE's request is accepted, to indicate that a request from the UE is not allowed, or to indicate a combination of these. Furthermore, when transmitting and receiving multiple identification information pieces, two or more of these identification information pieces can constitute one or more identification information pieces. It should be noted that information indicating support for various functions and information indicating requests for the use of various functions can be transmitted and received as the same identification information or as different identification information pieces.

[0212] The AMF may send at least one of the tenth to fifteenth identification information if it receives at least one of the first to second identification information from the UE and / or if there is an update to the UE's setting information since the last registration process.

[0213] When the AMF receives the first identification information and / or the second identification information from the UE, it includes at least one of the tenth to fifteenth identification information in the control message and sends it.

[0214] AMF can also include configured NSSAIs and / or allowed NSSAIs and / or denied NSSAIs and / or pending NSSAIs in the control message. It should be noted that the tenth to fifteenth identification information can be included in the allowed NSSAIs and / or denied NSSAIs and / or pending NSSAIs, or it can be sent as separate information.

[0215] AMF may include an empty value in the allowed NSSAI when the UE does not have an allowed S-NSSAI (allowed NSSAI) when the control message is sent, but there is a scheduled NSSAA procedure to be executed after this procedure is completed or in parallel with this procedure, or an NSSAA procedure is being executed between the UE and the network, or a pending NSSAI has been included in the control message to be sent.

[0216] AMF can include an empty value in the allowed NSSAI even if the UE does not have an allowed S-NSSAI (allowed NSSAI) when the control message is sent, but includes the tenth identification information in the control message, or if the first NSSAI is notified to the UE earlier than this procedure.

[0217] AMF can include the fifteenth identification information in the control message, provided that the thirteenth identification information, which is applicable to all PLMNs, is included in the control message.

[0218] The UE receives control messages and / or one or more of the tenth to fifteenth identification information from the network. More specifically, the UE receives control messages and / or one or more of the tenth to fifteenth identification information from the new AMF.

[0219] The UE can identify the received information based on the reception of at least one of the tenth to fifteenth identification information. Specifically, the UE can identify a state where the transmission of MM messages and / or SM messages related to the S-NSSAI mapped by the S-NSSAI shown in the tenth identification information and / or the fourteenth identification information and / or the fifteenth identification information is temporarily prohibited due to reaching the maximum number of UEs connected to each slice. It should be noted that, here, the MM procedure can be a registration request message, and the SM message can be a PDU session establishment request message.

[0220] The UE may receive control messages based on at least one of the tenth to fifteenth identification information and perform the following operations according to each tenth identification information.

[0221] The UE may include the S-NSSAI associated with the S-NSSAI shown in the tenth identification information and / or the S-NSSAI shown in the fourteenth identification information and / or the mapped S-NSSAI shown in the fifteenth identification information in the appropriate first NSSAI and store it. Specifically, the UE may append the received S-NSSAI shown in the fourteenth identification information to the first NSSAI associated with the information shown in the eleventh identification information and / or the thirteenth identification information.

[0222] Alternatively, the UE can append the S-NSSAI mapped as shown in the received fifteenth identification information to the first NSSAI, append the S-NSSAI related to the mapped S-NSSAI shown in the received fifteenth identification information to the first NSSAI corresponding to the current PLMN, append it to the first NSSAI corresponding to the current PLMN and the current access type, or append it to the first NSSAI(s) corresponding to the current PLMN and all access types.

[0223] Furthermore, if the S-NSSAI included in the first NSSAI stored by the UE is included in the UE storage and establishes a corresponding allowed NSSAI with the PLMN, access type and other access types requested by the UE in this process, the S-NSSAI can be deleted from the allowed NSSAI.

[0224] Furthermore, upon receiving the fifteenth identification information, the UE can store the S-NSSAI shown in the fifteenth identification information as a mapping of the S-NSSAI shown in the fourteenth identification information.

[0225] If the received thirteenth identification information is information applicable to all PLMNs, the UE may delete the S-NSSAI associated with the S-NSSAI mapped as shown in the fifteenth identification information from the allowed NSSAI corresponding to PLMNs other than the current PLMN.

[0226] The UE can identify the maximum number of UEs connected to each slice based on the reception of the tenth identification information and / or the eleventh identification information and / or the control message. Here, the S-NSSAI shown in the tenth identification information can be the S-NSSAI mapped from the fourteenth identification information and / or the fifteenth identification information.

[0227] The UE can receive and / or receive control messages based on at least one of the tenth to fifteenth identification information, and use the received backoff timer value to start counting or managing the backoff timer associated with the S-NSSAI. Here, the backoff timer value can be the timer value shown in the tenth and / or twelfth identification information, and the S-NSSAI can be the S-NSSAI mapped to the first and / or tenth and / or fourteenth identification information, and / or the S-NSSAI mapped to the fifteenth identification information.

[0228] While the backoff timer is in progress, the UE is prohibited from sending MM messages and SM messages related to the S-NSSAI corresponding to the backoff timer establishment, the S-NSSAI mapped to the backoff timer establishment, or the S-NSSAI mapped to the backoff timer establishment.

[0229] Furthermore, upon receiving the thirteenth identification information, the UE can adjust the backoff timer according to the effective range indicated by the thirteenth identification information.

[0230] Specifically, if the thirteenth identification information indicates information applicable to the current PLMN, the UE can adapt the backoff timer to the current PLMN. Specifically, the UE can stop counting or adjusting the backoff timer without a PLMN change, but constraints imposed by the backoff timer associated with the PLMN prior to the move can be lifted. In other words, in the event of a PLMN change, the UE maintains the backoff timer, but constraints on the PLMN prior to the move can be lifted.

[0231] Alternatively, the UE can also stop counting or setting backoff timers associated with the current PLMN when the PLMN changes. In other words, the UE can stop backoff timers when the PLMN changes, and restrictions on the PLMN before the move can also be lifted.

[0232] Alternatively, if the thirteenth identification information indicates applicability to all PLMNs, the UE can also adapt the backoff timer to all PLMNs. In other words, even if a PLMN change occurs, the UE can maintain the backoff timer without stopping. While the backoff timer is being executed, in the event of a PLMN change, the UE maintains a state that prohibits the use of the S-NSSAI associated with the mobile destination PLMN established by the mapping of the S-NSSAI corresponding to the backoff timer, or the S-NSSAI of the mobile destination PLMN associated with the mapped S-NSSAI, or the MM message and SM message of the mapped S-NSSAI.

[0233] Alternatively, if the thirteenth identification information indicates information adapted to the current registration area, the UE can adapt the backoff timer to the current registration area. In other words, as the UE leaves the registration area, the UE can stop the backoff timer counting or the backoff timer itself.

[0234] Furthermore, the UE can manage and / or store the first NSSAI associated with the eleventh identification information and / or the thirteenth identification information.

[0235] Here, with the stop or expiration of the backoff timer, the restriction is lifted, and the UE can transition to a state where it can send MM messages and SM messages that use the backoff timer to establish the corresponding S-NSSAI and / or the S-NSSAI mapped to the backoff timer. In other words, with the stop or expiration of the backoff timer, the UE can transition to a state where it can send MM messages that use the backoff timer-established S-NSSAI and / or the S-NSSAI mapped to the backoff timer as requested NSSAIs.

[0236] Furthermore, the UE can transition to a state capable of sending MM messages using the NSSAI associated with the backoff timer upon the stoppage or expiration of the backoff timer. In other words, the UE can transition to a state capable of sending MM messages using the NSSAI associated with the backoff timer as the requesting NSSAI upon the stoppage or expiration of the backoff timer.

[0237] Furthermore, with the termination or expiration of the backoff timer, the UE can delete the S-NSSAI corresponding to the backoff timer, or the S-NSSAI mapped to the backoff timer, or the S-NSSAI related to the S-NSSAI mapped to the backoff timer from the first NSSAI.

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

[0239] It should be noted that the AMF can select and determine which identification information from the tenth to the fifteenth identification information to include in the control message based on the received identification information and / or joiner information and / or network capability information and / or operator policies and / or network status and / or user registration information and / or the context maintained by the AMF.

[0240] Furthermore, when the control message is a registration acceptance message, AMF can either include an SM message (e.g., a PDU session establishment acceptance message) within the registration acceptance message or send the SM message (e.g., a PDU session establishment acceptance message) together with the registration acceptance message. This sending method can be performed when the SM message (e.g., a PDU session establishment request message) is included within the registration request message. Alternatively, this sending method can be performed when the SM message (e.g., a PDU session establishment request message) is sent together with the registration request message. AMF can indicate that the SM process has been accepted during the registration process by performing such sending methods.

[0241] In addition, based on the received identification information and / or joiner information and / or network capability information and / or operator policies and / or network status and / or user registration information and / or the context maintained by the AMF, the AMF can indicate that the UE's request has been accepted by sending a registration acceptance message, or that the UE's request has been rejected by sending a registration rejection message.

[0242] The UE receives a control message via 5G AN (gNB) (S608). When the control message is a registration acceptance message, the UE can identify that the UE's request implemented by the registration request message has been accepted, and the content 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 identify that the UE's request implemented by the registration request message has been rejected, and the content of various identification information included in the registration rejection message, by receiving the registration rejection message. Furthermore, the UE can identify that its request has been rejected even if a specified period has elapsed after sending the registration request message and no control message has been received.

[0243] The UE can further transmit the registration completion message as a response message to the registration acceptance message to the AMF via the 5G AN (gNB) when the control message is a registration acceptance message (S610). It should be noted that when the UE receives SM messages such as the PDU session establishment acceptance message, it can include the PDU session establishment completion message or other SM messages in the registration completion message, or it can include the SM message to indicate that the SM process is complete. Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but it is included in the RRC message for transmission and reception between the UE and the 5G AN (gNB).

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

[0245] Alternatively, each device can complete the registration process based on the sending and receiving of registration rejection messages.

[0246] It should be noted that each device can transition to or maintain a state where the UE is already registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission and reception of registration acceptance messages and / or registration completion messages. Alternatively, it can transition to or maintain a state where the UE is not currently registered in the network relative to the PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of registration rejection messages. Furthermore, transitions to different states can be based on the transmission and reception of registration completion messages or the completion of the registration process.

[0247] Furthermore, each device can perform processing based on the information sent and received during the registration process upon completion of the registration process. For example, the reason for the UE's request being rejected can be identified when information indicating that part of the UE's request has been rejected is sent and received. Moreover, each device can re-enact the process based on the reason for the UE's request being rejected, and can also perform the registration process for core network A or other cells.

[0248] Furthermore, based on the completion of the registration process, the UE can store the identification information received along with the registration acceptance message and / or registration rejection message, and can also identify the network.

[0249] Furthermore, each device can restart the registration process based on the expiration or termination of the backoff timer.

[0250] [4. Embodiments of the present invention]

[0251] The embodiments of this invention can be a combination of one or more of the processes described in the three sections. For example, in this embodiment described in the three sections, one or more mobile and periodic registration processes can be performed after the initial registration process is completed.

[0252] Specifically, after the initial registration process is completed, the UE can send an MM message or SM message using the S-NSSAI corresponding to the backoff timer, based on the expiration or termination of the backoff timer. It should be noted that one or more MM or SM processes can be executed before, after, or in parallel with the completion of the initial registration process.

[0253] [5. Variations]

[0254] The program that operates in the apparatus according to this invention can be a program that controls the Central Processing Unit (CPU) or similar device to enable the computer to perform its functions in order to realize the functions of the embodiments according to this invention. The program or the information processed by the program is temporarily stored in volatile memory such as Random Access Memory (RAM) or non-volatile memory such as flash memory, Hard Disk Drive (HDD) or other storage device systems.

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

[0256] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be installed or executed in a circuit, such as an integrated circuit or multiple integrated circuits. A circuit designed to perform the functions described in this specification 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 elements, discrete gate or transistor logic, discrete hardware parts, or a combination thereof. A general-purpose processor may be a microprocessor, or a processor, controller, microcontroller, or state machine of a conventional type. The aforementioned circuits may be constructed from digital circuits or analog circuits. Furthermore, in cases where advancements in semiconductor technology have led to the emergence of integrated circuit technologies that replace current integrated circuits, one or more embodiments of the present invention may also utilize new integrated circuits implemented using such technologies.

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

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

[0259] Explanation of reference numerals in the attached figures

[0260] 1. Mobile communication system

[0261] 10 UE_A

[0262] 30 PGW-U

[0263] 32 PGW-C

[0264] 35 SGW

[0265] 40 MME

[0266] 45 eNB

[0267] 50 HSS

[0268] 60 PCRF

[0269] 80 Access Network_A (E-UTRAN)

[0270] 90 Core Network_A

[0271] 120 Access Network_B (5G AN)

[0272] 122 gNB

[0273] 130 UPF

[0274] 132 SMF

[0275] 140 AMF

[0276] 150 UDM

[0277] 160 PCF

[0278] 190 Core Network_B

Claims

1. A user equipment (UE), characterized in that, The UE includes a transceiver unit, a control unit, and a storage unit. The transceiver sends a registration request message containing requested network slice selection assistance information (NSSAI), wherein the requested NSSAI includes first single network slice selection assistance information (S-NSSAI). Receive a registration acceptance message, the registration acceptance message containing the first S-NSSAI, a reason value indicating that the first S-NSSAI cannot be used, and the S-NSSAI mapped to the first S-NSSAI. When the reason value indicates that the first S-NSSAI cannot be used because the maximum number of UEs has been reached, The control unit, in the storage unit, appends the first S-NSSAI to the rejected NSSAI associated with the S-NSSAI that has reached the maximum number of UEs. If the reason value indicates that the first S-NSSAI is unavailable in the current public mobile network PLMN, then the first S-NSSAI is information unrelated to the access type.

2. A communication control method executed by a user equipment (UE), characterized in that, Send a registration request message containing requested Network Slice Selection Assistance Information (NSSAI), wherein the requested NSSAI includes a first Single Network Slice Selection Assistance Information (S-NSSAI). Receive a registration acceptance message, the registration acceptance message containing the first S-NSSAI, a reason value indicating that the first S-NSSAI cannot be used, and the S-NSSAI mapped to the first S-NSSAI. When the reason value indicates that the first S-NSSAI cannot be used because the maximum number of UEs has been reached, In the UE, the first S-NSSAI is appended to the rejected NSSAI associated with the S-NSSAI that has reached the maximum number of UEs. If the reason value indicates that the first S-NSSAI is unavailable in the current public mobile network PLMN, then the first S-NSSAI is information unrelated to the access type.

Images