1 / 25

IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0816-01-0000

IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0816-01-0000 Title: 802.21 – TGu Joint Discussions Date Submitted: November, 2006 Presented at IEEE 802.21 session #17 in Dallas, Texas. Authors or Source(s): Vivek Gupta, Michael G. Williams

tomas
Download Presentation

IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0816-01-0000

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0816-01-0000 Title: 802.21 – TGu Joint Discussions Date Submitted: November, 2006 Presented at IEEE 802.21 session #17 in Dallas, Texas. Authors or Source(s): Vivek Gupta, Michael G. Williams Abstract: Inputs from 802.21 to questions from TGu

  2. TGu Inputs • 11-06-1492-00-000u tgu-802-21-joint-session-update-tgu-network-selection-mih-support • 11-06-1543-00-000u-planning-november-2006-joint-session-between-802-21-and-802-11u

  3. Discussion Items • Information Service • List of IEs • Query Language • Static/Dynamic IEs • State 1 vs State 3 query • Maximum message length in State 1 Issues • MIH Events • MLME implications • Security Implications • Next Steps

  4. Network Discovery & Selection for 802.11 • Applicable in two cases: • When MN is ALREADY connected to some other network and needs to Handover an existing connection to 802.11 • The 802.11 radio may be in OFF state in this case • When evaluating 802.11 networks the Network Selection entity (in MN or Network) may need to know more about 802.11 network properties even before deciding to Power On the 802.11 radio • 802.21 IS can provide these properties • When MN is NOT connected to any network and needs to select an appropriate 802.11 network to connect to • 802.11 may be the DEFAULT radio to connect to on Power up or 802.11 may be the only network coverage available in that area

  5. 802.11 based Reference Network NAP NOC SSPN #1 NOC 802.21 IS AAA 802.21 IS AAA SSPN #1Core Network MIH MIH SSPN #2 NOC Tunnel NAPCore Network Internet 802.21 IS AAA Tunnel SSPN #2Core Network Hot Spot #1 Hot Spot #N Use 802.21 as Protocol for Network Selection

  6. 802.21 Information Service • Multiple Networks of different Network_Type may be available in a particular geographical area: • 802.11, 802.16, Cellular • For each Network_Type (such as 802.11) there may be several operators, providing several instances of a particular Network_Type • Operator_A, Operator_B, etc. may all have 802.11 network • The properties of these network instances may be different • 802.11 Network Standards they support (.11a/b/e/g/i/n/p/r/s/u/v…) • Cost, Security, Roaming Agreements etc. for these networks may be different • For each of the above Network Instance, there are different PoAs (APs for 802.11) • The properties of these APs may differ • Location, Subnet Information, Capabilities, etc.

  7. 802.21 Information Service List of Access Network Types (802.11, 802.16, Cellular) Access Network Properties 802.11 Network from Operator_A 802.11 Network from Operator_B 802.16 Network from Operator_A 802.16 Network from operator_C PoA Specific Properties Properties of each AP/BS

  8. Information Elements-1

  9. Information Elements-2

  10. Information Elements-3

  11. What 802.11 Information should be stored in 802.21 Information Server? • Guiding principles • Put the minimum information needed by STA for network selection and network identification—minimizes synchronization problems between configuration of 802.11 AN and 802.21-IS database • Include support for two types of queries: • Remote query (state 3 query): I’m in San Francisco and want to find out what hotspots are in Melbourne • Local query (state 1 query): I can see 3 hotspots now, which one is the best to associate with? • 802.21 IS does NOT distinguish between Access Network States • Do not include 802.11 AN dynamic information; examples include: • Channel number, • Transmit power • Traffic Load • None of the above are included in IS

  12. What 802.11 Information should be stored in 802.21 Information Server (cont.)? • Fundamental binding provided by 802.21-IS • SSPN to WLAN • WLAN identified by {SSID, ESSID} (Supported) • Recommended information to store in 802.21 database: • SSPN name/realm (Is this same as Operator Identifier?) • SSPN roaming partners (Supported) • Interworking services by SSPN (including emergency services) (Supported) • 802.11 AN parameters: • Location • Country/regulatory domain • {SSID, ESSID} • PHY types supported • 802.11e QoS support (Supported Phy types can be obtained from Network_Standards)

  13. Opcode Action ID SID (4) (10) (2) Octet 4 Octet 1 Octet 2 Octet 3 Ack Ack VER Reserved MIH Message ID (4) Req (1) Rsp (10) (16) (1) MIHF Fixed T r ansaction ID V a riable Load Length Header (16) (16) MIHF V a Variable Header (contains Header Identifiers in TL V format) MIHF V a riable Load MIHF Payload (contains other service specific TL V s) MIHF Protocol MIHF Payload MIHF Fixed Header MIHF Variable Header MIH FunctionFrame F

  14. MIHF Protocol – Fixed Header

  15. MIHF Protocol – Variable Header • Variable Header fields (Optional) • Session Identifier • MIHF Identifier

  16. MIHF IS Query Request MIH_Get_Information.Request -- IS Info Query Type -- IS Query Parameters Information Service MIH_Get_Information Request Fixed Header Ver (0) Ack (0) Rsp (0) Reserved (0) SID (4) OpCode (1) AID (21) Transaction Identifier Payload Length Payload IS Info Query Type Type = 4 Length = 1 Value = 1 (TLV) Type= 36 Length = ? Value = 1 (TLV Parameters) IS Query Parameters: Location, Span/Radius, etc.

  17. MIHF IS Query Response MIH_Get_Information.Response -- IS Info Query Type -- IS Response Parameters Information Service MIH_Get_Information Response Fixed Header Ver (0) Ack (0) Rsp (0) Reserved (0) SID (4) OpCode (2) AID (21) Transaction Identifier Payload Length Payload IS Info Query Type Type = 4 Length = 1 Value = 1 (TLV) Type= 37 Length = ? Value = 1 (TLV Parameters) IS Response Parameters…..

  18. MIHF Supported TLV Query Types • TLV Containers • List of Access Networks Container • TYPE_CONTAINER_LIST_OF_NETWORKS • Access Network Container • TYPE_CONTAINER_NETWORK • PoA Container • TYPE_CONTAINER_POA • Other Query parameters • Client Location • Radius of interest for networks • Queries • Any IE can be queried. • Any number of IEs can be queried in same request

  19. TGu- Query Examples • What WLANs support my subscriptions? • STA: provides list of subscriptions • 802.21-IS: provides list of {SSPN, SSID, ESSID} where SSPN’s includes roaming partners • Need to add • Is emergency service supported on this WLAN? • STA: provides ESSID(s) • 802.21-IS: provides list of {SSPN, SSID, ESSID} • Need to add • What interworking services are supported on this WLAN? • STA: provides ESSID(s) • 802.21-IS: provides list of {SSPN, SSID, ESSID, interworking services} • Supported (PoA capabilities IE)

  20. TGu - Query Examples (cont.) • Is VoIP services provided on this WLAN? • STA: provides ESSID(s) • 802.21-IS: provides list of {SSPN, SSID, ESSID} which support VoIP • Note that VoIP is just an example; query could be for any interworking service • Need to add • I’m traveling to Melbourne, what hotspots are located there? • STA: provides location (latitude, longitude), search radius • 802.21-IS: provides list of {SSPN, SSID, ESSID} • This could potentially generate a lengthy query response • Supported

  21. AP to 802.21-IS Protocol Issues • Mechanism to limit size of Query Response • Important only when client is in state 1 • When client is in state 3, any query response length is acceptable • Mechanism to identify final fragment of a multi-fragment Query Response

  22. Event Service • Link Layer Events • MIH Events • Can be local or remote • Remote MIHF entity has to subscribe for events it is interested in • Delivery through MIHF protocol

  23. Link Layer Events

  24. Next Steps

  25. Backup

More Related