연결된 기기의 데이터 가치를 극대화하려면 조직에서 데이터 분석을 수행할 수 있어야 합니다. 조직에서 기기를 분석 애플리케이션에 연결하는 방법에는 여러 가지가 있으며, 특정 연결된 기기 아키텍처의 이점은 조직의 사용 사례에 따라 다를 수 있습니다. 안내에 도움이 되도록 이 문서에서는 Google Cloud에서 연결된 기기 아키텍처 집합을 설명합니다. 이러한 아키텍처는 연결된 기기의 다양한 사용 사례 및 요구사항을 다룹니다.
이 문서는 Google Cloud의 IoT 아키텍처에 관한 정보를 제공하는 문서 시리즈의 일부입니다. 이 시리즈의 다른 문서에는 다음이 포함됩니다.
연결된 기기 아키텍처 개요 (이 문서) Google Cloud
독립형 MQTT 브로커: MQTT 브로커는 연결된 기기와Google Cloud 프로젝트 간과 기기 간에 양방향 통신을 제공합니다.
이 문서에서는 연결된 기기 아키텍처를 계획할 때 고려해야 하는 다음 측정기준에 따라 연결된 기기 사용 사례를 세 가지 카테고리로 그룹화합니다.
기기 수: 애플리케이션에 직접 연결된 기기 수를 고려하는 것이 중요합니다. 애플리케이션에 여러 최종 기기(예: 머신, 센서 또는 카메라)가 있고 이러한 기기가 중간 게이트웨이나 다른 기기(예: 휴대전화)에 연결되어 있는 경우 이러한 최종 기기가 애플리케이션에서 표시되고 관리되어야 하는지 여부를 파악하는 것이 중요합니다. 경우에 따라 개별 기기를 나타내야 할 수 있으며, 어떤 경우에는 중간 기기만 표시되면 됩니다.
Fleet 관리: 기기 상태 모니터링, 소프트웨어 및 펌웨어 업데이트, 구성 관리, 기타 Fleet 관리 기능과 같은 기능이 필요한지 고려하세요. 이러한 요구사항은 애플리케이션 아키텍처의 선택에 영향을 줍니다.
기기 간 메시지: 애플리케이션 아키텍처를 통한 기기 통신은 중요한 요소입니다. 예를 들어 일부 애플리케이션은 애플리케이션 아키텍처를 통해 연결된 기기 간의 통신에 종속됩니다. 다른 애플리케이션에는 기기 간에 메시지 전달 없이 각 기기와 애플리케이션 간에 엄격하게 발생하는 데이터 흐름이 있습니다.
요약 표
애플리케이션의 특성을 이해하면 사용 사례에 가장 적합한 아키텍처를 선택하는 데 도움이 됩니다. 선택을 돕기 위해 다음 표에는 이 시리즈에 설명된 각 연결된 아키텍처에서 제공하는 지원이 요약되어 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-09-09(UTC)"],[[["\u003cp\u003eOrganizations need data analysis to maximize the value of data from connected devices, and there are various ways to connect these devices to analytics applications.\u003c/p\u003e\n"],["\u003cp\u003eThis document outlines several connected device architectures on Google Cloud, addressing a variety of use cases and requirements.\u003c/p\u003e\n"],["\u003cp\u003eKey considerations when planning a connected device architecture include the number of devices, the necessity of fleet management, and the need for inter-device messaging.\u003c/p\u003e\n"],["\u003cp\u003eThe document classifies connected device use cases into three categories, considering the number of devices, fleet management needs, and inter-device communication requirements.\u003c/p\u003e\n"],["\u003cp\u003eThe document provides a summary table that compares connected architectures: MQTT Broker, IoT Platform, and device to Pub/Sub, highlighting their support for device limits, inter-device messaging, and fleet management.\u003c/p\u003e\n"]]],[],null,["# Connected device architectures on Google Cloud\n\nTo maximize the value of data from their connected devices, organizations need\nto be able to perform data analysis. There are many ways for organizations to\nconnect their devices to their analytics applications, and the benefits of\nspecific connected device architectures can vary depending on the use case of\nyour organization. To help guide you, this document describes a set of connected\ndevice architectures on Google Cloud. These architectures address a broad\nrange of use cases and requirements for connected devices.\n\nThis document is part of a series of documents that provide information about\nIoT architectures on Google Cloud. The other documents in this series\ninclude the following:\n\n- Connected device architectures on Google Cloud overview (this document).\n- [A standalone MQTT Broker](/architecture/connected-devices/mqtt-broker-architecture): An [MQTT](https://mqtt.org/) broker provides bidirectional communication between connected devices and Google Cloud projects, and between the devices.\n- [An IoT platform architecture on Google Cloud:](/architecture/connected-devices/iot-platform-product-architecture) An IoT platform provides additional device management capabilities along with data connectivity, which is important when you deploy a large fleet of connected devices.\n- [A direct connection to Pub/Sub](/architecture/connected-devices/device-pubsub-architecture): For data ingestion, the best choice might be for your devices to connect directly to Pub/Sub.\n- [Best practices for running an IoT backend on Google Cloud](/architecture/connected-devices/bps-running-iot-backend-securely).\n- [Best practices for automatically provisioning and configuring edge and bare metal systems and servers](/architecture/connected-devices/best-practices-provisioning-configuring-bare-metal).\n\nConnected device architectures summary\n--------------------------------------\n\nThis document groups connected device use cases into three categories, based on the following dimensions that you need to consider when you plan a\nconnected device architecture:\n\n- **Number of devices:** It's important to consider how many devices are\n directly connected to your application. If your application has many end\n devices (such as machines, sensors, or cameras), and if these devices are connected\n to an intermediate gateway or other device (such as a mobile phone),\n it's important to identify whether those end devices must be represented and\n managed in your application. In some cases you might need to represent each\n individual device; in other cases, only the intermediate device might\n need to be represented.\n\n- **Fleet management:** Consider whether you need capabilities like\n device status monitoring, software and firmware updates, configuration\n management, and other fleet management features. These requirements\n help to determine your choice of application architecture.\n\n- **Inter-device messaging:** Device communication through your\n application architecture is an important factor. For example, some\n applications depend on communication between the connected devices through\n your application architecture. Other applications have data flows that\n occur strictly between each device and your application, with no messaging\n between devices.\n\nSummary table\n-------------\n\nUnderstanding the characteristics of your application can help you to choose\nthe best architecture for your use case. To help guide your choice, the\nfollowing table summarizes the support that each of the connected architectures\nthat are described in this series offers:\n\nWhat's next\n-----------\n\n- Read about the best connected device architecture for your use case:\n - [A standalone MQTT Broker](/architecture/connected-devices/mqtt-broker-architecture):\n - [An IoT platform architecture on Google Cloud](/architecture/connected-devices/iot-platform-product-architecture).\n - [A direct connection to Pub/Sub](/architecture/connected-devices/device-pubsub-architecture).\n- Learn how to connect devices and build IoT applications on Google Cloud using [Intelligent Products Essentials](/architecture/intelligent-products-essentials-architecture).\n- Learn about practices for [automatically provisioning and configuring edge and\n bare metal systems and servers](/architecture/best-practices-provisioning-configuring-bare-metal).\n- For more reference architectures, diagrams, and best practices, explore the [Cloud Architecture Center](/architecture)."]]
