1. 1 WP2.5: Kick-off the work

2. 2 Outline Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Business model Requirements for network architecture Operating scenarios and technical solutions Specification of the network architecture Conclusion

3. 3 Revisit objectives of WP2.5 To define a scalable and manageable network architecture for the provision of selected broadband services. To determine appropriate network and application layer protocols for QoS and service provisioning. To determine and solve interoperability issues and to define mapping of QoS parameters between different layers. To investigate routing issues related to the mobile environment involving high speed moving vehicles and aerial platforms. To define an applicable network management architecture based on existing standards. To evaluate the implications of all-optical backhaul network

4. 4 Output of WP2.5 Deliverable: D27, Report defining network architecture and protocols (including interoperability issues and routing) (M36). Milestones and expected result M20: Definition of network architecture including management facilities M23: Evaluation of network and higher layer protocols for QoS and service provisioning in selected operating scenarios M26: Routing protocol implementation issues in specific operating environment involving high speed moving vehicles and aerial platforms M26: Specification of network management solutions M29: Definition of mapping of QoS parameters between different layers M30: Development of simulation model

5. 5 Outline Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Business model Requirements for network architecture Operating scenarios and technical solutions Specification of the network architecture Conclusion

6. 6 Operating Scenarios in Aspect of Network Architecture (from WP 1.1) Broadband Internet and Intranet for SOHO, SME with QoS support 1.Point-to-point 2.Multicast 3.Broadcast Private circuit: 1.Interconnection of different networks, ISPs 2.Backhaul link between a 3G base station and the core network 3.Bearer link inside a core network Mobility: backhaul link for WLAN hotspots on trains and coaches

7. 7 Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Business model Requirements for network architecture Operating scenarios and technical solutions Specification of the network architecture Conclusion Outline

8. 8 Selected Communication Standards (from WP 2.1) No perfect standard exists for HAP applications IEEE 802.11 with extended range Too limited for HAP IEEE 802.16 The selected standard for Helinet 802.16e supporting mobility (up to 100 km/h) is under standardization IEEE 802.20 Can be a good choice with mobility support (up to 250 km/h) Low data rate At the first stage of development DVB standards (S, S2, RTS, C, RTC) and others (HIPERACCESS, HIPERMAN)

9. 9 HAP Implementations No processing on board Subscriber station Gateway HAP HAP1 HAP4 HAP2 HAP3 Processing on board Optical link Implementation of network layer mechanisms

10. 10 Outline Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Business model Requirements for network architecture Operating scenarios and technical solutions Specification of the network architecture Conclusion

11. 11 Business models (from WP 1.1) Roles and players: Network operators (HAP operator, HAP network operator, terrestrial network operator) Service Provider (primary and 3 rd party) Subscribers and users Payment aspect: Provision aspect: SubscriberS. Provider HAP NO HAP Operator SubscriberS. Provider HAP NO HAP Operator Terrestrial NO NetworkService Infrastructure Terrestrial NO

12. 12 Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Business model Requirements for network architecture Operating scenarios and technical solutions Specification of the network architecture Conclusion Outline

13. 13 General requirements for network architecture Reduce payload onboard Provision of connectivity Layer 3: IPv4 and IPv6 Layer 2.5: optional MPLS Layer 2: Ethernet, ATM Routing: inter and intra AS unicast and multicast routing, high-speed mobitity and all- optical backhaul network. Facilitation of the interworking between operators Interface (protocol) AAA interworking problems Flexibility Service development, deployment and provisions Control and management AAA Resource management QoS Mobility and roaming

14. 14 Alternatives and Decisions Possible solutions for connectivity IP and MPLS functionalities (e.g.: routing) on board Ethernet switching functionality on board Why Ethernet switching? Cheap Plug-and-play (less configuration on board) Disadvantage: limited number of users, broadcast storm not easy to provide QoS Not easy to provide multicast services Why IP and MPLS on board? Rich of capabilities More powerful and easier to provide services Complex to manage Any over MPLS tunneling (transport, VPN)

15. 15 Outline Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Business model Requirements for network architecture Operating scenarios and technical solutions Specification of the network architecture Conclusion

16. 16 Internet access Scenario 1: HAP is a NAS DHCP and DNS by ISP user data is transferred to ISP first and then routed to the receiver. Subscriber station HAP Terrestrial core network Backhaul ISP PHY LL PPP IP/others PHY LL PHY LL IP PHY LL IP PPP IP (or MPLS) tunneling AAA server

17. 17 Internet access Scenario 2: HAP is an AAA client, AAA server can be RADIUS, TACACS, but should be Diameter because it support Mobile IP HAP gives IP address to subscribers user data are not necessarily transferred via ISP. Subscriber station HAP Terrestrial core network Backhaul 3 rd party ISP SS sends login information to HAP HAP, as AAA client, sends request to AAA server located at ISP If okay, gives IP address to the subscriber AAA server

18. 18 Intranet access Scenario 1 based on secured VPN: User has already IP connectivity User uses secured VPN to access its Intranet Simple, does not require any implementation in HAP Scenario 2 based on trusted VPN or hybrid VPN: User provides authentication information to HAP HAP identifies the user by request user information from the AAA server. HAP initiates a L2TP tunnel if it does not exist. Implementation overhead

19. 19 Bearer services L2TP HAP Network 1 Network 2 IP Sec LL tunnel HAP Network 1 Network 2 IP tunnel

20. 20 Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Requirements for network architecture Business model Operating scenarios and technical solutions Specification of the network architecture Conclusion Outline

21. 21 Helinet’s Results Related to Network Architecture Convergence sublayer above MAC and under IP QoS architectures and QoS mapping between L2 and L3 Simulation model Scheduling: RR and WRR Applications: Interactive voice, streaming multimedia and best-effort

22. 22 Interoperability with MAC Layer Further development of the convergence layer from Helinet: Not only for IP traffic but also for MPLS. QoS architectures: Intserv and Diffserv Helinet: Intserv for user links and Diffserv for backhaul links Mapping between IP QoS parameters and 802.16, 802.20 QoS parameters.

23. 23 Interfaces Customer Premise Equipment (CPE) LL2 on optical cross links Ethernet Simple Cheap Easy to maintain ATM Complicated Expensive Antenna Interface box

24. 24 Routing Requirements: Fast route change due to link failures All-optical backhaul network support Multicast support Mobility support Open question: Routing performance improvement techniques (caching)

25. 25 Unicast Routing HAPs and terrestrial gateway could form an AS (Autonomous System) Candidate Intra AS routing protocols: RIP: Routing Information Protocol (DV, hop count) OSPF: Open Shortest Path First (LS, more complex and advanced, multicast version) IGRP: Internal Gateway Routing Protocol (DV, any type of link cost) Inter AS routing protocols: BGP: Border Gateway Protocol AS

26. 26 Multicast Routing Between HAP and SS IGMP: Internet Group Management Protocol Candidate protocols for intra AS routing: DVMRP: Distance Vector Multicast Routing Protocol (source- based tree) MOSPF: Multicast Open Shortest Path First Protocol (extends OSPF) CBT: Core-Based Trees PIM: Protocol Independent Multicast Inter AS routing: BGMP: Border Gateway Multicast Protocol

27. 27 Mobility Support Mobile IP should be implemented Location management for mobile SS (updating and paging) Fast processing due to high-speed movements Diameter, the only AAA protocol supporting Mobil IP

28. 28 Simulation model Reuse the Helinet model with mobility extension and various traffic models from WP2.4 End-to-end performance Impact of rain attenuation on TCP performance Impact of optical link failures on routing performance Impact of hand-off due to SS mobility

29. 29 Suggestion of MAC Adaptive Mechanisms Adaptive mechanisms can be applied to achieve the best performance. Adaptive power control Adaptive FEC (Forward Error Correction) Adaptive modulation Adaptive rate For TCP traffic, we will suggest particular approach based on the nature of TCP. Start with TCP throughput formula Find suitable objective function Optimize objective function The work can be extended to QoS classes with different QoS parameters.

30. 30 Network management Network management protocols: SNMPv1, v2, v3 CMIP (Common Management Information Protocol) SNMP is recommended because of its simplicity and security 802.16 (802.20) MIB Define MIB for PHY and MAC layers Base Station and Subscriber Station. Other Interface MIB required at the BS, e.g. Ethernet MIB. Mobile IP MIB Integrate MIBs into a common tree

31. 31 Revisit the objectives of WP2.5 Potential services and applications Potential standards for PHY and LL Requirements for network architecture Business model Operating scenarios and technical solutions Specification of the network architecture Conclusion Outline

32. 32 Conclusion Protocol stack: 802.xx,DVB or others Convergence sublayer MPLS* IP *optional An intra AS unicast routing Inter AS unicast routing: BGP IGMP An intra AS multicast routing Inter AS multicast routing: Mobil IP Diameter client SNMP MIB and agent L2TP* IPSec* Mechanisms:

33. 33 Document Properties