6.4.1 UE-requested PDU session establishment procedure

6.4.1    UE-requested PDU session establishment procedure

6.4.1    UE请求的PDU会话建立过程

6.4.1.1 General

6.4.1.2 UE-requested PDU session establishment procedure initiation

6.4.1.3 UE-requested PDU session establishment procedure accepted by the network

6.4.1.4 UE-requested PDU session establishment procedure not accepted by the network

6.4.1.4.1 General
6.4.1.4.2 Handling of network rejection due to congestion control

6.4.1.4.3 Handling of network rejection not due to congestion control

6.4.1.5 Handling the maximum number of established PDU sessions

6.4.1.5A Handling the maximum number of allowed active user-plane resources for PDU sessions of UEs in NB-N1 mode

For a UE in NB-N1 mode, the UE's maximum number of supported user-plane resources is two (as defined in 3GPP TS 36.300 [25B]) when the UE sets the Multiple user-plane resources support bit to "Multiple user-plane resources supported" during the registration procedure for initial registration or for mobility and periodic registration update, and one otherwise.
对于NB-N1模式中的UE，当UE在初始注册或移动性和定期注册更新的注册过程中将多用户面资源支持位设置为“支持的多用户面资源”时，UE支持的用户平面资源的最大数量为两个（如3GPP TS 36.300[25B]中所定义），否则为一个。

For a UE operating in NB-N1 mode, if:
对于在NB-N1模式下操作的UE，如果：
a)    the UE's maximum number of supported user-plane resources is one, then only one PDU session can have active user-plane resources even though that UE might have established more than one PDU session; or
a） UE支持的用户面资源的最大数量是一个，那么即使UE可能已经建立了一个以上的PDU会话，也只有一个PDU会话可以具有活动用户面资源；或
b)    the UE's maximum number of supported user-plane resources is two, then only two PDU sessions can have active user-plane resources even though that UE might have established more than two PDU sessions.
b） UE支持的用户面资源的最大数量是两个，那么即使UE可能已经建立了两个以上的PDU会话，也只有两个PDU会话可以具有活动用户面资源。

When the maximum number of active user-plane resources is reached and upper layers request for more user-plane resources for PDU sessions other than the PDU sessions with those active user-plane resources, the UE can choose to release one or more of the PDU sessions with active user-plane resources to cater for the upper layer request. The choice of which PDU sessions to be released is implementation specific. However if there is a PDU session with an active user-plane that is used for exception data reporting (see subclause 6.2.13), that PDU session shall not be released.
当达到活动用户面资源的最大数量并且上层请求用于PDU会话的更多用户面资源而不是具有这些活动用户面的PDU会话时，UE可以选择释放具有活动用户面资源的一个或多个PDU会话以满足上层请求。释放哪些PDU会话的选择是特定于实现的。但是，如果PDU会话具有用于异常数据报告的活动用户面（见第6.2.13节），则不得释放该PDU会话。

If the maximum number of active user-plane resources is reached and the upper layers of the UE request user-plane resources for exception data reporting (see subclause 6.2.13), the UE shall release a PDU session that has user-plane resources to cater for the request for exception data reporting. The choice of which PDU session to be released is implementation specific.
如果达到活动用户面资源的最大数量，并且UE的上层请求用户面资源用于异常数据报告（见子条款6.2.13），则UE应释放具有用户面资源以满足异常数据报告请求的PDU会话。释放哪个PDU会话的选择是特定于实现的。
If the UE decides to release one or more active user-plane resources to cater for upper layer request, the UE shall release the PDU session via explicit 5GSM signalling.
如果UE决定释放一个或多个活动用户面资源以满足上层请求，则UE应通过显式5GSM信令释放PDU会话。

6.4.1.6 Abnormal cases in the UE

6.4.1.7 Abnormal cases on the network side

The following abnormal cases can be identified:
可以识别以下异常情况：
a)    If the received request type is "initial emergency request" and there is already another emergency PDU session for the UE, the SMF shall reject the PDU SESSION ESTABLISHMENT REQUEST message with 5GSM cause #31 "request rejected, unspecified" or release locally the existing emergency PDU session and proceed the new PDU SESSION ESTABLISHMENT REQUEST message
a） 如果接收到的请求类型为“初始紧急请求”，并且UE已经存在另一个紧急PDU会话，则SMF应拒绝具有5GSM原因#31“请求被拒绝，未指定”的PDU会话建立请求消息，或本地释放现有紧急PDU会话，并继续新的PDU对话建立请求消息
b)    The information for the PDU session authentication and authorization by the external DN in PDU DN request container is not compliant with local policy and user's subscription data
b） PDU DN请求容器中外部DN的PDU会话身份验证和授权信息不符合本地策略和用户的订阅数据

    If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the PDU session authentication and authorization by the external DN is required due to local policy and user's subscription data and 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 reject the PDU session establishment request including the 5GSM cause #29 "user authentication or authorization failed", in the PDU SESSION ESTABLISHMENT REJECT message.
如果正在建立的PDU会话是非紧急PDU会话，则请求类型不会设置为“现有PDU会话”，由于本地策略和用户的订阅数据，需要外部DN进行PDU会话认证和授权，并且SM PDU DN请求容器IE中的外部DN进行的PDU会话验证和授权的信息不符合本地策略和客户的订阅数据，SMF应拒绝PDU会话建立拒绝消息中包含5GSM原因#29“用户认证或授权失败”的PDU会话成立请求。

c)    UE-requested PDU session establishment with request type set to "initial request" or "initial emergency request" for an existing PDU session:
c） 对于现有PDU会话，UE请求PDU会话建立，请求类型设置为“初始请求”或“初始紧急请求”：
    If the SMF receives a PDU SESSION ESTABLISHMENT REQUEST message with a PDU session ID identical to the PDU session ID of an existing PDU session and with request type set to "initial request" or "initial emergency request", the SMF shall release locally the existing PDU session and proceed with the PDU session establishment procedure.
如果SMF收到PDU会话建立请求消息，其PDU会话ID与现有PDU会话的PDU会话标识相同，并且请求类型设置为“初始请求”或“初始紧急请求”，则SMF应在本地释放现有PDU对话，并继续PDU会话建设过程。

d)    UE-requested PDU session establishment with request type "existing PDU session" or "existing emergency PDU session" for a PDU session that does not exist:
d） UE请求PDU会话建立，请求类型为“现有PDU会话”或“现有紧急PDU会话”，用于不存在的PDU会话：
    If the SMF receives a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing PDU session" or "existing emergency PDU session", and the SMF does not have any information about that PDU session, then the SMF shall reject the PDU session establishment procedure with the 5GSM cause set to #54 "PDU session does not exist" in the PDU SESSION ESTABLISHMENT REJECT message.
如果SMF接收到PDU会话建立请求消息，请求类型设置为“现有PDU会话”或“现有紧急PDU会话”，并且SMF没有关于该PDU会话的任何信息，则SMF应拒绝PDU会话建立拒绝消息中的5GSM原因设置为#54“PDU会话不存在”的PDU会话设立过程。

e)    5G access network cannot forward the message:
e） 5G接入网无法转发消息：
    If the SMF determines based on content of the n2SmInfo attribute specified in 3GPP TS 29.502 [20A] that the DL NAS TRANSPORT message carrying the PDU SESSION ESTABLISHMENT ACCEPT was not forwarded to the UE by the 5G access network, then the SMF shall reject the PDU session establishment procedure with the 5GSM cause set to #26 "insufficient resources" in the PDU SESSION ESTABLISHMENT REJECT message.
如果SMF基于3GPP TS 29.502[20A]中指定的N2SINFO属性的内容确定携带PDU会话建立接受的DL NAS传输消息未被5G接入网络转发给UE，则SMF应在PDU会话建立拒绝消息中将5GSM原因设置为#26“资源不足”的情况下拒绝PDU会话确立过程。