new_releases 更新：查看
版本说明，了解新功能和产品动态。
RCS Business Messaging 术语表
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
下文列出了您在使用 RCS 商务消息功能进行开发时应了解的一些关键术语的定义。
A
- A2P
- 申请人。应用与用户之间的互动，由应用发起。
- 代理
- 对话式的品牌代表，由合作伙伴管理。包括用户互动时接触到的所有界面以及为互动提供支持所需的所有代码或基础架构。
B
- brand
- 由一个或多个代理代表的组织或群组。
C
- capabilities
- 设备支持的功能。
- 轮播界面
- 一个横向排列的卡片数组，观看者可以从中左右滑动并选择。
- Cloud Pub/Sub
- 一种全代管式实时消息传递服务，可让您在独立的应用之间发送和接收消息。
- 个会话
- 两方之间在一段时间内发送的一系列消息。
D
- 设备
- 一种可以接收消息的硬件，无论品牌、供应商或外形规格如何。
- Dialogflow
- Google 的自然语言理解 (NLU) 开发者工具，用于为 Google 助理构建对话式体验。它使用机器学习技术来理解用户所说内容的意图和上下文，以便以最实用的方式做出回应。如需将 Dialogflow 与 RBM 代理集成，请参阅 Dialogflow 集成。
E
- 事件
- 传达信息（例如送货收据）的场合。
G
- Google RCS 平台文档
- Google 不时提供和更新的有关使用 Google RCS 服务的文档或其他材料。Google RCS 文档位于 http://docs.jibemobile.com。
M
- 消息
- 一组由一方发送给另一方的离散内容（文本、媒体内容等）。
- MSISDN
- 移动台国际订阅者目录编号。用于在国际上识别设备的编号。电话号码。
否
- 自然语言理解
- “读取”消息内容的高级自然语言处理。用于实体检测、主题分类、情感检测等。
- NLU
- 自然语言理解。
P
- P2A
- 个人与应用。应用与用户之间的互动，由用户发起。
- 合作伙伴
- 使用 API 创建、管理或操作一个或多个代理的个人或群组。可以是集合商家、客户服务提供商、品牌、运营商或任何其他类型的组织或个人。
R
- RBM
- RCS Business Messaging
。
- RCS
- 富通讯解决方案。
- RCS Business Messaging
- 一种开发者平台，可让您通过 RCS 与用户进行通信。
- 声誉得分
- 代理的总体表现，基于用户反馈和其他信号（包括垃圾内容举报）计算得出。
- 复合信息卡
- 一个矩形单元，可包含图片、视频缩略图、文本以及建议的回复和建议的操作按钮。可以单独显示，也可以在轮播界面中显示。
- 富通讯解决方案
- 一种基于标准的通信协议，可为运营商网络提供丰富的消息功能。
- 记录级详细信息
- 在 RBM 结算报告中，代理与最终用户（通过 MSISDN 标识）之间交换的信息，包括日期、时间、数据传输、方向、类型（例如基于文本的消息、富媒体卡片、文件传输、垃圾内容报告等）以及与此类事件相关的结算会话信息，但不包括消息内容。
S
- 安全浏览
- 这项 Google 服务可识别潜在危险的网站和下载内容，并向用户发出警告。该功能会持续更新不安全网站的列表，其中包括已知存在恶意软件、钓鱼式攻击和垃圾软件的网站。安全浏览保护功能不仅适用于网络浏览器，还适用于 Gmail 和 Google 搜索等其他 Google 产品，以及 Google 信息和 iOS 等平台，可帮助保护用户在各种应用和设备中的安全。
- session
- 互动（例如对话中发送的消息）的时间限定分组。
- SIP
- 会话发起协议。
- 建议的操作
- 用于触发设备端操作的建议。
- 建议的回复
- 使用预定义文本进行回复的建议。
- 结算信息摘要
- 在 RBM 结算报告中，这是代理的结算会话信息，不含最终用户标识符。它可能包括会话的日期、时间、结算事件类型（例如单个消息或 A2P 对话）、时长、大小（以传输的数据量为单位）和深度（以发送的消息数为单位）。
T
- 流量限制
- 代理根据声誉等级每月可为每位用户发起的对话数量。
U
- 通用配置文件
- 一组适用于 RCS 部署的通用配置参数和功能，由 GSMA 发布并获得 Google 认可，旨在成为 RCS 的唯一全球实现。
W
- 网络钩子
- 合作伙伴指定的网址，RBM 平台会在此网址上发布消息和事件。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-04-03。
[null,null,["最后更新时间 (UTC)：2025-04-03。"],[[["\u003cp\u003eRCS Business Messaging involves interactions between applications and users (A2P) or vice versa (P2A), facilitated by agents that represent brands.\u003c/p\u003e\n"],["\u003cp\u003eKey elements in RCS Business Messaging include messages, conversations, carousels, and rich cards, which enhance user interaction.\u003c/p\u003e\n"],["\u003cp\u003eThe platform uses Natural Language Understanding (NLU) and services like Dialogflow to enhance conversational capabilities, understanding user intent.\u003c/p\u003e\n"],["\u003cp\u003ePartners manage and operate agents, while brands are the organizations represented through these agents within the RCS Business Messaging ecosystem.\u003c/p\u003e\n"],["\u003cp\u003eWebhooks and events are crucial for real-time communication, and Google's Safe Browsing service ensures the safety of users interacting with this platform.\u003c/p\u003e\n"]]],[],null,["# RCS Business Messaging Glossary\n\nThe following list defines some of the key terms you should know when developing\nwith RCS Business Messaging.\n\nA\n---\n\nA2P\n: Application-to-person. An interaction between an application and a user,\n initiated by the application.\n\nagent\n: A conversational representation of a brand, managed by a partner. Includes any\n interface users interact with and any code or infrastructure required to power\n the interaction.\n\nB\n---\n\nbrand\n: An organization or group represented by one or more agents.\n\nC\n---\n\ncapabilities\n: The features that a device supports.\n\ncarousel\n: A horizontal array of cards that the viewer can swipe left to right and select\n from.\n\nCloud Pub/Sub\n: A fully-managed real-time messaging service that lets you send and receive\n messages between independent applications.\n\nconversation\n: A series of messages between two parties over time.\n\nD\n---\n\ndevice\n: A piece of hardware that can receive messages, regardless of make, vendor, or\n form factor.\n\nDialogflow\n: Google's natural language understanding (NLU) developer tool for building\n conversational experiences for the Google Assistant. It uses machine learning to\n understand the intent and context of what a user says in order to respond in the\n most useful way. To integrate Dialogflow with your RBM agent, refer to\n [Dialogflow integration](/business-communications/rcs-business-messaging/guides/integrate/df).\n\nE\n---\n\nevent\n: An occasion that conveys information, such as a delivery receipt.\n\nG\n---\n\nGoogle RCS platform documentation\n: The documentation or other materials for the use of the Google RCS Services as\n may be provided and updated by Google from time to time. The Google RCS\n documentation is located at \u003chttp://docs.jibemobile.com\u003e.\n\nM\n---\n\nmessage\n: A discrete set of content (text, media, etc.) sent from one party to another.\n\nMSISDN\n: Mobile Station International Subscriber Directory Number. A number used to\n identify a device internationally. A phone number.\n\nN\n---\n\nNatural Language Understanding\n: Advanced natural language processing that \"reads\" the content of the message.\n Used for entity detection, topic classification, sentiment detection, and more.\n\nNLU\n: Natural Language Understanding.\n\nP\n---\n\nP2A\n: Person-to-application. An interaction between an application and a user,\n initiated by the user.\n\npartner\n: An individual or group that consumes APIs to create, manage, or operate one\n or more agents. May be an aggregator, a customer service provider, a brand, a\n carrier, or any other type of organization or individual.\n\nR\n---\n\nRBM\n: RCS Business Messaging.\n\nRCS\n: Rich Communications Services.\n\nRCS Business Messaging\n: A developer platform that lets you communicate with users over RCS.\n\nreputation score\n: An agent's overall performance based on user feedback and other signals,\n including spam reports.\n\nrich card\n: A rectangular unit that can contain an image, a video thumbnail, text, and\n suggested reply and suggested action buttons. Can be presented individually or\n in a carousel.\n\nRich Communications Services\n: A standards-based communication protocol that brings rich messaging\n functionality to carrier networks.\n\nrecord level detail\n: In the context of RBM billing reports, the information exchanged between\n agents and end users (identified by MSISDN) and includes the date, time, data\n transfer, direction, type (such as text-based message, rich cards, file\n transfer, spam reports, etc.), and billing session information pertaining to\n such events, but not message content.\n\nS\n---\n\nSafe Browsing\n: A Google service that identifies and warns users about potentially dangerous\n websites and downloads. It works by maintaining a constantly updated list of\n unsafe sites, including those known for malware, phishing, and unwanted\n software. [Safe Browsing](https://safebrowsing.google.com/)\n protection extends beyond web browsers to other Google products like Gmail and\n Search, as well as platforms like Google Messages and iOS, helping to safeguard\n users across various applications and devices.\n\nsession\n: A time-bound grouping of interactions, such as messages sent in a conversation.\n\nSIP\n: Session Initiation Protocol.\n\nsuggested action\n: A suggestion to trigger an on-device action.\n\nsuggested reply\n: A suggestion to reply with predefined text.\n\nsummary billing information\n: In the context of RBM billing reports, this is an agent's billing session\n information without end user identifiers. It may include the date, time, billing\n event type (like a Single Message or A2P Conversation), duration, size\n (in terms of data transferred), and depth (in terms of messages sent) of\n sessions.\n\nT\n---\n\ntraffic limit\n: The number of conversations the agent can initiate per user per month based on\n the reputation level.\n\nU\n---\n\nUniversal Profile\n: A common set of configuration parameters and functionality for RCS deployments,\n which is published by the GSMA and accepted by Google and intended to be the\n single global implementation for RCS.\n\nW\n---\n\nWebhook\n: A partner-specified URL where the RBM platform posts\n [messages](/business-communications/rcs-business-messaging/guides/build/messages/receive)\n and\n [events](/business-communications/rcs-business-messaging/guides/build/events)."]]
