WO2020145305A1

WO2020145305A1 - Ue and smf

Info

Publication number: WO2020145305A1
Application number: PCT/JP2020/000312
Authority: WO
Inventors: 強高倉
Original assignee: シャープ株式会社; 鴻穎創新有限公司
Priority date: 2019-01-10
Filing date: 2020-01-08
Publication date: 2020-07-16
Also published as: JP2020113883A

Abstract

The present invention provides a communication control method pertaining to control signal management based on reasons for refusal pertaining to a DN authentication procedure. The transmission of a new PDU session establishment message that uses the same parameter as the DNN included in a PDU session establishment message having been refused on the basis of a reason for refusal that indicates DN authentication failure other than EAP failure is suppressed. The transmission of a new PDU session establishment message that uses the same information as the combination of the DNN and an S-NSSAI included in the refused PDU session establishment message is suppressed.

Description

UE and SMF

The present invention relates to a UE (User Equipment; terminal device) and an SMF (Session Management Function). The present application claims priority based on Japanese Patent Application No. 2019-2868 filed in Japan on January 10, 2019, the contents of which are incorporated herein by reference.

3GPP (3rd Generation Partnership Project), which conducts standardization activities for mobile communication systems in recent years, is examining SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution). 3GPP specifies EPS (Evolved Packet System) as a communication system that realizes all-IP (Internet Protocol). The core network that constitutes EPS is called EPC (Evolved Packet Core).

In recent years, 3GPP is also studying the next-generation communication technology and system architecture of the 5G (5th Generation) mobile communication system, which is the next-generation mobile communication system. 5G System) is being specified (see Non-Patent Document 1 and Non-Patent Document 2). 5GS extracts the technical issues for connecting a wide variety of terminals to the cellular network and specifies solutions.

For example, optimization and diversification of communication procedures for supporting continuous mobile communication services according to terminals supporting a wide variety of access networks, and system architecture matching the optimization and diversification of communication procedures Optimization and the like are also listed as requirements.

In 5GS, control signal management based on reasons other than congestion management is being studied in addition to a mechanism that provides a function equivalent to congestion management (Non-Patent Documents 1 and 2 and Non-Patent Documents). 3).

However, the operation process related to session management of the terminal that the network has received the reason to notify the terminal to apply the control signal management based on the reason other than the congestion management is not clear. In particular, the control signal management process is not clarified when the PDU session establishment request for invoking the DN authentication procedure is rejected for reasons other than the authentication procedure.

One aspect of the present invention is made in view of such circumstances, and an object thereof is to provide a mechanism and a communication control method for realizing a control signal management process based on a reason other than congestion management. is there.

UE (User Equipment; terminal device) of the present invention includes a transmission unit, the first PDU (Protocol Data Unit or Packet Data Unit) session establishment request message, the first user identifier and the first DNN (Data Network) Name) is a PDU session establishment request message, the transmission unit, for the first PDU session establishment request message, EAP (Extensible Authentication Protocol)-failure including a rejection reason value indicating userauthentication or authorization failed When a PDU session establishment rejection message that does not include rejection reason information that indicates the message is received, the terminal power is turned on/off, or the USIM (Universal Subscriber Identity Module) is removed/inserted until the user ID is changed to a user ID different from the first user ID. Up to the above, the transmission of the second PDU session establishment request message using the user identifier for the first DNN is regulated.

UE of the present invention comprises a transmission unit, the first PDU session establishment request is a PDU session establishment request using the first user identifier and the first DNN and the first S-NSSAI, the transmission unit In response to the first PDU session establishment request, when a causevalue indicating the reason value of rejection indicating user authentication or authorization failed is received, until changing to a user identifier different from the first user identifier, or the terminal Until the power is turned on/off or the USIM (Universal Subscriber Identity Module) is removed/inserted, the second DPDU session establishment request using the user identifier is not made to the first DNN and the first S-NSSAI. Characterize.

According to one aspect of the present invention, the terminal device constituting the 5GS, and the device in the core network, each network slice and / or DNN or APN by the terminal device initiative or network initiative, especially except congestion management related to the DN authentication procedure. The control management process of can be implemented.

It is a figure which shows the outline of a mobile communication system. FIG. 1 is a diagram showing an example of a configuration of an access network in a mobile communication system. FIG. 1 is a diagram showing an example of a configuration of a core network in a mobile communication system. It is a figure which shows the apparatus structure of UE. It is a figure which shows the apparatus structure of eNB/NR node/WAG. It is a figure which shows the apparatus structure of AMF. It is a figure which shows the apparatus structure of SMF/UPF. It is a figure which shows an initial procedure. It is a figure which shows a registration procedure. It is a figure which shows the PDU session establishment procedure. It is a figure which shows the PDU session establishment authentication approval procedure. It is a figure which shows the RQoS activation procedure.

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

[1. System overview]
An outline of the mobile communication system in this embodiment will be described with reference to FIGS. 1, 2, and 3. FIG. 2 is a diagram showing details of an access network in the mobile communication system of FIG. FIG. 3 is a diagram mainly showing details of a core network in the mobile communication system of FIG. As shown in FIG. 1, the mobile communication system 1 (also referred to as 5GS) in the present embodiment is a terminal device (also referred to as a user device or a mobile terminal device) UE (User Equipment)_A10, an access network (AN; Access Network)_B. , A core network (CN; Core Network)_B190, and a data network (DN; Data Network)_A5, DN_B105.

Here, UE_A10 can connect to the network service via 3GPP access (also called 3GPP access or 3GPP access network) and/or non-3GPP access (also called non-3GPP access or non-3GPP access network). Any device. Also, the UE_A10 may include a UICC (Universal Integrated Circuit Card) and an eUICC (Embedded UICC). Further, UE_A10 may be a wirelessly connectable terminal device, ME (Mobile Equipment), MS (Mobile Station), CIoT (Cellular Internet of Things) terminal (CIoT UE), or the like.

UE_A10 can also connect to the access network and/or the core network. UE_A10 can also connect to DN_A5 via the access network and/or the core network. UE_A10 transmits/receives (communicates) user data with DN_A5 using a PDU (Protocol Data Unit or Packet Data Unit) session. Furthermore, communication of user data is not limited to IP (Internet Protocol) communication, and may be non-IP communication.

Here, IP communication is data communication using IP, and is data communication realized by transmitting and receiving IP packets to which an IP header is added. Note that the payload portion forming the IP packet may include user data transmitted/received by the UE_A 10. In addition, non-IP communication is data communication that does not use IP, and is data communication that is realized by transmitting and receiving data that does not have an IP header. For example, the non-IP communication may be data communication realized by transmitting and receiving application data to which an IP packet is not added, or UE_A10 by adding another header such as a MAC header or an Ethernet (registered trademark) frame header. User data to be transmitted/received may be transmitted/received.

Also, a PDU session is the connectivity established between UE_A10 and DN_A5 and/or DN_B105 to provide a PDU connection service. More specifically, the PDU session may be the connectivity established between UE_A10 and the external gateway. Here, the external gateway may be UPF, PGW (Packet Data Network Gateway), or the like. Also, the PDU session may be a communication path established for transmitting/receiving user data between the UE_A10 and the core network and/or DN (DN_A5 and/or DN_B105), or a communication path for transmitting/receiving PDU. Good. Furthermore, the PDU session may be a session established between UE_A10 and the core network and/or DN (DN_A5 and/or DN_B105), and transfer of one or more bearers or the like between each device in the mobile communication system 1. It may be a logical communication path configured by a path. More specifically, the PDU session may be a connection that UE_A10 establishes between the core network_B190 and/or an external gateway, and a connection established between UE_A10 and UPF (UPF_A235 and/or UPF_B237). But it's okay. Further, the PDU session may be connectivity and/or connection between the UE_A10 and the UPF (UPF_A235 and/or UPF_B237) via the NR node_A122. Further, the PDU session may be identified by the PDU session ID and/or the EPS bearer ID.

Note that UE_A10 can execute transmission/reception of user data using a PDU session with a device such as an application server arranged in DN_A5 and/or DN_B105. In other words, the PDU session can transfer user data transmitted and received between the UE_A10 and a device such as an application server arranged in the DN_A5 and/or DN_B105. Furthermore, each device (UE_A10, a device in the access network, and / or a device in the core network, and / or a device in the data network), in association with the PDU session, manages one or more pieces of identification information. May be. These identification information include APN (Access Point Name), TFT (Traffic Flow Template), session type, application identification information, DN_A5 and/or DN_B105 identification information, NSI (Network Slice Instance) identification information, and DCN. At least one of (Dedicated Core Network) identification information and access network identification information may be included, and other information may be further included. Further, when a plurality of PDU sessions are established, each piece of identification information associated with the PDU session may have the same content or different content. Furthermore, the NSI identification information is information that identifies the NSI, and may be the NSI ID or Slice Instance ID below.

The access network_B may be any of E-UTRAN (Evolved Universal Terrestrial Radio Access Network)_A80, 5G-RAN_A120, and WLAN ANc125, as shown in FIG. The E-UTRAN_A80 and/or 5G-RAN_A120 may be called a 3GPP access network, and the WLAN ANc125 may be called a non-3GPP access network. Each radio access network includes a device to which the UE_A 10 is actually connected (for example, a base station device or an access point) and the like.

For example, E-UTRAN_A80 is an LTE access network and is configured to include one or more eNB_A45. The eNB_A45 is a wireless base station to which the UE_A10 connects by E-UTRA (Evolved Universal Terrestrial Radio Access). Moreover, when there are a plurality of eNBs in the E-UTRAN_A80, each eNB may be connected to each other.

5G-RAN_A120 is a 5G access network, and is configured to include one or more NR node (New Radio Access Technology node)_A122. NR node_A122 is a wireless base station to which UE_A10 connects in 5G wireless access (5G Radio Access). Also, when there are multiple NR node_A 122 in 5G-RAN_A 120, each NR node_A 122 may be connected to each other.

Note that 5G-RAN_A120 may be an access network composed of E-UTRA and/or 5G RadioAccess. In other words, 5G-RAN_A120 may include eNB_A45, NR node_A122, or both. In this case, the eNB_A45 and the NR node_A122 may be the same device. Therefore, NR node_A122 can be replaced with eNB_A45.

WLAN ANc125 is a wireless LAN access network and is configured to include one or more WAG (WLAN Access Gateway)_A126. WAG_A126 is a wireless base station to which UE_A10 connects by wireless LAN access. Further, WAG_A126 may be a gateway for core network_B190 and WLAN ANc125. Further, in WAG_A126, the functional unit of the wireless base station and the functional unit of the gateway may be configured as separate devices.

In this specification, UE_A10 being connected to each radio access network means being connected to a base station device, an access point, etc. included in each radio access network, and data and signals to be transmitted and received. Also means that it goes through a base station device and an access point. The control message transmitted/received between UE_A10 and core network_B190 may be the same control message regardless of the type of access network. Therefore, UE_A10 and core network _B190 to send and receive messages via NR node_A122 is the same as UE_A10 and core network _B190 eNB_A45, and / or the same as sending a message via WAG_A126. Good.

Furthermore, the access network is a wireless network connected to UE_A10 and/or the core network. The access network may be a 3GPP access network or a non-3GPP access network. The 3GPP access network may be E-UTRAN_A80, 5G-RAN (Radio Access Network)_A120, and the non-3GPP access network may be WLAN ANc125. The UE_A10 may be connected to the access network in order to connect to the core network, or may be connected to the core network via the access network.

Also, DN_A5 and DN_B105 are data networks that provide communication services to UE_A10, and may be configured as a packet data service network or may be configured for each service. Further, DN_A5 and DN_B105 may include connected communication terminals. Therefore, connecting with DN_A5 and/or DN_B105 may be connecting with a communication terminal or server device arranged in DN_A5 and/or DN_B105. Furthermore, transmitting/receiving user data to/from DN_A5 and/or DN_B105 may be transmitting/receiving user data to/from a communication terminal or server device arranged in DN_A5 and/or DN_B105. Further, DN_A5 and/or DN_B105 are outside the core network in FIG. 1, but may be inside the core network.

Also, the core network_B 190 may be configured as a device in one or more core networks. Here, the device in the core network may be a device that executes some or all of the processes or functions of each device included in the core network_B 190. The device in the core network may be referred to as a core network device.

Furthermore, the core network is an IP mobile communication network operated by a mobile communication operator (MNO; Mobile Network Operator) connected to the access network and/or DN_A5. The core network may be a core network for a mobile communication operator that operates and manages the mobile communication system 1, or a virtual mobile communication operator or a virtual mobile communication operator such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler). It may be a core network for mobile communication service providers. The core network_B 190 may be an EPC (Evolved Packet Core) that constitutes an EPS (Evolved Packet System) or a 5GC (5G Core Network) that constitutes a 5GS. Furthermore, the core network_B 190 may be a core network of a system that provides 5G communication services. The core network_B 190 is not limited to this, and may be a network for providing mobile communication services.

Next, the core network_B190 will be explained. Core network_B190 includes AUSF (Authentication Server Function), AMF (Access and Mobility Management Function)_A240, SDSF (Structured Data Storage network function), UDSF (Unstructured Data Storage network function), NEF (Network Exposure Function), NRF (NF Repository Function), PCF (Policy Control Function), SMF (Session Management Function)_A230, SMF (Session Management Function)_B232, UDM (Unified Data Management), UPF (User Plane Function)_A235, UPF (User Plane Function) _B237, AF (Application Function), N3IWF (Non-3GPP InterWorking Function), at least one may be included. Then, these may be configured as an NF (Network Function). The NF may refer to a processing function configured in the network.

For the sake of simplification, FIG. 3 shows only AMF (AMF_A240), SMF (SMF_A230 and SMF_B232), and UPF (UPF_A235 and UPF_B237) among them, but the others (device and// Or NF) is not included. For simplification, UE_A10 is also referred to as UE, AMF_A240 is referred to as AMF, SMF_A230 and SMF_B232 are referred to as SMF, UPF_A235 and UPF_B237 are referred to as UPF, and DN_A5 and DN_B105 are also referred to as DN.

Also, in FIG. 3, an N1 interface (hereinafter also referred to as a reference point), an N2 interface, an N3 interface, an N4 interface, an N6 interface, an N9 interface, and an N11 interface are described. Here, the N1 interface is an interface between the UE and AMF, the N2 interface is an interface between (R)AN (access network) and AMF, and the N3 interface is (R)AN (access network). Interface between UPF, N4 interface between SMF and UPF, N6 interface between UPF and DN, N9 interface between UPF and UPF , N11 interface is the interface between AMF and SMF. Using these interfaces, communication can be performed between each device.

Note that FIG. 3 is a system configuration diagram when the UE simultaneously accesses two DNs using a plurality of PDU sessions. Two SMFs have been selected for two different PDU sessions. Also, in FIG. 3, there are two SMF_A230s and two UPF_A235s.

The following is a brief description of each device included in Core Network_B190.

First, AMF_A240 is connected to other AMF, SMF (SMF_A230 and/or SMF_B232), access network (that is, E-UTRAN_A80 and 5G-RAN_A120 and WLANANc125), UDM, AUSF, and PCF. AMF_A240 is the registration management (Registration management), connection management (Connection management), reachability management (Reachability management), mobility management (Mobility management) such as UE_A10, SM (Session Management) message transfer between UE and SMF. , Access Authentication (Access Authentication, Access Authorization), Security Anchor Function (SEA; Security Anchor Function), Security Context Management (SCM; Security Context Management), N2 interface support for N3IWF, NAS signal with UE via N3IWF It may play roles such as support of transmission/reception, authentication of UE connecting via N3IWF, management of RM states (Registration Management states), management of CM states (Connection Management states). Further, one or more AMF_A240 may be arranged in the core network_B190. AMF_A240 may be an NF that manages one or more NSI (Network Slice Instance). The AMF_A240 may be a shared CP function (CCNF; Control Plane Network Function) that is shared between multiple NSIs.

RM also has a non-registration state (RM-DEREGISTERED state) and a registration state (RM-REGISTERED state). In the RM-DEREGISTERED state, since the UE is not registered in the network, the UE context in AMF does not have valid location information or routing information for that UE, so AMF cannot reach the UE. is there. Further, in the RM-REGISTERED state, since the UE is registered in the network, the UE can receive a service that requires registration with the network.

Also, as the CM state, there are a non-connection state (CM-IDLE state) and a connection state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have the N2 interface connection (N2 connection) and the N3 interface connection (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. Further, in the CM-CONNECTED state, the UE may have an N2 interface connection (N2 connection) and/or an N3 interface connection (N3 connection).

Also, SMF_A230 is connected to AMF_A240, UPF_A235, UDM, and PCF. SMF_B232 is connected to AMF_A240, UPF_B237, UDM, and PCF. SMF_A230 and SMF_B232 are session management such as PDU session (Session Management), IP address allocation (IP address allocation) for UE, UPF selection and control, UPF setting for routing traffic to an appropriate destination, downlink Function to notify the arrival of data (Downlink Data Notification), AN specific SM information identifier (for each AN) sent via AN2 to AN via AMF, SSC mode for session It may play a role of determining (Session and Service Continuity mode) and roaming function. Further, although SMF_A230 and SMF_B232 are described as separate devices or NFs, they may be the same device or function.

UPF_A235 is also connected to DN_A5, SMF_A230, other UPFs, and access networks (that is, E-UTRAN_A80 and 5G-RAN_A120 and WLANANc125). UPF_B237 is connected to DN_B105, SMF_B232, another UPF, and an access network (that is, E-UTRAN_A80, 5G-RAN_A120, and WLANANc125). UPF_A235 and UPF_B237 are UL-CL (Uplink Classifier) that supports anchor for intra-RAT mobility or inter-RAT mobility, packet routing & forwarding, and routing of multiple traffic flows for one DN. Function, Branching point function that supports multi-homed PDU session, QoS processing for user plane, verification of uplink traffic (verification), buffering of downlink packet, downlink data notification (Downlink Data Notification) ), the trigger function, etc. may be taken. Further, UPF_A235 and UPF_B237 may be relay devices that transfer user data as a gateway between DN_A5 and core network_B190 and a gateway between DN_B105 and core network_B190, respectively. Note that UPF_A235 and UPF_B237 may be gateways for IP communication and/or non-IP communication. Further, UPF_A235 and UPF_B237 may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication. Further, a plurality of gateways may be gateways connecting the core network_B 190 and a single DN. The UPF_A235 and UPF_B237 may have connectivity with another NF, or may be connected to each device via the other NF.

Note that UPF_A235 and UPF_B237 are described as separate devices or NFs, but between UPF_A235 and the access network, and between UPF_B237 and the access network, UPF_A235 and UPF_B237 are different UPF, and common UPF_C239. (also called branching point or uplink classifier) may exist. If UPF_C239 is present, a PDU session between UE_A10 and DN_A5 is established via the access network, UPF_C239, UPF_A235, and a PDU session between UE_A10 and DN_B105 is established via the access network, UPF_C239, UPF_B237. Will be done.

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

Also, AUSF is connected to UDM and AMF_A240. AUSF functions as an authentication server.

SDSF provides functions for NEF to save and acquire information as structured data.

UDSF provides a function for all NFs to store and retrieve information as unstructured data.

NEF provides a means to securely provide the services and capabilities provided by the 3GPP network. Save information received from other NFs as structured data.

Upon receiving an NF Discovery Request from an NF instance, the NRF provides the NF with information about the discovered NF instance, information on available NF instances, and information about the services supported by that instance. To hold.

PCF is connected to SMF (SMF_A230, SMF_B232), AF, AMF_A240. Provide policy rules etc.

UDM is connected to AMF_A240, SMF (SMF_A230, SMF_B232), AUSF, and PCF. UDM includes UDM (FE front) and UDR (User Data Repository). UDMFE performs processing such as authentication information (credentials), location management (location management), and subscriber management (subscription management). UDR saves the data necessary for UDMFE to provide and the policy profiles required by PCF.

▽AF is connected to PCF. The AF influences traffic routing and participates in policy control.

N3IWF establishes an IPsec tunnel with UE, relays NAS (N1) signaling between UE and AMF, processes N2 signaling transmitted from SMF and relayed by AMF, and establishes IPsec Security Association (IPsec SA). It provides functions such as relaying user plane packets between UE and UPF, and AMF selection.

[1.2. Configuration of each device]
The configuration of each device will be described below. It should be noted that some or all of the functions of each device and each unit of each device described below may operate on physical hardware, or may be a logical hardware virtually configured on general-purpose hardware. It may be one that operates on wear.

[1.2.1. UE configuration]
First, a device configuration example of UE_A10 is shown in FIG. As shown in FIG. 4, UE_A10 includes a control unit_A400, a transmission/reception unit_A420, and a storage unit_A440. The transmission/reception unit_A420 and the storage unit_A440 are connected to the control unit_A400 via a bus. An external antenna 410 is connected to the transmitter/receiver_A 420. Further, the storage unit_A 440 stores the UE context 442.

The control unit_A400 is a functional unit for controlling the entire UE_A10, and realizes various processes of the entire UE_A10 by reading and executing various information and programs stored in the storage unit_A440.

The transceiver_A420 is a functional unit for the UE_A10 to connect to the base stations (E-UTRAN_A80 and 5G-RAN_A120) and/or the access point (WLANANc125) in the access network and to connect to the access network. In other words, the UE_A10 can connect to the base station and/or the access point in the access network via the external antenna 410 connected to the transceiver_A420. Specifically, UE_A10, via the external antenna 410 connected to the transceiver unit_A420, between the base station and / or access point in the access network, to transmit and receive user data and / or control information. You can

The storage unit_A440 is a functional unit that stores programs and data necessary for each operation of the UE_A10, and is configured by, for example, semiconductor memory, HDD (Hard Disk Drive), SSD (Solid State Drive), and the like. The storage unit_A440 stores identification information, control information, flags, parameters and the like included in control messages transmitted and received in a communication procedure described later. As the UE context 442 stored in the storage unit_A440, there may be a UE context used when connecting to the access network_B80/120/125 and a UE context used when connecting to the core network_B190. .. Also, the UE context 442 may include a UE context stored for each UE, a UE context stored for each PDU session, and a UE context stored for each bearer. The UE context stored for each UE may include IMSI, EMMState, GUTI, and MEIdentity. In addition, the UE context stored for each PDU session may include APN in Use, Assigned Session Type, IP Address(es), and Default Bearer. The UE context stored for each bearer may include EPS Bearer ID, TI, and TFT.

[1.2.2. eNB/NR node/WAG configuration]
Next, FIG. 5 shows a device configuration example of the eNB_A45, NR node_A122, and WAG_A126. As shown in FIG. 5, the eNB_A45, NR node_A122, and WAG_A126 are composed of a control unit_B500, a network connection unit_B520, a transmission/reception unit_B530, and a storage unit_B540. The network connection unit_B520, the transmission/reception unit_B530, and the storage unit_B540 are connected to the control unit_B500 via a bus. An external antenna 510 is connected to the transceiver_B530.

The control unit_B500 is a functional unit for controlling the entire eNB_A45, NR node_A122 and WAG_A126, and by reading out and executing various information and programs stored in the storage unit_B540, the eNB_A45, NR node_A122 , And various processes of the entire WAG_A126 are realized.

The network connection part_B520 is a function part for the eNB_A45, NR node_A122 and WAG_A126 to connect with the AMF_A240 and UPF_A235 in the core network. In other words, the eNB_A45, NR node_A122 and WAG_A126 can be connected to the AMF_A240 and UPF_A235 in the core network via the network connection unit_B520. Specifically, the eNB_A45, NR node_A122, and WAG_A126 can transmit/receive user data and/or control information to/from the AMF_A240 and/or UPF_A235 via the network connection unit_B520.

・Transceiver_B530 is a functional unit for connecting eNB_A45, NR node_A122 and WAG_A126 with UE_A10. In other words, the eNB_A45, NR node_A122, and WAG_A126 can transmit/receive user data and/or control information to/from the UE_A10 via the transmitting/receiving unit_B530.

The storage unit_B540 is a functional unit that stores programs and data necessary for each operation of the eNB_A45, NR node_A122, and WAG_A126. The storage unit_B 540 includes, for example, a semiconductor memory, an HDD, an SSD, or the like. The storage unit_B 540 stores identification information, control information, flags, parameters and the like included in control messages transmitted and received in a communication procedure described later. The storage unit_B540 may store these pieces of information as contexts for each UE_A10.

[1.2.3. AMF configuration]
Next, FIG. 6 shows a device configuration example of the AMF_A240. As shown in FIG. 6, the AMF_A240 includes a control unit_C600, a network connection unit_C620, and a storage unit_C640. The network connection unit_C620 and the storage unit_C640 are connected to the control unit_C600 via a bus. Further, the storage unit_C 640 stores the context 642.

The control unit_C600 is a functional unit for controlling the entire AMF_A240, and realizes various processes of the entire AMF_A240 by reading and executing various information and programs stored in the storage unit_C640.

Network connection unit_C620 is for AMF_A240 to connect with other AMF_240, SMF_A230, base stations (E-UTRAN_A80 and 5G-RAN_A120) and/or access point (WLANANc125), UDM, AUSF, PCF in the access network. Is a functional part of. In other words, the AMF_A240 can send and receive user data and/or control information to/from the base station and/or access point in the access network, UDM, AUSF, PCF via the network connection unit_C620. ..

The storage unit_C640 is a functional unit that stores programs and data necessary for each operation of the AMF_A240. The storage unit_C 640 includes, for example, a semiconductor memory, HDD, SSD, or the like. The storage unit_C 640 stores identification information, control information, flags, parameters and the like included in control messages transmitted and received in a communication procedure described later. The context 642 stored in the storage unit_C 640 may be a context stored for each UE, a context stored for each PDU session, or a context stored for each bearer. Contexts stored for each UE include IMSI, MSISDN, MM State, GUTI, MEIdentity, UERadioAccessCapability, UENetworkCapability, MSNetworkCapability, Access Restriction, MMEF-TEID, SGW F-TEID, eNB Address. , MMEUES1APID, eNBUES1APID, NRnodeAddress, NRnodeID, WAGAddress, WAGID. The context stored for each PDU session may include APNinUse, AssignedSessionType, IPAddress(es), PGWF-TEID, SCEFID, and Defaultbearer. Also, the contexts stored for each bearer are EPS Bearer ID, TI, TFT, SGW F-TEID, PGW F-TEID, MME F-TEID, eNB Address, NR node Address, WAG Address, eNB ID, NR node. It may include ID and WAG ID.

[1.2.4. SMF configuration]
Next, FIG. 7 shows a device configuration example of the SMF_A230 and SMF_B232. As shown in FIG. 7, the SMF_A230 includes a control unit_D700, a network connection unit_D720, and a storage unit_D740, respectively. The network connection unit_D720 and the storage unit_D740 are connected to the control unit_D700 via a bus. The storage unit_D 740 stores the context 742.

The control unit_D700 of the SMF_A230 is a functional unit for controlling the entire SMF_A230, and realizes various processes of the entire SMF_A230 by reading and executing various information and programs stored in the storage unit_D740. To do.

Also, the network connection part_D720 of SMF_A230 is a function part for SMF_A230 to connect with AMF_A240, UPF_A235, UDM, and PCF. In other words, the SMF_A230 can transmit/receive user data and/or control information to/from the AMF_A240, UPF_A235, UDM, and PCF via the network connection unit_D720.

Also, the storage unit_D740 of the SMF_A230 is a functional unit that stores programs and data necessary for each operation of the SMF_A230. The storage unit_D740 of the SMF_A230 is configured by, for example, a semiconductor memory, HDD, SSD or the like. The storage unit_D740 of the SMF_A230 stores identification information, control information, flags, parameters and the like included in control messages transmitted and received in a communication procedure described later. Further, as the context 742 stored in the storage unit _D740 of the SMF_A230, the context stored for each UE, the context stored for each APN, the context stored for each PDU session, and the bearer stored for each bearer. There may be context. The context stored for each UE may include IMSI, MEIdentity, MSISDN, and RATtype. The context stored for each APN may include APN in use. The context stored for each APN may be stored for each Data Network Identifier. The context stored for each PDU session may include Assigned Session Type, IP Address(es), SGW F-TEID, PGW F-TEID, and Default Bearer. The context stored for each bearer may include EPS Bearer ID, TFT, SGW F-TEID, and PGW F-TEID.

Note that SMF_B232 has the same configuration as SMA_A230.

[1.2.5. UPF configuration]
Next, FIG. 7 shows a device configuration example of UPF_A235 and UPF_B237. As shown in FIG. 7, the UPF_A235 includes a control unit_D700, a network connection unit_D720, and a storage unit_D740, respectively. The network connection unit_D720 and the storage unit_D740 are connected to the control unit_D700 via a bus. The storage unit_D 740 stores the context 742.

The control unit_D700 of the UPF_A235 is a functional unit for controlling the entire UPF_A235, and realizes various processes of the entire UPF_A235 by reading and executing various information and programs stored in the storage unit_D740. To do.

The UPF_A235 network connection unit_D720 is configured such that the UPF_A235 is a DN (that is, DN_A5 and/or DN_B105), an SMF_A230, another UPF_A235, and an access network (that is, E-UTRAN_A80, 5G-RAN_A120, and WLANANc125). It is a functional part for connecting. In other words, the UPF_A235, via the network connection_D720, the DN (i.e., DN_A5 and/or DN_B105), the SMF_A230, other UPF_A235, and the access network (i.e., E-UTRAN_A80 and 5G-RAN_A120 and WLANANc125). User data and/or control information can be sent to and received from.

Also, the storage unit_D740 of the UPF_A235 is a functional unit that stores programs and data necessary for each operation of the UPF_A235. The storage unit_D740 of the UPF_A235 is configured by, for example, a semiconductor memory, HDD, SSD, or the like. The storage unit_D 740 of the UPF_A 235 stores identification information, control information, flags, parameters, etc. included in control messages transmitted/received in a communication procedure described later. As the context 742 stored in the storage unit _D740 of the UPF_A235, the context stored for each UE, the context stored for each APN, the context stored for each PDU session, and the bearer stored for each bearer. There may be context. The context stored for each UE may include IMSI, MEIdentity, MSISDN, and RATtype. The context stored for each APN may include APN in use. The context stored for each APN may be stored for each Data Network Identifier. The context stored for each PDU session may include Assigned Session Type, IP Address(es), SGW F-TEID, PGW F-TEID, and Default Bearer. The context stored for each bearer may include EPS Bearer ID, TFT, SGW F-TEID, and PGW F-TEID.

Note that UPF_B237 has the same configuration as UPF_A235.

[1.2.6. Information stored in the storage unit of each device above]
Next, each information stored in the storage unit of each device will be described.

IMSI (International Mobile Subscriber Identity) is permanent identification information of the subscriber (user), and is identification information assigned to the user who uses the UE. The IMSI stored by UE_A10 and MME_A40/CPF_A140/AMF_A2400 and SGW_A35 may be equal to the IMSI stored by HSS_A50.

EMM State/MM State indicates the mobility management state of UE_A10 or MME_A40/CPF_A140/AMF_A240. For example, the EMM State/MM State may be an EMM-REGISTERED state in which UE_A10 is registered in the network (registration state) and/or an EMM-DEREGISTERD state in which UE_A10 is not registered in the network (non-registration state). The EMM State/MM State may be an ECM-CONNECTED state in which the connection between the UE_A 10 and the core network is maintained and/or an ECM-IDLE state in which the connection is released. The EMM State/MM State may be information that can distinguish the state in which the UE_A10 is registered in the EPC and the state in which the UE_A10 is registered in the NGC or 5GC.

GUTI (Globally Unique Temporary Identity) is temporary identification information of UE_A10. GUTI consists of MME_A40/CPF_A140/AMF_A240 identification information (GUMMEI (Globally Unique MME Identifier)) and specific MME_A40/CPF_A140/AMF_A240 identification information (M-TMSI (M-Temporary Mobile Subscriber Identity)). To be done. MEIdentity is the ID of UE_A10 or ME, and may be, for example, IMEI (International Mobile Equipment Identity) or IMEISV (IMEI Software Version). MSISDN represents the basic telephone number of UE_A10. The MSISDN stored by MME_A40/CPF_A140/AMF_A240 may be the information indicated by the storage unit of HSS_A50. Note that the GUTI may include information that identifies the CPF_140.

MME F-TEID is information that identifies MME_A40/CPF_A140/AMF_A240. The MMEF-TEID may include the IP address of MME_A40/CPF_A140/AMF_A240, may include the TEID (Tunnel Endpoint Identifier) of MME_A40/CPF_A140/AMF_A240, or both of them. Good. Further, the IP address of MME_A40/CPF_A140/AMF_A240 and the TEID of MME_A40/CPF_A140/AMF_A240 may be stored independently. Further, the MME F-TEID may be identification information for user data or identification information for control information.

∙ SGW F-TEID is information that identifies SGW_A35. The SGW F-TEID may include the IP address of SGW_A35, the TEID of SGW_A35, or both of them. Also, the IP address of SGW_A35 and the TEID of SGW_A35 may be stored independently. Moreover, the SGW F-TEID may be identification information for user data or identification information for control information.

PGW F-TEID is information that identifies PGW_A30/UPGW_A130/SMF_A230/UPF_A235. The PGW F-TEID may include the IP address of PGW_A30/UPGW_A130/SMF_A230/UPF_A235, may include the TEID of PGW_A30/UPGW_A130/SMF_A230/UPF_A235, or may include both of them. Good. Also, the IP address of PGW_A30/UPGW_A130/SMF_A230/UPF_A235 and the TEID of PGW_A30/UPGW_A130/SMF_A230/UPF_A235 may be stored independently. Moreover, the PGW F-TEID may be identification information for user data or identification information for control information.

ENB F-TEID is information that identifies eNB_A45. The eNB-F-TEID may include the IP address of the eNB_A45, the TEID of the eNB_A45, or both of them. Also, the IP address of eNB_A45 and the TEID of SGW_A35 may be stored independently. Further, the eNB F-TEID may be identification information for user data or identification information for control information.

Also, the APN may be identification information that identifies the core network and an external network such as a DN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30/UPGW_A130/UPF_A235 that connects the core network A_90. The APN may be a DNN (Data Network Name). Therefore, the APN may be expressed as a DNN or the DNN may be expressed as an APN.

Note that the APN may be identification information that identifies such a gateway, or identification information that identifies an external network such as a DN. When a plurality of gateways that connect the core network and the DN are arranged, there may be a plurality of gateways that can be selected by the APN. Further, one gateway may be selected from the plurality of gateways by another method using identification information other than APN.

UE Radio Access Capability is identification information indicating the wireless access capability of UE_A10. UENetworkCapability includes the security algorithms and key derivation functions supported by UE_A10. MS Network Capability is information including one or more pieces of information required for SGSN_A42 for UE_A10 having GERAN_A25 and/or UTRAN_A20 function. Access Restriction is registration information of access restriction. eNB Address is the IP address of eNB_A45. MMEUES1APID is information that identifies UE_A10 in MME_A40/CPF_A140/AMF_A240. The eNBUES1APID is information that identifies the UE_A10 in the eNB_A45.

APN in use is the recently used APN. APN in Use may be Data Network Identifier. This APN may be composed of network identification information and default operator identification information. Furthermore, APNinUse may be information that identifies the DN of the establishment destination of the PDU session.

Assigned Session Type is information indicating the type of PDU session. AssignedSessionType may be AssignedPDNType. The type of PDU session may be IP or non-IP. Further, when the PDU session type is IP, it may further include information indicating the type of PDN assigned from the network. The Assigned Session Type may be IPv4, IPv6, or IPv4v6.

Also, unless otherwise specified, the IP Address is the IP address assigned to the UE. The IP address may be an IPv4 address, an IPv6 address, an IPv6 prefix, or an interface ID. If the Assigned Session Type indicates non-IP, the IP Address element may not be included.

DN ID is identification information that identifies the core network_B190 and an external network such as a DN. Further, the DN ID can also be used as information for selecting a gateway such as UPGW_A130 or PF_A235 that connects the core network_B190.

Note that the DN ID may be identification information that identifies such a gateway, or identification information that identifies an external network such as a DN. If a plurality of gateways connecting the core network_B 190 and the DN are arranged, there may be a plurality of gateways selectable by the DN ID. Further, one gateway may be selected from the plurality of gateways by another method using identification information other than the DN ID.

Furthermore, the DN ID may be information equal to the APN or information different from the APN. If the DN ID and the APN are different information, each device may manage the information indicating the correspondence between the DN ID and the APN, or perform the procedure for inquiring the APN using the DN ID. You can also use the APN to carry out the procedure for inquiring the DN ID.

-SCEF ID is the IP address of SCEF_A46 used in the PDU session. The Default Bearer is information acquired and/or generated when a PDU session is established, and is EPS bearer identification information for identifying a default bearer associated with the PDU session.

EPS EPS Bearer ID is the identification information of the EPS bearer. Further, the EPS Bearer ID may be identification information for identifying an SRB (Signalling Radio Bearer) and/or a CRB (Control-plane Radio bearer) or may be identification information for identifying a DRB (Data Radio Bearer). TI (Transaction Identifier) is identification information that identifies a bidirectional message flow (Transaction). The EPS Bearer ID may be EPS bearer identification information for identifying a dedicated bearer. Therefore, the identification information for identifying the EPS bearer different from the default bearer may be used. TFT indicates all packet filters associated with the EPS bearer. The TFT is information for identifying a part of the user data to be transmitted/received, and the UE_A10 transmits/receives the user data identified by the TFT using the EPS bearer associated with the TFT. In other words, UE_A10 transmits/receives the user data identified by TFT using RB (Radio Bearer) associated with TFT. Further, the TFT may associate user data such as transmitted/received application data with an appropriate transfer path, or may be identification information for identifying the application data. Also, the UE_A10 may send and receive user data that cannot be identified by TFT using the default bearer. Further, the UE_A 10 may store the TFT associated with the default bearer in advance.

-Default Bearer is EPS bearer identification information that identifies the default bearer associated with the PDU session. The EPS bearer may be a logical communication path established between the UE_A10 and PGW_A30/UPGW_A130/UPF_A235, or a communication path forming a PDN connection/PDU session. Further, the EPS bearer may be a default bearer or a dedicated bearer. Further, the EPS bearer may be configured to include an RB established between the UE_A 10 and a base station and/or an access point in the access network. Furthermore, RBs and EPS bearers may be associated with each other on a one-to-one basis. Therefore, the RB identification information may be associated with the EPS bearer identification information in a one-to-one correspondence, or may be the same identification information. RB may be SRB and/or CRB or DRB. Further, the Default Bearer may be information acquired by the UE_A10 and/or SGW_A35 and/or PGW_A30/UPGW_A130/SMF_A230/UPF_A235 from the core network when the PDU session is established. The default bearer is an EPS bearer that is first established in a PDN connection/PDU session, and only one EPS bearer can be established in one PDN connection/PDU session. The default bearer may be an EPS bearer that can be used for communication of user data that is not associated with TFT. Further, the dedicated bearer is an EPS bearer that is established after the default bearer is established in the PDN connection/PDU session, and is an EPS bearer that can be established multiple times in one PDN connection/PDU session. is there. The dedicated bearer is an EPS bearer that can be used for communication of user data associated with TFT.

User Identity is information that identifies a subscriber. UserIdentity may be IMSI or MSISDN. Further, User Identity may be identification information other than IMSI and MSISDN. Serving Node Information is information that identifies MME_A40/CPF_A140/AMF_A240 used in the PDU session, and may be the IP address of MME_A40/CPF_A140/AMF_A240.

ENB Address is the IP address of eNB_A45. The eNB ID is information that identifies the UE within the eNB_A45. MME Address is the IP address of MME_A40/CPF_A140/AMF_A240. MME ID is information that identifies MME_A40/CPF_A140/AMF_A240. NRnodeAddress is the IP address of NRnode_A122. The NR node ID is information that identifies the NR node_A122. WAG Address is the IP address of WAG_A126. WAG_ID is information that identifies WAG_A126.

[1.3. Explanation of initial procedure]
Next, before explaining the detailed procedure of the initial procedure in the present embodiment, in order to avoid redundant explanation, terms unique to the present embodiment and main identification information used for each procedure will be explained in advance.

First, the network in this embodiment refers to at least a part of access network_B80/120/125, core network_B190, DN_A5, and DN_B105. Further, one or more devices included in at least a part of the access network_B80/120/125, the core network_B190, the DN_A5, and the DN_B105 may be referred to as a network or a network device. That is, the fact that the network transmits/receives messages and/or executes procedures means that the devices (network devices) in the network execute transmission/reception of messages and/or procedures.

In the present embodiment, the session management (SM; Session Management) message (also referred to as NAS (Non-Access-Stratum) SM message) may be a NAS message used in the procedure for SM, UE_A10 via AMF_A240. And SMF_A230 or SMF_B232. Further, the SM message includes a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session completion message, a PDU session rejection message, a PDU session change request message, a PDU session change acceptance message, a PDU session change rejection message, etc. May be. Moreover, the procedure for SM may include a PDU session establishment procedure, a PDU session change procedure, and the like.

The tracking area (TA; also referred to as Tracking Area) in the present embodiment is a range that can be represented by the location information of UE_A10 managed by the core network, and may be composed of, for example, one or more cells. Further, the TA may be in a range in which a control message such as a paging message is broadcast, or in a range in which the UE_A 10 can move without performing a handover procedure.

The TA list in this embodiment is a list that includes one or more TAs assigned by the network to UE_A10. Note that UE_A10 may be able to move without executing the registration procedure while moving in one or more TAs included in the TA list. In other words, the TA list may be a group of information indicating areas where the UE_A 10 can move without executing the registration procedure.

RQoS (Reflective QoS (Quality of Service)) in this embodiment is QoS supported by 5GC (5G Core). RQoS is QoS realized by UE_A10 creating a QoS rule (Derived QoS rule) based on the received downlink packet and/or downlink traffic. Note that each device may be capable of simultaneously applying RQoS and QoS that is not RQoS in the same PDU session. Further, in order to realize the adaptation of RQoS to traffic, the same QoS as that of the downlink packet to be paired may be applied to the QoS of the uplink packet.

The QoS rule (Derived QoS rule) in this embodiment is a rule for realizing user data communication using RQoS. The QoS rule may include a packet filter (Packet Filter), and/or a QFI (QoS Flow Identity), and/or a preceding value (Precedence value). Here, QFI may be an identifier for identifying a QoS flow. The preceding value indicates the priority, and the smaller the value, the higher the priority. The packet filter for the uplink packet may be generated based on the downlink packet. Furthermore, when RQoS via User Plane is enabled, the preceding value of the QoS rule may be set to a standardized value. Further, when RQoS via Control Plane is enabled, the preceding value of the QoS rule may be set to a value even transmitted/received by a control message via Control Plane. Note that the UE_A 10 may enable RQoS by creating a QoS rule, or may disable RQoS by deleting the QoS rule.

The RQoS timer (Reflective QoS Timer) in this embodiment is a timer for managing the activation of RQoS. Each device may enable RQoS only while the RQoS timer is running. In other words, each device may enable RQoS based on the start of the RQoS timer, and may disable RQoS based on the expiration of the RQoS timer. Further, the value of the RQoS timer may be a value transmitted from the network to UE_A10 in a PDU session establishment procedure or the like, or may be a preset value. It may be an RQ timer. Further, the RQoS timer may be a timer for managing activation of RQoS, but is not limited to this.

In the present embodiment, the authentication approval request information is information that UE_A10 requests to start the DN authentication approval procedure, and may be a variable indicating whether the DN authentication approval procedure is desired to be started or a service is specified. Name space, a user identifier, or an identifier for specifying the profile of the user. The DN authentication approval procedure may be a PDU session establishment authentication approval procedure. Also, the PDU session establishment authentication approval procedure may be realized using an authentication protocol EAP (Extensible Authentication Protocol) adopted or defined by the IETF.

In the present embodiment, the authentication/authorization information is information indicating the authorization approval result when responding to the DN authorization approval procedure from 3GPP NW, and may be a variable indicating whether the authorization is approved or not. It may be a namespace that specifies.

In the present embodiment, the DN authentication approval response information, for the information that UE_A10 responds to the authentication/authorization information issued by the DN, put when UE_A10 responds, even a namespace that identifies the service It may be a message response to the authentication/authorization information from the DN.

The user ID in this embodiment is an identifier that identifies a user in DN authentication approval. The user ID may be information that UE_A10 requests to activate the DN authentication approval procedure.

The user profile ID in this embodiment is an identifier that identifies a user profile in DN authentication approval. The UE_A10 may be information requesting activation of the DN authentication approval procedure.

The DN authentication approval in this embodiment is the next-generation security system of the 5G mobile communication system, which is the next-generation mobile communication system. This is a mechanism that enables authorization and authentication by DN during the PDU session establishment procedure, and may be a system that does not exist in the conventional 4G system. Further, in the next generation security system, the authentication and the authorization may be separated in relation to the DN authentication and authorization. Furthermore, by separating the authentication and the authorization, the owners of the authentication resource and the authorization resource may be able to perform the authorization and approval at their respective responsibilities, and flexible service deployment using the mobile communication system may be possible.

The first timer in the present embodiment is a timer for managing the start of a procedure for session management such as a PDU session establishment procedure and/or the transmission of an SM (Session Management) message such as a PDU session establishment request message. While the first timer is running, each device may be prohibited from starting a procedure for session management and/or transmitting/receiving an SM message. Note that the first timer may be set at least in either APN/DNN or slice unit. The SM message may be a NAS message used in the procedure for session management, and may be a control message transmitted/received between UE_A10 and SMF_A230 via AMF_A240. Further, the SM message includes a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session completion message, a PDU session rejection message, a PDU session change request message, a PDU session change acceptance message, a PDU session change rejection message, etc. May be. Furthermore, the procedure for session management may include a PDU session establishment procedure, a PDU session change procedure, and the like.

A network slice in this embodiment is a logical network that provides specific network capabilities and network characteristics. Hereinafter, the network slice may be referred to as an NW slice.

A network slice instance (NSI; Network Slice Instance) in this embodiment forms a network slice that is composed of an instance (entity) of a network function (NF) and a set of necessary resources and is arranged. Here, the NF is a processing function in the network and is adopted or defined by 3GPP. NSI is an entity of a network slice, which is composed of one or more in the core network_B 190. Further, the NSI may be configured by a virtual NF (Network Function) generated using NST (Network Slice Template). Here, NST is a logical representation of one or more NFs (Network Functions) associated with resource requests for providing required communication services and capabilities. That is, the NSI may be an aggregate in the core network_B 190 configured by a plurality of NFs. Further, the NSI may be a logical network configured to divide user data delivered by services or the like. One or more NFs may be configured in the network slice. The NF configured in the network slice may or may not be a device shared with other network slices. UE_A10 can be assigned to one or more network slices based on registration information and/or APN such as UE usage type and/or one or more network slice type IDs and/or one or more NS IDs.

The NSI (Network Slice Instance) in the present embodiment is an entity of a network slice (Network Slice) configured to have one or more in the core network_B 190. Further, the NSI in the present embodiment may be configured by a virtual NF (Network Function) generated using NST (Network Slice Template). Here, NST is a logical representation of one or more NFs (Network Functions) associated with resource requests for providing required communication services and capabilities. That is, the NSI may be an aggregate in the core network_B 190 configured by a plurality of NFs. Further, the NSI may be a logical network configured to divide user data delivered by services or the like. At least one NF may be configured in the network slice. The NF configured in the network slice may or may not be a device shared with other network slices. UE_A10 and/or devices in the network are NSSAI and/or S-NSSAI and/or UE usage type and/or one or more network slice type IDs and/or one or more NS IDs etc. It can be assigned to one or more network slices based on registration information and/or APN.

The S-NSSAI in this embodiment is an abbreviation for Single Network Slice Selection Assistance information and is information for identifying a network slice. S-NSSAI may consist of SST (Slice/Service type) and SD (Slice Differentiator). S-NSSAI may be configured with only SST, or may be configured with both SST and SD. Here, SST is information indicating the operation of the network slice expected in terms of functions and services. Further, SD may be information that complements SST when selecting one NSI from a plurality of NSI indicated by SST. The S-NSSAI may be unique information for each PLMN or may be standard information shared by the PLMNs. The network may also store one or more S-NSSAIs in the registration information of UE_A10 as the default S-NSSAI.

NSSAI (Single Network Slice Selection Assistance information) in this embodiment is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information that assists the access network or core network in selecting the NSI. UE_A10 may store NSSAI permitted from the network for each PLMN. Also, NSSAI may be information used to select AMF_A240.

The first NW slice in this embodiment is the NW slice to which the established PDU session belongs when UE_A10 connects to a specific DN. The first NW slice may be an NW slice managed in the operator A network or may be a NW slice commonly managed in the operator B network.

The second NW slice in this embodiment is an NW slice to which another PDU session that can be connected to the DN to which the PDU session belonging to the first NW slice is connected. The first NW slice and the second NW slice may be operated by the same operator or different operators.

The operator A network in this embodiment is a network operated by operator A. The NW slice common to the operator B may be expanded.

The operator B network in this embodiment is a network operated by operator B. The NW slice common to the operator A may be expanded.

The re-attempt information in the present embodiment is information for the NW to instruct the UE_A10 whether to allow reconnection using the same identification information for the rejected PDU session. The re-attempt information may be set for each UTRAN access, E-UTRAN access, and NR access.

The first behavior in this embodiment is a behavior in which the UE_A10 stores the slice information transmitted in the PDU session establishment request message in association with the transmitted PDU session identifier. In the first behavior, the UE_A10 may store the slice information transmitted in the PDU session establishment request message, or may store the slice information received when the PDU session establishment request message is rejected. ..

With the second behavior in the present embodiment, UE_A10, slice information different from the slice information previously specified in the PDU session establishment request message, using the APN / specified in the previously transmitted PDU session establishment request message. This is a behavior of transmitting a PDU session establishment request message for connecting to the same APN/DNN as the DNN. Specifically, the second behavior is that when the backoff timer value received from the network is zero or invalid, using slice information different from the slice information specified in the PDU session establishment request message transmitted previously, It may be the behavior of transmitting the PDU session establishment request message for connecting to the same APN/DNN as the PDU session establishment request message before. The second behavior is that if the previously transmitted PDU session establishment request message is rejected because it is not supported by the radio of the specific PLMN to which the specified APN/DNN is connected, or it is temporarily For this reason, if the previously sent PDU session establishment request message is rejected, the slice information different from the slice information previously specified in the PDU session establishment request message is used, and the previously sent PDU session establishment request message is sent. The behavior may be such that a PDU session establishment request message for connecting to the same APN/DNN as the specified APN/DNN is transmitted.

The third behavior in the present embodiment, UE_A10, when the PDU session establishment request message is rejected, until the first timer expires, using the same identification information, a new PDU session establishment request message. Is a behavior that does not send. Specifically, the third behavior is that if the backoff timer value received from the network is neither zero nor invalid, a new PDU session establishment request with the same identification information is used until the first timer expires. The behavior may be that the message is not transmitted. The third behavior is that the PDU session establishment request message is rejected when another PLMN is selected or when another NW slice is selected and the rejection reason for the network operation setting failure is received. When the backoff timer received at this time is activated, the behavior may be such that a new PDU session establishment request message using the same identification information is not transmitted until the first timer expires.

With the fourth behavior in the present embodiment, UE_A10 is, when the PDU session establishment request message sent in the Registration procedure is rejected, until the first timer expires, slice information, and / or DNN /. This is the behavior of not transmitting a new PDU session establishment request message that does not carry APN information. Specifically, the fourth behavior is that if the backoff timer received from the network is neither zero nor invalid, the slice information and/or the DNN/APN information is not added until the first timer expires. The behavior may be that the PDU session establishment request message is not transmitted.

The fifth behavior in this embodiment is the behavior in which the UE_A10 does not send a new PDU session establishment request message using the same identification information when the PDU session establishment request message is rejected. Specifically, the fifth behavior is a new PDU session establishment request message using the same identification information when UE_A10 and the PDU types supported by the network are different and the UEs are in the uniform PLMN. May not be transmitted.

The sixth behavior in the present embodiment, UE_A10, when the PDU session establishment request message is rejected, using the same identification information, as an initial procedure, is a behavior to send a new PDU session establishment request message. .. Specifically, the sixth behavior is that when the PDU session establishment request message is rejected because the target PDN session context does not exist in the handover from non-3GPP, the same identification information is used as an initial procedure, It may be a behavior of transmitting a new PDU session establishment request message.

The seventh behavior in this embodiment is the behavior of continuing the backoff timer received when the previous PDU session establishment request message was rejected when another NW slice was selected in the PLMN selection procedure. Specifically, the seventh behavior is that when the PDU session establishment request message is rejected, PLMN selection is performed, and in the selected PLMN, the NW slice specified in the PDU session establishment request message is common. When the NW slice can be designated, the behavior may be such that the backoff timer received when the PDU session establishment request message is rejected is continued.

The eighth behavior in this embodiment is a behavior in which the UE_A10 may set the value notified from the network as the first timer value, or sets the value set in the UE_A10 in advance. Specifically, the eighth behavior, UE_A10 may be a behavior to set the backoff timer value received in the rejection notification of the PDU session establishment request message as the first timer value, or to UE_A10 in advance. The behavior may be setting or a value to be held may be set as the first timer value. It should be noted that the eighth behavior in the case where the timer to be set in UE_A10 in advance or the timer to be held is set as the first timer value may be limited to HPLMN or uniform PLMN presence.

The ninth behavior in the present embodiment, UE_A10, when the PDU session establishment request message is rejected, terminal power on/off, or until USIM removal and insertion, is a behavior that does not send a new PDU session establishment request message. .. Specifically, the ninth behavior is when the backoff timer received from the network is invalid or when the reason included in the PDU session rejection message is different between UE_A10 and NW in PDU type. The behavior may be such that a new PDU session establishment request message is not transmitted until it is turned on/off or the USIM is removed/inserted. The ninth behavior is when the PDU session establishment request message is rejected because the specified APN/DNN is not supported by the connected PLMN radio, and the backoff timer information element from the network is If there is no Re-attempt information, or if reconnection of the PDU session to the uniform PLMN is allowed, the connected PLMN does not turn on/off the terminal power or insert/remove the USIM until a new PDU session. The behavior may be that the establishment request message is not transmitted. The ninth behavior is when the first PDU session establishment request message is rejected because the specified APN/DNN is not supported by the connected PLMN radio, and the backoff timer from the network If there is no information element and there is no Re-attempt information, or if reconnection of the PDU session to the uniform PLMN is not allowed, the connected PLMN does not turn on/off the terminal power or insert/remove the USIM. PDU session establishment request message may not be transmitted. The ninth behavior is when the PDU session establishment request message is rejected because the specified APN/DNN is not supported by the connected PLMN radio, and even if the backoff timer from the network is zero, it is invalid. Otherwise, the behavior may be such that a new PDU session establishment request message is not transmitted until the terminal power is turned on/off or the USIM is removed/inserted. The ninth behavior is when the PDU session establishment request message is rejected because the specified APN/DNN is not supported by the connected PLMN radio, and the backoff timer from the network is invalid. , A new PDU session establishment request message may not be transmitted until the terminal power is turned on/off or the USIM is removed/inserted.

The tenth behavior in this embodiment is the behavior in which the UE_A10 transmits a new PDU session establishment request message when the PDU session establishment request message is rejected. Specifically, the tenth behavior is the backoff timer information notified from the network when the backoff timer received from the NW is zero or when the PDU session establishment request message is rejected for a temporary reason. If there is no element itself, the behavior may be to send a new PDU session establishment request message. The tenth behavior is the case where another PLMN is selected, or another NW slice is selected, and the PDU session establishment request message is rejected for a temporary reason, and the target is the selected PLMN. If the back-off timer is not activated for the APN/DNN or if the back-off timer received from the network is invalid, the behavior may be that a new PDU session establishment request message is transmitted. The tenth behavior is when the PDU session establishment request message is rejected because the PDU type of the UE_A10 and the network are different, and when different PLMNs are selected, Re-attempt information is not received, or the equal PLMNs are received. If a PLMN not listed is selected, the PDP type is changed, the terminal power is turned on/off, or the USIM is removed/inserted, a new PDU session establishment request message is sent. Good. The 10th behavior is that the backoff timer notified by the network is zero when the first PDU session is rejected because the specified APN/DNN is not supported by the connected PLMN radio. In this case, the behavior may be to send a new PDU session establishment request message.

The eleventh behavior in this embodiment is behavior in which UE_A10 ignores the first timer and Re-attempt information. Specifically, the 11th behavior is when the PDU session establishment request message is rejected because the target PDN session context does not exist in the handover from non-3GPP, or the PDN connection In the case where the PDU session establishment request message is rejected because the number of bearers set up in has reached the maximum allowable number, UE_A10 is the behavior of ignoring the first timer and Re-attempt information. Good.

The equivalent PLMN in this embodiment is a PLMN treated as being the same HPLMN and the same PLMN in the network.

Next, the identification information in this embodiment will be described. The first identification information in the present embodiment is information indicating whether or not the UE_A 10 supports Reflective Quality of Service (RQoS). Further, the first identification information may indicate whether the UE_A10 supports UE-controlled RQoS and/or whether the UE_A10 supports network-led RQoS. The UE-controlled RQoS may be RQoS activated by the UE-initiated RQoS activation procedure, or may be RQoS invalidated by the first RQoS deactivation procedure. .. Further, the network-initiated controlled RQoS may be the RQoS activated by the network-initiated RQoS activation procedure or the RQoS invalidated by the second RQoS deactivation procedure. .. Further, the first identification information may correspond to the fourth identification information or the fifth identification information. That is, the first identification information, for user data communication with the DN identified by the fourth identification information, or for the PDU session identified by the fifth identification information, UE_A10 RQoS May mean information indicating whether or not to support. Further, the first identification information may be information having the meaning of the second identification information and/or the third identification information. That is, the first identification information may mean information indicating whether or not the UE_A 10 supports RQoS controlled via the Control Plane and/or the User Plane. Note that the RQoS controlled via the Control Plane may be the RQoS enabled and/or disabled via the Control Plane, and the RQoS controlled via the User Plane means the User Plane. RQoS may be enabled and/or disabled via the. Further, the first identification information may be information having the meaning of the sixth identification information. That is, the first identification information may be information indicating whether or not UE_A10 supports RQoS and also indicating that UE_A10 requests RQoS.

The second identification information in this embodiment is information indicating whether or not UE_A10 supports RQoS controlled via Control Plane. Also, the second identification information, whether UE_A10 supports RQoS controlled via Control Plane led by UE, and/or, UE_A10 supports RQoS controlled via Control Plane initiated by network. It may indicate whether or not to do. Further, the second identification information may correspond to the fourth identification information or the fifth identification information. That is, the second identification information, for user data communication with the DN identified by the fourth identification information, or for the PDU session identified by the fifth identification information, UE_A10 Control. It may mean information indicating whether to support RQoS controlled through Plane. Further, the second identification information may be information having the same meaning as the seventh identification information. That is, the second identification information indicates whether UE_A10 supports RQoS controlled via Control Plane, and, and, UE_A10 is information indicating that RQoS controlled via Control Plane is requested. It may be.

The third identification information in this embodiment is information indicating whether or not the UE_A10 supports RQoS controlled via User Plane. Also, the third identification information, whether UE_A10 supports RQoS controlled via User Plane led by UE, and/or, UE_A10 supports RQoS controlled via User Plane led by network. It may indicate whether or not to do. Further, the third identification information may correspond to the fourth identification information or the fifth identification information. That is, the third identification information, for user data communication with the DN identified by the fourth identification information, or for the PDU session identified by the fifth identification information, UE_A10 User It may mean information indicating whether to support RQoS controlled through Plane. Further, the third identification information may be information having the same meaning as the eighth identification information. That is, the third identification information indicates whether UE_A10 supports RQoS controlled via User Plane, and UE_A10 is information indicating that RQoS controlled via User Plane is requested. It may be.

The fourth identification information in this embodiment is a DNN (Data Network Name). The DNN may be information used to identify the DN (Data Network).

The fifth identification information in this embodiment is a PDU session ID (PDU Session ID). The PDU session ID may be information used to identify a PDU session.

The sixth identification information in this embodiment is information indicating that UE_A10 requests that RQoS be changed to enabled (usable state). Further, the sixth identification information, UE_A10 requests that the RQoS controlled by the UE is changed to enabled, and / or, UE_A10 is changed to the RQoS controlled by the network to enabled. It may indicate that the request is received. Requesting that RQoS should be changed to enabled may mean requesting permission to use RQoS. The sixth identification information may correspond to the fourth identification information and/or the fifth identification information. That is, the sixth identification information, for user data communication with the DN identified by the fourth identification information, or for the PDU session identified by the fifth identification information, UE_A10 RQoS May also mean information indicating that it is requested to have changed to enabled. Further, the sixth identification information may be information having the meanings of the seventh identification information and/or the eighth identification information. That is, the sixth identification information may mean information indicating that the UE_A10 requests that the RQoS controlled via the Control Plane and/or the User Plane be changed to enabled.

The seventh identification information in this embodiment is information indicating that the UE_A10 requests that the RQoS controlled via the Control Plane be changed to enabled. Further, the seventh identification information, UE_A10 is requested by the UE is requested to change the RQoS controlled via Control Plane to enabled, and / or, UE_A10 is the network initiative via Control Plane. It may indicate that the controlled RQoS should be requested to be changed to enabled. Further, the seventh identification information may correspond to the fourth identification information or the fifth identification information. That is, the seventh identification information, for user data communication with the DN identified by the fourth identification information, or for the PDU session identified by the fifth identification information, UE_A10 Control. It may mean information indicating that the RQoS controlled through the Plane is requested to be changed to enabled.

The eighth identification information in this embodiment is information indicating that the UE_A10 requests to change the RQoS controlled via the User Plane to enabled. Further, the eighth identification information, UE_A10 is requested by the UE to request to change the RQoS controlled via the User Plane to enabled, and / or, UE_A10 is the network initiative via the User Plane. It may indicate that the controlled RQoS should be requested to be changed to enabled. Also, the eighth identification information may correspond to the fourth identification information or the fifth identification information. That is, the eighth identification information, for user data communication with the DN identified by the eighth identification information, or for the PDU session identified by the fifth identification information, UE_A10 User It may mean information indicating that the RQoS controlled through the Plane is requested to be changed to enabled.

The 61st identification information in the present embodiment is information for requesting service authentication/authorization by the DN via the 3GPP interface in the DN connection. Furthermore, the 61st identification information may be information requesting execution of a PDU session establishment authentication approval procedure in the registration procedure and/or the PDU session establishment procedure. In other words, the 61st identification information may be information requesting service authentication/authorization by DN via the 3GPP interface in the registration procedure and/or the PDU session establishment procedure. As a specific example, the 61st identification information may be a flag requesting DN service authentication/authorization, a service name capable of identifying a specific DN service, or a user identifier (DN-specific It may be an identity) or a user profile identifier. Furthermore, the 61st identification information may be authentication approval request information.

The 71st identification information in this embodiment is information identifying that it belongs to the first NW slice. In other words, the 71st identification information may be information indicating that UE_A10 wants to establish a PDU session belonging to the first NW slice. As a specific example, the 71st identification information may be NSSAI that identifies the first NW slice. Note that the 71st identification information may be information for identifying a specific NW slice in the operator A network, or may be the same NW slice commonly in operator B (other operators than operator A). It may be information to be provided. Further, the 71st identification information may be information indicating the first NW slice set from the HPLMN, or may be information indicating the first NW slice acquired from AMF_A240 in the registration procedure. However, the information may be information indicating the first NW slice permitted from the network. Further, the 71st identification information may be information indicating the first NW slice stored for each PLMN.

The eleventh identification information in this embodiment is information indicating whether or not the network supports RQoS. Further, the eleventh identification information may indicate whether the network supports UE-controlled RQoS, and/or whether the network supports network-controlled RQoS. The eleventh identification information may correspond to the fourteenth identification information or the fifteenth identification information. That is, the eleventh identification information is used by the network for RQoS for user data communication with the DN identified by the fourteenth identification information, or for the PDU session identified by the fifteenth identification information. May mean information indicating whether or not to support. Further, the eleventh identification information may be information having the meaning of the twelfth identification information and/or the thirteenth identification information. That is, the eleventh identification information may mean information indicating whether the network supports RQoS controlled via the Control Plane and/or the User Plane. Further, the eleventh identification information may be information having the meaning of the seventeenth identification information. That is, the eleventh identification information may be information indicating whether or not the network supports RQoS and also indicating that the network accepts RQoS.

The twelfth identification information in this embodiment is information indicating whether or not the network supports RQoS controlled via Control Plane. Further, the twelfth identification information supports whether or not the network supports RQoS controlled by the UE through the Control Plane, and/or supports the network controlled RQoS by the network initiated through the Control Plane. It may indicate whether or not to do. The twelfth identification information may correspond to the fourteenth identification information or the fifteenth identification information. That is, the twelfth identification information is used by the network for controlling user data communication with the DN identified by the fourteenth identification information, or for a PDU session identified by the fifteenth identification information. It may mean information indicating whether to support RQoS controlled through Plane. Further, the twelfth identification information may be information having the meaning of the eighteenth identification information. That is, the twelfth identification information is information indicating whether or not the network supports RQoS controlled via Control Plane, and that the network accepts RQoS controlled via Control Plane. It may be.

The thirteenth identification information in this embodiment is information indicating whether or not the network supports RQoS controlled via User Plane. In addition, the 13th identification information, whether the network supports RQoS controlled via User Plane initiated by the UE, and/or the network supports RQoS controlled via User Plane initiated by the network. It may indicate whether or not to do. The thirteenth identification information may correspond to the fourteenth identification information or the fifteenth identification information. That is, the thirteenth identification information is used by the network for User data communication with the DN identified by the fourteenth identification information, or for the PDU session identified by the fifteenth identification information. It may mean information indicating whether to support RQoS controlled through Plane. The thirteenth identification information may also be information having the meaning of the nineteenth identification information. That is, the 13th identification information is information indicating whether or not the network supports RQoS controlled via User Plane, and that the network accepts RQoS controlled via User Plane. It may be.

The 14th identification information in this embodiment is DNN. The fourteenth identification information may be a DNN permitted by the network or a DNN selected by the network. Furthermore, the 14th identification information may be the same DNN as the 4th identification information or a different DNN.

The fifteenth identification information in this embodiment is a PDU session ID. The fifteenth identification information may be a PDU session ID permitted by the network or a PDU session ID selected by the network. Furthermore, the fifteenth identification information may be the same PDU session ID as the fifth identification information, or may be a different PDU session ID.

The 16th identification information in this embodiment is the timer value of the RQoS timer. The value indicated by the 16th identification information may be a value determined by the device in the core network, a value determined by the operator, or a value determined by a service provider other than the operator. May be. The 16th identification information may be transmitted and received in association with at least one of the 11th to 13th identification information and the 17th to 19th identification information.

The 17th identification information in this embodiment is information indicating that the network accepts to change RQoS to enabled. Further, the 17th identification information is that the network accepts that the RQoS controlled by the UE is changed to enabled, and/or, the RQoS that the network is controlled by the network is changed to enabled. May be indicated to be accepted. Accepting that RQoS is changed to enabled may mean that the use of RQoS is permitted. Further, the 17th identification information may correspond to the 14th identification information or the 15th identification information. That is, the 17th identification information is used by the network for RQoS for user data communication with the DN identified by the 14th identification information, or for the PDU session identified by the 15th identification information. It may mean information indicating that acceptance to change to enabled. Further, the 17th identification information may be information having the meaning of the 18th identification information and/or the 19th identification information. That is, the 17th identification information may be information indicating that the network accepts to change the RQoS controlled via the Control Plane and/or the User Plane to enabled.

The 18th identification information in this embodiment is information indicating that the network accepts to change the RQoS controlled via the Control Plane to enabled. Further, the 18th identification information is that the network accepts that the RUE controlled by the UE via Control Plane is changed to enabled, and/or the network is controlled by the network via the Control Plane. It may indicate that it accepts to change RQoS to enabled. Further, the 18th identification information may correspond to the 14th identification information or the 15th identification information. That is, the 18th identification information is used by the network for controlling user data communication with the DN identified by the 14th identification information, or for a PDU session identified by the 15th identification information. It may mean information indicating acceptance to change the RQoS controlled via the Plane to enabled.

The 19th identification information in this embodiment is information indicating that the network accepts to change the RQoS controlled via the User Plane to enabled. Also, the 19th identification information is that the network accepts that the UE takes the initiative to change the RQoS controlled via the User Plane to enabled, and/or the network takes the initiative to control the network via the User Plane. Accepting that the RQoS is changed to enabled. Further, the 19th identification information may correspond to the 14th identification information or the 15th identification information. That is, the 19th identification information is used by the network for User data communication with the DN identified by the 14th identification information, or for the PDU session identified by the 15th identification information. It may mean information indicating acceptance to change the RQoS controlled via the Plane to enabled.

The 21st identification information in this embodiment is a Cause value. The Cause value indicates the reason for refusal.Specifically, the service requested in the PDU session establishment request message is rejected by the external DN due to user authentication failure, or canceled by the external DN, or Canceled by the external packet data network (referred to as User authentication authentication or authorization failed), not allowing (rejecting) changing RQoS to enabled, enabling RQoS controlled via Control Plane and User Plane Do not allow to change (reject), do not allow to change (reject) only RQoS controlled via Control Plane, and enable only RQoS controlled via User Plane. At least one of not permitting (rejecting) to change may be indicated. Note that refusing to change RQoS to enabled may mean not allowing the use of RQoS. Furthermore, the 21st identification information may be information indicating that some requests have been rejected. The 21st information may be information including the meaning indicated by one or more of the 22nd to 29th identification information. Further, the 21st identification information may correspond to the 25th identification information or the 26th identification information. That is, the 21st identification information may mean the Cause value for the DN identified by the 25th identification information or the Cause value for the PDU session identified by the 26th identification information. The 21st identification information may correspond to a registration area (RA; Registration Area), a tracking area (TA; Tracking Area), or an access network (AN; Access Network). That is, the 21st identification information may mean the Cause area for the registration area, the tracking area, or the access network. Specifically, the 21st identification information may be a Cause value indicating that RQoS is not permitted in the DN identified by the 25th identification information, or the PDU session identified by the 26th identification information. It may be a Cause value indicating that RQoS is not allowed in. Furthermore, the 21st identification information may be a Cause value indicating that RQoS is not allowed in the registration area to which UE_A10 currently belongs, and/or the tracking area, or in the access network to which UE_A10 is connected. It may be a Cause value indicating that RQoS is not permitted. The Cause value indicated by the 21st identification information is not limited to these.

The 121st identification information in the present embodiment may be information indicating a detailed rejection reason supplementing the rejection reason indicated by the 21st identification information when the 21st identification information indicates User authentication or authorization authorization failed. The detailed rejection reason may be information indicating that the PDU session establishment authentication approval procedure has failed and/or information indicating that the authentication procedure using EAP in the PDU session establishment authentication approval procedure has failed. The EAP-failure used in the following description may be information indicating the reason for refusal of such details. Specifically, when the 61st identification information included in the PDU session establishment request message conforms to the local policy and/or the user subscriber information and the third condition determination by SMF_A230 is determined to be true, the PDU The session establishment authentication approval procedure (S1005) is executed. At this time, if the PDU session establishment authentication approval procedure fails, the PDU session establishment rejection message sent by SMF_A230 (S1022), the 21st identification information indicating User authentication authentication or authorization authorization failed and the 121st indicating EAP-failure. Identification information may be included. On the other hand, since the 61st identification information included in the PDU session establishment request message does not comply with the local policy and/or user subscriber information, if the third condition determination is determined to be false, PDU session establishment authentication approval The procedure (S1005) is not executed. At this time, the PDU session establishment rejection message (S1022) transmitted by SMF_A230 includes the 21st identification information indicating User authentication authentication or authorization authorization failed, but does not include the 121st identification information indicating EAP-failure. good. Here, if the 121st identification information indicating EAP-failure is included in the PDU session establishment rejection message (S1022), it means that the PDU session establishment authentication approval procedure using EAP is executed, and that procedure has failed. May be the case. On the other hand, if the 121st identification information indicating EAP-failure is not included in the PDU session establishment rejection message (S1022), the PDU session establishment authentication approval procedure using EAP is not executed, and the PDU session establishment using EAP is established. This may be the case where the reason for refusal other than the failure of the certification approval procedure is indicated. For example, as the reason for rejection other than the failure of the PDU session establishment authentication approval procedure using EAP, as described above, the 61st identification information included in the PDU session establishment request message conforms to the local policy and/or the user subscriber information. May not be the case.

The 22nd identification information in this embodiment is information indicating that the network does not support RQoS. The 22nd identification information may indicate that the network does not support UE-controlled RQoS and/or that the network does not support network-controlled RQoS. Further, the 22nd identification information may correspond to the 25th identification information or the 26th identification information. In this case, the 22nd identification information is used by the network for user data communication with the DN identified by the 25th identification information, or for the PDU session identified by the 26th identification information. It may mean information indicating that RQoS is not supported. The 22nd identification information may correspond to the registration area, the tracking area, or the access network. In this case, the 22nd identification information may mean, for the registration area, the tracking area, or the access network, information indicating that the network does not support RQoS. Further, the 22nd identification information may be information having the meanings of the 23rd identification information and/or the 24th identification information. That is, the 22nd identification information may be information indicating that the network does not support RQoS controlled via the Control Plane and/or the User Plane. Further, the 22nd identification information may be information having the meaning of the 27th identification information. That is, the 22nd identification information may be information indicating that the network does not support RQoS and that the network does not permit (reject) RQoS.

The 23rd identification information in this embodiment is information indicating that the network does not support RQoS controlled via Control Plane. In addition, the 23rd identification information, the network does not support RQoS controlled via the Control Plane initiated by the UE, and/or the network does not support RQoS controlled by the Control Plane initiated by the network. May be indicated. In addition, the 23rd identification information may correspond to the 25th identification information or the 26th identification information. That is, the 23rd identification information is used by the network for controlling user data communication with the DN identified by the 25th identification information, or for a PDU session identified by the 26th identification information. It may mean information indicating that RQoS controlled through Plane is not supported. The 23rd identification information may correspond to the registration area, the tracking area, or the access network. That is, the 23rd identification information may mean, for the registration area, the tracking area, or the access network, information indicating that the network does not support RQoS controlled via the Control Plane. Further, the 23rd identification information may be information having the meaning of the 28th identification information. That is, the 23rd identification information indicates that the network does not support RQoS controlled via Control Plane, and indicates that the network does not permit (reject) RQoS controlled via Control Plane. It may be information.

The 24th identification information in this embodiment is information indicating that the network does not support RQoS controlled via User Plane. Further, the 24th identification information, the network does not support RQoS controlled via the User Plane initiated by the UE, and / or the network does not support RQoS controlled by the User initiated Plane initiated by the network. May be indicated. Further, the 24th identification information may correspond to the 25th identification information or the 26th identification information. That is, the 24th identification information is used by the network for User data communication with the DN identified by the 25th identification information, or for the PDU session identified by the 26th identification information. It may mean information indicating that RQoS controlled through Plane is not supported. Further, the 24th identification information may correspond to the registration area, the tracking area, or the access network. That is, the 24th identification information may mean, for the registration area, the tracking area, or the access network, information indicating that the network does not support RQoS controlled through the User Plane. Further, the 24th identification information may be information having the meaning of the 29th identification information. That is, the 24th identification information indicates that the network does not support RQoS controlled via the User Plane, and indicates that the network does not permit (reject) RQoS controlled via the User Plane. It may be information.

The 25th identification information in this embodiment is a DNN. The 25th identification information may be a DNN not permitted by the network, or may be information indicating that the DNN identified by the fourth identification information is not permitted. Furthermore, the 25th identification information may be the same DNN as the 4th identification information.

The 26th identification information in this embodiment is a PDU Session ID. The 26th identification information may be a PDU session ID not permitted by the network, or may be information indicating that the PDU session ID identified by the fifth identification information is not permitted. Furthermore, the 26th identification information may be the same PDU session ID as the 5th identification information.

The 27th identification information in this embodiment is information indicating that the network does not allow (reject) changing RQoS to enabled. The 27th identification information does not allow (reject) changing the network-controlled RQoS to enabled to enabled, and/or changes the network-controlled RQoS to enabled to enabled RQoS. You may indicate that you do not permit (reject). Further, the 27th identification information may correspond to the 25th identification information or the 26th identification information. That is, the 27th identification information is used by the network for RQoS for user data communication with the DN identified by the 25th identification information or for the PDU session identified by the 26th identification information. It may mean the information indicating that the change to enabled is not permitted (rejected). The 27th identification information may correspond to a registration area, a tracking area, or an access network. That is, the 27th identification information may mean information indicating that the registration area, the tracking area, or the access network does not allow (reject) the network to change RQoS to enabled. .. The 27th identification information may be information having the meaning of the 28th identification information and/or the 29th identification information. That is, the 27th identification information may be information indicating that the network does not allow (reject) changing the RQoS controlled through the Control Plane and/or the User Plane to enabled.

The 28th identification information in this embodiment is information indicating that the network does not allow (reject) changing the RQoS controlled via the Control Plane to enabled. Further, the 28th identification information does not allow (reject) changing the RQoS controlled by the network via Control Plane to enabled by the UE, and/or the network takes Control Plane by the network. It may indicate not to allow (reject) changing the RQoS controlled via the. Further, the 28th identification information may correspond to the 25th identification information or the 26th identification information. That is, the 28th identification information is used by the network for controlling user data communication with the DN identified by the 25th identification information or for a PDU session identified by the 26th identification information. It may mean information indicating that the RQoS controlled through the Plane is not permitted (rejected) to be changed to enabled. The 28th identification information may correspond to a registration area, a tracking area, or an access network. That is, the 28th identification information does not allow (reject) the registration area, the tracking area, or the access network from changing the RQoS controlled by the network via the Control Plane to enabled. It may mean the information shown.

The 29th identification information in this embodiment is information indicating that the network does not allow (reject) changing the RQoS controlled via the User Plane to enabled. Further, the 29th identification information does not allow (reject) changing the RQoS controlled via the User Plane to enabled by the UE, and/or the network takes the User Plane on the initiative of the network. It may indicate not to allow (reject) changing the RQoS controlled via the. Further, the 29th identification information may correspond to the 25th identification information or the 26th identification information. That is, the 29th identification information is used by the network for user data communication with the DN identified by the 25th identification information or for the PDU session identified by the 26th identification information. It may mean information indicating that the RQoS controlled via the Plane is not permitted (rejected) to be changed to enabled. The 29th identification information may correspond to the registration area, the tracking area, or the access network. That is, the 29th identification information does not allow (reject) the registration area, the tracking area, or the access network from changing the RQoS controlled by the network via the User Plane to enabled. It may mean the information shown.

The 72nd identification information in this embodiment is information indicating a reason value (cause) indicating that this procedure is rejected. The 72nd identification information may be information indicating that the request for establishing the PDU session connecting to the DN is rejected. In other words, the 72nd identification information may be information indicating that the request for establishing the PDU session belonging to the first slice has been rejected, or establishment of the PDU session belonging to the first slice is permitted. The information may be information indicating that there is not. Here, the first slice may be the slice indicated by the 71st identification information, or may be a different slice. Further, the 72nd identification information may be information indicating that establishment of a PDU session belonging to the first slice in the DN identified by the 25th identification information is not permitted, or by the 26th identification information. It may be information indicating that establishment of the PDU session belonging to the first slice is not permitted in the identified PDU session. Further, the 72nd identification information may be information indicating that the registration area to which UE_A10 currently belongs, and/or that the establishment of the PDU session belonging to the first slice in the tracking area is not permitted, UE_A10 It may be information indicating that the establishment of the PDU session belonging to the first slice is not permitted in the access network to which is connected. The reason value indicating that this procedure indicated by the 72nd identification information is rejected is not limited to these. Further, the 72nd identification information may be information indicating the value of the first timer. UE_A10 may set the value indicated by the 72nd identification information in the first timer based on the reception of the 72nd identification information, or set the timer value set by another method. Alternatively, a random value may be set. Furthermore, the 72nd identification information may be an identifier that identifies the NW slice information to which the rejected PDU session request belongs. The NW slice indicated by the 72nd identification information may be the same NW slice as the NW slice indicated by the 71st identification information, or may be a different NW slice. Furthermore, the 72nd identification information may be an identifier that the NW instructs to reconnect after the PDU session is rejected. Further, the UE_A 10 may start execution of the set timer based on the rejection reason value, the NW slice information, and the identifier for instructing reconnection from the NW.

The 31st identification information in this embodiment is RQI (Reflective QoS Indication). The RQI may be information indicating that RQoS is activated or information indicating that RQoS is activated. More specifically, the 31st identification information may be information indicating that RQoS is enabled for user data communication of downlink packets, or RQoS for user data communication of uplink packets. It may be information indicating activation. Furthermore, the 31st identification information may be information requesting creation of a QoS rule for user data communication of an uplink packet.

The 32nd identification information in this embodiment is QFI. The 32nd identification information may be information identifying a QoS flow. Further, the 32nd identification information may be information indicating a flow in which a downlink packet with RQoS enabled is transferred, or information indicating a flow in which an uplink packet is transferred after enabling RQoS. It may be. Furthermore, the 32nd identification information may be information requesting that the user data communication of the uplink packet uses the QoS flow indicated by the 32nd identification information. Furthermore, the 32nd identification information may be information requesting the creation of a QoS rule for user data communication of an uplink packet using the QoS flow indicated by the 32nd identification information.

The forty-first identification information in this embodiment is information indicating that RQoS is requested by the initiative of the UE, or that activation of RQoS is requested by the initiative of the UE. More specifically, the 41st identification information may be information requesting activation of RQoS for user data communication of an uplink packet and/or a downlink packet. Furthermore, the 41st identification information may be information requesting creation of a QoS rule for user data communication of an uplink packet and/or a downlink packet. Furthermore, the 41st identification information may be information requesting the start of the network-initiated RQoS activation procedure.

The 42nd identification information in this embodiment is QFI (QoS Flow ID). QFI is information used to identify a flow to which RQoS is applied. The 42nd identification information may be information identifying a QoS flow. Further, the 42nd identification information may be information indicating a flow in which the uplink packet and/or the downlink packet is transferred after RQoS is enabled. Further, the 42nd identification information may be information requesting use of the QoS flow indicated by the 42nd identification information for user data communication of the uplink packet and/or the downlink packet. Further, the 42nd identification information may be information requesting the creation of a QoS rule for user data communication of an uplink packet and/or a downlink packet using the QoS flow indicated by the 42nd identification information. Good. Further, the 42nd identification information may be information requesting the start of the network-initiated RQoS activation procedure, or the RQoS indicating the QoS flow used in the network-initiated RQoS activation procedure indicated by the 42nd identification information. It may be information requesting a flow.

The 51st identification information in the present embodiment is information indicating that RQoS is not permitted (rejected), or information indicating that a request for enabling RQoS is not permitted (rejected). Furthermore, the 51st identification information may be information indicating the reason why the request of UE_A10 is rejected. Incidentally, the reason that the request of UE_A10 is rejected indicates that the access network to which UE_A10 is currently connected, and/or the registration area, and/or the tracking area is not permitted to enable RQoS. The information may be information, or may be information indicating that activation of RQoS is not permitted in the uplink packet for which UE_A10 has requested activation of RQoS. Furthermore, the reason that the request of UE_A10 is rejected may be information indicating that the activation of RQoS is temporarily prohibited, or indicates that the UE-initiated RQoS activation procedure is prohibited. It may be information. The reason why the request from UE_A10 is rejected may be information indicating that the network cannot accept the RQoS activation procedure initiated by the UE, and is not limited to this.

The 62nd identification information in this embodiment is the authentication/approval information issued by the DN acquired by the SMF_A230 in the authentication/approval procedure with the DN. As a specific example, the 62nd identification information may be a service name that the DN authenticates/approves, or an approval flag. Furthermore, the 62nd identification information may be information indicating that the DN_A5 indicates that the PDU session and/or the UE_A10 and/or the application is authenticated and/or authorized. Furthermore, the 62nd identification information may be information requesting confirmation of the authentication/authorization information issued by the DN indicated by the 62nd identification information of the UE_A10 and/or the application and/or the user. Furthermore, the 62nd identification information is information requesting service use selection from the service names of the UE_A10 and/or the application and/or the user that the DN indicated by the 62nd identification information authenticates/approves. May be.

The 63rd identification information in this embodiment is information indicating a response to the authentication/authorization information issued by the DN acquired by the SMF_A230 in the authentication/authorization procedure with the DN. As a specific example, the 63rd identification information may be information indicating a message response to the 62nd identification information, information indicating the same content as the information indicated by the 62nd identification information, or the 62nd Information indicating the service name selected by the UE_A 10 from among the service names included in the identification information may be used. Furthermore, the 63rd identification information, UE_A10, and/or the application, and/or the user, is information indicating that the authentication/authorization information issued by the DN indicated by the 62nd identification information has been confirmed. Good. Furthermore, the 63rd identification information is UE_A10, and/or the application, and/or the user, and the DN indicated by the 62nd identification information indicates that the service use selection is performed from the service names authenticated/approved. It may be information indicating. Furthermore, the 63rd identification information may be DN authentication approval response information.

Next, the initial procedure in this embodiment will be described with reference to FIG. Hereinafter, the initial procedure is also referred to as this procedure, and the initial procedure (this procedure) includes the registration procedure (Registration procedure), PDU session establishment procedure (PDU session establishment procedure), and RQoS (Reflective QoS (Quality of Service)) activation procedure. Is included. Details of the registration procedure, PDU session establishment procedure, and RQoS activation procedure will be described later.

Specifically, UE_A10 transitions to the state registered in the network (RM-REGISTERED state) when each device executes the registration procedure (S800). Next, each device executes the PDU session establishment procedure (S802), and UE_A10 establishes a PDU session with DN_A5 that provides the PDU connection service via the core network_B190, and the inter-device communication is performed. Transitions to the state where the PDU session is established. Note that this PDU session is assumed to be established via the access network, UPF_A235, but is not limited to this. That is, a UPF (UPF_C239) different from the UPF_A235 may exist between the UPF_A235 and the access network. At this time, this PDU session will be established via the access network, UPF_C239, and UPF_A235.

Next, each device creates a specific QoS rule for specific user data by executing the RQoS activation procedure (S804). Furthermore, each device, based on the creation of a specific QoS rule, enters a state in which user data communication using a specific QoS flow associated with a specific QoS rule can be executed for specific user data. Transition.

Next, after transitioning to a state where user data communication using a specific QoS flow can be executed, each device executes the RQoS deactivation procedure and deletes the specific QoS rule for the specific user data. Furthermore, each device, based on the deletion of the specific QoS rule, moves to a state in which the user data communication using the specific QoS flow associated with the specific QoS rule cannot be executed for the specific user data. And transition. This procedure is complete.

Note that each device may exchange various capability information and/or various request information of each device in the registration procedure and/or the PDU session establishment procedure. Further, when each device exchanges various information and/or negotiates various requests in the registration procedure, each device does not need to exchange various information and/or negotiate various requests in the PDU session establishment procedure. In addition, each device may perform the exchange of various information and/or the negotiation of various requests in the PDU session establishment procedure if the exchange of various information and/or the negotiation of various requests is not performed in the registration procedure. In addition, each device may exchange various information and/or negotiate various requests in the PDU session establishment procedure even when performing various information exchanges and/or various request negotiations in the registration procedure.

Also, each device may execute the PDU session establishment procedure during the registration procedure or after the completion of the registration procedure. In addition, when the PDU session establishment procedure is performed during the registration procedure, the PDU session establishment request message may be included in the registration request message and may be transmitted/received, and the PDU session establishment acceptance message may be included in the registration acceptance message. The PDU session establishment completion message may be included in the registration completion message and transmitted/received, and the PDU session establishment rejection message may be included in the registration rejection message and transmitted/received. When the PDU session establishment procedure is executed during the registration procedure, each device may establish the PDU session based on the completion of the registration procedure, or the PDU session may be established between the devices. You may make a transition.

In addition, each device involved in this procedure transmits and receives each control message described in this procedure, thereby transmitting and receiving one or more identification information included in each control message, and storing each transmitted and received identification information as a context. Good.

[1.3.1. Overview of registration procedure]
First, the outline of the registration procedure will be described. The registration procedure is a procedure for UE_A10 to register on the network (access network and/or core network_B190 and/or DN (DN_A5)) led by UE_A10. UE_A10 must be registered in the network. In other words, this procedure can be executed at any timing when the power is turned on, etc. In other words, UE_A10 may start this procedure at any timing if it is in the non-registered state (RM-DEREGISTERED state). Further, each device may transit to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.

Furthermore, this procedure updates the location registration information of the UE_A10 in the network, and / or, from the UE_A10 to the network to periodically notify the state of UE_A10, and / or to update specific parameters for the UE_A10 in the network. May be the procedure.

UE_A10 may start this procedure when it moves across TAs. In other words, the UE_A 10 may start this procedure when moving to a TA different from the TA shown in the held TA list. Further, the UE_A10 may start this procedure when the running timer expires. Furthermore, the UE_A 10 may start this procedure when the context of each device needs to be updated due to disconnection or invalidation (also referred to as deactivation) of the PDU session. Further, the UE_A10 may start this procedure when the capability information and/or the preference regarding the PDU session establishment of the UE_A10 change. Furthermore, UE_A10 may start this procedure periodically. Note that the UE_A 10 is not limited to these, and if the PDU session is established, the UE_A 10 can execute this procedure at any timing.

[1.3.1.1. Example of registration procedure]
An example of the procedure for executing the registration procedure will be described with reference to FIG. In this chapter, this procedure refers to the registration procedure. Each step of this procedure will be described below.

First, UE_A10 starts the registration procedure by transmitting a Registration Request message to AMF_A240 via NRnode (also called gNB)_A122 (S900) (S902) (S904). Further, UE_A10, by including the SM (Session Management) message (e.g., PDU session establishment request message) in the registration request message, or by sending the SM message (e.g., PDU session establishment request message) together with the registration request message. By doing so, procedures for SM such as PDU session establishment procedure may be started during the registration procedure.

Specifically, UE_A10 transmits an RRC (Radio Resource Control) message including a registration request message to NR node_A122 (S900). When receiving the RRC message including the registration request message, the NR node_A 122 extracts the registration request message from the RRC message and selects AMF_A240 as the NF or the shared CP function of the routing destination of the registration request message (S902). Here, the NR node_A122 may select the AMF_A240 based on the information included in the RRC message. The NR node_A122 transmits or transfers the registration request message to the selected AMF_A240 (S904).

Note that the registration request message is a NAS (Non-Access-Stratum) message sent and received on the N1 interface. Also, the RRC message is a control message transmitted and received between the UE_A10 and the NR node_A122. Further, the NAS message is processed in the NAS layer, the RRC message is processed in the RRC layer, and the NAS layer is a layer higher than the RRC layer.

Further, UE_A10, when there are a plurality of NSI requesting registration, may send a registration request message for each NSI, or send a plurality of registration request message, included in one or more RRC message. Good. Further, the plurality of registration request messages may be included in one or more RRC messages and transmitted as one registration request message.

Here, the UE_A 10 may include one or more pieces of identification information among the first to eighth pieces of identification information, the 61st piece of identification information, and the 71st piece of identification information in the registration request message and/or the RRC message. Two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information.

Further, UE_A10, by transmitting one or more pieces of identification information among the first to eighth pieces of identification information in the registration request message and/or the RRC message, may indicate that UE_A10 supports RQoS, It may be required to transit to a state in which RQoS can be used.

Furthermore, UE_A10, by transmitting one or more pieces of identification information among the first to eighth pieces of identification information in the registration request message and/or the RRC message, may indicate that UE_A10 does not support RQoS. It may indicate that RQoS does not require transition to a usable state.

More specifically, UE_A10, the first identification information, and / or second identification information, and / or sixth identification information, and / or 7 identification information in the registration request message and / or RRC message. By including it, it may be shown that UE_A10 supports RQoS controlled via Control Plane, or request that the RQoS controlled via Control Plane transits to a usable state. May be. In this case, UE_A10, the third identification information, and / or by transmitting without identifying the eighth identification information in the registration request message and / or RRC message, RQoS controlled via User Plane UE_A10. May not be supported, or may indicate that RQoS controlled via User Plane does not require transition to a usable state.

UE_A10 transmits the first identification information, and/or the second identification information, and/or the sixth identification information, and/or the seventh identification information included in the registration request message and/or the RRC message. By doing so, it may indicate that the UE_A10 does not support RQoS controlled via the Control Plane, or indicates that the RQoS controlled via the Control Plane does not require transition to a usable state. May be.

Furthermore, UE_A10 transmits the first identification information, and/or the third identification information, and/or the sixth identification information, and/or the eighth identification information included in the registration request message and/or the RRC message. By doing so, it may indicate that UE_A10 supports RQoS controlled via User Plane, or may request that RQoS controlled via User Plane transits to a usable state. .. In this case, UE_A10, the second identification information, and / or by transmitting without identifying the seventh identification information in the registration request message and / or RRC message, RQoS controlled via Control Plane UE_A10. May not be supported, or may indicate that RQoS controlled via the Control Plane does not require transition to a usable state.

UE_A10 transmits the first identification information, and/or the third identification information, and/or the sixth identification information, and/or the eighth identification information included in the registration request message and/or the RRC message. By doing so, it is possible to indicate that UE_A10 does not support RQoS controlled via User Plane, or to indicate that RQoS controlled via User Plane does not require transition to a usable state. May be.

Further, UE_A10, the first to the third identification information, by transmitting one or more identification information and fourth identification information among the sixth to eighth identification information in association with each other, identified by the fourth identification information. For the PDU session established for the DN to be established, it may be indicated whether UE_A10 supports RQoS, or whether it is required to make a transition to an available state for RQoS. Good.

Further, UE_A10, the first to third identification information, by transmitting one or more identification information and fifth identification information among the sixth to eighth identification information in association with each other, identified by the fifth identification information. For the PDU session to be performed, it may be indicated whether the UE_A 10 supports RQoS, or whether it is required to make a transition to an available state for RQoS.

Further, UE_A10, by including one or more pieces of identification information among the first to eighth pieces of identification information in the registration request message and/or the RRC message, whether UE_A10 supports RQoS controlled by UE. This may be indicated, or it may be indicated whether or not the UE-controlled RQoS requires a transition to a usable state.

Further, UE_A10, by including one or more pieces of identification information among the first to eighth pieces of identification information in the registration request message and/or the RRC message, whether or not UE_A10 supports RQoS controlled by the network. This may be indicated, or it may be indicated whether or not RQoS controlled by the network is required to transit to a usable state.

Also, UE_A10, by transmitting the first identification information, or by transmitting the second identification information and the third identification information, or by transmitting the sixth identification information, or, By transmitting the seventh identification information and the eighth identification information, or, if two or more identification information of these identification information is configured as one or more identification information, one or more of them By transmitting the identification information, UE_A10 may support RQoS controlled via Control Plane, and UE_A10 may support RQoS controlled via User Plane, or User It may be required to make a transition to a state in which RQoS controlled via Plane can be used and a state to be able to use RQoS controlled via User Plane.

Furthermore, UE_A10, by including the 61st identification information, and/or the fourth identification information, and/or the fifth identification information in the registration request message and/or the RRC message, and transmitting the 3GPP interface (N6 interface). Service authentication/authorization by DN via the above), or the PDU session establishment authentication and authorization procedure may be requested in this procedure.

More specifically, UE_A10, by transmitting the 61st identification information and the fourth identification information in association with each other, in the PDU session established for the DN identified by the fourth identification information, 3GPP Service authentication/authorization by DN_A5 via the interface may be requested, or execution of the PDU session establishment authentication approval procedure may be requested in this procedure.

Further, UE_A10, by transmitting the 61st identification information and the 5th identification information in association with each other, in the PDU session identified by the 5th identification information, service authentication/authorization by DN_A5 via the 3GPP interface. May be requested, or the PDU session establishment authentication approval procedure may be requested to be executed in this procedure.

Furthermore, UE_A10 belongs to the network slice by transmitting by including the 71st identification information, and/or the fourth identification information, and/or the fifth identification information in the registration request message and/or the RRC message. The establishment of a PDU session may be requested, the network slice to which the PDU session belongs requested by the UE_A 10 may be indicated, or the network slice to which the PDU session is due to belong may be indicated.

More specifically, UE_A10, by transmitting the 71st identification information and the fourth identification information in association with each other, in the PDU session established for the DN identified by the fourth identification information, the network The establishment of a PDU session belonging to a slice may be requested, the network slice requested by UE_A10 to which the PDU session belongs may be indicated, or the network slice to which the PDU session is due to belong may be indicated.

Further, UE_A10, by transmitting the 71st identification information and the fifth identification information in association with each other, in the PDU session identified by the fifth identification information, request establishment of a PDU session belonging to the network slice. The UE_A10 may indicate the network slice to which the PDU session belongs, or the network slice to which the PDU session will belong.

Further, UE_A10, the first to eighth identification information, the 61st identification information, by transmitting a combination of two or more identification information of the 71st identification information, even when making a request combining the above matters. Good. Note that the matter indicated by the UE_A10 transmitting each piece of identification information is not limited to these.

Incidentally, UE_A10, the identification information of the first to eight, the 61st identification information, of the 71st identification information, which identification information to put in the registration request message, capability information of UE_A10, and / or UE policy etc. Policy and/or UE_A10 preference and/or application (upper layer). Note that the determination of which identification information is included in the registration request message by the UE_A 10 is not limited to this.

Also, UE_A10 may include these pieces of identification information in a control message (for example, a NAS message or an RRC message) different from the registration request message, and transmit the control message.

When AMF_A240 receives a registration request message and/or a control message different from the registration request message, AMF_A240 executes the first condition determination. The first condition judgment is for judging whether AMF_A240 accepts the request of UE_A10. In the first condition determination, the AMF_A240 determines whether the first condition determination is true or false. AMF_A240, if the first condition determination is true (i.e., if the network accepts the request of UE_A10), starts the procedure (A) in this procedure, if the first condition determination is false (i.e. , If the network does not accept the request from UE_A10), start the procedure (B) in this procedure.

The following describes the steps when the first condition judgment is true, that is, each step of procedure (A) in this procedure. The AMF_A240 executes the fourth condition determination and starts the procedure (A) in this procedure. The fourth condition determination is to determine whether the AMF_A240 performs SM message transmission/reception with the SMF_A230. In other words, the fourth condition determination may be performed by the AMF_A240 during this procedure to determine whether or not to execute the PDU session establishment procedure. The AMF_A240 selects the SMF_A230 and transmits/receives the SM message to/from the selected SMF_A230 when the fourth condition determination is true (that is, when the AMF_A240 transmits/receives the SM message to/from the SMF_A230). When the fourth condition determination is false (that is, when the AMF_A240 does not perform the SM message transmission/reception with the SMF_A230), they are omitted (S906). When the AMF_A240 receives the SM message indicating the refusal from the SMF_A230, the AMF_A240 may stop the procedure (A) in this procedure and start the procedure (B) in this procedure.

Further, AMF_A240, based on the reception of the registration request message from UE_A10, and/or the completion of the transmission and reception of the SM message with SMF_A230, through NR node_A122, transmits a registration acceptance (Registration Accept) message to UE_A10. (S908). For example, when the fourth condition determination is true, AMF_A240 may transmit the registration acceptance message based on the reception of the registration request message from UE_A10. Further, when the fourth condition determination is false, the AMF_A240 may send the registration acceptance message based on the completion of the transmission/reception of the SM message with the SMF_A230. Here, the registration acceptance message may be transmitted as a response message to the registration request message. Further, the registration acceptance message is a NAS message transmitted/received on the N1 interface, for example, AMF_A240 transmits to the NR node_A122 as a control message of the N2 interface, and the NR node_A122 that receives the RRC message is transmitted to the UE_A10. May be included and transmitted.

Furthermore, when the fourth condition determination is true, the AMF_A240 sends the registration acceptance message including the SM message (e.g., PDU session establishment acceptance message) or the SM message (e.g., PDU) together with the registration acceptance message. Session establishment acceptance message). This transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included together with the registration request message, and the fourth condition determination is true. AMF_A240 may indicate that the procedure for the SM has been accepted by performing such a transmission method.

Here, AMF_A240, the registration acceptance message may include one or more pieces of identification information among the eleventh to nineteenth pieces of identification information, and by including these pieces of identification information, the request of UE_A10 is accepted. May be shown. Two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information.

Further, the AMF_A240 may indicate that the network supports RQoS by transmitting one or more pieces of identification information among the 11th to 19th pieces of identification information included in the registration acceptance message, and RQoS may be used. It may indicate that the request to transition to the state has been accepted.

More specifically, AMF_A240 shall include the 11th identification information, and/or the 12th identification information, and/or the 17th identification information, and/or the 18th identification information in the registration acceptance message and transmit the same. It may indicate that the network supports RQoS controlled via Control Plane, or that the request to transition to the state where RQoS controlled via Control Plane is enabled is accepted. Good. In this case, the AMF_A240 sends the 13th identification information and/or the 19th identification information without including it in the registration acceptance message, thereby confirming that the network does not support RQoS controlled via the User Plane. It may be shown, or it may be shown that the request to transit to the state in which the RQoS controlled via the User Plane can be used is rejected.

Further, AMF_A240, by transmitting the 11th identification information, and/or the 12th identification information, and/or the 17th identification information, and/or the 18th identification information included in the registration acceptance message, Control It may indicate that the network does not support RQoS controlled via Plane, or may indicate that the request for transitioning to the state in which RQoS controlled via Control Plane can be used is rejected.

Furthermore, AMF_A240, by including the 11th identification information, and/or the 13th identification information, and/or the 17th identification information, and/or the 19th identification information in the registration acceptance message, It may indicate that the network supports RQoS controlled via Plane, or may indicate that the request for transitioning to the state where RQoS controlled via User Plane can be used has been accepted. In this case, the AMF_A240 sends the 12th identification information and/or the 18th identification information without including it in the registration acceptance message, thereby confirming that the network does not support RQoS controlled via the Control Plane. It may be shown, or it may be shown that the request to transit to the state in which the RQoS controlled through the Control Plane can be used is rejected.

Also, AMF_A240, by transmitting the 11th identification information, and/or the 13th identification information, and/or the 17th identification information, and/or the 19th identification information included in the registration acceptance message, It may indicate that the network does not support RQoS controlled via Plane, or may indicate that the request for transitioning to the state in which RQoS controlled via User Plane can be used is rejected.

Further, the AMF_A240, the 11th to 13th identification information, by transmitting one or more of the identification information of the 17th to 19th identification information and the 14th identification information in association with each other, identification by the 14th identification information. It may indicate whether the network supports RQoS for the PDU session established for the DN to be established, or whether the request to transition to the state where RQoS is available is accepted. Good.

Further, the AMF_A240, the 11th to 13th identification information, by transmitting one or more of the identification information of the 17th to 19th identification information and the 15th identification information in association with each other, the AMF_A240 identifies the 15th identification information. For the PDU session to be performed, it may be indicated whether the network supports RQoS, or whether the request for transitioning to the state where RQoS is available is accepted.

Further, the AMF_A240, by including one or more pieces of identification information among the 11th to 19th pieces of identification information in the registration acceptance message, and indicating whether or not the network supports RQoS controlled by UE. Alternatively, it may indicate whether or not a request for transitioning to a state in which UE-controlled RQoS can be used is accepted.

Further, the AMF_A240 indicates whether or not the network supports RQoS controlled by the network by transmitting one or more pieces of identification information among the 11th to 19th pieces of identification information included in the registration acceptance message. Alternatively, it may indicate whether or not the request for transitioning to the state in which RQoS controlled by the network is enabled is accepted.

Furthermore, the AMF_A240 is applied to user data communication by associating and transmitting one or more pieces of identification information among the 11th to 15th identification information and the 17th to 19th identification information and the 16th identification information. The valid period of RQoS may be indicated, the valid period of RQoS after enabling RQoS for user data communication may be indicated, or the RQoS timer started when RQoS for user data communication is activated may be displayed. It may indicate the period until expiration.

Also, UE_A10, by transmitting the eleventh identification information, or by transmitting the twelfth identification information and thirteenth identification information, or by transmitting the seventeenth identification information, or, By transmitting the eighteenth identification information and the nineteenth identification information, or, if two or more identification information of these identification information are configured as one or more identification information, one or more of them By transmitting the identification information, it may be indicated that the network supports RQoS controlled via the Control Plane and the network supports RQoS controlled via the User Plane. It may indicate that the request to transit to the state in which the RQoS controlled via the above is accepted and the request to transit to the state in which the RQoS controlled via the User Plane is available are accepted.

Further, the AMF_A240 may make a request that combines the above-mentioned matters by combining and transmitting two or more pieces of identification information among the 11th to 19th pieces of identification information. Note that the fact that AMF_A240 transmits each piece of identification information is not limited to these.

Incidentally, AMF_A240, of the 11th to 19th identification information, which identification information to put in the registration acceptance message, the received identification information, and/or network capability information, and/or operator policy, and/or Alternatively, it may be determined based on the network status and/or user registration information (user subscription).

For example, the eleventh identification information, and/or the seventeenth identification information, if the network supports RQoS, and/or the first to third identification information, and/or the sixth to eighth identification information. It may be information transmitted when received. Furthermore, the twelfth identification information, and/or the eighteenth identification information, if the network supports RQoS controlled via Control Plane, and/or the first to third identification information, and/or It may be information transmitted when the sixth to eighth identification information is received. Furthermore, the thirteenth identification information, and/or the nineteenth identification information, if the network supports RQoS controlled via User Plane, and/or the first to third identification information, and/or It may be information transmitted when the sixth to eighth identification information is received.

Furthermore, the 14th identification information may be information indicating the same DNN as the DNN indicated by the fourth identification information, or may be information indicating a different DNN. Further, the fifteenth identification information may be information indicating the same PDU session ID as the PDU session ID indicated by the fifth identification information, or may be information indicating a different PDU session ID. Note that the determination of which identification information is included in the registration acceptance message by AMF_A240 is not limited to this.

UE_A10 receives the registration acceptance message via NRnode_A122 (S908). Upon receiving the registration acceptance message, UE_A10 recognizes the contents of various identification information included in the registration acceptance message.

UE_A10 further executes the first process based on the reception of the registration acceptance message (S909). It should be noted that the UE_A 10 may perform the first process based on the transmission of the registration completion message or may perform the first process based on the completion of this procedure.

Here, the first process may be a process in which UE_A10 recognizes the matter indicated by AMF_A240. Furthermore, the first process may be a process in which the UE_A10 stores the received identification information as a context, or may be a process of transferring the received identification information to an upper layer and/or a lower layer. .. Furthermore, the first process may be a process in which the UE_A10 recognizes that the request for this procedure has been accepted.

Furthermore, when UE_A10 receives one or more pieces of identification information from the eleventh to nineteenth pieces of identification information, the first process is UE_A10, the RQoS activation procedure, at any timing after the PDU session is established. It may be a process of transitioning to an executable state or a process of starting the RQoS enabling procedure after the PDU session is established.

More specifically, if the UE_A10 receives the 11th identification information, and/or the 12th identification information, and/or the 17th identification information, and/or the 18th identification information, the first process, It may be a process of transitioning the RQoS activation procedure controlled via the Control Plane to an executable state at an arbitrary timing after the PDU session is established. Furthermore, if the UE_A10 receives the 11th identification information, and/or the 13th identification information, and/or the 17th identification information, and/or the 19th identification information, the first processing is UserPlane. It may be a process of transiting the RQoS activation procedure controlled via the VoIP session to an executable state at an arbitrary timing after the PDU session is established.

Furthermore, if UE_A10 received one or more identification information and 16th identification information among the 11th to 19th identification information, the first process is UE_A10, the 16th identification information indicates the value of RQoS. It may be a process of setting a timer value. The first process is not limited to these processes.

Next, the UE_A10 transmits a Registration Complete message to the AMF_A240 based on the reception of the registration acceptance message and/or the completion of the first process (S910). Incidentally, when the UE_A10 receives the SM message such as the PDU session establishment acceptance message, the registration completion message may be transmitted by including the SM message such as the PDU session establishment completion message, or by including the SM message. , May indicate to complete the procedure for SM. Here, the registration completion message may be transmitted as a response message to the registration acceptance message. Further, the registration completion message is a NAS message transmitted and received on the N1 interface.For example, UE_A10 transmits to the NR node_A122 by including it in the RRC message, and the NR node_A122 that receives this transmits the N2 interface to the AMF_A240. It may be transmitted as a control message.

AMF_A240 receives the registration completion message (S910). Further, each device completes the procedure (A) in this procedure based on the transmission and reception of the registration acceptance message and/or the registration completion message.

Next, the step when the first condition judgment is false, that is, each step of the procedure (B) in this procedure will be described. The AMF_A240 starts the procedure of (B) in this procedure by transmitting a Registration Reject message to the UE_A10 via the NR node_A122 (S912). Here, the registration refusal message may be transmitted as a response message to the registration request message. Further, the registration rejection message is a NAS message transmitted/received on the N1 interface.For example, AMF_A240 transmits it to the NR node_A122 as a control message of the N2 interface, and the NR node_A122 that receives this message is an RRC message to the UE_A10. May be included and transmitted. The registration refusal message transmitted by AMF_A240 is not limited to this as long as it is a message that rejects the request of UE_A10.

Note that the procedure (B) in this procedure may be started when the procedure (A) in this procedure is stopped. In the procedure of (A), if the fourth condition determination is true, the AMF_A240 may send a registration rejection message including an SM message indicating rejection such as a PDU session establishment rejection message, or may reject the rejection. The inclusion of the implied SM message may indicate that the procedure for SM has been rejected. In that case, the UE_A 10 may further receive an SM message indicating rejection such as a PDU session establishment rejection message, or may recognize that the procedure for SM has been rejected.

Here, AMF_A240, the registration rejection message, the identification information of the 21st to 29th, may include one or more identification information of the 72nd identification information, by including these identification information, the request of UE_A10 May be rejected. Two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information.

Further, the AMF_A240 may indicate that the network does not support RQoS by transmitting one or more pieces of identification information out of the 21st to 29th identification information included in the registration refusal message, or RQoS can be used. It may indicate that the request to transition to the state has been rejected.

More specifically, AMF_A240 is the 21st identification information, and/or the 22nd identification information, and/or the 23rd identification information, and/or the 27th identification information, and/or the 28th identification information. By including it in the registration refusal message, it may indicate that the network does not support RQoS controlled via Control Plane, or transit to a state where RQoS controlled via Control Plane can be used. It may indicate that the request was rejected. In this case, the AMF_A240 sends the 24th identification information and/or the 29th identification information without including it in the registration refusal message so that the network supports RQoS controlled via the User Plane. It may be shown, or it may be shown that the request to transit to the state in which the RQoS controlled through the User Plane can be used is accepted.

Further, AMF_A240, the 21st identification information, and / or 22nd identification information, and / or 24th identification information, and / or 27th identification information, and / or 29th identification information registration refusal message. , It may indicate that the network does not support RQoS controlled via User Plane, or a request to transition to a state where RQoS controlled via User Plane can be used is rejected. You may indicate that it was done. In this case, AMF_A240 may indicate that the network supports RQoS controlled via Control Plane by transmitting without including the 23rd identification information and/or the 28th identification information. However, it may indicate that the request to transit to the state in which the RQoS controlled through the Control Plane can be used has been accepted.

Further, the AMF_A240 transmits the 21st identification information, and/or associates the 22nd to 24th identification information and the 27th to 29th identification information with one or more identification information and the 25th identification information. Indicates that the network does not support RQoS for the PDU session established for the DN identified by the fourth identification information and/or the 25th identification information received by AMF_A240. It may indicate that the request for transitioning to the RQoS enabled state has been rejected.

Further, the AMF_A240 transmits the 21st identification information, and/or associates the 26th identification information with one or more identification information of the 22nd to 24th identification information and the 27th to 29th identification information. By transmitting, by the fifth identification information received by AMF_A240, and / or for the PDU session identified by the 26th identification information, may indicate that the network does not support RQoS, RQoS is It may indicate that the request to transition to the usable state has been rejected.

Further, AMF_A240, by including one or more pieces of identification information among the 21st to 29th pieces of identification information in the registration refusal message, UE_A10 is currently in a registration area (Registration Area: RA), and/or For the tracking area (Tracking Area: TA), it may be indicated that the network does not support RQoS, or that the request to transit to a state in which RQoS can be used is rejected.

Further, AMF_A240, by including one or more pieces of identification information among the 21st to 29th pieces of identification information in the registration refusal message, and transmitting the access network to which UE_A10 is currently connected, the network does not support RQoS. May be indicated, or that the request to transit to the state in which RQoS is available may be rejected.

Furthermore, AMF_A240 may indicate that the network does not support RQoS controlled by UE by transmitting one or more pieces of identification information among the 21st to 29th pieces of identification information included in the registration rejection message. , It may indicate that the request to transit to the state in which UE-controlled RQoS is enabled is rejected.

Furthermore, the AMF_A240 may indicate that the network does not support RQoS controlled by the network by transmitting one or more pieces of identification information included in the 21st to 29th identification information in the registration refusal message. , It may indicate that the request to transit to a network-initiated controlled RQoS enabled state is rejected.

Also, UE_A10, by transmitting the 21st identification information, or, by transmitting the 22nd identification information, or by transmitting the 23rd identification information and the 24th identification information, or, By transmitting the 27th identification information, or by transmitting the 28th identification information and the 29th identification information, or, two or more identification information of these identification information is configured as one or more identification information If more than one of them is transmitted, the network does not support RQoS controlled via Control Plane, and the network does not support RQoS controlled via User Plane. May not be supported, or the request to transit to the state where RQoS controlled via Control Plane can be used is rejected, and the state where RQoS controlled via User Plane becomes available It may indicate that the request to transition is rejected.

Furthermore, AMF_A240, by including the 72nd identification information, and/or the 25th identification information, and/or the 26th identification information in the registration refusal message, thereby establishing the PDU session belonging to the network slice. It may indicate that the request was rejected, the network slice that the PDU session was not allowed to belong to, or the network slice that the PDU session was denied to belong to.

More specifically, the AMF_A240 transmits the 72nd identification information and the 25th identification information in association with each other, in the PDU session established for the DN identified by the 25th identification information, in the network. It may indicate that the request to establish the PDU session belonging to the slice has been rejected, or it may indicate a network slice that is not allowed to belong to the PDU session.

Further, the AMF_A240 sends the 61st identification information and the 26th identification information in association with each other, thereby requesting the establishment of the PDU session belonging to the network slice in the PDU session identified by the 26th identification information. May be rejected, or it may indicate a network slice that is not allowed to belong to the PDU session.

Furthermore, AMF_A240, by including the 72nd identification information included in the registration rejection message, in the registration area to which UE_A10 currently belongs, and/or in the tracking area, the establishment of the PDU session belonging to the network slice is confirmed. It may indicate that the request has been denied, or it may indicate a network slice that is not allowed to belong to the PDU session.

Furthermore, AMF_A240, by including the 72nd identification information in the registration reject message, in the access network to which UE_A10 is currently connected, the request for establishment of the PDU session belonging to the network slice is rejected. It may indicate a network slice that is not permitted to belong to the PDU session.

Furthermore, the AMF_A240 may indicate the value of the first timer by including the 72nd identification information in the registration refusal message, and after completing this procedure, the same procedure as this procedure should be performed again. You may indicate whether or not it is.

Furthermore, the AMF_A240 may make a request that combines the above-mentioned matters by transmitting a combination of two or more pieces of identification information of the 21st to 29th identification information and/or the 72nd identification information. Note that the fact that AMF_A240 transmits each piece of identification information is not limited to these.

Incidentally, AMF_A240 is the identification information received from the 21st to 29th identification information and the 72nd identification information, which identification information is to be included in the registration refusal message, and/or the capability information of the network, and/or It may be determined based on a policy such as an operator policy and/or the state of the network.

For example, the 21st identification information may be information transmitted when the network does not support RQoS and/or when one or more identification information items among the identification information items 1 to 8 are received. .. Furthermore, the 22nd identification information, and / or 27th identification information, if the network does not support RQoS, and / or 1 to 3 identification information, and / or 6 to 8 identification information It may be information transmitted when received. Furthermore, the 23rd identification information, and / or 28th identification information, if the network supports RQoS controlled via Control Plane, and / or 1 to 3 identification information, and / or It may be information transmitted when the sixth to eighth identification information is received. Furthermore, the 24th identification information, and/or the 29th identification information, when the network supports RQoS controlled via User Plane, and/or the first to third identification information, and/or It may be information transmitted when the sixth to eighth identification information is received.

Furthermore, the 25th identification information may be information indicating the same DNN as the DNN indicated by the fourth identification information. Furthermore, the 26th identification information may be information indicating the same PDU session ID as the PDU session ID indicated by the fifth identification information. Further, the 72nd identification information may be information transmitted when the 71st identification information is received and/or when the network slice indicated by the 71st identification information is not permitted by the network. The determination by AMF_A240 which identification information is included in the registration refusal message is not limited to this.

UE_A10 receives the registration refusal message. UE_A10 performs the second process based on the reception of the registration refusal message (S914). Further, the UE_A10 may perform the second process based on the completion of this procedure.

Here, the second process may be a process in which UE_A10 recognizes the matter indicated by AMF_A240. Furthermore, the second process may be a process in which the UE_A10 stores the received identification information as a context, or may be a process of transferring the received identification information to an upper layer and/or a lower layer. .. Further, the second process may be a process in which the UE_A10 recognizes that the request for this procedure is rejected.

Furthermore, if UE_A10 receives one or more pieces of identification information from the 21st to 29th identification information, the second process is UE_A10, a process of transitioning to a state in which the RQoS enabling procedure is not executable, or RQoS. It may be to maintain the non-application state.

More specifically, if the UE_A10 receives the 22nd identification information, and/or the 23rd identification information, and/or the 27th identification information, and/or the 28th identification information, the second process, It may be a process of transiting to a state in which the RQoS activation procedure controlled via the Control Plane is not executable. Furthermore, if the UE_A10 receives the 22nd identification information, and/or the 24th identification information, and/or the 27th identification information, and/or the 29th identification information, the second process is the UserPlane. The processing may be a process of transiting to a state in which the RQoS enabling procedure controlled via the non-executable state.

Furthermore, if the UE_A10 receives the 72nd identification information, the second process, UE_A10 may be a process of setting the value indicated by the 72nd identification information as the first timer value, the timer value. It may be a process of starting the first timer having set. Furthermore, when the UE_A10 receives the 72nd identification information, the second process may be a process of executing one or more of the first to eleventh behaviors.

Further, the second process may be a process in which the UE_A10 may start the procedure again after a certain period of time, and a process in which the request of the UE_A10 transits to a limited state. The second process is not limited to these processes.

Further, UE_A10 may recognize that the request of UE_A10 is rejected by receiving the registration refusal message or by not receiving the registration acceptance message. Each device completes the procedure (B) in this procedure based on the transmission and reception of the registration refusal message.

Each device completes this procedure (registration procedure) based on the completion of procedure (A) or (B) in this procedure. Each device may transition to the state (RM_REGISTERED state) in which UE_A10 is registered in the network based on the completion of the procedure (A) during this procedure, or the procedure (B) during this procedure. The UE_A10 may maintain the state (RM_DEREGISTERED state) in which the UE_A10 is not registered in the network based on the completion of the. Further, the transition of each device to each state may be performed based on the completion of this procedure or may be performed based on the establishment of the PDU session.

Furthermore, each device may perform processing based on the identification information transmitted and received in this procedure based on the completion of this procedure. In other words, the UE_A 10 may perform the first process or the second process based on the completion of this procedure.

Also, the first condition determination may be executed based on the identification information and/or the subscriber information and/or the operator policy included in the registration request message. For example, the first condition determination may be true when the network permits the request of UE_A10. Further, the first condition determination may be false if the network does not permit the request of UE_A10. Further, the first condition determination, the network of the UE_A10 registration destination, and / or devices in the network, the function requested by UE_A10 may be true if it supports, false if it does not support. Good. Furthermore, the first condition determination may be true when the network is determined to be in a congestion state, and may be false when it is determined that the network is not in a congestion state. The condition that determines whether the first condition determination is true or false is not limited to the condition described above.

Also, the fourth condition determination may be executed based on whether the AMF_A240 has received the SM, or may be executed based on whether the registration request message includes the SM message. For example, the fourth condition determination may be true if the AMF_A240 receives the SM and/or the SM message is included in the registration request message, if the AMF_A240 does not receive the SM, and / Or it may be false if the SM message was not included in the registration request message. The condition that determines whether the fourth condition determination is true or false is not limited to the condition described above.

[1.3.2. Overview of PDU session establishment procedure]
Next, an outline of a PDU session establishment procedure performed to establish a PDU session for DN_A5 will be described. Hereinafter, the PDU session establishment procedure is also referred to as this procedure. This procedure is a procedure for each device to establish a PDU session. It should be noted that each device may execute this procedure in a state where the registration procedure is completed, or may be executed during the registration procedure. Further, each device may start this procedure in the registered state, or may start this procedure at any timing after the registration procedure. Further, each device may establish a PDU session based on the completion of the PDU session establishment procedure. Furthermore, each device may establish a plurality of PDU sessions by executing this procedure a plurality of times.

[1.3.2.1. PDU session establishment procedure example]
An example of a procedure for executing the PDU session establishment procedure will be described with reference to FIG. Each step of this procedure will be described below. First, UE_A10 starts a PDU session establishment procedure by transmitting a PDU Session Establishment Request message (PDU Session Establishment Request) to SMF_A230 via NR node_A122 and AMF_A240 (S1000) (S1002) (S1004).

Specifically, UE_A10 transmits a PDU session establishment request message to AMF_A240 via NR node_A122 using the N1 interface (S1000). Upon receiving the PDU session establishment request message, the AMF_A240 selects SMF_A230 as the NF of the routing destination of the PDU session establishment request message (S1002), and transmits the PDU session establishment request message to the selected SMF_A230 using the N11 interface, or Transfer (S1004). Here, the AMF_A240 may select the routing destination SMF_A230 based on the information included in the PDU session establishment request message. More specifically, AMF_A240 is each identification information acquired based on the reception of the PDU session establishment request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network The routing destination SMF_A 230 may be selected based on the state and/or the context that the AMF_A 240 already holds.

Note that the PDU session establishment request message may be a NAS message. Further, the PDU session establishment request message is not limited to this as long as it is a message requesting establishment of a PDU session.

Here, UE_A10, the PDU session establishment request message, the identification information of the first to eighth, 61st identification information, may include one or more identification information of the 71st identification information, these identification information May be included to indicate the request of UE_A10. Two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information.

Furthermore, UE_A10 may indicate that R_QoS is supported by UE_A10 by including one or more pieces of identification information among the first to eighth pieces of identification information in the PDU session establishment request message and used by RQoS. It may be required to transition to a possible state.

Further, UE_A10 may indicate that UE_A10 does not support RQoS by transmitting by including one or more pieces of identification information in the PDU session establishment request message among the first to eighth pieces of identification information, and used by RQoS. It may indicate that the transition to a possible state is not required.

More specifically, the UE_A10 transmits the first identification information, and/or the second identification information, and/or the sixth identification information, and/or the seventh identification information included in the PDU session establishment request message. By doing so, it may indicate that UE_A10 supports RQoS controlled via Control Plane, or may request that RQoS controlled via Control Plane transits to a usable state. .. In this case, UE_A10 does not support RQoS controlled via User Plane by transmitting without including the third identification information and/or the eighth identification information in the PDU session establishment request message. This may be indicated, or it may be indicated that RQoS controlled via the User Plane is not required to transit to a usable state.

Also, UE_A10, by including the first identification information, and / or second identification information, and / or sixth identification information, and / or seventh identification information included in the PDU session establishment request message. , It may indicate that UE_A10 does not support RQoS controlled via Control Plane, or may indicate that RQoS controlled via Control Plane does not require transition to an available state. ..

Furthermore, UE_A10, by including the first identification information, and / or third identification information, and / or sixth identification information, and / or eighth identification information in the PDU session establishment request message by transmitting. , UE_A10 may support RQoS controlled via User Plane, or may request that RQoS controlled via User Plane transits to a usable state. In this case, UE_A10 does not support RQoS controlled via Control Plane by transmitting the second identification information and/or the seventh identification information without including it in the PDU session establishment request message. This may be indicated, or it may be indicated that RQoS controlled via the Control Plane does not require transition to an available state.

In addition, UE_A10, by including the first identification information, and / or third identification information, and / or sixth identification information, and / or eighth identification information in the PDU session establishment request message by transmitting. , It may indicate that UE_A10 does not support RQoS controlled via User Plane, or it may indicate that RQoS controlled via User Plane does not require transition to an available state. ..

Further, UE_A10, by including one or more pieces of identification information among the first to eighth pieces of identification information in the PDU session establishment request message, and indicating whether UE_A10 supports RQoS controlled by UE. Alternatively, it may indicate whether or not to request the RQoS controlled by UE to transit to a usable state.

Further, UE_A10, by transmitting one or more pieces of identification information among the first to eighth pieces of identification information included in the PDU session establishment request message, indicating whether or not UE_A10 supports RQoS controlled by network initiative. Alternatively, it may indicate whether or not the network-controlled RQoS requires transition to a usable state.

Also, UE_A10, by transmitting the first identification information, or by transmitting the second identification information and the third identification information, or by transmitting the sixth identification information, or, By transmitting the seventh identification information and the eighth identification information, or, if two or more identification information of these identification information is configured as the identification information of one or more identification information, among them By transmitting one or more pieces of identification information, UE_A10 supports RQoS controlled via Control Plane, and may indicate that UE_A10 supports RQoS controlled via User Plane, Alternatively, it may be requested to transit to a state where RQoS controlled via the User Plane can be used and to transit to a state where RQoS controlled via the User Plane can be used.

Further, UE_A10, by including the 61st identification information, and / or fourth identification information, and / or fifth identification information included in the PDU session establishment request message, 3GPP interface (N6 interface and the like). You may request service authentication/authorization by DN via this, or you may request to perform the PDU session establishment authentication authorization procedure in this procedure.

Furthermore, UE_A10, by including the 71st identification information, and / or fourth identification information, and / or fifth identification information included in the PDU session establishment request message, the PDU session belonging to the network slice. The establishment may be requested, the network slice to which the PDU session belongs, which the UE_A10 requests, may be indicated, or the network slice to which the PDU session is due to belong may be indicated.

Further, UE_A10, by transmitting the 61st identification information and the fifth identification information in association with each other, in the PDU session identified by the fifth identification information, request establishment of a PDU session belonging to the network slice. The UE_A10 may indicate the network slice to which the PDU session belongs, or the network slice to which the PDU session will belong.

Incidentally, UE_A10, the identification information of the first to eight, the 61st identification information, of the 71st identification information, which identification information to put in the PDU session establishment request message, capability information of UE_A10, and / or UE It may be determined based on a policy such as a policy and/or a preference of UE_A10 and/or an application (upper layer). Note that the determination of which identification information is included in the PDU session establishment request message by the UE_A 10 is not limited to this.

ㆍSMF_A230 receives the PDU session establishment request message and executes the third condition judgment. The third condition determination is for the SMF_A230 to determine whether to accept the request of the UE_A10. In the third condition determination, the SMF_A230 determines whether the third condition determination is true or false. The SMF_A230 starts the procedure (A) in this procedure when the third condition determination is true, and starts the procedure (B) in this procedure when the third condition determination is false. The steps when the third condition judgment is false will be described later.

The following describes the steps when the third condition judgment is true, that is, each step of procedure (A) in this procedure.

Here, SMF_A230, if the PDU session establishment request message includes SM PDU DN Request Container that includes the 61st identification information, and the 61st identification information conforms to the local policy and/or user subscriber information. , PDU session establishment authentication approval procedure is started (S1005). On the other hand, when the SMPDUN Request Request Container is not included in the PDU session establishment request message, the PDU session establishment authentication approval procedure is omitted. Details of the PDU session establishment authentication approval procedure will be described later.

Next, the SMF_A230 that started the PDU session establishment authentication approval procedure (S1005) sends a session establishment request message to the selected UPF_A235 (S1006), and starts the procedure of (A) in this procedure. .. Note that the SMF_A 230 may start the procedure (B) in this procedure based on the completion of the PDU session establishment authentication approval procedure, without starting the procedure (A) in this procedure.

Here, SMF_A230, each identification information acquired based on the reception of the PDU session establishment request message, and / or network capability information, and / or subscriber information, and / or operator policy, and / or network status, And/or one or more UPF_A 235 may be selected based on the context that SMF_A 230 already holds. When a plurality of UPF_A235 are selected, the SMF_A230 may send a session establishment request message to each UPF_A235.

UPF_A235 receives the session establishment request message and creates a context for the PDU session. Further, the UPF_A 235 receives the session establishment request message and/or transmits the session establishment response (Session Establishment response) message to the SMF_A 230 based on the creation of the context for the PDU session (S1008). Further, SMF_A230 receives the session establishment response message. The session establishment request message and the session establishment response message may be control messages transmitted and received on the N4 interface. Further, the session establishment response message may be a response message to the session establishment request message.

Further, the SMF_A230 may perform the address assignment of the address assigned to the UE_A10 based on the reception of the PDU session establishment request message and/or the selection of the UPF_A235 and/or the reception of the session establishment response message. The SMF_A 230 may perform the address assignment of the address assigned to the UE_A 10 during the PDU session establishment procedure or after the PDU session establishment procedure is completed.

Specifically, when allocating an IPv4 address without using DHCPv4, the SMF_A230 may perform address allocation during the PDU session establishment procedure or may send the allocated address to UE_A10. Furthermore, SMF_A230, when assigning an IPv4 address using DHCPv4 or DHCPv6 or SLAAC (Stateless Address Autoconfiguration), and/or an IPv6 address, and/or an IPv6 prefix, after the PDU session establishment procedure, the address may be assigned, The assigned address may be sent to UE_A10. The address allocation performed by SMF_A230 is not limited to these.

Further, SMF_A230 may include the assigned address in the PDU session establishment acceptance message and send it to UE_A10 based on the completion of the address assignment of the address to be assigned to UE_A10, or send it to UE_A10 after the completion of the PDU session establishment procedure. You may.

The SMF_A230 receives the PDU session establishment request message, and/or selects the UPF_A235, and/or receives the session establishment response message, and/or based on the completion of the address assignment of the address assigned to the UE_A10, to the UE_A10 via the AMF_A240. Send a PDU session establishment acceptance message (S1010).

Specifically, the SMF_A230 sends a PDU session establishment acceptance message to the AMF_A240 using the N11 interface, and the AMF_A240 receiving the PDU session establishment acceptance message sends a PDU session establishment acceptance message to the UE_A10 using the N1 interface. ..

If the PDU session is a PDN connection, the PDU session establishment acceptance message may be a PDN connection acceptance (PDN connectivity accept) message. Further, the PDU session establishment acceptance message may be a NAS message transmitted/received on the N11 interface and the N1 interface. The PDU session establishment acceptance message is not limited to this, and may be a message indicating that the establishment of the PDU session has been accepted.

Here, SMF_A230, the PDU session establishment acceptance message may include one or more pieces of identification information from the 11th to 19th identification information, by including these pieces of identification information, the request of UE_A10 was accepted. May be indicated. Two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information.

Further, the SMF_A230 may indicate that the network supports RQoS by transmitting one or more pieces of identification information among the 11th to 19th pieces of identification information included in the PDU session establishment acceptance message, and may be used by RQoS. It may indicate that the request to transition to a possible state has been accepted.

More specifically, the SMF_A230 transmits the 11th identification information, and/or the 12th identification information, and/or the 17th identification information, and/or the 18th identification information in the PDU session establishment acceptance message. By doing so, it may be indicated that the network supports RQoS controlled via Control Plane, or that the request to transition to the state where RQoS controlled via Control Plane can be used is accepted. May be shown. In this case, the SMF_A230 sends the 13th identification information and/or the 19th identification information without including it in the PDU session establishment acceptance message, so that the network does not support RQoS controlled via the User Plane. This may be indicated, or it may be indicated that the request for transitioning to the state in which RQoS controlled via the User Plane can be used is rejected.

Further, SMF_A230, by including the 11th identification information, and/or the 12th identification information, and/or the 17th identification information, and/or the 18th identification information in the PDU session establishment acceptance message. , It may indicate that the network does not support RQoS controlled via Control Plane, or it may indicate that the request to transition to the state where RQoS controlled via Control Plane can be used is rejected. Good.

Further, SMF_A230, by including the 11th identification information, and/or the 13th identification information, and/or the 17th identification information, and/or the 19th identification information in the PDU session establishment acceptance message. , May indicate that the network supports RQoS controlled via User Plane, or may indicate that a request to transition to a state in which RQoS controlled via User Plane can be used has been accepted. .. In this case, the SMF_A230 transmits the 12th identification information and/or the 18th identification information without including it in the registration acceptance message, thereby confirming that the network does not support RQoS controlled via the Control Plane. It may be shown or it may be shown that the request to transit to the state in which RQoS controlled via the Control Plane can be used is rejected.

Further, SMF_A230, by including the 11th identification information, and/or the 13th identification information, and/or the 17th identification information, and/or the 19th identification information in the PDU session establishment acceptance message. , May indicate that the network does not support RQoS controlled via User Plane, or may indicate that the request to transition to the state where RQoS controlled via User Plane can be used is rejected. ..

Further, the SMF_A230 identifies the 14th identification information by transmitting the 11th to 13th identification information, the 1st or more identification information of the 17th to 19th identification information and the 14th identification information in association with each other. It may indicate whether the network supports RQoS for the PDU session established for the DN to be established, or whether the request to transition to the state where RQoS is available is accepted. Good.

Further, the SMF_A230 identifies the 15th identification information by transmitting the 11th to 13th identification information and the 15th identification information by correlating one or more identification information among the 17th to 19th identification information. For the PDU session to be performed, it may be indicated whether or not the network supports RQoS, or it may be indicated whether or not the request to transit to the state in which RQoS is available is accepted.

Further, SMF_A230 indicates whether the network supports UE-controlled RQoS by transmitting one or more pieces of identification information among the 11th to 19th pieces of identification information included in the PDU session establishment acceptance message. Alternatively, it may indicate whether or not the request to make a transition to a state in which RQoS controlled by the UE is enabled is accepted.

Further, the SMF_A230 indicates whether or not the network supports RQoS controlled by the network by transmitting one or more pieces of identification information among the 11th to 19th pieces of identification information included in the PDU session establishment acceptance message. Alternatively, it may indicate whether or not a request to transit to a state in which RQoS controlled by the network is enabled is accepted.

Further, the SMF_A230 is applied to user data communication by associating and transmitting one or more pieces of identification information among the eleventh to fifteenth identification information and the seventeenth to nineteenth identification information and the sixteenth identification information. The RQoS valid period may be indicated, the RQoS effective period may be indicated after enabling RQoS for user data communication, or the RQoS timer started when RQoS is enabled for user data communication may be indicated. It may indicate the period until expiration.

Also, UE_A10, by transmitting the eleventh identification information, or by transmitting the twelfth identification information and thirteenth identification information, or by transmitting the seventeenth identification information, or, By transmitting the eighteenth identification information and the nineteenth identification information, or when two or more identification information items of these identification information items are configured as the identification information items of one or more identification information items, among them. By transmitting one or more pieces of identification information, it may be shown that the network supports RQoS controlled via Control Plane, and that the network supports RQoS controlled via User Plane, Indicates that the request to transition to the state where RQoS controlled via the Control Plane can be used has been accepted, and the request to transition to the state where RQoS controlled to be controlled via the User Plane has been accepted. Good.

Furthermore, the SMF_A230 may make a request that combines the above-mentioned matters by transmitting a combination of two or more pieces of identification information among the 11th to 19th pieces of identification information. It should be noted that the matters indicated by the SMF_A 230 transmitting each piece of identification information are not limited to these.

Incidentally, SMF_A230, the identification information received from the 11th to 19th identification information, which identification information to put in the PDU session establishment acceptance message, and/or the capability information of the network, and/or operator policy, etc. It may be determined based on the policy and/or the state of the network.

Furthermore, the 14th identification information may be information indicating the same DNN as the DNN indicated by the fourth identification information, or may be information indicating a different DNN. Further, the fifteenth identification information may be information indicating the same PDU session ID as the PDU session ID indicated by the fifth identification information, or may be information indicating a different PDU session ID. Note that the determination by SMF_A230 which identification information is included in the PDU session establishment acceptance message is not limited to this.

UE_A10 receives the PDU session establishment acceptance message. Upon receiving the PDU session establishment acceptance message, UE_A10 recognizes the contents of various identification information included in the PDU session establishment acceptance message.

UE_A10 further executes the third processing based on the reception of the PDU session establishment acceptance message (S1012). Note that the UE_A 10 may perform the third process based on the transmission of the PDU session establishment completion message or may be performed based on the completion of this procedure.

Here, the third process may be a process in which the UE_A10 recognizes the matter indicated by the SMF_A230. Furthermore, the third process may be a process in which the UE_A10 stores the received identification information as a context, or may be a process of transferring the received identification information to an upper layer and/or a lower layer. .. Furthermore, the third process may be a process in which the UE_A10 recognizes that the request for this procedure has been accepted.

Furthermore, when UE_A10 receives one or more pieces of identification information from among the eleventh to nineteenth pieces of identification information, the third process is a process in which UE_A10 transitions the RQoS enabling procedure to an executable state at any timing. It may be present or it may be the process of starting the RQoS activation procedure.

More specifically, if the UE_A10 receives the 11th identification information, and/or the 12th identification information, and/or the 17th identification information, and/or the 18th identification information, the third processing is, It may be a process of transitioning the RQoS activation procedure controlled via the Control Plane to a state in which it can be executed at an arbitrary timing. Furthermore, if the UE_A10 receives the 11th identification information, and/or the 13th identification information, and/or the 17th identification information, and/or the 19th identification information, the third processing is the UserPlane. It may be a process of transiting the RQoS enabling procedure controlled via the state to an executable state at an arbitrary timing.

Furthermore, if UE_A10 receives one or more identification information and 16th identification information among the 11th to 19th identification information, the third process is UE_A10, the 16th identification information indicates the value of RQoS. It may be a process of setting a timer value. The third process is not limited to these processes.

Next, UE_A10 receives the PDU session establishment acceptance message, and / or based on the completion of the third process, transmits a PDU session establishment completion message to SMF_A230 via AMF_A240 (SDU session establishment complete) message (S1014). .. Further, the SMF_A 230 receives the PDU session establishment completion message and executes the second condition determination.

Specifically, UE_A10 transmits a PDU session establishment completion message to AMF_A240 using the N1 interface, and AMF_A240 that has received the PDU session establishment completion message sends a PDU session establishment completion message to SMF_A230 using the N11 interface. ..

When the PDU session is a PDN connection, the PDU session establishment complete message may be a PDN connection complete message or a default EPS bearer context activation accept message. Further, the PDU session establishment completion message may be a NAS message transmitted/received on the N1 interface and the N11 interface. Further, the PDU session establishment completion message may be a response message to the PDU session establishment acceptance message, and is not limited to this, and may be a message indicating that the PDU session establishment procedure is completed.

The second condition determination is for SMF_A230 to determine the type of message on the N4 interface that is sent and received. When the second condition determination is true, SMF_A230 sends a session modification request message (SessionModification request) to UPF_A235 (S1018), and further, session modification acceptance (Session Modificationresponse) sent by UPF_A235 that received the session modification request message. ) Receive the message (S1020). If the second condition determination is false, SMF_A230 sends a session establishment request message to UPF_A235 (S1018), and further receives a session change accept message sent by UPF_A235 that received the session establishment request message (S1020). ..

Each device transmits/receives a PDU session establishment completion message, and/or a session change response message, and/or a session establishment response message, and/or sends/receives an RA based on (A) Complete the procedure.

Next, the step when the third condition judgment is false, that is, each step of the procedure (B) in this procedure will be described. The SMF_A230 transmits a PDU session establishment rejection message to the UE_A10 via the AMF_A240 (S1022), and starts the procedure (B) in this procedure.

Specifically, the SMF_A230 sends a PDU session establishment rejection message to the AMF_A240 using the N11 interface, and the AMF_A240 that receives the PDU session establishment request message sends a PDU session establishment rejection message to the UE_A10 using the N1 interface. ..

Note that if the PDU session is a PDN connection, the PDU session establishment rejection message may be a PDN connectivity reject message. Further, the PDU session establishment rejection message may be a NAS message transmitted and received on the N11 interface and the N1 interface. Further, the PDU session establishment rejection message is not limited to this, and may be a message indicating that the establishment of the PDU session is rejected.

Here, SMF_A230, in the PDU session establishment rejection message, the 21st to 29th identification information, may include one or more identification information of the 72nd identification information, by including these identification information, UE_A10 Request may have been denied. Two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information.

Further, the SMF_A230 may indicate that the network does not support RQoS by transmitting one or more pieces of identification information out of the 21st to 29th identification information included in the PDU session establishment rejection message and used by RQoS. It may indicate that the request to transition to a possible state has been rejected.

More specifically, the SMF_A230 is the 21st identification information, and/or the 22nd identification information, and/or the 23rd identification information, and/or the 27th identification information, and/or the 28th identification information. It may be possible to indicate that the network does not support RQoS controlled via Control Plane by including it in the PDU session establishment rejection message, and RQoS controlled via Control Plane can be used. It may indicate that the request to transition is rejected. In this case, the SMF_A230 transmits the 24th identification information and/or the 29th identification information without including it in the registration refusal message, so that the network supports RQoS controlled via the User Plane. It may be shown or it may be shown that the request to transit to the state in which RQoS controlled via the User Plane can be used is accepted.

Furthermore, the SMF_A230 establishes the PDU session with the 21st identification information, and/or the 22nd identification information, and/or the 24th identification information, and/or the 27th identification information, and/or the 29th identification information. It may be indicated that the network does not support RQoS controlled via User Plane by including it in the rejection message and a request to transit to a state where RQoS controlled via User Plane can be used. You may indicate that you have been rejected. In this case, the SMF_A 230 may indicate that the network supports RQoS controlled via the Control Plane by transmitting without including the 23rd identification information and/or the 28th identification information. However, it may indicate that the request for transitioning to the state in which RQoS controlled through the Control Plane can be used has been accepted.

Further, the SMF_A230 transmits the 21st identification information, and/or the 22nd to 24th identification information, and the 27th to 29th identification information one or more of the identification information and the 25th identification information are associated with each other. The SMF_A230 indicates that the network does not support RQoS for the PDU session established for the DN identified by the fourth identification information and/or the 25th identification information. It may indicate that the request for transitioning to the RQoS enabled state has been rejected.

Further, the SMF_A230 transmits the 21st identification information, and/or the 22nd to 24th identification information, the 27th to 29th identification information, and one or more of the identification information and the 26th identification information are associated with each other. May be transmitted to indicate that the network does not support RQoS for the PDU session identified by the fifth identification information and the 26th identification information received by SMF_A230, or RQoS can be used. It may indicate that the request to transition to the state has been rejected.

Furthermore, SMF_A230, by including one or more pieces of identification information among the 21st to 29th pieces of identification information in the PDU session establishment rejection message, the registration area to which UE_A10 currently belongs, and/or the tracking area. On the other hand, it may indicate that the network does not support RQoS, or it may indicate that the request for transitioning to the RQoS enabled state has been rejected.

Further, SMF_A230, by including one or more pieces of identification information in the 21st to 29th pieces of identification information in the PDU session establishment rejection message, and transmitting the RQoS to the access network to which UE_A10 is currently connected. It may indicate that it is not supported, or that the request to transition to the state in which RQoS is available is rejected.

Further, SMF_A230, by including one or more pieces of identification information among the 21st to 29th pieces of identification information in the PDU session establishment rejection message, and indicating that the network does not support UE-controlled RQoS. Alternatively, it may indicate that the request for transitioning to the UE-controlled RQoS enabled state is rejected. Further, the SMF_A230 sends one or more pieces of identification information out of the 21st to 29th pieces of identification information included in the PDU session establishment rejection message to indicate that the network does not support RQoS controlled by the network. It may indicate that the request to transit to the state where network-controlled RQoS is available is rejected.

Also, UE_A10, by transmitting the 21st identification information, or, by transmitting the 22nd identification information, or by transmitting the 23rd identification information and the 24th identification information, or, By transmitting the 27th identification information, or by transmitting the 28th identification information and the 29th identification information, or two or more of these identification information identification of one or more identification information When configured as information, the network does not support RQoS controlled via Control Plane by transmitting one or more pieces of identification information among them, and it is controlled via User Plane. It may indicate that the network does not support RQoS, the request to transition to the state where RQoS controlled via Control Plane can be used is rejected, and RQoS controlled via User Plane can be used. It may indicate that the request to transition to a different state has been rejected.

Furthermore, SMF_A230, by including the 72nd identification information, and / or 25th identification information, and / or 26th identification information included in the PDU session establishment rejection message, of the PDU session belonging to the network slice. It may indicate that the request for establishment has been rejected, or it may indicate a network slice that is not allowed to belong to the PDU session.

More specifically, the SMF_A230 transmits the 72nd identification information and the 25th identification information in association with each other, in the PDU session established for the DN identified by the 25th identification information, in the network. It may indicate that the request to establish the PDU session belonging to the slice has been denied, or it may indicate a network slice that is not allowed to belong to the PDU session.

Further, the SMF_A230 transmits the 61st identification information and the 26th identification information in association with each other to request the establishment of the PDU session belonging to the network slice in the PDU session identified by the 26th identification information. May be rejected, or it may indicate a network slice that is not allowed to belong to the PDU session.

Further, SMF_A230, by including the 72nd identification information included in the PDU session establishment rejection message, the registration area UE_A10 currently belongs to, and / or in the tracking area, in the PDU session belonging to the network slice. It may indicate that the request for establishment has been rejected, or it may indicate a network slice that is not allowed to belong to the PDU session.

Further, SMF_A230, by including the 72nd identification information in the PDU session establishment rejection message, in the access network to which UE_A10 is currently connected, the request to establish the PDU session belonging to the network slice is rejected. May be indicated, or a network slice not permitted to belong to the PDU session may be indicated.

Furthermore, the SMF_A230 may indicate the value of the first timer by including the 72nd identification information in the PDU session establishment refusal message and transmitting it, and after the completion of this procedure, the same procedure as this procedure may be performed again. It may indicate whether or not to implement.

Furthermore, the SMF_A230 may make a request that combines the above-mentioned matters by transmitting a combination of two or more pieces of identification information of the 21st to 29th identification information and/or the 72nd identification information. It should be noted that the matters indicated by the SMF_A 230 transmitting each piece of identification information are not limited to these.

Note that SMF_A230 is the identification information received from the 21st to 29th identification information and the 72nd identification information, which identification information is to be included in the PDU session establishment rejection message, and/or network capability information, and It may be determined based on a policy such as an operator policy and/or a network state.

For example, the 21st identification information may be information transmitted when the network RQoS is not supported and/or when one or more identification information items among the identification information items 1 to 8 are received. Furthermore, the 22nd identification information, and / or 27th identification information, if the network does not support RQoS, and / or 1 to 3 identification information, and / or 6 to 8 identification information It may be information transmitted when received. Furthermore, the 23rd identification information, and / or 28th identification information, if the network supports RQoS controlled via Control Plane, and / or 1 to 3 identification information, and / or It may be information transmitted when the sixth to eighth identification information is received. Furthermore, the 24th identification information, and/or the 29th identification information, when the network supports RQoS controlled via User Plane, and/or the first to third identification information, and/or It may be information transmitted when the sixth to eighth identification information is received.

Furthermore, the 25th identification information may be information indicating the same DNN as the DNN indicated by the fourth identification information. Furthermore, the 26th identification information may be information indicating the same PDU session ID as the PDU session ID indicated by the fifth identification information. Further, the 72nd identification information may be information transmitted when the 71st identification information is received and/or when the network slice indicated by the 71st identification information is not permitted by the network. The determination by SMF_A230 which identification information should be included in the PDU session establishment rejection message is not limited to this.

UE_A10 receives the PDU session establishment rejection message. UE_A10 performs the fourth process based on the reception of the PDU session establishment rejection message (S1024). Also, the UE_A 10 may perform the fourth process based on the completion of this procedure.

Here, the fourth process may be a process in which UE_A10 recognizes the matter indicated by SMF_A230. Furthermore, the fourth process may be a process in which the UE_A10 stores the received identification information as a context, or may be a process of transferring the received identification information to an upper layer and/or a lower layer. .. Furthermore, the fourth process may be a process in which the UE_A10 recognizes that the request for this procedure is rejected.

Furthermore, when UE_A10 receives one or more pieces of identification information from the 21st to 29th pieces of identification information, the fourth processing is UE_A10, a processing for transitioning to a state in which the RQoS enabling procedure is not executable, or RQoS. It may be to maintain the non-application state.

More specifically, if the UE_A10 receives the 22nd identification information, and/or the 23rd identification information, and/or the 27th identification information, and/or the 28th identification information, the fourth process is, It may be a process of transiting to a state in which the RQoS activation procedure controlled via the Control Plane is not executable. Furthermore, if the UE_A10 receives the 22nd identification information, and/or the 24th identification information, and/or the 27th identification information, and/or the 29th identification information, the fourth processing is the UserPlane. The processing may be a process of transiting to a state in which the RQoS enabling procedure controlled via the non-executable state.

Furthermore, if the UE_A10 receives the 72nd identification information, the fourth process, UE_A10 may be a process of setting the value indicated by the 72nd identification information as the first timer value, or the timer value. It may be a process of starting the first timer having set. Furthermore, when the UE_A10 receives the 72nd identification information, the fourth process may be a process of executing one or more of the first to eleventh behaviors.

Further, the fourth process may be a process in which the UE_A10 may restart this procedure after a certain period of time, or a process in which the request of the UE_A10 transits to a limited state.

Furthermore, if the 21st identification information indicates User authentication or authorization authorization failed, the 4th processing is the DNN and/or S-NSSAI used in the PDU session establishment procedure rejected for the rejection reason indicated by the 21st identification information. And/or a process of suppressing the process of reconnecting the PDU session using the same information as the user identifier.

For example, UE_10 may implement the following first procedure example as the fourth processing example. UE_A10 is DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI#A from the configured NSSAI for the HPLMN, using the user identifier #A indicated by the 61st identification information 1 PDU session establishment request message (S1000) is sent, the PDU session establishment rejection message (S1002) received from the network contains the 21st identification information indicating User authentication authentication or authorization failed, and the 121st identification information When not including, the UE_A10 may recognize that the PDU session establishment request is rejected because of User authentication authentication or authorization failed.

Note that the condition determination that SMF_A230 rejects due to User authentication or authorization failed may be determined based on the third condition determination.

At this time, UE_A10, the DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI#A from the configured NSSAI for the HPLMN, the 61st identification information indicating the user identifier #A, The transmission of the used second PDU session establishment request message may be set to be restricted.

Further, UE_A10 changes the user identifier indicated by the 61st identification information used in the first PDU session establishment request message (1000) and/or turns the terminal power on/off and/or USIM (Universal SubscriberIdentity Module). ) Is inserted/removed, targeting DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI#A from the configured NSSAI for the HPLMN sent in the first PDU session establishment request message (1000). The procedure may be such that reconnection using another PDU session establishment request message is not automatically performed.

Also, the conditions for reconnection by UE_A10 are not limited to these.

For example, UE_10 may implement the following second procedure example as the fourth processing example. UE_A10 is DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI#A from the configured NSSAI for the HPLMN, using the user identifier #A indicated by the 61st identification information 1 PDU session establishment request message (S1000) is sent, and the PDU session establishment rejection message (S1002) received from the network contains the 21st identification information indicating User authentication authentication or authorization failed, and indicates EAP-failure. When the 121st identification information is not included, the transmission of the second PDU session establishment request message using the 61st identification information indicating the user identifier #A is restricted, and the transmission of the second PDU session establishment request message is restricted. When changing to a different user identifier from the user identifier #A during the operation, DNN#A and/or S-NSSAI#A and/or mapped configured sent in the first PDU session establishment request message (1000) S-NSSAI#A from the configured NSSAI for the Set to allow the transmission of another PDU session establishment request message using the 61st identification information indicating a user identifier different from the user identifier #A for HPLMN May be done.

UE_10 may also implement the following third procedure example as the fourth processing example. UE_A10 is DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI#A from the configured NSSAI for the HPLMN, using the user identifier #A indicated by the 61st identification information 1 PDU session establishment request message (S1000) is sent, and the PDU session establishment rejection message (S1002) received from the network contains the 21st identification information indicating User authentication authentication or authorization failed, and indicates EAP-failure. When the 121st identification information is not included, the transmission of the second PDU session establishment request message using the 61st identification information indicating the user identifier #A is restricted, and the transmission of the second PDU session establishment request message is restricted. If the terminal power is turned on/off during the operation, the DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI# sent in the first PDU session establishment request message (1000) are sent. It may be set to allow the transmission of another PDU session establishment request message using the 61st identification information for A from the configured NSSAI for the HPLMN. At this time, the user identifier indicated by the 61st identification information may be user identifier #A or a user identifier different from user identifier #A.

UE_10 may also implement the following fourth procedure example as the fourth processing example. UE_A10 is DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI#A from the configured NSSAI for the HPLMN, using the user identifier #A indicated by the 61st identification information 1 PDU session establishment request message (S1000) is sent, and the PDU session establishment rejection message (S1002) received from the network contains the 21st identification information indicating User authentication authentication or authorization failed, and indicates EAP-failure. When the 121st identification information is not included, the transmission of the second PDU session establishment request message using the 61st identification information indicating the user identifier #A is restricted, and the transmission of the second PDU session establishment request message is restricted. If the USIM (Universal Subscriber Identity Module) is removed and inserted during the operation, DNN#A and/or S-NSSAI#A and/or mapped configured sent in the first PDU session establishment request message (1000). It may be set to allow the transmission of another PDU session establishment request message using the 61st identification information for S-NSSAI#A from the configured NSSAI for the HPLMN. At this time, the user identifier indicated by the 61st identification information may be user identifier #A or a user identifier different from user identifier #A. Further, the first to fourth procedure examples of the fourth processing example described above, UE_A10 is DNN#A and/or S-NSSAI#A and/or mapped configured S-NSSAI#A from the configured NSSAI for the To the HPLMN, the first PDU session establishment request message (S1000) is transmitted using the user identifier #A indicated by the 61st identification information, and the PDU session establishment rejection message (S1002) received from the network is User It may be applied even when including the 21st identification information indicating authorization and the 121st identification information indicating EAP-failure. The user identifier indicated by the 61st identification information included in the reconnection using the above PDU session establishment request message is indicated by the 61st identification information used in the first PDU session establishment request message (1000). It is not limited to the user identifier. For example, even if the user identifier #B different from the user identifier #A is used in the 61st identification information, the reconnection using the PDU session establishment request message may be set to be restricted.

Note that the fourth process is not limited to these processes.

Further, UE_A10 may recognize that the request of UE_A10 is rejected by receiving the PDU session establishment reject message or by not receiving the PDU session establishment accept message. Each device completes the procedure (B) in this procedure based on the transmission and reception of the PDU session establishment rejection message.

Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure. It should be noted that each device may transition to a state where the PDU session is established based on the completion of the procedure (A) in this procedure, or based on the completion of the procedure (B) in the procedure. , It may be recognized that this procedure has been rejected, or it may transit to a state in which a PDU session is not established.

Furthermore, each device may perform processing based on the identification information transmitted and received in this procedure based on the completion of this procedure. In other words, the UE_A 10 may perform the third processing or the fourth processing based on the completion of this procedure.

Also, the third condition determination may be executed based on the identification information and/or the subscriber information and/or the operator policy included in the PDU session establishment request message. For example, the third condition determination may be true when the network permits the authentication and/or the authorization by DN_A5 to be performed in this procedure. The third condition determination may be false if the network does not permit the DN_A5 to perform authentication and/or authorization in this procedure. Furthermore, the third condition determination is true when the network to which UE_A10 is connected and/or the device in the network supports performing authentication and/or authorization by DN_A5 in this procedure. If you don't support it, you can fake it. Furthermore, the third condition determination is that the PDU session establishment request message includes the SMPDUNDNRequestContainer that includes the 61st identification information, and the 61st identification information conforms to the local policy and/or user subscriber information. Can be true. It may also be true when the SMPDUN RequestContainer is not included in the PDU session establishment request message. On the other hand, if the PDU session establishment request message includes the SM PDU DN Request Container that includes the 61st identification information and the 61st identification information does not comply with the local policy and/or user subscriber information, it is false. You can The condition that determines whether the third condition determination is true or false is not limited to the condition described above. The condition that determines whether the third condition determination is true or false is not limited to the condition described above.

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

[1.3.3. Outline of PDU session establishment authentication approval procedure]
Next, an outline of a PDU session establishment authentication approval procedure performed by the DN_A5 to perform authentication and/or approval for a PDU session will be described. Hereinafter, the PDU session establishment authentication approval procedure is also referred to as this procedure. This procedure is a procedure for the DN_A5 and/or the device in the DN_A5 to authenticate and/or approve the PDU session. Each device may execute this procedure in a state where a PDU session is established, or may be executed in the PDU session establishment procedure. For example, the SMF_A 230 may start this procedure when receiving a PDU session establishment request message including at least the 61st identification information in the registration procedure and/or the PDU session establishment procedure. The SMF_A 230 may start this procedure when the 21st condition determination is true in the registration procedure and/or the PDU session establishment procedure.

Also, each device may start this procedure when the PDU session establishment procedure is completed, or may start this procedure at any timing after the PDU session establishment procedure. Further, each device may transit to a state where the PDU session is authenticated and/or approved by the device in the DN_A5 and/or the device in the DN_A5 based on the completion of the PDU session establishment authentication approval procedure.

[1.3.3.1. PDU session establishment authentication approval procedure example]
An example of the procedure for executing the PDU session establishment authentication approval procedure will be described with reference to FIG. Each step of this procedure will be described below. First, the SMF_A230 starts a PDU session establishment authentication approval procedure by transmitting an Authentication/Authorization Request message to the DN_A5 and/or a device in the DN_A5 via the UPF_A235 (S1100).

Specifically, the SMF_A230 selects UPF_A235 and/or DN_A5 and/or a device within DN_A5, and sends an authentication/authorization request message to the selected UPF_A235 using the N4 interface. Upon receiving the authentication/authorization request message, the UPF_A235 transmits or transfers the authentication/authorization request message to the DN_A5 and/or the device within the DN_A5 using the N6 interface. Here, SMF_A230, UE_A10, and / or information received from the device in the core network, and / or based on the information held by SMF_A230, UPF_A235, and / or DN_A5, and / or selects the device in DN_A5. Good. More specifically, the SMF_A230 is each identification information obtained based on the reception of the PDU session establishment request message, information obtained by inquiring the device in the core network, and/or subscriber information, and/or network capability. DN_A5 and/or DN_A5 may be selected based on information and/or operator policy, and/or network status, and/or context already held by AMF_A240.

Note that the PDU session establishment request message may be a NAS message. Further, the PDU session establishment request message may be any message as long as it is a message requesting establishment of a PDU session, and is not limited to this.

Furthermore, the resource publication of authentication/authorization for DN_A5 including the authentication/authorization request message exchange is performed even if the operator provides the API (Application Programming Interface) to DN_A5 and/or the service provider who provides the service on DN_A5. Good. The authentication/approval request message is transmitted/received between SMF_A230, and/or UPF_A235 and DN_A5, and/or a device included in DN_A5, and may be a message requesting authentication by DN_A5 and/or approval. It is not limited to this.

Here, SMF_A230, UE_A10, and / or information received from the device in the core network, and / or SMF_A230 may hold the information held in the authentication / authorization request message may be transmitted, or these identification information. The inclusion may indicate the request of UE_A10 and/or SMF_A230.

-DN_A5 and/or the device in DN_A5 receives the authentication/authorization request message. The DN_A5 and/or the device within the DN_A5 may perform the twenty-first condition determination based on the reception of the authentication/authorization request message. The twenty-first condition determination is for determining whether or not the DN_A5 and/or the device within the DN_A5 executes the PDU session authentication and/or authorization procedure by the DN_A5. In the 21st condition determination, the DN_A5 and/or the device within the DN_A5 determines whether the 21st condition determination is true or false. DN_A5 and/or the device in DN_A5 may continue this procedure if the 21st condition determination is true, or do not continue this procedure if the 21st condition determination is false and reject the request. The indicated message may be sent to SMF_A230 via UPF_A235.

Next, the device in DN_A5 and/or DN_A5 receives an authentication/authorization request message, and/or based on the 21st condition determination, based on the 21st condition determination, authentication/authorization request (authentication/authorizationRequest) to SMF_A230 via UPF_A235. Send the message (S1102).

Specifically, DN_A5 and/or the device in DN_A5 sends an authentication/authorization request message to UPF_A235 using the N6 interface. Upon receiving the authentication/authorization request message, UPF_A235 transmits or transfers the authentication/authorization request message to SMF_A230 using the N4 interface.

Based on the reception of the authentication/authorization request message, SMF_A230 sends a PDU session authentication request message to UE_A10 via AMF_A240 (S1104).

Specifically, the SMF_A230 sends a PDU session authentication request message to the AMF_A240 using the N11 interface, and the AMF_A240 receiving the PDU session authentication request message sends a PDU session authentication request message to the UE_A10 using the N1 interface. ..

Note that the PDU session authentication request message is not limited to this, and may be a message indicating that PDU session authentication/authorization by DN_A5 is requested.

Here, the SMF_A230 may include the 62nd identification information in the PDU session authentication request message, or may include the identification information to indicate the request of the DN_A5 and/or the device in the DN_A5. ..

Furthermore, SMF_A230, by including the 62nd identification information in the PDU session authentication request message and transmitting, DN_A5 performs authentication and/or authorization for the PDU session and/or UE_A10 and/or application. May be indicated, or UE_A10 and/or application and/or user may indicate that the authentication/authorization information of DN_A5 needs to be confirmed and/or selected.

Note that the SMF_A230 determines whether to include the 62nd identification information in the PDU session authentication request message, the received identification information and/or network capability information, and/or a policy such as an operator policy, and/or a network state. May be determined based on.

For example, when the SMF_A230 receives the PDU session establishment request message including the 61st identification information in the registration procedure and/or the PDU session establishment procedure, the SMF_A230 sends the PDU session authentication request message including the 62nd identification information. You may. The determination by SMF_A230 which identification information should be included in the PDU session authentication request message is not limited to this.

UE_A10 receives the PDU session authentication request message. By receiving the PDU session authentication request message, the UE_A10 recognizes the contents of various identification information included in the PDU session authentication request message.

UE_A10 further executes the fifth process based on the reception of the PDU session authentication request message (S1106). Note that the UE_A10 may perform the fifth process based on the transmission of the PDU session authentication acceptance message or the PDU session authentication rejection message, or upon completion of this procedure. You may implement based on.

Here, the fifth process may be a process in which the UE_A10 recognizes the matter indicated by the SMF_A230. Further, the fifth process, UE_A10 may be a process of storing the received identification information as a context, or may be a process of transferring the received identification information to an upper layer, and/or a lower layer. ..

Further, the fifth process, UE_A10 may be a process of determining whether the authentication/approval information indicated by the 62nd identification information is appropriate, or the authentication indicated by the received 62nd identification information. /It may be a process of inserting information indicating whether or not the approval information is appropriate in the 63rd identification information.

Further, the fifth process, UE_A10 may be a process of recognizing that the authentication/approval information indicated by the 62nd identification information is DN authentication/permission information, or the received 62nd identification information. It may be a process of inserting information indicating a response into the 63rd identification information, or a process of inserting the same authentication/authorization information as the received 62nd identification information into the 63rd identification information.

Furthermore, the fifth process, UE_A10 may be a process of selecting appropriate authentication / authorization information from the authentication / authorization information indicated by the 62nd identification information, based on the 62nd identification information. It may be a process of inserting the selected authentication/authorization information into the 63rd identification information.

Further, the fifth process may be a process in which UE_A10 notifies the upper layer, and/or the user of the 62nd identification information, or the upper layer notified of the 62nd identification information, and/or the user. May be a process of selecting appropriate authentication/approval information from the authentication/approval information indicated by the 62nd identification information.

Further, the fifth process, UE_A10 may be a process of acquiring authentication/authorization information selected based on the notified 62nd information from the upper layer, and/or the user, or an upper layer, And/or the authentication/authorization information acquired from the user may be included in the 63rd identification information.

Furthermore, the fifth process may be a process in which the UE_A10 executes the 22nd condition determination. The fifth process is not limited to these processes.

UE_A10 executes the 22nd condition determination based on the reception of the PDU session authentication/authorization request message and/or the completion of the 5th process. The 22nd condition determination is for determining whether or not the UE_A10 accepts the procedure of authenticating and/or approving the PDU session by the DN_A5. In the 22nd condition determination, the UE_A 10 determines whether the 22nd condition determination is true or false. UE_A10 starts the procedure (A) in this procedure when the 22nd condition determination is true, and starts the procedure (B) in this procedure when the 22nd condition determination is false. The steps in the case where the 22nd condition determination is false will be described later.

The following describes the steps when the 22nd condition judgment is true, that is, each step of the procedure (A) in this procedure. UE_A10 receives the PDU session authentication/authorization request message, and/or completes the fifth process, and/or based on the twenty-second condition determination, based on AMF_A240 to SMF_A230, PDU session authentication acceptance (PDU session authentication accept) ) Send the message (S1108).

Specifically, UE_A10 transmits a PDU session authentication acceptance message to AMF_A240 using the N1 interface, and AMF_A240 that receives the PDU session authentication acceptance message transmits a PDU session authentication acceptance message to SMF_A230 using the N11 interface. ..

Note that the PDU session authentication acceptance message may be a NAS message transmitted/received on the N1 interface and the N11 interface. Further, the PDU session authentication acceptance message may be a response message to the PDU session authentication request message, and is not limited to this, and may be a message indicating that the PDU session establishment authentication/approval procedure has been accepted.

Here, UE_A10 may include the 63rd identification information in the PDU session authentication acceptance message, or may include the identification information to indicate that the network request has been accepted.

Further, UE_A10, by including the 63rd identification information included in the PDU session authentication acceptance message, UE_A10, and / or application, and / or user, authentication / authorization information of DN_A5, indicates that. May be shown, the acceptance may be shown, or the selection may be shown.

Incidentally, UE_A10, whether to put the 63rd identification information in the PDU session authentication acceptance message, received identification information, and / or, UE_A10 capability information, and / or UE_A10 policy, and / or based on the state of UE_A10 You may decide.

For example, UE_A10, if the 62nd identification information is received, and/or if the received 62nd identification information can be accepted, the 63rd identification information is included in the PDU session authentication acceptance message and transmitted. Good. Note that the determination by the UE_A 10 which identification information should be included in the PDU session authentication acceptance message is not limited to this.

ㆍSMF_A230 receives the PDU session authentication acceptance message. Furthermore, each device completes the procedure (A) in this procedure based on the transmission and reception of the PDU session authentication acceptance message.

Next, the steps when the 22nd condition judgment is false, that is, each step of the procedure (B) in this procedure will be described. The UE_A10 receives the PDU session authentication/authorization request message, and/or completes the fifth process, and/or based on the twenty-second condition determination, based on the AMF_A240 to the SMF_A230, the PDU session authentication rejection (PDU session authenticationreject). ) Send the message (S1110).

Specifically, UE_A10 sends a PDU session authentication reject message to AMF_A240 using the N1 interface, and AMF_A240 that receives the PDU session authentication reject message sends a PDU session authentication reject message to SMF_A230 using the N11 interface. ..

Note that the PDU session authentication rejection message may be a NAS message transmitted/received on the N1 interface and the N11 interface. Further, the PDU session authentication rejection message may be a response message to the PDU session authentication request message, and is not limited to this, and may be a message indicating that the PDU session establishment authentication/authorization procedure is rejected.

Here, UE_A10 may include information indicating the reason why the PDU session authentication request message is rejected in the PDU session authentication rejection message, or by including these identification information, the network request is rejected. May be indicated.

Further, UE_A10, by including the information indicating the reason why the PDU session authentication request message is rejected in the PDU session authentication acceptance message, UE_A10, and / or application, and / or user, DN / A5 authentication / authorization. The information may indicate unacceptable or unselectable.

Incidentally, UE_A10 is, among the reasons that the PDU session authentication request message is rejected, which identification information to put in the PDU session authentication rejection message, the received identification information, and/or capability information of UE_A10, and/or UE_A10. Policy and/or the state of UE_A10. Note that the determination by the UE_A 10 which identification information is included in the PDU session authentication rejection message is not limited to this.

ㆍSMF_A230 receives the PDU session authentication rejection message. Further, each device completes the procedure (B) in this procedure based on the transmission and reception of the PDU session authentication rejection message.

SMF_A230 sends an Authentication/Authorization Response message via UPF_A235 based on the completion of the procedure (A) in this procedure and/or the completion of the procedure (B) in this procedure. It transmits to DN_A5 and/or the device in DN_A5 (S1112). In other words, SMF_A230 sends an authentication/authorization response message via UPF_A235 to the devices in DN_A5 and/or DN_A5 based on receiving the PDU session authentication accept message and/or receiving the PDU session authentication reject message. To do.

Specifically, SMF_A230 sends an authentication/authorization response message to UPF_A235 using the N4 interface. Upon receiving the authentication/authorization response message, the UPF_A235 transmits or transfers the authentication/authorization response message to the DN_A5 and/or the device within the DN_A5 using the N6 interface.

Even if the API (Application Programming Interface) provided by the operator to the service provider providing the service on DN_A5 and/or DN_A5, the resource disclosure of the authentication/authorization to DN_A5 including the authentication/authorization response message exchange is performed. Good. Further, the authentication/approval response message is transmitted/received between the SMF_A230 and/or UPF_A235 and the device included in DN_A5, and/or DN_A5, and may be any response message to the authentication/authorization request message, but is not limited to this. ..

Here, SMF_A230, UE_A10, and / or information received from the device in the core network, and / or SMF_A230 may be transmitted by including the information held in the authentication / authorization response message, the identification information of these. The inclusion may indicate the request of UE_A10 and/or SMF_A230.

Here, when the SMF_A230 receives the 63rd identification information, the authentication/approval response message may include the 63rd identification information, or by including these identification information, DN_A5 and/or DN_A5. It may indicate that the request of the device within has been accepted. When the reason why the PDU session authentication request message is rejected is received, the authentication/authorization response message may include the reason why the PDU session authentication request message was rejected, or by including these identification information, It may indicate that the request for DN_A5 and/or the devices in DN_A5 has been denied.

Note that the SMF_A230 may determine which identification information should be included in the authentication/authorization response message based on each identification information acquired based on the reception of the PDU session authentication acceptance message and/or the PDU session authentication rejection message. .. The determination by SMF_A230 which identification information should be included in the authentication/approval response message is not limited to this.

-DN_A5 and/or the device in DN_A5 receives the authentication/authorization response message. Furthermore, each device completes this procedure based on the transmission/reception of the PDU session authentication acceptance message and/or the transmission/reception of the PDU session authentication rejection message and/or the transmission/reception of the authentication/approval response message. It should be noted that each device may transit to a state in which the PDU session is authenticated and/or approved by DN_A5 based on the completion of the procedure (A) in this procedure, or (B) in this procedure. Based on the completion of the procedure of 1., it may be recognized that the procedure is rejected, and the PDU session may transit to a state in which it has not been authenticated and/or approved by DN_A5.

Furthermore, each device may perform processing based on the identification information transmitted and received in this procedure based on the completion of this procedure. In other words, the UE_A10 may adapt the acquired and/or selected DN_A5 issued authentication/authorization information based on the completion of this procedure.

The 21st condition determination may be performed based on the identification information and/or subscriber information included in the authentication/authorization request message and/or the DN_A5 policy. For example, the 21st condition determination may be true when the request of UE_A10 is granted by DN_A5 and/or the device in DN_A5. The twenty-first condition determination may be false if the request of UE_A10 is not permitted by DN_A5 and/or the device within DN_A5. Furthermore, the 21st condition determination is true if the device in the DN_A5 to which the UE_A10 is connected, and/or the device in the DN_A5 supports the function for authenticating and/or authorizing the PDU session by the DN_A5. Well, false if not supported. The condition that determines the truth of the 21st condition determination is not limited to the above-described condition.

The 22nd condition determination may be performed based on the identification information included in the PDU session authentication request message, and/or the capability information of UE_A10, and/or the policy of UE_A10, and/or the state of UE_A10. For example, the 22nd condition determination may be true when UE_A10 permits a request for authentication and/or authorization of a PDU session by DN_A5. The twenty-second condition determination may be false if the UE_A10 does not permit the PDU session authentication and/or authorization request by the DN_A5. The condition that determines the authenticity of the 22nd condition determination is not limited to the above-described condition.

[1.3.4. Overview of RQoS activation (activation) procedure]
Next, an outline of an RQoS activation (activation) procedure performed to activate (activate) RQoS for user data communication will be described. In this chapter, the RQoS activation procedure is also referred to as this procedure. This procedure is a procedure for each device to enable RQoS for user data communication. This procedure includes a UE-controlled RQoS activation procedure initiated by UE_A10 and a network-initiated RQoS activation procedure initiated by a device in the core network.

Note that each device may execute this procedure in a state where a PDU session is established, or may be executed during user data communication. Also, each device may start this procedure at any timing after the PDU session establishment procedure. Further, each device may activate RQoS for user data communication based on the completion of the RQoS activation procedure, or may perform user data communication using RQoS. Note that enabling RQoS for user data communication may mean controlling RQoS for user data communication, or may be enabling RQoS for a specific user data flow. .. Further, to enable RQoS for user data communication, UE_A10, the downlink packet received, and / or based on the identification information contained in the downlink packet, for the uplink traffic, and / or for the uplink packet It may be that a QoS rule (also referred to as Derived QoS Rule) is created and the use of the created QoS rule is started.

Here, this procedure may be a procedure for each device to activate RQoS for user data communication via the User plane, and is referred to as an RQoS activation procedure controlled via the User Plane. Good.

[1.3.4.1. Example of RQoS activation procedure controlled by UE]
An example of the procedure for executing the RQoS activation procedure controlled by the UE will be described with reference to FIG. In this chapter, the UE-controlled RQoS activation procedure is also referred to as this procedure. It should be noted that this procedure may be referred to as an RQoS activation procedure controlled via the UE-initiated User Plane. Each step of this procedure will be described. First, UE_A10 starts the RQoS activation procedure controlled by the UE by transmitting an uplink packet to UPF_A235 via NR node_A122 (S1200).

Specifically, UE_A10 transmits an uplink packet to UPF_A235 using a radio bearer and/or N3 interface and/or N9 interface. Here, the UE_A10 may select the routing destination UPF_A235 based on the information held by the UE_A10. More specifically, UE_A10, by comparing the routing information of the uplink packet, the routing rule that UE_A10 holds, and / or QoS rule, the QoS flow used to transmit the uplink packet, and / or UPF_A235. You may choose. Incidentally, UE_A10, the routing rule that matches the routing information of the uplink packet, and / or if there is no QoS rule, the default routing rule, and / or QoS flow used to transmit the uplink packet using the default QoS rule, And/or UPF_A235 may be selected. The default QoS rule is configured to include a QoS rule ID (QoS rule identifier), a QFI of a QoS flow, a packet filter of 1 or more, and a preceding value. However, the default QoS rule may be configured without the packet filter among these components, and in this case, the preceding value is set to the maximum value. That is, the priority should be the lowest.

Here, the routing information of the uplink packet may be information for identifying the application or may be a 5-tuple. More specifically, the routing information of the uplink packet is a destination IP address (target IP address), and/or a source IP address (source IP address), and/or a protocol number (protocol number), and/or Alternatively, it may be a destination port number (target port number) and/or a source port number (source port number), or may be information combining these. The routing information of the uplink packet is not limited to this.

Further, the uplink packet may be a message transmitted from the UE_A10 to the access network and/or the core network and/or the DN_A5 in the user data communication. Therefore, including the identification information in the uplink packet may mean including the identification information in the header of the uplink packet, or including the identification information in the header of the message of the uplink packet. Alternatively, the identification information may be included in the message of the uplink packet. Note that the UE_A10 may transmit a dummy uplink packet to the UPF_A235 when there is no uplink packet to be transmitted to the DN_A5 and/or the device in the DN_A5.

Here, UE_A10, the uplink packet, may include the 41st identification information, and / or 42nd identification information, by including these identification information, to enable the RQoS for user data communication. The request may be indicated.

Furthermore, UE_A10 may request to enable RQoS for user data communication by UE, by transmitting by including the 41st identification information and/or the 42nd identification information in the uplink packet. ..

Further, UE_A10, the 41st identification information, and / or by transmitting the 42nd identification information included in the uplink packet, the QoS flow used in the transmission and reception of the uplink packet indicated by the routing information of the uplink packet. May be requested to be changed to the QoS flow indicated by the 42nd identification information.

Incidentally, UE_A10, the 41st identification information, of the 42nd identification information, which identification information to put in the uplink packet, capability information of UE_A10, and / or policies such as UE policy, and / or UE_A10. You may decide based on a preference. Note that the determination by the UE_A 10 which identification information should be included in the uplink packet is not limited to this.

UPF_A235 receives the uplink packet (S1200). UPF_A235 may transfer the received uplink packet to DN_A5 and/or a device included in DN_A5 based on the reception of the uplink packet.

Next, UPF_A235 transmits a request notification message to SMF_A230 based on reception of an uplink packet and/or transfer of an uplink packet (S1202). Specifically, UPF_A235 sends a request notification message to SMF_A230 using the N4 interface. Furthermore, the request notification message is not limited to this as long as it is a message indicating a request to enable RQoS for user data communication.

Here, UPF_A235 may include the identification information included in the received uplink packet in the request notification message. In other words, the UPF_A235 may transmit the request notification message by including the received 41st identification information and/or the 42nd identification information, or by transmitting these identification information, user data communication May be indicated to require RQoS activation for.

SMF_A230 receives the request notification message (S1202) and executes the 31st condition determination. The 31st condition determination is for the SMF_A230 to determine whether to accept the request from the UE_A10. In the 31st condition determination, the SMF_A 230 determines whether the 31st condition determination is true or false. SMF_A230, if the 31st condition determination is true (that is, if accepting the request of UE_A10), start the procedure of (A) in this procedure, if the 31st condition determination is false (that is, If the request from UE_A10 is rejected), the procedure (B) in this procedure is started. The steps in the case where the 31st condition determination is false will be described later.

The following describes the steps when the 31st condition determination is true, that is, each step of the procedure (A) in this procedure. The SMF_A230 transmits the RQoS activation notification message to the UPF_A235 based on the 31st condition determination and/or the reception of the request notification message (S1204), and starts the procedure (A) in this procedure. Specifically, the SMF_A230 sends an RQoS activation notification message to the UPF_A235 using the N4 interface. The RQoS activation notification message is not limited to this, and may be a message indicating the activation of RQoS for user data communication.

Here, SMF_A230, the RQoS activation notification message, may include the 31st identification information, and / or 32nd identification information, by including these identification information, the request of UE_A10 was accepted. May be indicated.

Further, SMF_A230, by including the 31st identification information, and / or 32nd identification information included in the RQoS activation notification message, may indicate that the request for RQoS activation is accepted, It may be indicated that RQoS is enabled.

Further, SMF_A230, by including the 31st identification information, and / or 32nd identification information included in the RQoS activation notification message, the QoS flow used in the transmission and reception of a specific downlink packet, the 32nd It may indicate to change to the QoS flow indicated by the identification information.

Incidentally, the SMF_A230, the 31st identification information, of the 32nd identification information, which identification information to put in the RQoS activation notification message, the received identification information, and/or network capability information, and/or It may be determined based on a policy such as an operator policy and/or the state of the network.

For example, the SMF_A230, when receiving the 41st identification information, and/or the 42nd identification information, and/or accepting the request indicated by the received 41st identification information and/or the 42nd identification information , The 31st identification information, and/or the 32nd identification information may be included in the RQoS activation notification message and transmitted.

Note that the 32nd identification information may be determined based on the 42nd identification information. In other words, the 32nd identification information may be information identifying the same QoS flow as the QoS flow indicated by the 42nd identification information, or may identify a QoS flow different from the QoS flow indicated by the 42nd identification information. It may be information to be provided. The determination by SMF_A230 as to which identification information is included in the RQoS activation notification message is not limited to this.

Here, SMF_A230, each identification information acquired based on the reception of the request notification message, and / or network capability information, and / or subscriber information, and / or operator policy, and / or network state, and / Alternatively, the context for RQoS may be created based on the context already held by SMF_A230.

UPF_A235 receives the RQoS activation notification message (S1204). The UPF_A 235 recognizes the contents of various identification information included in the RQoS validation notification message by receiving the RQoS validation notification message. The UPF_A 235 may create a QoS rule and/or context for RQoS based on each piece of identification information acquired by receiving the RQoS activation notification message.

Further, UPF_A235 may receive the downlink packet transmitted by DN_A5 and/or the device in DN_A5 (S1206). UPF_A235 transmits a downlink packet to UE_A10 based on the reception of the RQoS activation notification message and/or the reception of the downlink packet from DN_A5 (S1206).

Specifically, UPF_A235 transmits downlink packets to UE_A10 using N9 interface and/or N3 interface and/or radio bearer. Here, the UPF_A 235 may select the UE_A 10 of the routing destination based on the information held by the UPF_A 235. More specifically, UPF_A235, by comparing the routing information of the downlink packet, the routing rule held by UPF_A235, and / or QoS rule, the QoS flow used for the transmission of the downlink packet, and / or UE_A10 You may choose. In addition, UE_A10, if there is no routing rule that matches the routing information of the downlink packet, and / or QoS rule, the default routing rule, and / or QoS flow used to transmit the downlink packet using the default QoS rule , And/or UPF_A235 may be selected.

Here, the routing information of the downlink packet may be information for identifying an application or may be a 5-tuple. More specifically, the routing information of the downlink packet is a destination IP address and/or a source IP address and/or a protocol number, a destination port number, and/or a source port number. Alternatively, the information may be a combination of these. The routing information of the downlink packet is not limited to this.

Further, the downlink packet, in the user data communication, may be a message transmitted to the UE_A10 from the device in the DN_A5, and / or DN_A5, the message transmitted from the device in the core network to UE_A10 Or a message for transferring these user data communication messages. Therefore, including the identification information in the downlink packet may mean including the identification information in the header of the downlink packet, or including the identification information in the header of the downlink packet that does not include the message used for transfer. It may be that the identification information is included in the header of the message used for forwarding the downlink packet, or that the identification information is included in the message used for forwarding the downlink packet. May be. Note that UPF_A235 may transmit a dummy downlink packet to UE_A10 when there is no downlink packet received from DN_A5 and/or a device in DN_A5.

Here, the UPF_A 235 may include the 31st identification information and/or the 32nd identification information in the downlink packet, and by including these identification information, the RQoS for user data communication is enabled. It may indicate that the request of UE_A10 is accepted.

Furthermore, UPF_A235 may indicate that the request for enabling RQoS has been accepted by transmitting by including the 31st identification information and/or the 32nd identification information in the downlink packet, or RQoS. May be enabled.

Furthermore, UPF_A235, by including the 31st identification information, and / or the 32nd identification information in the downlink packet to transmit, the QoS flow used in the transmission and reception of a specific downlink packet, the 32nd identification information. May be changed to the QoS flow indicated by.

Incidentally, UPF_A235, the 31st identification information, of the 32nd identification information, which identification information to put in the downlink packet, received identification information, and/or network capability information, and/or operator policy Etc., and/or may be determined based on the state of the network.

For example, UPF_A235, if the 31st identification information, and/or the 32nd identification information is received, and/or the 41st identification information, and/or the 42nd identification information is received, and/or If the SMF_A230 determines that the received request indicated by the 41st identification information and/or the 42nd identification information can be accepted, the 31st identification information and/or the 32nd identification information is included in the downlink packet. You may send it.

Note that the 32nd identification information may be determined based on the 42nd identification information. In other words, the 32nd identification information may be information identifying the same QoS flow as the QoS flow indicated by the 42nd identification information, or may identify a QoS flow different from the QoS flow indicated by the 42nd identification information. It may be information to be provided. Note that the determination by the UPF_A 235 which identification information should be included in the downlink packet is not limited to this.

UE_A10 receives the downlink packet (S1206). By receiving the downlink packet, UE_A10 recognizes the contents of various identification information included in the downlink packet.

UE_A10 further executes the sixth processing based on the reception of the downlink packet (S1208).

Here, the sixth process may be a process in which the UE_A10 recognizes the matter indicated by the UPF_A235. Furthermore, the sixth process may be a process in which the UE_A10 stores the received identification information as a context, and transfers the received identification information and/or user data to an upper layer and/or a lower layer. It may be processing.

Furthermore, the sixth process may be a process in which UE_A10 activates RQoS for user data communication. In other words, the sixth process, UE_A10, based on the received downlink packet, QoS rule for the uplink packet (Derived QoS QoS Rule), and / or may be a process of creating a routing rule. , The created QoS rule and/or the routing rule may be validated.

More specifically, the sixth process, UE_A10, even if the QoS rule associated with the routing information of the uplink packet paired with the routing information of the received downlink packet, and / or create a routing rule The created QoS rule and/or the routing rule may be validated. The QoS flow used for transferring the uplink packet indicated by the created QoS rule and/or the routing rule may be the QoS flow indicated by the 32nd identification information.

Further, the sixth process may be a process in which the UE_A10 recognizes the QoS flow and/or the QoS rule and/or the routing rule associated with the routing information of the received downlink packet. More specifically, in the sixth process, the UE_A10 recognizes that the QoS flow used to transfer the downlink packet indicated by the routing information of the received downlink packet is the QoS flow indicated by the 32nd identification information. You may.

Further, the sixth process may be a process in which the UE_A10 starts an RQoS timer (also referred to as a Reflective QoS Timer:RQ timer). More specifically, the sixth process may be a process in which the UE_A10 starts the RQoS timer in which the timer value received from the network and/or the timer value held by the UE_A10 is set.

Note that the RQoS timer may be started based on the creation and/or activation of the QoS rule and/or the routing rule. In addition, if the QoS rule associated with the routing information of the uplink packet paired with the routing information of the received downlink packet and/or the routing rule already exists, UE_A10 resets the running RQoS timer. You may start.

The timer value received from the network may be the timer value received from the device in the core network in the registration procedure and/or the PDU session establishment procedure, for example, in the registration procedure and/or the PDU session establishment procedure. It may be the timer value indicated by the 16th identification information. The timer value received from the network may be the timer value received by the UE_A10 from the network before the sixth process, but is not limited to this.

Also, the timer value held by UE_A10 may be the timer value preset in UE_A10 at the time of shipment. The timer value held by the UE_A10 may be the timer value set in the UE_A10, but is not limited to this.

Furthermore, if UE_A10 has previously transmitted an uplink packet containing the 41st identification information, and/or the 42nd identification information, the sixth process is UE_A10, UE-controlled RQoS activation controlled. It may be a process of recognizing that the procedure has been accepted by the network. The sixth process is not limited to these processes.

Next, the UE_A10 may transmit the uplink packet to the UPF_A235 based on the reception of the downlink packet and/or the completion of the sixth processing (S1210). Further, upon receiving the uplink packet, the UPF_A 235 may transfer the received uplink packet to the DN_A5 and/or the device within the DN_A5 (S1210). In this case, the DN_A5 and/or the device within the DN_A5 receives the uplink packet.

UE_A10 may use the QoS rule generated in the sixth process and/or the routing for transmitting the uplink packet. Furthermore, the uplink packet may be the same message as the previously transmitted uplink packet (S1200) or may be a different message.

Each device, based on the transmission and reception of downlink packets (S1206), and / or completion of the sixth process (S1208), and / or transmission and reception of uplink packets (S1210), the procedure of (A) in this procedure To complete.

Next, the steps when the 31st condition determination is false, that is, each step of the procedure (B) in this procedure will be described. The SMF_A230 transmits the RQoS validation rejection message to the UPF_A235 based on the thirty-first condition determination and/or the reception of the request notification message (S1212), and starts the procedure (B) in this procedure. Specifically, SMF_A230 sends an RQoS validation rejection message to UPF_A235 using the N4 interface. Note that the RQoS activation rejection message is not limited to this, and may be a message indicating that the request to activate RQoS for user data communication has been rejected.

Here, the SMF_A230 may include the 51st identification information in the RQoS activation refusal message, or may include the identification information to indicate that the request of the UE_A10 is rejected.

Furthermore, the SMF_A230 may indicate that the request for enabling RQoS has been rejected by transmitting the 51st identification information included in the RQoS enabling notification message, or may have rejected the request for enabling RQoS. It may indicate the reason or may indicate that RQoS cannot be activated.

Note that the SMF_A230 determines whether to include the 51st identification information in the RQoS activation rejection message, the received identification information, and/or the network capability information, and/or a policy such as an operator policy, and/or the network status. May be determined based on.

For example, SMF_A230, when receiving the 41st identification information, and/or the 42nd identification information, and/or when the 41st identification information and/or the received request indicated by the 42nd identification information cannot be accepted. The 51st identification information may be included in the RQoS activation notification message and transmitted. The determination by SMF_A230 which identification information should be included in the RQoS validation rejection message is not limited to this.

UPF_A235 receives the RQoS activation rejection message (S1212). UPF_A235 recognizes the content of various identification information contained in the RQoS validation rejection message by receiving the RQoS validation rejection message.

Further, UPF_A235 may receive the downlink packet transmitted from DN_A5 and/or the device in DN_A5 (S1214). UPF_A235 transmits the downlink packet to UE_A10 based on the reception of the RQoS activation rejection message and/or the reception of the downlink packet from DN_A5 (S1214).

Here, UPF_A235, the downlink packet may include the 51st identification information, by including this identification information, may indicate that RQoS for user data communication was not enabled, It may indicate that the UE_A10 request was not accepted.

Furthermore, the UPF_A235 may indicate that the request for enabling RQoS has been rejected by including the 51st identification information in the RQoS enabling notification message and transmitting it, or the request for enabling RQoS may be rejected. It may indicate the reason why it was done or indicate that RQoS cannot be activated.

The UPF_A235 determines whether to put the 51st identification information in the downlink packet, based on the received identification information and/or network capability information, and/or a policy such as an operator policy, and/or a network state. You may decide.

For example, UPF_A235, if the 51st identification information is received, and/or the 41st identification information, and/or if the 42nd identification information is received, and/or the received 41st identification information, and/or Alternatively, if the SMF_A 230 determines that the request indicated by the 42nd identification information cannot be accepted, the 51st identification information may be included in the RQoS activation notification message and transmitted. Note that the determination by the UPF_A 235 which identification information should be included in the downlink packet is not limited to this.

UE_A10 receives the downlink packet (S1214). By receiving the downlink packet, UE_A10 recognizes the contents of various identification information included in the downlink packet.

UE_A10 further executes the seventh process based on the reception of the downlink packet (S1216).

Here, UE_A10 is the 41st identification information, and / or if previously transmitted an uplink packet containing the 42nd identification information, the seventh process, UE_A10, UE-controlled RQoS activation procedure controlled May be the process of recognizing that it was rejected by the network, or the process of recognizing the reason why it was rejected.

In other words, the seventh process, UE_A10 may be a process of recognizing that the UE-led RQoS activation procedure controlled by the UE based on the received 51st identification information is not permitted, and is not permitted. It may be a process of recognizing the reason.

Further, the seventh process may be a process in which the UE_A10 starts a backoff timer for prohibiting the start of the RQoS activation procedure controlled by the UE for a certain period. The value of the back-off timer for prohibiting the start of the RQoS activation procedure controlled by the UE for a certain period may be a value preset in UE_A10 or a timer value received from the network. May be.

Further, the seventh process, UE_A10 may be a process of starting this procedure again after a certain period of time, is a process of starting a procedure for changing and/or disconnecting the established PDU session. It may be present, or may be a process of transitioning to a limited state of the request of UE_A10. The seventh process is not limited to these processes.

Each device completes the procedure (B) in this procedure based on transmission/reception of downlink packets (S1214) and/or completion of the seventh processing (S1216).

Each device completes this procedure based on the completion of procedure (A) or (B) in this procedure. It should be noted that each device may transition to a state in which RQoS for user data communication is enabled based on the completion of the procedure (A) in this procedure, or the procedure in (B) in this procedure. Based on the completion, it may be possible to recognize that this procedure has been rejected, transition to a state in which RQoS for user data communication is not enabled, or a state in which RQoS for user data communication is not applied. May be maintained.

Furthermore, each device may perform processing based on the identification information transmitted and received in this procedure based on the completion of this procedure. In other words, UE_A10 may perform the sixth process or the seventh process based on the completion of this procedure.

Furthermore, after completing this procedure, each device may perform user data communication using the QoS rule and/or the routing rule validated in this procedure. Furthermore, each device may start the RQoS deactivation procedure after completion of this procedure.

The 31st condition determination may be performed based on the uplink packet and/or the identification information and/or the subscriber information included in the request notification message, and/or the operator policy. For example, the thirty-first condition determination may be true when the network permits the request of UE_A10. The thirty-first condition determination may be false if the network does not permit the request from UE_A10. Further, the 31st condition determination, the network of the UE_A10 registration destination, and / or devices in the network, the function requested by UE_A10 may be true if it supports, false if it does not support. Good. The condition that determines the truth of the 31st condition determination is not limited to the above-described condition.

[1.3.4.2. Example of RQoS activation procedure controlled by network initiative]
An example of a procedure for executing the RQoS activation procedure controlled by the initiative of the network will be described with reference to FIG. In this chapter, the network-controlled RQoS activation procedure is also referred to as this procedure. It should be noted that this procedure may be referred to as an RQoS activation procedure controlled via a network-driven User Plane. Further, since the RQoS activation procedure controlled by the network is similar to the procedure (A) in the RQoS activation procedure controlled by the UE, only differences will be described here.

UE_A10 performs the above-described sixth process (S1208) based on the reception of the downlink packet (S1206). In the sixth process, the UE_A 10 can further reject the application of RQoS. In this case, UE_A10 transmits an uplink packet including information indicating that application of RQoS is rejected to UPF_A235 (S1210).

[1.3.5. Overview of RQoS deactivation procedure]
Next, a procedure for deactivating (also referred to as invalidating) activated Reflective QoS (RQoS) will be described. The procedures for deactivating RQoS include a first deactivation procedure initiated by the UE and a second deactivation procedure initiated by the network. These procedures are started while RQoS controlled via UP (User Plane) is valid. In other words, these procedures are started while the value of the RQoS timer has not expired.

Note that these procedures can also be used to disable RQoS controlled via UP initiated by the network initiative, and RQoS controlled via UP initiated by the UE initiative. It can also be used to disable.

[1.3.5.1. Outline of the first RQoS deactivation procedure]
First, the case of the first deactivation procedure will be described. UE_A10 is a device in the core network, in the header of the uplink packet to be transmitted, QFI (QoS Flow ID) for identifying the QoS flow to be deactivated, and a deactivation request (deactivation request). ) Indicating RQI (Reflective QoS Indication). When the RQI is composed of 1 bit, it is preferably set to 0, but it may be set to 1. Further, when the RQI is composed of a plurality of bits, it is preferable to set all 0s, but not limited to this, it may be set to all 1, for example. Further, the UE_A10 may include information indicating a deactivation request in the header of the uplink packet to be transmitted, instead of the RQI, and transmit the header. When requesting deactivation for multiple QoS flows, a set of QFI and RQI or a set of information indicating QFI and deactivation request is set in the header of the uplink packet. It can be included and sent. When requesting deactivation for all QoS flows, QFI may not be included. In addition, that UE_A10 includes information such as QFI and RQI in the header of the uplink packet may mean that UE_A10 includes information such as QFI and RQI in the uplink packet.

The device in the core network receives, from UE_A10, a header of an uplink packet including one or more sets of QFI and RQI, or one or more sets of QFI and information indicating a deactivation request. Here, the device in the core network may accept the request for deactivation for all the QoS flows when the deactivation is requested from the UE_A10 for the plurality of QoS flows, or all the QoS flows may be accepted. Request may be rejected, or a request for deactivation for some QoS flows may be accepted and a request for deactivation for the remaining QoS flows may be rejected. When the device in the core network accepts the deactivation request for a certain QoS flow, the QFI corresponding to the QoS flow and information indicating that the deactivation request is accepted are included in the downlink packet header. And send to UE_A10. Further, when rejecting a deactivation request for a certain QoS flow, the device in the core network sends the QFI corresponding to the QoS flow and information indicating that the deactivation request is rejected to the downlink packet. Include in the header of and send to UE_A10. Note that these pieces of information may be included in the header of one downlink packet and transmitted, or may be included in the headers of different downlink packets and transmitted. A device in the core network may not include a QFI if it accepts or rejects deactivation requests for all QoS flows. It should be noted that the fact that the device in the core network puts information such as QFI and RQI in the header of the downlink packet means that the device in the core network includes information such as QFI and RQI in the downlink packet. May be.

When UE_A10 receives the QFI and the header of the downlink packet containing the information indicating acceptance of the deactivation request, UE_A10 supports the QoS flow identified by the QFI even if the value of the RQoS timer has not disappeared. Delete the settings related to RQoS. In other words, UE_A10 receives the QFI and the header of the downlink packet containing the information indicating acceptance of the deactivation request, even if the execution of the RQoS timer has not expired, QoS identified by QFI. Delete the settings related to RQoS corresponding to the flow. At this time, UE_A10 applies default QoS to the QoS flow. On the contrary, UE_A10, QFI, when receiving the header of the downlink packet including information indicating that the request for deactivation is rejected, UE_A10, the setting related to RQoS corresponding to the QoS flow identified by QFI To maintain.

In addition, in the explanation for the first deactivation procedure, it was described that all the various information is included in the header and transmitted, but it is not limited to this. For example, UE_A10, when there is uplink data to be transmitted, at least part of various information that was included in the header of the uplink packet and transmitted, even if included in the uplink data and transmitted. Good. At this time, the network side can recognize the meaning of various information included in the uplink data. Further, when there is downlink data to be transmitted, the network may include at least a part of various information included in the header of the downlink packet for transmission in the downlink data. Good. At this time, the UE_A10 side can recognize the meaning of various types of information included in the downlink data.

[1.3.5.2. Overview of the second RQoS deactivation procedure]
Next, the case of the second deactivation procedure will be described. The device in the core network may be inactivated for all one or more QoS flows, may be inactivated for some QoS flows, or may be inactivated for some QoS flows. May be deactivated by When deactivating a certain QoS flow, the device in the core network includes a QFI corresponding to the QoS flow and information indicating deactivation, in the header of the downlink packet, and in UE_A10. To send. When deactivating a certain QoS flow, these pieces of information may be included in the header of one downlink packet and transmitted, or may be included in the headers of different downlink packets and transmitted. good. The device in the core network may not include the QFI when deactivating all the QoS flows. Note that the device in the core network does not transmit anything unless it is deactivated for a certain QoS flow.

When the UE_A10 receives the QFI and the header of the downlink packet including the information indicating that it is deactivated, the RQoS-related settings corresponding to the QoS flow identified by the QFI even if the value of the RQoS timer has not disappeared. To delete. In other words, UE_A10, when receiving the QFI and the header of the downlink packet containing information indicating deactivation, corresponds to the QoS flow identified by the QFI even if the execution of the RQoS timer has not expired. Delete the settings related to RQoS. At this time, UE_A10 applies default QoS to the QoS flow. On the contrary, when UE_A10 does not receive the QFI and the header of the downlink packet including the information indicating the deactivation, UE_A10 maintains the setting related to the RQoS corresponding to the QoS flow identified by the QFI.

Note that, in the explanation for the second deactivation procedure, it has been stated that all the various information is included in the header and transmitted, but it is not limited to this. For example, if there is downlink data to be transmitted, the network may include at least a part of various information included in the header of the downlink packet for transmission in the downlink data. Good. At this time, the UE_A10 side can recognize the meaning of various types of information included in the downlink data.

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

The program for realizing the functions of the embodiments according 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 in this recording medium. The “computer system” here is a computer system built in the apparatus and includes an operating system and hardware such as peripheral devices. Further, the “computer-readable recording medium” is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another computer-readable recording medium. Is also good.

Also, each functional block or various features of the device used in the above-described embodiments may be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other. Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor, conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be formed of a digital circuit or an analog circuit. Further, in the case where an integrated circuit technology that replaces the current integrated circuit has emerged due to the progress of semiconductor technology, one or more aspects of the present invention can use a new integrated circuit according to the technology.

Note that the present invention is not limited to the above embodiment. Although one example of the device is described in the embodiment, the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, such as an AV device or a kitchen device. It can be applied to terminal devices or communication devices such as cleaning/laundry equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

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

Claims

UE (User Equipment; terminal device),
Equipped with a transmitter,
The first PDU (Protocol Data Unit or Packet Data Unit) session establishment request message is a PDU session establishment request message using the first user identifier and the first DNN (Data Network Name),
The transmission unit, in response to the first PDU session establishment request message, including a rejection reason value indicating user authentication or authorization failed, EAP (Extensible Authentication Protocol)-PDU session establishment rejection message that does not include rejection reason information indicating failure. If the user ID is received, the user ID for the first DNN is changed until the user ID is changed to a user ID different from the first user ID, or the terminal power is turned on/off or the USIM (Universal Subscriber Identity Module) is removed/inserted. Regulate the transmission of the second PDU session establishment request message used,
UE characterized by that.
UE (User Equipment; terminal device),
Equipped with a transmitter,
The first PDU (Protocol Data Unit or Packet Data Unit) session establishment request message is a PDU session establishment request message using the first user identifier and the first DNN (Data Network Name),
The transmission unit, in response to the first PDU session establishment request message, including a rejection reason value indicating user authentication or authorization failed, EAP (Extensible Authentication Protocol)-PDU session establishment rejection message that does not include rejection reason information indicating failure. When receiving the, regulates the second PDU session establishment request message using the user identifier for the first DNN,
When regulating the second PDU session establishment request message, if changed to a user identifier different from the first user identifier, to the first DNN, the second PDU session using the user identifier Allow sending an establishment request message,
UE characterized by that.
UE (User Equipment),
Equipped with a transmitter,
The first PDU (Protocol Data Unit or Packet Data Unit) session establishment request uses the first user identifier and the first DNN (Data Network Name) and the first S-NSSAI (Single Network Slice Selection Assistance information). PDU session establishment request
The transmission unit, in response to the first PDU session establishment request, a PDU session establishment rejection message that does not include rejection reason information indicating EAP (Extensible Authentication Protocol)-failure including a rejection reason value indicating user authentication or authorization failed. If received, until changing to a user identifier different from the first user identifier, or until the terminal power on / off, or the removal and insertion of the USIM (Universal Subscriber Identity Module), to the first DNN and the first S-NSSAI Restricting the transmission of the second PDU session establishment request message using the user identifier for the
UE characterized by that.
UE (User Equipment; terminal device),
Equipped with a transmitter,
The first PDU (Protocol Data Unit or Packet Data Unit) session establishment request message, the first user identifier and the first DNN (Data Network Name) and the first S-NSSAI (Single Network Slice Selection Assistance information). The PDU session establishment request message used,
The transmission unit, with respect to the first PDU session establishment request message, a rejection reason value indicating a PDU session establishment rejection message that does not include rejection reason information indicating user authentication or authorization failed and indicating EAP (Extensible Authentication Protocol)-failure. When receiving the, regulates the second PDU session establishment request message using the user identifier for the first DNN and the first S-NSSAI,
When regulating the second PDU session establishment request message, if changed to a user identifier different from the first user identifier, the user identifier for the first DNN and the first S-NSSAI. Allows the transmission of the second PDU session establishment request message used,
UE characterized by that.
SMF (Session Management Function)
If the user identifier included in the PDU (Protocol Data Unit or Packet Data Unit) session establishment request does not comply with the local policy, the PDU session establishment authentication authorization procedure using EAP (Extensible Authentication Protocol) is not executed and user authentication is performed. An SMF having a transmission unit for transmitting a PDU session establishment refusal message to a UE (User Equipment; terminal device) including a rejection reason value indicating or authorization failed.