all | frequencies |
|
|
exhibits | applications |
---|---|---|---|---|---|
manuals |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 |
|
UserManual | Users Manual | 2.73 MiB | ||||
1 |
|
UserManual Safety | Users Manual | 232.49 KiB | ||||
1 | Cover Letter(s) | |||||||
1 | External Photos | |||||||
1 | Internal Photos | |||||||
1 | ID Label/Location Info | |||||||
1 | RF Exposure Info | |||||||
1 | Test Report | |||||||
1 | Test Setup Photos |
1 | UserManual | Users Manual | 2.73 MiB |
Technical Description MINI-LINK 6351 DESCRIPTION P R ELIMIN A R Y 1/22102-HRA 901 17/9 Uen PU1 Copyright Ericsson AB 20122016. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document. P R ELIMIN A R Y 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Contents Contents 1 2 3 3.1 3.2 3.3 3.4 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 5 5.1 5.2 6 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 Introduction Scenarios Radio Link Functions Adaptive Coding and Modulation Transmit Power Control Maximizing Radio Link Throughput Radio Link Compatibility P R ELIMIN A R Y Ethernet Functions Ethernet in Microwave Networks Ethernet Capacity Ethernet Services Quality of Service Ethernet Protection Delay Ethernet Operation and Maintenance Synchronization Functions Network Synchronized Mode Network Synchronization Methods Hardware Management DCN Management Tools and Interfaces Configuration Management Fault Management Performance Management Hardware Management Software Management License Management Security Management 1 3 5 5 7 8 9 11 11 12 13 20 26 26 26 31 31 32 33 35 35 36 41 41 42 44 44 44 45 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Technical Description 8 8.1 8.2 8.3 9 9.1 9.2 9.3 10 51 51 53 53 55 55 55 55 57 Accessories Power Over Ethernet Alignment Camera Commissioning Guide Federal Communications Commission and Industry Canada Notices Technical Specifications Power Supply Requirements Power Consumption Dimensions and Weight P R ELIMIN A R Y 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Introduction 1 Introduction MINI-LINK 6351 is a complete all-outdoor microwave packet radio with the capability of handling Ethernet traffic using frequencies in the 5962 GHz range. MINI-LINK 6351 P R ELIMIN A R Y
One interface for Power over Ethernet (1GE) The packet radio has the following interfaces:
Figure 1 MINI-LINK 6351 17252
One RJ45 interface for local management The hardware is described in Section 6 on page 33. Some functions described in this document are subject to license handling, that is, a soft key is required to enable a specific function. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 1 Technical Description P R ELIMIN A R Y 2 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Scenarios 2 Scenarios Micro RBS Packet Terminal 2G 2G Multiple RBSs Multi standard RBS6000/TCU 3 4 3 2 1 1 3 4 3 2 1 1 O&M O&M E1 / DS1 E1 / DS1 SYNC 2 SYNC 2 SYNC 1 SYNC 1 TR:2A-2B TR:4A-4B TR:3A-3B TR:1A-1B TR:3A-3B TR:1A-1B TR:4A-4B TR:2A-2B USER I/O USER I/O USB O&M USB O&M 10/100/1000 Base-T 4 2 10/100/1000 Base-T 4 2 DC -48V 2A MAX DC -48V 2A MAX
+ DC:2 - + DC:1 -
+ DC:2 - + DC:1 -
10/100/1000 Base-T / 100/1000 Base-X 10/100/1000 Base-T / 100/1000 Base-X Fault Power Oper Sync Fault Power Oper Sync ERICSSON MINI-LINK SP 110 ERICSSON MINI-LINK SP 110 TN TRX CBN FAU1 FAU1 PCU1 Cable shelf Air guide plate 4G 3G 4G 3G 4G Enterprise Ericsson SP Ericsson SP Packet Terminal Packet Terminal Packet Terminal Packet Terminal Towards HRAN/Metro MINI-LINK TN Packet Terminal MINI-LINK LH Packet Terminal P R ELIMIN A R Y Microwave 17258 Using the MINI-LINK product portfolio to build an Ethernet network means that there is a broad range of alternatives to choose from. There is support for high-capacity Ethernet transport with different bandwidth and capacity options over both radio and fixed connections. The products offer the size and capacity to meet the needs of both last mile access and first aggregation point, in a mobile backhaul network. Figure 2 Network Scenario Overview 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 3 Technical Description P R ELIMIN A R Y 4 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Radio Link Functions 3 Radio Link Functions 3.1 Adaptive Coding and Modulation The packet radio operates within the 5962 GHz frequency range, using 4, 16, 32, 64, 128, or 256 QAM, also supporting Adaptive Coding and Modulation
(ACM). Adaptive Coding and Modulation (ACM) enables automatic hitless switching between different ACM profiles, depending on radio channel conditions. Hitless ACM makes it possible to increase the available capacity over the same frequency channel during periods of normal propagation conditions. Code rate and modulation (and thereby capacity) are high during normal radio channel conditions and lower during less favorable channel conditions, for example, when affected by rain or snow. ACM profile switches are hitless, that is, error free. In situations where traffic interruption normally would occur, it is possible to maintain parts of the traffic by switching to a lower ACM profile, using hitless ACM. P R ELIMIN A R Y Figure 3 shows how the capacity changes when the received input signal crosses the receiver threshold for each ACM profile. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 5 Technical Description P R ELIMIN A R Y In order to handle channel variations, the channel conditions are continuously monitored on the Rx side by measurement of Signal to Noise and Interference Ratio (SNIR). When the receiver, based on this data, detects that channel conditions imply a change to the next higher or lower ACM profile, a message is sent to the transmitter on the other side requesting a higher or lower ACM profile. Upon receipt of such request the transmitter starts transmitting with the new ACM profile. Each direction is independent. At demodulation the receiver follows the ACM profile as a slave. When using only Adaptive Modulation, the steps in Figure 3 only differ in terms of modulation. When using ACM, the steps can differ in both coding and modulation, which increases the number of possible steps. Figure 3 Principles of Adaptive Coding and Modulation The ACM profile can also be configured with the maximum ACM profile equal to the minimum ACM profile, and thereby achieving a mode comparable to static mode, where the ACM profile remains unchanged. Hitless ACM is compatible with Automatic Transmit Power Control (ATPC), which is working in a closed loop only in the highest configured ACM profile. In lower ACM profiles the output power is set as high as possible. Note: Hitless ACM requires a license. 6 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Radio Link Functions Buffering Transmit Power Control ACM can influence the design of the buffer dimensioning. In case packet aging is not used, the maximum delay variation time will increase due to that the buffer is configured in bytes and that data will travel at a slower speed during lower ACM profile steps. When packet aging is enabled, the maximum delay variation time will be kept regardless of ACM profile level. This will also ensure that there is no old data in lower priority queues when the ACM profile is increased after a fading situation. ACM can influence the position of the narrowest congestion point in the network, with too small buffers this can have a strong negative impact on utilization and end user TCP performance. To ensure high link utilization and high TCP performance, buffers for TCP traffic should be dimensioned in the area above average Round Trip Time (RTT), which is typically in the area of 100200 ms. P R ELIMIN A R Y The radio transmit power can be controlled in Automatic Transmit Power Control (ATPC) mode, including setting of associated parameters. In Automatic Transmit Power Control (ATPC) mode the transmit power can be increased rapidly during fading conditions and allows the transmitter to operate at less than the maximum power during normal path conditions. The normally low transmit power allows more efficient use of the available spectrum while the high transmit power can be used as input to path reliability calculations, such as fading margin and carrier-to-interference ratio. The transmitter can be turned on or off from the management system. Transmit power Pmax 3.2 outP P min ATPC mode Figure 4 Transmit Power Control 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 16707 7 Technical Description ATPC is used to automatically adjust the transmit power Pout in order to maintain the received input level at the far-end radio at a target value. The received input level is compared with the target value, a deviation is calculated and sent to the near-end to be used as input for possible adjustment of the transmit power. 3.3 Layer Preamble Layer 2 Ethernet frame Layer 1 Ethernet packet Maximizing Radio Link Throughput In ATPC mode, the transmit power Pout varies between a selected maximum level Pmax and a minimum level Pmin. ECO mode is supported, and when ATPC mode is configured it is possible to achieve a power consumption reduction with maintained performance. The maximum bit rate of incoming traffic on the LAN interface can be significantly higher than the maximum bit rate over the radio link. For the radio link to match the frame rate on the LAN interface, it is necessary to increase the throughput on the radio link. This is done by stripping the IFG (interframe gap) and preamble, and optionally by using multilayer header compression on the Ethernet frames. P R ELIMIN A R Y 802.1Q tag
(optional) Start of frame Frame check MAC source destination sequence Ethertype delimiter Payload MAC IFG 16782 Stripping the Preamble, SFD, and IFG Figure 5 Ethernet Packet and Frame Structure On the LAN side, the Layer 2 Ethernet data is encapsulated by a Layer 1 header consisting of an Preamble sequence, an SFD and an IFG. The IFG, preamble and SFD are not needed in the traffic sent over the radio link. The IFG and preamble are stripped from the packet, leaving only the Ethernet Layer 2 frame. A small overhead is added to the frame before it is sent over the radio link. This way the traffic over the radio link consists almost entirely of the payload, making it possible for the radio link to keep the same frame rate as the LAN interface, even though the bit rate is lower. 8 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Radio Link Functions Multi-Layer Header Compression Table 1 512 4%
Frame Type To further increase the frame rate over the radio link, Multi-Layer Header Compression (MLHC) is used on the Ethernet frame. Fields in the header are converted to a hash number, potentially resulting in a significant reduction in the size of the frames sent over the radio link. Traffic Throughput Gain for Different Frame Types when using MLHC The MLHC algorithm inspects the header for Ethernet, IPv4, IPv6, UDP, MPLS
(up to three MPLS labels) and MPLS pseudowire information. See Table 1 for examples of traffic throughput gain (in percent) for different frame types and frame sizes when using MLHC:
Frame Size (Bytes) 128 64 42%
18%
P R ELIMIN A R Y Eth+S-tag+C
-tag Eth+S-tag+C
-tag+IPv4+U DP Eth+S-tag+C
-tag+IPv6+U DP Eth+ MPLS+I Pv4 Eth+C-tag+S
-tag+3*MPLS
+L2 PW Eth+C-tag+S
-tag+3*MPLS
+L3 PW Radio Link Compatibility 1500 1%
143%
278%
100%
89%
43%
88%
13%
32%
61%
10%
14%
N/A N/A 8%
3%
4%
7%
2%
3%
4%
3.4 MINI-LINK 6351 is only hop compatible with another MINI-LINK 6351. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 9 Technical Description P R ELIMIN A R Y 10 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions 4 Ethernet Functions 4.1
Synchronous Ethernet, see Section 5.2 on page 31. Ethernet Performance Counters, see Section 7.5.3 on page 43. Ethernet in Microwave Networks In addition to the Ethernet functions described in the following sections, the following related functions are also available:
The packet radio is targeting multiple applications and network environments with the embedded Ethernet capabilities. For information about the supported Ethernet services, see Section 4.3 on page 13. Compared to other transmission technologies, a microwave link can be characterized as a limited bandwidth connection. This implies that microwave equipment must be designed to enable maximum packet payload throughput in the available bandwidth over the radio interface. The following features improve the link efficiency:
P R ELIMIN A R Y For connections with limited bandwidth it is important to prioritize high priority packets when a connection is congested. Adaptive modulation seeks continuously to use the modulation alternatives that will maximize throughput under different conditions. Adaptive Modulation Low Residual BER Quality of Service Microwave links operate with large fade margins and forward error correction resulting in low residual BER level, typically 10-12. Header Compression The maximum bit rate of incoming traffic on the LAN interface can be significantly higher than the maximum bit rate over the radio link. To maximize the throughput on the radio link, parts of the Ethernet frame is removed and the remaining headers are compressed before it is sent over the radio link. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 11 Technical Description Ethernet WAN Buffer The WAN port buffer has been designed to handle burst and congestion in order to provide a high link utilization and goodput for high-speed data traffic. This means that queues configured to handle delay variation sensitive traffic such as synchronization traffic, shall be configured to be very short. Since extensive buffering has a negative impact on frame delay variation, it is important to have the possibility to configure buffer/queue size for different traffic classes independently. LAN port buffers are designed to be very small in order to keep delay variation as small as possible, whereas WAN port buffers are larger, to enable handling of congestion at the WAN port. Congestion at the WAN port can occur when the WAN port link speed is lower than the LAN port link speed. In contrast, for traffic queues for less delay variation sensitive traffic the Transmission Control Protocol/Internet Protocol (TCP/IP) has a congestion avoidance mechanism that is based on buffer utilization. In order to provide a high link utilization and high TCP goodput, queues configured to handle this type of traffic needs to be in the area of hundreds of milliseconds at the smallest congestion point, equivalent to the network end-to-end Round-Trip time. P R ELIMIN A R Y The ethernet capacity depends on the configuration of the NE. Ethernet Capacity Table 2 Ethernet Capacity Layer 1 Line Capacity (Mbps) ACM Profile CS (MHz) 64 QAM 32 QAM 16 QAM 4 QAM ACM 1000 1000 981 490 128 QAM 1000 250 200 4.2 64 QAM 32 QAM 16 QAM 4 QAM 1000 980 784 391 12 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions ACM Profile CS (MHz) 150 Layer 1 Line Capacity (Mbps) ACM 128 QAM 64 QAM 1000 869 724 32 QAM 50 382 191 100 385 481 578 673 770 289 579 4 QAM 4 QAM 64 QAM 16 QAM 32 QAM 64 QAM 16 QAM 128 QAM 256 QAM 128 QAM 256 QAM P R ELIMIN A R Y Ethernet services according to MEF (Metro Ethernet Forum) specifications are supported. Figure 6 shows a basic model for Ethernet services. The Ethernet service is provided by Metro Ethernet Network (MEN) provider. The Customer Edge (CE) and MEN exchange service frames across the User Network Interface (UNI). Ethernet Services 32 QAM 16 QAM 4 QAM 334 286 238 190 95 4.3 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 13 Technical Description User network interface UNI User network interface UNI Customer Edge Figure 6 Ethernet Service Model 12530
Point-to-Point EVC:
Based on Ethernet Virtual Connections (EVCs), the following service types are supported:
Edge Customer Metro Ethernet Network P R ELIMIN A R Y Ethernet Virtual Private LAN (EVPLAN) service Ethernet Virtual Private Line (EVPL) service Ethernet Private LAN (EPLAN) service Ethernet Private Line (EPL) service An EVC is an instance of an association of two or more UNIs. It performs two functions:
The LAN port can be used as a UNI, supporting up to 16 EVCs.
Multipoint-to-Multipoint EVC:
4.3.1 Ethernet Virtual Connection
Connects two or more customer sites (UNIs) enabling the transfer of Ethernet service frames between them. The rules under which a service frame is delivered to the destination UNI are specific to the particular service definition. Prevents data transfer between customer sites that are not part of the same EVC. Two types of EVCs are supported:
Point-to-Point EVC (E-Line) 14 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions
Multipoint-to-Multipoint EVC (E-LAN) Point-to-Point EVC (E-Line) In a Point-to-Point EVC, also known as E-Line, exactly two UNIs are associated with one another through the EVC. Service frames are transferred between them. Figure 7 illustrates two Point-to-Point EVCs. Edge EVC2 EVC1 Customer Metro Ethernet Network P R ELIMIN A R Y Customer Customer Edge In a Multipoint-to-Multipoint EVC, also known as E-LAN, two or more UNIs are associated with one another through the EVC. It allows unicast, broadcast and multicast service frames to be transferred from one ingress UNI to one or more egress UNIs. Figure 8 illustrates a Multipoint-to-Multipoint EVC. Multipoint-to-Multipoint EVC (E-LAN) 12566 Edge Customer Edge Figure 7 Point to Point EVC Metro Ethernet Network Customer Edge Figure 8 Multipoint to Multipoint EVC 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Customer Edge 12567 15 Technical Description 4.3.2 Ethernet Private Line Customer Edge Edge Customer The EPL is a type of Ethernet service based on a Point-to-Point EVC. It is a point-to-point connection between the packet radio and a remote network element, as shown in Figure 9. All Ethernet traffic ingress the UNI is mapped into a single EVC and transported through the Metro Ethernet Network. Metro Ethernet Network P R ELIMIN A R Y Basic error checking of the Ethernet frames is performed (for example, checking FCS, wrong Ethernet format, undersized packets or oversized packets). Rate limiting is used to police the ingress Ethernet traffic from the different subscribers to make it possible to meet the agreed Service Level Agreements (SLA). EPL is a port level service so there is no need for the customer and provider to negotiate things like VLAN to be used. All ingress frames from one UNI will be delivered to the other UNI without any modification to the packet. The following functions are supported to implement EPL:
12531 Drop non-conforming traffic or remark them with lower priority. Priority is used to make it possible for high priority packets to bypass low priority packets in buffers.
Figure 9 EPL 4.3.3 Ethernet Virtual Private Line The EVPL is an Ethernet service similar to the EPL, but EVPL allows service multiplexing at the UNI. This means that multiple EVCs can be accessed by the subscriber from the UNI. Furthermore, the different EVCs one can access at a particular UNI can be routed to different part of the network independently. 16 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions An example of EVPL is shown in Figure 10. Customer Edge Figure 10 EVPL Service Edge Customer Metro Ethernet Network P R ELIMIN A R Y Basic error checking of the Ethernet frames is performed (for example, checking FCS, wrong Ethernet format, undersized packets or oversized packets). Customer and service provider must agree on the mapping of different C-VLANs into the different EVCs. The mapping of C-VLAN to EVC can be one to one or many to one. Frames that arrive at the UNI with C-VLAN ID not recognized by the service provider will be dropped at the UNI. The following functions are supported to implement EVPL:
It is possible to have multiple active EVPL services. The number is limited to 16 EVCs per packet radio. The different Ethernet services can be routed in different directions in the network. Rate limiting is used to police the ingress Ethernet traffic from the different subscribers to make it possible to meet the agreed Service Level Agreements (SLA). 12533 Drop non-conforming traffic or remark them with lower priority. Priority is used to make it possible for high priority packets to bypass low priority packets in the buffers.
4.3.4 Ethernet Private LAN An EPLAN provides LAN-type connectivity between multiple subscriber sites through dedicated UNIs. An EPLAN service is shown in Figure 11. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 17 Technical Description Customer Edge Figure 11 EPLAN Metro Ethernet Network Edge Customer P R ELIMIN A R Y Basic error checking of the Ethernet frames is performed (for example, checking FCS, wrong Ethernet format, undersized packets or oversized packets). Rate limiting is used to police the ingress Ethernet traffic from the different subscribers to make it possible to meet the agreed Service Level Agreements (SLA). EPLAN is a port level service so there is no need for the customer and provider to negotiate things like VLAN to be used. The mapping of C-VLAN to EVC can be one to one or all to one. Frames that arrive at the UNI with C-VLAN ID not recognized by the service provider are dropped at the UNI. The following functions are supported to implement EVPL:
Drop non-conforming traffic or remark them with lower priority. 14076 Priority is used to make it possible for high priority packets to bypass low priority packets in the buffers.
4.3.5 Ethernet Virtual Private LAN The Ethernet Virtual Private LAN (EVPLAN) provides LAN-type connectivity between multiple subscriber sites through multiplexed UNIs. With a multiplex UNI, a particular customer site has access to multiple EVCs with that single UNI. The different EVCs one can access at a particular UNI can be routed to different parts of the network independently. 18 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions It is possible to have multiple active EVPLAN services. The number is limited to 16 EVCs per packet radio. The different Ethernet services can be routed in different directions in the network. The following functions are supported to implement EVPLAN:
Maintenance Domains Drop non-conforming traffic or remark them with lower priority. Priority is used to make it possible for high priority packets to bypass low priority packets in the buffers. Rate limiting is used to police the ingress Ethernet traffic from the different subscribers to make it possible to meet the agreed Service Level Agreements (SLA). Basic error checking of the Ethernet frames is performed (for example, checking FCS, wrong Ethernet format, undersized packets or oversized packets). P R ELIMIN A R Y MDs are hierarchal and as such, MDs of the same type do not overlap each other, for example, two MDs of the same level do not overlap each other. However, different MD types from different levels may overlap, for example, a Customer MD may overlap multiple Service Provider MDs, but the Customer MD cannot overlap another Customer MD. A Maintenance Domain (MD) is defined as a network or sub-network, at the Ethernet level, within which OAM frames are exchanged. An MD determines the span of an OAM flow, across network administrative boundaries. There are the following three types of MDs:
Network Operator MD Service Provider MD Customer MD
4.3.6 An MD consists of the following components:
Maintenance Entity (ME) An OAM entity that requires management.
Maintenance Domain (MD) A management space on a network.
Maintenance Association (MA) A group of MEs that belong to the same service inside a common MD.
Maintenance End Point (MEP) An OAM reference point that can initiate and terminate OAM frames, and that reacts to diagnostic OAM frames. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 19 Technical Description
Maintenance Intermediate Point (MIP) An OAM reference point that reacts to diagnostic OAM frames initiated by MEPs.
MD Level A way of distinguishing which MEs belong to the same MD. All MEs belonging to the same MD share the same MD Level. MINI-LINK Customer Network Element Customer Other Network P R ELIMIN A R Y 15527 Maintenance Domain (MD) Maintenance Association (MA) Maintenance End Point (MEP) Maintenance Intermediate Point (MIP) Figure 12 Ethernet Service OAM Network Overview 4.4 Quality of Service Quality of Service (QoS) is a set of mechanisms that makes it possible to prioritize Ethernet frames depending on traffic type, and to make sure that the capacity is sufficient to guarantee a congestion-free network. QoS is an alternative to overprovisioning the network. A network is logically separated in an operator domain and one or more customer domains, as in the example in Figure 13. 20 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions Figure 13 Customer and Operator Domains The priority of a frame in an end-to-end Ethernet connection can be different in different parts of the network. Customers set the priority to use in their domains, and the operator sets the priority to use in the operator domain. Figure 14 shows an overview of the QoS mechanisms that the packet radio supports. The following subsections describe the QoS mechanisms. Customer Domain Operator Domain Customer Domain Customer Priority Priority Customer Operator Priority P R ELIMIN A R Y 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 21 Technical Description Frame ingress INGRESS Queueing Tail dropping
WRED EGRESS Frame dropping Classification Marking Policing Trusted customer priority Mapping tables PCP MPLS DSCP Default priority Frame dropping Operator priority Switching Classification disabled or no trusted customer priority Mapping operator priority to priority queue P R ELIMIN A R Y Ethernet egress port Queueing
Aging Shaping buffer Frame dropping Scheduling Mapping table Priority queue 7 Priority queue 6 Priority queue 5 Priority queue 4 Priority queue 3 Priority queue 2 Frame egress Shaping Priority queue 1 Priority queue 0 Figure 14 Overview of the QoS Mechanisms In addition to the QoS mechanisms above, the packet radio also supports storm protection, which provides protection against broadcast and multicast storms. MINI-LINK 6351 supports multicast, unicast, and broadcast frames, and supports frames with a size up to 9,216 bytes (Jumbo Frames). 22 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions MINI-LINK 6351 supports priority handling according to IEEE802.1Q 2005 and IEEE802.1D 2004. In a network, it is important to only use one set of priority definitions (for example, IEEE 802.1D 2004). Otherwise, the handling of traffic types can differ between parts of the network in a non-predictable way.
Classification
MPLS TC value in the MPLS header The classification mechanism also supports the following types of combined customer priority extraction:
The classification mechanism extracts customer priority in frames that enter the operator domain. The classification mechanism can extract the following types of customer priority:
IPv6 DSCP value in the IP header IPv4 DSCP value in the IP header PCP value in the C-tag or S-tag of the Ethernet header P R ELIMIN A R Y IPv4 and IPv6 headers in that priority order The marking mechanism sets the operator priority to the default priority in the following cases:
If a frame contains trusted customer priority, the marking mechanism can use the customer priority together with a mapping table to set the operator priority.
MPLS headers, IP headers (both IPv4 and IPv6), and Ethernet headers, The marking mechanism sets the operator priority. Marking 4.4.1 4.4.2
the classification mechanism is disabled no trusted customer priority included in the frame 4.4.3 Policing The policing mechanism makes sure that a customer does not use more than the allowed resources in a network. The policing mechanism limits the input bit rates based on a bandwidth profile. The bandwidth profiles support the MEF concepts Committed Information 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 23 Technical Description Rate (CIR), Committed Burst Size (CBS), Excess Information Rate (EIR), and Excess Burst Size (EBS). The policing mechanism drops excess traffic if the bit rate reaches the configured maximum bit rate.
Per UNI Per EVC Per UNI + CoS The policing mechanism supports bandwidth profiles for MEF services in one of the following ways:
Per EVC + CoS Mapping Operator Priority to Priority Queue The Ethernet egress port has eight priority queues (also known as Traffic Classes (TCs)). The mechanism for mapping operator priority to priority queue uses a mapping table to forward frames to the correct priority queue. To handle temporary link congestion, the Ethernet egress port has a buffer. The priority queues share the buffer capacity. P R ELIMIN A R Y A combination of queue management mechanisms is often used to get the required behavior. The queuing mechanism supports the following queue management mechanisms for the priority queues:
Weighted Random Early Detection (WRED) Tail dropping Queuing Aging
4.4.4 4.4.5 4.4.6 Scheduling The scheduling mechanism handles congestion by emptying the priority queues according to one or both of the following algorithms:
Strict Priority (SP)
Weighted Fair Queuing (WFQ) The scheduling mechanism can be set up to work with one set of high-priority SP queues, one set of WFQ queues, and optionally one low-priority SP queue, as in the example in Figure 15. 24 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions Ethernet egress buffer Priority queue 7 Empty first Empty last Serve 10%
Serve 20%
Serve 30%
Serve 40%
Empty third WFQ queues Empty second Priority queue 0 Priority queue 1 Priority queue 2 Priority queue 3 Priority queue 4 Priority queue 5 Priority queue 6 Low-priority SP queue High-priority SP queues P R ELIMIN A R Y Number of WFQ queues Number of high-priority SP queues 8 0 2 3 3 4 Table 3 Supported Combinations of SP and WFQ Priority Queues The number of queues of each type is configurable (see Table 3). Figure 15 Example of Combined SP and WFQ Scheduling 0 8 6 5 4 3 0 0 0 0 1 1 Number of low-priority SP queues 4.4.7 Shaping The shaping mechanism enforces a bit rate that is lower than the line rate of the physical interface. The mechanism buffers excess frames and schedules them for later transmission. Shaping results in a smoother frame output bit rate. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 25 Technical Description 4.4.8 Storm Protection The storm protection mechanism protects other parts of the network from being affected by flooding from broadcast or multicast traffic at a very high bit rate. 4.5 4.5.1 4.6 4.7 4.7.1 Rapid Spanning Tree Protocol Ethernet Protection The packet radio only supports storm protection on EVC, not on the port. The packet radio supports the Rapid Spanning Tree Protocol (RSTP) according to the standard IEEE 802.1D (2004). Storm protection can be activated per EVC to reduce unwanted or hostile traffic. If the limit is reached, additional bits are discarded until the bit rate is below the specified threshold. The RSTP mechanism adapts to changes in the physical network topology
(that is, links going down and coming up) faster than the traditional STP variant. The STP variant takes a minute to adapt to a change, while the RSTP adapts in less than a second. P R ELIMIN A R Y Delay Typical delay performance per link for priority traffic is <100 s. Ethernet Operation and Maintenance This section describes O&M capabilities related to the Ethernet application. The packet radio supports the Ethernet link layer OAM based on the IEEE 802.3ah specification, which enables service providers to monitor and troubleshoot a single Ethernet link. The primary benefits of IEEE 802.3ah are that it enables the service provider to monitor a link for critical events and then, if necessary, put the remote device into loopback mode in order to do a test on the link. Ethernet Link OAM The following IEEE 802.3ah features are supported:
Discovery Identifies devices in the network and their OAM capabilities. It uses periodic OAM Protocol Data Units (PDUs) to advertise OAM mode, configuration, and capabilities; to advertise PDU configuration; and platform identity. 26 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04
Ethernet Functions Link Monitoring Detects and indicates link faults under a variety of conditions and uses the event notification OAM PDU to notify the remote OAM device when it detects problems on the link. Remote Failure Indication Notification of an Ethernet link failure to or from far end for an NE in operation. Ethernet Service OAM Ethernet Service OAM is used to manage networks comprising of multiple LANs. It supports fault management on Ethernet links, according to IEEE 802.1Q 2011, and performance management according to ITU Y.1731. Ethernet Service OAM can be used in both Customer mode and Provider mode, if Ethernet Service OAM PDUs are C- or S-VLAN tagged, and can be used in LAG and RSTP/MSTP scenarios. Remote Loopback Puts the remote link partner into loopback mode so that every frame received is transmitted back on the same port. This is used to ensure the quality of links during installation or troubleshooting. P R ELIMIN A R Y Other Network MINI-LINK Customer 4.7.2 Customer Network Element Maintenance Domain (MD) Maintenance Association (MA) Maintenance End Point (MEP) Maintenance Intermediate Point (MIP) Figure 16 Ethernet Service OAM Network Overview 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 15527 27 Technical Description 4.7.2.1 Ethernet Service OAM for Fault Management The four main Ethernet Service OAM for FM functions are as follows:
4.7.2.2 Ethernet Service OAM for Performance Management
Loopback Loopback is a troubleshooting tool that verifies the connectivity of a MEP with linked MEPs and linked Maintenance Intermediate Points (MIPs). Remote Defect Indication An MEP uses Remote Defect Indication
(RDI) to communicate with linked MEPs that a fault has occurred, usually that CCM confirmation were not received. The RDI is an indication that a fault has occurred either at the far-end MEP or between the two MEPs. Continuity Check Monitoring Continuity Check Monitoring detects service interruption between MEPs. Continuity Check Messages (CCMs) are sent from one MEP to another, enabling MEPs to locate other MEPs. CCM confirmation can also be requested by an MEP from a linked MEP, to ensure that the CCMs are sent and received without fault. The CCM intervals can be set at 3.3 ms, 10 ms, 100 ms, 1 s, 10 s, 1 min, or 10 min. P R ELIMIN A R Y Linktrace Linktrace is a bidirectional continuity check used for fault localization. When a Linktrace Message (LTM) is sent to a destination MEP or MIP, a Linktrace Reply (LTR) is expected from all the intermediate MIPs along the path to the destination and from the destination MEP or MIP itself. Missing or misordered LTRs point out the location of a fault in an efficient way. Throughput is a measurement on the basis of the Loop Back Message
(LBM) and Loop Back Response (LBR) messages. The throughput is measured by sending frames at an increasing rate (up to the theoretical maximum), graphing the percentage of received frames, and reporting the rate at which frames start being dropped. In general, this rate is dependent on the frame size. Performance management as defined by ITU Y.1731 is supported. The ITU Y.1731 standard specifies the following features:
Up to 90 Mbps of throughput testing traffic can be generated. Delay Measurement (DM) can be used for on-demand OAM to measure frame delay and frame delay variation. Frame delay and frame delay variation measurements are performed by sending periodic frames with DM information to the peer Maintenance End Point (MEP), and receiving frames with DM information from the peer MEP during the diagnostic interval. Each MEP can perform frame delay and frame delay variation measurement. When a MEP is enabled to generate frames with DM information, it periodically sends frames with DM information to its peer MEP in the same ME. When a MEP is enabled to generate frames with DM 28 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Ethernet Functions information, it also expects to receive frames with DM information from its peer MEP in the same ME.
Note: LM can be performed in two ways: single-ended LM and dual-ended LM. The radio only supports single-ended LM. A MEP sends frames with DM request information to its peer MEP, and receives frames with DM reply information from its peer MEP to perform two-way frame delay and two-way frame delay variation measurements. The Protocol Data Unit (PDU) used for DM request is Delay Measurement Message (DMM). The PDU used for DM reply is Delay Measurement Response (DMR). Single-Ended Loss Measurement (LM), including Loss Measurement Message (LMM) and Loss Measurement Response (LMR), is used to collect counter values applicable to ingress and egress service frames, where the counters maintain a count of transmitted and received data frames between a pair of MEPs. single-ended LM is used for on-demand OAM. In this case, a MEP sends frames with LM request information to its peer MEP and receives frames with LM reply information from its peer MEP to perform loss measurement. P R ELIMIN A R Y Average, maximum and minimum measured round trip delay of the Average, maximum and minimum measured round trip Inter Frame Average measured in one way frame loss ratio forward direction Total frames sent and received in forward direction Delay and delay variation measurements:
Frame loss measurements:
Delay Variation (IFDV) The radio supports storing a large amount of Performance Measurement (PM) data, including the following:
interval
Average measured in one way frame loss ratio reverse direction Total frames sent and received in reverse direction 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 29 Technical Description P R ELIMIN A R Y 30 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Synchronization Functions 5 Synchronization Functions 5.1 Network Synchronized Mode By default, the packet radio works in Free Running mode. In this mode, the packet radio is not a part of the synchronization network, and does not maintain a SEC. The packet radio can also be configured to work in Network Synchronized mode where it maintains a SEC and distributes synchronization and synchronization quality level status according to ITU-T G.8261, G.8262, and G.8264. Network Synchronized mode makes it possible to build a synchronized network where all the NEs are synchronized to the same source. Figure 17 shows an example of a network where the synchronization information is carried to all the NEs through an assigned path. In case of link failures, the synchronization can be reestablished using the unassigned synchronization paths. P R ELIMIN A R Y Active synchronization path Inactive synchronization path NE NE NE NE NE NE Figure 17 Master-Slave Synchronized Network 9531 In this mode, the packet radio uses the Node Clock on all the protocol layers generated in the node. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 31 Technical Description 5.2 Network Synchronization Methods The packet radio supports the following methods for network synchronization:
Synchronization over radio link Transparent Clock (TC) according to the IEEE 1588-2008 standard. It is possible to configure one or more of the above methods. If more methods are used, a general rule is to configure the packet radios on either side of a hop so that one uses Ethernet and the other uses radio link as sync source. If TC is used, it is recommended to enable SyncE. Synchronous Ethernet (SyncE) according to the ITU-T G.8261, G.8262, and G.8264 standards. P R ELIMIN A R Y 32 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Hardware 6 Hardware The packet radio is an antenna sphere painted light gray, with a wall mount and arm painted dark gray. MINI-LINK 6351 P R ELIMIN A R Y Figure 18 Mechanical Design The horizontal deflection angle (how much the antenna can be turned sideways) depends on the vertical deflection angle (how much the antenna is turned up or down). 17252 Vertical deflection angle 0
65
Maximum horizontal deflection angle 80
68
1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 33 Technical Description External Interfaces 1 _ 1 _ 1 0 9 0 3 1 5 P S C D D 1 2 4 3 P R ELIMIN A R Y Description Operation & Maintenance socket for local O&M cable. Test port for antenna alignment. Slot for RMM. Socket for PoE cable. The packet radio is environmentally sealed, so that it can withstand most conditions. The antenna, O&M cover, and PoE connection are sealed. Figure 19 External Interfaces, Mechanical Design Item 1 2 3 4 17255 34 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management Management DCN The packet radio supports L2 DCN, and needs to be configured as a host on a LAN with an IP address, a subnet mask, and a default gateway. The packet radio provides DCN over VLAN for transport of the O&M data. Figure 20 illustrates the DCN configuration. LAN CPU Packet Radio P R ELIMIN A R Y Internal DCN VLAN Switch Radio Terminal The remote supervision of the packet radio can be realized with a connection over the line side or the Radio Link in-band DCN management VLAN. The DCN is carried in-band on the traffic cable or the Radio Link on a separate VLAN. This VLAN is terminated in the packet radio. Figure 20 DCN over VLAN IP Services 7 7.1 7.1.1 The following standard external IP network services are supported:
All clocks, used for example, for time stamping alarms and events, can be synchronized with a Network Time Protocol (NTP) server. NTP authentication is supported. Secure File Transfer Protocol (SFTP) is used as a file transfer mechanism for software upgrade. An embedded Node GUI, including an overview of the and status information. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 35 Technical Description Packet Radio NTP DCN CLI SFTP Site LAN Figure 21 Management Tools and Interfaces IP Services Ethernet Switch P R ELIMIN A R Y an Ethernet management interface (not connected to the router) for local access a DCN for local and remote access (see Section 7.1 on page 35) Command Line Interface (CLI) The management tools can connect to the packet radio using one of the following management interfaces:
The packet radio provides two management tools:
Node GUI
7.2 36 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management ServiceOn Element Manager Ericsson IP Transport NMS CLI Local Port CLI Figure 22 Management Tools and Interfaces Site LAN DCN Ethernet Switch Packet Radio P R ELIMIN A R Y configuration management performance management software management fault management The CLI and the Node GUI can be used, for example, for the following management tasks:
The configuration management features of the Node GUI are limited compared to configuration management features of the CLI. 7.2.1 CLI A CLI provides commands for on-site installation, configuration management, fault management, performance management, and software upgrade. It is also used to configure the traffic routing function, protection and DCN. The CLI is used for local management, that is the packet radio is accessed locally, on the unit, by connecting a PC to the Ethernet Management Port, with a cable. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 37 7.2.2 7.2.3 Technical Description This CLI is similar to Ciscos industry standard router configuration and is accessed from a Command Prompt window using SSH. Node GUI The packet radio can also be accessed over the site LAN. In this case, a VLAN capable Ethernet switch has to be used, and the port where the PC is connected should be configured to be on the same VLAN as set up for the in-band DCN. The packet radio has a built-in GUI that provides tools for on-site installation and software upgrade. The Node GUI is used for local management, that is the packet radio is accessed locally, on the unit, by connecting a PC to the Ethernet Management Port, with a cable. The packet radio can also be accessed over the site LAN. In this case, a VLAN capable Ethernet switch has to be used, and the port where the PC is connected should be configured to be on the same VLAN as set up for the in-band DCN. P R ELIMIN A R Y The packet radio is managed remotely using ServiceOn Element Manager. ServiceOn Element Manager provides functions such as FM, CM, AM, PM and SM based on the recommendations from Open Systems Interconnect (OSI) model. The CM functionality is either embedded or provided using dedicated Local Managers and Element Managers. ServiceOn Element Manager can also be used to mediate FM, PM and Inventory data to other management systems. ServiceOn Element Manager Configuration Management Performance Management The system provides:
Fault Management Security Management Remote Software Upgrade
ServiceOn Element Manager provides element management services across a whole network. Network elements can be managed on an individual basis, providing the operator with remote access to several network elements, one by one. ServiceOn Element Manager supports a real time window reporting alarms and events from the managed network elements. It is possible to filter alarms on the basis of assigned resources and alarm filtering criteria. 38 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management 7.2.4 Ericsson IP Transport Network Management System 7.2.5 The Ericsson IP Transport Network Management System (IPT NMS) provides full management across a whole network through one easy to use browser. IPT NMS manages end-to-end L1, L2, and L3 services across TDM, Ethernet, and IP, IPT NMS also manages all standard Ethernet services. SNMP
General NE information data:
The packet radio supports fetching the following types of information:
IPT NMS is compatible with existing NMS hardware and operating systems, and easily integrates third-party network equipment. The packet radio has support for Simple Network Management Protocol
(SNMP) versions SNMPv1, SNMPv2c, and SNMPv3. This SNMP support enables integration with any SNMP-based network management system (NMS). The SNMP interface of the packet radio uses standard MIBs and enterprise MIBs. P R ELIMIN A R Y Historical alarms and events Performance counter values Alarm and event data:
Configuration data:
Performance data:
Environmental Inventory Basic
Radio link data Notifications from the packet radio are sent using SNMP v1, SNMP v2c, and SNMP v3 traps. 7.2.6 MINI-LINK Configuration Generator MINI-LINK Configuration Generator (CG) is an offline tool for simplifying the Network Rollout (NRO) process. MINI-LINK CG uses radio link planning data and transport planning data as input to create configuration scripts for NEs, see Figure 23. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 39 Technical Description MINI-LINK CG is compatible with MINI-LINK 6351 2.4 and later. MINI-LINK CG can combine radio link planning data and transport planning data to generate one common CLI configuration script. This enables an installation technician to configure each NE by deploying the script, rather than by performing configurations step-by-step in a graphical user interface. MINI-LINK CG provides offline validation to reduce configuration errors and does not need connect to the NE to create the configuration scripts The configuration scripts generated by MINI-LINK CG can be deployed to separate NEs through SOEM, through a CLI session, or by placing them on the RMMs in the packet radio (see Section 7.3.3 on page 41). MINI-LINK CG takes Network Configuration Files (NCFs) as input and generates CLI scripts for the NE included in the NCF. An NCF is an XML document that is compliant with a certain XML schema, called the NCF schema. MINI-LINK CG can also combine planning data in the NCF format with templates, and then merge and convert the NCFs to create deployable CLI configuration scripts for selected sites and NEs. P R ELIMIN A R Y MINI-LINK Configuration Generator (CG) Integrate and create File-based Network Installation technician CLI Scripts Network operator Rollout u b i r t s D
) L M X
(
e c a f r e n o t i t i Integration engineer t n I F C N p i r c S I L C Planning and Export Microwave Planning MINI-LINK Network/site engineer Transport Planning MINI-LINK Figure 23 MINI-LINK CG Overview 15804 For further information about MINI-LINK CG, see MINI-LINK CG documentation. 40 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management 7.3 Configuration Management Configuration management operations are performed using CLI or an XML-based protocol towards a ServiceOn Element Manager (SOEM). 7.3.1 7.3.2 7.3.3 Configuration File Automatic Rollback The configuration file is stored both in the RMM and in a flash memory on the packet radio. If a packet radio needs to be replaced, the RMM from the faulty packet radio can be inserted in the new packet radio. If a packet radio or an RMM is replaced, the configuration file identity of the RMM and flash memory are compared on power up. If the configuration file identity differs, the configuration file on the RMM is used. P R ELIMIN A R Y Unless a command to save the changes is entered within 15 minutes, the configuration automatically reverts to the state it was in before the changes were made, An automatic rollback function for the configuration is available. When this function is enabled, most changes to the configuration are temporary (to avoid malfunction, changes that has to do with the internal configuration database, licenses, software, and users are always saved). CLI scripts that are located on the RMM are executed automatically when the packet radio is powered up. MINI-LINK RMM Writer is needed to write scripts to the RMM. MINI-LINK RMM Writer is part of MINI-LINK Configuration Generator. Scripts on RMM 7.4 Fault Management All software and hardware in operation is monitored by the control system. The control system locates and maps faults to replaceable HW parts. The practical fault management is based around alarm and event notifications. Reporting of some alarms is turned off by default. Furthermore, alarm filter persistency is set for some types of alarms by default. This may prevent reporting of some types of alarms by default. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 41 Technical Description Alarm notifications can be enabled or disabled for the entire system (terminal). Disabling alarm notifications means that no new alarm or event notifications are sent to the management system. For a list of replaceable HW parts, see Section 7.6 on page 44. 7.5 7.5.1 7.5.2 General Radio Link Performance Counters Performance Management Fault management for Ethernet is described in Section 4.7 on page 26. The purpose of Performance Management for the packet radio is to monitor the performance of the Ethernet interface and the RF interface. Performance data is stored in a volatile memory, so that a restart will lose all gathered data. P R ELIMIN A R Y Data stored in the NE The counters for the current 15 minutes and the previous 9615 minutes The counters for the current 15 minutes and the previous 9615 minutes Counting Intervals 15 minutes intervals 15 minutes intervals The following table shows the performance counters that are monitored:
Stored in the NE Performance counter RF input power RF output power Table 4 Performance Counters, their Respective Counting Intervals, and the Type of Data 42 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management Table 4 Performance Counters, their Respective Counting Intervals, and the Type of Data Stored in the NE Performance counter Adaptive Modulation states Counting Intervals 15 minutes (default) or 24 hours intervals G.826 The following performance counters are used by G.826:
Errored Seconds (ES)
Severely Errored Seconds
(SES)
Background Block Error
(BBE) (only structured interfaces)
Unavailable Seconds (UAS)
Elapsed time
Background Block Data stored in the NE The seconds spent in each modulation as well as the number of changes between modulations are counted
Continuous data
The current 15 minutes and the previous 9615 minutes
The current 24 hours and the previous 3024 hours Continuous (default), 15 minutes, or 24 hours intervals P R ELIMIN A R Y Average, Max, and Min bandwidth Bandwidth utilization histogram Bandwidth Utilization Measures bandwidth utilization per port or per Traffic Class on the WAN port. The following Ethernet performance counters are available:
Queuing Delay Measures queuing delay per port or per Traffic Class on the WAN port. 7.5.3 Ethernet Performance Counters
Average, Max, and Min delay Delay histogram RMON Performance counters as specified in IETF RFC 2819.
Separate counters for LAN and WAN ports RMON counter statistics are sampled every 900 seconds (15 minutes) and stored in 96 intervals. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 43 Technical Description IfStatistics Counters Performance counters as specified in IETF RFC 1213.
Separate counters for LAN and WAN ports IfStatistics counters are continuous counters Hardware Management The replaceable parts of a packet radio system are:
When replacing an optical SFP, no configuration is needed. The packet radio unit
RMM RMMs containing new licenses can be replaced, no new configuration is needed. The packet radio is a single HW unit, including both a modem part and a radio part. P R ELIMIN A R Y The packet radio has a mini-SIM card reader on the board for the RMM. The RMM contains licenses and can be accessed in the RJ45 O&M Adapter. Optional features can be expanded by installing license keys that enable additional optional features. Licenses for optional features are distributed in a License Key File (LKF), which can be stored on the RMM. When replacing a packet radio, the new packet radio must be configured according to the set up requirements. The previous RMM or a new RMM must be inserted as they are not included with the package. The packet radio software is upgraded using a load module, which is downloaded from a server and stored in the flash memory. Software Management License Management 7.6 7.7 7.8 Features for the packet radio are only enabled if a corresponding license is available on the inserted RMM. To upgrade the licenses on the packet radio, new licenses can be downloaded remotely. The license key installation can be made both locally and remotely, without disturbing the traffic through the packet radio. License keys can also be preinstalled at delivery, when a complete and preconfigured packet radio is purchased. 44 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management For more information about license management, see License System. 7.9 Security Management
guest with read-only access operator with read and write access net-admin with read and write access sys-admin with read and write access net-admin have full read access, but limited write access. Note: Only the sys-admin has full read and write access. The operator and All management access to the NE is protected by a user name and a password. The following user roles are defined:
All users have an associated password. All users can change their own passwords, but only users with the sys-admin user role can change passwords for other users. P R ELIMIN A R Y The packet radio offers two types of authentication towards the external SSH server: passwords or the Rivest-Shamir-Adleman (RSA) key algorithm. The RSA algorithm uses a public and a private key for authentication and makes it possible to log on without a password. The key pair is generated on the SSH server with a maximum size of 1024 bits. The public key is placed on the SSH server, while the private key is installed on the packet radio. After the installation of the private key, the NE is able to log on to the external SSH server without a password. Another advantage of using RSA keys is that it provides protection for the external SSH server against brute-force attacks, as the keys used are too long to crack them. Secure Shell (SSH) protocol can be used for secure remote access and use of CLI commands. AAA Authentication, Authorization, and Accounting (AAA) is a security architecture for distributed systems. The Authentication process makes sure that only accepted users can log on to the system, for example, using user names and passwords. The Authorization process gives authenticated users certain permissions, for example, based user roles. The Accounting process records information about access and use of the system. There are three AAA policies in MINI-LINK: local, RADIUS, and TACACS+. Note:
If the connection to the remote AAA server is interrupted, the NE falls back to local authentication. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 45 Technical Description Local The local policy supports the following features:
Authentication
Authorization The NE uses local authorization information to distinguish which privileges belong to a role. The authorization process is based on the user role (system admin, network admin, operator, or guest). For local user authentication, the role is defined when the user account is created, and is stored locally as part of the user configuration. For local user authentication, it is necessary to supply authentication information in the form of a username and password. During the authentication process, the NE searches its locally stored configuration for a user with a matching username. If a matching username cannot be found, the request is refused. The maximum number of local users the packet radio supports is sixteen. P R ELIMIN A R Y The RADIUS protocol, which is based on a client-server model, enables remote access to networks and network services. When configured with the IP or host name of a RADIUS server, the NE can act as a RADIUS client. The format and validation of RADIUS packets is in accordance with the IETF protocol specification RFC 2865. The NE does not support RADIUS accounting features. RADIUS only encrypts the password in the Access-Request packet from the client to the server. The rest of the packet (for example, username, authorized services, and accounting) is not encrypted. RADIUS uses UDP, which offers best-effort delivery. RADIUS supports the following features:
RADIUS
Authentication The NE supports both local user authentication and remote authentication using RADIUS. A user needs to have an account created on the external server before logging on. Once the account is created, it can be configured to receive either local authentication or remote authentication using RADIUS. For local user authentication, it is necessary to supply authentication information in the form of a username and password. During the authentication process, the NE searches its locally stored configuration for a user with a matching username. If a matching username cannot be found, the request is refused. The maximum number of local users the NE supports is sixteen. 46 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management
Authorization The NE supports fetching the user roles through a RADIUS server. The NE uses local authorization information to distinguish which privileges belong to a role.
RADIUS Server-Client Feature The authorization process is based on the user role (system admin, network admin, operator, or guest). For local user authentication, the role is defined when the user account is created, and is stored locally as part of the user configuration. For authentication using RADIUS, the RADIUS server provides the user role when the user logs on to the NE . For locally-authenticated users, the locally stored user policy configuration will be used, for example, password expiration and user account expiration. The NE can be managed in situations when a RADIUS server is unreachable. Therefore it ensures there is always at least one locally-authenticated system administrator account. The default locally-authenticated system administrator account is admin. The NE does not allow any configuration change that would delete all locally-authenticated system administrator accounts. P R ELIMIN A R Y A RADIUS Access-Request message containing the authentication information is sent to a remote server. When the RADIUS server receives the request, it validates the client using a shared secret. If the client is valid, the RADIUS server consults its user database to validate the access. The server responds to an Access-Request message with either an Access-Reject message or an Access-Accept message. On receipt of an Access-Reject message, the client refuses access to the user. On receipt of an Access-Accept message, the client grants access to the user. The NE supports up to six RADIUS servers. It connects to the servers one-by-one according to their priorities. If no server is reachable, the NE enables local authentication automatically. The NE supports three RADIUS packet types: Access-Request, Access-Accept, and Access-Reject. If the NE does not receive a RADIUS response to an Access-Request message within the configured timeout, it keeps retransmitting the request until it receives a response, or until the configured number of maximum transmissions has been reached. TACACS+
The TACACS+ protocol enables the building of a system that secures remote access to networks and network services. TACACS+ is based on a client/server architecture. The TACACS+ servers are configured on a per-context basis, with a limit of six servers. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 47 Technical Description TACACS+ uses the Authentication, Authorization, and Accounting (AAA) architecture. This allows separate authentication solutions that can still use TACACS+ for authorization and accounting. TACACS+ uses TCP, which offers connection-oriented transport.
Authentication TACACS+ supports the following features:
TACACS+ encrypts the entire body of the packet, but leaves a standard TACACS+ header. Within the header is a field that indicates whether the body is encrypted or not. For debugging purposes, it is useful to have the body of the packets unencrypted. However, during normal operation, the body of the packet is fully encrypted for securer communications. The NE supports both local user authentication and remote authentication using TACACS+. A user needs to have an account created on the external server before logging on. Once the account is created, it can be configured to receive either local authentication or remote authentication using TACACS+. For local user authentication, it is necessary to supply authentication information in the form of a username and password. During the authentication process, the NE searches its locally stored configuration for a user with a matching username. If a matching username cannot be found, the request will be refused. The maximum number of local users the NE supports is sixteen. P R ELIMIN A R Y The authorization process is based on the user role (system admin, network admin, operator, or guest). For local user authentication, the role is defined when the user account is created, and is stored locally as part of the user configuration. For authentication using TACACS+, the TACACS+ server provides the user role when the user logs on to the NE. For locally-authenticated users, the locally stored user policy configuration will be used, for example, password expiration and user account expiration. The NE can be managed in situations when a TACACS+ server is unreachable. Therefore it ensures there is always at least one locally-authenticated system administrator account. The default locally-authenticated system administrator account is admin. The NE does not allow any change in configuration which would result in no locally-authenticated system administrator accounts. The NE supports fetching the user roles through a TACACS+ server, and the NE uses local authorization information to distinguish which role has what kinds of privileges. Authorization 48 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Management SFTP An SFTP server can be used to upgrade NE system software, instead of just using an FTP server. Using SFTP instead of FTP ensures that the entire session, including passwords, is encrypted. Firewall SSH - SSH server HTTP - Web server Security Protocols A firewall is in place for packet filtering on the IP address and the range of the IP address. The packet filter option is protection from external traffic connections through each possible port or service by closing or opening commands. To increase the security, it is possible for the operator to block a security protocol if a certain service is not needed, or to redirect a protocol to another port. The following security protocols are configurable:
P R ELIMIN A R Y HTTPS - Web server Secure Socket Layer (SSL) connection XRPC - XML based Remote Procedure Calls (XRPC) server The NE has a built-in web server that hosts the Node GUI as a web server application that is accessed using a web browser. By default, a web browser communicates with the web server over HTTPS using a default self-signed SSL/TLS certificate that is not unique for the NE. If the default certificate is not approved by the organizations security policy, it can be replaced with one of the following types of certificates:
A node-unique certificate that is signed by a trusted certificate provider. SSL/TLS Certificates SNMP - SNMP server
A node-unique self-signed certificate that is generated by the NE.
NTP Authentication To prevent manipulation of the time signal, the packet radio authenticates the NTP server it is connected to. An alarm is generated if the connection to the NTP server is lost. The user is able to do the following:
Enable/disable authentication 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 49 Technical Description
Download a keyfile from an external server. The keyfile contains a number of cryptographic NTP keys. P R ELIMIN A R Y 50 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Accessories 8 Accessories 8.1
Power Over Ethernet The equipment used for PoE support is the following:
The packet radio product program contains a number of accessories for installation and operation. This section gives additional technical information for some accessories. One electrical Ethernet cable can supply the packet radio with Ethernet payload, in-band DCN, and DC-power when using the Power Over Ethernet
(PoE) accessories. Pole mounting kit (optional) PoE injector, for either AC or DC power supply P R ELIMIN A R Y PoE cable Figure 24 PoE Overview 8.1.1 PoE Injector The PoE injector merges the Ethernet payload and the input power on to the wires in the electrical Ethernet cable. It also provides overvoltage protection towards the indoor parts, the power supply, and the Ethernet interface. The PoE injector supports one packet radio and can be mounted on a wall or in a mast using an optional pole mounting kit. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 51 Technical Description The Ethernet and PoE cables are connected to the injector using shielded RJ45 connectors. There are two versions of the injector: one for AC power supply and one for DC power supply. 8.1.2 Power Over Ethernet Cable Input Voltage:
Input Current:
Power supply requirements for the AC version:
Power supply requirements for the DC version:
Input Voltage:
Input Current:
Frequency:
1A 1A 50 to 60 Hz 30 to 60 V DC 100 to 240 V AC P R ELIMIN A R Y One Ethernet cable can supply the packet radio with Ethernet payload, in-band DCN, and DC-power. The cable has an angled, environmentally sealed, RJ45 connector on the end that is connected to the packet radio, and a standard RJ45 on the other. Figure 25 Power over Ethernet Cable 17254 52 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Accessories 8.2 Alignment Camera The alignment camera attaches to the MINI-LINK 6351 and streams the camera image over Wi-Fi to a smartphone running the MINI-LINK Alignment app, simplifying alignment. P R ELIMIN A R Y It is possible to use Commissioning Guide for the following tasks during installation:
Figure 26 Alignment Camera Commissioning Guide can run on a PC or on a mobile device (such as a mobile phone or tablet) that is connected to the packet radio. Commissioning Guide requires a web browser that supports HTML 5. 16635 8.3 Commissioning Guide
Antenna alignment Installation verification 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 53 Technical Description P R ELIMIN A R Y 54 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Technical Specifications 9 Technical Specifications 9.1 9.2 9.3 This section summarizes some technical specifications for the packet radio. Table 5 PoE Power Supply Power Consumption Power Supply Requirements The packet radio is power supplied with Power over Ethernet. Power Supply PoE+ PD Type 2 Proprietary PoE Nominal
+53 V DC
-48 V DC Maximum
+57 V DC
-58.8 V DC Minimum
+42.5 V DC
-39.5 V DC P R ELIMIN A R Y Sphere diameter: 175 mm The following dimensions and weight apply for the packet radio:
Dimensions and Weight The typical power consumption for one packet radio, excluding power cable loss, is < 25.5 W.
Weight: 2.4 kg
1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 55 Technical Description P R ELIMIN A R Y 56 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 Federal Communications Commission and Industry Canada Notices 10 Federal Communications Commission and Industry Canada Notices Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes: (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. This device complies with Part 15 of the FCC Rules and with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. P R ELIMIN A R Y This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Increase the separation between the equipment and receiver. Reorient or relocate the receiving antenna.
Changes or modifications made to this equipment not expressly approved by
(manufacturer name) may void the FCC authorization to operate this equipment. 1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04 57
1 | UserManual Safety | Users Manual | 232.49 KiB |
Supplementary Safety Information for MINI-LINK ETSIANSI SAFETY INFORMATION 124 46-HSD 101 16/1 Uen F Copyright Ericsson AB 20082011, 20132014. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document. 124 46-HSD 101 16/1 Uen F | 2014-10-29 Contents Contents 1 2 2.1 3 3.1 3.2 3.3 4 4.1 4.2 Introduction Radio Frequency Electromagnetic Exposure Compliance Distances for Electromagnetic Exposure Safety Requirements Access to Equipment Installation Hardware Installation Procedures and Tools Hazards Hoisting Working at Heights Reference List 1 1 1 2 2 3 3 3 3 3 5 124 46-HSD 101 16/1 Uen F | 2014-10-29 Supplementary Safety Information for MINI-LINK 124 46-HSD 101 16/1 Uen F | 2014-10-29 Radio Frequency Electromagnetic Exposure 1 2 Introduction This document supplements the following safety information:
Personal Health and Safety Information, Reference [2]
System Safety Information, Reference [3]
Radio Frequency Electromagnetic Exposure The radio frequency (RF) electromagnetic exposure levels from MINI-LINK antennas depend on the transmitted power level, antenna diameter, frequency, and distance from the antenna dish. As the antennas are highly directive, the emission in other directions than the main beam axis is negligible. 2.1 Compliance Distances for Electromagnetic Exposure The compliance distance is the minimum separation that should be kept between the antenna and a person in order to ensure that the relevant ICNIRP
(see Reference [1]) RF exposure limit is not exceeded. Ericsson has performed RF exposure assessments of the different MINI-LINK configurations in order to determine the compliance distances in different directions and specify so-called compliance boundaries for both general public and occupational exposure. Normal installation practice requires that the general public has no access to the area directly in front of the antenna, as any obstacle in the path will interrupt the transmission. Such practice will ensure that the general public does not have access to the volume within the compliance boundary as defined in Figure 1. The maximum RF exposure levels directly in front of the antennas do not exceed the limits for occupational exposure for MINI-LINK configurations with antenna diameters larger than 0.6 m. However for 0.2, 0.3, and 0.6 m antennas the occupational compliance boundary may extend up to 2 m as shown in Figure 1. 124 46-HSD 101 16/1 Uen F | 2014-10-29 1 Supplementary Safety Information for MINI-LINK Occupational boundary 2.0 m (7 ft) General public boundary 14.1 m (47 ft) 17050 Figure 1 Compliance boundary for radio frequency exposure The compliance boundary is defined as a cylinder with the same diameter as the antenna and extending in the main beam direction of the antenna up to the distances stated in Figure 1. Note: The compliance boundary described above has been defined to cover all MINI-LINK configurations. For many configurations the maximum RF exposure does not exceed the general public limits at any distance in front of the antenna. On request, Ericsson will provide RF exposure and compliance distance information for specific MINI-LINK configurations. 3 Safety Requirements The safety requirements in the following sections must be followed to avoid personal injury and damage to tangible property. It is the responsibility of the local project manager/supervisor to make certain that local regulations and the safety instructions in this document are known and followed. 3.1 Access to Equipment The equipment must be installed in a restricted access location and access shall be restricted to authorized personnel. The general public shall not have access to the volume inside the compliance boundary, as shown in Figure 1. 2 124 46-HSD 101 16/1 Uen F | 2014-10-29 Hazards 3.2 Installation Hardware Do not use any installation components other than what is enclosed with the equipment or recommended by Ericsson. 3.3 Installation Procedures and Tools The installation procedures in the relevant instructions must be followed. Make sure that working instructions are followed. 4 4.1 Hazards Hoisting
Make sure that all hoisting devices are properly stabilized and attached to Trained personnel must operate the hoisting device. Always check that all parts of the hoisting device are intact.
fixed objects, such as walls or buildings, before hoisting. Always hoist the equipment in the specified hoisting points. Never walk under hoisted loads. Follow local regulations for safety clothing and safety equipment for hoisting or moving goods. 4.2 Working at Heights When working at heights, for example on a mast, tower or roof, make sure no one is allowed to be located below the area where the work is performed. 124 46-HSD 101 16/1 Uen F | 2014-10-29 3 Supplementary Safety Information for MINI-LINK 4 124 46-HSD 101 16/1 Uen F | 2014-10-29 Reference List Reference List
[1] Guidelines for limiting exposure to time-varying electric, magnetic, and electromagnetic fields (up to 300GHz), International Commission on Non-Ionizing Radiation Protection, Health Physics, vol. 74, no. 4, 1998.
[2] Personal Health and Safety Information, 124 46-2885
[3] System Safety Information, 124 46-2886 124 46-HSD 101 16/1 Uen F | 2014-10-29 5
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2016-11-22 | 59000 ~ 62000 | DXX - Part 15 Low Power Communication Device Transmitter | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 | Effective |
2016-11-22
|
||||
1 | Applicant's complete, legal business name |
Ericsson AB
|
||||
1 | FCC Registration Number (FRN) |
0013476155
|
||||
1 | Physical Address |
PDU Radio
|
||||
1 |
Stockholm, N/A 164 80
|
|||||
1 |
Sweden
|
|||||
app s | TCB Information | |||||
1 | TCB Application Email Address |
O******@cetecom.com
|
||||
1 | TCB Scope |
A2: Low Power Transmitters (except Spread Spectrum) and radar detectors operating above 1 GHz
|
||||
app s | FCC ID | |||||
1 | Grantee Code |
TA8
|
||||
1 | Equipment Product Code |
AUKL50158-21H
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 | Name |
I******** T******
|
||||
1 | Title |
Head of PDU Radio
|
||||
1 | Telephone Number |
+46 1********
|
||||
1 | Fax Number |
+46 1********
|
||||
1 |
i******@ericsson.com
|
|||||
app s | Technical Contact | |||||
n/a | ||||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 | Equipment Class | DXX - Part 15 Low Power Communication Device Transmitter | ||||
1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Outdoor radio for small cell deployments | ||||
1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 | Modular Equipment Type | Does not apply | ||||
1 | Purpose / Application is for | Original Equipment | ||||
1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 | Grant Comments | Output power listed is average conducted. The antenna(s) used for this transmitter must be fixed-mounted on outdoor permanent structures with a separation distance of at least 0.34 meters from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. Users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. | ||||
1 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 | Firm Name |
CTC advanced GmbH (former CETECOM ICT Services )
|
||||
1 | Name |
G******** S****
|
||||
1 | Telephone Number |
49-68********
|
||||
1 | Fax Number |
49-68********
|
||||
1 |
t******@ctcadvanced.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15C | 59000.00000000 | 62000.00000000 | 0.0069000 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC