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

目录

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

空口日志： PDU session establishment accept

---

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

6.4.1.3网络接受的UE请求的PDU会话建立过程

If the connectivity with the requested DN is accepted by the network, the SMF shall create a PDU SESSION ESTABLISHMENT ACCEPT message.
如果网络接受与请求DN的连接，SMF应创建PDU会话建立接受消息。
If the UE requests establishing an emergency PDU session, the network shall not check for service area restrictions or subscription restrictions when processing the PDU SESSION ESTABLISHMENT REQUEST message.

如果UE请求建立紧急PDU会话，则网络在处理PDU会话建立请求消息时不应检查服务区域限制或订阅限制。
The SMF shall set the Authorized QoS rules IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the authorized QoS rules of the PDU session and may include the authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message set to the authorized QoS flow descriptions of the PDU session.
NOTE 1:    This is applicable also if the PDU session establishment procedure was initiated to perform handover of an existing PDU session between 3GPP access and non-3GPP access, and even if the authorized QoS rules and authorized QoS flow descriptions for source and target access of the handover are the same.
SMF应将PDU会话建立接受消息的授权QoS规则IE设置为PDU会话的授权QoS规则，并可将PDU会话建立接受消息的授权QoS流描述IE设置为PDU会话的授权QoS流描述。
注1：如果启动PDU会话建立过程以在3GPP接入和非3GPP接入之间执行现有PDU会话的切换，并且即使切换的源和目标接入的授权QoS规则和授权QoS流描述相同，这也适用。

The SMF shall ensure that the number of the packet filters used in the authorized QoS rules of the PDU Session does not exceed the maximum number of packet filters supported by the UE for the PDU session. If the received request type is "initial emergency request", the SMF shall set the Authorized QoS flow descriptions IE according to the initial QoS parameters used for establishing emergency services configured in the SMF emergency configuration data.
SMF应确保PDU会话的授权QoS规则中使用的包过滤器的数量不超过UE为PDU会话支持的最大包过滤器数量。如果收到的请求类型为“初始紧急请求”，则SMF应根据SMF紧急配置数据中配置的用于建立紧急服务的初始QoS参数设置授权QoS流描述。
SMF shall set the Authorized QoS flow descriptions IE to the authorized QoS flow descriptions of the PDU session, if:
a)    the Authorized QoS rules IE contains at least one GBR QoS flow;
b)    the QFI is not the same as the 5QI of the QoS flow identified by the QFI;
c)    the QoS flow can be mapped to an EPS bearer as specified in subclause 4.11.1 of 3GPP TS 23.502 [9]; or
d)    the QoS flow is established for the PDU session used for relaying, as specified in subclause 5.6.2.1 of 3GPP TS 23.304 [6E].
NOTE 2:    In cases other than above listed cases, it is up to the SMF implementation to include the authorized QoS flow description for the QoS flow in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message.
如果出现以下情况，SMF应将授权QoS流描述IE设置为PDU会话的授权QoS流描述：
a） 授权QoS规则IE包含至少一个GBR QoS流；
b） QFI与QFI识别的QoS流的5QI不同；
c） QoS流可以映射到EPS承载，如3GPP TS 23.502【9】4.11.1节中规定的；或
d） 根据3GPP TS 23.304【6E】5.6.2.1节的规定，为用于中继的PDU会话建立QoS流。
注2：在上述情况以外的情况下，SMF实现可以在PDU会话建立接受消息的授权QoS流描述IE中包含QoS流的授权QoS流描述。

If interworking with EPS is supported for the PDU session, the SMF shall set in the PDU SESSION ESTABLISHMENT ACCEPT message:
a)    the Mapped EPS bearer contexts IE to the EPS bearer contexts mapped from one or more QoS flows of the PDU session; and
b)    the EPS bearer identity parameter in the Authorized QoS flow descriptions IE to the EPS bearer identity corresponding to the QoS flow, for each QoS flow which can be transferred to EPS.
如果PDU会话支持与EPS互通，则应在PDU会话建立接受消息中设置SMF：
a） 映射的EPS承载上下文IE到从PDU会话的一个或多个QoS流映射的EPS承载上下文；和
b） 授权QoS流描述中的EPS承载身份参数，即对于可以传输到EPS的每个QoS流，对应于QoS流的EPS承载身份。

If the "Create new EPS bearer" operation code in the Mapped EPS bearer contexts IE was received, and there is no corresponding Authorized QoS flow descriptions IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a Mapped EPS bearer contexts IE to delete the mapped EPS bearer context. If the EPS bearer identity parameter in the Authorized QoS flow descriptions IE was received, the operation code is "Create new QoS flow description" and there is no corresponding Mapped EPS bearer contexts IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall not diagnose an error, and shall keep storing the association between the QoS flow and the corresponding EPS bearer identity.
如果接收到映射的EPS承载上下文IE中的“创建新的EPS承载”操作码，并且PDU会话建立接受消息中没有相应的授权QoS流描述IE，则UE应发送包括映射的EPS承载上下文IE的PDU会话修改请求消息，以删除映射的EPS承载上下文。如果接收到授权QoS流描述IE中的EPS承载身份参数，操作码为“创建新的QoS流描述”，并且PDU会话建立接受消息中没有对应的映射EPS承载上下文IE，则UE不应诊断错误，并应保持存储QoS流与对应EPS承载身份之间的关联。

Furthermore, the SMF shall store the association between the QoS flow and the mapped EPS bearer context, for each QoS flow which can be transferred to EPS.
The SMF shall set the selected SSC mode IE of the PDU SESSION ESTABLISHMENT ACCEPT message to:
a)    the received SSC mode in the SSC mode IE included in the PDU SESSION ESTABLISHMENT REQUEST message based on one or more of the PDU session type, the subscription and the SMF configuration;
b)    either the default SSC mode for the data network listed in the subscription or the SSC mode associated with the SMF configuration, if the SSC mode IE is not included in the PDU SESSION ESTABLISHMENT REQUEST message.
此外，对于可以传输到EPS的每个QoS流，SMF应存储QoS流和映射的EPS承载上下文之间的关联。
SMF应将PDU会话建立接受消息的选定SSC模式IE设置为：
a） 基于PDU会话类型、订阅和SMF配置中的一个或多个，在PDU会话建立请求消息中包括的SSC模式IE中接收到的SSC模式；
b） 订阅中列出的数据网络的默认SSC模式或与SMF配置相关的SSC模式，如果PDU会话建立请求消息中未包含SSC模式IE。

If the PDU session is an emergency PDU session, the SMF shall set the Selected SSC mode IE of the PDU SESSION ESTABLISHMENT ACCEPT message to "SSC mode 1". If the PDU session is a non-emergency PDU session of "Ethernet" or "Unstructured" PDU session type, the SMF shall set the Selected SSC mode IE to "SSC mode 1" or "SSC mode 2". If the PDU session is a non-emergency PDU session of "IPv4", "IPv6" or "IPv4v6" PDU session type, the SMF shall set the selected SSC mode IE to "SSC mode 1", "SSC mode 2", or "SSC mode 3".
如果PDU会话是紧急PDU会话，SMF应将PDU会话建立接受消息的选定SSC模式IE设置为“SSC模式1”。如果PDU会话是“以太网”或“非结构化”PDU会话类型的非紧急PDU会话，SMF应将所选SSC模式IE设置为“SSC模式1”或“SSC模式2”。如果PDU会话是“IPv4”、“IPv6”或“IPv4v6”PDU会话类型的非紧急PDU会话，则SMF应将所选SSC模式IE设置为“SSC模式1”、“SSC模式2”或“SSC模式3”。

If the PDU session is a non-emergency PDU session and the UE is not registered for onboarding services in SNPN, the SMF shall set the S-NSSAI IE of the PDU SESSION ESTABLISHMENT ACCEPT message to:
a)    the S-NSSAI of the PDU session; and
    b) the mapped S-NSSAI (if available in roaming scenarios).
如果PDU会话是非紧急PDU会话，并且UE未在SNPN中注册入站服务，则SMF应将PDU会话建立接受消息的S-NSSAI IE设置为：
a） PDU会话的S-NSSAI；和
b） 映射的S-NSSAI（如果在漫游场景中可用）。
The SMF shall set the Selected PDU session type IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the selected PDU session type, i.e. the PDU session type of the PDU session.
SMF应将PDU会话建立接受消息的选定PDU会话类型IE设置为选定的PDU会话类型，即PDU会话的PDU会话类型。

If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "IPv4v6", the SMF shall select "IPv4", "IPv6" or "IPv4v6" as the Selected PDU session type. If the subscription, the SMF configuration, or both, are limited to IPv4 only or IPv6 only for the DNN selected by the network, the SMF shall include the 5GSM cause value #50 "PDU session type IPv4 only allowed", or #51 "PDU session type IPv6 only allowed", respectively, in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT ACCEPT message.
如果PDU会话建立请求消息包括设置为“IPv4v6”的PDU会话类型，则SMF应选择“IPv4”、“IPv6”或“IPv4v6”作为所选PDU会话类型。如果网络选择的DNN的订阅、SMF配置或两者都仅限于IPv4或IPv6，则SMF应在PDU会话建立接受消息的5GSM原因IE中分别包含5GSM原因值#50“PDU会话类型IPv4 only allowed”或#51“PDU会话类型IPv6 only allowed”。
If the selected PDU session type is "IPv4", the SMF shall include the PDU address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the PDU address IE to an IPv4 address is allocated to the UE in the PDU session.
如果选择的PDU会话类型为“IPv4”，则SMF应在PDU会话建立接受消息中包括PDU地址IE，并应将PDU地址IE设置为在PDU会话中分配给UE的IPv4地址。
If the selected PDU session type is "IPv6", the SMF shall include the PDU address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the PDU address IE to an interface identifier for the IPv6 link local address allocated to the UE in the PDU session.
如果所选PDU会话类型为“IPv6”，则SMF应在PDU会话建立接受消息中包括PDU地址IE，并应将PDU地址IE设置为PDU会话中分配给UE的IPv6链路本地地址的接口标识符。

If the selected PDU session type is "IPv4v6", the SMF shall include the PDU address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the PDU address IE to an IPv4 address and an interface identifier for the IPv6 link local address, allocated to the UE in the PDU session.
如果选择的PDU会话类型为“IPv4v6”，则SMF应在PDU会话建立接受消息中包括PDU地址IE，并应将PDU地址IE设置为分配给PDU会话中UE的IPv4地址和IPv6链路本地地址的接口标识符。
If the selected PDU session type of a PDU session established by the W-AGF acting on behalf of the FN-RG is "IPv4v6" or "IPv6", the SMF shall also indicate the SMF's IPv6 link local address in the PDU address IE of the PDU SESSION ESTABLISHMENT ACCEPT message.
如果代表FN-RG的W-AGF建立的PDU会话的选定PDU会话类型为“IPv4v6”或“IPv6”，则SMF还应在PDU会话建立接受消息的PDU地址IE中指示SMF的IPv6链路本地地址。

If the PDU session is a non-emergency PDU session and the UE is not registered for onboarding services in SNPN, the SMF shall set the DNN IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the DNN determined by the AMF of the PDU session.
如果PDU会话是非紧急PDU会话，并且UE未在SNPN中注册入站服务，则SMF应将PDU会话建立接受消息的DNN IE设置为由PDU会话的AMF确定的DNN。
The SMF shall set the Session-AMBR IE of the PDU SESSION ESTABLISHMENT ACCEPT message to the Session-AMBR of the PDU session.
SMF应将PDU会话建立接受消息的会话AMBR IE设置为PDU会话的会话AMBR。

If the selected PDU session type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and if the PDU SESSION ESTABLISHMENT REQUEST message includes a 5GSM capability IE with the RQoS bit set to "Reflective QoS supported", the SMF shall consider that reflective QoS is supported for QoS flows belonging to this PDU session and may include the RQ timer IE set to an RQ timer value in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果所选PDU会话类型为“IPv4”、“IPv6”、“IPv4v6”或“Ethernet”，并且PDU会话建立请求消息包含5GSM能力IE，RQoS位设置为“反射QoS支持”，SMF应考虑对属于该PDU会话的QoS流支持反射QoS，并可在PDU会话建立接受消息中包括设置为RQ计时器值的RQ计时器IE。
If the selected PDU session type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and if the PDU SESSION ESTABLISHMENT REQUEST message includes a Maximum number of supported packet filters IE, the SMF shall consider this number as the maximum number of packet filters that can be supported by the UE for this PDU session. Otherwise the SMF considers that the UE supports 16 packet filters for this PDU session.
如果所选PDU会话类型为“IPv4”、“IPv6”、“IPv4v6”或“Ethernet”，并且如果PDU会话建立请求消息包括受支持的最大数量的包过滤器IE，则SMF应将该数量视为UE可为该PDU会话支持的最大包过滤器数量。否则，SMF认为UE支持该PDU会话的16个包过滤器。
The SMF shall consider that 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 are valid for the lifetime of the PDU session.
SMF应考虑UE支持的用于上行链路的用户面完整性保护的每个UE的最大数据速率和UE支持的用于下行链路的用户面完整性保护的每个UE的最大数据速率在PDU会话的生存期内有效。

If the value of the RQ timer is set to "deactivated" or has a value of zero, the UE considers that RQoS is not applied for this PDU session.
NOTE 3:    If the 5G core network determines that reflective QoS is to be used for a QoS flow, the SMF sends reflective QoS indication (RQI) to UPF to activate reflective QoS. If the QoS flow is established over 3GPP access, the SMF also includes reflective QoS Attribute (RQA) in QoS profile of the QoS flow during QoS flow establishment.
如果RQ计时器的值被设置为“停用”或值为零，则UE认为RQoS没有应用于该PDU会话。
注3：如果5G核心网络确定将反射QoS用于QoS流，则SMF向UPF发送反射QoS指示（RQI）以激活反射QoS。如果通过3GPP接入建立QoS流，则在QoS流建立期间，SMF还包括QoS流的QoS简档中的反射QoS属性（RQA）。

If the selected PDU session type is "IPv6" or "IPv4v6" and if the PDU SESSION ESTABLISHMENT REQUEST message includes a 5GSM capability IE with the MH6-PDU bit set to "Multi-homed IPv6 PDU session supported", the SMF shall consider that this PDU session is supported to use multiple IPv6 prefixes.
如果所选PDU会话类型为“IPv6”或“IPv4v6”，并且如果PDU会话建立请求消息包含5GSM功能IE，且MH6-PDU位设置为“支持多宿主IPv6 PDU会话”，则SMF应考虑支持此PDU会话使用多个IPv6前缀。
If the selected PDU session type is "Ethernet", the PDU SESSION ESTABLISHMENT REQUEST message includes a 5GSM capability IE with the EPT-S1 bit set to "Ethernet PDN type in S1 mode supported" and the network supports Ethernet PDN type in S1 mode, the SMF shall set the EPT-S1 bit of the 5GSM network feature support IE of the PDU SESSION ESTABLISHMENT ACCEPT message to "Ethernet PDN type in S1 mode supported".
如果所选PDU会话类型为“Ethernet”，PDU会话建立请求消息包括5GSM功能IE，EPT-S1位设置为“支持S1模式下的Ethernet PDN类型”，并且网络支持S1模式下的Ethernet PDN类型，SMF应将PDU会话建立接受消息的5GSM网络功能支持IE的EPT-S1位设置为“支持S1模式的以太网PDN类型”。
If the DN authentication of the UE was performed and completed successfully, the SMF shall set the EAP message IE of the PDU SESSION ESTABLISHMENT ACCEPT message to an EAP-success message as specified in IETF RFC 3748 [34], provided by the DN.
如果成功执行并完成了UE的DN认证，则SMF应将PDU会话建立接受消息的EAP消息IE设置为DN提供的IETF RFC 3748[34]中规定的EAP成功消息。
Based on local policies or configurations in the SMF and the Always-on PDU session requested IE in the PDU SESSION ESTABLISHMENT REQUEST message (if available), if the SMF determines that either:
a)    the requested PDU session needs to be established as an always-on PDU session (e.g. because the PDU session is for time synchronization or TSC, for URLLC, or for both), the SMF shall include the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the value to "Always-on PDU session required"; or
b)    the requested PDU session shall not be established as an always-on PDU session and:
i)    if the UE included the Always-on PDU session requested IE, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message and shall set the value to "Always-on PDU session not allowed"; or
ii)    if the UE did not include the Always-on PDU session requested IE, the SMF shall not include the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message.
基于SMF中的本地策略或配置以及PDU会话建立请求消息中请求的始终在线PDU会话IE（如果可用），如果SMF确定：
a） 请求的PDU会话需要建立为始终在线PDU会话（例如，因为PDU会话用于时间同步或TSC、URLLC或两者），SMF应在PDU会话建立接受消息中包含始终在线PDU会话指示IE，并应将值设置为“需要始终在线PDU会话”；或
b） 请求的PDU会话不得建立为始终在线的PDU会话，并且：
i） 如果UE包括始终在线的PDU会话请求IE，则SMF应在PDU会话建立接受消息中包括始终在线的PDU会话指示IE，并应将该值设置为“始终在线的PDU会话不允许”；或
ii）如果UE未包括始终在线的PDU会话请求IE，则SMF不得在PDU会话建立接受消息中包括始终在线的PDU会话指示IE。
If the PDU session is an MA PDU session, the SMF shall include the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message. The SMF shall set the content of the ATSSS container IE as specified in 3GPP TS 24.193 [13B]. If the UE requests to establish user plane resources over the second access of an MA PDU session which has already been established over the first access and the parameters associated with ATSSS previously provided to the UE are not to be updated, the "ATSSS container contents" shall not be included in the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果PDU会话是MA PDU会话，SMF应在PDU会话建立接受消息中包含ATSSS容器IE。SMF应按照3GPP TS 24.193【13B】的规定设置ATSSS容器IE的内容物。如果UE请求在已经在第一个接入中建立的MA PDU会话的第二个接入中建立用户平资源，并且不更新之前提供给UE的与ATSS相关联的参数，则“ATSSS容器内容”不应包括在PDU会话建立接受消息中的ATSSS容器IE中。
If the PDU session is a single access PDU session containing the MA PDU session information IE with the value set to "MA PDU session network upgrade is allowed" and:
a) if the SMF decides to establish a single access PDU session, the SMF shall not include the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message; or
b) if the SMF decides to establish an MA PDU session, the SMF shall include the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message, which indicates to the UE that the requested single access PDU session was established as an MA PDU Session.
如果PDU会话是包含MA PDU会话信息IE且其值设置为“允许MA PDU会话网络升级”的单接入PDU会话，并且：
a） 如果SMF决定建立单一接入PDU会话，则SMF不应在PDU会话建立接受消息中包含ATSSS容器IE；或
b） 如果SMF决定建立MA PDU会话，则SMF应在PDU会话建立接受消息中包括ATSSS容器IE，该消息向UE指示所请求的单接入PDU会话已建立为MA PDU会话。
If the network decides that the PDU session is only for control plane CIoT 5GS optimization, the SMF shall include the control plane only indication in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果网络决定PDU会话仅用于控制面CIoT 5GS优化，则SMF应在PDU会话建立接受消息中包含仅控制面指示。
If:
a)    the UE provided the IP header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message; and
b)    the SMF supports IP header compression for control plane CIoT 5GS optimization;
the SMF shall include the IP header compression configuration IE in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果：
a） UE在PDU会话建立请求消息中提供IP报头压缩配置IE；和
b） SMF支持IP报头压缩，用于控制面CIoT 5GS优化；
SMF应在PDU会话建立接受消息中包括IP报头压缩配置IE。
If:
a)    the UE provided the Ethernet header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message; and
b)    the SMF supports Ethernet header compression for control plane CIoT 5GS optimization;
the SMF shall include the Ethernet header compression configuration IE in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果：
a） UE在PDU会话建立请求消息中提供以太网报头压缩配置IE；和
b） SMF支持以太网报头压缩，用于控制面CIoT 5GS优化；
SMF应在PDU会话建立接受消息中包括以太网报头压缩配置IE。

If the PDU SESSION ESTABLISHMENT REQUEST included the Requested MBS container IE with the MBS operation set to "Join MBS session", the SMF:
a)    shall include the TMGI for the MBS session IDs that the UE is allowed to join, if any, in the Received MBS container IE, shall set the MBS decision to "MBS join is accepted" for each of those Received MBS information, and may include the MBS security container in each of those Received MBS information, and shall use separate QoS flows dedicated for multicast by including the Authorized QoS flow descriptions IE if no separate QoS flows dedicated for multicast exist or if the SMF wants to establish new QoS flows dedicated for multicast;
b)    shall include the TMGI for MBS session IDs that the UE is not allowed to join, if any, in the Received MBS container IE, shall set the MBS decision to "MBS join is rejected" for each of those Received MBS information and shall set the Rejection cause for each of those Received MBS information with the reason of rejection; and
c)    may include in the Received MBS container IE the MBS service area for each MBS session and include in it the MBS TAI list, the NR CGI list or both, that identify the service area(s) for the local MBS service
in the PDU SESSION ESTABLISHMENT ACCEPT message. If the UE has set the Type of MBS session ID to "Source specific IP multicast address" in the Requested MBS container IE for certain MBS session(s) in the PDU SESSION MODIFICATION REQUEST message, the SMF may include the Source IP address information and Destination IP address information in the Received MBS information together with the TMGI for each of those MBS sessions.
NOTE 4:    Including the Source IP address information and Destination IP address information in the Received MBS information in that case is to allow the UE to perform the mapping between the requested MBS Requested PEIPS assistance informationsession ID and the provided TMGI.
NOTE 5:    In SNPN, TMGI is used together with NID to identify an MBS Session.
如果PDU会话建立请求包括请求的MBS容器IE，并且MBS操作设置为“加入MBS会话”，则SMF：
a） 应包括允许UE加入的MBS会话ID的TMGI，如果有的话，在接收到的MBS容器IE中，应为每个接收到的MBS信息将MBS决策设置为“MBS加入被接受”，并且可以在每个接收到的MBS信息中包括MBS安全容器，并且应通过包括授权的QoS流描述IE来使用专用于多播的单独QoS流，即如果不存在专用于多播的单独QoS流，或者如果SMF想要建立专用于多播的新QoS流；
b） 应在接收到的MBS容器IE中包括不允许UE加入的MBS会话ID的TMGI（如果有），应为每个接收到的MBS信息将MBS决策设置为“MBS加入被拒绝”，并应为每个接收到的MBS信息用拒绝原因设置拒绝原因；和
c） 可以在接收到的MBS容器中包括每个MBS会话的MBS服务区域，并在其中包括MBS TAI列表、NR CGI列表或两者，其标识本地MBS服务的服务区域
在PDU会话建立中接受消息。如果UE在PDU会话修改请求消息中为某些MBS会话在请求的MBS容器IE中将MBS会话ID的类型设置为“源特定IP多播地址”，则SMF可以在接收到的MBS信息中包括源IP地址信息和目标IP地址信息，以及这些MBS会话中每个MBS会话的TMGI。
注4：在这种情况下，在接收到的MBS信息中包括源IP地址信息和目标IP地址信息是为了允许UE执行请求的MBS请求的PEIPS协助信息会话ID和提供的TMGI之间的映射。
注5：在SNPN中，TMGI与NID一起用于识别MBS会话。
If the request type is "existing PDU session", the SMF shall not perform network slice admission control for the PDU session, except for the following cases:
a)    when EPS counting is not required for the S-NSSAI of the PDU session for network slice admission control and the PDU session is established due to transfer the PDN connection from S1 mode to N1 mode in case of inter-system change; or
b)    handover of an existing PDU session between 3GPP access and non-3GPP access is performed.
The SMF shall send the PDU SESSION ESTABLISHMENT ACCEPT message.
如果请求类型为“现有PDU会话”，则SMF不得对PDU会话执行网络切片许可控制，但以下情况除外：
a） 当用于网络切片接纳控制的PDU会话的S-NSSAI不需要EPS计数，并且由于在系统间变化的情况下将PDN连接从S1模式转移到N1模式而建立PDU会话时；或
b） 在3GPP接入和非3GPP接入之间执行现有PDU会话的切换。
SMF应发送PDU会话建立接受消息。 
Upon receipt of a PDU SESSION ESTABLISHMENT ACCEPT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shall stop timer T3580, shall release the allocated PTI value and shall consider that the PDU session was established.
在收到PDU会话建立接受消息和PDU会话ID后，使用5.4.5节中规定的NAS传输过程，UE应停止计时器T3580，释放分配的PTI值，并应认为PDU会话已建立。
If the PDU session establishment procedure was initiated to perform handover of an existing PDU session between 3GPP access and non-3GPP access, then upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message the UE shall locally delete any authorized QoS rules, authorized QoS flow descriptions and the parameters provided in the Protocol configuration options IE when in S1 mode or the Extended protocol configuration options IE stored for the PDU session before processing the new received authorized QoS rules, authorized QoS flow descriptions and the parameters provided in the Extended protocol configuration options IE, if any.
NOTE 6:    For the case of handover from 3GPP access to non-3GPP access, deletion of the QoS flow descriptions implies deletion of the associated EPS bearer identities, if any, and according to subclause 6.1.4.1 also deletion of the associated EPS bearer contexts. Regarding the reverse direction, for PDU sessions via non-3GPP access the network does not allocate associated EPS bearer identities (see 3GPP TS 23.502 [9], subclause 4.11.1.4.1).
如果启动PDU会话建立过程以在3GPP接入和非3GPP接入之间执行现有PDU会话的切换，则在收到PDU会话建立接受消息后，在处理新接收的授权QoS规则、授权QoS流描述和扩展协议配置选项（如有）中提供的参数之前，UE应在本地删除任何授权的QoS规则，协议配置选项（即在S1模式下）或扩展协议配置选项（即为PDU会话存储的）中提供的授权QoS流描述和参数。
注6：对于从3GPP接入切换到非3GPP接入的情况，删除QoS流描述意味着删除相关的EPS承载身份（如有），并且根据第6.1.4.1款，也删除相关的EPS承载上下文。关于反向，对于通过非3GPP接入的PDU会话，网络不分配相关的EPS承载身份（参见3GPP TS 23.502[9]，第4.11.1.4.1节）。
If the PDU session establishment procedure was initiated to perform handover of an existing PDU session from 3GPP access to non-3GPP access and that existing PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS sessions and the SMF shall consider the UE as removed from the associated MBS sessions.
如果启动PDU会话建立过程以执行现有PDU会话从3GPP接入到非3GPP接入的切换，并且现有PDU会话与一个或多个MBS会话相关联，则UE应在本地离开相关的MBS会话，并且SMF应认为UE已从相关的MBS会话中移除。
For an MA PDU session already established on a single access, upon receipt of PDU SESSION ESTABLISHMENT ACCEPT message over the other access:
a)    the UE shall delete the stored authorized QoS rules;
b)    if the authorized QoS flow descriptions IE is included in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall delete the stored authorized QoS flow descriptions; and
c)    if the mapped EPS bearer contexts IE is included in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall delete the stored mapped EPS bearer contexts.
对于已经在单个接入上建立的MA PDU会话，在收到PDU会话建立后，通过其他接入接收消息：
a） UE应删除存储的授权QoS规则；
b） 如果授权QoS流描述IE包括在PDU会话建立接受消息中，则UE应删除存储的授权QoS流描述；和
c） 如果映射的EPS承载上下文IE包括在PDU会话建立接受消息中，则UE应删除存储的映射的EPS承载上下文。
The UE shall store the authorized QoS rules, and the session-AMBR received in the PDU SESSION ESTABLISHMENT ACCEPT message for the PDU session. The UE shall also store the authorized QoS flow descriptions if it is included in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message for the PDU session.
UE应存储授权的QoS规则，以及在PDU会话建立接受消息中接收的用于PDU会话的会话AMBR。如果授权QoS流描述包括在PDU会话的PDU会话建立接受消息的授权QoS流描述中，则UE还应存储授权QoS流描述。
If the number of the authorized QoS rules, the number of the packet filters, or the number of the authorized QoS flow descriptions associated with the PDU session have reached the maximum number supported by the UE upon receipt of a PDU SESSION ESTABLISHMENT ACCEPT message, then the UE may initiate the PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #26 "insufficient resources".
如果与PDU会话相关联的授权QoS规则的数量、分组过滤器的数量或授权QoS流描述的数量已经达到UE在接收到PDU会话建立接受消息时支持的最大数量，然后，UE可以通过发送具有5GSM原因#26“资源不足”的PDU会话释放请求消息来启动PDU会话释放过程。
For a PDU session that is being established with the request type set to "initial request", "initial emergency request" or "MA PDU request", or a PDU session that is being transferred from EPS to 5GS and established with the request type set to "existing PDU session" or "existing emergency PDU session" or a PDU session that is being handed over between non-3GPP access and 3GPP access and established with the request type set to "existing PDU session" or "existing emergency PDU session ", the UE shall verify the authorized QoS rules and the authorized QoS flow descriptions provided in the PDU SESSION ESTABLISHMENT ACCEPT message for different types of errors as follows:
对于正在建立的PDU会话，请求类型设置为“初始请求”、“初始紧急请求”或“MA PDU请求”，或正在从EPS转移到5GS并使用设置为“现有PDU会话”或“现有紧急PDU会话”的请求类型建立的PDU会话，或正在非3GPP接入和3GPP接入之间切换并使用设置为“现有PDU会话”或“现有紧急PDU会话”的请求类型建立的PDU会话，对于不同类型的错误，UE应验证PDU会话建立接受消息中提供的授权QoS规则和授权QoS流描述，如下所示：
a)    Semantic errors in QoS operations:
1)    When the rule operation is "Create new QoS rule", and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule.
2)    When the rule operation is "Create new QoS rule", and there is no rule with the DQR bit set to "the QoS rule is the default QoS rule".
3)    When the rule operation is "Create new QoS rule" and two or more QoS rules associated with this PDU session would have identical precedence values.
4)    When the rule operation is an operation other than "Create new QoS rule".
5)    When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", and the UE is in NB-N1 mode.
6)    When the rule operation is "Create new QoS rule" and two or more QoS rules associated with this PDU session would have identical QoS rule identifier values.
7)    When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", and the PDU session type of the PDU session is "Unstructured".
8)    When the flow description operation is an operation other than "Create new QoS flow description".
9)    When the flow description operation is "Create new QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule and the UE is NB-N1 mode.
10)    When the flow description operation is "Create new QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule, and the PDU session type of the PDU session is "Unstructured".
a） QoS操作中的语义错误：
1） 当规则操作为“创建新的QoS规则”，并且当已经存在默认QoS规则时，DQR位设置为“QoS规则是默认QoS规则”。
2） 当规则操作为“创建新的QoS规则”，并且没有将DQR位设置为“QoS规则是默认QoS规则”的规则时。
3） 当规则操作为“创建新的QoS规则”时，与此PDU会话相关的两个或多个QoS规则将具有相同的优先级值。
4） 当规则操作不是“创建新QoS规则”的操作时。
5） 当规则操作为“创建新的QoS规则”时，DQR位设置为“QoS规则不是默认的QoS规则”，并且UE处于NB-N1模式。
6） 当规则操作为“创建新的QoS规则”时，与此PDU会话相关联的两个或多个QoS规则将具有相同的QoS规则标识符值。
7） 当规则操作为“创建新的QoS规则”时，DQR位设置为“QoS规则不是默认的QoS规则”，并且PDU会话的PDU会话类型为“非结构化”。
8） 当流描述操作不是“创建新的QoS流描述”时。
9） 当流描述操作为“创建新的QoS流描述”时，与QoS流描述相关联的QFI与默认QoS规则的QFI不同，UE为NB-N1模式。
10） 当流描述操作为“创建新的QoS流描述”时，与QoS流描述相关联的QFI与默认QoS规则的QFI不同，并且PDU会话的PDU会话类型为“非结构化”。
In case 4, case 5, or case 7 if the rule operation is for a non-default QoS rule, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS rule with 5GSM cause #83 "semantic error in the QoS operation".
在情况4、情况5或情况7中，如果规则操作用于非默认QoS规则，则UE应发送具有5GSM原因为#83“QoS操作中的语义错误”的PDU会话修改请求消息以删除QoS规则。
In case 8, case 9, or case 10, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS flow description with 5GSM cause #83 "semantic error in the QoS operation".
在情况8、情况9或情况10中，UE应发送有5GSM原因#83“QoS操作中的语义错误”的PDU会话修改请求消息以删除QoS流描述。
Otherwise for all the cases above, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation".
否则，对于上述所有情况，UE应通过发送具有5GSM cause#83“QoS操作中的语义错误”的PDU会话释放请求消息来启动PDU会话释放过程。
b)    Syntactical errors in QoS operations:
1)    When the rule operation is "Create new QoS rule", the QoS rule is a QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the QoS rule is empty.
2)    When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is the default QoS rule", the PDU session type of the PDU session is "Unstructured", and the packet filter list in the QoS rule is not empty.
3)    When there are other types of syntactical errors in the coding of the Authorized QoS rules IE or the Authorized QoS flow descriptions IE, such as: a mismatch between the number of packet filters subfield and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned", or the QoS flow identifier is set to "no QoS flow identifier assigned".
4)    When, the rule operation is "Create new QoS rule", there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule and the UE determines, by using the QoS rule’s QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in 3GPP TS 23.501 [8] table 5.7.4-1).
5)    When the    flow description operation is "Create new QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in 3GPP TS 23.501 [8] table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI.
b） QoS操作中的语法错误：
1） 当规则操作为“创建新的QoS规则”时，QoS规则是IPv4、IPv6、IPv4v6或以太网PDU会话类型的PDU会话的QoS规则，QoS规则中的数据包过滤器列表为空。
2） 当规则操作为“创建新的QoS规则”时，DQR位设置为“QoS规则是默认QoS规则”，PDU会话的PDU会话类型为“非结构化”，QoS规则中的数据包过滤器列表不为空。
3） 当授权QoS规则IE或授权QoS流描述IE的编码中存在其他类型的语法错误时，例如：当规则操作为“删除现有QoS规则”或“创建新QoS规则”时，数据包过滤器子字段的数量与数据包过滤器列表中的数据包过滤器数量不匹配，或者，数据包过滤器子字段的数量大于数据包过滤器列表中数据包过滤器的最大可能数量（即，QoS规则IE中不包括QoS规则优先子字段），QoS规则标识符设置为“未分配QoS规则标识符”，或者QoS流标识符设置为“未分配QoS流标识符”。
4） 当规则操作为“创建新的QoS规则”时，不存在QFI对应于结果QoS规则的QFI的QoS流描述，并且UE通过使用QoS规则的QFI作为5QI来确定存在GBR QoS流的结果QoS规则（如3GPP TS 23.501[8]表5.7.4-1中所述）。
5） 当流描述操作为“创建新的QoS流描述”时，UE确定存在缺少至少一个强制性参数（即GFBR上行链路、GFBR下行链路、MFBR上行链路和MFBR下行链路）的GBR QoS流的QoS流描述（如3GPP TS 23.501[8]表5.7.4-1中所述）。如果QoS流描述不包括5QI，则UE通过使用QFI作为5QI来确定这一点。
In case 1, case 3 or case 4, if the QoS rule is not the default QoS rule, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a requested QoS rule IE to delete the QoS rule with 5GSM cause #84 "syntactical error in the QoS operation". Otherwise, if the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #84 "syntactical error in the QoS operation".
在情况1、情况3或情况4中，如果QoS规则不是默认QoS规则，则UE应发送PDU会话修改请求消息，包括请求的QoS规则IE，5GSM原因为#84“QoS操作中的语法错误”，以删除QoS规则。否则，如果QoS规则是默认QoS规则，则UE应通过发送带有5GSM原因#84“QoS操作中的语法错误”的PDU会话释放请求消息来启动PDU会话释放过程。
In case 2, if the QoS rule is the default QoS rule, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a requested QoS rule IE to delete all the packet filters of the default QoS rule. The UE shall include the 5GSM cause #84 "syntactical error in the QoS operation".
在情况2中，如果QoS规则是默认QoS规则，则UE应发送包括请求的QoS规则IE的PDU会话修改请求消息，以删除默认QoS规则的所有分组过滤器。UE应包括5GSM原因#84“QoS操作中的语法错误”。
In case 5, if the default QoS rule is associated with the QoS flow description which lacks at least one of the mandatory parameters, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #84 "syntactical error in the QoS operation". Otherwise, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS flow description which lacks at least one of the mandatory parameters and the associated QoS rule(s), if any, with 5GSM cause #84 "syntactical error in the QoS operation".
在情况5中，如果默认QoS规则与缺少至少一个强制性参数的QoS流描述相关联，则UE应通过发送带有5GSM cause#84“QoS操作中的语法错误”的PDU会话释放请求消息来启动PDU会话释放过程。否则，UE应发送PDU会话修改请求消息以删除缺少至少一个强制性参数和相关QoS规则（如果有的话）的QoS流描述，5GSM导致#84“QoS操作中的语法错误”。
NOTE 7:    It is not considered an error if the UE determines that after processing all QoS operations on QoS rules and QoS flow descriptions there is a QoS flow description that is not associated with any QoS rule and the UE is not in NB-N1 mode.
注7：如果UE确定在处理QoS规则和QoS流描述的所有QoS操作后，存在与任何QoS规则无关的QoS流描述，并且UE不处于NB-N1模式，则不认为是错误。
c)    Semantic errors in packet filters:
1)    When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document.
        If the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #44 "semantic error in packet filter(s)". Otherwise, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS rule with 5GSM cause #44 "semantic error in packet filter(s)".
c） 数据包筛选器中的语义错误：
1） 当数据包过滤器由冲突的数据包过滤器组件组成时，这些组件将使数据包过滤器无效，即没有任何IP数据包将适合此数据包过滤器。UE如何确定分组过滤器中的语义错误超出了本文档的范围。
如果QoS规则是默认QoS规则，则UE应通过发送带有5GSM原因#44“数据包过滤器中的语义错误”的PDU会话释放请求消息来启动PDU会话释放过程。否则，UE应发送PDU会话修改请求消息以删除5GSM原因为#44“分组过滤器中的语义错误”的QoS规则。
d)    Syntactical errors in packet filters:
1)    When the rule operation is "Create new QoS rule" and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers.
2)    When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier.
If the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #45 "syntactical errors in packet filter(s)". Otherwise, the UE shall send a PDU SESSION MODIFICATION REQUEST message to delete the QoS rule with 5GSM cause #45 "syntactical errors in packet filter(s)".
d） 数据包过滤器中的语法错误：
1） 当规则操作为“创建新的QoS规则”时，结果QoS规则中的两个或多个包过滤器将具有相同的包过滤器标识符。
2） 当包过滤器的编码中存在其他类型的语法错误时，例如使用包过滤器组件标识符的保留值。
如果QoS规则是默认的QoS规则，则UE应通过发送带有5GSM cause#45“分组过滤器中的语法错误”的PDU会话释放请求消息来启动PDU会话释放过程。否则，UE应发送PDU会话修改请求消息以删除5GSM原因为#45“分组滤波器中的语法错误”的QoS规则。
If the Always-on PDU session indication IE is included in the PDU SESSION ESTABLISHMENT ACCEPT message and:
a)    the value of the IE is set to "Always-on PDU session required", the UE shall consider the established PDU session as an always-on PDU session; or
b)    the value of the IE is set to "Always-on PDU session not allowed", the UE shall not consider the established PDU session as an always-on PDU session.
The UE shall not consider the established PDU session as an always-on PDU session if the UE does not receive the Always-on PDU session indication IE in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果始终在线的PDU会话指示IE包含在PDU会话建立接受消息中，并且：
a） IE的值设置为“需要始终在线PDU会话”，UE应将已建立的PDU会话视为始终在线PDU会话；或
b） IE的值设置为“不允许始终在线PDU会话”，UE不应将已建立的PDU会话视为始终在线PDU会话。
如果UE没有在PDU会话建立接受消息中接收到始终在线的PDU会话指示IE，则UE不应将已建立的PDU会话视为始终在线的PDU会话。
The UE shall store the mapped EPS bearer contexts, if received in the PDU SESSION ESTABLISHMENT ACCEPT message. Furthermore, the UE shall also store the association between the QoS flow and the mapped EPS bearer context, for each QoS flow which can be transferred to EPS, based on the received EPS bearer identity parameter in Authorized QoS flow descriptions IE and the mapped EPS bearer contexts. The UE shall check each mapped EPS bearer context for different types of errors as follows:
NOTE 8:    An error detected in a mapped EPS bearer context does not cause the UE to discard the Authorized QoS rules IE and Authorized QoS flow descriptions IE included in the PDU SESSION ESTABLISHMENT ACCEPT, if any.
如果在PDU会话建立接受消息中接收到，则UE应存储映射的EPS承载上下文。此外，UE还应基于授权QoS流描述IE中接收到的EPS承载身份参数和映射的EPS承载上下文，为可传输到EPS的每个QoS流存储QoS流和映射的EPS承载上下文之间的关联。UE应检查每个映射的EPS承载上下文是否存在以下不同类型的错误：
注8：在映射的EPS承载上下文中检测到的错误不会导致UE丢弃PDU会话建立接受中包括的授权QoS规则IE和授权QoS流描述IE（如果有）。

a)    Semantic error in the mapped EPS bearer operation:
1)    When the operation code is an operation code other than "Create new EPS bearer".
2)    When the operation code is "Create new EPS bearer" and there is already an existing mapped EPS bearer context with the same EPS bearer identity associated with any PDU session.
3)    When the operation code is "Create new EPS bearer" and the resulting mapped EPS bearer context has invalid or missing mandatory parameters (e.g., mapped EPS QoS parameters or traffic flow template for a dedicated EPS bearer context).
a） 映射的EPS承载操作中的语义错误：
1） 当操作代码是“创建新的EPS承载”以外的操作代码时。
2） 当操作代码为“创建新的EPS承载”并且已经存在具有与任何PDU会话相关联的相同EPS承载身份的现有映射EPS承载上下文时。
3） 当操作代码为“创建新的EPS承载”且生成的映射EPS承载上下文具有无效或缺失的强制性参数（例如，专用EPS承载上下文的映射EPS QoS参数或业务流模板）时。

In case 2, if the existing mapped EPS bearer context is associated with the PDU session that is being established, the UE shall not diagnose an error, further process the create request and, if it was process successfully, delete the old EPS bearer context.
在情况2中，如果现有映射的EPS承载上下文与正在建立的PDU会话相关联，则UE不应诊断错误，进一步处理创建请求，并且，如果处理成功，则删除旧的EPS承载上下文。
Otherwise, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity".
否则，UE应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除5GSM原因为#85“无效映射EPS承载身份”的映射EPS承载上下文。
b)    if the mapped EPS bearer context includes a traffic flow template, the UE shall check the traffic flow template for different types of TFT IE errors as follows:
b） 如果映射的EPS承载上下文包括业务流模板，则UE应检查业务流模板是否存在不同类型的TFT IE错误，如下所示：
1)    Semantic errors in TFT operations:
i)    When the TFT operation is an operation other than "Create a new TFT"
    The UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #41 "semantic error in the TFT operation".
1） TFT操作中的语义错误：
i） 当TFT操作不是“创建新TFT”操作时
UE应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除5GSM原因为#41“TFT操作中的语义错误”的映射EPS承载上下文。
2)    Syntactical errors in TFT operations:
i)    When the TFT operation = "Create a new TFT" and the packet filter list in the TFT IE is empty.
ii)    When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE).
    The UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message with to delete the mapped EPS bearer context 5GSM cause #42 "syntactical error in the TFT operation".
2） TFT操作中的语法错误：
i） 当TFT操作=“创建新TFT”且TFT IE中的数据包过滤器列表为空时。
ii）当TFT IE的编码中存在其他类型的语法错误时，例如当规则操作为“删除现有QoS规则”或“创建新QoS规则”时，包过滤器子字段的数量与包过滤器列表中的包过滤器数量不匹配，或者，包过滤器子字段的数量大于包过滤器列表中最大可能的包过滤器数量（即，QoS规则IE中不包括QoS规则优先子字段）。
UE应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除映射的EPS承载上下文5GSM原因#42“TFT操作中的语法错误”。
3)    Semantic errors in packet filters:
i)    When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document.
ii)    When the resulting TFT does not contain any packet filter which applicable for the uplink direction.
    The UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #44 "semantic errors in packet filter(s)".
3） 数据包过滤器中的语义错误：
i） 当数据包过滤器由冲突的数据包过滤器组件组成时，这些组件将使数据包过滤器无效，即没有任何IP数据包将适合此数据包过滤器。UE如何确定分组过滤器中的语义错误超出了本文档的范围。
ii）当生成的TFT不包含适用于上行链路方向的任何分组滤波器时。
UE应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除5GSM原因为#44“分组滤波器中的语义错误”的映射EPS承载上下文。

4)    Syntactical errors in packet filters:
i)    When the TFT operation = "Create a new TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers.
ii)    When the TFT operation = "Create a new TFT" and two or more packet filters in all TFTs associated with this PDN connection would have identical packet filter precedence values.
iii)    When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier.
    In case ii, if the old packet filters do not belong to the default EPS bearer context, the UE shall not diagnose an error and shall delete the old packet filters which have identical filter precedence values.
        In case ii, if one or more old packet filters belong to the default EPS bearer context, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical errors in packet filter(s)".
    In cases i and iii the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical error in packet filter(s)".
4） 数据包过滤器中的语法错误：
i） 当TFT操作=“创建新TFT”和结果TFT中的两个或多个包过滤器将具有相同的包过滤器标识符时。
ii）当TFT操作=“创建新TFT”和与此PDN连接相关的所有TFT中的两个或多个包过滤器将具有相同的包过滤器优先值时。
iii）当包过滤器的编码中存在其他类型的语法错误时，例如使用包过滤器组件标识符的保留值。
在情况ii中，如果旧分组滤波器不属于默认的EPS承载上下文，则UE不应诊断错误，并且应删除具有相同滤波器优先值的旧分组滤波器。
在情况ii中，如果一个或多个旧的分组过滤器属于默认的EPS承载上下文，则UE应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除具有5GSM原因为#45“分组过滤器中的语法错误”的映射的EPS承载上下文。
在情况i和iii中，UE应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除5GSM原因为#45“分组滤波器中的语法错误”的映射EPS承载上下文。

If the UE detects different errors in the mapped EPS bearer contexts, QoS rules or QoS flow descriptions, the UE may send a single PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts, QoS rules or QoS flow descriptions. In that case, the UE shall include a single 5GSM cause in the PDU SESSION MODIFICATION REQUEST message.
如果UE在映射的EPS承载上下文、QoS规则或QoS流描述中检测到不同的错误，则UE可以发送单个PDU会话修改请求消息以删除错误的映射的EPS承载上下文、QoS规则或QoS流描述。在这种情况下，UE应在PDU会话修改请求消息中包括单个5GSM原因。
NOTE 9:    The 5GSM cause to use cannot be different from: #41 "semantic error in the TFT operation", #42 "syntactical error in the TFT operation", #44 "semantic error in packet filter(s)", #45 "syntactical errors in packet filter(s)", #83 "semantic error in the QoS operation", #84 "syntactical error in the QoS operation", and #85 "Invalid mapped EPS bearer identity". The selection of a 5GSM cause is up to the UE implementation.
注9:5GSM使用原因不能不同于：#41“TFT操作中的语义错误”、#42“TFT操作中的语法错误”、#44“数据包过滤器中的语义错误”、#45“数据包过滤器中的语法错误”、#83“QoS操作中的语义错误”、#84“QoS操作中的语法错误”和#85“映射的EPS承载身份无效”。5GSM原因的选择取决于UE实现。
If there are mapped EPS bearer context(s) associated with a PDU session, but none of them is associated with the default QoS rule, the UE shall locally delete the mapped EPS bearer context(s) and shall locally delete the stored EPS bearer identity (EBI) in all the QoS flow descriptions of the PDU session, if any.
如果存在与PDU会话相关联的映射EPS承载上下文，但其中没有一个与默认QoS规则相关联，则UE应在本地删除映射的EPS承载上下文，并在PDU会话的所有QoS流描述（如果有）中本地删除存储的EPS承载身份（EBI）。
The UE shall only use the Control plane CIoT 5GS optimization for this PDU session if the Control plane only indication is included in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果PDU会话建立接受消息中包含仅控制面指示，则UE应仅对此PDU会话使用控制面CIoT 5GS优化。
If the UE requests the PDU session type "IPv4v6" and:
a)    the UE receives the selected PDU session type set to "IPv4" and does not receive the 5GSM cause value #50 "PDU session type IPv4 only allowed"; or
b)    the UE receives the selected PDU session type set to "IPv6" and does not receive the 5GSM cause value #51 "PDU session type IPv6 only allowed";
如果UE请求PDU会话类型“IPv4v6”，并且：
a） UE接收设置为“IPv4”的选定PDU会话类型，并且不接收5GSM原因值#50“仅允许IPv4的PDU会话类型”；或
b） UE接收设置为“IPv6”的选定PDU会话类型，并且不接收5GSM原因值#51“仅允许PDU会话类型IPv6”；
the UE may subsequently request another PDU session for the other IP version using the UE-requested PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) with a single address PDN type (IPv4 or IPv6) other than the one already activated.
UE随后可以使用UE请求的PDU会话建立过程，向相同的DNN（或没有DNN，如果UE没有指示DNN）和与（如果在漫游场景中可用）映射的S-NSSAI（或没有S-NSSAI，如果UE没有指示S-NSSAI）相关联的相同S-NSSAI请求另一个IP版本的PDU会话，该映射的S-NSSAI具有单地址PDN类型（IPv4或IPv6）而不是已经激活的。
If the UE requests the PDU session type "IPv4v6", receives the selected PDU session type set to "IPv4" and the 5GSM cause value #50 "PDU session type IPv4 only allowed", the UE shall not subsequently request another PDU session using the UE-requested PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) to obtain a PDU session type different from the one allowed by the network until any of the following conditions is fulfilled:
如果UE请求PDU会话类型“IPv4v6”，接收设置为“IPv4”的选定PDU会话类型和5GSM原因值#50“仅允许PDU会话类型IPv4”，随后，UE不得使用UE请求的PDU会话建立过程向相同的DNN（或没有DNN，如果UE未指示DNN）和与映射的S-NSSAI（或没有S-NSSAI，如果UE未指示S-NSSAI）相关联的相同S-NSSAI（如果在漫游场景中可用）请求另一个PDU会话，以获得不同于已被网络允许的PDU会话类型，直到满足以下任何条件：
a)    the UE is registered to a new PLMN;
b)    the UE is switched off; or
c)    the USIM is removed or the entry in the "list of subscriber data" for the current SNPN is updated.
a） UE注册到新的PLMN；
b） UE关闭；或
c） 删除USIM或更新当前SNPN的“用户数据列表”中的条目。
If the UE requests the PDU session type "IPv4v6", receives the selected PDU session type set to "IPv6" and the 5GSM cause value #51 "PDU session type IPv6 only allowed", the UE shall not subsequently request another PDU session using the UE-requested PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) to obtain a PDU session type different from the one allowed by the network until any of the following conditions is fulfilled:
如果UE请求PDU会话类型“IPv4v6”，则接收设置为“IPv6”的选定PDU会话类型和5GSM原因值#51“仅允许PDU会话类型IPv6”，随后，UE不得使用UE请求的PDU会话建立过程向相同的DNN（或没有DNN，如果UE未指示DNN）和与映射的S-NSSAI（或没有S-NSSAI，如果UE未指示S-NSSAI）相关联的相同S-NSSAI（如果在漫游场景中可用）请求另一个PDU会话，以获得不同于已被网络允许的PDU会话类型，直到满足以下任何条件：
a)    the UE is registered to a new PLMN;
b)    the UE is switched off; or
c)    the USIM is removed or the entry in the "list of subscriber data" for the current SNPN is updated.
a） UE注册到新的PLMN；
b） UE关闭；或
c） 删除USIM或更新当前SNPN的“用户数据列表”中的条目。
NOTE 10:    For the 5GSM cause values #50 "PDU session type IPv4 only allowed", and #51 "PDU session type IPv6 only allowed", re-attempt in S1 mode for the same DNN (or no DNN, if no DNN was indicated by the UE) is only allowed using the PDU session type(s) indicated by the network.
注10：对于5GSM原因值#50“PDU会话类型IPv4 only allowed”和#51“PDU会话类型IPv6 only allowed”，仅允许使用网络指示的PDU会话类型在S1模式下重新尝试相同的DNN（或没有DNN，如果UE指示没有DNN）。

If the selected PDU session type of the PDU session is "Unstructured" or "Ethernet", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. Additionally the UE shall also initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity".
如果PDU会话的选定PDU会话类型为“非结构化”或“以太网”，则UE支持系统间从N1模式更改为S1模式，UE不支持为S1模式中设置为“非IP”的PDN类型建立PDN连接，并且在PDU会话建立接受消息的授权QoS流描述IE中接收的一个或多个授权QoS流描述的参数列表字段包含EPS承载标识（EBI），则UE应从此类一个或多个授权QoS流描述的参数列表字段中局部移除EPS承载标识（EBI）。此外，UE还应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除5GSM原因为#85“无效映射EPS承载身份”的映射EPS承载上下文。
If the selected PDU session type of the PDU session is "Ethernet", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, the UE, the network or both of them do not support Ethernet PDN type in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION ESTABLISHMENT ACCEPT message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. Additionally, the UE shall also initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity".
如果PDU会话的选定PDU会话类型为“以太网”，则UE支持系统间从N1模式更改为S1模式，UE不支持为S1模式下设置为“非IP”的PDN类型建立PDN连接，UE、网络或两者均不支持S1模式下的以太网PDN类型，并且在PDU会话建立接受消息的授权QoS流描述IE中接收的一个或多个授权QoS流描述的参数列表字段包含EPS承载标识（EBI），则UE应从此类一个或多个授权QoS流描述的参数列表字段中局部移除EPS承载标识（EBI）。此外，UE还应通过发送PDU会话修改请求消息来启动PDU会话修改过程，以删除5GSM原因为#85“无效映射EPS承载身份”的映射EPS承载上下文。
If the UE receives an IPv4 Link MTU parameter, an Ethernet Frame Payload MTU parameter, an Unstructured Link MTU parameter, or a Non-IP Link MTU parameter in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall pass to the upper layer the received IPv4 link MTU size, the received Ethernet frame payload MTU size, the unstructured link MTU size, or the non-IP link MTU size.
如果UE在PDU会话建立接受消息的扩展协议配置选项IE中接收到IPv4链路MTU参数、以太网帧有效载荷MTU参数、非结构化链路MTU参数或非IP链路MTU参数，则UE应将接收到的IPv4链路MTU大小、接收到的以太网帧有效载荷MTU大小、非结构化链路MTU大小或非IP链路MTU大小传到上层。
NOTE 11:    The IPv4 link MTU size corresponds to the maximum length of user data packet that can be sent either via the control plane or via N3 interface for a PDU session of the "IPv4" PDU session type.
注11:IPv4链路MTU大小对应于可通过控制面或用于“IPv4”PDU会话类型的PDU会话的N3接口发送的用户数据包的最大长度。
NOTE 12:    The Ethernet frame payload MTU size corresponds to the maximum length of a payload of an Ethernet frame that can be sent either via the control plane or via N3 interface for a PDU session of the "Ethernet" PDU session type.
注12：以太网帧有效载荷MTU大小对应于以太网帧有效载荷的最大长度，该有效载荷可以通过控制面或用于“以太网”PDU会话类型的PDU会话的N3接口发送。
NOTE 13:    The unstructured link MTU size correspond to the maximum length of user data packet that can be sent either via the control plane or via N3 interface for a PDU session of the "Unstructured" PDU session type.
注13：非结构化链路MTU大小对应于用户数据包的最大长度，，用户数据包可以通过控制面或用于“非结构化”PDU会话类型的PDU会话的N3接口发送。
NOTE 14:    A PDU session of "Ethernet" or "Unstructured" PDU session type can be transferred to a PDN connection of "non-IP" PDN type, thus the UE can request the non-IP link MTU parameter in the PDU session establishment procedure. The non-IP link MTU size corresponds to the maximum length of user data that can be sent either in the user data container in the ESM DATA TRANSPORT message or via S1-U interface as specified in 3GPP TS 24.301 [15].
注14：“以太网”或“非结构化”PDU会话类型的PDU会话可以传输到“非IP”PDN类型的PDN连接，因此UE可以在PDU会话建立过程中请求非IP链路MTU参数。非IP链路MTU大小对应于可以在ESM数据传输消息的用户数据容器中或通过3GPP TS 24.301[15]中规定的S1-U接口发送的用户数据的最大长度。
If the 5G-RG receives an ACS information parameter in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the 5G-RG shall pass the ACS URL in the received ACS information parameter to the upper layer.
如果5G-RG在PDU会话建立接受消息的扩展协议配置选项IE中接收到ACS信息参数，则5G-RG应将接收到的ACS信息参数中的ACS URL传递给上层。
If the UE has indicated support for CIoT 5GS optimizations and receives a small data rate control parameters container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store the small data rate control parameters value and use the stored small data rate control parameters value as the maximum allowed limit of uplink user data for the PDU session in accordance with 3GPP TS 23.501 [8].
如果UE已指示支持CIoT 5GS优化，并在PDU会话建立接受消息的扩展协议配置选项IE中接收到小数据速率控制参数容器，根据3GPP TS 23.501[8]，UE应存储小数据速率控制参数值，并使用存储的小数据速率控制参数值作为PDU会话的上行链路用户数据的最大允许限制。
If the UE has indicated support for CIoT 5GS optimizations and receives an additional small data rate control parameters for exception data container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store the additional small data rate control parameters for exception data value and use the stored additional small data rate control parameters for exception data value as the maximum allowed limit of uplink exception data for the PDU session in accordance with 3GPP TS 23.501 [8].
如果UE已指示支持CIoT 5GS优化，并在PDU会话建立接受消息的扩展协议配置选项IE中接收到异常数据容器的额外小数据速率控制参数，根据3GPP TS 23.501[8]，UE应存储用于异常数据值的额外小数据速率控制参数，并使用存储的用于异常数据值的额外小数据速率控制参数作为PDU会话的上行链路异常数据的最大允许限制。
If the UE has indicated support for CIoT 5GS optimizations and receives an initial small data rate control parameters container or an initial additional small data rate control parameters for exception data container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall use these parameters for the newly established PDU Session. When the validity period of the initial parameters expire, the parameters received in a small data rate control parameters container or an additional small data rate control parameters for exception data container shall be used.
如果UE已指示支持CIoT 5GS优化，并在PDU会话建立接受消息的扩展协议配置选项IE中接收到初始小数据速率控制参数容器或异常数据容器的初始附加小数据速率控制参数，则UE应将这些参数用于新建立的PDU会话。当初始参数的有效期到期时，应使用小数据速率控制参数容器中接收的参数或异常数据容器的附加小数据速率控制参数。

If the UE receives a Serving PLMN rate control IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store the Serving PLMN rate control IE value and use the stored serving PLMN rate control value as the maximum allowed limit of uplink control plane user data for the corresponding PDU session in accordance with 3GPP TS 23.501 [8].
如果UE在PDU会话建立接受消息中接收到服务PLMN速率控制IE，则UE应存储服务PLMN速率控制IE值，并根据3GPP TS 23.501[8]将存储的服务PLMN速率控制值用作相应PDU会话的上行链路控制平面用户数据的最大允许限制。
If the UE receives an APN rate control parameters container or an additional APN rate control for exception data parameters container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store these parameters and use them to limit the rate at which it generates uplink user data messages for the PDN connection corresponding to the PDU session if the PDU session is transferred to EPS upon inter-system change from N1 mode to S1 mode in accordance with 3GPP TS 24.301 [15]. The received APN rate control parameters and additional APN rate control for exception data parameters shall replace any previously stored APN rate control parameters and additional APN rate control for exception data parameters, respectively, for this PDN connection.
如果UE在PDU会话建立接受消息的扩展协议配置选项IE中接收到APN速率控制参数容器或额外的APN速率控制异常数据参数容器，如果根据3GPP TS 24.301[15]，在系统间从N1模式切换到S1模式时，PDU会话被转移到EPS，则UE应存储这些参数并使用它们来限制其为与PDU会话相对应的PDN连接生成上行链路用户数据消息的速率。对于该PDN连接，接收到的APN速率控制参数和用于异常数据参数的附加APN速率控制应分别替换之前存储的任何APN速率控制参数和用于异常数据参数的附加APN速率控制。
If the UE receives an initial APN rate control parameters container or an initial additional APN rate control for exception data parameters container in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall store these parameters in the APN rate control status and use them to limit the rate at which it generates exception data messages for the PDN connection corresponding to the PDU session if the PDU session is transferred to EPS upon inter-system change from N1 mode to S1 mode in accordance with 3GPP TS 24.301 [15]. The received APN rate control status shall replace any previously stored APN rate control status for this PDN connection.
如果UE在PDU会话建立接受消息的扩展协议配置选项IE中接收到初始APN速率控制参数容器或初始附加APN速率控制异常数据参数容器，如果根据3GPP TS 24.301[15]，在系统间从N1模式切换到S1模式时，PDU会话被转移到EPS，则UE应将这些参数存储在APN速率控制状态中，并使用它们来限制其为与PDU会话相对应的PDN连接生成异常数据消息的速率。接收到的APN速率控制状态应替换之前存储的该PDN连接的任何APN速率控制状态。

NOTE 15:    In the PDU SESSION ESTABLISHMENT ACCEPT message, the SMF provides either APN rate control parameters container, or initial APN rate control parameters container, in the Extended protocol configuration options IE, but not both.
注15：在PDU会话建立接受消息中，SMF在扩展协议配置选项IE中提供APN速率控制参数容器或初始APN速率控制参数容器，但不能同时提供两者。
NOTE 16:    In the PDU SESSION ESTABLISHMENT ACCEPT message, the SMF provides either additional APN rate control for exception data parameters container, or initial additional APN rate control for exception data parameters container, in the Extended protocol configuration options IE, but not both.
注16：在PDU会话建立接受消息中，SMF在扩展协议配置选项IE中为异常数据参数容器提供额外的APN速率控制，或为异常数据参数容器提供初始额外的APN速率控制，但不能同时提供两者。

If the network accepts the use of Reliable Data Service to transfer data for the PDU session, the network shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the Reliable Data Service accepted indicator. The UE behaves as described in subclause 6.2.15.
如果网络接受使用可靠数据服务为PDU会话传输数据，则网络应在PDU会话建立接受消息中包括扩展协议配置选项IE，并包括可靠数据服务接受指示器。UE的行为如第6.2.15节所述。
If the UE indicates support of DNS over (D)TLS by providing DNS server security information indicator to the network and optionally, if the UE wishes to indicate which security protocol type(s) are supported by the UE, providing the DNS server security protocol support and the network wants to enforce the use of DNS over (D)TLS, the network may include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the DNS server security information with length of two octets. Upon receiving the DNS server security information, the UE shall pass it to the upper layer. The UE shall use this information to send the DNS over (D)TLS (See 3GPP TS 33.501 [24]).
如果UE通过向网络提供DNS服务器安全信息指示符来指示对（D）TLS上的DNS的支持，并且可选地，如果UE希望指示UE支持哪些安全协议类型，则提供DNS服务器安全协议支持，并且网络希望强制使用（D）TLS上的DNS，该网络可以在PDU会话建立接受消息中包括扩展协议配置选项IE，并包括长度为两个八位字节的DNS服务器安全信息。在接收到DNS服务器安全信息后，UE应将其传递给上层。UE应使用该信息通过（D）TLS发送DNS（参见3GPP TS 33.501[24]）。
NOTE 17:    Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501 [24] and it is implemented based on the operator requirement.
注17：（D）TLS上的DNS支持基于3GPP TS 33.501[24]中规定的信息要求，并根据运营商要求实施。
If the PDU SESSION ESTABLISHMENT REQUEST message includes the Service-level-AA container IE with the service-level device ID set to the CAA-level UAV ID, and the SMF is provided by the UAS-NF the successful UUAA-SM resultand the CAA-level UAV ID, the SMF shall store the successful result together with the authorized CAA-level UAV ID and transmit the PDU SESSION ESTABLISHMENT ACCEPT message to the UE, where the PDU SESSION ESTABLISHMENT ACCEPT message shall include the Service-level-AA container IE containing:
如果PDU会话建立请求消息包括服务级别AA容器IE，其服务级别设备ID设置为CAA级UAV ID，并且SMF由UAS-NF提供，则成功的UUAA-SM结果和CAA级UAV ID，SMF应将成功结果与授权的CAA级UAV ID一起存储，并将PDU会话建立接受消息发送给UE，其中PDU会话建立接受消息应包括服务级AA容器IE，其中包含：
a)    the service-level-AA response, with the SLAR bits set to "Service level authentication and authorization was successful";
b)     the service-level device ID with the value set to the CAA-level UAV ID; and
c)    if the UUAA payload is received from the UAS-NF:
1)    the service-level-AA payload type, with the values set to "UUAA payload"; and
2)    the service-level-AA payload, with the value set to the UUAA payload.
a） 服务级别AA响应，SLAR位设置为“服务级别身份验证和授权成功”；
b） 值设置为CAA级UAV ID的服务级设备ID；和
c） 如果从UAS-NF接收到UUAA有效载荷：
1） 服务级别AA有效负载类型，其值设置为“UUAA有效负载”；和
2） 服务级别AA负载，其值设置为UUAA负载。
NOTE 18:    UAS security information can be included in the UUAA payload by the USS as specified in 3GPP TS 33.256 [24B].
注18：根据3GPP TS 33.256[24B]中的规定，UAS安全信息可由USS包含在UUAA有效载荷中。

If the network accepts establishment of the PDU session for C2 communication, the network shall include the Service-level-AA container IE in the PDU SESSION ESTABLISHMENT ACCEPT message. The Service-level-AA container IE:
a)    includes C2 authorization result;
b)    can include C2 session security information; and
c)    can include service-level device ID with the value set to a new CAA-level UAV ID.
Upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message of the PDU session for C2 communication, if the Service-level-AA container IE is included and it contains a CAA-level UAV ID and the C2 authorization result, the UE shall replace its currently stored CAA-level UAV ID with the new CAA-level UAV ID.
如果网络接受建立用于C2通信的PDU会话，则网络应在PDU会话建立接受消息中包括服务级别AA容器IE。AA容器的服务级别IE：
a） 包括C2授权结果；
b） 可以包括C2会话安全信息；和
c） 可以包括服务级设备ID，其值设置为新的CAA级UAV ID。
在收到用于C2通信的PDU会话的PDU会话建立接受消息后，如果包括服务级AA容器IE，并且其包含CAA级UAV ID和C2授权结果，则UE应将其当前存储的CAA级UAV ID替换为新的CAA级UAV ID。

The SMF may be configured with one or more PVS IP addresses or PVS names associated with the DNN and S-NSSAI used for onboarding services in SNPN, for configuration of SNPN subscription parameters in PLMN via the user plane, or for configuration of a UE via the user plane with credentials for NSSAA or PDU session authentication and authorization procedure. If the PDU session was established for onboarding services in SNPN, or the PVS information request is included in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message establishing a PDU session providing connectivity for configuration of SNPN subscription parameters in PLMN via the user plane, the network may include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the PVS IP address(es) or the PVS name(s) or both associated with the DNN and S-NSSAI of the established PDU session, if available. If the PVS information request is included in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message establishing the PDU session providing connectivity for configuration of a UE via the user plane with credentials for NSSAA or PDU session authentication and authorization procedure, based on the subscribed DNN(s) and S-NSSAI(s) of the UE and the DNN and S-NSSAI of the established PDU session, the network should include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message and include the PVS IP address(es) or the PVS name(s) or both, which are associated with the established PDU session and per subscribed DNN(s) and S-NSSAI(s) of the UE, if available.
SMF可以配置一个或多个与DNN和S-NSSAI相关联的PVS IP地址或PVS名称，用于SNPN中的登录服务，用于通过用户面在PLMN中配置SNPN订阅参数，或用于通过用户面配置UE，并具有NSSAA或PDU会话认证和授权过程的凭据。如果PDU会话是为SNPN中的登录服务建立的，或者PVS信息请求包括在PDU会话建立请求消息的扩展协议配置选项IE中，正建立的PDU会话通过用户平面为PLMN中的SNPN订阅参数的配置提供连接，网络可以在PDU会话建立接受消息中包括扩展协议配置选项IE，并包括与已建立PDU会话的DNN和s-NSSAI相关联的PVS IP地址或PVS名称（如果可用）。如果PVS信息请求包括在建立PDU会话的PDU会话建立请求消息的扩展协议配置选项IE中，通过用户面为UE的配置提供连接，并具有NSSAA或PDU会话认证和授权过程的凭据，基于UE的订阅DNN和s-NSSAI以及已建立PDU会话的DNN和s-NSSAI，网络应在PDU会话建立接受消息中包括扩展协议配置选项IE，并包括PVS IP地址或PVS名称或两者，与已建立的PDU会话相关联，并根据UE的订阅DNN和s-NSSAI（如果可用）。
NOTE 20:    If the PDU session is established for configuration of SNPN subscription parameters in SNPN via the user plane by a UE which is not registered for onboarding services in SNPN, the SMF can include the PVS IP address(es) or the PVS name(s) or both, associated with the DNN and S-NSSAI of the established PDU session, if available, in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message.
注20：如果PDU会话是由未在SNPN中注册入站服务的UE通过用户面为SNPN中的SNPN订阅参数的配置而建立的，则SMF可以包括与所建立的PDU会话的DNN和s-NSSAI相关联的PVS IP地址或PVS名称或两者（如果可用），在PDU会话建立接受消息的扩展协议配置选项IE中。
If the UE indicates support for ECS configuration information provisioning by providing the ECS configuration information provisioning support indicator in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message, then the SMF may include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with at least one of ECS IPv4 Address, ECS IPv6 Address, and ECS FQDN included and may include an ECS provider identifier. The SMF may include spatial validity condition along with the ECS IPv4 Address, ECS IPv6 Address, or ECS FQDN respectively in the Extended protocol configuration options IE, if available. The UE upon receiving one or more ECS IPv4 address(es), if any, ECS IPv6 address(es), if any, or ECS FQDN(s), if any, an ECS provider identifier, if any, and the spatial validity condition associated with the ECS IPv4 Address, ECS IPv6 Address, or ECS FQDN respectively, if any, shall pass them to the upper layers.
如果UE通过在PDU会话建立请求消息的扩展协议配置选项IE中提供ECS配置信息提供支持指示符来指示对ECS配置信息提供的支持，然后，SMF可以包括在PDU会话建立接受消息的扩展协议配置选项IE中，包括ECS IPv4地址、ECS IPv6地址和ECS FQDN中的至少一个，并且可以包括ECS提供商标识符。SMF可以在扩展协议配置选项（如可用）中包括空间有效性条件以及ECS IPv4地址、ECS IPv6地址或ECS FQDN。UE在接收到一个或多个ECS IPv4地址（如有）、ECS IPv6地址（如有）或ECS FQDN（如有）、ECS提供商标识符（如有）以及分别与ECS IPv4地址、ECS IPv6地址或ECS FQDN（如有）相关联的空间有效性条件时，应将其传递给上层。
NOTE 21:    If an ECS provider identifier is included, then the IP address(es) and/or FQDN(s) are associated with the ECS provider identifier and replace previously provided ECS configuration information associated with the same ECS provider identifier, if any.
注21：如果包括ECS提供商标识符，则IP地址和/或FQDN与ECS提供商标识符关联，并替换先前提供的与同一ECS提供商标识符关联的ECS配置信息（如果有）。

If the SMF needs to provide DNS server address(es) to the UE and the UE has provided the DNS server IPv4 address request, the DNS server IPv6 address request or both of them, in the PDU SESSION ESTABLISHMENT REQUEST message, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them. If the UE supports receiving DNS server addresses in protocol configuration options and receives one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them, in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, then the UE shall pass the received DNS server IPv4 address(es), if any, and the received DNS server IPv6 address(es), if any, to upper layers.
如果SMF需要向UE提供DNS服务器地址，并且UE在PDU会话建立请求消息中提供了DNS服务器IPv4地址请求、DNS服务器IPv6地址请求或两者，则SMF应在PDU会话建立接受消息中包括扩展协议配置选项IE，包含一个或多个DNS服务器IPv4地址，一个或多个DNS服务器IPv6地址或两者。如果UE支持在协议配置选项中接收DNS服务器地址，并在PDU会话建立接受消息的扩展协议配置选项IE中接收一个或多个DNS服务器IPv4地址、一个或多个DNS服务器IPv6地址或两者，则UE应传递接收到的DNS服务器IPv4地址（如果有），和接收到的DNS服务器IPv6地址（如果有）发送到上层。
NOTE 22:    The received DNS server address(es) replace previously provided DNS server address(es), if any.
注22：收到的DNS服务器地址替换以前提供的DNS服务器地址（如果有）。
If the PDU session is established for IMS signalling and the UE has requested P-CSCF IPv6 address or P-CSCF IPv4 address, the SMF shall include P-CSCF IP address(es) in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message.
如果为IMS信令建立PDU会话，并且UE已请求P-CSCF IPv6地址或P-CSCF IPv4地址，则SMF应在PDU会话建立接受消息中的扩展协议配置选项中包括P-CSCF IP地址。
NOTE 23:    The P-CSCF selection functionality is specified in subclause 5.16.3.11 of 3GPP TS 23.501 [8].
注23:3GPP TS 23.501[8]的5.16.3.11节中规定了P-CSCF选择功能。
Upon receipt of the PDU SESSION ESTABLISHMENT ACCEPT message, if the UE included the PDU session pair ID in the PDU SESSION ESTABLISHMENT REQUEST message, the UE shall associate the PDU session with the PDU session pair ID. If the UE included the RSN in the PDU SESSION ESTABLISHMENT REQUEST message, the UE shall associate the PDU session with the RSN.
在收到PDU会话建立接受消息后，如果UE在PDU会话建立请求消息中包含PDU会话对ID，则UE应将PDU会话与PDU会话对ID相关联。如果UE在PDU会话建立请求消息中包含RSN，则UE应将PDU会话与RSN相关联。
If the UE supports EDC and the network allows the use of EDC, the SMF shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with the EDC usage allowed indicator. If the UE supports EDC and receives the EDC usage allowed indicator in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall indicate to upper layers that network allows the use of EDC.
如果UE支持EDC并且网络允许使用EDC，则SMF应在PDU会话建立接受消息中包括扩展协议配置选项，并带有EDC使用允许指示符。如果UE支持EDC并在PDU会话建立接受消息的扩展协议配置选项IE中接收到EDC使用允许指示符，则UE应向上层指示网络允许使用EDC。
If the UE supports EDC and the network requires the use of EDC, the SMF shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT ACCEPT message with the EDC usage required indicator. If the UE supports EDC and receives the EDC usage required indicator in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall indicate to upper layers that network requires the use of EDC.
如果UE支持EDC，并且网络需要使用EDC，则SMF应在PDU会话建立接受消息中包括扩展协议配置选项，并带有EDC使用要求指示符。如果UE支持EDC并在PDU会话建立接受消息的扩展协议配置选项IE中接收到EDC使用要求指示符，则UE应向上层指示网络需要使用EDC。
NOTE 24:    Handling of indication that network allows the use of EDC or that network requires the use of EDC is specified in 3GPP TS 23.548 [182].
注24:3GPP TS 23.548[182]规定了网络允许使用EDC或网络需要使用EDC的指示的处理。

空口日志： PDU session establishment accept

[0xB800]                 OTA LOG                  02:22:51.783             PDU session establishment accept PDU session establishment accept  1
02:22:51.783 [0xB800] PDU session establishment accept
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 = 194 (0xc2) (PDU session establishment accept)
nr5g_smm_msg
  pdu_session_estab_accept
    ssc_mode
      ssc_mode_val = 1 (0x1)
    pdu_session_type
      pdu_session_type = 3 (0x3) (IPv4v6)
    authorized_qos_rules
      num_recs = 1 (0x1)
      Qos_rule[0]
        qos_rule_id = 1 (0x1)
        rule_opcode = 1 (0x1) (Create new QoS rule)
        DQR = 1 (0x1)
        num_pkt_filter = 1 (0x1)
        pkt_filters[0]
          change_rule
            pkt_filter_dir = 2 (0x2) (uplink only)
            pkt_filter_id = 0 (0x0)
            num_comps = 1 (0x1)
            pkt_filters_comp_list[0]
              comp_type_id = 1 (0x1) (Match-all)
        rule_precedene_present = 1 (0x1)
        qos_rule_precedence = 255 (0xff)
        qfi_present = 1 (0x1)
        segregation = 0 (0x0)
        qfi = 1 (0x1)
    session_ambr
      length = 6 (0x6)
      session_ambr_dl_unit = 6 (0x6) (inc in multiple of 1 Mbps)
      session_ambr_dl = 2000 (0x7d0)
      session_ambr_ul_unit = 6 (0x6) (inc in multiple of 1 Mbps)
      session_ambr_ul = 1000 (0x3e8)
    _5gsm_cause_incl = 0 (0x0)
    pdu_addr_incl = 1 (0x1)
    pdu_addr
      length = 13 (0xd)
      si6lla = 0 (0x0)
      pdu_session_type = 3 (0x3)
      ipv6_addr[0] = 22 (0x16)
      ipv6_addr[1] = 105 (0x69)
      ipv6_addr[2] = 80 (0x50)
      ipv6_addr[3] = 248 (0xf8)
      ipv6_addr[4] = 254 (0xfe)
      ipv6_addr[5] = 28 (0x1c)
      ipv6_addr[6] = 208 (0xd0)
      ipv6_addr[7] = 21 (0x15)
      ipv4_addr[0] = 10 (0xa)
      ipv4_addr[1] = 0 (0x0)
      ipv4_addr[2] = 8 (0x8)
      ipv4_addr[3] = 155 (0x9b)
    rq_timer_incl = 0 (0x0)
    s_nssai_incl = 1 (0x1)
    s_nssai
      s_nssai_len = 1 (0x1)
      sst = 1 (0x1)
    always_on_pdu_session_ind_incl = 0 (0x0)
    mapped_eps_bearer_context_inc = 1 (0x1)
    mapped_eps_bearer_context
      num_bearer_context = 1 (0x1)
      bearer_context[0]
        eps_bearer_id = 5 (0x5)
        opcode = 1 (0x1) (Create new EPS bearer)
        E_bit = 1 (0x1)
        num_eps_params = 2 (0x2)
        eps_params[0]
          eps_params_id = 4 (0x4)
          bearer_context_params
            apn_ambr
              apn_ambr_dl = 254 (0xfe) (8640 kbps)
              apn_ambr_ul = 254 (0xfe) (8640 kbps)
              oct5_incl = 1 (0x1)
              apn_ambr_dl_ext = 226 (0xe2) (208 Mbps)
              oct6_incl = 1 (0x1)
              apn_ambr_ul_ext = 238 (0xee) (232 Mbps)
              oct7_incl = 1 (0x1)
              apn_ambr_dl_ext2 = 7 (0x7) (2008.640000 Mbps)
              oct8_incl = 1 (0x1)
              apn_ambr_ul_ext2 = 3 (0x3) (1008.640000 Mbps)
        eps_params[1]
          eps_params_id = 1 (0x1)
          bearer_context_params
            eps_qos
              qci = 9 (0x9) (QC9)
              oct4_incl = 0 (0x0)
              oct5_incl = 0 (0x0)
              oct6_incl = 0 (0x0)
              oct7_incl = 0 (0x0)
              oct8_incl = 0 (0x0)
              oct9_incl = 0 (0x0)
              oct10_incl = 0 (0x0)
              oct11_incl = 0 (0x0)
              oct12_incl = 0 (0x0)
              oct13_incl = 0 (0x0)
              oct14_incl = 0 (0x0)
              oct15_incl = 0 (0x0)
    eap_msg_incl = 0 (0x0)
    auth_qos_flow_desc_incl = 1 (0x1)
    qos_flow_desc
      num_qos_flow_desc = 1 (0x1)
      qos_flow_description[0]
        qfi = 1 (0x1)
        opcode = 1 (0x1) (Create new QoS flow description)
        e_bit = 1 (0x1)
        num_parameters = 2 (0x2)
        params[0]
          params_id = 7 (0x7)
          length = 1 (0x1)
          qos_flow_desc_params
            _5qi
              _5qi_value = 9 (0x9)
    ext_prot_config_incl = 1 (0x1)
    ext_prot_config
      ext = 1 (0x1)
      conf_prot = 0 (0x0)
      num_recs = 4 (0x4)
      prot_or_container[0]
        id = 32801 (0x8021) (IPCP)
        prot_or_container
          prot_len = 16 (0x10)
          ipcp_prot
            ipcp_prot_id = 3 (0x3) (CONF_NAK)
            identifier = 0 (0x0)
            rfc1332_conf_nak
              num_options = 2 (0x2)
              conf_options[0]
                type = 129 (0x81)
                rfc1877_primary_dns_server_add
                  length = 6 (0x6)
                  ip_addr = 3549004290 (0xd3898202) (211.137.130.2)
              conf_options[1]
                type = 131 (0x83)
                rfc1877_sec_dns_server_add
                  length = 6 (0x6)
                  ip_addr = 3549004306 (0xd3898212) (211.137.130.18)
      prot_or_container[1]
        id = 13 (0xd) (DNS Server IPv4 Address)
        prot_or_container
          prot_len = 4 (0x4)
          container
            container_contents[0] = 211 (0xd3)
            container_contents[1] = 137 (0x89)
            container_contents[2] = 130 (0x82)
            container_contents[3] = 2 (0x2)
      prot_or_container[2]
        id = 3 (0x3) (DNS Server IPv6 Address)
        prot_or_container
          prot_len = 16 (0x10)
          address
            addr = 0x240980702000f1100000000000000001 (2409:8070:2000:f110:0:0:0:1)
      prot_or_container[3]
        id = 3 (0x3) (DNS Server IPv6 Address)
        prot_or_container
          prot_len = 16 (0x10)
          address
            addr = 0x240980702000f0100000000000000001 (2409:8070:2000:f010:0:0:0:1)
    dnn_incl = 1 (0x1)
    dnn
      dnn_len = 6 (0x6)
      dnn_val[0] = 5 (0x5) (length)
      dnn_val[1] = 99 (0x63) (c)
      dnn_val[2] = 109 (0x6d) (m)
      dnn_val[3] = 100 (0x64) (d)
      dnn_val[4] = 116 (0x74) (t)
      dnn_val[5] = 106 (0x6a) (j)
    _5gsm_nwk_feature_support_incl = 0 (0x0)
    srv_plmn_rate_ctrl_incl = 0 (0x0)
    at_sss_container_incl = 0 (0x0)
    ctrl_plane_only_ind_incl = 0 (0x0)
    ip_hc_config_incl = 0 (0x0)
    ethernet_hc_config_incl = 0 (0x0)