You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of thinking about infrastructure only, networks, data, service, capabilities are all hyperlocal. Start thinking in terms of the overlapping of network transports and types of networks that are found. You should be able to discover the network transport sources and distinguish between the hyperlocal range (1-1000+) and use this as a mechanism for filtering, and also handling context switching:
Hyperlocal context range
1 feet (personal area network)
3 feet (personal area network)
5 feet (hyperlocal networks)
10 feet (hyperlocal networks)
30 feet (hyperlocal tidal zone to infrastructure networks)
50 feet (infrastructure networks)
100 feet (infrastructure networks)
300 feet (infrastructure networks)
1000 feet (wide area network)
1000+ feet (Metro area networks)
Scenarios
move from house to car
move from downstairs in house to upstairs
move from home to work
move from outside street to a starbucks
In every case the networks available and service will change. Currently our TCP/IP networks are still very dumb and don't really do anything to advertise services, and most discovery mechanisms are proprietary or are OS specific.
So in the cases above, how would we manage : security, advertisement of services, discovery of services, utilization of services.
The text was updated successfully, but these errors were encountered:
In the spirit of AI, AI needs contextual awareness badly. Contextually aware devices can do a better job at not doing a bad job at asking for the right things from AI models and Agents.
Instead of thinking about infrastructure only, networks, data, service, capabilities are all hyperlocal. Start thinking in terms of the overlapping of network transports and types of networks that are found. You should be able to discover the network transport sources and distinguish between the hyperlocal range (1-1000+) and use this as a mechanism for filtering, and also handling context switching:
Hyperlocal context range
Scenarios
In every case the networks available and service will change. Currently our TCP/IP networks are still very dumb and don't really do anything to advertise services, and most discovery mechanisms are proprietary or are OS specific.
So in the cases above, how would we manage : security, advertisement of services, discovery of services, utilization of services.
The text was updated successfully, but these errors were encountered: