1 / 6

Motivation

Motivation. ES/CS @ L3 enable both scenarios under 802.21 Terminal centric Allows terminals to send CS to network to trigger MIHO procedure to a L3 attachment point Network centric Allows any network node to send CS to terminals to initiate MIHO procedure

brendy
Download Presentation

Motivation

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. Motivation • ES/CS @ L3 enable both scenarios under 802.21 • Terminal centric • Allows terminals to send CS to network to trigger MIHO procedure to a L3 attachment point • Network centric • Allows any network node to send CS to terminals to initiate MIHO procedure • Allows terminals to report ES to network that aid in network centric MIHO management • Why L3? • L2 or MAC improvements terminate at AP/BS • MME using MIHO are generally deeper in the network • Works with no specific L2 improvements e.g. cellular • Backward compatible with older network equipment 21-05-0XX-00-0000

  2. ES/CS Higher Layer Requirements • Work is similar to IS higher layer MIIS for • Identifying usage scenarios • Provisioning models e.g. proxy and direct • Finalizing ES/CS MIH functionality • Message sequences, message types, data elements associated with each message • Other higher layer requirement categories • Transport Layer • Discovery • Registration and Deregistration • Capability negotiation • Security • Reliability and failure recovery 21-05-0XX-00-0000

  3. Usage Scenarios • 3 usage scenarios are envisioned • Terminal to Network • Network to Terminal • Network to Network • Can be realized with same direct & proxy models (as for IS) • Direct Model • Proxy Model Terminal MIH Service Node MIH Service Node MIH Service Node Terminal Proxy Node MIH Service Node MIH Service Node Proxy Node MIH Service Node 21-05-0XX-00-0000

  4. ES/CS Higher Layer RequirementsTransport • Should work with IPv4 and IPv6 • Preserve message boundaries • Provide NAT traversal • ?? • Notes: • No reliability expected from transport? • What about ES? Can we have an MIH level ACK? 21-05-0XX-00-0000

  5. ES/CS Higher Layer RequirementsDiscovery, Registration & Capability Negotiation • Discovery of MIH network nodes is a common problem (with IS) • Another approach is to integrate as info in the IS services • Need an “attachment” procedure to notify network of the availability of the terminal • Different from ES registrations • The mechanism can be used to do capability negotiation of what is supported at either ends 21-05-0XX-00-0000

  6. ES/CS Higher Layer RequirementsSecurity • To be added 21-05-0XX-00-0000

More Related