JP2022173615A - UE (User Equipment) - Google Patents

Abstract

To clarify detailed actions related to network slice access control considering interworking between a 5GS (5G System) or a 5GC (5G Core Network) and EPC (Evolved Packet Core), which is a 4G system core network.SOLUTION: Provided is a UE that comprises a transmission/reception unit and a control unit. When the transmission/reception unit receives from a base station device a registration acceptance message or a registration refusal message including a cause value indicating a fact that a maximum UE number per network slice has been exceeded, and when an E-UTRA (Evolved Universal Terrestrial Radio Access) capability is disabled, the control unit enables the E-UTRA capability and disables an N1 mode capability to 3GPP (3G Partnership Project) access to make a transition to a "5GMM-DEREGISTERED.NO-CELL-AVAILABLE" state.SELECTED DRAWING: Figure 6

Description

The present invention relates to UE (User Equipment).

3GPP (3rd Generation Partnership Project) is studying the system architecture of 5GS (5G System), which is the 5th generation (5G) mobile communication system, and discussions are being held to support new procedures and new functions. (See Non-Patent Documents 1 and 2). Release 15, which is the initial release of the 5G standard, introduced the concept of network slices, and Release 17 discusses functional extensions of the network slices (see Non-Patent Document 3).

3GPP TS 23.501 V17.0.0 (2021-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17) 3GPP TS 23.502 V17.0.0 (2021-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) 3GPP TR 23.700-40 V17.0.0 (2021-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhancement of Network Slicing Phase 2 (Release 17)

Non-Patent Document 3 discloses detailed operations related to network slice access control considering interworking between 5GS or 5GC (5G Core Network) and EPC (Evolved Packet Core), which is the core network of the 4G system. do not have.

One aspect of the present invention has been made in view of the circumstances as described above. To clarify.

Reason why the UE of one aspect of the present invention is a UE (User Equipment) including a transceiver and a controller, and the transceiver indicates from the base station apparatus that the maximum number of UEs per network slice has been exceeded. Upon receiving a registration accept message or a registration reject message containing a value, the control unit enables E-UTRA capability if E-UTRA capability is disabled and N1 mode capability for 3GPP access. is disabled and transitions to the 5GMM-DEREGISTERED.NO-CELL-AVAILABLE state.

According to the present invention, detailed operations related to network slice access control considering interworking between 5GS or 5GC and EPC, which is the core network of the 4G system, can be clarified.

1 is a diagram explaining an outline of a mobile communication system (EPS/5GS); FIG. FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS/5GS); It is a figure explaining the apparatus structure of UE. FIG. 2 is a diagram explaining the configuration of an access network device (gNB) in 5GS; FIG. 2 is a diagram illustrating the configuration of core network equipment (AMF/SMF/UPF) in 5GS; It is a figure explaining a registration procedure. FIG. 4 is a diagram for explaining a PDU session establishment procedure;

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

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

In FIG. 1, a mobile communication system 1 includes UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6. It is stated that

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

Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc. The interfaces that connect these devices/functions together are described.

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

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

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

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

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

Also, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as public wireless LAN. On the other hand, a trusted non-3GPP access network may be a 3GPP defined access network and may comprise a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF).

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

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

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

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

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

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

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

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

Also, the UE may connect to an access network. Also, the UE can connect to the core network via the access network. Furthermore, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can transmit/receive (communicate) user data with the PDN or DN. When transmitting/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 consists of an IP header and a payload. The payload part may include data transmitted and received by devices/functions included in EPS and devices/functions included in 5GS. Non-IP communication is data communication that does not use IP, and data is transmitted and received in a format different from the structure of IP packets. For example, non-IP communication may be data communication realized by sending and receiving application data to which no IP header is attached, or may be data communication realized by attaching another header such as a MAC header or Ethernet (registered trademark) frame header to the UE. User data to be transmitted and received may be transmitted and received.

In addition, devices not shown in FIG. 2 may be configured in access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A. For example, core network_A and/or core network_B may include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S).

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

Also, the AAA server is a device with authentication and authorization and billing functions that connects with AUSF directly or indirectly through other network devices. The AAA server may be a network device within the core network. Note that the AAA server may be included in the PLMN instead of being included in Core Network_A and/or Core Network_B. That is, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device within the PLMN managed by the 3rd Party.

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

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

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

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

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

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

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

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

[2.2. Equipment configuration of gNB]
Next, a device configuration example of the gNB will be described using FIG. The gNB consists 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. Transceiver_B 530 is connected to antenna 510 .

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

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

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

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

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

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

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

Network connection unit_B720 is a functional unit for AMF to connect with a base station apparatus (gNB) in 5G AN, and/or SMF, and/or PCF, and/or UDM, and/or SCEF. That is, AMF uses the network connection unit _B720 to connect the user Data and/or control information can be sent and received.

To explain in detail with reference to FIG. 2, AMF in 5GCN can communicate with gNB through N2 interface by using network connection part_A620, and with UDM through N8 interface. It can communicate with SMF via the N11 interface and with PCF via the N15 interface. Also, the AMF can transmit and receive NAS messages with the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is a logical one, in practice the communication between the UE and the AMF will take place over the 5G AN. Also, if 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 the AMF.

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

Also, in registration management, the RM state 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 with the network, so the UE context in the AMF does not have valid location and routing information for the UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, the UE is registered with the network so that the UE can receive services that require registration with the network. Note that the RM state may be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as a 5GMM-REGISTERED state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Also, NSSF (Network Slice Selection Function) may be a network function (also referred to as NF) that has a function of selecting a network slice that serves a UE.

Also, NWDAF (Network Data Analytics Function) may be an NF having a function of collecting data from an NF or an application function (also called AF).

A PCF (Policy Control Function) may be an NF having a function of determining a policy for controlling network behavior.

Also, NRF (Network Repository Function) may be an NF having a service discovery function. An NRF may be an NF capable of providing information of discovered NFs upon receiving a discovery request from another NF.

The Network Slice Admission Control Function (NSACF) also monitors the number of registered UEs per NS and/or the number of PDU sessions per NS for network slices (NSs) associated with NSAC (Network Slice Admission Control). and control functions. The NSACF may also be configured with the allowed maximum number of UEs per NS and/or maximum number of PDU sessions per NS for each NS associated with the NSAC. Also, the NSACF may have a function to increase or decrease the number of UEs registered with a certain NS so as not to exceed the maximum number of UEs allowed to register with that NS. The NSACF may also maintain a list of UE IDs registered with NSs associated with the NSAC. In addition, when the number of UEs registered with the NS increases (for example, when a certain UE newly transmits a registration request message to the NS), the NSACF determines that the ID of the UE is the UE registered with the NS. Check if it is already in the list of IDs, if the ID of that UE is not in the list, further check for that NS if the maximum number of UEs per NS has been reached may have a function. Also, if the registration status of the UE with the NS associated with the NSAC changes during the registration procedure and/or the de-registration procedure and/or the NSSAA procedure etc., the AMF shall notify the NSACF per NS may make a request for the maximum number of UEs in The NSACF may also have the ability to increase or decrease the number of PDU sessions for an NS so that the maximum number of PDU sessions allowed by that NS is not exceeded. Also, when the number of PDU sessions using an NS increases (for example, when a certain UE sends a PDU session establishment request message for that NS), the NSACF reaches the maximum number of UEs per NS for that NS. It may have a function to confirm whether or not there is The SMF may also request the NSACF regarding the maximum number of PDU sessions per NS during the PDU session establishment and/or PDU session release procedures.

In addition, an SM (session management) message (also referred to as NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and is transmitted and received between UE_A10 and SMF_A230 via AMF_A240. may be a control message that In addition, SM messages include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, and a PDU session establishment request message. PDU session modification command message, PDU session modification complete message, PDU session modification command reject message, PDU session modification reject message. PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete A message or the like may be included.

In addition, procedures for SM or SM procedures include PDU session establishment procedure, PDU session modification procedure, PDU session release procedure (UE-requested PDU session release procedure). may be Note that each procedure may be a procedure started from the UE, or may be a procedure started from the NW.

Also, MM (Mobility management) messages (also referred to as NAS MM messages) may be NAS messages used in procedures for MM, and may be control messages transmitted and received between UE_A10 and AMF_A240. Further, the MM message includes a Registration request message, a Registration accept message, a Registration reject message, a De-registration request message, a De-registration accept message. ) message, configuration update command message, configuration update complete message, Service request message, Service accept message, Service reject message, Notification ) message, Notification response message, etc. may be included.

Also, the procedures for MM or MM procedures are Registration procedure, De-registration procedure, Generic UE configuration update procedure, Authentication/Authorization procedure, Service request procedure ( Service request procedure, Paging procedure, Notification procedure.

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

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

A PDN (Packet Data Network) type indicates a 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. If non-IP is specified, it indicates that communication is to be performed by a communication method other than IP, rather than using IP.

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

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

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

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

A PLMN (Public land mobile network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator who is a communication carrier, and the operator can be identified by the PLMN ID. The PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the IMSI (International Mobile Subscriber Identity) of the UE may be the Home PLMN (HPLMN). Furthermore, the UE may hold an Equivalent HPLMN list for identifying one or more EPLMNs (Equivalent HPLMN) in USIM. A PLMN different from HPLMN and/or EPLMN may be VPLMN (Visited PLMN). A PLMN that the UE has successfully registered may be an RPLMN (Registered PLMN).

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

Also, a network slice instance (NSI) is configured with a network function (NF) instance (entity) and a set of necessary resources to form a network slice to be arranged. Here, NF is a processing function in a network, which is adopted or defined by 3GPP. One or more NSIs are entities of NSs configured in core network_B. Also, the NSI may be composed of a virtual NF (Network Function) generated using an NST (Network Slice Template). Here, an NST is a logical representation of one or more NFs associated with resource requirements for providing a desired communication service or capability. In other words, the NSI may be an aggregate within the core network_B 190 composed of multiple NFs. Also, the NSI may be a logical network configured to separate user data delivered by services or the like. One or more NFs may be configured in the NS. The NFs configured in the NS may or may not be devices shared with other NSs. UEs and/or devices in the network may, based on NSSAI and/or S-NSSAI and/or UE usage type and/or registration information such as one or more NSI IDs and/or APNs, one or more can be assigned to the NS of Note that the UE usage type is a parameter value included in the registration information of the UE used for identifying the NSI. UE usage type may be stored in HSS. AMF may select between SMF and UPF based on UE usage type.

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

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

A configured NSSAI (also referred to as Configured NSSAI) is an NSSAI that is provided and stored in the UE. The UE may store the configured NSSAI per PLMN. A configured NSSAI may be information configured by the network (or PLMN). An S-NSSAI included in a configured NSSAI may be expressed as a configured S-NSSAI. A configured S-NSSAI may be configured including an S-NSSAI and a mapped S-NSSAI.

Also, requested NSSAI (also called Requested NSSAI, Requested NSSAI) is the NSSAI provided by the UE to the network during the registration procedure. The requested NSSAI may be an allowed NSSAI or a configured NSSAI that the UE remembers. Specifically, the requested NSSAI may be information indicating the network slice that the UE wishes to access. An S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is included in an RRC (Radio Resource Control) message including a NAS message or NAS (Non-Access-Stratum) message sent from the UE to the network, such as a registration request message or a PDU session establishment request message. be done.

Also, allowed NSSAI (Allowed NSSAI, also referred to as Allowed NSSAI) is information indicating one or more network slices for which the UE is allowed. In other words, the allowed NSSAI is information identifying network slices that the network has allowed to connect to the UE. The UE and the network each store and manage the allowed NSSAI as UE information for each access (3GPP access or non-3GPP access). An S-NSSAI included in the allowed NSSAI may be expressed as an allowed S-NSSAI. allowed S-NSSAI may consist of S-NSSAI and mapped S-NSSAI.

A mapped S-NSSAI (also referred to as a mapped S-NSSAI) is an HPLMN's S-NSSAI mapped to a registered PLMN's S-NSSAI in a roaming scenario. The UE may store one or more mapped S-NSSAIs mapped to S-NSSAIs included in the configured NSSAI and Allowed NSSAI for each access type. Furthermore, the UE may store one or more mapped S-NSSAIs of the S-NSSAIs included in the rejected NSSAI.

Also, rejected NSSAI (also referred to as Rejected NSSAI) is information indicating one or more network slices for which the UE is not permitted. In other words, the rejected NSSAI is information identifying network slices that the network does not allow the UE to connect to. The rejected NSSAI may be information including one or more combinations of S-NSSAI and rejection reason values. Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and network may store and manage the rejected NSSAI appropriately, respectively, based on the rejection value associated with each S-NSSAI. Furthermore, the rejected NSSAI may be included in a NAS message transmitted from the network to the UE, such as a registration acceptance message, a configuration update command, a registration rejection message, or an RRC message including a NAS message. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected NSSAI may be any one of the first to third rejected NSSAIs and the pending NSSAI, or may be a combination thereof. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may consist of an S-NSSAI and a mapped S-NSSAI.

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

Also, the first rejected NSSAI is valid for the entire registered PLMN. In other words, the UE and/or NW may treat the first rejected NSSAI and the S-NSSAI included in the first rejected NSSAI as information independent of the access type. That is, the first rejected NSSAI may be valid information for 3GPP access and non-3GPP access.

The UE may delete the first rejected NSSAI from memory if it transitions to the unregistered state with both 3GPP access and non-3GPP access to the current PLMN. In other words, if the UE transitions to the non-registered state with respect to the current PLMN via an access, or has successfully registered with a new PLMN via a certain access, or attempts to register with a new PLMN via a certain access. If it fails and transitions to the non-registered state, and if the UE is in the non-registered state (non-registered state) via the other access, the UE deletes the first rejected NSSAI.

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

Also, the second rejected NSSAI is valid within the current registration area. That is, the UE and/or NW may treat the second rejected NSSAI and the S-NSSAI included in the second rejected NSSAI as information for each access type. That is, the second rejected NSSAI may be valid information for 3GPP access or non-3GPP access respectively. That is, the UE may delete the second rejected NSSAI from memory once it transitions to the unregistered state for an access.

Also, the third rejected NSSAI is an S-NSSAI that requires NSSAA, and is a set of one or more S-NSSAIs for which NSSAA for that S-NSSAI has failed or been revoked. The third rejected NSSAI may be an NSSAI stored by the UE and/or the NW, or transmitted from the NW to the UE. When the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information including one or more combinations of S-NSSAI and refusal reason values. The refusal reason value at this time may be "S-NSSAI is not available due to the failed or revoked network slice-specific authorization and authentication)", It may be information indicating that the NSSAA for the S-NSSAI associated with the refusal reason value has failed or been cancelled.

Also, the third rejected NSSAI is valid for the entire registered PLMN. In other words, the UE and/or NW may treat the third rejected NSSAI and the S-NSSAI included in the third rejected NSSAI as information independent of the access type. That is, the third rejected NSSAI may be valid information for 3GPP access and non-3GPP access. The third rejected NSSAI may be an NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI.

A third rejected NSSAI is a rejected NSSAI in which the UE identifies slices that were rejected due to a failed or canceled NSSAA from the core network. Specifically, the UE does not initiate a registration request procedure for the S-NSSAI contained in the third rejected NSSAI while storing the third rejected NSSAI. The third rejected NSSAI may be identification information including one or more S-NSSAI received from the core network associated with a rejection reason value indicating NSSAA failure. The third rejected NSSAI is information independent of access type. Specifically, if the UE memorizes the third rejected NSSAI, the UE attempts to send a registration request message containing the S-NSSAI contained in the third rejected NSSAI to both the 3GPP access and the non-3GPP access. It doesn't have to be. Alternatively, the UE may send a Registration Request message including the S-NSSAI included in the third rejected NSSAI based on UE policy. Alternatively, the UE may delete the third rejected NSSAI based on the UE policy and transition to a state where it can transmit a registration request message including the S-NSSAI included in the third rejected NSSAI. In other words, if the UE transmits a registration request message that includes the S-NSSAI included in the third rejected NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third rejected NSSAI. good.

In addition, pending NSSAI (pending NSSAI, also called Pending NSSAI) is S-NSSAI where the network requires network slice specific authentication, network slice specific authentication has not been completed, and it cannot be used in the current PLMN. A set of one or more S-NSSAIs. A pending NSSAI may be a 5GS Rejected NSSAI due to NSSAA or a pending NSSAI. The pending NSSAI may be an NSSAI stored by the UE or NW, or may be an NSSAI transmitted from the NW to the UE. The pending NSSAI is not limited to the rejected NSSAI, and may be an NSSAI independent of the rejected NSSAI. If the pending NSSAI is the NSSAI sent from the NW to the UE, the pending NSSAI may be information containing one or more combinations of S-NSSAI and refusal reason values. The reason for refusal value at this time may be "S-NSSAI (NSSAA is pending for the S-NSSAI)", and the S-NSSAI associated with the reason for refusal value is the S- It may be information indicating prohibition or pending use by the UE until the NSSAA for the NSSAI is completed.

Also, the pending NSSAI is valid throughout the registered PLMN. In other words, the UE and/or NW may treat the S-NSSAI included in the third rejected NSSAI and pending NSSAI as access-type-independent information. That is, pending NSSAI may be valid information for 3GPP access and non-3GPP access. The pending NSSAI may be a different NSSAI than the rejected NSSAI. The pending NSSAI may be the first rejected NSSAI.

Also, the pending NSSAI is an NSSAI composed of one or more S-NSSAIs that identify slices for which the UE is pending procedures. Specifically, the UE does not initiate a registration request procedure for the S-NSSAI contained in the pending NSSAI while storing the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI included in the pending NSSAI is completed. The pending NSSAI is identification information containing one or more S-NSSAIs received from the core network associated with a rejection reason value indicating pending for NSSAA. The pending NSSAI is information independent of access type. Specifically, if the UE memorizes the pending NSSAI, the UE does not attempt to send a registration request message containing the S-NSSAI contained in the pending NSSAI to both 3GPP and non-3GPP accesses.

A tracking area is a single or multiple ranges that can be represented by the location information of UE_A 10 managed by the core network. A tracking area may consist of multiple cells. Furthermore, the tracking area may be a range in which control messages such as paging are broadcast, or a range in which UE_A 10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or the like. Hereinafter, the tracking area may be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) composed of a TAC (Tracking area code) and a PLMN.

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

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

Network Slice-Specific Authentication and Authorization (NSSAA) is a function for implementing network slice-specific authentication and authorization. Network slice specific authentication and authorization allows UE authentication and authorization outside the core network, such as a 3rd party. PLMNs and network devices with NSSAA capability can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information. Additionally, a UE with NSSAA capability can manage and store rejected NSSAIs for pending NSSAAs and/or rejected NSSAIs for failed NSSAAs. In this paper, NSSAA may be referred to as network slice-specific authentication and authorization procedures or as authentication and authorization procedures.

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

Also, a UE in single registration mode has only one active MM state. That is, a UE in single registration mode is only active in either the RM state (5GMM state) in 5GC or the EMM state in EPC. Also, a UE in single registration mode is in 5GC NAS mode when connecting to 5GC, and is in EPC NAS mode when connecting to EPC. Also, since a UE in single registration mode can only register with either 5GC or EPC, there is no mapping between EPS-GUTI (also called 4G-GUTI) and 5G-GUTI when moving between EPC and 5GC. need to

Also, a UE in dual registration mode may be in a state where it can register independently for 5GC and EPC. A UE in dual registration mode can maintain 5G-GUTI and EPS-GUTI (also called 4G-GUTI) independently.

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

First, the first identification information is information indicating the network slice that the UE wishes to register. Also, the first identification may be the Requested NSSAI, which may be the NSSAI provided by the UE to the PLMN when registering with the network. Also, the first identification information may include one or more S-NSSAI. The S-NSSAI included in the first identification information may be the S-NSSAI included in the configured NSSAI associated with the current PLMN, or the S-NSSAI included in the allowed NSSAI associated with the current PLMN. -may be NSSAI. In other words, the first identification information is S-NSSAI included in the configured NSSAI associated with one or more current PLMNs, or S-NSSAI included in the allowed NSSAI associated with one or more current PLMNs. -NSSAI, or a combination of the two above. More specifically, the allowed NSSAI associated with the current PLMN may be the allowed NSSAI associated with the current PLMN and current access type.

Also, the S-NSSAI included in the first identification information may be a rejected NSSAI and/or an S-NSSAI that is not included in the pending NSSAI. Also, the S-NSSAI included in the first identification information may be an S-NSSAI whose associated backoff timer is not running.

Also, the eleventh identification information may be information indicating a network slice. Also, the eleventh identification information may be S-NSSAI. Also, the eleventh identification information may be information indicating an S-NSSAI that has reached the maximum number of UEs or the maximum number of PDU sessions that can be registered in the network slice. Also, the eleventh identification information may be included in the Allowed NSSAI transmitted from the network, may be included in the Rejected NSSAI transmitted from the network, or may be included in the Pending NSSAI transmitted from the network. Alternatively, it may be transmitted from the network as information different from these.

Also, the eleventh identification information may be NSSAI. Also, the eleventh identification information may be an Allowed NSSAI, a Rejected NSSAI, a Pending NSSAI, or an NSSAI different from these. The eleventh identification information may comprise one or more twelfth and/or thirteenth identification information.

Also, the twelfth identification information may be a cause value. Also, the twelfth identification information may be indicated as 5GMM (5G Mobility Management) cause.

Also, the twelfth identification information may indicate that the maximum number of UEs per NS has been exceeded, may indicate that the maximum number of UEs per NS has been reached, or an NS-related It may indicate that the quota has been exceeded.

Also, the twelfth identification information may indicate congestion, may indicate that redirection to EPC is required (Redirection to EPC required), or that there is no available NS ( No network slices available), Insufficient resources for specific NS and DNN (Insufficient resources for specific slice and DNN), Insufficient resources for specific NS Insufficient resources for specific slice may be indicated.

Also, the twelfth identification information may comprise one or more of the eleventh and/or thirteenth identification information.

Also, the thirteenth identification information may be a backoff timer value. Specifically, the thirteenth identification information may indicate a period during which the UE is prohibited from transmitting an MM message or SM message using the S-NSSAI indicated by the eleventh identification information. Also, the thirteenth identification information may indicate a period during which the UE is prohibited from returning to the N1 mode when the system is changed from the N1 mode to the S1 mode. Also, the 13th identification information is an MM message using the S-NSSAI indicated by the 11th identification information, although the UE can return to the N1 mode when the system is changed from the N1 mode to the S1 mode, Alternatively, it may indicate a period during which the UE is prohibited from transmitting SM messages.

Also, the thirteenth identification information may comprise one or more of the eleventh and/or twelfth identification information.

Also, the fourteenth identification information may be information including at least one of the eleventh to thirteenth identification information.

The 21st identification information is a PDU session ID that identifies a PDU session. Also, the twenty-first identification information may be a PDU session ID that identifies a PDU session for which establishment is requested.

Also, the twenty-second identification information is a PDU session type that identifies the type of PDU session. Also, the twenty-second identification information may be the PDU session type requested by the UE for the PDU session. Also, the 22nd identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).

Also, the twenty-third identification information is the SSC mode. Also, the twenty-third identification information may be the SSC mode requested by the UE for the PDU session. Also, the twenty-third identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.

Also, the twenty-fourth identification information is one or more S-NSSAIs. Also, the twenty-fourth identification information may be one or more S-NSSAIs requested by the UE for the PDU session to be established. Also, the twenty-fourth identification information may be one or more S-NSSAIs selected from the Allowed NSSAIs for the current access type. Specifically, the twenty-fourth identification information may be one or more S-NSSAIs allowed by the network as Allowed S-NSSAIs included in the registration acceptance message in the registration procedure. Also, not including the twenty-fourth identification information may be referred to as no S-NSSAI.

Also, the twenty-fifth identification information is DNN. Also, the twenty-fifth identification information may be a DNN that identifies a DN to which a PDU session that the UE requests to be established is connected. Also, not including the twenty-fifth identification information may be referred to as no DNN.

Also, the 26th identification information may be information including at least one of the 21st to 25th identification information.

The 31st identification information is a PDU session ID that identifies a PDU session. It may be a PDU session ID that identifies a PDU session that is allowed to be established by the network. The 31st identification information may be the same as the 21st identification information.

The 32nd identification information is a PDU session type that identifies the type of PDU session. Also, the thirty-second identification information may be the PDU session type selected by the network. Also, the 32nd identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).

The 33rd identification information is the SSC mode. Also, the thirty-third identification may be the SSC mode selected by the network for the PDU session. Also, the 33rd identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.

Also, the thirty-fourth piece of identification information is one or more S-NSSAIs. The thirty-fourth identification information may be the same as the twenty-fourth identification information. The thirty-fourth identification information may comprise one or more of the thirty-sixth and/or thirty-seventh identification information.

The thirty-fifth identification information is DNN. Also, the thirty-fifth identification information may be a DNN that identifies a DN to which the PDU session is connected. The thirty-fifth identification information may be the same as the twenty-fifth identification information.

Also, the thirty-sixth identification information may be a cause value. Also, the thirty-sixth identification information may be indicated as a 5GMM (5G Mobility Management) cause and/or a 5GSM (5G Session Management) cause.

Also, the thirty-sixth identification information may indicate that the maximum number of PDU sessions per NS has been exceeded, may indicate that the maximum number of PDU sessions per NS has been reached, or may indicate that the maximum number of PDU sessions per NS has been reached. MAY indicate that the NS-related quota has been exceeded.

In addition, the 36th identification information may indicate that resources are insufficient (Insufficient resources), or that resources for specific NS and DNN are insufficient (Insufficient resources for specific slice and DNN). It may indicate that there are insufficient resources for a specific NS (Insufficient resources for specific slice), or it may indicate that the maximum number of PDU sessions has been reached.

Also, the thirty-sixth identification information may comprise one or more of the thirty-fourth and/or thirty-seventh identification information.

Also, the 37th identification information may be a backoff timer value. Specifically, the thirty-seventh identification information may indicate a period during which the UE is prohibited from transmitting an MM message or an SM message using the S-NSSAI indicated by the thirty-fourth identification information. Also, the 37th identification information may indicate a period during which the UE is prohibited from returning to the N1 mode when the system is changed from the N1 mode to the S1 mode. Also, the 37th identification information is an MM message using the S-NSSAI indicated by the 11th identification information, although the UE can return to the N1 mode when the system is changed from the N1 mode to the S1 mode, Alternatively, it may indicate a period during which the UE is prohibited from transmitting SM messages.

Also, the thirty-seventh identification information may comprise one or more of the thirty-fourth and/or thirty-sixth identification information.

Also, the 38th identification information may be information including at least one of the 31st to 37th identification information.

[3. First embodiment]
First, procedures used in the first embodiment will be described. Procedures used in the first embodiment include a registration procedure, a PDU session establishment procedure, and the like. Each procedure will be described below.

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

[3.1. Registration procedure]
Next, the registration procedure will be explained using FIG. In this chapter, this registration procedure may be referred to simply as the Procedure. A registration procedure is a procedure for UE-initiated registration to access network_B and/or core network_B and/or DN. As long as the UE is not registered with the network, the UE can execute this procedure at any time, such as when it is powered on. In other words, the UE can start this procedure at any timing as long as it is in the non-registered state (5GMM-DEREGISTERED state). Also, each device (especially UE and AMF) can transition to the registered state (5GMM-REGISTED state) based on the completion of the registration procedure. Each registration state may be managed by each device for each access. Specifically, each device may independently manage the state of registration for 3GPP access (registered state or non-registered state) and the state of registration for non-3GPP access.

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

A UE may initiate a registration procedure upon mobility across TAs. In other words, the UE may initiate the registration procedure when moving to a TA different from the TA indicated in the TA list it maintains. Additionally, the UE may initiate a registration procedure when the context of each device needs to be updated due to PDU session disconnection or invalidation. In addition, the UE may initiate a registration procedure when there is a change in capability information and/or preferences regarding the UE's PDU session establishment. Further, the UE may initiate registration procedures periodically. Further, the UE may initiate the registration procedure based on completion of the registration procedure, or completion of the PDU session establishment procedure, or information received from the network in each procedure. That is, the registration process may be initiated after performing the procedures in Chapters 3.1 and/or 3.2. Note that the UE is not limited to these, and can execute the registration procedure at any timing.

Note that the procedure for the UE to transition from a state in which the UE is not registered with the network (non-registered state) to a state in which it is registered (registered state) is an initial registration procedure or registration for initial registration. It may be a registration procedure for initial registration. In addition, the registration procedure performed in a state in which the UE is registered in the network (registration state) is a registration procedure for mobility and periodic registration update or a registration procedure for mobility and periodic registration update. It may be a mobility and periodic registration procedure.

Details of the registration procedure described below are applicable to either of these.

First, the UE initiates the registration procedure by sending a Registration request message to the AMF (S600) (S602) (S604). Specifically, the UE transmits an RRC message including a registration request message to the base station apparatus (5G AN, also referred to as gNB) (S600). Note that the registration request message is a NAS message sent and received on the N1 interface. Also, the RRC message may be a control message transmitted and received between the UE and the base station apparatus. Also, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

Here, the UE may include the first identification information in the registration request message and/or the RRC message and transmit it. Here, the first identification information may be as described in Section 2.6. Furthermore, the UE may transmit identification information indicating the type of this procedure in the registration request message and/or the RRC message. Here, the identification information indicating the type of this procedure may be 5GS registration type IE (Information Element). The 5GS registration type IE is information to indicate the type of registration requested: initial registration, mobility registration updating, periodic registration updating. ), may indicate emergency registration.

The UE may include UE capability information in the Registration Request message to inform the network of the features that the UE supports. Here, the UE capability information may be the 5GMM capability IE of 5GS.

The UE uses these identification information as control messages different from these, for example, layers lower than the RRC layer (for example, MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP (Packet Data Convergence Protocol ) layer, SDAP (Service Data Adaptation Protocol) layer, etc.) may be included in a control message and transmitted. By transmitting these pieces of identification information, the UE may indicate that the UE supports each function, may indicate the UE's request, or indicate both.

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

The UE may remember allowed NSSAI, configured NSSAI, rejected NSSAI, mapped S-NSSAI.

The UE may include information other than the first identification information in the registration request message and/or the RRC message, such as including the UE ID and/or the PLMN ID and/or the AMF identification information. Here, the AMF identification information may be information that identifies an AMF or a set of AMFs, such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) or GUAMI (Globally Unique AMF Identifier). you can

Upon receiving the RRC message including the registration request message, the base station apparatus selects an AMF to transfer the registration request message (S602). Note that the base station apparatus may select an AMF based on identification information included in the registration request message and/or the RRC message. Specifically, when the first identification information is received, the base station apparatus may select the AMF to which the registration request message is to be sent based on the first identification information. Specifically, the base station apparatus may select an AMF included in the network slice identified by the first identification information or an AMF with connectivity to the network slice identified by the first identification information. good.

Note that the AMF selection method is not limited to this, and the base station apparatus may select an AMF based on other conditions.

The base station device extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S604). In addition, if the first identification information is included in the RRC message but not in the registration request message, the identification information included in the RRC message may be transferred to the selected AMF together with the registration request message. (S604).

If the AMF receives the registration request message, it can perform a first condition determination. The first condition determination is for determining whether or not the network accepts the request from the UE. The AMF may execute the procedures from S610 to S612 if it determines that the first condition determination is true. Also, the AMF may execute the procedure of S610 if the first condition determination is false.

Also, the first condition determination may be executed by a network function (also called NF) other than AMF. The NF may be, for example, NSACF. If an NF other than the AMF performs the first condition determination, the AMF provides that NF with information necessary to perform the first condition determination, specifically at least one of the information received from the UE. You may provide the part (S606). Then, if the NF determines whether the first conditional determination is true or false based on the information received from the AMF, it sends information including the result of the first conditional determination (that is, whether it is true or false) to the AMF. You can tell The AMF may determine identification information and/or control messages to send to the UE based on the result of the first condition determination received from the NF.

Note that if the first condition determination is true, the control message transmitted and received in S610 may be a registration accept message, and if the first condition determination is false, the control message transmitted and received in S610. The message may be a Registration reject message.

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

For example, the first conditional decision may be determined to be true if the network grants the UE's request, and the first conditional determination may be determined to be false if the network does not grant the UE's request. In addition, when the network to which the UE is registered and/or the device in the network supports the function requested by the UE, the first condition determination may be determined as true, and the function requested by the UE is supported. If not, the first conditional determination may be determined to be false. Further, the first conditional determination may be determined to be true if the transmitted/received identification information is permitted, and the first conditional determination may be determined to be false if the transmitted/received identification information is not permitted. Also, exceeding the maximum number of UEs per NS, or reaching the maximum number of UEs per NS, or exceeding the NS-related quota for the maximum number of UEs, or congestion, or requiring redirection to the EPC. (Redirection to EPC required), or No network slices available, or Insufficient resources for specific NS and DNN, or specific If the registration request is rejected due to reasons such as insufficient resources for the NS (Insufficient resources for specific slice) (hereinafter referred to as refusal reason 1), the first condition determination is determined to be false. good. Also, if the registration request is not rejected due to the reason for refusal 1, the first condition determination may be determined to be true.

The AMF may include one or more of the 11th to 14th identification information in the control message and transmit it. Here, the 11th to 14th identification information may be as described in Chapter 2.6. By sending these identification information and/or control messages, the AMF may indicate that the network supports each function, or indicate that the UE's request has been accepted. and may indicate that the request from the UE is not permitted, or may indicate information combining these. Furthermore, when a plurality of identification information are transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

When the AMF receives the registration request message including the first identification information from the UE, the AMF may include at least one identification information among the 11th to 14th identification information in the control message and transmit it.

In addition, even when the AMF receives a registration request message that does not include the first identification information from the UE, the AMF includes at least one identification information among the 11th to 14th identification information in the control message and transmits it. may

The AMF may further include configured NSSAI and/or allowed NSSAI and/or rejected NSSAI and/or pending NSSAI in the control message. Note that the eleventh to fourteenth identification information may be transmitted while being included in the allowed NSSAI, rejected NSSAI, and/or pending NSSAI, or may be transmitted as information different from these.

At the time of transmission of the control message, the AMF indicates that the UE does not have S-NSSAI (allowed NSSAI), but if there is a plan to perform the NSSAA procedure after completing this procedure or in parallel with this procedure, or if the UE and the network An empty value may be included in the allowed NSSAI and sent when the NSSAA procedure is being executed between them, or when the pending NSSAI is included in the control message and sent.

In addition, the AMF determines which identification information among the 11th to 14th identification information is included in the control message, each received identification information, and/or subscriber information, and/or network capability information, and/or It may be determined based on operator policy, and/or network conditions, and/or user registration information, and/or context held by the AMF, and/or the like.

In addition, AMF receives each identification information, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network status, and/or user registration information, and/or Based on the context held by the AMF, etc., it may indicate that the UE's request has been accepted by sending a Registration Accept message, or indicate that the UE's request has been rejected by sending a Registration Reject message. may be indicated.

Also, when rejecting the registration request due to refusal reason 1, the network (e.g., AMF and/or NSACF) indicates that the maximum number of UEs per NS has been exceeded and/or the maximum number of UEs per NS has been reached. , and/or exceeding the NS-related quota on the maximum number of UEs, and/or congestion, and/or Redirection to EPC required, and/or no NS available. (No network slices available), and/or Insufficient resources for specific NS and DNN, and/or Insufficient resources for specific NS resources for specific slice) may be set to the twelfth identification information.

The network (eg, AMF and/or NSACF) may then consider the UE's S1 mode capability to decide to reject using the twelfth identification. Here, the S1 mode may refer to a mode of the UE that can access the 4G core network via the 4G access network, and the S1 mode capability refers to the UE having the S1 mode capability, that is, the UE has the ability to access a 4G core network via a 4G access network, or it may mean that it has the ability to communicate using 4G.

In addition, since AMF and/or NSACF does not fall under reason 1 for refusal, if the request of the UE is permitted, or if the use of S-NSSAI included in the first identification information received from the UE is permitted, the S -NSSAI may be allowed S-NSSAI, and allowed S-NSSAI may be included in the eleventh identification information. In addition, since AMF and/or NSACF does not fall under reason 1 for refusal, if the request of the UE is permitted, or if the use of S-NSSAI included in the first identification information received from the UE is permitted, the S -NSSAI may be allowed S-NSSAI, and the eleventh identification information may include Allowed NSSAI including allowed S-NSSAI.

In addition, AMF and/or NSACF does not permit (reject) the UE's request or does not permit the use of S-NSSAI included in the first identification information received from the UE because it falls under reason 1 for refusal. When (rejecting), the S-NSSAI may be set as a rejected S-NSSAI, and the rejected S-NSSAI may be included in the eleventh identification information. In addition, AMF and/or NSACF does not permit (reject) the UE's request or does not permit the use of S-NSSAI included in the first identification information received from the UE because it falls under reason 1 for refusal. In the case of (rejection), the S-NSSAI may be a rejected S-NSSAI, and the eleventh identification information may include an Allowed NSSAI or a Rejected NSSAI including the rejected S-NSSAI.

In addition, since AMF and/or NSACF do not fall under reason 1 for refusal, when permitting the request of the UE or permitting the use of S-NSSAI included in the first identification information received from the UE, the 12th Do not include identification information for

In addition, AMF and/or NSACF does not permit (reject) the UE's request or does not permit the use of S-NSSAI included in the first identification information received from the UE because it falls under reason 1 for refusal. If (rejected), a twelfth identification may be included.

In addition, AMF and/or NSACF does not permit (reject) the UE's request or does not permit the use of S-NSSAI included in the first identification information received from the UE because it falls under reason 1 for refusal. In the case of (reject), the thirteenth identification information may include a backoff timer value.

The UE receives the control message (registration acceptance message or registration rejection message) and/or the transmitted 11th to 14th identification information via the base station apparatus (S610). If the control message is a registration acceptance message, the UE receives the registration acceptance message to recognize that the UE's request in the registration request message has been accepted and the contents of various identification information included in the registration acceptance message. can do. In addition, if the control message is a registration rejection message, the UE receives the registration rejection message, indicating that the request of the UE by the registration request message is rejected, and the content of various identification information included in the registration rejection message. can be recognized.

Also, when the UE receives the twelfth identification information via non-3GPP access, it may be regarded as an abnormal case. Also, the UE may regard the case of receiving the twelfth identification information via a cell belonging to SNPN as an abnormal case.

The UE may also set the 5GS update status (also referred to as 5U status) in the UE to 5U3 ROAMING NOT ALLOWED when the 12th identification is received. Here, 5U status specifies the state of the UE in the 5GMM layer, and 5U3 ROAMING NOT ALLOWED is for the previous registration, or the previous service request, or the previous movement and periodic registration update. The registration procedure for mobility and periodic registration update was performed correctly (successfully), but the response from the AMF was negative.

Also, when the UE receives the twelfth identification information, the UE may delete all 5G-GUTIs, previously registered TAIs, TAI lists, and the like. Additionally, the UE may reset a registration attempt counter. Here, the registration attempt counter is used to limit the number of registration attempts. In other words, the registration attempt counter may be used to limit the number of times the registration procedure is performed. The registration attempt counter is incremented by 1 each time the registration procedure fails, unless it is set to 5, but may be reset in certain cases. The registration attempt counter is also reset when the UE is powered on, when the USIM is inserted, when the registration procedure is successfully completed, and so on.

Also, when the UE receives the twelfth identification information, the UE may enable the E-UTRA capability if the E-UTRA capability is disabled. may disable the N1 mode capability for 3GPP access, or transition to the 5GMM-DERIGISTERED.NO-CELL-AVAILABLE state. Here, the E-UTRA capability may mean that the UE has the capability of accessing the 4G core network via the 4G access network, or that the UE has the capability of accessing the 4G access network. It may mean having, or it may mean the ability to communicate using 4G. In addition, N1 mode means the mode of the UE that can access the 5G core network via the 5G access network, and N1 mode capability means that the UE has N1 mode capability, that is, the UE can access the 5G It may mean having the ability to access the 5G core network through the access network. Also, 5GMM-DERIGISTERED.NO-CELL-AVAILABLE may be a state in which a 5G cell cannot be selected.

Also, the UE receives the twelfth identification information via 3GPP access, the UE is operating in single registration mode, and the twelfth identification information is received in the attach procedure in the EPS. If rejected using, the UE may act with EMM state, EPS update status, 4G-GUTI, attach attempt counter, etc. That is, the UE may operate using 4G parameters instead of 5G parameters. Here, the attach attempt counter is used to limit the number of attach attempts. In other words, the attach attempt counter may be used to limit the number of times the attach procedure is performed. The attach attempt counter is incremented by 1 each time the registration procedure fails, unless it is set to 5, but may be reset in certain cases. The attach attempt counter is also reset when the UE is powered on, when the USIM is inserted, when the attach procedure is successfully completed, and so on.

Further, the UE receives the twelfth identification information via 3GPP access, the UE is operating in single registration mode, and in the tracking area update procedure in the EPS, the twelfth If rejected using the identification information, the UE uses EMM state, EPS update status, 4G-GUTI, tracking area updating attempt counter, etc. , may work. That is, the UE may operate using 4G parameters instead of 5G parameters. Here, the tracking area update attempt counter is used to limit the number of tracking area update attempts. In other words, the tracking area update attempt counter may be used to limit the number of times the tracking area update procedure is performed. The Tracking Area Update Attempt Counter is incremented by 1 each time the registration procedure fails, unless it is set to 5, but may be reset in certain cases. The Tracking Area Update Attempt Counter is also reset when the UE is powered on, when the USIM is inserted, when the Tracking Area Update procedure is successfully completed, and so on.

Also, if the UE has received the twelfth identification information and has disabled the N1 mode capability, the UE's lower layers will detect that the current E-UTRA cell is If it does not provide information that it is connected to an EPC, it may search for a suitable E-UTRA cell to connect to the EPC.

Also, if the UE has received the twelfth identification information and has disabled the N1 mode capability, the UE's lower layers will detect that the current E-UTRA cell is If it provides information that it is connected to an EPC, core network selection may be performed to select an EPC.

Also, when the UE receives the 12th identification information and disables the N1 mode capability, the UE's lower layers connect to the EPC E-UTRA If no cell can be found, it may indicate to the lower layer to continue camping on the E-UTRA cell connected to the 5GC, it may start a timer, or it may indicate 5GMM-REGISTERED.LIMITED-SERVICE. state may be transitioned. Here, 5GMM-REGISTERED.LIMITED-SERVICE may be a state in which the UE knows that the selected cell cannot provide normal service. The UE may then enable N1 mode capability for 3GPP access when the timer expires.

Further, when the UE receives the eleventh identification information including Allowed S-NSSAI, the use of the S-NSSAI is permitted, and / or registration with the network is permitted, and / or the UE request has been granted.

Also, if the UE receives the 11th identification information including the Allowed S-NSSAI and does not receive the 12th identification information and/or the 13th identification information, the use of the S-NSSAI is It may recognize that it has been granted and/or that it has been granted registration with the network and/or that the UE's request has been granted.

Also, even if the UE receives the 11th identification information including the Allowed S-NSSAI, if the 12th identification information and/or the 13th identification information is also received, the use of the S-NSSAI was not allowed (rejected) and/or registration with the network was not allowed (rejected) and/or the UE's request was not granted (rejected) You may

In addition, when the UE receives the 11th identification information including the Rejected S-NSSAI, the use of the S-NSSAI was not permitted (rejected) and/or registration with the network was not permitted. (rejected) and/or that the UE's request was not granted (rejected).

In addition, when the UE receives the 11th identification information including the Rejected S-NSSAI and also receives the 12th identification information and/or the 13th identification information, the use of the S-NSSAI is acknowledge that it was not granted (rejected) and/or that it was not allowed (rejected) to register with the network and/or that the UE's request was not granted (rejected); may

Further, when the UE receives the 13th identification information, the UE sets the backoff timer value indicated by the 13th identification information to the S-NSSAI indicated by the 11th identification information, which is the timer that the UE has. may be started by setting a timer to Then, the UE may not be able to transmit the MM message and/or SM message for the S-NSSAI indicated by the 11th identification information while the timer corresponding to the S-NSSAI is running. Then, when the timer corresponding to the S-NSSAI indicated by the eleventh identification information expires, the UE may transmit the MM message and/or SM message for that S-NSSAI. Even if the UE transmits an MM message and/or an SM message for an S-NSSAI other than the S-NSSAI, even if the timer corresponding to the S-NSSAI indicated by the eleventh identification information is in operation. good.

Also, the UE, based on having received the eleventh identification information and/or the twelfth identification information and/or the thirteenth identification information and/or the fourteenth identification information, E-UTRAN and/or Alternatively, it may decide to communicate via EPC and/or EPS, or to change the system from N1 mode to S1 mode, or to change from communication using 5G to communication using 4G. In this case, the UE may perform an attach procedure and/or a tracking area update procedure in the EPS.

In addition, the UE, in the EPS, even when performing the attach procedure and / or tracking area update procedure, may continue the operation of the timer corresponding to the S-NSSAI indicated by the eleventh identification information. , may be stopped. If the UE continues to operate the timer corresponding to the S-NSSAI indicated by the eleventh identification information, the UE, in 5GS, until the timer expires, MM message and / or SM for that S-NSSAI You may not be able to send messages. Then, if the timer expires, the UE may be able to send MM and/or SM messages for that S-NSSAI in 5GS. Also, when the UE stops the operation of the timer corresponding to the S-NSSAI indicated by the 11th identification information, the UE may be able to transmit the MM message and/or SM message for that S-NSSAI in 5GS. .

Also, the UE may start a timer for releasing the NAS signaling connection when receiving a registration rejection message containing the twelfth identity.

Further, when the control message is a registration acceptance message, the UE can transmit a registration completion message to the AMF via the base station apparatus as a response message to the registration acceptance message (S612). Here, the registration completion message is a NAS message transmitted/received over the N1 interface, but may be included in an RRC message and transmitted/received between the UE and the base station apparatus.

AMF receives the registration completion message via the base station device (S612). Also, each device completes this procedure based on transmission/reception of a registration acceptance message and/or a registration completion message.

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

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

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

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

[3.2. PDU session establishment procedure]
Next, a PDU session establishment procedure will be described using FIG. In this chapter, this PDU session establishment procedure may be simply referred to as this procedure.

Also, the UE may perform this procedure after performing the procedures in Section 3.1 and/or Section 3.2 one or more times. The UE may also perform this procedure while in a registered state with the network.

Also, the UE may decide whether to perform this procedure based on the messages and/or information obtained in the procedures of Sections 3.1 and/or 3.2. For example, in the procedure of section 3.1, if the UE receives a registration accept message, the UE may perform this procedure. Also, in the procedure of section 3.1, if the UE receives the eleventh identification information including allowed S-NSSAI, the UE may perform this procedure. Also, in the procedure of Chapter 3.1, when the UE receives the 13th identification information, until the timer corresponding to the S-NSSAI indicated by the 11th identification information received simultaneously with the 13th identification information shall not initiate this procedure for that S-NSSAI. Also, in the procedure of section 3.1, when the UE receives the 13th identification information, whether the timer corresponding to the S-NSSAI indicated by the 11th identification information received at the same time as the 13th identification information expires Regardless, the UE may initiate this procedure for S-NSSAIs other than its S-NSSAI.

First, the UE initiates the PDU session establishment procedure by sending (S800) a NAS message containing an N1 SM container containing a PDU session establishment request message to the AMF via the access network. A NAS message is, for example, a message sent over the N1 interface and may be an uplink NAS TRANSPORT (UL NAS TRANSPORT) message. Note that the UE may start a timer associated with retransmitting the PDU session establishment request message by sending the PDU session establishment request message.

Here, the access network is 3GPP access or non-3GPP access, and may include base station equipment. That is, the UE transmits a NAS message to AMF via the base station apparatus.

In addition, the UE includes at least one of the 21st to 26th identification information in the PDU session establishment request message and/or the N1 SM container and/or the NAS message, so that the UE requests This can be notified to the network side. Here, the 21st to 26th identification information may be as described in Chapter 2.6.

It should be noted that the UE determines whether or not to transmit any of the 21st to 26th identification information to the network, the UE capability information, and/or the UE policy, and/or the UE state, and/or the user's registration. It may be determined based on information and/or context held by the UE.

For example, when the UE receives the 11th identification information including allowed S-NSSAI in the procedure of Chapter 3.1, the 24th identification information includes the S-NSSAI indicated by the 11th identification information, You may send.

Here, no S-NSSAI may mean that the UE does not include the 24th identification information in the PDU session establishment request message and/or N1 SM container and/or NAS message.

Also, no DNN may mean that the UE does not include the twenty-fifth identification information in the PDU session establishment request message and/or N1 SM container and/or NAS message.

Note that the UE uses these identification information in control messages different from these, for example, in control messages of layers lower than the NAS layer (eg, RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.), It may be included in a control message of a layer higher than the NAS layer (for example, transport layer, session layer, presentation layer, application layer, etc.) and transmitted.

Then, when the AMF receives the NAS message, it is able to know what the UE is requesting and/or the content of the information (message, container, information) contained in the NAS message.

Here, the AMF may or may not perform the third condition determination. Also, the third condition determination may be for determining whether the network accepts the request of the UE. If the AMF determines that the third condition determination is true, it may start the procedures after S802 in FIG. good.

Note that the third condition determination may be performed by an NF other than the AMF. The NF may be, for example, NSACF. If an NF other than the AMF performs the third condition determination, the AMF provides that NF with information necessary to perform the third condition determination, specifically at least one of the information received from the UE. You can provide the part. Then, if the NF determines the truth or falseness of the third condition determination based on the information received from the AMF, the information including the result of the third condition determination (that is, whether it is true or false) is sent to the AMF. You can tell The AMF may determine identification information and/or control messages to be sent to the UE based on the result of the third condition determination received from the NF.

Note that the third condition determination is based on information received from the UE (message, container, information) and/or information received from the AMF (message, container, information), and/or subscriber information (subscription information). , and/or network capability information, and/or UE policy, and/or operator policy, and/or network state, and/or user registration information, and/or information held by AMF, and/or NSACF It may be executed based on retained information or the like.

For example, the third conditional decision may be determined to be true if the network grants the UE's request, and the third conditional determination may be determined to be false if the network does not grant the UE's request. In addition, if the network to which the UE is connected and/or the device in the network supports the function requested by the UE, the third condition determination may be determined to be true, and the function requested by the UE is supported. If not, the third conditional decision may be determined to be false. Further, when the transmitted and received identification information is permitted, the third condition determination may be determined to be true, and when the transmitted and received identification information is not permitted, the third condition determination may be determined to be false. Also, exceeding the maximum number of PDU sessions per NS, or reaching the maximum number of PDU sessions per NS, or exceeding the NS-related quota for the maximum number of PDU sessions, or congestion, or redirection to EPC Redirection to EPC required, or No network slices available, or Insufficient resources for specific slice and DNN , or due to reasons such as insufficient resources for specific NS (hereinafter referred to as refusal reason 2), if the PDU session establishment request is rejected, the third condition determination may be determined to be false. Also, if the PDU session establishment request is not rejected due to rejection reason 2, the third condition determination may be determined to be true.

Incidentally, the conditions for judging the truth of the third condition determination need not be limited to the conditions described above.

Also, when rejecting the PDU session establishment request due to refusal reason 2, the network (e.g., AMF and/or NSACF) indicates that the maximum number of PDU sessions per NS has been exceeded and/or the maximum number of PDU sessions per NS has been exceeded. reached and/or exceeded the NS-related quota on the maximum number of PDU sessions, and/or congested, and/or Redirection to EPC required, and/or No network slices available and/or Insufficient resources for specific NS and DNN and/or Insufficient resources for specific NS Insufficient resources for specific slice may be set in the 36th identification information. The network (eg, AMF and/or NSACF) may then send a control message containing the 31st, 34th to 38th identification information to the UE.

At this time, the network (eg, AMF and/or NSACF) may consider the S1 mode capability of the UE to decide to reject using the 36th identification.

Note that if the network (eg, AMF and/or NSACF) does not receive the 24th identification information, the control message may not include the 34th identification information or indicate no S-NSSAI. The 34th identification information may be included in the transmission.

Also, if the network (for example, AMF and/or NSACF) does not receive the 25th identification information, the control message may not include the 35th identification information, or may not include the 35th identification information indicating no DNN. may be transmitted including the identification information of

In addition, when the UE receives the control message including the 36th identification information indicating the 5GMM cause from the AMF, the UE indicates that the 5GSM message could not be transferred due to the information indicated by the 36th identification information. May notify the 5GSM sublayer. In this case, the UE may treat the maximum number of PDU sessions of the PLMN performing this procedure as the maximum number of PDU sessions per NS. The UE may also abort this procedure or stop the timer associated with retransmitting the PDU Session Establishment Request message that was started by sending the PDU Session Establishment Request message.

Next, if the third condition determination is not performed, or if the third condition determination is performed and determined to be true, the AMF receives information such as information (message, container , information) is selected (S802). In addition, AMF may include information such as (message, container, information) contained in the NAS message, and/or subscriber information, and/or network capability information, and/or UE policy, and/or operator policy, and/or The transfer destination SMF may be selected based on the network status and/or the user registration information and/or the context held by the AMF.

Next, the AMF transmits at least part of the information (message, container, information) included in the NAS message received from the UE to the selected SMF, for example, via the N11 interface (S804).

Next, when the SMF receives the information etc. (message, container, information) sent from the AMF, it determines that the UE is requesting and/or the content of the information etc. (message, container, information) received from the AMF. can be recognized.

Here, the SMF may make a second condition determination. Also, the second condition determination may be for determining whether the network accepts the request of the UE. The SMF may start the procedure of (A) in FIG. 7 if it determines that the second condition determination is true, and if it determines that the second condition determination is false, proceed to the procedure of (B) in FIG. you can start.

Note that the second condition determination may be executed by an NF other than the SMF. The NF may be, for example, NSACF. If an NF other than the SMF performs the second condition determination, the SMF provides that NF with information necessary to perform the second condition determination, specifically at least one of the information received from the UE. part may be provided (S806). Then, if the NF determines the truth of the second conditional judgment based on the information received from the SMF, it sends information containing the result of the second conditional judgment (that is, whether it is true or false) to the SMF. You can tell The SMF may determine identification information and/or control messages to be sent to the UE based on the result of the second condition determination received from that NF.

Note that the second condition determination is based on information received from the UE (message, container, information), and/or information received from the AMF (message, container, information), and/or subscriber information (subscription information). , and/or network capability information, and/or UE policy, and/or operator policy, and/or network state, and/or user registration information, and/or information held by SMF, and/or NSACF It may be executed based on retained information or the like.

For example, the second conditional decision may be determined to be true if the network grants the UE's request, and the second conditional determination may be determined to be false if the network does not grant the UE's request. In addition, if the network to which the UE is connected and/or the device in the network supports the function requested by the UE, the second condition determination may be determined to be true, and the function requested by the UE is supported. If not, the second conditional decision may be determined to be false. Further, the second condition determination may be determined to be true when the transmitted/received identification information is permitted, and the second condition determination may be determined to be false when the transmitted/received identification information is not permitted. Also, when rejecting the PDU session establishment request due to rejection reason 2, the second condition determination may be determined to be false. Also, if the PDU session establishment request is not rejected due to rejection reason 2, the second condition determination may be determined to be true.

Also, when rejecting the PDU session establishment request due to refusal reason 2, the network (e.g., SMF and/or NSACF) indicates that the maximum number of PDU sessions per NS has been exceeded and/or the maximum number of PDU sessions per NS has been exceeded. reached and/or exceeded the NS-related quota on the maximum number of PDU sessions, and/or congested, and/or Redirection to EPC required, and/or No network slices available and/or Insufficient resources for specific NS and DNN and/or Insufficient resources for specific NS Insufficient resources for specific slice may be set in the 36th identification information.

At this time, the network (eg, SMF and/or NSACF) may consider the S1 mode capability of the UE to decide to reject using the 36th identification.

Note that the condition for judging the truth of the second condition determination need not be limited to the condition described above.

Next, each step of the procedure of (A) in FIG. 7 will be described.

The SMF may then select a UPF for the PDU session to establish and send an N4 session establishment request message to the selected UPF, eg, via the N4 interface (S808). The N4 session establishment request message may include at least part of the PCC rules received from the PCF.

Here, SMF receives information such as information (message, container, information) from AMF, and/or information such as PCC rules received from PCF, and/or subscriber information, and/or network capability information, and/or Alternatively, one or more UPFs may be selected based on UE policy and/or operator policy and/or network conditions and/or user registration information and/or context held by SMF. Also, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that UPF_230 is selected.

Next, when the UPF receives the N4 session establishment request message (S808), it can recognize the content of the information received from the SMF. Also, upon receiving the N4 session establishment request message, the UPF may send an N4 session establishment response message to the SMF, eg, via the N4 interface (S810).

Next, when the SMF receives the N4 session establishment response message as a response message to the N4 session establishment request message, it can recognize the contents of the information received from the UPF.

The SMF then, upon receipt of the PDU Session Establishment Request message and/or selection of the UPF and/or reception of the N4 Session Establishment Response message, for example, via the N11 interface, the N1 SM container, and/or Send N2 SM information and/or PDU session ID to AMF (S812). Here, the N1 SM container may include a PDU session establishment accept message.

Next, the AMF that has received the N1 SM container and/or the N2 SM information and/or the PDU session ID transmits a NAS message to the UE via the base station device included in the access network (S814) (S816 ). Here, NAS messages are sent, for example, via the N1 interface. Also, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

Specifically, when the AMF transmits an N2 PDU session request message to a base station device included in the access network (S814), the base station device that received the N2 PDU session request message sends the UE: Send a NAS message (S816). Here, the N2 PDU session request message may include the NAS message and/or N2 SM information. The NAS message may also include the PDU session ID and/or the N1 SM container.

Also, the PDU session establishment accept message may be a response message to the PDU session establishment request. Also, the PDU session establishment accept message may indicate that the PDU session establishment has been accepted.

Here, the SMF and/or AMF is a PDU session establishment accept message, and/or an N1 SM container, and/or a PDU session ID, and/or a NAS message, and/or N2 SM information, and/or an N2 PDU session request. Sending the message may indicate that at least part of the UE's request in the PDU Session Establishment Request message has been accepted.

wherein the SMF and/or AMF and/or NSACF, in the PDU Session Establishment Accept message and/or the N1 SM Container and/or the NAS message and/or the N2 SM Information and/or the N2 PDU Session Request message, At least one of the 31st to 35th and 38th identification information may be included in the transmission. Here, the 31st to 35th and 38th identification information may be as described in Chapter 2.6.

In addition, since SMF and/or NSACF do not fall under reason 2 for refusal, if the request of the UE is permitted, or the establishment of a PDU session is permitted via the S-NSSAI included in the 24th identification information received from the UE. If so, the thirty-sixth identification information may not be included.

In addition, since SMF and/or NSACF do not fall under reason 2 for refusal, if the request of the UE is permitted, or the establishment of a PDU session is permitted via the S-NSSAI included in the 24th identification information received from the UE. If so, the thirty-seventh identification information may not include the backoff timer value.

The thirty-fourth identification information may be the same as the twenty-fourth identification information.

Note that if the network (for example, SMF and/or NSACF) does not receive the 24th identification information, the control message may not include the 34th identification information or indicate no S-NSSAI. The 34th identification information may be included in the transmission.

Also, if the network (for example, SMF and/or NSACF) does not receive the 25th identification information, the control message may not include the 35th identification information, or may not include the 35th identification information indicating no DNN. may be transmitted including the identification information of

In addition, SMF and / or AMF and / or NSACF, by sending these identification information and / or PDU session establishment acceptance message, may indicate that the network supports each function, UE of It may indicate that the request has been accepted, may indicate that the request from the UE is not permitted, or may indicate a combination of these information. Furthermore, when a plurality of identification information are transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

Also, the SMF and/or AMF and/or NSACF may include configured NSSAI and/or allowed NSSAI and/or rejected NSSAI and/or pending NSSAI in the PDU session establishment accept message. The 31st to 35th and 38th identification information may be transmitted as being included in these NSSAIs, or may be transmitted as information different from these NSSAIs.

The SMF and/or AMF and/or NSACF can notify the UE of the content of these identities by transmitting at least one of these identities.

Note that the SMF and/or AMF and/or NSACF may include any identification in the PDU Session Establishment Accept message, and/or the N1 SM Container, and/or the NAS message, and/or the N2 SM Information, and/or the N2 PDU Session Request message. Each received identity information, and/or subscriber information, and/or network capability information, and/or UE policy, and/or operator policy, and/or network state, and/or user and/or information held by the SMF, and/or information held by the AMF, and/or information held by the NSACF, and/or the like.

Next, when the UE receives the NAS message via, for example, the N1 interface (S816), it indicates that the UE's request by the PDU session establishment request message has been accepted and/or information included in the NAS message (message, container, information) can be recognized.

Next, each step of the procedure of (B) in FIG. 7 will be described.

First, based on the reception of the PDU session establishment request message, the SMF sends the N1 SM container and/or the PDU session ID to the AMF via, for example, the N11 interface (S818). Here, the N1 SM container may include a PDU Session Establishment Rejection message.

Next, the AMF that has received the N1 SM container and/or the PDU session ID transmits NAS messages to the UE via base station devices included in the access network (S820) (S822). Here, NAS messages are sent, for example, via the N1 interface. Also, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may also include the PDU session ID and/or the N1 SM container.

Also, the PDU session establishment rejection message may be a response message to the PDU session establishment request. Also, the PDU session establishment rejected message may indicate that the PDU session establishment has been rejected.

Here, the SMF and/or AMF and/or NSACF send a PDU Session Establishment Reject message and/or N1 SM container and/or PDU Session ID and/or NAS message to send a PDU Session Establishment Request message. may indicate that the UE's request by is rejected.

Here, SMF and/or AMF and/or NSACF include at least one of the 31st to 38th identification information in the PDU session establishment rejection message and/or N1 SM container and/or NAS message. You may send. Here, the 31st to 38th identification information may be as described in Chapter 2.6.

In addition, SMF and / or AMF and / or NSACF, by sending these identification information and / or PDU session establishment rejection message, may indicate that the network does not support each function, UE It may indicate that the request is rejected, it may indicate that the request from the UE is not permitted, or information combining these may be indicated. Furthermore, when a plurality of identification information are transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

In addition, when SMF and/or NSACF receives a PDU session establishment request message and rejects the PDU session establishment request due to refusal reason 2, the network (for example, SMF and/or NSACF) exceeding the maximum number of PDU sessions per NS and/or reaching the maximum number of PDU sessions per NS and/or exceeding the NS-related quota for the maximum number of PDU sessions and/or congestion; OR Redirection to EPC required and/or No network slices available and/or Insufficient resources for specific NS and DNN (Insufficient resources for specific slice and DNN) and/or insufficient resources for a specific NS (Insufficient resources for specific slice) may be set in the 36th identification information.

At this time, the network (eg, SMF and/or NSACF) may consider the S1 mode capability of the UE to decide to reject using the 36th identification.

In addition, since SMF and/or NSACF falls under reason 2 for refusal, if the UE request is not permitted (rejected), or the PDU session via S-NSSAI included in the 24th identification information received from the UE A thirty-sixth identification may be included when disallowing (rejecting) the establishment of the

In addition, since SMF and/or NSACF falls under reason 2 for refusal, if the UE request is not permitted (rejected), or the PDU session via S-NSSAI included in the 24th identification information received from the UE If the establishment of is not permitted (rejected), the thirty-seventh identification information may include a backoff timer value.

The thirty-fourth identification information may be the same as the twenty-fourth identification information.

Note that if the network (for example, SMF and/or NSACF) does not receive the 24th identification information, the control message may not include the 34th identification information or indicate no S-NSSAI. The 34th identification information may be included in the transmission.

Also, if the network (for example, SMF and/or NSACF) does not receive the 25th identification information, the control message may not include the 35th identification information, or may not include the 35th identification information indicating no DNN. may be transmitted including the identification information of

Also, the SMF and/or NSACF may send configured NSSAI and/or allowed NSSAI and/or rejected NSSAI and/or pending NSSAI in the PDU session establishment accept message. The 31st to 38th identification information may be transmitted while being included in these NSSAIs, or may be transmitted as information different from these NSSAIs.

The SMF and/or AMF and/or NSACF can notify the UE of the content of these identities by transmitting at least one of these identities.

It should be noted that the SMF and/or AMF and/or NSACF may include any identification in the PDU Session Establishment Reject message, and/or the N1 SM Container, and/or the NAS message, and/or the N2 SM Information, and/or the N2 PDU Session Request message. Each received identity information, and/or subscriber information, and/or network capability information, and/or UE policy, and/or operator policy, and/or network state, and/or user and/or information held by the SMF, and/or information held by the AMF, and/or information held by the NSACF, and/or the like.

Next, when the UE receives the NAS message via, for example, the N1 interface (S822), the UE's request by the PDU session establishment request message is rejected and/or information included in the NAS message (message, container, information) can be recognized.

Also, when the UE receives the thirty-sixth identification information via non-3GPP access, it may be regarded as an abnormal case. Also, the UE may regard the case where the 36th identification information is received via a cell belonging to the SNPN as an abnormal case.

The UE may also set the 5GS update status (also referred to as 5U status) in the UE to 5U3 ROAMING NOT ALLOWED when the 36th identification is received.

Also, when the UE receives the thirty-sixth identification information, the UE may delete all 5G-GUTIs, previously registered TAIs, TAI lists, and the like. Additionally, the UE may reset a registration attempt counter.

In addition, when the UE receives the 36th identification information, if the E-UTRA capability is disabled, the UE may enable the E-UTRA capability. may disable the N1 mode capability for 3GPP access, or transition to the 5GMM-DERIGISTERED.NO-CELL-AVAILABLE state.

Also, the UE receives the 36th identification information via 3GPP access, the UE is operating in a single registration mode, and the 36th identification information is received in the attach procedure in the EPS. If rejected using, the UE may act with EMM state, EPS update status, 4G-GUTI, attach attempt counter, etc. That is, the UE may operate using 4G parameters instead of 5G parameters.

Further, the UE receives the 36th identification information via 3GPP access, the UE is operating in a single registration mode, and in the tracking area update procedure in the EPS, the 36th If rejected using the identification information, the UE uses EMM state, EPS update status, 4G-GUTI, tracking area updating attempt counter, etc. , may work. That is, the UE may operate using 4G parameters instead of 5G parameters.

Also, if the UE receives the 36th identification information and disables the N1 mode capability, the UE's lower layers will detect that the current E-UTRA cell is If it does not provide information that it is connected to an EPC, it may search for a suitable E-UTRA cell to connect to the EPC.

Also, if the UE receives the 36th identification information and disables the N1 mode capability, the UE's lower layers will detect that the current E-UTRA cell is If it provides information that it is connected to an EPC, core network selection may be performed to select an EPC.

Also, when the UE receives the 36th identification information and disables the N1 mode capability, the UE's lower layers connect to the EPC E-UTRA If no cell can be found, it may indicate to the lower layer to continue camping on the E-UTRA cell connected to the 5GC, it may start a timer, or it may indicate 5GMM-REGISTERED.LIMITED-SERVICE. state may be transitioned.

Also, when the UE receives the 34th identification information and/or the 36th identification information and/or the 37th identification information, the UE is not permitted to use the S-NSSAI indicated by the 34th identification information. and/or that the PDU session establishment was disallowed (rejected) and/or the UE's request was disallowed (rejected). .

Also, when the UE receives the 34th identification information and/or the 36th identification information and/or the 37th identification information, the UE is not permitted to use the S-NSSAI indicated by the 34th identification information. (rejected), and/or why the PDU session establishment was not allowed (rejected), and/or why the UE's request was not allowed (rejected), shall be specified in the thirty-sixth identification. You may recognize that it is based on the information presented in the information.

Further, when the UE receives the 34th identification information, and/or the 36th identification information, and/or the 37th identification information, the UE has a backoff timer value indicated by the 37th identification information. A timer corresponding to the S-NSSAI indicated by the thirty-fourth identification information may be set and started. Then, while the timer corresponding to the S-NSSAI indicated by the 34th identification information is running, the UE may not be able to transmit the MM message and/or SM message for that S-NSSAI. Then, when the timer corresponding to the S-NSSAI indicated by the 34th identification information expires, the UE may transmit the MM message and/or SM message for that S-NSSAI. Even if the UE transmits an MM message and/or an SM message for an S-NSSAI other than the S-NSSAI, even if the timer corresponding to the S-NSSAI indicated by the 34th identification information is in operation. good.

Also, the UE, based on having received the 34th identification information and/or the 36th identification information and/or the 37th identification information and/or the 38th identification information, E-UTRAN and/or Alternatively, it may decide to communicate via EPC and/or EPS, or to change the system from N1 mode to S1 mode, or to change from communication using 5G to communication using 4G. In this case, the UE may perform an attach procedure and/or a tracking area update procedure in the EPS.

In addition, the UE, in the EPS, even when performing the attach procedure and / or tracking area update procedure, may continue the operation of the timer corresponding to the S-NSSAI indicated by the 34th identification information , may be stopped. If the UE continues to operate the timer corresponding to the S-NSSAI indicated by the 34th identification information, the UE, in 5GS, until the timer expires, MM message and / or SM for that S-NSSAI You may not be able to send messages. Then, if the timer expires, the UE may be able to send MM and/or SM messages for that S-NSSAI in 5GS. Also, if the UE stops the operation of the timer corresponding to the S-NSSAI indicated by the 34th identification information, the UE may be able to transmit an MM message and/or an SM message for that S-NSSAI in 5GS. .

The UE may also start a timer for releasing the NAS signaling connection when receiving a registration rejection message containing the thirty-sixth identification.

In addition, when the UE does not receive the 34th identification information or receives the 34th identification information indicating no S-NSSAI, the UE recognizes that the above operation is for no S-NSSAI. you can

Also, when the UE does not receive the 35th identification information or receives the 35th identification information indicating no DNN, the UE may recognize that the above operation is for no DNN.

Each device may complete this procedure based on sending and receiving PDU session establishment accept messages. At this time, each device may transition to a state where it can communicate with the DN using the established PDU session.

Each device may complete this procedure based on sending and receiving a PDU Session Establishment Accept message or a PDU Session Establishment Reject message. At this time, since each device cannot establish a PDU session, it cannot communicate with the DN unless there is already an established PDU session.

Each process executed by the UE based on the reception of each identification information described above may be executed during this procedure, after completion of this procedure, or after completion of this procedure, even if it is executed based on the completion of this procedure. good.

Each device may complete this procedure based on sending and receiving PDU session establishment accept messages. At this time, each device may transition to a state where it can communicate with the DN using the newly established PDU session.

Each device may complete this procedure based on sending and receiving PDU Session Establishment Reject messages. At this time, since each device cannot establish a new PDU session, it cannot communicate with the DN if there is no already established PDU session.

Each process executed by the UE based on the reception of each identification information described above may be executed during this procedure, after completion of this procedure, or after completion of this procedure, even if it is executed based on the completion of this procedure. good.

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

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

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

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

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are included within the scope of the present invention. In addition, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of the present invention. be Moreover, it is an element described in each said embodiment, and the structure which replaced the element with which the same effect is produced is also included.

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

Claims (1)

A UE (User Equipment) comprising a transmitting/receiving unit and a control unit,
The transmitting/receiving unit receives from the base station apparatus a registration acceptance message or a registration rejection message including a reason value indicating that the maximum number of UEs per network slice has been exceeded;
The control unit
If the E-UTRA capability is disabled, enable the E-UTRA capability,
Disable N1 mode capability for 3GPP access,
transition to the 5GMM-DEREGISTERED.NO-CELL-AVAILABLE state,
A UE characterized by:

Images