@tencent-rtc/mcp 1.3.9 → 1.4.0

package/resource/doc/livekit/{live → core-sdk/live}/android/live-host-interaction.md

@@ -9,14 +9,11 @@ A typical "Host Co-hosting PK" session consists of three main stages, as shown b
 
 3. **PK Battle**: Both hosts compete in a PK battle, with scores updated in real time.
 
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/caa7340cc6b811f0b011525400bf7822.png)
-
-
 ## Implementation
 
 ### Step 1: Component Integration
 
-Refer to [Quick Start](https://write.woa.com/document/194571606056804352) to integrate AtomicXCore and complete the setup of LiveCoreView.
+Refer to Quick Start to integrate AtomicXCore and complete the setup of LiveCoreView.
 
 ### Step 2: Implement Cross-Room Co-hosting
 
@@ -25,7 +22,6 @@ The goal of this step is to display the video streams of two hosts in the same v
 #### Inviter (Host A) Implementation
 1. **Initiate Co-hosting Invitation**
 
-
    When Host A selects Host B in the UI and initiates a co-hosting request, call the `requestHostConnection` method.
 
    ``` kotlin
@@ -33,28 +29,28 @@ The goal of this step is to display the video streams of two hosts in the same v
    import io.trtc.tuikit.atomicxcore.api.CompletionHandler
    import io.trtc.tuikit.atomicxcore.api.live.CoHostLayoutTemplate
    import io.trtc.tuikit.atomicxcore.api.live.CoHostStore
-   
+
    // Host A's Activity
    class HostAActivity : AppCompatActivity() {
        private val liveId = "hostA_roomID" // Host A's Room ID
        private val coHostStore = CoHostStore.create(liveId)
-   
+
        // User clicks the "Co-host" button and selects Host B
        fun inviteHostB(targetHostLiveId: String) {
            val layout = CoHostLayoutTemplate.HOST_DYNAMIC_GRID // Select a layout template
            val timeout = 30 // Invitation timeout (seconds)
-   
+
            coHostStore.requestHostConnection(
                targetHostLiveID = targetHostLiveId,
                layoutTemplate = layout,
                timeout = timeout,
                extraInfo = null,
                completion = object : CompletionHandler {
-                   override fun onSuccess() { 
+                   override fun onSuccess() {
                        println("Co-hosting invitation sent, waiting for response...")
                    }
-   
-                   override fun onFailure(code: Int, desc: String) { 
+
+                   override fun onFailure(code: Int, desc: String) {
                        println("Invitation failed to send: $desc")
                    }
                }
@@ -64,7 +60,6 @@ The goal of this step is to display the video streams of two hosts in the same v
    ```
 2. **Listen for Invitation Result**
 
-
    Receive Host B's response via the CoHostListener callback methods.
 
    ``` java
@@ -73,7 +68,7 @@ The goal of this step is to display the video streams of two hosts in the same v
    import io.trtc.tuikit.atomicxcore.api.live.CoHostListener
    import io.trtc.tuikit.atomicxcore.api.live.CoHostStore
    import io.trtc.tuikit.atomicxcore.api.live.SeatUserInfo
-   
+
    class HostAActivity : AppCompatActivity() {
        private val liveId = "hostA_roomID" // Host A's Room ID
        private val coHostStore = CoHostStore.create(liveId)
@@ -81,20 +76,20 @@ The goal of this step is to display the video streams of two hosts in the same v
            override fun onCoHostRequestAccepted(invitee: SeatUserInfo) {
                println("Host ${invitee.userName} accepted your co-hosting invitation")
            }
-   
+
            override fun onCoHostRequestRejected(invitee: SeatUserInfo) {
                println("Host ${invitee.userName} rejected your invitation")
            }
-   
-           override fun onCoHostRequestTimeout(inviter: SeatUserInfo, invitee: SeatUserInfo) { 
+
+           override fun onCoHostRequestTimeout(inviter: SeatUserInfo, invitee: SeatUserInfo) {
                println("Invitation timed out, no response received")
            }
        }
-   
+
        override fun onCreate(savedInstanceState: Bundle?) {
            super.onCreate(savedInstanceState)
            // ... initialization code ...
-           
+
            // Initialize CoHostStore
            coHostStore.addCoHostListener(coHostListener)
        }
@@ -104,7 +99,6 @@ The goal of this step is to display the video streams of two hosts in the same v
 #### Invitee (Host B) Implementation
 1. **Receive Co-hosting Invitation**
 
-
    Host B listens for invitations from Host A via `CoHostListener`.
 
    ``` kotlin
@@ -112,12 +106,12 @@ The goal of this step is to display the video streams of two hosts in the same v
    import io.trtc.tuikit.atomicxcore.api.live.CoHostListener
    import io.trtc.tuikit.atomicxcore.api.live.CoHostStore
    import io.trtc.tuikit.atomicxcore.api.live.SeatUserInfo
-   
+
    // Host B's Activity
    class HostBActivity : AppCompatActivity() {
        private val liveId = "hostB_roomID" // Host B's Room ID
        private val coHostStore = CoHostStore.create(liveId)
-       
+
        private val coHostListener = object : CoHostListener() {
            override fun onCoHostRequestReceived(inviter: SeatUserInfo, extensionInfo: String) {
                println("Received co-hosting invitation from Host ${inviter.userName}")
@@ -129,7 +123,6 @@ The goal of this step is to display the video streams of two hosts in the same v
    ```
 2. **Respond to Co-hosting Invitation**
 
-
    After Host B receives the invitation, prompt for “Accept” or “Reject” and call the appropriate method:
 
    ``` kotlin
@@ -137,7 +130,7 @@ The goal of this step is to display the video streams of two hosts in the same v
    fun acceptInvitation(fromHostLiveId: String) {
        coHostStore.acceptHostConnection(fromHostLiveID = fromHostLiveId, completion = null)
    }
-   
+
    fun rejectInvitation(fromHostLiveId: String) {
        coHostStore.rejectHostConnection(fromHostLiveID = fromHostLiveId, completion = null)
    }
@@ -150,7 +143,6 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
 #### Challenger (e.g., Host A) Implementation
 1. **Initiate PK Challenge**
 
-
    When Host A clicks the "PK" button, call the `requestBattle` method.
 
    ``` kotlin
@@ -158,7 +150,7 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
    class HostAActivity : AppCompatActivity() {
        private val liveId = "hostA_roomID" // Host A's Room ID
        private val battleStore = BattleStore.create(liveId)
-   
+
        fun startPK(opponentUserId: String) {
            val config = BattleConfig(duration = 300) // PK lasts 5 minutes
            battleStore.requestBattle(
@@ -172,7 +164,6 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
    ```
 2. **Listen for PK Status**
 
-
    Use `BattleListener` to monitor key events such as the start and end of PK.
 
    ``` java
@@ -180,7 +171,7 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
    class HostAActivity : AppCompatActivity() {
        private val liveId = "hostA_roomID" // Host A's Room ID
        private val battleStore = BattleStore.create(liveId)
-       
+
        private val battleListener = object : BattleListener() {
            override fun onBattleStarted(
                battleInfo: BattleInfo,
@@ -189,12 +180,12 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
            ) {
                println("PK started")
            }
-   
+
            override fun onBattleEnded(battleInfo: BattleInfo, reason: BattleEndedReason?) {
                println("PK ended")
            }
        }
-   
+
        override fun onCreate(savedInstanceState: Bundle?) {
            super.onCreate(savedInstanceState)
            // ... other initialization code ...
@@ -206,7 +197,6 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
 #### Opponent (Host B) Implementation
 1. **Receive PK Challenge**
 
-
    Listen for PK invitations via `BattleListener`.
 
    ``` kotlin
@@ -214,7 +204,7 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
    class HostBActivity : AppCompatActivity() {
        private val liveId = "hostB_roomID" // Host B's Room ID
        private val battleStore = BattleStore.create(liveId)
-   
+
        private val battleListener = object : BattleListener() {
            override fun onBattleRequestReceived(battleID: String, inviter: SeatUserInfo, invitee: SeatUserInfo) {
                println("Received PK challenge from Host ${inviter.userName}")
@@ -222,7 +212,7 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
                // showPKChallengeDialog(battleID, inviter)
                }
            }
-       
+
            override fun onCreate(savedInstanceState: Bundle?) {
                super.onCreate(savedInstanceState)
                // ... other initialization code ...
@@ -232,7 +222,6 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
    ```
 2. **Respond to PK Challenge**
 
-
    Prompt Host B for “Accept” or “Reject” and call the corresponding method:
 
    ``` kotlin
@@ -241,7 +230,7 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
    fun acceptPK(battleId: String) {
        battleStore.acceptBattle(battleID = battleId, completion = null)
    }
-   
+
    // User clicks "Reject Challenge"
    fun rejectPK(battleId: String) {
        battleStore.rejectBattle(battleID = battleId, completion = null)
@@ -253,12 +242,10 @@ After a successful co-hosting connection, either host can initiate a PK. Use [Ba
 After the PK session, end the PK and disconnect co-hosting in sequence.
 1. **End PK Battle**
 
-
    PK typically ends automatically when the timer expires, but hosts can also end PK early. Use `exitBattle`:
-   
 
    > **Note****：**After PK ends, both hosts remain connected (side-by-side video streams). Only the PK progress bar and score panel are removed.
-   > 
+   >
 
    ``` java
    fun stopPK(battleId: String) {
@@ -275,7 +262,6 @@ After the PK session, end the PK and disconnect co-hosting in sequence.
    ```
 2. **Disconnect Cross-room Co-hosting**
 
-
    To return to solo live streaming, call `exitHostConnection`:
 
    ``` java
@@ -293,7 +279,6 @@ After the PK session, end the PK and disconnect co-hosting in sequence.
    ```
 3. **Listen for End Events**
 
-
    Handle UI cleanup in event listeners for consistency:
 
    ``` java
@@ -304,7 +289,7 @@ After the PK session, end the PK and disconnect co-hosting in sequence.
            // runOnUiThread { removeBattleUI() }
        }
    }
-   
+
    private val coHostListener = object : CoHostListener() {
        override fun onCoHostUserLeft(userInfo: SeatUserInfo) {
            println("Host ${userInfo.userName} has left the co-hosting session")
@@ -316,10 +301,7 @@ After the PK session, end the PK and disconnect co-hosting in sequence.
 
 ### Run and Test
 
-After integrating the above features, use Host A and Host B to test the corresponding operations. The runtime effect is shown below. For UI customization, see [Refine UI Details](https://write.woa.com/#.E5.AE.8C.E5.96.84-ui-.E7.BB.86.E8.8A.82).
-
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/20a4d9adc6ba11f087ad52540099c741.png)
-
+After integrating the above features, use Host A and Host B to test the corresponding operations. The runtime effect is shown below. For UI customization, see Refine UI Details.
 
 ## Refine UI Details
 
@@ -329,18 +311,14 @@ Use the slot capability in the `VideoViewAdapter` interface to overlay custom vi
 
 #### Implementation Example
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/701b2054c6ba11f08942525400e889b2.png)
-
-
 #### Implementation
 - **Step 1**: Create a foreground view `CustomSeatView` to display user information above the video stream.
-   
 
    > **Note：**
-   > 
+   >
 
    > For a complete implementation, refer to the [widgets](https://github.com/Tencent-RTC/TUIKit_Android/tree/main/live/tuilivekit/src/main/java/com/trtc/uikit/livekit/features/anchorboardcast/view/cohost/widgets) directory in the open-source TUILiveKit project.
-   > 
+   >
 
    ``` kotlin
    import android.content.Context
@@ -348,26 +326,26 @@ Use the slot capability in the `VideoViewAdapter` interface to overlay custom vi
    import android.view.Gravity
    import android.widget.LinearLayout
    import android.widget.TextView
-   
+
    // Custom user information overlay view (Foreground)
    class CustomSeatView(context: Context) : LinearLayout(context) {
        private val nameLabel: TextView
-   
+
        init {
            orientation = VERTICAL
            setBackgroundColor(Color.parseColor("#80000000")) // Semi-transparent black background
-   
+
            nameLabel = TextView(context).apply {
                setTextColor(Color.WHITE)
                textSize = 14f
                gravity = Gravity.CENTER
            }
-   
+
            addView(nameLabel)
            val layoutParams = nameLabel.layoutParams as LayoutParams
            layoutParams.setMargins(5, 0, 5, 5)
        }
-   
+
        fun setUserName(userName: String) {
            nameLabel.text = userName
        }
@@ -381,12 +359,12 @@ Use the slot capability in the `VideoViewAdapter` interface to overlay custom vi
    import androidx.appcompat.app.AppCompatActivity
    import io.trtc.tuikit.atomicxcore.api.ViewLayer
    import io.trtc.tuikit.atomicxcore.api.VideoViewAdapter
-   
+
    // 1. In your Activity, implement the VideoViewAdapter interface
    class YourActivity : AppCompatActivity(), VideoViewAdapter {
-   
+
        // ... Other code ...
-   
+
        // 2. Fully implement the interface method to handle both view layers
        override fun createCoHostView(coHostUser: TUIRoomDefine.SeatFullInfo?, viewLayer: ViewLayer?): View? {
            val seatInfo = coHostUser ?: return null
@@ -394,7 +372,7 @@ Use the slot capability in the `VideoViewAdapter` interface to overlay custom vi
            if (userId.isNullOrEmpty()) {
                return null
            }
-   
+
            return when (viewLayer) {
                ViewLayer.FOREGROUND -> {
                    val seatView = CustomSeatView(this)
@@ -419,12 +397,12 @@ Use the slot capability in the `VideoViewAdapter` interface to overlay custom vi
    import androidx.appcompat.app.AppCompatActivity
    import io.trtc.tuikit.atomicxcore.api.ViewLayer
    import io.trtc.tuikit.atomicxcore.api.VideoViewAdapter
-   
+
    // 1. In your Activity, implement the VideoViewAdapter interface
    class YourActivity : AppCompatActivity(), VideoViewAdapter {
-   
+
        // ... Other code ...
-   
+
        // 2. Fully implement the interface method to handle both view layers
        override fun createCoHostView(coHostUser: TUIRoomDefine.SeatFullInfo?, viewLayer: ViewLayer?): View? {
            val seatInfo = coHostUser ?: return null
@@ -432,7 +410,7 @@ Use the slot capability in the `VideoViewAdapter` interface to overlay custom vi
            if (userId.isNullOrEmpty()) {
                return null
            }
-   
+
            return when (viewLayer) {
                ViewLayer.FOREGROUND -> {
                    val seatView = CustomSeatView(this)
@@ -451,72 +429,15 @@ Use the slot capability in the `VideoViewAdapter` interface to overlay custom vi
    ```
 
 #### Parameter Description:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`seatInfo`</td>
-
-<td rowspan="1" colSpan="1" >`SeatFullInfo?`</td>
-
-<td rowspan="1" colSpan="1" >Seat information object containing user details</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`seatInfo.userId`</td>
-
-<td rowspan="1" colSpan="1" >`String?`</td>
-
-<td rowspan="1" colSpan="1" >User ID on the seat</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`seatInfo.userName`</td>
-
-<td rowspan="1" colSpan="1" >`String?`</td>
-
-<td rowspan="1" colSpan="1" >User nickname on the seat</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`seatInfo.userAvatar`</td>
-
-<td rowspan="1" colSpan="1" >`String?`</td>
-
-<td rowspan="1" colSpan="1" >User avatar URL</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`seatInfo.userMicrophoneStatus`</td>
-
-<td rowspan="1" colSpan="1" >`DeviceStatus`</td>
-
-<td rowspan="1" colSpan="1" >User microphone status</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`seatInfo.userCameraStatus`</td>
-
-<td rowspan="1" colSpan="1" >`DeviceStatus`</td>
-
-<td rowspan="1" colSpan="1" >User camera status</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`viewLayer`</td>
-
-<td rowspan="1" colSpan="1" >`ViewLayer`</td>
-
-<td rowspan="1" colSpan="1" >View layer enum<br>- `FOREGROUND`: Foreground widget view, always displayed on top of the video<br>- `BACKGROUND`: Background widget view, under the foreground view, displayed only when the user has no video stream (e.g., camera off), typically used for the user's default avatar or a placeholder image</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| `seatInfo` | `SeatFullInfo?` | Seat information object containing user details |
+| `seatInfo.userId` | `String?` | User ID on the seat |
+| `seatInfo.userName` | `String?` | User nickname on the seat |
+| `seatInfo.userAvatar` | `String?` | User avatar URL |
+| `seatInfo.userMicrophoneStatus` | `DeviceStatus` | User microphone status |
+| `seatInfo.userCameraStatus` | `DeviceStatus` | User camera status |
+| `viewLayer` | `ViewLayer` | View layer enum<br>- `FOREGROUND`: Foreground widget view, always displayed on top of the video<br>- `BACKGROUND`: Background widget view, under the foreground view, displayed only when the user has no video stream (e.g., camera off), typically used for the user's default avatar or a placeholder image |
 
 ### Displaying PK User Score on Video View
 
@@ -524,9 +445,6 @@ When the host starts a PK, you can attach a custom view to the opponent's video
 
 #### Implementation Example
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/ab241f91c6ba11f0a7775254005ef0f7.png)
-
-
 #### Implementation
 - **Step 1**: Create a custom PK user view. For a complete implementation, see [BattleMemberInfoView.kt](https://github.com/Tencent-RTC/TUIKit_Android/blob/main/live/tuilivekit/src/main/java/com/trtc/uikit/livekit/features/anchorboardcast/view/battle/widgets/BattleMemberInfoView.kt)  in the open-source TUILiveKit project.
 
@@ -541,54 +459,54 @@ When the host starts a PK, you can attach a custom view to the opponent's video
    import kotlinx.coroutines.CoroutineScope
    import kotlinx.coroutines.Dispatchers
    import kotlinx.coroutines.launch
-   
+
    // Custom PK User View
    class CustomBattleUserView(
        context: Context,
        private val liveId: String,
        private val battleUser: BattleUser
    ) : LinearLayout(context) {
-   
+
        private lateinit var scoreView: LinearLayout
        private lateinit var scoreLabel: TextView
        private val battleStore: BattleStore
-   
+
        init {
            orientation = VERTICAL
            gravity = Gravity.BOTTOM or Gravity.END
            setBackgroundColor(Color.TRANSPARENT)
            isClickable = false
-   
+
            battleStore = BattleStore.create(liveId)
-   
+
            // UI Layout
            setupUI()
            // Subscribe to score changes
            subscribeBattleState()
        }
-   
+
        private fun setupUI() {
            scoreView = LinearLayout(context).apply {
                setBackgroundColor(Color.parseColor("#66000000"))
                orientation = VERTICAL
                gravity = Gravity.CENTER
            }
-   
+
            scoreLabel = TextView(context).apply {
                setTextColor(Color.WHITE)
                textSize = 14f
                gravity = Gravity.CENTER
            }
-   
+
            scoreView.addView(scoreLabel)
            addView(scoreView)
-   
+
            val layoutParams = scoreView.layoutParams as LayoutParams
            layoutParams.width = LayoutParams.WRAP_CONTENT
            layoutParams.height = 48 // 24dp
            layoutParams.setMargins(0, 0, 10, 10)
        }
-   
+
        // Subscribe to PK score changes
        private fun subscribeBattleState() {
            CoroutineScope(Dispatchers.Main).launch {
@@ -606,83 +524,30 @@ When the host starts a PK, you can attach a custom view to the opponent's video
    ``` kotlin
    // 1. Have your Activity implement the VideoViewAdapter interface
    class YourActivity : AppCompatActivity(), VideoViewAdapter {
-   
+
        override fun createBattleView(battleUser: BattleUser?): View? {
            battleUser ?: return null
            // CustomBattleUserView is your custom PK user information view
            return CustomBattleUserView(this, liveId, battleUser)
        }
-   
+
    }
    ```
 
 #### Parameter Description:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`battleUser`</td>
-
-<td rowspan="1" colSpan="1" >`BattleUser?`</td>
-
-<td rowspan="1" colSpan="1" >PK user info object</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`battleUser.roomId`</td>
-
-<td rowspan="1" colSpan="1" >`String`</td>
-
-<td rowspan="1" colSpan="1" >PK room ID</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`battleUser.userId`</td>
-
-<td rowspan="1" colSpan="1" >`String`</td>
-
-<td rowspan="1" colSpan="1" >PK user ID</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`battleUser.userName`</td>
-
-<td rowspan="1" colSpan="1" >`String`</td>
-
-<td rowspan="1" colSpan="1" >PK user nickname</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`battleUser.avatarUrl`</td>
-
-<td rowspan="1" colSpan="1" >`String`</td>
-
-<td rowspan="1" colSpan="1" >PK user avatar URL</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`battleUser.score`</td>
-
-<td rowspan="1" colSpan="1" >`UInt`</td>
-
-<td rowspan="1" colSpan="1" >PK score</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| `battleUser` | `BattleUser?` | PK user info object |
+| `battleUser.roomId` | `String` | PK room ID |
+| `battleUser.userId` | `String` | PK user ID |
+| `battleUser.userName` | `String` | PK user nickname |
+| `battleUser.avatarUrl` | `String` | PK user avatar URL |
+| `battleUser.score` | `UInt` | PK score |
 
 ### Displaying PK Status on Video Stream
 
 #### Implementation Example
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/d7cf2fbec6ba11f0b011525400bf7822.png)
-
-
 #### Implementation
 - **Step 1**: Create a custom PK global view (CustomBattleContainerView). For a complete implementation, see [BattleInfoView.kt](https://github.com/Tencent-RTC/TUIKit_Android/blob/main/live/tuilivekit/src/main/java/com/trtc/uikit/livekit/features/anchorboardcast/view/battle/widgets/BattleInfoView.kt)  in the open-source TUILiveKit project.
 
@@ -704,162 +569,49 @@ When the host starts a PK, you can attach a custom view to the opponent's video
 In typical** live host PK scenarios,** the value of gifts received by the host is linked to the PK score (for example, when a viewer sends a "Rocket" gift, the host's PK score increases by 500 points). You can implement real-time PK score updates using our REST API.
 
 > **Note：**
-> 
+>
 
 > The PK score system in the `LiveKit` backend uses pure numeric calculation and accumulation. You must calculate the PK score according to your own business logic before calling the update API. See the following PK score calculation examples:
-> 
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >Gift Type</td>
-
-<td rowspan="1" colSpan="1" >Score Calculation Rule</td>
-
-<td rowspan="1" colSpan="1" >Example</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Basic Gift</td>
-
-<td rowspan="1" colSpan="1" >Gift value × 5</td>
-
-<td rowspan="1" colSpan="1" >10 RMB gift → 50 points</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Intermediate Gift</td>
-
-<td rowspan="1" colSpan="1" >Gift value × 8</td>
-
-<td rowspan="1" colSpan="1" >50 RMB gift → 400 points</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Advanced Gift</td>
-
-<td rowspan="1" colSpan="1" >Gift value × 12</td>
-
-<td rowspan="1" colSpan="1" >100 RMB gift → 1200 points</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Special Effect Gift</td>
-
-<td rowspan="1" colSpan="1" >Fixed high score</td>
-
-<td rowspan="1" colSpan="1" >520 RMB gift → 1314 points</td>
-</tr>
-</table>
-
-
+>
+| Gift Type | Score Calculation Rule | Example |
+| --- | --- | --- |
+| Basic Gift | Gift value × 5 | 10 RMB gift → 50 points |
+| Intermediate Gift | Gift value × 8 | 50 RMB gift → 400 points |
+| Advanced Gift | Gift value × 12 | 100 RMB gift → 1200 points |
+| Special Effect Gift | Fixed high score | 520 RMB gift → 1314 points |
 
 #### REST API Call Flow
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/8a84bf38c6df11f0b011525400bf7822.png)
-
-
 #### Key Process Description
 1. **Obtain PK Status:**
 
-  - **Callback Configuration**: Configure [PK Status Callback](https://write.woa.com/document/170203265552953344) to have the `LiveKit` backend actively notify your system when PK starts or ends.
+  - **Callback Configuration**: Configure PK Status Callback to have the `LiveKit` backend actively notify your system when PK starts or ends.
 
-  - **Active Query**: Your backend can call the [PK Status Query](https://write.woa.com/document/170220847572692992) API at any time to check the current PK status.
+  - **Active Query**: Your backend can call the PK Status Query API at any time to check the current PK status.
 
 2. **PK Score Calculation**: Your backend calculates the PK score increment based on your business rules.
 
-3. **PK Score Update**: Your backend calls the [Update PK Score](https://write.woa.com/document/170220034100383744) API to update the PK score in the LiveKit backend.
+3. **PK Score Update**: Your backend calls the Update PK Score API to update the PK score in the LiveKit backend.
 
 4. **LiveKit Backend Syncs to Client**: The backend automatically synchronizes the updated PK score to all clients.
 
-
 #### Involved REST API Endpoints
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**API**</td>
-
-<td rowspan="1" colSpan="1" >**Function Description**</td>
-
-<td rowspan="1" colSpan="1" >**Request Example**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Active API - Query PK Status</td>
-
-<td rowspan="1" colSpan="1" >Check whether the current room is in PK</td>
-
-<td rowspan="1" colSpan="1" >[Example](https://write.woa.com/document/170220847572692992)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Active API - Update PK Score</td>
-
-<td rowspan="1" colSpan="1" >Update the calculated PK score</td>
-
-<td rowspan="1" colSpan="1" >[Example](https://write.woa.com/document/170220034100383744)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Callback Configuration - PK Start Callback</td>
-
-<td rowspan="1" colSpan="1" >Receive real-time notification when PK starts</td>
-
-<td rowspan="1" colSpan="1" >[Example](https://write.woa.com/document/170203265552953344)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >Callback Configuration - PK End Callback</td>
-
-<td rowspan="1" colSpan="1" >Receive real-time notification when PK ends</td>
-
-<td rowspan="1" colSpan="1" >[Example](https://write.woa.com/document/170221608179601408)</td>
-</tr>
-</table>
-
+| **API** | **Function Description** | **Request Example** |
+| --- | --- | --- |
+| Active API - Query PK Status | Check whether the current room is in PK | Example |
+| Active API - Update PK Score | Update the calculated PK score | Example |
+| Callback Configuration - PK Start Callback | Receive real-time notification when PK starts | Example |
+| Callback Configuration - PK End Callback | Receive real-time notification when PK ends | Example |
 
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [CoHostStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-co-host-store/index.html)  and related classes, refer to the official API documentation included with the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Android/index.html) framework. The relevant stores used in this guide are as follows:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Store/Component**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-
-<td rowspan="1" colSpan="1" >**API Reference**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`LiveCoreView`</td>
-
-<td rowspan="1" colSpan="1" >Core view component for displaying and interacting with live video streams. Handles video rendering and view widgets, supports host streaming, audience co-hosting, host connections, and more.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`DeviceStore`</td>
-
-<td rowspan="1" colSpan="1" >Controls audio/video devices: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, and real-time device status monitoring.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`CoHostStore`</td>
-
-<td rowspan="1" colSpan="1" >Handles host cross-room connections: supports multiple layout templates (dynamic grid, etc.), initiates/accepts/rejects connections, and manages co-host interactions.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-co-host-store/index.html)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`BattleStore`</td>
-
-<td rowspan="1" colSpan="1" >Manages host PK battles: initiate PK (set duration/opponent), manage PK status (start/end), synchronize scores, and listen for battle results.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-battle-store/index.html)</td>
-</tr>
-</table>
-
+| **Store/Component** | **Description** | **API Reference** |
+| --- | --- | --- |
+| `LiveCoreView` | Core view component for displaying and interacting with live video streams. Handles video rendering and view widgets, supports host streaming, audience co-hosting, host connections, and more. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-live-core-view/index.html) |
+| `DeviceStore` | Controls audio/video devices: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, and real-time device status monitoring. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html) |
+| `CoHostStore` | Handles host cross-room connections: supports multiple layout templates (dynamic grid, etc.), initiates/accepts/rejects connections, and manages co-host interactions. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-co-host-store/index.html) |
+| `BattleStore` | Manages host PK battles: initiate PK (set duration/opponent), manage PK status (start/end), synchronize scores, and listen for battle results. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.live/-battle-store/index.html) |
 
 ## FAQs
 
@@ -868,7 +620,6 @@ For detailed information on all public interfaces, properties, and methods of [C
 
 - Check network stability. The invitation signaling has a default timeout of 30 seconds.
 
-
 ### What happens if one host disconnects from the network or the app crashes during co-hosting or PK?
 
 Both `CoHostStore` and `BattleStore` include built-in heartbeat and timeout detection. If one party exits abnormally, the other party is notified via events such as `onCoHostUserLeft` or `onUserExitBattle`. You can update the UI accordingly, for example, by displaying "The other party has disconnected" and ending the interaction.
@@ -882,7 +633,6 @@ The REST API meets the security, real-time, and scalability requirements for PK
 
 - **Flexible rule adaptation**: Backend configuration changes (such as adjusting gift-to-score mapping or bonus points) can be made without modifying the frontend, reducing iteration costs.
 
-
 ### How do I manage the lifecycle and events of custom views added via `VideoViewAdapter`?
 
-`LiveCoreView` automatically manages views returned by delegate methods, including adding and removing them. No manual lifecycle management is required.
+`LiveCoreView` automatically manages views returned by delegate methods, including adding and removing them. No manual lifecycle management is required.