hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.6.2 Multicast in a GPRS-based CN | The implementation of multicast in this case seems to be a different case. The main reason for this is the different business paradigm of the two networks, namely the current, best-effort Internet and the T-UMTS. In the former, there is intensive, time-based, signalling at the edges of the network, between the hosts an... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.7 Unidirectional link routing (UDLR) protocol | The UDLR protocol functionality becomes relevant in the case only a unidirectional link is used and, under the assumption of the Mobile IPv6-based CN. In this case, it is necessary to come up with a solution to the problems posed to the IGMP by the unidirectional nature of the satellite link. The IGMP, similar to the I... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.8 TCP and RTP/UDP flows transport | The TCP/IP suite provides applications mainly with two transport capabilities, expressed by Transport Control Protocol (TCP) and User Datagram Protocol (UDP). The former provides a reliable, byte-stream, connection-oriented service and is the workhorse protocol for the traditional (and most popular) Internet applicatio... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.8.1 TCP flows | The provision of asymmetric, TCP-based services is envisaged only in the bi-directional link, given the interactivity these services require. ETSI ETSI TR 101 865 V1.2.1 (2002-09) 105 |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.8.1.1 Issues | The problems TCP faces over satellite links have been a subject of research for quite some time, although it experienced a peak in the last 5-6 years. The propagation delay related to a GEO satellite and the wireless nature of the satellite link are the main factors of TCP performance degradation. The former reduces th... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.8.1.2 Countermeasures | A number of ways to attack these problems have been proposed. Maybe the most comprehensive summary of those is given in [44], which concluded the activities of TCPSAT group, a group established within IETF and dedicated to the study of the specific problems TCP faces in satellite environments. The majority of the solut... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.8.2 UDP flows | The efficient support of real-time, interactive services (e.g. VoIP) is not possible if the selected satellite constellation is a GEO based. The GEO satellite network introduces a latency of 250 ms, leading to a tolerable end-to-end delay, within the upper limit of 400 ms required by ETSI TIPHON WG specifications [47] ... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 8.9 IP QoS | Support of IP quality of service brings a number of issues that need to be investigated. Making the assumption that the core network will be based on an IP DiffServ solution - given its proven scalability compared to IntServ - careful considerations must be made with respect to how DiffServ or IntServ will be used in t... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 9 Standards and Regulatory Aspects | The ongoing ITU IMT-2000 regulatory work is discussed below. It should be noted that ITU-R created a special task group TG8/1 to select and evaluate candidate RTTs for both the terrestrial and satellite segments of IMT-2000. On completion of their work, TG8/1 was dissolved and future work relating to these, and any new... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 9.1 ITU-R Recommendations for IMT-2000 | Mobile systems are under responsibility of the Study Group 8 in the Radio-communication sector of the International Telecommunication Union (ITU-R). The Recommendations developed so far on IMT-2000 are (the complete list of recommendations on mobile can be found at: http://www.itu.int/itudoc/itu-r/rec/m/index.html: ETS... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 9.2 ITU-T Recommendations for IMT-2000 | A Special Study Group on « IMT-2000 and beyond » has been created during the World Telecommunication Standardization Assembly (WTSA-2000) held in Montreal, Quebec, Canada, from 27 September to 6 October 2000. This group has the primary responsibility within ITU-T for overall network aspects of IMT-2000 and beyond. This... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 9.3 ASMS Task Force | The ASMS-TF has a focus period of approximately 10 years consisting of a short term scenario of 1 to 4 years and a more long term scenario of 4 to 10 years. For the short term scenario it has been concluded that possible implementations must be based on existing technologies/architectures with minor modifications. It h... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.1 IST Project: VIRTUOUS | VIRTUOUS project aims at investigating the UMTS system in order to contribute to the standardization process for the satellite part while reducing the impact in introducing this new radio access segment. At the same time this project aims at defining a migration path from the second generation toward the third generati... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.2 ESA: ROBMOD and ATB | |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.2.1 Overview of the ROBMOD ESA project | The ESA ROBMOD project (Robust Modulation and Coding for Personal Communications Systems ) aims at defining and validating a candidate physical-layer approach for the satellite component of UMTS. ROBMOD saw the participation, under Space Engineering (I) prime-contractorship, of Ascom (CH), CoRiTel (I), IMST (D), Polite... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.2.2 Overview of the ATB ESA project | The ESA project "Advanced S-UMTS Test Bed" (ATB) represents the follow-on of ROBMOD (see ref. [1] for a description of the ESA early project), an activity which has resulted into the implementation of a comprehensive hardware Test Bed intended to validate the W-CDMA physical layer in a context faithfully representative... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.3 IST: SATIN | Project SATIN (Satellite over IP Network) is an in-depth research and technology project that will define and evaluate efficient S-UMTS access schemes based on packet-based protocols whilst allowing multicast service optimization. These access schemes will be based as much as possible on the UTRA access scheme to allow... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.4 IST: GAUSS | |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.4.1 Objectives | GAUSS is an RTD (Research and Technological Development) project founded by the European Community IST (Information Society Technologies) Programme. The GAUSS purpose is to analyse and demonstrate the potential integration ("Synergy") between navigation and communication services, by providing Galileo Navigation servic... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 10.4.2 Contribution to Standardization | Supporting the S-UMTS Standardization process and concertation with other relevant projects and researches is one of the main issues of the GAUSS project. As matter of fact, GAUSS is expected to give significantly contribution to some S-UMTS Standardization activities, in particular making recommendations and developin... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 11 Summary and Recommendations | |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 11.1 S-UMTS opportunities | Third-generation wireless networks will allow users to browse and download information from the Internet, receive pre- defined news and information bulletins containing full-motion video and even real-time broadcast, view and respond to video and audio e-mail, and access any of the information stored on their desktop P... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 11.2 Standardization objectives | Two parallel objectives have been identified: 1) An alignment of mobile satellite systems with terrestrial standards, especially with GSM 2+/GPRS and T-UMTS. This would apply to all areas of design but especially to mobile user equipment and ground networks. A key area is in development of interfaces between the satell... |
9c93b22846a27ede6d6f94031adc745f | 101 865 | 11.3 Recommendations for further work | With respect to S-UMTS standardization activities it is recommended to: 1) Start and/or continue the standardization of packet, broadcasting/multi-casting modes for S-UMTS. 2) Study the T-UMTS Iu interface compatibility with S-UMTS and define possible extension. 3) Maintain and extend the S-UMTS specifications accounti... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 1 Scope | The present document provides the results of studies into deployment of Multipoint-to-Multipoint systems. A range of issues has been considered, including co-existence with Point-to-Multipoint systems, capacity, spectral efficiency and coverage. Draft requirements for systems operating in various frequency bands have b... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] RAL CRABS Report D3P1B: "Line-of-sight propagation probabilities calculated from Rayleigh roof height distribution". [2] ITU-R Recommendation P.676-3: "Atmospheric attenuation". [3] ITU-R Recommendation P.840-2: "Rain attenuation". [4] ... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 3 Symbols and abbreviations | |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 3.1 Symbols | For the purposes of the present document, the following symbols apply: dB decibel dBm decibel relative to 1mW GHz Giga Hertz kbit/s kilobit per second ms millisecond ns nanosecond Mbit/s Megabit per second MHz Mega Hertz |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: BS Base Station BWA Broadband Wireless Access CCS Central Control Station CEPT European Conference of Postal and Telecommunications Administrations CRS Central Radio Station CS Central Station FDD Frequency Division Duplex FWA Fixed Wireless A... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 4 General characteristics | Broadband Wireless Access (BWA)systems have mostly used a P-MP architecture. Most ETSI standards for such systems assume a P-MP architecture. Developments have now made feasible alternative system architectures, in particular systems described as MP-MP, otherwise known as "Mesh" systems. In P-MP systems, core network t... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 4.1 MP-MP general system architecture | This clause describes how a typical MP-MP system can evolve from start-up through to high density deployment. It is possible to build a system with either directional or wide beam (even omni-directional) antennas but most advantage is obtained when narrow beam antennas are used throughout a system. With omni-directiona... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 4.1.1 Startup phase | Initially, there are no subscribers and there is no coverage. At least one point of connection has to be chosen to a core network and the first subscribers are then connected. A typical way to start is to deploy a small number of strategically sited "seed" node stations, which have line of sight to the first subscriber... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 4.1.2 Low density of subscribers | Once the initial startup phase has begun, it is not essential to deploy more "seed" node stations. Subsequent stations are either subscriber stations or points of connection to core networks. At low densities, the probability of interference between co-channel links is very low and much use can be made of time-domain t... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 4.1.3 High density of subscribers | As the system grows to accommodate more and more subscribers, the inter-node connections are adjusted accordingly. The mean link length decreases and the probability of co-channel interference slowly rises until a point is reached where an additional channel is needed to meet the total network capacity requirements. Th... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 4.2 Reference diagram | A reference diagram suitable for P-MP and MP-MP systems is shown in figure 2. CS TS Core Network TS TS TS TS RS TE TE RS TE TE TE TE TE TE F G to other CSs or CS TS Core Network TS TS TS TS RS TE TE RS TE TE TE TE TE TE F G to other CSs or Figure 2: Reference diagram for P-MP and MP-MP systems ETSI ETSI TR 101 939 V1.1... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5 Deployment issues | |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.1 Use as an access system | MP-MP systems can be used as access systems, in exactly the same way as P-MP systems. The system can be regarded as a "black box" which has interfaces to core networks and to end-users. The functionality of the "black box" is the same as that for a P-MP network, although the routing within the "black box" is different.... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.2 Coverage | Coverage in this context is defined as the probability that any new randomly placed subscriber requesting service within the operator's nominal service area can be successfully connected. For mass market deployment, it is likely that very high values must be achieved (>95 %). Most BWA systems operate in frequency bands... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.3 Spectrum Efficiency | Spectrum efficiency is an important factor in the choice of system architecture. A useful and meaningful measure of spectral efficiency is bit/s per MHz of spectrum per sq km of coverage. The spectrum efficiency of MP-MP networks can be very high and in many circumstances can be higher than that achieved by P-MP system... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.4 Backhaul links | Spectrum calculations from clause 5.3 are in most cases sufficient to include backhaul links to appropriate points of connection with core networks. In a P-MP system, the number of base stations is kept reasonably low and locations are chosen on the basis of good coverage. In a mesh network, traffic from core networks ... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.5 Use of TDD or FDD | Mesh systems can operate with TDD or FDD channel arrangements. A TDD system is usually simpler to implement. Channel plans, such as CEPT/REC T/R 13-02 [11] can easily be deployed, in either case. operating with FDD. The complete analysis of interference between mesh and P-MP systems requires use of a simulation tool. T... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.6 QoS issues | Different services have different requirements in terms of acceptable path delay, error-ratio performance and availability. Because MP-MP systems may use several radio hops to reach a particular end-user, there are constraints on design in order to achieve the necessary QoS requirements. As the network density rises, t... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.7 System capacity | The capacity of a mesh network is determined partly by the maximum bit rate on each link and partly by the arrangement of node stations in relation to the required traffic of each subscriber. A typical gross link capacity might be 100 Mbit/s, at which rate the spectral efficiencies and node densities shown in figure 4 ... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 5.8 Applicability of existing TM4 specifications | TM4 specifications for BWA systems cover equipment parameters but do not specify the details of deployment. Such specifications, including EN 301 213-1 [5] and EN 301 213-3 [6], generally assume a P-MP architecture. The reference diagram allows for base stations, terminal stations and repeaters but the exact deployment... |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 6 Co-ordination aspects | |
db6033b2534cad5a38bdc5b919292502 | 101 939 | 6.1 Co-existence between MP-MP and P-MP systems | This topic is discussed in more detail in annex C. A summary is given here. The introduction of Fixed Wireless Access services in Europe, including the 24,5 GHz to 29,5 GHz band has led to a number of studies into co-existence of various types of system. System architectures and design parameters vary considerably in d... |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 1 Scope | The purpose of the present document is to assist the Public Network Operators and Public Service Providers sharing the Telecommunications physical support with Broadcast systems based on cable technologies in producing publications that describe their public interfaces in accordance with article 4.2 of the Radio Equipm... |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 3 Definitions and abbreviations | |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Cable Modem Termination System (CMTS): located at the cable television system headend or distribution hub, which provides complementary functionality to the cable modems to enable data connectivity to wide-area network services Cable M... |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: BER Bit Error Rate CM Cable Modem CMTS CM Termination System CPE Customer Premises Equipment (equivalent to TTE) EMC ElectroMagnetic Compatibility (regulated by EU Directive 89/336/EC) EU European Union IEC International Electrotechnical Commi... |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 4 Guidance for publication | The following clauses gives guidance on the content and the format of the publication of access interfaces with public telecommunication networks, including where applicable, Supplementary Services. |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 4.1 Intellectual Property Rights (IPR) and Copyright | As part of the access interface publication, the PNO should make users and manufacturers aware of the potential for IPR rights in the implementation of the interface. However, it is the sole responsibility of the individual manufacturer to ensure that IPR issues are cleared. In so far as the publisher is aware of the s... |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 4.2 Content of access interface publications | Annex A contains an example that may be used in the specification of the access interface. The presentation style of annex A is provided for illustrative purposes only. The publication should contain sufficient information to enable manufacturers to design terminal equipment to inter-work with and to use all services o... |
bf079acabbaee2f9e1a4be0e0aeedeca | 101 857 | 5 Applicability of parameters to interface types | Annex B contains an extract from a report presented to TCAM in July 1999 by the European Commission. The present document was used by the EU Commission in deriving guidance documents on interface publication, [4], [5]. From annex B the following can be deduced: 1) For interfaces based on the Open Systems Interconnectio... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 1 Scope | The present document outlines and defines the functional requirements for an interoperable broadband fixed wireless access system operating at radio frequencies between 2 GHz and 11 GHz. The air interface will be optimized for PMP configurations, but may allow for flexible mesh deployments. It aims to establish whether... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI TR 101 177 V1.1.1 (1998): "Broadband Radio Networks (BRAN); Requirements and architectures for broadband fixed radio access networks (HIPERACCESS)". NOTE: TR 101 177 has served as a base line and platform for the present document. [... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 3 Definitions and abbreviations | |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: local access: short range (< 100 m) wireless access to other, possibly wired, networks This term is used in the telecommunications sense. remote access: long range (< 10 km) wireless access to other, possibly wired, networks Remote acc... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Assured Forwarding AirI Air Interface AP Access Point APC Access Point Controller APT Access Point Transceiver AT Access Terminal ATM Asynchronous Transfer Mode BER Bit Error Ratio BFWA Broadband Fixed Wireless Access BRAN Broadband Radio A... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4 Overview | This overview addresses the rationale for developing a separate standard for interoperable broadband fixed wireless access systems to operate at frequencies below 11 GHz. Although the scope of the current HIPERACCESS work item is not radio frequency specific, that work so far has addressed frequencies considerably high... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.1 Target markets | Broadband fixed wireless access systems based on HIPERMAN are intended to compete with, and complement other broadband wired access systems, such as xDSL and cable modems. In this context "broadband" means peak rate "above 2 Mbit/s" to provide such services as data, voice and video. The target markets to be addressed a... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.2 Application and Services | Broadband fixed wireless access (BFWA) networks should support a wide range of applications in use today and be extendable to support future services. The main user applications that can be foreseen today are as follows: • Internet access; • LAN bridging and Remote LAN access; • video-telephony and video conferencing; ... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.3 Features | The main features for HIPERMAN networks should be: • User installable terminals. Truck-rolls to engineer SU installation pose an undue burden on service initialization. NLOS operation capability, which eases antenna installation, in combination with turnkey SU solutions, enables user installable terminals, which signif... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.4 Topologies and deployment Scenarios | This clause presents a high level description of a system model to be used as a framework for standards development. The system shall support PMP topology and may support mesh topology. In PMP systems, all data traffic shall go through the base station that shall serve as a radio resource supervisor. In mesh systems al... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.4.1 Large Scale Deployments | To enable large-scale deployments efficiently, PHY and DLC protocols should permit good frequency reuse factors, providing at least 25 Mbit/s/sector. In order to reduce the interference level, the PHY and DLC protocols shall permit power control per subscriber up-link and should permit power control per subscriber down... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.5 System Reference Model | This clause presents the system reference model to be used as a framework for developing a standard for HIPERMAN. The model describes the main functionalities of the system, and the terminology to be used by the ETSI/BRAN working group in the creation of the standard. The following is a BFWA system reference model. ETS... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.5.1 Interoperability | Protocols are the heart of the HIPERMAN standard that ought to provision interoperability of multiple vendors' equipment. Interoperability between HIPERMAN systems shall occur at the Air Interface (AirI). |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.6 Spectrum Considerations | |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.6.1 Targeted Spectrum | The standard shall be optimized for radio systems in the frequency band 3,4 GHz to 4,2 GHz, but may be applicable to the range from 2 GHz to 11 GHz. (Bands around 2 GHz have been allocated for use by UMTS and will therefore not be available for use by FWA). [4] identifies "at present a single common harmonized frequenc... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.6.2 Duplex Mode | The standard shall support systems based on FDD, or TDD, or FDD and TDD efficiently In FDD mode, the base station shall support full-duplex FDD, while the SU should be able to operate in half-duplex FDD to reduce equipment cost. In TDD mode the system should support dynamic variable duration for the Up-link and the Dow... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.6.3 Channelization | HIPERMAN standards shall adhere to channel plans described in [9] and [8] for 3 400 MHz - 3 600 MHz and 3 600 MHz - 4 200 MHz bands respectively. However, sufficient flexibility must be provided to allow operation in regions where these recommendations are not followed and in other frequency bands below 11 GHz. Recomme... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 4.6.4 Co-existence considerations | ETSI TM4 has developed a number of standards for different access methods for fixed systems for these bands. Several European nations have awarded or are expected to award licences allowing operation of Fixed Wireless Access services in these preferred bands, and many of these services are in operation. Equipment used ... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 5 Services | This clause contains services, which pose requirements on the PHY and DLC layers. The QoS parameters supporting the described services are provided in clause 7.2.3. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 5.1 Internet Protocol Services | The system must be optimized to transport variable length IP datagrams. Both IP versions 4 and 6 must be supported. For efficient transport of IPv6, TCP/IP header compression over the air interface should be supported. It should be possible to support the emerging IP-QoS efforts (e.g. MPLS, Diffserv, RSVP). |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 5.2 Bridged LAN services and Remote LAN access | The protocols should support bridged LAN service and Remote LAN access capabilities. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 5.3 Voice services | The system shall support voice communications. The voice access transport shall be packet based. The system must support the QoS requirements of these services. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 5.4 Other Services | The system shall facilitate unicast, multicast, as well as broadcast services. ETSI ETSI TR 101 856 V1.1.1 (2001-03) 16 |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 6 External interfaces, and network management | |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 6.1 Network Management | The standard shall define a network management interface based on existing open standard protocols (for example SNMP), which enables the following management aspects: • Fault and Performance management The protocols must enable fault and performance monitoring, as well as provide means for local and remote testing. The... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 6.2 External Interfaces | |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 6.2.1 User Network Interface (UNI) | A single SU may comprise several UNIs. The DLC convergence layer at the SU shall support IP. It may support other interfaces, e.g. Ethernet, USB, and POTS. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 6.2.2 Service Node Interface (SNI) | The BS may comprise several SNIs. The DLC convergence layer at the BS shall be packet-based. It may be IP over Ethernet, Gigabit Ethernet, PPP, FDDI (ISO 8802-5) etc. ETSI ETSI TR 101 856 V1.1.1 (2001-03) 17 |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7 Transport requirements | Priority information given to the convergence layer shall be used for the QoS mechanism. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.1 Service independence | A HIPERMAN system shall provide services without requiring information on the type of application. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.2 Service Support | |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.2.1 Quality of Service | The system shall support QoS guarantees to provide the services that shall be transported. Thus, the protocol standards shall define interfaces and procedures that accommodate the requirements of the services with respect to allocation of prioritization of radio resources. The system shall support different classes for... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.2.2 Service Classes | Three classes of service are recognized as per IETF recommendations, which shall be supported: • Expedited Forwarding (EF): This class of service can have a varying bandwidth requirement over time, but tolerance of delay and jitter are limited (example: VoIP). • Assured Forwarding (AF): Within this class of service, th... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.2.3 Service QoS Mappings | The basic mechanism available within the systems for supporting QoS/service class requirements shall be able to allocate various bandwidths to various services. The protocols shall include a mechanism that can support dynamically variable bandwidth channels and paths (such as those defined for IP environments). Since c... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.3 Channel Conditions | Due to the multipath inherent in the targeted frequency bands, the system should be capable of handling several µs of delay spread with limited performance degradation. To accommodate changes in the channel characteristics, the PHY and DLC protocols shall specify functions and procedures to adjust parameters such as tr... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.4 Flexible Asymmetry | Over a short period of time (e.g. a few seconds) the traffic generated by and for any given user can be highly asymmetric in either way. The system shall efficiently support this type of asymmetric traffic. Over longer periods of time, a given user can need on average more bandwidth in one way than in the reverse way. ... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.5 Throughput requirements | |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.5.1 Target Throughput | To be competitive with wired solutions, it is desirable for the system to support a data rate at the APT of 25 Mbit/s, which is the instantaneous aggregated bit rate (up- plus downstream) between the PHY and the DLC layer, and shall be shared among the users or shall be capable of being allocated to one user. The syste... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.5.2 Expected throughput with current spectrum assignments | Achievable peak data rates depend on spectrum assignments, and hence cannot easily be specified. Instead, the systems shall use different modulation and/or coding options for different links to increase the overall system throughput. Thus, subscribers with weak signals will maintain an acceptable radio link quality thr... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.5.3 Spectrum requirements to meet target throughput | In order to achieve a continuous large-scale roll out without compromising data rate, the operator needs to have 9 channels in the cell plan. 64 QAM is foreseen as the highest modulation complexity feasible for HIPERMAN. Therefore a bandwidth of at least 10 MHz (note) is required to assure a net bit rate of 25 Mbit/s. ... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.6 Radio Link Availability | HIPERMAN based systems should support an availability of at least 99,9 % for the ranges as shown in Table 3. Rain effects may further deteriorate these numbers depending on the targeted spectrum. The system shall permit radio links to be engineered for different link availabilities, based on the preference of the syste... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.7 Scalability | The protocols should allow for different capacities and performance for the system instances. The system should support features to maximize the scalability of a deployment. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.8 Radio specific security requirements | The system shall provide secure means of authentication, authorization and adequate means of encryption to ensure privacy. |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.8.1 Authentication | There are two levels of authentication for the system. The first level of authentication is when the subscriber unit authenticates itself to the access network. This initial authentication shall be strong in order to prevent "enemy" subscriber unit from entering the network or an "enemy" base station from emulating a r... |
01fd32af3b06c1a479ed7241eb93d694 | 101 856 | 7.8.2 Authorization | Authorization is a security process that determines which services an authenticated user is permitted to invoke. Each user has a set of credentials that describe what the user is "allowed" to do. The standard shall identify a standard set of credentials and allow for vendors to extend the defined credentials with non-s... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.