hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 8.1 Capabilities and grades of NIU | Different tools and capabilities are provided by DVB-C (ETS 300 800 [1]). These tools do not need to be all implemented in the NIUs of the network. Depending on the services and the cost related to both INAs and NIUs, the operator/manufacturer may choose which option is best suited for its purposes/markets. The following subclauses describe the different tools and the grades provided by the present document along with the explanation of the advantages and disadvantages offered by each tool/grade. a) Out-Of-Band (OOB) / In-Band (IB) principle ETS 300 800 [1] is based either on OOB or IB downstream signalling. However, STBs do not need to support both systems. In the case of OOB signalling, a FIP is added. This path is reserved for interactivity data and control information only. The presence of this added FIP is in that case mandatory. However, it is also possible to send higher bit rate downstream information through a DVB-C channel whose frequency is indicated in the FIP. The main advantage of the OOB solution is the possibility to dissociate broadcasting and interactive data on two separate channels, which offers the flexibility to the user to watch any program on TV while doing interactive processing independently (superimposed image, separate PC connected to the STB, telephony, etc.). In the case of IB signalling, the FIP is embedded into the MPEG2-TS of a DVB-C channel. It is not mandatory to include the FIP in all DVB-C channels. The main advantage of the IB solution is to provide interactive data in the same channel as the broadcasting channel, thus providing a better link between the interactive session and the related broadcast program. Both systems can provide the same quality of service. Yet, the overall system architecture will differ between networks using IB STBs and OOB STBs. Both types of systems may exist on the same networks under the condition that different frequencies are used for each system. The main differences are the following: For the STB: In the case of OOB signalling, a second tuner is needed and additional demodulation functions shall be included in the NIU. In the case of IB signalling, a MAC extracting function from the MPEG2-TS flow shall be included in the NIU. For the INA: In the case of IB signalling, a MAC unit needs to be inserted between the MPEG2 multiplexers and the QAM modulators in order to add the MAC signalling into the MPEG2-TS flow. In the case of OOB signalling, a QPSK modulator is part of the INA. b) Rate downstream and upstream There are two rates provided for OOB downstream transmission corresponding to grade A of 1,544 Mbit/s and grade B of 3,088 Mbit/s. In the case of IB downstream signalling (see EN 300 429 [2]). There are three rates provided for upstream transmission corresponding to grade A of 256 kbit/s, grade B of 1,544 Mbit/s and grade C of 3,088 Mbit/s. All combinations of the above grades upstream and downstream are allowed, but NIUs do not need to support all grades. NIUs shall support at least one grade upstream and downstream. Grade A may be needed upstream for HFC networks with severe ingress noise, since it requires 200 kHz bandwidth only. The choice between 1,544 Mbit/s and 3,088 Mbit/s upstream or downstream is left to the manufacturer/operator. TR 101 196 V1.1.1 (1997-12) 22 c) Number of simultaneous ATM virtual connections per NIU For each connection provided by higher layers on the INA side (VPI/VCI), a connection ID is associated at the MAC layer. The maximum number of simultaneous connections that a NIU should support is defined as follows: - Grade A: Only one connection at a time can be handled by a NIU. In that case, all connections shall be managed at higher medium layers, and should all use the same VPI/VCI value identified as default connection in the present document; - Grade B: As many connections as needed, defined dynamically by the INA, following higher medium layers requests. NOTE: Grade A can offer the same quality of service than grade B, assuming connections are managed at the application layer, but requires less hardware in the NIU for queuing ATM cells before transmission. |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 8.2 Upstream frequencies dynamic allocation | The allocation of upstream frequencies is managed by the INA. This means that the INA can use any measurement tool to figure out which frequency is better to use at any time and can decide to switch all users present on a given frequency at any time if this frequency is too jammed for a correct reception. MAC messages are provided for this purpose. However, the present document does not indicate how the level of interference should be measured, and what level of interference requires switching. This is left up to the manufacturer, since it does not affect interoperability. |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 8.3 Initialization and set-up | Initialization and set-up comprises two major functions. The first one is the connection to the network, the second one is the identification of the grade required. Obviously, if the connection is not made, the second function is not possible. The following algorithm summarizes what the first steps of a NIU connection are. Lock up to the downstream control path (OOB or IB). If the operator wants to be as flexible as possible, both grades in the downstream OOB should be offered, in which case the NIU should first try to lock to its own fastest grade. Both IB and OOB can eventually be provided by the operator at the same time, in which case the NIU should refer to its own configuration to know which should be looked at first. However, the simplest solution is to impose a grade on all NIUs connected to the network such that only one type of modulators is used at the INA premises. The downstream control information then contains further instructions on the grade to use downstream (MAC provisioning channel message). In the case where it is different from what the NIU selected by default, the NIU should change to the new frequency/grade and lock up to the new downstream frequency. On this frequency, further instructions are given on the upstream grade to use (MAC default configuration message). The NIU shall then wait for the MAC Sign-On message from the INA before it tries to connect to the network. The INA will then go through the connection process one user at a time by sending a singlecast Ranging and Power Calibration message to the first NIU detected. This is absolutely necessary to avoid dead lock situations. Once the NIU has gone through the whole sign-on and calibration procedure, it receives a default connection from the INA, and thus becomes a separate ATM node. The INA manages all bandwidth assignments, so it always controls the traffic on the network. |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 9 Connections management | The goal of the MAC protocol is to provide tools for higher medium layer protocols in order to transmit and receive data transparently and independently of the physical layer. Higher medium layer services are provided by the INA to the STU. The INA is thus responsible of indicating the transmission mode and rate to the NIU for each type of service. Specifically, for each connection provided by higher layers on the INA side (VPI/VCI), a connection ID is associated at the MAC layer (see subclause 8.1 (c) for more details). However, bandwidth (time slots) does not need to be assigned immediately by the INA for a given connection. This means that a connection ID may exist at the NIU side without associated slot numbers. TR 101 196 V1.1.1 (1997-12) 23 The INA is responsible of providing transmission bandwidth to the NIUs when needed by higher layers. However, since the NIU shall transmit all data from the STU, the NIU is also responsible for requesting for more bandwidth if not already provided by the INA. A default connection is initiated by the INA when STBs are first turned on. This connection can be used to send data from higher layers leading to further interactive connections. This connection can be associated to a zero transmission rate (no initial bandwidth allocation). |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 9.1 Connection protocol and bandwidth assignment | In the ATM world, connections are virtual, that is, they specify a node to node path without necessarily assigning bandwidth. Specifically, for the HFC RC, the concept is the same. When a user is connected, it means that it has received a default connection between the INA and the NIU. Further connections can then be requested using that particular connection and bandwidth can be requested following specific access modes. Different access modes are provided to the NIUs within access regions specified by information contained in the slot boundary fields of the downstream superframes. The limits between access regions allow users to know when to send data on contention without risks of collision with contention-less type data. The following rules define how to select access modes: Data connections: When the INA assigns a connection ID to the NIU, it either specifies a slot list to be used (fixed rate access) or the NIU shall use contention or reserved access by following this algorithm: - When the NIU shall send more cells than what was assigned by the INA, it can use contention access only if the number of cells to transmit is less than Maximum_contention_access_message_length (specified in the MAC Connect message from the INA). In that case, it shall wait for the slot reception indicator before it is allowed to send other cells with the same VPI/VCI value. The NIU can send one request for reservation access if the number of cells is less than Maximum_reservation_access_message_length (specified in the MAC Connect message from the INA). If more cells shall be transmitted, the NIU shall send multiple requests for reservation access. MAC messages: - MAC messages can be sent on contention access or reservation access. MAC messages sent upstream shall be less than 40-byte long. If the MAC information exceeds 40 bytes, it shall be segmented into multiple 40 bytes independent MAC messages. Ranging access can only be used for specific MAC messages. a) Contention access Contention access indicates that data (MAC or bursty data traffic) is sent in the slots assigned to the contention access region in the UC. It can be used either to send MAC messages or data. The VPI, VCI of the ATM cells are then used to determine the type and direction of the data in higher layers. Contention based access provides instant channel allocation for the NIU. The contention based technique is used for multiple subscribers that will have equal access to the signalling channel. It is probable that simultaneous transmissions will occur. For each ATM cell transmitted by the NIU, a positive acknowledgement is sent back by the INA, utilizing the reception indicator field, for each successfully received ATM cell. In contention based access mode, a positive acknowledgement indicates that a collision did not occur. A collision occurs if two or more NIUs attempt ATM cell transmission during the same slot. A collision will be assumed if a NIU does not receive a positive acknowledgement. If a collision occurs, then the NIU will retransmit using a procedure to be defined. b) Ranging access Ranging access indicates that the data is sent in a slot preceded and followed by slots not used by other users. These slots allow users to adjust their clock depending on their distance to the INA such that their slots fall within the correct allocated time. They are either contention based when the ranging control slot indicator b0 received during the previous superframe was 1 (or when b1 to b6 = 55 to 63), or reserved if the INA indicates to the NIU that a specific slot is reserved for ranging. TR 101 196 V1.1.1 (1997-12) 24 c) Fixed rate access NOTE: Fixed rate is called contention-less in DAVIC. Fixed rate access indicates that data is sent in slots assigned to the fixed rate based access region in the UC. These slots are uniquely assigned to a connection by the INA. No fixed rate access can be initiated by the NIU. d) Reservation access Reservation access implies that data is sent in the slots assigned to the reservation region in the UC. These slots are uniquely assigned on a frame by frame basis to a connection by the INA. This assignment is made at the request of the NIU for a given connection. |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 9.2 Interface between MAC and medium higher layers (ATM) | When a NIU is first turned on, it is not identified as a single ATM node, since no connection is possible without ranging and sign-on. The set of all users is thus seen as one single node at the ATM layer. The connection used to transmit MAC messages between the INA and the NIU is the same for all users, since it is viewed by the INA as one node. The MAC address used in the MAC messages thus identifies each user at the MAC layer, but not at the ATM layer. However, once the NIU is calibrated, it receives a first default connection from the INA which then identifies the user as a specific node at the ATM layer. From then on, the MAC layer becomes transparent to the ATM layer and messages can be sent from an ATM server to each user on the network as if they were separate ATM nodes. NOTE: The default connection is not necessarily associated to a specific bandwidth, since bandwidth can be requested on demand. |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 9.3 Disconnection protocol | Different types of disconnection may occur. The following list describes each event and how the system shall be designed to recover from it. 1) Soft disconnection by NIU: This disconnection happens when the user makes a request to turn its STB off. In that case, each connection shall be turned off by the INA after a request from the user to the server at higher layers. 2) Hard disconnection by NIU (Power outage, plug fall, etc.): This disconnection happens by accident. In that case, the idle message which is supposed to be sent by each NIU periodically (around every 10 minutes) is not received by the INA. The INA then knows that the NIU is disconnected and considers all connections to be down. In the case where the STB recovers before these 10 minutes, it will try to start ranging again. If the INA receives requests for ranging from a NIU, it automatically considers the NIU as previously disconnected and considers all previous connections terminated. 3) Soft disconnection by INA: If the INA needs to receive maintenance, it first needs to stop all connections with each NIU. 4) Hard disconnection by INA: This could happen in case of a major alarm on the INA side. If the downstream stops, automatically all NIUs will reset since they do not receive control from the INA anymore. If the upstream burst demodulator stops, then the INA will send a soft disconnection or move the users to another frequency through the downstream control path. If the INA controller stops, then the NIUs will reset after a specific timeout at the higher layers. |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 10 Simulation of error performance and error handling | |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 10.1 Error performance of the physical layer | This subclause describes the robustness of the physical layer of the DVB-RCC upstream signal. The return paths of current CATV networks are multi-point-to-point connections. Therefore a lot of unwanted signals disturb the upstream signal. The physical parameters of these signals can vary considerably. The combination of all of these disturbing signals is called ingress noise. The properties of the return paths are indicated by Signal-to-Noise power Ratios (SNRs). TR 101 196 V1.1.1 (1997-12) 25 To obtain such SNRs, both the signal power and the power of the ingress noise are calculated at the input of the INA. These calculations are based on the transmit power levels which are recommended by the DVB-RCC (ETS 300 800 [1]) as well as being derived by measurement results. The resulting SNRs correspond to particular slot-loss rates. The correlation between both was obtained by computer simulations. Signal power The transmit power level of the STBs is given in ETS 300 800 [1]. The output level range is 85 - 122 dBµV (RMS). Since the upper boundary of 122 dBµV is very high for consumer STBs, the transmit power level of every individual STB should be reduced to the lowest possible value. However, for reasons of EMC, the value of 122 dBµV shall not be exceeded. The upstream signals are attenuated by passive elements like cables and power splitters. The range of the transmission loss in existing cable networks depends of their size. It is between 2 065 dB and 65 dB. The combination of transmit power level and transmission loss results in an area of possible input levels at INA (see figure 17). -89 20 30 40 50 60 -10 -20 -30 -40 -50 -60 -70 -80 -90 -44 -7 -52 input power at INA/[dBm] transmission loss/[dB] min. max. 0 max. transmit power min. transmit power Figure 17: Possible power range at INA of the upstream signal In large cable networks, in which, for example, the transmission loss covers the hole range of 45 dB (between 20 dB and 65 dB), the local head-end unit controls the STBs which are far away from the local head-end, so as to transmit at the maximum signal level. The received input power at INA is -52 dBm. If another STB which is very close to the local head-end (assumed transmission loss is minimal) transmits in the same return path as the first one, its level will be reduced by the control unit to obtain a constant input power. But the power level of the second STB cannot be reduced to below -44 dBm. Since the range of the transmission loss is greater than the control range of the STBs (as defined in the present document), the received power levels could differ by up to 8 dB. This discrepancy can be resolved by creating different network clusters. STBs which are not located in the same geographical area should not transmit in the same UC. Noise power Measurements of ingress noise were carried out at different local head-ends of different real cable networks. Since the physical parameters of ingress noise (bandwidth, amplitude density, etc.) varies from case to case, the results are given as statistical mean values of all channels. The measured ingress noise power N does not exceed these values during some percentage of time. Therefore the corresponding SNRs are guaranteed during the same percentage of time. Measurements show that some frequency ranges (e.g. 27 MHz) are very poor for upstream transmission. The network operator has the option to skip the worst channels and not to use them. When choosing 80 % of the whole upstream frequency range, the network operator is able to increase the statistical SNR performance by up to 3 dB. Table 2 shows an example of such measurement results. The filter used during the measurements had an equivalent noise bandwidth of 1 MHz. TR 101 196 V1.1.1 (1997-12) 26 Table 2: Statistical evaluation of measured power levels of ingress noise at INA % of time < 97 < 99 < 99,7 < 99,9 < 99,97 N / [dBm] -64,3 -56,5 -50 -45,4 -41,7 System behaviour Simulation results of the upstream signal show that a SNR of about 12 dB is sufficient for the recommended slot-loss rate of 10-6. This means that if an SNR of 12 dB occurs at a given percentage of time, the recommended slot-loss rate will be guaranteed during this time. During the remaining time the slot-loss rate increases. However, if the SNR decreases to 11 dB, the slot-loss rate will be increased to about 10-4. Figure 18 shows an example of the system behaviour when using an upstream data rate of 1,544 Mbit/s. The system quality is expressed in probability of time at which the recommended slot-loss rate is less than 10-6. All STBs which are located at the end of the network (high transmission loss) are controlled by the local head-end, so as to transmit at maximum power level. In this example their signals will produce the adequate SNR of 12 dB at 97 % of the time. The probability increases when the transmission loss decreases. If the transmission loss is lower than 42 dB the transmit power levels of the corresponding STBs should be reduced. The recommended slot-loss rate of 10-6 will be reached with a probability of more than 99,97 % of the time. The optimal transmit power-level curve is also given in this figure. The overall performance of the system, including all STBs which are connected to the network, depends on different parameters, which are: the mode of the used data rate (the performance of the system is better when using the mode in which 256 kbit/s are transmitted, but it is slightly worse using the 3,088 Mbit/s mode), the amounts of STBs and their individual transmission losses to the local head-end as well the quality of the cable network and, as a result of this, the effective ingress noise power. -89 20 30 40 50 60 -10 -20 -30 -40 -50 -60 -70 -80 -90 -7 -52 99.97 99.9 99.7 99 97 input power at INA/[dBm] probability of slot-loss rate less than 10-6 [% of time] transmission loss/[dB] min. max. 0 system reserve slot-loss rate higher than 10 max. transmit power min. transmit power -44 -6 optimal transmit power Figure 18: Possible power range at INA of the upstream signal TR 101 196 V1.1.1 (1997-12) 27 |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 10.2 Traffic | Whereas traffic is difficult to estimate without knowing the user behaviour as a function of the services offered, it is important to note that traffic is entirely managed by the INA and different parameters are available to modify the amount of requests sent by users on contention or reservation. This provides a very useful tool to optimize the throughput over time depending on the traffic or number of users connected on the available bandwidth. These parameters are the following: - access modes repartition using the slot boundary fields of the control path; - ranging slot control using the slot boundary fields of the control path; - reservation control using the slot boundary fields of the control path; - access mode as a function of the size of queues indicated in the MAC Connect messages. The algorithms used to optimize the traffic are left up to the manufacturers, since they do not affect interoperability. |
cd40c3e2f3776f330b4d764b60472458 | 101 196 | 10.3 Error handling | Error handling is required at the different layers depending on the location of transmission errors. If errors occur during data transmission, higher layers such as Transmission Control Protocol (TCP) in the case of Internet Protocol (IP) packets transmission will request for retransmission. In that case, no error handling procedure is necessary at the physical or MAC layer, more exactly, error handling procedure shall not be implemented at the MAC layer, since it may lead to dead lock situations where the higher layer and the MAC layer both request for retransmission at the same time. In the case of errors at the MAC layer, the situation is different. If a message that needs acknowledgement is incorrectly received, the acknowledgement will not happen and the message will have to be retransmitted. If the acknowledgement itself is not received, the INA will act as if the acknowledgement was not sent and will therefore reinitiate the whole MAC procedure. In the case of collisions between packets coming from different users, the same applies. If a MAC message is sent and a collision occurs, then the MAC message shall be sent again. If a data message is sent on contention and a collision occurs, then no retransmission of that packet should be undertaken, or a dead lock situation may occur. TR 101 196 V1.1.1 (1997-12) 28 History Document history V1.1.1 December 1997 Publication ISBN 2-7437-1827-7 Dépôt légal : Décembre 1997 |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 1 Scope | The present document describes and establishes simplified models of the different sections of the ground distribution network constituting the DC/I and the DC/C electrical power systems. These models are interworked to identify the common impedance where DC power supply currents can circulate (interconnection between DC/C and DC/I, DC/C and DC/C, DC/I and DC/I). These results allow the establishment of some basic engineering advice that should be applied to guarantee the good behaviour when interconnecting two systems. These precautions are given for functionality reasons: • the noise immunity of the pre-existing system and of the links between the system and the MDF should be conserved; and safety aspects: • the screens of signal cables between the pre-existing system and the Main Distribution Frame (MDF), the conductors and the connections of the pre-existing system have to withstand additional currents. |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 2 References | |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 2.1 Normative references | Normative references are not applicable in the present document. |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. 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 EN 300 253 "Environmental Engineering (EE); Earthing and bonding of ICT equipment powered by -48 VDC in telecom and data centres". |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 3 Definition of terms, symbols and abbreviations | |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 3.1 Terms | For the purposes of the present document, the following terms apply: DC power return conductor: name given to the 0V power supply conductor NOTE: It is also called "battery return". DC/C system: system where the DC power return conductors are connected to the Common Bonding Network (CBN), ensuring simultaneously the supply and protection functions NOTE: The DC/C system is also called a "2 wire system". ETSI ETSI TR 101 147 V1.2.1 (2025-02) 6 DC/I system: system where the current return function and the grounding of the equipment are separated NOTE: The DC/I system is also called a "3 wire system". |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: AC Alternating Current B1 Power source and the entry point of the system B2 The entry-point of the system room and the system C1 DC return conductors and CBN at MET C2 DC return conductors and CBN at power source level C3 DC return conductors and CBN at the SRPP of the system C4 DC return conductors and CBN in the system (SYST) D1 AC Mains Protective Conductor to the Power Plant G1 Power Plant to Main Earthing Terminal G2 Main Distribution Frame to the Main Earthing Terminal G3 Room Grounding Terminal to Main Earthing Terminal G4 Room Ground Terminal to SRPP G5 System to SRPP G6 Between 2 points of the system RB1 equivalent impedance is called RB 1 RB2 Equivalent impedance is called RB 2 RC1 Equivalent impedance is called RC 1 RC2 Equivalent impedance is called RC 2 RC3 Equivalent impedance is called RC 3 RC4 Equivalent impedance is called RC 4 RD 1 The equivalent impedance is called RD 1 RE For simplification reasons, the impedances RC 1, RC 2 and RG 1 (PWP grounds) have been replaced by the equivalent impedance RE 1 RG1 Equivalent impedance is called RG 1 RG2 Equivalent impedance is called RG 2 RG3 Equivalent impedance is called RG 3 RG4 Equivalent impedance is called RG 4 RG5 Equivalent impedance is called RG 5 RG6 Equivalent impedance is called RG 6 RS equivalent impedance is called RS S Between the System and |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CBN Common Bonding Network DC/C Direct Current/Common DC/I Direct Current/Isolated MDF Main Distribution Frame MET Mains Earthing Terminal PWP PoWer Plant. RGT Room Grounding Terminal. SRPP System Reference Potential Plane SYST System ETSI ETSI TR 101 147 V1.2.1 (2025-02) 7 |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4 Description of the DC/C and DC/I systems | |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.1 Global view of the systems | In this study, the DC power supply current is supplied by a power plant whose positive polarity (0 V) is connected to the CBN. This is generally the case for telecom buildings. The two systems (DC/C and DC/I) are made up of the following elements: 1) the PoWer Plant (PWP) installed outside the system; 2) the Grounding network System Reference Potential Plane (SRPP) integrating the system and which constitutes its reference plane; 3) the Telecom system (SYST) itself constituted by its items: racks, subracks, boxes, etc.; 4) the Main Distribution Frame (MDF) of the subscriber line and transmission circuit connection. MDF PW P RGT Screen of cable SRPP MDF MET SYST Load Figure 1: Entities constituting a DC/I system MDF PW P RGT MET Screen of cable SRPP MDF SYST Load Figure 2: Entities constituting a DC/C system |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.2 Identification of the connections | The paths which form the CBN are identified in figure 3. They have been divided in 4 groups: ETSI ETSI TR 101 147 V1.2.1 (2025-02) 8 1) The ground connections:[G]: ensure the equipotentiality and the earthing of the equipment for safety and functional reason. 2) The DC power conductors:[B]: are represented by the DC power return conductors. 3) The connection point of DC Power return conductor to the CBN:[C]: (according to clause 6.1 of ETSI EN 300 253 [i.1]). NOTE: Not all connections shown in the figures may be present. 4) The signal conductors:[S]: are cables and screens between the system and MDF. 5) A.C mains protective conductor: Refer to Annex C of ETSI EN 300 253 [i.1]. NOTE: In the installation, other possible paths exist, created by cable trays, building steel etc., but are not taken into account because their impedances are neither perfectly controlled nor guaranteed over time. It would be difficult or even uncertain to assess their contribution to the circulation of current. Figure 3: Power supply and ground connections in a system |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.3 Definition of the connections | |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.3.1 Ground connections (G connections) | G1: Power Plant to Main Earthing Terminal: (The equivalent impedance is called RG 1) • Represents the link from the power source and the MET. It is constituted: - either directly by a single conductor; or - by means of a ring conductor set up in the PWP room. ETSI ETSI TR 101 147 V1.2.1 (2025-02) 9 G2: Main Distribution Frame to the Main Earthing Terminal: (The equivalent impedance is called RG 2) • Represents the link between the metallic frame constituting the MDF and the MET. It is composed of: - either directly by only one conductor; or - by means of a ring conductor set up at the MDF room. G3: Room Grounding Terminal to Main Earthing Terminal: (The equivalent impedance is called RG 3) • Link between the ground interface Room Grounding Terminal (RGT) of the system room and the MET. It is made up of: - either directly by a single conductor; or - by the intermediary of the CBN and reinforcement conductors. NOTE 1: For small installations, RGT and MET can be merged. In this case: RG 3= 0. G4: Room Ground Terminal to SRPP: (The equivalent impedance is called RG 4) • Represents the proper impedance of the bonding network on which the system is installed. This impedance includes the system room ring conductor. G5: System to SRPP: (The equivalent impedance is called RG 5) • Represents the connection of an element or group of elements of a system to the room bonding network. G6: Between 2 points of the system: (The equivalent impedance is called RG 6) • Represents the ground impedance of the system. This is the impedance between the connecting point of the DC return conductor to the frame and the connecting point of the frame to the SRPP. NOTE 2: The value of this impedance depends both on the density of the bonding of the metallic parts and on the internal reference planes of the systems. |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.3.2 DC Power supply return links (B connection) | B1: Power source and the entry point of the system: (The equivalent impedance is called RB 1) • Is the DC power return section placed between the power source and the entry point of the system. B2: The entry-point of the system room and the system: (The equivalent impedance is called RB 2) • Is the DC power return section placed between the power source and the entry point of the system. NOTE 1: For DC/C distribution, the voltage drop along each DC power return conductor should be less than 1 V at maximum load current. One concern of this requirement is to avoid electrochemical corrosion in metallic structures by stray currents (see clause 6.1 of ETSI EN 300 253 [i.1]). NOTE 2: For DC/I distribution, the voltage drop in DC power return conductors is calculated to ensure that at the maximum load current the supply voltage at the power interface to the equipment is within its specified limits. |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.3.3 DC return conductor connections (C connections) | C1: DC return conductors and CBN at MET: (The equivalent impedance is called RC 1) • Represents the link between the DC return conductor and the MET. C2: DC return conductors and CBN at power source level: (The equivalent impedance is called RC 2) • Represents the link between the DC return conductor and the frame of the power source. C3: DC return conductors and CBN at the SRPP of the system: (The equivalent impedance is called RC 3) ETSI ETSI TR 101 147 V1.2.1 (2025-02) 10 • Represents the link between the DC return conductor and the RGT at the entry point of the system. C4: DC return conductors and CBN in the system (SYST): (The equivalent impedance is called RC 4) • Represents the link between the DC return conductor and the frame of the system. NOTE: For DC/I distribution , the connections C1, C3 and C4 do not exist. The impedances RC1, RC3 and RC4 are considered to be infinite. |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.3.4 Signal screen connections (S connections) | S: Between the System and MDF: (The equivalent impedance is called RS) • Represents the screens of signal cables which are at least bonded at each end to the metallic structure of the system and the MDF (according to clause 5.5 of ETSI EN 300 253 [i.1]). |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 4.3.5 AC Mains Protective Conductor (D1 connection) | D1: AC Mains Protective Conductor to the Power Plant: (The equivalent impedance is called RD 1) • Represents the link from the power source and the MET. It is constituted: - by a single conductor. |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 5 Modelling of the systems | |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 5.1 DC/C power supply model | 0V PW P RG T SRPP System L o a d M ET M DF RG2 RG3 RG1 RG5 RG6 RS RG4 RC2 SY ST RC4 RB2 RB1 RC3 RC1 1V Figure 4: Electrical diagram for DC/C power supply principle ETSI ETSI TR 101 147 V1.2.1 (2025-02) 11 |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 5.2 DC/I power supply model | The main characteristic of this distribution is the fact that the DC power supply current is confined to a single loop. 0V PW P R G T SR PP System L o a d M ET M D F R G 2 RG 3 R G 1 RG 5 RG 6 RS RG 4 R C2 SY ST RB2 RB1 Figure 5: Electrical diagram for DC/I power supply principle |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 6 Interworking | |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 6.1 Interworking between 2 systems | |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 6.1.0 Introduction | In all the following clauses, a new system (System B) is considered to be connected to a pre-existing one (System A). They are installed in the same CBN and exchanging signals through a common MDF. For each configuration, the currents circulating through the CBN are analysed. Engineering precautions resulting from this analysis are listed for each configuration. NOTE: For simplification reasons, the impedances RC 1, RC 2 and RG 1 (PWP grounds) have been replaced by the equivalent impedance RE 1. ETSI ETSI TR 101 147 V1.2.1 (2025-02) 12 |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 6.1.1 Interconnection between DC/C and DC/I models | 0V PW P RG T SRPP System A System B L o a d L o a d M ET M DF RB1 RB2 RG6 RG 5 RG 2 RG 3 RE1 RS RC3 RG 5 RG 6 RS RG 4 RC4 RB1 RB2 Figure 6: DC/I and DC/C interconnection This diagram shows that a part of the current consumed by System B(DC/C system) can pass through the common impedance of the two systems RG 2, RG 3 and RE 1 and through the impedances RG 5, RG 6 and RS of system A (DC/I system). Engineering precautions: It is recommended to verify the following points before interconnection: • the grounding conductors and connections of system A should be dimensioned to withstand the additional currents due to the introduction of the system B; • the voltages generated by additional current inside the bounding network of system A (RG6) do not reduce its noise immunity (reduction of the immunity of the asymmetrical links which are referenced to the ground of system A); • the signal cables between system A and MDF will neither suffer from excessive current heating, nor be subject to voltage drop (additional current through RS) which could create transmission faults in the case of asymmetrical links (for example: coaxial cables). NOTE: All these precautions will also have to be applied to the DC/I system in case of connection with a pre-existing DC/C one. ETSI ETSI TR 101 147 V1.2.1 (2025-02) 13 |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 6.1.2 Interconnection between 2 DC/C models | 0V PW P RGT SRPP System A System B L o a d L o a d M ET M DF RB1 RB2 RG6 RG5 RG2 RG3 RE1 RS RC3 RG5 RG6 RS RG4 RC4 RC4 RC3 RB1 RB2 Figure 7: 2 DC/C interconnection In this configuration, the total DC power supply current is split up into all ground connections of the 2 DC/C systems, and will modify the initial share of DC return current of system A. Engineering precautions: It is recommended to verify the following points before interconnection: • the conductors and the connections of the 2 systems (A and B) have been dimensioned to withstand the additional currents coming from the other system (B and A); • the voltages generated by additional current inside the bonding network of the 2 systems (RG6) do not reduce their noise immunity (reduction of the immunity of the asymmetrical links which are referenced to ground); • the signal cables between the 2 systems (A and B) and MDF will neither suffer from excessive current heating, nor be subject to voltage drop (additional current through RS) which could create transmission faults in the case of asymmetrical links (for example: coaxial cables). ETSI ETSI TR 101 147 V1.2.1 (2025-02) 14 |
dafcac7f5f700bde1f7c79bcffb5496d | 101 147 | 6.1.3 Interconnection between 2 DC/I models | 0V PW P R G T SRPP System A System B L o a d L o a d M ET M DF RB1 R B2 RG 6 RG 5 RG 2 R G 3 RE1 RS RG 5 R G 6 RS RG 4 R B2 RB1 Figure 8: 2 DC/I interconnection As there is no common path between grounding and power distribution, there is no mutual influence between the 2 systems. Engineering precautions: • none. ETSI ETSI TR 101 147 V1.2.1 (2025-02) 15 Annex A (informative): Bibliography • ETSI EN 300 132-1: "Environmental Engineering (EE); Power supply interface at the input to Information and Communication Technology (ICT) equipment; Part 1: Alternating Current (AC)". • ETSI EN 300 132-2: "Environmental Engineering (EE); Power supply interface at the input of Information and Communication Technology (ICT) equipment; Part 2: -48 V Direct Current (DC)". • ETSI EN 300 132-3: "Environmental Engineering (EE); Power supply interface at the input of Information and Communication Technology (ICT) equipment; Part 3: Up to 400 V Direct Current (DC)". ETSI ETSI TR 101 147 V1.2.1 (2025-02) 16 History Document history V1.1.2 February 1998 Published as ETSI EG 201 147 V1.2.1 February 2025 Publication |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 1 Scope | The scope of the present document is limited to the requirements and architectures for HIPERLAN Types 2. HIPERLAN Type1 is addressed by ETS 300 652 [2] and its related Conformance Test Specifications, [2a], [2b], [2c] and [2d]. HIPERLINK will be described in a TR produced by BRAN. The requirements address subjects like applications, traffic volumes and traffic patterns that underlie the projected spectrum requirements as well as the chosen architectures. The architectures address the communications layer models as well as the Reference models that identify the key interfaces subject to standardization. The architectures developed in the present document are intended to delineate the boundaries between HIPERLAN standards and standards for networks in which HIPERLANs may be used as subsystems or components. Scope of standardization The scope of the standards for HIPERLAN Types 2 is limited to the air interface specifications, the Data Link Control (DLC) layer specifications, the specifications of the management functions and the interworking functions. The DLC layer specification includes a specification of the services to be provided. The ETSI HIPERLAN/2 standards specify subsystems up to and including the DLC Layer. Interworking functions will be specified in liaison with other relevant technical standardization bodies. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] CEPT Recommendation T/R 22-06: "Harmonized radio frequency bands for High Performance Radio Local Area Networks (HIPERLANs) in the 5 GHz and 17 GHz frequency range". [2] EN 300 652: "Broadband Radio Access Networks (BRAN); HIgh PErformance Radio Local Area Network (HIPERLAN) Type 1; Functional specification". [2a] ETS 300 836-1: "Broadband Radio Access Networks (BRAN); HIgh PERformance Local Area Network (HIPERLAN) Type 1; Conformance testing specification; Part 1: Radio type approval and Radio Frequency (RF) conformance test specification". [2b] ETS 300 836-2: "Broadband Radio Access Networks (BRAN); HIgh PERformance Local Area Network (HIPERLAN) Type 1; Conformance testing specification; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification". [2c] ETS 300 836-3: "Broadband Radio Access Networks (BRAN); HIgh PERformance Local Area Network (HIPERLAN) Type 1; Conformance testing specification; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification". [2d] ETS 300 836-4: "Broadband Radio Access Networks (BRAN); HIgh PERformance Local Area Network (HIPERLAN) Type 1; Conformance testing specification; Part 4: Abstract Test Suite (ATS) specification". [2e] Void. ETSI TR 101 031 V2.2.1 (1999-01) 8 [2f] TR 101 177: "Broadband Radio Access Networks (BRAN); Requirements and architectures for broadband fixed radio access networks (HIPERACCESS)". [2g] TR 101 378: "Broadband Radio Access Networks (BRAN); Common ETSI - ATM Forum reference model for Wireless ATM Access Systems (WACS)". [3] ETS 300 328: "Radio Equipment and Systems (RES); Wideband transmission systems; Technical characteristics and test conditions for data transmission equipment operating in the 2,4 GHz ISM band and using spread spectrum modulation techniques". [4] ITU-T Recommendation Q.2931 (1995): "Broadband Integrated Services Digital Network (B-ISDN) - Digital subscriber signalling system no. 2 (DSS 2) - User-network interface (UNI) - Layer 3 specification for basic call/connection control". [5] ISO/IEC 8802-1: "Information technology -- Telecommunications and information exchange between systems -- Local and metropolitan area networks -- Specific requirements -- Part 1: Overview of Local Area Network Standards". [6] ERC Decision 96/03: "ERC Decision on the harmonized frequency band to be designated for the introduction of High Performance Radio Local Area Networks (HIPERLANs)". [7] ATM Forum Specification UNI 3.1: "User-Network Interface Specification". [8] ITU-T Recommendation I.356 (1996): "B-ISDN ATM layer cell transfer performance". |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 3 Definitions and abbreviations | |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: [local] access: This term is used in the telecommunications sense: short range (< 100 m) wireless access to other, possibly wired, networks. [remote] access: This terms is used in the telecommunications sense: long range (< 10 km) wireless access to other, possibly wired, networks. Remote access networks are also referred to as "local loop networks". [wireless] access subnetwork: A [wireless] subnetwork that is a physical subset of an access network. It is serviced by a single [wireless] access point. [wireless] access network: The combined [wireless ] subnetworks providing access to a single external network, e.g. an ATM switch. [wireless] access point: A device controlling a single [wireless ] access subnetwork. asynchronous traffic: Data traffic that characteristically has a statistical arrival and delay distribution. This typifies most LAN data traffic. Business Premises Network (BPN): A network covering a privately owned network. convergence sublayer: A sublayer that generates no protocol but that provides the wireless DLC layer with the information it needs to perform its QoS management functions as required. data confidentiality: Provisions for the protection of transmitted data from observation by unauthorized stations or other monitoring means. One measure for doing that is to implement encryption. Data Link Control (DLC): Layer 2 of the ISO/OSI reference model. Domestic Premises Network (DPN): A network covering home environment. downlink: The incoming data direction from a wireless terminal adapter perspective. ETSI TR 101 031 V2.2.1 (1999-01) 9 encryption: A means of obtaining data confidentiality. See also: Data confidentiality. handover: The changing of the path over which information flows between two communicating HIPERLAN nodes without being disconnected. HIPERLAN: HIgh PErformance Radio Local Area Network. interworking: Interaction between dissimilar sub-networks, end systems, or parts thereof, providing a functional entity capable of supporting end-to-end communications. Local Area Network (LAN): A group of user stations, each of which can communicate with at least one other using a common transmission medium commonly managed. Protocol Data Unit (PDU): Data unit exchanged between entities at the same ISO layer. Physical Layer (PHY): Layer 1 of the ISO/OSI reference model. The mechanism for transfer of symbols between HIPERLAN nodes. Service Data Unit (SDU): Data unit exchanged between adjacent ISO layers. time-bounded services: Time-bounded services denotes transfer services with low delay and low delay variance for use with voice and other real-time services. [wireless] terminal adapter: The functional components of a network node that provide the communications services and the related control functions. transceiver coverage area: The physical area serviced by a single transceiver. uplink: The outgoing data direction from wireless terminal adapter perspective. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAL ATM Adaptation Layer AP Access Point ARQ Automatic Retransmission reQuest ATM Asynchronous Transfer Mode BER Bit Error Rate B-ISDN Broadband Integrated Services Digital Network BPN Business Premises Network CATV Community Antenna TeleVision CEPT Conférence Européenne des administrations des Postes et des Télécommunications DLC Data Link Control DPN Domestic Premises Network DSDU DLC Service Data Unit EY-NPMA Elimination-Yield Non-pre-emptive Priority Multiple Access FEC Forward Error Correction FPLMTS Future Public Land Mobile Telecommunications System HDTV High Definition TeleVision HIPERACCESS HIgh PErformance Radio ACCESS HIPERLAN HIgh PErformance Radio Local Area Network HIPERLINK HIgh PErformance Radio LINK IP Internet Protocol ISM Industrial, Scientific and Medical LAN Local Area Network LLC Logical Link Control LME Layer Management Entity MAC Medium Access Control N/A Not Applicable OSI Open Systems Interconnection PCMCIA Personal Computer Memory Card Interface Association ETSI TR 101 031 V2.2.1 (1999-01) 10 PDA Personal Digital Assistant PDU Protocol Data Unit PHY Physical Layer QoS Quality of Service RF Radio Frequency SDTV Standard Definition TeleVision SDU Service Data Unit TCP Transport Control Protocol UMTS Universal Mobile Telecommunications System UNI User Network Interface UTRAN UMTS Terrestrial Radio Access Network VCR Video Cassette Recorder |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 4 Overview | The BRAN family of standards includes: HIPERLAN Type 1 (high speed wireless LANs), HIPERLAN Type 2 (short range wireless access to IP, ATM and UMTS networks) both operating in the 5 GHz band, HIPERACCESS (fixed wireless broadband point-to-multipoint) and HIPERLINK (wireless broadband interconnection) operating in the 17 GHz band. This is represented in the figure below together with the operating frequencies and indicative data transfer rates on the air interface. DLC PHY (5 GHz) (25 Mbit/s) MAC PHY (5 GHz) (19 Mbit/s) HIPERLAN Type 1 Wireless 8802 LAN HIPERLAN Type 2 Wireless IP, ATM and UMTS Short Range Access DLC PHY (17 GHz) (155 Mbit/s) HIPERLINK Wireless Broadband Interconnect PHY (various bands) (25 Mbit/s) DLC HIPER- ACCESS Wireless IP and ATM Remote Access Figure 2: Overview of HIPERLAN Types, HIPERACCESS and HIPERLINK |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 4.1 HIPERLAN Type 1, Wireless 8802 Local Area Networks | HIPERLAN Type 1 (HIPERLAN/1) is a wireless local area network that is ISO/IEC 8802-1 [5] compatible. It is intended to allow high performance wireless networks to be created, without existing wired infrastructure. Multiple HIPERLANs can co-exist in the same geographical area with equitable bandwidth sharing without co-ordination between them. In addition HIPERLAN Type 1 can be used as an extension of a wired local area network. HIPERLAN/1 offers unconstrained connectivity based on directed one-to-one communications as well as one-to-many broadcasts. The channel provides both self configurability and flexibility of use thanks to a distributed channel access (EY-NPMA) and standardized forwarding feature. The HIPERLAN/1 Functional Specification is given in ETS 300 652 [2]. ETSI TR 101 031 V2.2.1 (1999-01) 11 4.2 HIPERLAN Type 2, short range wireless access to IP, ATM and UMTS networks HIPERLAN Type 2 (HIPERLAN/2) is intended to provide local wireless access to IP, ATM and UMTS infrastructure networks by both moving and stationary terminals that interact with access points which, in turn, usually are connected to an IP, ATM or UMTS backbone network. A number of these access points will be required to service all but the smallest networks of this kind and therefore the wireless network as a whole shall support hand-overs of connections between access points. Further, such a wireless access network shall be able to provide the Quality of Service (QoS), including required data transfer rates, that users expect from a wired IP or ATM network. 4.3 HIPERACCESS, remote wireless access to IP and ATM networks HIPERACCESS provides outdoor, high speed (25 Mbit/s typical data rate) radio access, it provides fixed radio connections to customer premises and is capable of supporting multimedia applications. (Other technologies such as HIPERLAN/2 might be used for distribution within the premises.) HIPERACCESS will allow an operator to rapidly roll out a wide area broadband access network to provide connections to residential households and small businesses. However, HIPERACCESS may also be of interest to large organizations wishing to serve a campus and its surroundings and to operators of large physical facilities such as airports, universities, harbours etc. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 4.4 HIPERLINK, wireless interconnection | Interconnecting high data rate sources such as (access) networks requires high bit rates and large channel capacities. HIPERLINK provides point-to-point interconnection at very high data rates, e.g. up to 155 Mbit/s over distances up to 150 m. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5 Requirements | This clause deals with the general requirements that underlie the development of the HIPERLAN standards for wireless broadband access. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.1 Application environments | The following subclauses describe a number of application environments. The common denominator of these environments is that: - they are used in a geographically limited area; - they support multimedia services. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.1.1 Types of HIPERLAN application environments | Domestic Premises Network (DPN) environment The DPN environment covers the home and its immediate vicinity; it typically includes a localized radio extension to a broadband network. It is characterized by spot coverage areas, perhaps individual cells, one per home or building. Support for mobility beyond the coverage area is outside the scope of the present document. Business Premises Network (BPN) environment The BPN environment covers a network covering e.g. a company area, university campus hospital, industrial premises, airports, train stations, etc. It may offer access, switching and management functions within an arbitrary large coverage area serviced by multi-cellular wireless communications facilities. Thus, functions like handover and paging may be necessary within this environment. ETSI TR 101 031 V2.2.1 (1999-01) 12 |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.1.2 Types of networks | HIPERLANs may be used in a number of ways, for example: Wireless Access to Public Network HIPERLAN Type 2 may be used to gain access to a public network, for example, to provide Telepoint services. Wireless Access to Private Network HIPERLANs may be used to gain access to a private network, for example, business premises or campus networks. Temporary Network HIPERLANs may be used to create temporary networks, independent of an established wired local network. Such a network may be used semi-permanently, as an alternative for a wired network, and for ad-hoc purposes, for example for people to communicate and work on documents during a meeting. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.1.3 Usage environments. | The table below shows various examples of usage and applications in the networks types given above. A number of these application environments are analysed in the following subclauses. Table 1: Examples of usage environments Wireless Access to Public Networks Wireless Private Networks (access- and infrastructure) Temporary networks DPN - education - security, (sensors) - multimedia, e.g. radio CATV access point - mobile access to IP, ATM or UMTS network - education security (surveillance and sensors) - domestic cordless multi-media distribution - education - meetings - fairs - exhibition BPN - emergency networks telepoint - education - security, (sensors) - multimedia, e.g. radio CATV access point - mobile access to IP, ATM or UMTS network - manufacturing - office automation - education - financial transactions - medical/hospital - security (surveillance and sensors) - broadcast studios - maintenance of large objects - stock control - aircraft gate link - large meetings - offices - maintenance of large objects - industrial - emergency networks - exhibition |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.2 User scenarios | This subclause describes different scenarios in which HIPERLAN Type 2 may be used. • Infrastructure replacement scenario, i.e. when HIPERLANs could be used instead of cabling. • Cordless access scenario, in which users need to use HIPERLANs in different locations at different times possibly maintaining connectivity while in transit. • Wireless access to infrastructure scenario. • Specialized portable applications scenario, i.e. user uses a PDA type device mainly for specialized applications, e.g. maintenance or surveillance. • Domestic premises scenario, i.e. HIPERLANs are used in the home environment. ETSI TR 101 031 V2.2.1 (1999-01) 13 • Wireless manufacturing automation scenario, i.e. HIPERLANs are used in a factory or a large assembly / building facility. • Inter network communication scenario. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.2.1 Infrastructure replacement scenario | HIPERLANs can be used for wired infrastructure replacement in a number of scenarios including the replacement of wired premises networks. Typical cases could be temporary office installations or installations into spaces where building characteristics or protection prohibit the extensive use of a cabling. The infrastructure to be replaced includes stationary backbone networks operating at high speeds as well as wireless network terminations. Terminals typically connected to infrastructure networks typically are designed for fixed use. Such a terminal could, for example, be a workstation, a PC or any other purpose specific terminal. The applications are typically broadband applications. In this scenario the user device is mostly stationary and the main benefit derived from HIPERLANs is the wireless dimension. Thus, HIPERLANs shall provide or approximate fixed network QoS to a stationary user. The user should not be able to notice the difference between using the wireless system and a wired system. Table 2: An example of a wired infrastructure replacement scenario Attribute End-user equipment PC or work station Usage environment Offices etc. Range Up to 50 meters for indoor systems; QoS expectation Same as desktop Applications Same as desktop Mobility Limited Coverage Continuous User Density High |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.2.2 Cordless access scenario | In this scenario, the HIPERLAN user needs to perform his or her work at different locations at different times. The main end-user equipment would be a portable computer. Typically such a user would carry a portable computer to various places within the office and then use the computer while stationary. Typical places for using the HIPERLAN system outside a office room would be meeting rooms, dining facilities, patient wards, class rooms and auditoria as well as waiting rooms/halls. A cordless user will also access the public network, through base stations installed in locations such as railway stations, airports and shopping centres. In some cases, connectivity has to be maintained while the user is in transit from one location to another. The terminals in this scenario are movable. A typical terminal could be built around a laptop computer and a HIPERLAN card. The mobile node will in many cases be a battery driven device so that an economic consumption of power is required. ETSI TR 101 031 V2.2.1 (1999-01) 14 Table 3: An example of a cordless access scenario Attribute End-user equipment Portable computer, e.g. Notebook or Palmtop. Usage environment Offices, schools, hospitals, airports, railway stations, shopping centres, etc. Range Up to 50 meters for indoor systems; Up to 150 meters for outdoor systems. QoS expectation Similar to desktop Applications Similar to desktop Mobility none during use Coverage Continuous User Density High (e.g. in a meeting room) Power consumption Low |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.2.3 Specialized portable applications scenario | In the third scenario a user has a small (possibly dedicated) system like a PDA to access services. The applications are typical broadband applications, which shall be supported for mobile users with an acceptable QoS by the mobility functions in the network, e.g. handover. The QoS expected from the HIPERLAN system in this scenario could however be somewhat lower than the QoS of a fixed system. The user can be assumed to realize that a small loss in QoS is the price paid for the mobility gained. For example, the connection might tolerate a short interruption because of a handover (resulting in momentary disturbance in the video picture) etc. The terminal in this scenario is a mobile handheld terminal e.g. a PDA with a wireless network card or a dedicated mobile node. The applications are mostly dedicated mobile applications that are capable of operating at a lower QoS, as they would use mobile specific features to compensate for some mobile related problems. The mobile node will in many cases be a battery driven device so that an economic consumption of power is required. Table 4: An example of a specialized portable scenario Attribute End-user equipment Hand portable unit, PDA Usage environment Anywhere within or near private premises Range Up to 50 meters for indoor systems; Up to 150 meters for outdoor systems. QoS expectation Modest, but maintained during movement Applications Dedicated, could be mobile specific Mobility Walking speed or slow vehicle (e.g. forklift) Coverage Continuous User Density Low Power consumption Very low |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.2.4 Domestic premises scenario | In the domestic network scenario, many appliances, e.g. PC laptop, printer/fax machines, security systems, home appliances, digital HDTV/SDTV sets, digital Video Cassette Recorder (VCR), speakers and more could be linked in various ways. A typical scenario would be: 1) An entertainment cluster (video and sound) located in the living room transmitting to television sets located in the living room, kitchen and bedroom. 2) A music system in the living room transmitting to speakers located in the living room, bedroom or dining room. ETSI TR 101 031 V2.2.1 (1999-01) 15 3) Security features outside the home such as wireless security camera or remote sensors. These could either be located on the external walls of the property or at the boundary wall or a remote building such as a garage or recreation facility. 4) Outdoor speakers for barbecue/party. Assuming that the music system is located in the entertainment cluster in the living room, the transmission path and length may extend into the garden. From the above, it is obvious that the domestic network shall allow access to external networks e.g. digital television or be capable of working with no external links e.g. a music system with remote speakers. This system should be easily installable by non-technical people. A domestic network generally covers a much smaller area than either factory or office environments. The rooms in a domestic premises tend to be smaller when compared to work environments and have more compartmentalized structure (storage spaces and en-suites). Table 5: An example of a domestic premises scenario Attribute End-user equipment Computer, television, entertainment cluster, security systems, etc. Usage environment Domestic premises, i.e. small rooms with high attenuation Range Up to 15 meters QoS expectation Consistent with real-time multi-media services Applications Real-time multi-media Mobility Walking speed Coverage Continuous User Density Low |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.2.5 Industrial and transportation scenario | In manufacturing scenarios such as process automation, commissioning systems, baggage transfer, distribution systems, warehouse storage and retrieval services we have a large number of intelligent transportation elements which may move autonomously and automatically in a factory hall, a storage building, or in an airport. Such a system should cover approximately an area of 250 m × 250 m. Delay values and data losses are critical. The ability to support highly reliable real-time control and alarm data as well as other time bounded services is mandatory. Power consumption and the physical size of the communication device are not as critical as in other scenarios. Table 6: An example of a manufacturing scenario Attribute End-user equipment Intelligent transportation elements, autonomous, automatic vehicles, surveillance systems, monitors Usage environment Factory halls, airports, storehouses, industrial environments Range Up to 50 meters. Shadowing, highly variable radio channels QoS expectation Low delay, high error sensitivity, time bounded, real-time, short packets Applications Mobile, file transfer, control, alarms, surveillance, monitoring Mobility < 10 m/s Coverage Continuous User Density High (variable) Power consumption Not critical ETSI TR 101 031 V2.2.1 (1999-01) 16 |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.3 Application requirements | There are many applications that together form the requirements for wired as well as wireless systems. Many of these will be covered in later clauses, but a general application type, the multimedia application deserves special attention. Multimedia applications are becoming popular and are already beginning to demand wireless transport with a high quality of service. Multimedia applications shall be taken into account when defining the HIPERLAN family. Multimedia covers anything from basic messaging through to audio, video or any combination thereof. At the transport layer multimedia consists of two types of information flow; firstly the delivery of fixed packages of information and secondly the delivery of a stream of information which can be described by a certain data rate and delay tolerance. IP has been designed to cater specifically for data packet traffic with no specific QoS guarantees, i.e. best effort. However, new applications and protocols have been and are being developed which demand or provide QoS guarantees over IP networks. Examples of this are integrated services using RSVP and differentiated services. As users get accustomed to this level of service in their wired systems they are going to demand the same QoS on wireless systems. HIPERLAN/2 shall support IP applications and QoS. ATM is a transport mechanism, which has been designed to cater specifically for multimedia by being able to support very different kinds of connections with different QoS parameters. New applications will be developed which fully exploit the capabilities of the ATM transport technology, especially the availability of high bandwidth. Also for ATM, as users get accustomed to this level of service they are going to demand the same QoS on wireless systems. HIPERLAN/2 shall support ATM applications and QoS. The following subclauses describe a number of scenarios for HIPERLAN deployment. Two main scenarios are described, corresponding to an office and an industrial application. Each scenario is broken down further into typical activities and shows estimated data rate requirements for each activity. The purpose of this analysis is to provide a thorough basis for an estimate of HIPERLAN spectral requirements. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.3.1 Office HIPERLAN deployment scenario | The following activities are expected in an office deployment scenario for HIPERLAN over the next two or three years. The required data rates for each activity are given in a spreadsheet (table 7). Table7 also shows the calculation of an average data rate required to support the listed activities for each person in the office. These figures will be used shortly to compute estimates of the spectrum required to support typical office use of HIPERLANs. A list and brief description of office related activities that could be supported by HIPERLANs follows: Multimedia conference (large video displays) High quality video/audio channels with multiparty data links for the transmission of still images as well as the exchange of computer data including shared multi-user appplications. Telephone/Audio From toll quality telephone service to higher quality audio. General networked computing applications Examples of applications are: Client-server, Processing, Printing, E-mail, Messaging, Fax, Groupware, Games and Simulations, Network file systems, etc. The transfers are generally asymmetric and highly bursty. The data rate requirements are quite dependent on the level of mobility, i.e. the quality should be very similar to that one offered by a fixed LAN on a static mobile node, and temporarily degraded while on the move. Moreover, the bit rate should correspond to the processing speed of the terminal i.e. PDA, portable computer or workstation. The requirements for a wired-LAN QoS are upper bounds and may be considered as a basis for a wireless LAN: Multimedia database Encyclopaedia browsing, medical diagnosis records, electronic newspaper, bulletin board, World Wide Web, manuals, etc. Includes asymmetric, resource demanding applications and bursty non-real-time data. Security and monitoring Surveillance video/audio, Industrial or office security service, Alarms, etc. ETSI TR 101 031 V2.2.1 (1999-01) 17 Internet and Intranet Browsing The Internet has gained prominence far beyond the expectations expressed by experts only a few years ago. Today businesses of all kinds make extensive use of Internet and Intranet as a means to disseminate information about their products and services. Similarly, government institutions are getting ready to put their information on the Net. With the emergence of electronic payment the Net will become a commercial environment as well. For many international organizations, including ERO and ETSI, the Net has become an indispensable tool. As a consequence users spend hours a day "surfing" the Net to find and exchange information. This information is typically not just text form but includes extensive graphics as well as, in some cases, video and audio sequences. Teleworking Less prominent but gaining ground is the notion of teleworking. Teleworking may mean working at home but being in contact with colleagues at work and with customers through video/voice/data sessions. It also means collaboration between geographically separated persons, possibly a group of them. Here too, the ability of telecommunications to deliver high quality video and sound as well as real time data allows users to avoid costly and time consuming travel. Application developers have caught on to this opportunity. A variety of "screen sharing" tools is being developed that provide users with the means to work together in real time on the same electronic documents while being in eye and ear contact. Much like the Net browsers opened up the demand for Internet services so these sharing tools will create a large demand for teleworking services. Table 7: Predicted average data rate per HIPERLAN, office deployment Office application Link direction Average data rate Typical peak/average ratio Peak data rate Office application usage Weighted average data rate bits/s bits/s % bits/s/HIPERLAN 1. Video applications General Multimedia conferencing, including voice, video and computer data Uplink 1,00E+06 2,00 2,00E+06 7,00% 7,00E+04 Downlink 4,00E+06 1,50 6,00E+06 7,00% 2,80E+05 2. Telephone Uplink & downlink 3,40E+04 1,00 3,40E+04 10,00% 3,40E+03 3. General networked computing applications Uplink & downlink 2,50E+06 10,00 n/a 10,00% 1,25E+05 4. Multimedia database Uplink 1,00E+04 10,00 1,00E+05 7,00% 7,00E+02 Downlink 1,00E+05 10,00 1,00E+06 7,00% 7,00E+03 5. Security and monitoring Uplink 7,50E+05 2,00 1,50E+06 1,00% 7,50E+03 Downlink 6,40E+04 1,20 7,68E+04 1,00% 6,40E+02 6. Internet and intranet browsing Uplink 2,40E+03 10,00 2,40E+04 15,00% 3,60E+02 Downlink 1,00E+05 10,00 1,00E+06 15,00% 1,50E+04 7. Teleworking Uplink 1,00E+05 15,00 1,50E+06 10,00% 1,00E+04 Downlink 5,00E+05 5,00 2,50E+06 10,00% 5,00E+04 TOTALS: 100,00% 5,70E+05 bits/s/HIPERLAN Note: Peak data rates are not applicable where applications are insensitive to the data transfer delay. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.3.2 Industrial HIPERLAN deployment scenarios | Table 8 provides a breakdown of the data rate capacity required to support a typical industrial deployment of a HIPERLAN network on a piece of industrial plant or machinery assumed to contain 50 separate HIPERLAN equipments operating in a single radio locale defined by the operating radio range. A more general list of industrial activities that can be supported by HIPERLAN follows: Gatelink Gatelink is a typical example of multimedia networking in an industrial environment. The applications are in aircraft maintenance support, software loading of airborne systems, passenger service and entertainment, pilot briefing and backup of aircraft maintenance systems. The data rate requirements of Gatelink are not analysed further in the present document. ETSI TR 101 031 V2.2.1 (1999-01) 18 Manufacturing Applications In process automation, commissioning systems, baggage transfer and distribution systems we will find a mixture of services. Services will include non-real-time data for file transfer, software and configuration data download, as well as very time critical (real time) data transfer for control and alarm data. Also a mixture of conversational multimedia services for surveillance and monitoring purposes is needed. Industrial Remote control Remote control of some device. High quality asymmetric video/audio (MPEG-1 or MPEG-2, possibly multichannel and/or stereo picture), control information and computer data. Industrial monitoring Industrial monitoring is a specific application in industrial environments. The applications are for instance monitoring of oil pipelines or monitoring of production processes and resources like tanks in chemistry plants. Data is typically generated by a sensor, is very small as well as specific and has very stringent delay bound and variance. Normally the bandwidth needs are low. However, in certain circumstances (for instances fire or explosions) a very bursty and strongly correlated traffic can be generated by hundreds (thousands) of sensors which has to be handled by the network according to the QoS requirements. Table 8: Predicted average data rates per HIPERLAN for an industrial deployment Industrial application Link direction Average data rate Typical peak/average ratio Peak data rate Industrial application usage Weighted average data rate bits/s bits/s % bits/s/plant 1. File transfer Uplink & downlink 2,00E+06 5,00 1,00E+07 2,00% 4,00E+04 2. Software transfer Uplink & downlink 4,00E+05 2,00 8,00E+05 1,00% 4,00E+03 3. Configuration data Uplink & downlink 6,00E+05 20,00 1,20E+07 1,00% 6,00E+03 4. Control data Uplink 2,10E+07 2,00 4,20E+07 25,00% 5,25E+06 Downlink 2,10E+07 2,00 4,20E+07 25,00% 5,25E+06 5. Alarms Uplink & downlink 2,00E+04 20,00 4,00E+05 1,00% 2,00E+02 6. Surveillance Uplink & downlink 1,40E+07 2,00 2,80E+07 3,00% 4,20E+05 7. Monitoring Uplink & downlink 5,00E+05 1,00 5,00E+05 20,00% 1,00E+05 8. Video multipoint monitoring Uplink 7,50E+05 2,00 1,50E+06 10,00% 7,50E+04 Downlink 2,25E+06 1,50 3,38E+06 10,00% 2,25E+05 9. High bandwidth video multipoint monitoring Uplink 1,50E+06 2,00 3,00E+06 1,00% 1,50E+04 Downlink 7,50E+06 1,50 1,13E+07 1,00% 7,50E+04 TOTALS: 100,00% 1,15E+07 bits/s/plant Assuming there are 50 HIPERLANs per plant: 2,29E+05 bits/s/HIPERLAN |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.3.3 Public HIPERLAN deployment scenario | In table 9 the required data rates for the applications in a public deployment scenario are shown. Just as in the office scenario, the average data rate per person is also listed. The listed applications are the same as in the office scenario, since public access will mostly be available in geographically small (hot spot) areas. These hot spot areas will be at e.g. airports, hospitals, conference sites etc., i.e. areas in which the same access network can be used for both public (guests, ETSI TR 101 031 V2.2.1 (1999-01) 19 customers etc.) and private (employees of the operator) access. For simplicity, the same figures can be used for pure public access networks, e.g. in city centres. Table 9: Predicted average data rate per HIPERLAN, public deployment Public application Link direction Average data rate Typical peak/average ratio Peak data rate Office application usage Weighted average data rate bits/s bits/s % bits/s/HIPERLAN 1. Video applications General Multimedia conferencing, including voice, video and computer data Uplink 1,00E+06 2,00 2,00E+06 10,00% 1,00E+05 Downlink 4,00E+06 1,50 6,00E+06 10,00% 4,00E+05 2. Telephone Uplink & downlink 3,40E+04 1,00 3,40E+04 5,00% 1,70E+03 3. General networked computing applications Uplink & downlink 2,50E+06 10,00 n/a 5,00% 1,25E+05 4. Multimedia database Uplink 1,00E+04 10,00 1,00E+05 5,00% 5,00E+02 Downlink 1,00E+05 10,00 1,00E+06 5,00% 5,00E+03 5. Security and monitoring Uplink 7,50E+05 2,00 1,50E+06 5,00% 3,75E+04 Downlink 6,40E+04 1,20 7,68E+04 5,00% 3,20E+03 6. Internet and intranet browsing Uplink 2,40E+03 10,00 2,40E+04 15,00% 3,60E+02 Downlink 1,00E+05 10,00 1,00E+06 15,00% 1,50E+04 7. Teleworking Uplink 1,00E+05 15,00 1,50E+06 10,00% 1,00E+04 Downlink 5,00E+05 5,00 2,50E+06 10,00% 5,00E+04 TOTALS: 100,00% 7,48E+05 bits/s/HIPERLAN Note: Peak data rates are not applicable where applications are insensitive to the data transfer delay. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.3.4 Other HIPERLAN deployment scenarios | HIPERLAN can support many other activities and deployment scenarios other than those listed above. A number of the more prominent examples of alternative HIPERLAN deployments are described below and a TV, radio or recording studio deployment containing about 60 separate HIPERLAN equipments is analysed further in table 10: - Audio distribution. - High quality audio. - High quality Audio distribution. - High quality e.g. delivery of audio or wireless equipment for programme production (possible multiparty). - Database services. Inventory of available goods, On-floor customer services in shops, Menu of the company cafeteria, Telephone and contact information directory, etc. This deployment scenario is identified, but not analysed further in the present document. ETSI TR 101 031 V2.2.1 (1999-01) 20 Table 10: Predicted average data rates for broadcast or recording studio HIPERLAN deployments TV, radio or recording studio HIPERLAN application Link direction Average data rate Typical peak/average ratio Peak data rate Studio application usage Weighted average data rate bits/s bits/s % bits/s/deployment 1. Audio distribution, 8 channels Uplink & downlink 3,07E+06 1,00 3,07E+06 10,00 % 3,07E+05 2. High quality audio uplink, 1 stereo channel Uplink 3,84E+05 1,00 3,84E+05 10,00 % 3,84E+04 3. Telephone headsets, 10 lines Uplink & downlink 6,40E+05 1,00 6,40E+05 10,00 % 6,40E+04 4. Radio microphones, 30 off Downlink 1,15E+07 1,00 1,15E+07 30,00 % 3,46E+06 5. High quality video distribution, 8 channels Downlink 1,20E+07 1,00 1,20E+07 30,00 % 3,60E+06 6. High quality video uplink, 1 channel Uplink 1,50E+06 1,00 1,50E+06 10,00 % 1,50E+05 TOTALS: 100,00 % 7,62E+06 bits/s/deployment Assuming there are 60 HIPERLANs per deployment: 1,27E+05 bits/s/HIPERLAN 5.4 Summary of data rate requirements for HIPERLAN deployments A summary of the data rate requirements based on the example deployments listed above and analysed in tables 7, 8, 9 and 10, is given in table 11. The table includes some reasonable assumptions for the numbers of HIPERLAN terminals that would exist in each deployment and shows how the total data rate is calculated in each case. The table also includes factors for the efficiency of the network protocol (e.g. TCP/IP) and for the protocol efficiency of the air interface which takes into account the signalling traffic generated by the operation of the HIPERLAN MAC protocol which reduces the available channel capacity. Table 11: Summary of data rate requirements for HIPERLAN deployments Deployment example: Average data rate required per HIPERLAN Number of HIPERLANs per deployment Network access duty cycle Useful data rate required per deployment Approx. protocol efficiency Total data rate required per deployment bits/s/HIPERLAN % bits/s/deployment % bits/s/deployment Du Nh Au Du*Nh*Au Pe Du*Nh*Au/Pe Office 5,6960E+05 1200 31% 2,1189E+08 50% 4,2378E+08 Public 7,4826E+05 1200 10% 8,9791E+07 50% 1,7958E+08 Industrial 2,2920E+05 250 100% 5,7301E+07 50% 1,1460E+08 Studio 1,2693E+05 60 100% 7,6156E+06 50% 1,5231E+07 |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.5 Spectrum requirements | |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.5.1 Wireless access networks for office use | The spectrum requirements presented below are based on the required useful data rates analysed above for a large office area with access to a wired network scenario and certain assumptions about spectrum re-use factor and the spectral efficiency of the modulations that can be used. The following spectral requirements should be treated as typical values to guide decisions about present and future spectrum designations. - Total area covered: 24 000 m2, (approx. 160 metres × 160 metres). - Number of users: 1 200 (at 20 square metres per user). - Total data rate required: 424 Mbit/s/deployment (see table 11). ETSI TR 101 031 V2.2.1 (1999-01) 21 - Modulation efficiency: 1 bit/s/Hz. - Access point bandwidth: 25 MHz (governed by peak data rates needed for multimedia conferencing, as shown in table 7). - Minimum number of access points = 424 / 25 = 17. - Access point spacing = SQRT(24 000 / 17) = approx. 40 metres at most. Frequency re-use factor: 1/14 (see note). Therefore 14 × 25 = 350 MHz of spectrum is required to support this scenario. NOTE: Assuming a C/I requirement of 20dB and a propagation exponent of 3,5 gives us the following: C/I=3,5*10log(R/r)=20dB, where r is the cell radius and R is the frequency separation distance. The area covered by one cell is proportional to r2and the cluster area is proportional to R2. The cluster size is given by R2/ r2 = (1020/35)2 = 14. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 5.5.2 Wireless access networks for public use | The spectrum requirements can be calculated in a similar way for this scenario. A crucial point in these calculations is the choice of propagation exponent. A reasonable assumption is to use the same value as above and thus ending up with the same amount of needed spectrum. It should be noted, however, that in large open areas a smaller propagation exponent is likely, resulting in increased spectrum requirements. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 6 General considerations | |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 6.1 Regulatory constraints | Spectrum has been designated by the CEPT for the licence exempt use of HIPERLAN systems. At the time of writing the present document, 100 MHz of spectrum has been designated in the 5,2 GHz band for HIPERLAN Type 1, with a further 50 MHz available at the discretion of National Administrations (see CEPT Recommendation T/R 22-06 [1]). Licence exempt use implies the HIPERLAN systems should be able to co-exist with each other and with other radio services in the band and not cause undue interference. This will have implications for the design and specification of medium access methods and for type approval regimes for HIPERLAN equipment. Where different HIPERLAN types are required to share the same frequency band, equitable spectrum sharing rules are required as part of the type approval regime. Licensed use of HIPERLAN Type 2, preferably for public access, shall also be considered. Which frequency bands that may be appropriate for licensed use is for further study, but it is likely that such frequency bands should be found somewhere in the 4 GHz to 6 GHz band. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 6.2 Radio technology constraints | Technically, the lower frequencies are better suited for the mobile components because antenna efficiency is sufficient to allow the use of omni-directional antennas at the permitted RF power level of 1 Watt peak EIRP (see CEPT Recommendation T/R 22-06 [1]). With extensive signal processing, it is possible to achieve a range of 20 m to 50 m indoors at 5 GHz, depending on the environment. Outdoors at 5 GHz the range may be greater. In the 17 GHz band , only 100 mW EIRP RF power is allowed (see CEPT Recommendation T/R 22-06 [1]). With omni-directional antennas, range would be limited to a few meters. This makes its use for portable applications costly and inefficient. However, at these frequencies, the use of directional antennas is very effective and less cumbersome physically than at 5 GHz or lower frequencies. Therefore the 17 GHz band is best suited for infrastructure type networks, i.e. HIPERLINK. ETSI TR 101 031 V2.2.1 (1999-01) 22 Other considerations that govern the choice of frequency for mobile or stationary applications are: 1) RF component efficiency: the higher the operating frequency, the lower the efficiency of the RF power stage and other components. Stationary applications can bear this inefficiency much easier than mobile applications where (battery) power is a major factor. 2) RF component cost: the cost goes up with frequency. Here too it is the stationary applications that bear these higher costs more easily. 3) Wall attenuation: this too goes up with frequency, making continuous coverage difficult to achieve for systems supporting mobility. Point-to-point links, on the other hand, can be engineered to avoid this problem. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 6.3 User data security and privacy requirements | Users of HIPERLAN/2 systems may require protection of their transmissions from being intercepted by other users operating possibly co-located HIPERLAN/2 sub-networks. In addition they may require protection against misuse of their wireless networks by third parties. This requires the implementation of a data confidentiality service and therefore a specification of such a service as part of the HIPERLAN/2 standards. It should be noted that HIPERLAN/2 based systems may be used for public access networks which have their own security systems. Interworking between these and the HIPERLAN/2 confidentiality service should be taken into account. The level of protection provided shall be consistent with the protection provided by wired systems that do not implement a data confidentiality service. Further, the cryptographic algorithm shall not be subject to export controls and therefore allow world-wide use. ETSI has developed a cryptographic algorithm for HIPERLANs, the HIPERLAN Security Algorithm. This algorithm is designed to operate at 20+ Mbits/s and is available to ETSI members under a Confidentiality Agreement. The HIPERLAN/2 standard shall include functions for the selective use of encryption. The synchronization of the use of cryptographic keys between wireless terminals of a HIPERLAN is for further study. NOTE: Confidentiality services may be available within the host systems that make use of HIPERLAN/2 subsystems. Therefore, a confidentiality service within the HIPERLAN/2 subsystem should be an optional feature that users can activate as required. The protection from misuse by third parties is a systems concern that is common to all communications systems. This cannot be completely addressed within the scope of the HIPERLAN standards since these cover only the lower layers of the communications architecture. Network level security capabilities are addressed by IP, ATM and UMTS standards (in development); these are outside the scope of the HIPERLAN/2 Functional Standard. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 6.4 Human safety | HIPERLAN standards shall reference and comply with any appropriate human safety standards. It should be noted that HIPERLAN systems may not be suitable for use in safety critical applications. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7 Reference Model and Architecture | HIPERLAN Type 2 (HIPERLAN/2) systems provide short range, wireless access to multi-media services over IP or ATM. The scope of HIPERLAN/2 is limited to the air interface, the service interfaces of the wireless subsystem, the interworking functions and supporting capabilities required to realize these services. The following text outlines requirements, to be used as basis for the development of a functional standard. Currently available standards for TCP/IP systems include the link or physical layer, the network layer, transport layer and the application layer. The link and physical layers provide a means for transmitting a sequence of bits between a pair of nodes, but are not part of the TCP/IP protocol suite. The network layer consists of procedures that allow connection- less data to be transported across multiple networks, i.e. procedures for routing, segmentation etc. The transport layer supports connection-oriented or connection-less data to be exchanged between two hosts, which includes functions for ETSI TR 101 031 V2.2.1 (1999-01) 23 connection set up, flow control, error control etc. The application layer contains protocols for resource sharing, remote access, message exchange etc. Currently available standards for ATM systems include the ATM Physical Media layer (the bit transport), the ATM layer itself (cell processing and switching) and signalling protocols to support the connection set-up and release procedures (Signalling AAL), and a number of ATM Adaptation Layers (AALs) that enhance the basic ATM service to a level required by specific ATM service classes. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1 Reference model | |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.1 Services and capabilities | |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.1.1 Services | HIPERLAN/2 shall provide the following services: 1) Connection set-up with parameter negotiation for QoS guarantees in conjunction with respective core network layers. Outgoing and incoming connections shall be supported. Device addressing shall be consistent with world- wide roaming. 2) Releasing incoming connections and outgoing connections. 3) Unit data transfer subject to QoS parameters. NOTE: Unit Data transfer comprises both Request (= transmit) and Indication (= receive) primitives. HIPERLAN/2 shall implement traffic management within each access subnetwork to maximize adherence to QoS parameters established at connection set-up. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.1.2 Supporting capabilities | HIPERLAN/2 shall provide the following capabilities in support of the above services: 1) Association of wireless terminals in a logically distinct access subnetwork. 2) Informing the core network that hosts an access subnetwork of the changes in the population of associated wireless terminals. 3) Monitoring of radio conditions as basis for handover between access sub-networks and for informing user and hosting core network of the prevailing radio/traffic conditions. NOTE: This capability is required to support Terminal initiated handover between access sub-networks without loss of connection and with limited loss of Quality of Service. 4) Support for Battery Power Conservation. 5) Dynamic allocation of radio link frequencies and/or capacity. 6) Ad hoc functionality. A capability for communication without the presence of a fixed access point. The fixed access point mode shall have higher preference over ad hoc functionality. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.2 Reference model | HIPERLAN/2 comprises the following functional entities: NOTE 1: The entities are taken from the Common Reference Model (CRM) [2g], and in case of any differences CRM takes precedence. - Access Points (APs), which are the interface points to core networks. The AP may be decomposed into InterWorking Functions (IWFs) and an Access Point Controller (APC) controlling one or multiple Access Point Transceivers (APTs). ETSI TR 101 031 V2.2.1 (1999-01) 24 - Access Point Controllers (APCs) which present network-specific interfaces to the core network via InterWorking Functions (IWFs) which comply with appropriate standards. The APC provides methods to facilitate intra-AP handover and to control the routing of traffic through the HIPERLAN/2 network. - InterWorking Functions (IWFs), which translate the internal (B.2) interface of the HIPERLAN/2 network into network specific interfaces of the external core network and translate the internal (B.1) interface of the HIPERLAN/2 network to higher protocol layers within the wireless terminal. - Access Point Transceivers (APTs), distributed so as to be able to provide coverage throughout the service area of the Broadband Radio Access Network. These communicate via the air interfaces (W.1) with Radio Terminations (RTs). - Terminal Adapter (TAs). A terminal adapter comprises an RT and an IWF, and it presents connections for customers’ terminal. - Radio Terminations (RTs) are the radio parts of the TAs. The reference model is intended to align with the ITU IMT2000 and ETSI UMTS models of the radio access network and identifies the following reference points: Reference point WI.1: internal proprietary or standard interface of the terminal node that supports relevant core networks. Reference point B.1: a service interface which is defined in terms of abstract services and parameters for the User, Control and Management planes of the HIPERLAN/2 air interface protocol stack. This interface is expected to be a common definition for HIPERLAN/2 systems and for those HIPERACCESS systems which define interoperation via a common air interface. It may not actually exist, and is therefore not required to be present in any real implementation, but forms the basis for specification and testing. Reference point W.1: defines the radio interface between the Access Point Transceiver and the Radio Termination. It is an interoperability interface that includes a standardized air interface and can be used as a radio coexistence interface. Reference point B.2: a service interface which is defined in terms of abstract services and parameters for the User, Control and Management planes of the HIPERLAN/2 air interface protocol stack. This interface is expected to be a common definition for HIPERLAN/2 and those HIPERACCESS systems which define interoperation via a common air interface. It may not actually exist, and is therefore not required to be present in any real implementation, but forms the basis for specification and testing. NOTE 2: The Access Point may be considered to comprise one or more Access Point Transceivers connected to a single Access Point Controller. The interface between these two elements is not necessarily visible and is not specified. Reference point W.2: the interface is the supported standard interface to the relevant core network. It is in principle possible to specify interfaces for all core networks that BRAN systems support (see subclause 7.1.4). Reference point B.3: an interface over which are specified the mechanisms for communicating with the Element Management System, specific to the management of the radio access network. IWF AP Con- troller AP Trans- ceiver Core Network Radio Termi- nation IWF W.1 B.2 B.1 W.2 WI.1 Terminal Adapter HIPERLAN 2 System Access Point B.3 Wireless User Figure 4: HIPERLAN/2 generic reference model ETSI TR 101 031 V2.2.1 (1999-01) 25 |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.3 Layer architecture | The following figure shows the generic layer architecture model for HIPERLAN/2 systems. Core Network Access Point Wireless Terminal Radio Resource Control Association Control User traffic Call Control Network stack R-PHY R-DLC Convergence sublayer R-PHY R-DLC IWF Core network stack W.1 W.2 L M E L M E Radio Resource Control Association Control Access Point Control Access Point Control * Off-stack control * May be null if the network is not mobility-enhanced Application Convergence sublayer Core network stack Figure 5a: HIPERLAN/2 layer architecture ETSI TR 101 031 V2.2.1 (1999-01) 26 Core Network Access Point Wireless Terminal Radio Resource Control Association Control User traffic Call Control Network stack R-PHY R-DLC Convergence sublayer R-PHY R-DLC IWF Core network stack W.1 W.2 L M E L M E Radio Resource Control Association Control Access Point Control Access Point Control * Off-stack control * May be null if the network is not mobility-enhanced Application Convergence sublayer Core network stack Figure 5b: HIPERLAN/2 layer architecture The thick black line indicate call control flows and the grey band indicates user data flow. The thin arrowed black lines show the "off stack" control interfaces that allow user provided functions to control Radio DLC functions like (DLC) connection set-up and releasing. The access point acts as a multiplexer that supports mobility of wireless terminals within the access subnetwork serviced by the access point. It also provides information to the core network that is needed to support wireless terminal mobility with the access network. NOTE 1: The functions needed to support roaming between different access networks are outside the scope of the present document. The Radio DLC layer implements a service policy that takes into account such factors as Quality of Service per user connection, channel quality, number of terminal devices and medium sharing with other access sub-networks. It also maintains the quality of service on a virtual circuit basis. Depending on the type of service provided and channel quality, capacity and utilization, the DLC layer will implement a variety of means including FEC, ARQ and flow pacing to optimize the service provided to the (DLC) user. The Convergence Sublayer is defined as a sublayer that generates no protocol but that e.g. provides the wireless DLC layer with the information it needs to perform its QoS management functions as required and functionality for segmentation and reassembly. The Layer Management Entity (LME) of the DLC layer is used to convey traffic contract information and performance requirements between the DLC layer and the higher, connection control functions. NOTE 2: The wireless DLC and PHY layers are intended to be generic enough to support the services of at least those networks listed in subclause 7.1.4 by providing appropriate connection types and service qualities. ETSI TR 101 031 V2.2.1 (1999-01) 27 NOTE 3: The figure above (and figure 4) shows an "Access Point Control" function in the core network. This function may be provided in certain future core networks (e.g. UMTS) or may not be. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.4 Interworking | Radio dependent/core network independent and radio independent/core network dependent parts shall be distinguished. This will minimize the number of different radio specifications and also allows the same radio specifications to be used for a number of core networks. Furthermore, this approach will allow for an independent evolution of access and core networks. This general approach is illustrated in figure 6. Network Convergence sublayer Core Network 1 H/2 DLC H/2 PHY Core Network 2 Core Network 3 Figure 6: HIPERLAN/2 approach The convergence sublayer is a part of the interworking functionality. Interworking functions will be produced for at least IP, ATM and UMTS. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.4.1 IP Interworking | HIPERLAN/2 IP interworking requirements include: Interworking at the IP layer so as to provide a transparent service to the IP service users; mobility must be supported at the IP and the lower (radio) levels. It shall be possible to map IP QoS guarantees, whether it is RSVP, Differentiated Services or another alternative, to the radio DLC layer QoS mechanisms. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.4.2 ATM Interworking | HIPERLAN/2 ATM Interworking requirements include: 1) Interworking at the ATM layer so as to provide a transparent service to the ATM service users; this includes extension of ITU-T Recommendation Q.2931 [4] and the ATM Forum specification UNI 4.0 [7] for signalling and connection set-up and releasing functions. The extensions to ITU-T Recommendation Q.2931 [4] and the ATM Forum specification UNI 4.0 [7] are outside the scope of HIPERLAN/2; these specifications are expected to be developed by the ATM Forum. 2) Interworking between the access point and the ATM switch Resource management functions in support of mobile (as opposed to stationary) terminals. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.4.3 UMTS Interworking | The Universal Mobile Telecommunications System (UMTS) is the European version of IMT-2000 (3rd generation mobile systems). UMTS will incorporate a new generic radio access network, the UMTS Radio Access Network (URAN). The URAN may include several different realizations, of which the UTRAN (UMTS Terrestrial Radio Access Network) is one. The Iu interface forms the boundary between UTRAN and the UMTS core network. By connecting BRAN to the Iu interface, BRAN will form a complimentary realization of the URAN concept for broadband data services. UMTS interworking will provide BRAN with roaming support using the UMTS mobility infrastructure. ETSI TR 101 031 V2.2.1 (1999-01) 28 A BRAN realization of URAN should provide the same logical interface to the higher layers (i.e. layers belonging to the non-access stratum) as UTRAN. Hence, no changes in higher layers should be required. UMTS authentication, security and location management can be used over HIPERLAN/2. UMTS bearer setup requests should be mapped to the corresponding HIPERLAN/2 DLC connection by the convergence layer. A USIM (User Service Identity Module) may be needed in a HIPERLAN/2 terminal supporting UMTS interworking. Handovers within a BRAN subsystem should be invisible to the UMTS core network. Handovers between UTRAN and BRAN, in case of dual mode terminals, should be supported via the core network. The standard shall be specified so that it is attractive to facilitate dual-mode terminals for UMTS and GSM. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.1.5 Addressing | HIPERLAN/2 wireless terminals shall be addressable by their global address (so as to support world-wide and nomadic use). Internally, an access subnetwork may use abbreviated addressing of some kind in order to reduce protocol overhead. Broadcast and multicast mode shall be supported via DLC procedures for sending unacknowledged control and user data. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.2 Mobility support | HIPERLAN/2 shall support: 1) Roaming between access networks (with connection release and (re) set-up). 2) Continuous service while in motion within the contiguous area covered by the access network connected to a given switch or router. The rate of movement to be supported is: 1) 10 m/s linear; 2) 180 deg/sec rotation. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3 Requirements imposed on radio sub-system | |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.1 Radio range | HIPERLAN/2 shall provide a range of 30 m in a typical indoor environment and up to 150 m in a typical outdoor or large open indoor (e.g. large factory hall, airport) environment. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.2 Data rate | HIPERLAN/2 shall provide a peak data rate of at least 25 Mbit/s on top of the PHY layer. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.3 Delay spread | The system shall support rms delay spreads up to 220 ns in a range of different environments incorporating short range indoor, large open space indoor and outdoor environment. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.4 Antennas | The H/2 standard shall support different types of antennas, i.e. omni-directional, directional and smart antennas. The use of smart antennas shall not be precluded by the standard. ETSI TR 101 031 V2.2.1 (1999-01) 29 |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.5 Capacity and coverage | The capacity in terms of bits/s/hect of a HIPERLAN/2 network is limited by the number of RF channels available and the loading of these channels by HIPERLAN/2 networks or other systems operating within radio range of each other. Further, the actual capacity of a HIPERLAN/2 system depends on the protocol overhead, on the ratio between protocol overhead and traffic payload size and on the effective channel isolation. In 95 % of the coverage area (i.e. within the radio range) the MT should be able to provide at least 8 Mbit/s throughput (uplink+downlink data rates) above the PHY layer. In a single operated multicell environment the average system throughput (per AP) should at least be 20 Mbit/s above PHY layer. In 95% of the area the MT should be able to provide at least 4 Mbit/s throughput above the PHY layer. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.6 QoS, user data rate, transfer latency and transfer delay variance | When operating in an environment that does not vary, HIPERLAN/2 systems shall be able to maintain the data rate and QoS values of connections established at connection set up. (For the applicable QoS parameters, see ITU-T Recommendation I.356 [8] and equivalent ATM Forum documents). The following values are provided as guidelines for the Transfer Delay and Delay Variance: 1) Transfer Delay: < 5 msec; 2) Delay Variance: < 1 msec. These figures may not be realizable under all conditions and for all service categories. 1) They are based on the following: since transfer delay and delay variance accumulate along a communications path, these values are reasonable target values that allow additional delay in other network components. 2) The transfer delay of 5 msec allows a wireless terminal time to scan for activity on another channel - e.g. for acquisition of another access point for handover purposes. See also subclause 7.2.1. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.7 Residual errors | |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.7.1 Detected errors | The error detection and correction capabilities of ATM and IP stacks are typically low since they are designed for a basically reliable physical network. HIPERLAN/2 will make a best effort attempt to maintain the QoS of connections over time. However, link conditions and handover procedures may cause cells or packets to be lost or delayed beyond their intended delivery time. In the latter case HIPERLAN/2 may discard such data units. Recovery of this kind of error condition is outside the scope of HIPERLAN/2 and belongs to the higher layers of the protocol stack and/or application level recovery mechanisms. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.7.2 Undetected errors | The residual undetected error rate of HIPERLAN/2 should be in the same range as that of a wired IP or ATM system. This equates to an undetected DSDU error rate of <5 × 10-14 [IEEE 802]. HIPERLAN/2 shall meet these requirements through the use of the appropriate error detection mechanisms. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.3.8 Radio Resource Management | The standard shall support the following features: 1) Automatic Frequency Assignment: Automatic frequency assignment shall be supported, i.e. the system shall adapt to the radio propagation environment and interference conditions. 2) Link adaptation: The system shall be able to handle different interference and propagation environments, with the aim to maintain the QoS for a connection. E.g. for data rate scalability: The system shall be able to operate ETSI TR 101 031 V2.2.1 (1999-01) 30 with multiple modulation alphabets and channel coding rates to enable adaptation to local propagation and interference conditions. 3) Power Control: The output power of the mobile terminal shall be minimized while still maintaining agreed transmission and reception quality. |
3f0194517ce87f71fe87caa6bfe0735b | 101 031 | 7.4 End user requirements | HIPERLAN/2 implementations are targeted at portable applications such as Notebooks and Personal Digital Assistants. This puts constraints of size (PCMCIA Type 2 or 3), cost (should be a fraction of the user device cost) and power consumption (because of host battery limitations). These constraints may impact the functionality provided by the HIPERLAN/2 specification. For example, the wireless terminal adapter may have different modes of operation with different levels of power consumption. These modes of operation may have implications for the specification of the HIPERLAN/2 protocols, e.g. to support the signalling of mode transitions. 7.5 Network management The HIPERLAN/2 Functional Standard shall define Managed Objects for all the major functions and the monitoring of their performance. ETSI TR 101 031 V2.2.1 (1999-01) 31 Bibliography The following material, though not specifically referenced in the body of the present document (or not publicly available), gives supporting information. - ETR 069 (1992): "Radio Equipment and Systems (RES); HIgh PErformance Radio Local Area Network (HIPERLAN), Services and facilities". - ETR 226: "Radio Equipment and Systems (RES); High PErformance Radio Local Area Network (HIPERLAN), Architecture for Time Bound Services (TBS)". - ISO/IEC 7498-1 (1994): "Information technology -- Open Systems Interconnection -- Basic Reference Model: The Basic Model". - CCITT Recommendation E.163 (1988): "Numbering plan for the international telephone system". - CCITT Recommendation E.164 (1988): "Numbering plan for the ISDN era". - ISO/IEC 15802/1 (1995): "Information technology -- Telecommunications and information exchange between systems -- Local and metropolitan area networks -- Common specifications -- Part 1: Medium Access Control (MAC) service definition". - ISO/IEC 8802-2: "Information technology -- Telecommunications and information exchange between systems -- Local and metropolitan area networks -- Specific requirements -- Part 2: Logical link control". - ECMA TR/51 (1990): "Requirements for Access to Integrated Voice and Data local and Metropolitan Area Networks". - Anthony S. Acampora: "An Introduction to Broadband Networks: LANs, MANs, ATM, B-ISDN, and Optical Networks for Integrated Multimedia Telecommunications", Plenum Press, 1994. - D. McDysan, D. Spohn: "ATM - Theory and Application", McGraw-Hill Series on Computer Communications, 1994. - J. McQuillan: "Where are the ATM Applications?", Business Communications Review, November 1993. - CEC Deliverable R2066/LMF/GA1/DS/P/063/b1, UMTS Service Definitions -Issue 3, RACE Project R2066 MONET deliverable 63, December 1994. - CEC Deliverable R2066/LMF/GA1/DS/P/024/b1, UMTS Service constrains and objectives, RACE Project R2066 MONET deliverable 24, December 1993. ETSI TR 101 031 V2.2.1 (1999-01) 32 History Document history V1.1.1 July 1997 Publication V2.2.1 January 1999 Publication ISBN 2-7437-2757-8 Dépôt légal : Janvier 1999 |
a577e34d655048e4de969fdaeecc0250 | 101 075 | 1 Scope | The present document applies to any Base Station System type or part of a Base Station System and co-located equipment and equipment sites, unless otherwise stated. It applies regardless of ownership or responsibility for installation and maintenance of the equipment or network. The document does assume some previous knowledge of the subject matter and in some areas specialist understanding may be required. The present document addresses the following information: - product requirement overview; - equipment sites and installations; - general applicable specifications; - acoustic noise; - construction; - earthing and bonding; - environmental Conditions; - lightning protection; - power supplies; - reliability/Dependability; - specific applicable specifications for product release; - EMC; - type approval. |
a577e34d655048e4de969fdaeecc0250 | 101 075 | 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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] Void [2] 89/336/EEC: "Council Directive Relating to Electromagnetic Compatibility". [3] 92/31/EEC: "Council Directive Amending 89/336/EEC". [4] EN 60721-3-4: "Classification of environmental conditions Part 3: Classification of groups of environmental parameters and their severities, Stationary use at non-weather protected locations". [5] EN 60950: "Safety of information technology equipment". ETSI ETSI TR 101 075 V4.2.0 (2000-05) 7 (GSM 11.22 version 4.2.0) [6] ETS 300 019-1-1: "Equipment Engineering (EE); Environmental conditions and environmental test for telecommunications equipment, Part 1-1: Classification of environmental conditions, Storage". [7] ETS 300 019-1-2: "Equipment Engineering; Environmental conditions and environmental test for telecommunications equipment, Part 1-2: Classification of environmental conditions, Transportation". [8] ETS 300 019-1-3: "Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment: Part 1-3: Classification of environmental conditions, Stationary use at weatherprotected locations". [9] ETS 300 019-1-4: "Equipment Engineering (EE); Environmental conditions and environmental test for telecommunications equipment: Part 1-4: Classification of environmental conditions, Stationary use at non-weatherprotected locations". [10] ETS 300 019-2-1: "Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment, Part 2-1: Specification of environmental tests, Storage". [11] ETS 300 019-2-2: "Equipment Engineering (EE); Environmental conditions and environmental test for telecommunications equipment, Part 2-2: Specification of environmental tests, Transportation". [12] ETS 300 019-2-3: "Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 2-3: Specification of environmental tests, Stationary use at weatherprotected locations". [13] ETS 300 019-2-4: "Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 2-4: Specification of environmental tests, Stationary use at non-weatherprotected locations". [14] ETS 300 119-2: "Equipment Engineering (EE); European telecommunication standard for equipment practice; Part 2: Engineering requirements for racks and cabinets". [15] ETS 300 119-4: "Equipment Engineering (EE); European telecommunication standard for equipment practice, Part 4: Engineering requirements for subracks in miscellaneous racks and cabinets". [16] ETS 300 132-1: "Equipment Engineering (EE); Power supply interface at the input to telecommunications equipment;Part 1:Operated by alternating current (ac) derived from direct current (dc) sources'". [17] ETS 300 132-2: "Equipment Engineering (EE): Power supply interface at the input to telecommunications equipment; Part 2:Operated by direct current (dc)". [18] ETS 300 253: "Equipment Engineering (EE); Earthing and bonding of telecommunications equipment in telecommunication centres". [19] ETS 300 342-2: "Radio Equipment and Systems (RES); Electro-Magnetic Compatibility (EMC) for European digital cellular telecommunications systems (GSM 900 MHz and DCS 1 800 MHz), Part 2: Base Station radio and ancillary equipment". [20] ETR 035: "Equipment Engineering (EE); Environmental engineering; Guidance and terminology". [21] IEC Publication 99-1: "Part 1: Non-linear resistor type gapped surge arrestors for AC systems". [22] IEC Publication 529: "Degrees of protection provided by enclosures (IP Code)". [23] IEC 721-2-1: "Classification of environmental conditions". References: IEC Publication 721 Part 1. [24] IEC Publication 721-2-3 [3]: "Part 2: Environmental conditions appearing in nature. Air pressure". [25] IEC Publication 1024-1: "Protection of structures against lightning, Part 1 general principles". [26] IEC publication 1024-1-1: "Part 1: Guide A - Selection of protection levels for lightning protection systems". ETSI ETSI TR 101 075 V4.2.0 (2000-05) 8 (GSM 11.22 version 4.2.0) [27] [IEC 56 (Secretariat) 383: "Use of failure rate data intended for reliability prediction of components in electronic equipment, -Reference conditions, -Stress models for their conversion".] [28] ISO 1996/1 (1982-09-15): "Acoustics - Description and measurement of environmental noise - Part 1 Basic quantities and procedures". [29] ISO 3461: "Graphic symbols". [30] ISO 3864: "Safety signs and colours". [31] ISO 7779: "Acoustics - Measurement of airborne noise emitted by computer and business equipment". [32] [ISO 9001: "Specification for design/development, production, installation and servicing".] |
a577e34d655048e4de969fdaeecc0250 | 101 075 | 3 Definitions | |
a577e34d655048e4de969fdaeecc0250 | 101 075 | 3.1 Base Station System | Base Station System shall, for the purposes of this document, be defined as: equipment that contains operational radio and associated support elements that conform to the GSM 900 and DCS 1 800 recommendations within a single supporting fixed structure. EXAMPLE: Stand alone radio equipment. As above but combined with digital processing equipment. As above but combined with mains power interfaces. As above but combined with external communications equipment. |
a577e34d655048e4de969fdaeecc0250 | 101 075 | 3.2 Co-located equipment | Co-located equipment shall, for the purposes of this document, be defined as: equipment that is a support element for operational Base Station radio equipment that conforms to the GSM 900 and DCS 1 800 recommendations within a single fixed structure or as a separate unit that is permanently located with the radio equipment. EXAMPLE: Digital processing equipment. Power Supplies. Communications equipment. |
a577e34d655048e4de969fdaeecc0250 | 101 075 | 3.3 Weather protected locations (ETS 300 019-1-3) | A location at which the equipment is protected from weather influences. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.