3GPP TS 29244-g30 中英文对照 | 5.4.10 Charging

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

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

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

5.4.10 Charging 计费

For EPC, the charging requirements for online and offline charging in the PS domain specified in 3GPP TS 32.251 [17] shall be preserved with a split SGW, PGW and TDF architecture.

对于EPC，PS域中在线和离线计费的计费要求应采用分离式SGW、PGW和TDF架构。

For 5GC, the charging requirements for online and offline charging in the 5G data connectivity domain are specified in 3GPP TS 32.255 [45].

对于5GC，5G数据连接域中在线和离线计费的计费要求在3GPP TS 32.255[45]中规定。

Charging is supported by the CP function by activating in the UP function the measurement and reporting of the accumulated usage of network resources per:

CP功能通过在UP功能中激活网络资源累计使用量的测量和报告来支持计费：

- for EPC:

- IP-CAN bearer, for an SGW;

-IP-CAN承载，用于SGW；

- IP-CAN bearer, IP-CAN session and/or individual or group of service data flows, for a PGW;

-用于PGW的IP-CAN承载、IP-CAN会话和/或单个或组业务数据流；

- TDF session and/or individual or group of applications, for a TDF;

-TDF会话和/或单个或组应用程序，用于TDF；

- for 5GC:

- PDU session and/or individual or group of service data flows, for an SMF;

-SMF的PDU会话和/或单个或业务数据流组；

- QoS Flow, for an SMF.

-SMF的QoS流。

See clauses 5.3 and 7.8.4 of 3GPP TS 23.214 [2].

参见3GPP TS 23.214 [2]的第5.3和7.8.4节。

The CP function shall control the usage measurement and reporting in the UP function by:

CP功能应通过以下方式控制UP功能中的使用测量和报告：

- creating the necessary PDR(s) to represent the service data flow, application, bearer or session, if not already existing;

-创建必要的PDR以表示业务数据流、应用程序、承载或会话（如果尚未存在）；

- creating URR(s) for each Charging Key, combination of Charging Key and Service ID, or combination of Charging Key, Sponsor ID and Application Service Provider Id;

-为每个Charging Key、Charging Key和Service ID的组合或Charging Key、Sponsor ID和Application Service Provider ID的组合创建URR；

- associating the URR(s) to the relevant PDRs defined for the PFCP session, for usage reporting at IP-CAN bearer, IP-CAN session, TDF session, SDF or application level.

-将URR与为PFCP会话定义的相关PDR相关联，以便在IP-CAN承载、IP-CAN会话、TDF会话、SDF或应用程序级别进行使用情况报告。

For online charging, the CP function shall provision the URR with the Volume (or Time) Quota, and with the Volume (or Time) Quota if a quota threshold was received from the OCS, as specified in clause 5.2.2.2. Besides, when the OCS provides a final quota and requests to redirect the traffic towards a redirect destination when exhausing this quota, the CP function shall redirect the traffic towards a redirect destination as specified in clause 5.4.7 upon being notified that the final quota has been reached; to permit HTTP traffic redirection, the UP function should have at least one HTTP packet, e.g. the UP function may store one packet when reaching the Volume (or Time) Quota. An example call flow is depicted in Annex C.2.1.1.

对于在线计费，CP功能应向URR提供Volume Quota，如果从OCS接收到配额阈值，则提供Volume Quota。另外，当OCS提供一个最终配额，并在使用该配额时请求将流量重定向到重定向目的地时，CP功能在收到已达到最终配额的通知时，应将流量重定向到重定向目的地；为了允许HTTP流量重定向，UP功能应至少有一个重定向目的地HTTP包，例如UP函数在达到Volume Quota时可以存储一个包。

To avoid the risk of signalling storms between the CP and UP functions at times of tariff change, the CP function may include the Monitoring Time IE and zero or more Additional Monitoring IEs in the URR and set it to the time of tariff change to request the UP function to report separately the resource usage before and after the time of tariff change (see e.g. clause 6.3.7.1 of 3GPP TS 32.299 [18]).

为了避免在定价变化时CP和UP功能之间出现信令风暴的风险，CP功能可以包括URR中的Monitoring Time IE和零个或多个Additional Monitoring IE，并将其设置为定价变化时间，以请求UP功能分别报告定价变化时间前后的资源使用情况。