130 likes | 243 Views
Use cases for implementation of the NSI interface. Takahiro Miyamoto , Nobutaka Matsumoto KDDI R&D Laboratories Inc. This work is partially supported by NICT (National Institute of Information and Communications Technology), Japan. Abstract.
E N D
Use casesfor implementationof the NSI interface Takahiro Miyamoto, Nobutaka Matsumoto KDDI R&D Laboratories Inc. This work is partially supported by NICT (National Institute of Information and Communications Technology), Japan.
Abstract • The goal of this presentation is to contribute contents of section 12 in the architecture recommendation document. • Agenda • Single layer networks • Multi-layer technology with multiplexing • Recursive NS agents
Section 12 in recommendation document • Sections • 12 Examples and use cases • 12.1 GMPLS intradomain with NS agents • 12.2 Single layer networks • 12.3 Multi-layer technology networks • 12.4 Multi-layer technology with multiplexing • 12.5 Recursive NS agents • Contents • Overview of a use case application • Target network layer • Sequence to use NSI by the application • Functional / Non-functional requirements of the application
Requirements • Functional Requirements • Provisioning • Layer: L1 (lambda) / L2 (Ethernet) / L3 (IP) • Topology: P2P / P2MP / MP2MP • Scheduling: on demand / advanced reservation • Messaging: 1 phase commit / 2 phase commit • Monitoring: mandatory / optional • Non-functional Requirements • Spec • Bandwidth • Latency • Jitter • Fault handling: none / N+1 redundancy / … • Security
e.g. Visualization e.g. eVLBI Dynamically provisioning Statically provisioning Single layer networks • Application: Data transfer • Overview: To transfer data under stable network, a network path between a client and server is provisioned. The network path may be coallocated with computing resources. • Layer: L1 or L2
App UA#1 NSA#1 Find a data server where required data is stored Call NSI Request data request data download Call NSI Release Single layer networks Established
Single layer networks • Functional Requirements • Provisioning • Layer: L1, L2 • Topology: P2P • Scheduling: on demand, advanced reservation • Messaging: 1 phase commit, 2 phase commit • Monitoring: mandatory • Non-functional Requirements • Spec • Bandwidth: wide • Latency: low ~ • Jitter: low ~ • Fault handling: N+1 redundancy • Security:
L2 L2 (multiplexed) L2 L3 (multiplexed) L2 (multiplexed) Access Access OLT VoIP OLT CPE CPE VoIP Core (Mesh) Metro (Ring) Metro (Ring) VoIP VoIP Router VoIP VoIP Packet ADM Packet ADM Multi-layer technology with multiplexing This use case was presented at NSI-WG in OGF24. • Application: VoIP • Overview: To ensure end-to-end bandwidth and jitter, a telecom carrier will provide a guaranteed network path. In general, a telecom carrier’s network consists of access / metro network (layer 2 network) and core network (layer 3 network). Moreover, in the metro / core network, traffic of users will be aggregated into a network path. • Layer: L2 & L3 (multiplexed)
NSA#1 NSA#2 NSA#3 SIP server UA#1 Multi-layer technology with multiplexing VoIP client SIP signaling Find the destination client Calling Call NSI Request Established SIP session SIP signaling Call NSI Release
Multi-layer technology with multiplexing • Functional Requirements • Provisioning • Layer: L2, L3 • Topology: P2P • Scheduling: on demand • Messaging: 2 phase commit • Monitoring: mandatory • Non-functional Requirements • Spec • Bandwidth: narrow • Latency: low • Jitter: low • Fault handling: N+1 redundancy • Security:
NS#2 provides L2-NW over NS#1’s network. NS#1 provides L1-NW. Recursive NS agents • Application: Overlay network, Cloud networking • Overview: A network service agent provides underlay network connectivity. Another network service agent provides overlay network connectivity. • Layer: L1, L2 & L3
App UA#1 NSA#1 UA#2 Recursive NS agents NSA#2 Call NSI Request Call NSI Request Overlay network is established. Call NSI Release Call NSI Release
Recursive NS agents • Functional Requirements • Provisioning • Layer: L1, L2, L3 • Topology: P2P, P2MP, MP2MP • Scheduling: on demand, advanced reservation • Messaging: 1 phase commit, 2 phase commit • Monitoring: optional • Non-functional Requirements • Spec • Bandwidth: narrow ~ wide • Latency: low ~ • Jitter: low ~ • Fault handling: N+1 Redundancy (NS#1) • Security: