6.4.1.2 UE-requested PDU session establishment procedure initiation

最新推荐文章于 2023-11-16 17:13:11 发布

缘于自然8

最新推荐文章于 2023-11-16 17:13:11 发布

阅读量1.5k

点赞数

分类专栏： 3GPP TS 24.501 V17.6.1 文章标签：网络协议

本文链接：https://blog.youkuaiyun.com/wszzr999/article/details/125518231

版权

3GPP TS 24.501 V17.6.1 专栏收录该内容

16 篇文章

订阅专栏

本文详细介绍了UE请求的PDU会话建立过程，涵盖了UE如何创建PDU会话建立请求消息，包括选择PDU会话ID、设置请求类型、携带S-NSSAI、IP版本能力等关键信息。还讨论了紧急PDU会话的处理、UE在不同接入间的会话切换、多播会话支持、以及各种协议配置选项的情况。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

6.4.1.2 UE-requested PDU session establishment procedure initiation

6.4.1.2 UE请求的PDU会话建立过程启动

modem日志：

PDU session establishment req

UL NAS transport

6.4.1.2 UE-requested PDU session establishment procedure initiation

6.4.1.2 UE请求的PDU会话建立过程启动

In order to initiate the UE-requested PDU session establishment procedure, the UE shall create a PDU SESSION ESTABLISHMENT REQUEST message.
NOTE 0: When IMS voice is available over either 3GPP access or non-3GPP access, the "voice centric" UE in 5GMM-REGISTERED state will receive a request from upper layers to establish the PDU session for IMS signalling, if the conditions for performing an initial registration with IMS indicated in 3GPP TS 24.229 [14] subclause U.3.1.2 are satisfied.

为了启动UE请求的PDU会话建立过程，UE应创建PDU会话建立请求消息。
注0：当IMS语音通过3GPP接入或非3GPP接入可用时，如果满足3GPP TS 24.229【14】子条款U.3.1.2中所述的向IMS执行初始注册的条件，则处于5GMM注册状态的“以语音为中心”的UE将收到上层的请求，以建立用于IMS信令的PDU会话。

If the UE requests to establish a new PDU session, the UE shall allocate a PDU session ID which is not currently being used by another PDU session over either 3GPP access or non-3GPP access. If the N5CW device supports 3GPP access and requests to establish a new PDU session via 3GPP access, the N5CW device shall refrain from allocating "PDU session identity value 15". If the TWIF acting on behalf of the N5CW device requests to establish a new PDU session, the TWIF acting on behalf of the N5CW device shall allocate the "PDU session identity value 15".
The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION ESTABLISHMENT REQUEST message to the allocated PTI value.
如果UE请求建立新的PDU会话，则UE应分配当前未被另一个PDU会话通过3GPP接入或非3GPP接入使用的PDU会话ID。如果N5CW设备支持3GPP接入并请求通过3GPP接入建立新的PDU会话，则N5CW设备应避免分配“PDU会话标识值15”。如果代表N5CW设备的TWIF请求建立新的PDU会话，则代表N5CW设备的TWIF应分配“PDU会话标识值15”。
UE应分配当前未使用的PTI值，并将PDU会话建立请求消息的PTI IE设置为分配的PTI值。

If the UE is registered for emergency services over the current access, the UE shall not request establishing a non-emergency PDU session over the current access. If the UE is registered for emergency services over the current access it shall not request establishing an emergency PDU session over the non-current access except if the request is for transferring the emergency PDU session to the non-current access. Before transferring an emergency PDU session from non-3GPP access to 3GPP access, or before transferring a PDN connection for emergency bearer services from untrusted non-3GPP access connected to EPC to 3GPP access, the UE shall check whether emergency services are supported in the NG-RAN cell (either an NR cell or an E-UTRA cell) on which the UE is camping.
NOTE 1: Transfer of an existing emergency PDU session or PDN connection for emergency bearer services between 3GPP access and non-3GPP access is needed e.g. if the UE determines that the current access is no longer available.
如果UE在当前接入上注册了紧急服务，则UE不得请求在当前接入上建立非紧急PDU会话。如果UE通过当前接入注册了紧急服务，则其不得请求通过非当前接入建立紧急PDU会话，除非该请求是为了将紧急PDU会话转移到非当前接入。在将紧急PDU会话从非3GPP接入转移到3GPP接入之前，或者在将紧急承载服务的PDN连接从连接到EPC的不受信任的非3GPP接入转移到3GPP接入之前，UE应检查UE所在的NG-RAN小区（NR小区或E-UTRA小区）中是否支持紧急服务。
注1：如果UE确定当前接入不再可用，则需要在3GPP接入和非3GPP接入之间转移用于紧急承载服务的现有紧急PDU会话或PDN连接。

If the UE requests to establish a new emergency PDU session, the UE shall include the PDU session type IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall set the IE to the IP version capability as specified in subclause 6.2.4.2.
If the UE requests to establish a new non-emergency PDU session with a DN, the UE shall include the PDU session type IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall set the IE to one of the following values: the IP version capability as specified in subclause 6.2.4.2, "Ethernet" or "Unstructured" based on the URSP rules or based on UE local configuration (see 3GPP TS 24.526 [19]).

NOTE 2: When the UE initiates the UE-requested PDU session establishment procedure to transfer an existing non-IP PDN connection in the EPS to the 5GS, the UE can use locally available information associated with the PDN connection to select the PDU session type between "Ethernet" and "Unstructured".
如果UE请求建立新的紧急PDU会话，则UE应在PDU会话建立请求消息中包括PDU会话类型IE，并应将IE设置为子条款6.2.4.2中规定的IP版本能力。
如果UE请求使和DN建立新的非紧急PDU会话，则UE应在PDU会话建立请求消息中包括PDU会话类型IE，并应将IE设置为以下值之一：子条款6.2.4.2中规定的IP版本能力，基于URSP规则或基于UE本地配置的“以太网”或“非结构化”（参见3GPP TS 24.526[19]）。
注2：当UE启动UE请求的PDU会话建立过程以将EPS中现有的非IP PDN连接转移到5GS时，UE可以使用与PDN连接相关联的本地可用信息来选择“以太网”和“非结构化”之间的PDU会话类型。

If the UE requests to establish a new non-emergency PDU session with a DN and the UE requests an SSC mode, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to the SSC mode. If the UE requests to establish a PDU session of "IPv4", "IPv6" or "IPv4v6" PDU session type, the UE shall either omit the SSC mode IE or set the SSC mode IE to "SSC mode 1", "SSC mode 2", or "SSC mode 3". If the UE requests to establish a PDU session of "Ethernet" or "Unstructured" PDU session type, the UE shall either omit the SSC mode IE or set the SSC mode IE to "SSC mode 1" or "SSC mode 2". If the UE requests transfer of an existing PDN connection in the EPS to the 5GS or the UE requests transfer of an existing PDN connection in an untrusted non-3GPP access connected to the EPC to the 5GS, the UE shall set the SSC mode IE to "SSC mode 1".

If the UE requests to establish a new emergency PDU session, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to "SSC mode 1".
如果UE请求与DN建立新的非紧急PDU会话，并且UE请求SSC模式，则UE应将PDU会话建立请求消息的SSC模式IE设置为SSC模式。如果UE请求建立“IPv4”、“IPv6”或“IPv4v6”PDU会话类型的PDU会话，则UE应省略SSC模式IE或将SSC模式IE设置为“SSC模式1”、“SSC模式2”或“SSC模式3”。如果UE请求建立“以太网”或“非结构化”PDU会话类型的PDU会话，则UE应省略SSC模式IE或将SSC模式IE设置为“SSC模式1”或“SSC模式2”。如果UE请求将EPS中的现有PDN连接转移到5GS，或者UE请求将连接到EPC的不受信任非3GPP接入中的现有PDN连接转移到5GS，则UE应将SSC模式IE设置为“SSC模式1”。
如果UE请求建立新的紧急PDU会话，则UE应将PDU会话建立请求消息的SSC模式IE设置为“SSC模式1”。

If the UE requests to establish a new PDU session with a DN, the UE may include the SM PDU DN request container IE with a DN-specific identity of the UE complying with network access identifier (NAI) format as specified in IETF RFC 7542 [37].
NOTE 3: The UE can avoid including both the SM PDU DN request container IE and the extended protocol configuration options IE with PAP/CHAP protocol identifiers in the PDU SESSION ESTABLISHMENT REQUEST message. The way to achieve this is implementation dependent.
如果UE请求与DN建立新的PDU会话，则UE可以包括SM PDU DN请求容器IE，该容器具有符合IETF RFC 7542[37]中规定的网络访问标识符（NAI）格式的UE的DN特定标识。
注3：UE可以避免在PDU会话建立请求消息中同时包括SM PDU DN请求容器IE和有PAP/CHAP协议标识符的扩展协议配置选项IE。实现这一点的方法取决于实现。

If the UE requests to establish a new PDU session associated with multicast sessions and the UE at the same time intends to join one or more MBS multicast sessions, the UE should include the Requested MBS container IE in the PDU SESSION ESTABLISHMENT REQUEST message. In that case, the UE shall set the MBS operation to "Join MBS session" and include the MBS session information(s) and shall set the Type of MBS session ID for each of the MBS session information to either "Temporary Mobile Group Identity (TMGI)" or "Source specific IP multicast address" depending on the type of the MBS session ID available in the UE. Then the remaining values of each of the MBS session information shall be set as following:

a)   if the Type of MBS session ID is set to "Temporary Mobile Group Identity (TMGI)", the UE shall set the MBS session ID to the TMGI; or
b)   if the Type of MBS session ID is set to "Source specific IP multicast address for IPv4" or " Source specific IP multicast address for IPv6", the UE shall set the Source IP address information and the Destination IP address information to the corresponding values.
NOTE 4:   The UE obtains the details of the MBS session ID(s) i.e. TMGI, Source IP address information and Destination IP address information as a pre-configuration in the UE or during the MBS service announcement, which is out of scope of this specification.
如果UE请求建立与多播会话相关联的新PDU会话，并且UE同时打算加入一个或多个MBS多播会话，则UE应在PDU会话建立请求消息中包括所请求的MBS容器IE。在这种情况下，UE应将MBS操作设置为“加入MBS会话”，并包括MBS会话信息，并且应根据UE中可用的MBS会话ID的类型，将每个MBS会话信息的MBS会话ID的类型设置为“临时移动组标识（TMGI）”或“源特定IP多播地址”。然后，每个MBS会话信息的剩余值应设置如下：

a）如果MBS会话ID的类型设置为“临时移动组标识（TMGI）”，则UE应将MBS会话ID设置为TMGI；或
b）如果MBS会话ID的类型设置为“IPv4的源特定IP多播地址”或“IPv6的源特定IP多播地址”，则UE应将源IP地址信息和目标IP地址信息设置为相应的值。
注4：UE获取MBS会话ID的详细信息，即TMGI、源IP地址信息和目标IP地址信息，作为UE中的预配置或在MBS服务公告期间，这超出了本规范的范围。

The UE should set the RQoS bit to "Reflective QoS supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message if the UE supports reflective QoS and:

a)   the UE requests to establish a new PDU session of "IPv4", "IPv6", "IPv4v6" or "Ethernet" PDU session type;
b)   the UE requests to transfer an existing PDN connection in the EPS of "IPv4", "IPv6", "IPv4v6" or "Ethernet" PDN type or of "Non-IP" PDN type mapping to "Ethernet" PDU session type, to the 5GS; or
c)   the UE requests to transfer an existing PDN connection in an untrusted non-3GPP access connected to the EPC of "IPv4", "IPv6" or "IPv4v6" PDN type to the 5GS.
NOTE 5:   The determination to not request the usage of reflective QoS by the UE for a PDU session is implementation dependent.

如果UE支持反射QoS，则UE应在PDU会话建立请求消息的5GSM能力IE中将RQoS位设置为“反射QoS支持”，并且
a） UE请求建立“IPv4”、“IPv6”、“IPv4v6”或“Ethernet”PDU会话类型的新PDU会话；
b） UE请求将EPS中“IPv4”、“IPv6”、“IPv4v6”或“Ethernet”PDN类型或映射到“Ethernet”PDU会话类型的“非IP”PDN类型的现有PDN连接转移到5GS；或
c） UE请求将连接到“IPv4”、“IPv6”或“IPv4v6”PDN类型的EPC的不受信任的非3GPP接入中的现有PDN连接转移到5GS。
注5：不请求UE对PDU会话使用反射QoS的确定取决于实现。

The UE shall indicate the maximum number of packet filters that can be supported for the PDU session in the Maximum number of supported packet filters IE of the PDU SESSION ESTABLISHMENT REQUEST message if:
a) the UE requests to establish a new PDU session of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDU session type, and the UE can support more than 16 packet filters for this PDU session;

b) the UE requests to transfer an existing PDN connection in the EPS of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDN type or of "Non-IP" PDN type mapping to "Ethernet" PDU session type, to the 5GS and the UE can support more than 16 packet filters for this PDU session; or
c) the UE requests to transfer an existing PDN connection in an untrusted non-3GPP access connected to the EPC of "IPv4", "IPv6" or "IPv4v6" PDN type to the 5GS and the UE can support more than 16 packet filters for this PDU session.
在以下情况下，UE应在PDU会话建立请求消息的最大支持包过滤器数量IE中指示PDU会话可支持的最大包过滤器数量：
a） UE请求建立“IPv4”、“IPv6”、“IPv4v6”或“Ethernet”PDU会话类型的新PDU会话，UE可以支持该PDU会话的16个以上的包过滤器；
b） UE请求将“IPv4”、“IPv6”、“IPv4v6”或“Ethernet”PDN类型或映射到“Ethernet”PDU会话类型的“Non-IP”PDN类型的EPS中的现有PDN连接转移到5GS，并且UE可以为该PDU会话支持16个以上的包过滤器；或
c） UE请求将连接到“IPv4”、“IPv6”或“IPv4v6”PDN类型的EPC的不受信任的非3GPP接入中的现有PDN连接转移到5GS，并且UE可以为该PDU会话支持16个以上的包过滤器。

The UE shall include the Integrity protection maximum data rate IE in the PDU SESSION ESTABLISHMENT REQUEST message to indicate the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink.
UE应在PDU会话建立请求消息中包括完整性保护最大数据速率IE，以指示UE支持的上行链路用户面完整性保护的每个UE的最大数据速率，以及UE支持的下行链路用户面完整性保护的每个UE的最大数据速率。

The UE shall set the MH6-PDU bit to "Multi-homed IPv6 PDU session supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message if the UE supports multi-homed IPv6 PDU session and:
a) the UE requests to establish a new PDU session of "IPv6" or "IPv4v6" PDU session type; or.
b) the UE requests to transfer an existing PDN connection of "IPv6" or "IPv4v6" PDN type in the EPS or in an untrusted non-3GPP access connected to the EPC to the 5GS.
如果UE支持多宿IPv6 PDU会话，则UE应在PDU会话建立请求消息的5GSM能力IE中将MH6-PDU位设置为“支持多宿IPv6 PDU会话”，并且：
a） UE请求建立“IPv6”或“IPv4v6”PDU会话类型的新PDU会话；或
b） UE请求将EPS中的“IPv6”或“IPv4v6”PDN类型的现有PDN连接或连接到EPC的不受信任的非3GPP接入中的PDN连接转移到5GS。

The UE shall set the EPT-S1 bit to "Ethernet PDN type in S1 mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message if the UE supports Ethernet PDN type in S1 mode and requests "Ethernet" PDU session type.
如果UE支持S1模式下的以太网PDN类型并请求“以太网”PDU会话类型，则UE应在PDU会话建立请求消息的5GSM能力IE中将EPT-S1位设置为“支持S1模式下的以太网PDN类型”。

If the UE requests to establish a new PDU session as an always-on PDU session (e.g. because the PDU session is for time synchronization or TSC), the UE shall include the Always-on PDU session requested IE and set the value of the IE to "Always-on PDU session requested" in the PDU SESSION ESTABLISHMENT REQUEST message.
NOTE 6: Determining whether a PDU session is for time synchronization or TSC is UE implementation dependent.
如果UE请求将新PDU会话建立为永远在线PDU会话（例如，因为PDU会话用于时间同步或TSC），则UE应包括请求的永远在线PDU会话IE，并在PDU会话建立请求消息中将IE的值设置为“请求的永远在线PDU会话”。
注6：确定PDU会话是用于时间同步还是TSC取决于UE实现。

If the UE has an emergency PDU session, the UE shall not perform the UE-requested PDU session establishment procedure to establish another emergency PDU session. The UE may perform the UE-requested PDU session establishment procedure to transfer an existing emergency PDU session or an existing PDN connection for emergency services.
If:
a)   the UE requests to perform handover of an existing PDU session between 3GPP access and non-3GPP access;
b)   the UE requests to perform transfer an existing PDN connection in the EPS to the 5GS; or
c)   the UE requests to perform transfer an existing PDN connection in an untrusted non-3GPP access connected to the EPC to the 5GS;
the UE shall:

a) set the PDU session ID in the PDU SESSION ESTABLISHMENT REQUEST message and in the UL NAS TRANSPORT message to the stored PDU session ID corresponding to the PDN connection; and
b) set the S-NSSAI in the UL NAS TRANSPORT message to the stored S-NSSAI associated with the PDU session ID of a non-emergency PDU session. The UE shall not request to perform handover of an existing non-emergency PDU session between 3GPP access and non-3GPP access if the S-NSSAI is not included in the allowed NSSAI for the target access.
如果UE具有紧急PDU会话，则UE不应执行UE请求的PDU会话建立过程来建立另一个紧急PDU会话。UE可以执行UE请求的PDU会话建立过程，以转移现有紧急PDU会话或现有PDN连接以用于紧急服务。
如果：
a） UE请求在3GPP接入和非3GPP接入之间执行现有PDU会话的切换；
b） UE请求将EPS中现有的PDN连接转移到5GS；或
c） UE请求将连接到EPC的不可信非3GPP接入中的现有PDN连接转移到5GS；
UE应：
a）将PDU会话建立请求消息和UL NAS传输消息中的PDU会话ID设置为存储的PDN连接对应的PDU会话ID；和
b）将UL NAS传输消息中的S-NSSAI设置为与非紧急PDU会话的PDU会话ID关联的存储S-NSSAI。如果S-NSSAI未包含在目标接入的允许NSSAI中，则UE不得请求在3GPP接入和非3GPP接入之间执行现有非紧急PDU会话的切换。

If the N5CW device supports 3GPP access and requests to perform handover of an existing PDU session from non-3GPP access to 3GPP access, the N5CW device shall set the PDU session ID in the PDU SESSION ESTABLISHMENT REQUEST message and in the UL NAS TRANSPORT message to "PDU session identity value 15".
如果N5CW设备支持3GPP访问，并请求将现有PDU会话从非3GPP接入切换到3GPP接入，则N5CW设备应将PDU会话建立请求消息和UL NAS传输消息中的PDU会话ID设置为“PDU会话标识值15”。

If the UE is registered to a network which supports ATSSS and the UE requests to establish a new PDU session the UE may allow the network to upgrade the requested PDU session to an MA PDU session. In order to allow the network to upgrade the requested PDU session to an MA PDU session, the UE shall set "MA PDU session network upgrade is allowed" in the MA PDU session information IE and shall set the request type to "initial request" in the UL NAS TRANSPORT message. If the UE is registered to a network which does not support ATSSS, the UE shall not perform the procedure to allow the network to upgrade the requested PDU session to an MA PDU session.
如果UE注册到支持ATSS的网络，并且UE请求建立新的PDU会话，则UE可以允许网络将请求的PDU会话升级为MA PDU会话。为了允许网络将请求的PDU会话升级为MA PDU会话，UE应在MA PDU会话信息IE中设置“允许MA PDU会话网络升级”，并应在UL NAS传输消息中将请求类型设置为“初始请求”。如果UE注册到不支持ATSSS的网络，则UE不得执行允许网络将请求的PDU会话升级到MA PDU会话的过程。

If the UE is registered to a network which supports ATSSS, the UE may request to establish an MA PDU session. If the UE requests to establish an MA PDU session, the UE shall set the request type to "MA PDU request" in the UL NAS TRANSPORT message. If the UE is registered to a network which does not support ATSSS, the UE shall not request to establish an MA PDU session.
如果UE注册到支持atss的网络，则UE可以请求建立MA-PDU会话。如果UE请求建立MA PDU会话，则UE应在UL NAS传输消息中将请求类型设置为“MA PDU请求”。如果UE注册到不支持ATSSS的网络，则UE不得请求建立MA PDU会话。

When the UE is registered over both 3GPP access and non-3GPP access in the same PLMN and the UE requests to establish a new MA PDU session, the UE may provide an S-NSSAI in the UL NAS TRANSPORT message only if the S-NSSAI is included in the allowed NSSAIs of both accesses.
NOTE 7: If the UE requested DNN corresponds to an LADN DNN, the AMF does not forward the MA PDU session information IE to the SMF but sends the message back to the UE to inform of the unhandled request (see subclause 5.4.5.2.5).
当UE通过3GPP接入和非3GPP接入注册在同一PLMN中，并且UE请求建立新的MA PDU会话时，仅当S-NSSAI包括在两个接入的允许NSSAI中时，UE才可以在UL NAS传输消息中提供S-NSSAI。
注7：如果UE请求的DNN对应于LADN DNN，AMF不会将MA PDU会话信息IE转发给SMF，而是将消息发送回UE，以通知未处理的请求（见第5.4.5.2.5节）。

If the UE is registered to a network which supports ATSSS and the UE has already an MA PDU session established over one access, the UE may perform the UE-requested PDU session establishment procedure to establish user-plane resources over the other access for the MA PDU session as specified in subclause 4.22 of 3GPP TS 23.502 [9] and the S-NSSAI associated with the MA PDU session is included in the allowed NSSAI of the other access. If the UE establishes user-plane resources over the other access for the MA PDU session, the UE shall:
a)   set the request type to "MA PDU request" in the UL NAS TRANSPORT message;
b)   set the PDU session ID to the stored PDU session ID corresponding to the established MA PDU session in the PDU SESSION ESTABLISHMENT REQUEST message and in the UL NAS TRANSPORT message; and
c)   set the S-NSSAI in the UL NAS TRANSPORT message to the stored S-NSSAI associated with the PDU session ID.

如果UE注册到支持ATSSS的网络，并且UE已经通过一个接入建立了MA PDU会话，UE可以执行UE请求的PDU会话建立过程，以在3GPP TS 23.502【9】子条款4.22中规定的MA PDU会话的其他接入上建立用户面资源，并且与MA PDU会话相关联的S-NSSAI包括在其他接入的允许NSSAI中。如果UE通过MA PDU会话的其他接入上建立用户面资源，则UE应：
a）在UL NAS传输报文中将请求类型设置为“MA PDU请求”；
b）将PDU会话ID设置为与PDU会话建立请求消息和UL NAS传输消息中建立的MA PDU会话相对应的存储PDU会话ID；和
c）将UL NAS传输消息中的S-NSSAI设置为与PDU会话ID关联的存储S-NSSAI。

If the UE requests to establish a new MA PDU session or if the UE requests to establish a new PDU session and the UE allows the network to upgrade the requested PDU session to an MA PDU session:
a) if the UE supports ATSSS Low-Layer functionality with any steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501 [8], the UE shall set the ATSSS-ST bits to "ATSSS Low-Layer functionality with any steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message;
b) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501 [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message;

c) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501 [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; and
d) if a performance measurement function in the UE can perform access performance measurements using the QoS flow of the non-default QoS rule as specified in subclause 5.32.5 of 3GPP TS 23.501 [8], the UE shall set the APMQF bit to "Access performance measurements per QoS flow supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message.
如果UE请求建立新的MA PDU会话，或者如果UE请求建立新的PDU会话，并且UE允许网络将请求的PDU会话升级为MA PDU会话：
a）如果UE支持具有3GPP TS 23.501【8】子条款5.32.6中规定的任何转向模式的ATSSS低层功能，则UE应在PDU会话建立请求消息的5GSM能力IE中将ATSSS-ST位设置为“具有支持的任何转向模式的ATSSS低层功能”；

b）如果UE支持任何转向模式下的MPTCP功能，以及3GPP TS 23.501【8】子条款5.32.6中规定的仅支持主备转向模式下的ATSSS-LL功能，UE应在PDU会话建立请求消息的5GSM能力IE中将ATSSS-ST位设置为“支持任何转向模式的MPTCP功能和仅支持主备转向模式的ATSSS-LL功能”；
c）如果UE支持任何转向模式下的MPTCP功能和3GPP TS 23.501【8】子条款5.32.6中规定的任何转向模式下的ATSSS-LL功能，UE应在PDU会话建立请求消息的5GSM能力IE中将ATSSS-ST位设置为“支持任何转向模式的MPTCP功能和支持任何转向模式的ATSSS-LL功能”；和
d）如果UE中的性能测量功能可以使用3GPP TS 23.501【8】子条款5.32.5中规定的非默认QoS规则的QoS流执行访问性能测量，则UE应在PDU会话建立请求消息的5GSM能力IE中将APMQF位设置为“每个支持的QoS流的访问性能测量”。

If the UE requests to establish a new MA PDU session and the UE supports to establish a PDN connection as the user plane resource of an MA PDU session, the UE shall include the ATSSS request parameter in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message.
如果UE请求建立新的MA PDU会话，并且UE支持建立PDN连接作为MA PDU会话的用户平面资源，则UE应在PDU会话建立请求消息的扩展协议配置选项IE中包括ATSSS请求参数。

If the UE is registered to a network which does not support ATSSS and the UE has already an MA PDU session established over one access, the UE shall not attempt to establish user-plane resources for the MA PDU session over the network which does not support ATSSS as specified in subclause 4.22 of 3GPP TS 23.502 [9].
如果UE注册到不支持ATSS的网络，并且UE已经通过一个接入建立了MA PDU会话，则UE不得尝试通过不支持3GPP TS 23.502【9】4.22节中规定的ATSS的网络建立MA PDU会话的用户面资源。

If the UE supports 3GPP PS data off, except for the transfer of a PDU session from non-3GPP access to 3GPP access and except for the establishment of user plane resources on the other access for the MA PDU session, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include the 3GPP PS data off UE status. The UE behaves as described in subclause 6.2.10.
如果UE支持3GPP PS数据关闭，除了PDU会话从非3GPP接入转移到3GPP接入，以及除了在MA PDU会话的其他接入上建立用户面资源之外，UE应在PDU会话建立请求消息中包括扩展协议配置选项IE，并包括3GPP PS数据关闭UE状态。UE的行为如第6.2.10节所述。

If the UE supports Reliable Data Service, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include the Reliable Data Service request indicator. The UE behaves as described in subclause 6.2.15.
如果UE支持可靠数据服务，则UE应在PDU会话建立请求消息中包括扩展协议配置选项IE，并包括可靠数据服务请求指示符。UE的行为如第6.2.15节所述。

If the UE supports DNS over (D)TLS (see 3GPP TS 33.501 [24]), the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include DNS server security information indicator and optionally, if the UE wishes to indicate which security protocol type(s) are supported by the UE, it may include the DNS server security protocol support.
NOTE 8: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501 [24].
如果UE支持通过（D）TLS的DNS（参见3GPP TS 33.501[24]），则UE应在PDU会话建立请求消息中包括扩展协议配置选项IE，并包括DNS服务器安全信息指示符，并且可选地，如果UE希望指示UE支持哪种安全协议类型，则可包括DNS服务器安全协议支持。
注8:DNS over（D）TLS的支持基于3GPP TS 33.501【24】中规定的信息要求。

If:
a)   the PDU session type value of the PDU session type IE is set to "IPv4", "IPv6" or "IPv4v6";
b)   the UE indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and
c)   the network indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message;
the UE shall include the IP header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message.

如果：
a） PDU会话类型IE的PDU会话类型值设置为“IPv4”、“IPv6”或“IPv4v6”；
b） UE在注册请求消息的5GMM能力IE中表示“支持控制面CIoT 5GS优化”和“支持控制面CIoT 5GS优化的IP头压缩”；和
c）网络在注册接受消息的5GS网络支持特性IE中表示“支持控制面CIoT 5GS优化”和“支持控制面CIoT 5GS优化的IP头压缩”；
UE应在PDU会话建立请求消息中包括IP报头压缩配置IE。
If:
a)   the PDU session type value of the PDU session type IE is set to "Ethernet";
b)   the UE indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and
c)   the network indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message;

the UE shall include the Ethernet header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message.
如果：
a） PDU会话类型IE的PDU会话类型值设置为“Ethernet”；
b） UE在注册请求消息的5GMM能力IE中表示“支持控制面CIoT 5GS优化”和“支持控制面CIoT 5GS优化的以太网报头压缩”；和
c）网络在注册接受消息的5GS网络支持特性IE中表示“支持控制面CIoT 5GS优化”和“支持控制面CIoT 5GS优化的以太网报头压缩”；
UE应在PDU会话建立请求消息中包括以太网报头压缩配置IE。
If the UE supports transfer of port management information containers, the UE shall:
a) set the TPMIC bit to "Transfer of port management information containers supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message;

b)   if the UE requests to establish a PDU session of "Ethernet" PDU session type , include the DS-TT Ethernet port MAC address IE in the PDU SESSION ESTABLISHMENT REQUEST message and set its contents to the MAC address of the DS-TT Ethernet port used for the PDU session;
c)   if the UE-DS-TT residence time is available at the UE, include the UE-DS-TT residence time IE and set its contents to the UE-DS-TT residence time; and
d)   if a Port management information container is provided by the DS-TT, include the Port management information container IE in the PDU SESSION ESTABLISHMENT REQUEST message.
NOTE 9:   Only SSC mode 1 is supported for a PDU session which is for time synchronization or TSC.
如果UE支持端口管理信息容器的传输，则UE应：

a）在PDU会话建立请求消息的5GSM能力IE中，将TPMIC位设置为“支持的端口管理信息容器传输”；
b）如果UE请求建立“以太网”PDU会话类型的PDU会话，则在PDU会话建立请求消息中包括DS-TT以太网端口MAC地址IE，并将其内容设置为用于PDU会话的DS-TT以太网端口的MAC地址；
c）如果UE处有UE-DS-TT驻留时间，则包括UE-DS-TT驻留时间IE，并将其内容设置为UE-DS-TT驻留时间；和
d）如果DS-TT提供了端口管理信息容器，请在PDU会话建立请求消息中包含端口管理信息容器IE。
注9：用于时间同步或TSC的PDU会话仅支持SSC模式1。

If the UE supporting S1 mode supports receiving QoS rules with the length of two octets or QoS flow descriptions with the length of two octets via the Extended protocol configuration options IE, the UE shall include the QoS rules with the length of two octets support indicator or the QoS flow descriptions with the length of two octets support indicator, respectively, in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message.
如果支持S1模式的UE支持通过扩展协议配置选项IE接收长度为两个八位字节的QoS规则或长度为两个八位字节的QoS流描述，则UE应分别包括长度为两个八位字节支持指示符的QoS规则或长度为两个八位字节支持指示符的QoS流描述，在扩展协议配置选项中，即PDU会话建立请求消息中。

If:
-   the UE is operating in single-registration mode;
-   the UE supports local IP address in traffic flow aggregate description and TFT filter in S1 mode; and
-   the PDU session Type requested is different from "Unstructured".
the UE shall indicate the support of local address in TFT in S1 mode in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message.
如果：
-UE在单一注册模式下工作；
-UE支持业务流聚合描述中的本地IP地址和S1模式下的TFT过滤器；和
-请求的PDU会话类型不同于“非结构化”。
UE应在PDU会话建立请求消息中的扩展协议配置选项IE中指示对S1模式下TFT中本地地址的支持。

If the W-AGF acting on behalf of the FN-RG requests to establish a PDU session of "IPv6" or "IPv4v6" PDU session type, the W-AGF acting on behalf of the FN-RG may include in the PDU SESSION ESTABLISHMENT REQUEST message the Suggested interface identifier IE with the PDU session type value field set to "IPv6" and containing the interface identifier for the IPv6 link local address associated with the PDU session suggested to be allocated to the FN-RG.
如果代表FN-RG的W-AGF请求建立“IPv6”或“IPv4v6”PDU会话类型的PDU会话，代表FN-RG的W-AGF可在PDU会话建立请求消息中包括建议的接口标识符IE，其中PDU会话类型值字段设置为“IPv6”，并包含与建议分配给FN-RG的PDU会话相关联的IPv6链路本地地址的接口标识符。
If the UE supports provisioning of ECS configuration information to the EEC in the UE, then the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall include the ECS configuration information provisioning support indicator.
如果UE支持向UE中的EEC提供ECS配置信息，则UE应在PDU会话建立请求消息中包括扩展协议配置选项IE，并应包括ECS配置信息提供支持指示器。

If the UE supports receiving DNS server addresses in protocol configuration options, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and in the Extended protocol configuration options IE:
a)   if the UE requests to establish a PDU session of "IPv4" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv4 address request; and
b)   if the UE requests to establish a PDU session of "IPv6" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv6 address request.
如果UE支持在协议配置选项中接收DNS服务器地址，则UE应在PDU会话建立请求消息和扩展协议配置选项IE中包括扩展协议配置选项IE：
a）如果UE请求建立“IPv4”或“IPv4v6”PDU会话类型的PDU会话，则UE应包括DNS服务器IPv4地址请求；和
b）如果UE请求建立“IPv6”或“IPv4v6”PDU会话类型的PDU会话，则UE应包括DNS服务器IPv6地址请求。
If the UE supporting UAS services requests to establish a PDU session for C2 communication, the UE shall include the Service-level-AA container IE in the PDU SESSION ESTABLISHMENT REQUEST message. In the Service-level-AA container IE, the UE shall include:
a)   the service-level device ID with the value set to the CAA-level UAV ID of the UE; and
b)   if available, the service-level-AA payload with the value set to the C2 authorization payload and the service-level-AA payload type with the value set to "C2 authorization payload".
NOTE 10:   The C2 authorization payload in the service-level-AA payload can include the pairing information and the flight authorization information.
如果支持UAS服务的UE请求为C2通信建立PDU会话，则UE应在PDU会话建立请求消息中包含服务级别AA容器IE。在服务级别AA容器IE中，UE应包括：
a）将值设置为UE的CAA级UAV ID的服务级设备ID；和
b）如果可用，将值设置为C2授权有效载荷的服务级别AA有效载荷和将值设置为“C2授权有效载荷”的服务级别AA有效载荷类型。
注10：服务级别AA有效载荷中的C2授权有效载荷可包括配对信息和飞行授权信息。

If the UE supports the EAS rediscovery, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall include the EAS rediscovery support indication in the Extended protocol configuration options IE.
如果UE支持EAS重新发现，则UE应在PDU会话建立请求消息中包括扩展协议配置选项IE，并应在扩展协议配置选项IE中包括EAS重新发现支持指示。

If the UE needs to include a PDU session pair ID based on the matching URSP rule or UE local configuration, the UE shall include the PDU session pair ID IE in the PDU SESSION ESTABLISHMENT REQUEST message. If the UE needs to include an RSN based on the matching URSP rule or UE local configuration, the UE shall include the RSN IE in the PDU SESSION ESTABLISHMENT REQUEST message.
如果UE需要基于匹配的URSP规则或UE本地配置包括PDU会话对ID，则UE应在PDU会话建立请求消息中包括PDU会话对ID IE。如果UE需要基于匹配的URSP规则或UE本地配置包括RSN，则UE应在PDU会话建立请求消息中包括RSN IE。

If the UE is not registered for onboarding services in SNPN and needs PVS information, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include the PVS information request in the Extended protocol configuration options IE.
如果UE未在SNPN中注册登录服务，并且需要PVS信息，则UE应在PDU会话建立请求消息中包括扩展协议配置选项IE，并在扩展协议配置选项IE中包括PVS信息请求。

If the UE supports the EDC, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall include the EDC support indicator in the Extended protocol configuration options IE.
如果UE支持EDC，则UE应在PDU会话建立请求消息中包括扩展协议配置选项IE，并应在扩展协议配置选项IE中包括EDC支持指示器。

The UE shall transport:
a)   the PDU SESSION ESTABLISHMENT REQUEST message;
b)   the PDU session ID of the PDU session being established, being handed over, being transferred, or been established as an MA PDU session;
c)   if the request type is set to:
1)   "initial request" or "MA PDU request" and the UE determined to establish a new PDU session or an MA PDU session based on either a URSP rule including one or more S-NSSAIs in the URSP (see subclause 6.2.9) or UE local configuration, according to subclause 4.2.2 of 3GPP TS 24.526 [19]:
i)   in case of a non-roaming scenario, an S-NSSAI in the allowed NSSAI which corresponds to one of the S-NSSAI(s) in the matching URSP rule, if any, or else to the S-NSSAI(s) in the UE local configuration or in the default URSP rule, if any, according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526 [19]; or
ii)   in case of a roaming scenario:
A)   one of the mapped S-NSSAI(s) which corresponds to one of the S-NSSAI(s) in the matching URSP rule, if any, or else to the S-NSSAI(s) in the UE local configuration or in the default URSP rule, if any, according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526 [19]; and
B)   the S-NSSAI in the allowed NSSAI associated with the S-NSSAI in A); or
2)   "existing PDU session", an S-NSSAI, which is an S-NSSAI associated with the PDU session and (if available in roaming scenarios) a mapped S-NSSAI, with exception when S-NSSAI is not provided by the network in subclause 6.1.4.2;

d)   if the request type is set to:
1)   "initial request" or "MA PDU request" and the UE determined to establish a new PDU session or an MA PDU session based on either a URSP rule including one or more DNNs in the URSP (see subclause 6.2.9) or UE local configuration, according to subclause 4.2.2 of 3GPP TS 24.526 [19], a DNN which corresponds to one of the DNN(s) in the matching URSP rule, if any, or else to the DNN(s) in the UE local configuration or in the default URSP rule, if any, according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526 [19]; or
2)   "existing PDU session", a DNN which is a DNN associated with the PDU session;

e)   the request type which is set to:
1)   "initial request", if the UE is not registered for emergency services and the UE requests to establish a new non-emergency PDU session;
2)   "existing PDU session", if the UE is not registered for emergency services and the UE requests:
i)   handover of an existing non-emergency PDU session between 3GPP access and non-3GPP access;
ii)   transfer of an existing PDN connection for non-emergency bearer services in the EPS to the 5GS; or
iii)   transfer of an existing PDN connection for non-emergency bearer services in an untrusted non-3GPP access connected to the EPC to the 5GS;
3)   "initial emergency request", if the UE requests to establish a new emergency PDU session;
4)   "existing emergency PDU session", if the UE requests:
i)   handover of an existing emergency PDU session between 3GPP access and non-3GPP access;
ii)   transfer of an existing PDN connection for emergency bearer services in the EPS to the 5GS; or
iii)   transfer of an existing PDN connection for emergency bearer services in an untrusted non-3GPP access connected to the EPC to the 5GS; or
5)   "MA PDU request", if:
i)   the UE requests to establish an MA PDU session;
ii)   the UE requests to establish user plane resources over other access of an MA PDU session established over one access only; or
iii)   the UE performs inter-system change from S1 mode to N1 mode according to subclause 4.8.2.3.1 and requests transfer of a PDN connection which is a user plane resource of an MA PDU session; and
f)   the old PDU session ID which is the PDU session ID of the existing PDU session, if the UE initiates the UE-requested PDU session establishment procedure upon receiving the PDU SESSION MODIFICATION COMMAND messages with the 5GSM cause IE set to #39 "reactivation requested";
using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3580 (see example in figure 6.4.1.2.1).

UE应使用5.4.5节中规定的NAS传输过程传输，并且UE应启动计时器T3580（见图6.4.1.2.1中的示例）：
a） PDU会话建立请求消息；
b）正在建立、切换、转移或已建立为MA-PDU会话的PDU会话的PDU会话ID；
c）如果请求类型设置为：
1） “初始请求”或“MA PDU请求”，并且根据3GPP TS 24.526【19】的4.2.2节，UE确定基于在URSP中包括一个或多个S-NSSAI的URSP规则（参见6.2.96节）或UE本地配置建立一个新的PDU会话或MA PDU会话：
i）在非漫游场景下，根据3GPP TS 24.526【19】4.2.2节给出的条件，允许NSSAI中的S-NSSAI对应于匹配的URSP规则（如有）中的一个S-NSSAI，或UE本地配置或默认URSP规则（如有）中的S-NSSAI；或
ii）如果是漫游场景：
A）根据3GPP TS 24.526【19】4.2.2节给出的条件，映射的S-NSSAI中的一个对应于匹配的URSP规则中的一个S-NSSAI（如有），或者对应于UE本地配置中的S-NSSAI或默认的URSP规则中的S-NSSAI（如有）；并且
B）允许NSSAI中的S-NSSAI与A）中的S-NSSAI关联；或
2） “现有PDU会话”，是一个S-NSSAI，它是与PDU会话相关联的S-NSSAI，并且（如果在漫游场景中可用）是一个映射的S-NSSAI，除非网络在第6.1.4.2节中未提供S-NSSAI；

d）如果请求类型设置为：
1） “初始请求”或“MA PDU请求”，并且根据3GPP TS 24.526【19】第4.2.2节，UE根据URSP规则（包括URSP中的一个或多个DNN）（参见第6.2.9节）或UE本地配置，，确定建立新的PDU会话或MA PDU会话，DNN对应于匹配URSP规则中的一个DNN（如果有），或者根据3GPP TS 24.526【19】4.2.2节中给出的条件，或UE本地配置或默认URSP规则（如有）中的DNN；或
2） “现有PDU会话”，是与PDU会话相关联的DNN；
e）设置为的请求类型：
1） “初始请求”，如果UE未注册紧急服务，并且UE请求建立新的非紧急PDU会话；
2） “现有PDU会话”，如果UE未注册紧急服务，并且UE请求：
i）在3GPP接入和非3GPP接入之间切换现有的非紧急PDU会话；
ii）将EPS中用于非紧急承载服务的现有PDN连接转移到5GS；或
iii）将连接到EPC的不可信非3GPP接入中的非紧急承载服务的现有PDN连接转移到5GS；
3） “初始紧急请求”，如果UE请求建立新的紧急PDU会话；
4） “现有紧急PDU会话”，如果UE请求：
i）在3GPP接入和非3GPP接入之间切换现有的紧急PDU会话；
ii）将EPS中用于紧急承载服务的现有PDN连接转移到5GS；或
iii）将连接到EPC的不受信任非3GPP接入中用于紧急承载服务的现有PDN连接转移到5GS；或
5） “MA PDU请求”，如果：
i） UE请求建立MA-PDU会话；
ii）UE请求在仅通过一种接入建立的MA-PDU会话的其他接入上建立用户面资源；或
iii）UE根据4.8.2.3.1节执行从S1模式到N1模式的系统间改变，并请求传输作为MA PDU会话的用户面资源的PDN连接；和
f）旧PDU会话ID是现有PDU会话的PDU会话ID，如果UE在收到PDU会话修改命令消息时启动UE请求的PDU会话建立过程，5GSM cause IE设置为#39“reactivation requested”；
For bullet c) 1), if the matching URSP rule does not have an associated S-NSSAI, or if the UE does not have any matching URSP rule and there is no S-NSSAI in the UE local configuration or in the default URSP rule, the UE shall not provide any S-NSSAI in a PDU session establishment procedure.
对于项目符号c）1），如果匹配的URSP规则没有关联的S-NSSAI，或者如果UE没有任何匹配的URSP规则，并且UE本地配置或默认URSP规则中没有S-NSSAI，则UE不得在PDU会话建立过程中提供任何S-NSSAI。

For bullet d) 1), if the matching URSP rule does not have an associated DNN, or if the UE does not have any matching URSP rule and there is no DNN in the UE local configuration or in the default URSP rule and:
a) if the UE requests a connectivity to the default DNN for the S-NSSAI and the requested connectivity requires PAP/CHAP, the UE should provide a DNN in a PDU session establishment procedure; or
b) otherwise, the UE shall not provide any DNN in a PDU session establishment procedure.
对于项目符号d）1），如果匹配的URSP规则没有关联的DNN，或者如果UE没有任何匹配的URSP规则，并且UE本地配置或默认URSP规则中没有DNN，并且：
a）如果UE请求连接到S-NSSAI的默认DNN，并且请求的连接需要PAP/CHAP，则UE应在PDU会话建立过程中提供DNN；或
b）否则，UE不应在PDU会话建立过程中提供任何DNN。

If the request type is set to "initial emergency request" or "existing emergency PDU session" or the UE is registered for onboarding services in SNPN, neither DNN nor S-NSSAI is transported by the UE using the NAS transport procedure as specified in subclause 5.4.5.
如果请求类型设置为“初始紧急请求”或“现有紧急PDU会话”，或者UE在SNPN中注册了登船服务，则UE不会使用第5.4.5款规定的NAS传输程序传输DNN或S-NSSAI。

                  UE                                                             SMF

                               PDU SESSION ESTABLISHMENT REQUEST
         Start T3580  ------------------------------------------------------------->
		 
		                       PDU SESSION ESTABLISHMENT ACCEPT
		 Stop T3580   <-------------------------------------------------------------
		 
                                             
										 OR

								PDU SESSION ESTABLISHMENT REJECT		 
         Stop T3580   <-------------------------------------------------------------

Figure 6.4.1.2.1: UE-requested PDU session establishment procedure
图6.4.1.2.1:UE请求的PDU会话建立过程

Upon receipt of a PDU SESSION ESTABLISHMENT REQUEST message, a PDU session ID, optionally an S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI, optionally a DNN determined by the AMF, optionally a DNN selected by the network (if different from the DNN determined by the AMF), the request type, and optionally an old PDU session ID, the SMF checks whether connectivity with the requested DN can be established. If the requested DNN is not included, the SMF shall use the default DNN.
收到PDU会话建立请求消息后，PDU会话ID、与映射的S-NSSAI关联的S-NSSAI（如果在漫游场景中可用）、AMF确定的DNN、网络选择的DNN（如果与AMF确定的DNN不同）、请求类型和旧PDU会话ID，SMF检查是否可以建立与请求DN的连接。如果未包括请求的DNN，SMF应使用默认DNN。

If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session" and the PDU session authentication and authorization by the external DN is required due to local policy, the SMF shall check whether the PDU SESSION ESTABLISHMENT REQUEST message includes the SM PDU DN request container IE or the Service-level-AA container IE.
如果正在建立的PDU会话是非紧急PDU会话，则请求类型不要设置为“现有PDU会话”，并且由于本地策略，需要外部DN进行PDU会话身份验证和授权，SMF应检查PDU会话建立请求消息是否包括SM PDU DN请求容器IE或服务级别AA容器IE。

If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the SM PDU DN request container IE is included in the PDU SESSION ESTABLISHMENT REQUEST message, the PDU session authentication and authorization by the external DN is required due to local policy and user's subscription data, and:
a) the information for the PDU session authentication and authorization by the external DN in the SM PDU DN request container IE is compliant with the local policy and user's subscription data, the SMF shall proceed with the EAP Authentication procedure specified in 3GPP TS 33.501 [24] and refrain from accepting or rejecting the PDU SESSION ESTABLISHMENT REQUEST message until the EAP Authentication procedure finalizes; or
b) the information for the PDU session authentication and authorization by the external DN in the SM PDU DN request container IE is not compliant with the local policy and user's subscription data, the SMF shall consider it as an abnormal case and proceed as specified in subclause 6.4.1.7.
如果正在建立的PDU会话是非紧急PDU会话，则请求类型不要设置为“现有PDU会话”，SM PDU DN请求容器IE包含在PDU会话建立请求消息中，由于本地策略和用户订阅数据，需要外部DN进行PDU会话身份验证和授权，并且：
a） SM PDU DN请求容器IE中外部DN的PDU会话身份验证和授权信息符合本地策略和用户订阅数据，SMF应继续执行3GPP TS 33.501【24】中规定的EAP认证程序，并在EAP认证程序完成之前，避免接受或拒绝PDU会话建立请求消息；或
b） SM PDU DN请求容器IE中外部DN的PDU会话身份验证和授权信息不符合本地策略和用户订阅数据，SMF应将其视为异常情况，并按照第6.4.1.7节的规定进行处理。

If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the SM PDU DN request container IE is not included in the PDU SESSION ESTABLISHMENT REQUEST message and the PDU session authentication and authorization by the external DN is required due to local policy and user's subscription data, the SMF shall proceed with the EAP Authentication procedure specified in 3GPP TS 33.501 [24] and refrain from accepting or rejecting the PDU SESSION ESTABLISHMENT REQUEST message until the EAP Authentication procedure finalizes.
如果正在建立的PDU会话是非紧急PDU会话，则请求类型不要设置为“现有PDU会话”，SM PDU DN请求容器IE未包含在PDU会话建立请求消息中，并且由于本地策略和用户的订阅数据，需要外部DN进行PDU会话身份验证和授权，SMF应继续执行3GPP TS 33.501【24】中规定的EAP认证程序，并在EAP认证程序完成之前，避免接受或拒绝PDU会话建立请求消息。

If the SMF receives the old PDU session ID from the AMF and a PDU session exists for the old PDU session ID, the SMF shall consider that the request for the relocation of SSC mode 3 PDU session anchor with multiple PDU sessions as specified in 3GPP TS 23.502 [9] is accepted by the UE.
如果SMF从AMF接收到旧PDU会话ID，并且旧PDU会话ID存在一个PDU会话，则SMF应考虑UE接受3GPP TS 23.502[9]中规定的将SSC模式3 PDU会话锚重新定位到多个PDU会话的请求。

If the SMF receives the onboarding indication from the AMF, the SMF shall consider that the PDU session is established for onboarding services in SNPN.
如果SMF从AMF接收到登船指示，SMF应考虑为SNPN中的登船服务建立PDU会话。

If the UE has set the TPMIC bit to "Transfer of port management information containers supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message and has included a DS-TT Ethernet port MAC address IE (if the PDU session type is "Ethernet"), the Port management information container IE, and, optionally, the UE-DS-TT residence time IE in the PDU SESSION ESTABLISHMENT REQUEST message, the SMF shall operate as specified in 3GPP TS 23.502 [9] subclause 4.3.2.2.1.
如果UE已在PDU会话建立请求消息的5GSM能力IE中将TPMIC位设置为“支持的端口管理信息容器的传输”，并且已包括DS-TT以太网端口MAC地址IE（如果PDU会话类型为“Ethernet”），则端口管理信息容器IE，以及，可选地，UE-DS-TT驻留时间IE在PDU会话建立请求消息中，SMF应按照3GPP TS 23.502【9】4.3.2.2.1节的规定操作。

If requested by the upper layers the UE supporting UAS services initiates request to establish a PDU session for UAS services, the UE shall include the service-level device ID in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REQUEST message and set the value to the CAA-level UAV ID. The UE may include the service-level-AA server address in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REQUEST message and set the value to the USS address, if it is configured in the UE, and the UE may include the service-level-AA payload type, service-level-AA payload in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REQUEST message and set the value to "UUAA payload" and the UUAA payload respectively, if it is provided by the upper layer.
如果上层请求，支持UAS服务的UE会发起为UAS服务建立PDU会话的请求，UE应在PDU会话建立请求消息的服务级别AA容器IE中包含服务级别设备ID，并将该值设置为CAA级别UAV ID。如果在UE中配置了服务级别AA服务器地址，则UE可在PDU会话建立请求消息的服务级别AA容器IE中包含服务级别AA服务器地址，并将该值设置为USS地址，并且，如果由上层提供，则UE可以在PDU会话建立请求消息的服务级别AA容器IE中包括服务级别AA净荷类型、服务级别AA净荷，并将该值分别设置为“UUAA净荷”和UUAA净荷。
If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the Service-level-AA container IE is included in the PDU SESSION ESTABLISHMENT REQUEST message, and
a)   the service-level authentication and authorization by the external DN is required due to local policy;
b)   there is a valid user's subscription information for the requested DNN or for the requested DNN and S-NSSAI; and
c)   the information for the service-level authentication and authorization by the external DN in the Service-level-AA container IE includes CAA-level UAV ID,
then the SMF shall proceed with the UUAA-SM procedure as specified in 3GPP TS 23.256 [6AB] and refrain from accepting or rejecting the PDU SESSION ESTABLISHMENT REQUEST message until the service-level authentication and authorization procedure is completed.

如果正在建立的PDU会话是非紧急PDU会话，则请求类型未设置为“现有PDU会话”，服务级别AA容器IE包含在PDU会话建立请求消息中，并且
a）由于本地策略的原因，需要外部DN的服务级别身份验证和授权；
b）对于请求的DNN或请求的DNN和s-NSSAI，存在有效的用户订阅信息；和
c）服务级别AA容器IE中外部DN的服务级别身份验证和授权信息包括CAA级别UAV ID，
然后，SMF应继续执行3GPP TS 23.256[6AB]中规定的UUAA-SM程序，并在服务级别认证和授权程序完成之前，避免接受或拒绝PDU会话建立请求消息。

The UE supporting UAS services shall not request a PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) for which the UE has requested a service level authentication and authorization procedure which is ongoing.
If the PDU SESSION ESTABLISHMENT REQUEST message includes the PDU session pair ID IE, the RSN IE, or both, the SMF shall operate as specified in clause 5.33.2 of 3GPP TS 23.501 [8].
支持UAS服务的UE不得向相同的DNN（或如果UE未指示DNN，则无DNN）和相同的S-NSSAI（或如果UE未指示S-NSSAI，则无S-NSSAI）请求PDU会话建立过程，因为UE已经为其请求了正在进行的服务级身份验证和授权过程。
如果PDU会话建立请求消息包括PDU会话对ID IE、RSN IE或两者，则SMF应按照3GPP TS 23.501【8】第5.33.2节的规定运行。

modem日志：

PDU session establishment req

[0xB801] OTA LOG 02:22:51.622 PDU session establishment req PDU session establishment req 1
02:22:51.622 [0xB801] PDU session establishment req
pkt_version = 1 (0x1)
rel_number = 15 (0xf)
rel_version_major = 4 (0x4)
rel_version_minor = 0 (0x0)
prot_disc_type = 14 (0xe)
ext_protocol_disc = 46 (0x2e)
pdu_session_id = 1 (0x1)
proc_trans_id = 1 (0x1)
msg_type = 193 (0xc1) (PDU session establishment request)
nr5g_smm_msg
  pdu_session_estab_req
    integrity_prot_max_data_rate
      max_data_rate_per_UE_integrity_prot_ul = 0 (0x0)
      max_data_rate_per_UE_integrity_prot_dl = 0 (0x0)
    pdu_session_incl = 1 (0x1)
    pdu_session_type
      pdu_session_type = 3 (0x3) (IPv4v6)
    scc_mode_incl = 0 (0x0)
    _5gsm_cap_incl = 1 (0x1)
    _5gsm_cap
      tpmic = 0 (0x0)
      atsss_st = 0 (0x0)
      ept_s1 = 0 (0x0)
      mh6_pdu = 0 (0x0)
      Rqos = 0 (0x0)
      num_octs = 0 (0x0)
    max_num_supp_pkt_filter_incl = 0 (0x0)
    always_on_pdu_session_req_incl = 0 (0x0)
    pdu_dn_req_container_incl = 0 (0x0)
    ext_prot_config_incl = 1 (0x1)
    ext_prot_config
      ext = 1 (0x1)
      conf_prot = 0 (0x0)
      num_recs = 11 (0xb)
      prot_or_container[0]
        id = 32801 (0x8021) (IPCP)
        prot_or_container
          prot_len = 16 (0x10)
          ipcp_prot
            ipcp_prot_id = 1 (0x1) (CONF_REQ)
            identifier = 0 (0x0)
            rfc1332_conf_req
              num_options = 2 (0x2)
              conf_options[0]
                type = 129 (0x81)
                rfc1877_primary_dns_server_add
                  length = 6 (0x6)
                  ip_addr = 0 (0x0) (0.0.0.0)
              conf_options[1]
                type = 131 (0x83)
                rfc1877_sec_dns_server_add
                  length = 6 (0x6)
                  ip_addr = 0 (0x0) (0.0.0.0)
      prot_or_container[1]
        id = 13 (0xd) (DNS Server IPv4 Address Requestt)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[2]
        id = 3 (0x3) (DNS Server IPv6 Address Request)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[3]
        id = 1 (0x1) (P-CSCF IPv6 Address Request)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[4]
        id = 12 (0xc) (P-CSCF IPv4 Address Request)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[5]
        id = 18 (0x12) (P-CSCF Re-selection support)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[6]
        id = 10 (0xa) (IP address allocation via NAS signalling)
        prot_or_container
          prot_len = 0 (0x0)

      prot_or_container[7]
        id = 5 (0x5) (NWK Req Bearer Control indicator)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[8]
        id = 16 (0x10) (Ipv4 Link MTU Request)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[9]
        id = 17 (0x11) (MS support of Local address in TFT indicator)
        prot_or_container
          prot_len = 0 (0x0)
      prot_or_container[10]
        id = 35 (0x23) (QoS Rules with the length of 2 Octs support indicator)
        prot_or_container
          container_len = 0 (0x0)
    ip_hc_config_incl = 0 (0x0)
    ds_tt_ethernet_mac_add_incl = 0 (0x0)
    ue_ds_tt_residence_time_incl = 0 (0x0)
    port_management_incl = 0 (0x0)
    ethernet_hc_config_incl = 0 (0x0)
    pdu_addr_incl = 0 (0x0)

UL NAS transport

[0xB80B] OTA LOG 02:22:51.623 UL NAS transport UL NAS transport 102:22:51.623 [0xB80B] UL NAS transport
pkt_version = 1 (0x1)
rel_number = 15 (0xf)
rel_version_major = 4 (0x4)
rel_version_minor = 0 (0x0)
prot_disc_type = 14 (0xe)
ext_protocol_disc = 126 (0x7e)
security_header = 0 (0x0)
msg_type = 103 (0x67) (UL NAS transport)
nr5g_mm_msg
  ul_nas_transport
    payload_container_type = 1 (0x1) (N1 SM Info)
    payload_container
      default_payload_type
        num_bytes = 66 (0x42)
        pay_load_container[0] = 46 (0x2e)
        pay_load_container[1] = 1 (0x1)
        pay_load_container[2] = 1 (0x1)
        pay_load_container[3] = 193 (0xc1)
        pay_load_container[4] = 0 (0x0)
        pay_load_container[5] = 0 (0x0)
        pay_load_container[6] = 147 (0x93)
        pay_load_container[7] = 40 (0x28)
        pay_load_container[8] = 1 (0x1)
        pay_load_container[9] = 0 (0x0)
        pay_load_container[10] = 123 (0x7b)
        pay_load_container[11] = 0 (0x0)
        pay_load_container[12] = 53 (0x35)
        pay_load_container[13] = 128 (0x80)
        pay_load_container[14] = 128 (0x80)
        pay_load_container[15] = 33 (0x21)
        pay_load_container[16] = 16 (0x10)
        pay_load_container[17] = 1 (0x1)
        pay_load_container[18] = 0 (0x0)
        pay_load_container[19] = 0 (0x0)
        pay_load_container[20] = 16 (0x10)
        pay_load_container[21] = 129 (0x81)
        pay_load_container[22] = 6 (0x6)
        pay_load_container[23] = 0 (0x0)
        pay_load_container[24] = 0 (0x0)
        pay_load_container[25] = 0 (0x0)
        pay_load_container[26] = 0 (0x0)
        pay_load_container[27] = 131 (0x83)
        pay_load_container[28] = 6 (0x6)
        pay_load_container[29] = 0 (0x0)
        pay_load_container[30] = 0 (0x0)
        pay_load_container[31] = 0 (0x0)
        pay_load_container[32] = 0 (0x0)
        pay_load_container[33] = 0 (0x0)
        pay_load_container[34] = 13 (0xd)
        pay_load_container[35] = 0 (0x0)
        pay_load_container[36] = 0 (0x0)
        pay_load_container[37] = 3 (0x3)
        pay_load_container[38] = 0 (0x0)
        pay_load_container[39] = 0 (0x0)
        pay_load_container[40] = 1 (0x1)
        pay_load_container[41] = 0 (0x0)
        pay_load_container[42] = 0 (0x0)
        pay_load_container[43] = 12 (0xc)
        pay_load_container[44] = 0 (0x0)
        pay_load_container[45] = 0 (0x0)
        pay_load_container[46] = 18 (0x12)
        pay_load_container[47] = 0 (0x0)
        pay_load_container[48] = 0 (0x0)
        pay_load_container[49] = 10 (0xa)
        pay_load_container[50] = 0 (0x0)
        pay_load_container[51] = 0 (0x0)
        pay_load_container[52] = 5 (0x5)
        pay_load_container[53] = 0 (0x0)
        pay_load_container[54] = 0 (0x0)
        pay_load_container[55] = 16 (0x10)
        pay_load_container[56] = 0 (0x0)
        pay_load_container[57] = 0 (0x0)
        pay_load_container[58] = 17 (0x11)
        pay_load_container[59] = 0 (0x0)
        pay_load_container[60] = 0 (0x0)
        pay_load_container[61] = 35 (0x23)
        pay_load_container[62] = 0 (0x0)
        pay_load_container[63] = 0 (0x0)
        pay_load_container[64] = 36 (0x24)
        pay_load_container[65] = 0 (0x0)
    pdu_session_id_inc = 1 (0x1)
    pdu_session_id
      pdu_session_id2 = 1 (0x1)
    old_pdu_session_id_inc = 0 (0x0)
    req_type_incl = 1 (0x1)
    req_type
      req_type = 1 (0x1) (Initial request)
    s_nssai_incl = 0 (0x0)
    dnn_incl = 1 (0x1)
    dnn
      dnn_len = 4 (0x4)
      dnn_val[0] = 3 (0x3) (length)
      dnn_val[1] = 105 (0x69) (i)
      dnn_val[2] = 109 (0x6d) (m)
      dnn_val[3] = 115 (0x73) (s)
    add_info_incl = 0 (0x0)
    ma_pdu_session_incl = 0 (0x0)
    rel_assistance_incl = 0 (0x0)