WO2021241114A1 - User equipment (ue), core network device, access and mobility management function (amf), and session management function (smf) - Google Patents

Abstract

Provided is a communication means for realizing a function relating to management of information for providing, to a UE, a network slicing service corresponding to an area, in 5GS. Provided are a communication means and a method for initial registration and periodic or movement-based registration updating procedures, for the purpose of realizing management of information relating to a UE and a service area for each network slice, in 5GS. Additionally provided are a communication means and a method for: network slice-specific authentication/approval procedures after completion of registration procedures; UE setting updating procedures; and non-registration procedures.

Description

UE (User Equipment), core network device, AMF (Access and Mobility Management Function), and SMF (Session Management Function)

One aspect of the present invention relates to UE (User Equipment), core network device, AMF (Access and Mobility Management Function), and SMF (Session Management Function). This application claims priority to Japanese Patent Application No. 2020-093907 filed in Japan on May 29, 2020, the contents of which are incorporated herein by reference.

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

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 being studied as a system to realize 5G mobile communication systems. 5G System) is being specified (see Non-Patent Documents 1 to 3). 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.

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

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

In 3GPP, eNS (Enhancement of Network Slicing) is being studied in order to further study further functions related to network slicing. In 3GPP, as a study of Phase 2 of eNS, a service area (area of service) that can be accessed by the UE is defined for each network slice, and the addition of a function to provide services to the UE according to the area is considered. (See Non-Patent Documents 4 and 5).

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

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

In the UE (User Equipment) including the control unit and the transmission / reception unit according to one aspect of the present invention, the transmission / reception unit receives a control message including the first identification information from the control device, and the control message is registered. In the case of an acceptance message or a setting update command, the first identification information is Allowed NSSAI (Network Slice Selection Assistance Information) or Rejected NSSAI, and the control message is a registration refusal message or a non-registration request message. If there is, the first identification information is Rejected NSSAI, the first identification information includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information, and the control unit is the first. Based on the reception of the identification information of, the S-NSSAI and the area information are stored in association with each other, and when the first identification information is Rejected NSSAI, the S-NSSAI includes a reason value. The reason value indicates that the user is not in a place where the S-NSSAI can be connected, and based on the reception of the first identification information, the S-NSSAI cannot be used in the connected area. It is characterized by recognizing that.

The core network device according to one aspect of the present invention includes a control unit and a transmission / reception unit, and the transmission / reception unit receives a registration request message including UE capability information from a UE (User Equipment) and sends the UE to the UE. , A registration acceptance message including the first identification information is transmitted, and the first identification information is Allowed NSSAI (Network Slice Selection Assistance Information), Rejected NSSAI, or Pending NSSAI, and the first identification information is When the capability information of the UE includes S-NSSAI (Single Network Slice Selection Assistance Information) and indicates that the UE supports the area of service, the first identification information further includes the S-. It is characterized by including area information associated with NSSAI.

The UE (User Equipment) according to one aspect of the present invention includes a control unit and a transmission / reception unit, and the transmission / reception unit receives a control message including first identification information and network capability information from the control device. When the capability information of the network indicates that the network supports the area of service, the first identification information includes S-NSSAI (Single Network Slice Selection Assistance Information) and the area information. The control unit is characterized in that the S-NSSAI and the area information are associated and stored in association with each other based on the reception of the first identification information.

The UE (User Equipment) according to one aspect of the present invention includes a storage unit, a control unit, and a transmission / reception unit, and the storage unit corresponds to S-NSSAI (Single Network Slice Selection Assistance Information) and area information. Attached and stored, the control unit establishes a PDU (Protocol Data Unit) session associated with the S-NSSAI, and the UE indicates the area indicated by the area information from the area indicated by the area information. When moving outside, the transmission / reception unit performs a PDU session release procedure for releasing the PDU session, and the control unit deletes the S-NSSAI from the allowed NSSAI and sends the rejected NSSAI to the above. It is characterized in that the transmission / reception unit is set so as to be stored in S-NSSAI and the start of the PDU session establishment procedure and the PDU session change procedure using the S-NSSAI is prohibited.

The UE (User Equipment) according to one aspect of the present invention includes a storage unit, a control unit, and a transmission / reception unit, and the storage unit corresponds to S-NSSAI (Single Network Slice Selection Assistance Information) and area information. When the UE moves from outside the area indicated by the area information to the inside of the area indicated by the area information, the control unit receives the S from rejected NSSAI (Network Slice Selection Assistance Information). -Delete NSSAI and set the transmitter / receiver so that allowed NSSAI stores in the S-NSSAI and allows the start of the PDU session establishment procedure and PDU session change procedure using the S-NSSAI. It is characterized by doing.

The UE (User Equipment) according to one aspect of the present invention includes a control unit and a transmission / reception unit, and the transmission / reception unit receives a registration acceptance message including Pending NSSAI (Network Slice Selection Assistance Information) from the control device. The Pending NSSAI includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information, and executes a network slice authentication approval procedure using the S-NSSAI based on the reception of the transmission / reception unit and the Pending NSSAI. However, the control unit deletes the S-NSSAI and the area information from the Pending NSSAI when the control unit moves out of the area indicated by the area information during the execution of the network slice authentication approval procedure. And.

The core network device according to one aspect of the present invention includes a control unit and a transmission / reception unit, and the transmission / reception unit transmits a registration acceptance message including Pending NSSAI (Network Slice Selection Assistance Information) to a UE (User Equipment). However, the Pending NSSAI includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information, and the transmission / reception unit is described when the UE is located in the area indicated by the area information. The network slice authentication approval procedure using S-NSSAI is executed, and the UE indicates an area indicated by the area information from the areas indicated by the area information during the network slice authentication approval procedure using the S-NSSAI. When the user moves out of the network slice authentication approval procedure, the network slice authentication approval procedure is canceled.

An AMF (Access and Mobility Management Function) according to one aspect of the present invention includes a transmission / reception unit, a storage unit, and a control unit, and the transmission / reception unit is from a UE (User Equipment) via a first area. , S-NSSAI (Single Network Slice Selection Assistance Information) including requested NSSAI (Network Slice Selection Assistance Information) is received, and the storage unit stores the S-NSSAI and the area information associated with the S-NSSAI. Then, the control unit confirms the area information based on the reception of the S-NSSAI, and if the area information includes the first area, the UE is indicated by the area information. If the area information does not include the first area, it is determined that the UE is not in the area indicated by the area information.

An AMF (Access and Mobility Management Function) according to one aspect of the present invention includes a transmission / reception unit, a storage unit, and a control unit, and the transmission / reception unit is from a UE (User Equipment) via a first area. , The storage unit stores the S-NSSAI (Single Network Slice Selection Assistance Information) set in the UE and the area information associated with the S-NSSAI, and the control unit receives the registration request message. If the registration request message does not include requested NSSAI (Network Slice Selection Assistance Information), or if the area information includes the first area, the UE is set to the area indicated by the area information. If the area information does not include the first area, it is determined that the UE is not in the area indicated by the area information.

An SMF (Session Management Function) according to one aspect of the present invention includes a control unit and a transmission / reception unit, and the transmission / reception unit executes a PDU session establishment procedure for establishing a PDU (Protocol Data Unit) session. The control unit manages the PDU session in association with the area information, and the transmission / reception unit has the UE (User Equipment) moved from the area indicated by the area information to the outside of the area indicated by the area information. The first identification information indicating the above is received from the AMF (Access and Mobility Management Function), and the control unit releases the PDU session or corresponds to the PDU session based on the reception of the first identification information. It is characterized by releasing attached user plane resources.

According to one aspect of the present invention, eNS can be supported in 5GS, and a network slice service based on the area accessed by the UE can be provided.

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 one aspect of the present invention will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which one aspect of the present invention is applied will be described.

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

In FIG. 1, the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (PacketDataNetwork) _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, 5GAN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc. An interface for connecting these devices / functions to each other is described.

In the following, these devices / functions are described as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5GAN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc. , 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, the 5GS (5G System), which is a 5G system, is configured to include a UE, an access network_B, and a core network_B, but may further include a DN.

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

In addition, the access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNB (evolved Node B) 45 are arranged in E-UTRAN. In the following, eNB45 may be described by omitting a symbol like eNB. If 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 (5GAN). 5GAN is composed of NG-RAN (NG Radio Access Network) and / or non-3GPP access network. One or more gNB (NR Node B) 122s are placed in the NG-RAN. In the following, gNB122 may be described by omitting a symbol like 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 different function from the base station device (eNB) used in EPS, which is a 4G system. When there are a plurality of gNBs, each gNB is connected to each other by, for example, an Xn interface.

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

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

In the following, the device included in the access network_A and / or the access network_B and / or the access network_A, and / or the device included in the access network_B is the access network or the access network device. May be called.

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

In addition, core network_B corresponds to 5GCN (5G Core Network). For example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management) 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. Sometimes referred to as an internal device.

The core network (core network_A and / or core network_B) is a mobile network operator (Mobile) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN. It may be an IP mobile communication network operated by Network Operator; MNO), it may be a core network for a mobile communication operator that operates and manages mobile communication system 1, or it may be an MVNO (Mobile Virtual Network Operator). ), MVNE (Mobile Virtual Network Enabler), and other virtual mobile communication operators and virtual mobile communication service providers.

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

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

In the following, access network_A, core network_A, PDN, access network_B, core network_B, at least a part of DN, and / or one or more devices included in these are referred to as a network or network device. 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 are used. It means that at least a part and / or one or more devices contained therein send / receive messages and / or perform procedures.

Also, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send / 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 may add another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be sent and received may be sent and received.

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

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

Also, the AAA server is a device that has authentication, approval, and billing functions that connects directly to AUSF or indirectly via other network devices. The AAA server may be a network device in the core network. The AAA server may not be included in the core network_A and / or the core network_B, but may be included in the PLMN. That is, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device in PLMN managed by 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 has multiple UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150. Devices / functions such as 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 unit). 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, various information transmitted / received to / from PDN and / or DN) can be stored. 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 may store control messages and user data sent and received between 5GS and / or devices / functions included in EPS when interwork is performed between 5GS and EPS. can. At this time, not only those transmitted / received via the N26 interface but also those transmitted / received without the N26 interface can be stored.

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

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

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

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

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

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

Control unit_B500 is a functional unit that controls the operation and function of the entire gNB. The control unit_B500 realizes various processes in 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 to and from the AMF and / or the UPF using the network connection unit_B520.

The transmission / reception unit_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, gNB in 5GAN can communicate with AMF via the N2 interface by using the network connection part_B520, and 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 device 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 unit_B720 is a functional unit for AMF to connect to the base station equipment (gNB) in 5GAN and / or SMF, and / or PCF, and / or UDM, and / or SCEF. That is, the AMF uses the network connection _B720 to the user between the base station equipment (gNB) in 5GAN and / or the SMF and / or the PCF, and / or the UDM, and / or the SCEF. Data and / or control information can be sent and received.

More specifically with reference to Figure 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, it can communicate with the SMF via the N11 interface, and it can communicate with the PCF via the N15 interface. In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN. In addition, when the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

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

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

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

In other words, 5GMM-REGISTERED may be in a state where each device has established a 5GMM context or a state in which a PDU session context has been established. When each device is 5GMM-REGISTERED, UE_A10 may start sending / receiving user data or control message, 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 location information of UE_A10 may not be known to the network, or the network reaches UE_A10. It may be in an impossible state. If each device is 5GMM-DEREGISTERED, UE_A10 may start the registration procedure or establish the 5GMM context by executing the registration procedure.

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

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

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

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

[2.4. SMF device configuration]
Next, an example of the SMF device configuration will be described with reference to FIG. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.

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

The network connection part_B720 is a functional part for SMF to connect with AMF and / or UPF, and / or PCF, and / or UDM. That is, the SMF can send and receive user data and / or control information between the AMF and / or the UPF, and / or the PCF, and / or the UDM by using the network connection unit_B720.

More specifically with reference to Figure 2, the SMF within 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 SMF.

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

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

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

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

More specifically with reference to Figure 2, the UPF within the 5GCN can communicate with the gNB via the N3 interface by using the network connection _A620 and with the SMF via the N4 interface. It can communicate, it can communicate with the DN via the N6 interface, and it can communicate with other UPFs via the N9 interface.

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

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

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

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

Furthermore, the control plane is a control message sent and received to control the communication of the UE. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the 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 / received using the interface between the UE and NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or a C-Plane.

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

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

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

The SM (session management) message (also referred to as NAS (Non-Access-Stratum) SM message) may be a NAS message used in the procedure for SM, and is sent and received between UE_A10 and SMF_A230 via AMF_A240. It may be a control message to be performed. Further, the SM message includes a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session establishment reject message, and a PDU session modification request (PDU session modification). request) message, PDU session modification command (PDU session modification command) message, PDU session modification completion message (PDU session modification complete), PDU session change command rejection (PDU session modification command reject) message, PDU session modification rejection (PDU session modification) reject message, PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete (PDU session release complete) A message or the like may be included. In addition, the procedure for SM or SM procedure includes PDU session establishment procedure (PDU session establishment procedure), PDU session modification procedure (PDU session modification procedure), and PDU session release procedure (UE-requested PDU session release procedure). It may be. In addition, each procedure may be a procedure started from UE or a procedure started from NW.

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

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

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

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

In addition, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as a relationship between a DN that provides a PDU connectivity service and a UE, but it is established between the UE and an 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 on the DN.

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

Further, DNN (Data Network Name) may be identification information that identifies the core network and / or the external network such as DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 to connect 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. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Further, Ethernet may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is sent / received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology. As the P2P tunneling technique, for example, a UDP / IP encapsulation technique may be used. The PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.

PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator who is a (mobile) telecommunications carrier, and the operator can be identified by the PLMN ID. In this paper, PLMN may mean PLMN ID. The PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the IMSI (International Mobile Subscriber Identity) of the UE may be Home PLMN (HPLMN). The visited PLMN (Visited PLMN; VPLMN) may be a PLMN different from HPLMN or HEPLMN (Home Equivalent PLMN). PLMN may mean core network.

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

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

The current PLMN (current PLMN) is 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.

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

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

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

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

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

A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. Network slices may also be 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 composed of one or more in core network_B. Further, NSI may be configured by a virtual NF (Network Function) generated by using NST (Network Slice Template).

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

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

In addition, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying NS. S-NSSAI may be composed 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, the SD may be information that interpolates the SST when selecting one NSI from a plurality of NSIs represented by the SST. The S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs. Further, the network may store one or more S-NSSAI in the registration information of the UE 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 / received between the UE and the NW may be expressed as S-NSSAI IE (Information element). Furthermore, the S-NSSAI IE transmitted and received between the UE and NW indicates the S-NSSAI composed of the SST and / or SD of the registered PLMN, and / or the S-NSSAI of the HPLMN to which the S-NSSAI is mapped. SST and / or SD may be configured. One or more S-NSSAIs stored by the UE and / or NW may be composed of SST and / or SD, and S-NSSAI composed of SST and / or SD, and / or S-NSSAI thereof. An SST and / or SD indicating the S-NSSAI of the mapped HP LMN may be configured.

NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information that assists the access network or core network in selecting NSI. The UE may memorize the NSSAI permitted by 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 / or pending NSSAI, and / or the first NSSAI) to the PLMN and EPLMN.

Mapped S-NSSAI is an HPLMN S-NSSAI mapped to the registered PLMN S-NSSAI in a roaming scenario. The UE may store one or more mapped S-NSSAI mapped to the configured NSSAI and the S-NSSAI included in each access type allowed NSSAI. 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. Further, the UE equipped with the NSSAA function can manage, store, and transmit / receive the pending NSSAI and the third rejected NSSAI. In this paper, NSSAA may be referred to as network slice-specific authentication and authorization procedures and authentication and authorization procedures.

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

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

Also, configured NSSAI (configured NSSAI) is NSSAI supplied and stored in the UE. The UE may store the configured NSSAI for each PLMN. The UE may store the configured NSSAI in association with the PLMN. In this paper, the configured NSSAI associated with the PLMN may be expressed as the configured NSSAI for the PLMN, the configured NSSAI for the PLMN, the configured NSSAI for the PLMN, or the configured NSSAI associated with the PLMN. In addition, the UE may store a configured NSSAI that is not associated with the PLMN and is valid for all PLMNs, and such a configured NSSAI may be referred to as a "default configured NSSAI".

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

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

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

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

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

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

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

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

Also, rejected NSSAI (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 connections to the UE. The rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason for rejection value.

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

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

The rejected NSSAI may be any of the first to fourth 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.

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

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

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

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

The UE may delete the first rejected NSSAI from the memory when it transitions to the non-registered 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 if the registration with the new PLMN is successful via one access, or with the registration to 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 non-registered state with respect to the current PLMN via one access, the UE is registered with the current PLMN via the other access (registered state). The UE does not have to delete the first rejected NSSAI.

The second rejected NSSAI is a set of one or more S-NSSAIs that are not available in the current registration area among the S-NSSAIs that the UE has included in the requested NSSAI. The second rejected NSSAI may be a 5GS rejected NSSAI for the current registration area. The second rejected NSSAI may be a rejected NSSAI stored 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)", which is not possible in the current registration area, and the S-NSSAI associated with the reason value is It may be information indicating that it is not possible in the current registration area. The S-NSSAI included in the second rejected NSSAI may be expressed as the second rejected S-NSSAI.

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

The third rejected NSSAI is an S-NSSAI that requires an NSSAA, and is a set 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 (S-NSSAI not available due to the failed or revoked NSSAA) which is impossible due to the failure or cancellation of NSSAA" and is associated with the reason for refusal value. It may be information indicating that NSSAA for S-NSSAI has failed or 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 do it.

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

The third rejected NSSAI is a rejected NSSAI in which the UE identifies slices rejected due to the failure or cancellation of NSSAA 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 fourth rejected NSSAI is an S-NSSAI that requires area restriction by the area of service, and is a set of one or more S-NSSAI rejected from the network because there is no UE in the area where the S-NSSAI is permitted. Is. The fourth 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 fourth rejected NSSAI is transmitted from the NW to the UE, the fourth rejected NSSAI may be information that includes one or more combinations of the S-NSSAI and the reason for refusal value. The reason for refusal value at this time may be "S-NSSAI which is impossible because it is outside the area where the service of S-NSSAI is provided", and the service of S-NSSAI associated with the reason for refusal value. It may be information indicating that it is not possible because the UE is outside the area where is provided. The S-NSSAI included in the fourth rejected NSSAI may be expressed as the fourth rejected S-NSSAI.

The fourth rejected NSSAI may be information that further includes one or more combinations of S-NSSAI and area information.

The fourth rejected NSSAI may be applied to the entire registered PLMN, may be valid for all PLMNs, may be applied, and the area information to which the fourth rejected S-NSSAI is associated. It may be valid within the area indicated by and may be applied to the registered PLMN and EPLMN. The fact that the 4th rejected NSSAI applies to all PLMNs may mean that the 4th rejected NSSAI is not associated with the PLMN, and that the 4th rejected NSSAI is associated with the HPLMN. You can do it.

If the fourth rejected 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 is the fourth rejected. The S-NSSAI included in the NSSAI and the fourth rejected NSSAI may be treated as information that does not depend on the access type.

If the fourth rejected NSSAI is valid within the area indicated by the associated area information, the UE and / or NW will access the S-NSSAI contained in the fourth rejected NSSAI and the fourth rejected NSSAI. It may be treated as independent information for each type.

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

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

When the first NSSAI is sent from the NW to the UE, the first NSSAI is the S-NSSAI and the mapped S-NSSAI, the rejection reason value, the backoff timer value, and the validity period of the backoff timer value. The information may include one or a plurality of information indicating a range and information including at least one. The reason for refusal value at this time may be "S-NSSAI that has reached the maximum number of UEs for each network slice", and 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 5GMM 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 S-NSSAI related to the corresponding S-NSSAI or the mapped S-NSSAI. It may be information indicating.

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

The first NSSAI may be applied to the entire registered PLMN, may be valid for all PLMNs, may be applied, may be valid within the registered area, and may be valid 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 shall 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 the UE cannot and / or cannot use. The pending NSSAI may be a set of S-NSSAI whose network requires network slice specific authentication and whose network slice specific authentication has not been completed. The pending NSSAI may be a 5GS pending NSSAI. The pending NSSAI may be an NSSAI stored in the UE and / or the NW, or may be an NSSAI transmitted / received between the NW and the UE.

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

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

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

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

Pending NSSAI is an NSSAI composed of one or more S-NSSAI 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 the registration request message containing the S-NSSAI contained in the pending NSSAI to both 3GPP access and non-3GPP access.

Also, the area of service may be attribute information indicating the area in which the UE can access a specific network slice, in other words, the area of service allows the UE to establish a PDU session for a specific S-NSSAI. It may be information composed of one or more to indicate an area.

Here, the information about the area or area indicated (specifying) by the area of service may be a Tracking Area (TA), a registration area, or may be composed of one or a plurality of TAs (). It may be information (indicating a service area for each S-NSSAI), may be composed of one or more cells (coverage of eNB and / or gNB), or may be an area based on geolocation information. May be good. Here, the area based on the geolocation information may be composed of the coverage of one or more eNBs and / or gNBs mapped to the geolocation information, and one or more TAs mapped to the geolocation information. It may be composed of.

Further, the area of service may be composed of one or more entries, and each entry may contain information indicating a country and / or a region. Specifically, it may include one or more entries containing information indicating the country and / or region to which the service of the network slice is provided, based on the roaming agreement between HPLM and VPLMN.

Further, the state in which the UE is in the area of service may be a state in which the UE is connected or exists in the above-mentioned area associated with the S-NSSAI attempting to connect, and the UE may be present. The state where is outside the area of service may be a state in which the UE does not exist in the above-mentioned area associated with the S-NSSAI at which the UE attempts to connect.

The area indicated by the area of service may be determined by the Network Slice Provider (NSP), which provides the network slice service, or may be determined based on the network policy, and is not limited thereto.

Also, based on the area of service, the area where the S-NSSAI service is provided is also referred to as the service area.

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

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

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

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

Management of the maximum number of UEs connected to a slice is to manage the maximum number of UEs that can be registered in the network slice or S-NSSAI at the same time. Here, the UE registered in the network slice or S-NSSAI may mean that the S-NSSAI indicating the network slice is included in the allowed NSSAI and stored. Supports the function of managing the maximum number of UEs connected to a slice The device in the network can memorize whether or not the maximum number of UEs connected to a slice needs to be managed for each S-NSSAI, and the registered UEs It is possible to confirm whether or not the maximum number of constants has been reached during the registration procedure. 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 article, the maximum number of UEs connected to a slice may be expressed as the maximum number of UEs connected for each slice, or the maximum number of UEs that can be registered in a network slice or S-NSSAI, or the maximum number of UEs or a constant. ..

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

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

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 is now allowed to send MM and / or SM messages that were prohibited by the PLMN before the change in the new PLMN, 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 mapped S-NSSAI of the same S-NSSAI. It may mean.

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

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

Further, the backoff timer may be a timer associated with noNSSAI and prohibiting the transmission of MM messages using noNSSAI. In other words, UE_A10 may be set not to send MM messages using noNSSAI during the counting of this timer. Furthermore, UE_A10 may be set to allow the transmission of MM messages prohibited by the PLMN before the change in the new PLMN based on the specific conditions described later during the counting of this timer. 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 restricting the communication of user data via the control plane, or may be the same timer.

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

The first identification information in the present embodiment may be the capability information (capability) of the UE indicating that the UE supports the area of service.

More specifically, the first identification information is cored with information including area information and / or reason values associated with the network slice (S-NSSAI) that the UE has requested and / or has been granted from the core network to the core network. It may be ability information indicating that it has a function of transmitting, receiving, recognizing, storing, and processing with and from a network. Further, it may be shown that the UE supports the function of receiving, recognizing, and processing the information about the area of service from the core network by transmitting the first identification information to the core network.

Here, the UE that supports the area of service has the ability to send, receive, recognize, store, and process information about the provided area of service with and from the core network, and the UE-led or UE-led for the area of service. It may have the ability to perform network-driven procedures. Specifically, for example, a UE that supports an area of service may have a function of recognizing, storing, and processing information about an area associated with S-NSSAI received from the core network. -It may have a function to recognize, store, and process the reason value related to the area of service associated with NSSAI.

Further, the first identification information may be identification information for requesting the core network for the ability information of the core network indicating that UE_A10 supports the area of service.

Here, the information indicating the area may be the third identification information described later.

Alternatively, the first identification information may be the capability information of the UE indicating whether or not the UE supports the area of service.

The second identification information in the present embodiment is the ability information of the core network indicating that the core network supports the area of service.

More specifically, the second identification information contains information about the area of service, including the area information associated with the network slice (S-NSSAI) requested by the UE and / or the UE and / or the reason value. It may be ability information indicating that it has a function of transmitting, receiving, recognizing, storing, and processing with and from the UE.

Further, it may be shown that the core network supports the function of receiving, recognizing, and processing the information about the area of service from the UE by transmitting the second identification information to the UE.

Here, the UE that supports the area of service has the ability to send, receive, recognize, store, and process information about the provided area of service with and from the core network, and the UE-led or UE-led for the area of service. It may have the ability to perform network-driven procedures. Specifically, for example, a UE that supports an area of service may have a function of recognizing, storing, and processing information about an area associated with S-NSSAI received from the core network. -It may have a function to recognize, store, and process the reason value related to the area of service associated with NSSAI.

Further, the second identification information may be the identification information transmitted to UE_A10 based on the first identification information received from the UE.

Here, the information indicating the area may be the third identification information described later.

The third identification information in the present embodiment may be information indicating an area where the S-NSSAI service is provided.

Here, the area indicated by the third identification information may be information related to the area or area indicated (specifying) by the above-mentioned area of service, may be Tracking Area (TA), or may be a registration area. It may be information composed of one or more TAs (indicating a service area for each S-NSSAI), or it may be composed of one or more cells (eNB and / or gNB coverage). It may be an area based on geolocation information.

When the third identification information is an area based on the geolocation information, the identification information may be composed of the coverage of one or more eNBs and / or gNBs mapped to the geolocation information. It may be identification information composed of one or more TAs mapped to geolocation information.

The third identification information may be the area information included in the fourth rejected NSSAI.

The fourth identification information in the present embodiment is a reason value indicating that the UE is connected or is outside the area where the service of the network slice (S-NSSAI) attempting to connect is provided. You can do it. Further, the fourth identification information may be a reason value indicating that the UE has moved out of the area. Further, the fourth identification information may be a reason value indicating that the user is not in a place where the S-NSSAI can be connected.

Here, the fourth identification information may be a reason value (cause value) included in the rejected NSSAI information element (Information Element; IE), or may be another identification information associated with S-NSSAI. May be good.

[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 registration procedure, Network Slice-Specific Authentication and Authorization procedure, Generic UE configuration update procedure, and network-initiated non-registration procedure (Network-). Initiated de-registration procedure) is included. Is included. Each procedure will be explained below.

In each embodiment, as shown in FIG. 2, HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each 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 (especially UE and AMF) can transition to the registration state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration status (registered or unregistered status) for 3GPP access and the registration status for non-3GPP access.

In addition, the registration procedure updates the location registration information of the UE in the network and / or periodically notifies the network of the status of the UE from the UE and / or updates 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 by 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 capability 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 the UE is registered is referred to as an initial registration procedure (initial registration procedure) or a registration procedure for initial registration (registration procedure for initial registration). Alternatively, the registration procedure executed while the UE is registered in the network can be changed to the registration procedure (registration procedure for mobility and periodic registration update) or the transfer and regular registration procedure (registration procedure for mobility and periodic registration update). Mobility and periodic registration procedure) may be used.

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

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

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

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

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

Furthermore, UE_A10 may include S-NSSAI (NSSAA is pending for the S-NSSAI) requested by UE_A10 in requested NSSAI. Further, UE_A10 may indicate the request of the S-NSSAI by including the S-NSSAI in the requested NSSAI.

In addition, UE_A10 determines whether or not to send the first identification information, requested NSSAI to the network, UE capability information and / or UE policy, and / or UE status, and / or user registration information, and / Or may be selected and determined based on the context held by the UE.

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

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

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

For example, 5GAN120 (or gNB) may select an AMF that supports the function corresponding to the ability information indicated by the first identification information based on the first identification information and / or requested NSSAI. Specifically, 5GAN (or gNB) corresponds to the capability information of the UE indicated by the first identification information, and is included in the network slice based on the area of service, or has AMF having connectivity to the network slice. You may choose.

The selection method of AMF is not limited to this, and 5GAN (or gNB) may select AMF based on other conditions. 5GAN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected new AMF (S604). If at least one of the first and second identification information is not included in the registration request message and is included in the RRC message, the identification information included in the RRC message is selected as 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 determine the first condition after receiving the UE context from the old AMF142 (S606, S608). In that case, new AMF141 may execute S610 and / or S612 if the first condition determination is true. On the other hand, new AMF141 may execute S610 when the first condition determination is false.

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

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

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

Also, if the S-NSSAI contained in the requested NSSAI received from the UE is the information that identifies the slice that requires the NSSAA procedure, the result of the NSSAA procedure of the S-NSSAI that the AMF corresponds to the UE is successful. The first condition determination may be true if it is remembered to be. Alternatively, if 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.

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

AMF does not have S-NSSAI allowed for UE, and when the first NSSAI is assigned to UE, the first condition determination may be true or false.

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

The UE context transfer procedure (S606, S608) will be explained. new AMF141 sends a UE context request message to old AMF142 (S606). The old AMF142 sends the UE context to the new AMF 141 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 allowed NSSAI. Further, the UE context may include configured NSSAI and / or rejected NSSAI, NSSAI and / or pending NSSAI, and / or a first NSSAI. Also, allowed NSSAI and / or configured NSSAI and / or rejected NSSAI and / or pending NSSAI and / or first NSSAI included in the UE context, and S-NSSAI included in each NSSAI are sent to the UE. Information on whether or not the notification has been completed may be linked.

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

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

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

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

The new AMF141 may send the control message including one or more identification information among the second to fourth identification information. Here, the third identification information may be transmitted one or more in association with each S-NSSAI included in allowed NSSAI and / or rejected NSSAI, and the fourth identification information is included in rejected NSSAI. One or more may be transmitted in association with each S-NSSAI. In addition, new AMF141 may indicate that the network supports each function including the function related to the area of service by transmitting these identification information and / or the control message, and the request of the UE is accepted. It may indicate that the request has been made, 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.

In addition, new AMF141 transmits the control message (registration acceptance message or registration refusal message) including one or more of the second to fourth identification information based on the reception of the first identification information from the UE. You may.

In other words, the new AMF141 is included in the Allowed NSSAI, Rejected NSSAI, or Pending NSSAI transmitted by the new AMF141 if the first identification information received from the UE indicates that the UE supports the area of service. , Area information associated with one or more S-NSSAIs may be sent to the UE.

Alternatively, new AMF141 may send the second identification information and the area information associated with S-NSSAI and its S-NSSAI to the UE when the core network supports the area of service. The S-NSSAI and area information at this time may be one or more S-NSSAI and area information included in Allowed NSSAI, Rejected NSSAI, or Pending NSSAI.

The area information associated with S-NSSAI, which may be included in Allowed NSSAI, Rejected NSSAI, or Pending NSSAI transmitted from new AMF141 to UE, is Allowed NSSAI, Rejected NSSAI, or Pending NSSAI. It may be independent information.

In other words, if the new AMF141 does not receive the first identification from the UE, or if the new AMF141 receives the first identification from the UE that the UE does not support the area of service. Control may be executed not to transmit the area information associated with S-NSSAI included in Allowed NSSAI, Rejected NSSAI, or Pending NSSAI transmitted by new AMF141 to the UE.

Specifically, when the new AMF141 detects that the UE does not support the area of service, the new AMF141 will be described above even if the S-NSSAI requested by the UE is an S-NSSAI that requires the area of service. The area information associated with S-NSSAI does not have to be transmitted to the UE, and Allowed NSSAI, Rejected NSSAI, or Pending NSSAI that does not include the area information may be transmitted to the UE.

The area information associated with S-NSSAI, which may be included in Allowed NSSAI, Rejected NSSAI, or Pending NSSAI transmitted from new AMF141 to UE, is Allowed NSSAI, Rejected NSSAI, or Pending NSSAI. It may be independent information.

In addition, new AMF141 associates the service area information for each S-NSSAI included in the requested NSSAI sent by UE_A10 in the registration request message with each S-NSSAI as the third identification information, and uses it as a control message. It may be included and sent to the UE. Here, the information on the service area for each S-NSSAI may be held by each AMF that supports the area of service in the core network, or in the core network or core that manages the service area for each S-NSSAI. AMF may request and acquire a device outside the network.

Furthermore, based on the information of the area to which UE_A10 connects and the information of the service area for each S-NSSAI included in the requested NSSAI sent by UE_A10 in the registration request message, the UE is within the service area of S-NSSAI. It may be determined whether it is outside or outside, the fourth identification information is determined, associated with each S-NSSAI, included in the control message, and sent to the UE.

Further, for example, when UE_A10 does not include requested NSSAI in the registration request message, the area information for each S-NSSAI included in configured NSSAI and the area information or location information to which the UE is connected are taken into consideration in the third and third stages. / Or the fourth identification information may be determined and included in the control message and sent to the UE.

Here, for example, the registration acceptance message does not include the second identification information but contains the third and / or fourth identification information, so that the UE_A10 has the core network supporting the area of service. You may recognize that it is.

Also, for example, if the core network or AMF does not support the area of service, the registration acceptance message or registration refusal message may be sent to UE_A10 without including the second to fourth identification information. In other words, UE_A10 may recognize that the core network does not support the area of service because the registration acceptance message or registration refusal message does not contain the second to fourth identification information.

Further, for example, if the control message transmitted to the UE is a registration acceptance message, one or a plurality of S-NSSAIs included in allowed NSSAI and / or rejected NSSAI in the message are associated with each other. The third and / or fourth identification information of the above may be included.

Further, for example, when the control message transmitted to the UE is a registration refusal message, one or a plurality of thirds and / or fourths associated with each S-NSSAI included in the rejected NSSAI in the message. Identification information may be included.

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.

Here, it has been explained that the third and / or the fourth identification information is associated with the S-NSSAI contained in the allowed NSSAI and / or the rejected NSSAI and is included in the control message and transmitted to the UE. It may be associated with S-NSSAI included in PendingNSSAI and sent to the UE by including it in the control message.

Further, Allowed NSSAI and / or Rejected NSSAI included in the registration acceptance message may include S-NSSAI and a third identification information. Then, the UE may store the S-NSSAI and the third identification information in association with each other based on the reception of the Rejected NSSAI. Further, the S-NSSAI may include a fourth identification information, and it may be shown that the fourth identification information is not in a place where the S-NSSAI can be connected, for example. Further, the UE may recognize that the S-NSSAI cannot be used in the connected area based on the reception of the Rejected NSSAI.

Further, the Rejected NSSAI included in the registration refusal message may include S-NSSAI and a third identification information. Then, the UE may store the S-NSSAI and the third identification information in association with each other based on the reception of the Rejected NSSAI. Further, the S-NSSAI may include a fourth identification information, and it may be shown that the fourth identification information is not in a place where the S-NSSAI can be connected, for example. Further, the UE may recognize that the S-NSSAI cannot be used in the connected area based on the reception of the Rejected NSSAI.

Based on the reception of the second identification information from AMF and the area information associated with S-NSSAI and its S-NSSAI, the UE stores the received S-NSSAI in association with the area information. good.

Specifically, when the UE receives the second identification information, the Allowed NSSAI and the area information, and this area information is the information associated with the S-NSSAI included in the Allowed NSSAI, the UE determines. The received S-NSSAI may be associated with the area information and stored as Allowed NSSAI.

Similarly, when the UE receives the second identification information, the Rejected NSSAI and the area information, and this area information is the information associated with the S-NSSAI included in the Rejected NSSAI, or the fourth rejected. In the case of S-NSSAI, the UE may store the received S-NSSAI as rejected NSSAI in association with the area information.

Similarly, when the UE receives the second identification information, the Pending NSSAI, and the area information, and the area information is the information associated with the S-NSSAI included in the Pending NSSAI, the UE receives the second identification information. S-NSSAI may be associated with area information and stored as Pending NSSAI.

In other words, if the control message is a registration acceptance message, the control message may include Allowed NSSAI and / or Rejected NSSAI. Conversely, if the control message is a registration rejection message, the control message may include Rejected NSSAI.

Here, the Allowed NSSAI may include S-NSSAI and a third identification information. Further, the S-NSSAI and the identification information of the above 3 may be associated with each other. Further, the Allowed NSSAI may include identification information in which the S-NSSAI and the identification information of the above 3 are combined.

Further, the Rejected NSSAI may include S-NSSAI, a third identification information, and a fourth identification information. Further, the S-NSSAI, the identification information of the third, and the identification information of the fourth may be associated with each other. Further, the Allowed NSSAI may include identification information in which the S-NSSAI, the identification information of the third, and the identification information of the fourth are combined.

It should be noted that the AMF indicates which of the 2nd to 4th 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. It may be selected and determined based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the AMF.

Here, the AMF is located within the service area of a specific S-NSSAI (S-NSSAI # 1-1) based on the received S-NSSAI and the area information stored by the AMF. You may decide whether or not you are doing it. In other words, when the Requested NSSAI is provided by the UE, the AMF will use the specific S-NSSAI (S-) based on the S-NSSAI included in the Requested NSSAI and the area information stored by the AMF. It may be determined whether or not it is located within the service area of NSSAI # 1-1).

Specifically, if the area information associated with S-NSSAI # 1-1 includes the area where the UE is currently located, the UE will be the service of S-NSSAI # 1-1. It may be determined that it is located within the area. Conversely, if the area information associated with S-NSSAI # 1-1 does not include the area in which the UE is currently located, the AMF will say that the UE is in the service area of S-NSSAI # 1-1. It may be determined that it is located outside. The area information may be information acquired by AMF from another device such as UDM, or may be information set in AMF.

In addition, the AMF is based on the S-NSSAI (S-NSSAI # 1-1) provided to the UE and the area information stored by the AMF, and the UE is the service area of the S-NSSAI # 1-1. It may be determined whether or not it is located inside. In other words, if the UE does not provide the Requested NSSAI, the AMF will provide the UE based on the S-NSSAI (S-NSSAI # 1-1) provided to the UE and the area information stored by the AMF. , You may determine whether it is located within the service area of S-NSSAI # 1-1.

Specifically, if the area information associated with S-NSSAI # 1-1 includes the area where the UE is currently located, the UE will be the service of S-NSSAI # 1-1. It may be determined that it is located within the area. Conversely, if the area information associated with S-NSSAI # 1-1 does not include the area in which the UE is currently located, the AMF will say that the UE is in the service area of S-NSSAI # 1-1. It may be determined that it is located outside. The area information may be information acquired by AMF from another device such as UDM, or may be information set in 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 registration acceptance message together with the SM message (eg, PDU session establishment acceptance message). 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, the AMF can indicate that the procedure for SM has been accepted in the registration procedure.

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. The registration acceptance message may be sent to indicate that the UE request has been accepted, or the registration refusal message has been sent to indicate that the UE request has been rejected, based on the context held by the AMF. May be shown.

The UE receives the control message via 5GAN (gNB) (S608). When the control message is a registration acceptance message, the UE recognizes that the UE's 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, if 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 contained 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 within a predetermined period after the registration request message is transmitted.

If the control message is a registration acceptance message, the UE can further send a registration completion message to AMF via 5GAN (gNB) as a response message to the 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 5GAN (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 / reception of the registration refusal message.

In addition, each device may transition or maintain the state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission / reception of the registration acceptance message and / or the registration completion message. , Transition or maintenance to the state where the UE is not registered in the network (RM_DEREGISTERED state, or 5GMM-DEREGISTERED state) on the access that received the registration refusal message to the current PLMN based on the transmission and reception of the registration refusal message. You may. Further, the transition to each state of each device 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 carry out this procedure again based on the reason why the request of the UE is rejected, or may carry out the registration procedure for the core network_A or another cell.

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

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

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

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

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

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

[3.3. 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 executed by PLMN, and may be executed for each S-NSSAI (mapped S-NSSAI) and / or for each UE, which is the target of the NSSAA procedure. This procedure may be executed when the registration procedure is completed.

This procedure may be started by AMF140. For example, AMF140 may initiate this procedure based on the receipt of a registration request message from UE_A10. The AMF140 memorizes that at least one S-NSSAI or S-NSSAI mapped S-NSSAI requested by UE_A10 is an S-NSSAI that requires an NSSAA procedure, and further memorizes the result of the S-NSSAI NSSAA. 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. Furthermore, the information indicating the success of NSSAA may be allowed NSSAI. In other words, if the S-NSSAI is stored as allowed NSSAI, the AMF140 may recognize that the S-NSSAI's NSSAA was successful and may retain the NSSAA results.

Alternatively, AMF140 may start this procedure based on the request from AAA-S181. For example, based on the result of the NSSAA procedure that has already been 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.

The procedure will be explained below. The AMF140 sends an EAPID request message to UE_A10 via 5GAN (or gNB or non-3GPP access) (S700). The EAP ID request message may be included in the authentication request message (Authentication request message) which is a NAS message and may be transmitted, 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-NSSAI corresponding to this EAPID request message in the EAPID request message or the authentication request message including the EAPID request message. Here, the S-NSSAI may be the HPLMN S-NSSAI or the mapped S-NSSAI.

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

UE_A10 sends an EAPID response message to AMF140 based on the reception of the EAPID request message and / or the reception of S-NSSAI and / or the reception of the authentication request message (S702). The EAP ID response message may be included in the authentication response message (Authentication response message), which is a NAS message, and may be transmitted, 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 EAPID response message or the authentication request message including the EAPID response message including the S-NSSAI received from the AMF140. UE_A10 may send the EAPID response message including the EAPID which is the identification information of the UE corresponding to the S-NSSAI received from the AMF140. In addition, UE_A10 may include a plurality of EAPIDs and a plurality of S-NSSAIs in the EAPID response message, and each EAPID 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 reception of the EAPID response message from UE_A10 and / or the authentication response message which is the EAPID and / or NAS message (S704, S706). The AM140F may include the EAPID response message received from UE_A10 in the NSSAA authentication request message and send it to the AUSF180 and / or AAA-S181, or the EAPID and / included in the EAPID 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 EAPID and / or S-NSSAI contained in the authentication request message received from the AMF140 is an NSSAA authentication request. It may be included in the message and sent to AAA-S181.

AAA-S181 initiates the procedure for 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 AUFF180 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.

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 mapped S-NSSAI. AMF140 sends an authentication result message (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 NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message, or may be included in the NETWORK SLICE-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 send and receive "success" as an authentication result, they are associated with S-NSSAI sent and received together with the authentication result and stored as UE information as the state in which NSSAA is "successful". good. Similarly, when AMF140 and / or NW sends and receives "failure" 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 "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 S-NSSAI mapped S-NSSAI included in the allowed NSSAI. It may be stored as, or it may be stored by associating "allowed" with the received S-NSSAI. 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 the S-NSSAI mapped S-NSSAI included in the third rejected NSSAI. It may be stored as, or it may be stored 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 S-NSSAI mapped S included in the pending NSSAI. -If stored as NSSAI, UE_A10 may delete the S-NSSAI from the pending NSSAI, or delete the S-NSSAI associated with the S-NSSAI from the pending NSSAI.

The UE may also 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 has "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 non-registration procedure started by the network when there is a change in the allowed NSSAI and / or the S-NSSAI included in the rejected NSSAI for the UE. You may. The AMF may notify the UE of the new allowed NSSAI and the new rejected NSSAI using the UE setting update procedure. The AMF may notify the UE of the new rejected NSSAI using a network-initiated non-registration procedure.

If the UE moves out of the service area of S-NSSAI during the execution of this procedure, each device of the UE and / or the core network may cancel this procedure, and the UE may cancel the procedure. , Information about the S-NSSAI and / or the area associated with the S-NSSAI may be deleted. Here, the information about the area associated with S-NSSAI may be the third identification information received by the UE in the registration procedure.

In addition, the core network must not execute this procedure if the UE is outside the service area of S-NSSAI.

[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 executed by the network for the UE registered in the network.

Furthermore, devices in the core network such as AMF may start this procedure based on the update of network settings and / or the update of operator policy. The trigger of this procedure may be the detection of the mobility of the UE, the detection of the state change of the UE and / or the access network and / or the core network, or the state change of the network slice. It may be. Further, the trigger of this procedure may be the reception of a request from the DN and / or the application server of the DN, a change in network settings, or a change in operator policy. .. Further, the trigger of this procedure may be the expiration of the timer being executed. The trigger for the device in the core network to start this procedure is 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 or may start the behavior instructed by the network based on the completion of this procedure.

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 setting information of the UE that can be identified by using these control information can be obtained. , You may let the UE update. Further, the device in the core network may stop the function executed by the UE or cause the UE to start a new function by updating the setting information of the UE.

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

The AMF140 sends the configuration update command message including one or more of each NSSAI related to UE_A10 (hereinafter referred to as configured NSSAI, allowed NSSAI, rejected NSSAI, 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.

Furthermore, the AMF140 may send the setting update command message including the 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.

The 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 setting update command message from AMF140 via 5GAN120 (or gNB) (S800). UE_A10 may update the setting information of the UE based on the setting update command message and / or the identification information contained in the setting update command message.

The Allowed NSSAI and / or Rejected NSSAI included in the setting update command message is the same as the Allowed NSSAI and / or the Rejected NSSAI in the registration procedure in Chapter 3.2, and the S-NSSAI included in them is the third and / or the fourth. It may be associated with the identification information of.

Also, Allowed NSSAI included in the setting update command message may include S-NSSAI and a third identification information.

Further, the Rejected NSSAI included in the setting update command message may include the S-NSSAI and the third identification information. Then, the UE may store the S-NSSAI and the third identification information in association with each other based on the reception of the Rejected NSSAI. Further, the S-NSSAI may include a fourth identification information, and it may be shown that the fourth identification information is not in a place where the S-NSSAI can be connected, for example. Further, the UE may recognize that the S-NSSAI cannot be used in the connected area based on the reception of the Rejected NSSAI.

If the UE moves out of the service area indicated by the third identification information received in the procedure of Chapter 3.2 or 3.3 and this procedure is executed, the setting update command message will be displayed. In addition, it may contain information indicating that S-NSSAI is unavailable in the current area.

Also, if UE_A10 receives a TAI list, the received TAI list may be enabled, and if UE_A10 has already stored a valid TAI list, the old TAI list may be deleted or disabled. 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.

Also, UE_A10 may properly memorize each received NSSAI. Specifically, when UE_A10 receives the 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 in UE_A10" with "received configured NSSAI".

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

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

Or, when UE_A10 receives the configured NSSAI, "the first rejected NSSAI remembered by UE_A10 and associated with the current PLMN" and "the second rejected remembered by UE_A10 and associated with the current PLMN". At least one of "NSSAI" and "third rejected NSSAI remembered by UE_A10 and associated with the current PLMN" may be deleted.

In addition, when the UE_A10 receives the 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 more. Multiple "first NSSAI remembered by UE_A10 and associated with the current PLMN EPLMN" may be deleted.

Furthermore, when the UE_A10 receives the 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 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 in the 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 received and stored in advance by the UE belongs to EPLMN, UE_A10 receives allowed NSSAI. May be stored as "allowed NSSAI associated with the EPLMN to which the TAI included 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 "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, 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".

Further / or if multiple TAIs contained in the registration area stored by UE_A10 belong to different PLMNs, UE_A10 shall be stored with each "PLMN belonging to the TAI contained in the registration area" stored by UE_A10 and the current access type. You may replace "allowed NSSAI" associated with, with "received allowed NSSAI".

Specifically, when the registration area stored by UE_A10 contains 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 in "# 2".

Or, 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 "received allowed NSSAI" to ". It may be stored in one allowed NSSAI associated with the different PLMNs to which the TAI contained in the registration area belongs and the current access type.

Further / or when two or more TAIs contained in the registration area belong to multiple PLMNs, UE_A10 is stored in the UE_A10 "one or more PLMNs to which the TAI contained in the registration area belongs, and 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 contains 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 that 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".

Or, 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 "received allowed NSSAI" to ". 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 one or more 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 contains 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" only in the "allowed NSSAI # 1 associated with PLMN # 1 and the current access type".

When storing allowed NSSAI, UE_A10 may store allowed NSSAI in association with the registration area, or may store S-NSSAI included in allowed NSSAI 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". Further, when the "received allowed NSSAI" includes the 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 the UE_A10 receives the allowed NSSAI, "the first rejected NSSAI remembered by the UE_A10 and associated with the current PLMN" and "the first rejected NSSAI remembered by the UE_A10 and associated with the current PLMN". "The second rejected NSSAI" and "the second rejected NSSAI remembered by the UE_A10 and associated with the current PLMN and the current registration area" and "the second rejected NSSAI remembered by the UE_A10 and associated with the current PLMN," You may delete the S-NSSAI contained in the received allowed NSSAI from at least one of the "third rejected NSSAI", or you may delete the S-NSSAI contained in the allowed NSSAI received from all NSSAI. good.

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

Furthermore, when UE_A10 receives allowed NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "pending NSSAI stored by UE_A10 and associated with the current PLMN". Furthermore, when the UE_A10 receives the allowed 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". .. Further, when UE_A10 receives allowed 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". Or, when UE_A10 receives allowed NSSAI, delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI that UE_A10 remembers and is associated with all PLMNs". It's okay.

Furthermore, when the UE_A10 receives the 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 the S-NSSAI. It's okay. 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". , May be added to "Second Rejection NSSAI Associated with Current PLMN and Current Registration Area".

If UE_A10 receives the TAI list together with the rejected NSSAI, the current registration area will be indicated by the received TAI list. On the other hand, if UE_A10 does not receive the TAI list together with rejected NSSAI, the current registration area is indicated by the TAI list previously received and stored by UE_A10.

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 "Rejection Reason Value" Current Registration Area. The rejected S-NSSAI received in association with the "S-NSSAI" which is not possible in the second, associated with each "PLMN of one or more of its different PLMNs and the current registration area". It may be stored and / or added to "rejected NSSAI".

Further / or if one or more TAIs contained in the registration area belong to different PLMNs, the 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 contains 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 stored 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 "Rejection Reason Value" current registration area. The "rejected S-NSSAI" received in association with the "S-NSSAI" may be stored in "one second rejected NSSAI associated with the different PLMNs and the current registration area". ..

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will be stored by the UE_A10 as one second rejected associated with the multiple PLMNs and the current access type. 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 contains 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 that 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 included 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 "second rejected S- received. "NSSAI" may be stored only in "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" as the different one. Alternatively, it does not have to be stored as the second rejected NSSAI associated with multiple PLMNs.

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

Specifically, when the registration area stored by UE_A10 contains 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 so, UE_A10 stores 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 May be added to the third rejection NSSAI associated with the PLMN.

Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received rejected NSSAI may be deleted from "allowed NSSAI stored by 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". .. Further, 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". Or, when UE_A10 receives allowed NSSAI, delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI that UE_A10 remembers and is associated with all PLMNs". It's okay.

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". .. Further, 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 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 rejected NSSAI, it deletes 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". It's okay. Further, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "the first NSSAI stored by UE_A10 and associated with 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. Further, the UE sends a configuration update complete message to the AMF140 via 5GAN (gNB) as a response message to the configuration update command message based on the identification information contained in the configuration update command message. May (S802).

When UE_A10 sends a setting update completion command message, AMF140 receives a setting update completion message via 5GAN (gNB) (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 / 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. Further, when sending and receiving information indicating that the registration procedure needs to be executed, UE_A10 may start the registration procedure based on the completion of this procedure.

Furthermore, 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 the procedure for canceling the registration. This procedure may be a procedure for mobility management executed by the network 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 no longer has 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 by other procedures (eg NSSAA procedures) in the future.

First, AMF140 may start 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 5GAN (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 deregistered. Here, the reason value may be 5 GMM cause. Further, if the procedure is initiated based on the result of the NSSAA procedure, or upon completion of the NSSAA, the reason value may be a value indicating that no network slice is available. In that case, it may be 5GS 5GMM cause value # 62 “No network slices available”.

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 memory, and the behavior of the UE may be determined.

Furthermore, when the UE_A10 receives the 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 the S-NSSAI. It's okay. 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". , May be added to "Second Rejection NSSAI Associated with Current PLMN and Current Registration Area".

If UE_A10 receives the TAI list together with the rejected NSSAI, the current registration area will be indicated by the received TAI list. On the other hand, if UE_A10 does not receive the TAI list together with rejected NSSAI, the current registration area is indicated by the TAI list previously received and stored by UE_A10.

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 "Rejection Reason Value" Current Registration Area. The rejected S-NSSAI received in association with the "S-NSSAI" which is not possible in the second, associated with each "PLMN of one or more of its different PLMNs and the current registration area". It may be stored and / or added to "rejected NSSAI".

Further / or if one or more TAIs contained in the registration area belong to different PLMNs, the 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 contains 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 stored 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 "Rejection Reason Value" current registration area. The "rejected S-NSSAI" received in association with the "S-NSSAI" may be stored in "one second rejected NSSAI associated with the different PLMNs and the current registration area". ..

Further / or if multiple TAIs contained in the registration area belong to different PLMNs, the UE_A10 will be stored by the UE_A10 as one second rejected associated with the multiple PLMNs and the current access type. 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 contains 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 that 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 included 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 "second rejected S- received. "NSSAI" may be stored only in "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" as the different one. Alternatively, it does not have to be stored as the second rejected NSSAI associated with multiple PLMNs.

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

Specifically, when the registration area stored by UE_A10 contains 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 so, UE_A10 stores 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 May be added to the third rejection NSSAI associated with the PLMN.

Furthermore, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received rejected NSSAI may be deleted from "allowed NSSAI stored by 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". .. Further, 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". Or, when UE_A10 receives allowed NSSAI, delete the mapped S-NSSA or S-NSSAI included in the received allowed NSSAI from "the first NSSAI that UE_A10 remembers and is associated with all PLMNs". It's okay.

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". .. Further, 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 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 rejected NSSAI, it deletes 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". It's okay. Further, when UE_A10 receives rejected NSSAI, S-NSSAI included in the received allowed NSSAI may be deleted from "the first NSSAI stored by UE_A10 and associated with 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 5GAN (gNB). By receiving the non-registration request message, UE_A10 can recognize the contents of various identification information included in the non-registration request message.

UE_A10 may send a non-registration acceptance message (DEREGISTRAION ACCEPT message) to AMF140 via 5GAN (or gNB) in response to the reception of the non-registration request message. The non-registration acceptance message is a NAS message sent and received on the N1 interface. Further, the RRC message may be a control message transmitted / received between the UE and 5GAN (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.

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

As for the Rejected NSSAI included in the non-registration request message, the S-NSSAI included in the Rejected NSSAI in the registration procedure in Chapter 3.2 may be associated with the third and / or the fourth identification information.

Further, the Rejected NSSAI included in the non-registration request message may include the S-NSSAI and the third identification information. Then, the UE may store the S-NSSAI and the third identification information in association with each other based on the reception of the Rejected NSSAI. Further, the S-NSSAI may include a fourth identification information, and it may be shown that the fourth identification information is not in a place where the S-NSSAI can be connected, for example. Further, the UE may recognize that the S-NSSAI cannot be used in the connected area based on the reception of the Rejected NSSAI.

If the UE moves out of the service area indicated by the third identification information received in the procedures in Chapters 3.2 to 3.4 and this procedure is executed, the setting update command message will be displayed. In addition, it may contain information indicating that S-NSSAI is unavailable in the current area.

[4. Embodiment in one aspect of the present invention]
An embodiment of the present invention may be a combination of procedures described in one or more chapters 3. For example, in this embodiment, after the initial registration procedure described in Chapter 3 is completed, the NSSAA procedure may be performed and the UE setting update procedure may be executed.

Furthermore, each device (UE and device in the core network) may perform one or more movement 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, an example of a specific embodiment of the present invention will be described. In addition, each apparatus may carry out the behavior of a plurality of embodiments described below in combination.

Hereinafter, in the next section, the case where the UE moves from the inside to the outside of the S-NSSAI service area and the case where the UE moves from the inside to the outside of the S-NSSAI service area will be described.

[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 the UE and each device when the UE moves from the inside to the outside of the service area of S-NSSAI will be described.

The UE may receive a registration acceptance message containing the second identification information and / or the third identification information associated with each S-NSSAI contained in allowed NSSAI or Pending NSSSAI during the registration procedure in Chapter 3.2. .. Here, each S-NSSAI included in allowed NSSAI or Pending NSSSAI does not have to be associated with the fourth identification information, and the UE is in the service area of S-NSSAI included in allowed NSSAI or Pending NSSSAI. The UE and each device may be aware of this.

Next, for example, AMF may execute the NSSAA procedure in Chapter 3.3 for a specific S-NSSAI (S-NSSAI # 1-1) included in Pending NSSAI. If the UE moves out of the service area of S-NSSAI while NSSAA is being executed, each device of the UE and / or the core network may cancel this procedure, and the UE may cancel this procedure from the pending NSSAI. Information about the NSSAI and / or the area associated with the S-NSSAI may be deleted. Here, the information about the area associated with S-NSSAI may be the third identification information received by the UE in the registration procedure.

As a result, the UE may move out of the service area of S-NSSAI # 1-1 and recognize that S-NSSAI # 1-1 cannot be used.

Also, for example, the UE may establish a PDU session to a specific S-NSSAI (S-NSSAI # 1-2) included in allowed NSSAI. Here, when the UE moves out of the service area of S-NSSAI # 1-2, it may receive the non-registration request message including the rejected NSSAI described in Chapter 3.5. Here, the rejected NSSAI in the non-registration request message may include S-NSSAI # 1-2, and further, the third and / or the fourth identification information is associated with S-NSSAI # 1-2. good.

As a result, the UE may move out of the service area of S-NSSAI # 1-2 and recognize that S-NSSAI # 1-2 cannot be used.

The UE may move from within the service area of S-NSSAI # 1-1 to outside the service area of S-NSSAI # 1-1 at any time.

Furthermore, if the UE is located within the service area of S-NSSAI # 1-1, it is permitted to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may have been done. Furthermore, if the UE is located within the service area of S-NSSAI # 1-1, it initiates the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. May be good.

Furthermore, if the UE is located within the service area of S-NSSAI # 1-1, it is permitted to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may be set to be done. In other words, if the UE is located within the service area of S-NSSAI # 1-1, the PDU session establishment procedure and / or PDU session change procedure using S-NSSAI # 1-1 can be started. It may be set as follows.

Furthermore, if the UE is located outside the service area of S-NSSAI # 1-1, it is prohibited to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may have been done.

Furthermore, if the UE is located outside the service area of S-NSSAI # 1-1, it is prohibited to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may be set to be done. Furthermore, if the UE is located outside the service area of S-NSSAI # 1-1, the PDU session establishment procedure and / or PDU session change procedure using S-NSSAI # 1-1 will not be started. It may be set to.

In addition, the UE and / network will be based on the movement of the UE from within the service area of S-NSSAI # 1-1 to outside the service area of S-NSSAI # 1-1. A procedure for releasing the PDU session associated with -1 and / or the user plane resource associated with the PDU session may be initiated. Here, the procedure for releasing the PDU session associated with S-NSSAI # 1-1 may be the PDU session release procedure. Further, the network may be a device in the network. Specifically, the network may point to AMF or SMF.

In addition, the UE will move from Allowed NSSAI to S-NSSAI, which the UE remembers, based on the movement from within the service area of S-NSSAI # 1-1 to the outside of the service area of S-NSSAI # 1-1. You may delete # 1-1. In addition, the UE will change S-NSSAI # 1-1 to Rejected NSSAI based on the move from within the service area of S-NSSAI # 1-1 to the outside of the service area of S-NSSAI # 1-1. You may include it and memorize it. The Rejected NSSAI may be a Rejected NSSAI for managing an S-NSSAI that cannot be used in the current area.

In addition, the UE will move from the Pending NSSAI to the S-NSSAI that the UE remembers, based on the move from within the S-NSSAI # 1-1 service area to outside the S-NSSAI # 1-1 service area. You may delete # 1-1. In addition, the UE will change S-NSSAI # 1-1 to Rejected NSSAI based on the move from within the service area of S-NSSAI # 1-1 to the outside of the service area of S-NSSAI # 1-1. You may include it and memorize it. The Rejected NSSAI may be a Rejected NSSAI for managing an S-NSSAI that cannot be used in the current area.

In addition, the UE and / network will be based on the movement of the UE from within the service area of S-NSSAI # 1-1 to outside the service area of S-NSSAI # 1-1. Execution of the NSSAA procedure using -1 may be aborted.

In addition, the UE and / network will be based on the movement of the UE from within the service area of S-NSSAI # 1-1 to outside the service area of S-NSSAI # 1-1. You may set it so that the NSSAA procedure using -1 is not executed. In addition, the UE and / network will be based on the movement of the UE from within the service area of S-NSSAI # 1-1 to outside the service area of S-NSSAI # 1-1. It may be set so that the execution of the NSSAA procedure using -1 is prohibited.

[4.1. Second Embodiment]
Hereinafter, the second embodiment (hereinafter referred to as the present embodiment) will be described. In the present embodiment, the behavior of each device when the UE that has executed the registration procedure outside the service area of a specific S-NSSAI (S-NSSAI # 2) moves into the service area of the S-NSSAI # 2. An example will be described.

A UE that has executed a registration procedure outside the service area of S-NSSAI # 2 and received a control message containing rejected NSSAI and the third and / or fourth identification information from the core network is indicated by the third identification information. , Memorize the service area of S-NSSAI # 2.

Specifically, in the registration procedure in Chapter 3.2, the UE receives a registration acceptance message or registration refusal message containing the third and / or fourth identification information associated with each S-NSSAI included in rejected NSSSAI. You can do it. Here, the user may be in the service area of S-NSSAI included in rejected NSSAI, and the UE and each device may be aware of this.

Next, when the UE that recognizes that it has moved into the service area of the S-NSSAI moves into the service area of any S-NSSAI included in the rejected NSSIA, the UE moves from the rejected NSSAI to the S-. NSSAI may be deleted and the S-NSSAI may be stored in allowed NSSAI. For example, if the UE moves into the service area of S-NSSAI # 2 included in rejected NSSAI, the UE removes S-NSSAI # 2 from rejected NSSAI and adds S-NSSAI # 2 to allowed NSSAI. May be good.

Furthermore, the UE may transition to a state in which it is permitted or possible to start the execution of the PDU session establishment procedure using S-NSSAI # 2 and the PDU session change procedure, and the PDU session to S-NSSAI # 2. You may perform the establishment procedure.

The UE may move from outside the service area of S-NSSAI # 1-1 to inside the service area of S-NSSAI # 1-1 at any time.

Furthermore, if the UE is located within the service area of S-NSSAI # 1-1, it is permitted to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may have been done. Furthermore, if the UE is located within the service area of S-NSSAI # 1-1, it initiates the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. May be good.

Furthermore, if the UE is located within the service area of S-NSSAI # 1-1, it is permitted to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may be set to be done. In other words, if the UE is located within the service area of S-NSSAI # 1-1, the PDU session establishment procedure and / or PDU session change procedure using S-NSSAI # 1-1 can be started. It may be set as follows.

Furthermore, if the UE is located outside the service area of S-NSSAI # 1-1, it is prohibited to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may have been done.

Furthermore, if the UE is located outside the service area of S-NSSAI # 1-1, it is prohibited to start the PDU session establishment procedure and / or the PDU session change procedure using S-NSSAI # 1-1. It may be set to be done. Furthermore, if the UE is located outside the service area of S-NSSAI # 1-1, the PDU session establishment procedure and / or PDU session change procedure using S-NSSAI # 1-1 will not be started. It may be set to.

In addition, the UE and / network will be based on the movement of the UE from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1. The procedure for reestablishing the PDU session associated with -1 and / or the user plane resource associated with the PDU session may be initiated. Here, the procedure for reestablishing the PDU session associated with S-NSSAI # 1-1 may be the PDU session establishment procedure using S-NSSAI # 1-1. Further, the network may be a device in the network. Specifically, the network may point to AMF or SMF.

In addition, the UE will move from Rejected NSSAI to S-NSSAI, which the UE remembers, based on the movement from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1. You may delete # 1-1. In addition, the UE will convert S-NSSAI # 1-1 to Allowed NSSAI based on the move from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1. You may include it and memorize it. The Rejected NSSAI may be a Rejected NSSAI for managing an S-NSSAI that cannot be used in the current area.

In addition, the UE and / network will be based on the movement of the UE from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1. The NSSAA procedure using -1 may be initiated.

In addition, the UE and / network will be based on the movement of the UE from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1. The NSSAA procedure using -1 may be set to be executed. In addition, the UE and / network will be based on the movement of the UE from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1. It may be set to allow the execution of NSSAA procedures using -1.

In addition, the network is at least based on the movement of the UE from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1, at least S-NSSAI # 1-1. The UE setting update procedure or the de-registration procedure may be started using the and the fourth identification information. In other words, the network is, at least, based on the movement of the UE from outside the service area of S-NSSAI # 1-1 into the service area of S-NSSAI # 1-1. A configuration update command message or a DEREGISTRATION REQUEST message containing 1-1 and the fourth identification information may be sent to the UE. In this case, the fourth identification information may be information indicating that S-NSSAI # 1-1 cannot be used in the current area.

[5. Modification example]
The program that operates in 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 the information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, Hard Disk Drive (HDD), or other storage device system.

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

Further, each functional block or various features of the device used in the above-described embodiment can be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein can be 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 Combinations 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 also 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 the stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device or a kitchen device. , Cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living equipment.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment and includes design changes and the like within a range not deviating from the gist of the present invention. Further, the present invention can be variously modified within the scope of the claims, and the technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Will be. Further, the elements described in each of the above-described embodiments are included, and a configuration in which elements having the same effect are replaced with each other is also included.

Claims (11)

1. It is a UE (User Equipment) equipped with a control unit and a transmission / reception unit.
   The transmission / reception unit receives a control message including the first identification information from the control device, and receives the control message.
   When the control message is a registration acceptance message or a setting update command, the first identification information is Allowed NSSAI (Network Slice Selection Assistance Information) or Rejected NSSAI.
   When the control message is a registration refusal message or a non-registration request message, the first identification information is Rejected NSSAI.
   The first identification information includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information.
   The control unit stores the S-NSSAI and the area information in association with each other based on the reception of the first identification information.
   When the first identification information is Rejected NSSAI,
   The S-NSSAI includes a reason value and
   The reason value indicates that the user is not in a place where he / she can connect to the S-NSSAI.
   Based on the reception of the first identification information, it further recognizes that the S-NSSAI cannot be used in the connected area.
   UE characterized by that.
2. When moving from within the area indicated by the area information to outside the area indicated by the area information,
   The transmitting / receiving unit receives the second control message and receives the second control message.
   The second control message is a setting update command or a non-registration request message.
   The second control message contains information indicating that the S-NSSAI is unavailable in the current area.
   The UE according to claim 1, wherein the UE is characterized in that.
3. It is a core network device
   It has a control unit and a transmission / reception unit.
   The transmitter / receiver
   Receive a registration request message containing UE capability information from the UE (User Equipment),
   A registration acceptance message containing the first identification information is sent to the UE.
   The first identification information is Allowed NSSAI (Network Slice Selection Assistance Information), Rejected NSSAI, or Pending NSSAI.
   The first identification information includes S-NSSAI (Single Network Slice Selection Assistance Information).
   When the capability information of the UE indicates that the UE supports an area of service, the first identification information further includes area information associated with the S-NSSAI.
   A core network device characterized by that.
4. UE (User Equipment)
   It has a control unit and a transmission / reception unit.
   The transmission / reception unit receives a control message including the first identification information and network capability information from the control device, and receives the control message.
   When the capacity information of the network indicates that the network supports the area of service,
   The first identification information includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information.
   The control unit stores the S-NSSAI and the area information in association with each other based on the reception of the first identification information.
   UE characterized by that.
5. UE (User Equipment)
   It has a storage unit, a control unit, and a transmission / reception unit.
   The storage unit stores S-NSSAI (Single Network Slice Selection Assistance Information) in association with the area information.
   The control unit establishes a PDU (Protocol Data Unit) session associated with the S-NSSAI and establishes a PDU (Protocol Data Unit) session.
   When the UE moves from the area indicated by the area information to the outside of the area indicated by the area information.
   The transmission / reception unit carries out a PDU session release procedure for releasing the PDU session, and the transmission / reception unit performs a PDU session release procedure.
   The control unit
   Delete the above S-NSSAI from allowed NSSAI,
   Rejected NSSAI, memorized in the above S-NSSAI,
   The transmission / reception unit is set so that the start of the PDU session establishment procedure and the PDU session change procedure using the S-NSSAI is prohibited.
   UE characterized by that.
6. UE (User Equipment)
   It has a storage unit, a control unit, and a transmission / reception unit.
   The storage unit stores S-NSSAI (Single Network Slice Selection Assistance Information) in association with the area information.
   When the UE moves from outside the area indicated by the area information to inside the area indicated by the area information.
   The control unit
   Deleted the S-NSSAI from rejected NSSAI (Network Slice Selection Assistance Information).
   In allowed NSSAI, memorize in the above S-NSSAI,
   The transmission / reception unit is set so that the start of the PDU session establishment procedure and the PDU session change procedure using the S-NSSAI is permitted.
   UE characterized by that.
7. UE (User Equipment)
   It has a control unit and a transmission / reception unit.
   The transmission / reception unit receives a registration acceptance message including Pending NSSAI (Network Slice Selection Assistance Information) from the control device, and receives the registration acceptance message.
   The Pending NSSAI includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information.
   Based on the reception of the transmitting / receiving unit and the Pending NSSAI, the network slice authentication approval procedure using the S-NSSAI is executed.
   The control unit deletes the S-NSSAI and the area information from the Pending NSSAI when the control unit moves out of the area indicated by the area information during the execution of the network slice authentication approval procedure.
   UE characterized by that.
8. It is a core network device
   It has a control unit and a transmission / reception unit.
   The transmission / reception unit sends a registration acceptance message including Pending NSSAI (Network Slice Selection Assistance Information) to the UE (User Equipment).
   The Pending NSSAI includes S-NSSAI (Single Network Slice Selection Assistance Information) and area information.
   When the UE is located in the area indicated by the area information, the transmission / reception unit executes a network slice authentication approval procedure using the S-NSSAI.
   If the UE moves from the area indicated by the area information to the outside of the area indicated by the area information during the network slice authentication approval procedure using the S-NSSAI, the network slice authentication approval procedure is canceled. do,
   A core network device characterized by that.
9. AMF (Access and Mobility Management Function)
   It has a transmission / reception unit, a storage unit, and a control unit.
   The transmitting / receiving unit receives requested NSSAI (Network Slice Selection Assistance Information) including S-NSSAI (Single Network Slice Selection Assistance Information) from the UE (User Equipment) via the first area.
   The storage unit stores the S-NSSAI and the area information associated with the S-NSSAI, and stores the area information.
   The control unit
   Based on the reception of the S-NSSAI, the area information is confirmed and
   When the area information includes the first area, it is determined that the UE is in the area indicated by the area information.
   If the area information does not include the first area, it is determined that the UE is not in the area indicated by the area information.
   AMF characterized by that.
10. AMF (Access and Mobility Management Function)
    It has a transmission / reception unit, a storage unit, and a control unit.
    The transmission / reception unit receives a registration request message from the UE (User Equipment) via the first area, and receives the registration request message.
    The storage unit stores S-NSSAI (Single Network Slice Selection Assistance Information) set in the UE and area information associated with the S-NSSAI.
    The control unit
    If the registration request message does not include requested NSSAI (Network Slice Selection Assistance Information),
    When the area information includes the first area, it is determined that the UE is in the area indicated by the area information.
    If the area information does not include the first area, it is determined that the UE is not in the area indicated by the area information.
    AMF characterized by that.
11. SMF (Session Management Function)
    It has a control unit and a transmission / reception unit.
    The transmission / reception unit executes a PDU session establishment procedure for establishing a PDU (Protocol Data Unit) session.
    The control unit manages the PDU session in association with the area information.
    The transmission / reception unit receives first identification information from the AMF (Access and Mobility Management Function) indicating that the UE (User Equipment) has moved from the area indicated by the area information to the outside of the area indicated by the area information. ,
    The control unit releases the PDU session or releases the user plane resource associated with the PDU session based on the reception of the first identification information.
    SMF characterized by that.
    
    

Images