User equipment (UE)

Abstract

The behavior of the UE when the NPN used for the local service rejects login is ambiguous. A user equipment (UE) is provided with a transmission / reception unit, a control unit, and a storage unit. The control unit manages the first list and the second list. The first list is a list of a stand-alone Non-Public Network (SNPN) in which connection to a local service is temporarily prohibited, and the second list is a list of SNPNs in which connection to the local service is permanently prohibited. The transmission / reception unit transmits a login request message to a network, and receives a login rejection message including a first reason value or a second reason value from the network. The controller receives a first reason value indicating that the SNPN is temporarily unauthorized, and when the controller receives the first reason value, the controller stores the SNPN ID in the first list stored in the storage based on the first reason value. The control unit receives a second reason value indicating that the SNPN is permanently unauthorized, and stores the SNPN ID in the second list stored in the storage unit on the basis of the second reason value when the second reason value is received.

Description

Technical Field

[0001] The present invention relates to a UE (User Equipment). Background Art

[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System) as the fifth generation (5G) mobile communication system is studied, and discussions are held to support new processes and new functions (see non-patent documents 1 to 4). In recent years, discussions on the use of local services in NPN (Non-Public Network) have become active (see non-patent document 5). 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.7.1 (2022-06); 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 TS23.122V17.7.1(2022-06); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 17) Non-patent document 5: 3GPP TR23.700-08V1.0.0(2022-05); 3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Study on enhanced support of Non-Public Networks; Phase 2(Release 18) Summary of the invention Problem that the invention aims to solve

[0004] In 5GS (5G System), in order to provide various services, 5GCN (5G Core Network) as a new core network is studied. It should be noted that in 5GS, the provision of non-public networks such as NPN (Non-Public Network) that can be used by specific users for specific purposes and the functions used to implement non-public networks are also studied.

[0005] Currently, the behavior of a UE when a login is rejected by an NPN used for local services is unclear. Specifically, the NPN used for local services is sometimes an SNPN and sometimes a PNI-NPN. In the current specification, there is a rejection reason value corresponding to an SNPN or a rejection reason value corresponding to a PNI-NPN, but there is no rejection reason value corresponding to an NPN used for local services.

[0006] One solution of the present invention is completed in view of the above situation, and its purpose is to clarify the behavior of UE when the NPN used for local services refuses to log in. Technical Solution

[0007] A user equipment (UE) according to one embodiment of the present invention comprises a transceiver and a control unit, wherein the UE is characterized in that the control unit manages a first list and a second list, wherein the first list is a list of stand-alone non-public networks (SNPN) whose connection to a local service is temporarily prohibited, and the second list is a list of SNPNs whose connection to a local service is permanently prohibited, wherein the transceiver sends a login request message to a network, and the transceiver receives a login rejection message including a first reason value or a second reason value from the network, wherein the first reason value is a reason value indicating that the SNPN is temporarily not authorized, and upon receiving the first reason value, the control unit stores the SNPN ID in the first list stored in the storage unit based on the first reason value, and the second reason value is a reason value indicating that the SNPN is permanently not authorized, and upon receiving the second reason value, the control unit stores the SNPN ID in the second list stored in the storage unit based on the second reason value.

[0008] A communication control method performed by a user equipment (UE) according to one embodiment of the present invention is characterized in that it includes the following steps: a step of managing a first list and a second list, wherein the first list is a list of independent non-public networks (SNPNs) temporarily prohibited from connecting to local services, and the second list is a list of SNPNs permanently prohibited from connecting to local services; a step of the UE sending a login request message to a network; a step of the UE receiving a login rejection message including a first reason value or a second reason value from the network, wherein the first reason value is a reason value indicating temporary non-authorization of the SNPN, and the second reason value is a reason value indicating permanent non-authorization of the SNPN; a step of the UE storing the SNPN ID in the first list stored by the UE based on the first reason value upon receiving the first reason value; and a step of the UE storing the SNPN ID in the second list stored by the UE based on the second reason value upon receiving the second reason value. Effects of the Invention

[0009] According to a solution of the present invention, the behavior of a UE when an NPN used for local services refuses to log in can be clarified. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] 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 3This 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. Figure 7 This is a diagram illustrating the non-login process led by the UE. Figure 8 is a diagram showing a network-led non-login process. Fig. 9 It is a diagram showing the UE-led NAS transmission process. Fig.10 This diagram explains the network-driven NAS transmission process. DETAILED DESCRIPTION

[0011] 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]

[0012] 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 configuration of the mobile communication system 1 .

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

[0014] In the following, these devices and functions are sometimes recorded with omitted symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0015] In addition, Figure 2It records: UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170 and other devices and functions, as well as interfaces connecting these devices and functions.

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

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

[0018] 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 that can perform wireless communication, such as a portable phone or a smart phone, or a terminal device that can connect to both EPS and 5GS. UE can have UICC (Universal Integrated Circuit Card) or eUICC (EmbeddedUICC). It should be noted that UE can be expressed as a user device or as a terminal device.

[0019] 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 with an abbreviated 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.

[0020] 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 redesigned for 5GS, and has different functions from the base station device (eNB) used in 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.

[0021] In addition, the non-3GPP access network can be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network can 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 can be an access network specified by 3GPP and can have TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP Gateway function).

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

[0023] In addition, in the following, access network_A and / or access network_B and / or the device included in access network_A and / or the device included in access network_B are sometimes referred to as access networks or access network devices.

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

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

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

[0027] 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) with the 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).

[0028] In addition, Figure 1The case where PDN and DN are the same is recorded in the text, 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 for each service. Moreover, PDN can include connected communication terminals. Therefore, connection with PDN can be connection with communication terminals and server devices configured in PDN. Moreover, sending and receiving user data with PDN can also be sending and receiving user data with communication terminals and server devices configured in PDN. It should be noted that PDN can be expressed as DN, and DN can also be expressed as PDN.

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

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

[0031] 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 and functions included in EPS, and devices and functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, 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 a MAC header, Ethernet (registered trademark) frame header, or other headers to send and receive user data sent and received by the UE.

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

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

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

[0035] It should be noted that in Figure 2 In order to simplify the drawings, each device and function is recorded as one, but multiple similar devices and functions may be configured in the mobile communication system 1. Specifically, multiple devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150 may be configured in the mobile communication system 1.

[0036] UPF_A235 is connected to DN, SMF, other UPFs, and access network. UPF_A235 can play the following roles: anchor for intra-RAT mobility or inter-RAT mobility, packet routing and forwarding, UL CL (Uplink Classifier) ​​function to support routing of multiple service flows for one DN, branching point function to support multi-homed PDU session, QoS (Quality of Service) processing for user plane, verification of uplink service, buffering of downlink packets, triggering function of downlink data notification, etc. In addition, UPF_A235 can be a relay device that acts as a gateway between DN and core network_B190 to transmit user data. It should be noted that UPF_A235 can be a gateway for IP communication and / or non-IP communication. Moreover, UPF_A235 may have the function of transmitting IP communication and the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways may be gateways that connect the core network_B190 to a single DN. It should be noted that UPF_A235 may have connectivity with other NFs and may also be connected to each device via other NFs.

[0037] It should be noted that between UPF_A235 and the access network, there may be UPF_C239 (also called branching point or uplink classifier) ​​as a UPF different from UPF_A235 as a device or NF. In the presence of UPF_C239, the PDU session between the UE and the DN is established via the access network, UPF_C239, and UPF_A235.

[0038] In addition, UPF130 may be the same device as UPF_A235. It should be noted that UPF130 and UPF_A235 may be described by omitting the reference numerals like UPF. [2. Configuration of each device]

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

[0040] It should be noted that each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device and each function that appears below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit can not only store the information originally set from the factory stage, but also store various information sent and received between devices and functions other than its own device and its own function (for example, UE and / or access network device and / or core network device and / or PDN and / or DN). 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 and functions included in 5GS and / or EPS when intercommunication between 5GS and EPS is performed. At this time, not only the data sent and received via the N26 interface can be stored, but also the data not sent and received via the N26 interface can be stored. [2.1. UE device configuration]

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

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

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

[0044] Reference Figure 2 To 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.

[0045] The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for various actions of the UE. [2.2.gNB device configuration]

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

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

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

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

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

[0051] Storage unit_B540 is a functional unit used to store programs, user data, control information, etc. required for various actions of gNB. [2.3.AMF device configuration]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0071] 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. [2.5. UPF device configuration]

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

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

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

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

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

[0077] 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, branch 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 (Downlink Data Notification) function, etc.

[0078] 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 that connect the core network_B to 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.

[0079] It should be noted that the user plane is user data sent and received between the UE and the network. The user plane can use a PDN connection or a PDU session 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 can also be expressed as U-Plane.

[0080] Moreover, the control plane is a control message sent and received for communication control of the UE, etc. The control plane can use the NAS (Non-Access-Stratum) signaling connection between the UE and the MME 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 the UE and the NG RAN and the N2 interface for transmission and reception. In the following, the control plane can be expressed as either Control Plane or C-Plane.

[0081] Furthermore, U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data, and may be composed of multiple bearers. Furthermore, C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages, and may be composed of multiple bearers. [2.6. Description of other devices and / or functions]

[0082] Next, other devices and / or functions are described.

[0083] 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 performing the sending, receiving, and / or processing of messages may mean that a device (network device and / or control device) within the network performs the sending, receiving, and / or processing of messages. Conversely, the device within the network performs the sending, receiving, and / or processing of messages may mean that the network performs the sending, receiving, and / or processing of messages. In addition, the network may also be referred to as NW.

[0084] Furthermore, the network may refer to a PLMN (Public Land Mobile Network) or a NPN (Non-Public Network) described later. Furthermore, the network selection may refer to a PLMN selection or a SNPN selection.

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

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

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

[0088] UDM (Unified Data Management) may also refer to a NF having the following functions: authentication credential processing function, user identification processing function, access authentication function, login / mobility management function, subscriber information management (subscription management) function, etc.

[0089] The SM (Session Management) message may refer to a NAS message used in the SM process. The SM message may be called a NAS (Non-Access-Stratum) SM message. The SM message may be a control message sent and received between the UE_A10 and the SMF_A230 via the AMF_A240. Moreover, the SM message may include: PDU session establishment request message, PDU session establishment accept message, PDU session establishment reject message, PDU session change request message, PDU session change command message, PDU session change complete message, PDU session change command reject message, PDU session change reject message, PDU session modification reject message, PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete message, etc.

[0090] 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 network.

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

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

[0093] 5GS (5G System) service may refer to a connection service provided using the core network B190. Moreover, 5GS service may be a service different from EPS service or the same as EPS service.

[0094] Non-5GS services may refer to services other than 5GS services, and may also include EPS services and / or non-EPS services.

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

[0096] The N1 mode refers to a mode in which UE_A10 is allowed to access the 5GC via the 5G access network. In other words, the N1 mode may also be a mode for sending and receiving messages using the N1 interface.

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

[0098] 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 IPv4 is used to send and receive data. When IPv6 is specified, it indicates that IPv6 is used to send and receive data. When IPv4v6 is specified, it indicates that IPv4 or IPv6 is used to send and receive data. When non-IP is specified, it indicates that communication is not using IP, but communication is carried out through a communication method other than IP.

[0099] A PDU (Protocol Data Unit) session can be defined as the association between a DN and a UE that provide a PDU connectivity service, but it can also be the connectivity established between a UE and an external gateway. The UE establishes a PDU session in 5GS via the access network_B and the core network_B, thereby being able to use the PDU session to send and receive user data with the DN. Here, the external gateway may refer to UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers configured in the DN. 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, access network identification information, and SSC mode (SSC mode), and may further include other information. Moreover, in the case of establishing multiple PDU sessions, each identification information corresponding to the PDU session establishment may be the same content or different content.

[0100] DNN (Data Network Name) can refer to 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 a PGW / UPF connected to the core network B190. Furthermore, DNN can also be equivalent to APN (Access Point Name).

[0101] The PDU (Protocol Data Unit) session type indicates the type of PDU session, including 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 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.

[0102] PLMN (Public land mobile network) refers to 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 Subscription Identity) can be a home PLMN (Home PLMN, HPLMN). Moreover, the UE can maintain an equivalent PLMN list (Equivalent PLMN list) for identifying one or more EPLMNs (Equivalent PLMNs) 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 has successfully logged in can be an RPLMN (Registered PLMN).

[0103] In addition, a registered PLMN refers to a PLMN in which the UE has registered.

[0104] In addition, an equivalent PLMN is a PLMN that is processed as the same PLMN as any PLMN in the network. For example, the equivalent PLMN may be one or more PLMNs that are processed as the same as the registered PLMN.

[0105] PLMN selection may refer to a process for a UE to select a PLMN. Here, PLMN selection may be implemented when the UE is connected to a PLMN. Here, PLMN selection may be referred to as a PLMN selection process or a PLMN selection procedure.

[0106] Here, a UE that is not operating in SNPN access mode or SNPN access operation mode may also perform PLMN selection. In addition, a UE that is operating in SNPN access mode or SNPN access operation mode may not perform PLMN selection. In addition, PLMN selection can be performed without logging in. In other words, PLMN selection can be performed when the UE has not completed logging in to the network. PLMN selection can have an automatic PLMN selection mode and a manual PLMN selection mode. It should be noted that PLMN selection can represent an automatic PLMN selection mode or a manual PLMN selection mode.

[0107] Tracking area refers to one or more ranges that can be represented as location information of UE_A10 managed by the core network. It should be noted that 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 TA (Tracking Area). The tracking area can be identified by TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.

[0108] Registration area (Registration area or login area) refers to 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.

[0109] UE ID refers to information used to identify the UE. For example, UE ID may be SUCI or SUPI or IMSI or GUTI or 5G-GUTI or IMEI or IMEISV or TMSI or 5G-S-TMSI. Alternatively, UE ID may also be other information configured in an application or network. Moreover, UE ID may also be information used to identify a user.

[0110] SUCI (Subscription Concealed Identifier) ​​may be a privacy preserving identifier including a concealed SUPI. In addition, SUCI may be composed of a SUPI Type, a Home Network Identifier, a Routing Indicator, a Protection Scheme Id, a Home Network Public Key Identifier, and a Scheme Output.

[0111] SUPI (Subscription Permanent Identifier) ​​can be a globally unique identifier assigned to each subscriber in the 5G system. SUPI can be defined as a SUPI type and IMSI or NSI (Network Specific Identifier) ​​or GCI (Global Cable Identifier) ​​or GLI (Global Line Identifier). In addition, the SUPI type may represent IMSI or NSI or GCI or GLI. That is, when the SUPI type represents IMSI, the SUPI may be composed of a SUPI type representing IMSI and an IMSI. Similarly, when the SUPI type represents NSI, the SUPI may be composed of a SUPI type representing NSI and an NSI. In addition, when the SUPI type represents GCI, the SUPI may be composed of a SUPI type representing GCI and an GCI. In addition, when the SUPI type represents GLI, the SUPI may be composed of a SUPI type representing GLI and an GLI.

[0112] IMSI (International Mobile Subscription Identity) can be composed of MCC (MobileContry Code), MNC (Mobile Network Code) and MSIN (Mobile Subscriber Identification Number: mobile device user identification number).

[0113] 5G-GUTI (5G Globally Unique Temporary Identifier) ​​can be information for providing an identifier of a UE that does not have the ambiguity of an ambiguous UE or a user's permanent identity. In addition, 5G-GUTI can be information that can identify the AMF and the network. In addition, 5G-GUTI can also be information used by the network and the UE to establish the identity of the UE. In addition, 5G-GUTI can be composed of two elements: one is an element that identifies the AMF to which the 5G-GUTI is assigned, and the other is an element that uniquely identifies the UE within the AMF to which the 5G-GUTI is assigned. The former can be GUAMI (Glovally Unique AMF Identifier), and the latter can be 5G-TMSI (5G-Temporary Mobile Subscriber Identity). That is, 5G-GUTI can be composed of GUAMI and 5G-TMSI.

[0114] IMEI (International Mobile Station Equipment Identity) can be composed of TAC (Type Allocation Code), SNR (Serial Number), CD (Check Digit) / SD (Spare Digit).

[0115] IMEISV (International Mobile station Equipment Identity and Software Version number) can be composed of TAC (Type Allocation Code), SNR (Serial Number) and SVN (Software Version Number).

[0116] 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier: 5G S-temporary mobile user identifier) ​​can also be shortened 5G-GUTI. In addition, 5G-S-TMSI can also enable more efficient wireless signaling processes (such as paging (also known as paging process), service request (also known as service request process)). In addition, for paging, 5G-S-TMSI can be used to page UE. 5G-S-TMSI can be composed of AMF Set ID, AMF Pointer and 5G-TMSI.

[0117] A MAC address (Media Access Control address) may be a hardware address of a device connected to a shared medium. Alternatively, a MAC address may be a unique identification number assigned to a UE or a network device.

[0118] EUI-64 (IEEE Extended Unique Identifier) ​​may be a 64-bit identifier standardized by IEEE. In addition, EUI-64 may also be used when automatically generating an IPv6 address.

[0119] PEI (Permanent Equipment Identifier) ​​can be information for identifying UE. In addition, PEI can be defined as PEI type and IMEI or IMEISV or MAC address or EUI-64. Here, PEI type can represent IMEI or IMEISV or MAC address or EUI-64. That is, when PEI type represents IMEI, PEI can be composed of PEI type representing IMEI and IMEI. Similarly, when PEI type represents IMEISV, PEI can be composed of PEI type representing IMEISV and IMEISV. In addition, when PEI type represents MAC address, PEI can be composed of PEI type representing MAC address and MAC address. In addition, when PEI type represents EUI-64, PEI can be composed of PEI type representing EUI-64 and EUI-64.

[0120] 5GS mobile identity may be an IE for providing SUCI or 5G-GUTI or IMEI or IMEISV or 5G-S-TMSI or MAC address or EUI-64. In addition, 5GS mobile identity may be referred to as 5GS mobile identity information element (5GS mobile identity IE (information element)).

[0121] NPN (Non-Public Network) is a non-public network used by specific users for specific purposes. There are two types of NPN: SNPN (Stand-alone Non-Public Network) and PNI-NPN (Public Network Integrated NPN). It should be noted that NPN can represent SNPN, PNI-NPN, or both.

[0122] SNPN refers to a network operated by an NPN operator and is not affected by the functional parts provided by the PLMN. In other words, SNPN is a network dedicated to NPN that is independent of the generally public PLMN. SNPN can be a network identified by a SNPN ID (SNPN identity). It should be noted that the SNPN ID can be information that combines the PLMN ID with the NID (Network Identifier). It should be noted that the PLMN ID used for the SNPN ID can be information ensured for a private network. For example, the MCC included in the PLMN ID can be 999. Moreover, when the UE has logged in to the SNPN, the logged-in SNPN can also be referred to as a logged-in SNPN or RSNPN (registered SNPN).

[0123] NID refers to information that identifies a network. SNPN can be identified by information that combines PLMN ID and NID. NID can be information that is unique within the SNPN or globally unique.

[0124] PNI-NPN refers to a network implemented using the functional part of PLMN. In other words, PNI-NPN is an NPN implemented virtually within the PLMN. Moreover, PNI-NPN is an NPN that can be generated via the PLMN. It should be noted that PNI-NPN can be implemented using the function of network slicing. Specifically, PNI-NPN can be a network that can be implemented by using a network slice assigned to NPN. In this case, PNI-NPN can be identified by S-NSSAI or by a combination of S-NSSAI and CAG ID. Moreover, PNI-NPN can be implemented using DN. Specifically, PNI-NPN can be a network implemented by using the DN used for NPN. In this case, PNI-NPN can be identified by DNN or by a combination of DNN and CAG ID.

[0125] CAG (Closed Access Groups) is a group used when implementing PNI-NPN. In addition, CAG can be a group identified by CAG ID. In addition, CAG can be used to not attempt to access the network slice allocated to NPN from UEs that do not allow NPN.

[0126] CAG ID refers to information for identifying CAG within the PLMN. Moreover, CAG ID is an identifier unique within the PLMN.

[0127] SNPN enabled UE may refer to a UE that can utilize SNPN. SNPN enabled UE may store at least one piece of information related to SNPN. In other words, the setting information of the SNPN enabled UE may include information indicating that SNPN can be utilized. Moreover, the SNPN enabled UE may support the SNPN access mode or the SNPN access operation mode. In other words, the SNPN enabled UE may operate in the SNPN access mode or the SNPN access operation mode.

[0128] SNPN access mode may refer to a mode for the UE to select SNPN. In addition, the SNPN access mode may also be a mode in which the UE logs in to the SNPN. Moreover, the SNPN access mode may also be a mode in which the UE connects to the SNPN. In other words, a UE operating in the SNPN access mode may only select SNPN when selecting a network. In more detail, a UE operating in the SNPN access mode may only select SNPN via the Uu interface when selecting a network. In other words, a UE operating in the SNPN access mode may select SNPN instead of PLMN when selecting a network. Here, a UE operating in the SNPN access mode may also be expressed as a UE in the SNPN access mode. Moreover, a UE in the SNPN access mode may also be a SNPN valid UE.

[0129] SNPN access operation mode refers to the SNPN access mode or the mode of connecting to the SNPN via non-3GPP access. Here, the "non-3GPP access" in SNPN may refer to the situation where the UE is connected to the SNPN via a PLMN. In addition, when operating in the SNPN access mode, the UE may operate in the SNPN access operation mode. In addition, when not operating in the SNPN access mode, the UE may not operate in the SNPN access operation mode. Moreover, the UE in the SNPN access mode may also be the UE in the SNPN access operation mode. It should be noted that the SNPN access operation mode may also be renamed as the SNPN access mode.

[0130] SNPN selection may refer to a process for the UE to select a SNPN. In addition, SNPN selection may be a process implemented when the UE is connected to the SNPN. In addition, SNPN selection may be referred to as a SNPN selection process or a SNPN selection procedure. In addition, SNPN selection may be a process for the UE to select a SNPN. In addition, SNPN selection may also be a process implemented when the UE is connected to the SNPN.

[0131] Here, a UE operating in SNPN access mode or SNPN access operation mode may perform SNPN selection. In addition, a UE not operating in SNPN access mode or SNPN access operation mode may not perform SNPN selection. In addition, SNPN selection may have an automatic SNPN selection mode (automatic SNPN selection mode) and a manual SNPN selection mode (manual SNPN selection mode). In addition, SNPN selection may be performed without logging in. In other words, SNPN selection may be performed when the UE has not completed logging in to the network. It should be noted that SNPN selection may represent an automatic SNPN selection mode or a manual SNPN selection mode.

[0132] An equivalent SNPN may refer to an SNPN that is processed as the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more SNPNs that are processed as the same as a registered SNPN. Moreover, an equivalent SNPN may be a PLMN that is processed as the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more PLMNs that are processed as the same as a registered SNPN.

[0133] Moreover, the equivalent SNPN may be one or more SNPNs identified by the same PLMN ID as any SNPN, or may be a PLMN. For example, the equivalent SNPN may be one or more SNPNs identified by the same PLMN ID as the logged-in SNPN, or may be a PLMN. Moreover, the equivalent SNPN may be a PLMN identified by the same PLMN ID as the logged-in SNPN and an equivalent PLMN of the PLMN.

[0134] SOR is the abbreviation of Steering of Roaming, which refers to a method and technology for prompting the UE to roam to a network of a priority roaming destination (or a recommended roaming destination) indicated by the HPLMN.

[0135] SOR-CMCI (Steering of roaming connected mode control information) refers to the HPLMN information used to control the timing of the transition from 5GMM connected mode to 5GMM non-connected mode in order for the UE to perform SOR. SOR-CMCI can be included in the SOR information and / or SOR transparent container, and can also be included in other information elements for transmission and reception.

[0136] In addition, SOR-CMCI can be information that can control the timing of the network such as HPLMN to switch the UE in connected mode to non-connected mode for SOR. SOR-CMCI can be information based on the operator policy and / or HPLMN policy. SOR-CMCI can also be information set in each device, or it can be information notified to the UE from the NW.

[0137] In addition, the SOR-CMCI may be information provided by the SOR application function (Steering of Roaming application function; SOR-AF). In addition, the SOR-CMCI may also be information provided by the SOR-AF to the UE via the UDM and AMF.

[0138] In addition, the SOR-CMCI may be included in a secured packet. In addition, the SOR-CMCI may be included in the SOR information.

[0139] Furthermore, a SOR-CMCI may be composed of more than one SOR-CMCI rule.

[0140] The SOR-CMCI rule may be composed of a reference information (standard information) and a first timer value. Moreover, the reference information (standard information) and the first timer value may be associated. Here, the reference information may be referred to as a criterion.

[0141] Here, the benchmark information may be composed of a benchmark belonging to a PDU session (PDU session attribute type criterion) and / or a benchmark related to a service type (service type criterion) and / or a SOR security check criterion (SOR security check criterion) and / or a benchmark belonging to all types (match all type criterion). In addition, the benchmark information may be composed of a benchmark related to a local service.

[0142] Here, the benchmark associated with the local service may be a benchmark when the local service is used. In addition, the benchmark associated with the local service may be a benchmark used when connected to a hosting network. In addition, the benchmark associated with the local service may be simply referred to as a local service.

[0143] Moreover, the benchmark belonging to the PDU session can be benchmark information for identifying the corresponding PDU session. Specifically, the benchmark belonging to the PDU session can be composed of the DNN of the PDU session (DNN of the PDU session) or the S-NSSAI STT of the PDU session (S-NSSAI STT of the PDU session) or the STT and SD of the S-NSSAI of the PDU session (S-NSSAI SSTand SD of the PDU session). In addition, the benchmark belonging to the PDU session can be composed of benchmarks related to local services.

[0144] Furthermore, the benchmark related to the service type may be benchmark information for identifying the corresponding service. Specifically, the benchmark related to the service type may be composed of IMS registration related signaling, or MMTEL voice call, or MMTEL video call, or SMS over NAS or SMSoIP. Furthermore, the benchmark related to the service type may be composed of benchmarks related to local services.

[0145] Furthermore, the SOR security confirmation criterion may be composed of a SOR security check not successful. Furthermore, the SOR security confirmation criterion may be composed of a criterion related to the local service.

[0146] Furthermore, the reference belonging to all types may be reference information that is consistent (matched) in any state. Furthermore, the reference belonging to all types may be composed of references related to local services.

[0147] In addition, when multiple PDU sessions are established, the SOR-CMCI may include multiple SOR-CMCI rules. Furthermore, when multiple services are executed, multiple SOR-CMCI rules may also be included.

[0148] The SOR information (Steering of roaming information) may refer to the SOR information composed of information protected by the HPLMN. The SOR information may include information indicating whether to request an Ack (acknowledgement) as a response indicating successful reception of the roaming steering information from the UE.

[0149] The SOR information may include a list of recommended (or preferred) combinations of PLMN and access technology and information indicating that it (the list) is included, or a security-protected group and information indicating that it (the group) is included, or information indicating that the list of recommended combinations of PLMN and access technology is not included in the SOR information because there is no need to change the list of recommended combinations of PLMN and access technology stored in the UE.

[0150] The SOR information and an Ack as a response indicating that the UE successfully receives the SOR information may be included in a SOR transparent container information element included in a NAS message for transmission and reception.

[0151] Each device may manage and / or store multiple SOR-CMCIs for the UE, and may also manage and / or store one SOR-CMCI for the UE.

[0152] The first timer refers to a timer used to determine the timing for the UE in connected mode to transition to non-connected mode for SOR. The first timer may be a Tsor-cm timer of 3GPP. The first timer may be managed by the UE and / or the NW. The first timer may be managed per PDU session, per access type, per combination of each PDU session and access type, per service type, per PLMN, or per UE. In addition, the timer value set to the first timer may also be referred to as the first timer value.

[0153] In other words, more than one first timer may be managed in one UE, and one first timer may be managed in one UE. The first timer managed by the UE may store the PDU session ID and / or information indicating the access type and / or information indicating the combination of the PDU session and the access type and / or the service type and / or the PLMN ID in association.

[0154] The first timer value may be associated with each reference. In addition, the first timer value may also represent the time the UE waits before releasing the PDU session or service and entering an idle state. In addition, the first timer value may be a value for a Tsor-cm timer.

[0155] Based on the SOR-CMCI used when selecting the timer value to be set for the first timer, the benchmark corresponding to the selected timer value and / or the information belonging to the PDU session included in the benchmark and / or the information indicating the service type included in the benchmark and / or the information indicating the priority corresponding to the benchmark can be managed in correspondence with the first timer and / or the first timer value.

[0156] These PDU sessions identified by the information associated with the first timer or the PDU sessions using the information associated with the first timer can be referred to as PDU sessions associated with the first timer, and the services identified by the information associated with the first timer can also be referred to as services associated with the first timer.

[0157] It should be noted that, here, managing the first timer means starting and / or stopping and / or expiring and / or executing the first timer. In other words, the UE and / or NW managing the first timer means that the UE and / or NW starts and / or stops and / or expires and / or executes the first timer, and the state in which the UE and / or NW is managing the first timer means that the UE and / or NW is executing the first timer.

[0158] For example, the UE and / or NW may manage the first timer for each PDU session when multiple PDU sessions are established, or may manage only one first timer.

[0159] Moreover, for example, when the UE and / or NW establish a first PDU session and a second PDU session on 3GPP access, and establish a third PDU session and a fourth PDU session on non-3GPP access, the first timer associated with the 3GPP access and the first timer associated with the non-3GPP access can be managed, and multiple first timers associated with the first to fourth PDU sessions respectively can be managed at the same time.

[0160] Moreover, for example, when the UE and / or NW establish a MA PDU (Multi Access Protocol Data Unit) session for establishing user plane resources on both 3GPP access and non-3GPP access, the UE and / or NW can manage the first timer corresponding to the MA PDU session, and can also manage the first timer associated with the 3GPP access and the first timer associated with the non-3GPP access at the same time.

[0161] The temporarily forbidden SNPN list ("temporarily forbidden SNPNs" list) can also be managed independently for each access type. That is, the temporarily forbidden SNPN list can be managed for each 3GPP access or non-3GPP access. The temporarily forbidden SNPN list can be a list of SNPNs to which the UE cannot temporarily connect. In addition, in the case where the UE supports onboarding services in SNPNs, an additional "temporarily forbidden SNPNs" list for onboarding services can be managed.

[0162] In addition, when the UE supports local services, an additional list of SNPNs that are temporarily prohibited for local services can be managed.

[0163] The permanently forbidden SNPN list ("permanently forbidden SNPNs" list) can be managed independently for each access type. That is, the permanently forbidden SNPN list can be managed for each 3GPP access or non-3GPP access. The permanently forbidden SNPN list can be a list of SNPNs to which the UE cannot permanently connect. In addition, in the case where the UE supports onboarding services in SNPNs, an additional "permanently forbidden SNPNs" list for onboarding services can be managed.

[0164] In addition, when the UE supports local services, an additional list of SNPNs that are permanently prohibited for local services can be managed.

[0165] Furthermore, the UE may not be able to start the registration procedure for SNPNs in the temporarily banned SNPN list or the permanently banned SNPN list.

[0166] The list of SNPNs temporarily prohibited for local services may be used when the UE supports local services. The list of SNPNs temporarily prohibited for local services may be an additional list of SNPNs temporarily prohibited for local services. The list of SNPNs temporarily prohibited for local services may be a list of SNPNs providing local services to which the UE cannot temporarily connect.

[0167] In addition, the list of SNPNs temporarily prohibited for local service can be managed independently for each access type. That is, the list of SNPNs temporarily prohibited for local service can be managed for each 3GPP access or non-3GPP access.

[0168] The list of SNPNs permanently prohibited for local services may be used when the UE supports local services. The list of SNPNs permanently prohibited for local services may be an additional list of SNPNs permanently prohibited for local services. The list of SNPNs permanently prohibited for local services may be a list of SNPNs providing local services to which the UE cannot permanently connect.

[0169] In addition, the list of SNPNs permanently barred for local services can be managed independently for each access type. That is, the list of SNPNs permanently barred for local services can be managed for each 3GPP access or non-3GPP access.

[0170] The list of forbidden hosted networks may be used if the UE supports local services. The list of forbidden hosted networks may be a list of hosted networks to which the UE cannot connect.

[0171] In addition, the list of barred hosted networks can be managed independently per access type. That is, the list of barred hosted networks can be managed per 3GPP access or non-3GPP access.

[0172] Additionally, the list of banned hosted networks may also be managed as a list of temporarily banned hosted networks and / or a list of permanently banned hosted networks.

[0173] Localized services may refer to services provided in a specific / restricted area. In addition, local services may also be time-limited. Local services may also be referred to as local services. In addition, local services may also be implemented via applications such as live or on-demand voice or video streaming or video games or IMS. In addition, local services may also be implemented via connectivity such as UE to UE or UE to DN.

[0174] Additionally, local services can be referred to as managed networks. Additionally, local services can be provided by managed networks. Additionally, supporting local services can be referred to as supporting managed networks.

[0175] A localized service provider may refer to an application provider or network operator that localizes services and provides them to end users via a hosted network. In addition, a local service provider may also be an application provider or network operator that provides local services. In addition, a local service provider may also be a DN. In addition, a local service provider may also be a core network.

[0176] A hosted network may refer to a network that provides a connection to a local service. In addition, a hosted network may also be an NPN. Here, the NPN may be an SNPN or a PNI-NPN.

[0177] In addition, managed networks can be renamed as local services. In addition, supporting managed networks can be renamed as supporting local services.

[0178] The home network may be a network that has a subscription or certificate of the UE currently in use. In addition, the home network may be a PLMN or an NPN. Here, the NPN may be an SNPN or a PNI-NPN.

[0179] A home network service may refer to a service provided to a UE based on a subscription agreed upon with a home network operator. In addition, a home network service may also refer to a service provided by a home network. [2.7. Description of identification information in this embodiment]

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

[0181] First, the first identification information refers to information used to identify the SNPN. The first identification information may be the SNPN ID. In addition, the first identification information may be information combining the PLMN ID with the NID. Here, the PLMN ID may be composed of the MCC and the MNC. Moreover, the PLMN ID may be information within the 5GS mobile identity.

[0182] Next, the second identification information may refer to information indicating whether a closed access group (CAG) is supported. The second identification information may also be information indicating support for CAG. In addition, the second identification information may also be information indicating that CAG is not supported. In addition, the second identification information may also be a 5GMM capability. In addition, the second identification information may also be information included in the 5GMM capability.

[0183] Next, the third identification information may refer to information indicating whether a hosted network is supported. The third identification information may also be information indicating support for a hosted network. In addition, the third identification information may also be information indicating that a hosted network is not supported. In addition, the third identification information may also be a 5GMM capability. In addition, the third identification information may also be information included in the 5GMM capability.

[0184] In addition, the third identification information may also be information indicating whether the local service is supported. The third identification information may also be information indicating that the local service is supported. In addition, the third identification information may also be information indicating that the local service is not supported.

[0185] In addition, the third identification information may also be information indicating a request for use of a managed network. In other words, the third identification information may also be information indicating a request for connection to a managed network. In addition, the third identification information may also be information indicating a request for use of a local service. In other words, the third identification information may also be information indicating a request for connection to a local service.

[0186] In addition, the third identification information may also be information indicating a request for authentication and / or authorization to the hosting network. In addition, the third identification information may also be information indicating a request for authentication and / or authorization to the local service.

[0187] Next, the tenth identification information refers to SOR-CMCI. The tenth identification information may also be composed of one or more of the eleventh identification information and / or the twelfth identification information and / or the thirteenth identification information.

[0188] Next, the eleventh identification information refers to the SOR-CMCI rule. The eleventh identification information may also be composed of one twelfth identification information and one thirteenth identification information. In addition, the eleventh identification information may also be information included in the tenth identification information.

[0189] Next, the twelfth identification information refers to a criterion. The twelfth identification information may also be information included in the tenth identification information and / or the eleventh identification information.

[0190] In addition, the twelfth identification information may be composed of a criterion belonging to a PDU session (PDU session attribute type criterion) and / or a criterion related to a service type (service type criterion) and / or a SOR security check criterion (SOR security check criterion) and / or a criterion belonging to all types (match all type criterion). In addition, the criterion information may also be composed of a criterion related to a local service.

[0191] Here, the benchmark related to the local service may be a benchmark when the local service is used. In addition, the benchmark related to the local service may also be a benchmark used when connected to a managed network. In addition, the benchmark related to the local service may also be referred to as a benchmark representing the local service. In addition, the benchmark related to the local service may also be referred to as simply the local service.

[0192] Moreover, the benchmark belonging to the PDU session can be benchmark information for identifying the corresponding PDU session. Specifically, the benchmark belonging to the PDU session can be composed of the DNN of the PDU session, or the S-NSSAI STT of the PDU session, or the STT and SD of the S-NSSAI of the PDU session. In addition, the benchmark belonging to the PDU session can be composed of benchmarks related to local services.

[0193] Moreover, the benchmark related to the service type may be benchmark information for identifying the corresponding service. Specifically, the benchmark related to the service type may be composed of IMS login related signaling, or MMTEL voice call, or MMTEL video call, or SMS over NAS or SMSoIP. In addition, the benchmark related to the service type may be composed of benchmarks related to local services.

[0194] Furthermore, the SOR safety confirmation criterion may be constituted by the SOR safety check being unsuccessful. In addition, the SOR safety confirmation criterion may also be constituted by a criterion related to the local service.

[0195] Furthermore, the reference belonging to all types may be reference information that is consistent (matched) in any state. Furthermore, the reference belonging to all types may be composed of references related to local services.

[0196] Next, the thirteenth identification information refers to the first timer value. In addition, the thirteenth identification information may also be information included in the tenth identification information or the eleventh identification information.

[0197] In other words, the thirteenth identification information may be a timer value of the Tsor-cm timer. In addition, the thirteenth identification information may also be associated with the twelfth identification information. In addition, the thirteenth identification information may also indicate the time that the UE should wait before releasing the PDU session or service and entering the idle state.

[0198] In addition, the thirteenth identification information may be a value that is different for each UE.

[0199] In addition, the thirteenth identification information may also be a value that is different for each group of multiple UEs. In other words, the thirteenth identification information may also be a value that is different for each UE group including more than one UE. For example, when there are UE1, UE2, UE3, and UE4, UE1 and UE2 are UE group 1, and UE3 and UE4 are UE group 2, the thirteenth identification information for UE1 and UE2 (or UE group 1) may be timer value 1, and the thirteenth identification information for UE3 and UE4 (or UE group 2) may be timer value 2. That is, the thirteenth identification information may also be information including multiple timer values.

[0200] Next, the fourteenth identification information may refer to a reason value indicating that the local service has ended. In other words, the fourteenth identification information may also be a reason value indicating that the local service has become unavailable. The fourteenth identification information may also be a 5GMM reason value (also called a 5GMM cause value). In addition, the fourteenth identification information may also be information included in a 5GMM reason value.

[0201] Furthermore, the fourteenth identification information may be a reason value indicating that the hosted network has been stopped. In other words, the fourteenth identification information may be a reason value indicating that the hosted network has become unavailable.

[0202] Next, the fifteenth identification information may be information indicating a range of a registration wait time. The fifteenth identification information may also be a registration wait range. Here, the fifteenth identification information may also include a minimum registration wait time and a maximum registration wait time.

[0203] Furthermore, the fifteenth identification information may be information indicating a range of waiting time until the user returns to the home network. Here, the fifteenth identification information may include a minimum value and a maximum value.

[0204] In addition, the UE may also generate a random numerical value within the range of the minimum value and the maximum value of the fifteenth identification information. In addition, the numerical value generated using the fifteenth identification information may also be used as a timer value. That is, the UE may also start the timer using the timer value as the numerical value generated using the fifteenth identification information.

[0205] Next, the sixteenth identification information refers to a timer value. The sixteenth identification information may be a timer value indicating a time when the MM process including the login process is not started. For example, it may be that during the execution of the timer using the timer value indicated by the sixteenth identification information, the UE cannot start the MM process including the login process. Moreover, it may also be that based on the expiration of the timer using the timer value indicated by the sixteenth identification information, the UE starts the MM process including the login process.

[0206] In addition, the sixteenth identification information may also indicate a time. Specifically, the sixteenth identification information may also indicate a time when the MM process is not started. For example, it may be that the UE cannot start the MM process before the time indicated by the sixteenth identification information, or it may be that the UE can start the MM process when the time indicated by the sixteenth identification information has passed.

[0207] Next, the seventeenth identification information may refer to a reason value indicating that the hosted network is not authorized. The seventeenth identification information may also be a 5GMM reason value. In addition, the seventeenth identification information may also be information included in the 5GMM reason value.

[0208] Furthermore, the seventeenth identification information may be a reason value indicating that the local service is not permitted. In other words, the seventeenth identification information may be a reason value indicating that the connection to the hosted network is not permitted.

[0209] Next, the eighteenth identification information may refer to a reason value indicating that the SNPN is temporarily not authorized. The eighteenth identification information may also be #74 (Temporarily not authorized for this SNPN: temporarily not authorized for this SNPN). In addition, the eighteenth identification information may also be a 5GMM reason value. In addition, the eighteenth identification information may also be information included in the 5GMM reason value.

[0210] Next, the nineteenth identification information may refer to a reason value indicating that the SNPN is permanently not authorized. The nineteenth identification information may also be #75 (Permanently not authorized for this SNPN: permanently not authorized for this SNPN). In addition, the nineteenth identification information may also be a 5GMM reason value. In addition, the nineteenth identification information may also be information included in a 5GMM reason value.

[0211] Next, the twentieth identification information may be a list including one or more CAG IDs. The twentieth identification information may also be a CAG information list. In addition, the twentieth identification information may also be an extended CAG information list.

[0212] In addition, the twentieth identification information may also be a list including one or more CAG IDs for local services. In addition, the twentieth identification information may also be a CAG information list for local services. In addition, the twentieth identification information may also be an extended CAG information list for local services.

[0213] In addition, the twentieth identification information may also be a list including one or more CAG IDs for the managed network. In addition, the twentieth identification information may also be a CAG information list for the managed network. In addition, the twentieth identification information may also be an extended CAG information list for the managed network.

[0214] Next, the twenty-first identification information may be a reason value indicating that CAG is not authorized or only CAG cells are authorized. The twenty-first identification information may also be #76 (Not authorized for this CAG or authorized for CAG cells only: Not authorized for this CAG or only CAG cells are authorized). In addition, the twenty-first identification information may also be a 5GMM reason value. In addition, the twenty-first identification information may also be information included in the 5GMM reason value.

[0215] Next, the twenty-second identification information may be a list of identifiers of available managed networks. The twenty-second identification information may also be a list including SNPN IDs and / or CAG IDs. Here, the managed network may be an NPN. In other words, the managed network may be an SNPN or a PNI-NPN.

[0216] Next, the twenty-third identification information may be a list including identifiers of unavailable managed networks. The twenty-third identification information may also be a list including SNPN IDs and / or CAG IDs. Here, the managed network may be an NPN. In other words, the managed network may be an SNPN or a PNI-NPN. [3. Description of Processes Used in Each Embodiment]

[0217] Next, the procedures used in each embodiment are described. It should be noted that the procedures used in each embodiment include a registration procedure, a UE-initiated de-registration procedure, a network-initiated de-registration procedure, a UE-initiated NAS transport procedure, and a network-initiated NAS transport procedure. Each procedure is described below.

[0218] It should be noted that, in each embodiment, Figure 2As described above, the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are respectively configured as the same device (that is, the same physical hardware or 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 (that is, different physical hardware or 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]

[0219] First, use Figure 6 The registration procedure is described. The registration procedure is a process in 5GS. In this chapter, this process refers to the registration procedure. The registration procedure is a process for the UE to take the lead in logging in to the access network_B and / or core network_B and / or DN. If the UE is in a state where it is not logged in to the network, this process can be performed at any time, such as when the power is turned on. In other words, if the UE is in a non-logged-in state (RM-DEREGISTERED state), this process can be started at any time. In addition, each device (especially UE and AMF) can be transformed into a registered state (RM-REGISTERED state) based on the completion of the registration process. It should be noted that the registration status can be managed by each device for each access. Specifically, each device can independently manage the registration status for 3GPP access (registered state or non-registered state) and the registration status for non-3GPP access.

[0220] In addition, the registration procedure may be a registration procedure for initial registration. In addition, the registration procedure may be a registration procedure for mobility and periodic registration update.

[0221] Moreover, the login process may also be a process for updating the location login information of the UE in the network and / or periodically notifying the network of the status of the UE and / or updating specific parameters related to the UE in the network.

[0222] In addition, this process can be a login process for a local service or a login process for a hosted network.

[0223] The UE may start the login process when performing cross-TA (Tracking Area) mobility. In other words, the UE may also start the login process when it moves to a TA different from the TA shown by the maintained TA list. Furthermore, the UE may also start the login process when the context of each device needs to be updated due to the disconnection or disabling of the PDU session. Furthermore, the UE may also start the login process when the UE's capability information and / or preference selection related to the establishment of the PDU session changes. Furthermore, the UE may also start the login process periodically. Furthermore, the UE may also start the login process based on the completion of the UE setting update process. It should be noted that the UE can perform the login process at any timing and is not limited to this.

[0224] Furthermore, the UE may periodically start the login process even in the logged-in state.

[0225] It should be noted that the login process performed based on the mobility of the UE and the login process performed periodically may also be expressed as a login process for mobility and login update. In other words, the login process for mobility and login update may be a login process performed based on the mobility of the UE or a login process performed periodically. Moreover, the login process for mobility and login update may also be a login process performed based on the setting update of the UE. Moreover, the login process for mobility and login update may also be a login process performed to establish a communication path for sending and receiving user data. Moreover, the login process for mobility and login update may also be a login process performed based on a request from the network. Moreover, in other words, the login process for mobility and login update may be a login process other than the login process for initial login.

[0226] Next, each step of the login process is described. It should be noted that the login process described below can be a login process for initial login or a login process for mobility and login update.

[0227] First, the UE starts the login process by sending a registration request message (S800)(S802)(S804) to the AMF. Specifically, the UE sends an RRC (Radio Resource Control) message including a login request message to the 5G AN (or gNB) (S800). It should be noted that the login request message is a NAS message. In addition, the RRC message can be a control message sent and received between the UE and the 5G AN (or gNB). In addition, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. It should be noted that the NAS layer is a higher layer than the RRC layer.

[0228] Here, the UE may include one or more of the first to third identification information in a login request message and / or an RRC message to send. In more detail, the UE may include one or more of the first to third identification information in a login request message and / or an RRC message to send, or may include it in a control message different from them, such as a control message of a layer lower than the RRC layer (e.g., a MAC layer, an RLC layer, a PDCP layer) to send.

[0229] It should be noted that the UE can indicate to the network that the UE supports each function by sending these identification information, and can also indicate the UE's request. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, or as different identification information.

[0230] Moreover, the UE can indicate to the network the content represented by the identification information included in the login request message by including one or more of the first to third identification information in the login request message.

[0231] It should be noted that the UE can select and determine whether to include one or more of the first to third identification information in the login request message based on the subscriber information and / or the network status and / or the user's login information and / or the context maintained by the UE.

[0232] It should be noted that the UE may also include identification information other than the first to third identification information in the login request message and send it.

[0233] When the 5G AN (or gNB) receives the RRC message including the login request message, it selects the AMF to which the login request message is transmitted (S802). It should be noted that the 5G AN (or gNB) can select the AMF based on the information included in the login request message and / or the RRC message. The 5G AN (or gNB) extracts the login request message from the received RRC message and transmits the login request message to the selected AMF (S804).

[0234] The AMF can perform the first condition determination upon receiving the login request message. The first condition determination is used to determine whether the network (or AMF) accepts the UE's request. If the first condition determination is true, the AMF starts Figure 6 In contrast, when the first condition is false, the process starts Figure 6 (B) process.

[0235] It should be noted that the first conditional determination 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, etc. For example, it may be that when the network allows the UE's request, the first conditional determination is true, and when the network does not allow the UE's request, the first conditional determination is false. In addition, it may also be that when the network of the UE's login destination and / or the device within the network supports the function requested by the UE, the first conditional determination is true, and when the function requested by the UE is not supported, the first conditional determination is false. Moreover, it may also be that when the identification information sent and received is allowed, the first conditional determination is true, and when the identification information sent and received is not allowed, the first conditional determination is false. It should be noted that the conditions for determining the truth or falsehood of the first conditional determination may not be limited to the conditions described above.

[0236] First, the case where the first condition is judged to be true is described. Figure 6 In the process (A), the AMF sends a Registration accept message to the UE via the 5G AN (or gNB) as a response message to the Registration request message (S806). It should be noted that the Registration accept message is a NAS message sent and received on the N1 interface, but is included in the RRC message between the UE and the 5G AN (gNB).

[0237] The AMF may include one or more of the tenth to twenty-third identification information in the login acceptance message. It should be noted that the AMF may indicate that the network supports each function by sending these identification information, and may also indicate that the UE's request is accepted. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information may constitute one or more identification information. 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.

[0238] Moreover, the AMF can indicate to the UE the content represented by the identification information by including one or more of the tenth to twenty-third identification information in the login acceptance message. In addition, the AMF can also indicate the content of the identification information to the UE by sending a login acceptance message.

[0239] It should be noted that AMF can select and determine whether to include one or more of the tenth to twenty-third identification information in the login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF.

[0240] It should be noted that AMF can also include identification information other than the tenth to twenty-third identification information in the login acceptance message and send it.

[0241] In addition, the AMF can indicate that the UE's request is accepted by sending a login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF.

[0242] Furthermore, the AMF may include information indicating that part of the UE's request is rejected in the login acceptance message, or may indicate the reason why part of the UE's request is rejected by sending information indicating that part of the UE's request is rejected. Furthermore, the UE may identify the reason why part of the UE's request is rejected by receiving information indicating that part of the UE's request is rejected. It should be noted that the reason for rejection may be information indicating that the content represented by the identification information received by the AMF is not allowed.

[0243] Next, the UE receives a login acceptance message from the AMF via the 5G AN (gNB) (S806). By receiving the login acceptance message, the UE can identify that the UE's request based on the login request message is accepted and the contents of various identification information included in the login acceptance message.

[0244] Next, the UE may send a login completion message to the AMF via the 5G AN (gNB) as a response message to the login acceptance message, or may not do so (S808). Here, the login completion message is a NAS message sent and received on the N1 interface, but is included in the RRC message between the UE and the 5G AN (gNB).

[0245] Next, the AMF may or may not receive a login completion message via the 5G AN (gNB) (S808).

[0246] Each device completes the login based on the sending and receiving of the login acceptance message and / or the login completion message. Figure 6 (A) process.

[0247] Next, the case where the first condition is judged to be false is described. Figure 6In the process (B), the AMF sends a Registration reject message to the UE via the 5G AN (gNB) as a response message to the Registration Request message (S810). Here, the Registration reject message is a NAS message sent and received on the N1 interface, but is included in the RRC message between the UE and the 5G AN (gNB).

[0248] Here, the AMF may include one or more of the tenth to twenty-third identification information in the login rejection message. Moreover, the AMF may indicate that the UE's request is rejected by sending these identification information, and may also indicate the reason why the UE's request is rejected.

[0249] Moreover, the AMF may indicate to the UE the content represented by the identification information included in the login rejection message by including one or more of the tenth to twenty-third identification information in the login rejection message. In addition, the AMF may also indicate the content of these identification information to the UE by sending a login rejection message.

[0250] It should be noted that AMF can select and determine whether to include one or more of the tenth to twenty-third identification information in the login rejection message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF.

[0251] Furthermore, the AMF may indicate that the request of the UE based on the login request message is rejected by sending a login rejection message. Furthermore, the AMF may include information indicating the reason for rejection in the login rejection message and may also indicate the reason for rejection by sending the reason for rejection. Furthermore, the UE may identify the reason why the UE's request is rejected by receiving information indicating the reason why the UE's request is rejected. It should be noted that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not allowed.

[0252] Next, the UE receives a login rejection message from the AMF via the 5G AN (gNB) (S810). By receiving the login rejection message, the UE can identify that the UE's request based on the login request message is rejected and the contents of various identification information included in the login rejection message.

[0253] In addition, the UE may also recognize that the UE's request is rejected if it does not receive a login rejection message after a specified period of time has passed after sending the login request message.

[0254] Each device completes the process (B) in this process based on the transmission and reception of the login rejection message.

[0255] It should be noted that sometimes it will be suspended Figure 6 (A) The process starts Figure 6 (B) process.

[0256] Each device is based on Figure 6 The login process is completed by completing the process (A) or (B). It should be noted that each device can also be based on Figure 6 The UE is logged into the network (RM_REGISTERED state) upon completion of the (A) process. Figure 6 The completion of process (B) maintains the state where the UE is not logged into the network (RM_DEREGISTERED state), or it can be transformed into the state where the UE is not logged into the network.

[0257] Furthermore, each device may perform 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 portion of the UE's request was rejected is sent and received. Furthermore, each device may perform this process again based on the reason why the UE's request was rejected, and may also perform the login process on the core network_B or other cells.

[0258] Furthermore, the UE may store the identification information received together with the registration accept message or the registration reject message based on the completion of the registration procedure, and may also identify the determination of the network. [3.2. Non-login process]

[0259] Next, the de-registration procedure is described. In this chapter, this procedure refers to the de-registration procedure. The de-registration procedure is a process initiated by the UE or the network and is used to deregister the UE. The de-registration procedure can also be a process used to make the UE state a de-registration state.

[0260] If the UE is in a state of logging in to the network, the UE and the network can perform this process at any timing. In other words, if the UE is in a logged-in state, the UE and the network can start this process at any timing. In addition, each device (particularly the UE and the AMF) can transition to a non-logged-in state based on the completion of the non-logged-in process.

[0261] Moreover, devices within the core network such as AMF can start this process based on updates to network settings and / or updates to operator policies. It should be noted that the trigger for this process can be the detection of UE mobility, the detection of changes in the status of the UE and / or access network and / or core network, or changes in the status of a network slice. Moreover, the trigger for this process can be the reception of a request from the DN and / or the application server of the DN, a change in network settings, or a change in operator policies. It should be noted that the triggers for the devices within the core network to start this process are not limited to these.

[0262] Moreover, this process can be executed at any timing when each device has established a 5GMM context and / or each device is in a 5GMM connection mode.

[0263] In addition, in this process, each device may send and receive a message including identification information indicating the reason why the UE's login is released and / or identification information indicating the need to reselect the network. Moreover, based on the completion of this process, each device may delete the UE's context or start the behavior instructed by the network.

[0264] The UE can identify the reason why the UE's login is released based on the control information sent and received through this process. Moreover, along with identifying the reason why the UE's login is released, the UE can delete the UE's context and can also start reselecting the network. In other words, the device within the core network can enable the UE to identify the reason why the UE's login is released by leading this process and then sending the control message and control information of this process to the UE. Moreover, the device within the core network can delete the UE's context and can also enable the UE to start reselecting the network by identifying the reason why the UE's login is released.

[0265] It should be noted that the non-login process includes a UE-led non-login process and a network-led non-login process. The UE-led non-login process and the network-led non-login process are described below. [3.2.1. UE-led non-login process]

[0266] First, use Figure 7 The UE-initiated de-registration procedure is described. In this chapter, this procedure refers to the UE-initiated de-registration procedure. The UE-initiated de-registration procedure is a procedure initiated by the UE in the de-registration procedure. The following describes each step of this procedure.

[0267] First, the UE starts the deregistration process by sending a deregistration request message (S900) to the AMF via the 5G AN (or gNB).

[0268] Here, the UE may include one or more of the first to third identification information in a non-login request message. It should be noted that the UE may indicate the reason why the UE's login is released or the need for network reselection by sending these identification information. Moreover, two or more of these identification information may constitute one or more identification information. 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 as different identification information.

[0269] Moreover, the UE may also indicate to the AMF the content represented by the identification information included in the non-login request message by including one or more of the first to third identification information in the non-login request message.

[0270] It should be noted that the UE can select and determine whether to include one or more of the first to third identification information in the non-login request message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the UE.

[0271] In addition, the UE can request the deletion of the UE's context by sending a non-login request message based on the received identification information and / or subscriber information and / or UE capability information and / or UE status and / or user login information and / or context maintained by the UE.

[0272] Next, the AMF receives a non-login request message (S900) via the 5G AN (gNB). It should be noted that the AMF can identify the reason why the UE's login is released based on the non-login request message and / or the identification information included in the non-login request message.

[0273] Moreover, the AMF can send a deregistration accept message to the UE via the 5G AN (gNB) as a response message to the deregistration request message based on the identification information included in the deregistration request message (S902).

[0274] Next, the UE can also receive a non-login acceptance message (S902) via the 5G AN (gNB).

[0275] Each device completes this process based on the sending and receiving of the non-login request message and / or the non-login acceptance message.

[0276] Furthermore, each device may perform processing based on the information sent and received in this process based on the completion of this process. For example, each device may delete the context of the UE when sending and receiving update information for setting information.

[0277] Moreover, the UE can start the network reselection and / or login process based on the completion of this process, when sending or receiving information indicating the need to reselect the network and / or perform the login process. [3.2.2. Network-led non-login process]

[0278] Next, use Figure 8 The network-initiated de-registration procedure is described. In this chapter, this procedure refers to the network-initiated de-registration procedure. The network-initiated de-registration procedure is a procedure initiated by the network leader in the de-registration procedure. The following describes each step of this procedure.

[0279] First, the AMF starts the deregistration process by sending a deregistration request message (S1000) to the UE via the 5G AN (or gNB).

[0280] Here, the AMF may include one or more of the tenth to twenty-third identification information in the non-login request message. It should be noted that the AMF can indicate the reason why the UE's login is released or the need for network reselection by sending these identification information. Moreover, two or more of these identification information may constitute one or more identification information. 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 with the same identification information or as different identification information.

[0281] Moreover, the AMF may also indicate to the UE the content represented by the identification information included in the non-login request message by including one or more of the tenth to twenty-third identification information in the non-login request message.

[0282] It should be noted that AMF can select and determine whether to include one or more of the tenth to twenty-third identification information in the non-login request message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF.

[0283] In addition, the AMF can request to delete the UE's context by sending a non-login request message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF.

[0284] Next, the UE receives a non-login request message (S1000) via the 5G AN (gNB). The UE can identify the reason why the UE's login is released based on the non-login request message and / or the identification information included in the non-login request message, and can also implement network reselection.

[0285] Moreover, the UE can send a deregistration accept message to the AMF via the 5G AN (gNB) as a response message to the non-login request message based on the identification information included in the non-login request message (S1002).

[0286] Next, AMF may also receive a non-login acceptance message via 5G AN (gNB) (S1002). In addition, each device completes this process based on the sending and receiving of a non-login request message and / or a non-login acceptance message.

[0287] Furthermore, each device may perform processing based on the information sent and received in this process based on the completion of this process. For example, each device may delete the context of the UE when sending and receiving update information for setting information.

[0288] Moreover, the UE can start the network reselection and / or login process based on the completion of this process, when sending or receiving information indicating the need to reselect the network and / or perform the login process.

[0289] In the above process, the device in the core network can instruct the UE to delete the setting information applied by the UE by sending and receiving non-login request messages, and can also instruct the UE to stop or change the functions being executed. [3.3.NAS transmission process]

[0290] Next, the NAS transport procedure is described. In this chapter, this procedure refers to the NAS transport procedure. The NAS transport procedure is initiated by the UE or the network and is used to provide payload transmission between the UE and the AMF.

[0291] This process can be performed at any timing when each device has established a 5GMM context and / or each device is in 5GMM connection mode.

[0292] Moreover, devices within the core network such as AMF can start this process based on updates to network settings and / or updates to operator policies. It should be noted that the trigger for this process can be the detection of UE mobility, the detection of changes in the status of the UE and / or access network and / or core network, or changes in the status of a network slice. Moreover, the trigger for this process can be the reception of a request from the DN and / or the application server of the DN, a change in network settings, or a change in operator policies. It should be noted that the triggers for the devices within the core network to start this process are not limited to these.

[0293] In addition, each device can start the behavior instructed by the network based on the completion of this process.

[0294] It should be noted that the NAS transmission process includes a UE-led NAS transmission process and a network-led NAS transmission process. The following describes the UE-led NAS transmission process and the network-led NAS transmission process. [3.3.1.UE-led NAS transmission process]

[0295] First, use Fig. 9 The UE-initiated NAS transport procedure is described. In this chapter, this procedure refers to the UE-initiated NAS transport procedure. The UE-initiated NAS transport procedure is a process initiated by the UE in the NAS transport procedure. The following describes each step of this procedure.

[0296] First, the UE starts the NAS transmission process by sending a UL NAS TRANSPORT message to the AMF (S1100). The UL NAS transmission message may also be referred to as an Uplink Non-Access-Stratum transmission message.

[0297] Here, the UE may include one or more of the first to third identification information in the UL NAS transmission message. It should be noted that two or more of these identification information may constitute one or more identification information. 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 as different identification information.

[0298] Moreover, the UE may also indicate to the AMF the content represented by the identification information included in the UL NAS transmission message by including one or more of the first to third identification information in the UL NAS transmission message.

[0299] It should be noted that the UE can select and determine whether to include one or more of the first to third identification information in the UL NAS transmission message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the UE.

[0300] Next, the AMF receives the UL NAS transmission message (S1100).

[0301] Each device completes this process based on the sending and receiving of UL NAS transmission messages.

[0302] Furthermore, each device may implement processing based on the information sent and received during this process upon completion of this process. [3.3.2. Network-led NAS transmission process]

[0303] First, use Fig.10 The network-initiated NAS transport procedure is described. In this chapter, this procedure refers to the network-initiated NAS transport procedure. The network-initiated NAS transport procedure is the process initiated by the network in the NAS transport process. The following describes each step of this procedure.

[0304] First, the AMF starts the NAS transmission process by sending a DL NAS TRANSPORT message (S1200) to the UE. The DL NAS transmission message may also be referred to as a Downlink Non-Access-Stratum transmission message.

[0305] Here, the AMF may include one or more of the tenth to twenty-third identification information in the DLNAS transmission message. It should be noted that two or more of these identification information may constitute one or more identification information. 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 as different identification information.

[0306] Moreover, the AMF may also indicate to the UE the content represented by the identification information included in the DL NAS transmission message by including one or more of the tenth to twenty-third identification information in the DL NAS transmission message.

[0307] It should be noted that the AMF can select and determine whether to include one or more of the tenth to twenty-third identification information in the DL NAS transmission message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF.

[0308] Next, the UE receives a DL NAS transmission message (S1200).

[0309] Each device completes this process based on the sending and receiving of DL NAS transmission messages.

[0310] Furthermore, each device may implement processing based on the information sent and received during this process upon completion of this process. [4. Implementation Method]

[0311] Next, each embodiment will be described. [4.1. First embodiment]

[0312] First, the first embodiment is described. In this chapter, the first embodiment may be referred to as the present embodiment.

[0313] In this embodiment, the network may be a managed network, which may be a SNPN or a PNI-NPN.

[0314] In addition, in this embodiment, a login process and / or a UE-led NAS transmission process and / or a network-led NAS transmission process may be implemented.

[0315] In this implementation, the first control message may be a login acceptance message or a DL NAS transmission message.

[0316] The following describes each step of this process.

[0317] First, the network sends a first control message to the UE. Here, the network may also include one or more of the tenth to thirteenth identification information in the first control message and send it.

[0318] Here, the network may also include one or more of the tenth to thirteenth identification information in the first control message to indicate to the UE the content represented by the identification information included in the first control message.

[0319] Specifically, the network may indicate the SOR-CMCI to the UE by sending the tenth identification information. In addition, the network may also indicate the content of each identification information to the UE by sending the tenth identification information consisting of one or more identification information from the eleventh to the thirteenth identification information. Specifically, the network may indicate the SOR-CMCI and / or the SOR-CMCI rule and / or the benchmark and / or the first timer value to the UE by sending the tenth identification information consisting of one or more identification information from the eleventh to the thirteenth identification information.

[0320] In addition, the network may indicate the SOR-CMCI rule to the UE by sending the eleventh identification information. Here, the network may also include the eleventh identification information in the tenth identification information and send it to the UE. In addition, the network may also indicate the content of each identification information to the UE by sending the eleventh identification information consisting of one or more identification information from the twelfth to the thirteenth identification information. Specifically, the network may also indicate the SOR-CMCI rule and / or the benchmark and / or the first timer value to the UE by sending the eleventh identification information consisting of one or more identification information from the twelfth to the thirteenth identification information.

[0321] In addition, the network may indicate the reference to the UE by sending the twelfth identification information. Here, the network may also include the twelfth identification information in the tenth and / or eleventh identification information and send it to the UE.

[0322] Here, the network can set the DNN of the PDU session or a benchmark related to the local service in the twelfth identification information.

[0323] In addition, the network may indicate the first timer value to the UE by sending the thirteenth identification information. Here, the network may also include the thirteenth identification information in the tenth and / or eleventh identification information to send to the UE.

[0324] In addition, the network may indicate the content of each identification information included in the first control message to the UE by sending the first control message. In addition, the network may indicate the content of each identification information to the UE by sending each identification information.

[0325] It should be noted that the network can also select and determine whether to include one or more of the tenth to thirteenth identification information in the first control message based on the UE status and / or information received from the local service provider and / or information received from the UDM and / or information received from the AUSF, etc.

[0326] In addition, the network may also determine whether to send the first control message and / or each identification information based on the state of the UE and / or the information received from the local service provider and / or the information received from the UDM and / or the information received from the AUSF. In addition, the network may also send the first control message and / or each identification information based on the information received from the local service provider and / or the UDM. In addition, the network may also send the first control message and / or each identification information based on the information received from the AUSF indicating the end of the local service.

[0327] Next, the UE receives the first control message. In addition, the UE may also receive the first control message including at least one of the tenth to thirteenth identification information from the network.

[0328] Moreover, the UE may store the identification information received together with the first control message based on the reception of the first control message, and may also identify the determination of the network. In addition, the UE may identify the content of the identification information received together with the first control message based on the reception of the first control message.

[0329] Specifically, the UE may identify the SOR-CMCI upon receiving the tenth identification information. In addition, the UE may apply the SOR-CMCI upon receiving the tenth identification information. Specifically, the UE may implement the process when the SOR-CMCI is applied upon receiving the tenth identification information.

[0330] In addition, the UE may also identify each identification information when receiving the tenth identification information consisting of one or more identification information from the eleventh to thirteenth identification information. Specifically, the UE may also identify the SOR-CMCI and / or the SOR-CMCI rule and / or the benchmark and / or the first timer value when receiving the tenth identification information consisting of one or more identification information from the eleventh to thirteenth identification information.

[0331] In addition, the UE may also implement processing for each identification information when receiving the tenth identification information consisting of one or more identification information from the eleventh to the thirteenth identification information. Specifically, the UE may also implement processing for the SOR-CMCI and / or SOR-CMCI rule and / or benchmark and / or the first timer value when receiving the tenth identification information consisting of one or more identification information from the eleventh to the thirteenth identification information.

[0332] In addition, the UE may also identify the SOR-CMCI rule when receiving the eleventh identification information. In addition, the UE may also perform processing for the SOR-CMCI rule when receiving the eleventh identification information.

[0333] In addition, the UE may also identify each identification information when receiving the eleventh identification information consisting of one or more identification information from the twelfth to the thirteenth identification information. Specifically, the UE may also identify the SOR-CMCI rule and / or the benchmark and / or the first timer value when receiving the eleventh identification information consisting of one or more identification information from the twelfth to the thirteenth identification information.

[0334] In addition, the UE may also implement processing for each identification information when receiving the eleventh identification information consisting of one or more identification information from the twelfth to the thirteenth identification information. Specifically, the UE may also implement processing for the SOR-CMCI rule and / or benchmark and / or the first timer value when receiving the eleventh identification information consisting of one or more identification information from the twelfth to the thirteenth identification information.

[0335] In addition, the UE may also identify the benchmark when receiving the twelfth identification information. In addition, the UE may also perform processing on the benchmark when receiving the twelfth identification information.

[0336] In addition, the UE may also identify the first timer value when receiving the thirteenth identification information. In addition, the UE may also perform processing on the first timer value when receiving the thirteenth identification information.

[0337] Here, in the case where the twelfth identification information is a benchmark representing a local service, the UE can confirm whether the local service is in action and use the thirteenth identification information to start the associated first timer. In addition, in the case where the twelfth identification information is a benchmark representing a local service, the UE can confirm whether the local service is in action and use the thirteenth identification information to start the first timer associated with the twelfth identification information.

[0338] In addition, the UE may also start the associated first timer based on the twelfth identification information using the thirteenth identification information.

[0339] In addition, when the thirteenth identification information is associated with the twelfth identification information indicating a benchmark related to the local service, the thirteenth identification information may be a value different for each UE. In addition, when the thirteenth identification information is associated with the twelfth identification information indicating the DNN of the PDU session, the thirteenth identification information may be a value different for each UE.

[0340] In addition, when the thirteenth identification information is associated with the twelfth identification information indicating a benchmark related to the local service, the thirteenth identification information may be a different value for each UE group including one or more UEs. For example, when there are UE1, UE2, UE3, and UE4, UE1 and UE2 are UE group 1, and UE3 and UE4 are UE group 2, the thirteenth identification information for UE1 and UE2 (or UE group 1) may be timer value 1, and the thirteenth identification information for UE3 and UE4 (or UE group 2) may be timer value 2.

[0341] It should be noted that the above-mentioned behavior of the UE may be implemented after receiving the first control message. In addition, the above-mentioned behavior of the UE may also be implemented after receiving one or more identification information among the tenth to thirteenth identification information.

[0342] In addition, when receiving the first control message, the UE may also implement the behavior when receiving each identification information included in the first control message. [4.2. Second embodiment]

[0343] Next, the second embodiment is described. In this chapter, the second embodiment may be referred to as the present embodiment.

[0344] In this embodiment, the network may be a managed network, which may be a SNPN or a PNI-NPN.

[0345] Furthermore, in this embodiment, a network-led non-login process may be implemented.

[0346] The following describes each step of this process.

[0347] First, the network sends a non-login request message to the UE. Here, the network may include one or more identification information from the fourteenth to sixteenth identification information in the non-login request message and send it.

[0348] Here, the network may also indicate to the UE the content represented by the identification information included in the non-login request message by including one or more of the fourteenth to sixteenth identification information in the non-login request message.

[0349] Specifically, the network may indicate to the UE a reason value indicating that the local service has ended by sending the fourteenth identification information. In addition, the network may also indicate to the UE that the local service has ended by sending the fourteenth identification information.

[0350] In addition, the network may also indicate the range of the login waiting time to the UE by sending the fifteenth identification information. In addition, the network may also indicate the minimum login waiting time and the maximum login waiting time to the UE by sending the fifteenth identification information.

[0351] In addition, the network may also indicate the timer value to the UE by sending the sixteenth identification information.

[0352] In addition, the network may also indicate the content of each identification information included in the non-login request message to the UE by sending the non-login request message. In addition, the network may also indicate the content of each identification information to the UE by sending each identification information.

[0353] It should be noted that the network can also select and determine whether to include one or more of the fourteenth to sixteenth identification information in the non-login request message based on the UE status and / or information received from the local service provider and / or information received from the UDM and / or information received from the AUSF, etc.

[0354] In addition, the network may also determine whether to send a non-login request message and / or each identification information based on the status of the UE and / or information received from the local service provider and / or information received from the UDM and / or information received from the AUSF. In addition, the network may also send a non-login request message and / or each identification information based on information received from the local service provider and / or the UDM. In addition, the network may also send a non-login request message and / or each identification information based on information received from the AUSF indicating the end of the local service.

[0355] Next, the UE receives the non-registration request message. In addition, the UE may also receive a non-registration request message including one or more of the fourteenth to sixteenth identification information from the network.

[0356] Moreover, the UE may store the identification information received together with the non-login request message based on the reception of the non-login request message, and may also identify the determination of the network. In addition, the UE may also identify the content of the identification information received together with the non-login request message based on the reception of the non-login request message.

[0357] Specifically, the UE may also recognize that the local service has ended when receiving the fourteenth identification information. In addition, the UE may also delete the fifteenth or sixteenth identification information stored in the UE when receiving the fourteenth identification information.

[0358] In addition, when receiving the fifteenth identification information, the UE may also identify the range of the login waiting time. In addition, when receiving the fifteenth identification information, the UE may also delete the fifteenth identification information stored in the UE and store the received fifteenth identification information.

[0359] In addition, the UE may also identify the login waiting time when receiving the sixteenth identification information. In addition, the UE may also delete the sixteenth identification information stored in the UE when receiving the sixteenth identification information, and store the received sixteenth identification information.

[0360] In addition, when the UE receives the fourteenth identification information and receives the fifteenth or sixteenth identification information, the UE may delete the fifteenth or sixteenth identification information stored in the UE and store the received fifteenth or sixteenth identification information.

[0361] In addition, when determining to perform PLMN selection or SNPN selection and having the saved fifteenth identification information, the UE may also generate a random value within the range of the fifteenth identification information and use the generated value to start the second timer.

[0362] In addition, when the UE determines that PLMN selection or SNPN selection is to be performed and has the saved sixteenth identification information, the UE may also use the sixteenth identification information to start the second timer.

[0363] Here, the UE may not start the login process while the second timer is in operation. In addition, the UE may also perform the login process when the second timer expires.

[0364] It should be noted that the above-mentioned behavior of the UE may be implemented after receiving the non-login request message. In addition, the above-mentioned behavior of the UE may also be implemented after receiving one or more identification information among the fourteenth to sixteenth identification information.

[0365] In addition, when receiving a non-login request message, the UE may also implement the behavior when receiving each identification information included in the non-login request message. [4.3. Third embodiment]

[0366] Next, the third embodiment is described. In this chapter, the third embodiment may be referred to as the present embodiment.

[0367] In this embodiment, the network may be a managed network, which may be a SNPN or a PNI-NPN.

[0368] Furthermore, in this embodiment, a login process may also be implemented.

[0369] The following describes each step of this process.

[0370] First, the UE sends a login request message to the network. Here, the UE may include one or more of the first to third identification information in the login request message for sending.

[0371] Here, the UE may include one or more of the first to third identification information in the login request message to indicate to the network the content represented by the identification information included in the login request message.

[0372] Specifically, the UE may also indicate the SNPN ID to the network by sending the first identification information.

[0373] In addition, the UE may also indicate to the network whether it supports CAG by sending the second identification information. In addition, the UE may also indicate to the network whether it supports CAG by sending the second identification information. In addition, the UE may also indicate to the network whether it supports CAG by sending the second identification information.

[0374] In addition, the UE may indicate to the network that it supports the hosted network by sending the third identification information.

[0375] Next, the network sends a registration rejection message to the UE. Here, the network may include one or more identification information from the seventeenth to twenty-third identification information in the registration rejection message and send it.

[0376] Here, the network may include one or more of the seventeenth to twenty-third identification information in the login rejection message to indicate to the UE the content represented by the identification information included in the login rejection message.

[0377] Specifically, the network may also indicate to the UE that the hosted network is not authorized by sending the seventeenth identification information. In addition, the network may also indicate to the UE that the hosted network is not authorized by sending the seventeenth identification information.

[0378] In addition, the network may also indicate to the UE that the SNPN is temporarily not authorized by sending the eighteenth identification information. In addition, the network may also indicate to the UE that the SNPN represented by the first identification information is temporarily not authorized by sending the eighteenth identification information. In addition, the network may also indicate to the UE that the SNPN is temporarily not authorized by sending the eighteenth identification information.

[0379] In addition, the network may also indicate to the UE that the SNPN is permanently not authorized by sending the nineteenth identification information. In addition, the network may also indicate to the UE that the SNPN represented by the first identification information is permanently not authorized by sending the nineteenth identification information. In addition, the network may also indicate to the UE that the SNPN is permanently not authorized by sending the nineteenth identification information.

[0380] In addition, the network may also indicate to the UE a list including CAG IDs by sending twentieth identification information.

[0381] In addition, the network may indicate the content of each identification information included in the registration rejection message to the UE by sending the registration rejection message. In addition, the network may indicate the content of each identification information to the UE by sending each identification information.

[0382] It should be noted that the network can also select and determine whether to include one or more of the seventeenth to twenty-third identification information in the login rejection message based on the UE status and / or information received from the local service provider and / or information received from the UDM and / or information received from the AUSF, etc.

[0383] In addition, the network may also determine whether to send a login rejection message and / or each identification information based on the status of the UE and / or information received from the local service provider and / or information received from the UDM and / or information received from the AUSF. In addition, the network may also send a login rejection message and / or each identification information based on information received from the local service provider and / or the UDM. In addition, the network may also send a login rejection message and / or each identification information based on information received from the AUSF indicating the end of the local service.

[0384] Next, the UE receives the registration rejection message. In addition, the UE may also receive a registration rejection message including one or more of the seventeenth to twenty-third identification information from the network.

[0385] Furthermore, the UE may also store the identification information received together with the login rejection message based on the reception of the login rejection message, and may also identify the determination of the network. Furthermore, the UE may also identify the content of the identification information received together with the login rejection message based on the reception of the login rejection message.

[0386] Specifically, the UE may also recognize that the hosted network is not authorized upon receiving the seventeenth identification information.

[0387] In addition, the UE may also save the first identification information in a list of prohibited hosted networks based on the seventeenth identification information. In addition, the UE may also save the first identification information in a list of prohibited hosted networks based on the seventeenth identification information when the login request message is a message for a local service. Here, the list of prohibited hosted networks may refer to the same list as the twenty-third identification information.

[0388] In addition, the UE may not save the first identification information in the temporarily prohibited SNPN list and / or the permanently prohibited SNPN list based on the seventeenth identification information. In addition, the UE may not save the first identification information in the temporarily prohibited SNPN list and / or the permanently prohibited SNPN list based on the seventeenth identification information when the login request message is a message for local service.

[0389] In addition, the UE may also replace the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE with the received twentieth and / or twenty-second and / or twenty-third identification information based on the seventeenth or twenty-first identification information. In addition, the UE may also replace the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE with the received twentieth and / or twenty-second and / or twenty-third identification information based on the seventeenth or twenty-first identification information when the login request message is a message for a local service in the PNI-NPN. In other words, the UE may also replace the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE with the received twentieth and / or twenty-second and / or twenty-third identification information based on the seventeenth or twenty-first identification information when the login request message is a message for a hosted network as a PNI-NPN.

[0390] In addition, the UE may also, based on the seventeenth or twenty-first identification information, replace the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE with the received twentieth and / or twenty-second and / or twenty-third identification information when the UE supports the hosted network. In other words, the UE may also, based on the seventeenth or twenty-first identification information, replace the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE with the received twentieth and / or twenty-second and / or twenty-third identification information when the UE supports the local service.

[0391] In addition, the UE may also replace the entry of the serving VPLMN of the twentieth and / or the twenty-second and / or the twenty-third identification information stored in the UE with the entry of the serving VPLMN of the twentieth and / or the twenty-second and / or the twenty-third identification information received based on the seventeenth or twenty-first identification information. In addition, the UE may also replace the entry of the serving VPLMN of the twentieth and / or the twenty-second and / or the twenty-third identification information stored in the UE with the entry of the serving VPLMN of the twentieth and / or the twenty-second and / or the twenty-third identification information received based on the seventeenth or twenty-first identification information when the login request message is a message for a local service in the PNI-NPN. In other words, the UE may also replace the entry of the serving VPLMN of the twentieth and / or the twenty-second and / or the twenty-third identification information stored in the UE with the entry of the serving VPLMN of the twentieth and / or the twenty-second and / or the twenty-third identification information received based on the seventeenth or twenty-first identification information when the login request message is a message for a hosted network as a PNI-NPN.

[0392] In addition, the UE may also, based on the seventeenth or twenty-first identification information, replace the entry of the service VPLMN of the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE with the entry of the service VPLMN of the twentieth and / or twenty-second and / or twenty-third identification information received when the UE supports the hosted network. In other words, the UE may also, based on the seventeenth or twenty-first identification information, replace the entry of the service VPLMN of the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE with the entry of the service VPLMN of the twentieth and / or twenty-second and / or twenty-third identification information received when the UE supports local service.

[0393] In addition, the UE may also delete the twentieth and / or the twenty-second and / or the twenty-third identification information stored in the UE based on the seventeenth or twenty-first identification information. In addition, the UE may also delete the twentieth and / or the twenty-second and / or the twenty-third identification information stored in the UE based on the seventeenth or twenty-first identification information when the login request message is a message for a local service in the PNI-NPN. In other words, the UE may also delete the twentieth and / or the twenty-second and / or the twenty-third identification information stored in the UE based on the seventeenth or twenty-first identification information when the login request message is a message for a hosted network as a PNI-NPN.

[0394] In addition, the UE may also delete the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE based on the seventeenth or twenty-first identification information when the UE supports the hosted network. In other words, the UE may also delete the twentieth and / or twenty-second and / or twenty-third identification information stored in the UE based on the seventeenth or twenty-first identification information when the UE supports the local service.

[0395] In addition, the UE may also, upon receiving the eighteenth identification information, identify that the SNPN is temporarily not authorized. In addition, the UE may also, upon receiving the eighteenth identification information, identify that the SNPN represented by the first identification information is temporarily not authorized. In addition, the UE may also, upon receiving the eighteenth identification information, identify that the SNPN is temporarily not authorized.

[0396] In addition, the UE may also save the first identification information in the list of SNPNs temporarily prohibited for local services based on the eighteenth identification information. In addition, the UE may also save the first identification information in the list of SNPNs temporarily prohibited for local services based on the eighteenth identification information when the login request message is a message for local services in the SNPN. In other words, the UE may also save the first identification information in the list of SNPNs temporarily prohibited for local services based on the eighteenth identification information when the login request message is a message for a hosted network serving as the SNPN.

[0397] In addition, the UE may also, based on the eighteenth identification information, store the first identification information in a list of SNPNs temporarily prohibited for local services when the UE supports the hosted network. In other words, the UE may also, based on the eighteenth identification information, store the first identification information in a list of SNPNs temporarily prohibited for local services when the UE supports the local service.

[0398] In addition, the UE may also, upon receiving the nineteenth identification information, identify that the SNPN is permanently not authorized. In addition, the UE may also, upon receiving the nineteenth identification information, identify that the SNPN represented by the first identification information is permanently not authorized. In addition, the UE may also, upon receiving the nineteenth identification information, identify that the SNPN is permanently not authorized.

[0399] In addition, the UE may also save the first identification information in the list of SNPNs permanently prohibited for local services based on the nineteenth identification information. In addition, the UE may also save the first identification information in the list of SNPNs permanently prohibited for local services based on the nineteenth identification information when the login request message is a message for local services in the SNPN. In other words, the UE may also save the first identification information in the list of SNPNs permanently prohibited for local services based on the nineteenth identification information when the login request message is a message for a hosted network serving as the SNPN.

[0400] In addition, the UE may also, based on the nineteenth identification information, store the first identification information in a list of SNPNs permanently prohibited for local services when the UE supports a hosted network. In other words, the UE may also, based on the nineteenth identification information, store the first identification information in a list of SNPNs permanently prohibited for local services when the UE supports local services.

[0401] In addition, the UE may also replace the 20th identification information stored in the UE with the received 20th identification information when receiving the 20th identification information. In addition, the UE may also replace the 20th identification information stored in the UE with the received 20th identification information based on the seventeenth or twenty-first identification information when receiving the 20th identification information.

[0402] In addition, the UE may also, when receiving the twenty-first identification information, identify that the CAG cell is not authorized. In addition, the UE may also, when receiving the twenty-first identification information, identify that only the CAG cell is authorized.

[0403] In addition, the UE may also replace the 22nd identification information stored in the UE with the received 22nd identification information when receiving the 22nd identification information. In addition, the UE may also replace the 22nd identification information stored in the UE with the received 22nd identification information based on the 17th or 21st identification information when receiving the 22nd identification information.

[0404] In addition, the UE may also replace the twenty-third identification information stored in the UE with the received twenty-third identification information when receiving the twenty-third identification information. In addition, the UE may also replace the twenty-third identification information stored in the UE with the received twenty-third identification information based on the seventeenth or twenty-first identification information when receiving the twenty-third identification information.

[0405] In addition, when receiving the registration rejection message, the UE may also identify the content of each piece of identification information included in the registration rejection message. In addition, when receiving each piece of identification information, the UE may also identify the content of each piece of identification information.

[0406] It should be noted that the above-mentioned behavior of the UE may be implemented after receiving the login rejection message. In addition, the above-mentioned behavior of the UE may also be implemented after receiving one or more identification information among the seventeenth to twenty-third identification information.

[0407] In addition, when receiving the login rejection message, the UE may also implement the behavior when receiving each identification information included in the login rejection message. [5. Modifications]

[0408] The program that operates in the device according to one embodiment of the present invention may be a program that controls a central processing unit (CPU) or the like to enable a computer to function so as to implement the functions of the implementation method according to one 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.

[0409] 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 a device, and includes a computer system of hardware such as an operating system and peripheral devices. In addition, the "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short time, or other computer-readable recording media.

[0410] In addition, each functional block or each feature of the device used in the above-mentioned embodiments 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 circuit may be composed of digital circuits or analog circuits. In addition, in the case where integrated circuit technology that replaces current integrated circuits appears due to advances in semiconductor technology, one or more schemes of the present invention may also use new integrated circuits based on this technology.

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

[0412] 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, the present invention can be variously modified within the scope indicated by the claims, and the embodiments obtained by appropriately combining the technical solutions 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.

[0413] A user equipment (UE) of one embodiment of the present invention comprises a transceiver unit and a control unit, wherein the UE is characterized in that the transceiver unit sends a login request message including first identification information and second identification information, wherein the first identification information is information for identifying an SNPN, and the second identification information is information indicating support for a hosted network, and receives a login rejection message including a first reason value, wherein the first reason value is a reason value indicating non-authorization for the hosted network, and the control unit saves the first identification information in a prohibited hosted network list based on the first reason value when the login request message is a message for a local service in an SNPN.

[0414] A user equipment (UE) of one embodiment of the present invention comprises a transceiver unit and a control unit, wherein the UE is characterized in that the transceiver unit sends a login request message including first identification information and second identification information, wherein the first identification information is information for identifying an SNPN, and the second identification information is information indicating support for a hosted network, and receives a login rejection message including a first reason value or a second reason value, wherein the first reason value is a reason value indicating temporary non-authorization of the SNPN, and the second reason value is a reason value indicating permanent non-authorization of the SNPN, and based on the first reason value, the control unit saves the first identification information in a list of SNPNs temporarily prohibited for local services when the login request message is a message for local services in the SNPN, and based on the second reason value, the control unit saves the first identification information in a list of SNPNs permanently prohibited for local services when the login request message is a message for local services in the SNPN.

[0415] A user equipment (UE) of one embodiment of the present invention comprises a transceiver and a control unit, wherein the UE is characterized in that the transceiver sends a login request message including first identification information and second identification information, wherein the first identification information is information indicating whether a closed access group (CAG) is supported, and the second identification information is information indicating support for a hosted network, and receives a login rejection message including a first reason value and third identification information, wherein the first reason value is a reason value indicating that the hosted network is not authorized, and the third identification information is a list including CAG IDs, and the control unit replaces the third identification information stored in the UE with the received third identification information based on the first reason value when the login request message is a message for a local service in a PNI-NPN. (Cross-reference of related applications) This application claims the benefit of priority to Japanese patent application No. 2022-118330 filed on July 26, 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 (E-UTRAN) 90: Core Network_A 120: Access network_B (5G AN) 122: gNB 130: UPF 132: SMF 140:AMF 150: UDM 160: PCF 190: Core Network_B 235:UPF_A 239:UPF_C

Claims

1. A user equipment UE, the UE comprising a transceiver unit, a control unit and a storage unit, wherein the UE is characterized in that: The control unit manages the first list and the second list, The first list is a list of independent non-public networks SNPN for which connection to local services is temporarily prohibited, The second list is a list of SNPNs that are permanently prohibited for connection to local services, The transceiver sends a login request message to the network. The transceiver receives a login rejection message including a first reason value or a second reason value from the network, The first reason value is a reason value indicating that the SNPN is temporarily not authorized. Upon receiving the first reason value, the control unit stores the independent non-public network identifier SNPN ID in the first list stored in the storage unit based on the first reason value, The second reason value is a reason value indicating permanent non-authorization of the SNPN. When receiving the second reason value, the control unit stores the SNPN ID in the second list stored in the storage unit based on the second reason value.

2. A communication control method, performed by a user equipment UE, wherein the communication control method comprises the following steps: A process of managing a first list and a second list, wherein: The first list is a list of independent non-public networks SNPN for which connection to local services is temporarily prohibited, The second list is a list of SNPNs that are permanently prohibited for connection to local services; The UE sends a login request message to the network; The UE receives a login rejection message including a first reason value or a second reason value from the network, wherein: The first reason value is a reason value indicating that the SNPN is temporarily not authorized. The second reason value is a reason value indicating permanent non-authorization of the SNPN; Upon receiving the first reason value, based on the first reason value, the UE stores a standalone non-public network identifier, SNPN ID, in the first list stored by the UE; and Upon receiving the second reason value, the UE stores the SNPN ID in the second list stored in the UE based on the second reason value.

Images