2.15 Personal Network Blacklists (PNB) / 个人网络黑名单（PNB）

With this optional RCS feature that is enabled using the PNB MANAGEMENT configuration parameter (see section A.1.3), the RCS user may be provided with the possibility to manage their Personal Network Blacklist (PNB), in order to either prevent receiving undesired communications, messages or media.
通过使用PNB MANAGEMENT配置参数（参见第A.1.3节）启用该可选的RCS特征，可以为RCS用户提供管理其个人网络黑名单（PNB）的可能性，以便防止接收不期望的通信，消息或媒体。

The PNB feature relies on the Shared XDMS that is also used for SPI (see section 3.7). New lists are pre-defined in the Shared List XDMS as follows:
PNB功能依赖于也用于SPI的共享XDMS（参见第3.7节）。 新列表在共享列表XDMS中预定义如下：

  • “rcs_pnb_chat_blockedusers”: this list contains all blocked senders for chat
    “rcs_pnb_chat_blockedusers”：此列表包含所有已阻止的聊天发件人
  • “rcs_pnb_ft_blockedusers”: this list contains all blocked senders for file transfer
    “rcs_pnb_ft_blockedusers”：此列表包含文件传输的所有阻止的发件人
  • “rcs_pnb_standalone_blockedusers”: this list contains all blocked senders for standalone messages
    “rcs_pnb_standalone_blockedusers”：此列表包含独立消息的所有已阻止的发件人
  • “rcs_pnb_outchat_blockedusers”: this list contains all blocked recipients for chat
    “rcs_pnb_outchat_blockedusers”：此列表包含聊天的所有已阻止的收件人
  • “rcs_pnb_outft_blockedusers”: this list contains all blocked recipients for file transfer
    “rcs_pnb_outft_blockedusers”：此列表包含文件传输的所有已阻止的收件人
  • “rcs_pnb_outstandalone_blockedusers”: this list contains all blocked recipients for standalone messages
    “rcs_pnb_outstandalone_blockedusers”：此列表包含独立邮件的所有已阻止的收件人

2.15.1 RCS Applicability / RCS适用性

The enforcement of the PNB feature is performed by the Blacklist Policy Enforcement Function (BPEF) that could both:
PNB特征的实施由黑名单策略执行功能（BPEF）执行，其可以：

  • Be implemented as part of the relevant RCS application server (e.g. RCS Messaging Server), or,
    作为相关RCS应用服务器（例如RCS消息服务器）的一部分实现，或者，
  • In a separate server, which enforces the policy.
    在一个单独的服务器，强制执行策略。

The PNB feature applies only to the following RCS services:
PNB功能仅适用于以下RCS服务：

  • Standalone messaging (see section 3.2)
    独立消息传递（见第3.2节）
  • 1-to-1 chat (see section 3.3)
    1对1聊天（见第3.3节）
  • File transfer (see section 3.5).
    文件传输（见第3.5节）。

Taking into account the supported features, the BPEF can be completely collocated with the Messaging Server.
考虑到支持的功能，BPEF可以与消息传递服务器完全并置。

The PNB feature can be enabled or disabled. When enabled:
可以启用或禁用PNB功能。 启用时：

  • The BPEF shall apply triggers for checking the RCS user’s PNB, during the relevant RCS service traffic, on both originating and terminating traffic.
    BPEF应当在相关RCS服务业务期间在始发和终止业务上应用触发器以检查RCS用户的PNB。
  • RCS clients shall be configured with the PNB MANAGEMENT parameter (described in Annex A, section A.1.3), so it is possible to handle the PNB configuration from the client.
    RCS客户端应配置PNB管理参数（在附件A，A.1.3节中描述），因此可以处理来自客户端的PNB配置。

The functionality provided by BPEF is summarized below:
BPEF提供的功能总结如下：

  • On originating side:
    在发起端：
    • Checks the outgoing blacklists for the respective request (i.e. chat, file transfer or standalone messaging) and if the recipient is found in the applicable list (e.g. rcs_pnb_outchat_blockedusers for chat), the request is rejected.
      检查相应请求（即聊天，文件传输或独立消息传递）的传出黑名单，如果在适用列表中找到收件人（例如，用于聊天的rcs_pnb_outchat_blockedusers），则拒绝该请求。
  • On the terminating side:
    在接收端：
    • Checks the blacklists for the respective request (i.e. chat, file transfer or standalone messaging) and if the sender is found on the pertaining list (e.g. chat_blockedusers for chat), the request is rejected.
      检查相应请求的黑名单（即聊天，文件传输或独立消息传递），如果在相关列表中找到发件人（例如chat_blockedusers聊天），请求将被拒绝。
    • If supporting the Common Message Store feature and if allowed by local server policy, the Messaging Server stores the blocked message/chat/File Transfer event with the metadata content following Conversation History format as per [RCS-CPM-MSGSTOR-ENDORS].
      如果支持公共消息存储功能，并且如果本地服务器策略允许，消息服务器将按照[RCS-CPM-MSGSTOR-ENDORS]的对话历史格式存储阻止的消息/聊天/文件传输事件与元数据内容。

2.15.2 PNB management / PNB管理

The PNB can be updated in any of the following ways:
PNB可以以以下任何方式更新：

  1. The user performs the management of the lists from their RCS client by adding or deleting users in the list entries of the Shared List XDMS using XCAP, or
    用户通过使用XCAP在共享列表XDMS的列表条目中添加或删除用户来从他们的RCS客户端执行列表的管理，或者
  2. The RCS client supports the user, by prompting him/her to choose upon a rejection (e.g. chat, group chat or file transfer) to add the originator in the respective blacklist.
    RCS客户端通过提示他/她选择拒绝（例如聊天，群聊或文件传输）以将发起者添加到相应的黑名单中来支持用户。

Once the user rejected a Chat invitation, or a File Transfer, the RCS client UI may prompt them to select whether the rejection is permanent, or if it is a onetime rejection. A permanent rejection will trigger an update in the user’s respective black list, by adding the originator in that list.
一旦用户拒绝聊天邀请或文件传输，RCS客户端UI可以提示他们选择拒绝是否是永久的，或者是否是一次拒绝。 永久拒绝将通过在该列表中添加发起者来触发用户各自的黑名单中的更新。

Other options may be possible, such as allowing the RCS user to add other users in their PNBs from the viewing of the Conversation History.
其他选项也是可能的，例如允许RCS用户从对话历史的观看中添加其PNB中的其他用户。

Regardless of the trigger for the PNB update by the RCS Client, when such update needs to be done in the network, the RCS Client shall issue an XCAP request as per [XDM2.0_Core] procedures and as described in section 2.14.2.
不管RCS客户端对PNB更新的触发，当这种更新需要在网络中完成时，RCS客户端将根据[XDM2.0_Core]过程发出XCAP请求，如第2.14.2节所述。

2.15.2.1 Authorising PNB management requests / 授权PNB管理请求

The authorisation of the PNB management requests (get, update, delete) is done as described in section 2.14.2.2.
PNB管理请求（获取，更新，删除）的授权如2.14.2.2节所述完成。

results matching ""

    No results matching ""