tencentcloud-sdk-nodejs-intl-en 3.0.739 → 3.0.741

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tencentcloud-sdk-nodejs-intl-en",
-  "version": "3.0.739",
+  "version": "3.0.741",
   "description": "腾讯云 API NODEJS SDK",
   "main": "index.js",
   "scripts": {

package/tencentcloud/billing/v20180709/models.js

@@ -1071,7 +1071,7 @@ Note: To query the product codes used in the current month, call <a href="https:
         this.Context = null;
 
         /**
-         * 
+         * The account ID of the payer, which is the unique identifier of a Tencent Cloud user. This account is allowed to query its own bills by default. If an organization admin account needs to query the self-pay bills of members, this field should be specified as the member account ID.
          * @type {string || null}
          */
         this.PayerUin = null;
@@ -1515,13 +1515,13 @@ class BillDetailComponent extends  AbstractModel {
         this.UsedAmountUnit = null;
 
         /**
-         * 
+         * Raw usage/duration: The raw usage/duration of a component before deduction. Note: This field may return null, indicating that no valid values can be obtained.
          * @type {string || null}
          */
         this.RealTotalMeasure = null;
 
         /**
-         * 
+         * Deducted usage/duration (including packages): The usage/duration deducted with a package. Note: This field may return null, indicating that no valid values can be obtained.
          * @type {string || null}
          */
         this.DeductedMeasure = null;
@@ -2427,7 +2427,7 @@ Note: To query the product codes used in the current month, call <a href="https:
         this.BusinessCode = null;
 
         /**
-         * 
+         * The account ID of the payer, which is the unique identifier of a Tencent Cloud user. This account is allowed to query its own bills by default. If an organization admin account needs to query the self-pay bills of members, this field should be specified as the member account ID.
          * @type {string || null}
          */
         this.PayerUin = null;

package/tencentcloud/clb/v20180317/clb_client.js

@@ -83,6 +83,7 @@ const DescribeTargetGroupsRequest = models.DescribeTargetGroupsRequest;
 const DescribeTaskStatusResponse = models.DescribeTaskStatusResponse;
 const BatchRegisterTargetsResponse = models.BatchRegisterTargetsResponse;
 const ModifyLoadBalancerAttributesRequest = models.ModifyLoadBalancerAttributesRequest;
+const TypeInfo = models.TypeInfo;
 const DescribeLBListenersRequest = models.DescribeLBListenersRequest;
 const SlaUpdateParam = models.SlaUpdateParam;
 const Target = models.Target;
@@ -93,6 +94,7 @@ const DescribeClassicalLBHealthStatusResponse = models.DescribeClassicalLBHealth
 const DescribeClsLogSetRequest = models.DescribeClsLogSetRequest;
 const Listener = models.Listener;
 const LoadBalancerTraffic = models.LoadBalancerTraffic;
+const SpecAvailability = models.SpecAvailability;
 const ConfigListItem = models.ConfigListItem;
 const RegisterTargetsWithClassicalLBRequest = models.RegisterTargetsWithClassicalLBRequest;
 const ModifyDomainAttributesResponse = models.ModifyDomainAttributesResponse;
@@ -484,11 +486,10 @@ This is an async API. After it is returned successfully, you can call the `Descr
     }
 
     /**
-     * This API is used to upgrade a pay-as-you-go shared CLB instance to an LCU-supported CLB instance.<br/>
+     * This API is used to upgrade a pay-as-you-go shared CLB instance to an LCU-supported CLB instance. <br/>
 Limits
-- This API can be used to upgrade only a pay-as-you-go shared instance. A monthly subscription shared instance must be upgraded in the console.
-- An LCU-supported instance cannot be rolled back to a shared instance.
-- LCU-supported instances are in beta testing. To upgrade to an LCU-supported instance, [submit a ticket](https://intl.cloud.tencent.com/apply/p/hf45esx99lf?from_cn_redirect=1) for application.
+- This API can only be used to upgrade pay-as-you-go shared instances. To upgrade monthly-subscribed shared instances, please go to the CLB u200dconsole.
+- An LCU-supported instance cannot be changed back to a shared instance.
 - Classic CLB instances cannot be upgraded to LCU-supported instances.
      * @param {ModifyLoadBalancerSlaRequest} req
      * @param {function(string, ModifyLoadBalancerSlaResponse):void} cb

package/tencentcloud/clb/v20180317/models.js

@@ -501,7 +501,7 @@ Note: By default, the traffic goes to the primary AZ. The secondary AZs only car
         this.ZoneId = null;
 
         /**
-         * CLB network billing mode. This parameter is applicable only to public network CLB instances.
+         * It only works on LCU-supported instances on private networks and all instances on public networks.
          * @type {InternetAccessible || null}
          */
         this.InternetAccessible = null;
@@ -540,8 +540,8 @@ Note: If the specified VIP is occupied or is not within the IP range of the spec
         /**
          * Creates an LCU-supported instance.
 <ul><li>To create an LCU-supported instance, set this parameter to `SLA`, which indicates that an LCU-supported instance is created with the default specification in pay-as-you-go mode.
-<ul><li>If you enable general LCU-supported instances, `SLA` corresponds to the Super Large 1 specification. General LCU-supported instances are in beta testing, [submit a ticket](https://intl.cloud.tencent.com/apply/p/hf45esx99lf?from_cn_redirect=1) for application.</li>
-<li>If you enable ultra-large LCU-supported instances, `SLA` corresponds to the Super Large 4 specification. Ultra-large LCU-supported instances are in beta testing, [submit a ticket](https://console.cloud.tencent.com/workorder/category) for application.</li></ul></li><li>This parameter is not required when you create a shared instance.</li></ul>
+<ul><li>The default specification is Super Large 1.
+<li>If you have enabled Super u200dLarge LCU-supported instances, `SLA` corresponds to the Super Large 4 specification. Super u200dLarge LCU-supported specification is in beta now. u200cu200dTo join the beta, [submit a ticket](https://console.cloud.tencent.com/workorder/category). </li></ul></li><li>It’s not required for a shared CLB instance. </li></ul>
          * @type {string || null}
          */
         this.SlaType = null;
@@ -589,6 +589,12 @@ Note: The traffic only goes to the secondary AZ when the primary AZ is unavailab
          */
         this.LoadBalancerPassToTarget = null;
 
+        /**
+         * Upgrades to domain name-based CLB
+         * @type {boolean || null}
+         */
+        this.DynamicVip = null;
+
     }
 
     /**
@@ -648,6 +654,7 @@ Note: The traffic only goes to the secondary AZ when the primary AZ is unavailab
         this.SlaveZoneId = 'SlaveZoneId' in params ? params.SlaveZoneId : null;
         this.EipAddressId = 'EipAddressId' in params ? params.EipAddressId : null;
         this.LoadBalancerPassToTarget = 'LoadBalancerPassToTarget' in params ? params.LoadBalancerPassToTarget : null;
+        this.DynamicVip = 'DynamicVip' in params ? params.DynamicVip : null;
 
     }
 }
@@ -1155,13 +1162,13 @@ They represent weighted round robin, least connections, and IP hash, respectivel
         this.ForwardType = null;
 
         /**
-         * TRPC callee server route, which is required when `ForwardType` is "TRPC".
+         * TRPC callee server route, which is required when `ForwardType` is "TRPC". This is now only for internal usage.
          * @type {string || null}
          */
         this.TrpcCallee = null;
 
         /**
-         * TRPC calling service API, which is required when `ForwardType` is "TRPC".
+         * TRPC calling service API, which is required when `ForwardType` is "TRPC". This is now only for internal usage.
          * @type {string || null}
          */
         this.TrpcFunc = null;
@@ -3489,6 +3496,12 @@ class ModifyLoadBalancerAttributesRequest extends  AbstractModel {
          */
         this.DeleteProtect = null;
 
+        /**
+         * Modifies the second-level domain name of CLB from mycloud.com to tencentclb.com. Note that the sub-domain names will be changed as well. After the modification, mycloud.com will be invalidated. 
+         * @type {boolean || null}
+         */
+        this.ModifyClassicDomain = null;
+
     }
 
     /**
@@ -3515,6 +3528,52 @@ class ModifyLoadBalancerAttributesRequest extends  AbstractModel {
         this.LoadBalancerPassToTarget = 'LoadBalancerPassToTarget' in params ? params.LoadBalancerPassToTarget : null;
         this.SnatPro = 'SnatPro' in params ? params.SnatPro : null;
         this.DeleteProtect = 'DeleteProtect' in params ? params.DeleteProtect : null;
+        this.ModifyClassicDomain = 'ModifyClassicDomain' in params ? params.ModifyClassicDomain : null;
+
+    }
+}
+
+/**
+ * ISP Type
+ * @class
+ */
+class TypeInfo extends  AbstractModel {
+    constructor(){
+        super();
+
+        /**
+         * ISP Type
+Note: This field may return null, indicating that no valid values can be obtained.
+         * @type {string || null}
+         */
+        this.Type = null;
+
+        /**
+         * Specification availability
+Note: This field may return null, indicating that no valid values can be obtained.
+         * @type {Array.<SpecAvailability> || null}
+         */
+        this.SpecAvailabilitySet = null;
+
+    }
+
+    /**
+     * @private
+     */
+    deserialize(params) {
+        if (!params) {
+            return;
+        }
+        this.Type = 'Type' in params ? params.Type : null;
+
+        if (params.SpecAvailabilitySet) {
+            this.SpecAvailabilitySet = new Array();
+            for (let z in params.SpecAvailabilitySet) {
+                let obj = new SpecAvailability();
+                obj.deserialize(params.SpecAvailabilitySet[z]);
+                this.SpecAvailabilitySet.push(obj);
+            }
+        }
 
     }
 }
@@ -4131,6 +4190,43 @@ Note: This field may return `null`, indicating that no valid values can be obtai
     }
 }
 
+/**
+ * Specification availability
+ * @class
+ */
+class SpecAvailability extends  AbstractModel {
+    constructor(){
+        super();
+
+        /**
+         * Specification type
+Note: This field may return null, indicating that no valid values can be obtained.
+         * @type {string || null}
+         */
+        this.SpecType = null;
+
+        /**
+         * Specification availability
+Note: This field may return null, indicating that no valid values can be obtained.
+         * @type {string || null}
+         */
+        this.Availability = null;
+
+    }
+
+    /**
+     * @private
+     */
+    deserialize(params) {
+        if (!params) {
+            return;
+        }
+        this.SpecType = 'SpecType' in params ? params.SpecType : null;
+        this.Availability = 'Availability' in params ? params.Availability : null;
+
+    }
+}
+
 /**
  * Configuration content
  * @class
@@ -4609,7 +4705,8 @@ Note: This field may return null, indicating that no valid values can be obtaine
         this.TimeOut = null;
 
         /**
-         * Health check interval in seconds. Value range: 5-300. Default value: 5.
+         * Health check probing interval period. It defaults to `5`. For IPv4 CLB instances, the range is 2-300. u200dFor IPv6 CLB instances, the range is 5-300. Unit: second
+Note: For some IPv4 CLB instances created long ago, the range is 5-300.
 Note: This field may return null, indicating that no valid values can be obtained.
          * @type {number || null}
          */
@@ -6585,15 +6682,15 @@ Note: This field may return null, indicating that no valid values can be obtaine
         this.WafDomainId = null;
 
         /**
-         * TRPC callee server route, which is valid when `ForwardType` is `TRPC`.
-Note: this field may return null, indicating that no valid values can be obtained.
+         * TRPC callee server route, which is valid when `ForwardType` is `TRPC`. This is now only for internal usage.
+Note: This field may return null, indicating that no valid values can be obtained.
          * @type {string || null}
          */
         this.TrpcCallee = null;
 
         /**
-         * TRPC calling service API, which is valid when `ForwardType` is `TRPC`.
-Note: this field may return null, indicating that no valid values can be obtained.
+         * TRPC calling service API, which is valid when `ForwardType` is `TRPC`. This is now only for internal usage.
+Note: This field may return null, indicating that no valid values can be obtained.
          * @type {string || null}
          */
         this.TrpcFunc = null;
@@ -9254,7 +9351,12 @@ BANDWIDTH_PACKAGE: billed by bandwidth package (currently, this method is suppor
         this.InternetChargeType = null;
 
         /**
-         * Maximum outbound bandwidth in Mbps, which applies only to public network CLB. Value range: 0-65,535. Default value: 10.
+         * Maximum outgoing bandwidth in Mbps. It works on LCU-supported instances on private networks and all instances on public networks.
+- For shared and dedicated CLB instances on public networks, the range is 1Mbps-2048Mbps.
+- For all LCU-supported CLB instances:
+  - It defaults to General LCU-supported instance. SLA corresponds to Super Large 1, and the range of maximum outgoing bandwidth is 1 Mbps - 10240 Mbps.
+  - If you have enabled Super Large specification, the range of maximum outgoing bandwidth is 1 Mbps - 61440 Mbps Super u200dLarge LCU-supported specification is in beta now. u200cu200dTo join the beta, [submit a ticket](https://console.cloud.tencent.com/workorder/category).
+Note: This field may return null, indicating that no valid values can be obtained.
          * @type {number || null}
          */
         this.InternetMaxBandwidthOut = null;
@@ -9674,7 +9776,7 @@ They represent weighted round robin, least connections, and IP hash, respectivel
         this.Scheduler = null;
 
         /**
-         * Forwarding protocol between the CLB instance and real server. Currently, HTTP/HTTPS/TRPC are supported.
+         * Forwarding protocol between the CLB instance and real server. HTTP/HTTPS/TRPC are supported. TRPC is now only available for internal usage.
          * @type {string || null}
          */
         this.ForwardType = null;
@@ -9698,13 +9800,13 @@ They represent weighted round robin, least connections, and IP hash, respectivel
         this.TargetType = null;
 
         /**
-         * TRPC callee server route, which is required when `ForwardType` is `TRPC`.
+         * TRPC callee server route, which is required when `ForwardType` is "TRPC". This is now only for internal usage.
          * @type {string || null}
          */
         this.TrpcCallee = null;
 
         /**
-         * TRPC calling service API, which is required when `ForwardType` is `TRPC`.
+         * TRPC calling service API, which is required when `ForwardType` is "TRPC". This is now only for internal usage.
          * @type {string || null}
          */
         this.TrpcFunc = null;
@@ -10090,6 +10192,13 @@ Note: This field may return `null`, indicating that no valid values can be obtai
          */
         this.AvailabilitySet = null;
 
+        /**
+         * ISP Type
+Note: This field may return null, indicating that no valid values can be obtained.
+         * @type {Array.<TypeInfo> || null}
+         */
+        this.TypeSet = null;
+
     }
 
     /**
@@ -10111,6 +10220,15 @@ Note: This field may return `null`, indicating that no valid values can be obtai
             }
         }
 
+        if (params.TypeSet) {
+            this.TypeSet = new Array();
+            for (let z in params.TypeSet) {
+                let obj = new TypeInfo();
+                obj.deserialize(params.TypeSet[z]);
+                this.TypeSet.push(obj);
+            }
+        }
+
     }
 }
 
@@ -11157,7 +11275,7 @@ class TargetHealth extends  AbstractModel {
         this.HealthStatusDetail = null;
 
         /**
-         * Detailed information about the current health status. Alive: healthy; Dead: exceptional; Unknown: check not started/checking/unknown status. This parameter will be discarded soon. We recommend that you use the HealthStatusDetail parameter.
+         * (**This parameter will be disused soon. Please use `HealthStatusDetail` instead.**) Details of the current health status. Values: `Alive` (healthy), `Dead` (abnormal), `Unknown` (Health check not started/checking/unknown status)
          * @type {string || null}
          */
         this.HealthStatusDetial = null;
@@ -12086,6 +12204,7 @@ module.exports = {
     DescribeTaskStatusResponse: DescribeTaskStatusResponse,
     BatchRegisterTargetsResponse: BatchRegisterTargetsResponse,
     ModifyLoadBalancerAttributesRequest: ModifyLoadBalancerAttributesRequest,
+    TypeInfo: TypeInfo,
     DescribeLBListenersRequest: DescribeLBListenersRequest,
     SlaUpdateParam: SlaUpdateParam,
     Target: Target,
@@ -12096,6 +12215,7 @@ module.exports = {
     DescribeClsLogSetRequest: DescribeClsLogSetRequest,
     Listener: Listener,
     LoadBalancerTraffic: LoadBalancerTraffic,
+    SpecAvailability: SpecAvailability,
     ConfigListItem: ConfigListItem,
     RegisterTargetsWithClassicalLBRequest: RegisterTargetsWithClassicalLBRequest,
     ModifyDomainAttributesResponse: ModifyDomainAttributesResponse,

package/tencentcloud/common/sdk_version.js

@@ -1,2 +1,2 @@
-const sdkVersion = "3.0.739";
+const sdkVersion = "3.0.741";
 module.exports = sdkVersion

package/tencentcloud/trtc/v20190722/models.js

@@ -91,6 +91,12 @@ Grey: `0x999999`
          */
         this.CustomCrop = null;
 
+        /**
+         * The display mode of the sub-background image during output: 0 for cropping, 1 for scaling and displaying the background, 2 for scaling and displaying the black background, 3 for proportional scaling. If not filled in, the default is 3.
+         * @type {number || null}
+         */
+        this.BackgroundRenderMode = null;
+
     }
 
     /**
@@ -120,6 +126,7 @@ Grey: `0x999999`
             obj.deserialize(params.CustomCrop)
             this.CustomCrop = obj;
         }
+        this.BackgroundRenderMode = 'BackgroundRenderMode' in params ? params.BackgroundRenderMode : null;
 
     }
 }
@@ -311,6 +318,12 @@ Grey: 0x999999
          */
         this.WaterMarkList = null;
 
+        /**
+         * Background image display mode during output: 0 for crop, 1 for scale and display with black background, 2 for proportional scaling. The backend default is proportional scaling.
+         * @type {number || null}
+         */
+        this.BackgroundRenderMode = null;
+
     }
 
     /**
@@ -343,6 +356,7 @@ Grey: 0x999999
                 this.WaterMarkList.push(obj);
             }
         }
+        this.BackgroundRenderMode = 'BackgroundRenderMode' in params ? params.BackgroundRenderMode : null;
 
     }
 }

package/tencentcloud/trtc/v20190722/trtc_client.js

@@ -165,28 +165,61 @@ class TrtcClient extends AbstractClient {
     }
 
     /**
-     * This API is used to mix streams and relay the mixed stream to CDNs. You can use this API to do the following:
-1. Publish (also known as "relay") the audio/video stream of one anchor to CDNs. For details, see example 2 (starting a task to relay the audio and video of a stream) and example 3 (starting a task to relay only the audio of a stream).
-2. Mix the streams of multiple anchors in a room or in different rooms and publish the mixed stream to CDNs. You can use `AudioParams.SubscribeAudioList` to specify the users whose audios are mixed, and use `VideoParams.LayoutParams` to specify the layout of the anchors’ videos. For details, see example 1 (mixing streams and publishing the mixed stream to a CDN).
-3. Mix multiple streams in a room according to a template and publish the mixed stream to CDNs. The TRTC backend will detect the change of anchors in the room and adjust the video layout automatically according to the stream mixing template. The following template types are supported:
-     - Floating: The entire screen is covered by the video of the first user who enters the room, and the videos of other users are displayed as small windows in rows in the bottom-left corner in room entry sequence. The screen allows up to 4 rows of 4 small videos, which float over the large video. Up to 1 large and 15 small videos can be displayed.
-     - Grid: The videos of all users split the screen evenly. The more the users, the smaller the video dimensions. Up to 16 videos are supported.
-     - Screen sharing: This is designed for video conferencing and online education. The shared screen (or camera video of the anchor) is always displayed as the large video, which occupies the left half of the screen, and the videos of other users occupy the right half in up to two columns of up to eight small videos each. Up to 1 large video and 15 small videos can be displayed. If the upstream aspect ratio does not match the output, the large video on the left will be scaled and displayed in whole, while the small videos on the right will be cropped.
-4. Publish audio/video streams to up to 10 CDNs at a time. You can use `PublishCdnParams.PublishCdnUrl` to specify the URLs of the CDNs to publish to. To publish to Tencent Cloud’s CDN, set `PublishCdnParams.IsTencentCdn` to 1.
-5. Configure a server-side callback to have Tencent Cloud send relay status updates to your server in the form of HTTP/HTTPS POST requests. To use the callback for relay events, please contact Technical Support.
-6. The API supports four regions: Guangzhou, Shanghai, Beijing, and Hong Kong. If you relay to regions outside the Chinese mainland, select Hong Kong.
- 
-Notes:
-1. **Because On-Cloud MixTranscoding is a paid feature, calling this API will incur MixTranscoding fees. For details, see [Billing of MixTranscoding and Relay to CDN](https://intl.cloud.tencent.com/document/product/647/49446?from_cn_redirect=1).**
-2. **Relaying to third-party CDNs will incur relaying fees. For details, see [Billing of MixTranscoding and Relay to CDN](https://intl.cloud.tencent.com/document/product/647/82155?from_cn_redirect=1).**
-
-Others:
-1. You need to first call `StartPublishCdnStream` to start a relay task and get the task ID before you can use the `UpdatePublishCdnStream` API to modify the task and `StopPublishCdnStream` to stop the task.
-2. To ensure the stability of relaying, you cannot switch between relaying audio only, relaying audio and video, and relaying video only for the same task.
-3. To ensure the stability of relaying, you cannot change the video codec, audio codec, audio sample rate, audio bitrate, or sound channels using the `UpdatePublishCdnStream` API. We recommend you pass in all the other parameters when calling `UpdatePublishCdnStream`. If you only want to enable/disable transcoding, make sure you pass in all the other parameters.
-4. When you relay a single stream, specify both `AudioParams` and `VideoParams` to publish both audio and video, and specify only `AudioParams` to publish audio only. You cannot switch between the two modes during the relaying process. For `VideoParams`, set `Width`, `Height`, `Fps`, `Bitrate`, and `Gop` according to the actual settings used for publishing.
-5. The `SequenceNumber` parameter is required when you call `UpdatePublishCdnStream` to change the relaying parameters. It ensures that multiple requests for the same relaying task are in the correct order. The value of `SequenceNumber` increases each time a new request is made for the same task. If `InternalError` is returned, try again using the same `SequenceNumber`. You don’t need to handle the `FailedOperation.OutdateRequest` error.
-6. You can create a relay task before anchors enter a room, in which case you need to manually call `StopPublishCdnStream` to stop the task. If you don’t, after all the users whose streams are mixed leave the room, the TRTC backend will wait for the timeout period (`AgentParams.MaxIdleTime`) to elapse before stopping the relaying task.
+     * In a TRTC room, there may be multiple audio and video streams concurrently active. You can use the MixTranscoding API to notify Tencent Cloud server to mix multiple video screens from the same room or multiple rooms together, and specify the position of each screen, while mixing multiple audio streams together. The final result is a single audio and video stream, which can be used for recording and live viewing. It also supports pushing this mixed audio and video stream back to the TRTC room.
+
+The Cloud API MixTranscoding feature includes three interfaces:
+1. StartPublishCdnStream: Start a MixTranscoding task. This interface will initiate a new MixTranscoding task. After the task is successfully started, a unique TaskId will be returned under the sdkappid dimension. You need to save this TaskId, as it will be required for updating and stopping the task later.
+2. UpdatePublishCdnStream: Update the specified MixTranscoding task, including updating the video screen layout, updating the mixing list, updating the list of CDN addresses to be relayed, and updating the list of rooms to be pushed back.
+3. StopPublishCdnStream: Stop the specified MixTranscoding task.
+
+You can achieve the following goals through this set of interfaces:
+1. Set the final video and audio quality, including video resolution, video frame rate, video bitrate, and audio quality.
+2. Set the layout position of each screen. You only need to set it once. When you specify the MixTranscoding user to enter the room and send audio and video, the layout engine will automatically mix the user's screen to the specified layout position. You can also use the update interface to adjust the layout position.
+3. Set multiple CDN relay target addresses. A single relay task can support up to 10 CDN relay addresses at the same time.
+4. Set multiple room pushback lists. A single relay task can support up to 10 TRTC rooms for mixed stream pushback.
+
+The following layout templates are currently supported. Dynamic layout templates (floating template, grid template, screen sharing template) only support a single TRTC room, while custom templates support mixing audio and video streams from multiple TRTC rooms. The specific descriptions are as follows:
+1. Floating template: The video screen of the first user entering the room will fill the entire screen, and the video screens of other users will be arranged horizontally from the bottom left corner, displaying as small screens, with up to 4 rows and 4 screens per row. The small screens float above the large screen. It supports up to 1 large screen and 15 small screens. If the user only sends audio, it does not occupy the layout configuration by default, but it can also be set. Each sub-screen is rendered by default using the center cropping method, and the rendering method of the sub-screen can also be set uniformly.
+2. Grid template: The video screens of all users are of the same size, evenly dividing the entire screen. The more people there are, the smaller the size of each user's screen. It supports up to 16 screens. If the user only sends audio, it does not occupy the layout configuration by default, but it can also be set. Each sub-screen is rendered by default using the center cropping method, and the rendering method of the sub-screen can also be set uniformly.
+3. Screen sharing template: Suitable for video conference and online education scenarios. The screen sharing (or the main speaker's camera) always occupies the large screen position on the left side of the screen. You need to explicitly set the MixTranscoding user information that occupies the large screen. Other users are arranged vertically on the right side, with up to two columns and 8 small screens per column. It supports up to 1 large screen and 15 small screens. If the uplink resolution aspect ratio is different from the screen output aspect ratio, the large screen on the left side will be scaled to maintain content integrity, while the small screens on the right side will be cropped. The rendering method of the sub-screen can also be set uniformly.
+4. Custom layout template: Allows you to actively set the layout position according to your business needs. Each preset layout position supports named settings (named settings require specifying the room number and username) and unnamed settings. When a sub-screen is named, the position is reserved for the user, and the user will automatically occupy the position when entering the room and sending audio and video data. Other users will not occupy this position. When the preset layout position is not named, the layout engine will automatically fill in the order of entering the room. When the preset positions are full, no other users' screens and sounds will be mixed. Each sub-screen position supports setting placeholder images (BackgroundImageUrl). When the user does not enter the room or only sends audio data, the screen at this position can display the corresponding placeholder image.
+
+When using the relay API, you may incur the following costs depending on the usage characteristics:
+For MCU MixTranscoding fees, please refer to the documentation: Billing of MixTranscoding and Relay to CDN | Tencent Cloud.
+For non-Tencent Cloud CDN relay fees, please refer to the documentation: Billing of MixTranscoding and Relay to CDN | Tencent Cloud.
+
+Instructions for using parameters:
+1. AgentParams: Each relay task will pull a robot user into the TRTC room to pull the stream. You need to set this robot user through the AgentParams.UserId parameter. This robot ID cannot conflict with the normal user ID in the room, otherwise, the relay task will be abnormally terminated due to the robot user being kicked out of the TRTC room. You can avoid this by adding a special prefix. You can control the automatic termination of the relay task by setting AgentParams.MaxIdleTime. When this parameter is set, the relay task will automatically stop when all participating MixTranscoding anchors continuously leave the TRTC room for more than MaxIdleTime duration. Note: The relay task will not automatically stop when the participating MixTranscoding anchor only stops sending audio and video.
+2. WithTranscoding: If you need to mix multiple audio and video streams into one, WithTranscoding must be set to 1.
+3. AudioParams: The audio parameters and video parameters of the relay task are set separately. If you want to mix the audio of specified users, you need to explicitly set AudioParams.SubscribeAudioList. If you do not set AudioParams.SubscribeAudioList, the mixing engine will automatically mix the audio of all users in the TRTC room. If you want to mix the audio of all users in the TRTC room except for specified users, you can set the audio blacklist list through AudioParams.UnSubscribeAudioList.
+4. VideoParams: If you want to mix user videos, you can set it through VideoParams. If you only want to mix audio, you do not need to set VideoParams. You can set the screen layout mode through VideoParams.LayoutParams.MixLayoutMode, including dynamic layout (1: floating layout (default), 2: screen sharing layout, 3: grid layout) and custom layout. The dynamic layout mode is automatically mixed by the layout engine according to a fixed layout, and there is no need to set VideoParams.LayoutParams.MixLayoutList. When using the floating layout and screen sharing layout, you can specify the large screen user by setting VideoParams.LayoutParams.MaxVideoUser. The custom layout mode provides you with the ability to layout screens independently, and you can specify the layout position of each user through VideoParams.LayoutParams.MixLayoutList. In each layout parameter, you can specify the layout position for the specified user by setting the UserMediaStream parameter, or you can not set the UserMediaStream, and the layout engine will automatically fill in the order of users entering the TRTC room. In addition, you can set the rendering method (RenderMode) and cropping method (CustomCrop) for each layout position.
+5. VideoParams.WaterMarkList: If you want to overlay a watermark on the mixed screen, you can set it through VideoParams.WaterMarkList. It supports image watermarks and text watermarks and supports transparent channels.
+6. SingleSubscribeParams: If you want to push a single stream from the TRTC room to the CDN, you can set it using the SingleSubscribeParams parameter. In this case, you need to set the WithTranscoding parameter to 0.
+7. PublishCdnParams.N: If you want to push the stream to the CDN, you can set it using the PublishCdnParams.N parameter. It supports pushing to up to 10 CDN addresses at the same time. If the relay address is Tencent Cloud CDN, please set IsTencentCdn explicitly to 1; if you need to relay to a non-Tencent Cloud CDN, please contact Tencent Cloud Technical Support to enable it. Relaying to non-Tencent Cloud will incur relay fees. For fee information, please refer to the official documentation: On-Cloud Relay Billing Overview.
+8. FeedBackRoomParams.N: If you want to push the mixed audio and video stream back to the TRTC room, you can set it using the FeedBackRoomParams.N parameter. It supports pushing up to 10 streams back to the TRTC room at the same time. You need to specify the TRTC room number and robot ID (UserId) for the pushback. The robot ID cannot conflict with the normal user ID, otherwise, the relay task will be abnormally terminated due to the robot user being kicked out of the TRTC room. You can avoid this by adding a special prefix.
+9. SeiParams: If you want to add SEI information to the mixed audio and video stream, you can set it using the SeiParams parameter. It supports volume layout SEI and overlay relay request SEI. The content of the volume layout SEI is a fixed JSON structure, please see the SEI description in the following section of this chapter. You can set the SEI to follow the keyframe by setting the FollowIdr parameter. The description of the volume layout SEI is as follows:
+If your CDN audience needs to recognize the position of the participating MixTranscoding anchors and the volume information of the participating MixTranscoding anchors, you can use the volume layout SEI. The payload content and parameter description of the volume layout SEI are as follows:
+{ "app_data":"", "canvas":{ "w":1080, "h":960 }, "regions":[ { "uid":"65949987242835883c", "zorder":2, "volume":45, "x":270, "y":480, "w":540, "h":480 }, { "uid":"659c9d8d242b328d31", "zorder":2, "volume":0, "x":0, "y":0, "w":540, "h":480 }, { "uid":"64989a82272b308c", "zorder":2, "volume":91, "x":540, "y":0, "w":540, "h":480 } ], "ver":"1.0", "ts":1648544726 }
+canvas: This is the width and height of the VideoEncode setting in the MixTranscoding signaling, that is, the width and height of the entire canvas of the MixTranscoding output.
+regions: Contains the real mixed user ID and the corresponding sub-screen position. If the participating MixTranscoding user does not enter the TRTC room or does not turn on the video uplink, the regions will not include the user.
+uid: Represents the user ID participating in MixTranscoding.
+zorder: The layer of the participating MixTranscoding userid in the MixTranscoding output.
+x/y: The coordinates of the sub-screen of the participating MixTranscoding userid on the canvas.
+w/h: The size of the sub-screen of the participating MixTranscoding userid.
+volume: Represents the volume of the MixTranscoding user, with a value range of 0-100. The larger the value, the greater the volume of the user participating in MixTranscoding.
+ts: The server local second-level timestamp for outputting SEI. 
+ver: can be ignored.
+
+Usage Precautions:
+1. When using the Mixed Relay Interface, you need to call the Start Relay Task Interface (StartPublishCdnStream) first to get the Task ID from the response. Then, use the Task ID to update the relay task (UpdatePublishCdnStream) and stop the relay task (StopPublishCdnStream).
+2. The Relay API does not support initiating Automatic Bypass Tasks configured in the TRTC Console, nor does it support Custom Stream ID bypass tasks set in the TRTC SDK room entry interface.
+3. To ensure the stability of the relay link, the same relay task does not support switching between Audio only, Audio and Video, and Video only.
+4. To ensure the stability of the relay link, updating video parameters (codec) and audio parameters (codec, Sample rate, bitrate, and number of channels) is not supported during the Update Video process.
+5. When initiating a single stream bypass task, filling in both Audio Parameters and Video Parameters means Audio and Video bypass. If only Audio Parameters are filled in, it means Audio only bypass, and switching from Audio only to Audio and Video is not supported during the task progress. For Audio and Video bypass, the Width, Height, Fps, BitRate, and Gop in Video Parameters must be filled in according to the real upstream parameters.
+6. The SequenceNumber parameter must be carried in the update request to prevent request disorder. Customers must ensure that the SequenceNumber parameter increases when updating the same task, otherwise, the mix task update will fail.
+7. When calling the API, choose the region according to the following instructions: If the Application ID is 1400xxx, the region can be Beijing, Shanghai, Guangzhou, or Hong Kong. If your CDN audience is mainly overseas, please choose Hong Kong. If the Application ID is 200xxx or 400xxx, please choose Singapore.
+8. Streams pushed back to the TRTC room will not participate in the mixing of other push back room tasks. If one of the following conditions is met, it can participate in the mixing of other relay CDN tasks: (1) The push stream robot is specified to participate in the mixing in the video parameters of the relay CDN task; (2) The push stream robot is specified to participate in the mixing in the audio parameters of the relay CDN task through the whitelist method; (3) The room number of the mix user participating in the relay CDN task is completely different from the room number of the mix user corresponding to the push back robot.
+9. You can create a relay task before the anchor enters the room. When the relay task is finished, you need to call the stop interface actively. If you do not call the Stop Relay Task Interface, Tencent Cloud will automatically stop the mix relay task when all users participating in the mix have no data uploaded for a period of time exceeding the timeout (AgentParams.MaxIdleTime) set when starting the relay task.
      * @param {StartPublishCdnStreamRequest} req
      * @param {function(string, StartPublishCdnStreamResponse):void} cb
      * @public

package/tencentcloud/vod/v20180717/models.js

@@ -12284,6 +12284,12 @@ class AsrFullTextConfigureInfoForUpdate extends  AbstractModel {
          */
         this.SubtitleFormat = null;
 
+        /**
+         * Media source language value range: <li>zh: Mandarin </li> <li>en: English</li> <li>ja: Japanese </li> <li>zh-ca: Cantonese</li>
+         * @type {string || null}
+         */
+        this.SrcLanguage = null;
+
     }
 
     /**
@@ -12301,6 +12307,7 @@ class AsrFullTextConfigureInfoForUpdate extends  AbstractModel {
             this.SubtitleFormatsOperation = obj;
         }
         this.SubtitleFormat = 'SubtitleFormat' in params ? params.SubtitleFormat : null;
+        this.SrcLanguage = 'SrcLanguage' in params ? params.SrcLanguage : null;
 
     }
 }
@@ -27615,6 +27622,12 @@ class AsrFullTextConfigureInfo extends  AbstractModel {
          */
         this.SubtitleFormat = null;
 
+        /**
+         * Media source language value range: <li>zh: Mandarin </li> <li>en: English</li> <li>ja: Japanese </li> <li>zh-ca: Cantonese</li><font color=red>Note：</font> If it fills in an empty string or leave this parameter blank, it will be automatically recognized (it is recommended to fill in the language corresponding to the media to improve the recognition accuracy).
+         * @type {string || null}
+         */
+        this.SrcLanguage = null;
+
     }
 
     /**
@@ -27627,6 +27640,7 @@ class AsrFullTextConfigureInfo extends  AbstractModel {
         this.Switch = 'Switch' in params ? params.Switch : null;
         this.SubtitleFormats = 'SubtitleFormats' in params ? params.SubtitleFormats : null;
         this.SubtitleFormat = 'SubtitleFormat' in params ? params.SubtitleFormat : null;
+        this.SrcLanguage = 'SrcLanguage' in params ? params.SrcLanguage : null;
 
     }
 }