Transcript
IEEE ICC ‘16
Dynamic M2M Device Attachment and Redirection in Virtual Home Gateway Environments Apostolos Papageorgiou, NEC Labs Europe Roberto Bifulco, NEC Labs Europe Ernoe Kovacs, NEC Labs Europe Hans-Joerg Kolbe, Deutsche Telekom AG
Background: Virtual Home Gateway
USB Ethernet WiFi ZigBee Bluetooth UPnP ……
M2M devices
Network Protocol
Operator‘s Backend System
HGW
M2M devices’ drivers
▌The complexity of the Home Gateway (HGW) is an issue More expensive (CAPEX) More difficult to operate (OPEX) More difficult to troubleshoot (OPEX) More components can fail (OPEX) More components need update (OPEX)
2
© NEC Corporation 2016
NEC Public
Background: Virtual Home Gateway
USB Ethernet WiFi ZigBee Bluetooth UPnP ……
Network Protocol HGW
M2M devices’ drivers
M2M devices
USB Ethernet WiFi ZigBee Bluetooth UPnP ……
Bridged Residential Gateway Minimalized M2M Anchor
M2M devices
3
Operator‘s Backend System
© NEC Corporation 2016
Network Protocol
Protocol Virtualization
Operator‘s Backend System
vGW
M2M devices’ drivers NEC Public
Challenges and Opportunities ▌Device attachment The M2M anchor does not know the device
Drivers/Operating system compatibility issues
▌Protocol virtualization The selection of the backend server is pre-configured The selection of the backend server is static The device’s communication flow cannot be easily identified at the network level
▌Several “servers” to handle one home’s devices Decoupling the physical attachment point from the logical mounting point Support scalability
4
© NEC Corporation 2016
NEC Public
Virtualized access to M2M devices M2M Devices
M2M anchor S/W Incl.: Virtualization S/W, e.g., USB virt. client 1 M2M server config Device-to-port mapper
Network Controller ...
SDN
3
Virtualized access, e.g., with USB virtualization
M2M
2
10.0.0.1
M2M Access Manager
vGW ..... vGW
Minimalized M2M Anchor
10.0.0.2 M2M Access Manager
vGW ..... vGW
...... ...... ......
Minimalized M2M Anchor
M2M Srv. A
Network infr., e.g., OpenFlow switches
M2M Srv. B
........ ........ ........ ........ ........ .....
10.0.0.n
M2M Access Manager
vGW ..... vGW
M2M Srv. N
Servers or VMs
5
© NEC Corporation 2016
NEC Public
High-level process for mounting M2M devices M2M anchor
NW controller
NW switch
M2M servers
Generate constant 1 port Setup virtualized connection based on the M2M anchor‘s „server number configuration“ for this 1 device Inform upon failure
2 Find 2 capable server / VM
Add re-direction rule (Device traffic) (Device traffic) (Device traffic)
6
© NEC Corporation 2016
3
(Possibly redirected device traffic)
3 (Possibly redirected device traffic) (Possibly redirected device traffic)
NEC Public
2
Decide If able to mount
1. M2M anchor „device attachment logic“
X
Device-to-port mapper Z
This source port is maintained for any communication originated from the device and destined to the M2M server;
Different devices MUST have different source port numbers.
M2M anchor S/W Incl.: Virtualization S/W, e.g., USB virt. client M2M server config Device-to-port mapper
M2M Devices
Y
Minimalized M2M Anchor
Virt. technology
Port range
USB
4000-4999
Ethernet
5000-5999
...
...
Device
Src Port
X (USB)
4550
Y (Eth)
5001
Z (USB)
4551
...
...
▌Enables the identification of the network flows related to a device without requiring DPI (Deep Packet Inspection) providing additional „lightweight“ info about its virtualization technology 7
© NEC Corporation 2016
NEC Public
2. Troubleshooting & negotiation of device mounting Server info table
USB virt.
Ethernet virt.
... virt.
Load / Stats
Drivers info
10.X.X. 1
✘
✘
✔
...
...
10.X.X. 2
✔
✘
✔
...
...
...
✘
✔
✘
...
...
3
I cannot handle incoming packets from X.X.X.X:4551
Network Controller
...
SDN 4 M2M
Attempt to mount newly attached device
2
10.X.X.1
1 M2M Access Manager
vGW ..... vGW
1. If an M2M server fails to mount a device that was just plugged in, the M2M Access Manager is informed 2. The M2M access manager triggers an M2M server selection logic in the network controller (implicit information about the virtualization technology is provided via the port number) 3. The selection logic selects a different M2M server according to information provided and based on additional constraints (e.g., server load, type, etc.) 4. The selection decision is then transferred to the SDN controller
▌The software stack of the M2M server informs directly the network about its ability to handle the connection from a given device 8
© NEC Corporation 2016
NEC Public
3. SDN-based configuration of M2M traffic Network Controller
...
SDN
The SDN controller instructs the switch to forward any packet destined to the M2M server address to an actual M2M server (Translating from the IP address configured in the M2M anchor into the M2M server real IP address)
The SDN rule redirects the flows related to a device (identified using the SRC Port) to the newly selected M2M server
...
SRC IP
DST IP
SRC Port
DST port
Action
Any
1.1.1.1
Any
1111
- Set DST IP = 10.0.0.1 - Fw-to-M2M srv. B Port
M2M Anchor
1.1.1.1
4550
1111
- Set DST IP = 10.0.0.2 - Fw-to-M2M srv. B Port
▌The network is able to selectively redirect a network flow related to a given device attached to a given M2M Anchor
9
© NEC Corporation 2016
NEC Public
Alternatives
▌No one-size-fits-all solution ▌Usually a trade-off between flexibility/costs/complexity
10
© NEC Corporation 2016
NEC Public
Conclusion ▌A solution for attaching M2M devices in a Virtual Home Gateway environment ▌Virtual Home Gateways are starting to be deployed this year More relevant in future with IoT growth
▌No one-size-fits-all solution But if an SDN network is available, many advantages can be combined
▌And now… what about applications?
11
© NEC Corporation 2016
NEC Public
