1、TIA/EIA TELECOMMUNI CATIONS SYSTEMS BULLETIN Satellite ATM Networks: Architectures and Guidelines TSB91 MAY 1990 TELECOMMUNICATIONS INDUSTRY ASSOCIATION INDUSTRY ASSOClAliN Electronic Industriar Alllance STDmEIA TSBSL-ENGL 1778 m 323ibUO Ob10304 134 m NOTICE WEIA Engineering Standards and Publicatio
2、ns are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need.
3、Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of “MEIA from manufacturhg or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those ot
4、her than WEIA members, whether the standard is to be used either domestically or internationally. Standards, Publications and Buletins are adopted by EIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA/EIA does not assume any liability to any pa
5、tent owner, nor does it assume any obligation whatever to parties adopting the Standard, Publication, or Bulletin. Technical Bulletins are distinguished from TUVEIA Standards or Interim Standards, in that they contain a compilation of engineering data or information useful to the technical community
6、, and represent approaches to good engineering practices that are suggested by the formulating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly represent good engineering practice, or that may be acceptable to, or have been accepted by, appropriate b
7、odies. Parties who wish to bring other approaches to the attention of the formulating committee to be considered for inclusion in future revisions of this Builetin are encouraged to do so. It is the intention of the formulating committee to revise and update this Bulletin from time to time as may be
8、 occasioned by changes in technology, industry practice, or government regulations, or for other appropriate reasons. (From Project No. 4191, formulated under the cognizance of the TIA TR-34.1 Communications and Interoperability Subcommittee). hblished by ?IELEiCOMMUNICATIONS INDUSTRY ASSOCIATION 19
9、98 Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 PRICE: Please refer to the current Catalog of ELA, JEDEC and TIA STANDARDS and ENGINEERING PUBLICATIONS or cal Global Engineering Documents, USA and Canada (1-800-8547179) International (303-397-7956) All rights reserve
10、d Frinted in U.S.A. STD-EIA TSBSL-ENGL 1998 = 323Lib ObL0305 O70 TSB-9 1 Table of Contents Table of Contents i List of Figures ii Docum en t History ii 1 1 2 3 4 5 6 7 8 9 Scope 1 References 1 Definitions, Acronyms, and Abbreviations 1 3.1 Definitions 1 3.2 Acronyms and Abbreviations 2 Overview 2 Ro
11、uting, Rerouting, and Mobility Guidelines for Satellite ATM 3 5.1 Classification of Satellite Handovers 3 5.1.1 Inter-beam (Intra-satellite Handovers) 4 5.1.2 Inter-satellite Handovers 4 5.1.3 Summary of Satellite Handovers 4 5.2 Handovers in GEO/MEO/LEOs 4 5.2.1 Handovers in GEOs 5 5.2.2 Handovers
12、in MEOs 5 5.2.3 Handovers in LEOS 5 5.2.4 Handover Rates for LEO/MEO/GEO 5 Routing 6 Traffic Management 6 General Requirements and Governing Entities 6 7 Techniques for Improving Protocol Performance Over Satellites 1 O ATM Network Architectures for Bent Pipe Satellites 7 10.1 SATATM 1.1: Fixed ATM
13、Network Access and Network Interconnect 7 1 O. 1.1 Reference Architecture 8 10.1.2 Protocol reference model 8 10 10.2.1 Reference Architecture 10 10.2.2 Protocol reference model 11 11 10.3.1 Reference Architecture 11 10.3.2 Protocol reference model 12 13 10.2 SATATM 1.2: Mobile ATM Network Access 10
14、.3 SATATM 1.3 Mobile ATM Network Interconnect 11 ATM Network Architectures for Satellites With On-Board ATM Switches I See restrictions inside the cover page. TSB-9 1 Revision 1 2 11.1 SATATM 2.1: ATM Network Access 13 1 1.1.1 Reference Architecture 13 I 1.1.2 Protocol reference model 14 11.2 SATATM
15、 2.2: ATM Network Interconnect 15 1 1.2.1 Reference Architecture 15 1 1.2.2 Protocol reference model 15 11.3 SATATM 2.3: Full Mesh ATM 16 1 1.3.1 Reference Architecture 16 11.3.2 Protocol reference model 17 18 12 Reference Architecture Signaling Interfaces Date Remarks 12-29-97 TSB-91 Revision O 4-1
16、4-98 TSB-91 Revision 1 List of Fipures Figure I: SATATM 1.1 Reference Architecture. Figure 2: SATATM 1.1 Protocol Reference Model for Network Access. Figure 3: SA TATM I. I Protocol Reference Modelfor Network Interconnect. Figure 4: SATATM 1.2 Reference Architecture. 9 9 9 10 Figure 5: SA TATM 1.2 P
17、rotocol Reference Model. Figure 6: SATATM 1.3 Reference Architecture. II 12 Figure 7: SATATM 1.3 Protocol Reference Model. Figure 8: SATATM 2. I Reference Architecture. Figure 9: SATA TM 2.1 Protocol Referenee Model. Figure 1 O: SATATM 2.2 Reference Architecture. Figure 1 I: SATATM2.2 Protocol Refer
18、ence Model. Figure 12: SATATM 2.3 Reference Architecture. Figure 13: SATATM2.3 Protocol Reference Model. 13 14 14 15 16 17 18 Document History ,. 11 See restrictions inside the cover page. STD*EIA TSBSL-ENGL 1798 3234b00 Ob10307 943 TSB-9 1 1 Scope This document provides architectures and guidelines
19、 for satellite ATM (SATATM) networks. An important element of satellite ATM networking will involve support for the routing, rerouting, and handover of active connections. As a result, a framework for their use in satellite networks is presented and guidelines for their incorporation are provided. T
20、he guidelines and architectures presented here shall serve as a basis for the technical specifications for the SATATM networks identified here. 2 References ITU-T Recommendation 1.371 - Traffic Control and Congestion Control in B-ISDN, May 1996 ATM Forum Traffic Management Specification 4.0 TU-T Rec
21、ommendation 1.356 - B-ISDN ATM layer cell transfer performance ITU-R PDNR S.atm - Error Performance for ATM via Satellite ITU-R PDNR S.atm-av TU-R Recommendation M.687-2 - Future Public Land Mobile Telecommunications Systems (FPLMTS) ITU-R Recommendation M.816 - Framework for Seniices Supported on I
22、nternational Mobile Telecommunications-2000 (IMT-2000) ITU-R Recommendation M.817 - Future Public Land Mobile Telecommunications System: Network Architectures ITU-R Recommendation M.8 18-1 - Satellite Operation Within Future Public Land Mobile Telecommunications Systems (FPLMTS) ITU-R Recommendation
23、 M. 1034-1 - Requirements for the Radio Interface(s) for Future Public Land Mobile Telecommunication Systems IT-R Recommendation M. 1 167 - Framework for the Satellite Component of Future Public Land Mobile Telecommunication Systems (FPLMTS) ATM Forum Private Network-Network Interface Specification
24、Version 1 .O ATM Forum BISDN Inter Camer Interface (B-ICI) Specification IT-T Recommendation 1.4 13: B-ISDN User-Network Interface IT-T Recommendation 1.432: B-ISDN User Network Interface - Physical Layer Specification ITU-T Recommendation 4.293 1: B-ISDN DSS2 User Network Interface (UNI) Layer 3 Sp
25、ecification for Basic CallKonnection Control ATM Forum User-Network Interface (UNI) Specification Version 3.1 ATM Forum UNI Signaling Specification Version 4.0 3 Definitions, Acronvms. and Abbreviations 3.1 Definitions Automatic Repeat-Request (ARQ): Error control for data transmission. When errors
26、are detected by the receiver, a request is sent to the transmitter for retransmission of the errored byte, segment, or message. Data Link Control (DLC): Layer 2 of the ISO/OSI reference model. Fixed: Applied to a terminal or other device indicating that the device must remain in a futed location 1 S
27、ee restrictions inside the cover page. TSB-9 1 during operation and connection to the network. Forward Error Correction (FEC): A technique of digital error detection and correction used at the receiver. A limited number of bitdsymbols can be corrected. Bits are added to each transmitted character or
28、 block using a predetermined algorithm. Handover: A change of paths from a terminal and Access Point to another Access Point without disconnection. Logical Link Control (LLC): A sublayer of the DLC layer which manages the quality of service on a virtual circuit basis. FEC, ARQ, and flow are controll
29、ed here. A layer of the IS0 8802 above the MAC sublayer and below the Network layer. Medium Access Control (MAC): A sublayer of the DLC layer which manages channel quality, multiple terminal devices, and medium sharing. A layer of the IS0 8802 below the LLC sublayer and above the PHY layer. Mobile:
30、Applied to a terminal or other device indicating that the device remains operational and connected to the network while moving. Physical Layer (PHY): Layer 1 of the ISO/OSI reference model. SATATM: A network that makes use of satellites and canies ATM traffic. 3.2 Acronyms and Abbreviations ABR ARQ
31、DLC FEC GE0 “I LEO LLC MAC ME0 os1 PHY QOS UNI Available Bit Rate Automatic Repeat-Request Data Link Control Forward Error Correction Geosynchronous Earth Orbit Network-Network Interface Low Earth Orbit Link Level Control Medium Access. Control Middle Earth Orbit Open Systems Interconnection Physica
32、l Layer Quality of Service User-Network Interface 4 Overview In this document, three ATM network architectures for bent pipe satellites and three ATM network architectures for satellites with on-board ATM switches are described. These architectures differ from one another in terms of required level
33、of mobility, supported data rates, supported terrestrial interfaces, and on board processing and switching requirements. The ATM network architectures for bent pipe satellites considered are: 2 See restrictions inside the cover page. STD-EIA TSBSL-ENGL 1998 D 3234b00 ObL03U9 7Lb m TSB-9 1 i) SATATM
34、1.1, “Fixed ATM Network Access and Network Interconnect” which provides ATM network access to fixed terminals and interconnects fured ATM networks, ii) SATATM 1.2, “Mobile ATM Network Access” which provides ATM network access to mobile terminals, iii) SATATM 1.3, “Mobile ATM Network Interconnect” wh
35、ich provides connections between a mobile platform and a fxed network or between two mobile platforms. The satellites in architectures SATATM 1.1, 1.2, and 1.3 can cany non-ATM traffic as well. The ATM network architectures for satellites with on-board ATM switches are: i) ii) SATATM 2.2, “ATM Netwo
36、rk Interconnect” which provides high speed links to interconnect two iii) SATATM 2.3, “Full Mesh ATM in which several satellites form an ATM network in the sky and SATATM 2.1, “ATM Network Access” which provides ATM network access to termhals, ATM networks provide user access and network interconnec
37、tion services An important component of satellite ATM networking involves support for the rerouting of active connections. In this document, a description of rerouting issues is provided as well. This document addresses LEO, MEO, and GE0 satellite configurations. 5 Routinp, ReroutinP, and Mobility G
38、uidelines for Satellite ATM The satellite environment may require implementation of real time routing to support the mobility of end devices and nodes of the ATM network itself. This may require the network to have the capability to reroute active circuits in real time. In addition to supporting mob
39、ility the reroute capability can also be used to optimize network routing, respond to changing QoS requirements, and provide a Fault Tolerance mechanism. It is expected that the reroute protocols necessary to support these functions will be developed within the ATM Forum. The term handover is applie
40、d to the real time rerouting of mobile devices from one wireless physical path to another. 5.1 Classification of Satellite Handovers Handovers in satellites can be classified into those between (i) satellite beams of the same satellite and (ii) separate satellites. Handovers can be performed at eith
41、er the satellite link layer (i.e., below the ATM layer) or at ATM layers in coordination with the satellite lu they are End user to satellite 0 0 Satellite to satellite Network Access Point to satellite Coupled with the two satellite handover classifications, there are six possible handover scenario
42、s involving satellites: 1. End user to separate satellite 3 See restrictions inside the cover page. STD.EIA TSBSL-ENGL 1778 3234b00 ObL03LO 438 Performed by Handover Type Initiated by Inter-hub FES Fixed earth station (FES) Inter-satellite Intra-satellite End user Satellite (beam switching) End user
43、, FES, or Fixed earth station (FES) or satellite TSB-9 1 System LEONEO LEONE0 GEOMEO/LEO 2. End user to different satellite beam 3. Network Access Point to separate satellite 4. Network Access Point to different satellite beam 5. satellite to separate satellite 6. Satellite to different satellite be
44、am During handovers, traffic disruption may occur (perhaps resulting in some ATM cell loss), unless some advance procedures are performed prior to handovers. 5.1.1 Inter-beam (Intra-satellite Handovers) Satellites can employ beam multiplexing - where M independent beams are able to be reconfigured t
45、o service N different locations, resulting in a MX“ virtual beam system. Handovers which occur as a result of a mobile end user migrating outside the coverage of a satellite beam can be performed by using beam switching. This type of handover is commonly associated with GE0 satellite systems. Handov
46、ers in this case would be initiated by the end user or by the gateway and performed by satellite beam switching. Inter-hub handovers are a special class of intra-satellite handovers that occur between Fixed Earth Stations (FESs). It corresponds to a scenario where the current satellite remains visib
47、le to the mobile user but is moving out of visible range of the currently associated FES acting as the network access point or hub. This demands a handover to a new FES that is within the coverage of the existing satellite and within the visible range of the mobile user. Hence, inter-hub handovers a
48、re considered as a subset of intra-satellite handovers. Handovers in this scenario are initiated by the network since the network is aware whenever a satellite goes out of sight. The network will inform the mobile station about the need to perform a handover, together with information about the next
49、 hub that the mobile station has to connect to. 5.1.2 Inter-satellite Handovers Inter-satellite handovers are more complicated , and synchronization between the satellites concerned is necessary to ensure that on-going calls are not dropped and ATM cells continue to arrive in sequence. These handovers occur as LEOME0 satellites migrate over time in their orbits. It can also occur when a mobile user terminal or switch (example in an airplane) moves out of one satellites coverage and enters into another, Handover signaling between the ground station, the d
