Cover Image
市場調查報告書

軟體中心型通訊網路的服務鏈

Service Chaining in Software-Centric Telecom Networks

出版商 Heavy Reading 商品編碼 317878
出版日期 內容資訊 英文 46 Pages
商品交期: 最快1-2個工作天內
價格
Back to Top
軟體中心型通訊網路的服務鏈 Service Chaining in Software-Centric Telecom Networks
出版日期: 2014年11月03日 內容資訊: 英文 46 Pages
簡介

網路服務鏈,指的是具有可大大改變服務供應商的網路設計、運用方法之潛力的技術.過程之新組合。這個概念和電信業者網路上的軟體中心型技術(網路功能虛擬化(NFV)和軟體定義型網路(SDF))等的關聯性很深,具有比傳統更容易發展動態程式網路服務這樣的特徵。利用服務鏈,供應商不用在硬體水準改變網路,便可定義.發展軟體的「服務鏈」。服務鏈的概念本身從以前就存在,但由於其設計複雜,而無法完全實現。即使如此,各家供應商還是以迅速轉換到SDF為目標,致力於各種開發及普及的活動。已有許多先行導入案例,同時也產生應在公式標準化、規格決定前就發展並普及技術等見解。

本報告提供通訊業者的網路上推動服務鏈相關分析,概念上定義及其重要性,為提升商業方面吸引力的要件、近年的主要利用案例、從中得到的概念上的教訓、提供您實現服務鏈所需的技術子系統、各企業應該採取的引進策略,主要企業(全9公司)的解決方案概要,相關企業·產業的影響度等調查評估。

第1章 簡介及主要結論

  • 主要的分析結果
  • 分析範圍·結構

第2章 網路服務鏈:到底是什麼

  • 業務定義
  • 概念上的案例
  • 業務的案例:企業用服務
  • 業務的案例:行動服務
  • 概念的演進

第3章 主要配合措施與相關組織

  • ETSI的NFV(網路功能虛擬化)的發展情形圖
  • IETF的服務功能鏈
    • SFC架構
    • SFC的封裝(header)格式
    • 控制平面的機制
  • Open Networking Foundation (ONF)

第4章 利用案例:服務鏈使用的地方

  • 哪個服務功能使用
  • 實現用戶程序的網路服務
  • 企業用服務鏈
  • SGi-LAN
  • 層級3服務的PoP
  • 資料中心的網路

第5章 主要技術

  • 服務鏈的系統
  • 服務功能(VNF:網路功能虛擬化)
  • 流通量的特定與分類
  • 服務鏈的控制功能
  • 雲端管理平台和業務流程
  • 網路:軟體定義網路(SDN)及Virtual Overlays

第6章 供應商方面的方法

  • Alcatel-Lucent
  • Cisco Systems Inc.
  • ConteXtream Inc.
  • Ericsson AB
  • F5 Networks Inc.
  • Huawei Technologies Co. Ltd
  • Juniper Networks Inc.
  • Sandvine Inc.

附錄A:關於作者

附錄B:法律上的免責聲明

圖表一覽

目錄

Network service chaining is an emerging set of technologies and processes that have the potential to radically change how service provider networks are designed and operated. The concept is inherent to the use of software-centric technologies, such as network virtualization, network functions virtualization (NFV) and software-defined networking (SDN) in carrier networks. In essence, it enables operators to create more dynamic, programmable network services. It could even be considered the apogee of a software-centric network.

Using service chaining, operators will be able to define and configure customized "service chains" in software without having to make changes to the network at the hardware level. In principle, service chains can be coarse-grained (e.g., all consumer smartphone users) or highly granular (e.g., a particular set of smartphone users), depending on the service the operator wishes to provide. The service chaining concept, and its implementation, addresses the requirement for both optimization of the network, through better utilization of resources; and monetization, through the provision of services that are tailored to the customer context.

Service chaining is not a new idea. Insofar as network equipment is hardwired back-to-back to create a processing path, it has always existed. In fact, chaining of network functions in hardware is the de facto operating model. The challenge is that service functions are embedded in discrete and specialized appliances and, as a result, an end-to-end service can be complicated to design, deploy, configure, modify and support. Hardwired service chains are characterized by hand-crafted complexity, with lifecycles that are long and static. This makes changes complex and costly and in turn leads to "network ossification."

In competitive markets, with rapid innovation at the application layer, network ossification prevents operators from being able to efficiently support growing traffic load and limits their ability to address emerging use cases and business models. Ossification, in effect, limits the addressable market for telecom services. For a sector with modest top-line revenue growth (at best), this is obviously a problem that needs to be addressed urgently.

In response, network operators want to accelerate the transition to software-centric, programmable networks. Web-scale service providers have shown some of what can be achieved through the use of SDN and virtualization to offer cloud services, and now operators want to adopt and extend these ideas for the wide-area telecom network. Dynamic network service chaining is a consequence - and in many ways a culmination - of the transition to software-configurable networks in telecom and data center networks.

While the concept of service chaining is important and there is promising market activity, there is not a common definition of network service chaining. However, there are already several proofs-of-concept underway in operator networks, and some limited commercial deployments of dynamic service chaining. Typically, these trials are linked to the use of SDN and virtualization and applied to Layer 4-7 services in mobile (e.g., SGi-LAN) and wireline (e.g., enterprise services) networks. This is to be welcomed; given that agility and flexibility are the objectives of dynamic service chaining, the technology should be deployed commercially in advance of formal standardization and specification.

Service Chaining in Software-Centric Telecom Networks examines the drivers for service chaining in telecom operator networks and identifies the key technology innovations and architectural requirements needed to make the concept commercially attractive. It explores emerging use cases that take advantage of service chaining technology, discusses how different operators and vendors plan to implement the technology in their products and networks, and analyzes what can be learned from putative service chaining deployments in the software-defined data center.

This report profiles eight leading vendors of service chaining solutions, to provide a selection of different approaches to this evolving concept. The intent in the report is not to provide a comprehensive review of all vendors, which would be excessively long, but merely to offer an overview of the types of market propositions in play.

The service chain concept is shown in the excerpt below. Each circle represents a different service function (or network function) that is connected to other services via a network. The arrows represents three different service chains that comprise of a particular set of service functions connected in order.

Excerpt 1: Service Chaining Concept

                     Source: Heavy Reading.

Service chaining occurs along processing paths that reach across the network. Therefore, many organizations are involved in developing use cases and specifications, and many others are impacted by it. At some level, it is arguable that too many competing interests, backing too many specification initiatives, will result in overlap and confusion. In practice, however, we expect to see greater collaboration between groups as service chaining requirements and potential solutions become clearer. The excerpt below summarizes the most influential industry organizations working on service chaining.

Excerpt 2: Industry Organizations With Network Chaining Activities

                     Source: Heavy Reading.

Report Scope & Structure

Service Chaining in Software-Centric Telecom Networks is structured as follows:

Section I is an introduction to the report, with complete report key findings.

Section II introduces network service chaining, explains what it is, and discusses why it's important.

Section III examines the industry organizations that are defining and standardizing service chaining technology.

Section IV investigates use cases and asks where service chaining will be used first.

Section V covers the technologies and subsystems that are needed to realize service chaining in telco networks.

Section VI profiles vendor solutions and product development strategies.

Service Chaining in Software-Centric Telecom Networks is published in PDF format.

Table of Contents

LIST OF FIGURES

I. INTRODUCTION & KEY FINDINGS

  • 1.1. Key Findings
  • 1.2. Report Scope & Structure

II. NETWORK SERVICE CHAINING - WHAT IS IT

  • 2.1. Working Definitions
  • 2.2. A Conceptual Example
  • 2.3. Working Example - Enterprise Services
  • 2.4. Working Example - Mobile Services
  • 2.5. Evolution of the Concept

III. KEY INITIATIVES & ORGANIZATIONS

  • 3.1. ETSI NFV Forwarding Graph
  • 3.2. IETF Service Function Chaining
    • SFC Architecture
    • An SFC Encapsulation (Header) Format
    • Control Plane Mechanisms
  • 3.3. Open Networking Foundation

IV. USE CASES - WHERE WILL SERVICE CHAINING BE USED

  • 4.1. Which Service Functions
  • 4.2. User-Programmable Network Services
  • 4.3. Enterprise Service Chaining
  • 4.4. SGi-LAN
  • 4.5. Layer 3 Service PoP
  • 4.6. Data Center Networking

V. KEY TECHNOLOGIES

  • 5.1. Service Chaining System
  • 5.2. Service Functions (VNFs)
  • 5.3. Flow Identification & Classification
  • 5.4. Service Chain Controller
  • 5.5. Cloud Management Platform & Orchestration
  • 5.6. Networking: SDN & Virtual Overlays

VI. VENDOR APPROACHES

  • 6.1. Alcatel-Lucent
  • 6.2. Cisco Systems Inc.
  • 6.3. ConteXtream Inc.
  • 6.4. Ericsson AB
  • 6.5. F5 Networks Inc.
  • 6.6. Huawei Technologies Co. Ltd.
  • 6.7. Juniper Networks Inc.
  • 6.8. Sandvine Inc.

APPENDIX A: ABOUT THE AUTHOR

APPENDIX B: LEGAL DISCLAIMER

LIST OF FIGURES*

SECTION - I

SECTION - II

  • Figure 2.1: Service Chaining Concept
  • Figure 2.2: Flexible Service Chaining Scenarios
  • Figure 2.3: Enterprise Service Chaining
  • Figure 2.4: Gi-LAN Service Chaining
  • Figure 2.5: Dynamic Service Chaining (Embedded in Network Nodes)

SECTION - III

  • Figure 3.1: Industry Organizations With Network Chaining Activities
  • Figure 3.2: Mapping an NFV Forwarding Graph
  • Figure 3.3: Comparison of Physical & Virtual Forwarding Graphs
  • Figure 3.4: Mapping Virtualized & Non-Virtualized Functions to a Forwarding Graph
  • Figure 3.5: Service Chaining Data Information Model for NFV
  • Figure 3.6: SFC Architecture
  • Figure 3.7: SFC Control Plane Architecture
  • Figure 3.8: SDN/ONF Architecture for Flexible Service Chaining

SECTION - IV

  • Figure 4.1: NTT's Cloud Networking Services
  • Figure 4.2: Enterprise Service Chaining Proof-of-Concept
  • Figure 4.3: Migrating Physical CPE Functions to the Cloud
  • Figure 4.4: Migrating Physical CPE Functions to the Cloud
  • Figure 4.5: Classic Hardwired SGi Service Chain
  • Figure 4.6: Layer 3 Service Pop Architecture
  • Figure 4.7: Andromeda Network Virtualization Stack for Google Cloud Platform

SECTION - V

  • Figure 5.1: Generic Model for Network Service Chaining
  • Figure 5.2: NFV Architecture & Virtual Networking

SECTION - VI

  • Figure 6.1: Nuage Networks Virtualized Service Platform
  • Figure 6.2: ContexNet Architecture Overview
  • Figure 6.3: ContexNet Components
  • Figure 6.4: Overview of Ericsson's Service Chaining Solution
  • Figure 6.5: F5's Platform Applications
  • Figure 6.6: Service Chaining Using F5's Service Gateway
  • Figure 6.7: Huawei's Service Chaining Model (for Gi-LAN)
  • Figure 6.8: Huawei's Network Application Store Concept
  • Figure 6.9: Dynamic Service Chaining in Telco Data Center

* All charts and figures in this report are original to Heavy Reading, unless otherwise noted.

Back to Top