WO2024095782A1 - User equipment (ue) - Google Patents

Abstract

Currently, a behavior of UE for selecting an NPN for a local service is being considered. When the UE has selected an NPN, the UE performs a registration procedure with respect to the NPN. However, it is not clear how the UE behaves when the NPN for the local service is present but the registration procedure to the NPN fails. When one or more first SNPNs are present but registration to all the first SNPNs fails due to a failure of position registration, this user equipment (UE) waits until a new first SNPN becomes available, and executes a registration procedure with respect to the new first SNPN which has become available. Each of the first SNPNs indicates that a local service is allowed, and corresponds to local service information.

Description

UE (User Equipment)

This embodiment relates to UE (User Equipment). This application claims priority to Japanese Patent Application No. 2022-176017, filed on November 2, 2022, the contents of which are incorporated herein by reference.

The 3GPP (3rd Generation Partnership Project) is considering the system architecture of 5GS (5G System), a fifth-generation (5G) mobile communications system, and discussions are underway to support new procedures and new functions (see non-patent documents 1 to 4). In recent years, there has been active discussion about functions to realize localized services in NPNs (Non-Public Networks) (see non-patent document 5).

In order to provide a wide variety of services, a new core network, 5GCN (5G Core Network), is being considered for 5GS (5G System). Furthermore, for 5GS, the provision of private networks that can be used by specific users for specific purposes, such as NPN (Non-Public Network), which is defined separately from PLMN (Public Land Mobile Network), a public network, and functions to realize private networks are also being considered.

Currently, the behavior of the UE when selecting an NPN for local services is being considered. In addition, when the UE selects an NPN, it performs a registration procedure for that NPN. However, if an NPN exists for the local service, but the registration procedure for that NPN fails, it is not clear how the UE will behave.

This embodiment has been made in consideration of the above circumstances. Its purpose is to clarify the behavior of the UE when an NPN for local services exists, but the registration procedure to that NPN fails.

The User Equipment (UE) of this embodiment is characterized in that it includes a control unit, and when one or more first SNPNs exist, but registration to all of the first SNPNs fails due to a location registration failure, the control unit waits until a new first SNPN becomes available, and executes a registration procedure for the new first SNPN that has become available, and the first SNPN is an SNPN that indicates that local services are permitted and matches local service information.

According to this embodiment, it is possible to clarify the behavior of the UE when registration is rejected from an NPN for local services.

1 is a diagram illustrating an overview of a mobile communication system (EPS/5GS). A diagram explaining the detailed configuration of a mobile communication system (EPS/5GS). A diagram explaining the device configuration of a UE. A diagram explaining the configuration of an access network device (gNB) in 5GS. A diagram explaining the configuration of core network devices (AMF/SMF/UPF) in 5GS. FIG. 1 is a diagram illustrating a registration procedure.

Below, the best mode for implementing this embodiment will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which this embodiment is applied will be described.

[1. System Overview]
First, FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1. As shown in FIG.

In Figure 1, it is shown that the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

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

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

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

The 4G system EPS (Evolved Packet System) is composed of an access network_A and a core network_A, but may further include a UE and/or a PDN. The 5G system 5GS (5G System) is composed of a UE, an access network_B and a core network_B, but may further include a DN.

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

Furthermore, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and/or a wireless LAN access network. One or more eNBs (evolved Node B) 45 are deployed in E-UTRAN. In the following, eNB 45 may be written without the symbol eNB. In addition, when there are multiple eNBs, the eNBs are connected to each other, for example, via an X2 interface. In addition, one or more access points are deployed in the wireless LAN access network.

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

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

Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Furthermore, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Furthermore, nodes placed in access network_B may be collectively referred to as NG-RAN nodes.

Furthermore, in the following, access network_A, and/or access network_B, and/or devices included in access network_A, and/or devices included in access network_B may be referred to as access networks or access network devices.

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

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

Furthermore, in the following, core network_A and/or core network_B, devices included in core network_A, and/or devices included in core network_B may be referred to as core networks, or core network devices, or devices within a core network.

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

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

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

The UE can also connect to an access network. The UE can also connect to a core network via the access network. The UE can also connect to a PDN or DN via the access network and the core network. In other words, the UE can send and receive (communicate) user data with the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

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

In addition, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may be configured with devices not shown in FIG. 2. For example, core network_A and/or core network_B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

Here, the AUSF is a core network device equipped with an authentication function for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives an authentication request for 3GPP access and/or non-3GPP access from the UE and executes the authentication procedure.

The AAA server is a device that has authentication, authorization, and billing functions and is connected to the AUSF directly or indirectly via another network device. The AAA server may be a network device within the core network. The AAA server may not be included in core network_A and/or core network_B, but may be included in the PLMN. In other words, the AAA server may be a core network device, or a device outside the core network. For example, the AAA server may be a server device within the PLMN managed by a 3rd Party.

In FIG. 2, in order to simplify the drawing, each device and function is shown one by one, but the mobile communication system 1 may be configured with multiple similar devices and functions. Specifically, the mobile communication system 1 may be configured with multiple devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and/or UDM150.

The UPF_A235 is connected to the DN, the SMF, other UPFs, and the access network. The UPF_A235 may perform roles such as an anchor for intra-RAT mobility or inter-RAT mobility, packet routing & forwarding, an UL CL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, a branching point function that supports multi-homed PDU sessions, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and a trigger function for downlink data notification. The UPF_A235 may also be a relay device that forwards user data as a gateway between the DN and the core network_B190. The UPF_A235 may also be a gateway for IP communication and/or non-IP communication. Furthermore, UPF_A235 may have a function to forward IP communications, and may have a function to convert non-IP communications to IP communications. Furthermore, the multiple gateways may be gateways that connect the core network_B190 to a single DN. Furthermore, UPF_A235 may have connectivity with other NFs, and may be connected to each device via other NFs.

Note that UPF_C239 (also called a branching point or uplink classifier), which is a UPF different from UPF_A235, may exist as a device or NF between UPF_A235 and the access network. When UPF_C239 exists, the PDU session between the UE and the DN will be established via the access network, UPF_C239, and UPF_A235.

The UPF130 may be the same device as the UPF_A235. Note that the symbols for the UPF130 and UPF_A235 may be omitted and written as UPF.

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

In addition, each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device/function mentioned below is composed of, for example, a semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only the information that was originally set at the time of shipment, but also various information transmitted and received between the device/function other than the device/function itself (for example, UE, and/or access network device, and/or core network device, and/or PDN, and/or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc. contained in control messages transmitted and received within various communication procedures described below. In addition, each memory unit may store this information for each UE. In addition, in the case of interworking between 5GS and EPS, each memory unit can store control messages and user data transmitted and received between 5GS and/or devices/functions included in EPS. At this time, it is possible to store not only messages sent and received via the N26 interface, but also messages sent and received without going through the N26 interface.

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

The control unit_A300 is a functional unit that controls the operation and functions of the entire UE. The control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the memory unit_A340 as necessary.

The transceiver unit_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 unit_A320 to transmit and receive user data and/or control information between an access network device, and/or a core network device, and/or a PDN, and/or a DN.

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

The memory unit_A340 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UE.

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

The control unit_B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit_B500 realizes various processes in the gNB by reading and executing various programs stored in the memory unit_B540 as necessary.

The network connection unit _B520 is a functional unit that enables the gNB to communicate with the AMF and/or UPF. In other words, the gNB can send and receive user data and/or control information between the AMF and/or UPF using the network connection unit _B520.

The transceiver unit_B530 is a functional unit for wireless communication with the UE via the antenna 510. In other words, the gNB can transmit and receive user data and/or control information between the UE and the gNB using the transceiver unit_B530.

Explaining in more detail with reference to Figure 2, a gNB in a 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. The gNB can also communicate with a UE by using the transceiver unit_B530.

The memory unit_B540 is a functional unit for storing programs, user data, control information, etc. required for each operation of the gNB.

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

The control unit_B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit_B700 realizes various processes in the AMF by reading and executing various programs stored in the memory unit_B740 as necessary.

The network connection unit_B720 is a functional unit that enables the AMF to connect to a base station device (gNB), and/or an SMF, and/or a PCF, and/or an UDM, and/or an SCEF in a 5G AN. In other words, the AMF can use the network connection unit_B720 to transmit and receive user data and/or control information between a base station device (gNB), and/or an SMF, and/or a PCF, and/or an UDM, and/or an SCEF in a 5G AN.

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

The memory unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the AMF.

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

In addition, in registration management, the RM state for each UE is managed. The RM state may be synchronized between the UE and the AMF. There are two RM states: the unregistered state (RM-DEREGISTERED state) and the registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered in the network, so the UE context in the AMF does not have valid location information or routing information for the UE, and the AMF is therefore unable to reach the UE. In the RM-REGISTERED state, the UE is registered in the network, so the UE can receive services that require registration with the network. The RM state may also be expressed as the 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.

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

Furthermore, 5GMM-DEREGISTERED may mean that each device has not established a 5GMM context, that the location information of UE_A10 is not known to the network, or that the network is unable to reach UE_A10. When each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or establish a 5GMM context by performing the registration procedure.

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

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

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

Furthermore, one or more AMFs may be placed within the core network_B. Furthermore, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Furthermore, the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.

The N3IWF is a device and/or function that is placed between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.

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

The control unit_B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit_B700 realizes various processes in the SMF by reading and executing various programs stored in the memory unit_B740 as necessary.

The network connection unit _B720 is a functional unit that allows the SMF to connect to the AMF, and/or the UPF, and/or the PCF, and/or the UDM. In other words, the SMF can use the network connection unit _B720 to send and receive user data and/or control information between the AMF, and/or the UPF, and/or the PCF, and/or the UDM.

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

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

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

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

The control unit_B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit_B700 realizes various processes in the UPF by reading and executing various programs stored in the memory unit_B740 as necessary.

The network connection unit_B720 is a functional unit that enables the UPF to connect to a base station device (gNB) and/or SMF and/or DN in the 5G AN. In other words, the UPF can use the network connection unit_B720 to transmit and receive user data and/or control information between the base station device (gNB) and/or SMF and/or DN in the 5G AN.

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

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

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

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

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

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

Furthermore, the U-Plane (User Plane; UP) may be a communication path for sending and receiving user data and may be composed of multiple bearers.Furthermore, the C-Plane (Control Plane; CP) may be a communication path for sending and receiving control messages and may be composed of multiple bearers.

[2.6. Description of other equipment and/or functions]
Next, other devices and/or functions will be described.

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

Furthermore, the network may refer to a PLMN (Public Land Mobile Network) or a NPN (Non-Public Network) as described below. Furthermore, network selection may refer to a PLMN selection or an SNPN selection.

An NWDAF (Network Data Analytics Function) may be an NF that has the function of collecting data from NFs and application functions (also called AFs).

A PCF (Policy Control Function) may be an NF that has the function of determining policies for controlling network behavior.

An NRF (Network Repository Function) may be an NF that has a service discovery function. An NRF may be an NF that has a function to provide information about a discovered NF when it receives a discovery request for another NF from another NF.

UDM (Unified Data Management) may be an NF that has authentication credential processing functions, user identification processing functions, access authentication functions, registration/mobility management functions, subscription management functions, etc.

The SM (Session Management) message may be a NAS message used in procedures for SM. The SM message may also be referred to as a NAS (Non-Access-Stratum) SM message. The SM message may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, SM messages may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc.

Furthermore, the SM procedure (also referred to as the procedure for SM) may include a PDU session establishment procedure, a PDU session modification procedure, and a PDU session release procedure. Each procedure may be initiated by the UE or the network.

The MM (Mobility management) message may be a NAS message used in procedures for MM. The MM message may be referred to as a NAS MM message. The MM message may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc.

In addition, the MM procedures (also referred to as procedures for MM) may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

The 5GS (5G System) service may be a connection service provided using the core network_B190. Furthermore, the 5GS service may be a service different from the EPS service or a service similar to the EPS service.

Non-5GS services may be services other than 5GS services and may include EPS services and/or non-EPS services.

S1 mode is a mode in which UE_A10 is permitted to access the EPC via E-UTRAN. In other words, S1 mode may be a mode in which messages are sent and received using the S1 interface. The S1 interface may be composed of an S1-MME interface and an S1-U interface.

The N1 mode is a mode in which UE_A10 is permitted to access 5GC via a 5G access network. In other words, the N1 mode may be a mode in which messages are sent and received using the N1 interface.

An APN (Access Point Name) may be identification information that identifies a core network and/or an external network such as a PDN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30/UPF_A235 that connects the core network A_90.

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

A PDU (Protocol Data Unit) session can be defined as an association between a DN that provides a PDU connectivity service and a UE, but it may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and a DN by establishing a PDU session via an access network_B and a core network_B. Here, this external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data to and from a device such as an application server located in a DN using a PDU session. Each device (UE, and/or an access network device, and/or a core network device) may manage one or more pieces of identification information in association with a PDU session. These pieces of identification information may include one or more of the DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, or may further include other information. Furthermore, when multiple PDU sessions are established, each piece of identification information associated with a PDU session may be the same or different.

The DNN (Data Network Name) may be identification information that identifies a core network and/or an external network such as a DN. Furthermore, the DNN can also be used as information for selecting a gateway such as a PGW/UPF that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

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

　A PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. A PLMN is a network managed by an operator, which is a telecommunications carrier, and the operator can be identified by the PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscription Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may hold an Equivalent PLMN list in the USIM to identify one or more EPLMNs (Equivalent PLMNs). A PLMN different from the HPLMN and/or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN).

In addition, a registered PLMN is a PLMN to which a UE is registered.

In addition, an equivalent PLMN is a PLMN that is treated by the network as if it were the same PLMN as any PLMN. For example, an equivalent PLMN may be one or more PLMNs that are treated the same as a registered PLMN.

PLMN selection may be a procedure by which a UE selects a PLMN. Here, the PLMN selection may be performed when a UE connects to a PLMN. Here, the PLMN selection may be referred to as a PLMN selection process or a PLMN selection procedure.

Here, a UE not operating in the SNPN access mode or the SNPN access operation mode may perform PLMN selection. Also, a UE operating in the SNPN access mode or the SNPN access operation mode may not perform PLMN selection. Also, PLMN selection may be performed without registration. In other words, PLMN selection may be performed when the UE has not completed registration with the network. PLMN selection may include an automatic PLMN selection mode and a manual PLMN selection mode. Note that PLMN selection may refer to either the automatic PLMN selection mode or the manual PLMN selection mode.

A tracking area is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. The tracking area may be composed of multiple cells. Furthermore, the tracking area may be an area in which control messages such as paging are broadcast, or an area in which UE_A10 can move without performing a handover procedure. Furthermore, the tracking area may be a routing area, a location area, or anything similar. Hereinafter, the tracking area may be a TA (Tracking Area). The tracking area may be identified by a TAI (Tracking Area Identity) composed of a TAC (Tracking area code) and a PLMN.

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

The UE ID is information for identifying a UE. For example, the UE ID may be a SUCI, or a SUPI, or an IMSI, or a GUTI, or a 5G-GUTI, or an IMEI, or an IMEISV, or a TMSI, or a 5G-S-TMSI. Or, the UE ID may be other information configured within an application or a network. Additionally, the UE ID may be information for identifying a user.

The SUCI (Subscription Concealed Identifier) may be a privacy preserving identifier that includes a concealed SUPI. The SUCI may also 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.

SUPI (Subscription Permanent Identifier) may be a globally unique identifier assigned to each subscriber in a 5G system. SUPI may be defined as a SUPI type and an IMSI or an NSI or a Global Cable Identifier (GCI) or a Global Line Identifier (GLI). The SUPI type may also indicate an IMSI, an NSI, an GCI, or a GLI. That is, when the SUPI type indicates an IMSI, the SUPI may be composed of a SUPI type indicating an IMSI and an IMSI. Similarly, when the SUPI type indicates an NSI, the SUPI may be composed of a SUPI type indicating an NSI and an NSI. When the SUPI type indicates a GCI, the SUPI may be composed of a SUPI type indicating a GCI and a GCI. When the SUPI type indicates a GLI, the SUPI may be composed of a SUPI type indicating a GLI and a GLI.

The IMSI (International Mobile Subscription Identity) may consist of the MCC (Mobile Country Code), MNC (Mobile Network Code), and MSIN (Mobile Subscriber Identification Number).

5G-GUTI (5G Globally Unique Temporary Identifier) may be information for providing an unambiguous UE identifier that does not reveal the UE or the user's permanent identity. 5G-GUTI may also be information that can identify the AMF and the network. 5G-GUTI may also be information used by the network and the UE to establish the identity of the UE. 5G-GUTI may be composed of two elements: one that identifies the AMF that assigned the 5G-GUTI, and one that uniquely identifies the UE within the AMF that assigned the 5G-GUTI. The former may be GUAMI (Globally Unique AMF Identifier), and the latter may be 5G-TMSI (5G-Temporary Mobile Subscriber Identity). That is, 5G-GUTI may be composed of GUAMI and 5G-TMSI.

IMEI (International Mobile station Equipment Identity) may consist of TAC (Type Allocation Code), SNR (Serial Number) and CD (Check Digit)/SD (Spare Digit).

IMEISV (International Mobile station Equipment Identity and Software Version number) may consist of TAC (Type Allocation Code), SNR (Serial Number) and SVN (Software Version Number).

The 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) may be an abbreviation of 5G-GUTI. The 5G-S-TMSI may enable more efficient over-the-air signaling procedures, such as paging (also referred to as paging procedure) and service requests (also referred to as service request procedure). For paging, the UE may be paged using the 5G-S-TMSI. The 5G-S-TMSI may consist of the AMF Set ID, the AMF Pointer and the 5G-TMSI.

The Media Access Control address (MAC address) may be the hardware address of a device connected to the shared media. The MAC address may also be a unique identification number assigned to a UE or network device.

EUI-64 (IEEE Extended Unique Identifier) may be a 64-bit identifier standardized by the IEEE. EUI-64 may also be used when automatically generating IPv6 addresses.

The PEI (Permanent Equipment Identifier) may be information for identifying a UE. The PEI may be defined as a PEI type and an IMEI, IMEISV, MAC address, or EUI-64. Here, the PEI type may indicate an IMEI, IMEISV, MAC address, or EUI-64. That is, when the PEI type indicates an IMEI, the PEI may be composed of a PEI type indicating an IMEI and an IMEISV. Similarly, when the PEI type indicates an IMEISV, the PEI may be composed of a PEI type indicating an IMEISV and an IMEISV. When the PEI type indicates a MAC address, the PEI may be composed of a PEI type indicating a MAC address and an MAC address. When the PEI type indicates an EUI-64, the PEI may be composed of a PEI type indicating an EUI-64 and an EUI-64.

The 5GS mobile identity may be an IE for providing the SUCI, 5G-GUTI, IMEI, IMEISV, 5G-S-TMSI, MAC address, or EUI-64. The 5GS mobile identity may also be referred to as a 5GS mobile identity information element (5GS mobile identity IE).

NPN (Non-Public Network) is a private 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). Note that NPN may refer to SNPN, PNI-NPN, or both.

An SNPN is a network operated by an NPN operator and is not influenced by the functional units provided by a PLMN. In other words, an SNPN is an NPN-dedicated network that is independent of the publicly available PLMN. An SNPN may be a network identified by an SNPN identity (SNPN ID). The SNPN ID may be information that combines a PLMN ID and a Network identifier (NID). The PLMN ID used in the SNPN ID may be information reserved for a private network. For example, the MCC included in the PLMN ID may be 999. Furthermore, when a UE is registered to an SNPN, the registered SNPN may be referred to as a registered SNPN or an RSNPN (registered SNPN).

The NID is information that identifies a network. The SNPN may be identified by a combination of the PLMN ID and the NID. The NID may be information that is unique within the SNPN, or may be information that is unique worldwide.

The PNI-NPN is a network realized by utilizing the functional parts of the PLMN. In other words, the PNI-NPN is an NPN that is virtually realized within the PLMN. Furthermore, the PNI-NPN is an NPN that can be created via the PLMN. The PNI-NPN may be realized by using the function of a network slice. Specifically, the PNI-NPN may be a network that can be realized by using a network slice allocated for the NPN. In this case, the PNI-NPN may be identified by the S-NSSAI, or may be identified by a combination of the S-NSSAI and the CAG ID. Furthermore, the PNI-NPN may be realized by using a DN. Specifically, the PNI-NPN may be a network that can be realized by using a DN for the NPN. In this case, the PNI-NPN may be identified by the DNN, or may be identified by a combination of the DNN and the CAG ID.

CAG (Closed Access Groups) is a group used to realize PNI-NPN. A CAG may be a group identified by a CAG ID. A CAG may be used to prevent UEs that are not authorized for NPN from attempting to access a network slice allocated for the NPN.

The CAG ID is information that identifies a CAG within a PLMN. Furthermore, the CAG ID is a unique identifier within a PLMN.

A CAG cell is a cell where only members of the CAG can obtain normal service. A CAG cell for local service may be a cell where only members of the CAG can obtain local service. A CAG cell for local service may be a cell for local service.

An SNPN-enabled UE may be a UE that can use an SNPN. An SNPN-enabled UE may store at least one piece of information related to an SNPN. In other words, the configuration information of an SNPN-enabled UE may include information indicating that the use of an SNPN is possible. Furthermore, an SNPN-enabled UE may support an SNPN access mode or an SNPN access operation mode. In other words, an SNPN-enabled UE may operate in an SNPN access mode or an SNPN access operation mode.

The SNPN access mode may be a mode in which a UE selects an SNPN. The SNPN access mode may also be a mode in which a UE is registered in an SNPN. Furthermore, the SNPN access mode may be a mode in which a UE is connected to an SNPN. In other words, a UE operating in the SNPN access mode may select only an SNPN when selecting a network. More specifically, a UE operating in the SNPN access mode may select only an SNPN via the Uu interface when selecting a network. In other words, a UE operating in the SNPN access mode may select an SNPN without selecting a PLMN when selecting a network. Here, a UE operating in the SNPN access mode may be expressed as a UE in SNPN access mode. Furthermore, a UE in SNPN access mode may be an SNPN-enabled UE.

SNPN access operation mode is a mode in which a UE connects to an SNPN via SNPN access mode or non-3GPP access. Here, "non-3GPP access" in SNPN may refer to a case in which a UE connects to an SNPN via a PLMN. Furthermore, when a UE operates in SNPN access mode, it may operate in SNPN access operation mode. Furthermore, when a UE does not operate in SNPN access mode, it does not have to operate in SNPN access operation mode. Furthermore, a UE in SNPN access mode may be a UE in SNPN access operation mode. Furthermore, SNPN access operation mode may be read as SNPN access mode.

SNPN selection may be a procedure by which a UE selects an SNPN. SNPN selection may also be a procedure that is performed when a UE connects to an SNPN. SNPN selection may also be referred to as an SNPN selection process or an SNPN selection procedure. SNPN selection may also be a process by which a UE selects an SNPN. SNPN selection may also be a process that is performed when a UE connects to an SNPN.

Here, a UE operating in the SNPN access mode or the SNPN access operation mode may perform SNPN selection. Also, a UE not operating in the SNPN access mode or the SNPN access operation mode may not perform SNPN selection. Also, the SNPN selection may have an automatic SNPN selection mode and a manual SNPN selection mode. Also, the SNPN selection may be performed without registration. In other words, the SNPN selection may be performed when the UE has not completed registration with the network. Also, the SNPN selection may indicate the automatic SNPN selection mode or the manual SNPN selection mode.

An equivalent SNPN (equivalent PLMN) may be an SNPN that is treated as the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more SNPNs that are treated the same as a registered SNPN. Furthermore, an equivalent SNPN may be a PLMN that is treated as the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more PLMNs that are treated the same as a registered SNPN.

Furthermore, the equal SNPN may be one or more SNPNs, or may be a PLMN, identified by the same PLMN ID as any SNPN. For example, the equal SNPN may be one or more SNPNs, or may be a PLMN, identified by the same PLMN ID as a registered SNPN. Further, the equal SNPN may be a PLMN, or may be an equal PLMN of said PLMN, identified by the same PLMN ID as a registered SNPN.

The "temporarily forbidden SNPNs" list may be managed independently for each access type. That is, the temporarily forbidden SNPN list may be managed for each 3GPP access or non-3GPP access. The temporarily forbidden SNPN list may be a list of SNPNs to which the UE cannot temporarily connect. In addition, if the UE supports onboarding services in the SNPN, an additional "temporarily forbidden SNPNs" list for onboarding services may be managed.

　Also, if the UE supports localized services, a temporarily prohibited SNPN list may be maintained for additional localized services.

The "permanently forbidden SNPNs" list may be managed independently for each access type. That is, the permanently forbidden SNPN list may be managed for each 3GPP access or non-3GPP access. The permanently forbidden SNPN list may be a list of SNPNs to which the UE cannot permanently connect. In addition, if the UE supports onboarding services in the SNPN, an additional "permanently forbidden SNPNs" list for onboarding services may be managed.

　Also, if the UE supports localized services, a permanently prohibited SNPN list may be maintained for additional localized services.

In addition, the UE may not be able to initiate a registration procedure for an SNPN in the temporary or permanently prohibited SNPN list.

The list of SNPNs temporarily prohibited for local services may be used if 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.

Furthermore, the list of SNPNs temporarily prohibited for local services may be managed independently for each access type. That is, the list of SNPNs temporarily prohibited for local services may be managed for each 3GPP access or non-3GPP access.

The list of SNPNs permanently prohibited for local services may be used if 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.

Furthermore, the list of SNPNs that are permanently prohibited for local services may be managed independently for each access type. That is, the list of SNPNs that are permanently prohibited for local services may be managed for each 3GPP access or non-3GPP access.

The list of prohibited hosting networks may be used if the UE supports localized services. The list of prohibited hosting networks may be a list of hosting networks to which the UE cannot connect.

In addition, the list of prohibited hosting networks may be managed independently for each access type. That is, the list of prohibited hosting networks may be managed for each 3GPP access or non-3GPP access.

The list of prohibited hosting networks may also be maintained as a list of temporary prohibited hosting networks and/or a list of permanently prohibited hosting networks.

Localized services may be services that are provided in a specific/restricted area. Localized services may also be time-restricted. Localized services may be referred to as local services. Localized services may also be achieved through applications such as live or on-demand voice or video streams, video games, or IMS. Localized services may also be achieved through connectivity such as UE to UE or UE to DN.

Also, local services may be read as a hosting network. Local services may be provided by a hosting network. Local services are supported may be read as a hosting network is supported.

A localized service provider may be an application provider or a network operator that localizes a service and provides it to an end user via a hosting network. A localized service provider may also be an application provider or a network operator that provides a localized service. A localized service provider may also be a DN. A localized service provider may also be a core network.

A hosting network may be a network that provides connectivity to local services. A hosting network may also be an NPN. Here, the NPN may be an SNPN or a PNI-NPN.

Also, a hosting network may be read as local services. Also, a hosting network is supported may be read as local services are supported.

The home network may be the network that owns the subscription or credentials of the UE currently in use. The home network may be a PLMN or an NPN. Here, the NPN may be an SNPN or a PNI-NPN.

A home network service may be a service provided to a UE based on a subscription agreed with a home network operator. A home network service may also be a service provided by a home network.

The CAG information list may be a list containing one or more CAG IDs. The CAG information list may also be an extended CAG information list.

The CAG information list may also be a list including one or more CAG IDs for a local service. The CAG information list may also be a CAG information list for a local service. The CAG information list may also be an extended CAG information list for a local service.

The CAG information list may also be a list containing one or more CAG IDs for the hosting network. The CAG information list may also be a CAG information list for the hosting network. The CAG information list may also be an extended CAG information list for the hosting network.

The CAG information list may also consist of zero or more entries. Each entry may include one PLMN ID. Each entry may also include an Allowed CAG list. The Allowed CAG list may include zero or more CAG-IDs. Each entry may also optionally include an indication that the UE is only allowed to connect to 5GS via a CAG cell. Each entry may also include an indication that the UE is only allowed to connect to 5GS via a CAG cell for localized services.

UEs attached via E-UTRAN may perform location registration (LR) via the tracking area update procedure. UEs registered via NG-RAN may perform location registration (LR) via the registration procedure.

The prioritized list of SNPNs for localized services may include an SNPN ID, and/or a Group ID for Network Selection (GIN), and/or a subnetwork ID. The prioritized list of SNPNs for localized services may also include validity information. Here, the validity information may indicate a valid time or may indicate location information. The location information may be a TAI list or may be geographic information.

The first SNPN may be an SNPN indicating that an onboarding service is permitted. The first SNPN may also be an SNPN that matches the onboarding service information. The first SNPN may also be an SNPN that matches the onboarding service information if the onboarding service information is set in advance. In other words, the first SNPN may be an SNPN that indicates that an onboarding service is permitted and that matches the onboarding service information. In yet other words, the first SNPN may be an SNPN that indicates that a local service is permitted and that matches the onboarding service information if the onboarding service information is set in advance.

The second SNPN may be an SNPN that does not indicate that the onboarding service is permitted. The second SNPN may also be an SNPN that does not match the onboarding service information. The second SNPN may also be an SNPN that does not match the onboarding service information if the onboarding service information is set in advance. In other words, the second SNPN may be an SNPN that does not indicate that the onboarding service is permitted and does not match the onboarding service information. In yet other words, the second SNPN may be an SNPN that does not indicate that the onboarding service is permitted and does not match the onboarding service information if the onboarding service information is set in advance.

The third SNPN may be an SNPN indicating that local services are permitted. The third SNPN may also be an SNPN that matches the local service information. The third SNPN may also be an SNPN that matches the local service information if the local service information is set in advance. In other words, the third SNPN may be an SNPN indicating that local services are permitted and that matches the local service information. In yet other words, the third SNPN may be an SNPN indicating that local services are permitted and that matches the local service information if the local service information is set in advance.

The fourth SNPN may be an SNPN that does not indicate that local services are permitted. The fourth SNPN may also be an SNPN that does not match the local service information. The fourth SNPN may also be an SNPN that does not match the local service information if the local service information is pre-configured. In other words, the fourth SNPN may be an SNPN that does not indicate that local services are permitted and does not match the local service information. In yet other words, the fourth SNPN may be an SNPN that does not indicate that local services are permitted and does not match the local service information if the local service information is pre-configured.

[2.7. Description of Identification Information in the Present Embodiment]
Next, the identification information transmitted, received, and/or stored and/or managed by each device in this embodiment will be described.

First, the first identification information is information for identifying the SNPN. The first identification information may be an SNPN ID. Furthermore, the first identification information may be information that combines a PLMN ID and an NID. Here, the PLMN ID may be composed of an MCC and an MNC. Furthermore, the PLMN ID may be information within the 5GS mobile identity.

Next, the second identification information may be information indicating whether or not Closed Access Group (CAG) is supported. The second identification information may be information indicating that CAG is supported. The second identification information may also be information indicating that CAG is not supported. The second identification information may also be 5GMM capability. The second identification information may also be information included in 5GMM capability.

Next, the third identification information may be information indicating whether or not a hosting network is supported. The third identification information may be information indicating that a hosting network is supported. Furthermore, the third identification information may be information indicating that a hosting network is not supported. Furthermore, the third identification information may be 5GMM capability. Furthermore, the third identification information may be information included in the 5GMM capability.

The third identification information may also be information indicating whether or not a local service is supported. The third identification information may also be information indicating that a local service is supported. The third identification information may also be information indicating that a local service is not supported.

The third identification information may also be information indicating a request to use a hosting network. In other words, the third identification information may also be information indicating a request to connect to a hosting network. The third identification information may also be information indicating a request to use a local service. In other words, the third identification information may also be information indicating a request to connect to a local service.

The third identification information may also be information indicating that authentication and/or authorization is requested from the hosting network. The third identification information may also be information indicating that authentication and/or authorization is requested from a local service.

Next, the tenth identification information may be a list including one or more CAG IDs. The tenth identification information may be a CAG information list. Also, the tenth identification information may be an extended CAG information list.

The tenth identification information may also be a list including one or more CAG IDs for the local service. The tenth identification information may also be a CAG information list for the local service. The tenth identification information may also be an extended CAG information list for the local service.

The tenth identification information may also be a list including one or more CAG IDs for the hosting network. The tenth identification information may also be a CAG information list for the hosting network. The tenth identification information may also be an extended CAG information list for the hosting network.

The 11th identification information may then be a list containing identifiers of available hosting networks. The 11th identification information may be a list containing SNPN IDs and/or CAG IDs. Here, the hosting network may be an NPN. In other words, the hosting network may be an SNPN or a PNI-NPN.

[3. Description of procedures used in each embodiment]
Next, the procedures used in each embodiment will be described.

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

[3.1. Getting system information]
First, a process related to acquiring system information will be described. Acquiring system information may be a process in which a UE acquires and stores information broadcast by an NG-RAN node that provides access to one or more SNPNs.

Here, the information broadcast by the NG-RAN may include one or more PLMN IDs and/or a list of one or more NIDs per PLMN ID identifying the NPNs to which the NG-RAN provides access. Furthermore, the presence of an NID list for a PLMN ID may indicate that the associated PLMN ID and NID identify an SNPN. In other words, the UE may be able to identify the SNPN based on the NID list per PLMN ID broadcast by the NG-RAN node. Thus, the NG-RAN node may broadcast information identifying the SNPN and the UE may receive and store the information identifying the SNPN.

The information broadcast by the NG-RAN node may further include human-readable network names for each SNPN, used only for manual SNPN selection, and/or information to prevent UEs that do not support the SNPN from accessing the cell, and/or an indication for each SNPN of whether UE access using credentials from a Credentials Holder (CH) is supported, and/or a list of Group IDs (GINs) for network selection supported for each SNPN, and/or an indication for each SNPN of whether to allow registration attempts from UEs that are not explicitly configured to select the SNPN.

Furthermore, if the SNPN supports onboarding of UEs to the SNPN, the NG-RAN node may additionally broadcast for each cell an indication indicating whether onboarding is currently enabled for the SNPN (onboarding enabled indication). In other words, for example, the NG-RAN node may broadcast information identifying the ON-SNPN in cells where the SNPN is available as an ON-SNPN.

The acquisition of system information by the UE may be based on a system information acquisition procedure. In addition, the UE acquiring the system information may or may not be operating in the SNPN access mode.

In addition, the UE may use or take into account the SNPN information included in the received system information to perform SNPN selection, or SNPN selection for onboarding services, or SNPN selection for local services in the network selection described below.

[3.2. Network Selection]
Next, a process related to network selection will be described. Network selection is a process for an unregistered UE to select a PLMN, NPN, or SNPN to register with before performing a registration procedure. For example, the UE may perform network selection to select a different network when the UE is powered on, when the SIM is removed or inserted, or when the registration procedure fails.

　Below, we explain PLMN selection and SNPN selection.

3.2.1. PLMN selection
First, the PLMN selection will be described.

PLMN selection may be a procedure by which a UE selects a PLMN. Here, the PLMN selection may be performed when a UE connects to a PLMN. Here, the PLMN selection may be referred to as a PLMN selection process or a PLMN selection procedure.

Here, a UE not operating in the SNPN access mode or the SNPN access operation mode may perform PLMN selection. Also, a UE operating in the SNPN access mode or the SNPN access operation mode may not perform PLMN selection. Also, PLMN selection may be performed without registration. In other words, PLMN selection may be performed when the UE has not completed registration with the network. PLMN selection may include an automatic PLMN selection mode and a manual PLMN selection mode. Note that PLMN selection may refer to either the automatic PLMN selection mode or the manual PLMN selection mode.

In addition, there may be two PLMN selection modes: automatic PLMN selection mode and manual PLMN selection mode.

The PLMN selection may also be a PLMN selection for localized services in a PLMN. The PLMN selection may also be a PLMN selection for localized services in a CAG cell. The PLMN selection may also be a PLMN selection for localized services in a PNI-NPN.

The PLMN selection may also be a GAG selection. If the UE supports CAG, the PLMN selection may also be a CAG selection.

The PLMN selection steps are explained below.

The UE may select and attempt to register with another PLMN if available and permissible for (i), (ii), (iii), (iv), and (v) in the following order:

(i) The UE may select the HPLMN or the higher priority EHPLMN that is available.

(ii) The UE may select each PLMN in the "User Controlled PLMN Selector with Access Technology" data file in the SIM.

(iii) The UE may select each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM or each PLMN stored in the UE.

(iv) The UE may select, in random order, other PLMNs that have received high quality signals.

(v) The UE may select other PLMNs in order of decreasing signal quality.

(vi) The UE may select a PLMN that is a prohibited PLMN that broadcasts the PLMN ID of a PLMN determined by the UE to be in a disaster state or that broadcasts disaster-related indications and that meets the following conditions:

(vi-a)(vi-a) may be the behavior when the indication of applicability of the list of PLMNs to be used in disaster situations provided by the VPLMN is set to true. The UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the PLMN ID of the UE-determined PLMN to be in disaster situation, if any, in an order based on this list. Otherwise, if the UE does not have a stored list of PLMNs to be used in disaster situations associated with the PLMN ID of the UE-determined PLMN to be in disaster situation, the UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the PLMN ID of the HPLMN, if any, in an order based on this list.

(vi-b) If the indication of applicability of the list of PLMNs to be used in disaster situations provided by the VPLMN is set to false, the UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the HPLMN, if any, in an order based on this list.

(vii) The UE may broadcast the PLMN ID of the PLMN that the UE determines is in a disaster state or may select a PLMN, in a random order, relative to other prohibited PLMNs for which it will broadcast a disaster-related indication.

When carrying out the above procedures, the following requirements may apply:

In (a)(i) to (vii), the behavior when the UE supports CAG is as follows:

(a-1) If the UE is provided with a non-empty CAG information list, the UE may consider the PLMN indicated by the NG-RAN cell only if:

(a-1-A) The cell is a CAG cell, and the cell broadcasts a CAG-ID for a PLMN for which there is an entry with the PLMN ID of the PLMN in the CAG information list, and the CAG ID is included in the Allowed CAG list.

(a-1-B) Or, if the cell is not a CAG cell and there is no entry in the CAG information list with the PLMN ID of the PLMN. Or, if the cell is not a CAG cell and there is an entry in the CAG information list with the PLMN ID of the PLMN, but the entry does not contain an indication that the UE is only allowed to access 5GS via the CAG cell.

(a-2) If the UE is provided with an empty CAG information list or if the UE is not provided with a CAG information list, the UE may consider a PLMN indicated by an NG-RAN cell only if the cell is not a CAG cell.

If there are one or more available and permissible PLMNs, but registration to those PLMNs fails due to location registration failure or an entry in the CAG information list blocks the registration attempt, the UE again selects such a PLMN and transitions to the restricted service state.

　After completing the above PLMN selection process, the UE may perform the registration procedure for the selected network.

Furthermore, when the UE performs initial registration to a PLMN, the UE may indicate that the PLMN selected in the PLMN selection is the PLMN ID selected by the NG-RAN node. Furthermore, the NG-RAN may notify the AMF of the PLMN ID that identifies the selected PLMN indicated by the UE.

3.2.2. SNPN Selection
Next, SNPN selection will be described.

SNPN selection may be a procedure by which a UE selects an SNPN. SNPN selection may also be a procedure that is performed when a UE connects to an SNPN. SNPN selection may also be referred to as an SNPN selection process or an SNPN selection procedure. SNPN selection procedure may also be an automatic SNPN selection procedure or a manual SNPN selection procedure. SNPN selection may also be a process by which a UE selects an SNPN. SNPN selection may also be a process that is performed when a UE connects to an SNPN.

Here, a UE operating in the SNPN access mode or the SNPN access operation mode may perform SNPN selection. Also, a UE not operating in the SNPN access mode or the SNPN access operation mode may not perform SNPN selection. Also, the SNPN selection may have an automatic SNPN selection mode and a manual SNPN selection mode. Also, the SNPN selection may be performed without registration. In other words, the SNPN selection may be performed when the UE has not completed registration with the network. Also, the SNPN selection may indicate the automatic SNPN selection mode or the manual SNPN selection mode.

The SNPN selection may also be referred to as an SNPN selection mode procedure. The SNPN selection mode procedure may also be an automatic SNPN selection mode procedure or a manual SNPN selection mode procedure.

Furthermore, the SNPN selection mode procedure may be a procedure executed in an automatic SNPN selection mode, or a procedure executed in a manual SNPN selection mode. In other words, the automatic SNPN selection mode procedure may be a procedure executed in an automatic SNPN selection mode, and the manual SNPN selection procedure may be a procedure executed in a manual SNPN selection mode.

　Also, there may be two modes for SNPN selection: automatic SNPN selection mode and manual SNPN selection mode.

The SNPN selection may also be an SNPN selection for onboarding services in the SNPN. The SNPN selection may also be an SNPN selection for local services in the SNPN.

ON-SNPN selection may be an SNPN selection for an onboarding service, and may be performed when the UE onboards. Note that ON-SNPN selection may be one form of SNPN selection.

Also, a UE performing SNPN selection or ON-SNPN selection may be operating in SNPN access mode.

Furthermore, SNPN selection or ON-SNPN selection may have an automatic SNPN selection mode and a manual SNPN selection mode. Furthermore, automatic SNPN selection may be a form of automatic network selection, and manual SNPN selection may be a form of manual network selection.

Here, in the automatic SNPN selection mode, the UE may select an SNPN based on the last NSPN to which it registered, or a subscribed SNPN, or a "list of preferred SNPNs" which is a list of SNPNs managed by the UE or CH, etc.

Also here, in manual SNPN selection mode, the UE may provide the user with a list of SNPNs and associated human readable network names of the available SNPNs.

Furthermore, in acquiring the above-mentioned system information, the UE may perform SNPN selection using or considering the information received from the NG-RAN node and/or the information identifying the SNPN stored by the UE. Here, a UE supporting UE onboarding may have ON-SNPN selection information preset. Furthermore, a UE performing ON-SNPN selection may match the preset ON-SNPN selection information with the system information acquired from the above-mentioned NG-RAN node. More specifically, in ON-SNPN selection, the UE may match, for example, information identifying the SNPN (SNPN network identifier) and/or GIN included in the preset ON-SNPN selection information with the onboarding enabled indication included in the above-mentioned acquired system information.

The steps for selecting an SNPN are explained below.

If there is at least one entry in the list of subscriber data, the UE may select one entry, if any, in the list of subscriber data to use for automatic SNPN selection. Also, if there is at least one entry in the list of subscriber data, the UE may select a PLMN subscription, if any, to use for automatic SNPN selection.

Also, if there are zero or more entries in the list of subscriber data, the UE has a USIM with a PLMN subscription, and the UE is provided with SNPN selection parameters associated with the PLMN subscription, the UE may select one entry, if any, in the list of subscriber data to use for automatic SNPN selection.Also, if there are zero or more entries in the list of subscriber data, the UE has a USIM with a PLMN subscription, and the UE is provided with SNPN selection parameters associated with the PLMN subscription, the UE may select a PLMN subscription, if any, to use for automatic SNPN selection.

The UE may select one SNPN in the following order (a) through (c), if available and permitted:

(a) The UE may select the SNPN with which the UE was last registered.

(b) The UE may select an SNPN identified by the SNPN identifier of a subscribed SNPN in the selected entry of the list of subscriber data in the UE, if any.

(c) If the UE supports connection to an SNPN using credentials from the credential holder, or using the SNPN selection parameters of the selected entry in the list of subscriber data, or an SNPN associated with the selected PLMN, it may select the following SNPN:

(c-1) The UE may broadcast an indication that it supports connections using credentials from the credential holder and may select an SNPN identified by an SNPN identifier included in a user-controlled priority list of preferred SNPNs.

(c-2) The UE may broadcast an indication that it supports connections using credentials from the credential holder and select an SNPN identified by an SNPN identifier included in the credential holder-controlled priority list of preferred SNPNs.

(c-3) The UE may broadcast an indication that it supports connections using credentials from a credential holder and may select an SNPN that broadcasts a GIN that is included in the credential holder controlled priority list of GINs.

(c-4) The UE may select an SNPN identified by an SNPN identifier that is not included in the SNPN selection parameters of an entry in the list of subscriber data or in the SNPN selection parameters associated with the PLMN subscription, that does not broadcast a GIN included in the credential holder controlled preference list of GINs, and that broadcasts an indication that the SNPN will allow registration attempts from UEs that are not explicitly configured to select an SNPN.

The UE may restrict the UE's search to NG-RAN access technologies for the SNPN.

Once the UE has selected an SNPN, if a PLMN subscription is selected, the UE may attempt to register to the selected SNPN using the NG-RAN access technology and the subscriber identifier and credentials from the selected entry in the list of subscriber data or from the USIM.

If the registration matches, the UE may indicate the selected SNPN.

If registration is not possible because there is no SNPN that is available, authorized and identified by an SNPN identifier in an entry in the UE's subscriber data list, the UE may indicate "no service" to the user, wait until a new SNPN is available, authorized and identified by an SNPN identifier in an entry in the UE's subscriber data list, and repeat the SNPN selection mode procedure and/or the registration procedure.

If there were SNPNs available, permitted and identified by SNPN identifiers in entries in the UE's subscriber data list, but registration to those SNPNs failed due to a location registration failure, the UE may again select one of those SNPNs and transition to a restricted service state.

Next, we will explain SNPN selection in the onboarding service.

If the UE needs to connect to one SNPN for onboarding services in the SNPN, the UE may select one first SNPN.

Also, if one or more first SNPNs are available, the UE selects one of those first SNPNs based on a priority list of SNPNs for the onboarding service. In other words, if there are one or more available first SNPNs, the UE selects one of those first SNPNs based on a priority list of SNPNs for the onboarding service.

Also, for onboarding services in an SNPN, the UE does not need to select a second SNPN.

Once the UE has selected an SNPN for the onboarding service, the UE may attempt initial registration for the onboarding service on the SNPN on the selected SNPN. Also, once the UE has selected an SNPN for the onboarding service, the UE may attempt initial registration for the onboarding service on the SNPN on the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

If the registration fails and one or more other first SNPNs are available, the UE may select such other SNPN based on a priority list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the SNPN on the selected SNPN. Also, if the registration fails and one or more other first SNPNs are available, the UE may select such other SNPN based on a priority list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the SNPN on the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

In other words, if the registration fails and there are one or more other available first SNPNs, the UE may select such other SNPN based on a priority list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the SNPN on the selected SNPN. Also, if the registration fails and there are one or more other available first SNPNs, the UE may select such other SNPN based on a priority list of SNPNs for the onboarding service and may attempt initial registration for the onboarding service at the SNPN on the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

Also, if registration fails and one or more other first SNPNs are available, the UE may perform an SNPN selection for a non-onboarding service in the SNPN according to the UE's SNPN selection mode.

In other words, if registration fails and there are one or more other available first SNPNs, the UE may perform an SNPN selection for a non-onboarding service in the SNPN according to the UE's SNPN selection mode.

If registration fails and no other first SNPN is available, the UE may perform SNPN selection for a non-onboarding service in the SNPN according to the UE's SNPN selection mode.

In other words, if registration fails and there is no other first SNPN available, the UE may perform SNPN selection for non-onboarding services in the SNPN according to the UE's SNPN selection mode.

If registration is not possible because the first SNPN is not available, the UE may indicate to higher layers that there is no onboarding service, transition to a limited service state, wait until a new first SNPN is available, and repeat the SNPN selection mode procedure and/or the registration procedure. Also, if registration is not possible because the first SNPN is not available, the UE may perform an SNPN selection for a non-onboarding service SNPN in the SNPN selection mode of the UE.

In other words, if registration is not possible because no first SNPN is available, the UE may indicate to higher layers that there is no onboarding service, transition to a limited service state, wait until one new first SNPN is available, and repeat the SNPN selection mode procedure and/or registration procedure. Also, if registration is not possible because no first SNPN is available, the UE may perform an SNPN selection for a non-onboarding service SNPN in the UE's SNPN selection mode.

Also, if there are one or more first SNPNs but registration to all of the first SNPNs fails due to location registration failure, the UE may indicate to higher layers that there is no onboarding service, transition to a limited service state, wait until one new first SNPN becomes available, and repeat the SNPN selection mode procedure and/or the registration procedure.Also, if there are one or more first SNPNs but registration to all of the first SNPNs fails due to location registration failure, the UE may perform an SNPN selection for a SNPN that is not for onboarding service, using the UE's SNPN selection mode.

　After completing the above SNPN selection process, the UE may perform the registration procedure for the selected network.

Furthermore, when the UE performs initial registration to an SNPN or ON-SNPN, the UE may indicate that the SNPN or ON-SNPN selected in the SNPN selection is the PLMN ID and NID selected by the NG-RAN node. Further, the NG-RAN may notify the AMF of the PLMN ID and NID identifying the selected SNPN indicated by the UE.

[3.3. Registration Procedure]
First, the registration procedure will be described with reference to FIG. 6. The registration procedure is a procedure in 5GS. In this chapter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering to the access network_B, and/or the core network_B, and/or the DN. If the UE is not registered to the network, it can execute this procedure at any timing, such as when the power is turned on. In other words, if the UE is in a deregistered state (RM-DEREGISTERED state), it can start this procedure at any timing. Furthermore, each device (particularly the UE and the AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure. Note that the registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or deregistered state) for 3GPP access and the registration state for non-3GPP access.

The registration procedure may also be a registration procedure for initial registration. The registration procedure may also be a registration procedure for mobility and periodic registration update. The registration procedure may also be referred to as registration.

Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network and/or for periodically notifying the network of the status of the UE from the UE and/or for updating certain parameters related to the UE in the network.

This procedure may also be a registration procedure for a local service or a registration procedure for a hosting network.

The UE may initiate the registration procedure when mobility crosses TAs. In other words, the UE may initiate the registration procedure when it moves to a TA different from the TA indicated in the TA list it holds. Furthermore, the UE may initiate the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may initiate the registration procedure when there is a change in the capability information and/or preferences regarding the establishment of the UE's PDU session. Furthermore, the UE may initiate the registration procedure periodically. Furthermore, the UE may initiate the registration procedure based on the completion of a UE setting update procedure. Note that the UE can execute the registration procedure at any timing, without being limited to these.

Furthermore, the UE may periodically initiate the registration procedure even when in the registered state.

Note that the registration procedure performed based on the mobility of the UE and the registration procedure performed periodically may be expressed as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure performed based on the mobility of the UE, or may be a registration procedure performed periodically. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a setting update of the UE. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration update may be a registration procedure other than the registration procedure for initial registration.

Next, each step of the registration procedure will be explained. Note that the registration procedure explained below may be a registration procedure for initial registration, or a registration procedure for mobility and registration renewal.

First, the UE starts the registration procedure by sending a registration request message to the AMF (S800) (S802) (S804). Specifically, the UE sends an RRC message including a registration request message to the 5G AN (or gNB) (S800). The registration request message is a NAS message. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

Here, the UE may transmit one or more of the first to third pieces of identification information in a registration request message and/or an RRC message. In more detail, the UE may transmit one or more of the first to third pieces of identification information in a registration request message and/or an RRC message, or may transmit one or more of the first to third pieces of identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, a PDCP layer).

By transmitting these pieces of identification information, the UE may indicate to the network that the UE supports each function, or may indicate the UE's request. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Furthermore, the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

Furthermore, the UE may indicate to the network the contents indicated by the identification information included in the registration request message by including one or more of the first to third identification information in the registration request message and transmitting the message.

The UE may select and determine whether to include one or more of the first to third pieces of identification information in the registration request message based on subscriber information, and/or network status, and/or user registration information, and/or context held by the UE, etc.

The UE may also transmit identification information other than the first to third identification information in the registration request message.

When a 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to forward the registration request message (S802). The 5G AN (or gNB) can select an AMF based on information included in the registration request message and/or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S804).

When the AMF receives a registration request message, it can execute a first condition determination. The first condition determination is for determining whether the network (or AMF) accepts the UE's request. When the first condition determination is true, the AMF starts the procedure in (A) of FIG. 6, whereas when the first condition determination is false, the AMF starts the procedure in (B) of FIG. 6.

The first condition determination may be performed based on the reception of a registration request message, and/or each identification information included in the registration request message, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network status, and/or user registration information, and/or a context held by the AMF. For example, if the network permits the UE request, the first condition determination may be true, and if the network does not permit the UE request, the first condition determination may be false. In addition, if the network to which the UE is registered and/or a device in the network supports the function requested by the UE, the first condition determination may be true, and if the function requested by the UE is not supported, the first condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be false. In addition, the conditions for determining whether the first condition determination is true or false do not have to be limited to the above-mentioned conditions.

First, we will explain the case where the first condition judgment is true. In the procedure of (A) in Figure 6, 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). Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) as part of an RRC message.

The AMF may include one or more of the identification information items 10 to 11 in the registration acceptance message and transmit it. By transmitting these identification information items, the AMF may indicate that the network supports each function, or that the UE's request has been accepted. Furthermore, when multiple identification information items are transmitted and received, two or more of these identification information items may be configured as one or more identification information items. Furthermore, the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

Furthermore, the AMF may indicate to the UE the contents indicated by one or more of the identification information items 10 to 11 by including them in a registration acceptance message and sending the message. The AMF may also indicate to the UE the contents of these identification information items by sending a registration acceptance message.

The AMF may select and decide whether to include one or more of the identification information items 10 to 11 in the registration acceptance message based on each received identification information, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network status, and/or user registration information, and/or context held by the AMF, etc.

In addition, the AMF may also include identification information other than identification information 10 to 11 in the registration acceptance message.

The AMF may also indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and/or subscriber information, and/or network capability information, and/or operator policies, and/or network status, and/or user registration information, and/or context held by the AMF, etc.

Furthermore, the AMF may include information indicating that some of the UE's requests have been rejected in the registration acceptance message and send it, or may indicate the reason why some of the UE's requests have been rejected by sending the information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE's requests have been rejected by receiving the information indicating that some of the UE's requests have been rejected. The reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

Next, the UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S806). By receiving the registration acceptance message, the UE can recognize that the UE's request in the registration request message has been accepted, and the contents of the various identification information included in the registration acceptance message.

Then, the UE may or may not send a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S808). Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) as part of an RRC message.

Then, the AMF may or may not receive a registration completion message via the 5G AN (gNB) (S808).

Each device completes the procedure in Figure 6 (A) based on sending and receiving a registration acceptance message and/or a registration completion message.

Next, we will explain the case where the first condition judgment is false. In the procedure of (B) in Figure 6, 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 transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) as part of an RRC message.

Here, the AMF may send the registration rejection message including one or more of the identification information items 10 to 11. Furthermore, by sending these identification information items, the AMF may indicate that the UE request has been rejected, or may indicate the reason why the UE request has been rejected.

Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the registration rejection message by including one or more of the identification information items 10 to 11 in the registration rejection message and sending the message. The AMF may also indicate to the UE the contents of these identification information items by sending a registration rejection message.

The AMF may select and decide whether to include one or more of the identification information items 10 to 11 in the registration rejection message based on each received identification information, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network status, and/or user registration information, and/or context held by the AMF, etc.

Furthermore, the AMF may indicate that the UE's request via the registration request message has been rejected by sending a registration rejection message. Furthermore, the AMF may include information indicating the reason for the rejection in the registration rejection message and send it, or may indicate the reason for the rejection by sending the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). By receiving the registration rejection message, the UE can recognize that the UE's request in the registration request message has been rejected, and the contents of the various identification information included in the registration rejection message.

In addition, if the UE does not receive a registration rejection message even after a predetermined period of time has elapsed after sending a registration request message, the UE may recognize that the UE's request has been rejected.

Each device completes step (B) of this procedure based on sending and receiving the registration rejection message.

In addition, procedure (B) in Figure 6 may be started if procedure (A) in Figure 6 is aborted.

Each device completes the registration procedure based on the completion of the procedure in (A) or (B) of Figure 6. Furthermore, each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure in (A) of Figure 6. Furthermore, each device may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) based on the completion of the procedure in (B) of Figure 6, or may transition to a state in which the UE is not registered in the network.

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

Furthermore, the UE may store the identification information received with the registration accept or reject message and may recognize the network's decision based on the completion of the registration procedure.

[4. Embodiment]
Next, each embodiment will be described.

[4.1. First embodiment]
First, a first embodiment will be described. In this chapter, the first embodiment may be referred to as the present embodiment.

In this embodiment, the network may be a hosting network. Here, the hosting network may be an SNPN.

In addition, in this embodiment, PLMN selection and/or SNPN selection and/or registration procedures may be performed.

Below, we will explain each step of this procedure.

If the UE needs to connect to one SNPN for local services in the SNPN, the UE may select one third SNPN.

Also, if one or more third SNPNs are available, the UE selects one of those third SNPNs based on a priority list of SNPNs for local services. In other words, if there are one or more third SNPNs available, the UE selects one of those third SNPNs based on a priority list of SNPNs for local services.

Also, for localized services in the SNPN, the UE does not need to select the fourth SNPN.

Once the UE has selected an SNPN for localized services, the UE may attempt initial registration for localized services on the SNPN on the selected SNPN. Also, once the UE has selected an SNPN for localized services, the UE may attempt initial registration for localized services on the SNPN on the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

If the registration fails and/or one or more other tertiary SNPNs are available, the UE may select such other SNPN based on a priority list of SNPNs for localized services and may attempt initial registration for localized services at the SNPN on the selected SNPN. Also, if the registration fails and/or one or more other tertiary SNPNs are available, the UE may select such other SNPN based on a priority list of SNPNs for localized services and may attempt initial registration for localized services at the SNPN on the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

In other words, if the registration fails and/or there are one or more other available third SNPNs, the UE may select such other SNPN based on a priority list of SNPNs for localized services and may attempt initial registration for localized services at the SNPN on the selected SNPN. Also, if the registration fails and/or there are one or more other available third SNPNs, the UE may select such other SNPN based on a priority list of SNPNs for localized services and may attempt initial registration for localized services at the SNPN on the selected SNPN using the NG-RAN access technology and default UE credentials for primary authentication.

Also, if registration fails and/or one or more other third SNPNs are available, the UE may perform a non-local service SNPN selection in the SNPN according to the UE's SNPN selection mode.

In other words, if registration fails and/or there are one or more other available third SNPNs, the UE may perform a non-local service SNPN selection in the SNPN according to the UE's SNPN selection mode.

If registration fails and/or no other third SNPN is available, the UE may perform a non-local service SNPN selection at the SNPN according to the UE's SNPN selection mode.

In other words, if registration fails and/or there is no other third SNPN available, the UE may perform a non-local service SNPN selection in the SNPN according to the UE's SNPN selection mode.

If registration is not possible because a third SNPN is not available, the UE may indicate to higher layers that there is no local service, transition to a limited service state, wait until a new third SNPN is available, and repeat the SNPN selection mode procedure and/or the registration procedure. Also, if registration is not possible because a third SNPN is not available, the UE may perform a non-local service SNPN selection in the SNPN via the UE's SNPN selection mode.

In other words, if registration is not possible because no third SNPN is available, the UE may indicate to higher layers that there is no local service, transition to a limited service state, wait until one new third SNPN is available, and repeat the SNPN selection mode procedure and/or registration procedure. Also, if registration is not possible because no third SNPN is available, the UE may perform a non-local service SNPN selection in the SNPN via the UE's SNPN selection mode.

Also, if one or more third SNPNs exist but registration to all of the third SNPNs fails due to location registration failure, the UE may indicate to higher layers that there is no local service, transition to a limited service state, wait until one new third SNPN becomes available, and repeat the SNPN selection mode procedure and/or the registration procedure.Also, if one or more third SNPNs exist but registration to all of the third SNPNs fails due to location registration failure, the UE may perform an SNPN selection in the SNPN that is not for local service, using the UE's SNPN selection mode.

Also, if one or more third SNPNs exist but registration to all of the third SNPNs has failed due to a location registration failure, the UE may wait until one new third SNPN becomes available and perform the SNPN selection mode procedure and/or the registration procedure for the new third SNPN that has become available.

Also, if one or more third SNPNs exist but registration to all of the third SNPNs fails, the UE may indicate to higher layers that there is no local service, transition to a limited service state, wait until one new third SNPN becomes available, and repeat the SNPN selection mode procedure and/or the registration procedure.Also, if one or more third SNPNs exist but registration to all of the third SNPNs fails, the UE may perform an SNPN selection for a non-local service SNPN in the SNPN via the UE's SNPN selection mode.

Also, if one or more third SNPNs exist but registration to all of the third SNPNs has failed, the UE may wait until one new third SNPN becomes available and perform the SNPN selection mode procedure and/or the registration procedure for the new third SNPN that has become available.

　After completing the above SNPN selection process, the UE may perform the registration procedure for the selected network.

Furthermore, when the UE performs initial registration to an SNPN or ON-SNPN, the UE may indicate that the SNPN or ON-SNPN selected in the SNPN selection is the PLMN ID and NID selected by the NG-RAN node. Further, the NG-RAN may notify the AMF of the PLMN ID and NID identifying the selected SNPN indicated by the UE.

[4.2. Second embodiment]
Next, a second embodiment will be described. In this chapter, the second embodiment may be referred to as the present embodiment.

In this embodiment, the network may be a hosting network. Here, the hosting network may be a PNI-NPN.

In addition, in this embodiment, PLMN selection and/or SNPN selection and/or registration procedures may be performed.

Below, we will explain each step of this procedure.

The UE may select and attempt to register with another PLMN if available and permissible for (i), (ii), (iii), (iv), and (v) in the following order:

(i) The UE may select the HPLMN or the higher priority EHPLMN that is available.

(ii) The UE may select each PLMN in the "User Controlled PLMN Selector with Access Technology" data file in the SIM.

(iii) The UE may select each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM or each PLMN stored in the UE.

(iv) The UE may select, in random order, other PLMNs that have received high quality signals.

(v) The UE may select other PLMNs in order of decreasing signal quality.

(vi) The UE may select a PLMN that is a prohibited PLMN that broadcasts the PLMN ID of a PLMN determined by the UE to be in a disaster state or that broadcasts disaster-related indications and that meets the following conditions:

(vi-a)(vi-a) may be the behavior when the indication of applicability of the list of PLMNs to be used in disaster situations provided by the VPLMN is set to true. The UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the PLMN ID of the UE-determined PLMN to be in disaster situation, if any, in an order based on this list. Otherwise, if the UE does not have a stored list of PLMNs to be used in disaster situations associated with the PLMN ID of the UE-determined PLMN to be in disaster situation, the UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the PLMN ID of the HPLMN, if any, in an order based on this list.

(vi-b) If the indication of applicability of the list of PLMNs to be used in disaster situations provided by the VPLMN is set to false, the UE may select each PLMN in the list of PLMNs to be used in disaster situations stored in the UE associated with the HPLMN, if any, in an order based on this list.

(vii) The UE may broadcast the PLMN ID of the PLMN that the UE determines is in a disaster state or may select a PLMN, in a random order, relative to other prohibited PLMNs for which it will broadcast a disaster-related indication.

When carrying out the above procedures, the following requirements may apply:

In (a)(i) to (vii), the behavior when the UE supports CAG is as follows:

　(a-1) If the UE is provided with a non-empty CAG information list, the UE may consider the PLMN indicated by the NG-RAN cell only if:

(a-1-A) The cell is a CAG cell, and the cell broadcasts a CAG-ID for a PLMN for which there is an entry with the PLMN ID of the PLMN in the CAG information list, and the CAG ID is included in the Allowed CAG list.

(a-1-B) Or, if the cell is not a CAG cell and there is no entry in the CAG information list with the PLMN ID of the PLMN. Or, if the cell is not a CAG cell and there is an entry in the CAG information list with the PLMN ID of the PLMN, but the entry does not contain an indication that the UE is only allowed to access 5GS via the CAG cell.

(a-1-C) If the cell is a CAG cell for local services, and/or if the cell broadcasts a CAG-ID for a PLMN for which there is an entry with the PLMN ID of the PLMN in the CAG information list related to the local services, and/or if the CAG ID is included in the Allowed CAG list related to the local services.

(a-2) If the UE is provided with an empty CAG information list or if the UE is not provided with a CAG information list, the UE may consider a PLMN indicated by an NG-RAN cell only if the cell is not a CAG cell.

(a-3) If the UE is provided with a non-empty CAG information list and/or an indication that the UE is allowed to connect to 5GS via a CAG cell for localized services, the UE may consider the PLMNs indicated by the NG-RAN cell only if:

　After completing the above PLMN selection process, the UE may perform the registration procedure for the selected network.

Furthermore, when the UE performs initial registration to a PLMN, the UE may indicate that the PLMN selected in the PLMN selection is the PLMN ID selected by the NG-RAN node. Furthermore, the NG-RAN may notify the AMF of the PLMN ID that identifies the selected PLMN indicated by the UE.

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

In addition, a program for realizing the functions of the embodiment according to this embodiment may be recorded on a computer-readable recording medium. The program recorded on this recording medium may be read into a computer system and executed to realize the functions. The "computer system" here refers to a computer system built into a device, and includes hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that can be read by a computer.

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

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

The embodiment of this example has been described above in detail with reference to the drawings, but the specific configuration is not limited to this embodiment, and design changes and the like that do not deviate from the gist of this example are also included. Furthermore, this example can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of this example. Also included are configurations in which elements described in the above embodiments are substituted for elements that have similar effects.

Claims (1)

1. A User Equipment (UE),
   The UE includes a controller,
   If there are one or more first SNPNs, but the location registration fails and the registration to all of the first SNPNs fails, the control unit:
   Wait until a new primary SNPN is available,
   performing a registration procedure for said new first SNPN that has become available;
   The UE is characterized in that the first SNPN is an SNPN that indicates that local services are allowed and matches local service information.

Images