WO2021215227A1 - Ue (user equipment) - Google Patents

Abstract

Communication means are provided to realize a function relating to management of information for appropriate PLMN selection, taking into consideration network slice support for each PLMN in 5GS. Provided are a method for acquisition of information in an initial registration of UE, procedures for updating information, and PLMN selection based on information, and communication means, to realize management of information for appropriate PLMN selection, taking into consideration network slice support by a PLMN at a relocation destination of UE.

Description

UE (User Equipment)

The present invention relates to UE (User Equipment). The present application claims priority based on Japanese Patent Application No. 2020-077041 filed in Japan on April 24, 2020, the contents of which are incorporated herein by reference.

3GPP (3rd Generation Partnership Project), which is engaged in standardization activities for mobile communication systems in recent years, is studying SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution).

In recent years, 3GPP has also been studying the next-generation communication technology and system architecture of 5G (5th Generation) mobile communication systems, which are next-generation mobile communication systems. In particular, 5GS (5G) is a system that realizes 5G mobile communication systems. 5G System) is being specified (see Non-Patent Documents 1 to 4). 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.

In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services.

Furthermore, 5G defines network slices, which are logical networks that provide specific network functions and specific network characteristics for specific service types and specific groups. For example, the network slice may be a logical network provided for a terminal having a low latency function, or may be a logical network provided for a sensor terminal used for IoT (Internet of Things). good.

In 3GPP, eNS (Enhancement of Network Slicing) is being studied in order to further study further functions related to network slicing. 3GPP considers Phase 2 of the eNS as a feature for selecting the appropriate destination mobile network (VPLMN) in consideration of the slice support that the UE used in the home mobile network (HPLMN) at the destination. Considering addition (see Non-Patent Document 5).

However, the implementation method to meet the above requirements has not yet been clarified.

One aspect of the present invention has been made in view of the above circumstances, and is to provide a method for realizing a function for eNS in 5GS.

The UE (User Equipment) according to one aspect of the present invention includes a transmission / reception unit, a control unit, and a storage unit, and the transmission / reception unit is the first PLMN (Public Land Mobile Networks) in the first PLMN. Registration acceptance message containing the first S-NSSAI (Single Network Slice Selection Assistance Information) permitted to be used in the first S-NSSAI and the second PLMN ID indicating the second PLMN associated with the first S-NSSAI. Is received from the core network, the storage unit stores the second PLMN ID in association with the first S-NSSAI, and the control unit associates the first S-NSSAI with the first S-NSSAI. The second PLMN can be selected based on the second PLMN ID, the control unit transitions to the registration state based on the reception of the registration acceptance message, and the transmission / reception unit sends the registration acceptance message. After receiving, in the first PLMN, the first S-NSSAI permitted to be used in the first PLMN and the third PLMN associated with the first S-NSSAI are shown. When the setting update command including the PLMN ID is received, the storage unit stores the third PLMN ID and the first S-NSSAI in association with each other, and the control unit stores the first S. -It is characterized in that the third PLMN is selected based on the third PLMN ID associated with the NSSAI.

According to one aspect of the present invention, eNS support is possible in 5GS, and the visited mobile network (VPLMN) considering the support of slices used by the UE in the home mobile network (HPLMN) at the destination. You can choose.

It is a figure explaining the outline of the mobile communication system (EPS / 5GS). It is a figure explaining the detailed structure of the mobile communication system (EPS / 5GS). It is a figure explaining the apparatus configuration of UE. It is a figure explaining the structure of the access network apparatus (gNB) in 5GS. It is a figure explaining the structure of the core network apparatus (AMF / SMF / UPF) in 5GS. It is a figure explaining the registration procedure. It is a figure explaining the change / update procedure of a UE setting. It is a figure explaining the embodiment in one aspect of this invention.

Hereinafter, the best mode for carrying out one aspect of the present invention will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system when one aspect of the present invention is applied will be described.

[1. System overview]
First, FIG. 1 is a diagram for explaining the outline of the 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.

In FIG. 1, the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6. It is stated that

In the following, these devices / functions may be described by omitting symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. ..

In addition, Fig. 2 shows the devices / functions of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc. An interface for connecting these devices / functions to each other is described.

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

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

UE is a device that can connect to network services via 3GPP access (3GPP access network, also called 3GPP AN) and / or non-3GPP access (non-3GPP access network, also called 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 capable of connecting to both EPS and 5GS. The UE may be provided with UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device.

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

In addition, access network_B corresponds to 5G access network (5G AN). 5GAN is composed of NG-RAN (NG Radio Access Network) and / or non-3GPP access network. One or more gNB (NR Node B) 122s are placed in the NG-RAN. In the following, gNB122 may be described by omitting symbols such as eNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, gNB is a base station device newly designed for 5GS, and has a function different from that of the base station device (eNB) used in EPS, which is a 4G system. When there are a plurality of gNBs, each gNB is connected to each other by, for example, an Xn interface.

Further, the non-3GPP access network may be an untrusted non-3GPP (untrusted non-3GPP) access network or a trusted non-3GPP (trusted non-3GPP) access network. Here, the unreliable non-3GPP access network may be a non-3GPP access network that does not perform security management in the access network, for example, a public wireless LAN. On the other hand, the reliable non-3GPP access network may be an access network defined by 3GPP, and may include TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP Gateway function).

In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN may be referred to as non-3GPP access. In addition, the nodes arranged in the access network_B may be collectively referred to as NG-RAN nodes.

In the following, the devices included in the access network_A and / or the access network_B and / or the access network_A, and / or the devices included in the access network_B are the access network or the access network device. It may be called.

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

In addition, core network_B corresponds to 5GCN (5G Core Network). 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 in 5GCN. Here, 5GCN may be expressed as 5GC.

In the following, the core network_A and / or the core network_B, the device included in the core network_A, and / or the device included in the 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 network operator (Mobile) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN. It may be an IP mobile communication network operated by Network Operator; MNO), it may be a core network for a mobile communication operator that operates and manages mobile communication system 1, or it may be an MVNO (Mobile Virtual Network Operator). ), MVNE (Mobile Virtual Network Enabler), and other 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 PDN and DN are the same is described, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. The DN may be configured as a packet data service network or may be configured for each service. Further, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may be connecting to a communication terminal or server device arranged in the PDN. Further, sending and receiving user data to and from the PDN may be sending and receiving user data to and from a communication terminal or server device arranged in the PDN. Note that PDN may be expressed as DN, and DN may be expressed as PDN.

In the following, 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 in these are referred to as a network or network device. It may be called. That is, the fact that the network and / or the network device sends and receives messages and / or executes the procedure means that the access network_A, core network_A, PDN, access network_B, core network_B, and DN It means that at least a part 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. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send and receive (communicate) user data with the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

Here, IP communication is data communication using IP, and data is transmitted and received by IP packets. An IP packet is composed of an IP header and a payload part. The payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS. In addition, 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 an IP header is not added, or a UE can add another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be sent and received may be sent and received.

Further, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may be configured with devices not shown in FIG. For example, core network_A and / or core network_B and / or PDN_A and / or DN_A includes AUSF (Authentication Server Function) and AAA (Authentication, authorization, and accounting) server (AAA-S). May be good. The AAA server may be located outside the core network.

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

Also, the AAA server is a device that has authentication, approval, and billing functions that connects directly to AUSF or indirectly via other network devices. The AAA server may be a network device in the core network. The AAA server may not be included in the core network_A and / or the core network_B, but may be included in the PLMN. 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 in the PLMN managed by the 3rd Party.

Although each device / function is described one by one in FIG. 2 for the sake of simplification of the figure, a plurality of similar devices / functions may be configured in the mobile communication system 1. 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. Etc. 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 done. Further, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

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

[2.1. UE device configuration]
First, an example of a UE (User Equipment) device configuration 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, the transmission / reception unit_A320, and the storage unit_A340 are connected via a bus. The transmitter / receiver_A320 is connected to the antenna 310.

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 needed.

The transmission / reception unit_A320 is a functional unit for wireless communication with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can send and receive user data and / or control information between the access network device and / or the core network device and / or PDN and / or DN using the transmitter / receiver_A320. can.

Explaining in detail with reference to FIG. 2, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmission / reception unit_A320. In addition, the UE can communicate with the base station device (gNB) in the 5GAN by using the transmission / reception unit_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum) messages to and from AMF via the N1 interface by using the transmitter / receiver _A320. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN.

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

[2.2. GNB device configuration]
Next, an example of the device configuration of gNB will be described with reference to FIG. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transmission / reception unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transmission / reception unit_B530, and storage unit_B540 are connected via a bus. The transmitter / receiver_B530 is connected to the antenna 510.

Control unit_B500 is a functional unit that controls the operation and function of the entire gNB. The control unit_B500 realizes various processes in the gNB by reading and executing various programs stored in the storage unit_B540 as needed.

The network connection part_B520 is a functional part for gNB to communicate with AMF and / or UPF. That is, the gNB can send and receive user data and / or control information between the AMF and / or the UPF by using the network connection unit_B520.

The transmitter / receiver_B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit / receive user data and / or control information to / from the UE by using the transmission / reception unit_B530.

Explaining in detail with reference to FIG. 2, the gNB in the 5GAN can communicate with the AMF via the N2 interface by using the network connection _B520, and the UPF via the N3 interface. Can communicate with. In addition, gNB can communicate with the UE by using the transmission / reception unit_B530.

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

[2.3. AMF equipment configuration]
Next, an example of the AMF device configuration will be described with reference to FIG. The AMF consists 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. The AMF may be a node that handles the control plane.

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

The network connection part_B720 is a functional part for AMF to connect to the base station equipment (gNB) in 5GAN and / or SMF, and / or PCF, and / or UDM, and / or SCEF. That is, the AMF uses the network connection_B720 to communicate with the base station equipment (gNB) in 5GAN and / or SMF, and / or PCF, and / or UDM, and / or SCEF. Data and / or control information can be sent and received.

Explained in detail with reference to FIG. 2, the AMF within the 5GCN can communicate with the gNB via the N2 interface by using the network connection _A620 and with the UDM via the N8 interface. It can communicate, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN. If the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection _A620.

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

AMF has a function to exchange control messages with RAN using N2 interface, a function to exchange NAS messages with UE using N1 interface, a function to encrypt and protect the integrity of NAS messages, and registration management. (Registration management; RM) function, connection management (CM) function, reachability management (Reachability management) function, mobility management (Mobility management) function such as UE, SM (Session Management) between UE and SMF Message forwarding function, access authentication (Access Authorization) function, security anchor function (SEA; Security Anchor Functionality), security context management (SCM; Security Context Management) function, N2 for N3IWF (Non-3GPP Interworking Function) It has a function to support an interface, a function to support transmission / reception of NAS signals with a UE via N3IWF, a function to authenticate a UE connected via N3IWF, and the like.

Also, in registration management, the RM status for each UE is managed. The RM state may be synchronized between the UE and AMF. The RM state includes a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered in the network, and the UE context in the AMF does not have valid location information or routing information for the UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, the UE is registered in the network, so the UE can receive services that require registration with the network. The RM state may be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.

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

Furthermore, in 5GMM-DEREGISTERED, each device may be in a state where the 5GMM context has not been established, the position information of UE_A10 may not be known to the network, or the network reaches UE_A10. It may be in an impossible state. If each device is 5GMM-DEREGISTERED, UE_A10 may start the registration procedure or establish the 5GMM context by executing the registration procedure.

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

Furthermore, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). Furthermore, the CM state in non-3GPP access includes the non-connected state (CM-IDLE state over non-3GPP access) in non-3GPP access and the connection state (CM-CONNECTED state over non-3GPP access) in non-3GPP access. ) May be there. The disconnected 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 (5GMM mode). In this case, the non-connected state may be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state may be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Furthermore, the disconnected state in 3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over 3GPP access) in 3GPP access, and the connection state in 3GPP access is 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access). Further, the non-connection state in non-3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connection state in non-3GPP access is non. It may be expressed as 5GMM connection mode (5GMM-CONNECTED mode over non-3GPP access) in -3GPP access. The 5GMM non-connection mode may be expressed as an idle mode, and the 5GMM connection mode may be expressed as a connected mode.

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

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

[2.4. SMF device configuration]
Next, an example of the SMF device configuration will be described with reference to FIG. The SMF consists 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. The SMF may be a node that handles the control plane.

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

The network connection part_B720 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 between the AMF and / or the UPF and / or the PCF and / or the UDM by using the network connection part_B720.

Explained in detail with reference to FIG. 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface by using the network connection _A620 and with the UPF via the N4 interface. It can communicate, it can communicate with the PCF via the N7 interface, and it can communicate with the UDM via the N10 interface.

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

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

[2.5. UPF device configuration]
Next, an example of the UPF device configuration will be described with reference to FIG. The UPF consists 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. The UPF may be a node that handles the control plane.

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

The network connection unit_B720 is a functional unit for the UPF to connect to the base station equipment (gNB) and / or SMF and / or DN in 5GAN. That is, the UPF uses the network connection _B720 to send and receive user data and / or control information between the base station equipment (gNB) in 5GAN and / or SMF and / or DN. Can be done.

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

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

The UPF acts as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting the DN (ie, as a gateway between the DN and the core network_B). Data transfer function), packet routing and transfer function, UL CL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, and multi-homed PDU session support. It has a branching point function, a QoS (Quality of Service) processing function for userplane, a function for verifying uplink traffic, a function for buffering downlink packets, and a function for triggering downlink data notification (Downlink Data Notification).

The UPF may also be a gateway for IP communication and / or non-IP communication. In addition, the UPF may have a function of transferring IP communication, or may have a function of converting between non-IP communication and IP communication. Further, the plurality of gateways to be arranged may be a gateway connecting the core network_B and a single DN. The UPF may have connectivity with other NFs, or may be connected to each device via the other NFs.

The user plane is user data transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. Further, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface. Further, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and 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 a U-Plane.

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

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

[2.6. Description of other devices and / or functions and / or identification information in this embodiment]
Next, other devices and / or functions and / or identification information will be described.

The network refers to at least a part of the access network_B, core network_B, and DN. Further, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network device. That is, the fact that the network executes message transmission / reception and / or processing may mean that a device (network device and / or control device) in the network executes message transmission / reception and / or processing. .. Conversely, the fact that a device in the network executes message transmission / reception and / or processing may mean that the network executes message transmission / reception and / or processing.

In addition, SM (session management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and are sent and received between UE_A10 and SMF_A230 via AMF_A240. It may be a control message to be executed. In addition, SM messages include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, and a PDU session modification request (PDU session modification). request message, PDU session modification command message, PDU session modification complete message, PDU session modification command reject message, PDU session modification rejection (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 establishment procedure), PDU session modification procedure (PDU session modification procedure), and PDU session release procedure (UE-requested PDU session release procedure). It may be. Each procedure may be a procedure started from the UE or a procedure started from the NW.

Further, the MM (Mobility management) message (also referred to as NAS MM message) may be a NAS message used for the procedure for MM, and may be a control message sent and received between UE_A10 and AMF_A240. In addition, the MM message includes a registration request message, a registration accept message, a registration reject message, a de-registration request message, and a de-registration accept message. ) Message, configuration update command message, configuration update complete message, service request message, service accept message, service reject message, notification ) Messages, Notification response messages, etc. may be included. In addition, the procedure for MM or MM procedure is registration procedure (Registration procedure), deregistration procedure (De-registration procedure), generic UE configuration update procedure, authentication / approval procedure, service request procedure ( Service request procedure), paging procedure (Paging procedure), notification procedure (Notification procedure) may be included.

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

Further, the non 5GS service may be a service other than the 5GS service, and may include an EPS service and / or a non EPS service.

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

In addition, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the relationship between the DN that provides the PDU connectivity service and the UE, but it is established between the UE and the external gateway. It may be connectivity. By establishing a PDU session via the access network_B and the core network_B in 5GS, the UE can send and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. The UE can use the PDU session to send and receive user data to and from devices such as application servers located in the DN.

Note that each device (UE and / or access network device and / or core network device) may manage one or more identification information in association with each other for the PDU session. Note that these identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information. It may be further included. Further, when a plurality of PDU sessions are established, the identification information associated with the PDU session may have the same content or different contents.

Further, 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 the core network_B190. Further, the DNN may correspond to an APN (Access Point Name).

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. When Ethernet is specified, it indicates that Ethernet frames are sent and received. Further, Ethernet may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is sent and received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology. As the P2P tunneling technique, for example, a UDP / IP encapsulation technique may be used. The PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.

PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator who is a (mobile) telecommunications carrier, and the operator can be identified by the PLMN ID. 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 Home PLMN (HPLMN). The visited PLMN (Visited PLMN; VPLMN) may be a PLMN different from the HPLMN or HEPLMN (Home Equivalent PLMN). PLMN may mean core network.

Furthermore, the UE may have an Equivalent HPLMN list for identifying one or more EHPLMNs (Equivalent HPLMN, equivalent HPLMN) in the USIM. The PLMN different from HPLMN and / or EHPLMN may be VPLMN (Visited PLMN or vPLMN).

The PLMN that the UE has successfully registered may be an RPLMN (Registered PLMN, registered PLMN). Each device receives, / or retains, and / or stores an Equivalent PLMN list from the RPLMN to identify one or more EPLMNs (Equivalent PLMN, equivalent PLMN) that can be used equivalently to the RPLMN in the PLMN selection of the UE. You may.

The current PLMN (current PLMN) is a PLMN requested by the UE and / or a PLMN selected by the UE, and / or an RPLMN, and / or a PLMN permitted by the network, and / or a core network device that sends and receives messages. It may be the PLMN to which it belongs.

The requested PLMN means the network to which the message is sent when the UE sends the message. Specifically, it may be the PLMN selected by the UE when the UE sends a message. The required PLMN is the PLMN requested by the UE and may be the current PLMN. Further, when the UE is in the registered state, the requested PLMN may be the registered PLMN.

Further, the SOR transparent container information element (SOR (Steering of Roaming) transparent container IE) may include information for HPLMN and / or VPLMN to indicate the optimum roaming destination network for the roaming UE. Specifically, the SOR transparent container information element may include list of preferred PLMN / access technology combinations.

In addition, the SOR transparent container information element and / or list of preferred PLMN / access technology combinations may be included in the "Secured packet" encrypted by the security function of PLMN (HPLMN), and is called "Secured packet". It may be done.

The SOR application function (SOR-AF), which is one of the entities in the core network, may provide UDM with information including list of preferred PLMN / access technology combinations. The AMF may refer to the information including the list of preferred PLMN / access technology combinations provided to the UDM, generate the SOR transparent container information element based on this information, and send it to the UE.

Here, list of preferred PLMN / access technology combinations may be a list composed of combinations of PLMN (preferred PLMN) and access technology (access technology), and each combination may be arranged in descending order of priority. ..

In addition, for example, in the network switching by mobility of the UE and the PLMN selection by the automatic mode (Automatic mode) executed when the power is turned on at the roaming destination, the combination of PLMN and access technology has the highest priority and can be used. Allowable combinations may be selected.

A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. Network slices are sometimes referred to simply as slices.

A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be arranged. Here, NF is a processing function in the network and is adopted or defined in 3GPP. NSI is an entity of NS that consists of one or more in core network_B. Further, NSI may be composed of a virtual NF (Network Function) generated by using NST (Network Slice Template).

Here, NST is a logical expression of one or more NFs associated with a resource request for providing the required communication service and capability. In other words, the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs. In addition, NSI may be a logical network configured to separate user data delivered by services and the like. One or more NFs may be configured in NS. The NF configured in NS may or may not be a device shared with other NS.

UE and / or devices in the network are 1 or more based on NSSAI and / or S-NSSAI and / or UE usage type and / or registration information such as 1 or more NSI IDs and / or APN. Can be assigned to NS. The UE usage type is a parameter value included in the UE registration information used to identify the NSI. The UE usage type may be stored in the HSS. AMF may select SMF and UPF based on UE usage type.

In addition, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying NS. S-NSSAI may be composed of only SST (Slice / Service type), or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating the operation of NS expected in terms of functions and services. Further, SD may be information for interpolating SST when selecting one NSI from a plurality of NSIs represented by SST. The S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs. In addition, the network may store one or more S-NSSAI in the UE registration information as the default S-NSSAI. 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 related to the UE.

Further, the S-NSSAI transmitted and received between the UE and the NW may be expressed as S-NSSAI IE (Information element). Furthermore, the S-NSSAI IE transmitted and received between the UE and 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-NSSAIs stored by the UE and / or NW may be composed of SST and / or SD, and S-NSSAI composed of SST and / or SD, and / or S-NSSAI thereof. An SST and / or SD indicating the S-NSSAI of the mapped HP LMN may be configured.

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

Mapped S-NSSAI is an HPLMN S-NSSAI mapped to the registered PLMN S-NSSAI in a roaming scenario. The UE may store one or more mapped S-NSSAI mapped to the configured NSSAI and the S-NSSAI included in the allowed NSSAI of each access type. Further, the UE may store one or more mapped S-NSSAI of the first NSSAI and / or the rejected NSSAI and / or the S-NSSAI included in the pending NSSAI.

The Network Slice-Specific Authentication and Authorization (NSSAA) function is a function for realizing authentication and authorization peculiar to network slices. With network slice-specific authentication and authorization, UE authentication and authorization can be performed outside the core network such as 3rd Party. PLMN and network devices equipped with NSSAA function can execute NSSAA procedure for a certain S-NSSAI based on the registration information of UE. Further, the UE having the NSSAA function can manage, store, and transmit / receive the pending NSSAI and the third rejected NSSAI. In this paper, NSSAA may be referred to as a network slice-specific authentication and authorization procedure or an authentication and authorization procedure.

S-NSSAI that requires NSSAA is S-NSSAI that requires NSSAA, which is managed by the core network and / or the core network device. Further, the S-NSSAI requiring NSSAA may be an S-NSSAI other than HPLMN, which is managed by the core network and / or the core network device, and the S-NSSAI requiring NSSAA becomes the mapped S-NSSAI.

The core network and / or the core network device may store S-NSSAI that requires NSSAA by associating and storing information indicating whether S-NSSAI and NSSAA are required. The core network and / or the core network device further indicates that S-NSSAI that requires NSSAA and information indicating whether NSSAA is completed or not, or that NSSAA is completed, permitted, or successful. Information may be stored in association with each other. The core network and / or the core network device may manage S-NSSAI requiring NSSAA as information not related to the access network.

Also, configured NSSAI (configured NSSAI) is NSSAI supplied and stored in the UE. The UE may store the configured NSSAI for each 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. In addition, the UE may store a configured NSSAI that is not associated with the PLMN and is valid for all PLMNs, and such a configured NSSAI may be referred to as a "default configured NSSAI".

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

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

Also, requested NSSAI (requested NSSAI) is NSSAI provided from the UE to the network during the registration procedure. In the registration procedure, the S-NSSAI included in the requested NSSAI transmitted by the UE may be the allowed NSSAI stored in the UE or the S-NSSAI included in the configured NSSAI. In the PDU session establishment procedure, the S-NSSAI included in the requested NSSAI transmitted by the UE may be the S-NSSAI included in the allowed NSSAI stored in the UE.

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

Also, allowed NSSAI (permitted NSSAI) is information indicating one or more network slices in which the UE is permitted. In other words, allowed NSSAI is information that identifies the network slice that the network has allowed to connect to the UE.

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 NSSAI in association with the registration area.

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

In this paper, the 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. S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI. The allowed S-NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI.

Also, rejected NSSAI (rejected NSSAI) is information indicating one or more network slices for which the UE is not permitted. In other words, rejected NSSAI is information that identifies 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 the S-NSSAI and the reason for rejection value.

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

Furthermore, rejected NSSAI may be included in the NAS message sent from the network to the UE, such as the registration acceptance message, the setting update command, the registration refusal message, or the RRC message including the NAS message. S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI.

The rejected NSSAI may be any of the first to third rejected NSSAI, the pending NSSAI, and the first NSSAI, or may be a combination thereof. S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI. The rejected S-NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI.

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

In this paper, the rejected NSSAI associated with the PLMN may be expressed as the rejected NSSAI for the PLMN or the rejected NSSAI for the PLMN. The UE and / or NW may further store the second rejected NSSAI and / or the second rejected S-NSSAI in association with the registration area. The UE and / or NW may store the second rejected NSSAI and / or the second rejected S-NSSAI in association with the access type and / or registration area.

Here, the first rejected NSSAI is a set of one or more S-NSSAIs that are not available in the current PLMN among the S-NSSAIs included in the requested NSSAIs by the UE. The first rejected NSSAI may be a 5GS rejected NSSAI for the current PLMN, a rejected S-NSSAI for the current PLMN, or an S-NSSAI included in the rejected NSSAI for the current PLMN. There may be. The first rejected NSSAI may be a rejected NSSAI stored in the UE or NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the first rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the first rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason value. The reason for refusal value at this time may be "S-NSSAI (S-NSSAI not available in the current PLMN) which is not possible with the current PLMN or SNPN", and the S-NSSAI associated with the reason for refusal value is It may be information indicating that it is not possible with the current PLMN or SNPN. The S-NSSAI included in the first rejected NSSAI may be expressed as the first rejected S-NSSAI.

The first rejected NSSAI may be applied to the entire registered PLMN. The UE and / or NW may treat the S-NSSAI contained in the first rejected NSSAI and the first rejected NSSAI as information regardless of the access type. That is, the first rejected NSSAI may be valid information for 3GPP access and non-3GPP access.

The UE may delete the first rejected NSSAI from the memory when it transitions to the unregistered state with both 3GPP access and non-3GPP access to the current PLMN. In other words, if the UE transitions to the unregistered state with respect to the current PLMN via one access, or successfully registers with the new PLMN via one access, or registers with the new PLMN via one access. If the UE fails and transitions to the unregistered state, and the UE is not registered via the other access (unregistered state), the UE deletes the first rejected NSSAI. That is, when the UE transitions to the unregistered state for the current PLMN via one access, the UE is registered for the current PLMN via the other access (registered state). The UE does not have to delete the first rejected NSSAI.

The second rejected NSSAI is a set of one or more S-NSSAIs that are not available in the current registration area among the S-NSSAIs that the UE has included in the requested NSSAIs. The second rejected NSSAI may be a 5GS rejected NSSAI for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored in the UE or NW, or may be a rejected NSSAI transmitted from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason value. The reason for refusal value at this time may be "S-NSSAI (S-NSSAI not available in the current registration area) that is not possible in the current registration area", and the S-NSSAI associated with the reason value is It may be information indicating that it is not possible in the current registration area. The S-NSSAI included in the second rejected NSSAI may be expressed as the second rejected S-NSSAI.

The second rejected NSSAI may be valid within the current registration area and may be applied to the current registration area. The UE and / or NW may treat the S-NSSAI contained in the second rejected NSSAI and the second rejected NSSAI as information for each access type. That is, the second rejected NSSAI may be valid information for each of 3GPP access and non-3GPP access. That is, once the UE transitions to the unregistered state for a certain access, the UE may delete the second rejected NSSAI associated with the access from the memory.

The third rejected NSSAI is an S-NSSAI that requires NSSAA, and is a set of one or more S-NSSAIs for which NSSAA for that S-NSSAI has failed or has been revoked. The third rejected NSSAI may be an NSSAI stored in the UE and / or the NW, or may be an NSSAI transmitted / received between the NW and the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason for refusal value. The reason for refusal value at this time may be "S-NSSAI (S-NSSAI not available due to the failed or revoked NSSAA) which is impossible due to the failure or cancellation of NSSAA" and is associated with the reason for refusal value. It may be information indicating that NSSAA for S-NSSAI has failed or has been cancelled. The S-NSSAI included in the third rejected NSSAI may be expressed as the third rejected S-NSSAI.

The third rejected NSSAI may be applied to the entire registered PLMN, to the registered PLMN and / or EPLMN, or to all PLMNs. The fact that the third rejected NSSAI applies to all PLMNs may mean that the third rejected NSSAI is not associated with the PLMN, and that the third rejected NSSAI is associated with the HPLMN. You can do it.

Furthermore, the UE and / or NW may treat the third rejected NSSAI and the third rejected S-NSSAI as information that does not depend on the access type. That is, the third rejected NSSAI may be valid information for 3GPP access and non-3GPP access. The third rejected NSSAI may be an NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI. The third rejected NSSAI may be a 5GS rejected NSSAI for the failed or revoked NSSAA, a rejected S-NSSAI for the failed or revoked NSSAA, or a rejected NSSAI for the failed or revoked NS. It may be the included S-NSSAI.

The third rejected NSSAI is a rejected NSSAI in which the UE identifies slices rejected due to NSSAA failure or cancellation from the core network. Specifically, the UE does not start the registration request procedure for the S-NSSAI included in the third rejected NSSAI while storing the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAI received from the core network in association with the rejection reason value indicating the failure of NSSAA. The third rejected NSSAI is information that does not depend on the access type. Specifically, if the UE remembers the third rejected NSSAI, the UE attempts to send a registration request message containing the S-NSSAI contained in the third rejected NSSAI to both 3GPP and non-3GPP access. It does not have to be. Alternatively, the UE can send a registration request message including S-NSSAI included in the third rejected NSSAI based on the UE policy. Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state in which a registration request message including the S-NSSAI included in the third rejected NSSAI can be transmitted. In other words, if the UE sends a registration request message containing the S-NSSAI contained in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI. good.

The first NSSAI is information including one or more S-NSSAIs that have reached the maximum number of UEs for each network slice. The first NSSAI may be rejected NSSAI, allowed NSSAI, or pending NSSAI. The first NSSAI may be an NSSAI stored in the UE and / or the NW, or may be an NSSAI transmitted from the NW to the UE.

When the first NSSAI is sent from the NW to the UE, the first NSSAI is the S-NSSAI and the mapped S-NSSAI, the rejection reason value, the backoff timer value, and the validity period of the backoff timer value. The information may include one or a plurality of information indicating a range and information including at least one. The reason for refusal value at this time may be "S-NSSAI that has reached the maximum number of UEs for each network slice", and that the maximum number of UEs that can be allowed for S-NSSAI associated with the reason for refusal value has been reached. It may be the information to be shown. Here, the reason for refusal value may be the reason for refusal value included in rejected NSSAI, flag information, or 5 GMM cause. Further, at this time, the value of the backoff timer is the period during which the UE is prohibited from transmitting the MM message and the SM message using the corresponding S-NSSAI or S-NSSAI related to the mapped S-NSSAI. It may be information indicating.

Furthermore, the information indicating the valid period range of the backoff timer value is whether the backoff timer value is applied to the current PLMN (Public Land Mobile Network), all PLMNs, or the current registration. It may be information indicating whether the area is valid.

The first NSSAI may be applied to the entire registered PLMN, may be valid for all PLMNs, may be applied, may be valid within the registered area, and may be with the registered PLMN. It may be applied to the EPLMN, or it may be applied to one or more PLMNs to which the TAI included in the TA list (TAI list or registration area) belongs. The fact that the first NSSAI applies to all PLMNs may mean that the first NSSAI is not associated with the PLMN, or that the first NSSAI is associated with the HPLMN. ..

If the first NSSAI is valid for the entire registered PLMN, or if it applies to all PLMNs, or if it applies to the registered PLMN and / or EPLMN, then the UE and / or NW will be the first NSSAI and / or NW. The S-NSSAI included in the first NSSAI may be treated as information that does not depend on the access type. If the first NSSAI is valid within the registration area, or if it applies to one or more PLMNs to which the TAI contained in the TA list (TAI list or registration area) belongs, the UE and / or NW will be the first. The NSSAI of 1 and the S-NSSAI included in the 1st NSSAI may be treated as information for each access type.

The first NSSAI may be allowed NSSAI, rejected NSSAI, pending NSSAI, or information different from these.

Pending NSSAI is a set of one or more S-NSSAIs that the UE cannot and / or cannot use. The pending NSSAI is an S-NSSAI whose network requires network slice specific authentication, and may be a set of S-NSSAI whose network slice specific authentication has not been completed. The pending NSSAI may be a 5GS pending NSSAI. The pending NSSAI may be an NSSAI stored in the UE and / or the NW, or may be an NSSAI transmitted / received between the NW and the UE.

When the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason for refusal value. The reason for refusal value at this time may be "S-NSSAI (NSSAA is pending for the S-NSSAI)", and the S-NSSAI associated with the reason for refusal value is the S-NSSAI. It may be information indicating that the UE is prohibited or pending from use until the completion of NSSAA for NSSAI.

If the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be a set of combinations of S-NSSAI and mapped S-NSSAI.

The pending NSSAI may be applied to the entire registered PLMN, one or more EPLMNs of the registered PLMN and the registered PLMN, or all PLMNs. The fact that the pending NSSAI applies to all PLMNs may mean that the pending NSSAI is not associated with the PLMN, or that the pending NSSAI is associated with the HPLMN.

UE and / or NW may treat S-NSSAI included in pending NSSAI as information that does not depend on the access type. That is, pending NSSAI may be valid information for 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may be the first rejected NSSAI.

Pending NSSAI is an NSSAI composed of one or more S-NSSAIs in which the UE identifies the slice that is pending the procedure. Specifically, the UE does not start the registration request procedure for the S-NSSAI included in the pending NSSAI while storing the pending NSSAI. In other words, the UE will not use the S-NSSAI contained in the pending NSSAI during the registration process until the NSSAA for the S-NSSAI contained in the pending NSSAI is completed. pending NSSAI is information that does not depend on the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send the registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

The tracking area is a single or multiple range managed by the core network that can be represented by the location information of UE_A10. The tracking area may be composed of a plurality of cells. Further, the tracking area may be a range in which a control message such as paging is broadcast, or a range in which UE_A10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or the same as these. Hereinafter, the tracking area may be TA (Tracking Area). The tracking area may be identified by a TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.

The registration area (Registration area or registration area) is a set of one or more TAs assigned to the UE by AMF. Note that UE_A10 may be able to move without transmitting and receiving a signal for updating the tracking area while moving within one or a plurality of TAs included in the registration area. In other words, the registration area may be a group of information indicating an area in which UE_A10 can move without executing the tracking area update procedure. The registration area may be identified by a TAI list consisting of one or more TAIs.

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

UE ID is information for identifying the 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 IME ISV (IMEI Software Version). Alternatively, it may be TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in the application or network. Further, the UE ID may be information for identifying the user.

Management of the maximum number of UEs connected to a slice is to manage the maximum number of UEs that can be registered in the network slice or S-NSSAI at the same time. Here, the UE registered in the network slice or S-NSSAI may mean that the S-NSSAI indicating the network slice is included in the allowed NSSAI and stored. Supports the function of managing the maximum number of UEs connected to a slice The device in the network can memorize whether or not the maximum number of UEs connected to a slice needs to be managed for each S-NSSAI, and the registered UEs It can be confirmed during the registration procedure whether or not the maximum number of constants has been reached. In addition, each device that supports the function of managing the maximum number of UEs connected to a slice may be able to store the first NSSAI. In this paper, the maximum number of UEs connected to a slice may be expressed as the maximum number of UEs connected for each slice, the maximum number of UEs that can be registered in a network slice or S-NSSAI, the maximum number of UEs, or a constant. ..

The backoff timer is a timer for prohibiting the transmission of MM messages by the UE and / or the start of procedures by SM messages. The backoff timer is managed and executed by the UE. The backoff timer may be associated with S-NSSAI. The UE prohibits, restricts, or restricts the transmission of MM messages and / or the transmission of SM messages using the S-NSSAI while the backoff timer associated with the S-NSSAI is valid. It may be in the state of being done. These regulations may be regulations based on 5GS congestion management, or may be regulations including regulations based on 5GS congestion management.

The backoff timer may be a timer that is started and / or stopped in units of S-NSSAI and / or PLMN.

Specifically, the backoff timer may be associated with S-NSSAI, and may be a timer for prohibiting the transmission of MM messages and / or SM messages using a specific S-NSSAI. In other words, the UE may be configured not to send MM and / or SM messages using that particular S-NSSAI while this timer is counting.

In addition, the UE will allow the new PLMN to send MM and / or SM messages that were prohibited by the PLMN before the change, based on certain conditions described below, during the counting of this timer. It may be set. If it is expressed that the transmission of MM message and / or SM message, which was prohibited by PLMN before the change, is allowed, the same S-NSSAI and / as S-NSSAI associated with the backoff timer. Or it is permissible to send MM messages and / or SM messages using S-NSSAI related to the same S-NSSAI and / or S-NSSAI related to the same S-NSSAI mapped S-NSSAI. It may mean.

Furthermore, the backoff timer may be a timer for prohibiting the transmission of MM messages using a specific NSSAI. In other words, the UE may be configured not to send MM messages using that particular NSSAI and / or NSSAI containing a particular S-NSSAI while this timer is counting.

Furthermore, the UE may be set to allow the transmission of MM messages prohibited by the PLMN before the change in the new PLMN based on the specific conditions described later during the counting of this timer. If it is expressed that the transmission of MM messages, which was prohibited by the PLMN before the change, is allowed, the same NSSAI as the NSSAI associated with the backoff timer and / or the S associated with the backoff timer. -It may mean that the transmission of MM messages using NSSAI containing the same S-NSSAI as NSSAI is allowed. Furthermore, if it is expressed that the transmission of MM messages, which was prohibited by PLMN before the change, is allowed, NSSAI including S-NSSAI related to S-NSSAI associated with the backoff timer, and / or back. It may mean that the transmission of MM messages using NSSAI including S-NSSAI related to the mapped S-NSSAI of S-NSSAI associated with the off-timer is allowed.

Further, the backoff timer may be a timer associated with noNSSAI and prohibiting the transmission of the MM message using noNSSAI. In other words, UE_A10 may be set not to send MM messages using noNSSAI during the counting of this timer. In addition, UE_A10 may be set to allow the new PLMN to send MM messages that were prohibited by the PLMN before the change, based on certain conditions described below, during the counting of this timer. In addition, when it is expressed that the transmission of the MM message prohibited by the PLMN before the change is permitted, it may mean that the MM message using no NSSAI is permitted.

Furthermore, the backoff timer may be a 5 GMM timer and / or an EMM (EPS mobility management) timer. Further, the backoff timer may be a timer T3448 or a timer equivalent to the timer T3448. In other words, the backoff timer may be the same timer as the timer for regulating the communication of user data via the control plane, or may be the same timer.

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

The first identification information in the present embodiment includes NSSAI (S-NSSAI (s)) requested and / or permitted by UE_A10 and NSSAI (S-NSSAI (s)) requested and / or permitted by UE. With the capability information (capacity) of UE_A10 indicating that it supports the function of receiving, recognizing, processing, and storing the combined information from the network in association with the PLMN (visited PLMN; vPLMN) or EHPLMN of the visited visit. It may be there. Further, the first identification information may be UE capability information indicating whether UE_A10 supports the function.

Alternatively, the first identifying information receives and recognizes from the core network information containing one or more PLMNs (only) that UE_A10 supports only the requested and / or authorized NSSAI (S-NSSAI (s)). However, it may be UE_A10 capability information indicating that it supports the function to process. Further, the first identification information may be UE capability information indicating whether UE_A10 supports the function.

In addition, the first identifying information is a vPLMN that supports a combination of UE_A10 in the core network, UE_A10 requesting and / or allowed NSSAI and UE_A10 supporting vPLMN supporting requested and / or allowed NSSAI. Or with EHPLMN information or identification information to request core network capability information indicating that UE_A10 supports the ability to generate, process and transmit vPLMN information that supports the requested and / or authorized NSSAI. It may be there.

The combination of NSSAI (S-NSSAI (s)) and PLMNID that UE_A10 receives from the network, recognizes, and processes is the information that one PLMNID is associated with one S-NSSAI. It may be information in which multiple S-NSSAIs are associated and combined for one PLMNID, or information in which multiple PLMNIDs are associated and combined in one S-NSSAI. There may be.

The first identification information may be information indicating that UE_A10 has a function of storing an extended SOR (Steering of Roaming) transparent container information element (SOR transparent container IE), or may be information indicating that the UE_A10 has an extended allowed NSSAI. It may be information indicating that it has a function of storing.

For the second identification information in the present embodiment, the core network selects the PLMN (visited PLMN; vPLMN) of the UE_A10 visit that supports the NSSAI (S-NSSAI (s)) requested and / or permitted by the UE_A10. In addition, it may be the capability information of the core network indicating that it supports the function of transmitting the selected PLMN information (PLMN ID) to UE_A10. Further, the second identification information may be the capability information of the core network indicating whether or not the core network supports the above function.

Here, the PLMN information transmitted by the core network to the UE_A10 may be the information combined with the NSSAI requested by the core network and / or permitted from the core network, or may be the PLMN information selected as described above. It may be only information (PLMN ID).

Furthermore, when the core network sends PLMN information as combined information in association with NSSAI (slice information), it may be information in which one S-NSSAI is associated with one PLMN ID and combined, or 1 The information may be a combination of a plurality of S-NSSAIs associated with one PLMNID, or may be a combination of a plurality of PLMNIDs associated with a single S-NSSAI.

The third identification information in the present embodiment is the information (PLMN ID) that UE_A10 identifies one or more PLMNs (vPLMN (s)) that can be used as the destination network, and each PLMN supports it. The information may be a combination of NSSAI (S-NSSAI (s)) in association with each other, and may be information including a plurality of such combined information.

The combination of PLMN ID and NSSAI may be information in which one S-NSSAI is associated with one PLMN ID and combined, or a plurality of S-NSSAI are associated and combined with one PLMN ID. It may be the information that has been created, or it may be the information that one S-NSSAI is associated with and combined with a plurality of PLMN IDs.

Here, the PLMN information (PLMN ID) included in the third identification information is selected by the core network based on the S-NSSAI requested and / or permitted by UE_A10 in the home network (home PLMN; hPLMN). It may be one or more PLMN IDs.

Further, the third identification information is composed of one or a plurality of combinations in which information indicating access technology (access technology; PLMN Access Technology Identifier) is further associated in addition to the association between PLMN ID and S-NSSAI. Information may be included.

For example, the third identification information may be an information element that is an extension of the SOR (Steering of Roaming) transparent container information element (SOR transparent container IE), or may be information that is an extension of allowed NSSAI. Here, for example, the extended SOR transparent container information element is a combination of PLMN ID and access technology in the list of preferred PLMN / access technology combinations included in the SOR transparent container information element. In addition, NSSAI (S-NSSAI (s)) supported by each PLMN may be added to the combination. Also, for example, the extended allowed NSSAI adds one or more PLMN IDs that support each S-NSSAI in addition to the combination of multiple S-NSSAI and mapped S-NSSAI included in the allowed NSSAI. It may be composed of the above combinations and include other information.

Here, if UE_A10 does not show the ability to recognize the third identification information based on the second identification information, the core network should send the third identification information to the UE_A10. Instead, you may send the unextended SOR transparent container IE or the unextended allowed S-NSSAI.

The third identification information may be composed of an S-NSSAI (for example, allowed S-NSSAI) permitted by the core network to the UE and a list of one or more PLMNs associated with the S-NSSAI. Here, the core network may be PLMN.

The fourth identification information in the present embodiment may be identification information in which UE_A10 is composed of information (PLMN ID) for identifying one or more networks (vPLMN) that can be used as a destination network.

Here, the PLMN information (PLMN ID) included in the fourth identification information is selected by the core network based on the S-NSSAI requested and / or permitted by UE_A10 in the home network (home PLMN; hPLMN). It may be one or more PLMN IDs.

Further, the fourth identification information may be one or a plurality of combinations in which the PLMN ID and the information indicating the access technology (access technology; PLMN Access Technology Identifier) are associated with each other.

For example, the fourth identification information may be SOR transparent container IE, and for the information element, UE_A10 supports NSSAI (S-NSSAI (s)) requested and / or permitted to the network, and the core. It may contain one or more PLMNs (s) selected by the network.

Furthermore, the fourth identification information may be an information element that is an extension of the SOR transparent container information element (SOR transparent container IE), or may be information that is an extension of allowed NSSAI. Here, for example, the extended SOR transparent container information element is a combination of PLMN ID and access technology in the list of preferred PLMN / access technology combinations included in the SOR transparent container information element. In addition, NSSAI (S-NSSAI (s)) supported by each PLMN may be added to the combination. Also, for example, the extended allowed NSSAI adds one or more PLMN IDs that support each S-NSSAI in addition to the combination of multiple S-NSSAI and mapped S-NSSAI included in the allowed NSSAI. It may be composed of the above combinations and include other information.

Here, if UE_A10 does not show the ability to recognize the third identification information based on the second identification information, the core network should send the third identification information to the UE_A10. Instead, you may send a conventional SOR transparent container IE that does not consider PLMN's S-NSSAI support.

[3. First Embodiment]
[3.1. Explanation of procedures used in each embodiment]
Next, the procedure used in each embodiment will be described. The procedure used in each embodiment includes a registration procedure (Registration procedure), a UE configuration update procedure (Generic UE configuration update procedure), and PLMN selection. Each procedure will be explained below.

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

[3.2. Registration procedure]
First, the registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering with the access network_B and / or the core network_B and / or the DN. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (5GMM-DEREGISTERED state). In addition, each device (particularly UE and AMF) can transition to the registration state (5GMM-REGISTEDED 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 registered status (registered or unregistered status) for 3GPP access and the registered status for non-3GPP access.

In addition, the registration procedure is to update the UE location registration information in the network and / or to periodically notify the network of the UE status from the UE and / or to update certain parameters about the UE in the network. It may be the procedure of.

The UE may start the registration procedure when it has mobility across the TA (tracking area). In other words, the UE may start the registration procedure when it moves to a TA different from the TA indicated in the held TA list (TAI list or registration area). In addition, the UE may initiate this procedure when the running backoff timer, or other timer, has expired. In addition, the UE may initiate the registration process when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. In addition, the UE may initiate the registration process if there is a change in the ability information and / or preferences regarding the establishment of the UE's PDU session. In addition, the UE may initiate the registration process on a regular basis. In addition, the UE may be based on the completion of the UE configuration update procedure, or on the basis of the completion of the registration procedure, or on the basis of the completion of the PDU session establishment procedure, or on the basis of the completion of the PDU session management procedure, or in each procedure. The registration procedure may be initiated based on the information received from the network or based on the expiration or suspension of the backoff timer. The UE is not limited to these, and can execute the registration procedure at any timing.

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 defined as an initial registration procedure or a registration procedure for initial registration. Well, the registration procedure executed while the UE is registered in the network can be changed to the registration procedure (registration procedure for mobility and periodic registration update) or the transfer and regular registration procedure (registration procedure for mobility and periodic registration update). Mobility and periodic registration procedure) may be used.

The UE may execute the PLMN selection before the registration procedure or in the initial state of the registration procedure, and select and determine the PLMN required by the UE.

The new AMF141 in Fig. 6 indicates the AMF in which UE_A10 was registered by this procedure, and the old AMF142 means the AMF in which the UE was registered by the procedure prior to this procedure. If no change in AMF occurs in this procedure, the interface between old AMF142 and new AMF141 and the procedure between old AMF142 and new AMF141 do not occur, and new AMF141 may be the same device as old AMF142. In the present embodiment, when AMF is described, it may mean new AMF141, old AMF142, or both. Note that new AMF141 and old AMF142 may be AMF140.

First, UE_A10 starts the registration procedure by sending a registration request message to new AMF141 (S600) (S602) (S604). Specifically, the UE sends an RRC message including a registration request message to 5G AN120 (or gNB) (S600). The registration request message is a NAS message sent and received on the N1 interface. The RRC message may be a control message sent and received between the UE and 5G AN120 (or gNB). In addition, NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. The NAS layer is a higher layer than the RRC layer.

Here, UE_A10 can send the first identification information by including it in the registration request message and / or the RRC message. In addition, UE_A10 may send the registration request message and / or the RRC message with identification information indicating the type of this procedure. Here, the identification information indicating the type of this procedure may be 5GS registration type IE, and this procedure is for initial registration, for updating registration information due to movement, or for periodical update of registration information. Alternatively, it may be information indicating that the registration procedure is for emergency registration.

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

UE_A10 may send this identification information by including it in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer). Note that UE_A10 may indicate that UE_A10 supports each function by transmitting these identification information, may indicate a request of the UE, or may indicate both of them. .. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.

In addition, UE_A10 determines whether or not to transmit the first identification information to the network, the ability information of the UE and / or the UE policy, and / or the state of the UE, and / or the registration information of the user, and / or the UE. It may be selected and decided based on the context held by.

UE_A10 identifies and processes the combination information of PLMN ID and NSSAI (S-NSSAI) supported by PLMN contained in the third identification information and / or the fourth identification information used for PLMN selection after movement. The first identification information may be included in the registration request message and transmitted when the function for the above is provided. By transmitting the first identification information, UE_A10 processes the combination information of PLMN ID and NSSAI (S-NSSAI) supported by PLMN contained in the third identification information and / or the fourth identification information. It may be shown to the network that it has a function for the purpose.

Furthermore, UE_A10 may indicate that the first identification information is included in the registration request message and transmitted to request the network capability information indicating that the network supports the function corresponding to the first identification information. ..

In addition, UE_A10 retains the ability to support the function indicated by the first identification information, and UE_A10 is included in the NSSAI (requested NSSAI) requested to be used in the PLMN (HPLMN) registered by this procedure. It is assumed that one or more S-NSSAI will be used in VPLMN or EHPMN to register and connect after UE mobility occurs, and even if the first identification information is included in the registration request message when requested, it will be added to the network. You may send it.

UE_A10 may include other than the first identification information in the registration request message and / or the RRC message including the registration request message, for example, UEID and / or PLMNID and / or AMF identification information and / or requested NSSAI. May be included in the transmission.

Here, the AMF identification information may be information for identifying AMF or a set of AMF, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) or GUAMI (Globally Unique AMF Identifier). You can.

When UE_A10 stores "allowed NSSAI associated with the PLMN requested by the UE and the access type requested by the UE" and / or when "configured NSSAI for the requested PLMN" is stored. , And / or when storing the "default configured NSSAI", the UE may include the requested NSSAI in the registration request message and send it to the requesting PLMN.

Or, when the UE remembers "the allowed NSSAI associated with the PLMN different from the PLMN requested by the UE and the access type requested by the UE", the allowed NSSAI or the S-NSSAI included in the allowed NSSAI. However, if it is further associated with the requesting PLMN, UE_A10 may include the requested NSSAI in the registration request message and send it to the requesting PLMN.

Here, when the allowed NSSAI associated with the PLMN different from the PLMN requested by the UE or the S-NSSAI included in the allowed NSSAI is associated with the requested PLMN, for example, UE_A10 has a plurality of allowed NSSAIs. It may mean that it is stored in association with the PLMN (requested PLMN and other PLMN).

Alternatively, if the allowed NSSAI associated with a PLMN different from the PLMN requested by the UE or the S-NSSAI contained in the allowed NSSAI is associated with the PLMN requested, the PLMN is different from the PLMN required by the UE. When the UE stores the allowed NSSAI associated with or the S-NSSAI included in the allowed NSSAI and the PLMN list that supports the S-NSSAI, and the PLMN list contains the PLMN required by the UE. It may be.

In addition, UE_A10 may include the S-NSSAI included in the allowed NSSAI associated with the PLMN different from the PLMN requested by the UE in the requested NSSAI.

Alternatively, UE_A10 may include the mapped S-NSSAI of S-NSSAI included in the allowed NSSAI associated with the PLMN different from the PLMN requested by the UE in the Requested mapped NSSAI of 5GS.

Alternatively, UE_A10 may include the S-NSSAI included in the allowed NSSAI associated with the HPLMN in the 5GS Requested mapped NSSAI and send it to the network in the registration request procedure for the VPLMN.

In addition, UE_A10 can be sent by including the SM message (for example, PDU session establishment request message) in the registration request message, or by sending the SM message (for example, PDU session establishment request message) together with the registration request message. The PDU session establishment procedure may be started during the registration procedure.

When 5G AN120 (or gNB) receives an RRC message including a registration request message, it selects the AMF to which the registration request message is transferred (S602). The 5G AN120 (or gNB) can select AMF based on one or more identification information contained in the registration request message and / or the RRC message including the registration request message. Specifically, 5GAN (or gNB) may select new AMF141 to which the registration request message is sent based on the first identification information.

For example, 5G AN120 (or gNB) may select an AMF that supports a function corresponding to the ability information indicated by the first identification information based on the first identification information. Specifically, the 5GAN (or gNB) corresponds to the UE capability information indicated by the first identification information, and is included in the third identification information and / or the fourth identification information, PLMNID and /. Alternatively, an AMF having a function for generating and transmitting information combining PLMN's access technology and PLMN-supported NSSAI (S-NSSAI) may be selected.

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

When the new AMF141 receives the registration request message, it can execute the first condition determination. The first conditional determination is for determining whether or not the network (or new AMF141) accepts the UE request. new AMF141 executes the procedure from S606 to S612 when the first condition determination is true. On the other hand, new AMF141 may execute the procedure of S610 without executing the procedure of S606 to S608 when the first condition determination is false.

Alternatively, the new AMF141 may request the UE context from the old AMF142 and determine the first condition after receiving the UE context from the old AMF142 (S606, S608). In that case, new AMF141 may execute S610 and / or S612 if the first condition determination is true. On the other hand, new AMF141 may execute S610 when the first condition determination is false.

Here, when the first condition determination is true, the control message transmitted and received by the S610 may be a registration acceptance message, and when the first condition determination is false, the control message may be a registration acceptance message. The control message transmitted and received by the S610 may be a Registration reject message.

The first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF.

For example, if the network permits the UE request, the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be false.

Also, if the S-NSSAI included in the requested NSSAI received by the AMF is the information that identifies the slice that requires the NSSAA procedure, the result of the NSSAA procedure of the S-NSSAI that the AMF corresponds to the UE is successful. The first condition determination may be true if it is remembered to be. Alternatively, if there is no S-NSSAI allowed for the UE and there is no plan to assign allowed NSSAI to the UE in the future, the first condition determination may be false.

Also, if the S-NSSAI included in the requested NSSAI received from the UE by AMF is the information that identifies the slice that requires management of the maximum number of UEs to connect to the slice, and if the maximum number of UEs has not been reached, the first The condition determination may be true. Alternatively, even if there is no S-NSSAI allowed for the UE, the first condition determination may be true if it can be expected that the allowed NSSAI will be assigned to the UE in the future.

In AMF, when there is no S-NSSAI allowed in the UE and the first NSSAI is assigned to the UE, the first condition determination may be true or false.

If the AMF indicated in the AMF identification information included in the message received from the UE by the new AMF141 is the old AMF142, the new AMF141 executes the procedures of S606 and S608, and the new AMF141 is included in the message received from the UE_A10. If the AMF shown in the identification information is new AMF141, the procedure of S606 and S608 is not executed. In other words, if an AMF change occurs due to this procedure, the procedures for S606 and S608 will be executed, and if no change for AMF occurs, the procedures for S606 and S608 will be skipped.

The UE context transfer procedure (S606, S608) will be explained. new AMF141 sends a UE context request message to old AMF142 (S606). The old AMF142 sends the UE context to the new AMF141 based on the received UE context request message. new AMF141 creates a UE context based on the received UE context.

Here, the UE context sent from new AMF141 to old AMF142 may include UEID and allowed NSSAI. Further, the UE context may include configured NSSAI and / or rejected NSSAI, NSSAI and / or pending NSSAI, and / or a first NSSAI. Also, allowed NSSAI and / or configured NSSAI and / or rejected NSSAI and / or pending NSSAI and / or first NSSAI included in the UE context, and S-NSSAI included in each NSSAI are to the UE. Information on whether or not the notification has been completed may be linked.

Also, in the UE context, information on S-NSSAI that requires NSSAA procedure, and / or information indicating that the NSSAA procedure has been completed for the UE, that authentication has succeeded, and / or that authentication has failed. May be included.

Also, in the UE context, the information of S-NSSAI that requires management of the maximum number of UEs connected to the slice, and / or the information indicating that the maximum number of UEs has been reached, and / or the maximum number of UEs connected to the slice have been reached. Information indicating whether or not it may be included.

Information on the characteristics of these S-NSSAIs may be managed as one piece of information. Specifically, whether or not the network requires NSSAA for each S-NSSAI and whether or not NSSAA is successful. , Information indicating whether or not the maximum number of UEs connected to the slice needs to be managed and whether or not the maximum number of UEs connected to the slice has been reached may be stored in association with each other.

The new AMF141 may send a control message to the UE based on the determination of the first condition determination and / or based on the reception of the UE context from the old AMF142 (S610). The control message may be a registration acceptance message or a registration refusal message. The case where the control message sent to the UE is the registration acceptance message will be described below.

The new AMF141 may send the control message including at least one or more identification information out of the second to fourth identification information. Note that the new AMF141 may indicate that the network supports each function by transmitting these identification information and / or control messages, or may indicate that the UE request has been accepted. It may indicate that it does not allow or support the request from the UE, or it may indicate information that combines these. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.

Here, the second identification information may be the ability information indicating that the new AMF141 and / or the core network supports the function corresponding to the ability information indicated by the first identification information received from the UE.

The new AMF141 also indicates that the new AMF141 and / or the core network has the capabilities indicated by the second identification by including the third and / or fourth identification in the registration acceptance message. May be good. In other words, new AMF141 does not have to include the second identification information if it includes the third and / or 4 identification information in the registration acceptance message.

Furthermore, new AMF141 must not transmit the 3rd and / or 4th identification information if it does not receive the 1st identification information from the UE. In other words, if the new AMF141 does not receive the first identification information from the UE, the third and / or fourth identification information may be prohibited.

When the new AMF141 receives the first identification information from the UE, it may send at least one of the second to fourth identification information by including it in the control message.

Further, the new AMF141 may transmit at least one of the third identification information and / or the identification information of 4 when the setting information of the UE is updated.

The new AMF141 may further include the configured NSSAI and / or allowed NSSAI, and / or rejected NSSAI, and / or pending NSSAI, and / or the first NSSAI in the control message and transmit it to UE_A10.

new AMF141 does not allow S-NSSAI (allowed NSSAI) to the UE when sending a control message, but if there is a plan to execute the NSSAA procedure after the completion of this procedure or in parallel with this procedure, or with the UE If the NSSAA procedure is being executed between networks, or if the pending NSSAI is included in the control message and sent, an empty value may be included in the allowed NSSAI and sent.

new AMF141 does not allow S-NSSAI (allowed NSSAI) to UE when sending a control message, but when including the 10th identification information in the control message, and before this procedure, the 1st NSSAI is sent to UE. If notified, an empty value may be included in allowed NSSAI and sent.

When the 13th identification information indicating that the new AMF141 is applied to all PLMNs is included in the control message, the 15th identification information may be included in the control message together.

UE_A10 receives a control message and / or one or more of the 10th to 15th identification information from the network. More specifically, the UE receives a control message and / or one or more of the 10th to 15th identification information from new AMF141.

UE_A10 may recognize the received information based on the reception of at least one of the 10th to 15th identification information. Specifically, UE_A10 has reached the maximum number of UEs to be connected per slice, so that S-NSSAI indicated by the tenth identification information and / or S-NSSAI indicated by the fourteenth identification information, and / Alternatively, it may be recognized that the transmission of the MM message using the S-NSSAI related to the mapped S-NSSAI indicated by the fifteenth identification information and / or the transmission of the SM message is temporarily prohibited. .. Here, the MM procedure may be a registration request message, and the SM message may be a PDU session establishment request message.

UE_A10 may perform the following operations based on the reception of at least one or more of the identification information 2 to 4 and / or the reception of the control message.

UE_A10 recognizes that by receiving one or more of the second to fourth identification information, the network supports the function corresponding to the UE capability information indicated by the first identification information. You may.

When UE_A10 receives the third identification information and / or the fourth identification information without receiving the second identification information, the third identification information and / or the fourth identification information is extended. It may be recognized, stored, and processed as an unextended SOR transparent container information element or an unextended allowed NSSAI.

When UE_A10 receives the third identification information and / or the fourth identification information, UE_A10 may store or update these. For example, if this procedure is an initial registration procedure, or if the UE does not store or retain the third and / or fourth identification information, they may be stored. Also, for example, if this procedure is a registration procedure for renewal, or the UE has already received or stored or preconfigured the information contained in the third identification information and / or the fourth identification information. If it is retained, it may be updated by overwriting or adding it with the third identification information and / or the fourth identification information newly received by this procedure.

Specifically, when the third identification information is an extended SOR transparent container information element, UE_A10 obtains one or more pieces of information shown in the third identification information based on the reception of the third identification information. Remember. Furthermore, if UE_A10 already remembers the extended SOR transparent container information element or the unextended SOR transparent container information element, the old SOR transparent container information element may be deleted.

Alternatively, if the third identification information is an extended allowed NSSAI, UE_A10 stores one or more pieces of information shown in the third identification information based on the reception of the third identification information. Specifically, UE_A10 may update allowed NSSAI based on the reception of the third identification information. Furthermore, if UE_A10 already remembers allowed NSSAI, the old allowed NSSAI may be deleted.

More specifically, when the third identification information is an extended allowed NSSAI, UE_A10 is the S-NSSAI included in the allowed NSSAI shown in the third identification information based on the reception of the third identification information. May be stored in association with the current PLMN and access type. Further, UE_A10 may store the S-NSSAI included in the allowed NSSAI in association with the supported PLMN list.

When the fourth identification information is the SOR transparent container information element, UE_A10 may store the received SOR transparent container information element based on the reception of the fourth identification information. When the fourth identification information is allowed NSSAI, UE_A10 may store the received allowed NSSAI based on the reception of the fourth identification information.

Here, for example, the third identification information and / or the fourth identification information is the SOR transparent container information element of the AMF or UDM or SOR-AF or other core network device that received the first identification information from the UE. Based on, the UE may be new information generated by associating each PLMN that supports S-NSSAI (s) included in the permitted NSSAI (allowed NSSAI), or SOR transparent container information. The information may be generated by expanding or changing the element. Specifically, this association is made in addition to the association between the PLMN ID recorded in the PLMN ID and access technology list (list of preferred PLMN / access technology combinations) included in the SOR transparent container information element, and the PLMN ID. A SOR transparent container information element that has one or more S-NSSAIs included in the allowed NSSAI or allowed NSSAI that are supported for each, and one or more NSSAIs that are allowed PLMN ID, access technology, and UE as a set of information. Alternatively, it may be configured as an extended list of PLMN ID and access technology lists (list of preferred PLMN / access technology combinations).

Further, for example, the third identification information and / or the fourth identification information is for each S-NSSAI in which the AMF or UDM or other core network device that has received the first identification information from the UE is included in the allowed NSSAI. , It may be new information generated by associating with the PLMN ID of one or more VPLMNs that support S-NSSAI, or it may be information generated by extending or changing allowed NSSAI. .. Specifically, in addition to the association between S-NSSAI and mapped S-NSSAI, it may be configured as an extended list of allowed NSSAI with PLMN IDs supporting these S-NSSAI as one set of information.

Further, for example, when the third identification information is included in the registration acceptance message, the AMF may not include the allowed NSSAI, and may include the third identification information instead of the allowed NSSAI. In other words, the UE that receives the third identification information recognizes that the third identification information is information including allowed NSAAI, and uses the information included in the third identification information as allowed NSSAI in the subsequent various processes. You may.

In addition, AMF determines which identification information to be included in the control message among the second to fourth identification information, each received identification information and / or subscriber information, and / or network capability information, and / or. Selections and decisions may be made based on operator policy and / or network status and / or user registration information and / or context held by AMF.

Also, if the control message is a registration acceptance message, the AMF either sends the registration acceptance message with the SM message (eg, PDU session establishment acceptance message), or sends the SM message along with the registration acceptance message (eg, PDU session establishment). Acceptance message) can be sent. However, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included in the registration request message. Further, this transmission method may be executed when an SM message (for example, a PDU session establishment request message) is transmitted together with the registration request message. By performing such a transmission method, AMF can indicate that the procedure for SM has been accepted in the registration procedure.

In addition, AMF also 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 It may be shown that the UE request has been accepted by sending the registration acceptance message based on the context held by the AMF, or the UE request has been rejected by sending the registration refusal message. May be indicated.

The UE receives the control message via 5GAN (gNB) (S608). When the control message is a registration acceptance message, the UE recognizes that the UE request by the registration request message has been accepted and the contents of various identification information contained in the registration acceptance message by receiving the registration acceptance message. can do. Alternatively, when the control message is a registration refusal message, the UE receives the registration refusal message, so that the UE's request by the registration request message is rejected, and the contents of various identification information included in the registration refusal message. Can be recognized. Further, the UE may recognize that the request of the UE has been rejected if the control message is not received even after a predetermined period of time has elapsed after transmitting the registration request message.

The UE can further send a registration completion message to AMF via 5GAN (gNB) as a response message to the registration acceptance message when the control message is a registration acceptance message (S610). When the UE receives an SM message such as a PDU session establishment acceptance message, the UE may send the registration completion message including the SM message such as the PDU session establishment completion message, or by including the SM message. , May indicate that the procedure for SM has been completed. Here, the registration completion message is a NAS message sent and received on the N1 interface, but is included in the RRC message and sent and received between the UE and 5GAN (gNB).

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

Alternatively, each device may complete the registration procedure based on the transmission and reception of the registration refusal message.

In addition, each device may transition or maintain the state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission / reception of the registration acceptance message and / or the registration completion message. , Transition or maintenance to the state where the UE is not registered in the network (RM_DEREGISTERED state, or 5GMM-DEREGISTERED state) on the access that received the registration refusal message to the current PLMN based on the transmission and reception of the registration refusal message. You may. Further, the transition of each device to each state may be performed based on the transmission / reception of the registration completion message or the completion of the registration procedure.

Furthermore, each device may perform processing based on the information sent and received in the registration procedure based on the completion of the registration procedure. For example, when sending and receiving information indicating that a part of the UE's request has been rejected, the reason why the UE's request has been rejected may be recognized. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network_A or another cell.

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

Furthermore, the UE may delete one or more NSSAIs to be stored based on the completion of the registration procedure. Specifically, UE_A10 is the first to remember when UE_A10 transitions to the unregistered state on both accesses (3GPP access and non-3GPP access) to the current PLMN based on the completion of this procedure. The rejected NSSAI and / or the third rejected NSSAI and / or the first NSSAI may be deleted.

Furthermore, UE_A10 will be registered in the new registration area when UE_A10 transitions to the unregistered state on certain access (3GPP access and non-3GPP access) to the current PLMN based on the completion of this procedure. If successful, or if UE_A10 transitions to an unregistered or registered state on a given access as a result of performing a registration procedure in a new registration area, UE_A10 will have the current PLMN and the current registration area, and / Alternatively, the access type and the second rejected NSSAI associated with it may be deleted.

Furthermore, each device may start the registration procedure again based on the expiration or stop of the backoff timer.

Furthermore, each device may start the registration procedure again based on the update of the stored NSSAI.

Furthermore, each device may start the SM procedure by sending and receiving SM messages based on the transition or maintenance of the UE registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state).

[3.3. Update procedure]
Next, the renewal procedure will be described. In this chapter, the renewal procedure is also referred to as this procedure.

The update procedure updates the information (list of preferred PLMN / access technology combinations) stored by UE_A10 based on the third identification information and / or the fourth identification information received by UE_A10 in the registration procedure in Chapter 3.2. It may be a network-led or UE-led procedure for doing so. Specifically, registration procedures for renewal of registration at regular or arbitrary timings, and / or UE configuration update procedures, and / or network-led NAS transport procedures, and / Alternatively, it may be a UE-led NAS transport procedure.

In this procedure by the registration procedure, in the procedure described in Chapter 3.2, the UE_A10 receives the new third identification information and / or the fourth identification information from the core network, and the UE_A10 has already received and stored the third identification information. It may be a procedure for updating the identification information and / or the information based on the fourth identification information (list of preferred PLMN / access technology combinations).

In this procedure by network-led or UE-led NAS transport procedure, the update of the third identification information and / or the fourth identification information is performed by the core network in the DL NAS transport message of the third identification information and / or the fourth identification information. Information based on the third identification information and / or the fourth identification information (list of preferred PLMN / access technology) that is transmitted to UE_A10 including the identification information and received by UE_A10 that has already been received and stored. It may be a procedure to update combinations).

The method of updating the third identification information and / or the fourth identification information based on the reception of the third identification information and / or the fourth identification information by the UE may be the same as the registration procedure.

Here, the UE-led NAS transport procedure may be a procedure for the UE to provide each information to the core network. The information provided may include a transparent container information element. Further, the transparent container information element may be an extended transparent container information element.

Furthermore, the UE-led NAS transport procedure may be a procedure initiated by the UE sending a ULNAS transport message to the AMF. Further, the UE-led NAS transport procedure may be a procedure that is triggered by a change in the state of the UE, a change in the setting of the UE, or the like. Further, the UE-led NAS transport procedure may be a procedure started by an instruction from a higher layer.

Furthermore, the network-led NAS transport procedure may be a procedure for the core network to provide each information to the UE. The information provided may include a transparent container information element. Further, the transparent container information element may be an extended transparent container information element.

Furthermore, the network-driven NAS transport procedure may be a procedure started by AMF sending a DLNAS transport message to the UE. Further, the network-driven NAS transport procedure may be a procedure started based on the reception of the ULNAS transport message. Conversely, the network-driven NAS transport procedure may be a procedure that is started based on a trigger other than the reception of the ULNAS transport message. For example, the network-led NAS transport procedure may be a procedure that is triggered by a change in network status, a change in network settings, or the like.

This procedure by the UE setting update procedure will be explained in the next section 3.3.1.

[3.3.1. UE setting update procedure]
Next, the UE configuration update procedure will be described with reference to FIG. 7. Hereinafter, the UE setting update procedure is also referred to as this procedure. This procedure is a procedure for updating the UE setting information under the initiative of the core network. This procedure may be a procedure for mobility management that the network takes the initiative to execute for the UE registered in the network.

Furthermore, devices in the core network such as AMF may start this procedure based on the update of network settings and / or the update of operator policy. The trigger of this procedure may be the detection of the mobility of the UE, the detection of the state change of the UE and / or the access network and / or the core network, or the state change of the network slice. It may be. Further, the trigger of this procedure may be the reception of a request from the DN and / or the application server of the DN, a change in network settings, or a change in operator policy. .. Further, the trigger of this procedure may be the expiration of the timer being executed. The triggers for the devices in the core network to start this procedure are not limited to these. In other words, this procedure may be executed at any time after the above-mentioned registration procedure and / or PDU session establishment procedure is completed. Further, this procedure may be executed at any timing as long as each device has established a 5GMM context and / or each device is in the 5GMM connection mode.

In addition, each device sends and receives a message containing identification information for changing the setting information of the UE and / or identification information for stopping or changing the function executed by the UE during this procedure. May be good. Further, each device may update the setting information to the setting instructed by the network based on the completion of this procedure, or may start the behavior instructed by the network.

The UE may update the setting information of the UE based on the control information transmitted and received by this procedure. Further, the UE may stop the function being executed or start a new function as the setting information of the UE is updated. In other words, the device in the core network leads this procedure, and further, by transmitting the control message and control information of this procedure to the UE, the UE setting information that can be identified by using these control information can be obtained. , UE may update. Further, the device in the core network may stop the function executed by the UE by updating the setting information of the UE, or may cause the UE to start a new function.

First, AMF140 starts the UE setting update procedure by sending a configuration update command message to UE_A10 via 5G AN120 (or gNB) (S700).

The AMF140 may send the setting update command message including the third identification information and / or the fourth identification information. Here, the third identification information and / or the fourth identification information included in the setting update command message is included in the registration acceptance message in the registration procedure described in Chapter 3.2 by the UE, and is received and stored from the AMF. It may be a new value that updates the identification information and / or the fourth identification information of.

If the AMF140 has not received the registration request message containing the first identification information from the UE in the registration procedure described in Chapter 3.2, the third identification information and / or the fourth identification in this procedure. Do not send information.

In addition, the AMF140 also includes each identification information received, and / or subscriber information, and / or network capability information, and whether to include the third identification information and / or the fourth identification information in the setting update command message. It may be selected and determined based on / or the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the AMF140.

In addition, AMF140 also 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. A request for updating the setting information of UE_A10 may be indicated by sending a setting update command message based on the context held by the AMF140.

The UE may update the third identification information and / or the fourth identification information stored in the UE based on the third identification information and / or the fourth identification information. The method of updating the third identification information and / or the fourth identification information based on the reception of the third identification information and / or the fourth identification information by the UE may be the same as the registration procedure.

Further, the UE sends a configuration update complete message to the AMF140 via 5GAN (gNB) as a response message to the configuration update command message based on the identification information contained in the configuration update command message. May (S702).

When UE_A10 sends a setting update completion command message, AMF140 receives a setting update completion message via 5GAN (gNB) (S702). In addition, each device completes this procedure based on the transmission / reception of the setting update command message and / or the setting update completion message.

Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, when the update information for the setting information is transmitted and received, each device may update the setting information. Furthermore, when sending and receiving information indicating that the registration procedure needs to be performed, UE_A10 may start the registration procedure based on the completion of this procedure.

Further, UE_A10 may store the third identification information and / or the fourth identification information received together with the setting information command message based on the completion of this procedure, and may recognize the network decision. .. In addition, the UE may execute each procedure based on the stored information based on the completion of this procedure.

In the above procedure, by sending and receiving the setting update command message, the device in the core network can instruct the UE to update the setting information already stored or applied by the UE, and the UE executes the command. You can instruct to stop or change the function you are using.

[3.4. PLMN selection]
Next, the process related to PLMN selection will be described.

PLMN selection is when UE_A10 needs to switch from the currently registered and / or connected PLMN (here HPLMN) to another PLMN (VPLMN) due to movement (mobility), or in an area other than HPLMN. It may be a process executed by the UE when the power is turned on.

Also, the PLMN selection may be based on the third and / or fourth identification information received and stored by the UE_A10 in the registration and / or renewal procedures, and the identification used by the UE_A10 in the HPLMN. It may be a UE process that selects a combination of PLMN (VPLMN) ID and / or access technology that supports S-NSSAI and / or NSSAI (S-NSSAI (s)) that supports PLMN.

Here, for example, when the third identification information is an extended SOR transparent container information element, the PLMN selection may be executed in the automatic mode (Automatic mode), which is automatically performed, or can be used as indicated by UE_A10. It may be executed in the manual mode (Manual mode) manually performed by the user based on the PLMN. Here, PLMN selection by Automatic mode is used in the registration procedure to be executed next by selecting the combination with the highest priority from the combination of PLMN ID and access technology and / or NSSAI (1 or more S-NSSAI). You may. Here, the priority may be the order in which the combination of PLMN and access technology and / or NSSAI (one or more S-NSSAI) is stored, and the first stored PLMN ID and access technology and / or The PLMN ID included in the combination of NSSAI (1 or more S-NSSAI) may have the highest priority.

Also, for example, when the third identification information is an extended allowed NSSAI, the PLMN selection is based on the S-NSSAI that establishes a PDU session after the UE executes the registration procedure based on the PLMN selection. It may be the processing of the UE that selects.

Also, the PLMN selection executed when the power is turned on in an area other than the HPLMN is included in the third identification information and / or the fourth identification information and / or these that the UE has already received and stored. It may be executed based on the information obtained.

Here, when the PLMN ID supporting one or more S-NSSAIs used by the UE connected by HPLMN is not included in the third identification information and / or the fourth identification information. , The UE may select the highest priority PLMN ID from the third identification information and / or the fourth identification information, and execute the registration procedure based on the selected PLMN ID. The registration procedure may be executed based on NSSAI (allowed NSSAI) permitted by networks other than the above without selecting the PLMN ID, and the operation of the UE is not limited to these.

Further, the UE after executing the PLMN selection may execute the registration procedure to the PLMN of the connection destination selected and determined based on the PLMN selection. Here, this registration procedure may be a registration procedure executed by mobility or an initial registration procedure.

[4. Embodiment in one aspect of the present invention]
An embodiment of one aspect of the invention may be a combination of one or more procedures described in Chapter 3. For example, in the present embodiment, as shown in FIG. 8, after the registration procedure (S800) described in Chapter 3 is completed, the network or UE-led update procedure (S802) may or may not be executed. You may.

Here, the renewal procedure may be started at any time by the UE or the network, may be executed based on a setting or policy change in the UE or the network, or the UE subscription information or the UE subscription information stored by the network. , May be implemented based on changes in roaming agreements with other networks (PLMN), or slice support for other networks.

Based on the completion of these procedures (S800 and / or S802), each device in the UE and / or core network may transition to the first state (S804).

Here, in the first state (S804), the UE_A10 and each core network device may be in the registration state (RM-REGISTERED state), and / or in the registration procedure (S800) and / or the renewal procedure (S804). , UE_A10 may be in a state of receiving and storing the third identification information and / or the fourth identification information. Further, the first state (S804) may be a state in which UE_A10 has received the second identification information.

The third identification information may be an extended SOR transparent container information element and / or an extended allowed NSSAI, and is based on the first identification information transmitted by UE_A10 to the core network in the initial registration procedure. You may.

Next, UE_A10 in the first state may select PLMN (S806) when it is necessary to switch to another PLMN due to movement (mobility) or when the power is turned on in an area other than HPLMN. The PLMN selection may be based on the third and / or fourth identification information, which automatically implements the PLMN (VPLMN) ID that supports the specific S-NSSAI used by the UE_A10 on the HPLMN. It may be carried out manually by the user of UE_A10.

If two or more PLMN IDs are included in the plurality of third identification information and / or the fourth identification information, a higher PLMN ID may be selected based on the priority or the like. Here, the priority may be the order in which the PLMN ID and access technology and / or the combination of one or more S-NSSAIs are stored, and the first stored PLMN ID and access technology and / or one or more are stored. The S-NSSAI combination may have the highest priority.

Next, the PLMN ID of the connection destination is selected based on the PLMN selection, and the determined UE_A10 may execute the registration procedure (S808) for the selected and determined connection destination PLMN, and this registration procedure is performed by mobility. It may be a registration procedure to be executed, or it may be an initial registration procedure. In addition, the registration procedure for VPLM (PLMN # 2 in Fig. 8) may be the same as the registration procedure described in Chapter 3, or even if the registration request message does not include the first identification information. good.

Also, so far, the third identification information and / or the fourth identification information has described an embodiment in which UE_A10 receives and / or updates at HPLMN by a registration procedure and / or an update procedure. However, not limited to this, the VPLMN may also receive and / or update the third and / or fourth identification information by the registration procedure and / or the renewal procedure.

[5. Modification example]
The program that operates in the apparatus according to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to operate the computer so as to realize the functions of the embodiments according to the present invention. The program or information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, Hard Disk Drive (HDD), or other storage device system.

Note that the program for realizing the function of the embodiment according to the present invention may be recorded on a computer-readable recording medium. It may be realized by loading the program recorded on this recording medium into a computer system and executing it. The "computer system" as used herein is a computer system built into a device, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another recording medium that can be read by a computer. May be good.

Further, each functional block or various features of the device used in the above-described embodiment can be implemented or executed in an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Further, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or a plurality of aspects of the present invention can use a new integrated circuit according to the technology.

The invention of the present application is not limited to the above-described embodiment. In the embodiment, an example of the device has been described, but the present invention is not limited to this, and the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device or a kitchen device. It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

As described above, the embodiment of the present invention has been described in detail with reference to the drawings, but the specific configuration is not limited to this embodiment, and includes design changes and the like within a range that does not deviate from the gist of the present invention. Further, the present invention can be variously modified within the scope of the claims, and the technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Is done. In addition, the elements described in each of the above embodiments include a configuration in which elements having the same effect are replaced with each other.

Claims (1)

1. UE (User Equipment)
   It is equipped with a transmission / reception unit, a control unit, and a storage unit.
   The transmitter / receiver is the first PLMN (Public Land Mobile Networks), the first S-NSSAI (Single Network Slice Selection Assistance Information) permitted to be used in the first PLMN, and the first S-. Receive a registration acceptance message from the core network that includes a second PLMN ID that indicates the second PLMN associated with the NSSAI.
   The storage unit stores the second PLMN ID and the first S-NSSAI in association with each other.
   The control unit can select the second PLMN based on the second PLMN ID associated with the first S-NSSAI.
   The control unit transitions to the registration state based on the reception of the registration acceptance message, and then changes to the registration state.
   After receiving the registration acceptance message, the transmission / reception unit is associated with the first S-NSSAI permitted to be used in the first PLMN and the first S-NSSAI in the first PLMN. When a configuration update command containing a third PLMN ID indicating the third PLMN is received,
   The storage unit stores the third PLMN ID and the first S-NSSAI in association with each other.
   The control unit selects the third PLMN based on the third PLMN ID associated with the first S-NSSAI.
   UE characterized by that.

Images