WO2023157485A1 - User equipment (ue) - Google Patents

Abstract

In 5GS, with regard to the URSP rules that are used when UE connects to a VPLMN, which is a roamed-into network, it is not defined whether the URSP rules associated with a HPLMN or the URSP rules associated with the VPLMN are to be selected by UE or a network for delivery by the network to the UE and for use by the UE. UE and a network of the present invention provide a selection method and a communication means for transmitting and receiving, e.g., capability information and/or identifying information indicating a request, and for selecting and delivering, on the basis of the identifying information that has been transmitted and received, URSP rules associated with a HPLMN and/or URSP rules associated with the VPLMN as the URSP rules to be used by the UE connecting to the VPLMN.

Description

UE (User Equipment)

The present invention relates to UE (User Equipment).

3GPP (3rd Generation Partnership Project) studies, discusses, and formulates specifications to support new procedures and functions in the system architecture of 5GS (5G System), the 5th Generation (5G) mobile communication system. is performed (see Non-Patent Documents 1 to 5). Regarding the 5G UE (User Equipment) Policy, which was discussed up to the Release 17 standard, the expansion of its functions will be discussed in Release 18.

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

URSP (UE Route Selection Policy) rules provided as one of the policy information used when the UE connects to the VPLMN, which is the roaming destination network, are conventionally supported only for URSP rules associated with HPLMN. Ta. On the other hand, in the study of 5G UE policy expansion, further support for URSP rules associated with VPLMN is being studied. The details of procedures and methods for handling the storage or management of personal information are not clear.

The present invention has been made in view of the circumstances as described above. , and the information and procedures sent and received between the UE and the network that are required to implement these.

A UE (User Equipment) according to the embodiment of the present invention is a UE (User Equipment) that includes a transmitting/receiving unit, a storage unit, and a control unit. URSP (UE Route Selection Policy) rules of 1 are URSP rules associated with HPLMN (Home Public Land Mobile Network), and the transmitting/receiving unit, in the procedure for receiving the URSP rules started during the registration procedure , receives second URSP rules, said second URSP rules being URSP rules associated with a VPLMN (Visited Public Land Mobile Network), said control unit storing said first URSP rules in said storage unit The second URSP rules are stored without deleting the rules.

According to one embodiment of the present invention, a UE that has registered and connected to a VPLMN, which is a roaming destination network, is associated with HPLMN as URSP rules provided as one of UE policy information in the destination network. It is possible to provide a method for selecting either the URSP rules or the URSP rules associated with the VPLMN.

1 is a diagram explaining an outline of a mobile communication system (EPS/5GS); FIG. FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS/5GS); It is a figure explaining the apparatus structure of UE. FIG. 2 is a diagram explaining the configuration of an access network device (gNB) in 5GS; FIG. 2 is a diagram illustrating the configuration of core network devices (AMF/SMF/UPF/PCF) in 5GS; It is a figure explaining a registration procedure. FIG. 10 is a diagram explaining a UE policy delivery procedure;

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.

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

In Fig. 1, a 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. It is stated that

In the following, these devices and functions may be described with abbreviated symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. .

In addition, Fig. 2 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, N3IWF170, etc. The interfaces that connect these devices/functions together are described.

In the following, these devices/functions are described as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc. , symbols may be omitted.

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

A UE is a device capable of connecting to network services via a 3GPP access (also called a 3GPP access network, 3GPP AN) and/or a non-3GPP access (also called a non-3GPP access network, non-3GPP AN). be. The UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device connectable to both EPS and 5GS. A UE may comprise a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that the UE may be expressed as a user equipment, or may be expressed as a terminal equipment.

Also, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and/or wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are arranged in the E-UTRAN. In addition, below, eNB45 may be described by abbreviate|omitting a symbol like eNB. Also, if there are multiple eNBs, each eNB is connected to each other, for example, by an X2 interface. Also, one or more access points are arranged in the wireless LAN access network.

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

Also, 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 public wireless LAN. On the other hand, a trusted non-3GPP access network may be a 3GPP-specified access network and may comprise a trusted non-3GPP access point (TNAP) and a trusted non-3GPP Gateway function (TNGF).

Also, hereinafter, E-UTRAN and NG-RAN may be referred to as 3GPP access. Wireless LAN access networks and non-3GPP ANs are sometimes referred to as non-3GPP access. In addition, the nodes arranged in access network_B may also be collectively referred to as NG-RAN nodes.

Also, hereinafter, access network_A and/or access network_B and/or devices included in access network_A and/or devices included in access network_B are access networks or access network devices sometimes referred to as

In addition, Core Network_A supports EPC (Evolved Packet Core). EPC includes MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. placed.

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

Also, hereinafter, core network_A and/or core network_B, devices included in core network_A, and/or devices included in core network_B are the core network, or the core network device or the core network It may be called an internal device.

The core network (core network_A and/or core network_B) is a mobile communication carrier (Mobile It may be an IP mobile communication network operated by a network operator; ), MVNE (Mobile Virtual Network Enabler), and other core networks for virtual mobile communication operators and virtual mobile communication service providers.

The core network (core network_A and/or core network_B) and the access network (access network_A and/or access network_B) may be different for each mobile communication carrier.

Also, in Fig. 1, the case where the PDN and DN are the same is described, but they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. Note that the DN may be configured as a packet data service network, or may be configured for each service. Additionally, the PDN may include connected communication terminals. Therefore, connecting to a PDN may be connecting to a communication terminal or a server device located in the PDN. Furthermore, transmitting/receiving user data to/from the PDN may be transmitting/receiving user data to/from a communication terminal or a server apparatus arranged in the PDN. PDN may be expressed as DN, and DN may be expressed as PDN.

Also, hereinafter, access network_A, core network_A, PDN, access network_B, core network_B, at least a part of DN, and/or one or more devices included therein are referred to as network or network device is sometimes called. That is, the fact that the network and/or network devices send/receive messages and/or perform procedures means that Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN It means that at least some and/or one or more devices included therein send and receive messages and/or perform procedures.

Also, the UE can connect to the access network. Also, the UE can connect to the core network via the access network. Furthermore, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can transmit/receive (communicate) user data with the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

Here, IP communication is data communication using IP, and data is sent and received using IP packets. An IP packet consists of an IP header and a payload. The payload part may include data transmitted and received by devices/functions included in EPS and devices/functions included in 5GS. Non-IP communication is data communication that does not use IP, and data is transmitted and received in a format different from the structure of IP packets. For example, non-IP communication may be data communication realized by sending and receiving application data to which no IP header is attached, or may be data communication realized by attaching another header such as a MAC header or Ethernet (registered trademark) frame header to the UE. User data to be transmitted and received may be transmitted and received.

In addition, devices not shown in FIG. 2 may be configured in access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A. For example, Core Network_A and/or Core Network_B and/or PDN_A and/or DN_A include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S). good too. AAA servers may be located outside the core network.

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

　In addition, the AAA server is a device with authentication and authorization and billing functions that connects directly with AUSF or indirectly via other network devices. The AAA server may be a network device within the core network. Note that the AAA server may not be included in CoreNetwork_A and/or CoreNetwork_B, but may be included in PLMN or SNPN. That is, 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 SNPN managed by the 3rd Party.

In FIG. 2, each device/function is described one by one for the sake of simplification of the drawing, but the mobile communication system 1 may be configured with a plurality of similar devices/functions. Specifically, the mobile communication system 1 includes a plurality of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and/or UDM150. Such devices and functions may be configured.

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

In addition, each storage unit (storage unit_A340, storage unit_A440, storage unit_B540) in each device and function that appears below is, for example, a semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive) ), etc. In addition, each storage unit stores not only information originally set from the shipping stage, but also devices/functions other than the own device/function (for example, UE, and/or access network device, and/or core network device, and/or or PDN and/or DN), and can store various types of information sent and received. Further, each storage unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures to be described later. Also, each storage unit may store these pieces of information for each UE. In addition, when interworking between 5GS and EPS, each storage unit can store control messages and user data sent and received between devices and functions included in 5GS and/or EPS. can. At this time, not only data sent and received via the N26 interface but also data sent and received without the N26 interface can be stored.

[2.1. Equipment configuration of UE]
First, a device configuration example of UE (User Equipment) will be described with reference to FIG. The UE is composed of a control unit_A300, an antenna 310, a transmission/reception unit_A320, and a storage unit_A340. The control unit_A300, transmission/reception unit_A320, and storage unit_A340 are connected via a bus. Transceiver_A 320 is connected to antenna 310 .

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

The transmitting/receiving unit_A320 is a functional unit for wirelessly communicating with the base station device (eNB or gNB) in the access network via an antenna. That is, the UE can transmit/receive user data and/or control information to/from an access network device and/or a core network device and/or a PDN and/or a DN using the transmitting/receiving unit_A320. can.

To explain in detail with reference to FIG. 2, the UE can communicate with the base station apparatus (eNB) in E-UTRAN via the LTE-Uu interface by using the transceiver _A320. Also, the UE can communicate with the base station apparatus (gNB) within the 5G AN by using the transceiver _A320. Also, the UE can transmit and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transmitting/receiving unit_A320. However, since the N1 interface is a logical one, in practice the communication between the UE and the AMF will take place over the 5G AN.

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

[2.1.1. Equipment configuration of gNB]
Next, a device configuration example of the gNB will be described using FIG. The gNB is composed of a control unit_B400, an antenna 410, a network connection unit_B420, a transmission/reception unit_B430, and a storage unit_B440. The control unit_B400, network connection unit_B420, transmission/reception unit_B430, and storage unit_B440 are connected via a bus. Transceiver_B 430 is connected to antenna 410 .

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 storage unit_B440 as necessary.

　Network connection part_B420 is a functional part for gNB to communicate with AMF and/or UPF. That is, the gNB can transmit and receive user data and/or control information to/from AMF and/or UPF using Network Connection Unit_B420.

The transmitting/receiving unit_B430 is a functional unit for wireless communication with the UE via the antenna 410. That is, the gNB can transmit/receive user data and/or control information to/from the UE using the transmitting/receiving unit_B430.

To explain in detail with reference to Fig. 2, the gNB located in the 5G AN can communicate with the AMF through the N2 interface by using the Network Connection Part_B420, and the UPF through the N3 interface. can communicate with Also, the gNB can communicate with the UE by using the transceiver_B430.

The storage unit_B440 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[2.1.2. Equipment configuration of AMF]
Next, an example configuration of the AMF will be described with reference to FIG. The AMF is composed of a control unit_B500, a network connection unit_B520, and a storage unit_B540. The control unit_B500, network connection unit_B520, and storage unit_B540 are connected via a bus. AMF may be a node that handles the control plane.

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 storage unit_B540 as necessary.

The network connection unit_B520 is a functional unit for AMF to connect with the base station equipment (gNB) in the 5G AN, and/or SMF, and/or PCF, and/or UDM, and/or SCEF. That is, AMF uses the network connection unit _B520 to use the user Data and/or control information can be sent and received. The network connection unit_B520 may be a transmission/reception unit.

To explain in detail with reference to FIG. 2, AMF in 5GCN can communicate with gNB through N2 interface by using network connection part_A520, and with UDM through N8 interface. It can communicate with SMF via the N11 interface and with PCF via the N15 interface. Also, the AMF can transmit and receive NAS messages with the UE via the N1 interface by using the network connection unit_A520. However, since the N1 interface is a logical one, in practice the communication between the UE and the AMF will take place over the 5G AN. Also, when the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A520.

The storage unit_B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of AMF.

The AMF has functions to exchange control messages with the RAN using the N2 interface, functions to exchange NAS messages with the UE using the N1 interface, encryption and integrity protection functions for NAS messages, and registration management. (Registration management; RM) function, Connection management (CM) function, Reachability management function, Mobility management function for UE, SM (Session Management) between UE and SMF N2 for message forwarding function, Access Authentication, Access Authorization function, Security Anchor Functionality (SEA), Security Context Management (SCM) function, N3IWF (Non-3GPP Interworking Function) It has a function to support interfaces, a function to support transmission and reception of NAS signals with UEs via N3IWF, a function to authenticate UEs connected via N3IWF, and so on.

In addition, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and AMF. RM states include a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, so the UE context in the AMF does not have valid location and routing information for the UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, the UE is registered with the network so that the UE can receive services that require registration with the network. Note that the RM state may 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.

In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context or a state in which a PDU session context has been established. Note that if each device is 5GMM-REGISTERED, UE_A 10 may start sending and receiving user data and control messages, and may respond to paging. Furthermore, it should be noted that if each device is 5GMM-REGISTERED, UE_A 10 may perform registration procedures other than those for initial registration and/or service request procedures.

Furthermore, 5GMM-DEREGISTERED may be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network reaches UE_A10. It may be in a state of being disabled. Note that if each device is 5GMM-DEREGISTERED, UE_A 10 may initiate a registration procedure or establish a 5GMM context by performing the registration procedure.

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

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

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

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

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

[2.1.3. Equipment configuration of SMF]
Next, an example of the configuration of the SMF 132 will be described with reference to FIG. The SMF is composed of a control unit_B500, a network connection unit_B520, and a storage unit_B540. The control unit_B500, network connection unit_B520, and storage unit_B540 are connected via a bus. The SMF may be a node handling the control plane.

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

The network connection part_B520 is a functional part for SMF to connect with AMF and/or UPF and/or PCF and/or UDM. That is, the SMF can send and receive user data and/or control information to/from AMF and/or UPF and/or PCF and/or UDM using Network Connection Unit_B520. The network connection unit_B520 may be a transmission/reception unit.

To explain in detail with reference to FIG. 2, SMF in 5GCN can communicate with AMF through N11 interface by using network connection part_A520, and with UPF through N4 interface. Through the N7 interface, it can communicate with the PCF, and through the N10 interface, it can communicate with the UDM.

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

The SMF has session management functions such as establishment, modification, and release of PDU sessions, IP address allocation for UEs and their management functions, UPF selection and control functions, appropriate destinations (destination ), a function to send and receive the SM part of NAS messages, a function to notify that downlink data has arrived (Downlink Data Notification), AN via the N2 interface via AMF It has a function to provide AN-specific (for each AN) SM information sent to the network, a function to determine the SSC mode (Session and Service Continuity mode) for the session, a roaming function, etc.

[2.1.4. UPF equipment configuration]
Next, an example configuration of the UPF will be described with reference to FIG. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. A UPF may be a node that handles the control plane.

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

The network connection unit_B720 is a functional unit for UPF to connect with base station equipment (gNB) in 5G AN, and/or SMF, and/or DN. That is, the UPF uses the network connection unit _B720 to transmit and receive user data and/or control information between the base station device (gNB) in the 5G AN, and/or SMF, and/or DN. can be done. The network connection unit_B520 may be a transmission/reception unit.

To explain in detail with reference to FIG. 2, UPF in 5GCN can communicate with gNB through N3 interface by using network connection part_A520, and with SMF through N4 interface. It can communicate, through the N6 interface it can communicate with DNs, and it can communicate with other UPFs through the N9 interface.

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

The UPF functions as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting DNs (i.e. as a gateway between DNs and Core Network_B, allowing users data forwarding function), packet routing and forwarding function, UL CL (Uplink Classifier) function that supports routing of multiple traffic flows for one DN, multi-homed PDU session support It has branching point function, QoS (Quality of Service) processing function for user plane, uplink traffic verification function, downlink packet buffering, downlink data notification trigger function, etc.

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

Note that the user plane is user data transmitted and received between the UE and the network. User plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, for 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, for 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 expressed as U-Plane or UP.

Furthermore, the control plane is a control message that is sent and received to control UE communication. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. Additionally, for EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, for 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or as a C-Plane.

Furthermore, the U-Plane (User Plane; UP) may be a communication channel 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.

[2.1.5. Equipment configuration of PCF]
Next, a configuration example of the PCF used in each embodiment will be described with reference to FIG. The PCF is composed of a control unit_500, a network connection unit_520, and a storage unit_540. The control unit_500, network connection unit_520, and storage unit_540 are connected via a bus.

The control unit_500 is a functional unit that controls the operation and functions of the entire PCF. Note that the control unit_500 may process all the functions that other functional units (network connection unit_520, storage unit_540) in the PCF do not have. The control unit_500 implements various processes in the PCF by reading and executing various programs stored in the storage unit_540 as necessary.

The network connection unit_520 is a functional unit for PCF to connect with AMF and/or SMF and/or AF (Application Function). That is, the PCF can transmit and receive control information to and from AMF and/or SMF and/or AF using network connection unit_520. The network connection unit_B520 may be a transmission/reception unit.

PCF can communicate with AMF via N15 interface by using network connection part_520, can communicate with SMF via N7 interface, and can communicate with N5 interface (interface between PCF and AF). ) to communicate with AF.

The storage unit_540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UPF.

PCF also includes functions to support a unified policy framework, provide policy rules to control plane functions to enforce them, access subscription information, etc. have. The PCF also has a function to generate PCC rules, and/or first PCC rules, and/or second PCC rules, and URSP (UE Route Selection Policy) rules (URSP rule(s)). ing. These functions may all be controlled by the control unit_500.

In this specification, the PCF in HPLMN is also called H-PCF (Home PCF), and the PCF in VPLMN is also called V-PCF (Visited PCF). Further, for example, URSP rules generated by H-PCF are also referred to as URSP rules associated with HPLMN, and URSP rules generated by V-PCF are also referred to as URSP rules associated with VPLMN.

When roaming, V-PCF can be connected via H-PCF and N24 interface (interface between PCFs). That is, the V-PCF can transmit and receive control information to and from the H-PCF using the network connection unit_520.

[2.1.6. Description of other devices and/or functions]
Next, other devices and/or functions are described.

The PCF has functions such as providing policy rules.

In addition, the UDM has authentication credential processing function, user identification processing function, access authentication function, registration/mobility management function, subscription management function, etc.

In addition, the PCRF is connected to the PGW and/or PDN and has functions such as QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and PDN. Furthermore, the PCRF may be a device that creates and/or manages PCC (Policy and Charging Control) rules and/or routing rules used when each device transmits and receives user data.

In addition, HSS is connected to MME and/or SCEF and has functions such as managing subscriber information. HSS subscriber information is referred to, for example, during MME access control. Furthermore, the HSS may be connected with a location management device different from the MME.

[2.2. Explanation of terms in this embodiment]
Next, highly technical terms used in each embodiment and identification information used in procedures will be described.

　Network (NW) refers to at least part of Access Network_B, Core Network_B, and DN. Also, one or more devices included in at least part of access network_B, core network_B, and DN may be referred to as a network or a network device. In other words, the fact that a network performs message transmission/reception and/or processing may mean that a device in the network (a network device and/or a control device) performs message transmission/reception and/or processing. . Conversely, a device in the network performing message transmission/reception and/or processing may mean that the network performs message transmission/reception and/or processing.

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

SM (Session Management) messages (also called NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and are transmitted and received between UE_A10 and SMF_A230 via AMF_A240. may be a control message that In addition, SM messages 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, and a PDU session establishment request message. request) message, PDU session modification command message, PDU session modification complete message, PDU session modification command reject message, PDU session modification reject message. PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete A message or the like may be included. In addition, the procedure for SM or SM procedure includes PDU session establishment procedure, PDU session modification procedure, PDU session release procedure (UE-requested PDU session release procedure). may be Note that each procedure may be a procedure started from the UE, or may be a procedure started from the NW.

　In addition, MM (Mobility management) messages (also referred to as NAS MM messages) may be NAS messages used in procedures for MM, and may be control messages transmitted and received between UE_A10 and AMF_A240. In addition, MM messages include a Registration request message, a Registration accept message, a Registration reject message, a De-registration request message, a De-registration accept message. ) message, configuration update command message, configuration update complete message, Service request message, Service accept message, Service reject message, Notification ) message, Notification response message, etc. In addition, procedures for MM or MM procedures include Registration procedure, De-registration procedure, Generic UE configuration update procedure, Authentication/Authorization procedure, Service request procedure ( Service request procedure), Paging procedure, Notification procedure.

　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 a service similar to the EPS service.

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

Also, the PDN (Packet Data Network) type indicates the type of PDN connection, including IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. When non-IP is specified, it indicates that communication is to be performed by a communication method other than IP, rather than using IP.

Also, there are two types of access types: 3GPP access and non-3GPP access. Here, the information indicating the access type may be configured as an access type information element (IE). It may be identification information to indicate.

A PDU (Protocol Data Unit/Packet Data Unit) session can also be defined as an association between a DN that provides PDU connectivity services and a UE, but is established between the UE and an external gateway. connectivity. In 5GS, by establishing a PDU session via access network_B and core network_B, the UE can transmit and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. A UE can transmit and receive user data to and from a device such as an application server located in a DN using a PDU session.

Each device (UE, and/or access network device, and/or core network device) may associate and manage one or more pieces of identification information with respect to a PDU session. These identities may include one or more of DNN, QoS rules, PDU session type, application identities, NSI identities, access network identities, and SSC mode, and other information. Further may be included. Furthermore, when multiple PDU sessions are established, each piece of identification information associated with a PDU session may have the same content or different content.

Also, the DNN (Data Network Name) may be identification information that identifies the core network and/or the external network such as DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30/UPF_A235 that connects core network_B190. Furthermore, DNN may correspond to APN (Access Point Name).

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

Also, PLMN (Public Land Mobile Network) is a communication network that provides mobile wireless communication services. A PLMN is a network managed by an operator who is a (mobile) communication carrier, and the operator can be identified by the PLMN ID. Also, an operator may manage one or more PLMNs. In this paper, PLMN may mean PLMN ID. The PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the IMSI (International Mobile Subscriber Identity) of the UE may be the Home PLMN (HPLMN).

Furthermore, the UE may hold an Equivalent HPLMN list for identifying one or more E-HPLMNs (Equivalent HPLMN) in the USIM (Universal Subscriber Identity Module). A PLMN different from the HPLMN and/or E-HPLMN may be a VPLMN (Visited PLMN or VPLMN). Also, a PLMN that has been successfully registered by the UE may be an RPLMN (Registered PLMN). The current PLMN is defined as the PLMN requested by the UE and/or the PLMN selected by the UE and/or the RPLMN and/or the PLMN allowed by the network and/or the core network device sending and receiving the message. It may be the PLMN to which it belongs. A service provided by PLMN may be referred to as PLMN service, and a service provided by SNPN may be referred to as SNPN service.

A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. The UE and/or network may support network slices (NW slices; NS) in 5GS. A network slice may also simply be called a slice.

Also, a network slice instance (NSI) forms a network slice that is configured and arranged by a set of network function (NF) instances (entities) and necessary resources. Here, NF is a processing function in a network, which is adopted or defined by 3GPP. One or more NSIs are entities of NSs configured in core network_B. Also, the NSI may be composed of a virtual NF (Network Function) generated using an NST (Network Slice Template).

Here, an NST is a logical representation of one or more NFs that are associated with resource requirements for providing required communication services and capabilities. In other words, the NSI may be an aggregate within the core network_B 190 composed of multiple NFs. Also, the NSI may be a logical network configured to separate user data delivered by services or the like. One or more NFs may be configured in the NS. The NFs configured in the NS may or may not be devices shared with other NSs.

The UE and/or devices in the network may, based on NSSAI and/or S-NSSAI and/or UE usage type and/or registration information such as one or more NSI IDs and/or APN can be assigned to the NS of Note that the UE usage type is a parameter value included in the registration information of the UE used to identify the NSI. UE usage type may be stored in HSS. AMF may choose between SMF132 and UPF based on UE usage type.

In addition, S-NSSAI (Single NetworkSlice Selection Assistance Information) is information for identifying NS. S-NSSAI may consist of only SST (Slice/Service type), or may consist of both SST and SD (Slice Differentiator). Here, the SST is information indicating the expected behavior of the NS in terms of functions and services. Also, SD may be information for interpolating SST when selecting one NSI from a plurality of NSIs indicated by SST. The S-NSSAI may be information unique to each PLMN, or may be standard information shared among PLMNs. The network may also store one or more S-NSSAIs in the UE's registration information as default S-NSSAIs. Note that if the S-NSSAI is the default S-NSSAI and the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide the NS associated with the UE.

Also, the S-NSSAI sent and received between the UE and the NW may be expressed as an S-NSSAI IE (Information element). Furthermore, the S-NSSAI IE sent and received between the UE and the NW indicates the S-NSSAI composed of the SST and/or SD of the registered PLMN and/or the S-NSSAI of the HPLMN to which the S-NSSAI is mapped. SST and/or SD may be configured. One or more S-NSSAI stored by the UE and/or NW may be configured with SST and/or SD, or S-NSSAI configured with SST and/or SD and/or the S-NSSAI SST and/or SD indicating the S-NSSAI of the mapped HPLMN may be configured.

Also, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in the NSSAI is information that assists the access network or core network in selecting the NSI. The UE may store the NSSAI granted from the network per PLMN. Also, the NSSAI may be information used to select the AMF. The UE may apply each NSSAI (allowed NSSAI and/or configured NSSAI and/or rejected NSSAI and/or pending NSSAI and/or primary NSSAI) to PLMN and EPLMN.

Also, the configured NSSAI is the NSSAI that is provided and stored in the UE. The UE may store the configured NSSAI per PLMN. The UE may store the configured NSSAI in association with the PLMN. In this paper, the configured NSSAI associated with the PLMN may be expressed as the configured NSSAI for the PLMN, the configured NSSAI for the PLMN, the configured NSSAI for the PLMN, or the configured NSSAI associated with the PLMN. Also, the UE may store a configured NSSAI that is not associated with any PLMN and is valid for all PLMNs, and may set such a configured NSSAI as a "default configured NSSAI".

A configured NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

The configured NSSAI may be information configured by the network (or PLMN). An S-NSSAI included in a configured NSSAI may be expressed as a configured S-NSSAI. A configured S-NSSAI may be configured including an S-NSSAI and a mapped S-NSSAI. Alternatively, the PLMN's S-NSSAI may be expressed as "configured S-NSSAI", and the S-NSSAI mapped to the HPLMN as "mapped S-NSSAI to the configured NSSAI for the PLMN".

Also, the requested NSSAI is the 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.

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

　Allowed NSSAI is information indicating one or more network slices for which the UE is permitted. In other words, the allowed NSSAI is information identifying network slices that the network has allowed to connect to the UE.

The UE and/or NW may store and manage allowed NSSAI for each access (3GPP access or non-3GPP access) as UE information. The UE and/or NW may also manage allowed NSSAIs in association with registration areas.

Furthermore, the UE and/or NW may store and manage the allowed NSSAI as UE information in association with the PLMN. An allowed NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

In this article, allowed NSSAI associated with PLMN and access type may be expressed as allowed NSSAI for PLMN and access type, or allowed NSSAI for PLMN access type. An S-NSSAI included in an allowed NSSAI may be expressed as an allowed S-NSSAI. allowed S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI.

　In addition, rejected NSSAI is information indicating one or more network slices for which the UE is not permitted. In other words, the rejected NSSAI is information identifying network slices that the network does not allow the UE to connect to. The rejected NSSAI may be information that includes one or more combinations of S-NSSAI and rejection reason values.

Here, the refusal 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 value associated with each S-NSSAI.

Furthermore, the rejected NSSAI may be included in a NAS message sent from the network to the UE, such as a registration acceptance message, a configuration update command, a registration rejection message, or an RRC message containing a NAS message. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI.

The rejected NSSAI may be any one of the first to third rejected NSSAIs, the pending NSSAI, and the first NSSAI, or may be a combination thereof. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. A rejected S-NSSAI may be configured including an S-NSSAI and a mapped S-NSSAI.

The UE and/or NW may store and manage the rejected NSSAI in association with the PLMN as UE information. A rejected NSSAI may be associated with multiple PLMNs, and these multiple PLMNs may be EPLMNs.

A tracking area is a single or multiple ranges that can be represented by the location information of UE_A10 managed by the core network. A tracking area may consist of multiple cells. Furthermore, the tracking area may be a range in which control messages such as paging are broadcast, or a range in which UE_A 10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or the like. Hereinafter, the tracking area may be 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.

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

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

A UE ID is information for identifying a UE. Specifically, for example, the UE ID is SUCI (SUBscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), or IMEISV (IMEI Software Version). Alternatively, it may be TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information configured within the application or network. Furthermore, the UE ID may be information for identifying the user.

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

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

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 N1 over 3GPP access. A state in which a NAS signaling connection is not established may be expressed as the UE being in 5GMM-IDLE mode over 3GPP access.

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. , the state in which the 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.

Also, SNPN (Stand-alone Non-Public Network) is a type of NPN that is 5GS deployed for non-public use, NF operated by NPN operator and provided by PLMN is an NPN that does not depend on That is, the SNPN may be an NPN-only network independent of the PLMN. Also, the SNPN is identified by a combination of PLMN ID and NID (Network Identifier). The PLMN ID used for the SNPN ID may be information reserved for the private network, and the MCC included in the PLMN ID may be 999, for example.

Also, UEs that can use SNPN may support the SNPN access mode. Also, a UE configured to operate in SNPN access mode may be able to select and register with a SNPN and may not be able to select a PLMN. Also, a UE configured to operate in SNPN access mode may or may not be able to perform the SNPN selection procedure. Also, even if the UE is SNPN enabled, the UE that is not configured to operate in the SNPN access mode may not be able to select the SNPN and register with the SNPN, and the PLMN can be selected. Also, UEs that are not configured to operate in SNPN access mode may not be able to perform the SNPN selection procedure, and may be able to perform the PLMN selection procedure.

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 can select a SNPN via Uu or NWu established via a PDU session provided by a PLMN selected via Uu or NWu (non-3GPP access). good too. Also, a UE that does not operate in SNPN access mode can select a PLMN via Uu or NWu established via a PDU session provided by an SNPN selected via Uu or NWu (non-3GPP access). good too.

SNPN can use PLMN functions. Therefore, in this paper, PLMN may mean SNPN.

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

　Public network integrated NPN is a network realized using PLMN functional units. In other words, the Public network integrated NPN is an NPN that is virtually realized within the PLMN. Additionally, Public network integrated NPNs are NPNs that can be created via PLMN. Note that Public network integrated NPN may be implemented using the function of network slices. Specifically, a public network integrated NPN may be a network that can be implemented by using network slices allocated for the NPN. In this case, the Public network integrated NPN may be identified by S-NSSAI or by a combination of S-NSSAI and CAG ID.

In addition, Public network integrated NPN may be implemented using DN. Specifically, Public network integrated NPN may be a network that can be realized by using a DN for NPN. In this case, the Public network integrated NPN may be identified by DNN, or by a combination of DNN and CAG ID.

A CAG (Closed Access Groups) ID is information that identifies a group of subscribers permitted to connect to one or more cells associated with a CAG. A CAG may be a group identified by a CAG ID. CAG is a group used when implementing Public Network Integrated NPN with network slices. CAG may be used to prevent access attempts from UEs that are not NPN-authorized to network slices allocated for NPN. Furthermore, the CAG ID is unique information within the PLMN.

SNPN-enabled UE (SNPN enable UE) is a UE configured to use SNPN. A SNPN-enabled UE may store at least one piece of information about the SNPN. In other words, the configuration information of the SNPN-enabled UE may include information indicating that SNPN can be used. Additionally, an SNPN-enabled UE may support an SNPN access mode or an SNPN access mode of operation. In other words, a SNPN enabled UE may operate in SNPN access mode or SNPN access operation mode.

　In addition, the SNPN access mode is a mode in which the UE selects only SNPN. More specifically, the UE in SNPN access mode may be the mode of the UE when performing procedures, processing, etc. for registering and connecting to the SNPN. Further, when performing SNPN selection or ON-SNPN selection as network selection, or when performing normal registration procedures with SNPN, or when performing registration procedures for onboarding, or procedures for remote provisioning. should operate in SNPN access mode. Here, a UE operating in SNPN access mode may be referred to as a UE in SNPN access mode. Furthermore, a UE in SNPN access mode may be a SNPN enabled UE.

　In addition, SNPN access operation mode is a mode for connecting to SNPN via SNPN access mode or non-3GPP access. Here, "non-3GPP access" in SNPN may refer to the case where UE is connected to SNPN via PLMN. The UE may also operate in the SNPN access operation mode when operating in the SNPN access mode. Also, the UE may not operate in the SNPN access mode of operation if it does not operate in the SNPN access mode. Furthermore, the UE in SNPN access mode may be a UE in SNPN access mode of operation.

A UE operating in SNPN access mode or SNPN access operation mode may perform an SNPN selection process. UEs not operating in SNPN access mode or SNPN access operation mode may not perform the SNPN selection process. The SNPN selection process may have 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.

Also, UEs not operating in SNPN access mode or SNPN access operation mode may perform a PLMN selection process. A UE operating in SNPN access mode or 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 have an automatic PLMN selection mode and a manual PLMN selection mode.

A UE in SNPN access operation mode may mean a UE in SNPN access mode or a UE accessing SNPN via non-3GPP. In other words, even a UE that is not in SNPN access mode may be a UE in SNPN access operation mode when connecting to SNPN via non-3GPP.

In addition, 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 private use such as companies. There are two types of NPN: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. In addition, when described as NPN below, it may mean both SNPN and Public network integrated NPN.

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

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

In addition, URSP rules (UE Route Selection Policy rules) may consist of a list of one or more URSP rules (URSP (UE Route Selection Policy) Rule). Also, each URSP rule may consist of a rule precedence, and/or a traffic descriptor, and/or a list of route selection descriptors (List of Route Selection Descriptors). Here, the traffic descriptor may be used to specify matching conditions that the UE determines based on the URSP.

Here, the rule priority in URSP rules indicates the order of URSP rules enforced in the UE. When the UE receives URSP rules, that is, when it receives one or more URSP rules, the UE may refer to the rule priority in each URSP rule and apply the URSP rule with the highest priority first.

　In addition, the traffic descriptor in the URSP rules indicates when to apply the URSP rules. Here, the traffic descriptors in the URSP rule are application descriptors, and/or IP descriptors, and/or domain descriptors, and/or non-IP descriptors ( Non-IP descriptors), and/or DNN (Data Network Name), and/or Connection Capabilities.

Also, the application descriptor in the traffic descriptor in the URSP rule may contain the OS ID and the OS application ID.

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

Also, the domain descriptors in the traffic descriptor in the URSP rule may indicate the FQDN (Fully Qualified Domain Name) of the destination.

Also, the non-IP descriptor in the traffic descriptor in the URSP rule may indicate information identifying the destination of non-IP traffic (eg, ethernet traffic or unstructured traffic).

Also, the DNN in the traffic descriptor in the URSP rule may be information on the DNN provided by the application.

Also, the connection capability in the traffic descriptor in the URSP rule may indicate information provided by the UE's application when the UE requests connection to the network using a certain capability.

Also, the route selection descriptor list in the URSP rule may consist of one or more route selection descriptors (Route Selection Descriptor). Each route selection descriptor may consist of a rule selection descriptor precedence (Route Selection Descriptor Precedence) and/or a route selection component (Route selection components).

The rule selection descriptor priority indicates the order in which route selection descriptors are applied. When the UE receives the route selection descriptor list, that is, receives one or more route selection descriptors, the UE refers to the rule selection descriptor priority in each route selection descriptor, and selects the route selection description with higher priority. May be applied in order from child to child.

Also, the route selection configuration includes 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.

Here, the SSC mode selection may indicate that the application traffic is routed through the PDU session of the specified SSC mode.

The network slice selection may also indicate to route the application's traffic using one or more of the indicated PDU sessions that support S-NSSAI.

The DNN selection may also indicate that the application's traffic should be routed using PDU sessions that support one or more of the indicated DNNs.

　The PDU session type selection may also indicate that the application's traffic is routed using PDU sessions that support the indicated PDU session type.

Also, the non-seamless offload indication may indicate to offload application traffic to non-3GPP access.

Also, if the UE needs to establish a PDU session, the access type preference may indicate the access type for establishing the 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 3GPP access or non-3GPP access corresponding to the established SA PDU session may be indicated.

In addition, URSP rules may include URSP rules associated with HPLMN and URSP rules associated with VPLMN. Here, the URSP rules associated with the HPLMN may be the URSP rules generated by the HPLMN's PCF. Also, the URSP rules associated with the VPLMN may be the URSP rules generated by the V-PCF, which is the VPLMN's PCF. URSP rules may also be associated with the PLMN and sent and received between the UE and the network. More specifically, for example, an information element storing URSP rules may include the MCC and MNC of PLMN associated with each URSP rule. Further, the URSP rules may be associated with the PLMN and stored in each device of the UE or network.

Furthermore, the URSP rules used by the UE are generated based on the destination network and/or destination network policy and/or UE capabilities and/or network capabilities, UE subscriptions, etc. OK, let it be decided. More specifically, for example, if the UE is registered or attached to the HPLMN, it may use the URSP rules associated with the HPLMN. Also, for example, when the UE is registered or connected to the roaming destination VPLMN, the URSP rules associated with the HPLMN may be used, or the URSP rules associated with the VPLMN may be used.

SUPI (Subscription Permanent Identifier) is globally unique 5G subscriber permanent identification information assigned to each subscriber in the 5G system. SUPI types may include IMSI, NSI (Network Specific Identifier), GLI (Global Line Identifier), or GCI (Global Cable Identifier).

　SUCI (Subscription Concealed Identifier) is a privacy protection identifier that includes a concealed SUPI.

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

The first identification information in this embodiment is capability information indicating that the UE supports the use of URSP rules associated with the VPLMN. Here, the UE supports the URSP rules associated with the VPLMN, when the UE connects and/or registers with the VPLMN, it is possible to use the URSP rules generated by the VPLMN or the PCF in the VPLMN. It can be shown that

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

A UE supports URSP rules associated with a VPLMN may indicate that it is capable of storing the URSP rules generated/transmitted by the VPLMN or the PCF within the VPLMN. It may be indicated that it is possible to receive URSP rules generated by the VPLMN or the PCF within the VPLMN from the PCF of the VPLMN.

A UE supports URSP rules associated with a VPLMN means that it stores both the URSP rules generated/transmitted by the VPLMN or the PCF in the VPLMN and the URSP rules generated/transmitted by the HPLMN or the PCF in the HPLMN. It may be shown that it is possible to

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

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

Here, for example, the UE may include the first identification information in the registration request message to indicate that the UE supports the use of URSP rules associated with the VPLMN. Or, for example, the UE may not include the first identification information in the registration request message to indicate that the UE does not support the use of URSP rules associated with the VPLMN.

Also, the first identification information may be capability information indicating whether the UE supports the use of the 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 the 5GMM capability IE or may be included in the 5GMM capability IE.

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

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

Also, the first identification information may include the content of the second identification information described later. More specifically, for example, the UE transmits the first identification information to the network to request that the UE supports the use of the URSP rules associated with the VPLMN and to use the URSP rules associated with the VPLMN. It may indicate that That is, the UE may indicate a request to use the URSP rules associated with the VPLMN by sending the first identification information to the network or each device in the network.

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

For example, a UE attempting to register and/or connect to a VPLMN may send the second identification information in a message to the network or each device in the network as the URSP rules to indicate the use of the URSP rules associated with the VPLMN. You may indicate your request.

Also, the second identification information may include the content of the first identification information described above. More specifically, for example, the UE transmits the second identification information to the network to request that the UE supports the use of the URSP rules associated with the VPLMN and to use the URSP rules associated with the VPLMN. It may indicate that That is, the UE may indicate its support for using the URSP rules associated with the VPLMN by transmitting the second identification information to the network or each device in the network.

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

It should be noted that the second identification information may be information indicating the UE's preference regarding the URSP rules associated with the VPLMN. More specifically, the UE may indicate, via the second identification, a preference for URSP rules associated with the VPLMN to request the URSP rules associated with the VPLMN.

The third identification information in this embodiment may be capability information indicating that the VPLMN with which the UE registers and/or connects supports delivery of URSP rules associated with the VPLMN. Here, the third identification information may be identification information 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. .

Further, for example, the network or each device may indicate acceptance of the UE's request or use of the URSP rules associated with the VPLMN by transmitting third identification information to the UE. In other words, the UE receiving the third identification information may recognize that the network or each device has accepted the use of the URSP rules associated with the VPLMN.

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

The fourth identification information in this embodiment may indicate that the VPLMN with which the UE registers and/or connects distributes the URSP rules associated with the same VPLMN. Here, the fourth identification information is the response message when the network or each device receives a message containing the first and/or second identification information from the UE and accepts one or more of these identification information. It may be identification information to be included in the

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

[3. Embodiments of the present invention]
[3.1. Description of procedures or processes used in each embodiment]
Next, procedures used in each embodiment will be described. Note that the procedures or processes used in each embodiment may include registration procedures and UE policy delivery procedures.

Here, the registration procedure may be a procedure when the UE connects to the roaming destination network VPLMN, or may be an initial registration procedure.

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 timing as necessary after the registration procedure is completed.

In each embodiment, as shown in FIG. 2, HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are respectively the same device (that is, the same physical device). A case where they are configured as hardware, the same logical hardware, or the same software) will be described as an example. However, the contents described in this embodiment are also applicable when they are configured as different devices (that is, different physical hardware, different logical hardware, or different software). For example, data may be directly transmitted/received between them, data may be transmitted/received via the N26 interface between AMF and MME, or data may be transmitted/received via UE.

Each procedure will be explained below.

[3.1.1. Registration procedure]
A registration procedure will be described with reference to FIG. Note that the registration procedure in the present invention may be a registration procedure for registering with the VPLMN, which is the roaming destination network of the UE. Furthermore, in the following description, each device in the network may be a device within the VPLMN. In addition, hereinafter, the registration procedure is also referred to as this procedure.

In addition, unless otherwise specified, this procedure in the present invention may be an initial registration procedure. Alternatively, it may be a mobility and periodic registration update procedure.

The registration procedure is a procedure for the UE to take the lead in registering with access network_B and/or core network_B and/or DN and/or PLMN. As long as the UE is not registered with the network, the UE can execute this procedure at any time, such as when it is powered on. In other words, the UE can start this procedure at any timing as long as it is in the non-registered state (5GMM-DEREGISTERED state). Also, each device (especially UE and AMF) can transition to the registered state (5GMM-REGISTED state) based on the completion of the registration procedure. Each registration state may be managed by each device for each access. Specifically, each device may independently manage the state of registration for 3GPP access (registered state or non-registered state) and the state of registration for non-3GPP access.

Further, the registration procedure updates the location registration information of the UE in the network and/or periodically informs the network of the UE status from the UE and/or updates certain parameters of the UE in the network. procedure may be used.

　The UE may start the registration procedure when it moves across TAs (tracking areas). In other words, the UE may initiate the registration procedure when moving to a TA different from the TA indicated in the TA list (TAI list or registration area) it holds. Additionally, the UE may initiate this procedure when a running backoff timer or other timer expires. Additionally, the UE may initiate a registration procedure when the context of each device needs to be updated due to PDU session disconnection or invalidation. Additionally, the UE may initiate a registration procedure when there is a change in the UE's capability information and/or preferences regarding PDU session establishment. Further, the UE may initiate registration procedures periodically. Further, the UE may, based on completion of the UE configuration update procedure, or based on completion of the registration procedure, or based on completion of the PDU session establishment procedure, or based on completion of the PDU session management procedure, or at each procedure The registration procedure may be initiated based on information received from the network or based on expiry or deactivation of the backoff timer. Note that the UE is not limited to these, and can execute the registration procedure at any timing.

In addition, the procedure for transitioning from the state in which the UE is not registered in the network to the state in which it is registered is referred to as an initial registration procedure or a registration procedure for initial registration. Alternatively, the registration procedure performed while the UE is registered with the network can be called a registration procedure for mobility and periodic registration update or a roaming and periodic registration procedure. mobility and periodic registration procedure).

It should be noted that the UE may perform the aforementioned network selection before the registration procedure or in the initial state of the registration procedure to select and determine the PLMN or SNPN or ON-SNPN requested by the UE.

　New AMF 141 in Fig. 6 indicates the AMF in which UE_A10 is registered by this procedure, and old AMF 142 means the AMF in which the UE was registered by the procedure prior to this procedure. In this procedure, if no AMF change occurs, the interface between old AMF142 and new AMF141 and the procedure between old AMF142 and new AMF141 do not occur, and new AMF141 can be the same device as old AMF142. In this paper, when AMF is described, it may mean new AMF141, old AMF142, or both. Also, new AMF141 and old AMF142 may be AMF140.

First, UE_A 10 starts the registration procedure by sending a registration request message to new AMF 141 (S600) (S602) (S604). Specifically, the UE transmits an RRC message including a registration request message to the 5G AN 120 (or gNB) (S600). Note that the registration request message is a NAS message sent and received over the N1 interface. Also, the RRC messages may be control messages sent and received between the UE and the 5G AN 120 (or gNB). Also, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

Here, UE_A10 may include the first identification information and/or the second identification information in the registration request message and/or the NAS message including the registration request and/or the RRC message and/or transmit it. Note that the first and second identification information may be configured as information combining these.

Also, here, if the UE transmits the registration request message including the first identification information and/or the second identification information, the UE is a UE that supports the use of URSP rules associated with the VPLMN. It's okay. Further, a UE that supports the use of URSP rules associated with VPLMN may support the use of URSP rules associated with HPLMN in addition to supporting the use of URSP rules associated with PLMN.

If the UE supports the URSP rules associated with the VPLMN, the UE may transmit first identification information indicating that it supports the URSP rules associated with the VPLMN. In other words, the UE may send a 5GMM capability IE with the first identity set to indicate support for the URSP rules associated with the PLMN.

If the UE supports storing both the URSP rules associated with the VPLMN and the URSP rules associated with the HPLMN, the UE supports the use of the URSP rules associated with the VPLMN, or the URSP rules associated with the HPLMN A first identification may be transmitted indicating that the rules are supported.

Furthermore, the UE may transmit the second identification information as information indicating the UE's preferences regarding the URSP rules associated with the VPLMN. More specifically, the UE may indicate, via the second identification, a preference for URSP rules associated with the VPLMN to request the URSP rules associated with the VPLMN.

Also, the UE may further indicate that it supports the use of URSP rules associated with the VPLMN by transmitting the second identification information. More specifically, the UE may also be indicated to support the use of URSP rules associated with the VPLMN by not transmitting the first identity and only transmitting the second identity. .

Or, conversely, the UE may indicate a request to use the URSP rules associated with the VPLMN by sending only the first identification without sending the second identification.

Also, 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 does not support the URSP rules associated with the VPLMN. The first identification information indicating support for the URSP rules associated with the HPLMN may be transmitted, and the UE may transmit the URSP rules associated with the PLMN. It is not necessary to transmit the first identification information indicating support.

Furthermore, UE_A10 may send 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 5GS registration type IE. Alternatively, it may be information indicating that the registration procedure is for emergency registration.

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

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

UE_A10 may include the first identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (eg, MAC layer, RLC layer, PDCP layer) and transmit it. By transmitting these pieces of identification information, UE_A10 may indicate that UE_A10 supports each function, may indicate a UE request, or may indicate both of them. . Information indicating support for each function and information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

UE_A10 determines whether to transmit the first identification information to the network, UE capability information, and/or UE policy, and/or UE state, and/or user registration information, and/or UE may be selected and determined based on the context held by .

Further, UE_A 10 may send the registration request message including the first identification information to indicate that it requests network capability information indicating that the network supports the function corresponding to the first identification information. .

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 that includes the registration request message. For example, the UE may include a UE STATE INDICATION message generated by the UE in the registration request message.

Here, the UE state indication message may be included in the payload container information element in the registration request message, and the information element indicating the type of payload container (Payload container type information element) is May be a UE policy container. In addition, the UE may include a currently unused PTI (Procedure Transaction Identity) assigned by the UE to the PTI information element (PTI IE) in the UE status indication message.

In addition, a UE not operating in SNPN access operation mode shall transmit one or more UPSIs in the UE policy section identified in the PLMN ID part indicating the HPLMNs available to the UE or the selected PLMNs. MAY be included in the UPSI list information element (UE policy section identifier list information element (IE)) in the status indication message. Here, the selected PLMN may be VPLMN or EPLMN. Also, the PLMN ID part may be composed of MCC (Mobile Country Code) and MNC (Mobile Network Code).

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

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

Here, the purpose of the UE-initiated UE state indication procedure is to deliver the UPSI(s) of the UE policy section(s) or the UE supports ANDSP (Access Network Discovery and Selection Policy). or not, or deliver one or more OS IDs for the UE. where the UPSI(s) delivered by the UE in the UE initiated UE state indication procedure shall be the HPLMN or one or more UPSIs of the UE policy section identified by the UPSI with the PLMN ID part indicating the selected PLMN. you can Also, the selected PLMN may be the VPLMN or the EPLMN. Also, the PLMN ID part may be composed of MCC (Mobile Country Code) and MNC (Mobile Network Code).

Also, 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 the AMF or a set of AMFs, for example, 5G-S-TMSI ( 5G S-Temporary Mobile Subscription Identifier) or GUAMI (Globally Unique AMF Identifier).

Also, UE_A 10 transmits an SM message (eg, PDU session establishment request message) in the registration request message, or transmits an SM message (eg, PDU session establishment request message) together with the registration request message, The PDU session establishment procedure may be initiated during the registration procedure.

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

For example, based on the first identification information, the 5G AN 120 (or gNB) may select an AMF that supports the function corresponding to the capability information indicated by the first identification information. Specifically, the 5G AN (or gNB) corresponds to the UE capability information indicated by the first identification information, and distributes the URSP rules associated with the VPLMN or distributes the URSP rules associated with the VPLMN. An AMF that can be connected or communicated with the PCF to be performed may be selected.

　The AMF selection method is not limited to this, and the 5G AN (or gNB) may select AMF based on other conditions. The 5G AN (or gNB) extracts the registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). If the first identification information and/or the second identification information is included in the RRC message but not in the registration request message, the identification information included in the RRC message is sent to the selected AMF (new AMF141). , may be transferred together with the registration request message (S604).

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

Alternatively, the new AMF 141 may request the UE context from the old AMF 142 and receive the UE context from the old AMF 142 (S606, S608) before making the first condition determination. In that case, the new AMF 141 may execute S610 to S618 if the first conditional determination is true. On the other hand, the new AMF 141 may execute S614 if the first conditional determination is false.

Here, if the first condition determination is true, the control message transmitted and received in S614 may be a registration accept message, and if the first condition determination is false, The control message sent and received at S614 may be a Registration reject message.

In addition, the first condition determination is the reception of the registration request message, and/or each identification information included in the registration request message, and/or subscriber information, and/or network capability information, and/or operator policy, and It may be performed based on network conditions, and/or user registration information, and/or context held by the AMF, and/or the like.

For example, if the network permits the UE's request, the first condition determination may be true, and if the UE's request is not permitted by the network, the first condition determination may be false. In addition, if the network to which the UE is registered and/or the device in the network supports the function requested by the UE, the first condition determination is true and does not support the function requested by the UE. , the first conditional decision may be false. Further, the first conditional determination may be true if the transmitted/received identification information is permitted, and the first conditional determination may be false if the transmitted/received identification information is not permitted.

If the AMF indicated in the AMF identification information included in the message received by new AMF141 from UE is old AMF142, new AMF141 performs the procedures of S606 and S608, and the AMF included in the message received by new AMF141 from UE_A10. If the AMF indicated in the identification information is new AMF141, the procedures of S606 and S608 are not executed. In other words, if this procedure causes an AMF change, the procedures of S606 and S608 are executed, and if no AMF change occurs, the procedures of S606 and S608 are skipped.

　The UE context transfer procedure (S606, S608) will be explained.

First, new AMF 141 sends a UE context request message to old AMF 142 (S606). Here, the UE context request message sent by new AMF may be "Namf_Communication_UEContextTransfer". Furthermore, the UE context transmitted (S606) from the new AMF 141 to the old AMF 142 may contain the UE ID and allowed NSSAI.

Next, old AMF sends a UE context response message to new AMF as a response message to the received UE context request message (S608). Here, the old AMF may send the UE context to the new AMF 141 based on receiving the UE context request message. Further, the response message sent by old AMF may be "Response to Namf_Communication_UEContextTransfer". Furthermore, the old AMF may include the UE context and/or the SUPI (Subscription Permanent Identifier) in the UE context response message.

Note that if old ANF holds information about AM policy associations and UE policy associations (that is, policy control request triggers for UE policy update), old AMF will include these information in the UE context response message. may be included.

In addition, if the UE is performing the main registration procedure in the roaming network (VPLMN), the old AMF will further send the UE context response message including the V-PCF ID and H-PCF ID to the new AMF. good too. Here, the V-PCF ID and H-PCF ID received by the new AMF are used for PCF selection (S610) and/or AM policy association establishment/change (S612) and/or UE policy association establishment (S612). (S616) or the like. Details will be described later.

Furthermore, the New AMF that has received the UE context from the old AMF may generate the UE context based on the received UE context.

Next, new AMF executes PCF selection (S610). Here, the PCF selection indicates that the new AMF obtains the UE policy using the (V-)PCF identified by the (V-)PCF ID contained in the UE context (S608) received from the old AMF. May be executed when determined. Note that if the UE is performing registration procedures with the VPLMN, the AMF may select a V-PCF and obtain the UE policy from the selected V-PCF.

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

The new AMF 141 may then send a control message to the UE based on the determination of the first conditional 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. In the following, the case where the control message sent to the UE is a registration acceptance message will be described.

The new AMF 141 may send a control message including one or more of the third and/or fourth identification information. By transmitting these identification information and/or control messages, the new AMF 141 may indicate that the network supports the function indicated by the identification information, or that the UE request has been accepted. It may indicate that the request from the UE is not permitted or supported, or information combining these may be indicated. Also, the third and fourth identification information may be configured as information in which these are combined, or may be configured as identification information in which these are combined. Whether or not to include the third and/or fourth identification information in the control message may be determined by network capabilities, operator policy, or the like.

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

Here, for example, the third identification information is capability information indicating that the new AMF 141 and/or the core network support the function corresponding to the capability information indicated by the first identification information received from the UE. good.

Furthermore, the AMF may indicate that the UE has accepted the request indicated by the first and/or second identification information by transmitting the third identification information. More specifically, for example, the AMF sends the third identification information to the UE so that the UE indicates the request indicated by the first and/or second identification information or the use of the URSP rules associated with the VPLMN. The network or each device may indicate acceptance. In other words, the UE receiving the third identification information may recognize that the network or each device has accepted the use of the URSP rules associated with the VPLMN.

Also, for example, when the new AMF 141 receives the first and/or second identification information from the UE, even if the second identification information is not included in the control message, which is a registration acceptance message, The new AMF 141 and/or the core network recognizes the capability information of the UE indicated by the first identification information, and/or the new AMF 141 and/or the core network recognizes the function corresponding to the capability indicated by the first identification information. It may indicate to the UE that the network supports it.

Conversely, if the new AMF 141 does not include the third identification information in the control message that is the registration message, the new AMF 141 and/or the core network do not recognize the UE capability information indicated by the first identification information. , and/or the core network may indicate to the UE that the new AMF 141 and/or the core network do not support the functionality corresponding to the capabilities indicated by the first identification information.

Also, if the new AMF 141 does not receive the first identification information from the UE, it may or may not include the third identification information in the control message and transmit it.

Here, the fourth identification information may be a response corresponding to the content of the UE's request indicated by the second identification information received from the UE, and may indicate that the request from the UE is permitted. For example, if the AMF accepts or grants the UE's request indicated by the second identification, it may include the fourth identification in the control message and send it to the UE. Also, for example, when the AMF accepts or grants the request of the UE indicated by the second identification information, only the fourth identification information may be included in the control message.

Also, if the AMF does not receive the second identification information from the UE, it may include or not include the fourth identification information in the control message.

Further, for example, when the new AMF receives the first and/or second identification information from the UE, it sends a control message that is a registration acceptance message that does not include the third and/or fourth identification information. may indicate that the core network or new AMF has accepted the content indicated by the first and/or second identification information received from the UE. In other words, when the AMF receives the first and/or second identification information from the UE, the UE sends a registration acceptance message that does not include the third and/or fourth identification information. 1 and/or the second identification may indicate acceptance of the requested content.

Conversely, if the new AMF rejects what the first and/or second identification information received from the UE indicates, by sending a registration rejection message to the UE, the first and/or second identification information is May indicate content or rejection of the UE's request. Also, when the new AMF sends the registration rejection message to the UE, it may further include a cause value indicating the reason for rejection. Here, for example, the reason value indicating the reason for refusal may or may not be a reason indicating that the network or each device does not support the use of URSP rules associated with the VPLMN.

More specifically, for example, when the new AMF 141 receives the first and/or second identification information from the UE, a control message that is a registration acceptance message that does not include the third and/or fourth identification information By transmitting, the new AMF 141 and/or the core network recognize the UE capability information indicated by the first identification information, and/or the core network has the function corresponding to the capability indicated by the first identification information. It may indicate to the UE that the new AMF and/or core network support it. Note that, for example, when the new AMF transmits a registration rejection message to the UE, the core network does not recognize the UE capability information indicated by the first identification information received from the UE, the new AMF 141 and/or the core network. or not, and/or the core network may indicate to the UE that the new AMF and/or the core network do not support the capabilities corresponding to the capabilities indicated by the first identification.

Also, for example, when the new AMF 141 receives the first and/or second identification information from the UE, it transmits a control message that is a registration acceptance message that does not include the third and/or fourth identification information. new AMF 141 and / or that the core network recognizes the request of the UE indicated by the second identification information and / or that the core network supports the request indicated by the second identification information by The core network may indicate acceptance to the UE.

Also, for example, when the new AMF 141 receives the first and/or second identification information from the UE, it transmits a control message that is a registration acceptance message that does not include the third and/or fourth identification information. By, the new AMF 141 and / or the core network recognizes the UE capability information indicated by the first identification information and / or the UE request indicated by the second identification information, and / or the core network recognizes the first Indicate to the UE that the new AMF 141 and/or the core network support the capabilities corresponding to the capabilities indicated by the identification information, and/or that the core network supports the request indicated by the second identification information. / Or the core network may indicate acceptance to the UE.

Also, if the control message is a registration accept message, the AMF may send the registration accept message including an SM message (e.g., PDU session establishment accept message), or send an SM message (e.g., PDU session establishment accept message) together with the registration accept message. acknowledgment message) can be sent. However, this transmission method may be performed when an SM message (eg, a PDU session establishment request message) is included in the registration request message. Also, this transmission method may be performed when an SM message (eg, a PDU session establishment request message) is transmitted along with the registration request message. By performing such a transmission method, the AMF can indicate in the registration procedure that the procedure for the SM has been accepted.

In addition, the AMF receives each 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 Based on the context held by the AMF, etc., it may indicate that the UE's request has been accepted by sending a Registration Accept message, or indicate that the UE's request has been rejected by sending a Registration Reject message. may be indicated.

　The UE receives the control message via the 5G AN (gNB) (S614). If the control message is a registration acceptance message, the UE receives the registration acceptance message to recognize 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. can do. Or, if the control message is a registration rejection message, the UE receives the registration rejection message indicating that the UE's request in the registration request message is rejected, and the content of various identification information included in the registration rejection message. can be recognized. Also, the UE may recognize that the UE's request has been rejected if it does not receive the control message even after a predetermined period of time has elapsed after sending the registration request message.

Furthermore, if the control message is a registration acceptance message, the UE can transmit a registration complete message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S618). In addition, when the UE receives an SM message such as a PDU session establishment accept message, the UE may include an SM message such as a PDU session establishment complete message in the registration completion message, or may include the SM message. , may indicate that the procedure for SM is complete. Here, the registration completion message is a NAS message sent and received on the N1 interface, but is included in an RRC message and sent and received between the UE and the 5G AN (gNB).

　Next, the new AMF executes UE policy association establishment (S616). Here, the new AMF may send "Npcf_UEPolicyControl Create Request" to the PCF, and the PCF may send "Npcf_UEPolicyControl Create Response" to the new AMF to establish the UE policy association.

In addition, the PCF may trigger UE policy delivery procedures. Details of the UE policy delivery procedure are described in section 3.1.2.

　AMF receives the registration complete message via 5G AN (gNB) (S618). Also, each device completes this procedure based on transmission/reception of a registration acceptance message and/or a registration completion message.

Alternatively, each device may complete the registration procedure based on transmission/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. may

Each device may transition to or maintain a state in which the UE is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on transmission/reception of the registration acceptance message and/or the registration completion message. , based on the transmission and reception of the registration rejection message, the UE transitions to or maintains a state of not being registered with the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) on the access for which the UE received the registration rejection message for the current PLMN. You may Also, transition to each state of each device may be performed based on transmission/reception of a registration completion message or completion of a registration procedure.

Furthermore, each device may perform processing based on the information sent and received during the registration procedure upon completion of the registration procedure. For example, if information is sent or received indicating that some of the UE's requests were rejected, it may know why the UE's requests were rejected. Further, each device may perform this procedure again, or may perform the registration procedure for Core Network_A or another cell, based on the reason why the UE's request was rejected.

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

For example, when the UE receives the third and/or fourth identification information in the registration acceptance message in the registration procedure in the VPLMN, the UE receives the VPLMN in the UE policy delivery procedure described later during or after this procedure. It may recognize that URSP rules associated with are delivered and that use of the delivered URSP rules is permitted.

Further, for example, when the UE receives the third and/or fourth identification information in the registration acceptance message in the registration procedure in the VPLMN, the network supports delivery of the URSP rules associated with the VPLMN. You can recognize that there are

Note that if the UE receives a registration acceptance message that does not contain both the third and fourth identities in the registration procedure at the VPLMN, the URSP rules associated with the HPLMN are delivered and the use of the delivered URSP rules may recognize that is allowed.

Note that if the UE receives a registration accept message that does not contain both the third and fourth identities in the registration procedure at the VPLMN, the network does not support delivery of the URSP rules associated with the VPLMN. may be recognized.

[3.1.2. UE policy delivery procedure]
Next, the UE policy distribution procedure will be explained using FIG. Here, the UE policy delivery procedure is a PCF-initiated procedure for updating the configuration of the UE, and may be a procedure for providing the policy transparently to the UE by the PCF. Here transparent means that the UE policy sent by the PCF is not modified by the AMF and delivered to the UE using a transparent container. In addition, the UE policy distributed in this procedure may be URSP rules, and there may be URSP rules associated with HPLMN or URSP rules associated with VPLMN.

　The UE policy delivery procedure may be a UE Configuration Update procedure for transparent UE Policy delivery. Hereinafter, the UE policy distribution procedure is also referred to as this procedure. Note that this procedure may be a procedure that can be executed after the PCF selection by the AMF (S610) and the AM policy association establishment/change (S612) are completed.

This procedure may also be a network-requested UE policy management procedure, in which the PCF sends a "Manage UE policy command" containing UE policy information to the UE. good too. Here, "Manage UE policy command" may be a message sent to the UE as a DL NAS transport message. It should be noted that the detailed procedure of the UE policy management procedure for network requests may be the same as the procedure of the UE configuration update procedure for UE policy delivery.

In addition, this procedure may be a procedure that is executed at any time during the registration procedure or after the completion of the registration procedure. Here, when this procedure is executed during the registration procedure, it may be a procedure that is started by being triggered by the PCF in the aforementioned UE policy association establishment (S616).

Also, this procedure may be a procedure that is executed when the UE is performing registration procedures with the VPLMN, which is the roaming destination network, or has completed the registration procedures with the VPLMN. Here, the UE policy delivered to the UE visiting the VPLMN may be the URSP rules generated by the V-PCF and associated with the delivered VPLMN.

Furthermore, this procedure may be executed while the UE is registered with or connected to the HPLMN or VPLMN, which is the roaming destination network. More specifically, this procedure may be performed by the UE during the VPLMN registration procedure to the HPLMN, or at any time after the completion of the HPLMN or VPLMN registration procedure, initiated by the network or PCF. , may be a procedure to initiate. Note that the PCF may be the V-PCF when this procedure is executed in the VPLMN.

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 the UE policy update, or the like. In other words, the PCF may perform this procedure during the registration procedure, or after the completion of the registration procedure, at any time the UE policy needs to be updated. Here, the registration procedure may be an initial registration procedure.

More specifically, for example, the determination of UE policy update by PCF in the UE policy distribution procedure performed during the registration procedure is performed by New AMF (AMF) in PCF in the procedure of S616 described in Section 3.1.1. Update the UE policy information by comparing the PSI (policy section identifier) list contained in the UE policy information contained in the Npcf_UEPolicyControl_Create Request, which is a message sent to It may be based on the judgment of whether it must be done.

Or, for example, the determination of UE policy update by the PCF in a network-initiated network-initiated UE policy delivery procedure to be performed at any time, the PCF needs to check the latest list of PSIs and send them to the UE. May be based on determining UE policy.

　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). Here, 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. Further, the message sent from PCF to AMF may contain SUPI, UE policy container.

Note that here, if the PCF finds that the size of the UE policy information exceeds a predefined limit, the PCF will divide it into logically independent UE policies with a size less than the limit and call "Namf_Communication_N1N2MessageTransfer ” service operation may be performed and sent multiple times.

　Here, the UE policy sent from the PCF to the AMF in S702 may be URSP rules. More specifically, for example, in the registration procedure in the VPLMN, the UE includes the first and / or second identification information in the registration request message and transmits it to the network, and the content indicated by the one or more identification information is transmitted to the network. and the registration procedure is completed, the UE policy sent from the V-PCF to the (V-)AMF at S702 may be the URSP rules associated with the VPLMN generated by the V-PCF.

　Next, the AMF that received 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 AMF, and is executed when the UE is in the registered state (RM-REGISTERED state) and the disconnected state (CM-IDLE state). good. In other words, when the UE is in the registered state (RM-REGISTERED state) and the connected state (CM-CONNECTED state), the network-triggered service request (S704) may not be executed.

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

Further, the UE transmits the first and/or second identification information in a registration request message in the registration procedure in the VPLMN, and the content of the first and/or second identification information is accepted by the network. If so, the URSP rules received at S706 may be the URSP rules associated with the VPLMN.

Also, 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 URSP rules associated with HPLMN and/or URSP rules associated with VPLMN. Furthermore, when the UE receives URSP rules from the network in S706, it may manage storage, update, replacement, deletion, etc. for each PLMN associated with the received URSP. Also, the UE may store and manage 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 HPLMN.

Here, when the UE deletes the URSP rules, the URSP rules received by the UE from the network in S706 may be empty ("empty" or "0"). It may be per PLMN. In other words, if the URSP rules for a particular PLMN are empty, and the UE has already stored the URSP rules corresponding to that PLMN, the UE may delete the corresponding URSP rules. In other words, when deleting the URSP rules stored in the UE, the PCF may nullify the URSP rules corresponding to the PLMN to be deleted in generating the URSP rules.

Here, the behavior of the UE that received the URSP rules from the PCF via the AMF in S706 may be as follows.

For example, if the UE completes the registration procedure by sending a registration request message including the first and second identification information to the network in the VPLMN, then in S706 of the UE policy delivery procedure during the registration procedure or after the completion of the registration procedure The URSP rules associated with the received VPLMN may be associated with the VPLMN and stored. Furthermore, if the UE receives new URSP rules associated with the same VPLMN during another registration procedure or at S706 of the UE policy delivery procedure performed after the completion of the registration procedure, the UE will be associated with the VPLMN already stored. The old URSP rules may be updated or replaced with the new URSP rules. Furthermore, if empty URSP rules associated with the same VPLMN are received in S706 of the UE policy delivery procedure performed during another registration procedure or after completion of the registration procedure, the old URSP rules associated with the already remembered VPLMN URSP Rules may be deleted.

Also, for example, a UE that has already memorized the URSP rules associated with the HPLMN and connects to the VPLMN may use the URSP rules associated with the VPLMN in S706 of the UE policy distribution procedure that is performed during the registration procedure or after the registration procedure is completed. If received, the URSP rules associated with the received VPLMN may be stored without deleting the URSP rules associated with the already stored HPLMN.

Also, for example, if a UE that does not support the URSP rules associated with the VPLMN receives the URSP rules associated with the VPLMN at S706 of the UE policy delivery procedure performed during the registration procedure or after completing the registration procedure, the UE may , may not store the URSP rules associated with the received VPLMN, or may ignore the URSP rules associated with the received VPLMN.

　In addition, the behavior of the UE that received the URSP rules from the PCF via the AMF in S706 is not limited to these.

Upon receiving the UE policy from the PCF via the AMF, the UE updates the UE policy and transmits the UE policy distribution result to the AMF (S708).

Upon receiving the UE policy delivery result from the UE, the AMF uses the AMF service communication message notification service to send a message to the PCF (S710). Here, the message sent from the AMF to the PCF, more specifically, the UE policy container received by the AMF from the UE is transferred using the "Namf_Communication_N1MessageNotify" service operation. Note that S710 may be executed when the PCF has subscribed to receive acknowledgment of the UE policy container.

In addition, the PCF maintains and stores the latest list of PSI delivered to the UE in this procedure, and uses the Nudr_DM_Update (SUPI, Policy Data, Policy Set Entry, updated PSI data) service operation to update the latest PSI in the UDR. Update the list.

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

Here, the UE does not include any of the first and second identities if the UE did not indicate in its registration procedure with the VPLMN that it supports and/or requires the use of the URSP rules associated with the VPLMN. It may be to send a registration request message to the network (VPLMN). In other words, the UE neither supports the use of the URSP rules associated with the VPLMN nor requests the use of the URSP rules associated with the VPLMN to the network (VPLMN), and performs the registration procedure and the registration procedure with the VPLMN. may be performed.

Also, in the registration procedure in the VPLMN, a UE that has sent a registration request message that does not contain either the first identification information or the second identification information may be a UE that does not support the use of URSP rules associated with the PLMN. .

More specifically, for example, in the registration procedure in the VPLMN, the UE transmits a registration request message that does not include the first identification information and the second identification information to the network, and the network sends the UE It may be the case that the registration procedure is completed by transmitting the registration acceptance message.

During the registration procedure or in the UE policy delivery procedure after completion, if the UE receives the URSP rules associated with the VPLMN, the UE policy delivery result (S708) will be a message indicating that the UE policy delivery has failed. May be sent to AMF. Furthermore, the UE may not remember the URSP rules associated with the received VPLMN.

[3.3. Second embodiment]
A second embodiment of the present invention indicates that the UE, in the registration procedure to the VPLMN, supports and/or requires the use of URSP rules associated with the VPLMN, and during or after the registration procedure, the network or each of the networks. It is an embodiment regarding the behavior of the UE when the device sends the URSP rules associated with the VPLMN and the URSP rules associated with the HPLMN to the UE. The second embodiment is also referred to as the present embodiment in this chapter.

In other words, in the registration procedure in the VPLMN, the UE sends a registration request message containing the first identification and/or the second identification to the network, and the network sends a registration acceptance message to the UE. This may be the case when the registration procedure is completed.

If the URSP rules associated with the HPLMN and the URSP rules associated with the VPLMN are received during the registration procedure or in the UE policy delivery procedure after completion, the UE may store the received URSP rules for each PLMN. . Furthermore, the UE may preferentially use the URSP rules associated with the VPLMN that is the visiting PLMN.

[4. Modification]
The program that runs on the device according to the present invention may be a program that controls a central processing unit (CPU) or the like to make a computer function so as to implement the functions of the embodiments according to the present invention. Programs or information handled by the programs are temporarily stored in volatile memory such as random access memory (RAM), nonvolatile memory such as flash memory, hard disk drives (HDD), or other storage systems.

A program for realizing the functions of the embodiments related to the present invention may be recorded in a computer-readable recording medium. It may be realized by causing a computer system to read and execute the program recorded on this recording medium. The "computer system" here is a computer system built into the device, and includes hardware such as an operating system and peripheral devices. In addition, "computer-readable recording medium" means a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically retains a program for a short period of time, or any other computer-readable recording medium. good too.

Also, each functional block or features of the apparatus used in the above-described embodiments may be implemented or performed in an electrical circuit, eg, an integrated circuit or multiple integrated circuits. Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor or any conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit, or may be composed of an analog circuit. In addition, in the event that advances in semiconductor technology lead to the emergence of integrated circuit technology that can replace current integrated circuits, one or more aspects of the present invention can use new integrated circuits based on this technology.

It should be noted that the present invention is not limited to the above-described embodiments. In the embodiments, an example of the device is described, but the present invention is not limited to this, and stationary or non-movable electronic equipment installed indoors and outdoors, such as AV equipment, kitchen equipment , cleaning/washing equipment, air-conditioning equipment, office equipment, vending machines, other household equipment, and other terminal equipment or communication equipment.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are included within the scope of the present invention. In addition, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of the present invention. be Moreover, it is an element described in each said embodiment, and the structure which replaced the element with which the same effect is produced is also included.
(Cross reference to related applications)
This application claims the benefit of priority to Japanese Patent Application: Japanese Patent Application No. 2022-022068 filed on February 16, 2022, and by referring to it, all of its contents are Included in this document.

1 Mobile communication system
10 UE_A
30 PGW-U
32PGW-C
35 SGW
40 MMEs
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
140AMF
141 new AMF
142 old AMF
150UDM
160PCF
190 Core Network_B

Claims (1)

1. A UE (User Equipment) comprising a transmitting/receiving unit, a storage unit, and a control unit,
   The storage unit stores first URSP rules,
   The first URSP (UE Route Selection Policy) rules are URSP rules associated with HPLMN (Home Public Land Mobile Network),
   The transmitting/receiving unit receives the second URSP rules in the procedure for receiving URSP rules started during the registration procedure,
   The second URSP rules are URSP rules associated with VPLMN (Visited Public Land Mobile Network),
   The control unit stores the second URSP rules in the storage unit without deleting the first URSP rules.
   A UE characterized by:

Images