tencent cloud

Tencent Real-Time Communication

Release Notes and Announcements
Release Notes
Recent Product Announcement
TRTC Live (TUILiveKit) Product Launch Announcement
TRTC Conference Official Editions Launched
The commercial version of Conference is coming soon
Terms and Conditions Applicable to $9.9 Starter Package
Rules for the "First Subscription $100 Discount" Promotion
Announcement on the Start of Beta Testing for Multi-person Audio and Video Conference
TRTC Call Official Editions Launched
License Required for Video Playback in New Version of LiteAV SDK
TRTC to Offer Monthly Packages
Product Introduction
Overview
Concepts
Features
Strengths
Use Cases
Performance Statistics
Tencent RTC Quickplay: Experience Ultimate Real-Time Audio and Video Interaction!
Purchase Guide
Billing Overview
Free Minutes
Monthly subscription
Pay-as-you-go
TRTC Overdue and Suspension Policy
FAQs
Refund Instructions
User Tutorial
Free Demo
Call
Overview
Activate the Service
Run Demo
Integration
Offline Call Push
Conversational Chat
On-Cloud Recording
AI Noise Reduction
UI Customization
Calls integration to Chat
Additional Features
No UI Integration
Server APIs
Client APIs
Solution
ErrorCode
Release Notes
FAQs
Conference
Overview(TUIRoomKit)
Activate the Service (TUIRoomKit)
Run Demo(TUIRoomKit)
Integration(TUIRoomKit)
Screen Sharing (TUIRoomKit)
Schedule a meeting (TUIRoomKit)
In-meeting Call (TUIRoomKit)
UI Customization(TUIRoomKit)
Virtual Background (TUIRoomKit)
Conference Control (TUIRoomKit)
Cloud Recording (TUIRoomKit)
AI Noise Reduction (TUIRoomKit)
In-Conference Chat (TUIRoomKit)
Robot Streaming (TUIRoomKit)
Enhanced Features (TUIRoomKit)
Client APIs (TUIRoomKit)
Server APIs (TUIRoomKit)
FAQs (TUIRoomKit)
Error Code (TUIRoomKit)
SDK Update Log (TUIRoomKit)
Live
Billing of Video Live Component
Overview
Activating the Service (TUILiveKit)
Run Demo
No UI Integration
UI Customization
Live Broadcast Monitoring
Video Live Streaming
Voice Chat Room
Advanced Features
Client APIs
Server APIs
Error Codes
Release Notes
FAQs
RTC Engine
Activate Service
SDK Download
API Examples
Usage Guidelines
API Reference Manual
Advanced Features
AI Integration
Overview
Configure MCP Server
Install Skills
Integration Guide
FAQ
RTC RESTFUL API
History
Introduction
API Category
Room Management APIs
Stream mixing and relay APIs
On-cloud recording APIs
Data Monitoring APIs
Pull stream Relay Related interface
Web Record APIs
AI Service APIs
Cloud Slicing APIs
Cloud Moderation APIs
Making API Requests
Call Quality Monitoring APIs
Usage Statistics APIs
Data Types
Appendix
Error Codes
Console Guide
Application Management
Package Management
Usage Statistics
Monitoring Dashboard
Development Assistance
Solution
Real-Time Chorus
FAQs
Migration Guide
Billing
Features
UserSig
Firewall Restrictions
How to Downsize Installation Package
Android and iOS
Web
Flutter
Electron
TRTCCalling for Web
Audio and Video Quality
Others
Legacy Documentation
RTC RoomEngine SDK(Old)
Integrating TUIRoom (Web)
Integrating TUIRoom (Android)
Integrating TUIRoom (iOS)
Integrating TUIRoom (Flutter)
Integrating TUIRoom (Electron)
TUIRoom APIs
On-Cloud Recording and Playback (Old)
RTC Analytics Monthly Packages (Previous Version)
Protocols and Policies
Compliance
Security White Paper
Notes on Information Security
Service Level Agreement
Apple Privacy Policy: PrivacyInfo.xcprivacy
TRTC Policy
Privacy Policy
Data Processing And Security Agreement
Glossary

Concepts

PDF
Focus Mode
Font Size
Last updated: 2025-06-27 17:46:52
This document explains some of the basic concepts you may encounter while using TRTC services.

Application

In TRTC, business and projects are managed with applications. You can create different applications for your projects in the TRTC console to separate their data. Each Tencent Cloud account can create up to 100 TRTC applications.

SDKAppID

Tencent Cloud uses SDKAppID (application ID) to uniquely identify TRTC applications. It is generated automatically when you create an application in the TRTC console. Applications that do not have the same SDKAppID cannot communicate data with each other.

UserID

UserID (user ID) uniquely identifies a user in a TRTC application.
UserID is a mapping of the user accounts of your project in Tencent Cloud. Normally, you can use a username as UserID.
UserID should preferably be 32 bytes or shorter. It can contain digits, underscores, and letters (case sensitive).

Room

A room is a space where users can receive each other’s audio and video data in real time.
Rooms are virtual spaces TRTC uses to separate one user group from another.
Only users in the same room can receive each other’s audio and video.
A user can be in only one room at a time. A user who is already in a room must exit the room before they can enter another.
notice
The first user who enters a room is the owner of the room. Room owners cannot close rooms manually.
In call modes, TRTC closes a room when all users leave the room.
In live streaming modes, if the last user who exits a room is an anchor, TRTC will close the room immediately; if the user is an audience member, TRTC will close the room after 10 minutes.
A user is removed from a room 90 seconds after an unexpected disconnection occurs. If all users are disconnected, the room is closed after 90 seconds. The waiting time after a disconnection occurs is also billed.
If a user attempts to enter a room that does not exist, TRTC creates a room automatically.

Room ID

RoomID (room number/ID) uniquely identifies a room in a TRTC application. It is a UInt32 number that you assign to a room and maintain. Its value range is 1-4294967295.

UserSig

UserSig (user signature) is a security signature designed by Tencent Cloud to authenticate user logins and verify that a user is real. It helps prevent attackers from accessing your Tencent Cloud account. For more information, see FAQs > UserSig.

Push

Push is the operation in which a user uploads local audio/video data to the TRTC server.

Subscription

Subscription is the operation in which a user sends a request to the TRTC server to pull the audio/video data of a specified user.

Role

In TRTC, users can have either of two roles: anchor (TRTCRoleAnchor) and audience (TRTCRoleAudience).
An anchor can push local audio/video data to the server. They can also subscribe to and play back the audio/video data of other anchors.
Audience members can only subscribe to and play back the audio/video data of anchors.
In call modes, all users in a room have the anchor role. In live streaming modes, users in a room can be either anchors or audience memebers. A user can switch roles as needed.

CDN Live Watching

CDN live watching is also known as CDN relayed live streaming. TRTC uses relayed transcoding clusters to convert its UDP audio/video streams into RTMP streams in the cloud. The streams are then pushed to a standard live streaming system and distributed through CDNs to the audience. For details, see Relay to CDN.

On-cloud recording

The on-cloud recording feature of TRTC allows you to record an audio/video stream in real time using a RESTful API. It is flexible, light, and easy-to-use, saving you the trouble of deploying servers and recording modules. For details, see On-Cloud Recording.

On-Cloud MixTranscoding

In scenarios such as CDN live watching and on-cloud recording, you may need to mix multiple audio/video streams in a TRTC room into one stream. This can be achieved using TRTC’s stream mixing and transcoding MCU cluster. The MCU cluster can mix multiple audio/video streams as needed and distribute the mixed stream to live streaming CDNs and the on-cloud recording system. For details, see Relay to CDN.

Dumb terminal

A user entering a room on a dumb terminal will not be detected by the SDK, and remote users will not receive notifications when the user enters or exits the room.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback