User equipment (UE)

Abstract

When UE has connected to a VPLMN as a network for roaming in 5GS, it is not certain whether URSP rules associated with an HPLMN or URSP rules associated with the VPLMN will be selected by the UE or the network, delivered to the UE by the network, and used by the UE as the URSP rules to be used by the UE. Provided are a selection method and a communication means that involve UE and a network transmitting / receiving identification information or the like that indicates capability information and / or a request and, on the basis of the transmitted / received identification information, selecting and delivering URSP rules associated with an HPLMN and / or URSP rules associated with a VPLMN as URSP rules to be used by the UE as connected to the VPLMN.

Description

UE (User Equipment)

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

[0002] The 3GPP (3rd Generation Partnership Project) is currently studying, discussing, and formulating specifications to support new procedures and functions in the system architecture of the 5th generation (5G) mobile communication system, the 5GS (5G System) (see Non-Patent Documents 1 to 5). Regarding the 5G User Equipment (UE) Policy, which was discussed up to the Release 17 standard, Release 18 will discuss the expansion of its functions.

[0003] 3GPP TS 23.501 V17.3.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 17)3GPP TS 23.502 V17.3.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 17)3GPP TS 23.503 V17.3.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 17)3GPP TS 24.501 V17.5.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17)3GPP TS 24.526 V17.5.0 (2021-12); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; User Equipment (UE) policies for 5G System (5GS); Stage 3 (Release 17)

[0004] In 5GS (5G System), a new core network called 5GCN (5G Core Network) is being considered to provide a wide variety of services. Currently, an extension of the 5G UE (User Equipment) Policy that has been discussed so far is being considered for 5GS.

[0005] The UE Route Selection Policy (URSP) rules, which are provided as part of the policy information used when a UE connects to a VPLMN (roaming destination network), have traditionally only supported URSP rules associated with HPLMNs. However, in the study of extending 5G UE policies, support for URSP rules associated with VPLMNs is being considered. However, the details of the methods for selecting between these two types of URSP rules, the methods for transmitting and receiving, and the procedures and methods for storing and managing URSP rules in the UE or network equipment have not been clarified.

[0006] The present invention has been made in consideration of the above circumstances, and provides a method for a UE connected to a VPLMN and each device in the network to select appropriate URSP rules, a procedure for distributing the selected URSP rules, and information and procedures transmitted and received between the UE and the network necessary to execute these.

[0007] In an embodiment of the present invention, a UE (User Equipment) is a UE (User Equipment) comprising a transceiver unit, a memory unit, and a control unit, wherein the UE does not support URSP (UE Route Selection Policy) rules associated with a VPLMN (Visited Public Land Mobile Network), and when the transceiver unit receives URSP rules associated with the VPLMN in a procedure for receiving URSP rules initiated during the registration procedure, the control unit does not store the URSP rules associated with the VPLMN in the memory unit.

[0008] According to one embodiment of the present invention, a method is provided for a UE that has registered and connected to a VPLMN, a roaming network, to select either the URSP rules associated with the HPLMN or the URSP rules associated with the VPLMN as the URSP rules provided as part of the UE policy information in the connected network.

[0009] FIG. 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS / 5GS). FIG. 3 is a diagram illustrating a device configuration of a UE. FIG. 4 is a diagram illustrating a configuration of an access network device (gNB) in 5GS. FIG. 5 is a diagram illustrating a configuration of a core network device (AMF / SMF / UPF / PCF) in 5GS. FIG. 6 is a diagram illustrating a registration procedure. FIG. 7 is a diagram illustrating a UE policy distribution procedure.

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The best mode for carrying out the present invention will be described below with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which the present invention is applied will be described.

[0011] [1. System Overview] First, FIG. 1 is a diagram for explaining an overview 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.

[0012] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network _A80, core network _A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6.

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

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

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

[0016] The 4G system EPS (Evolved Packet System) includes 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) includes a UE, an access network B, and a core network B, but may further include a DN.

[0017] A UE is a device that can connect to a network service 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). A UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device that can connect to both EPS and 5GS. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that a UE may be referred to as a user device or a terminal device.

[0018] Furthermore, access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are deployed in the E-UTRAN. Note that, hereinafter, the eNB 45 may be referred to by abbreviating the symbol eNB. If there are multiple eNBs, the eNBs are connected to each other, for example, via an X2 interface. Furthermore, one or more access points are deployed in the wireless LAN access network.

[0019] Furthermore, 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. Note that, hereinafter, the gNB 122 may be referred to by its symbol abbreviated as eNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs and connects to the 5GCN via an NG interface (including an N2 interface or an 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 EPS system. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

[0020] 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 include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF).

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

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

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

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

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

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

[0027] The core network (core network_A and / or core network_B) and the access network (access network_A and / or access network_B) may differ depending on the mobile communication operator.

[0028] Also, while FIG. 1 illustrates 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 mean connecting to a communication terminal or a server device located in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal or a server device located in the PDN. The PDN may be referred to as the DN, and the DN may be referred to as the PDN.

[0029] In addition, hereinafter, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device sends or receives a message and / or performs a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein send or receive a message and / or perform a procedure.

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

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

[0032] In addition, access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A may include devices not shown in Fig. 2. For example, core network _A and / or core network _B and / or PDN_A and / or DN_A may include an AUSF (Authentication Server Function) and an AAA (Authentication, Authorization, and Accounting) server (AAA-S). The AAA server may be located outside the core network.

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

[0034] The AAA server is a device that has authentication, authorization, and accounting 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 the core network _A and / or the core network _B, but may be included in the PLMN or the SNPN. 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 or the SNPN that is managed by a third party.

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

[0036] [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, as logical (virtual) hardware configured on general-purpose hardware, or 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.

[0037] Each storage unit (storage unit_A340, storage unit_A440, storage unit_B540) in each device / function mentioned below is configured with, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Each storage unit can store not only information originally configured at the time of shipment but also various information transmitted and received between the device / function and itself (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each storage unit can also store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Each storage unit may also store this information for each UE. Furthermore, when interworking between 5GS and EPS is performed, each storage unit can store control messages and user data transmitted and received between the device / function included in 5GS and / or EPS. In this case, not only information transmitted and received via the N26 interface but also information transmitted and received without via the N26 interface can be stored.

[0038] [2.1. Device configuration of UE] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 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.

[0039] The control unit _A300 is a functional unit that controls the operation and functions of the entire UE. The control unit _A300 realizes various processing in the UE by reading and executing various programs stored in the memory unit _A340 as necessary.

[0040] The transceiver unit _A320 is a functional unit for wireless communication 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.

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

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

[0043] [2.1.1. Device Configuration of gNB] Next, an example of the device configuration of a gNB will be described using Figure 4. The gNB is composed of a control unit _B400, an antenna 410, a network connection unit _B420, a transceiver unit _B430, and a memory unit _B440. The control unit _B400, the network connection unit _B420, the transceiver unit _B430, and the memory unit _B440 are connected via a bus. The transceiver unit _B430 is connected to the antenna 410.

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

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

[0046] The transceiver unit _B430 is a functional unit for wireless communication with the UE via the antenna 410. That is, the gNB can transmit and receive user data and / or control information to and from the UE using the transceiver unit _B430.

[0047] 2, a gNB in ​​a 5G AN can communicate with an AMF via an N2 interface by using a network connection unit _B420, and can communicate with a UPF via an N3 interface, and can communicate with a UE by using a transceiver unit _B430.

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

[0049] [2.1.2. AMF Device Configuration] Next, an example of the AMF device configuration will be explained using Figure 5. The AMF is composed of a control unit _B500, a network connection unit _B520, and a memory unit _B540. The control unit _B500, the network connection unit _B520, and the memory unit _B540 are connected via a bus. The AMF may be a node that handles the control plane.

[0050] The control unit _B500 is a functional unit that controls the operation and functions of the entire AMF. The control unit _B500 realizes various processes in the AMF by reading and executing various programs stored in the memory unit _B540 as needed.

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

[0052] 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 _A520, 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 with the UE via the N1 interface by using the network connection unit _A520. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via the 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit _A520.

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

[0054] The AMF has functions such as 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) functions, connection management (CM) functions, reachability management functions, mobility management functions for UEs, etc., transferring SM (Session Management) messages between the UE and the SMF, access authentication (Access Authorization) functions, security anchor functionality (SEA), security context management (SCM), a function to support the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function to support sending and receiving NAS signals with the UE via the N3IWF, and a function to authenticate UEs connected via the N3IWF.

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

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

[0057] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which UE_A10's location information is not known to the network, or a state in which UE_A10 is unreachable from the network. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or may establish a 5GMM context by performing the registration procedure.

[0058] In addition, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have 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.

[0059] 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 include 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 include 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). Note that the non-connected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.

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

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

[0062] In addition, the N3IWF is a device and / or function located between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.

[0063] [2.1.3. Device configuration of SMF] Next, an example of the device configuration of SMF132 will be explained using Figure 5. The SMF is composed of a control unit _B500, a network connection unit _B520, and a memory unit _B540. The control unit _B500, the network connection unit _B520, and the memory unit _B540 are connected via a bus. The SMF may be a node that handles the control plane.

[0064] The control unit _B500 is a functional unit that controls the operation and functions of the entire SMF. The control unit _B500 realizes various processing in the SMF by reading and executing various programs stored in the memory unit _B540 as needed.

[0065] The network connection unit _B520 is a functional unit for connecting the SMF to the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can send and receive user data and / or control information between the AMF, and / or UPF, and / or PCF, and / or UDM using the network connection unit _B520. The network connection unit _B520 may be a transceiver unit.

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

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

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

[0069] [2.1.4. UPF Device Configuration] Next, an example of the UPF device configuration will be explained using Figure 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.

[0070] The control unit _B700 is a functional unit that controls the operation and functions of the entire UPF.The control unit _B700 realizes various processing in the UPF by reading and executing various programs stored in the memory unit _B740 as needed.

[0071] The network connection unit _B720 is a functional unit for the UPF to connect to a base station device (gNB), and / or SMF, and / or DN within the 5G AN. That is, the UPF 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 SMF, and / or DN within the 5G AN. The network connection unit _B520 may be a transceiver unit.

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

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

[0074] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a gateway between DN and core network_B that forwards user data), packet routing and forwarding functions, 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, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notifications.

[0075] 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 a function for converting non-IP communication and IP communication. Furthermore, 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.

[0076] The user plane refers to user data transmitted and received between a UE and a 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 U-Plane or UP.

[0077] 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 referred to as the control plane or the C-Plane.

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

[0079] [2.1.5. PCF Device Configuration] Next, an example of the device configuration of the PCF used in each embodiment will be described using Figure 5. The PCF is composed of a control unit 500, a network connection unit 520, and a memory unit 540. The control unit 500, the network connection unit 520, and the memory unit 540 are connected via a bus.

[0080] The control unit _500 is a functional unit that controls the operation and functions of the entire PCF. The control unit _500 may process all functions that other functional units in the PCF (network connection unit _520, memory unit _540) do not have. The control unit _500 realizes various processes in the PCF by reading and executing various programs stored in the memory unit _540 as needed.

[0081] The network connection unit _B520 is a functional unit for connecting the PCF to the AMF, and / or SMF, and / or AF (Application Function). In other words, the PCF can send and receive control information between the AMF, and / or SMF, and / or AF using the network connection unit _B520. The network connection unit _B520 may be a transmitting and receiving unit.

[0082] By using the network connection unit _520, the PCF can communicate with the AMF via the N15 interface, with the SMF via the N7 interface, and with the AF via the N5 interface (the interface between the PCF and the AF).

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

[0084] The PCF has functions to support a unified policy framework, provide policy rules to control plane functions to enforce them, and access subscription information. The PCF also has functions to generate PCC rules, first PCC rules, and / or second PCC rules, and URSP (UE Route Selection Policy) rules (URSP rule(s)). All of these functions may be controlled by the control unit_500.

[0085] In this specification, a PCF in an HPLMN is also referred to as an H-PCF (Home PCF), and a PCF in a VPLMN is also referred to as a V-PCF (Visited PCF). Furthermore, for example, URSP rules generated by an H-PCF are also referred to as URSP rules associated with an HPLMN, and URSP rules generated by a V-PCF are also referred to as URSP rules associated with a VPLMN.

[0086] During roaming, the V-PCF can connect to the H-PCF via the N24 interface (interface between PCFs). That is, the V-PCF can send and receive control information to and from the H-PCF using the network connection unit _520.

[0087] [2.1.6. Description of Other Devices and / or Functions] Next, other devices and / or functions will be described.

[0088] The PCF has a function to provide policy rules.

[0089] The UDM also has functions such as authentication credential processing, user identification processing, access authentication, registration / mobility management, and subscription management.

[0090] The PCRF is connected to the PGW and / or PDN and has a function of managing QoS for data delivery. For example, it manages the QoS of the communication path between the UE_A10 and the PDN. Furthermore, the PCRF may be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when transmitting and receiving user data.

[0091] The HSS is connected to the MME and / or SCEF and has a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, when controlling access to the MME. Furthermore, the HSS may be connected to a location management device different from the MME.

[0092] [2.2. Explanation of Terms Used in the Present Embodiment] Next, highly specialized terms used in each embodiment and identification information used in the procedures will be explained.

[0093] A network (NW) refers to at least a portion of an access network _B, a core network _B, and a DN. Furthermore, one or more devices included in at least a portion of an access network _B, a core network _B, and a 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 within the network (network devices and / or control devices) transmit, receive, and / or process messages. Conversely, when a device within the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0094] Furthermore, the network may refer to a PLMN (Public Land Mobile Network), an NPN (Non-Public Network), or an SNPN (Stand-alone Non-Public Network). Furthermore, when it is expressed that a UE performs network selection, it may indicate that the UE performs PLMN selection, or that the UE performs SNPN selection. In this specification, the access network, core network, PLMN, and SNPN are also referred to as networks or NWs.

[0095] In addition, the SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure.Each procedure may be initiated from the UE or from the NW.

[0096] Furthermore, an MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used in procedures for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc. In addition, the procedures for MM or MM procedures may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

[0097] In addition, 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 may be a service similar to the EPS service.

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

[0099] Also, 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 via a communication method other than IP.

[0100] There are two types of access types: 3GPP access and non-3GPP access. Here, information indicating the access type may be configured as an access type information element (IE), and may be, for example, identification information indicating the access type used in signaling between the UE and the core network or in transmitting and receiving user data.

[0101] Furthermore, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN that provides a PDU connectivity service and a UE, but it may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data to and from 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, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session.

[0102] Each device (UE, and / or access network device, and / or core network device) may associate one or more pieces of identification information with a PDU session and manage them. These pieces of identification information may include one or more of the following: 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, the identification information associated with the PDU sessions may be the same or different.

[0103] Furthermore, the DNN (Data Network Name) may be identification information that identifies the 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 PGW_A30 / UPF_A235 that connects the core network _B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0104] Furthermore, the PDU (Protocol Data Unit / Packet 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. Furthermore, Ethernet may 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 or the like 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 if the UE is capable of using both IPv4 and IPv6.

[0105] A PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator, which is a (mobile) communications carrier, and the operator can be identified by a PLMN ID. An operator may manage one or more PLMNs. In this document, PLMN may also mean PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN).

[0106] Furthermore, the UE may maintain an Equivalent HPLMN list in its Universal Subscriber Identity Module (USIM) to identify one or more Equivalent HPLMNs (E-HPLMNs). A PLMN different from the HPLMN and / or E-HPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN). The current PLMN may be a PLMN requested by the UE, a PLMN selected by the UE, an RPLMN, a PLMN permitted by the network, and / or a PLMN to which a core network device that transmits or receives messages belongs. Note that a service provided by a PLMN may be referred to as a PLMN service, and a service provided by an SNPN may be referred to as an SNPN service.

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

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

[0109] Here, an NST is a logical representation of one or more NFs associated with resource requirements for providing the required communication services and capabilities. In other words, an NSI may be a collection of multiple NFs within the core network_B190. An NSI may also be a logical network configured to separate user data delivered by services, etc. An NS may be configured with one or more NFs. The NFs configured in an NS may or may not be devices shared with other NSs.

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

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

[0112] Furthermore, the S-NSSAI transmitted and received between the UE and the NW may be expressed as an S-NSSAI IE (Information element). Furthermore, the S-NSSAI IE transmitted and received between the UE and the NW may be configured with an S-NSSAI configured with an SST and / or SD of the registered PLMN, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN to which the S-NSSAI is mapped. One or more S-NSSAIs stored in the UE and / or NW may be configured with an SST and / or SD, or may be configured with an S-NSSAI configured with an SST and / or SD, and / or an SST and / or SD indicating the S-NSSAI of the HPLMN to which the S-NSSAI is mapped.

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

[0114] Also, a configured NSSAI is an NSSAI provided and stored in the UE. The UE may store a configured NSSAI for each PLMN. The UE may store a configured NSSAI in association with a PLMN. In this document, a configured NSSAI associated with a PLMN may be expressed as a configured NSSAI for the PLMN, a configured NSSAI of the PLMN, a configured NSSAI for the PLMN, or a configured NSSAI associated with the PLMN. Also, a UE may not be associated with a PLMN and may store a configured NSSAI that is valid for all PLMNs, and such a configured NSSAI may be referred to as a "default configured NSSAI."

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

[0116] The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be expressed as the configured S-NSSAI. The configured S-NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI. Alternatively, the S-NSSAI of the PLMN may be expressed as the "configured S-NSSAI", and the S-NSSAI to which the configured S-NSSAI is mapped to the HPLMN may be expressed as the "mapped S-NSSAI to the configured NSSAI for the PLMN".

[0117] Furthermore, the requested NSSAI is an NSSAI provided by the UE to the network during the registration procedure. In the registration procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI or configured NSSAI stored by the UE. In the PDU session establishment procedure, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI stored by the UE.

[0118] The requested NSSAI may be information indicating a network slice requested by the UE. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is transmitted in a NAS message, such as a registration request message or a PDU session establishment request message, transmitted from the UE to the network, or in a Radio Resource Control (RRC) message including a Non-Access-Stratum (NAS) message.

[0119] Also, the allowed NSSAI is information indicating one or more network slices to which the UE is permitted. In other words, the allowed NSSAI is information identifying a network slice to which the network permits the UE to connect.

[0120] The UE and / or NW may store and manage the allowed NSSAI for each access (3GPP access or non-3GPP access) as information of the UE. The UE and / or NW may further manage the allowed NSSAI in association with a registration area.

[0121] Furthermore, the UE and / or NW may store and manage an allowed NSSAI associated with a PLMN as information of the UE. The allowed NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0122] In this document, an allowed NSSAI associated with a PLMN and an access type may be expressed as an allowed NSSAI for the PLMN and access type, or an allowed NSSAI for the access type of the PLMN. An S-NSSAI included in an allowed NSSAI may be expressed as an allowed S-NSSAI. An allowed S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0123] Further, the rejected NSSAI is information indicating one or more network slices to which the UE is not permitted. In other words, the rejected NSSAI is information identifying a network slice to which the network does not permit the UE to connect. The rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value.

[0124] Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network may store and manage the rejected NSSAI appropriately based on the rejection reason value associated with each S-NSSAI.

[0125] Furthermore, the rejected NSSAI may be included in an NAS message transmitted from the network to the UE, such as a registration accept message, a configuration update command, or a registration reject message, or in an RRC message including an NAS message. The S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI.

[0126] The rejected NSSAI may be any one of the first to third rejected NSSAIs, the pending NSSAI, and the first NSSAI, or a combination of these. An S-NSSAI included in the rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0127] The UE and / or NW may store and manage the rejected NSSAI associated with the PLMN as information of the UE. The rejected NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

[0128] A tracking area is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may be composed of multiple cells. Furthermore, a tracking area may be 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, a tracking area may be a routing area, a location area, or anything similar. Hereinafter, a tracking area may be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking area code) and a PLMN.

[0129] A registration area is a collection of one or more TAs assigned to a UE by the AMF. 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 signals for tracking area update. 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.

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

[0131] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in an application or a network. Furthermore, the UE ID may be information for identifying a user.

[0132] The N1 NAS signaling connection is a connection between the UE and the network (AMF), and may be managed and exist independently for 3GPP access and non-3GPP access.

[0133] The state in which the N1 NAS signaling connection is established may be 5GMM-CONNECTED mode. The state in which the N1 NAS signaling connection is not established may be 5GMM-IDLE mode.

[0134] In other words, a state in which an N1 NAS signaling connection is established over 3GPP access may be expressed as the UE being in 5GMM-CONNECTED mode over 3GPP access, and a state in which an N1 NAS signaling connection is not established over 3GPP access may be expressed as the UE being in 5GMM-IDLE mode over 3GPP access.

[0135] Similarly, a state in which an N1 NAS signaling connection is established over non-3GPP access may be expressed as the UE being in 5GMM-CONNECTED mode over non-3GPP access, and a state in which an N1 NAS signaling connection is not established over non-3GPP access may be expressed as the UE being in 5GMM-IDLE mode over non-3GPP access.

[0136] An SNPN (Stand-alone Non-Public Network) is a type of NPN that is a 5GS network deployed for non-public use. It is operated by an NPN operator and is independent of the NFs provided by the PLMN. In other words, an SNPN may be an NPN-dedicated network that is independent of the PLMN. An SNPN is identified by a combination of a PLMN ID and a Network Identifier (NID). The PLMN ID used for the SNPN ID may be information reserved for private networks; for example, the MCC included in the PLMN ID may be 999.

[0137] Furthermore, a UE capable of using an SNPN may support an SNPN access mode. A UE configured to operate in the SNPN access mode may be able to select an SNPN and register with the SNPN, but may not be able to select a PLMN. A UE configured to operate in the SNPN access mode may be able to perform an SNPN selection procedure, but may not be able to perform a PLMN selection procedure. Even if a UE is capable of using an SNPN (SNPN enabled), a UE not configured to operate in the SNPN access mode may not be able to select an SNPN and register with the SNPN, but may be able to select a PLMN. A UE not configured to operate in the SNPN access mode may not be able to perform an SNPN selection procedure, but may be able to perform a PLMN selection procedure.

[0138] Also, a UE operating in SNPN access mode may be able to select an SNPN via Uu (3GPP access). Also, a UE operating in SNPN access mode may be able to select an SNPN via Uu or NWu established via a PDU session provided by a selected PLMN via Uu or NWu (non-3GPP access). Also, a UE not operating in SNPN access mode may be able to select a PLMN via Uu or NWu established via a PDU session provided by a selected SNPN via Uu or NWu (non-3GPP access).

[0139] An SNPN can use the functionality of a PLMN, so in this document, a PLMN may refer to an SNPN.

[0140] An NID (Network Identifier) ​​is information that identifies a network. An SNPN may be identified by information that combines a PLMN ID and an NID. The NID may be unique information within the SNPN, or may be unique information.

[0141] A public network integrated NPN is a network realized using the functional units of a PLMN. In other words, a public network integrated NPN is an NPN that is virtually realized within a PLMN. Furthermore, a public network integrated NPN is an NPN that can be created via a PLMN. Note that a public network integrated NPN may be realized using the functionality of a network slice. Specifically, a public network integrated NPN may be a network that can be realized by using a network slice allocated for the NPN. In this case, the public network integrated NPN may be identified by an S-NSSAI or a combination of an S-NSSAI and a CAG ID.

[0142] Furthermore, the public network integrated NPN may be realized using a DN. Specifically, the public network integrated NPN may be a network that can be realized by using a DN for the NPN. In this case, the public network integrated NPN may be identified by the DNN or by a combination of the DNN and a CAG ID.

[0143] A CAG (Closed Access Groups) ID is information that identifies a group of subscribers that are permitted to connect to one or more cells associated with the CAG. A CAG may be a group identified by a CAG ID. A CAG is a group used when implementing a public network integrated NPN in a network slice. A CAG may be used to prevent UEs that are not permitted to access a network slice allocated for the NPN from attempting to access the network slice. Furthermore, a CAG ID is unique information within a PLMN.

[0144] An SNPN-enabled UE is a UE configured to 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.

[0145] Also, the SNPN access mode is a mode in which a UE selects only an SNPN. More specifically, a UE in the SNPN access mode may be a mode of a UE when performing procedures, processes, etc. for registering and connecting to an SNPN. Furthermore, a UE that performs SNPN selection or ON-SNPN selection as network selection, or performs a normal registration procedure to an SNPN, or performs a registration procedure for onboarding, or performs a procedure for remote provisioning, must operate in the SNPN access mode. Here, a UE operating in the SNPN access mode may be referred to as a UE in the SNPN access mode. Furthermore, a UE in the SNPN access mode may be a UE in which an SNPN is enabled.

[0146] Also, the SNPN access operation mode is a mode of connecting to the SNPN via the SNPN access mode or non-3GPP access. Here, "non-3GPP access" in the SNPN may refer to a case where the UE connects to the SNPN via a PLMN. Also, when the UE operates in the SNPN access mode, it may operate in the SNPN access operation mode. Also, when the UE does not operate in the SNPN access mode, it may not operate in the SNPN access operation mode. Furthermore, a UE in the SNPN access mode may be a UE in the SNPN access operation mode.

[0147] A UE operating in an SNPN access mode or an SNPN access operation mode may perform the SNPN selection process. A UE not operating in an SNPN access mode or an SNPN access operation mode may not perform the SNPN selection process. The SNPN selection process may include an automatic SNPN selection mode and a manual SNPN selection mode. The SNPN selection procedure may be performed without registration. In other words, the SNPN selection procedure may be performed when the UE has not completed registration with the network.

[0148] Furthermore, a UE not operating in the SNPN access mode or the SNPN access operation mode may perform the PLMN selection process. A UE operating in the SNPN access mode or the SNPN access operation mode may not perform the PLMN selection process. The PLMN selection procedure may be performed without registration. In other words, the PLMN selection procedure may be performed when the UE has not completed registration with the network. The PLMN selection process may include an automatic PLMN selection mode and a manual PLMN selection mode.

[0149] A UE in an SNPN access operation mode may refer to a UE in an SNPN access mode or a UE that accesses an SNPN via non-3GPP. In other words, even if a UE is not in an SNPN access mode, it may be a UE in an SNPN access operation mode if it connects to an SNPN via non-3GPP.

[0150] A Non-Public Network (NPN) is a private network that is not intended for general use, but is used by specific users for specific purposes, such as for private use by companies. There are two types of NPNs: Stand-alone Non-Public Networks (SNPNs) and Public network integrated NPNs. Note that when referring to NPNs below, it can refer to both SNPNs and Public network integrated NPNs.

[0151] A UE operating in an SNPN access mode or an SNPN access operation mode may perform an onboarding network selection process. In other words, when an onboarding network selection process is performed, the UE may operate in an SNPN access mode or an SNPN access operation mode.

[0152] Furthermore, the URSP (UE Route Selection Policy) may be a policy used by the UE to determine whether a detected application is associated with an established PDU session, offloaded to a non-3GPP access outside the PDU session, routed via a ProSe (Proximity based Services) Layer 3 UE-to-Network relay outside the PDU session, or can trigger the establishment of a new PDU session. Note that the URSP may be a policy included in the UE policy information provided by the PCF.

[0153] Furthermore, URSP rules (UE Route Selection Policy rules) may be configured as a list of one or more URSP (UE Route Selection Policy) rules. Furthermore, each URSP rule may be configured as a rule precedence, a traffic descriptor, and / or a list of route selection descriptors. Here, the traffic descriptor may be used to specify a matching condition determined by the UE based on the URSP.

[0154] Here, the rule priority of the URSP rules indicates the order in which the URSP rules are enforced in the UE. When the UE receives URSP rules, that is, when it receives one or more URSP rules, it may refer to the rule priority of each URSP rule and apply the URSP rules in order from the highest priority rule.

[0155] Furthermore, the traffic descriptors in the URSP rules indicate when the URSP rules should be applied, and may be composed of application descriptors, IP descriptors, domain descriptors, non-IP descriptors, data network names (DNNs), and connection capabilities.

[0156] Additionally, the application descriptor in the traffic descriptor in the URSP rule may include an OS ID and an OS application ID.

[0157] Furthermore, the IP descriptor in the traffic descriptor in the URSP rule indicates information that identifies the destination of the IP traffic, and may include, for example, an IP address, an IPv6 network prefix, a port number, a protocol number, and the like.

[0158] Furthermore, the domain descriptors in the traffic descriptors in the URSP rules may indicate the FQDN (Fully Qualified Domain Name) of the destination.

[0159] Furthermore, the non-IP descriptor in the traffic descriptor in the URSP rule may indicate information that identifies the destination of non-IP traffic (for example, ethernet traffic or unstructured traffic).

[0160] Also, the DNN in the traffic descriptor in the URSP rule may be information about the DNN provided by the application.

[0161] Additionally, the connection capability in the traffic descriptor in the URSP rule may indicate information provided by an application of the UE when the UE requests connection to a network using a certain capability.

[0162] Additionally, a Route Selection Descriptor List in a URSP rule may consist of one or more Route Selection Descriptors, each of which may consist of a Route Selection Descriptor Precedence and / or Route Selection Components.

[0163] The rule selection descriptor priority indicates the order in which the route selection descriptors are applied. When the UE receives a route selection descriptor list, that is, when it receives one or more route selection descriptors, it may refer to the rule selection descriptor priority in each route selection descriptor and apply the route selection descriptors in order from the highest priority to the lowest priority.

[0164] The route selection configuration may also include SSC Mode Selection, and / or Network Slice Selection, and / or DNN Selection, and / or PDU Session Type Selection, and / or Non-Seamless Offload indication, and / or Access Type preference.

[0165] Here, the SSC mode selection may indicate that the application's traffic is to be routed through a PDU session of the specified SSC mode.

[0166] The network slice selection may also indicate that the application's traffic is to be routed using a PDU session that supports one or more of the indicated S-NSSAIs.

[0167] The DNN selection may also indicate that the application's traffic should be routed using a PDU session that supports one or more of the indicated DNNs.

[0168] The PDU session type selection may also indicate that the application's traffic should be routed using a PDU session that supports the indicated PDU session type.

[0169] Additionally, the non-seamless offload indication may indicate that the traffic of the application is to be offloaded to a non-3GPP access.

[0170] Furthermore, the access type preference may indicate an access type for establishing a PDU session when the UE needs to establish a PDU session. Here, the access type may indicate 3GPP, non-3GPP, multi-access, or eATSSS. Here, eATSSS may be specified when establishing a PDU session using the eATSSS function, and may indicate 3GPP access or non-3GPP access corresponding to the SA PDU session to be established.

[0171] The URSP rules may include URSP rules associated with the HPLMN and URSP rules associated with the VPLMN. Here, the URSP rules associated with the HPLMN may be generated by the PCF of the HPLMN. The URSP rules associated with the VPLMN may be generated by the V-PCF, which is the PCF of the VPLMN. The URSP rules may be associated with a PLMN and transmitted and received between the UE and the network. More specifically, for example, the information element storing the URSP rules may include the MCC and MNC of the PLMN associated with each URSP rule. Furthermore, the URSP rules may be associated with a PLMN and stored in each device of the UE or the network.

[0172] Furthermore, the URSP rules used by the UE may be generated or determined based on the destination network and / or the destination network's policy and / or the UE's capabilities and / or the network's capabilities, the UE's subscription, etc. More specifically, for example, if the UE is registered or connected to an HPLMN, the URSP rules associated with the HPLMN may be used. Also, for example, if the UE is registered or connected to a roaming VPLMN, the UE may use the URSP rules associated with the HPLMN or the URSP rules associated with the VPLMN.

[0173] SUPI (Subscription Permanent Identifier) ​​is a globally unique permanent identification information of 5G subscribers assigned to each subscriber in the 5G system. The type of SUPI can be IMSI, NSI (Network Specific Identifier), GLI (Global Line Identifier), or GCI (Global Cable Identifier).

[0174] A Subscription Concealed Identifier (SUCI) is a privacy-preserving identifier that contains a concealed SUPI.

[0175] [2.3. Description of Identification Information in This Embodiment] Next, the identification information transmitted, received, stored, and managed by each device in this embodiment will be described.

[0176] In this embodiment, the first identification information is capability information indicating that the UE supports the use of URSP rules associated with the VPLMN, where supporting the URSP rules associated with the VPLMN may indicate that the UE can use the URSP rules generated by the VPLMN or a PCF in the VPLMN when connecting to and / or registering with the VPLMN.

[0177] Here, the UE supporting the use of the URSP rules associated with the VPLMN may indicate that the UE supports the URSP rules associated with the VPLMN.

[0178] A UE supporting URSP rules associated with a VPLMN may indicate that it is capable of storing URSP rules generated / sent by the VPLMN or a PCF within the VPLMN, or may indicate that it is capable of receiving URSP rules generated by the VPLMN or a PCF within the VPLMN from the VPLMN or a PCF within the VPLMN.

[0179] A UE supporting URSP rules associated with a VPLMN may indicate that it is capable of storing both URSP rules generated / sent by a VPLMN or a PCF within the VPLMN and URSP rules generated / sent by a HPLMN or a PCF within the HPLMN.

[0180] The URSP rules distributed by the VPLMN may be URSP rules generated by the VPLMN or a PCF of the VPLMN, or may be URSP rules generated and / or distributed by a V-PCF (Visited PCF). The URSP rules may include URSP rules associated with the VPLMN and URSP rules associated with the HPLMN.

[0181] Here, the URSP rules associated with the HPLMN may be URSP rules generated by the HPLMN or the PCF of the HPLMN, or, for example, when the UE is connected to a VPLMN, may be URSP rules delivered to the UE from the H-PCF (Home PCF) via the V-PCF.

[0182] Here, for example, the UE may indicate that it supports the use of URSP rules associated with the VPLMN by including the first identification information in the registration request message, or may indicate that it does not support the use of URSP rules associated with the VPLMN by not including the first identification information in the registration request message.

[0183] Alternatively, the first identification information may be capability information indicating whether the UE supports the use of URSP rules associated with the VPLMN. In this case, for example, the first identification information may indicate that the UE does not support the use of URSP rules associated with the VPLMN. The first identification information may be a 5GMM capability IE or may be included in the 5GMM capability IE.

[0184] The first identification information may be information indicating that the UE supports URSP rules associated with a VPLMN, or supports URSP rules associated with a HPLMN, or supports both.

[0185] In this specification, unless otherwise specified, the first identification information refers to capability information indicating that the UE supports the use of the URSP rules associated with the VPLMN.

[0186] Furthermore, the first identification information may include the content of the second identification information described below. More specifically, for example, the UE may transmit the first identification information to the network to indicate that the UE supports the use of the URSP rules associated with the VPLMN and requests the use of the URSP rules associated with the VPLMN. In other words, the UE may transmit the first identification information to the network or each device in the network to indicate that it requests the use of the URSP rules associated with the VPLMN.

[0187] The second identification information in this embodiment is identification information indicating that the UE requests the URSP rules associated with the VPLMN.

[0188] For example, a UE attempting to register and / or connect to a VPLMN may indicate a request to use the URSP rules associated with the VPLMN as the URSP rules by sending second identification information in a message to the network or each device in the network.

[0189] Furthermore, the second identification information may include the content of the first identification information. More specifically, for example, the UE may transmit the second identification information to the network to indicate that the UE supports the use of the URSP rules associated with the VPLMN and requests the use of the URSP rules associated with the VPLMN. In other words, the UE may transmit the second identification information to the network or each device in the network to indicate that it supports the use of the URSP rules associated with the VPLMN.

[0190] Alternatively, the content of the second identification information may be included in the first identification information. More specifically, for example, the UE may transmit the first identification information to the network to indicate that the UE supports the use of URSP rules associated with the VPLMN and requests the use of the URSP rules associated with the VPLMN. That is, the UE may transmit the first identification information to the network or each device in the network to indicate that the UE requests the use of the URSP rules associated with the VPLMN.

[0191] The second identification information may be information indicating a preference of the UE regarding URSP rules associated with the VPLMN. More specifically, the UE may indicate a preference regarding URSP rules associated with the VPLMN using the second identification information, thereby indicating that it requests URSP rules associated with the VPLMN.

[0192] In this embodiment, the third identification information may be capability information indicating that the VPLMN to which the UE is registered and / or connected supports delivery of URSP rules associated with the VPLMN, and the third identification information may be identification information to be included in a response message when the network or each device receives a request message including the first identification information from the UE and accepts the first identification information.

[0193] Furthermore, for example, the network or each device may indicate that it has accepted the UE's request or the use of the URSP rules associated with the VPLMN by sending the third identification information to the UE. In other words, the UE that has received the third identification information may recognize that the network or each device has accepted the use of the URSP rules associated with the VPLMN.

[0194] Note that the behavior of the UE, the core network, or each device regarding the transmission and reception of the third identification information is not limited to these, and details including other behaviors will be described later.

[0195] In this embodiment, the fourth identification information may indicate that the VPLMN to which the UE is registered and / or connected distributes the URSP rules associated with the VPLMN, where the fourth identification information may be included in a response message when the network or each device receives a message including the first and / or second identification information from the UE and accepts one or more of the first and / or second identification information.

[0196] Note that the behavior of the UE, the core network, or each device regarding the transmission and reception of the fourth identification information is not limited to these, and details including other behaviors will be described later.

[0197] [3. Embodiments of the Present Invention] [3.1. Description of Procedures or Processing Used in Each Embodiment] Next, procedures used in each embodiment will be described. Note that the procedures or processing used in each embodiment may include a registration procedure and a UE policy distribution procedure.

[0198] Here, the registration procedure may be a procedure when the UE connects to a VPLMN, which is a roaming network, or may be an initial registration procedure.

[0199] In addition, the UE policy distribution procedure may include a UE policy distribution procedure that is executed during the registration procedure, and a UE policy distribution procedure that is executed at any time as needed after the registration procedure is completed.

[0200] 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, 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, different logical hardware, or different software). For example, data may be transmitted and received directly between these devices, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE.

[0201] Each procedure will be explained below.

[0202] [3.1.1. Registration Procedure] The registration procedure will be described with reference to FIG. 6. The registration procedure in the present invention may be a registration procedure for registering with a VPLMN, which is a network to which the UE has roamed. Furthermore, in the following description, each device in the network may be a device within the VPLMN. Furthermore, hereinafter, the registration procedure will also be referred to as this procedure.

[0203] Furthermore, unless otherwise specified, the procedure in the present invention may be an initial registration procedure, or a mobility and periodic registration update procedure.

[0204] The registration procedure is a procedure initiated by the UE to register with the access network _B, and / or the core network _B, and / or the DN, and / or the PLMN. If the UE is not registered with a network, it can execute this procedure at any time, for example, when it is powered on. In other words, if the UE is in a deregistered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (5GMM-REGISTED state) based on the completion of the registration procedure. Note that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or unregistered state) for 3GPP access and the registration state for non-3GPP access.

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

[0206] A UE may initiate a registration procedure when it moves across tracking areas (TAs). In other words, a UE may initiate a registration procedure when it moves to a TA different from the TA indicated in its TA list (TAI list or registration area). Furthermore, a UE may initiate this procedure when a running backoff timer or other timer expires. Furthermore, a UE may initiate a registration procedure when a context update for each device is required due to a PDU session disconnection or invalidation. Furthermore, a UE may initiate a registration procedure when a change occurs in the UE's capability information and / or preferences related to PDU session establishment. Furthermore, a UE may initiate a registration procedure periodically. Furthermore, a UE may initiate a registration procedure based on the completion of a UE configuration update procedure, a registration procedure, a PDU session establishment procedure, a PDU session management procedure, information received from the network in each procedure, or the expiration or stopping of a backoff timer. Note that the UE may perform the registration procedure at any timing, not limited to these.

[0207] The procedure for the UE to transition from a state where it is not registered in the network to a state where it is registered may be referred to as an initial registration procedure or a registration procedure for initial registration, and the registration procedure performed when the UE is registered in the network may be referred to as a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0208] In addition, the UE may perform the above-mentioned network selection before the registration procedure or in the initial state of the registration procedure to select and determine the PLMN, SNPN, or ON-SNPN requested by the UE.

[0209] In Figure 6, new AMF141 indicates the AMF to which UE_A10 is registered through this procedure, and old AMF142 refers to the AMF to which the UE was registered through a procedure prior to this procedure. If no AMF changes occur during this procedure, the interface between old AMF142 and new AMF141 and the procedure between old AMF142 and new AMF141 do not occur, and new AMF141 may be the same device as old AMF142. Note that in this document, when referring to AMF, it may mean new AMF141, old AMF142, or both. Furthermore, new AMF141 and old AMF142 may be AMF140.

[0210] First, UE_A10 starts the registration procedure by sending a registration request message to new AMF141 (S600) (S602) (S604). Specifically, the UE sends an RRC message including the registration request message to 5G AN120 (or gNB) (S600). Note that the registration request message is a NAS message transmitted and received on the N1 interface. Also, the RRC message may be a control message transmitted and received between the UE and 5G AN120 (or gNB). Also, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

[0211] Here, UE_A10 may transmit the first identification information and / or the second identification information in a registration request message, and / or an NAS message including a registration request, and / or an RRC message. Note that the first and second identification information may be configured as a combination of these.

[0212] In addition, when the UE transmits the registration request message including the first identification information and / or the second identification information, the UE may be a UE that supports the use of the URSP rules associated with the VPLMN. Furthermore, a UE that supports the use of the URSP rules associated with the VPLMN may support the use of the URSP rules associated with the HPLMN in addition to supporting the use of the URSP rules associated with the PLMN.

[0213] If the UE supports the URSP rules associated with the VPLMN, the UE may send the first identification information indicating that the URSP rules associated with the VPLMN are supported. In other words, the UE may send the 5GMM capability IE with the first identification information set to indicate that the URSP rules associated with the PLMN are supported.

[0214] If the UE supports storing both the URSP rules associated with the VPLMN and the URSP rules associated with the HPLMN, the UE may send first identification information indicating that the UE supports using the URSP rules associated with the VPLMN or supports the URSP rules associated with the HPLMN.

[0215] Furthermore, the UE may transmit the second identification information as information indicating a preference of the UE regarding the URSP rules associated with the VPLMN. More specifically, the UE may indicate a preference for the URSP rules associated with the VPLMN by using the second identification information, thereby indicating that the UE requests the URSP rules associated with the VPLMN.

[0216] The UE may also indicate that it supports the use of URSP rules associated with the VPLMN by transmitting the second identity. More specifically, the UE may indicate that it supports the use of URSP rules associated with the VPLMN by transmitting only the second identity without transmitting the first identity.

[0217] Alternatively, the UE may indicate that it requests the use of the URSP rules associated with the VPLMN by transmitting only the first identity without transmitting the second identity.

[0218] Furthermore, if the UE does not support the URSP rules associated with the VPLMN, the UE may support the URSP rules associated with the HPLMN, in which case the UE may transmit first identification information indicating that it does not support the URSP rules associated with the VPLMN, or may transmit first identification information indicating that it supports the URSP rules associated with the HPLMN, or may not transmit first identification information indicating that the UE supports the URSP rules associated with the PLMN.

[0219] Furthermore, UE_A10 may transmit a registration request message and / or an RRC message including identification information indicating the type of this procedure. Here, the identification information indicating the type of this procedure may be a 5GS registration type IE, and may be information indicating that this procedure is a registration procedure for initial registration, for updating registration information due to movement, for periodic registration information update, or for emergency registration.

[0220] Here, the identification information indicating the type of this procedure being the 5GS registration type IE may mean that the identification information indicating the type of this procedure is included and set in the 5GS registration type IE.

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

[0222] UE_A10 may transmit the first 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, or a PDCP layer).By transmitting these identification information, UE_A10 may indicate that UE_A10 supports each function, may indicate a UE request, or may indicate both.In addition, the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

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

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

[0225] The UE_A10 may include information other than the first and / or second identification information in the registration request message and / or the NAS message or RRC message containing the registration request message. For example, the UE may include a UE STATE INDICATION message generated by the UE in the registration request message.

[0226] Here, the UE status indication message may be included in a payload container information element in the registration request message, and the payload container type information element may be a UE policy container. Furthermore, the UE may include a currently unused PTI (Procedure Transaction Identity) assigned by the UE in a PTI information element (PTI IE) in the UE status indication message.

[0227] Furthermore, a UE not operating in an SNPN access operation mode may include one or more UPSIs in a UE policy section identified by a PLMN ID part in a UE status indication message, which indicates a HPLMN available to the UE or a selected PLMN. Here, the selected PLMN may be a VPLMN or an EPLMN. The PLMN ID part may also consist of a Mobile Country Code (MCC) and a Mobile Network Code (MNC).

[0228] Furthermore, a UE operating in an SNPN access operation mode may include one or more UPSIs in the UE policy section identified by the UPSI, where the UPSI may include the MCC (Mobile Country Code) and MNC (Mobile Network Code) indicated by the PLMN ID portion of the selected SNPN, or may include the NID of the selected SNPN.

[0229] Here, the UE state indication message may be a message for a UE-initiated UE state indication procedure and may also be a message sent from the UE to the PCF, where the UE-initiated UE state indication procedure may be a procedure performed during a registration procedure, and the UE state indication message may be sent to the (V-)PCF via the (V-)AMF during the registration procedure.

[0230] Here, the purpose of the UE-initiated UE status indication procedure may be to deliver UPSI(s) in UE policy section(s), or to indicate whether the UE supports Access Network Discovery and Selection Policy (ANDSP), or to deliver one or more OS IDs of the UE. Here, the UPSI(s) delivered by the UE in the UE-initiated UE status indication procedure may be one or more UPSI(s) in the UE policy section(s) identified by a UPSI having a PLMN ID portion indicating a HPLMN or a selected PLMN. The selected PLMN may be a VPLMN or an EPLMN. The PLMN ID portion may be composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC).

[0231] Here, the AMF identification information to be included in the registration request message and / or the RRC message containing the registration request message may be information that identifies an AMF or a set of AMFs, and may be, for example, a 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or a GUAMI (Globally Unique AMF Identifier).

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

[0233] When the 5G AN 120 (or gNB) receives an RRC message including a registration request message, it selects an AMF to which to transfer the registration request message (S602). Note that the 5G AN 120 (or gNB) can select an AMF based on one or more pieces of identification information included in the registration request message and / or the RRC message including the registration request message. Specifically, the 5G AN (or gNB) may select a new AMF 141 to which to send the registration request message based on first identification information.

[0234] For example, the 5G AN 120 (or gNB) may select, based on the first identification information, an AMF that supports a function corresponding to the capability information indicated by the first identification information. Specifically, the 5G AN (or gNB) may select an AMF that corresponds to the capability information of the UE indicated by the first identification information and that distributes URSP rules associated with the VPLMN or that can connect to or communicate with a PCF that distributes the URSP rules associated with the VPLMN.

[0235] Note that the method of selecting an AMF is not limited to this, and the 5G AN (or gNB) may select an AMF based on other conditions. The 5G AN (or gNB) extracts a registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). Note that if the first identification information and / or the second identification information are not included in the registration request message but are included in the RRC message, the identification information included in the RRC message may be transferred to the selected AMF (new AMF 141) together with the registration request message (S604).

[0236] When the new AMF 141 receives the registration request message, it can execute a first condition determination. The first condition determination is for determining whether or not the network (or the new AMF 141) accepts the UE's request. When the first condition determination is true, the new AMF 141 executes the procedures from S606 to S618. On the other hand, when the first condition determination is false, the new AMF 141 may execute the procedure of S614 without executing the procedures from S606 to S602.

[0237] Alternatively, the new AMF 141 may request the UE context from the old AMF 142 and perform the first condition determination after receiving the UE context from the old AMF 142 (S606, S608). In this case, the new AMF 141 may execute S610 to S618 if the first condition determination is true. On the other hand, the new AMF 141 may execute S614 if the first condition determination is false.

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

[0239] Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or each identification information contained in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

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

[0241] If the AMF indicated in the AMF identification information included in the message received by new AMF 141 from the UE is old AMF 142, new AMF 141 executes the procedures of S606 and S608, and if the AMF indicated in the AMF identification information included in the message received by new AMF 141 from UE_A10 is new AMF 141, new AMF 141 does not execute the procedures of S606 and S608. In other words, if an AMF change occurs due to this procedure, the procedures of S606 and S608 are executed, and if no AMF change occurs, the procedures of S606 and S608 are skipped.

[0242] The UE context transfer procedure (S606, S608) will be described.

[0243] First, the new AMF 141 transmits a UE context request message to the old AMF 142 (S606). Here, the UE context request message transmitted by the new AMF may be "Namf_Communication_UEContextTransfer." Furthermore, the UE context transmitted from the new AMF 141 to the old AMF 142 (S606) may include a UE ID and an allowed NSSAI.

[0244] Next, the old AMF transmits a UE context response message to the new AMF as a response message to the received UE context request message (S608). Here, the old AMF may transmit the UE context to the new AMF 141 based on the reception of the UE context request message. Furthermore, the response message transmitted by the old AMF may be "Response to Namf_Communication_UEContextTransfer". Furthermore, the old AMF may transmit the UE context response message including the UE context and / or a SUPI (Subscription Permanent Identifier).

[0245] Note that here, if the old ANF holds information about the AM policy association and the UE policy association (i.e., the policy control request trigger for the UE policy update), the old AMF may include this information in the UE context response message.

[0246] Furthermore, when the UE is performing a permanent registration procedure in a roaming network (VPLMN), the old AMF may further include the V-PCF ID and the H-PCF ID in the UE context response message and send it to the new AMF. Note that the V-PCF ID and the H-PCF ID received by the new AMF may be used in PCF selection (S610) and / or AM policy association establishment / change (S612) and / or UE policy association establishment (S616), which will be described later. Details will be described later.

[0247] Furthermore, the new AMF that receives the UE context from the old AMF may generate a UE context based on the received UE context.

[0248] Next, the new AMF performs PCF selection (S610). Here, the PCF selection may be performed if the new AMF decides to obtain the UE policy using the (V-)PCF identified by the (V-)PCF ID included in the UE context (S608) received from the old AMF. Note that if the UE is performing a registration procedure with the VPLMN, the AMF may select a V-PCF and obtain the UE policy from the selected V-PCF.

[0249] Next, the new AMF performs AM policy association establishment / change (S612). Here, if the new AMF selects a new (V-)PCF in PCF selection (S610), the new AMF performs AM policy association establishment with the selected (V-)PCF. Also, if the (V-)PCF identified by the (V-)PCF ID included in the UE context from the old AMF is used in S608, the new AMF performs AM policy association change.

[0250] Next, the new AMF 141 may send a control message to the UE based on the determination of the first condition determination and / or based on receiving the UE context from the old AMF 142 (S614). The control message may be a registration accept message or a registration reject message. The following describes the case where the control message sent to the UE is a registration accept message.

[0251] The new AMF 141 may include one or more of the third and / or fourth identification information in the control message and transmit it. By transmitting this identification information and / or the control message, the new AMF 141 may indicate that the network supports the function indicated by the identification information, may indicate that the UE request has been accepted, may indicate that the request from the UE is not permitted or supported, or may indicate a combination of these. The third and fourth identification information may be configured as information combining these, or may be configured as identification information combining these. Whether the third and / or fourth identification information is included in the control message may be determined based on the network capabilities, operator policy, etc.

[0252] For example, the AMF may send the third and / or fourth identification information to the UE to indicate that the UE has accepted the request indicated by the first and / or second identification information. Further, the UE and each device may perform a procedure for using the URSP rules associated with the VPLMN during or after completion of this procedure, and may perform a UE policy delivery procedure described below.

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

[0254] Furthermore, the AMF may indicate that the UE has accepted the request indicated by the first and / or second identification information by sending the third identification information. More specifically, for example, the AMF may indicate that the network or each device has accepted the request indicated by the UE by the first and / or second identification information or the use of URSP rules associated with the VPLMN by sending the third identification information to the UE. In other words, the UE that receives the third identification information may recognize that the network or each device has accepted the use of URSP rules associated with the VPLMN.

[0255] Furthermore, for example, when new AMF141 receives first and / or second identification information from a UE, even if the second identification information is not included in the control message, which is a registration acceptance message, new AMF141 may indicate to the UE that new AMF141 and / or the core network recognize the UE's capability information indicated by the first identification information and / or that the core network supports the function corresponding to the capability indicated by the first identification information.

[0256] Conversely, if new AMF141 does not include the third identification information in the control message, which is a registration message, it may indicate to the UE that new AMF141 and / or the core network do not recognize the UE's capability information indicated by the first identification information, and / or that the core network does not support the function corresponding to the capability indicated by the first identification information.

[0257] Furthermore, if the new AMF 141 does not receive the first identification information from the UE, the new AMF 141 may transmit the control message with or without including the third identification information.

[0258] Here, the fourth identification information may be a response corresponding to the request content of the UE indicated by the second identification information received from the UE, and may indicate that the request from the UE is permitted. For example, when the AMF accepts or permits the request of the UE indicated by the second identification information, the AMF may include the fourth identification information in a control message and transmit it to the UE. Also, for example, when the AMF accepts or permits the request of the UE indicated by the second identification information, the AMF may include only the fourth identification information in the control message.

[0259] In addition, if the AMF does not receive the second identification information from the UE, it may send the fourth identification information by including it in the control message, or it may send it without including it.

[0260] Furthermore, for example, when the new AMF receives the first and / or second identity information from the UE, the core network or the new AMF may indicate that it has accepted the content indicated by the first and / or second identity information received from the UE by sending a control message that is a registration accept message that does not include the third and / or fourth identity information. In other words, when the AMF receives the first and / or second identity information from the UE, the AMF may indicate that it has accepted the content requested by the UE in the first and / or second identity information by sending a registration accept message that does not include the third and / or fourth identity information.

[0261] Conversely, if the new AMF rejects the content indicated by the first and / or second identification information received from the UE, it may indicate that it has rejected the content indicated by the first and / or second identification information or the UE's request by transmitting a registration rejection message to the UE. Furthermore, when the new AMF transmits the registration rejection message to the UE, it may further include a cause value indicating the reason for the rejection. Here, for example, the cause value indicating the reason for the rejection may be, but is not limited to, a reason indicating that the network or each device does not support the use of the URSP rules associated with the VPLMN.

[0262] More specifically, for example, when new AMF 141 receives the first and / or second identification information from the UE, it may transmit a control message that is a registration accept message that does not include the third and / or fourth identification information, thereby indicating to the UE that new AMF 141 and / or the core network recognize the capability information of the UE indicated by the first identification information and / or that the core network supports the function corresponding to the capability indicated by the first identification information. Note that, for example, when new AMF transmits a registration rejection message to the UE, the core network may indicate to the UE that new AMF 141 and / or the core network do not recognize or cannot recognize the capability information of the UE indicated by the first identification information received from the UE and / or that the core network does not support the function corresponding to the capability indicated by the first identification information.

[0263] Also, for example, when new AMF141 receives the first and / or second identification information from the UE, it may indicate to the UE that new AMF141 and / or the core network recognize the UE's request indicated by the second identification information and / or that new AMF141 and / or the core network have accepted that the core network will respond to the request indicated by the second identification information by sending a control message that is a registration acceptance message that does not include the third and / or fourth identification information.

[0264] Furthermore, for example, when new AMF141 receives the first and / or second identification information from the UE, it may send a control message that is a registration acceptance message that does not include the third and / or fourth identification information, thereby indicating to the UE that new AMF141 and / or the core network recognize the UE capability information indicated by the first identification information and / or the UE request indicated by the second identification information, and / or that the core network supports the function corresponding to the capability indicated by the first identification information, and / or that new AMF141 and / or the core network have accepted that the core network will support the request indicated by the second identification information.

[0265] Furthermore, when the control message is a registration acceptance message, the AMF can include an SM message (e.g., a PDU session establishment acceptance message) in the registration acceptance message and send it, or can send an SM message (e.g., a PDU session establishment acceptance message) together with the registration acceptance message. However, this sending method may also be performed when an SM message (e.g., a PDU session establishment request message) is included in the registration request message. Also, this sending method may be performed when an SM message (e.g., a PDU session establishment request message) is sent together with the registration request message. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure.

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

[0267] The UE receives a control message via the 5G AN (gNB) (S614). If the control message is a registration acceptance message, the UE can recognize by receiving the registration acceptance message that the UE's request in the registration request message has been accepted and the contents of various identification information included in the registration acceptance message. Alternatively, if the control message is a registration rejection message, the UE can recognize by receiving a registration rejection message that the UE's request in the registration request message has been rejected and the contents of various identification information included in the registration rejection message. Furthermore, if the UE does not receive a control message even after a predetermined period has elapsed since sending the registration request message, the UE may recognize that the UE's request has been rejected.

[0268] If the control message is a registration accept message, the UE can further transmit a registration complete message to the AMF via the 5G AN (gNB) as a response message to the registration accept message (S618). When the UE receives an SM message such as a PDU session establishment accept message, the UE may transmit an SM message such as a PDU session establishment complete message in the registration complete message, or may indicate that the SM procedure has been completed by including the SM message. Here, the registration complete message is an NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0269] Next, the new AMF executes UE policy association establishment (S616). Here, the new AMF may send an "Npcf_UEPolicyControl Create Request" to the PCF, and the PCF may send an "Npcf_UEPolicyControl Create Response" to the new AMF, thereby establishing the UE policy association.

[0270] Additionally, the PCF may trigger a UE policy distribution procedure, the details of which are described in section 3.1.2.

[0271] The AMF receives a registration completion message via the 5G AN (gNB) (S618). In addition, each device completes this procedure based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0272] Alternatively, each device may complete the registration procedure based on the transmission and reception of a registration acceptance message or a registration rejection message. Note that the UE policy distribution procedure performed during this procedure may continue after the completion of the registration procedure, or the registration procedure may be completed based on the completion of the UE policy distribution procedure performed during this procedure.

[0273] Each device may transition to or maintain a state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on sending and receiving a registration accept message and / or a registration complete message, or may transition to or maintain a state in which the UE is not registered in the network on the access from which the registration reject message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on sending and receiving a registration reject message. Also, the transition to each state of each device may be based on sending and receiving a registration complete message or completion of the registration procedure.

[0274] 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, if the device transmits or receives information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's requests have been rejected, or may perform the registration procedure for core network_A or another cell.

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

[0276] For example, if the UE receives the third and / or fourth identification information included in a registration acceptance message during a registration procedure in a VPLMN, the UE may recognize that the URSP rules associated with the VPLMN have been delivered in the UE policy delivery procedure described below, which is performed during or after this procedure, and that the UE is authorized to use the delivered URSP rules.

[0277] Furthermore, for example, if the UE receives the third and / or fourth identification information in a registration accept message during the registration procedure in the VPLMN, the UE may recognize that the network supports the distribution of URSP rules associated with the VPLMN.

[0278] Furthermore, if the UE receives a registration acceptance message that does not include both the third and fourth identification information during the registration procedure in the VPLMN, it may recognize that the URSP rules associated with the HPLMN have been delivered and that the use of the delivered URSP rules is permitted.

[0279] Furthermore, if the UE receives a registration accept message during the registration procedure in the VPLMN that does not include both the third and fourth identification information, it may recognize that the network does not support the distribution of URSP rules associated with the VPLMN.

[0280] [3.1.2. UE Policy Delivery Procedure] Next, the UE policy delivery procedure will be described with reference to FIG. 7. Here, the UE policy delivery procedure is a PCF-initiated procedure for updating the UE configuration, and may be a procedure for the PCF to transparently provide a policy to the UE. Here, "transparently" means that the UE policy sent by the PCF is not changed by the AMF and is delivered to the UE using a transparent container. Furthermore, the UE policy delivered in this procedure may be URSP rules, and may be URSP rules associated with the HPLMN or URSP rules associated with the VPLMN.

[0281] The UE policy delivery procedure may be a UE Configuration Update procedure for transparent UE Policy delivery. Hereinafter, the UE policy delivery procedure is also referred to as this procedure. This procedure may be a procedure that can be executed after the AMF selects a PCF (S610) and establishes / changes an AM policy association (S612).

[0282] This procedure may be a network-requested UE policy management procedure, or a procedure in which the PCF sends a "Manage UE policy command" including UE policy information to the UE. Here, the "Manage UE policy command" may be a message sent to the UE as a DL NAS transport message. Note that the detailed procedure of the network-requested UE policy management procedure may be the same as the procedure of the UE configuration update procedure for UE policy distribution.

[0283] This procedure may be executed during the registration procedure or at any timing after the completion of the registration procedure. When this procedure is executed during the registration procedure, it may be started by being triggered by the PCF in the above-mentioned UE policy association establishment (S616).

[0284] This procedure may also be performed when the UE is in the process of registering with the VPLMN, which is the network to which the UE has roamed, or has completed the registration procedure with the VPLMN. Here, the UE policy delivered to the UE visiting the VPLMN may be the URSP rules associated with the VPLMN that are generated and delivered by the V-PCF.

[0285] Furthermore, this procedure may be performed while the UE is registered or connected to the HPLMN or the VPLMN, which is the network to which the UE has roamed. More specifically, this procedure may be performed while the UE is registering to the HPLMN or the VPLMN, or may be initiated by the network or PCF at any time after the registration procedure to the HPLMN or the VPLMN is completed. Note that when this procedure is performed in the VPLMN, the PCF may be a V-PCF.

[0286] In this procedure, the PCF first decides to update the UE policy (S700). Here, the PCF's decision to update the UE policy may be based on the registration procedure, the need for a UE policy update, etc. In other words, the PCF may execute this procedure during the registration procedure, or may execute this procedure at any timing when a UE policy update becomes necessary after the registration procedure is completed. Note that the registration procedure here may be an initial registration procedure.

[0287] More specifically, for example, in the UE policy distribution procedure performed during the registration procedure, the PCF's decision to update the UE policy may be based on a determination of whether the UE policy information needs to be updated and provided to the UE via the AMF using a DL NAS TRANSPORT message by comparing the PSI (policy section identifier) ​​list contained in the UE policy information included in the Npcf_UEPolicyControl_Create Request, a message sent by the New AMF (AMF) to the PCF, in the procedure S616 described in Chapter 3.1.1.

[0288] Alternatively, for example, in a network-initiated UE policy distribution procedure performed at any time, the PCF's decision to update the UE policy may be based on checking the latest list of PSI and determining the UE policy that needs to be sent to the UE.

[0289] Next, the PCF that has decided to update the UE policy sends a message to the AMF using the AM service communication message transfer service (S702). More specifically, the message sent from the PCF to the AMF may be sent by the PCF executing the "Namf_Communication_N1N2MessageTransfer" service operation provided by the AMF. Furthermore, the message sent from the PCF to the AMF may include a SUPI and a UE policy container.

[0290] If the PCF determines that the size of the UE policy information exceeds a predefined limit, the PCF may divide the UE policy information into logically independent UE policies with a size less than the limit and send them by executing the "Namf_Communication_N1N2MessageTransfer" service operation multiple times.

[0291] Here, the UE policy transmitted from the PCF to the AMF in S702 may be URSP rules. More specifically, for example, in a registration procedure in a VPLMN, if the UE transmits a registration request message including first and / or second identification information to the network, and the contents indicated by the one or more identification information are accepted by the network and the registration procedure is completed, the UE policy transmitted from the V-PCF to the (V-)AMF in S702 may be URSP rules associated with the VPLMN generated by the V-PCF.

[0292] Next, the AMF that receives the message sent from the PCF by the "Namf_Communication_N1N2MessageTransfer" service operation (S702) executes a network-triggered service request (S704). Note that the network-triggered service request may be a service request procedure initiated by the network or the AMF, and may be executed when the UE is in a registered state (RM-REGISTERED state) and a disconnected state (CM-IDLE state). In other words, when the UE is in a registered state (RM-REGISTERED state) and a connected state (CM-CONNECTED state), the network-triggered service request (S704) does not need to be executed.

[0293] After completing S702 and / or S703, the AMF performs UE policy distribution (S706). Here, the UE policy distribution may be performed by the AMF sending a DL NAS transport message including UE policy information to the UE. Here, the UE policy included in the DL NAS transport message may be URSP rules.

[0294] Furthermore, if the UE sends first and / or second identification information in a registration request message during the registration procedure with the VPLMN and the contents of the first and / or second identification information are accepted by the network, the URSP rules received in S706 may be the URSP rules associated with the VPLMN.

[0295] Furthermore, before the UE receives the URSP rules from the network in S706, the UE may store the URSP rules in advance. More specifically, the UE may store the URSP rules associated with the HPLMN and / or the URSP rules associated with the VPLMN. Furthermore, when the UE receives the URSP rules from the network in S706, the UE may manage the received URSP rules, such as storing, updating, replacing, or deleting, for each PLMN associated with the associated URSP. The UE may also store and manage the URSP rules for each PLMN. In other words, for example, the UE may independently store and manage the URSP rules associated with the VPLMN or the HPLMN.

[0296] Here, the UE may delete the URSP rules if the URSP rules received by the UE from the network in S706 are empty ("empty" or "0"), and the URSP rules to be deleted may be for each PLMN. In other words, if the URSP rules for a specific PLMN are empty and the UE already stores URSP rules corresponding to the PLMN, the UE may delete the corresponding URSP rules. In other words, when deleting URSP rules stored in the UE, the PCF may empty the URSP rules corresponding to the PLMN to be deleted when generating the URSP rules.

[0297] Here, the behavior of the UE that receives the URSP rules from the PCF via the AMF in S706 may be as follows:

[0298] For example, when the UE completes a registration procedure in a VPLMN by transmitting a registration request message including first and second identification information to the network, the UE may store, in association with the VPLMN, the URSP rules associated with the VPLMN received during the registration procedure or in S706 of the UE policy distribution procedure executed after the completion of the registration procedure. Furthermore, when the UE receives new URSP rules associated with the same VPLMN during another registration procedure or in S706 of the UE policy distribution procedure executed after the completion of the registration procedure, the UE may update or replace the old URSP rules associated with the VPLMN that it has already stored with the new URSP rules. Furthermore, when the UE receives empty URSP rules associated with the same VPLMN during another registration procedure or in S706 of the UE policy distribution procedure executed after the completion of the registration procedure, the UE may delete the old URSP rules associated with the VPLMN that it has already stored.

[0299] Also, for example, if a UE that has already stored URSP rules associated with an HPLMN and is connecting to a VPLMN receives URSP rules associated with the VPLMN at S706 of the UE policy distribution procedure executed during or after the registration procedure is completed, the UE may store the URSP rules associated with the received VPLMN without deleting the URSP rules associated with the HPLMN that it has already stored.

[0300] Also, for example, if a UE that does not support URSP rules associated with a VPLMN receives URSP rules associated with the VPLMN at S706 of the UE policy distribution procedure executed during the registration procedure or after the completion of the registration procedure, the UE may not store the URSP rules associated with the received VPLMN or may ignore the URSP rules associated with the received VPLMN.

[0301] Note that the behavior of the UE that receives the URSP rules from the PCF via the AMF in S706 is not limited to these.

[0302] The UE that receives the UE policy from the PCF via the AMF updates the UE policy and transmits the delivery result of the UE policy to the AMF (S708).

[0303] The AMF that receives the UE policy delivery result from the UE sends a message to the PCF using the AMF service communication message notification service (S710). More specifically, the message sent from the AMF to the PCF is the UE policy container that the AMF received from the UE, which is forwarded using the "Namf_Communication_N1MessageNotify" service operation. Note that S710 may be executed when the PCF subscribes to receive a reception notification of the UE policy container.

[0304] Furthermore, the PCF maintains and stores the latest list of PSI delivered to the UE in this procedure and updates the latest list of PSI in the UDR using the Nudr_DM_Update (SUPI, Policy Data, Policy Set Entry, updated PSI data) service operation.

[0305] [3.2. First Embodiment] The first embodiment of the present invention relates to the behavior of a UE when, during or after the registration procedure to a VPLMN, the network or each device in the network transmits the URSP rules associated with the VPLMN to the UE if the UE does not indicate support and / or request for the use of the URSP rules associated with the VPLMN during the registration procedure to the VPLMN. Note that the first embodiment is also referred to as the present embodiment in this chapter.

[0306] Here, when the UE does not indicate support and / or a request for the use of the URSP rules associated with the VPLMN in the registration procedure with the VPLMN, the UE may transmit a registration request message that does not include either the first or second identification information to the network (VPLMN). In other words, the UE may perform the registration procedure and the registration procedure with the VPLMN without indicating to the network (VPLMN) that it supports or requests the use of the URSP rules associated with the VPLMN.

[0307] Also, in a registration procedure in a VPLMN, a UE that sends a registration request message that does not include either the first identification information or the second identification information may be a UE that does not support the use of the URSP rules associated with the PLMN.

[0308] More specifically, this embodiment may be, for example, a case where, in a registration procedure in a VPLMN, a UE sends a registration request message to a network that does not include either the first identification information or the second identification information, and the network completes the registration procedure by sending a registration acceptance message to the UE.

[0309] If the UE receives URSP rules associated with the VPLMN during the registration procedure or after the registration procedure is completed, the UE may transmit a message indicating that the UE policy distribution has failed to the AMF as a result of the UE policy distribution (S708). Furthermore, the UE may not store the URSP rules associated with the VPLMN.

[0310] [3.3. Second Embodiment] The second embodiment of the present invention relates to the behavior of a UE when, during a registration procedure with a VPLMN, the UE indicates support for and / or a request for the use of URSP rules associated with the VPLMN, and the network or each device in the network transmits the URSP rules associated with the VPLMN and the URSP rules associated with the HPLMN to the UE during or after the registration procedure is completed. Note that the second embodiment is also referred to as the present embodiment in this chapter.

[0311] In other words, this embodiment may be a case where, in a registration procedure in a VPLMN, the UE sends a registration request message including first identification information and / or second identification information to the network, and the network completes the registration procedure by sending a registration accept message to the UE.

[0312] If the UE receives URSP rules associated with the HPLMN and URSP rules associated with the VPLMN during or after the registration procedure, the UE may store the received URSP rules for each PLMN. Furthermore, the UE may preferentially use the URSP rules associated with the VPLMN, which is the serving PLMN.

[0313] [4. Modifications] A program running on an apparatus according to the present invention may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a non-volatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

[0314] A program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium. The program may be read into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may also refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0315] Additionally, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, such as an integrated circuit or multiple integrated circuits. The electrical 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 electrical circuit may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge that replace current integrated circuits, one or more aspects of the present invention may utilize new integrated circuits based on that technology.

[0316] The present invention is not limited to the above-described embodiment. Although one example of a device has been described in the embodiment, the present invention is not limited to this and can be applied to terminal devices or communication devices for stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0317] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the present invention. Furthermore, the present invention allows various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Also included are configurations in which elements described in the above embodiments are substituted with elements that achieve similar effects. (Cross-Reference to Related Applications) This application claims priority to Japanese Patent Application No. 2022-022069, filed February 16, 2022, the entire contents of which are incorporated herein by reference.

[0318] 1 Mobile communication system 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access network_A (E-UTRAN) 90 Core network_A 120 Access network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 141 new AMF 142 old AMF 150 UDM 160 PCF 190 Core network_B

Claims

[Claim 1] A UE (User Equipment) comprising a transmitting / receiving unit, a storage unit, and a control unit, The aforementioned memory unit stores URSP (UE Route Selection Policy) rules associated with HPLMN (Home Public Land Mobile Network), If the aforementioned UE does not support URSP (UE Route Selection Policy) rules associated with VPLMN (Visited Public Land Mobile Network), The aforementioned transmitting and receiving unit is Information indicating that the UE does not support URSP (UE Route Selection Policy) associated with VPLMN (Visited Public Land Mobile Network) is sent to the network through a procedure led by the UE. In the UE policy management procedure, if a Manage UE policy command is received from the network, which includes information about URSP associated with VPLMN, The control unit ignores the information regarding the URSP associated with the VPLMN in the storage unit. The memory unit maintains the URSP rules associated with the HPLMN stored in it. A UE characterized by the following: