What should be a home telecommunications system?
I propose to consider, think about the concept of a home telecommunications system (Home Telecommunication System, HTS), and more specifically, its infrastructure.
Why do you need? In order to use their gadgets, PCs and other various electronic devices, at least somehow using (or potentially capable of) information flows, whether it be data transmission in all its forms or various analog audio, video, ...
And how to do it? It is possible (and necessary! But impossible on the knees, even if only because of the concept) to assemble from all the already existing enterprise solutions.
For the time being, very common words sound; a little more detailed and concrete thought on the tree will flow further.
The purpose of the article: to create the most understandable representation of what should be modern HTS; throw grains :).
HTS Stack - Classic:
1) physical infrastructure of data transmission, ore infrastructure.
2) intellectual management of this infrastructure, system (and, possibly, user) services.
These are basic, basic tasks. The rest will grow over them already. The rest is existing and future software and devices, which will do, as it seems to me, the main features for the user and cash for software / device manufacturers. The analogy with computers is quite acceptable: a technically standardized market, on the basis of which a huge amount (including in $) of software and related hardware has grown. In other words: computers are HTS, software on computers are applications in HTS and a bunch of devices. He brought the analogy with the computers also because it clearly shows how HTS can be turned into a tangible product for producers and consumers from the next manila period (I will sometimes broadcast it with stamps).
HTS is just the next step in the way people work with information around a person in their home environment. And the next stage is the work of a single HTS network (Global HTS, GHTS).
By default, we are talking about the space inside the apartment, cottage, private house (hereinafter referred to as all types types “home”) and the surrounding space. We consider everything for the household market, the home user.
First, typical user scenarios and their solution (disordered and non-systemic, with intersections).
Task: Move around your home with WiFi, Bluetooth devices (including stationary), without thinking about the location of the equipment (access points, AP), collisions with other equipment, their own household appliances and neighbors ...
Solution: WiFi and Bluetooth (BT) networks with controller and AP.
')
Task: To watch, listen and even transfer media content with minimal gestures, almost without thinking where to which regular audio-video (AV) cable to throw, how to set up broadcast over the network, etc.
Solution: (and here, briefly again, only common words) The introduction (and refinement) of surviving and promising standards relating to the transmission and playback of multimedia on various devices.
Banal household example: playing audio stream from a smartphone. The smartphone clings to BT headphones. Went around the corner, "unsuccessfully" turned away - and that's all. How to change the situation, without changing anything in user devices? In the house, there is a BT network, and the headphones and the smartphone are connected not to each other, but to the BT network; further obvious.
Task: To have the fastest and most reliable communication with the outside world, not scoring, through what is better here and now - your cable Internet, 4G, up to public WiFi, the neighboring network (if there is also HTS) ...
Solution: Find, analyze and optimally use all available resources (= communication channels) with the outside world.
Task: Communicate with text, voice, video, without hesitation (further - see p.3).
Solution: On top of the decision p.3
Task: Securely store your (and not your) diverse data.
Solution: DSS using all available internal and external resources.
Task: (auto) management of engineering systems at home.
Solution: you need a “brain” with connection to these engineering systems.
[what else is needed at home?]
Quickly go through each item that we have today for each part.
Here iron realization interests - suddenly the bike is already there; Data transmission technology can not yet be discussed: we have onboard WiFi, BT.
Only full-fledged WiFi controllers that can fully interact with clients, listen to interference and other people's networks are suitable for our task, then, based on all the data received on the autopilot, optimally distribute power, frequencies and even radiation directivity of their APs (phase antennas). The closest are non-cheap systems from the SMB segment, in which the functionality has been cut. As far as I understand, now smart systems are gradually occupying a niche ( for example , and there is no longer a mesh).
There are no network solutions for BT. If there is, then a unique, non-standard, approximately as in the article Tarson and in the comments to it.
Unlike the previous paragraph, here, on the contrary, it is not the devices that are interested, but the standards and protocols used — what the infrastructure should support.
Well, there is a decent set of technologies, from conditionally standard / universal Miracast ), DLNA ) to vendor / proprietary AirPlay , Google Cast , WiDi and (for now?) Exotic WHDI . Looking into a ghostly future, if protocols such as WiGig are launched, multimedia standards will drastically change / be created.
Total: we have a zoo without a clear leader.
They are also interested in the protocols / standards by which our house looks outside (and outside they look at our house). You can, if desired, to do the classification, for example: wired and wireless, digital and analog, etc. While it is enough to list.
1. Of course, copper Ethernet, which is 10/100 / 1000Base-T. And even 10G.
2. The same, but optics. Here we remember the built-in and SFP-interfaces. The latter are not present in the equipment for the house, but why not.
3. We slightly grab the responsibility of the operator / provider - various xPONs , as well as various branches / developments like GEPON.
4. Gradually dying off xDSL . I suspect that technology is alive and well in many places on the planet, so we leave it.
5. Mobile (which is cellular) communication. Generations from 2G to 4G with a 5G sight (short label - at the bottom of the article ). In addition to the standards themselves, we also remember about the variations of frequencies used by countries.
6. Satellite communication. Within our system - as another (Ethernet) channel.
7. Public WiFi. Visible open WiFi networks.
8. Digital TV broadcast , five groups of formats ATSC, DMB, DTMB, DVB, ISDB. Looking ahead, we can immediately say - we drop the analog broadcasting, it is too expensive in terms of processing resources to push it into the home system.
9. Analog telephone lines (FXO).
Communication takes place through the PSTN , today including from analog lines to mobile operators, and the Internet has not yet been regulated by government bureaucracies. User terminals, from hardware to software: analog devices, mobile phones, specialized (video, SIP, DECT, etc.) terminals, software on devices.
At the moment, an average family has a decent variety of hardware and software clients that are almost completely unrelated to each other and work on virtually all internal and external communication channels. Each person has a whole set of devices, and even if one discards all the little / rarely used ones and leaves the smartphone, then there is a zoo of applications on it.
Typical: in smartphones (photo), on computers (everything), for advanced - “clouds”. Particularly advanced (% shares) are able to synchronize semi- and automatically.
There are no solutions for the average user, which allows to store and use their data qualitatively (reliably, quickly, safely, on different devices, etc.) without recesses in the IT world.
For all the previous tasks there is some kind of understanding, quite understandable sets and combinations of technologies, devices. Immediately, once again bumping into another article about the smart home, something like “damn both your homes” is usually pulled out. Who in what is ready, and what just is not invented by the devil knows how many strange (for the house) technologies. All solutions out of the box are reduced to about a light bulb / outlet, controlled from a telephone (oh yeah, smart home!). Everything else looks monstrous, not replicable, expensive.
So far with a stretch, more like the future than the present, purely software solutions such as Alexa (Amazon) , Siri (Apple) , Google Assistant , Alice (Yandex) can be counted as smart home. Very similar to the fact that such a smart home control in the coming years should be de facto. So far, practical implementations, for example, Home Sapiens (thanks for the hint to readers), have not fired.
So, what we have. User requirements are poorly correlated with real implementations. There is no complete solution. The situation for each type of functionality is approximately the same as in the tablet about WiFi.
How does the HTS.
The complex is built according to the principles of software-defined (SDx) systems under AI control (I use it not for the sake of convenience, but only for the essence of the truth for the sake of). Basically, HTS should work no longer in the traditional paradigm (especially with handles of stuffed) templates, but in real-time, to dynamically provide the optimal telecom. Wednesday at any time.
HTS combines elements of both a centralized system (there is a core) and a decentralized one (the components have some autonomy). Within the framework of GHTS, respectively, there is a common interaction logic within the GHTS and there is a full autonomy mode of HTS.
All system management is performed by the main and mandatory component of the MainBox ; it is the core and brain of the system. The remaining components (denoted as xBox) are optional, have their own specializations, contain a minimum of intelligence, but sufficient, for example, to work in the current mode when the kernel rolls off.
WLBox provides all possible wireless interfaces.
MediaBox is designed to connect media devices (TV, monitors, computers) in HTS.
OutWLBox is the WLBox option for installation as close as possible to the edges of the room, and for private households and outside the house. Among other things, provides communication with mobile operators.
mWLBox is a truncated version of the WLBox to support the most common WiFi and BT protocols. The more of them in the house, the better.
All interfaces between all HTS components — 1 / 2.5 / 5 / 10G Ethernet, WiFi, and HomePlug — work as one communication channel. Each HTS component has these three sets of interfaces on board.
All external wired communications are also via MainBox , wireless - primarily through OutWLBox . The larger the AP, the less their transmit power, the more segmented the radio band.
Each wireless interface of each component operates within its own distributed network. Network controllers (which are in MainBox ) know about each other and use this info (there is a conditional "supercontroller"). We get:
- optimal use of the radio frequency range within the HTS;
- no collisions within each network and between HTS networks;
- minimizing problems with other (unmanaged HTS) sources of interference;
- individual monitoring of the state of each user device, providing it with the maximum channel capacity;
- automatic roaming and handover;
- And still a number of specific and not very opportunities.
Wireless networks require minimization of the distances between components due to the characteristics of the BT and WiFi protocols. In particular, small areas of maximum data transfer rate. Especially for this purpose - mWLBox .
In the ideal case, when your HTSs are also deployed in neighboring apartments and there is a connection between them (the higher-speed, the better), all the listed features work even more efficiently - all neighboring HTSs automatically not only agree with each other about the use of the radio band, but also they are trying to create a single network (taking into account certain restrictions, for example, prohibiting or severely limiting the use of external connections of a neighboring HTS with limited traffic).
On top of this topology, a distributed storage and file transfer system (let's call it DSSEF - Distributed System Storage and Exchange File) is launched, acting for the benefit of both users and operator (s) GHTS. Current types of DSSEF - IPFS , DeNet
Common to all HTS components:
- food both from the power supply network, and on PoE (except the MainBox itself);
- interfaces for work in the HTS network - 1 / 2.5 / 5 / 10G Ethernet, WiFi and HomePlug;
- have the most common interfaces for working with user devices, such as WiFi and BT;
- stuffing (except for MainBox ) - bundles of SoC + FPGA;
- On board a set of Big Brother to work smart home; something like this: camera, microphone, speaker, various sensors (movement, temperature, humidity, light, etc.); there is also a separate serious section for study;
- all the logic of radio interfaces, from management to radio modules - reprogrammable ( an example of a similar ideology), which will allow eliminating bugs, choosing regional patterns, changing parameters when changing regional standards without changing iron and without user input;
- the mode of preserving the maximum efficiency with the loss of the kernel
It includes a server, a switch, a set of wireless interfaces and a UPS.
On the server to spin the entire set of software - virtual (s) / OS, controllers, etc. The composition of iron (processor, memory) will be clear after specifying tasks, understanding the composition of software. Very pre-desktop processor level Core i5 / i7, Ryzen 5/7.
The switch, as in all other components, works on the principle of SDN. Ethernet ports looking inside an HTS network are no worse than PoE + (30 W). Ideally, 60 watts. Also through it are all wired connections outside to service providers (Communications service provider, CSP).
UPS provides the entire complex with power supply. It is built on the ideology of online transformation (perhaps something similar to the study of R4ABI ).
Component providing network connections:
- inside HTS;
- HTS with home devices;
- between HTSs within GHTS.
A kit like this:
- WiFi: 802.11ac and 802.11n with development to ax , ad with development to ay , aj, af , ah ;
- BT: BT 5 ;
- IoT: Zigbee , Z-Wave , LPWAN Kit;
- DECT;
- Ethernet: autosense 1 / 2.5 / 5 / 10G (PoE 802.3bt Type 4 - for MainBox exactly; perhaps for the components that the user will plug into the power grid). For a network of HTS components and for connecting home devices;
- HomePlug: HomePlug AV2 ;
- Femtocell (or Picocell): under a big question (you have to dig).
Lists the desired specification. There is a convention broken down by groups; for example, part of the WiFi standards are also used for IoT. All protocols / standards are in maximum implementation. The result should be a compromise, first of all, between the technical functionality, size, compatibility. An antenna-feeder system covering all (or the vast majority) implementations of the interfaces used should be designed. Requires serious R & D.
Strongly truncated version of the WLBox with the most common interfaces (WiFi, BT) for installation in conditional "white" spots. The more installed in the house, the better.
It provides the operation of user devices at the border of the house, communication with external wireless networks: cellular operators, satellite navigation systems. Main tasks:
- coverage of internal and immediate external borders of the house;
- communication with user devices outside the house, their allocation from a high-speed intrahouse network;
- voice communication and data transmission over networks of cellular operators;
- geolocation on satellite navigation systems;
- connect with neighboring HTS;
- connection with adjacent open WiFi networks (backup channel in case of main accident).
Mounted on the edge of the house; options:
- flat: by the window, on the balcony / loggia;
- private house: by the window, from the outside of the wall.
The set of interfaces is similar to the WLBox with a smaller number of Ethernet and USB ports, plus cellular operators ( 3/4 / 5G) satellite global and regional navigation systems (GPS, GLONASS, ...).
In the future, for private homes, you can develop a separate version of OutWLBox for installation on the roof.
Component that provides media devices in the HTS. In fact, consists of two parts: a set of wireless interfaces and MediaCenter . The composition of the set of wireless interfaces is similar to the WLBox with possible minor adjustments. If a MediaBox is installed in the room, then WLBox in the same room will most likely be redundant.
MediaCenter Tasks:
- transfer of multimedia (audio, video) stream to display / voice devices (monitors, TV, projectors, various audio amplifiers) via standard multimedia interfaces (HDMI, DVI, DisplayPort, Thunderbolt, analog audio);
- work on wireless standardized and vendor protocols with their supporting devices (see p.2.2);
- receiving multimedia stream through standard interfaces from user devices.
The system is very complex in terms of hardware, and especially software. Soft, eat-but, must be accompanied. And all this should be sold on a large scale, and not within the limits of one country.
It seems to me that the development of such a system can be pulled only by giants of the type (in alphabetical and not probabilistic order) of Cisco, Google, HP, Huawei and the like [in a couple of these offices threw up their offer (in another form, it eats but :)) - full ignore]. Why - the reason has already been said: even the components are very difficult to implement, and what can we say about the system in the complex? For example, just look at how long and painfully these same companies build only their WiFi solutions. Similar to network monitoring. And when did the concept of SDN appear, and where is it now? And so you can go through many key things.
On the other hand, there are a number of reasons why the idea of ​​HTS inside these offices most likely will not shoot.
The idea of ​​a company from scratch to implement (at least, development) HTS is tempting. In addition to decent financial investments and competent (yes, it is already ridiculous, but let me fantasize) the management will remain the most important thing - sales.
Above is just one of the options for the system. Good for its huge potential, bad cumbersome because of the fundamental approach, similar to large corporate systems. Most likely, such systems will evolve differently, in the opposite direction - from small to large. Now you can see the first shoots, very slowly approaching from all sides. Gradually, a large number of disparate conditionally “smart” devices appear, from the glorified light bulb to more or less complex smart homes.
One of the options for starting the implementation of the idea is to develop the architecture of the entire solution, but to create and implement a system consisting only of the first kernel version as a router with some minimal set of functionality and mWLBox with the expectation that only the full-featured kernel will be replaced later. Further, the system can be upgraded with different components, whether it be power outlets, various clocks, small audio speakers, and numerous other devices that already exist and surrounding us — you can embed a lot of HTS components into them.
As I see it, HTS, especially GHTS, which implements "smart" telecom. The infrastructure of the house has a huge mutually beneficial potential for all participants in the system (hardware and software manufacturers, vendors, network and service operators, and, of course, users).
Why do you need? In order to use their gadgets, PCs and other various electronic devices, at least somehow using (or potentially capable of) information flows, whether it be data transmission in all its forms or various analog audio, video, ...
And how to do it? It is possible (and necessary! But impossible on the knees, even if only because of the concept) to assemble from all the already existing enterprise solutions.
For the time being, very common words sound; a little more detailed and concrete thought on the tree will flow further.
The purpose of the article: to create the most understandable representation of what should be modern HTS; throw grains :).
HTS Stack - Classic:
1) physical infrastructure of data transmission, ore infrastructure.
2) intellectual management of this infrastructure, system (and, possibly, user) services.
These are basic, basic tasks. The rest will grow over them already. The rest is existing and future software and devices, which will do, as it seems to me, the main features for the user and cash for software / device manufacturers. The analogy with computers is quite acceptable: a technically standardized market, on the basis of which a huge amount (including in $) of software and related hardware has grown. In other words: computers are HTS, software on computers are applications in HTS and a bunch of devices. He brought the analogy with the computers also because it clearly shows how HTS can be turned into a tangible product for producers and consumers from the next manila period (I will sometimes broadcast it with stamps).
HTS is just the next step in the way people work with information around a person in their home environment. And the next stage is the work of a single HTS network (Global HTS, GHTS).
By default, we are talking about the space inside the apartment, cottage, private house (hereinafter referred to as all types types “home”) and the surrounding space. We consider everything for the household market, the home user.
First, typical user scenarios and their solution (disordered and non-systemic, with intersections).
1. User requests
1.1. Freedom of movement (mobility)
Task: Move around your home with WiFi, Bluetooth devices (including stationary), without thinking about the location of the equipment (access points, AP), collisions with other equipment, their own household appliances and neighbors ...
Solution: WiFi and Bluetooth (BT) networks with controller and AP.
')
1.2. Freedom of Multimedia
Task: To watch, listen and even transfer media content with minimal gestures, almost without thinking where to which regular audio-video (AV) cable to throw, how to set up broadcast over the network, etc.
Solution: (and here, briefly again, only common words) The introduction (and refinement) of surviving and promising standards relating to the transmission and playback of multimedia on various devices.
Banal household example: playing audio stream from a smartphone. The smartphone clings to BT headphones. Went around the corner, "unsuccessfully" turned away - and that's all. How to change the situation, without changing anything in user devices? In the house, there is a BT network, and the headphones and the smartphone are connected not to each other, but to the BT network; further obvious.
1.3. Access to the outside world (where the Internet, of course, the main)
Task: To have the fastest and most reliable communication with the outside world, not scoring, through what is better here and now - your cable Internet, 4G, up to public WiFi, the neighboring network (if there is also HTS) ...
Solution: Find, analyze and optimally use all available resources (= communication channels) with the outside world.
1.4. Communication people
Task: Communicate with text, voice, video, without hesitation (further - see p.3).
Solution: On top of the decision p.3
1.5. Data storage
Task: Securely store your (and not your) diverse data.
Solution: DSS using all available internal and external resources.
1.6. Smart House
Task: (auto) management of engineering systems at home.
Solution: you need a “brain” with connection to these engineering systems.
[what else is needed at home?]
2. Reality + small perspective view
Quickly go through each item that we have today for each part.
2.1. Mobility
Here iron realization interests - suddenly the bike is already there; Data transmission technology can not yet be discussed: we have onboard WiFi, BT.
| Properties | Home router | + repeaters | Smart systems | Budget from corporate ( Small Medium Business ) |
|---|---|---|---|---|
| Functional | 1 AP | several APs (mesh, but not always): poor use of FBand , lower speed | Most likely, there is no network auto-optimization | |
| Difficulty of use | almost plug'n'play | relatively simple setup | plug'n'play | qualification required |
| Cost of | $ | $$ | $$$ | $$$$ |
Only full-fledged WiFi controllers that can fully interact with clients, listen to interference and other people's networks are suitable for our task, then, based on all the data received on the autopilot, optimally distribute power, frequencies and even radiation directivity of their APs (phase antennas). The closest are non-cheap systems from the SMB segment, in which the functionality has been cut. As far as I understand, now smart systems are gradually occupying a niche ( for example , and there is no longer a mesh).
There are no network solutions for BT. If there is, then a unique, non-standard, approximately as in the article Tarson and in the comments to it.
2.2. Multimedia
Unlike the previous paragraph, here, on the contrary, it is not the devices that are interested, but the standards and protocols used — what the infrastructure should support.
Well, there is a decent set of technologies, from conditionally standard / universal Miracast ), DLNA ) to vendor / proprietary AirPlay , Google Cast , WiDi and (for now?) Exotic WHDI . Looking into a ghostly future, if protocols such as WiGig are launched, multimedia standards will drastically change / be created.
Total: we have a zoo without a clear leader.
2.3. Communication with the outside world
They are also interested in the protocols / standards by which our house looks outside (and outside they look at our house). You can, if desired, to do the classification, for example: wired and wireless, digital and analog, etc. While it is enough to list.
1. Of course, copper Ethernet, which is 10/100 / 1000Base-T. And even 10G.
2. The same, but optics. Here we remember the built-in and SFP-interfaces. The latter are not present in the equipment for the house, but why not.
3. We slightly grab the responsibility of the operator / provider - various xPONs , as well as various branches / developments like GEPON.
4. Gradually dying off xDSL . I suspect that technology is alive and well in many places on the planet, so we leave it.
5. Mobile (which is cellular) communication. Generations from 2G to 4G with a 5G sight (short label - at the bottom of the article ). In addition to the standards themselves, we also remember about the variations of frequencies used by countries.
6. Satellite communication. Within our system - as another (Ethernet) channel.
7. Public WiFi. Visible open WiFi networks.
8. Digital TV broadcast , five groups of formats ATSC, DMB, DTMB, DVB, ISDB. Looking ahead, we can immediately say - we drop the analog broadcasting, it is too expensive in terms of processing resources to push it into the home system.
9. Analog telephone lines (FXO).
2.4. Communication people
Communication takes place through the PSTN , today including from analog lines to mobile operators, and the Internet has not yet been regulated by government bureaucracies. User terminals, from hardware to software: analog devices, mobile phones, specialized (video, SIP, DECT, etc.) terminals, software on devices.
At the moment, an average family has a decent variety of hardware and software clients that are almost completely unrelated to each other and work on virtually all internal and external communication channels. Each person has a whole set of devices, and even if one discards all the little / rarely used ones and leaves the smartphone, then there is a zoo of applications on it.
2.5. Data storage
Typical: in smartphones (photo), on computers (everything), for advanced - “clouds”. Particularly advanced (% shares) are able to synchronize semi- and automatically.
There are no solutions for the average user, which allows to store and use their data qualitatively (reliably, quickly, safely, on different devices, etc.) without recesses in the IT world.
2.6. Smart House
For all the previous tasks there is some kind of understanding, quite understandable sets and combinations of technologies, devices. Immediately, once again bumping into another article about the smart home, something like “damn both your homes” is usually pulled out. Who in what is ready, and what just is not invented by the devil knows how many strange (for the house) technologies. All solutions out of the box are reduced to about a light bulb / outlet, controlled from a telephone (oh yeah, smart home!). Everything else looks monstrous, not replicable, expensive.
So far with a stretch, more like the future than the present, purely software solutions such as Alexa (Amazon) , Siri (Apple) , Google Assistant , Alice (Yandex) can be counted as smart home. Very similar to the fact that such a smart home control in the coming years should be de facto. So far, practical implementations, for example, Home Sapiens (thanks for the hint to readers), have not fired.
So, what we have. User requirements are poorly correlated with real implementations. There is no complete solution. The situation for each type of functionality is approximately the same as in the tablet about WiFi.
3. System Description
How does the HTS.
3.1. Schematic topology
The complex is built according to the principles of software-defined (SDx) systems under AI control (I use it not for the sake of convenience, but only for the essence of the truth for the sake of). Basically, HTS should work no longer in the traditional paradigm (especially with handles of stuffed) templates, but in real-time, to dynamically provide the optimal telecom. Wednesday at any time.
HTS combines elements of both a centralized system (there is a core) and a decentralized one (the components have some autonomy). Within the framework of GHTS, respectively, there is a common interaction logic within the GHTS and there is a full autonomy mode of HTS.
All system management is performed by the main and mandatory component of the MainBox ; it is the core and brain of the system. The remaining components (denoted as xBox) are optional, have their own specializations, contain a minimum of intelligence, but sufficient, for example, to work in the current mode when the kernel rolls off.
WLBox provides all possible wireless interfaces.
MediaBox is designed to connect media devices (TV, monitors, computers) in HTS.
OutWLBox is the WLBox option for installation as close as possible to the edges of the room, and for private households and outside the house. Among other things, provides communication with mobile operators.
mWLBox is a truncated version of the WLBox to support the most common WiFi and BT protocols. The more of them in the house, the better.
All interfaces between all HTS components — 1 / 2.5 / 5 / 10G Ethernet, WiFi, and HomePlug — work as one communication channel. Each HTS component has these three sets of interfaces on board.
All external wired communications are also via MainBox , wireless - primarily through OutWLBox . The larger the AP, the less their transmit power, the more segmented the radio band.
Each wireless interface of each component operates within its own distributed network. Network controllers (which are in MainBox ) know about each other and use this info (there is a conditional "supercontroller"). We get:
- optimal use of the radio frequency range within the HTS;
- no collisions within each network and between HTS networks;
- minimizing problems with other (unmanaged HTS) sources of interference;
- individual monitoring of the state of each user device, providing it with the maximum channel capacity;
- automatic roaming and handover;
- And still a number of specific and not very opportunities.
Wireless networks require minimization of the distances between components due to the characteristics of the BT and WiFi protocols. In particular, small areas of maximum data transfer rate. Especially for this purpose - mWLBox .
In the ideal case, when your HTSs are also deployed in neighboring apartments and there is a connection between them (the higher-speed, the better), all the listed features work even more efficiently - all neighboring HTSs automatically not only agree with each other about the use of the radio band, but also they are trying to create a single network (taking into account certain restrictions, for example, prohibiting or severely limiting the use of external connections of a neighboring HTS with limited traffic).
On top of this topology, a distributed storage and file transfer system (let's call it DSSEF - Distributed System Storage and Exchange File) is launched, acting for the benefit of both users and operator (s) GHTS. Current types of DSSEF - IPFS , DeNet
3.2. Components
Common to all HTS components:
- food both from the power supply network, and on PoE (except the MainBox itself);
- interfaces for work in the HTS network - 1 / 2.5 / 5 / 10G Ethernet, WiFi and HomePlug;
- have the most common interfaces for working with user devices, such as WiFi and BT;
- stuffing (except for MainBox ) - bundles of SoC + FPGA;
- On board a set of Big Brother to work smart home; something like this: camera, microphone, speaker, various sensors (movement, temperature, humidity, light, etc.); there is also a separate serious section for study;
- all the logic of radio interfaces, from management to radio modules - reprogrammable ( an example of a similar ideology), which will allow eliminating bugs, choosing regional patterns, changing parameters when changing regional standards without changing iron and without user input;
- the mode of preserving the maximum efficiency with the loss of the kernel
3.2.1. Mainbox
It includes a server, a switch, a set of wireless interfaces and a UPS.
On the server to spin the entire set of software - virtual (s) / OS, controllers, etc. The composition of iron (processor, memory) will be clear after specifying tasks, understanding the composition of software. Very pre-desktop processor level Core i5 / i7, Ryzen 5/7.
The switch, as in all other components, works on the principle of SDN. Ethernet ports looking inside an HTS network are no worse than PoE + (30 W). Ideally, 60 watts. Also through it are all wired connections outside to service providers (Communications service provider, CSP).
UPS provides the entire complex with power supply. It is built on the ideology of online transformation (perhaps something similar to the study of R4ABI ).
3.2.2. Wlbox
Component providing network connections:
- inside HTS;
- HTS with home devices;
- between HTSs within GHTS.
A kit like this:
- WiFi: 802.11ac and 802.11n with development to ax , ad with development to ay , aj, af , ah ;
- BT: BT 5 ;
- IoT: Zigbee , Z-Wave , LPWAN Kit;
- DECT;
- Ethernet: autosense 1 / 2.5 / 5 / 10G (PoE 802.3bt Type 4 - for MainBox exactly; perhaps for the components that the user will plug into the power grid). For a network of HTS components and for connecting home devices;
- HomePlug: HomePlug AV2 ;
- Femtocell (or Picocell): under a big question (you have to dig).
Lists the desired specification. There is a convention broken down by groups; for example, part of the WiFi standards are also used for IoT. All protocols / standards are in maximum implementation. The result should be a compromise, first of all, between the technical functionality, size, compatibility. An antenna-feeder system covering all (or the vast majority) implementations of the interfaces used should be designed. Requires serious R & D.
3.2.3. mWLBox
Strongly truncated version of the WLBox with the most common interfaces (WiFi, BT) for installation in conditional "white" spots. The more installed in the house, the better.
3.2.4. Outwlbox
It provides the operation of user devices at the border of the house, communication with external wireless networks: cellular operators, satellite navigation systems. Main tasks:
- coverage of internal and immediate external borders of the house;
- communication with user devices outside the house, their allocation from a high-speed intrahouse network;
- voice communication and data transmission over networks of cellular operators;
- geolocation on satellite navigation systems;
- connect with neighboring HTS;
- connection with adjacent open WiFi networks (backup channel in case of main accident).
Mounted on the edge of the house; options:
- flat: by the window, on the balcony / loggia;
- private house: by the window, from the outside of the wall.
The set of interfaces is similar to the WLBox with a smaller number of Ethernet and USB ports, plus cellular operators ( 3/4 / 5G) satellite global and regional navigation systems (GPS, GLONASS, ...).
In the future, for private homes, you can develop a separate version of OutWLBox for installation on the roof.
3.2.5. Mediabox
Component that provides media devices in the HTS. In fact, consists of two parts: a set of wireless interfaces and MediaCenter . The composition of the set of wireless interfaces is similar to the WLBox with possible minor adjustments. If a MediaBox is installed in the room, then WLBox in the same room will most likely be redundant.
MediaCenter Tasks:
- transfer of multimedia (audio, video) stream to display / voice devices (monitors, TV, projectors, various audio amplifiers) via standard multimedia interfaces (HDMI, DVI, DisplayPort, Thunderbolt, analog audio);
- work on wireless standardized and vendor protocols with their supporting devices (see p.2.2);
- receiving multimedia stream through standard interfaces from user devices.
4. General reflections
The system is very complex in terms of hardware, and especially software. Soft, eat-but, must be accompanied. And all this should be sold on a large scale, and not within the limits of one country.
It seems to me that the development of such a system can be pulled only by giants of the type (in alphabetical and not probabilistic order) of Cisco, Google, HP, Huawei and the like [in a couple of these offices threw up their offer (in another form, it eats but :)) - full ignore]. Why - the reason has already been said: even the components are very difficult to implement, and what can we say about the system in the complex? For example, just look at how long and painfully these same companies build only their WiFi solutions. Similar to network monitoring. And when did the concept of SDN appear, and where is it now? And so you can go through many key things.
On the other hand, there are a number of reasons why the idea of ​​HTS inside these offices most likely will not shoot.
The idea of ​​a company from scratch to implement (at least, development) HTS is tempting. In addition to decent financial investments and competent (yes, it is already ridiculous, but let me fantasize) the management will remain the most important thing - sales.
Above is just one of the options for the system. Good for its huge potential, bad cumbersome because of the fundamental approach, similar to large corporate systems. Most likely, such systems will evolve differently, in the opposite direction - from small to large. Now you can see the first shoots, very slowly approaching from all sides. Gradually, a large number of disparate conditionally “smart” devices appear, from the glorified light bulb to more or less complex smart homes.
One of the options for starting the implementation of the idea is to develop the architecture of the entire solution, but to create and implement a system consisting only of the first kernel version as a router with some minimal set of functionality and mWLBox with the expectation that only the full-featured kernel will be replaced later. Further, the system can be upgraded with different components, whether it be power outlets, various clocks, small audio speakers, and numerous other devices that already exist and surrounding us — you can embed a lot of HTS components into them.
As I see it, HTS, especially GHTS, which implements "smart" telecom. The infrastructure of the house has a huge mutually beneficial potential for all participants in the system (hardware and software manufacturers, vendors, network and service operators, and, of course, users).
Source: https://habr.com/ru/post/370853/
All Articles