JP2021166360A - UE (User Equipment) - Google Patents

Abstract

To provide communication means for realizing functions regarding management of information on network slices in 5GS.SOLUTION: The present invention provides methods and communication means for procedures in an initial registration of UE and a periodic or mobility based registration, for realizing management of information on network slices in 5GS. The present invention further provides methods and communication means for a network slice-specific authentication and authorization procedure, a UE configuration update procedure and a de-registration procedure, after completion of the registration procedures.SELECTED DRAWING: Figure 6

Description

The present invention relates to UE (User Equipment).

The 3GPP (3rd Generation Partnership Project), which has been working on the standardization of 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 (5GS) is a system that realizes 5G mobile communication systems. 5G System) is being specified (see Non-Patent Document 1 and Non-Patent Document 2). 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.

3GPP TS 23.501 V16.4.0 (2020-3); 3rd GenerationPartnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16) 3GPP TS 23.502 V16.4.0 (2020-3); 3rd GenerationPartnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16) 3GPP TS 24.501 V16.4.0 (2020-3); 3rd GenerationPartnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16)

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

In addition, 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 study further functions related to network slicing. As part of Phase 2 of eNS, 3GPP is considering adding a function to manage the number of UEs allowed for each slice or the number of sessions to be connected.

However, the actual method for satisfying the above requirements has not been clarified.

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) of the embodiment of the present invention includes a transmission / reception unit and a storage unit, and the transmission / reception unit receives the first rejection NSSAI (Network Slice Selection Assistance Information) from the core network and receives the UE. If more than one tracking area information contained in the information indicating the registration area stored by is belonging to different PLMNs, the storage unit includes the received first reject NSSAI in each reject NSSAI associated with each PLMN. It is characterized by remembering.

The UE (User Equipment) of the embodiment of the present invention includes a transmission / reception unit and a storage unit, and the transmission / reception unit receives the first rejection NSSAI (Network Slice Selection Assistance Information) from the core network. When multiple tracking area information contained in the information indicating the registration area stored by the UE belongs to a plurality of different PLMNs, the storage unit associates the received first rejection NSSAI with the plurality of different PLMNs. It is characterized by being included in one rejection NSSAI and memorized.

The UE (User Equipment) according to the embodiment of the present invention includes a transmission / reception unit, a storage unit, and a control unit, and the transmission / reception unit transmits a first PLMN request NSSAI (Network Slice Selection Assistance Information) to the UE. If multiple tracking area information contained in the information indicating the registration area stored in the storage belongs to a plurality of different PLMNs, the control unit makes a request NSSAI a rejection associated with each of the plurality of different PLMNs and the registration area. It is characterized by not including S-NSSAI included in NSSAI.

According to the present invention, eNS can be supported in 5GS, and the number of UEs allowed for each slice can be managed.

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 Network Slice specific authentication and authorization procedure. It is a figure explaining the change / update procedure of a UE setting. It is a figure explaining the non-registration procedure which a network starts.

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

[1. System overview]
First, FIG. 1 is a diagram for explaining 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 (DataNetwork) _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, 5G AN, 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 an access network_A and a core network_A, but may further include a UE and / or a 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.

A UE is a device that can connect to network services via 3GPP access (3GPP access network, also referred to as 3GPP AN) and / or non-3GPP access (non-3GPP access network, also referred to as 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 include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device.

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). 5G AN consists 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 the 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 located 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.

In addition, core network_A corresponds to EPC (Evolved Packet Core). For example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway) -U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. are arranged in EPC. NS.

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) and the like 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). Alternatively, it may be a core network for a virtual mobile network operator such as MVNE (Mobile Virtual Network Enabler) or a virtual mobile communication service provider.

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

Further, in FIG. 1, the case where the PDN and the DN are the same is described, but they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. 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.

The UE can also 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 having an authentication function for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives an authentication request for 3GPP access and / or non-3GPP access from the UE and executes the authentication procedure.

The AAA server is also a device having authentication, authorization 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 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, 5GAN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150, etc. The device / function of the above 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.

The control unit_A300 is a functional unit that controls the operation and function 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 apparatus (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmitter / receiver_A320. In addition, the UE can communicate with the base station device (gNB) in the 5G AN by using the transmitter / receiver _A320. In addition, the UE can send and receive NAS (Non-Access-Stratum) messages to and from the AMF via the N1 interface by using the transmitter / receiver _A320. However, because the N1 interface is logical, communication between the UE and AMF is actually done via 5G AN.

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.

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

To explain in detail with reference to FIG. 2, the gNB in the 5G AN 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. Further, the 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_B720 is a functional unit for AMF to connect to the base station equipment (gNB) in 5G AN 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 5G AN 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, because the N1 interface is logical, communication between the UE and AMF is actually done via 5G AN. 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 function, Mobility management function such as UE, SM (Session Management) message between UE and SMF Transfer function, Access Authentication (Access Authorization) function, Security Anchor Functionality (SEA), Security Context Management (SCM) function, N2 interface support for N3IWF (Non-3GPP Interworking Function) , It has a function to support the transmission and reception of NAS signals with the UE via N3IWF, and a function to authenticate the UE connected via N3IWF.

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 5 GMM 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.

In connection management, the CM status of 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).

Further, 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 states in non-3GPP access include the non-3GPP access non-connected state (CM-IDLE state over non-3GPP access) and the non-3GPP access connected state (CM-CONNECTED state over 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). Further, the non-connected state in 3GPP access may be expressed as 5GMM non-connected mode (5GMM-IDLE mode over 3GPP access) in 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access). Further, the non-connected state in non-3GPP access may be expressed as 5GMM-IDLE mode over non-3GPP access in non-3GPP access, and the connected state in non-3GPP access is non-. It may be expressed as 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.

In addition, one or more AMFs may be arranged in the core network_B. In addition, AMF may be an NF that manages one or more NSIs (Network Slice Instances). The AMF may also be a shared CPNF (Control Plane Network Function) (CCNF) shared among a plurality of NSIs.

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

[2.4. SMF device configuration]
Next, an example of the 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.

The control unit_B700 is a functional unit that controls the operation and function 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.

The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the 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.

The control unit_B700 is a functional unit that controls the operation and function 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_B720 is a functional unit for the UPF to connect to the base station equipment (gNB) and / or SMF and / or DN in the 5G AN. 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 the 5G AN and / or the SMF and / or the 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 the 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 forwarding function), packet routing and forwarding function, UL CL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, Branching that supports multi-homed PDU sessions. It has a point function, a QoS (Quality of Service) processing function for the user plane, a function for verifying uplink traffic, a function for buffering downlink packets, and a function for triggering 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 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 NGRAN 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.

Further, the control plane is a control message sent and received to control the communication of the UE and the like. 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 UE and NGRAN and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or a C-Plane.

Further, 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, core network_B, and DN may be referred to as a network or a network device. That is, the fact that the network executes the transmission / reception and / or processing of messages may mean that the devices (network devices and / or control devices) in the network execute the transmission / reception and / or processing of messages. .. 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 PDU session establishment request messages, PDU session establishment accept messages, PDU session establish reject messages, and PDU session modification requests. request message, PDU session modification command message, PDU session modification complete message, PDU session modification command reject message, PDU session modification reject ) Messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, PDU session release complete messages, etc. May be included. In addition, the procedure for SM or SM procedure includes PDU session establishment procedure, PDU session modification procedure, and 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 in the procedure for MM, and may be a control message sent and received between UE_A10 and AMF_A240. In addition, the MM messages include Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages, and De-registration accept messages. , Configuration update command message, configuration update complete message, service request message, service accept message, service reject message, notification message, Notification response messages and the like may be included. The procedures for MM or MM are registration procedure, de-registration procedure, generic UE configuration update procedure, authentication / approval procedure, and service request procedure (Registration procedure). It may include a service request procedure, a paging procedure, and a notification procedure.

Further, the 5GS (5G System) service may be a connection service provided by 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.

Also, 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.

In addition, 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, the DNN (Data Network Name) may be identification information that identifies the core network and / or an external network such as a DN. Furthermore, DNN can also be used as information for selecting a gateway such as 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 UE's IMSI (International Mobile Subscriber Identity) may be the Home PLMN (HPLMN). PLMN may mean core network.

In addition, the UE may have an Equivalent HPLMN list in the USIM to identify one or more EHPLMNs (Equivalent HPLMNs). The PLMN different from HPLMN and / or EHPLMN may be VPLMN (Visited PLMN).

The PLMN successfully registered by the UE may be an RPLMN (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 the PLMN requested by the UE and / or the PLMN selected by the UE and / or the RPLMN, and / or the PLMN permitted by the network, and / or the 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.

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. In addition, NSI may be composed of virtual NF (Network Function) generated by using NST (Network Slice Template).

Here, NST is a logical representation of one or more NFs associated with a resource request to provide the required communication service or capability. That is, 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 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 only of 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 an S-NSSAI IE (Information element). Furthermore, the S-NSSAIIE transmitted and received between the UE and NW is the S-NSSAI composed of the SST and / or SD of the registered PLMN, and / or the SST indicating the S-NSSAI of the HP LMN to which the S-NSSAI is mapped. 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 a registered PLMN S-NSSAI in a roaming scenario. The UE may store one or more mapped S-NSSAIs that are mapped to the configured NSSAIs and the S-NSSAIs included in the allowed NSSAIs for 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 contained 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. In addition, a UE with NSSAA functionality can manage, store, and send and receive pending NSSAI and a 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.

The S-NSSAI requiring NSSAA is an S-NSSAI requiring NSSAA 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 managed by the core network and / or the core network device, in which the S-NSSAI requiring NSSAA becomes the mapped S-NSSAI.

The core network and / or the core network device may store the S-NSSAI that requires NSSAA by associating and storing information indicating whether or not 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 is NSSAI supplied and stored in the UE. The UE may store the configured NSSAI for each PLMN. The UE may remember the configured NSSAI in association with the PLMN. In this paper, the configured NSSAI associated with the PLMN may be expressed as the configured NSSAI for the PLMN, the configured NSSAI for the PLMN, the configured NSSAI for the PLMN, or the configured NSSAI associated with the PLMN. Also, the UE may remember the configured NSSAI that is not associated with the PLMN and is valid for all PLMNs, and such configured NSSAI may be referred to as the "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 described 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 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, requestedNSSAI 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 a PDU session establishment request message. ..

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

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

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

In this paper, the allowedNSSAI associated with the PLMN and the access type may be expressed as the allowedNSSAI for the PLMN and the access type, or the allowedNSSAI for the access type of the PLMN. S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI. The allowed S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI.

Also, rejected NSSAI is information indicating one or more network slices for which the UE is not allowed. 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.

Further, the 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 S-NSSAI and mapped S-NSSAI.

The UE and / or NW may store and manage the rejected NSSAI in association with the 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. good. The first rejected NSSAI may be a rejected NSSAI stored by 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 currently It may be information indicating that it is not possible in PLMN or SNPN of. 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 memory if 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 current PLMN via one access, the UE is registered to the current PLMN via the other access (registered state). The UE does not have to remove the first rejected NSSAI.

The second rejected NSSAI is a set of one or more S-NSSAIs that the UE has included in the requested NSSAIs that are not available in the current registration area. The second rejected NSSAI may be the rejected NSSAI for the current registration area of 5GS. The second rejected NSSAI may be a rejected NSSAI stored by 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)", 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 an access, the UE may delete the second rejected NSSAI associated with that access from memory.

The third rejected NSSAI is an S-NSSAI that requires an NSSAA and is a collection of one or more S-NSSAIs for which the 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 rejection value. The reason for refusal value at this time may be "S-NSSAI not available due to the failed or revoked NSSAA" and is associated with the reason for refusal value. It may be information indicating that NSSAA for S-NSSAI has failed or was canceled. 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.

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 a different NSSAI than the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI. The third rejected NSSAI may be the 5GS rejected NSSAI for the failed or revoked NSSAA, the rejected S-NSSAI for the failed or revoked NSSAA, or the S included in the rejected NSSAI for the failed or revoked NSSAA. -May be 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 initiate 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 sent. 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 remove 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 a rejected NSSAI, an allowed NSSAI, or a 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 effective period range of the value of the backoff timer is whether the value of the backoff timer is applied to the current PLMN (Public Land Mobile Network), all PLMNs, or the current registration area. It may be information indicating whether it is valid or not.

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

A pending NSSAI is a set of one or more S-NSSAIs that a UE cannot and / or cannot use. The pendingNSSAI is an S-NSSAI whose network requires network slice specific authentication, and may be a set of S-NSSAIs 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. Information may indicate that the UE is prohibited or pending from use until the NSSAA is completed.

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, to one or more EPLMNs of the registered PLMN and the registered PLMN, or to 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.

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

A 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 remembers the pending NSSAI, the UE does not attempt to send a registration request message containing the S-NSSAI contained in the pending NSSAI to both 3GPP access and non-3GPP access.

The tracking area is a singular or plural range managed by the core network and 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 a TA (Tracking Area). The tracking area may be identified by a TAI (Tracking Area Identity) composed of a TAC (Tracking area code) and a PLMN.

A registration area is a set of one or more TAs that AMF assigns to a UE. 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 in the TAI list belong to different PLMNs, those PLMNs may be EPLMNs.

The UE ID is information for identifying the UE. Specifically, for example, the UE ID is SUCI (SUbscription Concealed Identifier) or SUPI (Subscription Permanent Identifier), or GUTI (Globally Unique Temporary Identifier), or IMEI (International Mobile Subscriber Identity), or IME ISV (IMEI Software Version) or , TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set within the application or network. Further, the UE ID may be information for identifying the user.

The maximum number of UEs connected to a slice is managed at the same time as the maximum number of UEs that can be registered in the network slice or S-NSSAI. 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 the MM message by the UE and / or the start of the procedure by the SM message. 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.

Further, the backoff timer may be a timer for prohibiting the transmission of the MM message 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.

In addition, the UE may be configured 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. 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 no NSSAI and for prohibiting the transmission of the MM message using no NSSAI. In other words, UE_A10 may be set not to send MM messages using no NSSAI while this timer is counting. 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.

Further, 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 is information indicating the network slice requested by the UE. The first identification information may be information including one or more S-NSSAI associated with the network slice requested by the UE. The network slice requested by the UE here may be a network slice that the UE wants to use, or a network slice that requires the UE to be permitted to use by the network. The S-NSSAI included in the first identification information may be the S-NSSAI included in the configured NSSAI associated with the current PLMN, or the S included in the allowed NSSAI associated with the current PLMN. -May be NSSAI.

In other words, the first identity is contained in the S-NSSAI associated with the configured NSSAI associated with one or more current PLMNs, or the allowed NSSAI associated with one or more current PLMNs. It may be S-NSSAI or a combination of the above two. More specifically, the allowed NSSAI associated with the current PLMN may be an allowed NSSAI associated with the current PLMN and the current access type. Further, the first identification information may be 5GS requested NSSAI.

The S-NSSAI included in the first identification information may be an S-NSSAI stored by the UE and not included in the rejected NSSAI associated with the current PLMN, and / or stored by the UE. , S-NSSAI not included in the pending NSSAI associated with the current PLMN, or S-NSSAI remembered by the UE and not included in the first NSSAI associated with the current PLMN. You can.

Further, the S-NSSAI included in the first identification information is the S-NSSAI in the UE, or the S-NSSAI in which the backoff timer associated with the mapped S-NSSAI of the S-NSSAI is not executed. You can.

The second identification information may be information indicating that the UE supports a function for managing the maximum number of UEs connected to the slice. Alternatively, the second identification information may be information indicating whether or not the UE supports a function for managing the maximum number of UEs connected to the slice. The second identification information may be 5G MM capability information. The second identification information may be information indicating that the UE can store it.

The tenth identification information may be information indicating S-NSSAI that has reached the maximum number of UEs that can be registered in the network slice or S-NSSAI. The tenth identification information may be included in the allowed NSSAI transmitted from the network, the rejected NSSAI transmitted from the network, or the pending NSSAI transmitted from the network. , Information different from these may be transmitted from the network.

Further, the tenth identification information may be NSSAI. Further, the tenth identification information may be allowed NSSAI or rejected NSSAI. Furthermore, the tenth identification information may be pending NSSAI or may be a different NSSAI.

The tenth identification information may be the first NSSAI or the S-NSSAI contained in the first NSSAI. The tenth identification information may be configured to include at least one of the eleventh to fifteenth identification information. Specifically, the tenth identification information includes the S-NSSAI that has reached the maximum number of UEs that can be registered in the network slice or S-NSSAI, the mapped S-NSSAI of the S-NSSAI, and the network slice or S-NSSAI. The reason value indicating that the maximum number of UEs that can be registered has been reached, the value of the backoff timer indicating the period during which the UE is prohibited from sending the registration request message using the S-NSSAI, and the backoff timer. It may be configured to include at least one or more information indicating the effective range of the above. Furthermore, the tenth identification information is a reason value indicating that the maximum number of UEs that can be registered for the network slice has been reached, and a backoff timer indicating the period during which the transmission of the registration request message using no NSSAI is prohibited. It may be configured to include at least one or more information among the value and the information indicating the effective range of the backoff timer. The reason value indicating that the maximum number of UEs that can be registered for the network slice has been reached, the value of the backoff timer indicating the period during which the transmission of the registration request message using no NSSAI is prohibited, and the backoff timer. The information indicating the effective range of is not included in the tenth identification information, and may be transmitted and received separately. Here, when the tenth identification information is included in the rejected NSSAI, the reason value included in the tenth identification information may be a rejection reason value.

The eleventh identification information may be information indicating to the UE that the network has reached the maximum number of UEs that can be registered in the network slice or S-NSSAI, and / or a reason value. The eleventh identification information may be information indicating that the use of S-NSSAI is rejected or restricted because the maximum number of UEs to be connected for each slice has been reached, and / or a reason value. In other words, the eleventh identification information is information and a reason value indicating that the use of S-NSSAI is rejected or restricted because the UE has reached the maximum number of UEs to be connected per slice from the network. The eleventh identification information may be included in the tenth identification information, and is shown in the S-NSSAI shown in the fourteenth identification information contained in the same tenth identification information, and / or in the fifteenth identification information. May be associated with mappedS-NSSAI. The eleventh identification information may be associated with each identification information contained in the same tenth identification information. When the eleventh identification information is included in the rejected NSSAI, the eleventh identification information may be a refusal reason value. The eleventh identification information may be flag information.

Further, the eleventh identification information may be a reason value indicating that the connection to the slice is restricted and / or not permitted. Further, the eleventh identification information may be a reason value indicating that registration in the slice is restricted and / or not permitted.

Further, the eleventh identification information may be a 5GMM (5G Mobility Management) cause. Further, the eleventh identification information may be the 22nd 5GMM cause. Here, the 22nd 5GMM cause may be a reason value indicating congestion. In addition, the 22nd 5GMM cause may be information sent to the UE due to network congestion.

Further, the eleventh identification information may be a 5GMM cause other than the 22nd 5GMM cause. For example, the eleventh identification information may be information transmitted to the UE due to congestion of the network slice. Further, the eleventh identification information may be information transmitted to the UE due to lack of resources in the network slice. Further, the eleventh identification information may be a reason value indicating that the requested service cannot be provided due to insufficient resources for a specific slice.

The twelfth identification information may be the value of the backoff timer. Specifically, the twelfth identification information transmits an MM message using the S-NSSAI shown in the fourteenth identification information and / or the fifteenth identification information contained in the ten identification informations in which the UE is the same. It may be information indicating the period during which the network prohibits sending SM messages other than the PDU connection release request message. In other words, the twelfth identification information sends a registration request message using the S-NSSAI shown in the fourteenth identification information and / or the fifteenth identification information contained in the ten identification informations in which the UE is the same. That may be information indicating the period prohibited by the network.

The twelfth identification information may be included in the tenth identification information, and is shown in the S-NSSAI shown in the fourteenth identification information contained in the same tenth identification information, and / or in the fifteenth identification information. May be associated with mapped S-NSSAI. The twelfth identification information may be associated with each identification information contained in the same tenth identification information.

The thirteenth identification information is information indicating the effective range of the backoff timer. Specifically, the thirteenth identification information may be information indicating the effective range of the backoff timer counted by the UE, using the value of the corresponding backoff timer. More specifically, the thirteenth identification information is that the corresponding backoff timer is applied to the current PLMN (UE-requested PLMN, or RPLMN), or to all PLMNs. It may be information indicating. Further, or, the thirteenth identification information may be information indicating that it is applied to the current registration area.

Further, the thirteenth identification information may be information indicating the scope of regulation or information indicating the scope to which the regulation is applied. The regulation may be a regulation based on congestion management. More specifically, the regulation may limit the transmission of UE MM messages. Further, the regulation may be realized by a back-off timer.

The thirteenth identification information may be included in the tenth identification information, in which case the value of the corresponding backoff timer is the value indicated by the twelfth identification information contained in the same tenth identification information. good. Further, in that case, the thirteenth identification information may be associated with each identification information contained in the same tenth identification information.

The 14th identification information is information indicating S-NSSAI that has reached the maximum number of UEs that can be registered for each S-NSSAI. The 14th identification information may be the S-NSSAI included in the 10th identification information and is associated with the mapped S-NSSAI shown in the 15th identification information contained in the same 10th identification information. good. The fourteenth identification information may be associated with each identification information contained in the same tenth identification information. Further, the 14th identification information may be S-NSSAI.

The fifteenth identification is the HPLMN S-NSSAI associated with the corresponding S-NSSAI. Specifically, if the current PLMN (current PLMN, or PLMN requested by the UE, or RPLMN, PLMN selected by the UE) is not an HPLMN, the fifteenth identification information is mapped to the S-NSSAI of the current PLMN. It may be information indicating the S-NSSAI of the HPLMN. The fifteenth identification information may be mapped S-NSSAI.

The fifteenth identification information may be the mapped S-NSSAI included in the tenth identification information, and is associated with the S-NSSAI shown in the fourteenth identification information contained in the same tenth identification information. Often, in that case, it may be the mapped S-NSSAI of the S-NSSAI shown in the 14th identification information. The fifteenth identification information may be associated with each identification information contained in the same tenth identification information. Further, the fifteenth identification information may be the mapped S-NSSAI of the S-NSSAI indicated by the fourteenth identification information.

[3.1. Explanation of procedures used in each embodiment]
Next, the procedure used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a Network Slice-Specific Authentication and Authorization procedure, a UE configuration update procedure, and a network-initiated de-registration procedure. procedure) is included. Is included. Each procedure will be explained below.

In each embodiment, as shown in FIG. 2, the HSS and UDM, the PCF and PCRF, the SMF and PGW-C, and the 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. Alternatively, the registration procedure performed while the UE is registered on the network can be changed to the registration procedure for mobility and periodic registration update or the mobility and periodic registration update. and periodic registration procedure).

The new AMF141 in FIG. 6 indicates the AMF in which UE_A10 is registered by this procedure, and the old AMF142 means the AMF in which the UE is 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. The 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 also be a control message sent and received between the UE and 5GAN120 (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 transmit at least one of the first and second 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 UE capability information in a registration request message to notify the network of the features that UE_A10 supports. Here, the capability information of the UE may be 5G MM capability of 5GS.

UE_A10 may send these identification information by including them 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. .. 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.

In addition, UE_A10 determines whether or not to transmit the first and second identification information to the network, UE capability information and / or UE policy, and / or UE status, and / or user registration information, and /. Alternatively, it may be selected and decided based on the context held by the UE.

If UE_A10 has a function for managing the maximum number of UEs connected to a slice, or if it requires at least one S-NSSAI that requires management for managing the maximum number of UEs connected to a slice, a second identification information. May be sent. UE_A10 may notify the network that it has a function of storing the first NSSAI by transmitting the second identification information.

In addition, if UE_A10 has NSSAA functionality or requests at least one S-NSSAI that identifies a slice that requires NSSAA, it will send capability information in the registration request message indicating that it supports NSSAA functionality. May be good. UE_A10 requests the network to treat this UE as a UE with NSSAA function by sending capability information indicating that it supports the NSSAA function, and to perform authentication and approval procedures by the NSSAA function in the procedure related to UE. You may.

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

Or, if 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. If the TAI contained in the registration area associated with belongs to the PLMN requested by the UE, the UE may include the first identification information in the registration request message and send it to the requested PLMN.

UE_A10 may determine the information contained in the first identification information based on one or more NSSAIs stored by the UE. One or more NSSAIs stored by the UE may be, for example, the allowed NSSAI associated with the requested PLMN and the requested access type, and / or the configured NSSAI associated with the requested PLMN, and / or the default configured NSSAI, and / or the request. It may be a rejected NSSAI associated with the PLMN. Further / or the one or more NSSAIs stored by the UE may be a pending NSSAI and / or a first NSSAI.

Further / or one or more NSSAIs stored by the UE are allowed NSSAIs associated with PLMNs other than PLMNs requested by the UE and access types and / or access types requested by the UE, and / or request. It may be a second rejected NSSAI associated with a PLMN other than the PLMN and the current registration area. Furthermore, UE_A10 may also store the mapped S-NSSAI of S-NSSAI included in each NSSAI stored by the UE.

The UE may select one or more S-NSSAIs from the allowed NSSAIs and / or configured NSSAIs to be stored and include them in the first identification information for transmission.

Specifically, if UE_A10 remembers the allowed NSSAI associated with the requested PLMN and the requested access type, the UE_A10 will include the allowed NSSAI, or its allowed NSSAI, in the first identification information. One or more S-NSSAIs included may be included and transmitted.

Further / or when storing the configured NSSAI associated with the PLMN requested by the UE_A10, the UE_A10 includes the configured NSSAI or one or more S-NSSAI contained in the configured NSSAI in the first identification information. May be sent.

Furthermore, if UE_A10 remembers "allowed NSSAI associated with PLMNs other than the requested PLMN and the requested access type", then the allowed NSSAI or the S-NSSAI contained in the allowed NSSAI, If the TAI contained in the associated registration area (TAI list) is associated with the requested PLMN, the UE_A10 will include the allowed NSSAI, or one or more Ss contained in the allowed NSSAI, in the first identification. -You may send including NSSAI.

In other words, UE_A10 is the "S-NSSAI contained in the allowed NSSAI associated with the PLMN other than the requested PLMN and the registration area," or the "PLMN other than the requested PLMN" stored in the first identification information. The allowed NSSAI associated with the "S-NSSAI associated with the registration area" may be included, and at least one TAI contained in this registration area may belong to the first PLMN.

The first identification information may be configured to include one or more of the above S-NSSAI. However, UE_A10 may be controlled so that one or more S-NSSAIs included in the first identification information do not overlap.

Further, when the rejected NSSAI is stored for the PLMN requested by the UE_A10, the UE_A10 may be transmitted without being included in the first identification information by the S-NSSAI included in the rejected NSSAI.

Specifically, if the UE_A10 remembers the "first rejected NSSAI associated with the requesting PLMN", the UE_A10 sends the S-NSSAI contained in the first rejected NSSAI without including it in the first identification information. You may. In other words, UE_A10 controls that one or more S-NSSAIs contained in the first identification information are no longer S-NSSAIs contained in the "first rejected NSSAI associated with the requested PLMN" stored by the UE. You can.

Further, if UE_A10 stores at least one "second rejected NSSAI associated with the requested PLMN or EPLMN and the current registration area", UE_A10 is included in those second rejected NSSAIs- NSSAI may be transmitted without being included in the first identification information. In other words, UE_A10 is a second rejected NSSAI associated with each "requested PLMN or EPLMN and current registration area" stored by UE_A10 by one or more S-NSSAIs contained in the first identification information. You may perform control that is not S-NSSAI included in.

If the information indicating the current registration area stored by UE_A10 includes a TAI belonging to one or more PLMNs different from the requested PLMN, the different PLMN is the EPLMN of the requested PLMN, and UE_A10 is A second, where one or more S-NSSAIs contained in the first identification information are associated with each "one of the different PLMNs and the current registration area" stored by UE_A10. You may perform control that is not S-NSSAI included in "rejected NSSAI".

In other words, if the information indicating the current registration area stored by UE_A10 includes a TAI belonging to one or more PLMNs different from the requested PLMN, the UE_A10 will include each "the different one or more" in the first identification information. It is not necessary to include the S-NSSAI included in the "second rejected NSSAI" associated with the PLMN of one of the multiple PLMNs and the current registration area.

Furthermore, if the UE_A10 remembers the "third rejected NSSAI associated with the requesting PLMN", the UE_A10 may transmit the S-NSSAI contained in the third rejected NSSAI without including it in the first identification information. good. In other words, UE_A10 controls that one or more S-NSSAIs contained in the first identification information are no longer S-NSSAIs contained in the "third rejected NSSAI associated with the requested PLMN" stored in the UE_A10. You can.

Furthermore, if UE_A10 remembers at least one "third rejected NSSAI associated with the requested PLMN EPLMN", UE_A10 does not include the S-NSSAI contained in that third rejected NSSAI in the first identification. May be sent to. In other words, UE_A10 is the S-NSSAI in which one or more S-NSSAIs contained in the first identification information are contained in each "third rejected NSSAI associated with the EPLMN of the requested PLMN" stored in the _UE_A10. You may control the disappearance.

Furthermore, if UE_A10 remembers the "third rejected NSSAI valid for all PLMNs", UE_A10 is the S-NSSAI contained in the third rejected NSSAI, or the S-NSSAI to which the S-NSSAI is mapped. Alternatively, the S-NSSAI associated with the S-NSSAI or the mapped S-NSSAI of the S-NSSAI may be transmitted without being included in the first identification information. In other words, UE_A10 is S-NSSAI, or S-NSSAI thereof, in which one or more S-NSSAI contained in the first identification information is included in each "third rejected NSSAI valid for all PLMNs" stored in UE_A10. -You may control the NSSAI to no longer be the mapped S-NSSAI, or the S-NSSAI associated with that S-NSSAI, or the mapped S-NSSAI of that S-NSSAI. The "third rejected NSSAI valid for all PLMNs" may mean a third rejected NSSAI that is not associated with the PLMN, or may mean a third rejected NSSAI that is associated with the HPLMN.

Further, when the UE stores the "pending NSSAI associated with the requesting PLMN", the UE may transmit the S-NSSAI included in the pending NSSAI without including it in the first identification information. In other words, the UE may control that one or more S-NSSAIs included in the first identification information are no longer S-NSSAIs included in the "pending associated with the requested PLMN" stored by the UE.

Further, if the UE remembers at least one "pending NSSAI associated with the requested PLMN EPLMN", the UE may transmit the S-NSSAI contained in the pending NSSAI without including it in the first identification information. .. In other words, the UE may control that one or more S-NSSAIs included in the first identification information are no longer S-NSSAIs included in each "pending NSSAI associated with the EPLMN of the requested PLMN".

Furthermore, if the UE remembers "pending NSSAI valid for all PLMNs", the UE is either the S-NSSAI contained in the pending NSSAI, or the S-NSSAI to which the S-NSSAI is mapped, or the S-NSSAI. The S-NSSAI associated with, or the mapped S-NSSAI of the S-NSSAI may be transmitted without being included in the first identification information. In other words, the UE is mapped to one or more S-NSSAIs included in the first identification information, S-NSSAIs included in each "pending NSSAI valid for all PLMNs", or its S-NSSAIs. Control may be performed to eliminate the S-NSSAI, or the S-NSSAI associated with the S-NSSAI, or the mapped S-NSSAI of the S-NSSAI. The "pending NSSAI valid for all PLMNs" may mean a pending NSSAI that is not associated with a PLMN, or may mean a pending NSSAI that is associated with an HPLMN.

Furthermore, UE_A10 indicates that the S-NSSAI, if the backoff timer associated with a certain S-NSSAI is enabled, in other words, if the backoff timer is running, or until the backoff timer is stopped. Alternatively, the S-NSSAI related to the S-NSSAI may be transmitted without being included in the first identification information. Specifically, if the S-NSSAI associated with the backoff timer is the S-NSSAI associated with the requested PLMN or the S-NSSAI included in the NSSAI associated with the requested PLMN, The UE_A10 may transmit the S-NSSAI without including it in the first identification information while the backoff timer is counting or until the backoff timer expires or is stopped. Alternatively, if the S-NSSAI associated with the backoff timer is associated with the HPLMN, UE_A10 does not include the requested PLMN S-NSSAI mapped to that S-NSSAI in the first identification. You may send it. Note that the S-NSSAI associated with the backoff timer is associated with the HPLMN may mean that the backoff timer is valid for all PLMNs, and the backoff timer is associated with the PLMN. It may mean that it is not associated.

Further, if the UE remembers the "first NSSAI associated with the requested PLMN", the UE may transmit the S-NSSAI contained in the first NSSAI without including it in the first identification information. .. In other words, the UE controls that one or more S-NSSAIs included in the first identification information are no longer included in the "first NSSAI associated with the requested PLMN" stored by the UE. You can.

Furthermore, if the UE remembers at least one "first NSSAI associated with the requested PLMN EPLMN", the UE does not include the S-NSSAI contained in that first NSSAI in the first identification information. You may send it. In other words, the UE controls that one or more S-NSSAIs contained in the first identification information are no longer S-NSSAIs contained in each "first NSSAI associated with the EPLMN of the requested PLMN". good.

Furthermore, if the UE remembers the "first NSSAI valid for all PLMNs", the UE will either use the S-NSSAI contained in the first NSSAI, or the S-NSSAI to which the S-NSSAI is mapped. It may be transmitted without being included in the identification information of 1. In other words, the UE maps one or more S-NSSAIs contained in the first identification information to S-NSSAIs included in each "first NSSAI valid for all PLMNs", or its S-NSSAIs. You may perform control that is no longer the S-NSSAI that was done. The "first NSSAI valid for all PLMNs" may mean the first NSSAI not associated with the PLMN or the first NSSAI associated with the HPLMN.

UE_A10 may include the registration request message and / or the RRC message containing the registration request message other than the identification information of the first and second, for example, including the UE ID and / or the PLMN ID and / or the AMF identification information. You may send it. Here, the AMF identification information may be information that identifies 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.

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 the 5G AN120 (or gNB) receives an RRC message containing a registration request message, it selects the AMF to forward the registration request message (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, the 5G AN (or gNB) may select the new AMF 141 to which the registration request message is sent based on at least one of the first and second identification information.

For example, 5G AN120 (or gNB) may select AMF based on the first identification information. Specifically, the 5G AN (or gNB) may select an AMF included in the network slice identified by S-NSSAI included in the first identification information or having connectivity to the network slice. ..

Further, for example, the 5G AN120 (or gNB) has a function for managing the maximum number of UEs connected to the slice and / or a function for managing the maximum number of UEs connected to the slice based on the second identification information. AMF with connectivity to the provided network may be selected.

The method of selecting AMF is not limited to this, and 5G AN (or gNB) may select AMF based on other conditions. 5G AN (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 at least one of the first and second 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 selected by AMF (new AMF141). May be forwarded with the registration request message (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 if 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 make the first condition determination 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 accept message, and when the first condition determination is false, the control message may be a registration accept 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 allows 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 from the UE by AMF is the information that identifies the slice that requires the NSSAA procedure, the result of the NSSAA procedure of S-NSSAI corresponding to the UE by AMF is also successful. The first condition determination may be true if it is remembered to be. Alternatively, if the UE does not have S-NSSAI allowed and there are no plans 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, the first condition determination may be true if the UE does not have an allowed S-NSSAI but can be expected to continue to allocate allowed NSSAI to the UE.

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 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 described. new AMF141 sends a UE context request message to old AMF142 (S606). The old AMF142 sends a 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 UE ID and allowedNSSAI. In addition, 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 the first NSSAI included in the UE context, and S-NSSAI included in each NSSAI are notified to the UE. Information on whether or not is 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 first conditional decision and / or 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 new AMF141 may include one or more tenth identification information in the control message and send it. Alternatively, the new AMF141 may send the control message including at least one of the 10th to 15th 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 the request from the UE is not permitted, 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.

When the new AMF141 receives the first identification information and / or the second identification information from the UE, at least one of the tenth to fifteenth identification information may be included in the control message and transmitted.

Further, the new AMF141 may transmit at least one of the tenth to fifteenth identification information when the UE setting information is updated.

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

The tenth to fifteenth identification information may be included in the allowed NSSAI and / or the rejected NSSAI, and / or the pending NSSAI, and / or the first NSSAI, and may be transmitted, and these NSSAIs. May be good.

new AMF141 does not have S-NSSAI (allowed NSSAI) allowed to the UE when sending a control message, but if the NSSAA procedure is planned to be executed after the completion of this procedure or in parallel with this procedure, or with the UE If the NSSAA procedure is being performed 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 UE to S-NSSAI (allowed NSSAI) when sending a control message, but if the 10th identification information is included in the control message, and before this procedure, the 1st NSSAI is sent to the UE. If notified, an empty value may be included in allowed NSSAI and sent.

When the new AMF141 includes the thirteenth identification information in the control message indicating that it applies to all PLMNs, the fifteenth 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 identifications from the new AMF 141.

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 10th identification information and / or S-NSSAI indicated by the 14th identification information, and / or It may be recognized that the transmission of the MM message and / or the transmission of the SM message using the S-NSSAI related to the mapped S-NSSAI indicated by the fifteenth identification information 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 for each of the tenth identification information based on the reception of at least one or more of the tenth to fifteenth identification information and / or the reception of the control message.

UE_A10 is related to S-NSSAI indicated by the 10th identification information and / or S-NSSAI indicated by the 14th identification information and / or mapped S-NSSAI indicated by the 15th identification information. May be included and stored in the appropriate first NSSAI. Specifically, the UE transfers the received S-NSSAI indicated by the 14th identification information to the 1st NSSAI associated with the information indicated by the 11th identification information and / or the 13th identification information. You may add it.

Alternatively, UE_A10 may add the mapped S-NSSAI indicated by the received 15th identification information to the 1st NSSAI, or the S-NSSAI regarding the mapped S-NSSAI indicated by the received 15th identification information. May be added to the first NSSAI associated with the current PLMN, or the second associated with the current PLMN and the current access type (registered access type, 3GPP access or non-3GPP access). It may be added to one NSSAI or to the first NSSAI associated with the current PLMN and all access types.

Furthermore, when the S-NSSAI included in the first NSSAI stored by the UE is included in the allowed NSSAI stored by the UE and associated with the PLMN and access type requested by the UE in this procedure and other access types. , You may delete the S-NSSAI from allowed NSSAI.

Further, when the UE_A10 receives the fifteenth identification information, the UE_A10 may store the S-NSSAI indicated by the fifteenth identification information as the mapped S-NSSAI of the S-NSSAI indicated by the fourteenth identification information.

When the UE receives the information indicating that the 13th identification information is applied to all PLMNs, the UE is mapped from the allowed NSSAI corresponding to the PLMN other than the current PLMN, which is indicated by the 15th identification information. S-NSSAI related to S-NSSAI may be deleted.

UE_A10 is the maximum number of UEs that S-NSSAI shown in the 10th identification information connects to each slice based on the reception of the 10th identification information and / or the 11th identification information and / or the reception of the control message. You may recognize that you have reached. Here, the S-NSSAI shown in the tenth identification information may be the S-NSSAI shown in the fourteenth identification information and / or the mapped S-NSSAI shown in the fifteenth identification information.

UE_A10 was associated with S-NSSAI using the value of the backoff timer received based on the reception of at least one or more of the 10th to 15th identification information and / or the reception of the control message. The backoff timer may be counted, the backoff timer may be started, or the backoff timer may be managed. Here, the value of the backoff timer may be the value of the timer shown in the tenth identification information and / or the twelfth identification information, and the S-NSSAI is the first identification information and / or. It may be the S-NSSAI shown in the tenth identification information and / or the fourteenth identification information, and / or the mapped S-NSSAI shown in the fifteenth identification information.

While the backoff timer is running, UE_A10 is associated with S-NSSAI associated with the backoff timer, mappedS-NSSAI (HPLMN S-NSSAI) associated with the backoff timer, or backoff timer. The transmission of MM messages and SM messages using S-NSSAI related to the mapped S-NSSAI may be prohibited.

Further, when UE_A10 receives the thirteenth identification information, the backoff timer may be applied according to the effective range shown in the thirteenth identification information.

Specifically, if the thirteenth identification information is information indicating that it is applied within the current PLMN, UE_A10 may apply the backoff timer within the current PLMN. Specifically, with the PLMN change, UE_A10 does not have to stop the backoff timer count or the backoff timer, but is regulated by the backoff timer associated with the PLMN before the move. May be released. In other words, if the PLMN is changed, the UE will maintain the backoff timer, but the restrictions on the PLMN before the move may be lifted.

Alternatively, UE_A10 may stop the count of the backoff timer associated with the current PLMN or the backoff timer due to the change of the PLMN. In other words, UE_A10 may stop the backoff timer when the PLMN is changed, and the restriction on the PLMN before the move may be lifted.

Alternatively, if the thirteenth identification information is information indicating that it is applied to all PLMNs, UE_A10 may apply the backoff timer to all PLMNs. In other words, UE_A10 may maintain the backoff timer without stopping it in the event of a PLMN change. If a PLMN change occurs while the backoff timer is running, UE_A10 will take the S-NSSAI of the destination PLMN associated with the mapped S-NSSAI of the S-NSSAI to which the backoff timer was associated. , Or the S-NSSAI of the destination PLMN related to the mapped S-NSSAI, or the MM message and SM message using the mapped S-NSSAI may be maintained in a prohibited state.

Alternatively, if the thirteenth identification information is information indicating that it is applied in the current registration area, UE_A10 may apply the backoff timer in the current registration area. In other words, as UE_A10 leaves the registration area, UE_A10 may stop the count of the backoff timer or the backoff timer.

In addition, UE_A10 manages and / or stores the eleventh identification information and / or one or more S-NSSAIs contained in the first NSSAI or the first NSSAI associated with the thirteenth identification information. You can do it.

Here, when the backoff timer is stopped or expires, the restriction is lifted, and UE_A10 is S-NSSAI to which the backoff timer is associated, and / or mapped S-NSSAI to which the backoff timer is associated. You may transition to the state where you can send MM messages and SM messages using S-NSSAI and / or mapped S-NSSAI to which the backoff timer is associated. In other words, upon stopping or expiring the backoff timer, UE_A10 is S-NSSAI for S-NSSAI with which the backoff timer was associated and / or S-NSSAI for mapped S-NSSAI with which the backoff timer was associated. And / or the mapped S-NSSAI to which the backoff timer is associated may be used for the requested NSSAI, and the state may be changed to the state in which the MM message can be transmitted.

Further, UE_A10 may transition to a state in which MM messages can be transmitted using NSSAI associated with the backoff timer when the backoff timer is stopped or expired. In other words, UE_A10 may transition to a state in which the NSSAI associated with the backoff timer can be used as the requested NSSAI to send an MM message when the backoff timer is stopped or expired.

Furthermore, upon stopping or expiring the backoff timer, UE_A10 will start with the first NSSAI, the S-NSSAI with which the backoff timer was associated, or the mapped S-NSSAI with which the backoff timer was associated, or The S-NSSAI associated with the mapped S-NSSAI to which the backoff timer was associated may be deleted.

Specifically, when the backoff timer is valid for the registered PLMN, upon stopping or expiring the backoff timer, UE_A10 is associated with the backoff timer from the first NSSAI associated with the current PLMN. The S-NSSAI associated with the backoff timer, the mapped S-NSSAI associated with the backoff timer, or the S-NSSAI associated with the mapped S-NSSAI associated with the backoff timer may be deleted.

In addition, when the backoff timer is valid for the registered PLMN, upon stopping or expiring the backoff timer, UE_A10 was associated with the backoff timer from the first NSSAI applied to all PLMNs. The S-NSSAI, or the mapped S-NSSAI associated with the backoff timer, or the S-NSSAI associated with the mapped S-NSSAI associated with the backoff timer may be deleted.

Alternatively, if the backoff timer is valid for all PLMNs, upon stopping or expiring the backoff timer, UE_A10 will have a backoff timer associated with it from the first NSSAI applied to all PLMNs. You may delete the S-NSSAI that was associated with the backoff timer, or the mapped S-NSSAI that was associated with the backoff timer, or the S-NSSAI associated with the mapped S-NSSAI that was associated with the backoff timer.

Furthermore, when the backoff timer is valid for all PLMNs, the backoff timer is associated with the S- from the first NSSAI applied to each PLMN upon stoppage or expiration of the backoff timer. The NSSAI, or the mapped S-NSSAI associated with the backoff timer, or the S-NSSAI associated with the mapped S-NSSAI associated with the backoff timer may be deleted.

That is, the S-NSSAI associated with the backoff timer, the mapped S-NSSAI associated with the backoff timer, or the S-NSSAI associated with the mapped S-NSSAI associated with the backoff timer. However, if it is included in a plurality of first NSSAIs and stored by UE_A10, UE_A10 may delete the corresponding S-NSSAI from all the corresponding first NSSAIs.

Specifically, for example, when the backoff timer # 1 associated with the S-NSSAI # 1 is managed as valid in all PLMNs, the UE is accompanied by the stop or expiration of the backoff timer # 1. Removes S-NSSAI # 1 from the first NSSAI # 1 associated with PLMN # 1, and further mapsped S-NSSAI from the first NSSAI # 2 to S-NSSAI # 1 associated with PLMN # 2. You may delete the S-NSSAI # 2 associated with.

Also, when UE_A10 receives a TAI list, the received TAI list may be enabled, and if UE_A10 already remembers a valid TAI list, the old TAI list may be deleted or invalidated. Hereinafter, a valid TAI list may be expressed as a registration area. If UE_A10 does not store a valid TAI list and does not receive a TAI list from the core network during this procedure, the valid TAI list may not be stored.

In addition, UE_A10 may appropriately store each received NSSAI. Specifically, when UE_A10 receives a configured NSSAI, the received configured NSSAI may be stored as "configured NSSAI associated with the current PLMN". That is, UE_A10 may replace "configured NSSAI associated with the current PLMN stored by UE_A10" with "received configured NSSAI".

Furthermore, when the UE_A10 receives the configured NSSAI, the mapped S-NSSAI of the S-NSSAI included in the "configured NSSAI associated with the current PLMN stored in the UE_A10" may be deleted. Further, if the "received configured NSSAI" contains one or more mapped S-NSSAIs, UE_A10 may store one or more of those mapped S-NSSAIs.

Furthermore, when UE_A10 receives a configured NSSAI, it may delete "rejected NSSAI remembered by UE_A10 and associated with the current PLMN".

Alternatively, when the UE_A10 receives a configured NSSAI, the "first rejected NSSAI remembered by the UE_A10 and associated with the current PLMN" and the second rejected NSSAI remembered by the UE_A10 and associated with the current PLMN. And "Third rejected NSSAI remembered by UE_A10 and associated with the current PLMN" may be deleted.

In addition, when the UE_A10 receives a configured NSSAI, "the first NSSAI remembered by the UE_A10" and / or "the first NSSAI remembered by the UE_A10 and associated with the current PLMN", and / or one or Multiple "first NSSAIs remembered by UE_A10 and associated with the current PLMN EPLMN" may be deleted.

In addition, when UE_A10 receives a configured NSSAI, "pending NSSAI remembered by UE_A10" and / or "pending NSSAI remembered by UE_A10 and associated with the current PLMN", and / or one or more "UE_A10". May delete the "first pending NSSAI" that is remembered and associated with the current PLMN EPLMN.

Furthermore, when UE_A10 receives an allowed NSSAI, it may store the received allowed NSSAI as "allowed NSSAI associated with the current PLMN and the current access type". That is, UE_A10 may replace the "allowed NSSAI associated with the current PLMN and the current access type" stored by UE_A10 with the "received allowed NSSAI".

Furthermore, if UE_A10 receives a TAI list and allowed NSSAI from new AMF141, and if at least one TAI contained in the TAI list belongs to EPLMN, UE_A10 will refer to the received allowed NSSAI as "EPLMN to which TAI contained in TAI list belongs". And the current access type, and may be remembered as "allowed NSSAI" associated with.

Or, if UE_A10 does not receive the TAI list and receives allowed NSSAI from new AMF141, and if the TAI included in the TAI list that the UE has received and stored in advance belongs to EPLMN, UE_A10 receives allowed NSSAI. May be stored as "allowed NSSAI associated with the EPLMN to which the TAI in the TAI list belongs and the current access type".

That is, if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs, and UE_A10 sets the "received allowed NSSAI" to each " It may be stored in one allowed NSSAI associated with one of the different PLMNs and the current access type.

In other words, the UE_A10 may store the "received allowed NSSAI" in the "allowed NSSAI associated with the PLMN to which the TAI included in the registration area stored by the UE_A10 belongs and the current access type".

Furthermore, if multiple TAIs contained in the registration area stored by UE_A10 belong to different PLMNs, UE_A10 will be stored with each "PLMN to which the TAI contained in the registration area belongs and the current access type" stored by UE_A10. The "allowed NSSAI" associated with, may be replaced with the "received allowed NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. If UE_A10, the "received allowed NSSAI" is "allowed NSSAI # 1 associated with PLMN # 1 and the current access type" and "allowed NSSAI associated with PLMN # 2 and the current access type". You may memorize it as "# 2".

Alternatively, if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs, and UE_A10 reads "received allowed NSSAI" as "received allowed NSSAI". It may be stored in one allowed NSSAI associated with the different PLMNs to which the TAIs contained in the registration area belong and the current access type.

Further / or when two or more TAIs contained in the registration area belong to more than one PLMN, UE_A10 is stored in the UE_A10 "one or more PLMNs to which the TAI contained in the registration area belongs, the current access type, and / or the current access type. One allowed NSSAI associated with may be replaced with a "received allowed NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 1 which is EPLMN. In this case, UE_A10 may store the "received allowed NSSAI" in the "allowed NSSAI # 1 associated with PLMN # 1 and PLMN # 2 and the current access type".

Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs, and UE_A10 reads "received allowed NSSAI" as "received allowed NSSAI". Only one allowed NSSAI associated with the RPLMN and the current access type may be stored. In other words, even if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the UE_A10 will transfer the "received allowed NSSAI" to the different PLMNs. It does not have to be remembered as the associated allowed NSSAI.

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 "receives one allowed NSSAI associated with the RPLMN and the current access type" stored by the UE_A10. You may replace it with "allowed NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 1 which is EPLMN. In this case, UE_A10 may only store the "received allowed NSSAI" in the "allowed NSSAI # 1 associated with PLMN # 1 and the current access type".

When UE_A10 stores the allowed NSSAI, the allowed NSSAI may be stored in association with the registration area, or the S-NSSAI included in the allowed NSSAI may be stored in association with the registration area.

Furthermore, when UE_A10 receives allowed NSSAI, it may delete the mapped S-NSSAI of S-NSSAI included in "allowed NSSAI deleted based on reception" or "old allowed NSSAI updated based on reception". Furthermore, if the "received allowed NSSAI" includes mapped S-NSSAI, UE_A10 may store one or more of the mapped S-NSSAI.

Furthermore, when UE_A10 receives allowed NSSAI, "rejected NSSAI remembered by UE_A10 and associated with the current PLMN" may be deleted.

Specifically, when UE_A10 receives an allowed NSSAI, "the first rejected NSSAI remembered by UE_A10 and associated with the current PLMN" and "UE_A10 remembered and associated with the current PLMN," "Second rejected NSSAI" and "second rejected NSSAI remembered by UE_A10 and associated with the current PLMN and current registration area" and "second rejected NSSAI remembered by UE_A10 and associated with the current PLMN" The S-NSSAI contained in the received allowed NSSAI may be deleted from at least one of "3 rejected NSSAI", or the S-NSSAI contained in the allowed NSSAI received from all NSSAI may be deleted.

Specifically, when UE_A10 receives an allowed NSSAI, it is associated with the current registration area and further received from the "second rejected NSSAI remembered by the UE_A10 and associated with the current PLMN". You may delete the S-NSSAI contained in.

Furthermore, when the UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives an allowed NSSAI, the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI may be deleted from "pending NSSAI remembered by UE_A10 and associated with all PLMNs". .. Further, when UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Furthermore, when the UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can.

Furthermore, when UE_A10 receives a rejected NSSAI, it stores the S-NSSAI contained in the received rejected NSSAI as "rejected NSSAI associated with the current PLMN" based on the rejection reason value associated with that S-NSSAI. You can. That is, UE_A10 may add "S-NSSAI included in the received rejected NSSAI" to the "rejected NSSAI associated with the current PLMN" stored in UE_A10.

Specifically, if UE_A10 receives the rejection reason value "S-NSSAI not possible with the current PLMN or SNPN" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the S-NSSAI now. May be added to the first rejection NSSAI associated with the PLMN of.

Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI not possible in the current registration area" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the "received rejected S-NSSAI". , "Second rejection NSSAI associated with the current PLMN and the current registration area" may be added.

When UE_A10 receives the TAI list together with the rejected NSSAI, the current registration area is indicated by the received TAI list. On the other hand, if UE_A10 did not receive the TAI list with rejected NSSAI, the current registration area is indicated by the TAI list that UE_A10 previously received and stored.

If the TAI contained in the current registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is the "reason for refusal value" current registration area. The rejected S-NSSAI received in association with the "S-NSSAI" which is not possible in the second is associated with each "PLMN of one or more different PLMNs and the current registration area". It may be stored and / or added to "rejected NSSAI".

Furthermore, if one or more TAIs contained in the registration area belong to different PLMNs, UE_A10 will be stored in each "PLMN to which the TAI contained in the registration area belongs and the current access type." The "rejected S-NSSAI received in association with the rejection reason value" S-NSSAI which is not possible in the current registration area "" may be added to the associated second rejected NSSAI and stored.

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. If UE_A10, the "received second rejected S-NSSAI" is referred to as "the second rejected NSSAI # 1 associated with PLMN # 1 and the current registration area" and "PLMN # 2 and the current registration". It may be remembered in the second rejected NSSAI # 2 associated with the area.

Alternatively, if the TAI contained in the registration area belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is not possible in the "reason for refusal value" current registration area. The "rejected S-NSSAI" received in association with the "S-NSSAI" may be stored in the "one second rejected NSSAI associated with the different PLMN and the current registration area". ..

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will store one second rejected associated with the "these multiple PLMNs and the current access type" that the UE_A10 remembers. You may add and memorize "Rejected S-NSSAI received in association with the rejection reason value" S-NSSAI which is not possible in the current registration area "" to "NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. In this case, UE_A10 may store the "received second rejected S-NSSAI" in the "second rejected NSSAI # 1 associated with PLMN # 1 and PLMN # 2 and the current registration area".

Furthermore, if the TAI contained in the TAI list indicating the current registration area belongs to EPLMN, UE_A10 will set the S-NSSAI associated with the received rejection reason value "S-NSSAI not possible in the current registration area" to "TAI". It may be stored as a "second rejected NSSAI" associated with the EPLMN to which the TAI contained in the list belongs and the current access type.

Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is the "received second rejected S-". The "NSSAI" may be stored only in the "one second rejected NSSAI associated with the RPLMN and the current access type". In other words, even if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the UE_A10 will display the "received second rejected S-NSSAI" in the different one or more. It does not have to be remembered as the second rejected NSSAI associated with multiple PLMNs.

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will store the "RPLMN and one second rejected NSSAI associated with the current access type" that the UE_A10 remembers. It may be replaced with "received second rejected S-NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 1 which is EPLMN. If UE_A10 remembers and / or adds the "received second rejected S-NSSAI" only to the "second rejected NSSAI # 1 associated with PLMN # 1 and the current access type". good.

In addition, if UE_A10 receives the rejection reason value "S-NSSAI not possible due to NSSAA failure or cancellation" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the S-NSSAI, the current S-NSSAI. May be added to the third rejection NSSAI associated with the PLMN.

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "allowed NSSAI stored by the UE_A10 and associated with the current PLMN".

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when the UE_A10 receives the rejected NSSAI, the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI that the UE_A10 remembers and is associated with all PLMNs". .. Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Furthermore, when the UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can.

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when the UE_A10 receives the rejected NSSAI, the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI that the UE_A10 remembers and is associated with all PLMNs". .. Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Further, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can. Further, when UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the EPLMN".

In addition, each process that the UE shown above executes based on the reception of each identification information may be executed during this procedure or after the completion of this procedure, or may be executed based on the completion of this procedure after the completion of this procedure. good.

It should be noted that the AMF determines which of the 10th to 15th identification information is included in the control message, each of the received identification information and / or the subscriber information, and / or the 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 control messages via 5G AN (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 also send a registration completion message to AMF via 5G AN (gNB) as a response message to the registration acceptance message if 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. , Based on the transmission and reception of the registration refusal message, the UE transitions or maintains the state (RM_DEREGISTERED state, or 5GMM-DEREGISTERED state) that is not registered in the network on the access that received the registration refusal message to the current PLMN. 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.

Further, each device may perform processing based on the information transmitted / 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.

In addition, 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.

In addition, the UE may delete one or more NSSAIs to remember based on the completion of the registration process. 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.

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

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

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

[3.3. Network Slice-Specific Authentication and Authorization Procedure]
Next, the Network Slice-Specific Authentication and Authorization (NSSAA) procedure will be described with reference to FIG. Hereinafter, the NSSAA procedure is also referred to as this procedure. This procedure may be a procedure for the core network to carry out UE authentication and approval procedures for slices that require NSSAA procedures. Here, the certification procedure and the approval procedure may be a recertification procedure and a reapproval procedure.

This procedure is a procedure performed by the PLMN and may be performed on a per S-NSSAI (mapped S-NSSAI) and / or per UE subject to the NSSAA procedure. This procedure may be executed when the registration procedure is completed.

This procedure may be initiated by AMF140. For example, AMF140 may initiate this procedure based on the receipt of a registration request message from UE_A10. The AMF140 remembers that at least one S-NSSAI or S-NSSAI mapped S-NSSAI requested by UE_A10 is an S-NSSAI that requires NSSAA procedures, and also remembers the NSSAA results of that S-NSSAI. If not, you may start this procedure. Here, the result of NSSAA may be information indicating that NSSAA has succeeded, information indicating that NSSAA has failed, or both. In addition, the information indicating the success of NSSAA may be allowed NSSAI. In other words, if the S-NSSAI is remembered as an allowed NSSAI, the AMF140 may recognize that the S-NSSAI's NSSAA was successful and may retain the NSSAA results.

Alternatively, AMF140 may initiate this procedure at the request of AAA-S181. For example, based on the result of the NSSAA procedure already executed, AAA-S181 again executes NSSAA against the S-NSSAI while AMF140 and / or NW manages S-NSSAI as allowed NSSAI. AMF may initiate this procedure at the request of AAA-S181. In this case, this procedure may be an NSSAA procedure initiated by AAA-S.

This procedure will be described below. The AMF140 sends an EAP ID request message to UE_A10 via 5G AN (or gNB or non-3GPP access) (S700). The EAP ID request message may be sent by being included in the authentication request message which is a NAS message, or may be an authentication request message which is a NAS message. The authentication request message, which is a NAS message, may be a 5GS NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message. The AMF140 transmits one or more S-NSSAIs corresponding to the EAP ID request message or the authentication request message including the EAP ID request message. Here, the S-NSSAI may be the HPLMN S-NSSAI or the mapped S-NSSAI.

Based on the transmission of the EAP ID request message, the AMF140 requests UE_A10 for one or more EAP IDs as UE identification information used to execute NSSAA for one or more S-NSSAIs.

UE_A10 sends an EAP ID response message to the AMF140 based on the receipt of the EAP ID request message and / or the reception of the S-NSSAI and / or the authentication request message (S702). The EAP ID response message may be sent by being included in the authentication response message which is a NAS message, or may be an authentication response message which is a NAS message. The authentication response message, which is a NAS message, may be a 5GS NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message. UE_A10 may send the EAP ID response message or the authentication request message including the EAP ID response message including the S-NSSAI received from the AMF140. UE_A10 may send the EAP ID response message including the EAP ID, which is the identification information of the UE corresponding to the S-NSSAI received from the AMF140. Note that UE_A10 may include a plurality of EAP IDs and a plurality of S-NSSAIs in the EAP ID response message, and each EAP ID and each S-NSSAI may be transmitted in association with each other.

The AMF140 sends an NSSAA authentication request message to AAA-S181 via AUSF180 based on the receipt of the EAP ID response message from UE_A10 and / or the EAPID and / or the NAS message authentication response message (S704, S706). ). The AM140F may include the EAP ID response message received from UE_A10 in the NSSAA authentication request message and send it to AUSF180 and / or AAA-S181, or the EAP ID and / contained in the EAP ID response message received from UE_A10. Alternatively, S-NSSAI may be included in the NSSAA authentication request message and sent to AUSF180 and / or AAA-S181.

The NSSAA authentication request message sent from AMF140 to AUSF180 and the NSSAA authentication request message sent from AUFF180 to AAA-S181 may be the same message or different messages. Specifically, the AUSF180 may forward the NSSAA authentication request message received from the AMF140 to the AAA-S181, or the EAP ID and / or S-NSSAI contained in the authentication request message received from the AMF140 is the NSSAA authentication request. It may be included in the message and sent to AAA-S181.

AAA-S181 initiates the process of exchanging messages required for authentication between UE_A10 and AAA-S181 based on the receipt of the NSSAA authentication request message and / or at least one piece of information contained in the NSSAA authentication request message. Good (S708). The message used for the message exchange procedure between AAA-S181 and UE_A10 may be an EAP message.

Next, AAA-S181 sends an NSSAA authentication response message to AMF140 via AUSF180 as a response to the authentication request message received from AMF140 (S710, S712).

The NSSAA authentication response message transmitted from AAA-S181 to AUFF180 and the NSSAA authentication response message transmitted from AUSF180 to AMF140 may be the same message or different messages. Specifically, the AUSF180 may forward the NSSAA authentication response message received from the AAA-S181 to the AAA-S181, and the authentication result and / or the S-NSSAI included in the authentication response message received from the AAA-S181. May be included in the NSSAA authentication response message and sent to AMF140.

The AUSF180 sends the NSSAA authentication response message including the authentication result and S-NSSAI. Here, the authentication result may be information indicating success or failure. Here, the S-NSSAI included in the NSSAA authentication response message may be the HPLMN S-NSSAI or the mappedS-NSSAI. The AMF140 sends an authentication result message to UE_A10 based on the reception of the NSSAA authentication response message (S714). The AMF140 may send the authentication result message including the NSSAA authentication response message or the authentication result and S-NSSAI contained in the NSSAA authentication response message.

The authentication result message may be a 5GS NETWORKSLICE-SPECIFIC AUTHENTICATION RESULT message, or may be included in the NETWORKSLICE-SPECIFIC AUTHENTICATION RESULT message and sent.

Each device may complete this procedure based on the transmission and reception of the authentication result message. Each device may update the stored information based on the information transmitted and received in this procedure based on the completion of this procedure. Specifically, AMF140 and / or NW may store the authentication result for each S-NSSAI based on the transmission / reception of the authentication result. For example, when AMF140 and / or NW sends and receives "success" as an authentication result, it is associated with S-NSSAI sent and received together with the authentication result, and is stored as UE information as the state in which NSSAA is "successful". good. Similarly, when AMF140 and / or NW sends and receives a "failure" as an authentication result, it associates it with the S-NSSAI sent and received together with the authentication result and stores it as UE information as the state in which NSSAA is "failed". You can do it.

Further, if this procedure is a procedure started based on the reception of the registration request message from UE_A10, the AMF140 may update the allowed NSSAI and / or the rejected NSSAI for the UE based on the transmission / reception of the authentication result. Specifically, for example, when the AMF140 sends and receives "success" as the authentication result, the S-NSSAI sent and received together with the authentication result is included in the allowed NSSAI, or the mapped S-NSSAI of the S-NSSAI included in the allowed NSSAI. It may be memorized as, or "allowed" may be associated with the received S-NSSAI and memorized. Similarly, when the AMF140 sends and receives "failure" as the authentication result, the S-NSSAI sent and received together with the authentication result is used as the third rejected NSSAI or as the mapped S-NSSAI of the S-NSSAI included in the third rejected NSSAI. It may be memorized, or it may be memorized by associating "rejected" with the received S-NSSAI. Furthermore, when AMF sends and receives "failure" or "success" as the authentication result, the S-NSSAI sent and received by UE_A10 together with the authentication result is included in the pending NSSAI, or the mapped S of the S-NSSAI included in the pending NSSAI. -If remembered as NSSAI, UE_A10 may remove the S-NSSAI from the pending NSSAI, or remove the S-NSSAI associated with the S-NSSAI from the pending NSSAI.

In addition, the UE may store the authentication result for each S-NSSAI based on the transmission / reception of the authentication result. Specifically, for example, when the UE sends and receives "success" as the authentication result, it is associated with the S-NSSAI sent and received together with the authentication result, and is stored as the UE information as the state in which NSSAA is "successful". good. Similarly, when the UE sends and receives a "failure" as an authentication result, it may be associated with the S-NSSAI sent and received together with the authentication result and stored as UE information as a state in which NSSAA is "failed".

In addition, each device may perform processing based on the update of the stored information based on the completion of this procedure. For example, based on the completion of this procedure, AFM will start the UE setting update procedure or the network-initiated non-registration procedure when there is a change in the allowed NSSAI for the UE and / or the S-NSSAI included in the rejected NSSAI. You may. The AMF may use the UE configuration update procedure to notify the UE of the new allowed NSSAI and the new rejected NSSAI. The AMF may notify the UE of the new rejected NSSAI using a network-initiated non-registration procedure.

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

Further, a device in the core network such as AMF may start this procedure based on the update of the network setting and / or the update of the 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, the AMF140 initiates the UE configuration update procedure (S800) by sending a Configuration update command message to UE_A10 via 5G AN120 (or gNB).

The AMF140 sends the configuration update command message including one or more of each NSSAI related to UE_A10 (hereinafter, means configured NSSAI, and allowed NSSAI, and rejected NSSAI, and pending NSSAI, and the first NSSAI). You may. The AMF may indicate the new UE setting information or request the update of the UE setting information by transmitting one or more of each NSSAI. 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, the AMF140 may send the configuration update command message with a TAI list indicating the new registration area.

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.

In addition, AMF140 includes each NSSAI, TAI list in the setting update command message, each received identification information and / or subscriber information, and / or network capability information, and / or operator policy, and / or It may be selected and determined based on 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.

UE_A10 receives a configuration update command message from AMF140 via 5G AN120 (or gNB) (S800). UE_A10 may update the UE configuration information based on the configuration update command message and / or the identification information contained in the configuration update command message.

Also, when UE_A10 receives a TAI list, the received TAI list may be enabled, and if UE_A10 already remembers a valid TAI list, the old TAI list may be deleted or invalidated. Hereinafter, a valid TAI list may be expressed as a registration area. If UE_A10 does not store a valid TAI list and does not receive a TAI list from the core network during this procedure, the valid TAI list may not be stored.

In addition, UE_A10 may appropriately store each received NSSAI. Specifically, when UE_A10 receives a configured NSSAI, the received configured NSSAI may be stored as "configured NSSAI associated with the current PLMN". That is, UE_A10 may replace "configured NSSAI associated with the current PLMN stored by UE_A10" with "received configured NSSAI".

Furthermore, when the UE_A10 receives the configured NSSAI, the mapped S-NSSAI of the S-NSSAI included in the "configured NSSAI associated with the current PLMN stored in the UE_A10" may be deleted. Further, if the "received configured NSSAI" contains one or more mapped S-NSSAIs, UE_A10 may store one or more of those mapped S-NSSAIs.

Furthermore, when UE_A10 receives a configured NSSAI, it may delete "rejected NSSAI remembered by UE_A10 and associated with the current PLMN".

Alternatively, when the UE_A10 receives a configured NSSAI, the "first rejected NSSAI remembered by the UE_A10 and associated with the current PLMN" and the second rejected NSSAI remembered by the UE_A10 and associated with the current PLMN. And "Third rejected NSSAI remembered by UE_A10 and associated with the current PLMN" may be deleted.

In addition, when the UE_A10 receives a configured NSSAI, "the first NSSAI remembered by the UE_A10" and / or "the first NSSAI remembered by the UE_A10 and associated with the current PLMN", and / or one or Multiple "first NSSAIs remembered by UE_A10 and associated with the current PLMN EPLMN" may be deleted.

In addition, when UE_A10 receives a configured NSSAI, "pending NSSAI remembered by UE_A10" and / or "pending NSSAI remembered by UE_A10 and associated with the current PLMN", and / or one or more "UE_A10". May delete the "first pending NSSAI" that is remembered and associated with the current PLMN EPLMN.

Furthermore, when UE_A10 receives an allowed NSSAI, it may store the received allowed NSSAI as "allowed NSSAI associated with the current PLMN and the current access type". That is, UE_A10 may replace the "allowed NSSAI associated with the current PLMN and the current access type" stored by UE_A10 with the "received allowed NSSAI".

Furthermore, if UE_A10 receives a TAI list and allowed NSSAI from new AMF141, and if at least one TAI contained in the TAI list belongs to EPLMN, UE_A10 will refer to the received allowed NSSAI as "EPLMN to which TAI contained in TAI list belongs". And the current access type, and may be remembered as "allowed NSSAI" associated with.

Or, if UE_A10 does not receive the TAI list and receives allowed NSSAI from new AMF141, and if the TAI included in the TAI list that the UE has received and stored in advance belongs to EPLMN, UE_A10 receives allowed NSSAI. May be stored as "allowed NSSAI associated with the EPLMN to which the TAI in the TAI list belongs and the current access type".

That is, if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs, and UE_A10 sets the "received allowed NSSAI" to each " It may be stored in one allowed NSSAI associated with one of the different PLMNs and the current access type.

In other words, the UE_A10 may store the "received allowed NSSAI" in the "allowed NSSAI associated with the PLMN to which the TAI included in the registration area stored by the UE_A10 belongs and the current access type".

Furthermore, if multiple TAIs contained in the registration area stored by UE_A10 belong to different PLMNs, UE_A10 will be stored with each "PLMN to which the TAI contained in the registration area belongs and the current access type" stored by UE_A10. The "allowed NSSAI" associated with, may be replaced with the "received allowed NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. If UE_A10, the "received allowed NSSAI" is "allowed NSSAI # 1 associated with PLMN # 1 and the current access type" and "allowed NSSAI associated with PLMN # 2 and the current access type". You may memorize it as "# 2".

Alternatively, if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs, and UE_A10 reads "received allowed NSSAI" as "received allowed NSSAI". It may be stored in one allowed NSSAI associated with the different PLMNs to which the TAIs contained in the registration area belong and the current access type.

Further / or when two or more TAIs contained in the registration area belong to more than one PLMN, UE_A10 is stored in the UE_A10 "one or more PLMNs to which the TAI contained in the registration area belongs, the current access type, and / or the current access type. One allowed NSSAI associated with may be replaced with a "received allowed NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 1 which is EPLMN. In this case, UE_A10 may store the "received allowed NSSAI" in the "allowed NSSAI # 1 associated with PLMN # 1 and PLMN # 2 and the current access type".

Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs, and UE_A10 reads "received allowed NSSAI" as "received allowed NSSAI". Only one allowed NSSAI associated with the RPLMN and the current access type may be stored. In other words, even if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the UE_A10 will transfer the "received allowed NSSAI" to the different PLMNs. It does not have to be remembered as the associated allowed NSSAI.

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 "receives one allowed NSSAI associated with the RPLMN and the current access type" stored by the UE_A10. You may replace it with "allowed NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 1 which is EPLMN. In this case, UE_A10 may only store the "received allowed NSSAI" in the "allowed NSSAI # 1 associated with PLMN # 1 and the current access type".

When UE_A10 stores the allowed NSSAI, the allowed NSSAI may be stored in association with the registration area, or the S-NSSAI included in the allowed NSSAI may be stored in association with the registration area.

Furthermore, when UE_A10 receives allowed NSSAI, it may delete the mapped S-NSSAI of S-NSSAI included in "allowed NSSAI deleted based on reception" or "old allowed NSSAI updated based on reception". Furthermore, if the "received allowed NSSAI" includes mapped S-NSSAI, UE_A10 may store one or more of the mapped S-NSSAI.

Furthermore, when UE_A10 receives allowed NSSAI, "rejected NSSAI remembered by UE_A10 and associated with the current PLMN" may be deleted.

Specifically, when UE_A10 receives an allowed NSSAI, "the first rejected NSSAI remembered by UE_A10 and associated with the current PLMN" and "UE_A10 remembered and associated with the current PLMN," "Second rejected NSSAI" and "second rejected NSSAI remembered by UE_A10 and associated with the current PLMN and current registration area" and "second rejected NSSAI remembered by UE_A10 and associated with the current PLMN" The S-NSSAI contained in the received allowed NSSAI may be deleted from at least one of "3 rejected NSSAI", or the S-NSSAI contained in the allowed NSSAI received from all NSSAI may be deleted.

Specifically, when UE_A10 receives an allowed NSSAI, it is associated with the current registration area and further received from the "second rejected NSSAI remembered by the UE_A10 and associated with the current PLMN". You may delete the S-NSSAI contained in.

Furthermore, when the UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives an allowed NSSAI, the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI may be deleted from "pending NSSAI remembered by UE_A10 and associated with all PLMNs". .. Further, when UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Furthermore, when the UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can.

Furthermore, when UE_A10 receives a rejected NSSAI, it stores the S-NSSAI contained in the received rejected NSSAI as "rejected NSSAI associated with the current PLMN" based on the rejection reason value associated with that S-NSSAI. You can. That is, UE_A10 may add "S-NSSAI included in the received rejected NSSAI" to the "rejected NSSAI associated with the current PLMN" stored in UE_A10.

Specifically, if UE_A10 receives the rejection reason value "S-NSSAI not possible with the current PLMN or SNPN" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the S-NSSAI now. May be added to the first rejection NSSAI associated with the PLMN of.

Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI not possible in the current registration area" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the "received rejected S-NSSAI". , "Second rejection NSSAI associated with the current PLMN and the current registration area" may be added.

When UE_A10 receives the TAI list together with the rejected NSSAI, the current registration area is indicated by the received TAI list. On the other hand, if UE_A10 did not receive the TAI list with rejected NSSAI, the current registration area is indicated by the TAI list that UE_A10 previously received and stored.

If the TAI contained in the current registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is the "reason for refusal value" current registration area. The rejected S-NSSAI received in association with the "S-NSSAI" which is not possible in the second is associated with each "PLMN of one or more different PLMNs and the current registration area". It may be stored and / or added to "rejected NSSAI".

Furthermore, if one or more TAIs contained in the registration area belong to different PLMNs, UE_A10 will be stored in each "PLMN to which the TAI contained in the registration area belongs and the current access type." The "rejected S-NSSAI received in association with the rejection reason value" S-NSSAI which is not possible in the current registration area "" may be added to the associated second rejected NSSAI and stored.

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. If UE_A10, the "received second rejected S-NSSAI" is referred to as "the second rejected NSSAI # 1 associated with PLMN # 1 and the current registration area" and "PLMN # 2 and the current registration". It may be remembered in the second rejected NSSAI # 2 associated with the area.

Alternatively, if the TAI contained in the registration area belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is not possible in the "reason for refusal value" current registration area. The "rejected S-NSSAI" received in association with the "S-NSSAI" may be stored in the "one second rejected NSSAI associated with the different PLMN and the current registration area". ..

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will store one second rejected associated with the "these multiple PLMNs and the current access type" that the UE_A10 remembers. You may add and memorize "Rejected S-NSSAI received in association with the rejection reason value" S-NSSAI which is not possible in the current registration area "" to "NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. In this case, UE_A10 may store the "received second rejected S-NSSAI" in the "second rejected NSSAI # 1 associated with PLMN # 1 and PLMN # 2 and the current registration area".

Furthermore, if the TAI contained in the TAI list indicating the current registration area belongs to EPLMN, UE_A10 will set the S-NSSAI associated with the received rejection reason value "S-NSSAI not possible in the current registration area" to "TAI". It may be stored as a "second rejected NSSAI" associated with the EPLMN to which the TAI contained in the list belongs and the current access type.

Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is the "received second rejected S-". The "NSSAI" may be stored only in the "one second rejected NSSAI associated with the RPLMN and the current access type". In other words, even if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the UE_A10 will display the "received second rejected S-NSSAI" in the different one or more. It does not have to be remembered as the second rejected NSSAI associated with multiple PLMNs.

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will store the "RPLMN and one second rejected NSSAI associated with the current access type" that the UE_A10 remembers. It may be replaced with "received second rejected S-NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 1 which is EPLMN. If UE_A10 remembers and / or adds the "received second rejected S-NSSAI" only to the "second rejected NSSAI # 1 associated with PLMN # 1 and the current access type". good.

In addition, if UE_A10 receives the rejection reason value "S-NSSAI not possible due to NSSAA failure or cancellation" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the S-NSSAI, the current S-NSSAI. May be added to the third rejection NSSAI associated with the PLMN.

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "allowed NSSAI stored by the UE_A10 and associated with the current PLMN".

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when the UE_A10 receives the rejected NSSAI, the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI that the UE_A10 remembers and is associated with all PLMNs". .. Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Furthermore, when the UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can.

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when the UE_A10 receives the rejected NSSAI, the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI that the UE_A10 remembers and is associated with all PLMNs". .. Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Further, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can. Further, when UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the EPLMN".

In addition, each process that the UE shown above executes based on the reception of each _A10 identification information may be executed during this procedure or after the completion of this procedure, or is executed based on the completion of this procedure after the completion of this procedure. You may. In addition, 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 (S802).

The AMF140 receives a configuration update completion message via 5G AN (gNB) when UE_A10 sends a configuration update completion command message (S802). 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.

Further, 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 identification information received together with the setting information command message based on the completion of this procedure, or 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 applied by the UE, and the UE is executing. You can instruct to stop or change the function.

[3.5. Network-initiated non-registration procedure]
Next, the network-initiated de-registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the non-registration procedure initiated by the network. The network-initiated non-registration procedure is manually performed by the network to access network_A and / or core network_A, access network_B, and / or core network_B, and / or DN, and / or PDN. This is a procedure for canceling registration. This procedure may be a procedure for mobility management that the network takes the initiative to execute for the UE registered in the network.

AMF can execute this procedure at any time as long as the UE is registered in the network (RM-REGISTERED state or 5GMM-REGISTEDED state). For example, AMF may start this procedure with the update of UE registration information. More specifically, the AMF may initiate this procedure when the UE registration information is no longer allowed NSSAI based on the completion of the NSSAA procedure. In other words, AMF may initiate this procedure if there is no S-NSSAI allowed to the UE and there are no plans to add S-NSSAI to allowed NSSAI in the future due to other procedures (eg NSSAA procedures).

First, the AMF140 may initiate this procedure by sending a De-registration request message to UE_A10 (S900). Here, the non-registration request 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 5G AN (gNB).

The AMF140 may send the non-registration request message including at least one identification information of each NSSAI (hereinafter, rejected NSSAI, and pending NSSAI, and the first NSSAI). The AMF may send the non-registration request message with additional reason value and / or information indicating the access type to be unregistered. Here, the reason value may be 5 GMM cause. In addition, if the procedure is initiated based on the results of the NSSAA procedure, or upon completion of the NSSAA, the reason value may be a value indicating that no network slices are available. In that case, 5GS 5GMM cause value # 62 “No network slices available” may be used.

The AMF140 may indicate that the network does not support each function by transmitting these identification information and / or an unregistered message, or may request a transition to the unregistered state. However, the change of AMF140 may be notified, the registration procedure may be continuously instructed, or the combined information may be shown. 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.

UE_A10 recognizes the rejected S-NSSAI and the reason for rejection based on the reception of at least one of each NSSAI and / or the reception of the reason value and / or the reception of other identification information and / or the state of the UE, and The memory and the behavior of the UE may be determined.

Furthermore, when UE_A10 receives a rejected NSSAI, it stores the S-NSSAI contained in the received rejected NSSAI as "rejected NSSAI associated with the current PLMN" based on the rejection reason value associated with that S-NSSAI. You can. That is, UE_A10 may add "S-NSSAI included in the received rejected NSSAI" to the "rejected NSSAI associated with the current PLMN" stored in UE_A10.

Specifically, if UE_A10 receives the rejection reason value "S-NSSAI not possible with the current PLMN or SNPN" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the S-NSSAI now. May be added to the first rejection NSSAI associated with the PLMN of.

Furthermore, if UE_A10 receives the rejection reason value "S-NSSAI not possible in the current registration area" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the "received rejected S-NSSAI". , "Second rejection NSSAI associated with the current PLMN and the current registration area" may be added.

When UE_A10 receives the TAI list together with the rejected NSSAI, the current registration area is indicated by the received TAI list. On the other hand, if UE_A10 did not receive the TAI list with rejected NSSAI, the current registration area is indicated by the TAI list that UE_A10 previously received and stored.

If the TAI contained in the current registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is the "reason for refusal value" current registration area. The rejected S-NSSAI received in association with the "S-NSSAI" which is not possible in the second is associated with each "PLMN of one or more different PLMNs and the current registration area". It may be stored and / or added to "rejected NSSAI".

Furthermore, if one or more TAIs contained in the registration area belong to different PLMNs, UE_A10 will be stored in each "PLMN to which the TAI contained in the registration area belongs and the current access type." The "rejected S-NSSAI received in association with the rejection reason value" S-NSSAI which is not possible in the current registration area "" may be added to the associated second rejected NSSAI and stored.

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. If UE_A10, the "received second rejected S-NSSAI" is referred to as "the second rejected NSSAI # 1 associated with PLMN # 1 and the current registration area" and "PLMN # 2 and the current registration". It may be remembered in the second rejected NSSAI # 2 associated with the area.

Alternatively, if the TAI contained in the registration area belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is not possible in the "reason for refusal value" current registration area. The "rejected S-NSSAI" received in association with the "S-NSSAI" may be stored in the "one second rejected NSSAI associated with the different PLMN and the current registration area". ..

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will store one second rejected associated with the "these multiple PLMNs and the current access type" that the UE_A10 remembers. You may add and memorize "Rejected S-NSSAI received in association with the rejection reason value" S-NSSAI which is not possible in the current registration area "" to "NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 2 which is EPLMN. In this case, UE_A10 may store the "received second rejected S-NSSAI" in the "second rejected NSSAI # 1 associated with PLMN # 1 and PLMN # 2 and the current registration area".

Furthermore, if the TAI contained in the TAI list indicating the current registration area belongs to EPLMN, UE_A10 will set the S-NSSAI associated with the received rejection reason value "S-NSSAI not possible in the current registration area" to "TAI". It may be stored as a "second rejected NSSAI" associated with the EPLMN to which the TAI contained in the list belongs and the current access type.

Alternatively, if the TAI contained in the registration area stored by UE_A10 belongs to one or more PLMNs different from the RPLMN, the different one or more PLMNs are EPLMNs and UE_A10 is the "received second rejected S-". The "NSSAI" may be stored only in the "one second rejected NSSAI associated with the RPLMN and the current access type". In other words, even if the TAI contained in the registration area stored in the UE_A10 belongs to one or more PLMNs different from the RPLMN, the UE_A10 will display the "received second rejected S-NSSAI" in the different one or more. It does not have to be remembered as the second rejected NSSAI associated with multiple PLMNs.

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will store the "RPLMN and one second rejected NSSAI associated with the current access type" that the UE_A10 remembers. It may be replaced with "received second rejected S-NSSAI".

Specifically, when the registration area stored by UE_A10 includes TAI # 1 and TAI # 2, TAI # 1 belongs to PLMN # 1 which is RPLMN, and TAI # 2 belongs to PLMN # 1 which is EPLMN. If UE_A10 remembers and / or adds the "received second rejected S-NSSAI" only to the "second rejected NSSAI # 1 associated with PLMN # 1 and the current access type". good.

In addition, if UE_A10 receives the rejection reason value "S-NSSAI not possible due to NSSAA failure or cancellation" and the rejected S-NSSAI associated with the rejection reason value, UE_A10 will receive the S-NSSAI, the current S-NSSAI. May be added to the third rejection NSSAI associated with the PLMN.

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "allowed NSSAI stored by the UE_A10 and associated with the current PLMN".

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when the UE_A10 receives the rejected NSSAI, the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI that the UE_A10 remembers and is associated with all PLMNs". .. Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Furthermore, when the UE_A10 receives the allowed NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Alternatively, when UE_A10 receives an allowed NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can.

Furthermore, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "pending NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when the UE_A10 receives the rejected NSSAI, the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI may be deleted from the "pending NSSAI that the UE_A10 remembers and is associated with all PLMNs". .. Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with EPLMN".

Further, when the UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received rejected NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the current PLMN". Furthermore, when UE_A10 receives a rejected NSSAI, it removes the mapped S-NSSA or S-NSSAI contained in the received allowed NSSAI from the "first NSSAI that UE_A10 remembers and is associated with all PLMNs". You can. Further, when UE_A10 receives the rejected NSSAI, the S-NSSAI included in the received allowed NSSAI may be deleted from the "first NSSAI stored by the UE_A10 and associated with the EPLMN".

In addition, each process that the UE shown above executes based on the reception of each _A10 identification information may be executed during this procedure or after the completion of this procedure, or is executed based on the completion of this procedure after the completion of this procedure. You may.

UE_A10 receives a non-registration request message via 5G AN (gNB). UE_A10 can recognize the contents of various identification information included in the non-registration request message by receiving the non-registration request message.

UE_A10 may send a non-registration acceptance message (DEREGISTRAION ACCEPT message) to AMF140 via 5G AN (or gNB) upon receipt of the non-registration request message. The non-registration acceptance message is a NAS message sent and received on the N1 interface. The RRC message may also be a control message sent and received between the UE and 5G AN (or gNB).

Each device may transition to a state in which the UE is not registered in the network (RM_DEREGISTERED state, or 5GMM-DEREGISTERED state) based on the transmission / reception of the registration acceptance message. Further, the transition of each device to each state may be performed based on the completion of this procedure.

Further, each device may perform processing based on the information transmitted and received in this procedure based on the completion of the non-registration procedure. For example, UE_A10 may start the registration procedure based on the completion of the non-registration procedure.

[4. Embodiment in the present invention]
An embodiment of the present invention may be a combination of procedures described in one or more chapters three. For example, in the present embodiment, after the initial registration procedure described in Chapter 3 is completed, the NSSAA procedure may be executed and the UE setting update procedure may be executed. In addition, each device (UE and device in the core network) may perform one or more mobile and periodic registration procedures based on the completion of the initial registration procedure. Alternatively, after the initial registration procedure described in Chapter 3 is completed, the NSSAA procedure may be carried out and the network-initiated non-registration procedure may be carried out.

Hereinafter, a specific example of the embodiment of the present invention will be described. In addition, each device may carry out the behavior of a plurality of embodiments described below in combination.

Specifically, the behavior of each device during transmission / reception of allowed NSSAI may conform to the first embodiment, and the behavior of the second rejected NSSAI during transmission / reception may conform to the second embodiment. Alternatively, the behavior of each device during transmission / reception of the allowed NSSAI may conform to the first embodiment, and the behavior of the second rejected NSSAI during transmission / reception may conform to the third embodiment.

Alternatively, the behavior of each device during transmission / reception of the allowed NSSAI may conform to the second embodiment, and the behavior of the second rejected NSSAI during transmission / reception may conform to the first embodiment. The behavior of each device during transmission / reception of allowed NSSAI may conform to the second embodiment, and the behavior of each device during transmission / reception of the second rejected NSSAI may conform to the third embodiment.

Alternatively, the behavior of each device during transmission / reception of allowed NSSAI may conform to the third embodiment, and the behavior of the second rejected NSSAI during transmission / reception may conform to the first embodiment. The behavior of each device during transmission / reception of allowed NSSAI may conform to the third embodiment, and the behavior of the second rejected NSSAI during transmission / reception may conform to the second embodiment.

[4.1. First Embodiment]
Hereinafter, the first embodiment (hereinafter referred to as the present embodiment) will be described. In this embodiment, an example of the behavior of each device after transmission / reception of each NSSAI and the behavior of each device after the occurrence of PLMN change when the TA included in the current registration area belongs to a different PLMN. To explain.

In this embodiment, the UE can store the received allowed NSSAI in a plurality of allowed NSSAIs based on the current registration area. Further / or in this embodiment, the UE can store or add the S-NSSAI contained in the received second rejected NSSAI to the plurality of second rejected NSSAIs based on the current registration area.

Specifically, in the present embodiment, the UE is in the first registration procedure for the 3GPP access of PLMN # 1 by sending the first registration request message to the core network of PLMN # 1 on the 3GPP access. To start.

The UE may receive a first registration acceptance message or a first registration refusal message from PLMN # 1 (core network) during the first registration process.

Here, the first registration acceptance message or the first registration refusal message may include a TAI list indicating a registration area. If the first registration acceptance message or the first registration refusal message contains a new TAI list, the UE treats the TAI list as available (valid). If the UE remembers the old TAI list when it receives the new TAI list, the old TAI list is treated as deleted or unavailable.

If the first registration acceptance message or the second registration refusal message does not include the TAI list indicating the registration area, the UE treats the TAI list already stored as valid. Hereinafter, the area indicated by the TAI list valid after receiving the registration acceptance message or the registration refusal message is treated as the current registration area.

If the UE does not include a TAI list indicating the registration area in the first registration acceptance message or the second registration refusal message, and if the UE does not remember a valid registration area, the UE is a valid registration area. (TAI list) is not stored.

Hereinafter, the area indicated by the TAI list (if any) valid after receiving the first registration acceptance message or the first registration refusal message is treated as the current registration area.

For example, if the UE receives the allowed NSSAI contained in the first registration acceptance message, and if the current registration area also contains TAI # 1 belonging to PLMN # 1 and TAI # 2 belonging to PLMN # 2, the UE Can store the allowed NSSAI received in each of the allowed NSSAI # 1 associated with PLMN # 1 and the allowed NSSA # 2 associated with PLMN # 2.

Similarly, for example, when the UE receives the second rejected NSSAI contained in the first registration acceptance message or the first registration refusal message, the TAI # 1 and PLMN # belonging to PLMN # 1 are further added to the current registration area. If a TAI # 2 belonging to 2 is included, the UE receives the second rejected NSSAI # 1 associated with the PLMN # 1 and the second rejected NSSAI # 2 associated with the PLMN # 2, respectively. The S-NSSAI included in the second rejected NSSAI can be stored.

Here, if the first registration procedure is the initial registration procedure, the first registration refusal message does not include the TAI list indicating the registration area, but the second rejected NSSAI is included, the registration area where the UE is valid. The UE may store the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI # 3 associated with the PLMN # 1 based on not remembering.

Here, the S-NSSAI included in the second rejected NSSAI # 3 may be associated with the registration area and not stored, or may be associated with the dummy registration area information. Here, the dummy registration area information may be empty registration area information.

Alternatively, if the UE does not remember the current registration area, the second rejected NSSAI received by the UE from PLMN # 1 during the initial registration procedure does not have to be remembered.

The first registration procedure may be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and the behavior of the registration procedure described in Chapter 3 may be carried out.

The following behavior will be explained when at least TAI # 1 and TAI # 2 are included in the current registration area, and when TAI # 1 belongs to PLMN # 1 and TAI # 2 belongs to PLMN # 2. ..

Next, the UE undergoes a PLMN change with no change in the registration area. Specifically, for example, the case where the UE moves from TAI # 1 to TAI # 2 will be described.

After the UE moves from TAI # 1 to TAI # 2, a move or regular registration process occurs. Although the cause of this registration procedure is not particularly specified, it may be, for example, a registration procedure that occurs regularly.

The UE may carry out a second registration procedure for PLMN # 2 3GPP access based on TAI # 2 belonging to PLMN # 2. The UE may initiate the registration process by sending a second registration request message to PLMN # 2 (core network) that includes at least the first identification information.

Here, the UE may include the S-NSSAI included in the allowed NSSAI # 2 associated with the PLMN # 2 in the first identification information. Further, the UE may control the first identification information so as not to include the S-NSSAI contained in the second rejected NSSAI # 2 associated with the PLMN # 2. In other words, the S-NSSAI contained in the first identification information does not have to be included in the second rejected NSSAI # 2 associated with PLMN # 2.

PLMN # 2 (core network) may send a second registration acceptance message or a second registration refusal message to the UE based on the receipt of the second registration request message.

The UE performs the same behavior as the first registration procedure based on the reception of the second registration acceptance message or the second registration refusal message.

The second registration procedure may also be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and the behavior of the registration procedure described in Chapter 3 may be carried out.

As described above, in the present embodiment, each device stores the received allowed NSSAI and / or the second rejected NSSAI in the plurality of allowed NSSAI and / or the plurality of second rejected NSSAI based on the current registration area. be able to.

In this embodiment, only the registration procedure has been described, but other procedures may be used. Specifically, instead of the registration acceptance message or registration refusal message, the UE receives the allowed NSSAI and / or the second rejected NSSAI in the setting update command message during the UE setting update procedure described in Chapter 3, and each NSSAI. It may behave based on the reception of.

Alternatively, the UE receives the allowed NSSAI and / or the second rejected NSSAI in the non-registration request message during the non-registration procedure initiated by the network described in Chapter 3 instead of the registration acceptance message or registration refusal message, and each NSSAI It may behave based on reception.

[4.1. Second Embodiment]
Hereinafter, the second embodiment (hereinafter referred to as the present embodiment) will be described. In this embodiment, an example of the behavior of each device after transmission / reception of each NSSAI and the behavior of each device after the occurrence of PLMN change when the TA included in the current registration area belongs to a different PLMN. To explain.

In the first embodiment, the received allowed NSSAI is stored in a plurality of allowed NSSAIs based on the current registration area, whereas in the present embodiment, the UE stores the received allowed NSSAI based on the current registration area. It can be stored in one allowed NSSAI associated with multiple PLMNs.

Similarly, based on the first embodiment, the current registration area, the S-NSSAI contained in the received second rejected NSSAI is stored in the plurality of second rejected NSSAIs, whereas in the present embodiment, the S-NSSAI is stored in the plurality of second rejected NSSAIs. The UE can store or add the S-NSSAI contained in the received second rejected NSSAI to one second rejected NSSAI associated with multiple PLMNs based on the current registration area.

Specifically, in the present embodiment, the UE is in the first registration procedure for the 3GPP access of PLMN # 1 by sending the first registration request message to the core network of PLMN # 1 on the 3GPP access. To start.

The UE may receive a first registration acceptance message or a first registration refusal message from PLMN # 1 (core network) during the first registration process.

Here, the first registration acceptance message or the first registration refusal message may include a TAI list indicating a registration area. If the first registration acceptance message or the first registration refusal message contains a new TAI list, the UE treats the TAI list as available (valid). If the UE remembers the old TAI list when it receives the new TAI list, the old TAI list is treated as deleted or unavailable.

If the first registration acceptance message or the second registration refusal message does not include the TAI list indicating the registration area, the UE treats the TAI list already stored as valid. Hereinafter, the area indicated by the TAI list valid after receiving the registration acceptance message or the registration refusal message is treated as the current registration area.

If the UE does not include a TAI list indicating the registration area in the first registration acceptance message or the second registration refusal message, and if the UE does not remember a valid registration area, the UE is a valid registration area. (TAI list) is not stored.

Hereinafter, the area indicated by the TAI list (if any) valid after receiving the first registration acceptance message or the first registration refusal message is treated as the current registration area.

For example, if the UE receives the allowed NSSAI contained in the first registration acceptance message, and if the current registration area also contains TAI # 1 belonging to PLMN # 1 and TAI # 2 belonging to PLMN # 2, the UE Can store the received allowed NSSAI in the allowed NSSAI # 1 associated with PLMN # 1 and PLMN # 2.

Similarly, for example, when the UE receives the second rejected NSSAI contained in the first registration acceptance message or the first registration refusal message, the TAI # 1 and PLMN # belonging to PLMN # 1 are further added to the current registration area. If TAI # 2 belonging to 2 is included, the UE remembers the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI # 1 associated with PLMN # 1 and PLMN # 2. can do.

Here, if the first registration procedure is the initial registration procedure, the first registration refusal message does not include the TAI list indicating the registration area, but the second rejected NSSAI is included, the registration area where the UE is valid. The UE may store the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI # 3 associated with the PLMN # 1 based on not remembering.

Here, the S-NSSAI included in the second rejected NSSAI # 3 may be associated with the registration area and not stored, or may be associated with the dummy registration area information. Here, the dummy registration area information may be empty registration area information.

Alternatively, if the UE does not remember the current registration area, the second rejected NSSAI received by the UE from PLMN # 1 during the initial registration procedure does not have to be remembered.

The first registration procedure may be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and the behavior of the registration procedure described in Chapter 3 may be carried out.

The following behavior will be explained when at least TAI # 1 and TAI # 2 are included in the current registration area, and when TAI # 1 belongs to PLMN # 1 and TAI # 2 belongs to PLMN # 2. ..

Next, the UE undergoes a PLMN change with no change in the registration area. Specifically, for example, the case where the UE moves from TAI # 1 to TAI # 2 will be described.

After the UE moves from TAI # 1 to TAI # 2, a move or regular registration process occurs. Although the cause of this registration procedure is not particularly specified, it may be, for example, a registration procedure that occurs regularly.

The UE may carry out a second registration procedure for PLMN # 2 3GPP access based on TAI # 2 belonging to PLMN # 2. The UE may initiate the registration process by sending a second registration request message to PLMN # 2 (core network) that includes at least the first identification information.

Here, the UE may include the S-NSSAI included in the allowed NSSAI # 1 associated with the PLMN # 1 and the PLMN # 2 in the first identification information. Further, the UE may control the first identification information so that the S-NSSAI included in the second rejected NSSAI # 1 associated with PLMN # 1 and PLMN # 2 is not included. In other words, the S-NSSAI contained in the first identification information does not have to be included in the second rejected NSSAI # 1 associated with PLMN # 1 and PLMN # 2.

PLMN # 2 (core network) may send a second registration acceptance message or a second registration refusal message to the UE based on the receipt of the second registration request message.

The UE performs the same behavior as the first registration procedure based on the reception of the second registration acceptance message or the second registration refusal message.

The second registration procedure may also be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and the behavior of the registration procedure described in Chapter 3 may be carried out.

As described above, in the present embodiment, each device transfers the received allowed NSSAI and / or the second rejected NSSAI with one allowed NSSAI and / or a plurality of PLMNs associated with the plurality of PLMNs based on the current registration area. Can be stored in one associated second rejected NSSAI.

In this embodiment, only the registration procedure has been described, but other procedures may be used. Specifically, instead of the registration acceptance message or registration refusal message, the UE receives the allowed NSSAI and / or the second rejected NSSAI in the setting update command message during the UE setting update procedure described in Chapter 3, and each NSSAI. It may behave based on the reception of.

Alternatively, the UE receives the allowed NSSAI and / or the second rejected NSSAI in the non-registration request message during the non-registration procedure initiated by the network described in Chapter 3 instead of the registration acceptance message or registration refusal message, and each NSSAI It may behave based on reception.

[4.1. Third Embodiment]
Hereinafter, the third embodiment (hereinafter referred to as the present embodiment) will be described. In this embodiment, an example of the behavior of each device after transmission / reception of each NSSAI and the behavior of each device after the occurrence of PLMN change when the TA included in the current registration area belongs to a different PLMN. To explain.

In the first embodiment, the received allowed NSSAI is stored in the plurality of allowed NSSAIs based on the current registration area, and in the second embodiment, the UE stores the received allowed NSSAI in the plurality of allowed NSSAIs based on the current registration area. Whereas the one allowed NSSAI associated with the PLMN is stored, in the present embodiment, the received allowed NSSAI is stored in one allowed NSSAI belonging only to the current PLMN.

Similarly, in the first embodiment, the UE stores the S-NSSAI contained in the received second rejected NSSAI in the plurality of second rejected NSSAIs based on the current registration area, and in the second embodiment. The UE was able to store or add the S-NSSAI contained in the received second rejected NSSAI to one second rejected NSSAI associated with multiple PLMNs, based on the current registration area. On the other hand, in the present embodiment, the received S-NSSAI included in the second rejected NSSAI is stored in one second rejected NSSAI belonging only to the current PLMN.

Further, in the present embodiment, even if the UE is an allowed NSSAI belonging to a PLMN other than the PLMN (core network) to which the registration request message is sent, the TAI included in the registration area associated with the allowed NSSAI is currently present. When associated with a PLMN (destination PLMN), the registration request message may include the S-NSSAI included in the allowed NSSAI.

Further, in the present embodiment, when the UE sends a registration request message, if at least one TAI included in the current registration area belongs to a PLMN different from the destination of the registration request message, the UE is further sent to the different PLMN. When storing the associated second rejected NSSAI, the UE may implement a control that does not include the S-NSSAI contained in the second rejected NSSAI associated with the different PLMN in the registration request message.

Specifically, in the present embodiment, the UE is in the first registration procedure for the 3GPP access of PLMN # 1 by sending the first registration request message to the core network of PLMN # 1 on the 3GPP access. To start.

The UE may receive a first registration acceptance message or a first registration refusal message from PLMN # 1 (core network) during the first registration process.

Here, the first registration acceptance message or the first registration refusal message may include a TAI list indicating a registration area. If the first registration acceptance message or the first registration refusal message contains a new TAI list, the UE treats the TAI list as available (valid). If the UE remembers the old TAI list when it receives the new TAI list, the old TAI list is treated as deleted or unavailable.

If the first registration acceptance message or the second registration refusal message does not include the TAI list indicating the registration area, the UE treats the TAI list already stored as valid. Hereinafter, the area indicated by the TAI list valid after receiving the registration acceptance message or the registration refusal message is treated as the current registration area.

If the UE does not include a TAI list indicating the registration area in the first registration acceptance message or the second registration refusal message, and if the UE does not remember a valid registration area, the UE is a valid registration area. (TAI list) is not stored.

Hereinafter, the area indicated by the TAI list (if any) valid after receiving the first registration acceptance message or the first registration refusal message is treated as the current registration area.

For example, if the UE receives the allowed NSSAI contained in the first registration acceptance message, and if the current registration area also contains TAI # 1 belonging to PLMN # 1 and TAI # 2 belonging to PLMN # 2, the UE Can store the allowed NSSAI received in each of the allowed NSSAI # 1 associated with PLMN # 1 and PLMN # 2 and the allowed NSSA # 2 associated with PLMN # 2.

Similarly, for example, when the UE receives the second rejected NSSAI contained in the first registration acceptance message or the first registration refusal message, the TAI # 1 and PLMN # belonging to PLMN # 1 are further added to the current registration area. If a TAI # 2 belonging to 2 is included, the UE will have a second rejected NSSAI # 1 associated with PLMN # 1 and PLMN # 2 and a second rejected NSSAI # 2 associated with PLMN # 2. In addition, the S-NSSAI included in the second rejected NSSAI received in each can be stored.

Here, if the first registration procedure is the initial registration procedure, the first registration refusal message does not include the TAI list indicating the registration area, but the second rejected NSSAI is included, the registration area where the UE is valid. The UE may store the S-NSSAI contained in the received second rejected NSSAI in the second rejected NSSAI # 3 associated with the PLMN # 1 based on not remembering.

Here, the S-NSSAI included in the second rejected NSSAI # 3 may be associated with the registration area and not stored, or may be associated with the dummy registration area information. Here, the dummy registration area information may be empty registration area information.

Alternatively, if the UE does not remember the current registration area, the second rejected NSSAI received by the UE from PLMN # 1 during the initial registration procedure does not have to be remembered.

The first registration procedure may be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and the behavior of the registration procedure described in Chapter 3 may be carried out.

The following behavior will be explained when at least TAI # 1 and TAI # 2 are included in the current registration area, and when TAI # 1 belongs to PLMN # 1 and TAI # 2 belongs to PLMN # 2. ..

Next, the UE undergoes a PLMN change with no change in the registration area. Specifically, for example, the case where the UE moves from TAI # 1 to TAI # 2 will be described.

After the UE moves from TAI # 1 to TAI # 2, a move or regular registration process occurs. Although the cause of this registration procedure is not particularly specified, it may be, for example, a registration procedure that occurs regularly.

The UE may carry out a second registration procedure for PLMN # 2 3GPP access based on TAI # 2 belonging to PLMN # 2. The UE may initiate the registration process by sending a second registration request message to PLMN # 2 (core network) that includes at least the first identification information.

Here, the UE may include the S-NSSAI included in the allowed NSSAI # 12 associated with PLMN # 1 and PLMN # 2 in the first identification information. Further, the UE may control the first identification information so as not to include the S-NSSAI contained in the second rejected NSSAI # 12 associated with PLMN # 1 and PLMN # 2. In other words, the S-NSSAI contained in the first identification information does not have to be included in the second rejected NSSAI # 12 associated with PLMN # 1 and PLMN # 2.

PLMN # 2 (core network) may send a second registration acceptance message or a second registration refusal message to the UE based on the receipt of the second registration request message.

The UE performs the same behavior as the first registration procedure based on the reception of the second registration acceptance message or the second registration refusal message.

The second registration procedure may also be the registration procedure described in Chapter 3, and the behavior of each device is not limited to the above, and the behavior of the registration procedure described in Chapter 3 may be carried out.

As described above, in the present embodiment, each device makes the received allowed NSSAI and / or the second rejected NSSAI one allowed NSSAI and / or the one allowed NSSAI associated with the current PLMN (RPLMN) regardless of the current registration area. Or store in one second rejected NSSAI associated with the current PLMN (RPLMN).

Furthermore, even if the UE is an allowed NSSAI associated with a PLMN other than the requested PLMN, if the TAI contained in the registration area to which the allowed NSSAI is associated belongs to the current PLMN, the allowed NSSAI is also included. , Can be used to generate the first identification information.

In addition, the UE has a second rejected NSSAI associated with a PLMN other than the requested PLMN, as well as a second rejected NSSAI associated with the requested PLMN, based on the current registration area. Can be used to generate identification information.

In this embodiment, only the registration procedure has been described, but other procedures may be used. Specifically, instead of the registration acceptance message or registration refusal message, the UE receives the allowed NSSAI and / or the second rejected NSSAI in the setting update command message during the UE setting update procedure described in Chapter 3, and each NSSAI. It may behave based on the reception of.

Alternatively, the UE receives the allowed NSSAI and / or the second rejected NSSAI in the non-registration request message during the non-registration procedure initiated by the network described in Chapter 3 instead of the registration acceptance message or registration refusal message, and each NSSAI It may behave based on reception.

[5. Modification example]
The program that operates on the apparatus according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to operate a 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.

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. Is also good.

Further, each functional block or feature of the device used in the above-described embodiment may 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.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included. 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.

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

Claims (3)

UE (terminal device; User Equipment)
It has a transmitter / receiver and a storage unit.
The transmitter / receiver receives the first rejection NSSAI (Network Slice Selection Assistance Information) from the core network, and receives the first rejection NSSAI (Network Slice Selection Assistance Information).
When a plurality of tracking area information included in the information indicating the registration area stored in the UE belongs to different PLMNs,
The storage unit
The received first rejection NSSAI is included in each rejection NSSAI associated with each PLMN and stored.
UE, which is characterized by that. UE (terminal device; User Equipment)
It has a transmitter / receiver and a storage unit.
The transmitter / receiver receives the first rejection NSSAI (Network Slice Selection Assistance Information) from the core network, and receives the first rejection NSSAI (Network Slice Selection Assistance Information).
When a plurality of tracking area information included in the information indicating the registration area stored in the UE belongs to a plurality of different PLMNs.
The storage unit
The received first rejection NSSAI is included and stored in one rejection NSSAI associated with the plurality of different PLMNs.
UE, which is characterized by that. UE (terminal device; User Equipment)
It is equipped with a transmitter / receiver, a storage unit, and a control unit.
The transmitter / receiver transmits the first PLMN request NSSAI (Network Slice Selection Assistance Information).
When a plurality of tracking area information included in the information indicating the registration area stored in the UE belongs to a plurality of different PLMNs.
The control unit does not include in the request NSSAI the S-NSSAI included in the rejection NSSAI associated with each of the plurality of different PLMNs and the registration area.
UE, which is characterized by that.

Images