WO2021132190A1 - Ue - Google Patents

Abstract

One embodiment of the present invention provides a communication method which uses the ATSSS function or eATSSS function and takes UE capability and/or the 5GC capability and/or a UE request or the like into consideration, as a result of: transmission by a UE to a core network of a PDU session establishment request message which includes information expressing that the UE supports the eATSSS function for communicating using two SA PDU sessions configured from a first SA PDU session using 3GPP access and a second SA PDU session using non-3GPP access, information expressing that the UE supports the ATSSS-LL function, and information expressing that the UE supports the MPTCP function; and verification thereby that the SA PDU sessions for the eATSSS function have been established upon receiving, from the core network, a PDU session establishment acceptance message which includes the ATSSS container IE which includes the ATSSS rule which includes the steering function expressing the eATSSS function.

Description

UE

This application relates to UE. This application claims the benefit of priority to Japanese Patent Application No. 2019-232440, which is a Japanese patent application filed on December 24, 2019, and by referring to it, the content of the application is claimed. All are included in this application.

The 3GPP (3rd Generation Partnership Project) is studying the system architecture of 5GS (5G System), which is a 5th generation (5G) mobile communication system, and discussions are being held to support new procedures and new functions. There is. In 5GS, a new core network, 5GC (5G Core Network), is being considered in order to provide a wide variety of services. Release 16 uses a special PDU session called a multi-access PDU session (also called a MA PDU session) instead of the PDU (Protocol Data Unit) session (also called a single access PDU session or SA PDU session) specified in Release 15. Discussions have begun to support the ATSSS (Access Traffic Steering, Switching and Splitting) function (also referred to as the ATSSS function of Release 16) that communicates with 5GS (see Non-Patent Documents 1 to 4). .. Furthermore, in Release 17, a technology for improving the ATSSS function will be examined (see Non-Patent Document 5).

In Release 17, where new functions are added based on the contents of Release 16, UE (User Equipment) supports the ATSSS function that communicates using the MAPDU session, but it is an improved function of the ATSSS function and MAPDU. There may be UEs that do not support the eATSSS (enhanced ATSSS or evolved ATSSS) function (also called the second ATSSS function, the ATSSS function of Release 17) that communicates by a session-free method. In addition, there may be UEs that do not support the ATSSS function but support the eATSSS function, and UEs that support both the ATSSS function and the eATSSS function.

Similarly, for 5GC, there may be a 5GC that supports the ATSSS function but does not support the eATSSS function, a 5GC that does not support the ATSSS function but supports the eATSSS function, and a 5GC that supports both the ATSSS function and the eATSSS function. ..

In such a situation, for example, even if the UE requests the establishment of a PDU session for communication using the ATSSS function or eATSSS function, or the UE performs communication using the ATSSS function or eATSSS function. Whether or not it requires the establishment of a PDU session to do so, 5GC is the UE's ability (also known as UE capability) and / or the 5GC's ability (also referred to as Network capability) and / or the UE's preference (also referred to as UE capability). Based on UE preference) etc., it may be possible to allow the establishment of a PDU session for communication using the ATSSS function or eATSSS function.

However, the solution to such a problem is not disclosed.

One aspect of the present invention has been made in view of the above circumstances, and an object thereof is an ATSSS function in consideration of the ability of UE and / or the ability of 5GC and / or the desire of UE. Alternatively, it is to realize a communication method using the eATSSS function.

The UE of one embodiment of the present invention is a UE (User Equipment) including a control unit and a transmission / reception unit, and the transmission / reception unit is via a first SA PDU session via 3GPP access and non-3GPP access. Information indicating that the UE supports the eATSSS function that communicates using two SA PDU sessions consisting of a second SA PDU session, information indicating that the UE supports the ATSSS-LL function, and MPTCP. A PDU session establishment request message containing information indicating that the function is supported by the UE is sent to the core network, and the PDU containing the ATSSS container IE containing the ATSSS rule including the steering function indicating the eATSSS function from the core network. Upon receiving the session establishment acceptance message, the control unit recognizes that the SA PDU session for the eATSSS function has been established.

According to one aspect of the present invention, a communication method using the ATSSS function or the eATSSS function can be realized in consideration of the capability of the UE and / or the capability of 5GC and / or the desire of the UE.

It is a figure explaining the outline of the mobile communication system 1. It is a figure explaining the detailed structure of the mobile communication system 1. It is a figure explaining the apparatus configuration of UE. It is a figure mainly explaining the structure of an access network apparatus. It is a figure mainly explaining the structure of a core network apparatus. It is a figure explaining the registration procedure. It is a figure explaining the PDU session establishment procedure through 3GPP access. It is a figure explaining the PDU session establishment procedure through non-3GPP access.

In the following, the mobile communication system, the configuration of each device, highly specialized terms used in each embodiment, identification information, etc., which have many common parts in each embodiment, will be described, and then the present invention will be implemented. Each embodiment will be described.

[1. Overview of mobile communication system]
Here, the mobile communication system will be described.

First, FIG. 1 is a diagram for explaining the outline of the mobile communication system 1, and FIG. 2 is a diagram for explaining the detailed configuration of the mobile communication system 1.

FIG. 1 shows that the mobile communication system 1 is composed of UE (User Equipment) _10, access network _100, access network _102, core network _200, and DN (Data Network) _300. In addition, these devices / networks may be described by omitting symbols such as UE, access network, core network, DN and the like.

In Fig. 2, UE_10, base station device_110, base station device_120, AMF (Access and Mobility Management Function) _210, SMF (Session Management Function) _220, UPF (User Plane Function) _230, N3IWF (Non) -3GPP InterWorking Function) _240, PCF (Policy Control Function) _250, DN_300 and other device / network functions, and interfaces for connecting these devices / network functions to each other are described.

Note that 5GS (5G System), which is a 5G system, is configured to include a UE, an access network, and a core network, but may also include a DN.

UE is a device that can connect to network services via 3GPP access (3GPP access network, also called 3GPP AN) and / or non-3GPP access (non-3GPP access network, also called non-3GPP AN). is there. The UE may be a terminal device capable of wireless communication such as a mobile phone or a smartphone, and may be a terminal device capable of connecting to EPS (Evolved Packet System), which is a 4G system, or 5GS. In addition, the UE may be provided with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device. The UE may be able to use the ATSSS function and / or the eATSSS function.

The access network may also be referred to as a 5G access network (5G AN). 5GAN is composed of NG-RAN (NG Radio Access Network) and / or non-3GPP access network (non-3GPP AN).

One or more base station devices are installed in NG-RAN. The base station device may be gNB. gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to 5GC via an NG interface (including an N2 interface or an N3 interface). That is, gNB is a base station device newly designed for 5GS and has a function different from that of the base station device (eNB) used in EPS. When there are a plurality of gNBs, each gNB is connected to each other by, for example, an Xn interface. The base station device_110 corresponds to gNB.

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

Further, in the following, the device included in the access network and / or the device included in the access network may be referred to as an access network device.

Access network _100 supports 3GPP access, and access network _102 supports non-3GPP access.

In addition, the base station device _110 is arranged in the access network _100, and the base station device _120 and / or TNAP (Trusted Non-3GPP Access Point) is arranged in the access network _102. The base station device_110 and / or the base station device_120 and / or TNAP may be able to use the ATSSS function and / or the eATSSS function.

Access network_102 may also be referred to as Untrusted Non-3GPP access or Trusted Non-3GPP access. The base station device _120 and N3IWF in Fig. 2 describe the case of Untrusted Non-3GPP access. That is, when the access network_102 is Untrusted Non-3GPP access, the base station device _120 and N3IWF are used. When the access network_102 is Trusted Non-3GPP access (also referred to as TNAN), TNAP and TNGF (Trusted Non-3GPP Gateway Function) are used instead of the base station device _120 and N3IWF.

In addition, the core network is compatible with 5GC (5G Core Network). For example, AMF, UPF, SMF, PCF and the like are arranged in 5GC. Here, 5GC may be expressed as 5GCN. The AMF and / or UPF and / or SMF and / or PCF may be able to use the ATSSS function and / or the eATSSS function.

Also, N3IWF and TNGF may be located in access network_102 or core network_200. N3IWF and / or TNGF may be able to utilize the ATSSS function and / or the eATSSS function.

In the following, the core network and / or the device included in the core network may be referred to as a core network device.

The core network may be an IP mobile communication network operated by a mobile network operator (MNO) that connects the access network and the DN, or a mobile network operator 1 that operates and manages the mobile communication system 1. It may be a core network for a mobile network operator, or a core network for a virtual mobile network operator such as MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual mobile communication service provider. ..

Further, the DN may be a DN that provides a communication service to the UE. Further, the DN may be configured as a packet data service network or may be configured for each service. Further, the DN may include a connected communication terminal. Therefore, connecting to the DN may be connecting to a communication terminal or server device arranged in the DN. Further, sending and receiving user data to and from the DN may be sending and receiving user data to and from a communication terminal or server device arranged in the DN.

In the following, at least a part of an access network, a core network, a DN, and / or one or more devices included in these may be referred to as a network or a network device. That is, a network and / or network device sending and receiving messages and / or performing a procedure means that an access network, a core network, at least a portion of a DN, and / or one or more devices contained therein. , Sending and receiving messages, and / or performing procedures.

Also, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the DN via the access network and the core network. That is, the UE can send / receive (communicate) user data with the DN. Further, when the UE transmits / receives user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

Here, IP communication is data communication using IP, and data is transmitted and received by IP packets. An IP packet is composed of an IP header and a payload part. The payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS.

In addition, non-IP communication is data communication that does not use IP, and data is transmitted and received in a format different from the structure of IP packets. For example, non-IP communication may be data communication realized by sending and receiving application data to which an IP header is not added, or a UE can add another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be sent and received may be sent and received.

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

In addition, each storage unit (storage unit_330, storage unit_440, storage unit_540) in each device / function appearing below is, for example, a semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive). ) Etc. In addition, each storage unit has not only the information originally set from the shipping stage, but also devices / functions other than its own device / function (for example, UE and / or access network device, and / or core network device, and /. Or PDN and / or DN) can store various information sent and received. In addition, each storage unit can store identification information, control information, flags, parameters, and the like included in control messages transmitted and received in various communication procedures described later. Further, each storage unit may store such information for each UE.

[2.1. UE_10 device configuration]
First, an example of the device configuration of the UE used in each embodiment will be described with reference to FIG. The UE is composed of a control unit_300, an antenna_310, a transmission / reception unit_320, and a storage unit_330. The control unit_300, the transmission / reception unit_320, and the storage unit_330 are connected via a bus. The transmitter / receiver_320 is connected to the antenna_310.

Control unit_300 is a functional unit that controls the operation and functions of the entire UE. The control unit_300 may process all the functions that the other functional units (transmission / reception unit_320, storage unit_330) in the UE do not have. The control unit_300 realizes various processes in the UE by reading and executing various programs stored in the storage unit_330 as needed.

Further, the control unit_300 determines whether or not to request the communication by the ATSSS function and / or the eATSSS function according to the control information received from the core network side or the control information stored in the storage unit_330. It may have a function to perform. For example, the control unit_300 may determine whether to require communication by the ATSSS function and / or the eATSSS function based on one or more URSP rules received from the PCF.

In addition, the control unit_300 has a function of determining to which access the uplink traffic should be routed according to one or more ATSSS rules received from the SMF when communicating by the ATSSS function or the eATSSS function. May have.

In addition, the control unit_300 controls the transmission / reception unit 320 so that it can communicate appropriately according to these decisions.

The transmission / reception unit_320 is a functional unit for wireless communication with a base station device or the like in the access network via the antenna_310. That is, the UE can send and receive user data and / or control information to and from the access network device and / or the core network device and / or the DN by using the transmission / reception unit_320.

Specifically, the UE can communicate with the base station device_110, the base station device_120, and TNAP by using the transmission / reception unit_320. That is, the UE communicates with the base station device_110 when communicating via 3GPP access. The UE also communicates with base station device_120 or TNAP when communicating via non-3GPP access. More specifically, the UE communicates with base station apparatus_120 when communicating via Untrusted non-3GPP access, and the UE communicates with TNAP when communicating via Trusted non-3GPP access. .. In this way, there can be three communication paths between the UE and the access network device.

In addition, the UE can communicate with the core network device (AMF, SMF, UPF, etc.) by using the transmitter / receiver _320.

In addition, the UE can send and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface (the interface between the UE and AMF). However, since the N1 interface is a logical interface, communication between the UE and AMF is actually performed via base station device_110, base station device_120, and TNAP. Specifically, when communicating via 3GPP access, the UE can communicate with AMF via base station device_110. In addition, when communicating via non-3GPP access (Untrusted non-3GPP access), the UE can communicate with AMF via base station device _120 and N3IWF. In addition, when communicating via non-3GPP access (Trusted non-3GPP access), the UE can communicate with AMF via TNAP and TNGF. In this way, there can be three communication paths between the UE and AMF. The information exchanged between the UE and AMF may be mainly control information.

In addition, the UE can communicate with the SMF using the N1 interface and the N11 interface (the interface between the AMF and the SMF). Specifically, the UE can communicate with the SMF via the AMF. More specifically, the UE can communicate with the SMF via the base station device_110 and the AMF when communicating via 3GPP access. Further, when communicating via non-3GPP access (Untrusted non-3GPP access), the UE can communicate with SMF via base station device _120 and N3IWF and AMF. In addition, when communicating via non-3GPP access (Trusted non-3GPP access), the UE can communicate with SMF via TNAP, TNGF, and AMF. In this way, there can be three communication paths between the UE and SMF. The information exchanged between the UE and the SMF may be mainly control information.

Also, the UE can communicate with the UPF using the N3 interface (the interface between the access network and the UPF). Specifically, the UE can communicate with the UPF via the base station device_110 when communicating via 3GPP access. Further, when communicating via non-3GPP access (Untrusted non-3GPP access), the UE can communicate with the UPF via the base station device _120 and N3IWF. Also, when communicating via non-3GPP access (Trusted non-3GPP access), the UE can communicate with the UPF via TNAP and TNGF. In this way, there can be three communication paths between the UE and UPF. The information exchanged between the UE and the UPF may be mainly user data.

In addition, the UE can communicate with the PCF using the N1 interface, the N11 interface, and the N7 interface (the interface between the SMF and the PCF). Specifically, the UE can communicate with the PCF via AMF and SMF. More specifically, the UE can communicate with the PCF via the base station device_110 and the AMF and SMF when communicating via 3GPP access. Further, when communicating via non-3GPP access (Untrusted non-3GPP access), the UE can communicate with the PCF via the base station device _120, N3IWF, AMF, and SMF. In addition, when communicating via non-3GPP access (Trusted non-3GPP access), the UE can communicate with PCF via TNAP, TNGF, AMF, and SMF. In this way, there can be three communication paths between the UE and the PCF. The information exchanged between the UE and the PCF may be mainly control information.

In addition, the UE can communicate with the DN using the N3 interface and the N6 interface (the interface between the UPF and the DN). Specifically, when communicating via 3GPP access, the UE can communicate with the DN via base station device_110 and UPF. Further, when communicating via non-3GPP access (Untrusted non-3GPP access), the UE can communicate with the DN via the base station device _120, N3IWF, and UPF. In addition, when communicating via non-3GPP access (Trusted non-3GPP access), the UE can communicate with the DN via TNAP, TNGF, and UPF. In this way, there can be three communication paths between the UE and the DN. The information exchanged between the UE and the DN may be mainly user data.

It should be noted that the above only describes the communication between the UE and the typical device / function in the present specification, and the UE is a device / function other than the above, that is, an access network device and / or a core network device other than the above. Etc. may be able to communicate with.

The storage unit_330 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UE. Further, it is desirable that the control information received from the core network side is stored in the storage unit_330. For example, the storage unit_330 may store the ATSSS rule and / or the first ATSSS rule and / or the second ATSSS rule and the like.

Also, the UE may be a UE that supports the ATSSS function and / or the eATSSS function.

[2.2. Device configuration of base station device_110]
Next, a device configuration example of the base station device_110 used in each embodiment will be described with reference to FIG.

Base station device_110 is a base station device located in 3GPP access. The base station device_110 is composed of a control unit_400, an antenna_410, a network connection unit_420, a transmission / reception unit_430, and a storage unit_440. The control unit _400, the network connection unit _420, the transmission / reception unit _430, and the storage unit _440 are connected via a bus. The transmitter / receiver_430 is connected to the antenna_410.

Control unit_400 is a functional unit that controls the operation and functions of the entire base station device_110. The control unit_400 may process all the functions that the other functional units (network connection unit_420, transmission / reception unit_430, storage unit_440) in the base station apparatus_110 do not have. The control unit _400 realizes various processes in the base station device _110 by reading and executing various programs stored in the storage unit _440 as needed.

The network connection unit_420 is a functional unit for the base station device_110 to communicate with other access network devices and / or AMF and / or UPF. That is, the base station device_110 can send and receive control information and / or user data with other access network devices and / or AMF and / or UPF and the like by using the network connection unit_420. ..

Specifically, the base station device_110 can communicate with other access network devices via the Xn interface (interface between access network devices) by using the network connection unit_420. The base station apparatus_110 can communicate with the AMF via the N2 interface (the interface between the access network and the AMF) by using the network connection unit_420. Further, the base station device_110 can communicate with the UPF via the N3 interface by using the network connection unit_420.

The transmitter / receiver_430 is a functional unit for wireless communication with the UE via the antenna_410. That is, the base station device_110 can transmit / receive user data and / or control information between the UE and the UE by using the transmission / reception unit_430 and the antenna_410.

Further, the base station device_110 has a function of transmitting the user data and / or the control information to the core network device when the user data and / or the control information addressed to the core network device is received from the UE. Further, the base station device_110 has a function of transmitting the user data and / or the control information to the UE when the user data and / or the control information addressed to the UE is received from the core network device.

It should be noted that the above only describes the communication between the base station device_110 and a typical device / function, and the base station device_110 is a device / function other than the above, that is, an access network device other than the above and /. Alternatively, it may be able to communicate with a core network device or the like.

The storage unit_440 is a functional unit for storing programs, user data, control information, etc. required for each operation of the base station device_110.

Further, the base station device_110 may be a base station device that supports the ATSSS function and / or the eATSSS function.

[2.3. Device configuration of base station device_120]
Next, a device configuration example of the base station device_120 used in each embodiment will be described with reference to FIG.

Base station device_120 is a base station device located in non-3GPP access (Untrusted non-3GPP access). The base station device_120 is composed of a control unit_400, an antenna_410, a network connection unit_420, a transmission / reception unit_430, and a storage unit_440. The control unit _400, the network connection unit _420, the transmission / reception unit _430, and the storage unit _440 are connected via a bus. The transmitter / receiver_430 is connected to the antenna_410.

Control unit_400 is a functional unit that controls the operation and functions of the entire base station device_120. The control unit_400 may process all the functions that the other functional units (network connection unit_420, transmission / reception unit_430, storage unit_440) in the base station apparatus_120 do not have. The control unit _400 realizes various processes in the base station apparatus _120 by reading and executing various programs stored in the storage unit _440 as needed.

The network connection unit_420 is a functional unit for the base station device_120 to communicate with the N3IWF, and is a functional unit for communicating with the AMF and / or UPF via the N3IWF. That is, the base station device_120 can send and receive control information and / or user data to and from the N3IWF by using the network connection unit_420. Further, the base station apparatus _120 can transmit and receive control information and / or user data with the AMF and / or the UPF or the like via the N3IWF by using the network connection unit _420.

That is, the base station device_120 can communicate with the N3IWF via the Y2 interface (the interface between the access network and the N3IWF) by using the network connection unit_420. In addition, the base station device_120 can communicate with the AMF via the N2 interface (the interface between the N3IWF and the AMF) via the N3IWF. In addition, the base station device_120 can communicate with the UPF via the N3 interface (the interface between the N3IWF and the UPF) via the N3IWF.

The transmitter / receiver_430 is a functional unit for wireless communication with the UE via the antenna_410. That is, the base station apparatus_120 uses the transmitter / receiver _430 and the antenna_410 to transmit user data and / or control information between the UE and the UE via the Y1 interface (the interface between the access network and the UE). You can send and receive.

Further, the base station device_120 has a function of transmitting the user data and / or the control information to the core network device when the user data and / or the control information addressed to the core network device is received from the UE. Further, the base station apparatus_120 has a function of transmitting the user data and / or the control information to the UE when the user data and / or the control information addressed to the UE is received from the core network apparatus.

It should be noted that the above only describes the communication between the base station device_120 and a typical device / function, and the base station device_120 is a device / function other than the above, that is, an access network device other than the above and /. Alternatively, it may be able to communicate with a core network device or the like.

The storage unit_440 is a functional unit for storing programs, user data, control information, etc. required for each operation of the base station device_120.

Further, the base station device_120 may be a base station device that supports the ATSSS function and / or the eATSSS function.

[2.4. TNAP device configuration]
Next, an example of the TNAP device configuration used in each embodiment will be described with reference to FIG. TNAP is a base station device (also referred to as an access point) located in non-3GPP access (Trusted non-3GPP access). TNAP consists of a control unit_400, an antenna_410, a network connection unit_420, a transmission / reception unit_430, and a storage unit_440. The control unit _400, the network connection unit _420, the transmission / reception unit _430, and the storage unit _440 are connected via a bus. The transmitter / receiver_430 is connected to the antenna_410.

Control unit_400 is a functional unit that controls the operation and functions of the entire TNAP. The control unit_400 may process all the functions that the other functional units (network connection unit_420, transmission / reception unit_430, storage unit_440) in TNAP do not have. The control unit _400 realizes various processes in TNAP by reading and executing various programs stored in the storage unit _440 as needed.

The network connection unit_420 is a functional unit for TNAP to communicate with TNGF, and is a functional unit for communicating with AMF and / or UPF via TNGF. That is, TNAP can send and receive control information and / or user data to and from TNGF using the network connection unit_420. In addition, TNAP can send and receive control information and / or user data to and from AMF and / or UPF and the like via TNGF using the network connection unit_420.

That is, TNAP can communicate with TNGF via the Ta interface (the interface between TNAP and TNGF) by using the network connection part_420. In addition, TNAP can communicate with AMF via N2 interface (interface between TNGF and AMF) via TNGF. In addition, TNAP can communicate with UPF via N3 interface (interface between TNGF and UPF) via TNGF.

The transmitter / receiver_430 is a functional unit for wireless communication with the UE via the antenna_410. That is, TNAP can send and receive user data and / or control information to and from the UE via the Yt interface (interface between TNAP and UE) using the transmitter / receiver _430 and antenna_410. ..

Further, TNAP has a function of transmitting user data and / or control information to the core network device when receiving user data and / or control information addressed to the core network device from the UE. Further, TNAP has a function of transmitting the user data and / or the control information to the UE when the user data and / or the control information addressed to the UE is received from the core network device.

It should be noted that the above only describes the communication between TNAP and a typical device / function, and TNAP communicates with a device / function other than the above, that is, an access network device and / or a core network device other than the above. You may be able to.

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

Further, the TNAP may be a TNAP that supports the ATSSS function and / or the eATSSS function.

[2.5. Device configuration of N3IWF_240]
Next, an example of the device / functional configuration of the N3IWF used in each embodiment will be described with reference to FIG. N3IWF is a device and / or function that is placed between non-3GPP access and 5GC when a UE connects to 5GS via non-3GPP access (Untrusted non-3GPP access). It is located in non-3GPP access (Untrusted non-3GPP access) or core network. N3IWF consists of a control unit_500, a network connection unit_520, and a storage unit_540. The control unit_500, network connection unit_520, and storage unit_540 are connected via a bus.

Control unit_500 is a functional unit that controls the operation and functions of the entire N3IWF. The control unit_500 may process all the functions that the other functional units (network connection unit_520, storage unit_540) in the N3IWF do not have. The control unit _500 realizes various processes in the N3 IWF by reading and executing various programs stored in the storage unit _540 as needed.

The network connection unit_520 is a functional unit for N3IWF to communicate with the base station device_120 and / or AMF and / or UPF. That is, the N3IWF can send and receive control information and / or user data to and from the base station device_120 using the network connection unit_520. In addition, N3IWF can send and receive control information and / or user data with AMF and / or UPF, etc. using the network connection unit_520.

That is, the N3IWF can communicate with the base station device_120 via the Y2 interface by using the network connection part_520. The N3IWF can also communicate with the AMF via the N2 interface. N3IWF can also communicate with UPF via the N3 interface.

The above only describes the communication between the N3IWF and a typical device / function, and the N3IWF communicates with a device / function other than the above, that is, an access network device and / or a core network device other than the above. You may be able to.

Storage unit_540 is a functional unit for storing programs, user data, control information, etc. required for each operation of N3IWF.

N3IWF has a function to establish an IPsec tunnel between the UE and an IPsec tunnel, a function to terminate the N2 interface for the control plane, a function to terminate the N3 interface for the user plane, a function to relay NAS signaling between the UE and AMF, and a PDU session. Ability to process N2 signaling from SMF for and QoS, a function to establish IPsec SA (Security Association) to support PDU session traffic, a function to relay userplane packets between UE and UPF (IPsec) Includes packet encapsulation / decapsulation for N3 tunnels), functions as a local mobility anchor within an untrusted non-3GPP access network, and the ability to select AMF. All of these functions may be controlled by the control unit_500.

Further, the N3IWF may be an N3IWF that supports the ATSSS function and / or the eATSSS function.

[2.6. TNGF equipment configuration]
Next, an example of the device / functional configuration of the TNGF used in each embodiment will be described with reference to FIG. TNGF is a device and / or function that is placed between non-3GPP access and 5GC when a UE connects to 5GS via non-3GPP access (Trusted non-3GPP access). It is located in non-3GPP access (Trusted non-3GPP access) or core network. The TNGF consists of a control unit_500, a network connection unit_520, and a storage unit_540. The control unit_500, network connection unit_520, and storage unit_540 are connected via a bus.

Control unit_500 is a functional unit that controls the operation and functions of the entire TNGF. The control unit_500 may process all the functions that the other functional units (network connection unit_520, storage unit_540) in the TNGF do not have. The control unit_500 realizes various processes in the TNGF by reading and executing various programs stored in the storage unit_540 as needed.

Network connection _520 is a functional unit for TNGF to communicate with TNAP and / or AMF and / or UPF. That is, the TNGF can send and receive control information and / or user data to and from TNAP using the network connection unit_520. Further, the TNGF can send and receive control information and / or user data to and from the AMF and / or the UPF or the like by using the network connection unit_520.

In other words, TNGF can communicate with TNAP via the Y2 interface by using the network connection part_520. The TNGF can also communicate with the AMF via the N2 interface. TNGF can also communicate with UPF via the N3 interface.

The above only describes the communication between the TNGF and a typical device / function, and the TNGF communicates with a device / function other than the above, that is, an access network device and / or a core network device other than the above. You may be able to.

Storage unit_540 is a functional unit for storing programs, user data, control information, etc. required for each operation of TNGF.

In addition, TNGF has a function to terminate the N2 interface and N3 interface, a function to act as an approver when the UE registers with 5GC via TNAN, a function to select AMF, and a NAS message between UE and AMF. Ability to relay transparently (without processing), process SMF and N2 signaling to support PDU sessions and QoS, relay PDUs between UE and UPF transparently (without processing) It has a function and a function as a local mobility anchor in TNAN. All of these functions may be controlled by the control unit_500.

Further, the TNGF may be a TNGF that supports the ATSSS function and / or the eATSSS function.

[2.7. Device configuration of AMF_210]
Next, an example of the AMF device configuration used in each embodiment will be described with reference to FIG. The AMF consists of a control unit_500, a network connection unit_520, and a storage unit_540. The control unit_500, network connection unit_520, and storage unit_540 are connected via a bus. The AMF may be a node that handles the control plane.

Control unit_500 is a functional unit that controls the operation and functions of the entire AMF. The control unit_500 may process all the functions that the other functional units (network connection unit_520, storage unit_540) in the AMF do not have. The control unit_500 realizes various processes in AMF by reading and executing various programs stored in the storage unit_540 as needed.

The network connection _520 is a base station device in 5GAN and / or other AMF and / or SMF, and / or PCF, and / or NSSF (Network Slice Selection Function), and / or UDM. (Unified Data Management) and / or a functional part for connecting to SCEF (Service Capability Exposure Function). That is, the AMF uses the network connection _520 to use the base station equipment in 5GAN and / or other AMF and / or SMF, and / or PCF, and / or NSSF, and / or UDM, and User data and / or control information can be sent and received with / or SCEF.

Explaining in detail with reference to FIG. 2, the AMF in the 5GC can communicate with the base station device via the N2 interface by using the network connection _520, and the N14 interface (between AMFs). Can communicate with other AMFs via interface), can communicate with SMF via N11 interface, and can communicate with PCF via N15 interface (interface between AMF and PCF). It can communicate with NSSF via the N22 interface (the interface between AMF and NSSF) and with UDM via the N8 interface (the interface between AMF and UDM). In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_520. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN.

Storage unit_540 is a functional unit for storing programs, user data, control information, etc. required for each operation of AMF.

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

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

In other words, the 5GMM-REGISTERED state may be a state in which each device has established a 5GMM context or a PDU session context. When each device is in the 5GMM-REGISTERED state, UE_10 may start sending and receiving user data and control messages, or may respond to paging. Further, when each device is in the 5GMM-REGISTERED state, UE_10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.

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

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

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

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

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

Also, the AMF may be an AMF that supports the ATSSS function and / or the eATSSS function.

[2.8. Device configuration of SMF_220]
Next, an example of the device configuration of the SMF used in each embodiment will be described with reference to FIG. The SMF consists of a control unit_500, a network connection unit_520, and a storage unit_540. The control unit_500, network connection unit_520, and storage unit_540 are connected via a bus. The SMF may be a node that handles the control plane.

Control unit_500 is a functional unit that controls the operation and functions of the entire SMF. The control unit_500 may process all the functions that the other functional units (network connection unit_520, storage unit_540) in the SMF do not have. The control unit_500 realizes various processes in the SMF by reading and executing various programs stored in the storage unit_540 as needed.

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

To explain in detail with reference to FIG. 2, the SMF in the 5GC can communicate with the AMF via the N11 interface by using the network connection _520, and the N4 interface (between the SMF and UPF). It can communicate with the UPF via the interface), with the PCF via the N7 interface, and with the UDM via the N10 interface (the interface between the SMF and UDM).

Storage unit_540 is a functional unit for storing programs, user data, control information, etc. required for each operation of SMF.

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

Further, the SMF may have a function of generating a first ATSSS rule and a first N4 rule from the first PCC rule received from the PCF and from the first PCC rule. In addition, the SMF may manage (that is, map) the first PCC rule, the first ATSSS rule, and the first N4 rule in association with each other. Further, the SMF may have a function of generating a second ATSSS rule and a second N4 rule from the second PCC rule received from the PCF and the second PCC rule. In addition, the SMF may manage (that is, map) the second PCC rule, the second ATSSS rule, and the second N4 rule in association with each other.

These functions may be controlled by the control unit_500. Further, the mapped information may be stored in the storage unit_540.

Further, the SMF may be an SMF that supports the ATSSS function and / or the eATSSS function.

[2.9. Device configuration of UPF_230]
Next, an example of the device configuration of the UPF used in each embodiment will be described with reference to FIG. The UPF consists of a control unit_500, a network connection unit_520, and a storage unit_540. The control unit_500, network connection unit_520, and storage unit_540 are connected via a bus. The UPF may be a node that handles the user plane.

Control unit_500 is a functional unit that controls the operation and functions of the entire UPF. The control unit_500 may process all the functions that the other functional units (network connection unit_520, storage unit_540) in the UPF do not have. The control unit_500 realizes various processes in the UPF by reading and executing various programs stored in the storage unit_540 as needed.

The network connection unit_520 is a functional unit for the UPF to connect to the base station equipment and / or SMF and / or other UPFs and / or DNs in 5GAN. That is, the UPF uses the network connection _520 to communicate with the base station equipment in 5GAN and / or SMF and / or other UPFs and / or DNs for user data and / or control information. Can be sent and received.

Explained in detail with reference to FIG. 2, the UPF in the 5GC can communicate with the base station equipment via the N3 interface by using the network connection _520, via the N4 interface. It can communicate with SMF, can communicate with other UPFs via N9 interface (interface between UPFs), and can communicate with DN via N6 interface.

Storage unit_540 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF. Further, it is desirable that the control information received from the SMF is stored in the storage unit_540. For example, the storage unit_540 may store the N4 rule and / or the first N4 rule and / or the second N4 rule.

The UPF functions as an anchor point (also called an endpoint) for intra-RAT mobility or inter-RAT mobility, and as an external PDU session point for interconnecting to the DN (that is, between the DN and the core network). As a gateway for user data), packet routing and forwarding function, ULCL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, multi-homed Routing point function to support PDU session, QoS (Quality of Service) processing function for userplane, uplink traffic verification function, downlink packet buffering, downlink data notification (Downlink Data Notification) trigger function, etc. Have. The UPF also has the ability to determine for which access downlink traffic should be routed based on the N4 rule and / or the first N4 rule and / or the second N4 rule received from the SMF. May have. All of these functions may be controlled by the control unit_500.

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

The user plane (also referred to as U-Plane or UP) may be user data transmitted / received between the UE and the network. The user plane may be sent and received using a PDU session. Further, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface.

Furthermore, the control plane (also called C-Plane, CP) is a control message sent and received to control the communication of the UE. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and AMF. Further, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and NG RAN and the N2 interface.

Further, the user plane may be a communication path for transmitting and receiving user data, and may be composed of a plurality of bearers. Further, the communication path for transmitting and receiving user data may be referred to as user plane resources. Further, the control plane may be a communication path for transmitting and receiving control messages, and may be composed of a plurality of bearers.

Also, the UPF may be a UPF that supports the ATSSS function and / or the eATSSS function.

[2.10. Device configuration of PCF_250]
Next, an example of the device configuration of the PCF used in each embodiment will be described with reference to FIG. The PCF is composed of a control unit_500, a network connection unit_520, and a storage unit_540. The control unit_500, network connection unit_520, and storage unit_540 are connected via a bus.

Control unit_500 is a functional unit that controls the operation and functions of the entire PCF. The control unit_500 may process all the functions that the other functional units (network connection unit_520, storage unit_540) in the PCF do not have. The control unit_500 realizes various processes in the PCF by reading and executing various programs stored in the storage unit_540 as needed.

Network connection part_520 is a functional part for PCF to connect with AMF and / or SMF and / or AF (Application Function). That is, the PCF can send and receive control information between the AMF and / or the SMF and / or the AF by using the network connection part_520.

The PCF can communicate with the AMF via the N15 interface and with the SMF via the N7 interface by using the network connection _520, and the N5 interface (the interface between the PCF and AF). ) Can be communicated with AF.

Storage unit_540 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF.

In addition, PCF has a function to support a unified policy framework, a function to provide policy rules to a control function (control plane function) to enforce them, a function to access registration information, etc. have. The PCF also has a function of generating a PCC rule and / or a first PCC rule and / or a second PCC rule, a URSP (UE Route Selection Policy) rule, and the like. All of these functions may be controlled by the control unit_500.

Also, the PCF may be a PCF that supports the ATSSS function and / or the eATSSS function.

[3. Explanation of highly specialized terms and identification information used in each embodiment]
Next, highly specialized terms and identification information used in each embodiment will be described in advance.

[3.1. Explanation of highly specialized terms used in each embodiment]
First, highly specialized terms used in each embodiment will be described.

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

In addition, SM (session management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and are sent and received between UE and SMF via AMF. It may be a control message to be executed. 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 response message, and the like. You may. The procedure for SM may also include a PDU session establishment procedure.

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

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

Further, DNN (Data Network Name) may be identification information that identifies the core network and / or the external network such as DN. Furthermore, DNN can also be used as information for selecting a gateway such as UPF that connects the core network. The DNN may correspond to the APN (Access Point Name) in EPS.

A PDU session can be defined as a relationship between a DN that provides a PDU connectivity service and a UE. Specifically, a PDU session is between a UE and an external gateway or DN. It may be the connectivity established in. By establishing a PDU session via the access network and the core network in 5GS, the UE can send and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. The UE can use the PDU session to send and receive user data to and from devices such as application servers located in the DN. The PDU connectivity service is a service that provides PDU exchange between the UE and the DN. In addition, this PDU session may be composed of user plane resources in one access network (3GPP access network or non-3GPP access network). Further, unlike the MA PDU session, the PDU session may be a PDU session that is not simultaneously configured by user plane resources via 3GPP access and user plane resources via non-3GPP access. Further, such a PDU session may be referred to as an SA (Single Access) PDU session.

Further, the SA PDU session may mean an SA PDU session via 3GPP access and an SA PDU session via non-3GPP access used for communication by the eATSSS function.

The eATSSS function uses at least two SA PDU sessions consisting of one or more SA PDU sessions via 3GPP access and one or more SA PDU sessions via non-3GPP access. It may be a function that enables communication between the UE and the DN. That is, the UE can use the eATSSS function to send and receive user data to and from devices / functions such as DNs and / or application servers located in DNs using two or more SA PDU sessions.

In addition, the fact that the UE communicates by the eATSSS function means that the UE consists of at least one SA PDU session via 3GPP access and one or more SA PDU sessions via non-3GPP access. It means communicating with DN using the above SA PDU session. Also, the fact that the UE communicates by the eATSSS function may mean that the UE communicates with the DN using only two or more SA PDU sessions via 3GPP access, or via non-3GPP access. It may mean communicating with the DN using only two or more SA PDU sessions.

Further, the MA PDU session may be a PDU session that provides a PDU connectivity service capable of using one 3GPP access network and one non-3GPP access network at the same time. The MA PDU session may also be a PDU session that provides PDU connectivity services that can use one 3GPP access network or one non-3GPP access network at any given time. In other words, a MAPDU session may consist of userplane resources via 3GPP access and / or userplane resources via non-3GPP access. In addition, the fact that the UE communicates by the ATSSS function may mean that the UE communicates with the DN using the MAPDU session.

In addition, the ATSSS function enables communication between the UE and DN using one MAPDU session consisting of userplane resources via 3GPP access and / or userplaneresources via non-3GPP access. It may be a function to make. That is, the UE can send and receive user data to and from a device / function such as an application server located in a DN and / or a DN by using one MAPDU session by the ATSSS function.

Also, the fact that the UE communicates by the ATSSS function may mean that the UE communicates with the DN using one MAPDU session, or the UE uses only userplane resources via 3GPP access. It may mean communicating with the DN, or it may mean that the UE communicates with the DN using only userplane resources via non-3GPP access, or userplane resources via 3GPP access. And may mean communicating with the DN using userplane resources via non-3GPP access.

Note that each device (UE and / or access network device and / or core network device) has one or more identification information, DNN, TFT, PDU session type, and application identification for the SA PDU session or MA PDU session. Information, NSI identification information, access network identification information, SSC mode, and other information may be managed in association with each other.

In the following, the MA PDU session and the SA PDU session may be collectively referred to as a PDU session.

The PDU (Protocol Data Unit or Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet (registered trademark), and Unstructured. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When Ethernet (registered trademark) is specified, it indicates that Ethernet (registered trademark) frames are transmitted and received. In addition, Ethernet (registered trademark) may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is sent and received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology. As the P2P tunneling technique, for example, a UDP / IP encapsulation technique may be used. The PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6. IP may also be expressed as IPv4 v6.

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

A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be arranged. Here, NF is a processing function in a network and is adopted or defined in 3GPP. NSI is an entity of NS that consists of one or more in the core network. Further, NSI may be composed of a virtual NF (Network Function) generated by using NST (Network Slice Template). Here, NST is a logical representation of one or more NFs associated with a resource request to provide the required communication service or capability. That is, the NSI may be an aggregate in a core network composed of a plurality of NFs. In addition, NSI may be a logical network configured to separate user data delivered by services and the like. One or more NFs may be configured in NS. The NF configured in NS may or may not be a device shared with other NS. UE and / or devices in the network are 1 or more based on NSSAI and / or S-NSSAI and / or UE usage type and / or registration information such as 1 or more NSI IDs and / or APN. Can be assigned to NS. The UE usage type is a parameter value included in the UE registration information used to identify the NSI. The UE usage type may be stored in the HSS. AMF may select SMF and UPF based on UE usage type.

In addition, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying NS. S-NSSAI may be composed of only SST (Slice / Service type), or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating the operation of NS expected in terms of functions and services. Further, SD may be information for interpolating SST when selecting one NSI from a plurality of NSIs represented by SST. The S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs. In addition, the network may store one or more S-NSSAI in the UE registration information as the default S-NSSAI. If the S-NSSAI is the default S-NSSAI and the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide the NS related to the UE.

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

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

In addition, SSC mode 1 is a mode in which the network maintains the connectivity service provided to the UE. When the PDU session type associated with the PDU session is IPv4 or IPv6, the IP address may be maintained when the session service is continued.

Furthermore, SSC mode 1 may be a session service continuation mode in which the same UPF is maintained regardless of the access technology used when the UE connects to the network. More specifically, SSC mode 1 is a mode that realizes session service continuation even when UE mobility occurs, without changing the UPF used as the PDU session anchor of the established PDU session. Good.

In addition, SSC mode 2 is a mode in which the network releases the connectivity service provided to the UE and the corresponding PDU session. In SSC mode 2, if the PDU session type associated with the PDU session is IPv4, IPv6 or IPv4v6, even if the IP address assigned to the UE is released when changing the anchor of the PDU session. Good.

Furthermore, SSC mode 2 may be a session service continuation mode in which the same UPF is maintained only within the serving area of the UPF. More specifically, SSC mode 2 may be a mode that realizes session service continuation without changing the UPF used by the established PDU session as long as the UE is within the serving area of the UPF. Furthermore, SSC mode 2 is a mode that realizes session service continuation by changing the UPF used by the established PDU session when UE mobility occurs, such as leaving the serving area of the UPF. Good.

Here, the serving area of the UPF may be an area where one UPF can provide the session service continuation function, or a subset of the access network such as RAT and cell used when the UE connects to the network. It may be. Further, the subset of access networks may be a network composed of one or more RATs and / or cells.

Note that the change of the anchor point of the PDU session of SSC mode 2 (hereinafter, also referred to as PDU session anchor and PSA) may be realized by each device executing the procedure of changing the PSA of SSC mode 2. The anchor or the anchor point may be expressed as an end point.

In addition, SSC mode 3 is a mode in which changes in the user plane are revealed to the UE while the network guarantees that connectivity will not be lost. In the case of SSC mode 3, a PDU session passing through the new PDU session anchor point may be established before the established PDU session is disconnected in order to realize better connectivity service. In addition, in SSC mode 3, if the PDU session type associated with the PDU session is IPv4, IPv6 or IPv4v6, the IP address assigned to the UE will not be maintained when changing the anchor of the PDU session. May be good.

In addition, SSC mode 3 is a new PDU session established between the UE and the UPF, and / or a new PDU session via the new UPF for the same DN before disconnecting the communication path, and / Alternatively, the mode may be a session service continuation mode that allows the establishment of a communication path. Further, SSC mode 3 may be a mode of session service continuation that allows the UE to be multihoming. Further, SSC mode 3 may be a mode in which session service continuation using a plurality of PDU sessions and / or UPFs associated with PDU sessions is permitted. In other words, in the case of SSC mode 3, each device may realize session service continuation using a plurality of PDU sessions, or may realize session service continuation using a plurality of UPFs.

Here, if each device establishes a new PDU session and / or communication path, the selection of the new UPF may be carried out by the network, and the new UPF is where the UE connects to the network. It may be the most suitable UPF. In addition, if the UPF used by multiple PDU sessions and / or PDU sessions is enabled, the UE immediately implements the mapping of the application and / or flow communication to the newly established PDU session. It may be carried out based on the completion of communication.

Note that the change of the anchor point of the PDU session of SSC mode 3 may be realized by each device executing the procedure of changing the PSA of SSC mode 3.

Also, the default SSC mode is the SSC mode used by the UE and / or the network when a specific SSC mode is not determined. Specifically, the default SSC mode is the SSC mode used by the UE when there is no SSC mode request from the application and / or when there is no UE policy to determine the SSC mode for the application. May be good. Further, the default SSC mode may be the SSC mode used by the network when there is no request for the SSC mode from the UE.

The default SSC mode may be set for each DN, may be set for each PDN, or may be set for each PDN, based on the subscriber information and / or the operator policy and / or the UE policy. , And / or may be set for each subscriber. Further, the default SSC mode may be information indicating SSC mode 1, SSC mode 2 or SSC mode 3.

Also, IP address preservation is a technology that allows you to continue to use the same IP address. If IP address maintenance is supported, the UE can continue to use the same IP address for user data communication even when moving out of the TA. In other words, if IP address maintenance is supported, each device may be able to continue to use the same IP address for user data communication as the anchor point of the PDU session changes. ..

In addition, the steering function is such that the UE that supports the ATSSS function and / or the eATSSS function and the network that supports the ATSSS function and / or the eATSSS function steer the traffic via 3GPP access and / or non-3GPP access. It may be a function to steer, switch, or split. Specifically, the steering function may include an MPTCP (Multi-Path Transmission Control Protocol) function, an ATSSS (Access Traffic Steering, Switching, Splitting) -LL (Low-Layer) function, and an eATSSS function.

Here, the MPTCP function is a steering function of the layer above the IP layer and is applied to TCP traffic. Traffic to which the MPTCP function is applied may be referred to as an MPTCP flow. In addition, the MPTCP function of the UE can communicate with the MPTCP proxy function of the UPF using the userplane of 3GPP access and / or non-3GPP access. Also, if the UE requests a PDU session and provides MPTCP capability, the MPTCP function may be enabled, and if the UPF agrees to enable the MPTCP function, the UPF will enable the MPTCP Proxy function. You can. The network also assigns one IP address / prefix and two IP addresses / prefixes (also called link-specific multipath addresses) for PDU sessions. One of the link-specific multipath addresses is used to establish a subflow via 3GPP access and the other is used to establish a subflow via non-3GPP access. Also, the link-specific multicast address is used only for the MPTCP function of the UE. Cannot route via N6. In addition, the network can send MPTCP proxy information (which may include the IP address, port number, and type of MPTCP proxy) to the UE. Here, the type may be Type 1 (transport converter). In addition, the network may provide the UE with a list of apps to which the MPTCP function should be applied.

In addition, the ATSSS-LL function is a steering function in the layer below the IP layer, and is applied to all types of traffic (TCP traffic, UDP (User Data Protocol) traffic, ethernet traffic, etc.). Traffic to which the ATSSS-LL function is applied may be referred to as Non-MPTCP flow. The UPF may also support steering functions that are the same as or similar to the ATSSS-LL function. In addition, the ATSSS-LL function of the UE determines the steering, switch, and split of upstream traffic based on the ATSSS rules and local conditions. Also, when the UE requests an SA PDU session and provides ATSSS-LL capability, the ATSSS-LL function may be enabled, and when the UE provides ATSSS-LL capability, the ATSSS-LL function in UPF is enabled. May become.

In addition, the eATSSS function may be a new steering function different from the MPTCP function and the ATSSS-LL function. Further, the eATSSS function may be the same function as the MPTCP function or the ATSSS-LL function. Further, the eATSSS function may be a function including the MPTCP function and the ATSSS-LL function. That is, the MPTCP function and the ATSSS-LL function may be a part of the steering function that realizes the ATSSS function, or may be a part of the steering function that realizes the eATSSS function.

Further, the ATSSS rules may be a list of one or more ATSSS rules. ATSSS rules may consist of a rule precedence and / or a traffic descriptor and / or an access selection descriptor.

Here, the rule priority in the ATSSS rule defines the order of the ATSSS rules evaluated in the UE. When the UE receives ATSSS rules, that is, when it receives one or more ATSSS rules, it may refer to the rule priority in each ATSSS rule and evaluate in order from the ATSS rule with the highest priority.

Also, the traffic descriptor in the ATSSS rule indicates when to apply the ATSSS rule. Here, the traffic descriptor in the ATSSS rule may be composed of an application descriptor and / or an IP descriptor and / or a non-IP descriptor.

Here, the application descriptor in the traffic descriptor in the ATSSS rule may indicate information that identifies the application that generates the traffic.

Further, the IP descriptor in the traffic descriptor in the ATSSS rule may indicate information for identifying the destination of the IP traffic.

Further, the non-IP descriptor in the traffic descriptor in the ATSSS rule may indicate information for identifying the destination of non-IP traffic (for example, ethernet traffic or unstructured traffic).

Further, the access selection descriptor in the ATSSS rule may be composed of the steering mode and / or the steering function.

Here, the steering mode may be information indicating whether the traffic of the service data flow (also referred to as SDF) should be distributed to 3GPP access or non-3GPP access. In addition, the steering mode may include four modes: Active-Standby, Smallest Delay, Load-Balancing, and Priority-based.

In addition, Active-Standby sets active access and standby access, and when active access is available, steers the service data flow (SDF) for that access, and that active access is used. When it becomes impossible, it may be a mode to switch SDF to standby access. In addition, Active-Standby sets only active access, and if standby access is not set, it steers the service data flow (SDF) for that access when active access is available. The mode may be such that the SDF cannot be switched to standby access even if active access becomes unavailable.

In addition, Smallest Delay may be a mode in which the service data flow (SDF) is steered for an access having the minimum RTT (Round-Trip Time). Also, when this mode is set, the UE and UPF may make measurements to determine the RTT when communicating via 3GPP access and the RTT when communicating via non-3GPP access.

Also, Load-Balancing may be a mode that separates the service data flow (SDF) for both accesses. If Load-Balancing is specified, it may also include information indicating the percentage of service data flow (SDF) that should be sent via 3GPP access and non-3GPP access.

Priority-based is also used to steer all traffic in the service data flow (SDF) for high priority access until it is determined to be congested. Mode may be used. Also, if it is determined that the access is congested, the SDF traffic will be sent not only to the high priority access but also to the low priority access. Mode may be. Further, when high priority access becomes unavailable, all the traffic of SDF may be sent to low priority access.

In addition, the steering function in the access selection descriptor in the ATSSS rule is the steering function supported by the UE, the MPTCP function, the ATSSS-LL function, or the eATSSS function in order to steer the traffic of the service data flow (also referred to as SDF). May indicate which of the above should be used.

Also, the N4 rule may have the same configuration as the ATSSS rule.

Further, URSP rules ((UERouteSelectionPolicy) rules) may be composed of one or more URSP rules (UERouteSelectionPolicyRule) paste. Further, each URSP rule may be composed of a rule priority (Rule Precedence) and / or a traffic descriptor (Traffic descriptor) and / or a route selection descriptor list (List of Route Selection Descriptors).

Here, the rule priority in the URSP rule indicates the order of the URSP rules enforced in the UE. When the UE receives URSP rules, that is, when it receives one or more URSP rules, it may refer to the rule priority in each URSP rule and apply it in order from the URSP rule with the highest priority.

Also, the traffic descriptor in the URSP rule indicates when to apply the URSP rule. Here, the traffic descriptors in the URSP rule are the application descriptors and / or the IP descriptors, and / or the domain descriptors, and / or the non-IP descriptors ( It may consist of Non-IP descriptors) and / or DNN (Data Network Name) and / or Connection Capabilities.

Further, the application descriptor in the traffic descriptor in the URSP rule may include the OS ID and the OS application ID.

Further, the IP descriptor in the traffic descriptor in the URSP rule indicates information for identifying the destination of the IP traffic, and may include, for example, an IP address, an IPv6 network prefix, a port number, a protocol number, and the like.

Further, the domain descriptor (Domain descriptors) in the traffic descriptor in the URSP rule may indicate the FQDN (Fully Qualified Domain Name) of the destination.

Further, the non-IP descriptor in the traffic descriptor in the URSP rule may indicate information for identifying the destination of non-IP traffic (for example, ethernet traffic or unstructured traffic).

Also, the DNN in the traffic descriptor in the URSP rule may be information about the DNN provided by the application.

Also, the connection capability in the traffic descriptor in the URSP rule may indicate the information provided by the UE application when the UE requests a connection to the network using some capability.

Further, the route selection descriptor list in the URSP rule may be composed of one or more route selection descriptors (Route Selection Descriptor). Each route selection descriptor may be composed of a rule selection descriptor priority (Route Selection Descriptor Precedence) and / or a route selection configuration (Route selection components).

The rule selection descriptor priority indicates the order in which the route selection descriptor is applied. When the UE receives the route selection descriptor list, that is, when it receives one or more route selection descriptors, it refers to the rule selection descriptor priority in each route selection descriptor and describes the route selection with high priority. It may be applied in order from the child.

The route selection configuration includes SSC mode selection (SSC Mode Selection) and / or network slice selection (Network Slice Selection) and / or DNN selection (DNN Selection) and / or PDU session type selection (PDU Session Type Selection). ), And / or a non-seamless Offload indication, and / or an Access Type preference.

Here, the SSC mode selection may indicate that the application traffic is routed through the specified SSC mode PDU session.

Also, network slice selection may indicate routing application traffic using the indicated PDU sessions that support one or more S-NSSAI.

DNN selection may also indicate routing application traffic using a PDU session that supports one or more of the indicated DNNs.

Also, PDU session type selection may indicate that application traffic is routed using a PDU session that supports the indicated PDU session type.

Also, the non-seamless offload instruction may indicate that the application traffic is offloaded for non-3GPP access.

Also, the access type preference may indicate the access type that establishes the PDU session when the UE needs to establish the PDU session. Here, the access type may indicate 3GPP, non-3GPP, or Multi-Access, or eATSSS. Here, eATSSS may be specified when establishing a PDU session using the eATSSS function, and 3GPP access or non-3GPP access corresponding to the established SA PDU session may be indicated.

In addition, the first PCC rule is a rule that shows how to distribute uplink traffic and downlink traffic in two SA PDU sessions used for communication by the eATSSS function to 3GPP access and non-3GPP access. May be. In other words, the first PCC rule is for the first SA PDU session via 3GPP access and non-3GPP access for uplink and downlink traffic in the two SA PDU sessions used for communication by the eATSSS function. It may be a rule that shows how to distribute with the second SA PDU session via. In addition, the first PCC rule is how to distribute the uplink traffic and downlink traffic in the two SA PDU sessions used for communication by the eATSSS function to the first SA PDU session via 3GPP access. It may be a rule that only indicates whether to do it. In addition, the first PCC rule is how the uplink traffic and downlink traffic in the two SA PDU sessions used for communication by the eATSSS function are for the second SA PDU session via non-3GPP access. It may be a rule that only indicates whether to distribute to. This rule may be included in the first PCC rule as eATSSS policy control information.

The second PCC rule is a rule that shows how to distribute uplink traffic and downlink traffic in the MA PDU session used for communication by the ATSSS function to 3GPP access and non-3GPP access. You can. In other words, the second PCC rule is userplane resources via 3GPP access and userplane via non-3GPP access for uplink and downlink traffic in the MAPDU session used for communication by the ATSSS function. It may be a rule that indicates how to distribute with resources. The second PCC rule is how to distribute the uplink traffic and downlink traffic in the MAPDU session used for communication by the ATSSS function to the userplane resources via 3GPP access in the MAPDU session. It may be a rule in which only the user is shown. The second PCC rule is how to deal with uplink traffic and downlink traffic in the MAPDU session used for communication by the ATSSS function for userplane resources via non-3GPP access in the MAPDU session. It may be a rule that only indicates whether to distribute. This rule may be included in the first PCC rule as ATSSS policy control information.

In addition, the first ATSSS rule may be a rule that indicates how to distribute uplink traffic in two SA PDU sessions used for communication by the eATSSS function to 3GPP access and non-3GPP access. .. In other words, the first ATSSS rule is for uplink traffic in the two SA PDU sessions used for communication by the eATSSS function, the first SA PDU session via 3GPP access and the first via non-3GPP access. It may be a rule that shows how to distribute in 2 SA PDU sessions. Also, the first ATSSS rule is only how to distribute the uplink traffic in the two SA PDU sessions used for communication by the eATSSS function to the first SA PDU session via 3GPP access. It may be the rule shown. In addition, the first ATSSS rule is how to distribute the uplink traffic in the two SA PDU sessions used for communication by the eATSSS function to the second SA PDU session via non-3GPP access. It may be a rule that only shows. Further, the first ATSSS rule may include a steering function indicating either the steering function supported by the UE, the MPTCP function, the ATSSS-LL function, or the eATSSS function as described above. Also, the first ATSSS rule is sent from the SMF to the UE and used in the UE.

The second ATSSS rule may be a rule that indicates how to distribute the uplink traffic in the MA PDU session used for communication by the ATSSS function to 3GPP access and non-3GPP access. In other words, the second ATSSS rule is that for uplink traffic in the MAPDU session used for communication by the ATSSS function, userplane resources via 3GPP access and userplane resources via non-3GPP access. It may be a rule that indicates how to distribute. In addition, the second ATSSS rule only shows how the uplink traffic in the MAPDU session used for communication by the ATSSS function is distributed to the userplane resources via 3GPP access in the MAPDU session. It may be a rule that is used. In addition, the second ATSSS rule is only how to distribute the uplink traffic in the MA PDU session used for communication by the ATSSS function to the user plane resources via non-3GPP access in the MA PDU session. May be the rule shown. In addition, the second ATSSS rule may include a steering function indicating either the steering function supported by the UE, the MPTCP function, the ATSSS-LL function, or the eATSSS function as described above. Also, the second ATSSS rule is sent from the SMF to the UE and used in the UE.

The first N4 rule may also be a rule that indicates how to distribute downlink traffic in two SA PDU sessions used for communication by the eATSSS function to 3GPP access and non-3GPP access. .. In other words, the first N4 rule is for downlink traffic in the two SA PDU sessions used for communication by the eATSSS function, the first SA PDU session via 3GPP access and the first via non-3GPP access. It may be a rule that shows how to distribute in 2 SA PDU sessions. Also, the first N4 rule is only how to distribute the downlink traffic in the two SA PDU sessions used for communication by the eATSSS function to the first SA PDU session via 3GPP access. It may be the rule shown. Also, the first N4 rule is how to distribute the downlink traffic in the two SA PDU sessions used for communication by the eATSSS function to the second SA PDU session via non-3GPP access. It may be a rule that only shows. Also, the first N4 rule is sent from the SMF to the UPF and used in the UPF.

The second N4 rule may be a rule that indicates how to distribute the downlink traffic in the MA PDU session used for communication by the ATSSS function to 3GPP access and non-3GPP access. In other words, the second N4 rule is that for downlink traffic in the MAPDU session used for communication by the ATSSS function, userplane resources via 3GPP access and userplane resources via non-3GPP access. It may be a rule that indicates how to distribute. Also, the second N4 rule only shows how the downlink traffic in the MAPDU session used for communication by the ATSSS function is distributed to the userplane resources via 3GPP access in the MAPDU session. It may be a rule that is used. In addition, the second N4 rule is only how to distribute the downlink traffic in the MA PDU session used for communication by the ATSSS function to the user plane resources via non-3GPP access in the MA PDU session. May be the rule shown. Also, the second N4 rule is sent from the SMF to the UPF and used in the UPF.

[3.2. Description of identification information used in each embodiment]
Next, the identification information used in each embodiment will be described.

First, the first identification information is DNN. Further, the first identification information may be information indicating the DNN required by the UE. The first identification information may be a DNN that identifies the DN to which the PDU session requesting establishment is connected.

Further, the second identification information may indicate whether or not the UE supports the ATSSS-LL function. Further, the second identification information may be information indicating UE capability. Further, the second identification information may be expressed as information indicating ATSSS-LL capability.

Further, the third identification information may indicate whether or not the UE supports the MPTCP function. Further, the third identification information may be information indicating UE capability. Further, the third identification information may be expressed as information indicating MPTCP capability. The second identification information and the third identification information may be expressed as information indicating ATSSS capability.

Further, the fourth identification information may indicate whether or not the UE supports the eATSSS function. Further, the fourth identification information may be information indicating UE capability. Further, the fourth identification information may be expressed as information indicating eATSSS capability. The information indicating the ATSSS capability may include a fourth identification information in addition to the second identification information and the third identification information.

The fifth identification information is the PDU session ID for identifying the PDU session. The fifth identification information may be the PDU session ID for identifying the MA PDU session when the UE requests the establishment of the MA PDU session, and the SA when the UE requests the establishment of the SA PDU session. It may be a PDU session ID for identifying the PDU session. That is, the fifth identification information may be information associated with the ninth identification information.

The sixth identification information is the PDU session type. Further, the sixth identification information may be information indicating the PDU session type requested by the UE. Further, the sixth identification information may be a PDU session type for identifying the type of PDU session. Further, the sixth identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).

The seventh identification information is the SSC mode. Further, the seventh identification information may be the SSC mode required by the UE for the PDU session. Further, the seventh identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.

Also, the eighth identification information is one or more S-NSSAI. Further, the eighth identification information may be one or more S-NSSAI required by the UE. Further, the eighth identification information may be one or more S-NSSAI required by the UE for the PDU session. In addition, the eighth identification information is permitted by the network for at least one access (3GPP access or non-3GPP access) as Allowed NSSAI included in the Registration Accept message in the Registration procedure. It can be at least one S-NSSAI.

Here, with S-NSSAI permitted for both accesses, connection to the network via 3GPP access is permitted, and connection to the network via non-3GPP access is permitted. May mean S-NSSAI.

In addition, the ninth identification information indicates that the establishment of the MA PDU session (for the ATSSS function) is requested, and / or the establishment of the SA PDU session (for the eATSSS function) is requested. It may be information. Further, the ninth identification information may be information indicating that communication by the ATSSS function is requested and / or information indicating that communication by the eATSSS function is requested. In addition, the ninth identification information is information indicating that the establishment of userplane resources is requested via the 3GPP access that constitutes the MAPDU session, or the userplane resources via the non-3GPP access that constitutes the MAPDU session. It may be information indicating that the establishment of is requested. Further, the ninth identification information may be a request type. That is, the request type (Request type), which is the ninth identification information, requests the establishment of the MA PDU session (for the ATSSS function) and / or the establishment of the SA PDU session (for the eATSSS function). Request and / or request communication by the ATSSS function, and / or request communication by the eATSSS function, and / or request the establishment of user plane resources via the 3GPP access that constitutes the MAPDU session. It may be indicated that and / or requesting the establishment of user plane resources via non-3GPP access that constitutes the MAPDU session. For example, when requesting the establishment of a MAPDU session (for the ATSSS function) and / or when requesting communication by the ATSSS function, and / or establishing userplane resources via the 3GPP access that constitutes the MAPDU session. And / or when requesting the establishment of userplane resources via non-3GPP access that constitutes an MAPDU session, the request type, which is the ninth identifying information, may indicate MAPDUrequest. .. Also, for example, when requesting the establishment of an SA PDU session (for the eATSSS function) and / or when requesting communication by the eATSSS function, the request type that is the ninth identification information is eATSSS or eATSSS request. , Or SA PDU request may be indicated.

The tenth identification information is the PDU session ID for identifying the already established SA PDU session. For example, the tenth identification information may be the PDU session ID for identifying the SA PDU session via 3GPP access when the SA PDU session via 3GPP access has already been established. Also, for example, the tenth identification information is the PDU session ID for identifying the SA PDU session via non-3GPP access when the SA PDU session via non-3GPP access has already been established. It may be there.

Further, the eleventh identification information may be information having one or more information indicated by the first to ten identification information. For example, in the eleventh identification information, the second to fourth identification information can be combined into one identification information. In this way, by using the eleventh identification information, the information may be provided as one piece of information summarizing the second identification information, the third identification information, and the fourth identification information.

The 21st identification information is DNN. Further, the 21st identification information may be information indicating the DNN permitted by the network. Further, the 21st identification information may be a DNN that identifies the DN to which the established PDU session is connected.

Further, the 22nd identification information may indicate whether or not the network supports the ATSSS-LL function. Further, the 22nd identification information may be information indicating network capability. Further, the 22nd identification information may be expressed as information indicating ATSSS-LL capability.

Further, the 23rd identification information may indicate whether or not the network supports the MPTCP function. Further, the 23rd identification information may be information indicating network capability. Further, the 23rd identification information may be expressed as information indicating MPTCP capability. The 22nd identification information and the 23rd identification information may be expressed as information indicating ATSSS capability.

Further, the 24th identification information may indicate whether or not the network supports the eATSSS function. Further, the 24th identification information may be information indicating network capability. Further, the 24th identification information may be expressed as information indicating eATSSS capability. The information indicating the ATSSS capability may include the 24th identification information in addition to the 22nd identification information and the 23rd identification information.

The 25th identification information is the PDU session ID for identifying the PDU session to be established. The 25th identification information may be the PDU session ID for identifying the MA PDU session when the establishment of the MA PDU session is permitted, and the SA when the establishment of the SA PDU session is permitted. It may be a PDU session ID for identifying the PDU session.

The 26th identification information is the PDU session type. Further, the 26th identification information may be information indicating the PDU session type permitted by the network. Further, the 26th identification information may be a PDU session type for identifying the type of PDU session. Further, the 26th identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).

Also, the 27th identification information is in SSC mode. Also, the 27th identification information may be in SSC mode allowed by the network for the PDU session to be established. Further, the 27th identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.

Also, the 28th identification information is 1 or more S-NSSAI. Further, the 28th identification information may be one or more S-NSSAIs permitted by the network. Also, the 28th identification information may be one or more S-NSSAIs allowed by the network for the PDU session to be established. Further, the 28th identification information may be one or more S-NSSAI selected from one or more S-NSSAI included in the eighth identification information. Further, the 28th identification information may be one or more S-NSSAI selected from one or more S-NSSAI not included in the eighth identification information.

Further, the 29th identification information may be information indicating that the information has been approved by the network. For example, the 29th identity indicates that the establishment of a MAPDU session (for the ATSSS function) was allowed and / or the establishment of userplane resources via 3GPP access in the MAPDU session was allowed. And / or it may indicate that the establishment of userplane resources via non-3GPP access in the MAPDU session is permitted, and / or that communication by the ATSSS function is permitted. Also, the 29th identity is that the establishment of SA PDU session (for eATSSS function) is permitted and / or the establishment of user plane resources via 3GPP access is permitted, and / or non. -3 It may indicate that the establishment of user plane resources via GPP access is permitted and / or communication by the eATSSS function is permitted.

The thirtieth identification information is the ATSSS rule, the first ATSSS rule, or the second ATSSS rule. The steering function included in the thirtieth identification information may be the steering function supported by the UE and / or the ATSSS-LL function and / or the MPTCP function and / or the eATSSS function.

Further, the 31st identification information may be information instructing to execute the registration procedure and / or the PDU session establishment procedure. In addition, the 31st identification information executes the registration procedure and / or the PDU session establishment procedure in order to establish the SA PDU session that has not been established yet among the two SA PDU sessions used for communication by the eATSSS function. It may be information instructing to do. In addition, the 31st identification information is used for the registration procedure and / or to establish the SA PDU session for user plane resources via access that has not yet been established among the MA PDU sessions used for communication by the ATSSS function. It may be information instructing the execution of the PDU session establishment procedure. The instruction to execute the registration procedure and / or the PDU session establishment procedure may be transmitted by transmitting at least a part of the identification information of Nos. 21 to 30 and 32.

Further, the 32nd identification information may be information having one or more information indicated by the 21st to 31st identification information. For example, as the 32nd identification information, the 22nd to 24th identification information can be combined into one identification information. In this way, by using the 32nd identification information, information may be provided as one piece of information summarizing the 22nd identification information, the 23rd identification information, and the 24th identification information.

[4. First Embodiment]
In this embodiment, when the UE is registered in the same PLMN (operator's core network) via 3GPP access and non-3GPP access, a MA PDU session and / or for communication using the ATSSS function. The procedure for establishing a PDU session for establishing an SA PDU session for communication using the eATSSS function will be described with reference to FIGS. 7 and 8.

Also, the UE may start the PDU session establishment procedure if it supports the ATSSS function and / or the eATSSS function. Further, when the UE supporting the ATSSS function requests communication by the ATSSS function, the PDU session establishment procedure may be started. Further, when the UE supporting the eATSSS function requests communication by the eATSSS function, the PDU session establishment procedure may be started. Further, when the UE supporting the ATSSS function and the eATSSS function requests the communication by the ATSSS function and / or the communication by the eATSSS function, the PDU session establishment procedure may be started. If the user has previously set the UE that supports the ATSSS function and / or the eATSSS function to communicate using the ATSSS function and / or the eATSSS function, the UE starts the PDU session establishment procedure. Good. In addition, the UE is information stored in advance in the UE and / or information received in advance from the access network and / or information received in advance from the core network (for example, information received in a procedure such as a registration procedure). , And / or including the URSP rules received in advance from the PCF), etc., the PDU session establishment procedure may be started.

[4.1. 3 PDU session establishment procedure via 3GPP access]
Next, the PDU session establishment procedure executed via 3GPP access will be described with reference to FIG. First, the UE initiates the PDU session establishment procedure by sending a NAS message containing the N1SM container containing the PDU session establishment request message to the AMF via the access network (S700). The NAS message is, for example, a message transmitted via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message.

Here, the access network is 3GPP access or non-3GPP access, but the case of 3GPP access will be described below as an example. That is, the UE sends a NAS message to the AMF via the base station device included in the 3GPP access.

In addition, the UE sends the PDU session establishment request message and / or the N1SM container and / or the NAS message by including at least one of the identification information 1 to 9 and 11 so that the UE can send the message. The request can be notified to the network side.

Here, the identification information of Chapters 1 to 9 and 11 may be as described in Chapter 3.2.

The UE preferably supports at least one of the functions indicated by the second to fourth identification information, and if the function is supported, the identification information supports the function. It is preferable to show.

In addition, regarding the identification information of the first to 9th and 11th, the UE has a layer lower than the NAS layer (for example, RRC (Radio Resource Control) layer, MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP. It may be included in a control message of (PacketDataConvergenceProtocol) layer, etc.) or a control message of a layer higher than the NAS layer (for example, transport layer, session layer, presentation layer, application layer, etc.).

Next, when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the contents of the information (message, container, information) contained in the NAS message.

Here, the AMF is a PDU if the UE is registered via both accesses, but the S-NSSAI (eighth identification information) received from the UE is not allowed for both accesses. The request to establish a session may be rejected. The AMF may also reject the request to establish a PDU session if the network and / or core network device does not support the ATSSS and / or eATSSS functions.

Here, the fact that the UE is registered via both accesses means that the UE is registered in the network via 3GPP access and the UE is registered in the network via non-3GPP access. May mean.

Also, if S-NSSAI is not allowed for both accesses, then the connection to the network via 3GPP access is not allowed and the connection to the network via non-3GPP access is allowed. It may mean S-NSSAI that has not been done.

Further, when rejecting the request for establishing a PDU session, each device may skip, that is, cancel the steps after S702.

Further, when rejecting the PDU session establishment request, the AMF may send a NAS message to the UE containing information indicating that the PDU session establishment request is rejected. At this time, the AMF does not need to send at least a part of the information (message, container, information) included in the NAS message received from the UE to the SMF. In addition, the UE may detect that this procedure has not been completed normally or that this procedure has been completed abnormally by receiving this NAS message from AMF.

Also, when rejecting the PDU session establishment request, the AMF sends information to the SMF indicating that the PDU session establishment request is rejected, and the SMF sends the N1 SM container containing the PDU session establishment refusal message. The including NAS message may be sent to the UE. At this time, the PDU session establishment refusal message and / or the N1SM container and / or the NAS message may contain information indicating that the PDU session establishment request is rejected. In addition, the UE received a PDU session establishment refusal message and / or N1SM container and / or NAS message from the SMF, and this procedure was not completed normally, or this procedure was completed abnormally. You may detect that you have done so.

Next, AMF selects SMF as the transfer destination of at least a part of the information (messages, containers, information) contained in the NAS message received from the UE (S702). In addition, AMF includes information (messages, containers, information) contained in NAS messages, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or. The transfer destination SMF may be selected based on the network status and / or the user's registration information and / or the context held by the AMF. The AMF may also select an SMF that supports the ATSSS function and / or the eATSSS function. Here, it is assumed that SMF_220 that supports the ATSSS function and / or the eATSSS function is selected.

Next, the AMF transmits at least a part of the information (message, container, information) contained in the NAS message received from the UE to the selected SMF, for example, via the N11 interface (S704). The AMF may also send information to the SMF indicating that the UE is registered for both accesses.

Next, when the SMF receives the information (message, container, information) transmitted from the AMF, the UE requests and / or the content of the information (message, container, information) received from the AMF. Can be recognized.

Here, the SMF may determine the first condition. Further, the first condition determination may be for determining whether or not to accept the UE request. Further, in the first condition determination, the SMF determines whether the first condition determination is true or false. Further, if the SMF determines that the first condition determination is true, the procedure (A) in FIG. 7 may be started, and if the first condition determination is determined to be false, the procedure for rejecting the UE request. May start. The procedure for rejecting a UE request is described in Chapter 4.4.

The first condition determination is information received from AMF (messages, containers, information) and / or subscriber information (subscription information), and / or network capability information, and / or UE policy, and /. Alternatively, it may be executed based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the SMF.

For example, if the network permits the UE request, the first condition determination may be determined to be true, and if the UE request is not permitted by the network, the first condition determination may be determined to be false. Also, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the first condition determination may be determined to be true, and the functions required by the UE are supported. If not, the first condition determination may be determined to be false. Further, when the transmitted / received identification information is permitted, the first condition determination may be determined to be true, and when the transmitted / received identification information is not permitted, the first condition determination may be determined to be false.

Also, if the network allows the establishment of SA PDU sessions for communication using the eATSSS function, and / or if it allows the establishment of userplane resources via 3GPP access, and / or communication using the eATSSS function. If permitted, the first condition determination may be determined to be true. Also, if the network does not allow the establishment of SAPDU sessions for communication using the eATSSS function, and / or if it does not allow the establishment of userplane resources via 3GPP access, and / or communication using the eATSSS function. If not permitted, the first condition determination may be determined to be false.

Also, if the network allows the establishment of MAPDU sessions and / or the establishment of userplane resources via 3GPP access in MAPDU sessions, and / or if communication by the ATSSS function is permitted. The first condition determination may be determined to be true. Also, if the network does not allow the establishment of MAPDU sessions and / or the establishment of userplane resources via 3GPP access in MAPDU sessions, and / or does not allow communication by the ATSSS function. The first condition determination may be determined to be false.

The condition for determining the authenticity of the first condition determination is not limited to the above-mentioned condition.

Next, each step of the procedure (A) in Fig. 7 will be explained.

First, SMF may select PCF. For example, the SMF may select an appropriate PCF based on the received identification information. For example, the SMF may select a PCF that supports the ATSSS function and / or the eATSSS function. Here, it is assumed that PCF_250 that supports the ATSSS function and / or the eATSSS function is selected.

Next, the SMF may send at least part of the information (messages, containers, information) received from the AMF to the PCF (S706).

In addition, if the SMF decides to allow the establishment of an SA PDU session for communication using the eATSSS function, and / or if it decides to allow the establishment of user plane resources via 3GPP access, and / Alternatively, the SMF may send additional information to the PCF if it decides to allow communication by the eATSSS function. Here, as additional information, "information indicating that the establishment of the SA PDU session for communication using the eATSSS function is permitted" and / or "the establishment of user plane resources via 3GPP access is permitted". Information indicating that, and / or "permitting communication by the eATSSS function", and / or "access type corresponding to the established SA PDU session and / or user plane resources" may be included. Here, the access type may indicate 3GPP access.

In addition, when the SMF decides to allow the establishment of the MAPDU session and / or when it decides to allow the establishment of userplane resources via 3GPP access in the MAPDU session, and / or communication by the ATSSS function. The SMF may send additional information to the PCF if it decides to allow. Here, as additional information, "information indicating that the establishment of the MA PDU session is permitted" and / or "information indicating that the establishment of user plane resources via 3GPP access in the MA PDU session is permitted". , And / or "permitting communication by the eATSSS function" and / or "access type corresponding to userplane resources in the established MAPDU session" may be included. Here, the access type may indicate 3GPP access.

Although the above judgment is described as being made by SMF, it may be made by PCF. That is, the SMF and / or the PCF may make the above judgment. If the SMF does not make the above decision, the SMF may not send the above additional information to the PCF.

Next, when the PCF receives the information (message, container, information) sent from the SMF, it can recognize the contents.

The PCF is based on the information received from the SMF (messages, containers, information) and / or the UE policy, and / or the operator policy, and / or the subscriber information (subscription information), etc., as described above in the SMF. A judgment similar to the judgment may be made.

If the PCF makes the above judgment, the PCF may transmit to the SMF the above additional information described as being transmitted from the SMF to the PCF.

Further, when the PCF detects that the above judgment is made in the SMF, it is not necessary to make this judgment (may be skipped).

Also, if the SMF and / or PCF allows the establishment of SA PDU sessions for communication using the eATSSS function, and / or if the establishment of user plane resources via 3GPP access is permitted, and / Alternatively, if communication by the eATSSS function is permitted, the PCF may generate a first PCC rule.

Also, if the SMF and / or PCF allows the establishment of a MAPDU session, and / or if the establishment of userplane resources via 3GPP access in the MAPDU session is permitted, and / or communication by the ATSSS function. If allowed, the PCF may generate a second PCC rule.

Then, when the PCF generates the first PCC rule or the second PCC rule, the generated PCC rule may be transmitted to the SMF.

Note that the PCF may generate the first PCC rule and the second PCC rule as one common PCC rule. That is, the PCC rule may include a first PCC rule and / or a second PCC rule. The PCF may then send the generated PCC rules to the SMF.

Next, when the SMF receives the information transmitted from the PCF, it can recognize the contents of the information.

Then, when the SMF receives the first PCC rule from the PCF, the SMF may generate the first ATSSS rule (30th identification information) and the first N4 rule from the first PCC rule. In addition, the SMF may manage (that is, map) the first PCC rule, the first ATSSS rule, and the first N4 rule in association with each other.

Further, when the SMF receives the second PCC rule from the PCF, the SMF may generate the second ATSSS rule (30th identification information) and the second N4 rule from the second PCC rule. In addition, the SMF may manage (that is, map) the second PCC rule, the second ATSSS rule, and the second N4 rule in association with each other.

When the SMF receives the PCC rule instead of the first PCC rule or the second PCC rule from the PCF, the SMF generates the ATSSS rule (30th identification information) and the N4 rule from the PCC rule. Good. In this case, the ATSSS rule may include a first ATSSS rule and / or a second ATSSS rule, and an N4 rule may include a first N4 rule and / or a second N4 rule. You can. In addition, the SMF may manage (that is, map) the PCC rule, the ATSSS rule, and the N4 rule in association with each other.

Next, the SMF selects the UPF for the PDU session to be established, and sends an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S708).

Further, when the SMF receives the first PCC rule from the PCF, the SMF may include the first N4 rule in the N4 session establishment request message. Further, when the SMF receives the second PCC rule from the PCF, the SMF may include the second N4 rule in the N4 session establishment request message. Further, when the SMF receives the PCC rule from the PCF, the SMF may include the N4 rule in the N4 session establishment request message.

Here, SMF refers to information received from AMF (messages, containers, information) and / or information received from PCF and / or subscriber information, and / or network capability information, and / or UE policy. One or more UPFs may be selected based on and / or operator policy and / or network status and / or user registration information and / or context held by the SMF. Also, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF.

Also, if the SMF and / or PCF allows the establishment of SA PDU sessions for communication using the eATSSS function, and / or if the establishment of user plane resources via 3GPP access is permitted, and / Alternatively, if communication by the eATSSS function is permitted, the SMF may select a UPF that supports the eATSSS function.

Also, if the SMF and / or PCF allows the establishment of a MAPDU session, and / or if the establishment of userplane resources via 3GPP access in the MAPDU session is permitted, and / or communication by the ATSSS function. If allowed, the SMF may choose a UPF that supports the ATSSS feature.

Here, it is assumed that UPF_230 that supports the ATSSS function and / or the eATSSS function is selected.

Next, when the UPF receives the N4 session establishment request message (S708), the UPF can recognize the content of the information received from the SMF.

Further, when the UPF receives the first N4 rule or the second N4 rule or the N4 rule from the SMF, the UPF may be set to operate according to the received N4 rule.

That is, when the UPF receives the first N4 rule, the 3GPP access that is going to be established by this procedure (PDU session establishment procedure) for the downlink traffic in the two SA PDU sessions used for communication by the eATSSS function is performed. The first SA PDU session via the first SA PDU session may be set to operate according to the first N4 rule. The UPF operates according to the first N4 rule for the second SA PDU session via non-3GPP access that is scheduled to be established in the second PDU session establishment procedure executed after this procedure. It is preferable that the setting is not performed at this timing, but it may be performed.

In addition, even if the UPF receives the first N4 rule in this procedure (PDU session establishment procedure), it operates according to the first N4 rule for the first SA PDU session via 3GPP access. It is not necessary to make the setting to make it. In this case, the UPF will send an N4 session establishment request message after the second PDU session establishment procedure performed after this procedure allows the establishment of a second SA PDU session via non-3GPP access. Based on the reception, the first SA PDU session via 3GPP access and the second SA PDU session via non-3GPP access may be set to operate according to the first N4 rule.

Also, when the UPF receives the N4 rule including the first N4 rule, the same setting may be made.

In addition, when the UPF receives the second N4 rule, it will use userplane resources via 3GPP access and user via non-3GPP access for downlink traffic in the MAPDU session used for communication by the ATSSS function. You may set plane resources to operate according to the second N4 rule.

Also, when the UPF receives an N4 rule including the second N4 rule, the same setting may be made.

Further, the UPF may send an N4 session establishment response message to the SMF, for example, via the N4 interface, based on the reception of the N4 session establishment request message and / or the completion of the above settings (S710). This N4 session establishment response message may be sent including information indicating that the above settings have been completed. In addition, if the UPF does not apply the first N4 rule to the SA PDU session via 3GPP access, this N4 session establishment response message will be sent to the SA PDU session via 3GPP access. It may be sent with information indicating that the first N4 rule has not been applied.

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

The SMF then receives the PDU session establishment request message and / or the UPF selection and / or receives the N4 session establishment response message, for example, via the N11 interface, the N1 SM container, and / or N2 SM information and / or PDU session ID (25th identification information) is sent to AMF (S712). Here, the N1SM container may include a PDU session establishment acceptance message, and further, the PDU session establishment acceptance message includes an ATSSS container IE (Information Element) and / or a new ATSSS container IE. Good.

Next, the AMF that receives the N1 SM container and / or N2 SM information and / or the PDU session ID (25th identification information) sends a NAS message to the UE via the access network (S714) (S714). S716). Here, the NAS message is transmitted, for example, via the N1 interface. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

Specifically, when the AMF sends an N2 PDU session request message to the access network (S714), the access network that receives the N2 PDU session request message sends a NAS message to the UE (S716). ). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. In addition, the NAS message may include a PDU session ID (25th identification information) and / or an N1 SM container.

Here, the access network is 3GPP access. That is, the AMF sends a NAS message to the UE via the base station device_110 included in the 3GPP access.

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

Here, the SMF and / or AMF are the ATSSS container IE and / or the new ATSSS container IE, and / or the PDU session establishment acceptance message, and / or the N1 SM container, and / or the PDU session ID (25th identification). Information) and / or NAS message and / or N2SM information and / or N2PDU session request message indicates that at least part of the UE request by the PDU session establishment request message has been accepted. You may.

Here, if the SMF and / or PCF permits the establishment of an SA PDU session for communication using the eATSSS function, and / or if the establishment of user plane resources via 3GPP access is permitted, and If communication by the / or eATSSS function is permitted, the SMF and / or AMF will use the ATSSS container IE and / or the new ATSSS container IE, and / or the PDU session establishment acceptance message, and / or the N1 SM container, and /. Alternatively, the NAS message and / or the N2SM information and / or the N2PDU session request message may include at least one of the 21st to 32nd identification information and be transmitted.

Here, the identification information of Chapters 21 to 32 may be as described in Chapter 3.2.

The 21st identification information is a DNN that identifies the DN to which the SA PDU session for communication using the eATSSS function is connected. The 21st identification information may be the same as the 1st identification information.

In addition, the network preferably supports at least one of the functions indicated by the 22nd to 24th identification information, and if it supports the function, the identification information supports the function. It is preferable to show.

Further, the 25th identification information is a PDU session ID for identifying the SA PDU session via 3GPP access, and may be the same as the 5th identification information.

Also, the 29th identity is that the establishment of SA PDU session (for eATSSS function) is permitted and / or the establishment of userplane resources via 3GPP access is permitted, and / or eATSSS. It may indicate that communication by the function is permitted.

Further, the thirtieth identification information may be the ATSSS rule or the first ATSSS rule. As the steering function included in the thirtieth identification information, it is preferable that the steering function supported by the UE or the eATSSS function is shown.

In addition, the 31st identification information indicates that the PDU session establishment procedure is executed in order to establish the SA PDU session that has not yet been established among the two SA PDU sessions used for communication by the eATSSS function. It may be information.

In addition, SMF and / or AMF may use ATSSS container IE and / or new ATSSS container IE and / or PDU session establishment acceptance message and / or N1 SM container and / or NAS message, and / or N2 SM information. , And / or N2 PDU session request message includes at least one of the 21st to 32nd identification information to allow the establishment of an SA PDU session for communication using the eATSSS function. And / or the establishment of userplane resources via 3GPP access was permitted, and / or communication by the eATSSS function was permitted, and / or two SA PDU sessions used for communication by the eATSSS function. Of these, the UE may be instructed to perform the PDU session establishment procedure in order to establish an SA PDU session that has not yet been established.

Also, if the SMF and / or PCF allows the establishment of a MAPDU session, and / or if the establishment of userplane resources via 3GPP access in the MAPDU session is permitted, and / or communication by the ATSSS function. If allowed, the SMF and / or AMF will use the ATSSS container IE and / or the new ATSSS container IE and / or the PDU session establishment acceptance message and / or the N1 SM container and / or the NAS message, and / Alternatively, the N2SM information and / or the N2PDU session request message may include at least one of the identification informations 21 to 30, 32.

Here, the identification information of Chapters 21 to 30 and 32 may be as described in Chapter 3.2.

Here, the 21st identification information is a DNN that identifies the DN to which the MA PDU session is connected. The 21st identification information may be the same as the 1st identification information.

In addition, the network preferably supports at least one of the functions indicated by the identification information Nos. 22 to 23, and if the function is supported, the identification information supports the function. It is preferable to show.

Further, the 25th identification information is a PDU session ID for identifying the MA PDU session, and may be the same as the 5th identification information.

Also, the 29th identification information is that the establishment of MAPDU session (for ATSSS function) is permitted and / or the establishment of userplane resources via 3GPP access in MAPDU session is permitted. And / or it may indicate that communication by the ATSSS function is permitted.

Further, the thirtieth identification information may be an ATSSS rule or a second ATSSS rule. The steering function included in the thirtieth identification information is preferably a steering function supported by the UE, an ATSSS-LL function, or an MPTCP function.

Note that SMF and / or AMF can use the control messages of layers lower than the NAS layer (for example, RRC layer, MAC layer, RLC layer, PDCP layer, etc.) and the NAS layer for the identification information of the 21st to 30th and 32nd. May be included in the control message of the upper layer (for example, transport layer, session layer, presentation layer, application layer, etc.) and transmitted.

In addition, SMF and / or AMF may use ATSSS container IE and / or new ATSSS container IE and / or PDU session establishment acceptance message and / or N1 SM container and / or NAS message, and / or N2 SM information. , And / or the establishment of the MA PDU session is permitted by sending the N2 PDU session request message including at least one of the identification information of Nos. 21 to 30 and 32, and / or the MA PDU. The UE may be notified that the establishment of userplane resources via 3GPP access in the session is permitted and / or communication by the ATSSS function is permitted.

SMF and / or AMF can notify the UE of the contents of these identification information by transmitting at least one of these identification information.

Note that SMF and / or AMF are ATSSS container IE and / or new ATSSS container IE and / or PDU session establishment acceptance message and / or N1 SM container and / or NAS message, and / or N2 SM information. , And / or which identification information is included in the N2 PDU session request message, each received identification information and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy. , And / or the state of the network, and / or the user's registration information, and / or the context held by the SMF and / or AMF, etc., may be selected and determined.

Next, when the UE receives the NAS message via, for example, the N1 interface (S716), the UE request by the PDU session establishment request message is accepted, and / or the information contained in the NAS message, etc. (message, Can recognize the contents of containers and information).

For example, when the UE receives a PDU session establishment acceptance message containing the ATSSS container IE and / or the new ATSSS container IE containing the thirtieth identification information including the steering function indicating the eATSSS function, the UE performs the eATSSS function. The establishment of an SA PDU session for communication used was permitted, and / or an SA PDU session for communication using the eATSSS function was established, and / or user plane resources via 3GPP access. The establishment was allowed, and / or userplane resources were established via 3GPP access, and / or communication by the eATSSS function was permitted, and / or two used for communication by the eATSSS function. You may recognize that you are instructed to perform a PDU session establishment procedure to establish an SA PDU session that has not yet been established.

Also, for example, if the UE requests the establishment of an SA PDU session (for the eATSSS function) or sends a ninth identification information indicating that it requires communication by the eATSSS function, the UE supports it. When the UE receives a PDU session establishment acceptance message containing the ATSSS container IE and / or the new ATSSS container IE containing the 30th identification information including the steering function indicating the steering function, the UE uses the eATSSS function. The establishment of SA PDU session for communication was permitted, and / or the establishment of SA PDU session for communication using the eATSSS function, and / or the establishment of user plane resources via 3GPP access. Allowed and / or established userplane resources via 3GPP access, and / or allowed communication with the eATSSS feature, and / or two SA PDUs used for communication with the eATSSS feature You may recognize that you are instructed to perform a PDU session establishment procedure to establish a SA PDU session that has not yet been established.

Also, for example, when the UE receives the 24th identification information indicating that the network supports the eATSSS function, the UE is allowed to establish a SA PDU session for communication using the eATSSS function. , And / or an SA PDU session for communication using the eATSSS function has been established, and / or the establishment of user plane resources via 3GPP access has been permitted, and / or user via 3GPP access. The plane resources have been established, and / or communication with the eATSSS function has been permitted, and / or the SA PDU session that has not yet been established out of the two SA PDU sessions used for communication with the eATSSS function has been established. You may recognize that you are instructed to perform the PDU session establishment procedure.

Also, for example, when the UE receives the 29th identification information and / or the 31st identification information, the UE is permitted to establish an SA PDU session for communication using the eATSSS function, and / Alternatively, an SA PDU session for communication using the eATSSS function has been established, and / or the establishment of userplane resources via 3GPP access has been permitted, and / or userplaneresources via 3GPP access. To establish an SA PDU session that has been established and / or has been allowed to communicate with the eATSSS function, and / or has not yet been established, of the two SA PDU sessions used for communication with the eATSSS function. , You may recognize that you are instructed to perform the PDU session establishment procedure.

In addition, the UE was allowed to establish an SA PDU session for communication using the eATSSS function, and / or an SA PDU session for communication using the eATSSS function was established, and / or 3GPP. The establishment of userplane resources via access was permitted, and / or the establishment of userplane resources via 3GPP access, and / or communication by the eATSSS function was permitted, and / or the eATSSS function. 3GPP access after recognizing that you are instructed to perform a PDU session establishment procedure to establish an SA PDU session that has not yet been established out of the two SA PDU sessions used for communication by The SA PDU session via SA PDU session may be established. In other words, each device, including the UE, may be ready to communicate with the DN using a SA PDU session via 3GPP access.

Also, for example, establishing a PDU session including an ATSSS container IE and / or a new ATSSS container IE that includes a thirtieth identification information including a steering function supported by the UE, or an ATSSS-LL function, or a steering function indicating the MPTCP function. When the UE receives the acceptance message, the UE establishes a MAPDU session via 3GPP access and non-3GPP access, and / or userplane resources established via 3GPP access in the MAPDU session. You may recognize that.

Also, after the UE recognizes that a MAPDU session has been established via 3GPP access and non-3GPP access, and / or userplane resources have been established via 3GPP access in the MAPDU session, then 3GPP The MAPDU session using userplane resources via access and non-3GPP access may be established. In other words, each device including the UE may be in a state where it can communicate with the DN using the MAPDU session composed of userplane resources via 3GPP access. Also, the UE may be in a state where it can communicate with the DN. Based on the contents of etc. (message, container, information), the 25th identification information (PDU session ID) received is for identifying the MA PDU session or identifies the SA PDU session via 3GPP access. It may be possible to identify whether it is for.

With the above, the procedure (A) in Fig. 7 may be completed normally.

Regarding the behavior of each device after this, "when the establishment of the MAPDU session is permitted and / or when the establishment of userplane resources via 3GPP access in the MAPDU session is permitted, and / or ATSSS. "When communication by function is permitted" is explained in Chapter 4.2, and "When establishment of SA PDU session for communication using eATSSS function is permitted, and / or user planet resources via 3GPP access". When the establishment of is permitted and / or when communication by the eATSSS function is permitted ”is explained in Chapter 4.3.

[4.2. When the establishment of MA PDU session for communication by ATSSS function is permitted]
Next, in Chapter 4.1, if the SMF and / or PCF allows the establishment of MA PDU sessions, and / or if the establishment of user plane resources via 3GPP access in MA PDU sessions is permitted, and / Alternatively, if communication by the ATSSS function is permitted, each device including the UE may execute the procedure (B) in FIG. The procedure (B) in FIG. 7 will be described below.

First, the UE that received the NAS message on the S716 has established a MAPDU session via 3GPP access and non-3GPP access, and / or a userplane via 3GPP access in the MAPDU session, as described above. It may be in a state of recognizing that resources have been established. That is, each device including the UE may be in a state in which a MAPDU session using userplane resources via 3GPP access and non-3GPP access has been established. In other words, each device including the UE may be in a state where it can communicate with the DN using a MAPDU session composed of userplane resources via 3GPP access.

Next, the SMF may send an N4 session correction request message to the already selected UPF_230 via the N4 interface (S718). Here, the N4 session correction request message does not need to be transmitted including the N4 rule or the second N4 rule, but may be included.

Next, when UPF_230 receives the N4 session correction request message, it can recognize the content of the information received from SMF. In addition, when the UPF receives the second N4 rule, it will use userplane resources via 3GPP access and user via non-3GPP access for downlink traffic in the MAPDU session used for communication by the ATSSS function. You may set plane resources to operate according to the second N4 rule. Further, the UPF may make the same setting when receiving the N4 rule including the second N4 rule.

In addition, UPF_230 may send an N4 session correction response message to SMF via the N4 interface (S720). When the above settings are made, the N4 session correction response message may include information indicating that the settings have been completed.

Next, when the SMF receives the N4 session correction response message, it can recognize the content of the information received from the UPF. Note that S718 and S720 may be omitted.

Next, the SMF transmits the N2SM information and / or the PDU session ID and / or the access type to the AMF via, for example, the N11 interface (S722). Here, the PDU session ID may be the same as the PDU session ID transmitted by S712, and the access type may indicate non-3GPP access. Further, the SMF does not need to send the N1SM container to the AMF, but may send it. Note that the SMF may indicate that N2SM information should be transmitted via non-3GPP access by transmitting the PDU session ID and / or access type to the AMF.

Next, when the AMF receives the N2SM information and / or the PDU session ID and / or the access type, it should send the N2SM information via the non-3GPP access specified by the access type. May be recognized.

Next, when the MA PDU session uses untrusted non-3GPP access, AMF may send an N2 PDU session request message to N3IWF. Further, when the MA PDU session uses Trusted non-3GPP access, AMF may send an N2 PDU session request message to TNGF and / or TNAP. Here, it is assumed that the N2 PDU session request message is sent to N3IWF (S724). In addition, the N2 PDU session request message may include N2 SM information. In addition, the N2 PDU session request message does not have to include the NAS message, but may be included.

Next, N3IWF executes the procedure for establishing IPsec child SA (security association) with the UE via the access network (S726).

Specifically, the N3IWF requests the IKE Create_Child_SA in accordance with the IKEv2 standard described in RFC 7296 to establish an IPsec Child SA for MA PDU sessions (user plane resources via non-3GPP access in MA PDU sessions). Send a message to the UE. Here, the IKE Create_Child_SA request message may indicate that the requested IPsec Child SA operates in tunnel mode. Also, the IKE Create_Child_SA request message may include the PDU session ID associated with this Child SA. In other words, the IPsec Child SA may be associated with the PDU session ID of the MA PDU session.

Next, when the UE accepts IPsec Child SA, it sends an IKE Create_Child_SA response message to N3IWF.

From the above, IPsec Child SA is established between UE and N3IWF.

After the IPsec Child SA is established, the N3IWF can send a NAS message including a PDU session establishment acceptance message to the UE via the base station device_120. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

Further, the SMF and / or AMF may send the N2SM information and / or the N2PDU session request message including at least one of the identification informations 21 to 30 and 32. The SMF and / or AMF may notify the UE and / or N3IWF and / or the access network of the content of these identifications by transmitting at least one of these identifications.

The contents of the identification information of Nos. 21 to 30 and 32 may be the same as the contents in the procedure of (A) in FIG.

The UE is allowed to establish a MA PDU session for communication using the ATSSS function based on the reception of the IKE Create_Child_SA request message and / or the transmission of the IKE Create_Child_SA response message, and / or the ATSSS function. An MA PDU session has been established for communication using, and / or the establishment of userplane resources via non-3GPP access in the MA PDU session has been permitted, and / or non- in the MA PDU session. It may be recognized that userplane resources have been established via 3GPP access and / or communication by the ATSSS function has been permitted.

The N4 rule or the second N4 rule in the UPF may be applied after receiving the N4 session establishment request message of S708 or after receiving the N4 session correction request message of S718.

Further, the application of the ATSSS rule or the second ATSSS rule in the UE may be performed after receiving the NAS message of S716, or may be performed after the establishment of IPsec Child SA of S726.

With the above, the procedure (B) in Fig. 7 is completed normally.

At this stage, each device including the UE can establish a MA PDU session using userplane resources via non-3GPP access in addition to the already established userplane resources via 3GPP access. .. In other words, each device including the UE is ready to communicate with the DN using a MAPDU session with userplane resources via 3GPP access and userplane resources via non-3GPP access. Good.

[4.3. When the establishment of SA PDU session for communication by eATSSS function is permitted]
Next, in Chapter 4.1, if the SMF and / or PCF allows the establishment of SA PDU sessions for communication using the eATSSS function, and / or the establishment of user plane resources via 3GPP access. PDUs to establish an unestablished SA PDU session of the two SA PDU sessions used for communication with the eATSSS function and / or when communication with the eATSSS function is permitted. When instructed to perform a session establishment procedure, each device, including the UE, has the procedure in Figure 8 (second SA PDU session) to establish an SA PDU session (second SA PDU session) via non-3GPP access. PDU session establishment procedure via non-3GPP access) may be initiated. In this case, it is not necessary to execute (B) in FIG. The procedure shown in FIG. 8 will be described below.

First, the UE that received the NAS message on the S716, as described above, the UE was allowed to establish a SA PDU session for communication using the eATSSS function, and / or communication using the eATSSS function. SA PDU session was established for, and / or user plane resources were allowed to be established via 3GPP access, and / or userplane resources were established via 3GPP access, and / or Perform a PDU session establishment procedure to establish an SA PDU session that has not yet been established out of the two SA PDU sessions used for communication by the eATSSS function and / or communication by the eATSSS function. You may be in a state of recognizing that you are instructed to do so. That is, each device including the UE may be in a state in which an SA PDU session (first SA PDU session) via 3GPP access has been established. In addition, each device including the UE may be in a state of being able to communicate with the DN by using the first SA PDU session via 3GPP access.

First, the UE starts the PDU session establishment procedure by sending a NAS message containing the N1SM container including the PDU session establishment request message to the AMF via the access network (S800). The NAS message is, for example, a message transmitted via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message. The PDU session establishment request message was established for sending and receiving NAS messages between the UE and AMF by, for example, performing a registration procedure via non-3GPP access before this procedure. It may be sent to AMF using IPsec SA.

Here, the access network is non-3GPP access. Further, as described above, non-3GPP access includes Untrusted non-3GPP access and Trusted non-3GPP access, but here, the case of Untrusted non-3GPP access will be described as an example. That is, the UE sends a NAS message to the AMF via the base station device_120 included in the non-3GPP access.

The UE also requests the PDU session establishment request message and / or the N1SM container and / or NAS message by including at least one of the identification information 1 to 11. This can be notified to the network side.

Here, the identification information of Chapters 1 to 11 may be as described in Chapter 3.2.

Here, the first identification information is the DNN that identifies the DN to which the second SA PDU session is connected. This first identification information is preferably the same as the first identification information and / or the 21st identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that this second identification information is the same as the second identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that this third identification information is the same as the third identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that this fourth identification information is the same as the fourth identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

The UE preferably supports at least one of the functions indicated by the second to fourth identification information, and if the function is supported, the identification information supports the function. It is preferable to show.

The fifth identification information is the PDU session ID for identifying the second SA PDU session. This fifth identification information is preferably different from the fifth identification information and / or the 25th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. This is established by the SA PDU session (first SA PDU session) established by the PDU session establishment procedure executed via 3GPP access and the PDU session establishment procedure executed through this non-3GPP access. This may be because the SA PDU session (second SA PDU session) is a different SA PDU session.

Further, it is preferable that the sixth identification information is the same as the sixth identification information and / or the 26th identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, this 7th identification information may be the same as or different from the 7th identification information and / or the 27th identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access. May be good.

Further, this eighth identification information may be the same as or different from the eighth identification information and / or the 28th identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access. May be good.

Further, the ninth identification information may be information indicating that the establishment of the SA PDU session (for the eATSSS function) is requested and / or information indicating that communication by the eATSSS function is requested. This ninth identification information may be a request type. That is, the request type, which is the ninth identification information, may indicate that the establishment of the SA PDU session (for the eATSSS function) is requested and / or the communication by the eATSSS function is requested. For example, when requesting the establishment of an SA PDU session (for the eATSSS function) and / or when requesting communication by the eATSSS function, the request type that is the ninth identification information is eATSSS, or eATSSS request, or SA PDU request may be indicated.

Further, this tenth identification information is preferably the same as the fifth identification information and / or the 25th identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access, and in this procedure. It is preferably different from the fifth identification information to be transmitted.

Regarding the identification information of the first to eleventh, the UE has a control message of a layer lower than the NAS layer (for example, RRC layer, MAC layer, RLC layer, PDCP layer) and a layer higher than the NAS layer (transport layer). , Session layer, presentation layer, application layer) may be included in the control message and sent.

When the identification information of 1st to 9th and 11th transmitted in this procedure is the same as the identification information of 1st to 9th and 11th transmitted in (PDU session establishment procedure executed via 3GPP access). The UE does not have to transmit at least a part of the identification information of the first to ninth and eleventh in this PDU session establishment procedure.

Next, when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the contents of the information (message, container, information) contained in the NAS message.

Here, the AMF is the first if the UE is registered via both accesses, but the S-NSSAI (8th identification information) received from the UE is not permitted for both accesses. The request to establish the SA PDU session of 2 may be rejected. The AMF may also reject the request to establish a second SA PDU session if the network and / or core network device does not support the eATSSS feature.

Here, the fact that the UE is registered via both accesses means that the UE is registered in the network via 3GPP access and the UE is registered in the network via non-3GPP access. May mean.

Also, if S-NSSAI is not allowed for both accesses, then the connection to the network via 3GPP access is not allowed and the connection to the network via non-3GPP access is allowed. It may mean S-NSSAI that has not been done.

Further, when rejecting the request for establishing the second SA PDU session, each device may skip, that is, cancel the step after S802.

Further, when rejecting the request for establishing the second SA PDU session, the AMF may send a NAS message to the UE containing information indicating that the request for establishing the second SA PDU session is rejected. At this time, the AMF does not need to send at least a part of the information (message, container, information) included in the NAS message received from the UE to the SMF. In addition, the UE may detect that this procedure has not been completed normally or that this procedure has been completed abnormally by receiving this NAS message from AMF.

Also, when rejecting the request to establish a second SA PDU session, the AMF sends information to the SMF indicating that the request to establish the PDU session is rejected, and the SMF includes a PDU session establishment refusal message. A NAS message containing an N1 SM container may be sent to the UE. At this time, the PDU session establishment refusal message and / or the N1SM container and / or the NAS message may contain information indicating that the request for establishing the second SA PDU session is rejected. In addition, the UE received a PDU session establishment refusal message and / or N1SM container and / or NAS message from the SMF, and this procedure was not completed normally, or this procedure was completed abnormally. You may detect that you have done so.

Next, AMF selects SMF as the transfer destination of at least a part of the information (messages, containers, information) contained in the NAS message received from the UE (S802). In addition, AMF includes information (messages, containers, information) contained in NAS messages, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or. The transfer destination SMF may be selected based on the network status and / or the user's registration information and / or the context held by the AMF. The AMF may also select an SMF that supports the ATSSS function and / or the eATSSS function. Here, it is assumed that SMF_220 that supports the ATSSS function and / or the eATSSS function is selected.

Next, the AMF transmits at least a part of the information (message, container, information) contained in the NAS message received from the UE to the selected SMF, for example, via the N11 interface (S804). The AMF may also send information to the SMF indicating that the UE is registered for both accesses.

Next, when the SMF receives the information (message, container, information) transmitted from the AMF, the UE requests and / or the content of the information (message, container, information) received from the AMF. Can be recognized.

Here, the SMF may determine the first condition. Further, the first condition determination may be for determining whether or not to accept the UE request. Further, in the first condition determination, the SMF determines whether the first condition determination is true or false. Further, if the SMF determines that the first condition determination is true, the procedure (A) in FIG. 8 may be started, and if the first condition determination is determined to be false, the procedure for rejecting the UE request. May start. The procedure for rejecting a UE request is described in Chapter 4.4.

The first condition determination is information received from AMF (messages, containers, information) and / or subscriber information (subscription information), and / or network capability information, and / or UE policy, and /. Alternatively, it may be executed based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the SMF.

For example, if the network permits the UE request, the first condition determination may be determined to be true, and if the UE request is not permitted by the network, the first condition determination may be determined to be false. Also, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the first condition determination may be determined to be true, and the functions required by the UE are supported. If not, the first condition determination may be determined to be false. Further, when the transmitted / received identification information is permitted, the first condition determination may be determined to be true, and when the transmitted / received identification information is not permitted, the first condition determination may be determined to be false.

Also, if the network allows the establishment of SA PDU sessions for communication using the eATSSS function, and / or if it allows the establishment of userplane resources via non-3GPP access, and / or by the eATSSS function. When communication is permitted, the first condition determination may be determined to be true. Also, if the network does not allow the establishment of SAPDU sessions for communication using the eATSSS function, and / or if it does not allow the establishment of userplane resources via non-3GPP access, and / or by the eATSSS function. If communication is not permitted, the first condition determination may be determined to be false.

The condition for determining the authenticity of the first condition determination is not limited to the above-mentioned condition.

Next, each step of the procedure (A) in Fig. 8 will be explained.

First, SMF may select PCF. For example, the SMF may select an appropriate PCF based on the received identification information. For example, the SMF may select a PCF that supports the ATSSS function and / or the eATSSS function. Also, for example, if the SMF detects that this procedure has been performed to establish an SA PDU session used for communication by its eATSSS function, it may select a PCF that has already been selected. Here, it is assumed that PCF_250 that supports the ATSSS function and / or the eATSSS function is selected.

Next, the SMF may send at least a part of the information (messages, containers, information) received from the AMF to the PCF (S806).

In addition, if the SMF decides to allow the establishment of an SA PDU session for communication using the eATSSS function, and / or if it decides to allow the establishment of user plane resources via non-3GPP access, And / or if it decides to allow communication by the eATSSS function, the SMF may send additional information to the PCF. Here, as additional information, "information indicating that the establishment of the SA PDU session for communication using the eATSSS function is permitted" and / or "establishment of user plane resources via non-3GPP access" is provided. Information indicating that it has been permitted, and / or "communication by the eATSSS function has been permitted", and / or "access type corresponding to the established SA PDU session and / or user plane resources" may be included. Here, the access type may indicate non-3GPP access.

Although the above judgment is described as being made by SMF, it may be made by PCF. That is, the SMF and / or the PCF may make the above judgment. If the SMF does not make the above decision, the SMF may not send the above additional information to the PCF.

Next, when the PCF receives the information (message, container, information) sent from the SMF, it can recognize the contents.

The PCF is based on the information received from the SMF (messages, containers, information) and / or the UE policy, and / or the operator policy, and / or the subscriber information (subscription information), etc., as described above in the SMF. A judgment similar to the judgment may be made.

If the PCF makes the above judgment, the PCF may transmit to the SMF the above additional information described as being transmitted from the SMF to the PCF.

Further, when the PCF detects that the above judgment is made in the SMF, it is not necessary to make this judgment (may be skipped).

Also, if the SMF and / or PCF permits the establishment of SA PDU sessions for communication using the eATSSS function, and / or if the establishment of user plane resources via non-3GPP access is permitted. And / or if communication by the eATSSS function is permitted, the PCF may generate a first PCC rule or PCC rule.

If the first PCC rule or PCC rule generated in the PDU session establishment procedure via 3GPP access includes a distribution rule for the second SA PDU session via non-3GPP access, the PCF will It is not necessary to generate this first PCC rule or PCC rule. In this case, it is not necessary to send the first PCC rule or PCC rule to the SMF.

Also, if the first PCC rule or PCC rule generated in the PDU session establishment procedure via 3GPP access does not include a distribution rule for the second SA PDU session via non-3GPP access, non. -You may generate a first PCC rule or PCC rule that contains a distribution rule for a second SA PDU session via 3GPP access.

In addition, if the PCF does not generate the first PCC rule or PCC rule in the PDU session establishment procedure via 3GPP access, the distribution rule for the second SA PDU session via 3GPP access in this procedure. , And a first PCC rule or PCC rule containing a distribution rule for a second SA PDU session via non-3GPP access may be generated.

Then, when the PCF generates the first PCC rule, the generated PCC rule may be sent to the SMF.

Note that the PCF may generate the first PCC rule as the above-mentioned PCC rule. That is, the PCC rule may include the first PCC rule. The PCF may then send the generated PCC rules to the SMF.

Next, when the SMF receives the information transmitted from the PCF, it can recognize the contents of the information.

Then, when the SMF receives the first PCC rule from the PCF, the SMF may generate the first ATSSS rule (30th identification information) and the first N4 rule from the first PCC rule. In addition, the SMF may manage (that is, map) the first PCC rule, the first ATSSS rule, and the first N4 rule in association with each other.

When the SMF receives the PCC rule instead of the first PCC rule from the PCF, the SMF may generate the ATSSS rule (30th identification information) and the N4 rule from the PCC rule. In this case, the ATSSS rule may be the same as the first ATSSS rule, and the N4 rule may be the same as the first N4 rule. In addition, the SMF may manage (that is, map) the PCC rule, the ATSSS rule, and the N4 rule in association with each other.

Next, the SMF selects the UPF for the first SA PDU session and sends an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S808).

Further, when the SMF receives the first PCC rule from the PCF, the SMF may include the first N4 rule in the N4 session establishment request message. Further, when the SMF receives the PCC rule from the PCF, the SMF may include the N4 rule in the N4 session establishment request message.

Here, SMF refers to information received from AMF (messages, containers, information) and / or information received from PCF and / or subscriber information, and / or network capability information, and / or UE policy. One or more UPFs may be selected based on and / or operator policy and / or network status and / or user registration information and / or context held by the SMF. Also, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF.

Also, if the SMF and / or PCF permits the establishment of SA PDU sessions for communication using the eATSSS function, and / or if the establishment of user plane resources via non-3GPP access is permitted. And / or if communication by the eATSSS function is permitted, the SMF may select a UPF that supports the eATSSS function.

In addition, the SMF may select the UPF if it has already been selected in the PDU session establishment procedure executed via 3GPP access.

Here, it is assumed that UPF_230 that supports the ATSSS function and / or the eATSSS function is selected.

Next, when the UPF receives the N4 session establishment request message (S808), the UPF can recognize the content of the information received from the SMF.

Further, when the UPF receives the first N4 rule or the N4 rule from the SMF, the UPF may be set to operate according to the received N4 rule.

That is, when the UPF receives the first N4 rule, it is trying to establish downlink traffic in the two SA PDU sessions used for communication by the eATSSS function by this procedure (PDU session establishment procedure) non-3GPP. The second SA PDU session via access may be set to operate according to the first N4 rule. In addition, when the UPF receives the first N4 rule, it will access the first SA PDU session and non-3GPP access via 3GPP access for downlink traffic in the two SA PDU sessions used for communication by the eATSSS function. The second SA PDU session via the above may be set to operate according to the first N4 rule. Further, when the UPF receives an N4 rule having the same contents as the first N4 rule, the UPF may make the same settings as described above.

Further, the UPF may send an N4 session establishment response message to the SMF, for example, via the N4 interface, based on the reception of the N4 session establishment request message and / or the completion of the above settings (S810). This N4 session establishment response message may be sent including information indicating that the above settings have been completed.

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

The SMF then receives the PDU session establishment request message and / or the UPF selection and / or receives the N4 session establishment response message, for example, via the N11 interface, the N1 SM container, and / or N2 SM information and / or PDU session ID (25th identification information) is sent to AMF (S812). Here, the N1SM container may include a PDU session establishment acceptance message, and further, the PDU session establishment acceptance message includes an ATSSS container IE (Information Element) and / or a new ATSSS container IE. Good.

Next, the AMF receives the N1 SM container and / or N2 SM information and / or the PDU session ID (25th identification information).

Then, when an SA PDU session is established via non-3GPP access (untrusted non-3GPP access), AMF may send an N2 PDU session request message to N3IWF (S814). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. In addition, the NAS message may include a PDU session ID (25th identification information) and / or an N1 SM container. When an SA PDU session is established via Trusted non-3GPP access, AMF may send an N2 PDU session request message to TNGF and / or TNAP.

Next, N3IWF executes the procedure for establishing IPsec child SA (security association) with the UE via the access network (S816).

Specifically, N3IWF sends an IKE Create_Child_SA request message to the UE in accordance with the IKEv2 standard described in RFC 7296 in order to establish an IPsec Child SA for an SA PDU session via non-3GPP access. Here, the IKE Create_Child_SA request message may indicate that the requested IPsec Child SA operates in tunnel mode. Also, the IKE Create_Child_SA request message may include the PDU session ID associated with this Child SA. In other words, the IPsec Child SA may be associated with the PDU session ID of the SA PDU session via non-3GPP access.

Next, when the UE accepts IPsec Child SA, it sends an IKE Create_Child_SA response message to N3IWF.

From the above, IPsec Child SA is established between UE and N3IWF.

After the IPsec Child SA is established, the N3IWF can send a NAS message including a PDU session establishment acceptance message to the UE via the base station device_120. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

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

Here, the SMF and / or AMF are the ATSSS container IE and / or the new ATSSS container IE, and / or the PDU session establishment acceptance message, and / or the N1 SM container, and / or the PDU session ID (25th identification). Information) and / or NAS message and / or N2SM information and / or N2PDU session request message indicates that at least part of the UE request by the PDU session establishment request message has been accepted. You may.

Also, if the SMF and / or PCF allows the establishment of SA PDU sessions for communication using the eATSSS function, and / or if the establishment of user plane resources via 3GPP access is permitted, and / Or, if communication by the eATSSS function is permitted, the SMF and / or AMF will use the ATSSS container IE and / or the new ATSSS container IE, and / or the PDU session establishment acceptance message, and / or the N1 SM container, and / or. The NAS message and / or N2SM information and / or N2PDU session request message may include at least one of the 21st to 30th and 32nd identification information.

Here, the identification information of Chapters 21 to 30 and 32 may be as described in Chapter 3.2.

Here, the 21st identification information is a DNN that identifies the DN to which the second SA PDU session is connected. The 21st identification information is preferably the same as the 1st identification information and / or the 21st identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. Further, it is preferable that the 21st identification information is the same as the 1st identification information transmitted / received in the PDU session establishment procedure.

Further, it is preferable that the 22nd identification information is the same as the 22nd identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that the 23rd identification information is the same as the 23rd identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that the 24th identification information is the same as the 24th identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

In addition, the network preferably supports at least one of the functions indicated by the 22nd to 24th identification information, and if it supports the function, the identification information supports the function. It is preferable to show.

Further, the 25th identification information may be a PDU session ID that identifies the second SA PDU session. This 25th identification information is preferably different from the 5th identification information and / or the 25th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. Further, the 25th identification information may be the same as the 5th identification information transmitted / received in the PDU session establishment procedure.

Further, the 26th identification information may be the PDU session type of the second SA PDU session. The 26th identification information is preferably the same as the 6th identification information and / or the 26th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. Further, the 26th identification information may be the same as the 6th identification information transmitted / received in the PDU session establishment procedure.

Further, the 27th identification information may be the SSC mode of the second SA PDU session. This 27th identification information may be the same as or different from the 7th identification information and / or the 27th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. .. Further, the 27th identification information may be the same as or different from the 7th identification information transmitted / received in the PDU session establishment procedure.

Also, the 28th identification information may be one or more S-NSSAI. This 28th identification information may be the same as or different from the 8th identification information and / or the 28th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. .. Further, the 28th identification information may be the same as or different from the 8th identification information transmitted / received in the PDU session establishment procedure.

Also, the 29th identity indicates that the establishment of a SA PDU session (for the eATSSS function) was allowed and / or that the user plane resources were allowed to be established via non-3GPP access, and / Alternatively, it may indicate that communication by the eATSSS function is permitted.

Further, the thirtieth identification information may be the ATSSS rule or the first ATSSS rule. As the steering function included in the thirtieth identification information, it is preferable that the steering function supported by the UE or the eATSSS function is shown.

In addition, SMF and / or AMF may use ATSSS container IE and / or new ATSSS container IE and / or PDU session establishment acceptance message and / or N1 SM container and / or NAS message, and / or N2 SM information. , And / or N2 PDU session request message includes at least one of the 21st to 30th and 32nd identification information to allow the establishment of an SA PDU session for communication using the eATSSS function. The UE may be notified that it has been done and / or that the establishment of userplane resources via non-3GPP access has been permitted and / or that communication by the eATSSS function has been permitted.

SMF and / or AMF can notify the UE and / or N3IWF and / or access network of the contents of these identification information by transmitting at least one of these identification information.

Note that SMF and / or AMF are ATSSS container IE and / or new ATSSS container IE and / or PDU session establishment acceptance message and / or N1 SM container and / or NAS message, and / or N2 SM information. , And / or which identification information is included in the N2 PDU session request message, each received identification information and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy. , And / or the state of the network, and / or the user's registration information, and / or the context held by the SMF and / or AMF, etc., may be selected and determined.

Next, when the UE receives the NAS message via, for example, the N1 interface (S816), the UE request by the PDU session establishment request message is accepted, and / or the information contained in the NAS message, etc. (message, Can recognize the contents of containers and information).

For example, when the UE receives a PDU session establishment acceptance message containing the ATSSS container IE and / or the new ATSSS container IE containing the thirtieth identification information including the steering function indicating the eATSSS function, the UE performs the eATSSS function. The establishment of an SA PDU session for communication used was permitted, and / or an SA PDU session for communication using the eATSSS function was established, and / or a user plane via non-3GPP access. It may be recognized that the establishment of resources has been permitted and / or that userplane resources have been established via non-3GPP access and / or that communication by the eATSSS function has been permitted.

Also, for example, if the UE requests the establishment of an SA PDU session (for the eATSSS function) or sends a ninth identification information indicating that it requires communication by the eATSSS function, the UE supports it. When the UE receives a PDU session establishment acceptance message containing the ATSSS container IE and / or the new ATSSS container IE containing the thirtieth identification information including the steering function indicating the steering function, the UE uses the eATSSS function. The establishment of an SA PDU session for communication was permitted, and / or an SA PDU session for communication using the eATSSS function was established, and / or user plane resources via non-3GPP access. You may recognize that the establishment was allowed and / or that userplane resources were established via non-3GPP access and / or that communication by the eATSSS function was allowed.

Also, for example, when the UE receives the 24th identification information indicating that the network supports the eATSSS function, the UE is allowed to establish a SA PDU session for communication using the eATSSS function. , And / or an SA PDU session for communication using the eATSSS function has been established, and / or the establishment of user plane resources via non-3GPP access has been permitted, and / or non-3GPP access. It may be recognized that user plane resources have been established via, and / or communication by the eATSSS function has been permitted.

Also, for example, the establishment of a SA PDU session (for the eATSSS function) was allowed, and / or the establishment of userplane resources via non-3GPP access was allowed, and / or communication by the eATSSS function. When the UE receives the 29th identification information indicating that is permitted, the UE is permitted to establish an SA PDU session for communication using the eATSSS function, and / or the eATSSS function. The SA PDU session for the communication used was established, and / or the establishment of userplane resources via non-3GPP access was permitted, and / or the userplane resources via non-3GPP access It may be recognized that it has been established and / or that communication by the eATSSS function has been permitted.

In addition, the UE identifies the SA PDU session via non-3GPP access by the 25th identification information (PDU session ID) received based on the contents of the information (message, container, information) contained in the NAS message. It may be possible to identify that it is for the purpose of doing so.

With the above, the procedure (A) in Fig. 8 may be completed normally.

At this stage, each device including the UE is in a state where a second SA PDU session is established via non-3GPP access. The UE uses two SA PDU sessions, which consist of an already established first SA PDU session via 3GPP access and a second SA PDU session via non-3GPP access, with the DN. Communication may be possible. That is, the UE may be in a state where communication by the eATSSS function is possible.

Although the case of Untrusted non-3GPP access has been described here as an example, it can also be applied to the case of Trusted non-3GPP access by replacing the base station devices _120 and N3IWF_240 with TNAP and TNGF, respectively. ..

[4.4. If the UE request is rejected]
Next, in Chapters 4.1 and / or 4.3, the procedure for rejecting the UE's request, which is executed when the first condition determination is false, will be described. This procedure may be initiated, for example, when the request to establish a PDU session is rejected, as described above.

First, the SMF sends a PDU session establishment refusal message to the UE via the AMF. Specifically, the SMF sends a PDU session establishment refusal message to the AMF, for example, via the N11 interface. When the AMF receives the PDU session establishment request message from the SMF, it sends a NAS message including a PDU session establishment refusal message to the UE, for example, using the N1 interface.

Here, the SMF may indicate that the UE request by the PDU session establishment request message has been rejected by sending the PDU session establishment refusal message.

By receiving the PDU session establishment refusal message, the UE can recognize that the UE request by the PDU session establishment request message has been rejected. That is, the UE can recognize that the request to establish a PDU session has been rejected by the network.

This completes the procedure for rejecting the UE request. The completion of the procedure for rejecting the UE request may mean that the PDU session establishment procedure has not been completed normally, or that the PDU session establishment procedure has been completed abnormally. In this case, the PDU session cannot be established.

[4.5. Application example]
Section 4.1 described the case where each device including the UE executes the PDU session establishment procedure via 3GPP access.

And in Chapter 4.2, when SMF and / or PCF permits the establishment of MAPDU sessions and / or when the establishment of userplane resources via 3GPP access in MAPDU sessions is permitted in Chapter 4.1. And / or when communication by the ATSSS function is permitted, the procedure to be executed by each device including the UE after the procedure in Chapter 4.1 is explained.

Also, in Chapter 4.3, in Chapter 4.1, when the SMF and / or PCF permits the establishment of an SA PDU session for communication using the eATSSS function, and / or the establishment of user plane resources via 3GPP access. To establish an SA PDU session that has not yet been established, of the two SA PDU sessions used for communication with the eATSSS function and / or when communication with the eATSSS function is permitted. Described the procedure that each device, including the UE, performs after the procedure in Chapter 4.1 when instructed to perform the PDU session establishment procedure.

Also, in Chapter 4.4, we explained the procedure for rejecting the UE request that is executed when the first condition judgment is determined to be false in the procedure in Chapter 4.1 and / or the procedure in Chapter 4.3.

That is, in Chapters 4.1 to 4.4, each device, including the UE, first performs a PDU session establishment procedure via 3GPP access, and then, if necessary, a PDU session establishment procedure via non-3GPP access. The case of executing it was explained.

However, each device including the UE may first execute the PDU session establishment procedure via non-3GPP access, and then, if necessary, execute the PDU session establishment procedure via 3GPP access. Even in such a case, in Chapters 4.1 to 4.4 above, "3GPP access" is replaced with "non-3GPP access", and "base station equipment_110" is replaced with "base station equipment_120 and N3IWF_240" or "TNAP and It can be applied by replacing it with "TNGF".

[5. Second Embodiment]
In this embodiment, the MA PDU session and / or eATSSS for communicating using the ATSSS function when the UE is registered in different PLMNs (operator core networks) via 3GPP access and non-3GPP access. The procedure for establishing a PDU session for establishing an SA PDU session for performing communication using a function will be described with reference to FIGS. 7 and 8.

Also, the UE may start the PDU session establishment procedure if it supports the ATSSS function and / or the eATSSS function. Further, when the UE supporting the ATSSS function requests communication by the ATSSS function, the PDU session establishment procedure may be started. Further, when the UE supporting the eATSSS function requests communication by the eATSSS function, the PDU session establishment procedure may be started. Further, when the UE supporting the ATSSS function and the eATSSS function requests the communication by the ATSSS function and / or the communication by the eATSSS function, the PDU session establishment procedure may be started. If the user has previously set the UE that supports the ATSSS function and / or the eATSSS function to communicate using the ATSSS function and / or the eATSSS function, the UE starts the PDU session establishment procedure. Good. In addition, the UE is the information stored in advance in the UE and / or the information received in advance from the access network, and / or the information received in advance from the core network (information received in procedures such as registration procedures, and information received in advance. / Or the PDU session establishment procedure may be started based on (including URSP rules, etc. received in advance from the PCF).

[5.1. 3 PDU session establishment procedure via 3GPP access]
Next, the PDU session establishment procedure executed via 3GPP access will be described with reference to FIG. Since the contents described in Chapter 4.1 can be applied as they are to this chapter, the explanation of this chapter is omitted.

Regarding the behavior of each device after the procedure (A) in Fig. 7 is completed normally, "when the establishment of the MA PDU session is permitted and / or user plane resources via 3GPP access in the MA PDU session" When the establishment of SATSSS function is permitted and / or when communication by the ATSSS function is permitted, described in Chapter 5.2, and when the establishment of SA PDU session for communication using the eATSSS function is permitted. , And / or when the establishment of userplane resources via 3GPP access is permitted, and / or when communication by the eATSSS function is permitted ”is explained in Chapter 5.3.

The procedure for rejecting the UE request will be explained in Chapter 5.4.

[5.2. When the establishment of MA PDU session for communication by ATSSS function is permitted]
Then, in Chapter 5.1, if the SMF and / or PCF allows the establishment of MA PDU sessions, and / or if the establishment of user plane resources via 3GPP access in MA PDU sessions, and / Alternatively, if communication by the ATSSS function is permitted, each device including the UE will perform the procedure shown in Fig. 8 (PDU session establishment procedure via non-3GPP access) in order to establish user plane resources via non-3GPP access. ) May start. In this case, it is not necessary to execute (B) in FIG. The procedure shown in FIG. 8 will be described below.

First, the UE that received the NAS message on the S716 has established a MAPDU session via 3GPP access and non-3GPP access, and / or a userplane via 3GPP access in the MAPDU session, as described above. It may be in a state of recognizing that resources have been established. That is, each device including the UE may be in a state in which a MAPDU session using userplane resources via 3GPP access and non-3GPP access has been established. In other words, each device including the UE may be in a state where it can communicate with the DN using a MAPDU session composed of userplane resources via 3GPP access.

First, the UE starts the PDU session establishment procedure by sending a NAS message containing the N1SM container including the PDU session establishment request message to the AMF via the access network (S800). The NAS message is, for example, a message transmitted via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message. The PDU session establishment request message was established for sending and receiving NAS messages between the UE and AMF by, for example, performing a registration procedure via non-3GPP access before this procedure. It may be sent to AMF using IPsec SA.

Here, the access network is non-3GPP access. Further, as described above, non-3GPP access includes Untrusted non-3GPP access and Trusted non-3GPP access, but here, the case of Untrusted non-3GPP access will be described as an example. That is, the UE sends a NAS message to the AMF via the base station device_120 included in the non-3GPP access.

In addition, the UE sends the PDU session establishment request message and / or the N1SM container and / or the NAS message by including at least one of the identification information 1 to 9 and 11 so that the UE can send the message. The request can be notified to the network side.

Here, the identification information of Chapters 1 to 9 and 11 may be as described in Chapter 3.2.

The first identification information is the DNN that identifies the DN to which the MA PDU session is connected. This first identification information is preferably the same as the first identification information and / or the 21st identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that this second identification information is the same as the second identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that this third identification information is the same as the third identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that this fourth identification information is the same as the fourth identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

The UE preferably supports at least one of the functions indicated by the second to fourth identification information, and if the function is supported, the identification information supports the function. It is preferable to show.

The fifth identification information is the PDU session ID for identifying the MA PDU session. This fifth identification information is preferably the same as the fifth identification information and / or the 25th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. This is because this procedure was performed to establish user plane resources via non-3GPP access that make up the MA PDU session established in the PDU session establishment procedure performed via 3GPP access. It may be because it is a procedure. That is, it may be because the MA PDU sessions are the same.

The sixth identification information is the PDU session type of the MA PDU session. This sixth identification information is preferably the same as the sixth identification information and / or the 26th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access.

The seventh identification information is the SSC mode required by the UE for the MAPDU session. This 7th identification information may be the same as or different from the 7th identification information and / or the 27th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. ..

Also, the eighth identification information is one or more S-NSSAI required by the UE. The eighth identification information is the Allowed NSSAI contained in the Registration Accept message in the Registration procedure executed before the start of this procedure, and both access (3GPP access and non-3GPP) by the network. It may be one or more S-NSSAIs allowed for access). This eighth identification information may be the same as or different from the eighth identification information and / or the 28th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. ..

Further, the ninth identification information may indicate that communication by the ATSSS function is requested. This ninth identification information may indicate that communication by the ATSSS function is required.

Further, the ninth identification information may be information indicating that the establishment of the MAPDU session (for the ATSSS function) is requested and / or information indicating that communication by the ATSSS function is requested. This ninth identification information may be a request type. Further, the ninth identification information may be information indicating that the establishment of user plane resources is requested via the non-3GPP access constituting the MAPDU session. This ninth identification information may be a request type. That is, the request type, which is the ninth identification information, requests the establishment of a MA PDU session (for the ATSSS function) and / or requests communication by the ATSSS function, and / or MA. It may indicate that it requires the establishment of userplane resources via the non-3GPP access that makes up the PDU session. For example, when requesting the establishment of a MAPDU session (for the ATSSS function) and / or when requesting communication with the eATSSS function, and / or userplane resources via non-3GPP access that constitutes the MAPDU session. When requesting the establishment of, the request type, which is the ninth identification information, may indicate MAPDUrequest.

In addition, regarding the identification information of the first to 9th and 11th, the UE has a control message of a layer lower than the NAS layer (for example, RRC layer, MAC layer, RLC layer, PDCP layer) and a layer higher than the NAS layer (trans). It may be included in the control message of the port layer, session layer, presentation layer, application layer) and sent.

The identification information of Nos. 1 to 9 and 11 in this PDU session establishment procedure is the same as the identification information of Nos. 1 to 9 and 11 in the previous PDU session establishment procedure (PDU session establishment procedure executed via 3GPP access). If they are the same, the UE does not have to transmit the identification information of the first to ninth and eleventh in this PDU session establishment procedure.

Next, when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the contents of the information (message, container, information) contained in the NAS message.

Here, the AMF is MA if the UE is registered via both accesses, but the S-NSSAI (8th identification) received from the UE is not allowed for both accesses. Requests to establish userplane resources via non-3GPP access that make up a PDU session may be rejected. In addition, AMF may reject the request to establish userplane resources via non-3GPP access that constitutes the MAPDU session if it does not support the ATSSS function.

Here, the fact that the UE is registered via both accesses means that the UE is registered in the network via 3GPP access and the UE is registered in the network via non-3GPP access. May mean.

Also, if S-NSSAI is not allowed for both accesses, then the connection to the network via 3GPP access is not allowed and the connection to the network via non-3GPP access is allowed. It may mean S-NSSAI that has not been done.

Further, when rejecting the request for establishing user plane resources via the non-3GPP access constituting the MAPDU session, each device may skip, that is, cancel the step after S802.

Also, when rejecting the request to establish userplane resources via the non-3GPP access that constitutes the MAPDU session, AMF rejects the request to establish userplane resources via the non-3GPP access that constitutes the MAPDU session. A NAS message containing information indicating that it should be sent may be sent to the UE. At this time, the AMF does not need to send at least a part of the information (message, container, information) included in the NAS message received from the UE to the SMF. In addition, the UE may detect that this procedure has not been completed normally or that this procedure has been completed abnormally by receiving this NAS message from AMF.

Also, when rejecting a request to establish userplane resources via non-3GPP access that constitutes a MAPDU session, AMF tells SMF userplaneresources via non-3GPP access that constitutes a MAPDU session. The SMF may send a NAS message containing an N1 SM container containing a PDU session establishment refusal message to the UE by sending information indicating that it rejects the establishment request. At this time, the PDU session establishment refusal message and / or the N1SM container and / or NAS message contains information indicating that the user plane resources establishment request via the non-3GPP access constituting the MAPDU session is rejected. May be included. In addition, the UE received a PDU session establishment refusal message and / or N1SM container and / or NAS message from the SMF, and this procedure was not completed normally, or this procedure was completed abnormally. You may detect that you have done so.

Next, AMF selects SMF as the transfer destination of at least a part of the information (messages, containers, information) contained in the NAS message received from the UE (S802). In addition, AMF includes information (messages, containers, information) contained in NAS messages, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or. The transfer destination SMF may be selected based on the network status and / or the user's registration information and / or the context held by the AMF. The AMF may also select an SMF that supports the ATSSS function and / or the eATSSS function. Here, it is assumed that SMF_220 that supports the ATSSS function and / or the eATSSS function is selected.

Next, the AMF transmits at least a part of the information (message, container, information) contained in the NAS message received from the UE to the selected SMF, for example, via the N11 interface (S804). The AMF may also send information to the SMF indicating that the UE is registered for both accesses.

Next, when the SMF receives the information (message, container, information) transmitted from the AMF, the UE requests and / or the content of the information (message, container, information) received from the AMF. Can be recognized.

Here, the SMF may determine the first condition. Further, the first condition determination may be for determining whether or not to accept the UE request. Further, in the first condition determination, the SMF determines whether the first condition determination is true or false. Further, if the SMF determines that the first condition determination is true, the procedure (A) in FIG. 8 may be started, and if the first condition determination is determined to be false, the procedure for rejecting the UE request. May start. The procedure for rejecting a UE request is described in Chapter 5.4.

The first condition determination is information received from AMF (messages, containers, information) and / or subscriber information (subscription information), and / or network capability information, and / or UE policy, and /. Alternatively, it may be executed based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the SMF.

For example, if the network permits the UE request, the first condition determination may be determined to be true, and if the UE request is not permitted by the network, the first condition determination may be determined to be false. Also, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the first condition determination may be determined to be true, and the functions required by the UE are supported. If not, the first condition determination may be determined to be false. Further, when the transmitted / received identification information is permitted, the first condition determination may be determined to be true, and when the transmitted / received identification information is not permitted, the first condition determination may be determined to be false.

Also, when the network allows the establishment of MAPDU sessions and / or when the establishment of userplane resources via non-3GPP access in MAPDU sessions is permitted, and / or when communication by the ATSSS function is permitted. May determine that the first condition determination is true. Also, if the network does not allow the establishment of MAPDU sessions and / or the establishment of userplane resources via non-3GPP access in MAPDU sessions, and / or does not allow communication by the ATSSS function. May determine that the first condition determination is false.

The condition for determining the authenticity of the first condition determination is not limited to the above-mentioned condition.

Next, each step of the procedure (A) in Fig. 8 will be explained.

First, SMF may select PCF. For example, the SMF may select an appropriate PCF based on the received identification information. For example, the SMF may select a PCF that supports the ATSSS function and / or the eATSSS function. Also, for example, if SMF detects that this procedure has been executed to establish userplane resources via non-3GPP access that constitutes the MAPDU session used for communication by its ATSSS function, You may select a PCF that has already been selected. Here, it is assumed that PCF_250 that supports the ATSSS function and / or the eATSSS function is selected.

Next, the SMF may send at least a part of the information (messages, containers, information) received from the AMF to the PCF (S806).

In addition, the SMF decides to allow the establishment of a MAPDU session for communication using the ATSSS function, and / or to allow the establishment of userplane resources via non-3GPP access in the MAPDU session. And / or if it decides to allow communication by the ATSSS function, the SMF may send additional information to the PCF. Here, as additional information, "information indicating that the establishment of the MA PDU session for communication using the ATSSS function is permitted" and / or "user plane via non-3GPP access in the MA PDU session". Includes "information indicating that the establishment of resources is permitted" and / or "permission of communication by the ATSSS function" and / or "access type corresponding to the established MA PDU session and / or user plane resources". You can do it. Here, the access type may indicate non-3GPP access.

Although the above judgment is described as being made by SMF, it may be made by PCF. That is, the SMF and / or the PCF may make the above judgment. If the SMF does not make the above decision, the SMF may not send the above additional information to the PCF.

Next, when the PCF receives the information (message, container, information) sent from the SMF, it can recognize the contents.

The PCF is based on the information received from the SMF (messages, containers, information) and / or the UE policy, and / or the operator policy, and / or the subscriber information (subscription information), etc., as described above in the SMF. A judgment similar to the judgment may be made.

If the PCF makes the above judgment, the PCF may transmit to the SMF the above additional information described as being transmitted from the SMF to the PCF.

Further, when the PCF detects that the above judgment is made in the SMF, it is not necessary to make this judgment (may be skipped).

Also, if the SMF and / or PCF allows the establishment of a MAPDU session for communication using the ATSSS function, and / or the establishment of userplane resources via non-3GPP access in the MAPDU session is permitted. If so, and / or if communication by the ATSSS function is permitted, the PCF may generate a second PCC rule or PCC rule.

If the second PCC rule or PCC rule generated in the PDU session establishment procedure via 3GPP access includes a distribution rule for userplane resources via non-3GPP access, the PCF will use this second PCF rule. PCC rules or PCC rules need not be generated. In this case, it is not necessary to send a second PCC rule or PCC rule to the SMF.

Also, if the second PCC rule or PCC rule generated in the PDU session establishment procedure via 3GPP access does not include a distribution rule for userplane resources via non-3GPP access, non-3GPP access. A second PCC rule or PCC rule may be generated that includes a distribution rule for userplane resources via.

In addition, if the PCF does not generate a second PCC rule or PCC rule in the PDU session establishment procedure via 3GPP access, in this procedure, the distribution rule for userplane resources via 3GPP access and 3GPP A second PCC rule or PCC rule may be generated that includes a distribution rule for userplane resources via access.

Then, when the PCF generates the second PCC rule, the generated PCC rule may be sent to the SMF.

Note that the PCF may generate the second PCC rule as the above-mentioned PCC rule. That is, the PCC rule may be the same as the second PCC rule. The PCF may then send the generated PCC rules to the SMF.

Next, when the SMF receives the information transmitted from the PCF, it can recognize the contents of the information.

Then, when the SMF receives the second PCC rule from the PCF, the SMF may generate the second ATSSS rule (30th identification information) and the second N4 rule from the second PCC rule. In addition, the SMF may manage (that is, map) the second PCC rule, the second ATSSS rule, and the second N4 rule in association with each other.

When the SMF receives the PCC rule instead of the second PCC rule from the PCF, the SMF may generate the ATSSS rule (30th identification information) and the N4 rule from the PCC rule. In this case, the ATSSS rule may be the same as the second ATSSS rule, and the N4 rule may be the same as the second N4 rule. In addition, the SMF may manage (that is, map) the PCC rule, the ATSSS rule, and the N4 rule in association with each other.

Next, the SMF selects the UPF for the MAPDU session and sends an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S808).

Further, when the SMF receives the second PCC rule from the PCF, the SMF may include the second N4 rule in the N4 session establishment request message. Further, when the SMF receives the PCC rule from the PCF, the SMF may include the N4 rule in the N4 session establishment request message.

Here, SMF refers to information received from AMF (messages, containers, information) and / or information received from PCF and / or subscriber information, and / or network capability information, and / or UE policy. One or more UPFs may be selected based on and / or operator policy and / or network status and / or user registration information and / or context held by the SMF. Also, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF.

Also, if the SMF and / or PCF allows the establishment of a MAPDU session for communication using the ATSSS function, and / or the establishment of userplane resources via non-3GPP access in the MAPDU session is permitted. If so, and / or if communication by the ATSSS function is permitted, the SMF may select a UPF that supports the ATSSS function.

In addition, the SMF may select the UPF if it has already been selected in the PDU session establishment procedure executed via 3GPP access.

Here, it is assumed that UPF_230 that supports the ATSSS function and / or the eATSSS function is selected.

Next, when the UPF receives the N4 session establishment request message (S808), the UPF can recognize the content of the information received from the SMF.

Further, when the UPF receives the second N4 rule or the N4 rule from the SMF, the UPF may be set to operate according to the received N4 rule.

That is, when the UPF receives the second N4 rule, the downlink traffic in the MA PDU session used for communication by the ATSSS function is non in the MA PDU session that is going to be established by this procedure (PDU session establishment procedure). -3 You may set the user plane resources via GPP access to operate according to the second N4 rule. In addition, when the UPF receives the second N4 rule, it will use userplane resources via 3GPP access and userplane via non-3GPP access for downlink traffic in the MAPDU session used for communication by the ATSSS function. You may set resources to operate according to the second N4 rule. Further, when the UPF receives an N4 rule having the same contents as the second N4 rule, the UPF may make the same settings as described above.

Further, the UPF may send an N4 session establishment response message to the SMF, for example, via the N4 interface, based on the reception of the N4 session establishment request message and / or the completion of the above settings (S810). This N4 session establishment response message may be sent including information indicating that the above settings have been completed.

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

The SMF then receives the PDU session establishment request message and / or the UPF selection and / or receives the N4 session establishment response message, for example, via the N11 interface, the N1 SM container, and / or N2 SM information and / or PDU session ID (25th identification information) is sent to AMF (S812). Here, the N1SM container may include a PDU session establishment acceptance message, and further, the PDU session establishment acceptance message includes an ATSSS container IE (Information Element) and / or a new ATSSS container IE. Good.

Next, the AMF receives the N1 SM container and / or N2 SM information and / or the PDU session ID (25th identification information).

Then, when user plane resources are established via non-3GPP access (untrusted non-3GPP access), AMF may send an N2 PDU session request message to N3IWF (S814). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. In addition, the NAS message may include a PDU session ID (25th identification information) and / or an N1 SM container. When user plane resources are established via Trusted non-3GPP access, AMF may send an N2 PDU session request message to TNGF and / or TNAP.

Next, N3IWF executes the procedure for establishing IPsec child SA (security association) with the UE via the access network (S816).

Specifically, N3IWF sends an IKE Create_Child_SA request message to the UE in accordance with the IKEv2 standard described in RFC 7296 in order to establish IPsec Child SA for user plane resources via non-3GPP access. Here, the IKE Create_Child_SA request message may indicate that the requested IPsec Child SA operates in tunnel mode. Also, the IKE Create_Child_SA request message may include the PDU session ID associated with this Child SA. In other words, the IPsec Child SA may be associated with the PDU session ID of a MA PDU session that includes user plane resources via non-3GPP access.

Next, when the UE accepts IPsec Child SA, it sends an IKE Create_Child_SA response message to N3IWF.

From the above, IPsec Child SA is established between UE and N3IWF.

After the IPsec Child SA is established, the N3IWF can send a NAS message including a PDU session establishment acceptance message to the UE via the base station device_120. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

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

Here, the SMF and / or AMF are the ATSSS container IE and / or the new ATSSS container IE, and / or the PDU session establishment acceptance message, and / or the N1 SM container, and / or the PDU session ID (25th identification). Information) and / or NAS message and / or N2SM information and / or N2PDU session request message indicates that at least part of the UE request by the PDU session establishment request message has been accepted. You may.

Also, if the SMF and / or PCF allows the establishment of a MAPDU session for communication using the ATSSS function, and / or the establishment of userplane resources via non-3GPP access in the MAPDU session is permitted. If so, and / or if communication by the ATSSS function is permitted, the SMF and / or AMF will use the ATSSS container IE and / or the new ATSSS container IE, and / or the PDU session establishment acceptance message, and / or N1. The SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message may include at least one of the 21st to 30th and 32nd identification information.

Here, the identification information of Chapters 21 to 30 and 32 may be as described in Chapter 3.2.

Here, the 21st identification information is a DNN that identifies the DN to which the MA PDU session is connected. The 21st identification information is preferably the same as the 1st identification information and / or the 21st identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. Further, it is preferable that the 21st identification information is the same as the 1st identification information transmitted / received in the PDU session establishment procedure.

Further, it is preferable that the 22nd identification information is the same as the 22nd identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that the 23rd identification information is the same as the 23rd identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

Further, it is preferable that the 24th identification information is the same as the 24th identification information transmitted / received in the PDU session establishment procedure executed via 3GPP access.

In addition, the network preferably supports at least one of the functions indicated by the 22nd to 24th identification information, and if it supports the function, the identification information supports the function. It is preferable to show.

Further, the 25th identification information may be a PDU session ID that identifies the MA PDU session. This 25th identification information is preferably the same as the 5th identification information and / or the 25th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. Further, the 25th identification information may be the same as the 5th identification information transmitted / received in the PDU session establishment procedure.

Further, the 26th identification information may be the PDU session type of the MA PDU session. The 26th identification information is preferably the same as the 6th identification information and / or the 26th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. Further, the 26th identification information may be the same as the 6th identification information transmitted / received in the PDU session establishment procedure.

Also, the 27th identification information may be in the SSC mode of the MAPDU session. This 27th identification information may be the same as or different from the 7th identification information and / or the 27th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. .. Further, the 27th identification information may be the same as or different from the 7th identification information transmitted / received in the PDU session establishment procedure.

Also, the 28th identification information may be one or more S-NSSAI. This 28th identification information may be the same as or different from the 8th identification information and / or the 28th identification information transmitted and received in the PDU session establishment procedure executed via 3GPP access. .. Further, the 28th identification information may be the same as or different from the 8th identification information transmitted / received in the PDU session establishment procedure.

In addition, the 29th identification information allows the establishment of MAPDU sessions for communication using the ATSSS function, and / or the establishment of userplane resources via non-3GPP access in MAPDU sessions. It may indicate that it has been done and / or that communication by the ATSSS function is permitted.

Also, the 30th identification information is the ATSSS rule or the second ATSSS rule. The steering function included in the thirtieth identification information is preferably a steering function supported by the UE, an ATSSS-LL function, or an MPTCP function.

In addition, SMF and / or AMF may use ATSSS container IE and / or new ATSSS container IE and / or PDU session establishment acceptance message and / or N1 SM container and / or NAS message, and / or N2 SM information. , And / or N2 PDU session request message includes at least one of the 21st to 30th and 32nd identification information to allow the establishment of a MA PDU session for communication using the ATSSS function. And / or an MA PDU session for communication using the ATSSS function was established, and / or the establishment of user plane resources via non-3GPP access in the MA PDU session was permitted. And / or notify the UE that userplane resources have been established via non-3GPP access in the MAPDU session and / or that communication by the ATSSS function has been permitted.

SMF and / or AMF can notify the UE and / or N3IWF and / or access network of the contents of these identification information by transmitting at least one of these identification information.

Note that SMF and / or AMF are ATSSS container IE and / or new ATSSS container IE and / or PDU session establishment acceptance message and / or N1 SM container and / or NAS message, and / or N2 SM information. , And / or which identification information is included in the N2 PDU session request message, each received identification information and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy. , And / or the state of the network, and / or the user's registration information, and / or the context held by the SMF and / or AMF, etc., may be selected and determined.

Next, when the UE receives the NAS message via, for example, the N1 interface (S816), the UE request by the PDU session establishment request message is accepted, and / or the information contained in the NAS message, etc. (message, Can recognize the contents of containers and information).

For example, when the UE receives a PDU session establishment acceptance message containing the ATSSS container IE containing the 30th identification information including the steering function indicating the ATSSS function, the UE receives the MA PDU session for communication using the ATSSS function. Established, and / or a MA PDU session for communication using the ATSSS function was established, and / or the establishment of user plane resources via non-3GPP access in the MA PDU session was permitted. It may be recognized that it has been done and / or that userplane resources have been established via non-3GPP access in the MAPDU session and / or that communication by the ATSSS function has been permitted.

Also, for example, if the UE requests the establishment of a MAPDU session (for the ATSSS function) or sends a ninth identification information indicating that it requests communication by the ATSSS function, the UE supports it. When the UE receives the PDU session establishment acceptance message containing the ATSSS container IE containing the 30th identification information including the steering function indicating the steering function, the UE establishes the MA PDU session for communication using the ATSSS function. Was allowed, and / or a MA PDU session was established for communication using the ATSSS function, and / or user plane resources were allowed to be established via non-3GPP access in the MA PDU session. You may recognize that and / or that userplane resources have been established via non-3GPP access in the MAPDU session and / or that communication by the ATSSS function has been permitted.

Also, for example, when the UE receives the 22nd identification information indicating that the network supports the ATSSS-LL function and / or the 23rd identification information indicating that the network supports the MPTCP function, the UE Is allowed to establish a MA PDU session for communication using the ATSSS function, and / or an MA PDU session for communication using the ATSSS function has been established, and / or in the MA PDU session. The establishment of userplane resources via non-3GPP access was permitted, and / or the establishment of userplane resources via non-3GPP access in the MAPDU session, and / or communication by the ATSSS function was permitted. You may recognize that it has been done.

Also, for example, the establishment of MAPDU sessions (for ATSSS functionality) was allowed, and / or the establishment of userplane resources via non-3GPP access in MAPDU sessions was allowed, and / or When the UE receives the 29th identification information indicating that communication using the ATSSS function is permitted, the UE is permitted to establish a MA PDU session for communication using the ATSSS function, and / Alternatively, an MA PDU session for communication using the ATSSS function has been established, and / or the establishment of user plane resources via non-3GPP access in the MA PDU session has been permitted, and / or the MA PDU session. It may be recognized that userplane resources have been established via non-3GPP access in, and / or communication by the ATSSS function has been permitted.

In addition, the UE is for identifying the MA PDU session by the 25th identification information (PDU session ID) received based on the contents of the information (message, container, information) contained in the NAS message. You may be able to identify that.

With the above, the procedure (A) in Fig. 8 may be completed normally.

At this stage, each device including the UE is in a state where user plane resources have been established via non-3GPP access. The UE may be ready to communicate with the DN using the already established MAPDU session consisting of userplane resources via 3GPP access and userplaneresources via non-3GPP access. .. That is, the UE may be in a state where communication by the ATSSS function is possible.

Although the case of Untrusted non-3GPP access has been described here as an example, it can also be applied to Trusted non-3GPP access by replacing the base station devices _120 and N3IWF_240 with TNAP and TNGF, respectively. ..

[5.3. When the establishment of SA PDU session for communication by eATSSS function is permitted]
Next, in Chapter 5.1, if the SMF and / or PCF allows the establishment of SA PDU sessions for communication using the eATSSS feature, and / or the establishment of user plane resources via 3GPP access. PDUs to establish an unestablished SA PDU session of the two SA PDU sessions used for communication with the eATSSS function and / or when communication with the eATSSS function is permitted. When instructed to perform a session establishment procedure, each device, including the UE, has the procedure in Figure 8 (second SA PDU session) to establish an SA PDU session (second SA PDU session) via non-3GPP access. PDU session establishment procedure via non-3GPP access) may be initiated. In this case, it is not necessary to execute (B) in FIG. The procedure shown in FIG. 8 will be described below. Since the contents described in Chapter 4.3 can be applied as they are to this chapter, the explanation of this chapter is omitted. The procedure for rejecting the UE request is explained in Chapter 5.4.

[5.4. If the UE request is rejected]
Next, in Chapters 5.1 and / or 5.3, the procedure for rejecting the UE's request, which is executed when the first condition determination is false, will be described. Since the contents described in Chapter 4.4 can be applied as they are to this chapter, the explanation of this chapter is omitted.

[5.5. Application example]
Chapter 5.1 described the case where each device including the UE executes the PDU session establishment procedure via 3GPP access.

And in Chapter 5.2, when SMF and / or PCF permits the establishment of MAPDU sessions and / or when the establishment of userplane resources via 3GPP access in MAPDU sessions is permitted in Chapter 5.1. And / or when communication by the ATSSS function is permitted, the procedure to be executed by each device including the UE after the procedure in Chapter 5.1 is explained.

Also, in Chapter 5.3, in Chapter 5.1, when the SMF and / or PCF permits the establishment of an SA PDU session for communication using the eATSSS function, and / or the establishment of user plane resources via 3GPP access. To establish an SA PDU session that has not yet been established, of the two SA PDU sessions used for communication with the eATSSS function and / or when communication with the eATSSS function is permitted. Described the procedure that each device, including the UE, performs after the procedure in Chapter 5.1 when instructed to perform the PDU session establishment procedure.

Also, in Chapter 5.4, we explained the procedure for rejecting the UE request that is executed when the first condition judgment is determined to be false in the procedure in Chapter 5.1 and / or the procedure in Chapter 5.3.

That is, in Chapters 5.1 to 5.4, each device, including the UE, first performs a PDU session establishment procedure via 3GPP access, and then, if necessary, a PDU session establishment procedure via non-3GPP access. The case of executing it was explained.

However, each device including the UE may first execute the PDU session establishment procedure via non-3GPP access, and then, if necessary, execute the PDU session establishment procedure via 3GPP access. Even in such a case, in Chapters 5.1 to 5.4 above, "3GPP access" is replaced with "non-3GPP access", and "base station device_110" is replaced with "base station device_120 and N3IWF_240" or "TNAP and". It can be applied by replacing it with "TNGF".

[6. Third Embodiment]
In this embodiment, when the UE is registered in PLMN (Operator's Core Network) via 3GPP access or non-3GPP access, MA PDU session and / or eATSSS for communication using the ATSSS function. The procedure for establishing a PDU session for establishing an SA PDU session for performing communication using a function will be described with reference to FIGS. 7 and 8.

Also, the UE may start the PDU session establishment procedure if it supports the ATSSS function and / or the eATSSS function. Further, when the UE supporting the ATSSS function requests communication by the ATSSS function, the PDU session establishment procedure may be started. Further, when the UE supporting the eATSSS function requests communication by the eATSSS function, the PDU session establishment procedure may be started. Further, when the UE supporting the ATSSS function and the eATSSS function requests the communication by the ATSSS function and / or the communication by the eATSSS function, the PDU session establishment procedure may be started. If the user has previously set the UE that supports the ATSSS function and / or the eATSSS function to communicate using the ATSSS function and / or the eATSSS function, the UE starts the PDU session establishment procedure. Good. In addition, the UE is the information stored in advance in the UE and / or the information received in advance from the access network, and / or the information received in advance from the core network (information received in procedures such as registration procedures, and information received in advance. / Or the PDU session establishment procedure may be started based on (including URSP rules, etc. received in advance from the PCF).

Here, consider the case where the UE is registered in the PLMN via 3GPP access and not registered in the PLMN via non-3GPP access.

[6.1. 3 PDU session establishment procedure via 3GPP access]
Next, since the UE is registered in the PLMN via 3GPP access, the PDU session establishment procedure executed via 3GPP access will be described with reference to FIG. 7. Since the contents described in Chapter 4.1 can be applied as they are to this chapter, the explanation of this chapter is omitted.

Regarding the behavior of each device after the procedure (A) in Fig. 7 is completed normally, "when the establishment of the MA PDU session is permitted and / or user plane resources via 3GPP access in the MA PDU session" When the establishment of SATSSS function is permitted and / or when communication by the ATSSS function is permitted, described in Chapter 6.3, and when the establishment of SA PDU session for communication using the eATSSS function is permitted. , And / or when the establishment of userplane resources via 3GPP access is permitted, and / or when communication by the eATSSS function is permitted ”is explained in Chapter 6.4.

Also, after the procedure in Figure 7 (A) in Chapter 6.1 is successfully completed, the UE is registered with the network via non-3GPP access before performing the procedure in Chapter 6.3 or the procedure in Chapter 6.4. You need to perform the procedure in Chapter 6.2 because you need to.

The procedure for rejecting the UE request will be explained in Chapter 6.5.

[6.2. Registration procedure]
Next, after the procedure in Figure 7 (A) in the procedure in Chapter 6.1 is successfully completed, the UE enters the network via non-3GPP access in order to perform the procedure in Chapter 6.3 or the procedure in Chapter 6.4. To register, each device, including the UE, performs a registration procedure via non-3GPP access. This registration procedure will be described with reference to FIG. Here, non-3GPP access will be described by taking the case of Untrusted non-3GPP access as an example. The registration procedure is also referred to as this procedure. The registration procedure is a procedure in 5GS. The registration procedure is a procedure for the UE to take the initiative in registering with the access network and / or the core network and / or the DN. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (RM-DEREGISTERED state). In addition, each device (particularly UE and AMF) can transition to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.

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

The UE may start the registration procedure when it has mobility across TAs. In other words, the UE may start the registration process when it moves to a TA that is different from the TA shown in the TA list it holds. In addition, the UE may initiate this procedure when the running timer expires. In addition, the UE may initiate the registration process when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. In addition, the UE may initiate the registration process if there is a change in the ability information and / or preferences regarding the establishment of the UE's PDU session. In addition, the UE may initiate the registration process on a regular basis. Further, the UE may start the registration procedure based on the completion of the UE setting update procedure. The UE is not limited to these, and can execute the registration procedure at any timing.

First, the UE may start the procedure for establishing an IPsec SA (security association) with N3IWF.

After that, the UE starts the registration procedure by sending a registration request message to AMF via 5GAN (S600) (S602) (S604). Specifically, the UE sends a registration request message to N3IWF via base station device_120 in 5GAN (S600). The registration request message is a NAS message.

Here, the UE can send the registration request message including the identification information of the 2nd to 4th, 8th, and 11th, but may include it in a control message different from these and send it.

Here, the identification information of Chapters 2 to 4, 8 and 11 may be as described in Chapter 3.2.

The UE can notify the network of the contents of these identification information by transmitting these identification information. These identifications may be included in these messages to indicate the UE's request.

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

When the N3IWF in 5GAN receives the registration request message, it selects the AMF to which the registration request message is transferred (S602). N3IWF in 5GAN can select AMF based on the information contained in the registration request message. Here, it is assumed that AMF_210 is selected. GNB_110 in 5GAN forwards the received registration request message to the selected AMF_210 (S604).

Upon receiving the registration request message, AMF_210 can recognize what the UE is requesting and / or the contents of various identification information contained in the registration request message.

AMF_210 can execute the second condition determination when it receives the registration request message. The second condition determination is for determining whether or not the network (or AMF) accepts the UE request. If the second condition determination is true, the AMF starts the procedure (A) in FIG.

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

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

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

AMF_210 selects SMF when the fourth condition determination is true and sends and receives SM messages to and from the selected SMF, whereas when the fourth condition determination is false, AMF_210 sends and receives SM messages. , Do not execute them (S606). Here, it is assumed that SMF_220 is selected. Further, even if the fourth condition determination is true, AMF_210 may cancel the procedure of (A) in FIG. 6 when receiving an SM message indicating rejection from SMF.

Note that AMF_210 can notify SMF_220 of the identification information received in the registration request message when sending and receiving SM messages to and from SMF_220 in S606. SMF_220 can acquire the identification information received from AMF_210 by sending and receiving SM messages to and from AMF.

Then, when IPsec SA is established between the UE and N3IWF, N3IWF notifies AMF that the UE context has been established.

The AMF_210 then receives the registration request message and / or sends and receives the SM message to and from the SMF_220 as a response message to the registration request message via the N3IWF and the base station device_120. Send a Registration accept message to (S608). For example, if the fourth condition determination is true, AMF_210 may send a registration acceptance message based on the receipt of the registration request message from the UE. Further, if the fourth condition determination is false, AMF_210 may send a registration acceptance message based on the completion of transmission / reception of the SM message to / from SMF_220. The registration acceptance message is a NAS message sent and received on the N1 interface.

AMF_210 may send the registration acceptance message including at least one of the 22nd to 24th, 28th, and 32nd identification information.

Here, the identification information of Chapters 22 to 24, 28, and 32 may be as described in Chapter 3.2.

In addition, AMF_210 can notify the UE of the contents of these identification information by transmitting at least one of these identification information. In addition, AMF_210 may indicate that the network supports each function by transmitting these identification information, or may indicate that the UE request has been accepted. Further, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.

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

In addition, AMF_210 can send the registration acceptance message including the SM message (for example, the PDU session establishment acceptance message), or send the SM message (for example, the PDU session establishment acceptance message) together with the registration acceptance message. However, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true. By performing such a transmission method, AMF can indicate that the procedure for SM has been accepted in the registration procedure.

In addition, AMF_210 also receives each identification information and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or. It may be shown that the UE request has been accepted by sending the registration acceptance message based on the context held by the AMF.

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

The UE receives the registration acceptance message via gNB_110 (S608). By receiving the registration acceptance message, the UE can recognize that the UE's request by the registration request message has been accepted and / or the content of each identification information contained in the registration acceptance message.

The UE can further send a registration completion message to AMF_210 via gNB_110 as a response message to the registration acceptance message (S610). When the UE receives an SM message such as a PDU session establishment acceptance message, the UE may send the registration completion message including the SM message such as the PDU session establishment completion message, or by including the SM message. , May indicate that the procedure for SM has been completed. Here, the registration completion message is a NAS message sent and received on the N1 interface, but is included in the RRC message and sent and received between the UE and gNB.

AMF_210 receives a registration completion message via gNB_110 (S610). In addition, each device completes the procedure (A) in FIG. 6 based on the transmission / reception of the registration acceptance message and / or the registration completion message.

When the procedure (A) in Fig. 6 is completed, the UE may be registered in the network via non-3GPP access.

Next, the case where the second condition discrimination is false will be described. The AMF_210 sends a Registration reject message to the UE via the N3IWF and the base station device_120 as a response message to the registration request message (S612). Here, the registration refusal message is a NAS message sent and received on the N1 interface.

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

The UE receives the registration refusal message via the N3IWF and the base station device_120 (S612). By receiving the registration refusal message, the UE can recognize that the UE request by the registration request message has been rejected and the contents of various identification information contained in the registration refusal message. Further, the UE may recognize that the request of the UE has been rejected if the registration refusal message is not received even after a predetermined period of time has elapsed after transmitting the registration request message. Each device completes this procedure based on sending and receiving a registration refusal message.

If the fourth condition determination is true in the procedure (A) of FIG. 6, AMF_210 may send a registration refusal message including an SM message indicating rejection such as a PDU session establishment refusal message. Alternatively, the SM message indicating refusal may be included to indicate that the procedure for SM has been rejected. In that case, the UE may further receive an SM message indicating rejection, such as a PDU session establishment refusal message, or may recognize that the procedure for SM has been rejected.

Each device completes the registration procedure based on the completion of the procedure (A) in Fig. 6. Each device may transition to the state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure (A) in FIG. Further, the transition of each device to each state may be performed based on the completion of the registration procedure, or may be performed based on the establishment of the PDU session.

Furthermore, each device may perform processing based on the information sent and received in the registration procedure based on the completion of the registration procedure. For example, when sending and receiving information indicating that a part of the UE's request has been rejected, the reason why the UE's request has been rejected may be recognized. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network or another cell.

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

[6.3. When the establishment of MA PDU session for communication by ATSSS function is permitted]
Then, in Chapter 6.1, if the SMF and / or PCF allows the establishment of MA PDU sessions, and / or if the establishment of user plane resources via 3GPP access in MA PDU sessions, and / Alternatively, if communication by the ATSSS function is permitted, each device including the UE that has completed the registration procedure in Chapter 6.2 will have the procedure shown in Figure 8 (non-) to establish user plane resources via non-3GPP access. 3 PDU session establishment procedure via GPP access) may be started. In this case, it is not necessary to execute (B) in FIG. The procedure shown in FIG. 8 will be described below. Since the contents described in Chapter 5.2 can be applied as they are to this chapter, the explanation of this chapter is omitted.

The procedure for rejecting the UE request will be explained in Chapter 6.5.

[6.4. When the establishment of SA PDU session for communication by eATSSS function is permitted]
Next, in Chapter 6.1, if the SMF and / or PCF allows the establishment of SA PDU sessions for communication using the eATSSS feature, and / or the establishment of user plane resources via 3GPP access. PDUs to establish an unestablished SA PDU session of the two SA PDU sessions used for communication with the eATSSS function and / or when communication with the eATSSS function is permitted. Each device, including the UE that completed the registration procedure in Chapter 6.2, establishes an SA PDU session (second SA PDU session) via non-3GPP access when instructed to perform the session establishment procedure. In order to do so, the procedure shown in FIG. 8 (PDU session establishment procedure via non-3GPP access) may be started. In this case, it is not necessary to execute (B) in FIG. The procedure shown in FIG. 8 will be described below. Since the contents described in Chapter 5.3 can be applied as they are to this chapter, the explanation of this chapter is omitted. The procedure for rejecting the UE request will be explained in Chapter 6.5.

[6.5. If the UE request is rejected]
Next, in Chapters 6.1 and / or 6.4, the procedure for rejecting the UE's request, which is executed when the first condition determination is false, will be described. Since the contents described in Chapter 4.4 can be applied as they are to this chapter, the explanation of this chapter is omitted.

[6.6. Application example]
Section 6.1 described the case where each device including the UE executes the PDU session establishment procedure via 3GPP access.

Then, in Chapter 6.2, we explained the case where each device including UE executes the registration procedure via non-3GPP access.

Also, in Chapter 6.3, when SMF and / or PCF permits the establishment of MAPDU sessions and / or when the establishment of userplane resources via 3GPP access in MAPDU sessions is permitted in Chapter 6.1. And / or when communication by the ATSSS function is permitted, the procedure to be executed by each device including the UE after the procedure in Chapter 6.2 is explained.

Also, in Chapter 6.4, in Chapter 6.1, when the SMF and / or PCF permits the establishment of an SA PDU session for communication using the eATSSS function, and / or the establishment of user plane resources via 3GPP access. To establish an SA PDU session that has not yet been established, of the two SA PDU sessions used for communication with the eATSSS function and / or when communication with the eATSSS function is permitted. Described the procedure that each device, including the UE, performs after the procedure in Chapter 6.2 when instructed to perform the PDU session establishment procedure.

Also, in Chapter 6.5, we explained the procedure for rejecting the UE request that is executed when the first condition judgment is determined to be false in the procedure in Chapter 6.1 and / or the procedure in Chapter 6.4.

That is, in Chapters 6.1 to 6.5, each device, including the UE, first performs a PDU session establishment procedure via 3GPP access, and then, if necessary, a PDU session establishment procedure via non-3GPP access. The case of executing it was explained.

However, each device including the UE may first execute the PDU session establishment procedure via non-3GPP access, and then, if necessary, execute the PDU session establishment procedure via 3GPP access. Even in such a case, in Chapters 6.1 to 6.5 above, "3GPP access" is replaced with "non-3GPP access", and "base station device_110" is replaced with "base station device_120 and N3IWF_240" or "TNAP and". It can be applied by replacing it with "TNGF".

[7. Others]
The program that operates in the device according to one aspect of the present invention is a program that controls a central processing unit (CPU) or the like to operate a computer so as to realize the functions of the embodiment according to one aspect of the present invention. Is also good. The program or information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, Hard Disk Drive (HDD), or other storage device system.

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

Further, each functional block or various features of the device used in the above-described embodiment can be implemented or executed in an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Further, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or a plurality of aspects of the present invention can use a new integrated circuit according to the technology.

The invention of the present application is not limited to the above-described embodiment. In the embodiment, an example of the device has been described, but the present invention is not limited to this, and the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device or a kitchen device. It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

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

1 Mobile communication system
10 UE
100 access network
102 Access network
110 Base station equipment
120 base station equipment
200 core network
210 AMF
220 SMF
230 UPF
240 N3IWF
250 PCF
300 DN

Claims (1)

1. It is a UE (User Equipment) equipped with a control unit and a transmission / reception unit.
   The transmitter / receiver
   UE support eATSSS feature for communicating using two SA PDU sessions consisting of a first SA PDU session via 3GPP access and a second SA PDU session via non-3GPP access. Send a PDU session establishment request message to the core network, including information indicating that the UE supports the ATSSS-LL function, and information indicating that the UE supports the MPTCP function.
   When a PDU session establishment acceptance message containing an ATSSS container IE containing an ATSSS rule including a steering function indicating the eATSSS function is received from the core network,
   The control unit recognizes that an SA PDU session for the eATSSS function has been established.

Images