IOTY Protocol, for worldwide IoT devices
  • πŸ•ΆοΈOverview
  • πŸ’‘Introduction
    • πŸ§˜β€β™‚οΈOur vision: make accessible IoT
    • πŸš€IoT: a growth market
    • πŸ€–Problem: interoperability
    • βš™οΈHow blockchain works
      • πŸ—³οΈTrust through blockchain
      • πŸ“”Automate actions with smart contracts
    • πŸŒ€Our solution to these challenges
  • πŸ˜Άβ€πŸŒ«οΈComplex ecosystem
    • 🌐Too much diversity of technologies
    • 🚧Each network as its own standard
    • 🎊Lack of interoperability
    • β›ˆοΈCascade of isolated systems
    • 🦸Business challenges
  • πŸ›‘οΈSafety and traceability
    • πŸ’’Insecure networks
    • πŸ–²οΈIoT data difficult to track
    • *️Cyber risks
    • πŸͺŸTrust needed
  • πŸͺ…CONNECTIFY' system
    • πŸ—οΈSeamless integration into CONNECTIFY
    • β˜€οΈCONNECTIFY: a problem resolver
    • πŸͺͺOur industrialization platform
    • πŸ’»Simple interface
  • πŸ’«IOTY Protocol
    • ✨Decentralized platform
    • ✍️Message signature
    • 🫧Encrypted storage
  • πŸ”…IOTY Network
    • πŸ“±App IOTY
    • πŸ“²SDK
    • β›³Wifi Geoloc
  • πŸ’ŽUse cases
    • πŸ’ Industry 4.0
    • 🧬Healthcare
    • 🏠Smart home
    • πŸ›΅Mobility
    • πŸ™οΈSmart cities
  • 🌽Grant Program
  • πŸ’²Tokenomics $IOTY
    • β›²Token Metrics
    • πŸ¦‹Overview of the $IOTY
    • πŸ–οΈMinting Mechanism
    • ❇️Use of Proceeds
    • 🐳Utilities
  • 🎯Roadmap and go to market
    • 🧩Milestones
    • πŸ‘¨β€πŸ’ΌTechnological and partnerships
    • πŸ’ΈFund-raising
    • πŸ›’long-term roadmap
    • πŸ‘₯KPI objectives
  • 🏁To conclude
  • 🏒Compagny
    • πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦Team
    • πŸŽͺMedia kit
    • βš–οΈDisclaimer
    • πŸ’₯Risks
Powered by GitBook
On this page
  1. Complex ecosystem

Cascade of isolated systems

Sensors > Cloud > Platforms > Applications

The typical architecture of an IoT solution takes the form of a cascade of disconnected systems:

  • The connected objects themselves, which integrate sensors and connectivity solutions. They can implement different standards of transmission (LoRa, Sigfox, Kineis...). This also raises the issue of managing multiple IDs within a single device.

  • The network cloud, which receives the signal and converts it into digital data. Data received from different platforms and objects. Here too, proprietary protocols are used.

  • Platforms, which collect data from objects within range and route it to operators' servers. They use dedicated protocols to communicate with the objects.

  • Business applications that exploit this data for specific use cases (predictive maintenance, geolocation, etc.). They interact with the platforms via dedicated APIs.

Each link in this chain has its own technology and communication standards. There is no end-to-end interoperability between the sensor and the final application. It's a stack of compartmentalized systems, where every change of protocol or standard generates significant friction. The CONNECTIFY approach aims to unify this architecture through federating technologies.

PreviousLack of interoperabilityNextBusiness challenges

Last updated 1 year ago

πŸ˜Άβ€πŸŒ«οΈ
β›ˆοΈ