The list below defines some of the key terms you should know when developing with RCS Business Messaging.
A
- A2P
- Application-to-person. An interaction between an application and a user, initiated by the application.
- agent
- A conversational representation of a brand, managed by a partner. Includes any interface users interact with and any code or infrastructure required to power the interaction.
B
- brand
- An organization or group represented by one or more agents.
C
- capabilities
- The features that a device supports.
- carousel
- A horizontal array of cards that the viewer can swipe left to right and select from.
- Cloud Pub/Sub
- A fully-managed real-time messaging service that allows you to send and receive messages between independent applications.
- conversation
- A series of messages between two parties over time.
D
- device
- A piece of hardware that can receive messages, regardless of make, vendor, or form factor.
- Dialogflow
- Google's natural language understanding (NLU) developer tool for building conversational experiences for the Google Assistant. It uses machine learning to understand the intent and context of what a user says in order to respond in the most useful way.
E
- event
- An occasion that conveys information, such as a delivery receipt.
J
- Jibe documentation
- The documentation or other materials for the use of the Jibe Services as may be provided and updated by Jibe from time to time. The Jibe documentation is currently located at [http://docs.jibemobile.com](http://docs.jibemobile.com){: .external }.
M
- message
- A discrete set of content (text, media, etc.) sent from one party to another.
- MSISDN
- Mobile Station International Subscriber Directory Number. A number used to identify a device internationally. A phone number.
N
- Natural Language Understanding
- Advanced natural language processing that "reads" the content of the message. Used for entity detection, topic classification, sentiment detection, and more.
- NLU
- Natural Language Understanding.
P
- P2A
- Person-to-application. An interaction between an application and a user, initiated by the user.
- partner
- An individual or group that consumes APIs to create, manage, or operate one or more agents. May be an aggregator, a customer service provider, a brand, a carrier, or any other type of organization or individual.
R
- RBM
- RCS Business Messaging.
- RCS
- Rich Communications Services.
- RCS Business Messaging
- A developer platform that lets you communicate with users over RCS.
- rich card
- A rectangular unit that can contain an image, video thumbnail, text, interactive links, etc. Can be presented individually or in a carousel.
- Rich Communications Services
- A standards-based communication protocol that brings rich messaging functionality to carrier networks.
- record level detail
- In the context of RBM billing reports, the information exchanged between agents and end users (identified by MSISDN) and includes the date, time, data transfer, direction, type (such as text-based message, rich cards, file transfer, spam reports, etc.), and billing session information pertaining to such events, but not message content.
S
- session
- A time-bound grouping of interactions, such as messages sent in a conversation.
- SIP
- Session Initiation Protocol.
- suggested action
- A suggestion to trigger an on-device action.
- suggested reply
- A suggestion to reply with predefined text.
- summary billing information
- In the context of RBM billing reports, an agent’s billing session information without end user identifiers, such as the date, time, type (such as A2P Single Message or A2P Conversation), duration, size (in terms of data transferred), or depth (in terms of messages sent) of sessions.
U
- Universal Profile
- A common set of configuration parameters and functionality for RCS deployments, which is published by the GSMA and accepted by Jibe and intended to be the single global implementation for RCS.