Glossary

To ensure clear communication during integration, this document lists specific terms and concepts commonly used in the TiRTC AI Chat integration process.

Basic Concepts

• TiRTC AI Chat A real-time voice interaction service built on Tange's underlying TiRTC X technology. It allows IoT devices and cloud-based AI agents to exchange two-way audio, video, captions, and control events over a single low-latency connection.

• Application Server The backend system developed and maintained by the customer. It handles end-user device management, plan authorization, and obtains credentials required for device-to-cloud connections via Tange's server API.

• Device IoT hardware or terminal applications integrated with the TiRTC SDK, such as AI toys, smart cameras, and robots. It connects to the Tange platform over the network to send audio uplinks and receive voice downlinks.

Identity and Authentication

• Server Credentials (AccessKey/SecretKey) Also known as AK/SK, these are issued by the Tange platform to customer developers and must only be stored on the application server. They are used for TGV1-HMAC-SHA256 signature verification when calling server APIs (e.g., requesting a device connection Token) and must never be sent to or hardcoded into terminal devices.

• Connection Credentials (peer_id / Token) Short-lived access credentials obtained by the application server from the Tange platform. They consist of a peer_id (connection target descriptor) and a Bearer token.

  • Business Token: Typically refers to the login or authorization token issued by your application server to your end users.
  • TiRTC-X Token (or Connection Token): The short-lived encrypted string returned by the platform, specifically used by the device for TiRtcWhipConnect.

Roles and Sessions

• Agent / Role The AI configuration that executes dialogue logic in the cloud. It defines the large language model prompt, welcome message, voice, and any knowledge bases or action capabilities used during the conversation.
• role_id The globally unique identifier for an AI agent role. It is required when the application server requests connection credentials and when the device initiates a session (start_session).
• session_id A unique session ID returned by the Tange platform after a successful start_session. It is used to identify a specific interaction round for log tracing, troubleshooting, or billing.

Media and Signaling

• WHIP (WebRTC-HTTP Ingestion Protocol) An HTTP-based WebRTC signaling protocol. TiRTC AI Chat uses it as the standard handshake protocol for establishing the underlying media channel between the device and the platform.

• Command Channel A low-latency two-way data channel established over the underlying media channel (such as DataChannel). Handshakes, interruptions, captions, and device capability calls during AI conversations are transmitted on this channel. The reserved developer command word is agreed upon as 0x2100.

• VAD (Voice Activity Detection) Determines whether someone is speaking in the current audio stream. The Tange cloud runs cloud-based VAD for more precise interruption and turn-taking. The device does not necessarily need to run local VAD, or it can perform basic silence elimination (with caution to avoid truncating speech).