IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN: 21-12-0058- MuGM
Title: Requirements for New MIH Applications
Date Submitted: May, 15, 2012
Presented at IEEE 802.21 session #50 in Atlanta
Authors or Source(s):
Toru Kambayashi and Yoshihiro Ohba (TOSHIBA), Stephan
Chasko (Landis+Gyr)
Abstract: This document describes new use cases and securityrelated requirements which the use cases introduce. The new use
cases described here are load balancing, f/w update and
failover/failback=restoration in mesh network of smart meters.
21-12-0058- MuGM
IEEE 802.21 presentation release statements
This document has been prepared to assist the IEEE 802.21 Working Group. It is
offered as a basis for discussion and is not binding on the contributing
individual(s) or organization(s). The material in this document is subject to
change in form and content after further study. The contributor(s) reserve(s)
the right to add, amend or withdraw material contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate
material contained in this contribution, and any modifications thereof, in the
creation of an IEEE Standards publication; to copyright in the IEEE’s name
any IEEE Standards publication even though it may include portions of this
contribution; and at the IEEE’s sole discretion to permit others to reproduce in
whole or in part the resulting IEEE Standards publication. The contributor also
acknowledges and accepts that this contribution may be made public by IEEE
802.21.
The contributor is familiar with IEEE patent policy, as stated
outlined
in in
Section
Section
6 of
6.3the
of
the IEEE-SA
IEEE-SA
Standards
Standards
Board
Board
bylaws
Operations Manual
<http://standards.ieee.org/guides/opman/sect6.html#6.3> and
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6>
and in
in
Understanding Patent Issues During IEEE Standards Development
http://standards.ieee.org/board/pat/guide.html>
http://standards.ieee.org/board/pat/faq.pdf>
21-12-0058- MuGM
Glossary
• B/W - Backward
• F/W – Forward or firmware
• GM - Group Manager
• MIH - Media Independent Handover
• MIHF - Media Independent Handover Function
• MN - Mobile Node
• PoA - Point of Attachment
21-12-0058- MuGM
Target Use Cases
• Applications
• Handover for load balance
• F/W Update
• Handover in case of a system failure (failover and restoration),
etc.
Mesh Network
of Smart
Meters
Collector 1
Mesh Network
of Smart
Meters
Collector 2
Mesh Network
of Smart
Meters
21-12-0058- MuGM
Collector 3
Control
Center
Group Manager
• Conditions for Group of MNs
• One group has one and only one group id: Each MN in a group has the
group id for the group
• One MN may belong to multiple groups
• Only a GM can create a new group. Only a GM can break up a group
• When a new group is created, the GM distributes the group id to the
members of the group
• When a group is to be broken up, the GM issues the command to the
members of the group to delete the group id
• Only a GM has capability to separate one group into multiple groups
• Especially, a GM may exclude one MN out of a group
• The GM distributes (new) group ids
• Only a GM has capability to unite multiple groups into one group
• Especially, a GM may make one MN join a group
• The GM distributes a (new) group id
• The commands issued by a GM and the relevant events should be secured
• One multicast address may accommodate MNs which belong multiple
groups. MNs in a group may listen to multiple multicast channels
21-12-0058- MuGM
Control Center
• The Control Center issues the commands to the MIHFs so that
it controls the sequences of load balancing, f/w update,
failover/restoration, etc.
21-12-0058- MuGM
Model for Load Balancing
MIH
MIH
MIH
MN
MN
MIH
MN
21-12-0058- MuGM
MIH
PoS
Control Center
Candidate PoA
MIH
Serving PoA
MIH
PoS
Group Manager
Example Scenario for Load Balancing
Groups:
•
Let group G1 and group G1’ be groups the member MNs of which
currently communicate the Serving PoA
• The union of G1 and G1’ is the set of all the MNs which currently
communicate the Serving PoA
• The intersection of G1 and G1’ is empty
• G1’ is the group to handover
•
Let group G2 be the set of all the MNs which currently communicate the
Candidate PoA
Actions:
1. The Control Center makes the GM pass the group id of G1’ to the
Candidate PoA
2. The Control Center obtains the group id of G1’ from the GM
3. The Control Center issues (via multicast channels through the Serving
PoA) to the member MNs of G1’, i.e. designating them by the group id, a
command for handover to the Candidate PoA
4. The handover is completed
5. The Control Center may make the GM unite G1’ and G2
21-12-0058- MuGM
Example Scenario for Load Balancing
* Authentication between an MN in G1’ and the Candidate PoA
will be performed later if necessary
21-12-0058- MuGM
Model for F/W, configuration update
MIH
MIH
MN
MN
MIH
MN
21-12-0058- MuGM
MIH
PoS
Update Srv
MIH
PoS
Group Manager
MIH
PoS
Control Center
Example Scenario for F/W Update
Groups:
• Let group G1 be the set of all the MNs which are the targets of
the f/w update
Actions:
• The Control Center makes the GM pass the group id of G1 to
the Update Server
• The Update Server issues a command for f/w update and
distributes (via all the available multicast channels) the
command with the new f/w to the members of G1
• The f/w update is completed
• The Control Center may make the GM unite G1 with a group of
MNs that have the updated version of f/w
21-12-0058- MuGM
Model for Failover
MIH
MN
MIH
MN
21-12-0058- MuGM
MIH
MN
MIH
MN
MIHs
Candidate PoAs
MIH
Serving PoA
MIH
PoS
Control Center
MIH
PoS
Group Manager
Example Scenario for Failover
Groups:
• Let groups G1, G2, …, Gn be groups the member MNs of which
currently communicate the Serving PoA
• The union of G1, G2, …, Gn is the set of all the MNs which
currently communicate the Serving PoA
• The intersection of any two groups is empty
• G1, G2, …, Gn are to failover to PoAs: A1, A2, …, An
respectively. A1, A2, …, An are preliminarily chosen by the
Control Center
• Each group potentially has a communication channel to the
corresponding PoA, in addition to the one to the currently
Serving PoA
21-12-0058- MuGM
Example Scenario for Failover
Actions:
1. The Control Center obtains from the GM the group ids of G1, G2,
…, Gn
2. The Control Center issues (via the multicast channels through the
Serving PoA) to the member MNs of G1, G2, …, Gn commands for
handover to A1, A2, …, An respectively. These are maintenance
steps that are done before a failover scenario happens
3. The Serving PoA drops. The MNs of G1, G2, …, Gn see the failed
PoA, and move to their candidate PoA groups
4. The failover is completed
5. The Control Center may make the GM unite the groups which
communicate A1, A2, …, An respectively
21-12-0058- MuGM
Example Scenario for Restoration
Groups:
• Let groups G1, G2, …, Gn be groups of MNs which currently
communicate PoAs: A1, A2, …, An
• G1, G2, …, Gn are the groups to be restored
Actions:
1. The Control Center chooses a Candidate PoA
2. The Control Center makes the GM pass the group ids of G1, G2, …,
Gn to the Candidate PoA
3. The Control Center obtains from the GM the group ids of G1, G2,
…, Gn
4. The Control Center distributes (via multicast channels through the
Candidate PoA) to the member MNs of G1, G2, …, Gn commands
for restoration to the Candidate PoA
5. The restoration is completed
21-12-0058- MuGM
Model for Restoration (for Failover)
MIH
MN
MIH
MN
21-12-0058- MuGM
MIH
MN
MIH
MN
MIHs
Serving PoAs
MIH
Candidate PoA
MIH
PoS
Control Center
MIH
PoS
Group Manager
Some Further Considerations
• What is the authority to issue commands to a GM? How should
we define it?
• For generation, break-up, unification or separation of groups
• What should be contents of attributes/IEs? To whom should the
information be provided?
• What should be secured?
• May an MN outside of a group know who is the members of
a group?
• May an MN in a group know who is the members of a
group?
• May an MN outside of a group know that a group-related
command targeted the group is issued? etc.
• These points should be considered and clarified for each of
the use cases
21-12-0058- MuGM