tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Feature Overview

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-12-26 15:27:04
This document primarily outlines the approach to implement a dynamic packaging solution for Android APK multichannel at the edge using Tencent Cloud's EdgeOne, COS (Cloud Object Storage), and SCF (Serverless Cloud Function) products. Compared to traditional packaging methods, this solution provides a one-stop dynamic packaging and acceleration capability, reducing the maintenance complexity of multichannel APK packages and lowering the integration cost.
The solution supports multi-channel packaging based on Android APK V1/V2 signatures, where the V2 signature method is compatible with open-source multi-channel packaging solutions VasDolly and Walle. It also supports customizing channel packaging through v2-Custom to write channel information into specified blockId, meeting diverse needs for channel distribution and statistics.

Background Introduction

APK (Android Application Package) is the installation package for Android applications. When an app releases a new version, it typically requires the creation of distinct channel installation packages for each distribution channel. These packages are then uploaded to the respective application markets. After users download and install the app from a specific channel, they subsequently report data. Management personnel utilize channel identifiers to track key data for each channel, such as channel download volume, conversion rates, and other critical metrics. However, the following challenges are encountered:
1. High Maintenance Cost of Channel Packages: After completing Android app development, it is typically promoted across various channels online and offline, including online app markets, affiliate networks, search engines, and offline promotions. The total number of online and offline channel partners can reach up to thousands. Maintaining a set of channel packages for each channel incurs high costs and is inefficient.
2. Difficulty in Channel Statistics: In the scenario of having multiple channels, it is necessary to calculate the installation-to-payment conversion rates for different channels. However, traditional channel analytics rely on methods like invitation codes or manual processes, leading to suboptimal results in automated statistics.
3. Inefficient Acceleration: When using CDN for APK download acceleration, each APK channel package requires individual caching, leading to uneven acceleration effects.
Therefore, against this backdrop, EdgeOne has introduced the dynamic packaging solution for multi-channel Android APKs at the edge.

Principle Introduction

The implementation of dynamic packaging for Android APK multichannel involves the following key conditions:
1. Preprocessing of APK Package: Inject blank data into the APK parent package and process it into a valid file.
2. Channel Information Injection during APK Package Download: Dynamically inject channel information into the appropriate location of the APK package when the user initiates a download operation, returning the modified APK for user download.
By employing the above approach, the decoupling of preprocessed APK packages and the channel information injection operation is achieved. The entire solution process is illustrated in the diagram below:

Solution Advantages

1. Reduced Channel Package Maintenance Costs: Developers only need to maintain an original Android APK parent package, eliminating the need to manage individual packages for each channel partner. EdgeOne provides default packaging tools, allowing users to deploy easily through simple UI configuration templates, significantly enhancing the efficiency of multichannel packaging.
2. Accurate and Efficient Channel Statistics: Users can trigger edge functions by accessing a URL with channel parameters, dynamically inserting channel identifiers into the APK package, and returning it for user download. Simultaneously, data reporting and statistics are efficiently completed.




Directions

Suppose you are a game manufacturer with a new Android app game (example: v2_src.APK) that you want to release across various channels to increase exposure and attract more players. These channels may include major app markets, app stores, social media platforms, game forums, advertising platforms, etc. Your goal is to efficiently inject channel identifiers, track channel revenue, and accelerate the download of the APK for each channel. The distribution will be centralized using the domain apk.example.com.




ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック