3GPP TS 29244-g30 中英文对照 | 6.3.3 PFCP Session Modification Procedure

学习5G知识，势必要去阅读相关的技术标准，而纯英文的标准协议对于初学者来说是个门槛。

个人在学习5G标准3GPP TS 29244-g30过程中，也发现google的机器翻译实在晦涩难懂，所以个人在借助百度翻译（中国人更懂中文）的同时，人工对每句话进行了校对。

在自己学习的同时，也将翻译内容分享给给广大网友。由于个人能力有限，翻译不到位的地方还请各位网友们指正。

6.3.3 PFCP Session Modification Procedure PFCP会话修改程序

6.3.3.1 General

The PFCP Session Modification procedure shall be used to modify an existing PFCP session, e.g. to configure a new rule, to modify an existing rule, to delete an existing rule.

PFCP Session Modification程序应用于修改现有PFCP会话，例如配置新规则、修改现有规则、删除现有规则。

6.3.3.2 CP Function behaviour CP功能行为

The CP function initiates the PFCP Session Modification procedure to modify an existing PFCP session, e.g. triggered by a modification of PDN connection, IP CAN session or TDF session.

CP功能启动PFCP Session Modification程序，以修改现有的PFCP会话，例如由修改PDN连接、IP CAN会话或TDF会话触发。

The CP function shall:

CP功能应：

- include a complete PDI if the PDI in the existing PDR is to be updated;

-如果要更新现有PDR中的PDI，则包括完整的PDI；

- remove locally the reference to a rule in the PDRs when the related Rule is deleted;

-当相关Rule被删除时，本地删除对PDRs中规则的引用；

- provide all the new, updated or deleted Rules. The Updated Rules shall contain only the information which are changed, added and/or deleted.

-提供所有新的、更新的或删除的Rule。Updated Rule应仅包含更改、添加和/或删除的信息。

The CP function shall not include multiple updates in a PFCP Modification Request message, e.g. Create PDR, Update PDR and Remove PDR, for the same rule identified by the Rule ID.

CP功能不应在PFCP Modification Request消息中包含多个更新，例如，对于Rule ID标识的同一规则，Create PDR、Update PDR和Remove PDR。

When the CP function receives a PFCP Session Modification Response with the cause "success" it shall continue with the procedure which has initiated the PFCP Session Modification procedure.

当CP功能收到原因为“success”的PFCP Session Modification Response时，应继续启动PFCP Session Modification程序的程序。

6.3.3.3 UP Function Behaviour UP功能行为

When the UP function receives a PFCP Session Modification Request it shall:

当UP功能收到PFCP Session Modification Request时，它应：

- send the PFCP Session Modification Response message with a rejection cause value set to "Session context not found" if the F-SEID included in the PFCP Session Modification Request message is unknown;

-如果PFCP Session Modification Request消息中包含的F-SEID未知，则发送拒绝原因值设置为“Session context not found”的PFCP Session Modification Response消息；

- reject a modification request which would relate to a rule not existing in the UP function;

-拒绝与UP功能中不存在的规则相关的修改请求；

- discard any updates on the PFCP session context included in the PFCP Session Modification Request message if the request is rejected and send a PFCP Session Modification Response with an appropriate error cause together with additional information e.g. indicating the first Rule ID of the Rule causing the error. In this case, the UP function shall continue with the existing PFCP session context for the PFCP session as if the PFCP Session Modification Request had not been received;

-如果请求被拒绝，则放弃对PFCP Session Modification Request消息中包含的PFCP会话上下文的任何更新，并发送带有适当错误原因的PFCP Session Modification Response以及附加信息，例如，指示导致错误的Rule的第一个Rule ID。在这种情况下，UP功能应继续使用PFCP会话的现有PFCP会话上下文，就像没有收到PFCP Session Modification Request一样；

- remove all rules identified by a Rule ID to be removed and remove the Rule ID from the PDR(s) from where they are referenced;

-删除由要删除的Rule ID标识的所有规则，并从引用规则的PDR中删除Rule ID；

- send the PFCP Session Modification Response with an acceptance cause value if all the requested modifications are accepted and performed successfully.

-如果所有请求的修改都被接受并成功执行，则发送带有接受原因值的PFCP Session Modification Response。