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
- 行動台國際訂戶目錄號碼。用於在國際上識別裝置的號碼。電話號碼。
否
- 自然語言理解
- 進階自然語言處理,可「讀取」訊息內容。用於實體偵測、主題分類、情緒偵測等。
- 自然語言理解
- 自然語言理解。
P
- P2A
- 人與應用程式。由使用者啟動的應用程式與使用者互動。
- 合作夥伴
- 使用 API 建立、管理或操作一或多個服務的個人或群組。可能是匯入網站、客戶服務供應商、品牌、電信業者,或任何其他類型的機構或個人。
R
- RBM
- RCS Business Messaging。
- RCS
- 進階通訊解決方案。
- RCS Business Messaging
- 開發人員平台,可讓您透過 RCS 與使用者通訊。
- 信譽分數
- 根據使用者意見回饋和其他信號 (包括垃圾內容報告) 評估代理的整體表現。
- 複合式資訊卡
- 矩形單元,可包含圖片、影片縮圖、文字,以及建議回覆和建議動作按鈕。可單獨顯示,或在輪轉介面中顯示。
- 進階通訊解決方案
- 這是一種以標準為基礎的通訊協定,可為電信業者網路提供豐富的訊息功能。
- 記錄層級詳細資料
- 在 RBM 結帳報表中,代理人和使用者 (以 MSISDN 識別) 之間交換的資訊,包括日期、時間、資料傳輸、方向、類型 (例如文字訊息、互動式資訊卡、檔案傳輸、垃圾訊息回報等),以及與這類事件相關的結帳工作階段資訊,但不包含訊息內容。
S
- 安全瀏覽
- Google 服務,可識別可能有風險的網站和下載內容,並向使用者發出警告。這項服務會持續更新不安全網站清單,包括惡意軟體、網路釣魚和垃圾軟體網站。安全瀏覽防護功能不僅適用於網路瀏覽器,還可用於 Gmail、Google 搜尋等其他 Google 產品,以及 Google 訊息和 iOS 等平台,有助於保護使用者在各種應用程式和裝置上的安全。
- 工作階段
- 以時間為限制的互動群組,例如在對話中傳送的訊息。
- SIP
- 對話啟動協定。
- 建議的動作
- 建議觸發裝置端動作。
- 建議回覆
- 建議使用預先定義的文字回覆。
- 帳單資訊摘要
- 在 RBM 結帳報表中,這是代理人的結帳工作階段資訊,不含使用者 ID。可能包含日期、時間、帳單事件類型 (例如單一訊息或 A2P 對話)、持續時間、大小 (以傳輸的資料為準) 和深度 (以傳送的訊息為準)。
T
- 流量限制
- 服務專員每個月可與每位使用者進行對話的次數 (視信譽等級而定)。
U
- 通用個人資料
- 一組適用於 RCS 部署作業的通用設定參數和功能,由 GSMA 發布並獲得 Google 認可,旨在成為 RCS 的單一全球實作項目。
W
- Webhook
- 合作夥伴指定的網址,RBM 平台會在該網址發布訊息和事件。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-04-03 (世界標準時間)。
[null,null,["上次更新時間: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)."]]