1、 ETSI TS 102 856-1 V1.1.1 (2011-07)Technical Specification Satellite Earth Stations and Systems (SES);Broadband Satellite Multimedia (BSM);Multi-Protocol Label Switching (MPLS)interworking over satellite;Part 1: MPLS-based Functional ArchitectureETSI ETSI TS 102 856-1 V1.1.1 (2011-07)2Reference DTS/
2、SES-00306 Keywords architecture, broadband, IMS, internet, interworking, IP, MPLS, multimedia, satellite ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la
3、 Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents betwe
4、en such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be
5、subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor
6、/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand th
7、e ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 102
8、856-1 V1.1.1 (2011-07)3Contents Intellectual Property Rights 5g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 9g34 General . 10g34.1 BSM . 10g34.1.1 BSM
9、Functional Architecture . 10g34.1.2 BSM QoS Architecture . 10g34.1.3 BSM Traffic Classes . 10g34.2 MPLS . 11g34.2.1 MPLS Objectives 11g34.2.2 MPLS Signalling 11g34.2.3 MPLS QoS Issues . 11g34.2.4 MPLS Traffic Engineering . 12g34.2.5 MPLS Encapsulation 12g34.2.6 MPLS VPNs . 13g34.3 Functional Require
10、ments 13g35 MPLS/BSM Functional Architecture . 13g35.1 Scenario A: Full Interworking of MPLS 14g35.1.1 Network Architecture . 14g35.1.2 Protocol Stack . 17g35.1.3 QoS Provisioning 19g35.1.3.1 BSM Traffic Classes . 19g35.1.3.2 DiffServ . 20g35.1.3.3 IntServ . 21g35.1.4 Traffic Engineering . 21g35.1.5
11、 Resiliency . 22g35.2 Scenario B: Interworking Using IP Tunnels . 23g35.2.1 Network Architecture . 24g35.2.2 Protocol Stack . 25g35.2.3 QoS Provisioning 25g35.2.4 Traffic Engineering . 26g35.2.5 Resiliency . 26g36 MPLS/BSM-Specific Functional Elements 26g36.1 LSR/ST . 26g36.2 LSR/Hub 27g36.3 LSR/GW
12、. 27g36.4 LSR/OBP-Sat . 27g3Annex A (informative): Use Cases 28g3A.1 MPLS Network using Scenario A1 28g3A.2 MPLS Network using Scenario B1 29g3A.3 MPLS Network using Scenario A2 29g3A.4 MPLS VPN using Scenario A1 30g3ETSI ETSI TS 102 856-1 V1.1.1 (2011-07)4Annex B (informative): MPLS Transport Profi
13、le . 32g3Annex C (informative): Bibliography . 33g3History 34g3ETSI ETSI TS 102 856-1 V1.1.1 (2011-07)5Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly
14、available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
15、server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may bec
16、ome, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and Systems (SES). The present document is part 1 of a multi-part deliverable covering the issues related to the use of MPLS (Multi-Protocol Label
17、 Switching) in “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM)“, as identified below: Part 1: “MPLS-based Functional Architecture“; Part 2: “Negotiation and management of MPLS labels and MPLS signalling with attached networks“. Introduction Multi-protocol Label Swit
18、ching (MPLS) is employed today as a solution for delivering quality of service (QoS) on IP-based terrestrial networks by providing QoS-based routing of IP traffic, among other advanced capabilities. Compatibility between the BSM and MPLS networks should be an essential feature, for example to provid
19、e extensions and interconnectivity to terrestrial MPLS networks and/or a satellite back-up for terrestrial MPLS networks. The ability to support MPLS efficiently and in a standardised manner over a BSM network forms the core rationale for the present document. This work on MPLS and QoS is independen
20、t of, but complementary to, the existing BSM specifications on QoS, in particular TS 102 463 5 and TS 102 464 6. ETSI ETSI TS 102 856-1 V1.1.1 (2011-07)61 Scope The present technical specifications extend and complement the existing BSM QoS functional architecture to enable transport of MPLS signall
21、ing and data flows over a BSM network in a way such that MPLS networks connected by different STs can communicate as if they were connected by standard terrestrial LSRs (label switching routers). The present document forms part 1 of this multi-part deliverable. It defines the main architectural conc
22、epts, including the network architecture and protocol stacks, and outlines the key QoS, traffic engineering and resiliency provisions. Several architecture variants are defined and their main characteristics are analysed, also taking into account three different BSM network types. An Annex sketches
23、a set of use cases that illustrate different application and configuration scenarios of the present specifications. In a separate document, TS 102 856-2 11, the detailed procedures in BSM network entities and related signalling issues are addressed. A particular focus is placed on the fully integrat
24、ed MPLS/BSM architecture as defined in the present document. The setup of multicast MPLS paths is considered out of scope of this multi-part deliverable. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For speci
25、fic references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference.
26、NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. 1 ETSI TS 102 292: “Satellite Earth Station
27、s and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; Functional architecture for IP interworking with BSM networks“. 2 ETSI TS 102 295: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; BSM Traffic Classes“.
28、 3 ETSI TS 102 357 (V1.1.1): “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Common Air interface specification; Satellite Independent Service Access Point SI-SAP“. 4 ETSI TS 102 462: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM)
29、; QoS Functional Architecture“. 5 ETSI TS 102 463: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with IntServ QoS“. 6 ETSI TS 102 464: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with DiffServ Qos“.
30、 7 ETSI TS 102 672: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Management Functional Architecture“. ETSI ETSI TS 102 856-1 V1.1.1 (2011-07)78 ETSI TS 102 673: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Performance Parame
31、ters“. 9 ETSI TS 102 675-1: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Part 1: Performance Management at the SI-SAP“. 10 ETSI TS 102 675-2: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Part 2: Performance Management Inform
32、ation Base“. 11 ETSI TS 102 856-2: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Multi-Protocol Label Switching (MPLS) interworking over satellite; Part 2: Negotiation and management of MPLS labels and MPLS signalling with attached networks“. 2.2 Informative refe
33、rences The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TR 101 984: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Services and architecture
34、s“. i.2 IETF RFC 1633: “Integrated Services in the Internet Architecture: an Overview“. i.3 IETF RFC 2205: “Resource Reservation Protocol (RSVP) - Version 1 Functional Specification“. i.4 IETF RFC 2210: “The Use of RSVP with IETF Integrated Services“. i.5 IETF RFC 2702: “Requirements for Traffic Eng
35、ineering over MPLS“. i.6 IETF RFC 2983: “DiffServ and Tunnels“. i.7 IETF RFC 3107: “Carrying Label Information in BGP-4“. i.8 IETF RFC 3031: “Multiprotocol Label Switching Architecture“. i.9 IETF RFC 3209: “RSVP-TE Extensions to RSVP for LSP Tunnels“. i.10 IETF RFC 3270: “MPLS Support of Differentia
36、ted Services“. i.11 IETF RFC 3564: “Requirements for Support of Differentiated Services - aware MPLS Traffic Engineering“. i.12 IETF RFC 3630: “Traffic Engineering Extensions to OSPF Version 2“. i.13 IETF RFC 4023: “Encapsulating MPLS in IP or GRE“. i.14 IETF RFC 4090: “Fast Reroute Extensions to RS
37、VP-TE for LSP Tunnels“. i.15 IETF RFC 4124: “Protocol Extensions for Support of DiffServ-aware MPLS Traffic Engineering“. i.16 IETF RFC 4271: “A Border Gateway Protocol 4 (BGP-4)“. i.17 IETF RFC 4364: “BGP MPLS IP VPNs“. i.18 IETF RFC 4577: “OSPF as the Provider/Customer Edge Protocol for BGP/MPLS I
38、P VPNs“. i.19 IETF RFC 5036: “LDP Specification“. i.20 IETF RFC 5586: “MPLS Generic Associated Channel“. i.21 IETF RFC 5654 - Requirements of an MPLS Transport Profile“. i.22 IETF RFC 5860: “Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks“. i.23 IETF RFC
39、 5921: “A Framework for MPLS in Transport Networks“. ETSI ETSI TS 102 856-1 V1.1.1 (2011-07)8i.24 IETF RFC 5950: “Network Management Framework for MPLS-based Transport Networks“. i.25 IETF RFC 5960: “MPLS Transport Profile Data Plane Architecture“. 3 Definitions and abbreviations 3.1 Definitions For
40、 the purposes of the present document, the following terms and definitions apply: architecture: abstract representation of a communications system NOTE: Three complementary types of architecture are defined: square4 Functional Architecture: the discrete functional elements of the system and the asso
41、ciated logical interfaces. square4 Network Architecture: the discrete physical (network) elements of the system and the associated physical interfaces. square4 Protocol Architecture: the protocol stacks involved in the operation of the system and the associated peering relationships. BSM network: BS
42、M subnetwork together with the BSM interworking and adaptation functions that are required to provide IP interfaces (i.e. layer 3 and below) to attached networks BSM subnetwork: all the BSM network elements below the Satellite Independent Service Access Point (SI-SAP) control plane: plane that has a
43、 layered structure and performs the call control and connection control functions; it deals with the signalling necessary to set up, supervise and release calls and connections label switched path: path through one or more LSRs at one level of the hierarchy followed by a packets in a particular FEC
44、NOTE: This definition is taken from RFC 3031 i.8. label switching router: MPLS node which is capable of forwarding native L3 packets NOTE: This definition is taken from RFC 3031 i.8. MPLS label: label which is carried in a packet header, and which represents the packets FEC NOTE: This definition is
45、taken from RFC 3031 i.8. MPLS node: node which is running MPLS NOTE 1: An MPLS node will be aware of MPLS control protocols, will operate one or more L3 routing protocols, and will be capable of forwarding packets based on labels. An MPLS node may optionally be also capable of forwarding native L3 p
46、ackets. NOTE 2: This definition is taken from RFC 3031 i.8. multi-protocol label switching: IETF working group and the effort associated with the working group NOTE: This definition is taken from RFC 3031 i.8. user plane: plane that has a layered structure and provides user information transfer, alo
47、ng with associated controls (e.g. flow control, recovery from errors, etc.) ETSI ETSI TS 102 856-1 V1.1.1 (2011-07)93.2 Abbreviations For the purposes of the present document, the following abbreviations apply: 3GPP 3rdGeneration Partnership Project BA Behaviour Aggregate BGP Border Gateway Protocol
48、 BSM Broadband Satellite Multimedia CE Customer Edge DiffServ Differentiated Services DS Differentiated ServicesDSCP DiffServ Code Point E-LSP Explicitly TC-encoded PHB Scheduling Class FEC Forwarding Equivalence Class GRE Generic Routing Encapsulation GW Gateway HTTP Hypertext Transfer Protocol IET
49、F Internet Engineering Task Force IntServ Integrated Services IP Internet ProtocolIPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 L1 Layer 1L2 Layer 2L3 Layer 3LAN Local Area Network LER Label Edge Router L-LSP Label-Only-Inferred PHB Scheduling Class LSA Link State Advertisement LSP Label Switched Path LSR Label Switching Router MPLS Multi-Protocol Label Switching NCC Network Control Centre NMC Network Management Centre NMS Network Management System OAM Operations, Admi
