hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2d520303cd2976db96cb1a2e37effa96 | 102 859-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: • terms given in TS 102 636-6-1 [1]; • terms given in ISO/IEC 9646-1 [2] and in ISO/IEC 9646-7 [3]. In particular, the following terms given in ISO/IEC 9646-1 [2] apply: Implementation Conformance Statement (ICS): statement made by the... |
2d520303cd2976db96cb1a2e37effa96 | 102 859-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: GVL Geographical Virtual Link ICS Implementation Conformance Statement IPv6 Internet Protocol version 6 ITS Intelligent Transportation Systems IUT Implementation Under Test LAN Local Area Network NBMA Non-Broadcast Multi-Access NDMA Non-Broadc... |
2d520303cd2976db96cb1a2e37effa96 | 102 859-1 | 4 Conformance requirement concerning PICS | If it claims to conform to the present document, the actual PICS proforma to be filled in by a supplier shall be technically equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and ordering of the proforma items. An ICS which conforms to the present document shall be a ... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 1 Scope | The BSM/MPLS technical specifications extend and complement the existing BSM functional architecture ([1] to [3]) and the SI-SAP interface [4] to enable transport of MPLS signalling 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 b... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 292: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; Functional architecture for IP interworking with BSM networks". [2] ETSI TR 101 984: "Satellite... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 2.2 Informative references | 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 TS 102 602: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia; Connection Control Protocol (C2P) for DVB-RCS; Specifica... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 3 Definitions and abbreviations | |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 3.1 Definitions | For 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: Functional Architecture: the discrete functional elements of the system and the associated logical interfac... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Assured Forwarding ATM Asynchronous Transfer Mode BA Behaviour Aggregate BE Best Effort BNMS BSM Network Management System BSM Broadband Satellite Multimedia BSMS BSM System CL Controlled Load CS Class Selector DiffServ Differentiated servi... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 4 General background on MPLS and BSM | |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 4.1 MPLS labels allocation and distribution | MPLS adds a header (also called the "shim header") in front of IP packets, it can contain one or more "MPLS headers" in a stack (also called the "label stack"). An MPLS header is 32 bits long and contains four fields: • label value (20 bits), • Traffic Class (TC) field (3 bits), for QoS priority, it was originally call... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 4.2 General QoS issues in MPLS | Providing QoS support in MPLS networks means that packets are forwarded via MPLS label swapping, but different packet flows of different service classes are treated in different ways (see [i.7]). We will consider the most general case in which an extended, hybrid (i.e. terrestrial IP and BSM) MPLS network is running RS... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 4.5 Relevance of the present document for Scenarios B and C | Scenarios B and C were introduced in TS 102 856-1 [13]. In Scenario B, the BSM network is processing only IP packets. The QoS requirements linked to the encapsulated MPLS packet have to be mapped onto the encapsulating IP header, so that the BSM entities can process and forward these IP datagrams following exactly the ... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 5 U-plane MPLS data transfer in BSM Systems | In an ST the SI-SAP provides to the higher layers a data transfer service, which is used to transfer PDUs from the Satellite-Independent (SI) layers down to the Satellite-Dependent (SD) layers at the ingress ST, and from the SD layers to the SI layers at the egress ST. This is done by taking the SI PDU as a Service Dat... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 5.1 SI-SAP as external interface | An external MPLS router (LSR/LER) may need to be connected to an SD-only capable ST through a physical SI-SAP interface over which the primitives will be exchanged. Even if physically separated, the MPLS router and the SD-only ST represent logically a fully integrated MPLS-enabled ST, so this situation falls in the sam... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 5.2 SD transport of MPLS packets | There are two possible ways of handling MPLS packets at SD layers: • encapsulate the MPLS packet in the SD link layer protocol; • strip off the MPLS header and map in onto an SD identifier. The former method allows "transport" of the MPLS label transparently, and is the most flexible way; the method always works also i... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6 C-plane procedures for MPLS in BSM Systems | The issues arising in the C-plane from the introduction of MPLS derive from the fact that the way, in which MPLS packets have to be forwarded through the SI-SAP, needs to be specified. Basically there are only two issues to be specified, namely the service level which has to be assigned to each LSP (i.e. the QID to be ... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.1 Forwarding policies for MPLS signaling | MPLS signaling packets are used to setup LSPs and to distribute labels, so that the MPLS switch can be configured for the different operations which need to be performed: label swapping (at the LSR), label pushing and popping (at the LER). This signaling is performed by means of IP-based protocol, RSVP-TE or LDP. These... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.1.1 MPLS-signalling QID: IP_queue_label and QIDSPEC parameters | The value of the IP_queue_label parameter is implementation dependent and not relevant here; anyway an example may help to understand its meaning and may also help in the choice of QIDSPEC. For example, at IP level the MPLS signalling packets could be mapped onto a DiffServ Assured Forwarding (AF) class of high priorit... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.1.2 MPLS-signalling QID: destination BSM_ID parameter | The destination BSM_ID for these MPLS signalling packets can be derived by means of usual SI-SAP address resolution primitives, as these packets are plain IP packets. |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.1.3 MPLS-signalling QID: lease time parameter | The lease time of the QID meant to be used to forward MPLS signalling has to be "0x0", which means that the QID is of hard state and it does not expire. ETSI ETSI TS 102 856-2 V1.1.1 (2011-07) 17 |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.2 QoS and resource allocation | In terms of QoS, MPLS requires minor C-plane modifications in order to be accommodated in a BSM-compliant ST. When receiving MPLS signalling packets, QIDs have to be opened, modified or closed. Each LSP may be mapped onto a single QID or multiple LSPs may be mapped onto the same QID, also an LSP may be mapped onto mult... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.2.1 DiffServ | Figure 6.1 shows the numbering relationship between DiffServ PHBs, LSPs (of type L- and of type E-) and QIDs. With this model in mind it is clear that when handling (i.e. opening, modifying, or closing) a QID associated to a specific LSP (or to a group of LSPs), the characteristics of the PHB(s) mapped onto that LSP(s)... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.2.2 IntServ | Figure 6.2 shows the numbering relationship between IntServ flows (Guaranteed Service, GS, and Controlled Load, CL), LSPs and QIDs. It is here assumed that each IntServ flow is associated to one LSP. This may not be the only possibility, but probably the most likely one, because RSVP-TE, which can be used to create LSP... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.3 MPLS interfaces at SI-SAP | This clause describes a preferred method for implementing standard MPLS over BSM networks (which can be easily generalized for any satellite network). The forwarding of an IP packet through the SI-SAP undergoes two steps: 1) the destination IP address in the IP header is used to discover the next-hop IP address (by loo... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.3.1 MPLS outgoing interface at the ingress ST | For each MPLS path an ingress ST should determine the next-hop BSM_ID that is associated with an incoming MPLS label. This can be derived knowing the next-hop IP address associated to that MPLS label. When the ST starts receiving MPLS-labelled packets, the IP headers should no longer be inspected, and so the associatio... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 6.3.2 MPLS incoming interface at the egress ST | At the egress ST a dual procedure has to take place. The reason is that an MPLS node applies the appropriate operations on an MPLS-labelled packet (swapping or popping), also based on the incoming interface of the packet (see use of the ILM table, previously explained); this is done to avoid inspection of the IP header... |
a6f9aa311da66fd0df68e7e3db380136 | 102 856-2 | 7 M-plane procedures in support of MPLS | When running an LSP over a satellite interface, it is important to monitor the link attributes in particular to respond to variable or adaptive rate of the satellite link (including outages and rain fades) or to accept/reject new resource reservation requests. In order for the BNMS to constantly monitor link attributes... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 1 Scope | The present technical specifications extend and complement the existing BSM QoS functional architecture to enable transport of MPLS signalling 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 switc... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 292: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; Functional architecture for IP interworking with BSM networks". [2] ETSI TS 102 295: "Satellite... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 2.2 Informative references | 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 architectures". [i.2] IETF RFC 1633: ... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 3 Definitions and abbreviations | |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 3.1 Definitions | For 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: Functional Architecture: the discrete functional elements of the system and the associated logical interfac... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project BA Behaviour Aggregate BGP Border Gateway Protocol BSM Broadband Satellite Multimedia CE Customer Edge DiffServ Differentiated Services DS Differentiated Services DSCP DiffServ Code Point E-LSP Explicitl... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4 General | This clause identifies and briefly sketches the core technologies that need to be brought together to define an integrated MPLS/BSM architecture. |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.1 BSM | ETSI's Working Group SES BSM has made substantial progress over the past decade in defining an IP-based BSM network. Among the technical specifications and reports generated by the WG, TS 102 292 [1] (Functional Architecture for IP Interworking with BSM Networks) and TS 102 462 [4] (QoS Functional Architecture) are esp... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.1.1 BSM Functional Architecture | TS 102 292 [1] introduces a satellite-independent service access point, the SI-SAP interface. This interface provides the higher-layer BSM functions inside the satellite terminal with a service access point for the lower layer (satellite-specific) functions. It allows the BSM protocols developed in the satellite-indepe... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.1.2 BSM QoS Architecture | Central to the QoS capability of a BSM network is the concept of QIDs (Queue Identifier). These represent abstract queues that are defined at the SI-SAP for the purpose of transferring user data via the SI-SAP. The satellite dependent layers are responsible for assigning satellite capacity to these abstract queues acco... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.1.3 BSM Traffic Classes | Service providers are generally not interested in the specific QoS mechanisms or in numerically quantifying QoS attributes, like maximum allowed delay or jitter, per application. Rather, it must simply be ensured that traffic entering the BSM is characterised, sorted and processed according to its characteristic. For t... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.2 MPLS | |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.2.1 MPLS Objectives | MPLS is an IETF mechanism (RFC 3031 [i.8]) that enables packet switched networks to operate more efficiently and under greater control by the network operator. When MPLS was first introduced in the mid-1990's, the primary goal was to provide new capabilities in IP routers to optimise overall traffic throughput and to c... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.2.2 MPLS Signalling | Historically, MPLS was conceived as a mechanism to segregate IP traffic into distinct LSPs for QoS and traffic engineering purposes. Different LSPs would carry different types of traffic which could receive dedicated handling and forwarding by MPLS routers according to their priority. These LSPs can be established in d... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.2.3 MPLS QoS Issues | As regards the support of QoS in MPLS networks, an obvious approach is to simply send QoS-sensitive traffic over dedicated, traffic-engineered LSP tunnels whose participating LSRs exhibit the desired pre-arranged forwarding behaviour. The issue here is how to manage such a QoS provision on a large scale. One approach w... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.2.4 MPLS Traffic Engineering | Traffic Engineering is concerned with performance optimisation of operational networks. RFC 2702 [i.5] (Requirements for Traffic Engineering over MPLS) identifies the functional capabilities required to implement policies that facilitate efficient and reliable network operations in an MPLS network. An important concept... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.2.5 MPLS Encapsulation | The core operation in MPLS networks is the forwarding of LSPs, and this operation is performed by MPLS enabled IP routers. Since non-MPLS capable IP routers cannot interpret the MPLS shim header, such routers cannot forward LSPs. However, it is possible to tunnel LSPs across a non-MPLS enabled IP network. This is done ... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.2.6 MPLS VPNs | The problem of how to deliver VPN solutions over IP networks has long been debated by the IP community, including the MPLS Working Group. With RFC 4364 [i.17] (BGP MPLS IP VPNs), a stable MPLS-based solution is now available which in fact extends MPLS into a new application area. RFC 4364 i.17 describes a method by whi... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 4.3 Functional Requirements | When considering the integration of MPLS capabilities with BSM networks, the following high-level functional requirements are identified: 1) The integrated MPLS/BSM functional architecture should support all of the features of MPLS. 2) There shall be no requirement for modification of MPLS protocols (MPLS control and d... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5 MPLS/BSM Functional Architecture | This clause defines scenarios for integrated MPLS/BSM functional architectures. The common theme in all these scenarios is that a terrestrial MPLS-based IP network is interconnected with a BSM network, thus enabling MPLS- based traffic to enter the BSM network. The different scenarios introduced below are characterised... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1 Scenario A: Full Interworking of MPLS | This clause introduces an integrated MPLS/BSM scenario whereby full interworking between the MPLS and BSM networks is realised (Scenario A). From an MPLS network point of view, this means that the functional characteristics of LSPs entering the BSM network do not differ from LSPs that run across terrestrial links. From... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.1 Network Architecture | Figures 5.1 to 5.3 introduce Scenario A1, which is defined in terms of fully MPLS capable ST and Hub (respectively GW) entities. Figure 5.1 shows the architecture of Scenario A1 for the case when the BSM network is of type TSS. In this case, LSPs inside the BSM network directly interconnect the combined LSR/ST only wit... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.2 Protocol Stack | This clause specifies the protocol stacks for the variants of Scenario A introduced above. The discussion here is kept at a conceptual level and any details, in particular relating to SI-SAP and the procedures at the user, control and management planes, are given in TS 102 856-2 [11]. Figure 5.5 shows the protocol stac... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.3 QoS Provisioning | The problem of how to introduce QoS awareness in BSM networks is addressed in the three technical specifications TS 102 462 [4] (QoS functional architecture), TS 102 464 [6] (Interworking with DiffServ QoS) and TS 102 463 [5] (Interworking with IntServ QoS). The central theme in these specifications concerns the mappin... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.3.1 BSM Traffic Classes | As mentioned in the clauses 4.1.2 and 4.1.3, the BSM traffic classes were constructed for the purpose of capturing and categorising a wide spectrum of observed traffic characteristics. They do not correspond to any specific Internet QoS model. In fact, for a given QoS model (e.g. DiffServ, IntServ, or any proprietary o... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.3.2 DiffServ | Figure 5.9 illustrates the relationship between the IP layer, the BSM SD layer, and the MPLS sublayer for the case when the DiffServ model is used at the IP layer. No distinction is made here between the user, control and management planes. For each layer, certain key parameters that are relevant in the present context... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.3.3 IntServ | IntServ is an IETF architecture (defined in RFC 1633 [i.2]) that supports guaranteed QoS in IP networks. In contrast to DiffServ, the IntServ model relies on a resource reservation protocol, RSVP (defined in RFC 2205 [i.3]), to request and reserve the required resources along the path. An RSVP request contains the so-c... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.4 Traffic Engineering | As discussed in clause 4.2.4, traffic engineering in MPLS networks deals with the problem of mapping traffic trunks onto LSPs with the objective to optimise network resource utilisation and traffic performance. Since, in Scenario A, all BSM network entities that process IP traffic are fully MPLS-capable routers, all IE... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.1.5 Resiliency | As part of the overall TE framework, resiliency is concerned with the robustness, survivability and (automatic) restorability of a network in the event of a variety of possible failure modes. Concerning MPLS networks, resilience features appear in several TE-specific IETF specifications already mentioned in the previou... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.2 Scenario B: Interworking Using IP Tunnels | This clause introduces an MPLS/BSM scenario whereby no direct interworking between the MPLS and BSM network is foreseen (Scenario B). The sole objective here is to ensure that the LSP is tunnelled across the BSM network, thus enabling it to emerge intact at the other side. Consequently, no explicit MPLS specific treatm... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.2.1 Network Architecture | Figure 5.11 depicts the architecture of Scenario B1, using a BSM network of type TSS as an example. The following considerations however apply to all types of BSM network. The figure first of all shows that all BSM entities remain unaffected by MPLS. In fact, the encapsulation or decapsulation procedures are performed ... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.2.2 Protocol Stack | Figure 5.13 shows the protocol stack for Scenario B1. Since the BSM network is transparent to MPLS, the protocol stack remains unchanged with respect to the original BSM stack, and no MPLS functionality is present inside the BSM network. Note that the fact that the IP layer encapsulates MPLS affects neither the protoco... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.2.3 QoS Provisioning | Since the BSM network is transparent for MPLS, BSM entities have no access to the MPLS shim header and are thus unable to realise any specific QoS requirements that may be encoded in the MPLS TC field and/or the MPLS label. In order to provide specific QoS guarantees to the tunnelled portion of the LSP, therefore, the ... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.2.4 Traffic Engineering | Traffic engineering in a Scenario-B MPLS/BSM network can be performed using the same procedures and mechanisms as in ordinary MPLS networks (and in Scenario A). In contrast to Scenario A, however, the BSM stations (ST, Hub, GW) are not MPLS capable, thus requiring functionally separated LSRs to be introduced outside th... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 5.2.5 Resiliency | Similarly, the resiliency procedures described for the case of Scenario A (see clause 5.1.5) also apply for Scenario B. Again, however, the peculiar architectural feature of Scenario B that the MPLS hop across the BSM network consists of three physical links, constrains the flexibility of TE/resiliency actions that exi... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 6 MPLS/BSM-Specific Functional Elements | In this clause the various functional entities of the MPLS/BSM scenarios introduced in the previous clause will be briefly described and their key features summarised. TS 102 856-2 [11] will define the involved user, control, and management plane procedures in detail. |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 6.1 LSR/ST | The LSR/ST is a BSM functional network entity that provides MPLS-based interworking between the BSM network and a premises network. It combines the role of an LSR (MPLS-enabled IP router) with that of a BSM ST. Specifically, when communicating with other LSRs, this entity behaves like an ordinary LSR, and when communic... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 6.2 LSR/Hub | The LSR/Hub functional entity appears in network topologies where double-hops occur between remote stations. The LSR/Hub relays this double-hop traffic by means of MPLS switching, thus acting like an ordinary LSR. In terms of its role as a BSM station, the LSR/Hub is capable of both receiving traffic from, and transmit... |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 6.3 LSR/GW | The LSR/GW functional entity provides MPLS-based interworking between the BSM network and external networks. It thus provides the same basic functions as the LSR/ST, both in terms of its role as an LSR and as a BSM station. The capabilities described for the LSR/ST in clause 6.1 thus also apply for the LSR/GW. |
6dc69f59cf10bd5f15508ebf43211fb2 | 102 856-1 | 6.4 LSR/OBP-Sat | The LSR/OBP-Sat functional entity appears in Scenario A2 in clause 5.1 (Figure 5.4), where a BSM network of type RSM is assumed. As this scenario is not analysed in detail in the present document, the LSR/OBP-Sat will not be discussed further here. ETSI ETSI TS 102 856-1 V1.1.1 (2011-07) 28 Annex A (informative): Use C... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 1 Scope | The integration and interoperability of BSM networks with the NGN is specified in terms of the functional architecture and associated functions and interfaces. The present document is based on and uses TISPAN (release 2) definitions and terminology (since TISPAN release 3 is not yet fully specified). |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 292: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; Functional architecture for IP interworking with BSM networks". [2] ETSI TS 102 357: "Satellite... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 2.2 Informative references | 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 architectures". ETSI ETSI TS 102 855 ... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 3 Definitions and abbreviations | |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 3.1 Definitions | For 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: - Functional Architecture: the discrete functional elements of the system and the associated logical interfac... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: (NGN)-GETS Government Emergency Telecommunications Services (NGN is GETS with NGN) (x)DSL Digital Subscriber Line NOTE: x means the different flavours of DSL. 3GPP 3rd Generation Partnership Project AF Access Function AMF Access Management Fun... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4 NGN Impacts on BSM Networks | |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.1 Background | The Next Generation Network (NGN) is intended to support a set of assured (and best-effort) end-to-end services over a network composed of heterogeneous sub-networks, and based on the Internet Protocol (IP). One of the main characteristics of the NGN architecture is the uncoupling of services and underlying transport f... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.2 NGN Network Architecture | Figure 4.2 shows a combined physical and functional overview of the NGN network as defined by ES 282 001 [5] (NGN Functional Architecture). In the figure the BSM network may take the place of an access transport function (network). The functional entities that make up a subsystem may be distributed over network/service... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.2.1 Service Stratum | The NGN needs to support a wide variety of application services. In the Service Stratum therefore, while IMS (see annex A for a description) is at the heart of all emerging NGN standards, it is just one of a number of Service Control Subsystems. Examples of other Service Control Subsystems include for example PSTN emul... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.2.2 Transport Stratum | IP-connectivity is provided to the NGN customer equipment and to other networks by the Transport Stratum. This transport layer comprises a Transport Control Sublayer on top of transport processing functions in the access and core networks. Equivalent functions should exist in the User Equipment. |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.2.2.1 Transport Control Sublayer | The Transport Control Sublayer is further divided in two subsystems that work closely together: • Network Attachment Subsystem (NASS): - Manages all aspect of network attachment such as IP address provisioning (e.g. DHCP), network level user authentication, authorisation of network access and access network configurati... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.2.2.2 Transport Processing Functions | Transport processing functions in the access and core networks include functions supporting packet forwarding and routing. These are: • Media Gateway Function (MGF): - The MGF is a translation service that handling the disparate telecommunications networks over the NGN especially transcoding/mapping between IP and lega... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3 Service requirements | |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.1 General NGN Service Requirements | Apart from the "fundamental capabilities" described above namely packet-based transfer, separation of control functions and support for a wide range of services, other capabilities offered by the NGN architecture are summarised in table 4.1. ETSI ETSI TS 102 855 V1.1.1 (2011-03) 14 Table 4.1: NGN capabilities Capabilit... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2 BSM-Specific Service Requirements | In order to better identify how and where the NGN architecture and IMS functions a number of use cases are described in this clause. While representative how offered services they are illustrative in nature and of course not a comprehensive list. a) VOIP and convergence; b) IPTV and IP video: - Live/linear TV; - Video ... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.1 VOIP and convergence | This is the traditional NGN/IMS service and the impetus behind the original architecture. For the BSM network, which is already all-IP the use of NGN/IMS for voice services completely decouples the BSM network transport from the VOIP service. For example when a VOIP device registers on the VOIP service via the IMS core... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.2 IPTV and IP video | Current IPTV offerings are based on broadband wireline networks most often Digital Subscriber lines (xDSL), But the expansion of IPTV into underserved areas requires the use of Fixed Satellite Services (FSS) and hence the BSM networks. In addition, BSM networks will most likely see an upsurge of over the top (OTT) IP v... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.3 Live/linear TV | Live TV is currently most likely a multicast service using MPEG-4 codecs (of many profiles) over User Datagram Protocol directly or with the Real Time Protocol (RTP) over UDP. With IMS, the role of the BSM operator is to allocate enough resources for the IPTV session and to control QoS elements, like overall delay, esp... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.4 Video on Demand (VoD) | For BSM networks, VoD services are not greatly different than linear TV services except that VoD is more likely to have less stringent QoS requirements. But it is also well known that VoD will soon be a multiscreen and multinetwork offering. Hence the use of the IMS functions allows the BSM networks to deliver VoD serv... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.5 Emergency/Disaster Services | There are two potential services for BSM networks in emergency or disaster services: providing emergency telecommunications as defined in the ETSI EMTEL specifications (emtel.etsi.org) and supporting first responders (Government Emergency Telecommunications Services based on NGN - NGN-GETS). |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.6 Primary Infrastructure | The obvious use case for the BSM system for both EMTEL and NGN-GETS is for the BSM network to provide an instant infrastructure. For the first responders this assumes the BSM system, via the NGN infrastructure will interconnect to the TETRA (Terrestrial Trunked Radio) communication network for example via common gatewa... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.7 Infrastructure Support | A second use case is for the BSM system to back an existing terrestrial infrastructure and provide added capacity in the disaster zone. This is a preventive measure to avoid the collapse of that infrastructure under additional traffic requirements. In both cases the NGN architecture provides a policy based resource man... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.3.2.8 Smart Grid/telemetry | While it is unlikely that a BSM network will be used to monitor individual elements of the smart grid infrastructure unless these are critical, the use of the BSM system for aggregated traffic is likely. In this use case, we omit the use of smart grid services in disaster areas which is covered in the previous clause b... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 4.4 Interworking requirements | There are two fundamental ways of interconnection of the NGN with access networks (such as BSM) as well as with other NGN segments: a) Interconnection at the Service Layer - Service-Oriented Interconnection (SOIX). b) Interconnection at the Transport Layer - Connectivity-Oriented Interconnection (CoIx). Only SOIX fully... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5 BSM/NGN Architecture | In this clause the main functional elements of the BSM/NGN architecture are described with their mapping onto BSM functional elements. A general overview of the BSM-NGN architecture is given in clause 5.1 followed by specific architectures to be used for specific BSM scenarios in clause 5.2. |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.1 BSM-Specific NGN Architecture | Figure 5.1 illustrates the potential overall BSM integration as an access network in the NGN architecture. More detailed examples are given in clause 5.2. ETSI ETSI TS 102 855 V1.1.1 (2011-03) 17 Other Subsystems Core IMS PSTN/ISDN Emulation Subsystem Other Subsystems Core IMS PSTN/ISDN Emulation Subsystem User Equipme... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.2 Scenarios | A number of scenarios are possible in which the BSM network may be integrated with the NGN with varying complexity and capabilities to match short term or longer term objectives. Specific BSM/NGN Architecture Scenarios are therefore specified below in which some of the BSM service requirements of clause 4.3.2 are used ... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.2.1 IMS Service Access - Star network-based (1) | This scenario provide a minimum set of functions, keeping complexity at a low level and making this model suitable for easier transition to NGN by providing dynamic QoS management as well as unified subscriber management across the BSM network and other NGN networks. The scenario concerns a satellite star network topol... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.