User equipment, UE, and access and mobility management function, AMF

Abstract

The present invention clarifies an efficient control method relating to an unavailable period, UE behavior and network behavior associated with the unavailable period. When an unavailable period is stored, the UE deletes the stored unavailable period when the event ends.

Description

Technical Field

[0001] The present invention relates to UE (User Equipment) and AMF (Access and Mobility Management Function). Background Art

[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System) as the fifth generation (5G) mobile communication system was studied, and discussions were made to support new processes and new functions (see non-patent documents 1 to 3). In addition, as one of the research projects in Release 18, the use of unavailability periods (hereinafter also referred to as unavailability periods, uncommunicable periods, uncommunicable periods, and unusable periods) to control UE (User Equipment) and networks when events such as OS (Operating System) upgrades, security patch updates, modem resets, and modem software updates occur was studied (see non-patent document 4). Prior art literature Non-patent literature

[0003] Non-patent document 1: 3GPP TS23.501V17.5.0 (2022-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Systemarchitecture for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 2: 3GPP TS23.502V17.5.0 (2022-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 3: 3GPP TS24.501V17.6.1 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) Non-patent document 4: 3GPP TR 23.700-61V18.0.0(2022-06); 3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Study on Seamless UE context recovery (Release 18) Summary of the invention Problem that the invention aims to solve

[0004] Although Non-Patent Document 4 describes a portion of UE behavior and network behavior when the above-mentioned event occurs, efficient operation of the system as a whole cannot be achieved with just this description.

[0005] One solution of the present invention is completed in view of the above situation, and clarifies an efficient control method related to the unavailable period, and the UE behavior and network behavior associated with the unavailable period. Technical Solution

[0006] A UE according to one aspect of the present invention is a UE (User Equipment) having a control unit and a storage unit, wherein when an unavailable period is stored in the storage unit, the control unit deletes the unavailable period stored in the storage unit when an event ends.

[0007] In addition, an AMF of one scheme of the present invention is an AMF (Access and Mobility Management Function) having a control unit, a transceiver unit and a storage unit, and the AMF is characterized in that when the transceiver unit stores an unavailable period in the storage unit, when a login request message that does not include the unavailable period is received from the UE, the control unit deletes the unavailable period stored in the storage unit, and the transceiver unit sends a login acceptance message including a timer value that does not take into account the unavailable period, and entrusts the network exposure function NEF to delete the unavailable period. Beneficial Effects

[0008] According to one solution of the present invention, an efficient control method related to the unavailable period, and UE behavior and network behavior associated with the unavailable period can be clarified. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 This is a diagram illustrating the outline of a mobile communication system (EPS / 5GS). Figure 2 This is a diagram illustrating the detailed structure of the mobile communication system (EPS / 5GS). Figure 3 This is a diagram illustrating the device structure of UE. Figure 4 This is a diagram illustrating the structure of the access network device (gNB) in 5GS. Figure 5 This is a diagram that illustrates the structure of the core network device (AMF / SMF / UPF) in 5GS. Figure 6 This is a diagram for explaining the login process. DETAILED DESCRIPTION

[0010] Hereinafter, the best mode for implementing one aspect of the present invention will be described with reference to the drawings. It should be noted that in this embodiment, an embodiment of a mobile communication system in which one aspect of the present invention is applied will be described as an example. [1. System Overview]

[0011] first, Figure 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment. Figure 2 It is a diagram for explaining the detailed structure of the mobile communication system 1.

[0012] exist Figure 1 It is recorded that the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network: packet data network)_A5, access network_B120, core network_B190, and DN (Data Network: data network)_A6.

[0013] In the following, these devices / functions may be recorded with omitted symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0014] In addition, Figure 2The following devices / functions are recorded: UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170 and other devices / functions as well as interfaces connecting these devices / functions to each other.

[0015] In the following, for these devices / functions, symbols are sometimes omitted, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

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

[0017] UE is a device that can connect to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (non-3GPP access, also known as non-3GPP access network, non-3GPP AN). UE can be a terminal device such as a portable phone or a smart phone that can perform wireless communications, or it can be a terminal device that can connect to EPS and / or 5GS. UE can have a UICC (Universal Integrated Circuit Card) or an eUICC (EmbeddedUICC). It should be noted that UE is sometimes expressed as a user device or a terminal device.

[0018] In addition, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in E-UTRAN. It should be noted that, in the following, eNB45 is sometimes recorded by omitting the symbol like eNB. In addition, when there are multiple eNBs, each eNB is connected to each other, for example, via an X2 interface. In addition, one or more access points are configured in the wireless LAN access network.

[0019] In addition, access network_B corresponds to the 5G access network (5G AN). 5G AN is composed of NG-RAN (NG Radio Access Network: NG wireless access network) and / or non-3GPP access network. One or more gNB (NRNodeB: NR Node B) 122 are configured in NG-RAN. It should be noted that, in the following, the symbol gNB122 is sometimes omitted like gNB. gNB is a node that provides NR (New Radio: New Radio) user plane and control plane to UE, and is a node connected to 5GCN via an NG interface (including N2 interface or N3 interface). That is, gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) designed for EPS as a 4G system. In addition, when there are multiple gNBs, each gNB is connected to each other, for example, via an Xn interface.

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

[0021] In addition, below, E-UTRAN and NG-RAN are sometimes referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN are sometimes referred to as non-3GPP access. In addition, nodes configured in access network_B are sometimes collectively referred to as NG-RAN nodes.

[0022] In addition, below, access network_A, access network_B, and the devices included in access network_A and the devices included in access network_B are sometimes referred to as access networks or access devices or devices within access networks.

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

[0024] In addition, core network_B corresponds to 5GCN (5G Core Network). In 5GCN, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc. are configured. Here, 5GCN can be expressed as 5GC.

[0025] In addition, below, core network_A, core network_B, and the devices included in core network_A and the devices included in core network_B are sometimes referred to as core networks, core network devices, or devices within the core network.

[0026] The core network (core network_A and / or core network_B) can be an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator; MNO) that connects the access network (Access Network_A and / or Access Network_B) and PDN and / or DN, or it can be a core network used by a mobile communication operator that operates and manages the mobile communication system 1, or it can be a 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).

[0027] In addition, Figure 1The case where PDN and DN are the same is recorded in the specification, but they can also be different. PDN can be a DN (Data Network) that provides communication services to UE. It should be noted that DN can be constructed as a packet data service network or can be constructed for each service. Moreover, PDN can include connected communication terminals. Therefore, connection with PDN can be connection with communication terminals and server devices configured for PDN. Moreover, sending and receiving user data with PDN can be sending and receiving user data with communication terminals and server devices configured for PDN. It should be noted that PDN can be expressed as DN, and DN can be expressed as PDN.

[0028] In addition, hereinafter, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein are sometimes referred to as a network or a network device. That is, the network and / or network device sending and receiving messages and / or executing a process means that at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein send and receive messages and / or execute a process.

[0029] In addition, the UE can be connected to the access network. In addition, the UE can be connected to the core network via the access network. Moreover, the UE can be connected to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data between the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication can be used, but also non-IP communication can be used.

[0030] Here, IP communication refers to data communication using IP, in which data is sent and received through IP packets. An IP packet consists of an IP header and a payload portion. The payload portion may include data sent and received by devices / functions included in EPS and devices / functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, in which data is sent and received in a form different from the structure of IP packets. For example, non-IP communication may be data communication achieved by sending and receiving application data that is not assigned an IP header, or may be assigned other headers such as a MAC header, Ethernet (registered trademark) frame header, etc. to send and receive user data sent and received by the UE.

[0031] In addition, the access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may have a configuration not recorded in Figure 2For example, an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S) may be included in the core network_A and / or the core network_B.

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

[0033] In addition, the AAA server is a device that is directly connected to the AUSF or indirectly connected via other network devices and has authentication, authorization and billing functions. The AAA server can be a network device within the core network. It should be noted that the AAA server can be included in the PLMN but not included in the core network_A and / or core network_B. That is, the AAA server can be either a core network device or a device outside the core network. For example, the AAA server can be a server device within the PLMN managed by a third party (3rd Party).

[0034] It should be noted that in Figure 2 In the figure, for the sake of simplicity, each device / function is described as one, but multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150 may be configured in the mobile communication system 1. [2. Configuration of each device]

[0035] Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment is described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware configured on general hardware, or as software. In addition, at least part (including all) of the functions of each device can also be configured as physical hardware, logical hardware, or software.

[0036] It should be noted that the storage units (storage unit_A340, storage unit_B540, storage unit_B740) in each device and function that appear below are composed of, for example, semiconductor memories, SSDs (Solid State Drives), HDDs (Hard Disk Drives), etc. In addition, each storage unit can store not only the information originally set at the factory stage, but also various information sent and received between the device itself and devices / functions other than the function (such as UEs and / or access network devices and / or core network devices and / or PDNs and / or DNs). In addition, each storage unit can store identification information, control information, flags, parameters, etc. included in the control messages sent and received in various communication processes described later. In addition, each storage unit can also store this information for each UE. In addition, each storage unit can store control messages and user data sent and received between the devices / functions included in the 5GS and / or EPS when intercommunication between the 5GS and the EPS is performed. At this time, not only data sent and received via the N26 interface can be stored, but also data not sent and received via the N26 interface can be stored. [2.1. UE device configuration]

[0037] First, use Figure 3 An example of the configuration of a UE (User Equipment) is described. The UE is composed of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, the transceiver_A320, and the storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.

[0038] The control unit_A300 is a functional unit that controls the overall actions 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.

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

[0040] Reference Figure 2To explain in detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver_A320. In addition, the UE can communicate with the base station device (gNB) in the 5G AN by using the transceiver_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum: non-access layer) messages with the AMF via the N1 interface by using the transceiver_A320. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN.

[0041] The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for each action of the UE. In addition, the storage unit_340 may have a function of storing control information sent and received between the access network device, the core network device, and the DN. [2.2.gNB device configuration]

[0042] Next, use Figure 4 The following describes an example of the gNB device configuration. The gNB is composed 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, the network connection unit_B520, the transceiver unit_B530, and the storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0043] The control unit_B500 is a functional unit that controls the overall actions 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 in the gNB.

[0044] The network connection unit_B520 is a functional unit for gNB to communicate with 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 between the AMF and / or UPF.

[0045] The transceiver_B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can use the transceiver_B530 to send and receive user data and / or control information between the UE.

[0046] Reference Figure 2 To explain in detail, the gNB in ​​the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. In addition, the gNB can communicate with the UE by using the transceiver unit_B530.

[0047] Storage unit_B540 is a functional unit for storing programs, user data, control information, etc. required for various actions of gNB. In addition, storage unit_540 can have the function of storing control information sent and received between UE, other access network devices (base station devices), core network devices, and DN. [2.3. Device structure of AMF]

[0048] Next, use Figure 5 The following describes an example of the device configuration of AMF. AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. AMF can be a node that operates a control plane.

[0049] The control unit_B700 is a functional unit that controls the entire 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 in the AMF.

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

[0051] Reference Figure 2 To explain in detail, the AMF in 5GCN can communicate with gNB via the N2 interface, can communicate with UDM via the N8 interface, can communicate with SMF via the N11 interface, and can communicate with PCF via the N15 interface by using the network connection unit_A620. In addition, the AMF can send and receive NAS messages with the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN. In addition, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface by using the network connection unit A620.

[0052] The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each action of the AMF. In addition, the storage unit_740 may have the function of storing control information sent and received between the UE, the access network device, other core network devices, and the DN.

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

[0054] In addition, the RM state of each UE is managed in the login management. The RM state can be synchronized between the UE and the AMF. As the RM state, there are a non-logged-in state (RM-DEREGISTERED state) and a logged-in state (RM-REGISTERED state). In the RM-DEREGISTERED state, since the UE has not logged in to the network, the UE context in the AMF does not have valid location information and routing information for the UE, so the AMF is in a state where the UE cannot be reached. In addition, in the RM-REGISTERED state, the UE has logged in to the network, so the UE can receive services that require login to the network. It should be noted that the RM state can be expressed as a 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state can be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state can be expressed as a 5GMM-REGISTERED state.

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

[0056] Moreover, 5GMM-DEREGISTERED can be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network cannot reach UE_A10. It should be noted that when each device is 5GMM-DEREGISTERED, UE_A10 can start the login process or establish a 5GMM context by executing the login process.

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

[0058] Moreover, in connection management, it can also be divided into CM state in 3GPP access and CM state in non-3GPP access for management. In this case, as the CM state in 3GPP access, there can be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over3GPP access). Moreover, as the CM state in non-3GPP access, there can be a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTEDstate over non-3GPP access). It should be noted that the non-connected state can be expressed as an idle mode, and the connected state mode can be expressed as a connected mode.

[0059] It should be noted that the CM state can also be expressed as 5GMM mode. In this case, the non-connected state can also be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state can also be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Moreover, the non-connected state in 3GPP access can also be expressed as 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access can also be expressed as 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Moreover, the non-connected state in non-3GPP access can also be expressed as 5GMM non-connected mode in non-3GPP access (5GMM-IDLE modeover non-3GPP access), and the connected state in non-3GPP access can also be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). It should be noted that the 5GMM non-connected mode can be expressed as an idle mode, and the 5GMM connected mode can be expressed as a connected mode.

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

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

[0062] Next, use Figure 5 An example of the device configuration of SMF is described. SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. SMF can be a node that operates a control plane.

[0063] The control unit_B700 is a functional unit that controls the entire 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 in the SMF.

[0064] The network connection unit_B720 is a functional unit for connecting the SMF 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 between the AMF and / or UPF and / or PCF and / or UDM and / or NSACF.

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

[0066] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of SMF.

[0067] SMF has the following functions: session management functions such as establishment, modification, and release of PDU sessions, 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 the SM part of NAS messages, functions for notifying that downlink data has arrived (Downlink Data Notification), functions for providing AN-specific (each AN's) SM information sent to AN via AMF and through the N2 interface, functions for determining the SSC mode (Session and Service Continuity mode) for the session, roaming functions, etc.

[0068] In addition, the storage unit 740 may have the function of storing control information sent and received between the UE, access network devices, other core network devices, and DN. [2.5. UPF device configuration]

[0069] Next, use Figure 5 The following describes an example of the device configuration of the UPF. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The UPF may be a node that operates the control plane.

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

[0071] 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 in 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 the base station device (gNB) and / or SMF and / or DN in the 5G AN.

[0072] Reference Figure 2 To explain in detail, the UPF in 5GCN can communicate with gNB via the N3 interface, communicate with SMF via the N4 interface, communicate with DN via the N6 interface, and communicate with other UPFs via the N9 interface by using the network connection unit _A620.

[0073] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of UPF.

[0074] 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 interconnecting with DN (that is, serving as a gateway between DN and core network_B to transmit user data), routing and transmission of packets, UL CL (Uplink Classifier) ​​function that supports routing of multiple service flows for one DN, branching point function that supports multi-homed PDU sessions, QoS (Quality of Service) processing function for user plane, verification function of uplink services, triggering buffering of downlink packets, downlink data notification function, etc.

[0075] In addition, UPF can be a gateway for IP communication and / or non-IP communication. In addition, UPF can have the function of transmitting IP communication and can also have the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways can be gateways connecting the core network_B with a single DN. It should be noted that UPF can have connectivity with other NFs and can also be connected to each device via other NFs.

[0076] In addition, the storage unit 740 may have the function of storing control information sent and received between the UE, access network devices, other core network devices, and DN.

[0077] It should be noted that the user plane (user plane; also called UP) is user data (user data) sent and received between the UE and the network. The user plane can use the PDN connection in the case of 4G or the PDU session in the case of 5G for transmission and reception. Moreover, in the case of EPS, the user plane can also use the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface for transmission and reception. Moreover, in the case of 5GS, the user plane can also be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. In the following, the user plane may also be expressed as U-Plane.

[0078] Moreover, the control plane (also referred to as CP) is a control message sent and received for communication control of UE, etc. The control plane can use the NAS (Non-Access-Stratum) signaling connection between UE and MME for transmission and reception. The control plane can use the NAS (Non-Access-Stratum) signaling connection between UE and AMF for transmission and reception. Moreover, in the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for transmission and reception. Moreover, in the case of 5GS, the control plane can also use the interface between UE and NG RAN and the N2 interface for transmission and reception. In the following, the control plane can be expressed as Control Plane or C-Plane.

[0079] Furthermore, the user plane (U-Plane, User Plane; UP) may be a communication path for sending and receiving user data, and may be composed of multiple bearers. Furthermore, the control plane (C-Plane, Control Plane; CP) may be a communication path for sending and receiving control messages, and may be composed of multiple bearers. [2.6. Description of other devices and / or functions and identification information of this embodiment]

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

[0081] The network refers to at least a part of the access network_B, the core network_B, and the DN. In addition, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may also be referred to as a network or a network device. That is, the network executing the sending, receiving, and / or processing of messages may mean that a device (network device and / or control device) in the network executes the sending, receiving, and / or processing of messages. Conversely, the device in the network executing the sending, receiving, and / or processing of messages may mean that the network executes the sending, receiving, and / or processing of messages.

[0082] In addition, NSSF (Network Slice Selection Function) can refer to a network function (also called NF) that has the function of selecting a network slice to serve the UE.

[0083] Furthermore, NWDAF (Network Data Analytics Function) may refer to a NF having a function of collecting data according to an NF or an application function (also referred to as AF).

[0084] Furthermore, PCF (Policy Control Function) may refer to an NF having a function of determining a policy for controlling the behavior of a network.

[0085] Furthermore, NRF (Network Repository Function) may refer to an NF having a service discovery function. NRF may be an NF having a function of providing information of a discovered NF when receiving a discovery request of another NF from a certain NF.

[0086] In addition, NSACF (Network Slice Admission Control Function) may have the function of monitoring and controlling the number of logged-in UEs for each NS and / or the number of PDU sessions for each NS for a network slice (NS) associated with NSAC (Network Slice Admission Control). In addition, NSACF may be set for each NS associated with NSAC using the maximum number of UEs allowed for each NS and / or the maximum number of PDU sessions for each NS. In addition, NSACF may also have the function of increasing or decreasing the number of UEs logged into a certain NS in a manner that does not exceed the maximum number of UEs allowed to log into a certain NS. In addition, NSACF may also maintain a list of UE IDs logged into the NS associated with NSAC. In addition, in the case where the number of UEs logged into the NS increases (for example, in the case where a certain UE has newly sent a login request message to the NS), NSACF may have the following function: confirm whether the ID of the UE is included in the list of UE IDs logged into the NS, and in the case where the ID of the UE is not included in the list, further confirm whether the maximum number of UEs per NS is reached for the NS. In addition, during the login process and / or non-login process and / or NSSAA process, etc., in the case where the registration status of the UE of the NS associated with the NSAC changes, the AMF may make a request to the NSACF regarding the maximum number of UEs per NS. In addition, the NSACF may also have the function of increasing or decreasing the number of PDU sessions for a certain NS in a manner not exceeding the maximum number of PDU sessions allowed by the NS. In addition, in the case where the number of PDU sessions using the NS increases (for example, when a UE sends a PDU session establishment request message for the NS), the NSACF may have the function of confirming whether the maximum number of UEs per NS has been reached for the NS. In addition, the SMF may make a request to the NSACF regarding the maximum number of PDU sessions per NS during the PDU session establishment process and / or the PDU session release process.

[0087] In addition, the SM (session management) message (also called NAS (Non-Access-Stratum) SM message) can be a NAS message used in the process of SM, or a control message sent and received between UE_A10 and SMF_A230 via AMF_A240. Moreover, the SM message can include: PDU session establishment request message, PDU session establishment accept message, PDU session rejection message, PDU session change request message, PDU session change command message, PDU session change complete message, PDU session change command rejection message, PDU session change rejection message, PDU session release request message, PDU session release rejection message, PDU session release command message, PDU session release complete message, etc.

[0088] In addition, the SM process (also called the process for SM) may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each process may be initiated by the UE or by the NW.

[0089] In addition, the MM (Mobility management) message (also called NAS MM message) can be a NAS message used for the MM process, or a control message sent and received between UE_A10 and AMF_A240. Moreover, the MM message can include: a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc.

[0090] In addition, the MM process (also known as the process used for MM) may include: registration procedure, de-registration procedure (De-registration procedure, also known as non-registration procedure), generic UE configuration update procedure, authentication, authorization procedure, service request procedure, paging procedure, and notification procedure.

[0091] In addition, 5GS (5G System) services may be connection services provided using the core network B190. Furthermore, 5GS services may be services different from EPS services or services similar to EPS services.

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

[0093] In addition, the PDN (Packet Data Network) type indicates the type of PDN connection, which includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. When non-IP is specified, it indicates that communication is performed not only by communication using IP, but also by communication methods other than IP.

[0094] In addition, a PDU (Protocol Data Unit) session can be defined as an association between a DN and a UE that provides a PDU connectivity service, but can also be a connectivity established between a UE and an external gateway. The UE establishes a PDU session via the access network_B and the core network_B in the 5GS, thereby enabling the use of the PDU session to send and receive user data with the DN. Here, the external gateway may refer to a UPF, a SCEF, etc. The UE can use the PDU session to send and receive user data with a device such as an application server configured in the DN.

[0095] Furthermore, an MA PDU session may refer to a PDU session that provides a PDU connectivity service using a 3GPP access and / or a non-3GPP access.

[0096] It should be noted that each device (UE and / or access network device and / or core network device) can also establish a correspondence between one or more identification information and the PDU session for management. It should be noted that these identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information and access network identification information, and may further include other information. Moreover, in the case of establishing multiple PDU sessions, the identification information corresponding to the PDU session establishment may be the same content or different content.

[0097] In addition, DNN (Data Network Name) can be identification information for identifying a core network and / or an external network such as a DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 to which the core network B190 is connected. Furthermore, DNN can also be equivalent to APN (Access Point Name).

[0098] In addition, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it means that IPv4 is used to send and receive data. When IPv6 is specified, it means that IPv6 is used to send and receive data. When Ethernet is specified, it means that Ethernet frames are sent and received. In addition, Ethernet can indicate that communication without using IP is performed. When Unstructured is specified, it means that Point-to-Point (P2P) tunnel technology is used to send and receive data to an application server located in the DN. As a P2P tunnel technology, for example, UDP / IP encapsulation technology can also be used. It should be noted that in addition to the above, IP can also be included in the PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0099] In addition, PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator as a communication operator, and the operator can be identified by the PLMN ID. The PLMN that is consistent with the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) can be a home PLMN (Home PLMN: HPLMN). Moreover, the UE can maintain an equivalent HPLMN list (Equivalent HPLMN list) for identifying one or more EHPLMNs (Equivalent HPLMN) in the USIM (Universal Subscriber Identity Module). A PLMN different from the HPLMN and / or EPLMN can be a VPLMN (Visited PLMN). The PLMN to which the UE successfully logs in can be an RPLMN (Registered PLMN; also called a logged-in PLMN). It should be noted that the services provided by PLMN can be read as PLMN services, and the services provided by SNPN can be read as SNPN services.

[0100] In addition, a network slice (NS) refers to a logical network that provides specific network capabilities and network characteristics. UE and / or network can support network slicing (NW slicing; NS) in 5GS. Sometimes network slicing is also referred to as slicing.

[0101] In addition, a network slice instance (NSI) refers to a network slice formed and configured by a collection of instances (entities) of network functions (NFs) and required resources. Here, NF refers to a processing function in a network, which is adopted or defined in 3GPP. NSI is an entity that constitutes one or more NSs in the core network_B. In addition, NSI can be composed of a virtual NF (Network Function) generated using NST (Network Slice Template). Here, NST refers to a logical expression of one or more NFs associated with a resource request for providing the requested communication service and capability. That is, NSI may refer to an aggregate within the core network_B190 composed of multiple NFs. In addition, NSI may be a logical network configured to divide the user data sent according to services, etc. More than one NF may be configured in the NS. The NF configured in the NS may be a device shared with other NSs, or may not be a device shared with other NSs. The UE and / or the device in the network can be assigned to one or more NSs based on the login information such as NSSAI and / or S-NSSAI and / or UE usage type (UE usage type) and / or one or more NSI IDs and / or APN. It should be noted that the UE usage type is a parameter value included in the login information of the UE for identifying the NSI. The UE usage type can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usage type.

[0102] In addition, S-NSSAI (Single Network Slice Selection Assistance information) is information for identifying NS. S-NSSAI can be composed of SST (Slice / Servicetype) only, or it can be composed of SST and SD (Slice Differentiator). Here, SST refers to information indicating the expected actions of NS in terms of functions and services. In addition, SD can be information that interpolates SST when selecting an NSI from multiple NSIs shown in SST. S-NSSAI can be information specific to each PLMN, or it can be standard information common among PLMNs. In addition, the network can store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, the network can provide NS related to the UE when the UE does not send a valid S-NSSAI to the network in the login request message.

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

[0104] In addition, configured NSSAI (also called Configured NSSAI) is NSSAI that can be applied to more than one PLMN or SNPN, and is NSSAI provided to the UE for storage. The UE can store the configured NSSAI for each PLMN, and can also store the configured NSSAI for each NPN (hereinafter, SNPN and / or PNI-NPN are sometimes collectively expressed as NPN). In addition, the configured NSSAI may be information set by the network (PLMN or SNPN). In addition, the S-NSSAI included in the configured NSSAI may be expressed as configured S-NSSAI (configured S-NSSAI). In addition, the configured S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI (mapped S-NSSAI). In addition, the configured NSSAI may include a configured NSSAI stored in the UE and a configured NSSAI sent from the network to the UE.

[0105] In addition, the requested NSSAI (requested NSSAI, also called Requested NSSAI) is the NSSAI provided from the UE to the network (current PLMN (also called serving PLMN, current PLMN) or NPN (also called servingNPN, current NPN)) during the login process. The S-NSSAI included in the requested NSSAI may be an S-NSSAI selected from one or more S-NSSAIs included in the set NSSAI and / or allowed NSSAI (allowed NSSAI) that have established a corresponding connection with the current PLMN or NPN. In addition, the S-NSSAI included in the requested NSSAI may be an S-NSSAI selected in a manner that does not include one or more S-NSSAIs included in the pending NSSAI (pendingNSSAI) and / or rejected NSSAI (rejected NSSAI). In addition, the requested NSSAI may be information indicating a network slice that the UE wants to log in to or access. In addition, the S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. In addition, the request NSSAI may be included in a NAS message such as a login request message sent from the UE to the network (PLMN or SNPN) and / or an RRC (Radio Resource Control) message including a NAS (Non-Access-Stratum) message. In addition, the request NSSAI may include the request NSSAI stored in the UE and the request NSSAI sent from the UE to the network (PLMN or SNPN).

[0106] In addition, allowed NSSAI (Allowed NSSAI, also known as Allowed NSSAI) is information indicating one or more network slices that the UE is allowed to connect to. In other words, allowed NSSAI may be information identifying a network slice that allows the network to connect to the UE. In addition, allowed NSSAI may be information indicating one or more S-NSSAI that can be used in the current PLMN or SNPN in the current login area. The UE and the network store and manage allowed NSSAI for each access (3GPP access or non-3GPP access) as information of the UE, respectively. The S-NSSAI included in the allowed NSSAI may be expressed as allowed S-NSSAI (allowed S-NSSAI). Allowed S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI. In addition, the allowed NSSAI may include allowed NSSAI stored in the UE and allowed NSSAI sent from the network to the UE.

[0107] In addition, mapped S-NSSAI (mapped S-NSSAI, also called Mapped S-NSSAI) can be the S-NSSAI of the HPLMN mapped to the S-NSSAI of the logged-in PLMN in a roaming scenario. In addition, the mapped S-NSSAI can be the S-NSSAI basically used when the UE is roaming, or it can be the S-NSSAI that is not used when the UE is not roaming (also called non-roaming). In addition, the UE can store a mapped S-NSSAI mapped to one or more set NSSAIs and the S-NSSAI included in the allowed NSSAI of each access type. In addition, the UE may also store a mapped S-NSSAI included in one or more rejected NSSAIs or a mapped S-NSSAI corresponding to the S-NSSAI included in the rejected NSSAI. In addition, the mapped NSSAI (mapped NSSAI) may include a mapped NSSAI stored in the UE and a mapped NSSAI sent from the network to the UE.

[0108] In addition, rejected NSSAI (rejected NSSAI, also referred to as Rejected NSSAI) is information indicating one or more network slices that are not allowed for the UE. In other words, rejected NSSAI is information identifying a network slice that does not allow the network to connect to the UE. Rejected NSSAI may be information including a combination of one or more S-NSSAI and a rejection reason value (hereinafter also referred to as reason value, rejection reason). Here, the rejection reason value refers to information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network may appropriately store and manage rejected NSSAI based on establishing corresponding rejection reason values ​​for each S-NSSAI. Moreover, rejected NSSAI may also be included in a NAS message sent from the network to the UE, such as a login acceptance message, a setting update command, a login rejection message, or an RRC message including a NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as rejected S-NSSAI. Here, rejected NSSAI may mean any one of the first to fourth rejected NSSAIs. In addition, rejected S-NSSAI may also mean rejected S-NSSAI included in any one of the first to fourth rejected NSSAIs. The reject NSSAI may be any one of the first to fourth reject NSSAIs and pending NSSAI, or a combination thereof. The S-NSSAI included in the reject NSSAI may be expressed as reject S-NSSAI. The reject S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI.

[0109] Here, the first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN. In other words, the first rejected NSSAI may be an NSSAI that is not available in the current PLMN or SNPN. In addition, the first rejected NSSAI may also be a set of one or more S-NSSAIs that are not available in the current PLMN or SNPN in the S-NSSAI included in the rejected NSSAI by the UE. The first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN of 5GS. In addition, the first rejected S-NSSAI may be a rejected S-NSSAI for the current PLMN or SNPN, or may be an S-NSSAI included in the rejected NSSAI for the current PLMN or SNPN. In addition, the first rejected NSSAI may be a rejected NSSAI stored by the UE and / or NW, or may be a rejected NSSAI sent from the NW to the UE. In the case where the first rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the first rejection NSSAI may be information including a combination of one or more S-NSSAIs and a reason value. The rejection reason value may mean "S-NSSAI not available in the current PLMN or SNPN", or it may mean that the S-NSSAI corresponding to the rejection reason value is not available in the current PLMN or SNPN.

[0110] In addition, the first rejection NSSAI may be valid in the entire registered PLMN or registered SNPN. In other words, the UE and / or NW may regard the first rejection NSSAI and the S-NSSAI included in the first rejection NSSAI as information that is independent of the access type. That is, the first rejection NSSAI may be information that is valid for 3GPP access (3GPP access) and non-3GPP access (non-3GPP access).

[0111] The UE can delete the first rejection NSSAI from the storage when the current PLMN or SNPN is transitioned to a non-logged state in both 3GPP access and non-3GPP access. In other words, when the UE transitions to a non-logged state for the current PLMN or SNPN via a certain access, or successfully logs in to a new PLMN or SNPN via a certain access, or fails to log in to a new PLMN via a certain access and transitions to a non-logged state, and when the UE is in a state (non-logged state) without being logged in through the access of the other party, the UE can delete the first rejection NSSAI.

[0112] In addition, the S-NSSAI included in the first rejected NSSAI in the storage unit of the UE may be considered unavailable in the entire current PLMN or SNPN. That is, the UE may be in a state where the MM process and / or SM process using the S-NSSAI is prohibited in the entire current PLMN or SNPN.

[0113] In addition, the second rejected NSSAI may be a rejected NSSAI for the current login area (also referred to as the registration area). In other words, the second rejected NSSAI may be an NSSAI that is not available in the current login area. In addition, the second rejected NSSAI may also be a set of one or more S-NSSAIs that are not available in the current login area as the S-NSSAI included in the request NSSAI by the UE. In addition, the second rejected NSSAI may also be a rejected NSSAI for the current login area of ​​5GS (rejected NSSAI for the current registration area). In addition, the second rejected NSSAI may also be a rejected NSSAI stored by the UE and / or NW, or a rejected NSSAI sent from the NW to the UE. In the case where the second rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the second rejected NSSAI may be information including a combination of one or more S-NSSAIs and a reason value. The reason value may mean "S-NSSAI not available in the current registration area", or it may mean that the S-NSSAI corresponding to the reason value is not available in the current registration area.

[0114] In addition, the second rejection NSSAI may be valid within the current login area. That is, the UE and / or NW may regard the second rejection NSSAI and the S-NSSAI included in the second rejection NSSAI as information for each access type. That is, the second rejection NSSAI may be information valid for 3GPP access or non-3GPP access, respectively. That is, the UE may delete the second rejection NSSAI from the storage once it becomes a non-logged state for a certain access.

[0115] In addition, the S-NSSAI included in the second rejected NSSAI in the storage unit of the UE may be considered unavailable in the current login area. That is, the UE may be in a state where the MM process and / or SM process using the S-NSSAI is prohibited in the entire current login area.

[0116] In addition, the third reject NSSAI is an S-NSSAI that requires NSSAA, and is a set of one or more S-NSSAIs for which NSSAA fails or is canceled for the S-NSSAI. The third reject NSSAI can be an NSSAI stored by the UE and / or NW, or it can be sent from the NW to the UE. In the case where the third reject NSSAI is sent from the NW to the UE, the third reject 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 is not available due to the failed or revoked network slice-specific authorization and authentication" or information indicating the failure or cancellation of NSSAI for the S-NSSAI corresponding to the rejection reason value.

[0117] In addition, the third rejection NSSAI is valid throughout the logged-in PLMN. In other words, the UE and / or NW may regard the third rejection NSSAI and the S-NSSAI included in the third rejection NSSAI as information that is independent of the access type. That is, the third rejection NSSAI may be information that is valid for 3GPP access and non-3GPP access. The third rejection NSSAI may be an NSSAI different from the rejection NSSAI. The third rejection NSSAI may also be the first rejection NSSAI.

[0118] The third rejection NSSAI is a rejection NSSAI for the UE to identify the slices rejected by the core network due to NSSAA failure or cancellation. Specifically, the UE does not start the login request process for the S-NSSAI included in the third rejection NSSAI while storing the third rejection NSSAI. The third rejection NSSAI may be identification information including one or more S-NSSAIs received from the core network corresponding to the rejection reason value indicating the failure of NSSAA. The third rejection NSSAI is information that does not depend on the access type. Specifically, when the UE stores the third rejection NSSAI, the UE may not attempt to send a login request message including the S-NSSAI included in the third rejection NSSAI to both 3GPP access and non-3GPP access. Alternatively, the UE can send a login request message including the S-NSSAI included in the third rejection NSSAI based on the UE policy. Alternatively, the UE can delete the third rejection NSSAI based on the UE policy and transform into a state in which a login request message including the S-NSSAI included in the third rejection NSSAI can be sent. In other words, in the case where the UE sends a login request message including the S-NSSAI included in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI.

[0119] In addition, the S-NSSAI included in the third rejected NSSAI in the storage unit of the UE may be considered unavailable in the entire current PLMN or SNPN. That is, the UE may be in a state where the MM process and / or SM process using the S-NSSAI is prohibited in the entire current login area.

[0120] In addition, the fourth rejected NSSAI may be a rejected NSSAI for the current tracking area. In other words, the fourth rejected NSSAI may be an NSSAI that is not available in the current tracking area.

[0121] In addition, the fourth rejected NSSAI may be a rejected NSSAI for the current tracking area in the current registration area. In other words, the fourth rejected NSSAI may be an NSSAI that is not available in the current tracking area in the current registration area.

[0122] In addition, the fourth rejected NSSAI may be an NSSAI that is not available in the current tracking area in the current login area, and may be an NSSAI that is available in other tracking areas in the current login area.

[0123] In addition, the fourth rejected NSSAI may be an NSSAI that is not available in the current tracking area in the current login area, or an NSSAI that is not available in other tracking areas in the current login area or other login areas (different from the current login area).

[0124] In addition, the fourth rejected NSSAI may also be a set of S-NSSAIs included by the UE in the requested NSSAI, which is a set of S-NSSAIs sent by the AMF using an S-NSSAI that is not available in the current tracking area or a rejection reason indicating that the S-NSSAI is not available in the current tracking area.

[0125] In addition, in a roaming scenario (in roaming), the fourth rejected NSSAI may include more than one S-NSSAI for the current PLMN, and may also include a set of mapped S-NSSAIs if available.

[0126] In addition, the fourth rejection NSSAI may also be a rejection NSSAI stored by the UE and / or the NW, or a rejection NSSAI sent from the NW to the UE. In the case where the fourth rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the fourth rejection NSSAI may be information including a combination of one or more S-NSSAIs and a reason value. The reason value may be the twelfth identification information.

[0127] In addition, the fourth rejected NSSAI may be valid for 3GPP access and non-3GPP access. In other words, the UE and / or NW may regard the fourth rejected NSSAI as independent of the access type, or may regard the fourth rejected NSSAI as dependent on the access type. In further other words, the UE and / or NW may manage and / or store the fourth rejected NSSAI per access type, or may not manage and / or store the fourth rejected NSSAI per access type.

[0128] Here, the fourth rejection NSSAI is independent of the access type, for example, it may mean that when the UE receives the fourth rejection NSSAI via 3GPP access, the fourth rejection NSSAI or the S-NSSAI included in the fourth rejection NSSAI cannot be utilized via 3GPP access or non-3GPP access. Similarly, it may also mean that when the UE receives the fourth rejection NSSAI via non-3GPP access, the fourth rejection NSSAI or the S-NSSAI included in the fourth rejection NSSAI cannot be utilized via 3GPP access or non-3GPP access. It should be noted that when the fourth rejection NSSAI is independent of the access type, it is ideal that the UE and / or NW does not store the fourth rejection NSSAI according to each access type (that is, it is not stored separately according to each access type, but only the fourth rejection NSSAI is stored), but it is not limited to this.

[0129] In addition, the case where the fourth rejection NSSAI depends on the access type may, for example, mean that when the UE receives the fourth rejection NSSAI via 3GPP access, the fourth rejection NSSAI or the S-NSSAI included in the fourth rejection NSSAI cannot be used via 3GPP access, but it may not mean that it cannot be used via non-3GPP access. That is, it may mean that the fourth rejection NSSAI or the S-NSSAI included in the fourth rejection NSSAI is not restricted in the use of non-3GPP access. Similarly, it may also mean that when the UE receives the fourth rejection NSSAI via non-3GPP access, the fourth rejection NSSAI or the S-NSSAI included in the fourth rejection NSSAI cannot be used via non-3GPP access, but it may not mean that it cannot be used via 3GPP access. That is, it may mean that the fourth rejection NSSAI or the S-NSSAI included in the fourth rejection NSSAI is not restricted in the use of 3GPP access. It should be noted that when the fourth reject NSSAI depends on the access type, it is ideal that the UE and / or NW stores the fourth reject NSSAI according to each access type (that is, the fourth reject NSSAI is stored according to each access type), but it is not limited to this.

[0130] Alternatively, in the case where the UE does not have a valid login area and / or tracking area, the fourth rejection NSSAI may be applied to the login area and / or tracking area that receives the rejection NSSAI.

[0131] In addition, in the case where the current login area or the current tracking area in the current login area includes a TAI (Tracking Area Identity) belonging to a PLMN or SNPN different from the current PLMN or SNPN, and the PLMN or SNPN different from the current PLMN or SNPN is in an equivalent PLMN (equivalent PLMN) or equivalent SNPN (equivalent SNPN) relationship, the fourth rejection NSSAI can also be applied to these PLMNs or SNPNs in the current login area and / or the current tracking area. In other words, in the current login area or the current tracking area, the fourth rejection NSSAI can be applied not only to the current PLMN or SNPN, but also to the equivalent PLMN or equivalent SNPN.

[0132] In addition, in case the S-NSSAI included in the Request NSSAI by the UE is the fourth Reject NSSAI, the AMF may reject the Login Request message.

[0133] In addition, when the 5GS registration type indicates a mobile registration update, and the purpose of starting the login process is not to change the network slice to which the UE is currently logged in, and the UE is in the current login area or the current tracking area, the UE may not include a request for NSSAI in the login process.

[0134] In addition, the S-NSSAI included in the fourth denied NSSAI (also referred to as the fourth denied S-NSSAI) may also be associated with one or more tracking areas that cannot utilize the denied S-NSSAI (the fourth denied S-NSSAI).

[0135] In addition, the UE may exchange the stored setting NSSAI with the new setting NSSAI when a new setting NSSAI for the current PLMN or SNPN is provided. In this case, the UE may also delete the mapping S-NSSAI for the stored setting NSSAI and store the mapping S-NSSAI for the new setting NSSAI, and may also delete the stored fourth rejection NSSAI, and may also delete the S-NSSAI included in the mapping S-NSSAI for the new setting NSSAI for the current PLMN or SNPN from the mapping S-NSSAI for the stored fourth rejection NSSAI.

[0136] In addition, the UE may also delete the S-NSSAI included in the new allowed NSSAI from the stored fourth rejected NSSAI when receiving the new allowed NSSAI for the current PLMN or SNPN. In this case, the UE may also delete the S-NSSAI included in the mapping S-NSSAI for the new allowed NSSAI for the current PLMN or SNPN from the mapping S-NSSAI for the stored fourth rejected NSSAI.

[0137] In addition, when the UE receives the S-NSSAI (fourth rejection S-NSSAI) of the rejection NSSAI (fourth rejection NSSAI) included in the login acceptance message, the login rejection message, the non-login request message, or the setting update command message, it can store the received fourth rejection S-NSSAI in the UE in the rejection NSSAI and the mapping S-NSSAI for the rejection NSSAI based on the rejection reason, or it can store it in the fourth rejection NSSAI and the mapping S-NSSAI for the fourth rejection NSSAI.

[0138] Moreover, when the UE receives the S-NSSAI (fourth reject S-NSSAI) of the reject NSSAI (fourth reject NSSAI) included in the login acceptance message, the login rejection message, the non-login request message or the setting update command message, and the S-NSSAI is included in the reject NSSAI IE, the UE may also delete the S-NSSAI (fourth reject S-NSSAI) included in the fourth reject NSSAI associated with the same access type from the allowed NSSAI stored by the UE for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN.

[0139] Moreover, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) of a rejected NSSAI (fourth rejected NSSAI) included in a login acceptance message, a login rejection message, a non-login request message, or a setting update command message when not roaming, and the S-NSSAI is included in an extended rejected NSSAI IE (Extended rejected NSSAIIE), the S-NSSAI (fourth rejected S-NSSAI) included in the fourth rejected NSSAI associated with the same access type may also be deleted from the allowed NSSAI stored by the UE for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN.

[0140] Moreover, when the UE receives an S-NSSAI (fourth reject S-NSSAI) including a reject NSSAI (fourth reject NSSAI) included in a login acceptance message, a login rejection message, a non-login request message, or a setting update command message during roaming, and the S-NSSAI is included in an extended reject NSSAI IE, the S-NSSAI (fourth reject S-NSSAI) included in the fourth reject NSSAI associated with the same access type may also be deleted from the allowed NSSAI stored by the UE for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN.

[0141] Moreover, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) of a rejected NSSAI (fourth rejected NSSAI) included in a login acceptance message, a login rejection message, a non-login request message, or a setting update command message when not roaming, it may also delete the S-NSSAI included in the mapping S-NSSAI of the fourth rejected NSSAI associated with the same access type from the allowed NSSAI stored by the UE for the current PLMN or SNPN and its equivalent PLMN or equivalent SNPN.

[0142] Moreover, when the UE receives an S-NSSAI (fourth rejected S-NSSAI) including a rejected NSSAI (fourth rejected NSSAI) included in a login acceptance message, a login rejection message, a non-login request message, or a setting update command message during roaming, the UE may also delete the S-NSSAI included in the mapping S-NSSAI of the fourth rejected NSSAI associated with the same access type from the mapping S-NSSAI of the allowed NSSAI stored by the UE.

[0143] Moreover, when the UE receives the S-NSSAI (fourth reject S-NSSAI) of the reject NSSAI (fourth reject NSSAI) included in the login acceptance message, the login rejection message, the non-login request message or the setting update command message, and the S-NSSAI is included in the reject NSSAI IE, the UE may also delete the S-NSSAI (fourth reject S-NSSAI) included in the fourth reject NSSAI associated with the same access type from the pending NSSAI stored by the UE for the current PLMN or SNPN and its equivalent PLMN or SNPN.

[0144] Moreover, when the UE receives an S-NSSAI (fourth reject S-NSSAI) including a reject NSSAI (fourth reject NSSAI) included in a login acceptance message, a login rejection message, a non-login request message, or a setting update command message when not roaming, and the S-NSSAI is included in an extended reject NSSAI IE, the S-NSSAI (fourth reject S-NSSAI) included in the fourth reject NSSAI associated with the same access type may also be deleted from the pending NSSAI stored by the UE for the current PLMN or SNPN and its equivalent PLMN or SNPN.

[0145] Moreover, when the UE receives an S-NSSAI (fourth reject S-NSSAI) including a reject NSSAI (fourth reject NSSAI) included in a login acceptance message, a login rejection message, a non-login request message, or a setting update command message when not roaming, and the S-NSSAI is included in the extended reject NSSAI IE, the S-NSSAI included in the mapped S-NSSAI of the fourth reject NSSAI associated with the same access type may also be deleted from the pending NSSAI stored by the UE for the current PLMN or SNPN and its equivalent PLMN or SNPN.

[0146] Moreover, when the UE receives an S-NSSAI (fourth reject S-NSSAI) including a reject NSSAI (fourth reject NSSAI) included in a login acceptance message, a login rejection message, a non-login request message, or a setting update command message during roaming, and the S-NSSAI is included in the extended reject NSSAI IE, the S-NSSAI included in the mapping S-NSSAI of the fourth reject NSSAI associated with the same access type may also be deleted from the mapping S-NSSAI of the pending NSSAI stored by the UE.

[0147] In addition, the UE may also delete the fourth rejected NSSAI and / or its access type stored by the UE when the login for access via receiving the fourth rejected NSSAI or the fourth rejected S-NSSAI is released, in other words, when the UE completes the non-login process via the access.

[0148] In addition, when the UE moves from a tracking area in which the fourth rejected NSSAI or the fourth rejected S-NSSAI is received to another tracking area, the UE may delete the fourth rejected NSSAI and / or its access type stored by the UE.

[0149] In addition, the UE may also delete the fourth rejected NSSAI and / or its access type stored by the UE when transitioning from the 5GMM-REGISTERED state to the 5GMM-DEREGISTERED state, or when transitioning from the 5GMM-DEREGISTERED state to the 5GMM-REGISTERED state.

[0150] In addition, the UE that receives the fourth rejection NSSAI included in the login acceptance message or the login rejection message or the setting update command message or the non-login request message may also perform an action based on the rejection reason of the rejection S-NSSAI (fourth rejection S-NSSAI) included in the fourth rejection NSSAI. Specifically, when the rejection reason included in the rejection S-NSSAI indicates "S-NSSAI not available in the current tracking area" and / or "S-NSSAI not available in the current tracking area in the current registration area" and / or "No network slices available", the UE may prohibit the use of the fourth S-NSSAI in the current tracking area. That is, the UE may be in a state where the MM process and / or SM process using the fourth S-NSSAI in the current tracking area is prohibited.

[0151] It should be noted that, when the power of the UE is cut off, the UE moves out of the current tracking area, the UICC including the USIM is removed from the UE, or the fourth rejected NSSAI or the fourth rejected S-NSSAI stored by the UE is deleted, the restriction can be lifted. That is, the UE can be in a state where the MM process and / or SM process using the fourth S-NSSAI can be performed in the current tracking area.

[0152] In addition, the UE may, when sending a login request message including a request NSSAI, select the S-NSSAI included in the request NSSAI from among the S-NSSAIs other than the S-NSSAI included in the stored fourth rejection NSSAI (fourth rejection S-NSSAI) and / or the S-NSSAI included in the mapped S-NSSAI for the fourth rejection NSSAI.

[0153] In addition, in the case where the UE sends a login request message including capability information indicating that NSSAA is not supported and requesting NSSAI, and the S-NSSAI included in the requesting NSSAI is the S-NSSAI associated with NSSAI, the AMF may send a login acceptance message including a rejection of NSSAI, wherein the rejection of NSSAI includes the S-NSSAI and a rejection reason indicating "S-NSSAI not available in the current tracking area" and / or "S-NSSAI not available in the current tracking area in the current registration area" and / or "No network slices available".

[0154] In addition, the fourth rejection S-NSSAI may be not only the rejection S-NSSAI included in the fourth rejection NSSAI, but also the rejection S-NSSAI not included in the fourth rejection NSSAI. In addition, the record related to the fourth rejection NSSAI mentioned above may also be replaced by the record related to the fourth rejection S-NSSAI.

[0155] In addition, the fourth reject NSSAI and the fourth reject S-NSSAI may be included as LADN information included in a login acceptance message or a setting update command, and notified to the UE from the core network side.

[0156] In addition, the mapped S-NSSAI for the fourth rejected NSSAI may refer to the mapped S-NSSAI corresponding to the fourth rejected NSSAI. In other words, the mapped S-NSSAI for the fourth rejected NSSAI may be the S-NSSAI of the HPLMN mapped to the S-NSSAI of the logged-in PLMN (that is, the S-NSSAI included in the fourth rejected NSSAI or the fourth rejected S-NSSAI) in the roaming scenario.

[0157] In addition, the mapping S-NSSAI for the fourth rejected NSSAI may be valid for 3GPP access and non-3GPP access. In other words, the UE and / or NW may regard the mapping S-NSSAI for the fourth rejected NSSAI as independent of the access type, or may regard the mapping S-NSSAI for the fourth rejected NSSAI as dependent on the access type. In further other words, the UE and / or NW may manage and / or store the mapping S-NSSAI for the fourth rejected NSSAI per access type, or may not manage and / or store the mapping S-NSSAI for the fourth rejected NSSAI per access type.

[0158] Here, the mapping S-NSSAI of the fourth rejected NSSAI being independent of the access type may mean, for example, that when the UE receives the mapping S-NSSAI of the fourth rejected NSSAI via 3GPP access, the mapping S-NSSAI of the fourth rejected NSSAI cannot be utilized via 3GPP access or non-3GPP access. Similarly, it may also mean that when the UE receives the mapping S-NSSAI of the fourth rejected NSSAI via non-3GPP access, the mapping S-NSSAI of the fourth rejected NSSAI cannot be utilized via 3GPP access or non-3GPP access. It should be noted that when the mapping S-NSSAI of the fourth rejected NSSAI is independent of the access type, it is ideal that the UE and / or NW do not store the mapping S-NSSAI of the fourth rejected NSSAI according to each access type (that is, do not store separately according to each access type, but only store the fourth rejected NSSAI), but it is not limited to this.

[0159] In addition, the mapping S-NSSAI of the fourth rejected NSSAI depends on the access type, which may mean, for example, that when the UE receives the mapping S-NSSAI of the fourth rejected NSSAI via 3GPP access, the mapping S-NSSAI of the fourth rejected NSSAI cannot be used via 3GPP access, but it may not mean that it cannot be used via non-3GPP access. That is, it may mean that the mapping S-NSSAI of the fourth rejected NSSAI is not restricted in the use of non-3GPP access. Similarly, it may also mean that when the UE receives the mapping S-NSSAI of the fourth rejected NSSAI via non-3GPP access, the mapping S-NSSAI of the fourth rejected NSSAI cannot be used via non-3GPP access, but it may not mean that it cannot be used via 3GPP access. That is, it may mean that the mapping S-NSSAI of the fourth rejected NSSAI is not restricted in the use of 3GPP access. It should be noted that when the mapping S-NSSAI of the fourth rejected NSSAI depends on the access type, it is ideal that the UE and / or NW stores the mapping S-NSSAI of the fourth rejected NSSAI according to each access type (that is, the fourth rejected NSSAI is stored according to each access type), but is not limited to this.

[0160] In addition, it can also be assumed that the S-NSSAI included in the fourth rejected NSSAI and / or the fourth rejected S-NSSAI and / or the mapping S-NSSAI to the fourth rejected NSSAI in the storage unit of the UE cannot be used for processing in the current tracking area or in the current tracking area in the current login area. That is, the UE may be in a state where the MM process and / or SM process using the S-NSSAI is prohibited in the current tracking area or in the current tracking area in the current login area. In other words, the UE may be in a state where the MM process and / or SM process using the S-NSSAI is not prohibited in a tracking area outside the current tracking area or in a tracking area outside the current tracking area in the current login area.

[0161] In addition, pending NSSAI (also called pending NSSAI, Pending NSSAI) is an S-NSSAI for which the network requires network slice specific authentication (network slice specific authentication), and is a collection of one or more S-NSSAIs that are not available in the current PLMN if the network slice specific authentication is not completed. Pending NSSAI can be a rejected NSSAI (Rejected NSSAI due to NSSAA) or a pending NSSAI of 5GS. Pending NSSAI can be an NSSAI stored by the UE or NW, or it can be an NSSAI sent from the NW to the UE. It should be noted that the pending NSSAI is not limited to the rejected NSSAI, and can also be an NSSAI different from the rejected NSSAI. In the case where the pending NSSAI is the NSSAI sent from the NW to the UE, the pending NSSAI can be information including a combination of one or more S-NSSAI and a rejection reason value. The rejection reason value at this time may be "NSSAA is pending for the S-NSSAI", which may be information indicating that the UE is prohibited or pending from using the S-NSSAI corresponding to the rejection reason value until the NSSAA for the S-NSSAI is completed.

[0162] In addition, the pending NSSAI is valid throughout the logged-in PLMN. In other words, the UE and / or NW may regard the S-NSSAI included in the third rejected NSSAI and the pending NSSAI as information that has nothing to do with the access type. That is, the pending NSSAI may be information that is valid for both 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may also be the first rejected NSSAI.

[0163] In addition, the pending NSSAI is an NSSAI composed of one or more S-NSSAIs for the UE to identify the slices pending for the process. Specifically, the UE does not start the login request process for the S-NSSAI included in the pending NSSAI while storing the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the login process until the NSSAA for the S-NSSAI included in the pending NSSAI is completed. The pending NSSAI is identification information including one or more S-NSSAIs received from the core network in correspondence with the pending rejection reason value indicating the NSSAA. The pending NSSAI is information that is independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send a login request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0164] The tracking area is one or more ranges managed by the core network that can be represented as the location information of UE_A10. The tracking area can be composed of multiple cells. Moreover, the tracking area can be either a range for broadcasting control messages such as paging, or a range where UE_A10 can move without performing a switching process. Moreover, the tracking area can be either a routing area or a positioning area, as long as it is the same area as these areas. Hereinafter, the tracking area may also be referred to as TA (Tracking Area). The tracking area can be identified by TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.

[0165] The login area (also called Registration area or registration area) is a set of one or more TAs assigned to the UE by the AMF. It should be noted that it is better for UE_A10 to move without sending or receiving signals for tracking area update while moving within one or more TAs included in the registration area. In other words, the registration area can be an information group indicating the area where UE_A10 can move without performing the tracking area update process. The registration area can be identified by a TAI list consisting of one or more TAIs.

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

[0167] Network Slice-Specific Authentication and Authorization (NSSAA) refers to the functions used to implement network slice-specific authentication and authorization. In network slice-specific authentication and authorization, UE authentication and authorization can be performed outside the core network such as a third party. PLMNs and network devices with NSSAA functions can perform NSSAA procedures on a certain S-NSSAI based on the UE's login information. Moreover, UEs with NSSAA functions can manage and store pending rejected NSSAI for NSSAA and / or failed rejected NSSAI for NSSAA. In this document, NSSAA is sometimes referred to as a network slice-specific authentication and authorization process, an authentication and authorization process.

[0168] The S-NSSAI requiring NSSAA is an S-NSSAI requiring NSSAA that is managed by the core network and / or the core network device. The core network and / or the core network device may store the S-NSSAI requiring NSSAA by establishing a correspondence between information indicating whether the S-NSSAI and NSSAA are required. The core network and / or the core network device may also establish a correspondence between the S-NSSAI requiring NSSAA and information indicating whether the NSSAA is completed or information indicating the status of allowing or successfully completing the NSSAA, and store them. The core network and / or the core network device may manage the S-NSSAI requiring NSSAA as information that is independent of the access network.

[0169] In addition, a UE in single login mode has only one activated MM state. That is, a UE in single login mode is activated only in either the RM state (5GMM state) in 5GC or the EMM state in EPC. In addition, a UE in single login mode is in 5GC NAS mode when connected to 5GC and in EPC NAS mode when connected to EPC. In addition, a UE in single login mode can only log in to either 5GC or EPC, so it is necessary to map EPS-GUTI (also called 4G-GUTI) to 5G-GUTI when moving between EPC and 5GC.

[0170] In addition, the UE in dual login mode can be in a state where it can independently log in to the 5GC and EPC. The UE in dual login mode can independently maintain the 5G-GUTI and EPS-GUTI (also called 4G-GUTI).

[0171] In addition, SNPN is a type of NPN of 5GS developed for non-public use. It is an NPN that is operated by an NPN operator and does not rely on the NF provided by the PLMN. In addition, SNPN can be identified by a combination of PLMN ID and NID (Network Identifier). In addition, a UE that can use SNPN can support SNPN access mode (also called SNPN access operation mode). In addition, a UE set to act in SNPN access mode may be able to select SNPN and log in to SNPN, but may not be able to select PLMN. In addition, a UE set to act in SNPN access mode may be able to perform the SNPN selection process, but may not be able to perform the PLMN selection process. In addition, even if the UE can use SNPN (SNPN enabled), a UE that is not set to act in SNPN access mode may not be able to select SNPN and log in to SNPN, but may be able to select PLMN. In addition, a UE that is not set to act in SNPN access mode may not be able to perform the SNPN selection process, but may be able to perform the PLMN selection process.

[0172] In addition, a UE that performs actions in SNPN access mode may select SNPN via Uu (3GPP access). In addition, a UE that performs actions in SNPN access mode may also select SNPN via Uu or NWu, wherein Uu or NWu is established via a PDU session provided by a PLMN, and the PLMN is selected via Uu or NWu (non-3GPP access). In addition, a UE that does not perform actions in SNPN access mode may also select PLMN via Uu or NWu, wherein Uu or NWu is established via a PDU session provided by a SNPN, and the SNPN is selected via Uu or NWu (non-3GPP access).

[0173] It should be noted that the SNPN access mode can be managed and / or applied in units of access. That is, it can be managed and / or applied through 3GPP access and non-3GPP access, respectively. In other words, the activation or deactivation of the SNPN access mode for 3GPP access and the activation or deactivation of the SNPN access mode for non-3GPP access can be independent. That is, when the SNPN access mode for 3GPP access is activated, the SNPN access mode for non-3GPP access can be activated or disabled. In addition, when the SNPN access mode for 3GPP access is disabled, the SNPN access mode for non-3GPP access can be activated or disabled.

[0174] Here, the SNPN access mode for 3GPP access (SNPN access mode for3GPP access) may also be referred to as the SNPN access mode in 3GPP access (SNPN access mode over 3GPP access) or the SNPN access mode via 3GPP access (SNPN access mode via 3GPP access).

[0175] In addition, the SNPN access mode for non-3GPP access (SNPN access mode for non-3GPPaccess) can also be called the SNPN access mode in non-3GPP access (SNPN access mode over non-3GPPaccess) or the SNPN access mode via non-3GPP access (SNPN access mode via non-3GPPaccess).

[0176] In addition, "activate" can be replaced by "action", and "disable" can be replaced by "no action". That is, the SNPN access mode for 3GPP access being activated may mean acting in the SNPN access mode for 3GPP access. In addition, the SNPN access mode for 3GPP access being disabled may mean not acting in the SNPN access mode for 3GPP access. In addition, the SNPN access mode for non-3GPP access being activated may mean acting in the SNPN access mode for non-3GPP access. In addition, the SNPN access mode for non-3GPP access being disabled may mean not acting in the SNPN access mode for non-3GPP access.

[0177] In addition, when the UE roams between SNPNs, the SNPN can be classified into a Home SNPN (also called HSNPN) and a Visited SNPN (also called VSNPN). It should be noted that when the UE does not roam between SNPNs, the SNPN can be considered the same as the Home SNPN.

[0178] In addition, the home SNPN may refer to a SNPN to which the UE can log in as a home. In addition, the home SNPN may also refer to the SNPN that the UE first selects in the SNPN selection. In addition, the home SNPN may also refer to a SNPN in which at least a portion of the information included in the SNPN identity (SNPN identity, also called SNPN ID) matches at least a portion of the information included in the IMSI of the UE. In addition, the home SNPN may also refer to a SNPN in which the MCC and MNC included in the PLMN Identity (PLMN Identity, also called PLMN ID) included in the SNPN identity (also called SNPN ID) match the MCC and MNC included in the IMSI of the UE.

[0179] In addition, a visited SNPN may refer to a SNPN that the UE can log in to other than as a home. In addition, a visited SNPN may also refer to a SNPN that the UE does not log in to as a home. In addition, a visited SNPN may also refer to a SNPN that the UE does not select first in the SNPN selection. In addition, a visited SNPN may also refer to a SNPN in which at least a portion of the information included in the SNPN identifier (also called SNPN ID) does not match at least a portion of the information included in the IMSI of the UE. In addition, a visited SNPN may also refer to a SNPN in which the MCC and MNC included in the PLMN identifier (also called PLMN ID) included in the SNPN identifier (also called SNPN ID) do not match the MCC and MNC included in the IMSI of the UE.

[0180] In addition, an equivalent HSNPN (equivalent HSNPN, also called equivalent Home SNPN, EHSNPN) may be an SNPN that is considered to be equivalent to the current SNPN (herein, the home SNPN (also called HSNPN)) in SNPN selection and / or cell selection and / or cell reselection. In addition, an equivalent HSNPN may also refer to one or more SNPNs included in an equivalent HSNPN list, and may also refer to one or more SNPNs that are not included in an equivalent VSNPN (equivalent VSNPN) list.

[0181] In addition, an equivalent VSNPN (also called equivalent Visited SNPN, EVSNPN) may refer to an SNPN that is considered to be equivalent to the current SNPN (here, a visited SNPN (also called VSNPN)) in SNPN selection and / or cell selection and / or cell reselection. In addition, an equivalent VSNPN may also refer to one or more SNPNs included in an equivalent VSNPN list, and may also refer to one or more SNPNs that are not included in an equivalent HSNPN list.

[0182] In addition, an equivalent SNPN (also referred to as ESNPN) may be a concept including an equivalent HSNPN and / or an equivalent VSNPN. That is, ESNPN may refer to an equivalent HSNPN and / or an equivalent VSNPN.

[0183] In addition, the SNPN successfully logged in by the UE may be a RSNPN (Registered SNPN; also called a logged-in SNPN).

[0184] Next, in the present embodiment, identification information transmitted, received, stored and / or managed by each device will be described.

[0185] First, the first identification information is the request NSSAI (also referred to as the request NSSAI IE).

[0186] Furthermore, the second identification information is information of the unavailable period or including the unavailable period.

[0187] In addition, the third identification information is information indicating the type of login requested. The third identification information may be a 5GS registration type. In addition, the third identification information may indicate an initial registration, a mobility registration updating, a periodic registration updating, an emergency registration, an SNPN onboarding registration, a disaster roaming mobility registration updating, or a disaster roaming periodic registration updating. In addition, the third identification information may indicate a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability.

[0188] In addition, the fourth identification information is UE capability information. The fourth identification information may be 5GMM capability (5GMMcapability). In addition, the fourth identification information may also be information indicating whether the UE supports functions related to the unavailable period. In addition, the fourth identification information may also be information indicating that the UE supports functions related to the unavailable period.

[0189] Furthermore, the fifth identification information may be information indicating a request for transmission of an updated timer value. Furthermore, the fifth identification information may be information indicating a request for transmission of an updated twelfth identification information.

[0190] Furthermore, the sixth identification information is information configured to include at least one of the first to fifth identification information.

[0191] In addition, the eleventh identification information may be information indicating a network slice. The eleventh identification information may also be NSSAI. Specifically, the eleventh identification information may also be allowed NSSAI and / or rejected NSSAI and / or extended rejected NSSAI and / or pending NSSAI and / or set NSSAI sent from the network to the UE.

[0192] In addition, the twelfth identification information is a timer value. The twelfth identification information may also be a T3512 value (T3512 value). Here, the T3512 value may be a timer value set as a periodic registration update timer (periodic registration update timer).

[0193] Furthermore, the thirteenth identification information is information indicating the extension of the periodic login update timer. The thirteenth identification information may also be information indicating the extension of the already set periodic login update timer.

[0194] In addition, the fourteenth identification information is network capability information. The fourteenth identification information may also be 5GS network feature support (5GS network feature support). In addition, the fourteenth identification information may also be information indicating whether the network supports functions related to the unavailable period. In addition, the fourteenth identification information may also be information indicating that the network supports functions related to the unavailable period.

[0195] Furthermore, the fifteenth identification information is information indicating whether the setting related to the unavailable period is completed. Furthermore, the fifteenth identification information may indicate that the setting related to the unavailable period is completed, or may indicate that the setting related to the unavailable period is not completed.

[0196] Furthermore, the sixteenth identification information is information configured to include at least one of the eleventh to fifteenth identification information.

[0197] It should be noted that the first to sixth identification information and the eleventh to sixteenth identification information may be information pre-stored by the UE and / or the base station and / or the AMF and / or a core network device or network function other than the AMF. In addition, when sending and receiving these identification information, the receiving side may store the received identification information. [3. First embodiment]

[0198] First, the procedures used in the first embodiment are described. The procedures used in the first embodiment include a registration procedure. Each procedure is described below.

[0199] It should be noted that, in the first embodiment, Figure 2As described in the , the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are respectively configured as the same device / function (that is, the same physical hardware, the same logical hardware, or the same software) is used as an example for explanation. However, the content described in this embodiment can also be applied to the case where they are configured as different devices / functions (that is, different physical hardware, different logical hardware, or different software). For example, data can be sent and received directly between them, data can be sent and received via the N26 interface between AMF and MME, and data can be sent and received via UE. [3.1. Login process]

[0200] Next, use Figure 6 The registration procedure is described. In this chapter, the registration procedure is sometimes referred to as this procedure. The registration procedure is a process for the UE to take the lead in logging into the access network_B and / or core network_B and / or DN. The UE can perform this procedure in a state where it is not logged into the network (also called a non-logged-in state, 5GMM-DEREGISTERED state), or in a state where it is logged into the network (also called a logged-in state, 5GMM-REGISTERED state). For example, a UE in a non-logged-in state can start this procedure at any timing. In addition, each device (especially the UE and AMF) can transition to a registered state (5GMM-REGISTERED state) based on the completion of the registration procedure. It should be noted that the registration state can be managed by each device for each access. Specifically, each device can independently manage the registration state for 3GPP access (registered state or non-registered state) and the registration state for non-3GPP access.

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

[0202] The UE can start the login process when it moves to a TA that is outside the current login area. In other words, the UE can start the login process when it moves to a TA different from the TA shown in the maintained TA list. Furthermore, the UE can also start the login process when the context of each device needs to be updated due to the disconnection or failure of the PDU session. Furthermore, the UE can also start the login process when the capability information and / or preferences related to the establishment of the UE's PDU session change. Moreover, the UE can also start the login process periodically. Moreover, the UE can also start the login process based on the completion of the MM process or the SM process or the information received from the network in each process. In addition, the UE can also start this process after the completion of this process. It should be noted that the UE can perform the login process at any timing, and is not limited to this.

[0203] In addition, (a) this process can be started by a UE that is not logged in; (b) this process can also be started by a UE that is logged in; (c) this process can also be started by a UE that is logged in, that is, a UE that has not scheduled events such as OS upgrade, security patch update, modem reset, modem software update, etc.; (d) this process can also be started by a UE that is logged in, that is, the UE is started before the above-mentioned events are scheduled but the events are executed; (e) this process can also be started by a UE that is logged in or not logged in, that is, a UE that has scheduled the above-mentioned events, and although the events are executed, the events are terminated halfway; (f) this process can also be started by a UE that is logged in or not logged in, that is, a UE that has scheduled the above-mentioned events, and executed and completed the events.

[0204] In addition, this process can also be performed in a PLMN (HPLMN or VPLMN) or an equivalent PLMN or a SNPN or an equivalent SNPN.

[0205] It should be noted that the above-mentioned process for transitioning from a state where the UE is not logged in to the network (non-logged in state) to a logged in state (logged in state) may be an initial registration procedure or a registration procedure for initial registration. In addition, the registration procedure performed in a state where the UE is logged in to the network (logged in state) may also be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0206] It should be noted that the UE may store at least one of the NSSAIs recorded in Chapter 2.6 and / or the S-NSSAIs included in the NSSAIs at the time of starting this process.

[0207] The details of the login process described below can be applied to any of these.

[0208] First, the UE starts the registration process by sending a registration request message (S600)(S602)(S604) to the AMF. Specifically, the UE sends an RRC message including a registration request message to a base station device (also called 5G AN, gNB) (S600). It should be noted that the registration request message may be a NAS message sent and received on the N1 interface. In addition, the RRC message may be a control message sent and received between the UE and the base station device. In addition, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. It should be noted that the NAS layer is a layer higher than the RRC layer.

[0209] Here, the UE can include the first to sixth identification information in a login request message and / or an RRC message for transmission. Here, the first to sixth identification information can be as described in Chapter 2.6.

[0210] In addition, the UE may include the identification information in a control message different from the information, for example, in a control message of a layer lower than the RRC layer (for example, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, a SDAP (Service Data Adaptation Protocol) layer, etc.). It should be noted that by sending the identification information, the UE may indicate that the UE supports various functions, may indicate the UE's request, or may indicate both.

[0211] In addition, the information indicating whether the function requested by the UE is supported and the information indicating whether the use of the function is allowed can be sent as the same identification information. In other words, by sending information indicating that the UE supports a certain function, the UE can be instructed to request the use of the function. In addition, by sending information indicating that the UE requests the use of a certain function, the UE can be instructed to support the function. In addition, by sending information indicating that the UE does not support a certain function, the UE can be instructed not to request the use of the function. In addition, by sending information indicating that the UE does not request the use of a certain function, the UE can be instructed not to support the function.

[0212] It should be noted that the UE can select and determine whether to send which of the first to sixth identification information to the network based on the UE's capability information and / or UE policy, and / or the UE's status and / or the user's login information and / or the context maintained by the UE and / or the identification information sent and received in the process executed before this process.

[0213] In addition, the UE can determine whether to send which of the first to sixth identification information to the network each time in the above (a) to (f).

[0214] For example, a UE that does not support functions related to the unavailable period may not send the second identification information.

[0215] In addition, for example, a UE that does not support functions related to unavailable periods may not send the third identification information indicating "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability".

[0216] In addition, for example, a UE that does not support functions related to unavailability periods may also send third identification information indicating "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" (for example, initial login, mobile login update, periodic login update, etc.).

[0217] In addition, for example, a UE that does not support a function related to an unavailable period may also send fourth identification information indicating that the UE does not support a function related to an unavailable period.

[0218] In addition, for example, a UE that does not support the function related to the unavailable period may not send the fourth identification information indicating that it supports the function related to the unavailable period.

[0219] In addition, for example, a UE supporting functions related to unavailable periods may not send the second identification information in (a) and / or (c) and / or (f).

[0220] In addition, for example, a UE supporting a function related to an unavailable period may send the second identification information at (d) and / or (e).

[0221] In addition, for example, a UE supporting functions related to unavailability periods may also send second identification information indicating a new (updated) unavailability period at time (e), that is, during an already set unavailability period, when an event cannot be completed or the already set unavailability period is extended.

[0222] In addition, for example, a UE that supports functions related to unavailability periods may also send third identification information other than "login for an unavailability period or login related to an unavailability period or login for unavailability or login related to unavailability" (for example, initial login, mobile login update, periodic login update, etc.) at (a) and / or (c) and / or (f).

[0223] In addition, for example, a UE that supports a function related to an unavailable period may also send a third identification information indicating "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" at (d) and / or (e).

[0224] In addition, for example, a UE supporting a function related to an unavailable period may also send fourth identification information indicating support for the function related to an unavailable period.

[0225] In addition, for example, a UE that supports the function related to the unavailable period may not send the fourth identification information indicating that the UE does not support the function related to the unavailable period.

[0226] In addition, for example, when a timer for using an unavailable period is started or during the unavailable period, if there is a change in the period of the unavailable period, the UE may send second identification information including the value of the changed unavailable period.

[0227] In addition, for example, the UE may send the second identification information when being notified of an unavailable period from an upper layer.

[0228] In addition, for example, the UE may generate an unavailable period based on information notified from an upper layer.

[0229] In addition, for example, when the UE is a UAV (Uncrewed Aerial Vehicle), the unavailable period can be sent to the UAV-C (UAV controller). In addition, when the UE is a UAV, the unavailable period can also be sent to the UAV-C via the network and / or USS (Uncrewed Aerial System Service Supplier) and / or UTM (Uncrewed Aerial System Traffic Management) and / or UAS-NF (Uncrewed Aerial System Network Function). In addition, when the UE is a UAV, the unavailable period can also be sent to the USS and / or UTM and / or UAS-NF.

[0230] It should be noted that the above is only an example, and the UE's judgment on whether to send any of the first to sixth identification information to the network does not need to be limited to the above conditions, but can also be performed by combining the above conditions.

[0231] In addition, the UE may also include information other than the first to sixth identification information in the login request message and / or RRC message, for example, it may include UE ID and / or PLMN ID and / or AMF identification information for transmission. Here, the AMF identification information may refer to information that identifies the AMF or a set of AMFs, for example, it may refer to 5G-S-TMSI (5G S-TemporaryMobileSubscriptionIdentifier: 5G S-TemporaryMobileSubscriptionIdentifier), GUAMI (Globally UniqueAMF Identifier: Globally UniqueAMF Identifier).

[0232] Next, when the base station device receives the RRC message including the login request message, it selects the AMF to forward the login request message (S602). It should be noted that the base station device can select the AMF based on the identification information included in the login request message and / or the RRC message. For example, the base station device can select the AMF included in the network slice identified by the first identification information or the AMF having connectivity to the network slice identified by the first identification information. It should be noted that the method for selecting the AMF is not limited to this, and the base station device can also select the AMF based on conditions other than this.

[0233] In addition, the base station device extracts the login request message from the received RRC message and forwards the login request message to the selected AMF (S604). It should be noted that, when the first to sixth identification information are not included in the login request message but included in the RRC message, these identification information can be forwarded to the selected AMF together with the login request message (S604).

[0234] Then, the AMF may perform a first condition determination upon receiving the login request message and / or identification information. The first condition determination is used to determine whether the network accepts the request of the UE. The AMF may perform the processes of S610 to S612 when the first condition determination is determined to be true. In addition, the AMF may also perform the process of S610 when the first condition determination is determined to be false.

[0235] In addition, the first condition determination may also be performed by a network function (also referred to as NF) other than the AMF. In the case where the NF other than the AMF performs the first condition determination, the AMF may provide the NF with the information required for the first condition determination, specifically, at least a portion of the information received from the UE (S606). Further, in the case where the NF determines the truth or falsity of the first condition determination based on the information received from the AMF, information including the result of the first condition determination (in short, true or false) may be transmitted to the AMF. The AMF may determine the identification information and / or control message to be sent to the UE based on the result of the first condition determination received from the NF.

[0236] It should be noted that the control message sent and received in S610 may be a registration accept message or a registration reject message. In addition, for example, when the first condition is true, the control message sent and received in S610 may be a registration accept message, and when the first condition is false, the control message sent and received in S610 may be a registration accept message or a registration reject message.

[0237] It should be noted that the first condition judgment can be performed based on the reception of the login request message and / or the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF included in the login request message.

[0238] For example, in the case where the network allows or does not reject the UE's request, the first conditional judgment can be determined to be true, and in the case where the network does not allow or reject the UE's request, the first conditional judgment can be determined to be false. In addition, in the case where the network only allows or does not reject a part of the UE's request, the first conditional judgment can be determined to be true even in the case of a request from the UE that is not allowed. In addition, in the case where the network does not allow or reject all UE's requests, the first conditional judgment can be determined to be false. In addition, in the case where the network and / or network device that the UE wants to log in supports the function requested by the UE, the first conditional judgment can be determined to be true, and in the case where the function requested by the UE is not supported, the first conditional judgment can be determined to be false. Moreover, in the case where the identification information sent and received is allowed, the first conditional judgment can be determined to be true, and in the case where the identification information sent and received is not allowed, the first conditional judgment can be determined to be false.

[0239] In addition, the AMF may include one or more of the eleventh to sixteenth identification information in the control message and send it to the UE via the base station device. Here, the eleventh to sixteenth identification information may be as described in Chapter 2.6. It should be noted that, by sending these identification information and / or control messages, the AMF may indicate whether the network supports each function, whether to accept the UE's request, or a combination of these. It should be noted that the information indicating support for each function and the information indicating a request to use each function may be sent and received as the same identification information, or may be sent and received as different identification information. In addition, the information indicating whether the function requested by the UE is supported and the information indicating whether the use of the function is allowed may be sent as the same identification information. For example, the permission to use the function requested by the UE may be indicated by sending information indicating support for the function requested by the UE. In addition, the support for the function requested by the UE may be indicated by sending information indicating permission to use the function requested by the UE. In addition, the use of the function requested by the UE may be indicated by sending information indicating that the use of the function requested by the UE is allowed. In addition, the use of the function requested by the UE may be indicated by sending information indicating that the function requested by the UE is not supported. In addition, the non-support of the function requested by the UE may be indicated by sending information indicating that the use of the function requested by the UE is not allowed.

[0240] In addition, the AMF may include at least one of the eleventh to sixteenth identification information in a control message and send it when a login request message including at least one of the first to sixth identification information is received from the UE or a login request message not including at least one of the first to sixth identification information is received from the UE.

[0241] In addition, the AMF can determine whether which of the eleventh to sixteenth identification information is included in the control message based on the received identification information and / or subscriber information and / or network capability information and / or operation policy and / or network status and / or user login information and / or context maintained by the AMF and / or identification information sent and received in a process performed before this process.

[0242] In addition, the AMF can determine whether to send which of the eleventh to sixteenth identification information to the UE based on the received control message and / or identification information each time in the above (a) to (f).

[0243] For example, in a case where the network does not support functions related to the unavailable period, that is, when the second identification information is received from the UE, the AMF may send twelfth identification information determined without considering the unavailable period represented by the second identification information.

[0244] In addition, for example, in the case where the UE and / or the network do not support functions related to the unavailability period, the AMF may not send the thirteenth identification information.

[0245] In addition, for example, in the case where the network does not support the function related to the unavailable period, the AMF may send the fourteenth identification information indicating that the function related to the unavailable period is not supported, or may not send the fourteenth identification information indicating that the function related to the unavailable period is supported.

[0246] In addition, for example, in the case where the UE and / or the network does not support functions related to the unavailability period, the AMF may not send the fifteenth identification information.

[0247] In addition, for example, in the case where the network supports a function related to an unavailable period, that is, when the second identification information is received from the UE, the AMF may send a twelfth identification information indicating a timer value determined in consideration of the second identification information. For example, the AMF may set the T3512 value to a period longer than the period indicated by the second identification information when not sending the T3512 value to the UE, and send the twelfth identification information indicating the T3512 value. In addition, for example, the AMF may also compare the T3512 value with the period indicated by the second identification information when the T3512 value has been sent to the UE, and in the case where the T3512 value is the same as or longer than the period indicated by the second identification information, set the T3512 value to the period already sent, and send the twelfth identification information indicating the T3512 value. Conversely, in a case where the T3512 value is the same as or shorter than the period represented by the second identification information, the AMF may set the T3512 value to a period longer than the period represented by the second identification information and send the twelfth identification information representing the T3512 value.

[0248] In addition, for example, in the case where the network supports functions related to unavailability periods, that is, when the second identification information is not received from the UE, the AMF can send twelfth identification information determined without considering the second identification information.

[0249] In addition, for example, in the case where the network supports functions related to unavailability periods, that is, when the third identification information indicating "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" is not received from the UE, the twelfth identification information and / or the thirteenth identification information may not be sent.

[0250] In addition, for example, in the case where the network supports functions related to unavailability periods, that is, when the third identification information indicating "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" is received from the UE, the AMF may also send the twelfth identification information and / or the thirteenth identification information.

[0251] In addition, for example, in the case where the network supports functions related to unavailability periods, the AMF may also send thirteenth identification information.

[0252] In addition, for example, in the case where the network supports functions related to unavailability periods, that is, when the second identification information and the third identification information indicating "is a login for an unavailability period or a login related to an unavailability period or a login for unavailability or a login related to unavailability" are received from the UE, the AMF may also send the twelfth identification information and / or the thirteenth identification information.

[0253] In addition, for example, in the case where the network supports functions related to unavailable periods, the AMF may also send fourteenth identification information indicating support for functions related to unavailable periods.

[0254] In addition, for example, when the present process is performed via 3GPP access, the AMF may send the twelfth identification information, and when the present process is performed via non-3GPP access, the AMF may not send the twelfth identification information.

[0255] In addition, for example, regardless of whether the present process is performed via 3GPP access or non-3GPP access, the AMF may send the eleventh to sixteenth identification information.

[0256] In addition, for example, when receiving the second identification information and / or the third identification information indicating "a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability", the AMF can identify that an event occurs in the UE, and can also identify that an event occurs in the UE in the near future, and can also identify that an event occurs in the UE after the completion of this process, and can also send the twelfth identification information and / or the thirteenth identification information.

[0257] In addition, for example, in the case where the UE and / or the network do not support functions related to the unavailable period, the AMF may not send the twelfth identification information indicating the timer value of the unavailable period length, or may send the twelfth identification information without considering the unavailable period.

[0258] In addition, for example, in the case where the UE and / or the network supports functions related to the unavailable period, the AMF may send twelfth identification information indicating a timer value longer than the unavailable period.

[0259] In addition, for example, in an action using a timer for an unavailable period or during an unavailable period, upon receiving fifth identification information indicating a request for sending an updated timer value from the UE, the AMF may send twelfth identification information indicating an updated timer value.

[0260] In addition, for example, in the case where the UE and the network support the function related to the unavailable period, the AMF may send the fifteenth identification information. In addition, for example, in the case where the UE and the network support the function related to the unavailable period, that is, when the setting related to the unavailable period is completed, the AMF may send a control message including the fifteenth identification information indicating that the setting related to the unavailable period is completed. In addition, for example, in the case where the UE and the network support the function related to the unavailable period, that is, when the setting related to the unavailable period is not completed, the AMF may send a control message including the fifteenth identification information indicating that the setting related to the unavailable period is not completed.

[0261] In addition, for example, in the case where the network (also known as a network device, network function) does not support functions related to the unavailable period, that is, when the second identification information is received from the UE, the AMF may be unable to recognize the content, may ignore the content, or may discard the second identification information.

[0262] In addition, for example, in the case where the network does not support functions related to unavailability periods, that is, when third identification information indicating "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" is received from the UE, the AMF may be unable to recognize the content, or may ignore the content, or may discard the third identification information, or may recognize it as other than "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" (for example, initial login, mobile login update, periodic login update, etc.) and store it.

[0263] In addition, for example, in the case where the network supports functions related to unavailability periods, upon receiving the second identification information from the UE, the AMF can identify the content and also store it.

[0264] In addition, for example, in the case where the network supports functions related to unavailability periods, that is, when third identification information indicating "is a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" is received from the UE, the AMF can identify the content and store it.

[0265] In addition, for example, even in the case where the network supports functions related to unavailability periods, that is, when third identification information indicating "a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" is received from the UE, the AMF can also identify it as other than "a login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" (for example, initial login, mobile login update, periodic login update, etc.) and store it.

[0266] In addition, for example, it may be that, in an action using a timer for an unavailable period, when second identification information indicating an updated unavailable period is received from a UE, the stored unavailable period for the UE is updated, the timer is stopped, and the timer is started using the updated unavailable period.

[0267] In addition, for example, during the unavailable period, when second identification information indicating an updated unavailable period is received from the UE, the stored unavailable period for the UE may be updated, the unavailable period may be stopped, and the updated unavailable period may be started.

[0268] In addition, for example, when receiving a login request message including second identification information from the UE, the AMF may start a timer or an unavailable period using the unavailable period indicated by the second identification information.

[0269] In addition, for example, in the case where the AMF receives a login request message including the second identification information and / or the third identification information from the UE and / or sends a control message including at least one of the eleventh to sixteenth identification information to the UE, the AMF may start a timer or an unavailable period using the unavailable period indicated by the second identification information, or may store the unavailable period as a UE context for the UE (setting information for the UE). For example, the AMF may store an unavailable period for the UE (i.e., a period during which the UE cannot communicate) and / or the UE cannot communicate during the unavailable period in the UE context for the UE, and the AMF may also recognize that the validity period of the setting information stored in the UE context is the period of the unavailable period indicated by the second identification information. For example, the AMF may also store the setting information in the UE context for the UE, and start a timer or an unavailable period using the unavailable period indicated by the second identification information. Moreover, the AMF may also delete the setting information from the UE context for the UE when the timer expires or when the unavailable period has passed.

[0270] In addition, for example, the AMF may not send control information (e.g., NAS message) to the UE during a timer action using an unavailable period for the UE or during the unavailable period for the UE, may not send user data to the UE, may buffer control information or user data, or may instruct control information or user data to be buffered in other network devices. In addition, the AMF may send control information (e.g., NAS message) to the UE, may send user data to the UE, may send buffered control information or user data, or may instruct control information or user data buffered in other network devices to be sent to the UE when a timer action using an unavailable period for the UE expires or when the unavailable period for the UE has passed.

[0271] In addition, for example, the AMF may notify the base station device serving the UE that the UE cannot communicate and / or the unavailable period for the UE during the period in which the setting information as described above is stored in the UE context for the UE. Then, the base station device receiving this information may recognize that the UE is in a state where it cannot communicate, and may not send a control message and / or RRC message to the UE.

[0272] In addition, for example, when the setting information as described above is stored in the UE context for the UE, the AMF may also notify the NEF (Network Exposure Function) as a core network device of the unavailable period for the UE. In addition, the NEF that receives the information may store the unavailable period for the UE, or may recognize that the UE is in a state where it cannot communicate, or may notify the AF (Application Function) of the unavailable period for the UE. The AF that receives the information may store the unavailable period for the UE, or may recognize that the UE is in a state where it cannot communicate.

[0273] In addition, for example, when the AMF stores the setting information as described above in the UE context for the UE, upon receiving a login request message from the UE that does not include the second identification information and / or includes third identification information other than "login for an unavailable period or a login related to an unavailable period or a login for unavailability or a login related to unavailability" (for example, initial login, mobile login update, periodic login update, etc.), the AMF may delete the setting information stored in the UE context, thereby storing and identifying that the UE can communicate.

[0274] In addition, for example, when deleting the above-mentioned information from the UE context for the UE, the AMF may also delegate the deletion of the unavailable period for the UE to the NEF (Network Exposure Function) as a core network device. In addition, the NEF that receives the information may delete the unavailable period for the UE, or may recognize that the UE is in a communicative state, or may delegate the deletion of the unavailable period for the UE to the AF (Application Function). The AF that receives the information may delete the unavailable period for the UE, or may recognize that the UE is in a communicative state.

[0275] In addition, for example, the AMF may also send a twelfth identification information indicating a timer value that does not take into account the unavailability period when deleting the setting information as described above from the UE context for the UE.

[0276] It should be noted that the above is merely an example, and the judgment of whether AMF sends any of the eleventh to sixteenth identification information to the network does not need to be limited to the above conditions, and can be performed by combining the above conditions.

[0277] In addition, the AMF may indicate that the UE's request is accepted by sending a login accept message, or may indicate that the UE's request is rejected by sending a login reject message.

[0278] Next, the UE receives a control message (login acceptance message or login rejection message) and / or the eleventh to sixteenth identification information sent via the base station device (S610). In the case where the control message is a login acceptance message, the UE can identify and store the acceptance of the UE's request implemented by the login request message and the content of each identification information included in the login acceptance message by receiving the login acceptance message. In addition, in the case where the control message is a login rejection message, the UE can also identify and store the rejection of the UE's request implemented by the login request message and the content of each identification information included in the login rejection message by receiving the login rejection message. In addition, the UE can also perform actions based on the received control message and / or identification information.

[0279] For example, when the UE receives a control message during the login process starting at (d) above, it may start a timer using an unavailable period or start an unavailable period. The unavailable period may be an unavailable period sent via the second identification information.

[0280] In addition, for example, when the UE receives a control message during the login process started at (e) above, it can start a timer using the updated unavailable period, or start the updated unavailable period. The unavailable period can be the unavailable period sent via the second identification information.

[0281] For example, upon receiving the eleventh identification information, the UE may store the allowed NSSAI and / or rejected NSSAI and / or extended rejected NSSAI and / or pending NSSAI and / or set NSSAI included in the eleventh identification information.

[0282] In addition, for example, the UE may also start the timer using the T3512 value represented by the twelfth identification information when receiving the twelfth identification information. Then, after 3GPP access, the UE in 5GMM-CONNECTED mode may reset the timer when the timer expires and start it using the initial value. In addition, after 3GPP access, the UE in 5GMM-IDLE mode may also start the login process for periodic login update when the timer expires.

[0283] In addition, for example, a UE supporting functions related to unavailability periods can, upon receiving the thirteenth identification information, use the T3512 value that has already started to reset the timer in action, and use the T3512 value represented by the twelfth identification information received this time or already received to start the timer.

[0284] In addition, for example, a UE that supports functions related to unavailable periods can, when receiving the fourteenth identification information indicating that the network supports the functions related to unavailable periods, identify that the network supports the functions related to unavailable periods, and when receiving the fourteenth identification information indicating that the network does not support the functions related to unavailable periods, identify that the network does not support the functions related to unavailable periods.

[0285] In addition, for example, a UE supporting functions related to unavailable periods may execute events after this process is completed even if it receives the fourteenth identification information indicating that the network does not support functions related to unavailable periods.

[0286] In addition, for example, when a UE that supports functions related to unavailable periods receives the fourteenth identification information indicating that the network does not support functions related to unavailable periods, after an event occurs after the completion of this process (for example, (d) or (e)), the UE may not include the second identification information in the login request message in the login process initiated by the UE or the non-login request message in the non-login process, and may not send the login request message or non-login request message including the second identification information.

[0287] In addition, for example, when a UE that does not support functions related to the unavailable period receives the thirteenth identification information, it may be unable to recognize the content, may ignore the content, or may discard the thirteenth identification information.

[0288] In addition, for example, when a UE that does not support functions related to unavailable periods receives the fourteenth identification information indicating support for functions related to unavailable periods or indicating non-support for functions related to unavailable periods, the UE may be unable to recognize the content, may ignore the content, or may discard the fourteenth identification information.

[0289] In addition, for example, when a UE that does not support functions related to the unavailable period receives the fifteenth identification information, it may be unable to recognize the content, may ignore the content, or may discard the fifteenth identification information.

[0290] In addition, for example, a UE that does not support a function related to an unavailable period may not be able to start a timer using an unavailable period or an unavailable period when receiving a control message.

[0291] In addition, for example, a UE supporting a function related to an unavailable period may use the unavailable period to start a timer or an unavailable period when receiving a control message.

[0292] In addition, for example, when a UE supporting a function related to an unavailable period receives the fourteenth identification information indicating support for the function related to the unavailable period, the UE can use the unavailable period to start a timer or an unavailable period.

[0293] In addition, for example, when a UE supporting a function related to an unavailable period receives the fourteenth identification information indicating that the function related to the unavailable period is not supported, the UE may start a timer or an unavailable period without using the unavailable period.

[0294] In addition, for example, when a UE supporting functions related to the unavailable period receives a control message during the login process starting at (d) above, it can recognize that the settings related to the unavailable period in the network are completed.

[0295] In addition, for example, when a UE that supports functions related to unavailable periods receives twelfth identification information representing a T3512 value that is greater than the T3512 value set in the timer that has already been started during the login process starting at (d) above, it can recognize that the settings related to the unavailable period in the network are completed.

[0296] In addition, for example, when a UE supporting functions related to the unavailable period receives the twelfth identification information indicating a T3512 value larger than the unavailable period and / or the fifteenth identification information indicating that the settings related to the unavailable period are completed during the login process starting at (d) above, it can recognize that the settings related to the unavailable period in the network are completed.

[0297] In addition, for example, when a UE supporting a function related to an unavailable period receives the fifteenth identification information indicating that the setting related to the unavailable period is not completed during the login process started at (d) above, it can be recognized that the setting related to the unavailable period in the network is not completed. In this case, the UE can start the login process again or start the non-login process in order to perform the setting related to the unavailable period.

[0298] In addition, for example, when a UE supporting a function related to an unavailable period does not receive a control message during the login process started at (d) above, it can be recognized that the setting related to the unavailable period in the network is not completed. In this case, the UE can start the login process again or start the non-login process in order to perform the setting related to the unavailable period.

[0299] In addition, for example, when the UE updates the unavailable period in an action using a timer for the unavailable period, it can update the stored unavailable period, stop the timer, start the timer using the updated unavailable period, or send a login request message or a non-login request message including second identification information indicating the updated unavailable period.

[0300] In addition, for example, when the UE updates the unavailable period during the unavailable period, it can use the updated unavailable period to start, and can also send a login request message or a non-login request message including second identification information indicating the updated unavailable period.

[0301] In addition, for example, when an event ends, the UE can delete the stored unavailable period, and when there is a timer using the unavailable period in an action, the UE can stop the timer, end the unavailable period, or send a login request message that does not include the second identification information.

[0302] In addition, for example, when the UE establishes a PDU session or an MA (Multi-Access) PDU session before starting a timer using an unavailable period, the PDU session release procedure may be started in order to release the established PDU session or MA PDU session.

[0303] In addition, for example, when the UE establishes a PDU session or an MA PDU session before starting the unavailable period, in order to release the established PDU session or MA PDU session, a PDU session release procedure may be started.

[0304] In addition, for example, after the present process started at (d) or (e) above is completed and a PDU session or MA PDU session is established before the execution event, a PDU session release process may be started in order to release the established PDU session or MA PDU session.

[0305] In addition, for example, the UE may not start the PDU session establishment process, and may not perform the MM process and / or the SM process during an operation using a timer for the unavailable period or during the unavailable period.

[0306] In addition, for example, when the UE receives an MM message and / or SM message from the core network during an action using a timer for an unavailable period or during an unavailable period, the UE may ignore the MM message and / or SM message or discard the MM message and / or SM message.

[0307] In addition, for example, when a login acceptance message is received, at the timing of starting this process, the UE in 5GMM-IDLE mode can be switched to 5GMM-CONNECTED mode, and at the timing of starting this process, the UE in 5GMM-CONNECTED mode can also maintain the 5GMM-CONNECTED mode.

[0308] In addition, for example, when a login rejection message is received, the UE in 5GMM-IDLE mode can maintain the 5GMM-IDLE mode at the timing of starting this process, and the UE in 5GMM-CONNECTED mode can also be transformed into the 5GMM-IDLE mode at the timing of starting this process.

[0309] In addition, for example, when a control message is received during the login process started at (d) above, the UE can execute an event.

[0310] In addition, when the control message is a login acceptance message, the UE can also send a login completion message to the AMF (S612) via the base station device as a response message to the login acceptance message. Here, the login completion message is a NAS message sent and received on the N1 interface, but it can also be sent and received between the UE and the base station device in an RRC message.

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

[0312] In addition, each device may also complete the login process based on the sending and receiving of the login rejection message.

[0313] It should be noted that each device can transition or maintain the state in which the UE has logged in to the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of the login acceptance message and / or the login completion message, and can also transition or maintain the state in which the UE has not logged in to the network for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending and receiving of the login rejection message. In addition, the transition of each device to each state can also be based on the sending and receiving of the login completion message or the completion of the login process.

[0314] Moreover, each device may implement processing based on information sent and received during the login process based on the completion of the login process. For example, the reason why the UE's request was rejected may be identified when information indicating that a part of the UE's request was rejected is sent and received. Furthermore, each device may implement this process again based on the reason why the UE's request was rejected, and may also implement the login process for the core network_A and other cells.

[0315] Furthermore, the UE may store the identification information received together with the registration accept message and / or the registration reject message based on the completion of the registration procedure, and may also identify the determination of the network.

[0316] In addition, each device can establish corresponding storage for the information sent and received in this process. [4. Modifications]

[0317] The program that operates through the device of one embodiment of the present invention may be a program that controls a central processing unit (CPU) and the like to make the computer function to implement the functions of the embodiment of the present invention. The program or the information processed by the program is temporarily stored in a volatile memory such as a random access memory (RAM) or a non-volatile memory such as a flash memory, a hard disk drive (HDD) or other storage device system.

[0318] It should be noted that the program for realizing the functions of the implementation method involved in one scheme of the present invention may also be recorded in a computer-readable recording medium. It can be realized by reading the program recorded in the recording medium into a computer system and executing it. The "computer system" mentioned here refers to a computer system built into the device, and includes a computer system of hardware such as an operating system and peripherals. In addition, the "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically retains a program for a short time, or other computer-readable recording media.

[0319] In addition, each functional block or each feature of the device used in the above-mentioned embodiment can be installed or executed in a circuit, such as an integrated circuit or multiple integrated circuits. Circuits designed in a manner to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor may be a microprocessor, or it may be a processor, controller, microcontroller or state machine of the previous type. The aforementioned circuit may be composed of digital circuits or analog circuits. In addition, in the case where integrated circuit technology that replaces existing integrated circuits emerges with the advancement of semiconductor technology, one or more schemes of the present invention may also use new integrated circuits based on this technology.

[0320] It should be noted that the invention of the present application is not limited to the above-mentioned embodiments. In the embodiments, an example of a device is described, but an embodiment of the invention of the present application is not limited thereto, and can be applied to fixed or non-movable electronic devices set up indoors and outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, other life equipment, and other terminal devices or communication devices.

[0321] The embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present invention. In addition, a scheme of the present invention can be variously changed within the scope shown in the technical scheme, and the embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other. (Cross-reference of related applications) This application claims the benefit of priority to Japanese patent application No. 2022-102471 filed on June 27, 2022, the entire contents of which are incorporated herein by reference. Description of Reference Numerals 1: Mobile communication system 10: UE_A 30: PGW-U 32: PGW-C 35: SGW 40: MME 45: eNB 50:HSS 60: PCRF 80: Access network_A 90: Core Network_A 120: Access network_B 122: gNB 130: UPF 132: SMF 140:AMF 150: UDM 160: PCF 170:N3IWF 190: Core Network_B

Claims

1. A user equipment UE, comprising a control unit and a storage unit, wherein the UE is characterized in that: When the unavailable period is stored in the storage unit, the control unit deletes the unavailable period stored in the storage unit when the event ends.

2. The UE according to claim 1, characterized in that The UE further includes a transceiver configured to transmit a login request message that does not include an unavailable period.

3. The UE according to claim 1, characterized in that In a case where a protocol data unit PDU session or a multiple access protocol data unit MA PDU session is established before the timer using the unavailable period is started, the control unit starts a PDU session release procedure for releasing the established PDU session or MA PDU session.

4. The UE according to claim 1, characterized in that The control unit does not start a protocol data unit (PDU) session establishment procedure during an operation using a timer for an unavailable period.

5. The UE according to claim 1, characterized in that In the operation using the unavailable period timer, When the transceiver receives a mobility management MM message and / or a session management SM message from the core network, The control unit ignores the MM message and / or the SM message.

6. The UE according to claim 1, characterized in that: The transceiver transmits a registration request message including the unavailable period when notified of the unavailable period from an upper layer.

7. An access and mobility management function AMF, comprising a control unit, a transceiver unit and a storage unit, wherein the AMF is characterized in that: When the transceiver stores the unavailable period in the storage unit, and receives a registration request message not including the unavailable period from the UE, the control unit deletes the unavailable period stored in the storage unit, The transceiver sends a login acceptance message including a timer value regardless of the unavailable period, The delegated network exposure function NEF deletion is unavailable during the period.

Images