60 likes | 150 Views
ES/CS Work Status. Agreement on the transport requirements Ongoing email discussion on some aspects MIH discovery MIH Capability discovery MIH Registration Split requirements at MIH protocol level and transport level. ES/CS Message Reliability. Objective
E N D
ES/CS Work Status • Agreement on the transport requirements • Ongoing email discussion on some aspects • MIH discovery • MIH Capability discovery • MIH Registration • Split requirements at MIH protocol level and transport level 21-05-0XX-00-0000
ES/CS Message Reliability • Objective • ES/CS messages must have reliability • Approaches • MIH protocol level reliability • Efficient and optimized communication => no transport reliability • Reliability at transport level • May have to use a session based transport e.g. TCP • May add transport message exchanges => latency • MIH Protocol level reliability requires • NAT-PT tranversal (already agreed) • Firewall traversal (new one) 21-05-0XX-00-0000
MIH State Diagram MIH Idle MIH Discovery MIH ES/CS Registration MIH Capability Discovery MIH Active 21-05-0XX-00-0000
MIH Discovery & Capability Discovery • MIH Discovery • to discover the address of MIH nodes in the network • Not defined in IEEE 802.21 • Transport specific approach e.g. 802.11, IETF • MIH Capability discovery • To exchange MIH service capabilities between peers • Part of MIH protocol • Within the scope of IEEE 802.21 21-05-0XX-00-0000
MIH ES/CS Registration • What is ES/CS Registration? • MIH protocol level message exchange to create MIH pairing • MIH peer registers with remote MIH peer to create a session for MIH message exchanges • MIH peers may not provide or accept MIH messages without an active registration session => alleviates security problem • Can remain active even after handovers • Why ES/CS Registration? • Peer node to request for specific event indications • Peer node to send specific commands • Establishes a session setup and assigns an id • When to do ES/CS Registration? • Follows MIH discovery procedure • Before sending any ES/CS MIH messages • Deregistration to remove the MIH pairing 21-05-0XX-00-0000
ES/CS Work Next Steps • Create a doc format for ES/CS requirements for next meeting • Finalize MIH level protocol functionality related to capability discovery and registration 21-05-0XX-00-0000