[{"data":1,"prerenderedAt":605},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-iot-system-integration-four-layers":106,"article-related-zh-tw-iot-system-integration-four-layers":588},{"@context":4,"@graph":5},"https:\u002F\u002Fschema.org",[6,85,97],{"@type":7,"@id":8,"name":9,"alternateName":10,"description":17,"knowsAbout":18,"legalName":27,"foundingDate":28,"numberOfEmployees":29,"taxID":30,"url":31,"logo":32,"founder":33,"contactPoint":35,"address":49,"location":55,"sameAs":75},"Organization","https:\u002F\u002Fjoinx.co\u002F#organization","JoinX哲煜科技",[11,12,13,14,15,16],"JoinX","TWJOIN","哲煜科技","哲煜科技股份有限公司","TWJOIN 哲煜科技","twjoin.com","JoinX 哲煜科技（原品牌名 TWJOIN）是 2016 年在台北成立的軟體開發公司，80+ 人自有團隊，承接客製系統、APP、AI 導入與 IoT 開發，以及軟體外包與既有系統接手維運，服務 220+ 客戶、完成 520+ 專案。",[19,20,21,22,23,24,25,26],"軟體外包","客製化系統開發","APP 開發","AI 導入","AI Agent 開發","IoT APP 開發","ERP 系統整合","既有系統接手維運","JoinX Co., Ltd.","2016-04-28",80,"43774383","https:\u002F\u002Fjoinx.co","https:\u002F\u002Fjoinx.co\u002Fimages\u002Flogo-with-name.png",{"@id":34},"https:\u002F\u002Fjoinx.co\u002F#person-jack-lee",[36],{"@type":37,"contactType":38,"url":39,"telephone":40,"email":41,"areaServed":42,"availableLanguage":45},"ContactPoint","customer service","https:\u002F\u002Fjoinx.co\u002Fcontact-us","+886-2-8771-9095","service@joinx.co",[43,44],"TW","JP",[46,47,48],"zh-Hant","en","ja",{"@type":50,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":54,"addressCountry":43},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[56,63,69],{"@type":57,"name":58,"address":59},"Place","JoinX 台中辦公室",{"@type":50,"streetAddress":60,"postalCode":61,"addressLocality":62,"addressRegion":54,"addressCountry":43},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":57,"name":64,"address":65},"JoinX 高雄辦公室",{"@type":50,"streetAddress":66,"postalCode":67,"addressLocality":68,"addressRegion":54,"addressCountry":43},"民族一路80號2樓之一","807","高雄市三民區",{"@type":57,"name":70,"address":71},"JoinX 東京辦公室",{"@type":50,"streetAddress":72,"postalCode":73,"addressLocality":74,"addressCountry":44},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[76,77,78,79,80,81,82,83,84],"https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Ftwjoin","https:\u002F\u002Fwww.facebook.com\u002FJoinX.TW","https:\u002F\u002Ftw.linkedin.com\u002Fcompany\u002F%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fwww.youtube.com\u002Fc\u002Fjoinstuido%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fmedium.com\u002Ftwjoin","https:\u002F\u002Fwww.104.com.tw\u002Fcompany\u002F1a2x6bjomb","https:\u002F\u002Fclutch.co\u002Fprofile\u002Fjoinx","https:\u002F\u002Fwww.goodfirms.co\u002Fcompany\u002Ftwjoin","https:\u002F\u002Ftwjoin.com",{"@type":86,"@id":34,"name":87,"alternateName":88,"jobTitle":89,"worksFor":90,"url":91,"sameAs":92},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https:\u002F\u002Fjack88.joinx.co\u002F",[93,94,95,96],"https:\u002F\u002Fwww.instagram.com\u002Fjack88.podcast\u002F","https:\u002F\u002Fwww.threads.net\u002F@jack88.podcast","https:\u002F\u002Fjoinx.co\u002Fjack88\u002F","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjacklee-taiwan\u002F",{"@type":98,"@id":99,"url":31,"name":9,"alternateName":100,"publisher":101,"inLanguage":102},"WebSite","https:\u002F\u002Fjoinx.co\u002F#website",[11,13,9],{"@id":8},[103,104,105],"zh-Hant-TW","en-US","ja-JP",{"id":107,"title":108,"body":109,"category":553,"cover":554,"dateModified":555,"description":556,"extension":557,"faq":555,"hasCoverTitle":558,"locale":559,"meta":560,"navigation":561,"need":562,"path":563,"seo":564,"seoDescription":555,"seoTitle":555,"sources":565,"stem":578,"takeaways":579,"time":585,"type":586,"__hash__":587},"content\u002Fzh-tw\u002Farticle\u002Fiot-system-integration-four-layers.md","IoT 系統整合怎麼選？裝置、閘道、雲端、APP 四層的分工、驗收與費用",{"type":110,"value":111,"toc":530},"minimark",[112,120,129,134,137,218,221,225,228,289,292,296,299,302,306,309,312,315,318,322,325,359,362,366,369,446,453,457,460,465,471,475,480,484,489,492,495,499,502,506,509,513,516,520,523,527],[113,114,115,119],"p",{},[116,117,118],"strong",{},"硬體廠要讓設備連上 APP 與雲端，整合的關鍵不在某一層做得多好，而在四層之間的介面有沒有人負責。"," 裝置、閘道、雲端、APP 往往由不同團隊開發，每一層單獨測都正常，接在一起才發現指令對不上、資料格式不同。以下用四層架構說明分工、驗收與費用怎麼算。",[113,121,122,123,128],{},"如果你還在準備外包設備 APP 的需求，可以先看",[124,125,127],"a",{"href":126},"\u002Farticle\u002Fdevice-app-development-guide\u002F","設備 APP 開發：硬體廠外包前要準備的 6 件事","；這篇接著談四層整合時的分工。",[130,131,133],"h2",{"id":132},"iot-系統的四層架構是什麼","IoT 系統的四層架構是什麼？",[113,135,136],{},"四層是裝置、閘道、雲端、APP。裝置負責感測與執行，閘道負責轉換協定與轉送資料，雲端負責帳號、資料與遠端控制，APP 是使用者操作的介面。",[138,139,140,159],"table",{},[141,142,143],"thead",{},[144,145,146,150,153,156],"tr",{},[147,148,149],"th",{},"層",[147,151,152],{},"做什麼",[147,154,155],{},"常見負責方",[147,157,158],{},"主要交付物",[160,161,162,177,191,205],"tbody",{},[144,163,164,168,171,174],{},[165,166,167],"td",{},"裝置",[165,169,170],{},"感測、控制、韌體、無線連線",[165,172,173],{},"硬體廠的韌體團隊",[165,175,176],{},"韌體、通訊協定文件、射頻認證",[144,178,179,182,185,188],{},[165,180,181],{},"閘道",[165,183,184],{},"協定轉換、離線暫存、轉送到雲端",[165,186,187],{},"硬體廠，或由手機 APP 兼任",[165,189,190],{},"閘道韌體或軟體、轉送規則",[144,192,193,196,199,202],{},[165,194,195],{},"雲端",[165,197,198],{},"裝置註冊與綁定、資料儲存、遠端控制、OTA 派送、管理後台",[165,200,201],{},"軟體開發團隊",[165,203,204],{},"雲端服務、API 文件、管理後台",[144,206,207,210,213,215],{},[165,208,209],{},"APP",[165,211,212],{},"配對、控制、狀態顯示、推播、上架",[165,214,201],{},[165,216,217],{},"iOS／Android APP、上架帳號設定",[113,219,220],{},"裝置要在台灣上市，使用藍牙或 Wi-Fi 等無線射頻時，還要符合 NCC 的低功率射頻器材技術規範，這屬於裝置層，由硬體團隊負責。",[130,222,224],{"id":223},"每一層之間誰負責介面文件","每一層之間，誰負責介面文件？",[113,226,227],{},"介面要指定一方主筆、另一方簽核。四層之間有三個主要介面：裝置與 APP、裝置與雲端、雲端與 APP，任何一個沒寫清楚，整合時就會來回修改。",[138,229,230,246],{},[141,231,232],{},[144,233,234,237,240,243],{},[147,235,236],{},"介面",[147,238,239],{},"要寫清楚什麼",[147,241,242],{},"建議主筆",[147,244,245],{},"簽核",[160,247,248,262,276],{},[144,249,250,253,256,259],{},[165,251,252],{},"裝置 ↔ APP",[165,254,255],{},"配對流程、指令與回應格式、錯誤碼",[165,257,258],{},"韌體團隊",[165,260,261],{},"APP 團隊",[144,263,264,267,270,273],{},[165,265,266],{},"裝置（或閘道）↔ 雲端",[165,268,269],{},"連線方式、訊息主題與資料格式、OTA 流程",[165,271,272],{},"雙方共同，由整合方主筆",[165,274,275],{},"硬體廠",[144,277,278,281,284,287],{},[165,279,280],{},"雲端 ↔ APP",[165,282,283],{},"API 規格、帳號與權限、推播規則",[165,285,286],{},"雲端團隊",[165,288,261],{},[113,290,291],{},"裝置連雲端常用 MQTT，OASIS 的 MQTT 5.0 標準定義了發布與訂閱的訊息格式；但主題怎麼命名、資料欄位怎麼定義，標準不會替你決定，要寫進雙方的介面文件。",[130,293,295],{"id":294},"每個產品都需要閘道嗎","每個產品都需要閘道嗎？",[113,297,298],{},"不一定。藍牙裝置常由手機 APP 兼任閘道，把資料轉送到雲端；Wi-Fi 裝置可以直接連上雲端。場域內有大量低功耗感測器時，才需要獨立的閘道硬體。",[113,300,301],{},"閘道這一層最容易被忽略的是「斷線時怎麼辦」：網路中斷時資料要不要暫存、恢復後怎麼補傳、重複的資料怎麼處理。手機兼任閘道時，這些邏輯就落在 APP 裡，APP 的開發範圍也會跟著變大。",[130,303,305],{"id":304},"雲端與-app-這兩層要做到哪些事","雲端與 APP 這兩層，要做到哪些事？",[113,307,308],{},"雲端要做裝置註冊與帳號綁定、資料儲存、遠端控制、OTA 派送，以及給客服與業務用的管理後台；APP 要做配對、控制、狀態顯示、推播與上架。兩層通常由同一個軟體團隊負責，API 才好對齊。",[113,310,311],{},"資安要求也落在這兩層與裝置之間。ETSI EN 303 645 是消費性 IoT 的資安基準，要求不使用共用的預設密碼、軟體可以安全更新、通訊要加密；NIST 的 NISTIR 8259A 則列出裝置應具備的資安能力，例如裝置識別與軟體更新。",[113,313,314],{},"規格書裡把這些要求寫成每一層的驗收項目，整合時才不會變成「大家都以為別人會做」。",[316,317],"article-cta",{},[130,319,321],{"id":320},"四層整合要怎麼驗收","四層整合要怎麼驗收？",[113,323,324],{},"先分層驗收，再做跨層整合測試。每一層都對照介面文件測完，再用實機把整條流程串起來測，最後在不同品牌與版本的手機上驗證。",[326,327,328,335,341,347,353],"ol",{},[329,330,331,334],"li",{},[116,332,333],{},"裝置層","：依通訊協定文件逐一測試每個指令的回應與錯誤碼，並確認射頻認證時程。",[329,336,337,340],{},[116,338,339],{},"閘道層","：拔掉網路再接回，確認資料有暫存、有補傳、沒有重複。",[329,342,343,346],{},[116,344,345],{},"雲端層","：測試帳號綁定與解除、遠端控制的回應時間、OTA 分批派送與失敗重試，並確認後台看得到每台裝置的韌體版本。",[329,348,349,352],{},[116,350,351],{},"APP 層","：在約定的手機機型清單上測試配對、控制與推播，並完成 App Store 與 Google Play 的送審。",[329,354,355,358],{},[116,356,357],{},"跨層整合","：模擬真實情境，例如裝置斷電再開機、OTA 更新到一半中斷、使用者換手機重新登入。",[113,360,361],{},"驗收標準要在開發前寫進合約，而不是測試時才討論。JoinX 交付前會自行完成原始碼掃描與弱點掃描；需要黑箱測試時委由第三方進行，我們可以協助聯繫、推薦廠商，並修補後交付。",[130,363,365],{"id":364},"iot-系統整合的費用怎麼算","IoT 系統整合的費用怎麼算？",[113,367,368],{},"依層拆開估。裝置韌體由硬體團隊負責或另行估價；APP 與雲端後台依 JoinX 的台灣客製專案行情，單一裝置控制 APP 約 NT$50 萬至 120 萬，含雲端、推播與 OTA 的功能型約 NT$120 萬至 300 萬。",[138,370,371,388],{},[141,372,373],{},[144,374,375,378,382,385],{},[147,376,377],{},"範圍",[147,379,381],{"align":380},"right","費用區間",[147,383,384],{},"常見內容",[147,386,387],{},"時程",[160,389,390,404,418,432],{},[144,391,392,395,398,401],{},[165,393,394],{},"需求與通訊協定盤點",[165,396,397],{"align":380},"NT$10 萬～30 萬",[165,399,400],{},"盤點裝置、通訊協定與資料流，產出可比較的規格",[165,402,403],{},"2～4 週",[144,405,406,409,412,415],{},[165,407,408],{},"單一裝置控制 APP",[165,410,411],{"align":380},"NT$50 萬～120 萬",[165,413,414],{},"配對、控制、狀態顯示，含簡易後台",[165,416,417],{},"6～12 週",[144,419,420,423,426,429],{},[165,421,422],{},"功能型",[165,424,425],{"align":380},"NT$120 萬～300 萬",[165,427,428],{},"帳號與多裝置、雲端後台、推播、OTA",[165,430,431],{},"3～6 個月",[144,433,434,437,440,443],{},[165,435,436],{},"平台型",[165,438,439],{"align":380},"依需求定價",[165,441,442],{},"多品牌版本、大量裝置、資料分析或 AI",[165,444,445],{},"6 個月以上",[113,447,448,449,452],{},"閘道韌體與裝置韌體一樣，由硬體團隊負責或另行估價；雲端主機、推播與上架帳號年費依實際用量另計；上線後的維運另訂合約。完整的服務範圍可參考 ",[124,450,24],{"href":451},"\u002Fiot-app\u002F","。",[130,454,456],{"id":455},"joinx-在四層整合裡負責哪些部分","JoinX 在四層整合裡負責哪些部分？",[113,458,459],{},"JoinX 負責 APP 與雲端後台，韌體由硬體廠或原本的韌體廠商負責。開發初期先和韌體團隊確認通訊協定、指令格式與錯誤碼，開發期間用實機一起測試。",[461,462,464],"h3",{"id":463},"空調換氣設備商淨流換氣系統-app-與管理後台","空調換氣設備商：淨流換氣系統 APP 與管理後台",[113,466,467,470],{},[116,468,469],{},"做法："," 2025 年起為空調換氣設備商開發淨流換氣系統的 APP，接著擴充管理後台與 API，並另做合作品牌版本的 APP 與年度維護。",[461,472,474],{"id":473},"電子儀器公司測量儀-android-app-與-web-版","電子儀器公司：測量儀 Android APP 與 Web 版",[113,476,477,479],{},[116,478,469],{}," 2024 年起開發測量儀的 Android APP，之後追加 Web 版功能與 UI\u002FUX 優化。",[461,481,483],{"id":482},"咖啡機業者咖啡機操作-app","咖啡機業者：咖啡機操作 APP",[113,485,486,488],{},[116,487,469],{}," 2026 年起開發用手機 APP 操作咖啡機設備的 APP，上線後持續擴充功能。",[113,490,491],{},"依保密約定，以上案例以產業描述呈現。",[130,493,494],{"id":494},"常見問題",[461,496,498],{"id":497},"四層可以全部交給同一家廠商嗎","四層可以全部交給同一家廠商嗎？",[113,500,501],{},"可以，但硬體廠通常會保留裝置與韌體。比較常見的分工是硬體廠負責裝置與閘道，軟體團隊負責雲端與 APP，雙方用介面文件對齊。",[461,503,505],{"id":504},"介面文件要由誰寫","介面文件要由誰寫？",[113,507,508],{},"建議由該介面「提供資料的一方」主筆，例如裝置與 APP 之間的通訊協定由韌體團隊主筆，雲端 API 由雲端團隊主筆；另一方簽核後才開始開發。",[461,510,512],{"id":511},"已經有雲端平台只要做-app-可以嗎","已經有雲端平台，只要做 APP 可以嗎？",[113,514,515],{},"可以。前提是雲端平台的 API 文件完整，並且能提供測試環境與測試帳號。APP 團隊會先確認 API 能不能支援配對、控制與推播的需求，再估範圍。",[461,517,519],{"id":518},"裝置還在開發中四層可以同時進行嗎","裝置還在開發中，四層可以同時進行嗎？",[113,521,522],{},"可以。先約定通訊協定與 API 的草稿，各層同時開發，APP 與雲端先用模擬資料做流程，等裝置可以實機測試時再一起驗證。",[461,524,526],{"id":525},"上線後四層要怎麼維運","上線後四層要怎麼維運？",[113,528,529],{},"每一層都有各自的更新節奏：韌體靠 OTA 更新，雲端要監控與備份，APP 要配合 iOS 與 Android 每年改版。維運合約要寫清楚每一層由誰負責、問題回報後多久回應。",{"title":531,"searchDepth":532,"depth":532,"links":533},"",2,[534,535,536,537,538,539,540,546],{"id":132,"depth":532,"text":133},{"id":223,"depth":532,"text":224},{"id":294,"depth":532,"text":295},{"id":304,"depth":532,"text":305},{"id":320,"depth":532,"text":321},{"id":364,"depth":532,"text":365},{"id":455,"depth":532,"text":456,"children":541},[542,544,545],{"id":463,"depth":543,"text":464},3,{"id":473,"depth":543,"text":474},{"id":482,"depth":543,"text":483},{"id":494,"depth":532,"text":494,"children":547},[548,549,550,551,552],{"id":497,"depth":543,"text":498},{"id":504,"depth":543,"text":505},{"id":511,"depth":543,"text":512},{"id":518,"depth":543,"text":519},{"id":525,"depth":543,"text":526},"技術分享","\u002Fimages\u002Fblog\u002Fiot-system-integration-four-layers.webp",null,"硬體廠要讓設備連上 APP 與雲端，最常出問題的不是單一層做不好，而是裝置、閘道、雲端、APP 四層之間沒人負責介面。本文用四層架構說明每一層通常由誰負責、層與層之間的介面文件怎麼分工、每一層要怎麼驗收，以及費用怎麼拆開來算，並附上 JoinX 做過的設備 APP 案例。","md",false,"zh-tw",{},true,"IoT APP","\u002Fzh-tw\u002Farticle\u002Fiot-system-integration-four-layers",{"title":108,"description":556},[566,569,572,575],{"name":567,"issuer":568},"MQTT Version 5.0","OASIS",{"name":570,"issuer":571},"ETSI EN 303 645 Cyber Security for Consumer Internet of Things: Baseline Requirements","ETSI",{"name":573,"issuer":574},"NISTIR 8259A IoT Device Cybersecurity Capability Core Baseline","美國國家標準與技術研究院（NIST）",{"name":576,"issuer":577},"低功率射頻器材技術規範","國家通訊傳播委員會（NCC）","zh-tw\u002Farticle\u002Fiot-system-integration-four-layers",[580,581,582,583,584],"IoT 系統可以拆成裝置、閘道、雲端、APP 四層，每一層都要有明確的負責方與交付物。","最常出問題的是層與層之間的介面，所以通訊協定、資料格式與 API 文件要指定一方主筆、另一方簽核。","不是每個產品都需要獨立閘道：藍牙裝置常由手機當閘道，Wi-Fi 裝置可以直接連上雲端。","驗收要分層做，再做跨層的整合測試，例如斷網後重連、OTA 失敗重試、iOS 與 Android 改版後的配對。","費用依層拆開估：韌體由硬體團隊負責或另估，APP 與雲端後台依 JoinX 行情約 NT$50 萬至 300 萬，雲端主機依用量另計。","2026\u002F11\u002F04","blog","0sY2W6AVn5QG4-j8q1WsKSrkv4zggLz-lVxBSLmPufs",[589,594,599],{"slug":590,"title":591,"time":592,"cover":593,"need":562},"device-app-development-guide","設備 APP 開發：硬體廠外包前要準備的 6 件事（藍牙、Wi-Fi、韌體與上架）","2026\u002F11\u002F03","\u002Fimages\u002Fblog\u002Fdevice-app-development-guide.webp",{"slug":595,"title":596,"time":597,"cover":598,"need":562},"bluetooth-wifi-iot-business-value","藍牙、Wi-Fi 與 IoT 如何串聯設備、創造商業價值","2025\u002F09\u002F26","\u002Fimages\u002Fblog\u002Fbluetooth-wifi-iot-business-value.webp",{"slug":600,"title":601,"time":602,"cover":603,"need":604},"pos-system-guide","POS 系統怎麼選？套裝、雲端 POS 與客製 POS 的差異、硬體、串接與費用（2026）","2026\u002F11\u002F12","\u002Fimages\u002Fblog\u002Fpos-system-guide.webp","POS 系統",1794558641767]