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

Glossary

PDF
Focus Mode
Font Size
Last updated: 2024-07-16 15:38:55

AccountType

AccountType is the account type used to log in to a TRTC application in TRTC v1. It is automatically assigned for user authentication after the TRTC application is created and is no longer required in v2.

Room

A room is an audio/video space where users can receive each other's real-time audio/video streams.
In TRTC, room is a virtual concept used to separate a group of users from another group.
A user's audio/video streams can be received only by other users in the same room.
A user can be in only one room at any time point and can enter another room only after exiting the current room.
Note:
The user who creates a room will be the room owner, but this user cannot close the room actively.
The server will close the room as soon as all users actively exit the room.
If a user is disconnected exceptionally, the server will remove this user from the room after 30 seconds. If all users are disconnected exceptionally, the server will automatically close the room after 30 seconds.
When a user attempts to enter a room that does not exist, the TRTC backend will create the room first and then add the user to the room.

Role name

After you create a role parameter set for a specified device platform integrated with TRTC v1 in the TRTC Console, you can name this set of parameters, and this name is referred to as a role name. After a user enables the camera or mic and upstreams the audio/video streams in a room, the role to be used during room entry can be specified by the role name, which confirms the parameters for data streaming. This concept is no longer required in v2.
Note:
During room entry, if a user uses a role name that has not been configured in the console, the user can still enter the room, but the default role will be used.
After room entry, the user can change the role by calling the role switching API.
Switching to a non-existent role with the API will throw back a failure callback.
After the role configuration is modified, logging in to the client again is required to make the new configuration take effect (the SDK will pull the configuration from the backend when login is successful. If the pull fails, the role will not be found).

Relayed live streaming

Relayed live streaming is a live broadcasting mode that is usually used for data forwarding between audio/video systems with different protocols. In this mode, the TRTC server pushes the audio/video data in a chat room to the LVB service through RTMP push, thereby implementing the features of relayed live streaming, relayed push, On-Cloud MixTranscoding, and On-Cloud Recording.

PrivateMapKey

PrivateMapKey (room ticket) is a credential used for permission verification when a user attempts to enter a room, which is equivalent to the key to a specified room (RoomID). It is usually used to authenticate room entry and implement room entry restrictions and is issued by your business server. For more information on its generation method, please see Room Entry Permission Protection.

Group

The group system in TRTC v1 uses the group feature of the Tencent Cloud Instant Messaging (IM) service.
Note:
Group and room are two different concepts completely independent of each other.

RoomID

RoomID (room number) is used in TRTC to uniquely identify a room. It is a number in the uint32 range that is maintained and assigned on your own.

SDKAPPID

SDKAPPID (application ID) is a unique ID used by the Tencent Cloud backend to differentiate between different TRTC applications. It is automatically generated when an application is created in the TRTC Console. The data under different SDKAPPID is not interconnected.

Tencent Real-Time Communication

Developed by Tencent Cloud based on Tencent's over a decade of expertise in QQ audio/video chat technologies, Tencent Real-Time Communication (TRTC) provides cross-platform, high-quality, and customizable real-time communication services by leveraging the WebRTC capabilities of Tencent Browsing Service (TBS) and TRTC SDKs. It enables you to build an audio/video communication platform from scratch quickly through Mobile QQ, WeChat Mini Program, WeChat Official Account, QQ Browser, and over 20,000 TBS-enabled apps with no knowledge of audio/video technologies required.

TRTC

For more information, please see TRTC.

UserID

UserID (user ID) is used to uniquely identify a user in a TRTC application.
UserID maps a user account in your business system to Tencent Cloud. Usually, you can directly use a username as the UserID.
The recommended length of UserID is below 32 bytes. It can be a combination of letters, digits, and underscores but cannot only contain digits. It is case insensitive.

UserSig

UserSig (user signature) is used for user login authentication to make sure that the user's identity is authentic. For more information on its generation method, please see Signature Generation.

Help and Support

Was this page helpful?

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

Feedback