WO2021235271A1 - User Equipment (UE) AND COMMUNICATION CONTROL METHOD - Google Patents

Abstract

In a 5G system (5GS), control processing of User Equipment (UE) and control processing of a control device in a core network are unclear when the UE moves between public land mobile networks (PLMNs) and/or non-public networks (NPNs). Provided is a communication means for, in a 5G system (5GS), transitioning the state of User Equipment (UE) to a new state when the UE has moved between public land mobile networks (PLMNs), moved between non-public networks (NPNs), or moved between a PLMN and an NPN. Moreover, provided is a communication means for, in a 5GS, canceling a restriction of UE when the UE has moved between PLMNs, moved between NPNs, or moved between a PLMN and an NPN, the restriction having been executed by a control device in a core network.

Description

UE (User Equipment) and communication control method

This disclosure relates to UE (User Equipment) and communication control method. This application claims priority based on Japanese Patent Application No. 2020-088865 filed in Japan on May 21, 2020, the contents of which are incorporated herein by reference.

The 3GPP (3rd Generation Partnership Project) has begun studying the system architecture of the next generation, that is, the 5GS (5G System), which is the 5th generation (5G) mobile communication system, and will support new procedures and new functions. Discussions are taking place (see Non-Patent Document 1, Non-Patent Document 2, Non-Patent Document 3, and Non-Patent Document 4).

For example, optimization and diversification of communication procedures to support continuous mobile communication services for a wide variety of services, optimization of communication procedures, and optimization of system architecture according to diversification are also required. It is listed as a condition.

In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services. In 5GS, it is not possible for a specific user to use it for a specific purpose, such as NPN (Non-Public Network), which is defined separately from the public network PLMN (Public Land Mobile Network). The provision of public networks and the functions for realizing private networks are also being considered.

However, when the UE (User Equipment) is registered in the NPN, the processing of the control device of the core network and the processing of the UE are not clear.

One aspect of the present invention has been made in view of the above circumstances, and an object thereof is the processing of the control device of the core network and the processing of the UE when the UE is registered in the NPN in 5GS. It is to provide a realization method.

The UE (User Equipment; terminal device) of one aspect of the present invention is based on a transmission / reception unit that receives an indication indicating that an RRC (Radio Resource Control) connection has been suspended from a lower layer, and a transmission / reception unit that receives the indication. When the UE is registered in the SNPN (Stand-alone Non-Public Network), the control unit is provided with a control unit that transitions to 5GMM-CONNECTED (5G Mobility Management CONNECTED) mode with RRC inactive indication. Based on the selection of PLMN (Public land mobile network), the transition from the above 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE (5G Mobility Management IDLE) mode is characterized.

The UE (User Equipment; terminal device) communication control method of one aspect of the present invention includes a step of receiving an indication indicating that an RRC (Radio Resource Control) connection has been suspended from a lower layer, and a step of receiving the indication indicating that the RRC (Radio Resource Control) connection has been suspended. If the UE has a step to transition to 5GMM-CONNECTED (5G Mobility Management CONNECTED) mode with RRC inactive indication based on reception, and the UE is registered in the SNPN (Stand-alone Non-Public Network), the UE Is characterized by transitioning from the 5GMM-CONNECTED mode with RRC inactive indication to the 5GMM-IDLE (5G Mobility Management IDLE) mode based on the selection of PLMN (Public land mobile network).

According to one aspect of the present invention, in 5GS, it is possible to realize the control process of the control device in the core network and the control process of the UE when the UE moves between PLMNs and NPNs. Become. Furthermore, in 5GS, it is also possible to realize the control processing of the control device in the core network and the control processing of the UE when moving between the PLMN and the SNPN.

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 procedure of 1st to 4th. It is a figure explaining the registration procedure. It is a figure explaining the PDU session establishment procedure. It is a figure explaining the RRC connection release procedure.

The best mode for carrying out the present invention will be described with reference to the drawings.

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

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

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

In addition, Fig. 2 shows the devices / functions of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, UDM150, etc. Interfaces that connect devices and functions to each other are described.

In the following, these devices / functions are referred to as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5GAN, AMF, UPF, SMF, PCF, UDM, etc. 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.

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 referred to as a core network or a core network device. There is.

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), etc. may be a core network for virtual mobile communication operators and virtual mobile communication service providers.

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.

[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, 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 and receiving user data and control messages, or may respond to paging. Further, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.

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

Also, in connection management, the CM status for each UE is managed. The CM state may be synchronized between the UE and AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 interface connection (N2 connection) 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, function for sending and receiving the SM part of NAS message, function for notifying 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) sent 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 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]
Next, other devices and / or functions will be described.

PCF has a function to provide policy rules.

In addition, UDM has an authentication information processing function, a user identification processing function, an access authentication function, a registration / mobility management function, a subscriber information management function, and the like.

In addition, PCRF is connected to PGW and / or PDN, and has a function of performing QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and PDN. Further, the PCRF may be a device for creating and / or managing PCC (Policy and Charging Control) rules and / or routing rules used by each device when transmitting and receiving user data.

In addition, HSS is connected to MME and / or SCEF, and has a function to manage subscriber information. HSS subscriber information is referred to, for example, when controlling access to MME. In addition, the HSS may be connected to a location management device different from the MME.

In addition, SCEF is connected to DN and / or PDN, MME and HSS, and has a function as a relay device that transfers user data as a gateway connecting DN and / or PDN and core network_A. .. SCEF may be a gateway for non-IP communication. Furthermore, SCEF may have a function of converting non-IP communication and IP communication. Also, multiple such gateways may be located in the core network_A. The SCEF may be configured outside or inside the core network.

[3. Terminology / identification information used in each embodiment, explanation of procedure]
In each embodiment, at least one term / identification information and procedure to be used will be explained in advance.

[3.1. Explanation of terms and identification information used in each embodiment]
First, highly specialized terms used in each embodiment and identification information used in the procedure will be described in advance.

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.

Furthermore, the network may refer to PLMN (Public Land Mobile Network) or NPN, which will be described later. Further, when it is expressed that the UE makes a network selection, it may indicate that the UE makes a PLMN selection, or it may indicate that the UE makes an SNPN selection.

Also, the registered PLMN (registered PLMN) is the PLMN in which the UE is registered.

Equivalent PLMN is a PLMN that is treated as if it were the same PLMN as any PLMN in the network. For example, an equal PLMN may be one or more PLMNs treated the same as a registered PLMN.

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. In addition, SM messages include PDU session establishment request messages, PDU session establishment acceptance messages, PDU session completion messages, PDU session rejection messages, PDU session change request messages, PDU session change acceptance messages, PDU session change response messages, and the like. You may. The procedure for SM may also include a PDU session establishment procedure.

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.

In addition, the single registration mode is a mode in which UE_A10 maintains a common registration state for the 5GMM state and EMM state when N1 mode and S1 mode are available.

In addition, the dual registration mode is a mode in which UE_A10 maintains the registered state independently of the 5GMM state and the EMM state when the N1 mode and the S1 mode are available. In the case of dual registration mode, UE_A10 may be registered in the network only in N1 mode (that is, registered only in 5GC), or may be registered in the network only in S1 mode (registered only in EPC). Alternatively, it may be registered in the network (registered in both 5GC and EPC) in both N1 mode and S1 mode.

Also, in order to interwork between 5GS and EPC, UEs that support both 5GC and EPC NAS can operate in single registration mode or dual registration mode.

In addition, S1 mode is a mode that allows UE_A10 to access EPC via E-UTRAN. In other words, the S1 mode may be a mode in which messages are sent and received using the S1 interface. The S1 interface may be composed of an S1-MME interface and an S1-U interface.

In addition, N1 mode is a mode that allows UE_A10 to access 5GC via a 5G access network. In other words, the N1 mode may be a mode in which messages are sent and received using the N1 interface.

Further, APN (Access Point Name) may be identification information that identifies the core network and / or the external network such as PDN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 to connect the core network A_90.

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.

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.

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

A network slice 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 of only SST (Slice / Service type) or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating the operation of NS expected in terms of functions and services. Further, 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.

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.

In addition, SSC (Session and Service Continuity) mode indicates the mode of session service continuity (Session and Service Continuity) supported by the system and / or each device in the 5G system (5GS). More specifically, it may be a mode indicating the types of session service continuation supported by the PDU session established between UE_A10 and UPF. The SSC mode may be a mode indicating the type of session service continuation set for each PDU session. Further, the SSC mode may be composed of three modes, SSC mode 1, SSC mode 2, and SSC mode 3. The SSC mode associated with the PDU session does not have to be changed for the life of the PDU session.

The RRC (Radio Resource Control) connection is a connection established between the UE and the base station device in the access network. More specifically, an RRC connection is a connection established at a Uu reference point between a UE and a base station device in an access network. The RRC connection may be configured with a wireless bearer. Further, the RRC connection may be a connection established in 3GPP access. Further, the RRC connection may be a connection established in the RRC layer below the NAS layer. Further, the RRC connection may be a connection established and / or released by sending and receiving an RRC message of the RRC layer. Further, the RRC connection may be a connection that is suspended by sending and receiving RRC messages of the RRC layer.

In addition, 5GMM-CONNECTED mode with RRC inactive indication is a state indicating that the state of the NAS layer is a connected state even though the RRC layer is inactive. In other words, the 5GMM-CONNECTED mode with RRC inactive indication may be in a state where the radio bearer is released while maintaining the context of the NAS signaling connection and / or the NAS signaling connection.

Furthermore, 5GMM-CONNECTED mode with RRC inactive indication may be in a state where the RRC connection is suspended. More specifically, in 5GMM-CONNECTED mode with RRC inactive indication, the NAS layer state is the connected state, but the RRC connection may be suspended. In other words, the 5GMM-CONNECTED mode with RRC inactive indication may be in a suspended state of the RRC connection while maintaining the context of the NAS signaling connection and / or the NAS signaling connection.

Here, the UE may transition from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication from the lower layer based on the reception of information indicating that the RRC connection has been suspended. Furthermore, the UE transitions only the state for 3GPP access from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication from the lower layer based on the reception of information indicating that the RRC connection has been suspended. May be good. The information indicating that the RRC connection has been suspended may be an indication indicating that the RRC connection has been suspended.

In addition, support for 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer can be maintained in the connected state even when a notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean that it is supported. Furthermore, the use of 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer is maintained in the connected state even when the notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean.

Also, PDU session with suspended user-plane resources is a PDU session in which user plane resources are established or re-established and the wireless bearer is suspended. Here, the timing at which the wireless bearer is suspended may be the timing at which the UE transitions to 5GMM-CONNECTED mode with RRC inactive indication. Further, the radio bearer may be a data radio bearer.

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 TA list is a list that includes one or more TAs assigned to UE_A10 by the network. Note that UE_A10 may be able to move without executing the tracking area update procedure while moving within one or more TAs included in the TA list. In other words, the UE_A10 may be a group of information indicating an area in which the TA list can be moved without performing the tracking area update procedure. The TA list may be expressed as a TAI list composed of one or more TAI (Tracking area identity), and hereinafter, the TAI list may refer to the TA list.

LADN (Local Area Data Network) is a DN that a UE can connect to only in a specific location, and provides connectivity to a specific DNN (that is, LADN DNN). The LADN may be a DN that can be connected at a particular location by using a PDU session associated with a particular DNN. Further, the LADN may be a DN that can be connected at a specific location by using a PDU session associated with a specific combination of a specific DNN and a specific S-NSSAI.

LADN information is information related to LADN. The LADN information may be information indicating a specific LADN available to the UE. The LADN information may include LADN DNN and LADN service area information. More specifically, the LADN information may include one or more pieces of information existing for each LADN (hereinafter, referred to as information indicating LADN). Further, the information indicating LADN may include LADN DNN and LADN service area information. Here, the LADN DNN may be information that identifies the LADN, may be information that identifies the DN that is treated as the LADN, or may be a DNN that is used when establishing a PDU session for the LADN. ..

If the LADN information is the conventional LADN information, the LADN information may be the information having the configuration described above. Specifically, when the LADN information is conventional LADN information, the LADN service area may be the conventional LADN service area.

On the contrary, when the LADN information is the extended LADN information, the LADN information may be the information in which a part of the configuration described above is extended. Specifically, if the LADN information is extended LADN information, the LADN service area may be the extended LADN service area. Further, when the LADN information is extended LADN information, the information indicating LADN may further include information indicating the period during which the LADN service area is valid and / or information indicating the particle size of the LADN service area. Further, if the LADN information is extended LADN information, the information indicating LADN may further include S-NSSAI.

The LADN service area is an area where a PDU session can be established for LADN. The LADN service area may be an area where connection to LADN is possible. Further, the LADN service area may be an area indicated by the LADN service area information. Here, the LADN service area information may be information that identifies the LADN service area, and may be provided as a set of tracking areas or as a TAI (Tracking area identity) list.

If the LADN service area is a conventional LADN service area, the LADN service area may be an area composed of tracking areas that belong to the registration area to which the UE is currently connected. In other words, if the LADN service area is a conventional LADN service area, the LADN service area may be an area composed of one or more tracking areas. Conversely, when the LADN service area is an extended LADN service area, the LADN service area may be an area composed of the tracking area, or may be covered by some base stations in the tracking area. Area may be. Further, when the LADN service area is an extended LADN service area, the LADN service area may be an area having a size other than the area configured by the tracking area, or may be an area independent of the tracking area. May be good. In other words, if the LADN service area is an extended LADN service area, the LADN service area may be an area composed of one or more tracking areas, or may be composed of one or more tracking areas. It may be an area different from the area.

Further, when the LADN service area is an area composed of one or more tracking areas, the LADN service area information may be a tracking area ID list composed of one or more tracking area IDs. On the contrary, when the LADN service area is different from the area composed of one or more tracking areas, the LADN service area information may be information that requires assistance from RAN (Radio Access Network). , Information that does not require RAN assistance may be used. Here, the information that requires RAN assistance may be cell information or base station information. Further, the information that requires RAN assistance may be a cell ID or a base station ID. Further, the information that requires RAN assistance is not limited to these, and may be information defined by RAN. Further, the information that does not require RAN assistance may be physical location information or location information that can be acquired by the application. Further, the information that does not require RAN assistance is not limited to these, and may be information that can be acquired other than RAN. Here, RAN may be expressed as an access network. Conversely, the access network may be referred to as RAN.

Expansion of the LADN service area may mean using a LADN service area having a particle size different from that of the conventional LADN service area. Further, the expansion of the LADN service area may mean using the expanded LADN information different from the conventional LADN information. Further, the extension of the LADN service area may mean connecting to the extended LADN, which is different from the conventional LADN.

That is, if each device supports the expansion of the LADN service area, the expanded LADN service area, which is different from the conventional LADN service area, may be applicable in addition to the conventional LADN service area. Further, if each device supports the expansion of the LADN service area, the expanded LADN information different from the conventional LADN information may be available in addition to the conventional LADN information. Further, if each device supports the expansion of the LADN service area, it may be possible to connect to the extended LADN different from the conventional LADN in addition to the conventional LADN.

Conversely, if some of the devices do not support the expansion of the LADN service area, the expanded LADN service area may not be adaptable and only the conventional LADN service area may be adaptable. Further, if some of the devices do not support the expansion of the LADN service area, the expanded LADN information may not be available and only the traditional LADN information may be available. Further, if some of the devices do not support the expansion of the LADN service area, it may not be possible to connect to the expanded LADN, but only to the conventional LADN.

Further, if each device supports the usage restriction of the extended LADN service area, the extended LADN service area may not be applicable, and only the conventional LADN service area may be applicable. Further, if each device supports the use restriction of the extended LADN service area, the extended LADN information may not be available and only the conventional LADN information may be available. Further, if each device supports the extended usage restrictions of the LADN service area, it may not be possible to connect to the extended LADN, but only to the conventional LADN.

Conversely, if each device does not support the use restrictions for the extended LADN service area, the extended LADN service area may also be adaptable. Further, if each device does not support the use restrictions of the extended LADN service area, the extended LADN information may also be available. In addition, if each device does not support the extended usage restrictions of the LADN service area, it may be possible to connect to the extended LADN.

A PDU session for LADN (PDU session for LADN) is a PDU session associated with a DNN associated with LADN. The PDU session for LADN may be a PDU session established for LADN. In other words, it may be a PDU session established between the UE and LADN, or it may be a PDU session used for user data communication between the UE and LADN. The PDU session for LADN may be a PDU session that can be established only in the LADN service area. In other words, the UE may be able to establish a PDU session for LADN by using a particular DNN at a particular location. Furthermore, in other words, the UE may be able to establish a PDU session for LADN at a particular location by using a particular combination of a particular DNN and a particular S-NSSAI.

In addition, Non-Public Network (NPN) is a private network that is used by specific users for specific purposes, such as private use such as companies, not for general use. There are two types of NPN: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. When NPN is described below, it may mean both SNPN and Public network integrated NPN.

SNPN is a network operated by the NPN operator and not affected by the functional parts provided by PLMN. In other words, the SNPN is an NPN-only network independent of the publicly available PLMN. The SNPN may be a network identified by the SNPN identity (SNPN ID). The SNPN ID may be information that is a combination of the PLMN ID and the Network identifier (NID). The PLMN ID used for the SNPN ID may be information reserved for the private network, and for example, the MCC included in the PLMN ID may be 999. Further, when the UE is registered in the SNPN, the registered SNPN may be referred to as a registered SNPN or RSNPN (registered SNPN).

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

Public network integrated NPN is a network realized by using the functional parts of PLMN. In other words, the Public network integrated NPN is an NPN that is virtually realized within the PLMN. Furthermore, Public network integrated NPN is an NPN that can be created via PLMN. The Public network integrated NPN may be realized by using the function of the network slice. Specifically, the Public network integrated NPN may be a feasible network by using the network slice assigned for the NPN. In this case, the Public network integrated NPN may be identified by S-NSSAI or by a combination of S-NSSAI and CAG ID.

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

CAG (Closed Access Groups) ID is information that identifies a group of subscribers who are allowed to connect to one or more cells associated with CAG. The CAG may be a group identified by the CAG ID. CAG is a group used to realize Public network integrated NPN in network slices. The CAG may be used to prevent attempts to access network slices assigned for NPNs from UEs that do not allow NPNs. Furthermore, the CAG ID is unique information within the PLMN.

A UE with SNPN enabled (SNPN enable UE) is a UE for which the use of SNPN is set. An SNPN-enabled UE may store at least one piece of information about the SNPN. In other words, the setting information of the UE in which the SNPN is valid may include information indicating that the SNPN can be used. In addition, SNPN-enabled UEs may support SNPN access modes. In other words, a UE with SNPN enabled may operate in SNPN access mode.

SNPN access mode (SNPN access mode) is the mode in which SNPN is selected. The SNPN access mode may be a mode in which the UE is registered in the SNPN. Further, the SNPN access mode may be a mode in which the UE is connected to the SNPN. In other words, a UE operating in SNPN access mode may select only SNPN when selecting a network. More specifically, a UE operating in SNPN access mode may select only SNPN via the Uu interface when selecting a network. In other words, a UE operating in SNPN access mode may select SNPN instead of PLMN when selecting a network. Here, a UE operating in the SNPN access mode may be expressed as a UE in the SNPN access mode. Further, the UE in the SNPN access mode may be a UE in which the SNPN is valid.

Equivalent PLMN may be an SNPN that is treated as if it were the same SNPN as any SNPN. For example, an equal SNPN may be one or more SNPNs that are treated the same as a registered SNPN.

Furthermore, the equal SNPN may be a PLMN that is treated as if it were the same SNPN as any SNPN. For example, the equal SNPN may be one or more PLMNs treated the same as the registered SNPN.

Further, the equal SNPN may be one or more SNPNs identified by the same PLMN ID as any SNPN, or may be a PLMN. For example, the equal SNPN may be one or more SNPNs identified by the same PLMN ID as the registered SNPN, or it may be a PLMN. Further, the equal SNPN may be a PLMN identified by the same PLMN ID as the registered SNPN, and an equal PLMN of the PLMN.

The first identification information is information indicating the suspension of the RRC connection. The first identification information may be a suspend setting information element. Further, the first identification information may be a suspend indication. Further, the first identification information may be identification information indicating that the RRC connection is suspended. Further, the first identification information may be identification information indicating that the RRC connection has been suspended.

Further, the first identification information may be information for transitioning the state of the RRC connection to the RRC_INACTIVE state. In other words, the first identification information may be information indicating that the RRC layer transitions to the disabled state.

Further, the first identification information is based on the identification information received by the network and / or the capability information of the network and / or the operator policy and / or the state of the network and / or the registration information of the user. It may be information to be selected and determined. Further, the first identification information may be information selected and determined based on other identification information selected by the network in this procedure.

The eleventh identification information is information indicating the PDU session type. The eleventh identification information may be information indicating the PDU session type requested by the UE. More specifically, the eleventh identification information may be information indicating the PDU session type requested by the UE and associated with the PDU session established in this procedure. Further, the eleventh identification information may be information selected and determined based on the setting of the UE and / or the state of the UE and / or the user policy and / or the request of the application.

Here, the PDU session type selected by the UE may be set in the eleventh identification information. Specifically, IPv4 may be set or IPv6 may be set as the PDU session type in the eleventh identification information. Further, IPv4v6 may be set as the PDU session type in the eleventh identification information. Further, the eleventh identification information may be set to Unstructured or Ethernet as the PDU session type. The PDU session type set in the eleventh identification information is not limited to these.

The twelfth identification information is information indicating DNN. The twelfth identification information may be information indicating the DNN requested by the UE. More specifically, the twelfth identification information may be information indicating the DNN associated with the PDU session established in this procedure requested by the UE. Further, the twelfth identification information may be information selected and determined based on the setting of the UE and / or the state of the UE and / or the user policy and / or the request of the application.

The thirteenth identification information is information indicating S-NSSAI. The thirteenth identification information may be information indicating S-NSSAI requested by the UE. More specifically, the thirteenth identification information may be information indicating the S-NSSAI associated with the PDU session established in this procedure, which is requested by the UE. Further, the thirteenth identification information may be information selected and determined based on the setting of the UE and / or the state of the UE and / or the user policy and / or the request of the application. Further, the thirteenth identification information may be the S-NSSAI included in the NSSAI transmitted / received in the registration procedure, or may be the S-NSSAI stored in the UE.

The 21st identification information is information indicating the PDU session type. The 21st identification information may be information indicating the PDU session type selected by the network. More specifically, the 21st identification information may be information indicating the PDU session type selected by the network and associated with the PDU session established in this procedure.

Further, the 21st identification information is based on the identification information received by the network and / or the capability information of the network and / or the operator policy and / or the state of the network and / or the registration information of the user. It may be information to be selected and determined. Further, the 21st identification information may be information selected and determined based on other identification information selected by the network in this procedure.

Here, the PDU session type selected by the network may be set in the 21st identification information. Specifically, IPv4 may be set or IPv6 may be set as the PDU session type in the 21st identification information. Further, IPv4v6 may be set as the PDU session type in the 21st identification information. Further, the 21st identification information may be set to Unstructured or Ethernet as the PDU session type. The PDU session type set in the 21st identification information is not limited to these.

Further, the PDU session type set in the 21st identification information may be the same PDU session type as the PDU session type set in the 11th identification information received, or the 11th identification information received may be the same. The PDU session type may be different from the set PDU session type.

The 22nd identification information is information indicating DNN. The 22nd identification information may be information indicating the DNN selected by the network. More specifically, the 22nd identification information may be network-selected information indicating the DNN associated with the PDU session established in this procedure.

Further, the 22nd identification information is based on the identification information received by the network and / or the capability information of the network and / or the operator policy and / or the state of the network and / or the registration information of the user. It may be information to be selected and determined. Further, the 22nd identification information may be information selected and determined based on other identification information selected by the network in this procedure.

The 23rd identification information is information indicating S-NSSAI. The 23rd identification information may be information indicating S-NSSAI selected by the network. More specifically, the 23rd identification information may be network-selected information indicating the S-NSSAI associated with the PDU session established in this procedure.

In addition, the 23rd identification information is the identification information received by the network and / or the information associated with the NSI, and / or the capability information of the network, and / or the operator policy, and / or the state of the network, and / Or the information may be selected and determined based on the user's registration information or the like. Further, the 23rd identification information may be information selected and determined based on other identification information selected by the network in this procedure.

The 24th identification information is a reason value indicating the reason why the UE request is not permitted. The 24th identification information may be a 5GSM (5GS Session Management) reason value. Further, the 24th identification information may be information indicating that the PDU session type requested by the UE is not permitted. In other words, the 24th identification information may be information indicating that a PDU session type other than the PDU session type requested by the UE is permitted.

Further, the 24th identification information is the identification information received from the UE and / or the capability information of the network and / or the operator policy and / or the state of the network and / or the user registration information and / or the UE. The information may be selected and determined by the network based on the area to which it currently belongs.

Furthermore, the 24th identification information may be the 50th 5GSM reason value indicating that only IPv4 is permitted as the PDU session type. In other words, the 24th identification information may be 5GSM cause # 50 "PDU session type IPv4 only allowed". Note that 5GSM cause # 50 "PDU session type IPv4 only allowed" may be a reason value indicating that only IPv4 is permitted as the PDU session type for the requested IP connectivity.

Furthermore, the 24th identification information may be the 51st 5GSM reason value indicating that only IPv6 is permitted as the PDU session type. In other words, the 24th identification information may be 5GSM cause # 51 "PDU session type IPv6 only allowed". Note that 5GSM cause # 51 "PDU session type IPv6 only allowed" may be a reason value indicating that only IPv6 is permitted as the PDU session type for the requested IP connectivity.

Furthermore, the 24th identification information may be information indicating that IPv4 v6 is not permitted as the PDU session type. The 24th identification information may be information indicating that IPv4 is not permitted as the PDU session type. The 24th identification information may be information indicating that IPv6 is not permitted as the PDU session type.

Furthermore, the 24th identification information may be information indicating that the PDU session type cannot establish an IPv4 PDU session using the same DNN and / or the same S-NSSAI. Further, the 24th identification information may be information indicating that the PDU session type cannot establish an IPv6 PDU session using the same DNN and / or the same S-NSSAI.

[3.2. Explanation of procedures used in each embodiment]
Next, the procedure used in each embodiment will be described. The procedure used in each embodiment includes a registration procedure (Registration procedure), a PDU session establishment procedure (PDU session establishment procedure), and a UE setting update procedure (Generic UE configuration update procedure). 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.1. Registration procedure]
First, the registration procedure will be described with reference to FIG. 7. The registration procedure is a procedure in 5GS. 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 (RM-DEREGISTERED state). In addition, each device (particularly UE and AMF) can transition to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.

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

The UE may start the registration procedure when it has mobility across TAs. In other words, the UE may initiate the registration process when it moves to a TA that is different from the TA shown in the TA list it holds. In addition, the UE may initiate this procedure when the running timer expires. 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. Further, the UE may start the registration procedure based on the completion of the UE setting update procedure. The UE is not limited to these, and can execute the registration procedure at any timing.

Furthermore, the UE may start the registration procedure on a regular basis even if it is in the registered state. In other words, the UE may initiate the registration process based on the expiration of the timer. Further, the UE may start the registration procedure with the LADN information stored. In addition, the UE may initiate the registration process with the PDU session established. The PDU session may be a PDU session associated with LADN information, or may be a PDU session for LADN. Further, the PDU session may be a PDU session associated with NSSAI.

Note that the registration procedure executed based on the mobility of the UE and the registration procedure executed regularly may be expressed as the registration procedure for mobility and registration renewal. In other words, the registration procedure for mobility and renewal of registration may be a registration procedure performed based on the mobility of the UE, or may be a registration procedure performed periodically. Further, the registration procedure for mobility and registration renewal may be a registration procedure executed based on the setting update of the UE. Further, the registration procedure for mobility and registration renewal may be a registration procedure executed to establish a communication path for transmitting and receiving user data. Further, the registration procedure for mobility and registration renewal may be a registration procedure performed based on a request from the network. Further, in other words, the registration procedure for mobility and registration renewal may be a registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration renewal may be referred to as this procedure.

Next, we will explain each step of the registration procedure. The registration procedure described below may be an initial registration procedure or a registration procedure for mobility and registration renewal.

First, the UE starts the registration procedure by sending a registration request message to AMF (S800) (S802) (S804). Specifically, the UE sends an RRC message including a registration request message to 5GAN (or gNB) (S800). The registration request message is a NAS message. Further, the RRC message may be a control message transmitted / received between the UE and 5GAN (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, the UE may send one or more identification information by including it in a registration request message and / or an RRC message, but a control message different from these, for example, a layer lower than the RRC layer (for example, an RRC layer). , MAC layer, RLC layer, PDCP layer) may be included in the control message and transmitted. By transmitting these identification information, the UE may indicate that the UE supports each function, or may indicate a request of the UE. 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 to the same identification information or may be transmitted / received as different identification information.

The UE can also send the registration request message by including the SM message (eg, PDU session establishment request message), or by sending the SM message (eg, PDU session establishment request message) together with the registration request message. The PDU session establishment procedure may be started during the registration procedure.

When 5GAN (or gNB) receives an RRC message including a registration request message, it selects the AMF to which the registration request message is forwarded (S802). Note that 5GAN (or gNB) can select AMF based on the information contained in the registration request message and / or RRC message. 5GAN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S804).

When the AMF 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 AMF) accepts the UE's request. The AMF initiates the procedure (A) in FIG. 7 if the first condition determination is true, whereas the AMF initiates the procedure (B) in FIG. 7 if the first condition determination is false.

The first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF. For example, if the network allows the UE request, the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be false. The condition for determining the truth of the first condition determination is not limited to the above-mentioned condition.

First, the case where the first condition discrimination is true will be described. The AMF can first execute the fourth condition determination in the procedure (A) of FIG. The fourth condition determination is for determining whether or not the AMF sends and receives SM messages to and from the SMF.

The fourth condition determination may be executed based on whether or not the AMF has received the SM message. Further, the fourth condition determination may be executed based on whether the registration request message includes the SM message. For example, if the AMF received the SM message and / or if the registration request message contained the SM message, the fourth condition determination may be true and if the AMF did not receive the SM message. And / or if the registration request message does not contain an SM message, the fourth condition determination may be false. The condition for determining the truth of the fourth condition determination is not limited to the above-mentioned condition.

AMF selects SMF if the fourth condition is true and sends and receives SM messages to and from the selected SMF, whereas AMF is false if the fourth condition is false. , Do not execute them (S806). Further, even if the fourth condition determination is true, the AMF may cancel the procedure of FIG. 7 (A) when it receives an SM message indicating rejection from the SMF. At this time, AMF can start the procedure of (B) in FIG.

In S806, when sending and receiving SM messages to and from SMF, AMF can notify SMF of the identification information received in the registration request message. The SMF can acquire the identification information received from the AMF by sending and receiving SM messages to and from the AMF.

The AMF then sends the UE via 5GAN (or gNB) as a response message to the registration request message based on the receipt of the registration request message and / or the completion of sending and receiving the SM message to and from the SMF. Send a Registration accept message (S808). For example, if the fourth condition determination is false, the AMF may send a registration acceptance message based on the receipt of the registration request message from the UE. Further, if the fourth condition determination is true, the AMF may send a registration acceptance message based on the completion of sending and receiving the SM message to and from the SMF. The registration acceptance message is a NAS message sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and 5GAN (gNB).

AMF may send one or more identification information in the registration acceptance message. By transmitting these identification information, the AMF may indicate that the network supports each function, or may indicate that the UE request has been accepted. 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 to the same identification information or may be transmitted / received as different identification information.

In addition, AMF indicates which identification information is included in the registration acceptance message, each identification information received, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status. , And / or based on the user's registration information and / or the context held by AMF, etc., may be selected and determined.

Further, the AMF can send the registration acceptance message including the SM message (for example, the PDU session establishment acceptance message), or send the SM message (for example, the PDU session establishment acceptance message) together with the registration acceptance message. 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 and the fourth condition determination is true. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true. 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. It may be shown that the request of the UE has been accepted by sending the registration acceptance message based on the context held by the AMF.

In addition, the AMF may send the registration acceptance message with information indicating that some of the UE's requests have been rejected, or it may send information indicating that some of the UE's requests have been rejected. This may indicate the reason why some of the UE's requests were rejected. In addition, the UE may recognize why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by AMF is not permitted.

The UE receives the registration acceptance message via 5GAN (gNB) (S808). By receiving the registration acceptance message, the UE can recognize 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.

The UE can also send a registration completion message to AMF via 5GAN (gNB) as a response message to the registration acceptance message (S810). 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) (S810). Further, each device completes the procedure (A) in FIG. 7 based on the transmission / reception of the registration acceptance message and / or the registration completion message.

Next, the case where the first condition discrimination is false will be described. In the procedure (B) of FIG. 7, the AMF sends a registration rejection message to the UE via 5GAN (gNB) as a response message to the registration request message (S812). Here, the registration refusal 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).

Note that the AMF may indicate that the UE request by the registration request message has been rejected by sending the registration refusal message. In addition, the AMF may send the registration refusal message with information indicating the reason for refusal, or may send the reason for refusal to indicate the reason for refusal. Further, the UE may recognize the reason why the UE's request is rejected by receiving the information indicating the reason why the UE's request is rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by AMF is not permitted.

UE receives a registration refusal message via 5GAN (gNB) (S812). By receiving the registration refusal message, the UE can recognize that the UE's request by the registration request message has been rejected and the contents of various identification information contained in the registration refusal message. Further, the UE may recognize that the request of the UE has been rejected if the registration refusal message is not received even after a predetermined period has elapsed after the registration request message is transmitted. Each device completes the procedure (B) in this procedure based on the transmission / reception of the registration refusal message.

Note that the procedure (B) in Fig. 7 may be started when the procedure in (A) in Fig. 7 is canceled. In the procedure (A) of FIG. 7, if the fourth condition determination is true, the AMF may send the registration refusal message including the SM message indicating rejection such as the PDU session establishment refusal message. , The inclusion of an SM message indicating rejection may indicate that the procedure for SM has been rejected. In that case, the UE may further receive an SM message indicating rejection, such as a PDU session establishment refusal message, or may recognize that the procedure for SM has been rejected.

Each device completes the registration procedure based on the completion of the procedure (A) or (B) in Fig. 7. Each device may transition to the state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure (A) in FIG. 7, or the procedure in (B) in FIG. 7 is completed. Based on the above, the UE may be maintained in the state of not being registered in the network (RM_DEREGISTERED state), or the UE may be transitioned to the state of not being registered in the network. Further, the transition of each device to each state may be performed based on the completion of the registration procedure or may be performed based on the establishment of the PDU session.

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

[3.2.2. PDU session establishment procedure]
Next, an outline of the PDU session establishment procedure for establishing a PDU session for a DN will be described with reference to FIG. The PDU session establishment procedure is a procedure in 5GS. Hereinafter, this procedure refers to the procedure for establishing a PDU session. The PDU session establishment procedure is a procedure for each device to establish a PDU session. Each device can start the PDU session establishment procedure at any time when the registration procedure is completed and the registration state is reached. In addition, each device may be able to execute the PDU session establishment procedure in the registration procedure. In addition, each device may establish a PDU session based on the completion of the PDU session establishment procedure.

The PDU session establishment procedure may be a procedure initiated by the UE or a procedure requested and initiated by the UE. In other words, the PDU session establishment procedure may be a UE request PDU session establishment procedure. Each device can establish a plurality of PDU sessions by executing the PDU session establishment procedure a plurality of times.

Here, if the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for LADN, each device establishes a PDU session for LADN based on the completion of the PDU session establishment procedure. You may. In other words, if the PDU session establishment procedure is a PDU session establishment procedure using LADN DNN, each device may establish a PDU session for LADN based on the completion of the PDU session establishment procedure.

In addition, if the UE is located in an area where connection to LADN is possible and / or in the LADN service area, the PDU session establishment procedure to establish a PDU session for LADN. May start. Conversely, if the UE is located outside the LADN service area, execution of the PDU session establishment procedure for establishing a PDU session for LADN may be prohibited.

In other words, each device establishes a PDU session for LADN if the UE is located in an area where it can connect to LADN and / or if the UE is located in the LADN service area. In addition, the PDU session establishment procedure may be executed. Conversely, the network device may reject the request for a PDU session establishment procedure to establish a PDU session for LADN if the UE is located outside the LADN service area.

First, the UE sends a NAS message containing a PDU session establishment request message to the SMF via 5GAN (gNB) and AMF (S900) (S902) (S904), PDU session. Start the establishment procedure.

Specifically, the UE sends a NAS message including a PDU session establishment request message to AMF via 5GAN (gNB) via the N1 interface (S900). The NAS message including the PDU session establishment request message may be an MM message. Further, the MM message may be an uplink NAS transport (UL NAS TRANSPORT) message. Here, when it is expressed that the PDU session establishment request message includes identification information and / or a value, it may mean that it is included in the MM message including the PDU session establishment request message.

Here, the UE may transmit at least one of the 11th to 13th identification information including the identification information in the PDU session establishment request message and / or the NAS message, but these are different. It may be included in the control message of a control message, for example, a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, a PDCP layer) and transmitted. These identifications may be included in these messages to indicate the UE's request. 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.

Specifically, the UE may include the eleventh identification information in the PDU session establishment request message. Further, the UE may include the twelfth identification information and / or the thirteenth identification information in the uplink NAS transport message together with the PDU session establishment request message containing at least the eleventh identification information. In addition, the UE may send the uplink NAS transport message to the AMF (S900). In other words, the UE may send the twelfth identification information and / or the thirteenth identification information to the AMF together with the PDU session establishment request message containing the eleventh identification information. In other words, the UE may send a PDU session establishment request message containing the eleventh identification information to the AMF together with the twelfth identification information and / or the thirteenth identification information.

Further, the UE may indicate a request for establishment of the PDU session establishment request message of the PDU session type indicated by the eleventh identification information by transmitting the eleventh identification information. Further, the UE may indicate the PDU session type requested by the UE by transmitting the eleventh identification information.

Furthermore, the UE may indicate a request to establish a PDU session associated with the DNN indicated by the twelfth identification information by transmitting the twelfth identification information. Further, the UE may indicate the DNN requested by the UE by transmitting the twelfth identification information. The twelfth identification information may be a DNN that identifies a DN that supports one or more functions indicated by the identification information transmitted and received together with the twelfth identification information. Further, the twelfth identification information may be the DNN received in the registration procedure or may be the LADN DNN.

Furthermore, the UE may indicate a request for establishing a PDU session associated with the S-NSSAI indicated by the thirteenth identification information by transmitting the thirteenth identification information. Further, the UE may indicate the S-NSSAI requested by the UE by transmitting the thirteenth identification information. The thirteenth identification information may be S-NSSAI that identifies an NS that supports one or more functions indicated by the identification information transmitted and received together with the thirteenth identification information.

When the AMF receives the NAS message including the PDU session establishment request message (S900), it extracts the PDU session establishment request message from the NAS message and selects SMF as the forwarding destination of the PDU session establishment request message (S902). In addition, AMF shall include each identification information and / or subscriber information contained in the PDU session establishment request message and / or NAS message, and / or network capability information, and / or operator policy, and / or network status. And / or the transfer destination SMF may be selected based on the user's registration information and / or the context held by the AMF.

AMF forwards the PDU session establishment request message to the selected SMF via the N11 interface (S904).

When the SMF receives the PDU session establishment request message (S904), it recognizes various identification information contained in the PDU session establishment request message. Then, the SMF executes the third condition determination. The third condition determination is for the SMF to determine whether or not to accept the UE's request. In the third condition determination, the SMF determines whether the third condition determination is true or false. If the third condition determination is true, the procedure of FIG. 8 (A) is started, and if the third condition determination is false, the procedure of FIG. 8 (B) is started.

The third condition determination is the PDU session establishment request message and / or each identification information included in the PDU session establishment request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy. , And / or based on the state of the network, and / or the user's registration information, and / or the context held by the SMF, etc. For example, if the network allows the UE request, the third condition may be true. Also, if the network does not allow the UE request, the third condition determination may be false. Furthermore, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the third condition determination may be true and does not support the functions required by the UE. In this case, the third condition determination may be false. Further, if the transmitted / received identification information is permitted, the third condition determination may be true, and if the transmitted / received identification information is not permitted, the third condition determination may be false. The condition for determining the truth of the third condition determination is not limited to the above-mentioned condition.

Next, the steps when the third condition determination is true, that is, each step of the procedure (A) in FIG. 8 will be described. The SMF selects the UPF to which the PDU session is established, sends a session establishment request message to the selected UPF via the N4 interface (S906), and starts the procedure of (A) in FIG.

Here, the SMF obtains each identification information and / or subscriber information and / or network capability information acquired based on the reception of the PDU session establishment request message, and / or the operator policy, and / or the network status. And / or one or more UPFs may be selected based on the user's registration information and / or the context held by the SMF. When a plurality of UPFs are selected, the SMF may send a session establishment request message to each UPF.

The UPF receives the session establishment request message from the SMF (S906) via the N4 interface and creates a context for the PDU session. In addition, the UPF receives the session establishment request message and / or sends the session establishment response message to the SMF via the N4 interface based on the creation of the context for the PDU session (S908).

The SMF receives the session establishment response message from the UPF via the N4 interface as a response message to the session establishment request message (S908). The SMF may assign an address to the UE based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the session establishment response message.

The SMF receives the PDU session establishment request message and / or selects the UPF and / or receives the session establishment response message and / or the UE via the AMF based on the completion of the address assignment of the address assigned to the UE. Sends a PDU session establishment acceptance message to (S910) (S912).

Specifically, when the SMF sends a PDU session establishment acceptance message to the AMF via the N11 interface (S910), the AMF that receives the PDU session establishment request message establishes a PDU session to the UE via the N1 interface. Send a NAS message containing an acceptance message (S912). The PDU session establishment acceptance message may be a NAS message and may be a response message to the PDU session establishment request. In addition, the PDU session establishment acceptance message may be sent and received by including the N1 interface in the MM message. Further, the MM message may be a NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, when it is expressed that the PDU session establishment acceptance message includes identification information and / or a value, it may mean that it is included in the MM message including the PDU session establishment acceptance message. In addition, the PDU session establishment acceptance message can indicate that the PDU session establishment has been accepted.

Here, the SMF and AMF may indicate that the UE request by the PDU session establishment request has been accepted by sending the PDU session establishment acceptance message.

The SMF and AMF may send the PDU session establishment acceptance message including at least one of the 21st to 24th identification information. In addition, SMF and AMF may indicate that the network supports each function by transmitting these identification information, or may indicate that the request of the UE has been accepted. 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 to the same identification information or may be transmitted / received as different identification information.

Further, the SMF and AMF may indicate acceptance of the PDU session establishment request of the PDU session type indicated by the 21st identification information by transmitting the 21st identification information, and the PDU session is established. You may show that. In addition, the SMF and AMF may indicate the PDU session type selected and determined by the network to send the 21st identification information. The PDU session type indicated by the 21st identification information may be the same PDU session type as the received 11th identification information, or may be a PDU session type different from the received 11th identification information. good.

Further, the SMF and AMF may indicate the acceptance of the request for establishing the PDU session associated with the DNN indicated by the 22nd identification information by transmitting the 22nd identification information, or the PDU session is established. It may be shown that. In addition, the SMF and AMF may indicate the DNN selected and determined by the network to transmit the 22nd identification information. The 22nd identification information may be a DNN that identifies a DN that supports one or more functions indicated by the identification information transmitted and received together with the 22nd identification information. Further, the 22nd identification information may be the DNN transmitted in the registration procedure or may be the LADN DNN.

Further, the SMF and AMF may indicate acceptance of the request for establishing the PDU session associated with the S-NSSAI indicated by the 23rd identification information by transmitting the 23rd identification information, or the PDU session may indicate acceptance. It may be shown to be established. In addition, the SMF and AMF may indicate that the 23rd identification information is transmitted, the network has selected and determined S-NSSAI. The 23rd identification information may be S-NSSAI that identifies an NS that supports one or more functions indicated by the identification information transmitted and received together with the 23rd identification information. Further, the 23rd identification information may be S-NSSAI transmitted in the registration procedure.

Furthermore, the SMF and / or AMF may send the 24th identification information to indicate that some of the UE's requests are not allowed. Specifically, the SMF and / or AMF may send the 24th identification information to indicate that the PDU session type requested by the UE is not allowed.

Furthermore, the SMF and / or AMF may send the 24th identification information to indicate that only PDU session types different from the PDU session type requested by the UE are allowed. Further, by transmitting the 24th identification information, the SMF and / or the AMF sets the PDU session type different from the PDU session type indicated by the 11th identification information received as the 21st identification information. You may indicate that you are.

Specifically, if the PDU session type indicating the eleventh identification information is IPv4v6 or IPv6 and the permitted PDU session type is IPv4, SMF and / or AMF will use the PDU session in the 21st identification information. IPv4 may be set as the type. Further, in this case, the SMF and / or the AMF may set the reason value indicating that only IPv4 is permitted in the 24th identification information. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that only IPv4 is permitted as the PDU session type. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that IPv6 and / or IPv4v6 are not permitted as the PDU session type.

Here, the reason value indicating that only IPv4 is permitted may be the 50th 5GSM reason value. Further, the reason value indicating that only IPv4 is permitted may be the reason value indicating that only IPv4 is permitted as the PDU session type. In other words, the reason value indicating that only IPv4 is allowed may be the reason value indicating that only the PDU session type of IPv4 is allowed.

Further, if the PDU session type indicating the 11th identification information is IPv4v6 or IPv4 and the permitted PDU session type is IPv6, SMF and / or AMF will be added to the 21st identification information as the PDU session type. IPv6 may be set. Further, in this case, the SMF and / or the AMF may set the reason value indicating that only IPv6 is permitted in the 24th identification information. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that only IPv6 is permitted as the PDU session type. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that IPv4 and / or IPv4 v6 are not permitted as the PDU session type.

Here, the reason value indicating that only IPv6 is permitted may be the 51st 5GSM reason value. Further, the reason value indicating that only IPv6 is permitted may be a reason value indicating that only IPv6 is permitted as the PDU session type. In other words, the reason value indicating that only IPv6 is allowed may be the reason value indicating that only the PDU session type of IPv6 is allowed.

In addition, SMF and AMF each received identification information and / or subscriber information, and whether to include one or more identification information in the PDU session establishment acceptance message from at least the 21st to 24th identification information, and It may be selected and determined based on / or network capability information and / or operator policy, and / or network status, and / or user registration information, and / or AMF-held context.

Also, SMF and AMF can include the selected and / or allowed PDU session ID in the PDU session establishment acceptance message. SMF and AMF can also specify a PDU session type that indicates the type of PDU session selected and / or allowed. As the PDU session type, any one of IPv4, IPv6, IPv4v6, Ethernet, and Unstructured can be specified as described above. The SMF and AMF can also include the SSC mode of the selected and / or allowed PDU session in the PDU session establishment acceptance message.

Furthermore, SMF and AMF can include the approved QoS rule group in the PDU session establishment acceptance message. The approved QoS rule group may include one or more QoS rules. Further, if a plurality of QoS flows and / or user plane radio bearers are established in this procedure, the approved QoS rule group may include a plurality of QoS rules. Conversely, if only one QoS flow and / or user plane radio bearer is established in this procedure, the approved QoS rule group may include one QoS rule.

In addition, the SMF may send the PDU session establishment acceptance message with information indicating that some requests from the UE have been rejected, or information indicating that some requests from the UE have been rejected. May indicate why some of the UE's requests were rejected. In addition, the UE may recognize why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

The UE receives the PDU session establishment acceptance message from the SMF (S910) (S912). Specifically, the UE receives the NAS message including the PDU session establishment acceptance message from the AMF via the N1 interface after the PDU session establishment acceptance message is sent from the SMF to the AMF (S910). .. The UE may send a PDU session establishment complete message to the SMF via AMF based on the receipt of the PDU session establishment acceptance message and / or the NAS message including the PDU session establishment acceptance message. (S914) (S916). By receiving the PDU session establishment acceptance message, the UE can detect that the UE's request by the PDU session establishment request has been accepted.

Specifically, the UE sends a PDU session establishment completion message to the AMF via the N1 interface (S914). When the AMF receives the PDU session establishment completion message from the UE, it sends the PDU session establishment completion message to the SMF via the N11 interface (S916).

The PDU session establishment completion message sent by AMF to SMF may be a response message to the PDU session establishment acceptance message sent from SMF to AMF by S910. Further, the PDU session establishment completion message may be a NAS message. Further, the PDU session establishment completion message may be any message indicating that the PDU session establishment procedure is completed.

When the SMF receives the PDU session establishment completion message from the AMF via the N11 interface (S916), the SMF can execute the second condition determination. The second condition determination is to determine the type of message sent and received on the N4 interface. If the second condition determination is true, the SMF sends a session change request message to the UPF via the N4 interface (S918) and receives a session change acceptance message sent by the UPF as its response message (S918). S920). If the second condition determination is false, the SMF sends a session establishment request message to the UPF via the N4 interface (S918) and receives a session change acceptance message sent by the UPF as its response message (S918). S920).

Note that the second condition determination may be executed based on whether or not a session on the N4 interface for the PDU session has been established. For example, if the session on the N4 interface for the PDU session is established, the second condition determination may be true, and if the session on the N4 interface for the PDU session is not established, the second condition is true. The condition determination of is false. The condition for determining the truth of the second condition determination is not limited to the above-mentioned condition.

Each device completes the procedure (A) during the PDU session establishment procedure based on the transmission / reception of the PDU session establishment completion message and / or the transmission / reception of the session change response message and / or the transmission / reception of the session establishment response message. When the procedure (A) during this procedure is completed, the UE is in a state where a PDU session for the DN has been established. Here, if the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for LADN, each device is for LADN based on the completion of procedure (A) during this procedure. PDU session may be established.

Next, each step of the procedure (B) during the PDU session establishment procedure will be described. The SMF sends a PDU session establishment reject message to the UE via the AMF (S922) (S924). Specifically, the SMF sends a PDU session establishment rejection message to the AMF via the N11 interface (S922). When the AMF receives a PDU session establishment request message from the SMF via the N11 interface (S922), it sends a PDU session establishment rejection message to the UE using the N1 interface (S924).

The PDU session establishment refusal message may be a NAS message or an SM message transmitted from the SMF to the UE. Further, the PDU session establishment refusal message may be any message indicating that the establishment of the PDU session has been rejected. In addition, the PDU session establishment refusal message may be sent and received by including the N1 interface in the MM message. Further, the MM message may be a NAS message or a downlink NAS transport (DL NAS TRANSPORT) message. Here, when it is expressed that the PDU session establishment refusal message includes identification information and / or a value, it may mean that it is included in the MM message including the PDU session establishment refusal message.

Here, the SMF may indicate that the UE request by the PDU session establishment request has been rejected by sending the PDU session establishment refusal message. In addition, the SMF may send the PDU session establishment rejection message with information indicating the reason for rejection, or may send the reason for rejection to indicate the reason for rejection. Further, the UE may recognize the reason why the UE's request is rejected by receiving the information indicating the reason why the UE's request is rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.

The SMF and / or AMF may send the PDU session establishment rejection message with at least the 24th identification information and / or the backoff timer value, and the 24th identification information and / or the backoff timer. By sending a value, it may indicate that the UE's request has been rejected, or it may indicate why the UE's request has been rejected.

Furthermore, the SMF and / or AMF may send the 24th identification information to indicate that the UE request is not permitted. Specifically, the SMF and / or AMF may send the 24th identification information to indicate that the PDU session type requested by the UE is not allowed.

Specifically, if the PDU session type indicating the 11th identification information is IPv4v6 or IPv6, and the permitted PDU session type is IPv4, SMF and / or AMF will use IPv4 only for the 24th identification information. You may set a reason value to indicate that is allowed. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that only IPv4 is permitted as the PDU session type. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that IPv6 and / or IPv4v6 are not permitted as the PDU session type.

Here, the reason value indicating that only IPv4 is permitted may be the 50th 5GSM reason value. Further, the reason value indicating that only IPv4 is permitted may be the reason value indicating that only IPv4 is permitted as the PDU session type. In other words, the reason value indicating that only IPv4 is allowed may be the reason value indicating that only the PDU session type of IPv4 is allowed.

Furthermore, if the PDU session type indicating the 11th identification information is IPv4v6 or IPv4 and the permitted PDU session type is IPv6, SMF and / or AMF are only allowed to use IPv6 for the 24th identification information. You may set a reason value indicating that it is. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that only IPv6 is permitted as the PDU session type. Further, in this case, the SMF and / or the AMF may transmit the 24th identification information to indicate that IPv4 and / or IPv4 v6 are not permitted as the PDU session type.

Here, the reason value indicating that only IPv6 is permitted may be the 51st 5GSM reason value. Further, the reason value indicating that only IPv6 is permitted may be a reason value indicating that only IPv6 is permitted as the PDU session type. In other words, the reason value indicating that only IPv6 is allowed may be the reason value indicating that only the PDU session type of IPv6 is allowed.

In addition, the SMF and / or AMF may instruct the UE to set the backoff timer value to the value to be transmitted by transmitting the backoff timer value, or the backoff with the transmitted value set. You may instruct to start the timer.

It should be noted that the SMF and / or AMF should include at least the 24th identification information in the PDU session establishment refusal message, each identification information received, and / or the subscriber information, and / or the network capability information, and /. Alternatively, 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.

By receiving the PDU session establishment refusal message, the UE can recognize that the UE request by the PDU session establishment request has been rejected and the contents of various identification information included in the PDU session establishment refusal message.

Each device completes the PDU session establishment procedure based on the completion of the procedure (A) or (B) in FIG. In addition, each device may transition to the state in which the PDU session is established based on the completion of the procedure of FIG. 8 (A), or the PDU is based on the completion of the procedure of FIG. 8 (B). You may recognize that the session establishment procedure has been rejected, or you may transition to a state where the PDU session has not been established. Furthermore, the UE can communicate with the DN using the established PDU session by completing the procedure (A) in FIG.

Further, each device may perform processing based on the information transmitted / received in the PDU session establishment procedure based on the completion of the PDU session establishment procedure. For example, if each device sends and receives information indicating that some of the UE's requests have been rejected, it may recognize the reason why the UE's request was rejected. Further, each device may perform this procedure again based on the reason why the request of the UE is rejected, or may perform the PDU session establishment procedure for another cell.

In addition, the UE may store the identification information received with the PDU session establishment acceptance message and / or the PDU session establishment rejection message based on the completion of the PDU session establishment procedure, and may recognize the network decision. good.

For example, when each device sends and receives the 21st identification information, it may establish a PDU session of the PDU session type indicated by the 21st identification information. Further, the UE may recognize that when the 21st identification information is received, a PDU session of the PDU session type indicated by the 21st identification information is established. In addition, the UE may recognize the PDU session type selected and determined by the network when it receives the 21st identification.

Further, each device may establish a PDU session associated with the DNN indicated by the 22nd identification information when the 22nd identification information is transmitted / received. Further, the UE may recognize that when the 22nd identification information is received, the PDU session associated with the DNN indicated by the 22nd identification information is established. In addition, the UE may recognize the DNN selected and determined by the network when it receives the 22nd identification information. The 22nd identification information may be a DNN that identifies a DN that supports one or more functions indicated by the identification information transmitted and received together with the 22nd identification information. Further, the 22nd identification information may be the DNN received in the registration procedure or may be the LADN DNN.

Further, each device may establish a PDU session associated with the S-NSSAI indicated by the 23rd identification information when the 23rd identification information is transmitted / received. Further, the UE may recognize that when the 23rd identification information is received, the PDU session associated with the S-NSSAI indicated by the 23rd identification information is established. Further, the UE may recognize the S-NSSAI selected and determined by the network when it receives the 23rd identification information. The 23rd identification information may be S-NSSAI that identifies an NS that supports one or more functions indicated by the identification information transmitted and received together with the 23rd identification information. Further, the 23rd identification information may be the S-NSSAI received in the registration procedure or the S-NSSAI.

Furthermore, when the UE receives the 24th identification information, it may recognize that a part of the UE's request is not permitted. Specifically, the UE may recognize that the PDU session type requested by the UE is not allowed when it receives the 24th identification information. In other words, the UE may recognize that when it receives the 24th identification information, a PDU session of a PDU session type other than the PDU session type requested by the UE is established.

In addition, the UE may recognize that only IPv4 is allowed as the PDU session type if it receives a 24th identification with a reason value that indicates that only IPv4 is allowed. .. Further, in this case, the UE may indicate that IPv6 and / or IPv4v6 are not allowed as the PDU session type.

Here, the reason value indicating that only IPv4 is permitted may be the 50th 5GSM reason value. Further, the reason value indicating that only IPv4 is permitted may be the reason value indicating that only IPv4 is permitted as the PDU session type. In other words, the reason value indicating that only IPv4 is allowed may be the reason value indicating that only the PDU session type of IPv4 is allowed.

Furthermore, when the UE receives the 24th identification information in which the reason value indicating that only IPv4 is permitted is set, the UE may execute the behavior A. More specifically, the eleventh identification information configured with IPv4v6 is transmitted, the 21st identification information configured with IPv4, and the 24th identification information set with a reason value indicating that only IPv4 is permitted. Upon receiving the identification information, the UE may perform behavior A. In other words, the UE behaves when it requests an IPv4 v6 PDU session type and receives a PDU session type with IPv4 and a 24th identification with a reason value indicating that only IPv4 is allowed. A may be carried out.

Behavior A is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set is prohibited. There may be. Further, behavior A is a behavior that prohibits the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. You may. Further, behavior A may be a behavior that uses the same DNN and / or the same S-NSSAI and a PDU session type in which IPv6 is set so that a new PDU session establishment procedure is not started. .. Furthermore, behavior A is a behavior that transitions to a state in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set is prohibited. You may.

In addition, the UE is prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type while performing Behavior A. You may be. In addition, the UE is prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type while performing Behavior A. It may be set to. In addition, the UE is prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type while performing Behavior A. It may be in a state of being.

Further, the behavior A may be carried out until the UE is registered in the new PLMN, or may be carried out until the UE is registered in the new SNPN. More specifically, if the UE is registered in the PLMN, behavior A may be performed until the UE is registered in a PLMN other than the equal PLMN, or until the UE is registered in the SNPN. It may be carried out. Furthermore, if the UE is registered in the SNPN, behavior A may be performed until the UE is registered in a SNPN other than the equal SNPN, or until the UE is registered in the PLMN. May be good.

In other words, if the UE is not operating in SNPN access mode, behavior A may be performed until the UE is registered with a PLMN other than the equal PLMN, or until the UE is registered with the SNPN. It may be carried out. Furthermore, if the UE is operating in SNPN access mode, behavior A may be performed until the UE is registered with a non-equal SNPN, or until the UE is registered with the PLMN. May be done.

Furthermore, behavior A may be performed until the PDU session type is changed. Further, behavior A may be performed until the UE is switched off or until the USIM is removed.

The PLMN other than the equal PLMN may be a PLMN that is not on the list of equal PLMNs. In other words, registering a UE with a non-equal PLMN may indicate that the UE is registered with a new PLMN that is not on the list of equal PLMNs.

Furthermore, the PLMN other than the equal PLMN may be a PLMN that is not included in the list of equal PLMNs. In other words, registering a UE with a PLMN other than the equal PLMN may indicate that the UE is registered with a new PLMN that is not on the list of equal PLMNs.

Furthermore, the SNPN other than the equal SNPN may be an SNPN that is not on the list of equal SNPNs. In other words, registering a UE with a non-equal SNPN may indicate that the UE is registered with a new SNPN that is not on the list of equal SNPNs.

Further, the SNPN other than the equal SNPN may be an SNPN that is not included in the list of equal SNPNs. In other words, registering a UE with an SNPN other than the equal SNPN may indicate that the UE is registered with a new SNPN that is not included in the list of equal SNPNs.

Here, the same DNN may be the same DNN as the DNN included in the 12th identification information and transmitted / received in this procedure, or the same DNN as the DNN included in the 22nd identification information and transmitted / received. There may be. Further, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI included in the 13th identification information and transmitted / received in this procedure, and may be included in the 23rd identification information and transmitted / received. It may be the same S-NSSAI as S-NSSAI.

Furthermore, the new PDU session establishment procedure may be a PDU session establishment procedure different from this procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure performed after the completion of this procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure performed after the completion of this procedure.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is the same DNN and / or the same S-NSSAI and IPv6. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv6. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

In addition, the UE may recognize that only IPv6 is allowed as the PDU session type if it receives a 24th identification with a reason value that indicates that only IPv6 is allowed. .. Further, in this case, the UE may indicate that IPv4 and / or IPv4 v6 are not allowed as the PDU session type.

Here, the reason value indicating that only IPv6 is permitted may be the 51st 5GSM reason value. Further, the reason value indicating that only IPv6 is permitted may be a reason value indicating that only IPv6 is permitted as the PDU session type. In other words, the reason value indicating that only IPv6 is allowed may be the reason value indicating that only the PDU session type of IPv6 is allowed.

Furthermore, when the UE receives the 24th identification information in which the reason value indicating that only IPv6 is permitted is set, the UE may execute the behavior B. More specifically, the eleventh identification information configured with IPv4v6 is transmitted, the 21st identification information configured with IPv6, and the 24th identification information set with a reason value indicating that only IPv6 is permitted. Upon receiving the identification information, the UE may perform behavior B. In other words, the UE behaves when it requests an IPv4 v6 PDU session type and receives a PDU session type with IPv6 configured and a 24th identification with a reason value indicating that only IPv6 is allowed. B may be carried out.

Behavior B is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is prohibited. There may be. Further, behavior B is a behavior that prohibits the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. You may. Further, behavior B may be a behavior that uses the same DNN and / or the same S-NSSAI and a PDU session type in which IPv4 is set so that a new PDU session establishment procedure is not started. .. Furthermore, behavior B is a behavior that transitions to a state in which the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is prohibited. You may.

In addition, the UE is prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type while performing Behavior B. You may be. In addition, the UE is prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type while performing Behavior B. It may be set to. In addition, the UE is prohibited from initiating a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type while performing Behavior B. It may be in a state of being.

Furthermore, behavior B may be carried out until the UE is registered in the new PLMN, or may be carried out until the UE is registered in the new SNPN. More specifically, if the UE is registered in the PLMN, behavior B may be performed until the UE is registered in a PLMN other than the equal PLMN, or until the UE is registered in the SNPN. It may be carried out. Furthermore, if the UE is registered in the SNPN, behavior B may be performed until the UE is registered in a SNPN other than the equal SNPN, or until the UE is registered in the PLMN. May be good.

In other words, if the UE is not operating in SNPN access mode, behavior B may be performed until the UE is registered with a PLMN other than the equal PLMN, or until the UE is registered with the SNPN. It may be carried out. Furthermore, if the UE is operating in SNPN access mode, behavior B may be performed until the UE is registered with a non-equal SNPN, or until the UE is registered with the PLMN. May be done.

Furthermore, behavior B may be performed until the PDU session type is changed. Further, behavior B may be performed until the UE is switched off or until the USIM is removed.

The PLMN other than the equal PLMN may be a PLMN that is not on the list of equal PLMNs. In other words, registering a UE with a non-equal PLMN may indicate that the UE is registered with a new PLMN that is not on the list of equal PLMNs.

Furthermore, the PLMN other than the equal PLMN may be a PLMN that is not included in the list of equal PLMNs. In other words, registering a UE with a PLMN other than the equal PLMN may indicate that the UE is registered with a new PLMN that is not on the list of equal PLMNs.

Furthermore, the SNPN other than the equal SNPN may be an SNPN that is not on the list of equal SNPNs. In other words, registering a UE with a non-equal SNPN may indicate that the UE is registered with a new SNPN that is not on the list of equal SNPNs.

Further, the SNPN other than the equal SNPN may be an SNPN that is not included in the list of equal SNPNs. In other words, registering a UE with an SNPN other than the equal SNPN may indicate that the UE is registered with a new SNPN that is not included in the list of equal SNPNs.

Here, the same DNN may be the same DNN as the DNN included in the 12th identification information and transmitted / received in this procedure, or the same DNN as the DNN included in the 22nd identification information and transmitted / received. There may be. Further, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI included in the 13th identification information and transmitted / received in this procedure, and may be included in the 23rd identification information and transmitted / received. It may be the same S-NSSAI as S-NSSAI.

Furthermore, the new PDU session establishment procedure may be a PDU session establishment procedure different from this procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure performed after the completion of this procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure performed after the completion of this procedure.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is the same DNN and / or the same S-NSSAI and IPv4. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv4. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

Further, when the UE receives the back-off timer value, the UE may set the back-off timer value to the back-off timer, or may start the back-off timer in which the received back-off timer value is set. Here, even if the UE receives the backoff timer value, if it receives the 24th identification information, the received backoff timer value may be ignored and the backoff timer may not be started. May be good. Conversely, the UE may set the received backoff timer value as the backoff timer even when the backoff timer value and the 24th identification information are received, and the received backoff timer value may be set. You may start the set backoff timer.

Furthermore, if the UE receives the 24th identification information, after the completion of this procedure, the UE starts the PDU session establishment procedure under other conditions based on the completion of this procedure and / or the reception of the 24th identification information. You can do it. If the UE is executing the back timer, the PDU session establishment procedure may be started under other conditions after the count of the back-off timer has expired.

Here, the fact that the UE starts the PDU session establishment procedure under other conditions means that, for example, the PDU session establishment procedure is performed by setting a DNN different from the DNN transmitted earlier by the UE in the DNN information element and transmitting it to the network. May be started. Furthermore, the fact that the UE starts the PDU session establishment procedure under other conditions means that the S-NSSAI, which is different from the S-NSSAI sent earlier by the UE, is set in the S-NSSAI information element and sent to the network. It may be to start the session establishment procedure.

Furthermore, the fact that the UE initiates the PDU session establishment procedure under other conditions means that the PDU session type that is different from the PDU session type that the UE sent earlier is set in the PDU session type information element and sent to the network. It may be to start the session establishment procedure. Furthermore, when the UE starts the PDU session establishment procedure under other conditions, it means that the PDU session establishment procedure is started by changing the area where the UE is located and then sending the PDU session establishment request message. May be good.

Furthermore, the fact that the UE starts the PDU session establishment procedure under other conditions may mean that the UE starts the PDU session establishment procedure without using the DNN. Furthermore, the fact that the UE starts the PDU session establishment procedure under other conditions may mean that the UE starts the PDU session establishment procedure without using S-NSSAI.

When the UE receives the 24th identification information, after the completion of this procedure, the PDU session establishment procedure using the DNN and / or S-NSSAI and / or PDU session type requested by the UE is not started. , Or may transition to a stopped state or a prohibited state. Here, the PDU session establishment procedure using the DNN and / or S-NSSAI and / or PDU session type requested by the UE is the DNN and / or S-NSSAI and / or the UE requested earlier. It may be a PDU session establishment procedure initiated by sending a PDU session establishment request message containing a PDU session type. In other words, upon receiving the 24th identification, the UE may be prohibited from PDU session establishment procedures using the same DNN and / or the same S-NSSAI and / or the same PDU session type. With the same DNN and / or the same S-NSSAI, sending PDU session establishment request messages containing the same PDU session type may be prohibited.

If the UE receives the 24th identification information, the PDU session establishment procedure using the same DNN and / or the same S-NSSAI and / or the same PDU session type is prohibited for a certain period after the completion of this procedure. It may transition to the state of being. In addition, if the UE receives the 24th identification information, it will send a PDU session establishment request message containing the same PDU session type with the same DNN and / or the same S-NSSAI for a period of time after the completion of this procedure. You may transition to the prohibited state. Here, the fixed period may be a period set by the back-off timer value, or may be another period set by the network or the UE.

[3.2.3. RRC connection release procedure]
Next, the outline of the RRC connection release procedure for releasing or suspending the RRC connection will be described with reference to FIG. The RRC connection release procedure is a procedure in 5GS. Hereinafter, this procedure refers to the RRC connection release procedure. The RRC connection release procedure is a procedure for each device to release or suspend an RRC connection. The base station device in the access network can start the RRC connection release procedure at any time when the registration procedure is completed and the registration state is reached. In addition, each device may release or suspend the RRC connection based on the completion of the RRC connection release procedure.

The RRC connection release procedure may be a procedure that is started by the base station device in the access network, or may be a procedure that is requested and started by the core network device. Further, the RRC connection release procedure may be a procedure that is triggered by the transmission of an RRC message from the UE.

For example, the base station device and / or the core network device in the access network may initiate the RRC connection release procedure based on the change in the state of the UE, or may start the RRC connection release procedure based on the change in the subscriber information of the UE. The RRC connection release procedure may be started. In addition, the base station device and / or the core network device in the access network may initiate the RRC connection release procedure based on the change in network settings, or the RRC connection based on the change in network status. You may start the release procedure. Further, the base station device and / or the core network device in the access network may start the RRC connection release procedure based on the detection that the transmission / reception unit of the user data has disappeared, and the RRC connection becomes unnecessary. The RRC connection release procedure may be started based on the detection of the occurrence. The trigger for the base station device and / or the core network device in the access network to start the RRC connection release procedure is not limited to these.

First, the base station device (gNB) in the access network starts the RRC connection release procedure by sending an RRC release (RRC release) message to the UE (S1000).

Specifically, gNB sends an RRC release message to the UE via the Uu interface (S1000). The RRC release message may be an RRC message.

Here, gNB may include at least the first identification information in the RRC release message and send it. These identifications may be included in these messages to indicate a gNB request.

Furthermore, gNB may indicate that the RRC connection is suspended by transmitting the first identification information. In other words, gNB may disable the RRC connection state or suspend the RRC connection state by transmitting the first identification information.

Furthermore, gNB may instruct the UE to suspend the RRC connection by transmitting the first identification information. In addition, gNB may instruct the UE to deactivate the state of the RRC connection or suspend the state of the RRC connection by sending the first identification information. May be good.

Here, suspending the RRC connection may mean disabling the RRC connection. Further, disabling the state of the RRC connection may mean deactivating the state of the RRC layer. Further, suspending the state of the RRC connection may mean suspending the state of the RRC layer.

Furthermore, gNB may transition to the RRC_INACTIVE state by transmitting the first identification information. Further, the gNB may instruct the UE to transition to the RRC_INACTIVE state by transmitting the first identification information.

UE receives the RRC release message (S900). The UE may recognize and store the identification information contained in the RRC release message based on the receipt of the RRC release message.

Furthermore, UE_R may release the RRC connection or suspend the RRC connection based on the reception of the RRC release message. In addition, UE_R may disable the state of the RRC connection or suspend the state of the RRC connection based on the receipt of the RRC release message.

Furthermore, UE_R may send information indicating that the RRC connection has been suspended to the upper layer based on the reception of the RRC release message. In addition, UE_R may transition to the RRC_INACTIVE state based on the receipt of the RRC release message.

Here, UE_R may be a functional unit responsible for the function of the RRC layer of the UE. Further, the upper layer may be a NAS layer. Further, the information indicating that the RRC connection has been suspended may be an indication indicating that the RRC connection has been suspended. Further, the information indicating that the RRC connection has been suspended may be the first identification information.

Furthermore, UE_N may receive information from the lower layer indicating that the RRC connection has been suspended. Further, UE_N may transition to 5GMM-CONNECTED mode with RRC inactive indication based on the reception of information indicating that the RRC connection has been suspended from the lower layer. More specifically, UE_N may transition from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on the reception of information from the lower layer indicating that the RRC connection has been suspended.

Here, UE_N transitions only the 3GPP access status from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication from the lower layer based on the reception of information indicating that the RRC connection has been suspended. You may. In other words, UE_N does not have to transition to 5GMM-CONNECTED mode with RRC inactive indication regarding the non-3GPP access status even if it receives information from the lower layer indicating that the RRC connection has been suspended. ..

Here, UE_N may be a functional unit responsible for the function of the NAS layer of the UE. In other words, UE_N may be a transmission / reception unit that is responsible for the function of the NAS layer of the UE, or may be a functional unit that is responsible for the function of the NAS layer of the UE. Further, the lower layer may be an RRC layer. Further, the information indicating that the RRC connection has been suspended may be an indication indicating that the RRC connection has been suspended. Further, the information indicating that the RRC connection has been suspended may be the first identification information.

Each device completes the RRC connection release procedure based on the transmission / reception of RRC release and / or the transition to each state. In addition, each device may release the RRC connection or suspend the RRC connection based on the completion of this procedure. Further, each device may transition to a suspended state of the RRC connection or a disabled state of the RRC connection based on the completion of this procedure. Further, each device may transition to the RRC_INACTIVE state based on the completion of this procedure.

Furthermore, each device may transition to 5GMM-CONNECTED mode with RRC inactive indication based on the completion of this procedure. More specifically, each device may transition from 5GMM-CONNECTED mode to 5GMM-CONNECTED mode with RRC inactive indication based on the completion of this procedure.

[4. First Embodiment]
Next, the first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In this embodiment, the UE selects and executes one or more procedures from the first to fourth procedures.

In addition, the UE determines which of the procedures 1 to 4 is to be executed, the setting information of the UE and / or the information received from the network, and / or the mode of the UE, and / or the capability information of the UE. It may be decided based on.

[4.1. First procedure]
Next, the first procedure will be described with reference to FIG. Hereinafter, the first procedure will be referred to as this procedure. In the first procedure, the UE first makes the first network selection (S600). Then, based on the first network selection, the UE connects to the selected network and initiates the registration process (S602). Next, each device performs the registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing the PDU session establishment procedure initiated by the UE (S604), and is in a state where communication using the PDU session can be performed between the UE and the DN. Transition. Next, each device sends and receives user data using a PDU session.

Next, each device may perform the RRC connection release procedure at any time (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

Next, the UE makes a second network selection at any time (S608). Next, based on the second network selection, the UE connects to the selected network and initiates the registration procedure and / or the PDU session establishment procedure (S610) (S612). Next, each device performs a UE-initiated registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device transitions to a state in which communication using the PDU session can be performed between the UE and the DN based on the completion of the registration procedure and / or the PDU session establishment procedure. Next, each device sends and receives user data using a PDU session. With the above, the first procedure is completed.

Here, the UE may execute the second network selection based on the change in the state of the UE, or may execute the second network selection based on the change in the setting subscriber information of the UE. good. In addition, the UE may perform a second network selection based on changes in the UE settings, or may perform a second network selection based on the movement of the UE. Further, the UE may perform a second network selection based on the receipt of a control message from the network, or may perform a second network selection based on instructions from the network. Here, the control message may be a NAS message or a control message other than the NAS message. Specifically, the control message may be a non-registration request message or a registration refusal message. The trigger for the UE to execute the second network selection is not limited to these.

In the first procedure, the UE may select PLMN and select PLMN in the first network selection. More specifically, the UE selects PLMN in the first network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. Specifically, when the UE is not operating in the SNPN access mode, it may perform PLMN selection in the first network selection and select PLMN.

Furthermore, in the first procedure, the UE may be registered with the PLMN based on the first network selection. In other words, the UE may transition to the PLMN registered state based on the first network selection. Further, in the first procedure, the UE may be registered with the PLMN after the completion of the first network selection. In other words, it may be in the state of being registered in the PLMN.

Further, in the first procedure, the UE may perform PLMN selection in the second network selection and select PLMN. More specifically, the UE selects PLMN in the second network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. In addition, the UE will in the second network selection based on changes in the UE configuration information and / or information received from the network and / or UE mode changes and / or UE capability information. PLMN may be selected. Specifically, when the UE is not operating in the SNPN access mode, it may perform PLMN selection in the second network selection and select PLMN.

Further, when PLMN is selected in the first network selection, the UE may transition to a state in which the SNPN access mode is not activated. Further, the UE may transition to a state in which the SNPN access mode is not activated when PLMN is selected in the second network selection.

Furthermore, the UE may select PLMN based on the first network selection, connect to the selected PLMN, or implement both. Further, the UE may transition to the selected state of the PLMN or the state registered in the PLMN based on the first network selection.

Furthermore, the UE may select a new PLMN based on the second network selection, move from the current PLMN to the new PLMN, or both. Furthermore, the UE may transition to the selected state of the new PLMN based on the second network selection, or may transition from the state registered in the current PLMN to the state registered in the new PLMN. good.

Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode or from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the second network selection. You don't have to.

Specifically, the UE may transition to the 5GMM-IDLE mode based on the selection of PLMN other than equal PLMN. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN other than equal PLMN. More specifically, when registered in PLMN, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN other than equal PLMN. Further, when the UE is not operating in the SNPN access mode, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN other than equal PLMN.

Furthermore, the UE may transition only the 3GPP access status from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN other than equal PLMN.

On the contrary, the UE does not have to transition to the 5GMM-IDLE mode based on the selection of the PLMN which is the equal PLMN. In other words, the UE does not have to transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN which is an equal PLMN. More specifically, when registered in the PLMN, the UE does not have to transition from the 5GMM-CONNECTED mode with RRC inactive indication to the 5GMM-IDLE mode based on the selection of the PLMN which is an equal PLMN. Further, when the UE is not operating in the SNPN access mode, it is not necessary to transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN which is an equal PLMN.

Note that the selection of a PLMN other than the equal PLMN may indicate that a PLMN that is not an equal PLMN with respect to the registered PLMN is selected as a new PLMN. Further, the selection of a PLMN other than the equal PLMN may mean that a PLMN that is not an equal PLMN with respect to the registered PLMN is selected as the new PLMN, and the UE is included in the selected new PLMN.

Further, the selection of the PLMN which is the equal PLMN may indicate that the PLMN in the list of equal PLMNs is selected as the new PLMN. Further, the selection of a PLMN that is an equal PLMN may mean that the PLMN in the list of equal PLMNs is selected as the new PLMN and the UE is included in the selected new PLMN. In other words, the selection of a PLMN that is an equal PLMN may mean that the PLMN contained in the list of equal PLMNs is selected as the new PLMN and the UE is included in the selected new PLMN.

Furthermore, the UE may carry out behavior C or continue behavior A based on the second network registration.

Specifically, the UE may carry out behavior C based on the registration of PLMNs other than equal PLMNs. In other words, if the UE is performing behavior A, it may perform behavior C based on the registration of PLMNs other than the equal PLMN.

Conversely, the UE may continue behavior A based on the registration of the PLMN, which is an equal PLMN. In other words, if the UE is performing behavior A, it may continue behavior A based on the registration of the PLMN, which is an equal PLMN.

Here, behavior A may be the same as behavior A during the PDU session establishment procedure. Further, the behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. .. In addition, behavior C recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is lifted. May be. In addition, behavior C is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 to be lifted. May be. Furthermore, behavior C is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set is lifted. May be.

Further, the behavior C may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. Further, behavior C is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is allowed. You may. Further, behavior C is a behavior that is set to allow the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6. You may. Furthermore, even if behavior C is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. good. Furthermore, behavior C is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. You may.

Furthermore, the UE may perform behavior D or continue behavior B based on the second network registration.

Specifically, the UE may carry out behavior D based on the registration of PLMNs other than equal PLMNs. In other words, when the UE is implementing the behavior B, the UE may perform the behavior D based on the registration of PLMNs other than the equal PLMN.

On the contrary, the UE may continue the behavior B based on the registration of the PLMN which is the equal PLMN. In other words, if the UE is performing behavior B, it may continue behavior B based on the registration of the PLMN, which is an equal PLMN.

Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Further, the behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. .. Furthermore, behavior D recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is lifted. May be. Furthermore, behavior D is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set to be lifted. May be. Furthermore, behavior D is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is lifted. May be.

Further, the behavior D may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. Further, behavior D is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is allowed. You may. Further, behavior D is a behavior that is set so that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is permitted. You may. Further, even if the behavior D is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. good. Furthermore, behavior D is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. You may.

Note that the registration of a PLMN other than the equal PLMN may indicate that the PLMN is registered in a new PLMN that is not the equal PLMN with respect to the registered PLMN. Further, registration of a PLMN that is an equal PLMN may indicate that it is registered in a new PLMN in the list of equal PLMNs.

Furthermore, the same DNN may be the same DNN as the sent / received DNN in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN that was included in the 12th identification information and sent / received in the previously performed PDU session establishment procedure, or may be included in the 22nd identification information and sent / received. It may be the same DNN as the DNN. Further, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted / received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI sent and received included in the 13th identification information in the previously performed PDU session establishment procedure, and the 23rd. It may be the same S-NSSAI as the S-NSSAI sent and received included in the identification information of.

Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is the same DNN and / or the same S-NSSAI and IPv6. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv6. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is the same DNN and / or the same S-NSSAI and IPv4. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv4. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

Furthermore, if the request for the PDU session establishment procedure is rejected, each device does not have to establish the PDU session. In this case, after the completion of the PDU session establishment procedure, each device may perform processing based on the information contained in the PDU session establishment refusal message, or perform processing based on the information contained in the PDU session establishment refusal message. By doing so, the first procedure may be completed.

[4.2. Second procedure]
Next, the second procedure will be described with reference to FIG. Hereinafter, the second procedure will be referred to as this procedure. In the second procedure, the UE first makes the first network selection (S600). Then, based on the first network selection, the UE connects to the selected network and initiates the registration process (S602). Next, each device performs the registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing the PDU session establishment procedure initiated by the UE (S604), and is in a state where communication using the PDU session can be performed between the UE and the DN. Transition. Next, each device sends and receives user data using a PDU session.

Next, each device may perform the RRC connection release procedure at any time (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

Next, the UE makes a second network selection at any time (S608). Next, based on the second network selection, the UE connects to the selected network and initiates the registration procedure and / or the PDU session establishment procedure (S610) (S612). Next, each device performs a UE-initiated registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device transitions to a state in which communication using the PDU session can be performed between the UE and the DN based on the completion of the registration procedure and / or the PDU session establishment procedure. Next, each device sends and receives user data using a PDU session. With the above, the second procedure is completed.

Here, the UE may execute the second network selection based on the change in the state of the UE, or may execute the second network selection based on the change in the setting subscriber information of the UE. good. In addition, the UE may perform a second network selection based on changes in the UE settings, or may perform a second network selection based on the movement of the UE. Further, the UE may perform a second network selection based on the receipt of a control message from the network, or may perform a second network selection based on instructions from the network. Here, the control message may be a NAS message or a control message other than the NAS message. Specifically, the control message may be a non-registration request message or a registration refusal message. The trigger for the UE to execute the second network selection is not limited to these.

In the second procedure, the UE may perform PLMN selection in the first network selection and select PLMN. More specifically, the UE selects PLMN in the first network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. Specifically, when the UE is not operating in the SNPN access mode, it may perform PLMN selection in the first network selection and select PLMN.

Furthermore, in the second procedure, the UE may be registered with the PLMN based on the first network selection. In other words, the UE may transition to the PLMN registered state based on the first network selection. Further, in the second procedure, the UE may be registered with the PLMN after the completion of the first network selection. In other words, it may be in the state of being registered in the PLMN.

Further, in the second procedure, the UE may perform SNPN selection in the second network selection and select SNPN. More specifically, the UE selects the SNPN in the second network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. In addition, the UE will in the second network selection based on changes in the UE configuration information and / or information received from the network and / or UE mode changes and / or UE capability information. SNPN may be selected. Specifically, when operating in the SNPN access mode, the UE may perform SNPN selection and select SNPN instead of PLMN selection in the second network selection.

Further, when PLMN is selected in the first network selection, the UE may transition to a state in which the SNPN access mode is not activated. Further, the UE may transition to the state in which the SNPN access mode is activated when SNPN is selected in the second network selection.

Furthermore, the UE may select PLMN based on the first network selection, connect to the selected PLMN, or implement both. Further, the UE may transition to the selected state of the PLMN or the state registered in the PLMN based on the first network selection.

Furthermore, the UE may select the SNPN based on the second network selection, move from the PLMN to the SNPN, or both. Further, the UE may transition to the selected state of the SNPN based on the second network selection, or may transition from the state registered in the PLMN to the state registered in the SNPN.

Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the second network selection.

Specifically, the UE may transition to 5GMM-IDLE mode based on the selection of SNPN. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN. More specifically, when registered in PLMN, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN. Further, when the UE is not operating in the SNPN access mode, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN.

Furthermore, the UE may transition only the 3GPP access status from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN.

Note that the selection of SNPN may indicate that a new SNPN is selected. Further, the selection of the SNPN may mean that a new SNPN is selected and the UE is included in the selected new SNPN.

Furthermore, the UE may perform behavior C based on the second network registration.

Specifically, the UE may perform behavior C based on the registration to the new SNPN. In other words, if the UE is performing behavior A, it may perform behavior C based on its registration with the new SNPN.

Here, behavior A may be the same as behavior A during the PDU session establishment procedure. Further, the behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. .. In addition, behavior C recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is lifted. May be. In addition, behavior C is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 to be lifted. May be. Furthermore, behavior C is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set is lifted. May be.

Further, the behavior C may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. Further, behavior C is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is allowed. You may. Further, behavior C is a behavior that is set to allow the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6. You may. Furthermore, even if behavior C is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. good. Furthermore, behavior C is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. You may.

Furthermore, the UE may perform behavior D based on the second network registration.

Specifically, the UE may perform behavior D based on registration with the new SNPN. In other words, if UE is performing behavior B, it may perform behavior D based on its registration with the new SNPN.

Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Further, the behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. .. Furthermore, behavior D recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is lifted. May be. Furthermore, behavior D is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set to be lifted. May be. Furthermore, behavior D is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is lifted. May be.

Further, the behavior D may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. Further, behavior D is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is allowed. You may. Further, behavior D is a behavior that is set so that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is permitted. You may. Further, even if the behavior D is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. good. Furthermore, behavior D is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. You may.

Note that registration to a new SNPN may indicate registration to a new SNPN.

Furthermore, the same DNN may be the same DNN as the sent / received DNN in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN that was included in the 12th identification information and sent / received in the previously performed PDU session establishment procedure, or may be included in the 22nd identification information and sent / received. It may be the same DNN as the DNN. Further, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted / received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI sent and received included in the 13th identification information in the previously performed PDU session establishment procedure, and the 23rd. It may be the same S-NSSAI as the S-NSSAI sent and received included in the identification information of.

Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is the same DNN and / or the same S-NSSAI and IPv6. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv6. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is the same DNN and / or the same S-NSSAI and IPv4. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv4. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

Furthermore, if the request for the PDU session establishment procedure is rejected, each device does not have to establish the PDU session. In this case, after the completion of the PDU session establishment procedure, each device may perform processing based on the information contained in the PDU session establishment refusal message, or perform processing based on the information contained in the PDU session establishment refusal message. By doing so, the second procedure may be completed.

[4.3. Third procedure]
Next, the third procedure will be described with reference to FIG. Hereinafter, the third procedure will be referred to as this procedure. In the third procedure, the UE first makes the first network selection (S600). Then, based on the first network selection, the UE connects to the selected network and initiates the registration process (S602). Next, each device performs the registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing the PDU session establishment procedure initiated by the UE (S604), and is in a state where communication using the PDU session can be performed between the UE and the DN. Transition. Next, each device sends and receives user data using a PDU session.

Next, each device may perform the RRC connection release procedure at any time (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

Next, the UE makes a second network selection at any time (S608). Next, based on the second network selection, the UE connects to the selected network and initiates the registration procedure and / or the PDU session establishment procedure (S610) (S612). Next, each device performs a UE-initiated registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device transitions to a state in which communication using the PDU session can be performed between the UE and the DN based on the completion of the registration procedure and / or the PDU session establishment procedure. Next, each device sends and receives user data using a PDU session. With the above, the third procedure is completed.

Here, the UE may execute the second network selection based on the change in the state of the UE, or may execute the second network selection based on the change in the setting subscriber information of the UE. good. In addition, the UE may perform a second network selection based on changes in the UE settings, or may perform a second network selection based on the movement of the UE. Further, the UE may perform a second network selection based on the receipt of a control message from the network, or may perform a second network selection based on instructions from the network. Here, the control message may be a NAS message or a control message other than the NAS message. Specifically, the control message may be a non-registration request message or a registration refusal message. The trigger for the UE to execute the second network selection is not limited to these.

In the third procedure, the UE may perform SNPN selection in the first network selection and select SNPN. More specifically, the UE selects the SNPN in the first network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. Specifically, when operating in the SNPN access mode, the UE may perform SNPN selection instead of PLMN selection in the first network selection and select SNPN.

Furthermore, in the third procedure, the UE may be registered with the SNPN based on the first network selection. In other words, the UE may transition to the state registered in the SNPN based on the first network selection. Further, in the third procedure, the UE may be registered with the SNPN after the completion of the first network selection. In other words, it may be in the state of being registered in SNPN.

Further, in the third procedure, the UE may perform PLMN selection in the second network selection and select PLMN. More specifically, the UE selects PLMN in the second network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. In addition, the UE will in the second network selection based on changes in the UE configuration information and / or information received from the network and / or UE mode changes and / or UE capability information. PLMN may be selected. Specifically, when the UE is not operating in the SNPN access mode, it may perform PLMN selection in the second network selection and select PLMN.

Further, when SNPN is selected in the first network selection, the UE may transition to the state in which the SNPN access mode is activated. Further, the UE may transition to a state in which the SNPN access mode is not activated when PLMN is selected in the second network selection.

Furthermore, the UE may select an SNPN based on the first network selection, connect to the selected SNPN, or both. Further, the UE may transition to the selected state of the SNPN or the state registered in the SNPN based on the first network selection.

Furthermore, the UE may select PLMN based on the second network selection, move from SNPN to PLMN, or both. Further, the UE may transition to the selected state of the PLMN based on the second network selection, or may transition from the state registered in the SNPN to the state registered in the PLMN.

Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the second network selection.

Specifically, the UE may transition to the 5GMM-IDLE mode based on the PLMN selection. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the PLMN selection. More specifically, when registered in the SNPN, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN. Further, when operating in the SNPN access mode, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of PLMN.

Furthermore, the UE may transition only the 3GPP access status from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the PLMN selection.

Note that the selection of PLMN may indicate that a new PLMN is selected. Further, the selection of PLMN may mean that a new PLMN is selected and the UE is included in the selected new PLMN.

Furthermore, the UE may perform behavior C based on the second network registration.

Specifically, the UE may implement behavior C based on the registration in the new PLMN. In other words, if the UE is performing behavior A, it may perform behavior C based on its registration on the new PLMN.

Here, behavior A may be the same as behavior A during the PDU session establishment procedure. Further, the behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. .. In addition, behavior C recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is lifted. May be. In addition, behavior C is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 to be lifted. May be. Furthermore, behavior C is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set is lifted. May be.

Further, the behavior C may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. Further, behavior C is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is allowed. You may. Further, behavior C is a behavior that is set to allow the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6. You may. Furthermore, even if behavior C is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. good. Furthermore, behavior C is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. You may.

Furthermore, the UE may perform behavior D based on the second network registration.

Specifically, the UE may perform behavior D based on the registration in the new PLMN. In other words, if the UE is performing behavior B, it may perform behavior D based on its registration in the new PLMN.

Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Further, the behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. .. Furthermore, behavior D recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is lifted. May be. Furthermore, behavior D is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set to be lifted. May be. Furthermore, behavior D is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is lifted. May be.

Further, the behavior D may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. Further, behavior D is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is allowed. You may. Further, behavior D is a behavior that is set so that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is permitted. You may. Further, even if the behavior D is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. good. Furthermore, behavior D is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. You may.

Note that registration to a new PLMN may indicate registration to a new PLMN.

Furthermore, the same DNN may be the same DNN as the sent / received DNN in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN that was included in the 12th identification information and sent / received in the previously performed PDU session establishment procedure, or may be included in the 22nd identification information and sent / received. It may be the same DNN as the DNN. Further, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted / received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI sent and received included in the 13th identification information in the previously performed PDU session establishment procedure, and the 23rd. It may be the same S-NSSAI as the S-NSSAI sent and received included in the identification information of.

Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is the same DNN and / or the same S-NSSAI and IPv6. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv6. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is the same DNN and / or the same S-NSSAI and IPv4. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv4. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

Furthermore, if the request for the PDU session establishment procedure is rejected, each device does not have to establish the PDU session. In this case, after the completion of the PDU session establishment procedure, each device may perform processing based on the information contained in the PDU session establishment refusal message, or perform processing based on the information contained in the PDU session establishment refusal message. By implementing it, the third procedure may be completed.

[4.4. Fourth procedure]
Next, the fourth procedure will be described with reference to FIG. Hereinafter, the fourth procedure is referred to as this procedure. In the fourth procedure, the UE first makes the first network selection (S600). Then, based on the first network selection, the UE connects to the selected network and initiates the registration process (S602). Next, each device performs the registration procedure initiated by the UE (S602). Next, each device establishes a PDU session by performing the PDU session establishment procedure initiated by the UE (S604), and is in a state where communication using the PDU session can be performed between the UE and the DN. Transition. Next, each device sends and receives user data using a PDU session.

Next, each device may perform the RRC connection release procedure at any time (S606). Note that each device may proceed to the next step without performing the RRC connection release procedure.

Next, the UE makes a second network selection at any time (S608). Next, based on the second network selection, the UE connects to the selected network and initiates the registration procedure and / or the PDU session establishment procedure (S610) (S612). Next, each device performs a UE-initiated registration procedure and / or a PDU session establishment procedure (S610) (S612). Next, each device transitions to a state in which communication using the PDU session can be performed between the UE and the DN based on the completion of the registration procedure and / or the PDU session establishment procedure. Next, each device sends and receives user data using a PDU session. With the above, the fourth procedure is completed.

Here, the UE may execute the second network selection based on the change in the state of the UE, or may execute the second network selection based on the change in the setting subscriber information of the UE. good. In addition, the UE may perform a second network selection based on changes in the UE settings, or may perform a second network selection based on the movement of the UE. Further, the UE may perform a second network selection based on the receipt of a control message from the network, or may perform a second network selection based on instructions from the network. Here, the control message may be a NAS message or a control message other than the NAS message. Specifically, the control message may be a non-registration request message or a registration refusal message. The trigger for the UE to execute the second network selection is not limited to these.

In the fourth procedure, the UE may perform SNPN selection in the first network selection and select SNPN. More specifically, the UE selects the SNPN in the first network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. Specifically, when operating in the SNPN access mode, the UE may perform SNPN selection instead of PLMN selection in the first network selection and select SNPN.

Furthermore, in the fourth procedure, the UE may be registered with the SNPN based on the first network selection. In other words, the UE may transition to the state registered in the SNPN based on the first network selection. Further, in the fourth procedure, the UE may be registered with the SNPN after the completion of the first network selection. In other words, it may be in the state of being registered in SNPN.

Further, in the fourth procedure, the UE may perform SNPN selection in the second network selection and select SNPN. More specifically, the UE selects the SNPN in the second network selection based on the UE configuration information and / or the information received from the network and / or the UE mode and / or the UE capability information. You may. In addition, the UE will in the second network selection based on changes in the UE configuration information and / or information received from the network and / or UE mode changes and / or UE capability information. SNPN may be selected. Specifically, when operating in the SNPN access mode, the UE may perform SNPN selection and select SNPN instead of PLMN selection in the second network selection.

Further, when SNPN is selected in the first network selection, the UE may transition to the state in which the SNPN access mode is activated. Further, the UE may transition to the state in which the SNPN access mode is activated when SNPN is selected in the second network selection.

Furthermore, the UE may select an SNPN based on the first network selection, connect to the selected SNPN, or both. Further, the UE may transition to the selected state of the SNPN or the state registered in the SNPN based on the first network selection.

Furthermore, the UE may select a new SNPN based on the second network selection, move from the current SNPN to the new SNPN, or both. Furthermore, the UE may transition to the selected state of the new SNPN based on the second network selection, or may transition from the state registered in the current SNPN to the state registered in the new SNPN. good.

Furthermore, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode or from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the second network selection. You don't have to.

Specifically, the UE may transition to 5GMM-IDLE mode based on the selection of SNPN other than equal SNPN. In other words, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN other than equal SNPN. More specifically, when registered in the SNPN, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN other than equal SNPN. Further, when operating in the SNPN access mode, the UE may transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN other than equal SNPN.

Furthermore, the UE may transition only the 3GPP access status from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN other than equal SNPN.

On the contrary, the UE does not have to transition to the 5GMM-IDLE mode based on the selection of the SNPN which is the equal SNPN. In other words, the UE does not have to transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode based on the selection of SNPN which is an even SNPN. More specifically, when registered in the SNPN, the UE does not have to transition from the 5GMM-CONNECTED mode with RRC inactive indication to the 5GMM-IDLE mode based on the selection of the SNPN which is the equal SNPN. Further, when operating in the SNPN access mode, the UE does not have to transition from the 5GMM-CONNECTED mode with RRC inactive indication to the 5GMM-IDLE mode based on the selection of the SNPN which is the equal SNPN.

Note that the selection of an SNPN other than the equal SNPN may indicate that the SNPN that is not the equal SNPN for the registered SNPN is selected as the new SNPN. Further, the selection of the SNPN other than the equal SNPN may mean that the SNPN that is not the equal SNPN to the registered SNPN is selected as the new SNPN, and the UE is included in the selected new SNPN.

Further, the selection of the SNPN which is the equal SNPN may indicate that the SNPN in the list of equal SNPNs is selected as the new SNPN. Further, the selection of the SNPN which is the equal SNPN may mean that the SNPN in the list of equal SNPNs is selected as the new SNPN and the UE is included in the selected new SNPN. In other words, the selection of an SNPN that is an equal SNPN may mean that the SNPN contained in the list of equal SNPNs is selected as the new SNPN and the UE is included in the selected new SNPN.

Furthermore, the UE may carry out behavior C or continue behavior A based on the second network registration.

Specifically, the UE may perform behavior C based on the registration of SNPNs other than equal SNPNs. In other words, when performing behavior A, the UE may perform behavior C based on the registration of SNPNs other than equal SNPNs.

On the contrary, the UE may continue the behavior A based on the registration of the SNPN which is the equal SNPN. In other words, if the UE is performing behavior A, it may continue behavior A based on the registration of the SNPN, which is an even SNPN.

Here, behavior A may be the same as behavior A during the PDU session establishment procedure. Further, the behavior C may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. .. In addition, behavior C recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is lifted. May be. In addition, behavior C is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 to be lifted. May be. Furthermore, behavior C is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set is lifted. May be.

Further, the behavior C may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. Further, behavior C is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is allowed. You may. Further, behavior C is a behavior that is set to allow the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6. You may. Furthermore, even if behavior C is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. good. Furthermore, behavior C is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv6 is set. You may.

Furthermore, the UE may perform behavior D or continue behavior B based on the second network registration.

Specifically, the UE may perform behavior D based on the registration of SNPNs other than equal SNPNs. In other words, when performing behavior B, the UE may perform behavior D based on the registration of SNPNs other than equal SNPNs.

On the contrary, the UE may continue the behavior B based on the registration of the SNPN which is the equal SNPN. In other words, if the UE is performing behavior B, it may continue behavior B based on the registration of the SNPN, which is an even SNPN.

Here, behavior B may be the same as behavior B during the PDU session establishment procedure. Further, the behavior D may be a behavior that lifts the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. .. Furthermore, behavior D recognizes that the prohibition on starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is lifted. May be. Furthermore, behavior D is a behavior that sets the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set to be lifted. May be. Furthermore, behavior D is a behavior that transitions to a state in which the prohibition of starting a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is lifted. May be.

Further, the behavior D may be a behavior that allows the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. Further, behavior D is a behavior that recognizes that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is allowed. You may. Further, behavior D is a behavior that is set so that the start of a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set is permitted. You may. Further, even if the behavior D is a behavior that sets a new PDU session establishment procedure to be started using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. good. Furthermore, behavior D is a behavior that transitions to a state in which the start of a new PDU session establishment procedure is permitted using the same DNN and / or the same S-NSSAI and the PDU session type in which IPv4 is set. You may.

Note that the registration of an SNPN other than the equal SNPN may indicate that the SNPN is registered in a new SNPN that is not the equal SNPN with respect to the registered SNPN. Further, registration of an SNPN that is an equal SNPN may indicate that it is registered in a new SNPN in the list of equal SNPNs.

Furthermore, the same DNN may be the same DNN as the sent / received DNN in the previously performed PDU session establishment procedure. In other words, the same DNN may be the same DNN that was included in the 12th identification information and sent / received in the previously performed PDU session establishment procedure, or may be included in the 22nd identification information and sent / received. It may be the same DNN as the DNN. Further, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI transmitted / received in the previously performed PDU session establishment procedure. In other words, the same S-NSSAI may be the same S-NSSAI as the S-NSSAI sent and received included in the 13th identification information in the previously performed PDU session establishment procedure, and the 23rd. It may be the same S-NSSAI as the S-NSSAI sent and received included in the identification information of.

Here, the new PDU session establishment procedure may be a PDU session establishment procedure different from the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be a PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure. In other words, the new PDU session establishment procedure may be another PDU session establishment procedure performed after the completion of the previously performed PDU session establishment procedure.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv6 is the same DNN and / or the same S-NSSAI and IPv6. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv6 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv6. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

In addition, the new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and the PDU session type configured with IPv4 is the same DNN and / or the same S-NSSAI and IPv4. It may be a new PDU session establishment procedure for the configured PDU session type. In other words, a new PDU session establishment procedure using the same DNN and / or the same S-NSSAI and an IPv4 configured PDU session type is the same DNN and / or the same S-NSSAI and IPv4. May be the procedure for establishing a PDU session for a UE request for the PDU session type for which is set.

Furthermore, if the request for the PDU session establishment procedure is rejected, each device does not have to establish the PDU session. In this case, after the completion of the PDU session establishment procedure, each device may perform processing based on the information contained in the PDU session establishment refusal message, or perform processing based on the information contained in the PDU session establishment refusal message. By implementing it, the fourth procedure may be completed.

[5. Modification example]
The program that operates on the apparatus according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to operate a computer so as to realize the functions of the embodiments according to the present invention. The program or 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 the program recorded on this recording medium into a computer system and executing it. 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. Is also 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 (6)

1. UE (User Equipment)
   From the lower layer, the transmitter / receiver that receives an indication indicating that the RRC (Radio Resource Control) connection has been suspended, and
   It is equipped with a control unit that transitions to 5GMM-CONNECTED (5G Mobility Management CONNECTED) mode with RRC inactive indication based on the reception of the indication.
   When the UE is registered in the SNPN (Stand-alone Non-Public Network), the control unit changes from the 5GMM-CONNECTED mode with RRC inactive indication to 5GMM based on the selection of PLMN (Public land mobile network). -Transition to IDLE (5G Mobility Management IDLE) mode,
   UE characterized by that.
2. When the UE is registered in the SNPN, the control unit transitions from the 5GMM-CONNECTED mode with RRC inactive indication to the 5GMM-IDLE mode based on the selection of an SNPN that is not an equal SNPN with respect to the SNPN. ,
   The UE according to claim 1, wherein the UE is characterized in that.
3. The control unit maintains the 5GMM-CONNECTED mode with RRC inactive indication when the UE enters a new SNPN included in the list of equal SNPNs.
   The UE according to claim 2, wherein the UE is characterized in that.
4. It is a communication control method for UE (User Equipment).
   A step that receives an indication from the lower layer that the RRC (Radio Resource Control) connection has been suspended, and
   It has a step of transitioning to 5GMM-CONNECTED (5G Mobility Management CONNECTED) mode with RRC inactive indication based on the reception of the indication.
   When the UE is registered in the SNPN (Stand-alone Non-Public Network), the UE changes from the 5GMM-CONNECTED mode with RRC inactive indication to 5GMM- based on the selection of PLMN (Public land mobile network). Transition to IDLE (5G Mobility Management IDLE) mode,
   UE communication control method characterized by that.
5. When the UE is registered in the SNPN, the UE transitions from the 5GMM-CONNECTED mode with RRC inactive indication to the 5GMM-IDLE mode based on the selection of an SNPN that is not an equal SNPN with respect to the SNPN.
   The UE communication control method according to claim 4, wherein the UE communication is controlled.
6. The UE maintains the 5GMM-CONNECTED mode with RRC inactive indication when the UE enters a new SNPN included in the list of equal SNPNs.
   The UE communication control method according to claim 5.
   
   

Images