
AWS enables Communication Service Providers to manage Customer Premises Equipment through multiple command-and-control architectures using AWS IoT Core, supporting both legacy TR-069 and modern TR-369 (USP) standards with options for cloud, edge, or hybrid deployment models.


<div><p>This article explores CPE (Customer Premises Equipment) command and control architectures for Communication Service Providers migrating from TR-069 to the modern USP (TR-369) standard on AWS.</p><ul><li>Architecture 1: Custom agent on CPE uses AWS IoT Device Shadows for eventual consistency management</li><li>Architecture 2: Native USP agent on CPE with Lambda functions converting between USP Protobuf and JSON formats</li><li>Architecture 3: Real-time RPC architecture for immediate responses requiring direct device communication</li><li>Architecture 4: USP controllers deployed at edge via AWS IoT Greengrass for disconnected scenarios and low-latency needs</li><li>Multiple architectures support hybrid TR-069 and TR-369 coexistence during migration periods</li><li>AWS IoT Core Rules Engine decodes Protobuf messages, reducing Lambda processing overhead</li></ul><p>AWS enables CSPs to design flexible, scalable CPE management architectures supporting both legacy and modern standards with cloud and edge processing options.</p></div>


Related articles