tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
DocumentaçãoCloud Object StorageAPI DocumentationData Processing APIsAI-Based Content RecognitionHuman Recognition

Human Recognition

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2026-01-09 22:12:42

Feature Overview

Tencent Cloud DataV provides human body recognition and outputs video images through the AIBodyRecognition interface, including their positions (rectangle frames) and confidence degrees.
Note:
This interface belongs to a GET request, uses a synchronous request method, and requires carrying a signature. For specific signature settings, please see Request Signature.

Authorization Description

When using with a sub-account, the ci:CreateBodyRecognitionJob permission is required. For details, see CI action.

Service Activation

Using this feature requires enabling Cloud Infinite in advance and binding a bucket. For details, see Bind Bucket.
Use this feature requires enabling AI Content Recognition service in advance via console or API. For details, see Enable AI Content Recognition Service.

Use Limits

When using this API, please first confirm the relevant restrictions. For details, see Usage Limits.


Request Syntax

GET /ObjectKey?ci-process=AIBodyRecognition&detect-url=<detect-url> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Note:
Authorization: Auth String (See Request Signature document.)

Request Content

Parameter Name
Description
Type
Required or Not
ci-process
Cloud Infinite processing capability Human recognition fixed as AIBodyRecognition
String
Yes
ObjectKey
object filename, for example picture.jpg
String
No
detect-url
You can handle any publicly accessible image link by filling in detect-url. If detect-url is not specified, the backend will default to processing the ObjectKey. If detect-url is filled in, the backend will process the detect-url link, and there is no need to fill in the ObjectKey.
example for detect-url: http://www.example.com/abc.jpg, needs to be url encoded, processed result is
http%25253A%25252F%25252Fwww.example.com%25252Fabc.jpg
String
No

Request header

This API only uses common request headers. For details, see Common Request Headers documentation.

Request body

This request has no request body.

Response

Response Headers

This API only returns the public response header. For details, see Common Response Headers documentation.

Response Body

The response body is returned as application/xml. The specific data content is as follows:
Node Name (Keyword)
Parent Node
Description
Type
RecognitionResult
None.
Container for saving Logo recognition results
Container
The content of Response
Node Name (Keyword)
Parent Node
Description
Type
Status
RecognitionResult
Human recognition result. 0 indicates no recognition, 1 indicates recognition.
Int
PedestrianInfo
RecognitionResult
Human recognition results, possibly multiple.
Container
LogoInfo node content:
Node Name (Keyword)
Parent Node
Description
Type
Name
PedestrianInfo
Recognition type, default for human recognition: person
String
Score
PedestrianInfo
Confidence degree of human body, value range [0-100]. Higher value indicates higher probability.
String
Location
PedestrianInfo
Coordinates of human body detected in figure
Container
Location node content:
Node Name (Keyword)
Parent Node
Description
Type
Point
Location
Coordinate point of human body (X coordinate, Y coordinate)
String

Example

Request

GET /?ci-process=RecognizeLogo&detect-url=<detect-url> HTTP/1.1
Host: examplebucket-1250000000.cos.ap-chengdu.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 414641
Date: xxxxxx
Server: tencent-ci
x-cos-request-id: NTk0MjdmODlfMjQ4OGY3XzYzYzhfMjc=

<RecognitionResult>
    <Status>1</Status>
    <PedestrianInfo>
        <Name>person</Name>
        <Score>90</Score>
        <Location>
            <Point>162,266</Point>
            <Point>162,716</Point>
            <Point>392,716</Point>
            <Point>392,266</Point>
        </Location>
        <Name>person</Name>
        <Score>89</Score>
        <Location>
            <Point>682,162</Point>
            <Point>682,479</Point>
            <Point>783,479</Point>
            <Point>783,162</Point>
        </Location>
    </PedestrianInfo>
</RecognitionResult>

Anterior: Face EffectPróximo: Pet Recognition

Ajuda e Suporte

Esta página foi útil?

comentários