1 / 11

Considerations about Network Selection

This article discusses the considerations and information that should be provided to a terminal for network selection, including network identification, roaming agreements, costs, authentication mechanisms, and end-to-end QoS. It also proposes using this information to establish formal requirements for network selection.

pricet
Download Presentation

Considerations about Network Selection

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. Considerations aboutNetwork Selection Eleanor Hepworth, Siemens Roke Manor Stefan Berg, Siemens Wolfgang Gröting, Siemens Eleanor Hepworth, Siemens Roke Manor

  2. What’s the Problem? • Need to provide the terminal with information to choose the appropriate network • In general, at different times (while attaching to a network) the information can be provided • Pre-association • Post-association/pre-authentication • Post-authentication NOW • Let‘s focus on ‚pre-association’ and… • …have a closer look on the information itself Eleanor Hepworth, Siemens Roke Manor

  3. A user scenario – without network advertisements Hotspot #1 Internet No Real time support 4. Start VoIP session 2. Start VoIP Application AP 1. Advertise Network identifier User 6.Stop VoIP session Hotspot #2 Real Time support 2. Advertise Network identifier 7. Re-Start VoIP session 3. Connect to Hotspot #1 (wild guess) 5. User unsatisfied with Quality AP Eleanor Hepworth, Siemens Roke Manor

  4. A user scenario – with network advertisements (e.g. QoS) Hotspot #1 Internet No Real time support 2. Start VoIP Application AP 1. Advertise Network identifier, no real time support User Hotspot #2 Real Time support 1. Advertise Network identifier with real time support 5.Start VoIP session 3. Evaluate application requirements & user preferences 4. Chose Hotspot #2, since its support real time services 6.  User … AP  Better user experience, reduced application delay, reduced signalling over the air Eleanor Hepworth, Siemens Roke Manor

  5. What Information would be useful? • Network Identification • Roaming Agreements • Costs for Network Usage • Authentication Mechanisms • E2E QoS / Bearer Service Eleanor Hepworth, Siemens Roke Manor

  6. Only Network Identification or even more? • Mandatory for network identification purpose • Pre-association; beacon and/or probe • Current Practice: • The SSID is used to advertise the network identity • Data-Format SSID: 32byte • But: • Which identity needs to be advertised? • Can other network characteristics be derived from the identifier? • A structured SSID namespace could provide additional information and support network selection e.g. this is a public or private hotspot, 3GPP interworking/roaming capabilities, etc Eleanor Hepworth, Siemens Roke Manor

  7. What about Roaming Agreements? • Mandatory for authentication purpose • Reasonably pre-association; beacon and/or probe • Motivation: Indicate all supported roaming partners • STA impact: new mechanism to transfer and evaluate the information • Amount of data: 10s or 100s of bytes • Assuming 10 roaming partners example data formats could be: Eleanor Hepworth, Siemens Roke Manor

  8. Do we need Charging Information? • Optional, it’s nice to know about the cost of using the network • Preferably pre-association; beacon and/or probe • STA impact: new mechanism to transfer and evaluate the information • Many, many options; could be a large list with quite an amount of data • Amount of data: 10s or 100s of bytes • Example data formats for AP and 10 roaming partners: Eleanor Hepworth, Siemens Roke Manor

  9. What about Authentication Mechanisms and new user signup services? • Mandatory for authentication purposes and helpful for new user signup support • Preferably pre-association; beacon and/or probe • WPA/802.1X is already advertised: privacy bit is set or not • In case of UAM: indication needed on subscriber selection support • STA impact: new mechanism to transfer and evaluate the information • Amount of data: 10s of bytes • Example data formats for AP and 10 roaming partners: Eleanor Hepworth, Siemens Roke Manor

  10. What about end-2-end QoS? • Optional for bearer service selection • Pre-association; beacon and/or probe • Motivation: • 802.11e realizes only over the air QoS • Provide a hint on network capabilities (QoS classes) • Provide information on supported QoS mechanisms • STA impact: new mechanism to transfer and evaluate the information • Amount of data: 10s of bytes • Example data formats for AP and 10 roaming partners: Eleanor Hepworth, Siemens Roke Manor

  11. Conclusionsand Proposal • Mandatory information and its characteristics have been identified Proposal: • Use the information outline here in establishing formal requirements for network selection and … • … identify, what is feasible to advertise pre-association Questions: • Are there any other things that people feel should be included? Eleanor Hepworth, Siemens Roke Manor

More Related