Documentos de Académico
Documentos de Profesional
Documentos de Cultura
RAN Overview
Page 4
Page 5
RAN Architecture A RAN is composed of RNCs, NodeBs, and the M2000. RNCs and NodeBs are network elements; the M2000 is an Element Management System (EMS). RNCs, NodeBs, and the M2000 are connected to each other, forming a RAN.
Page 6
Page 7
Page 8
Session services: have very high requirements for real-time transmission and allow error codes to a certain extent. Session services include the voice service and video phone service. Flow services: have high requirements for real-time transmission and are transmitted through stable and continuous data flows. An example of flow services is the multi-media service. Interaction services: have only moderate requirements for real-time transmission but require integrity and accuracy of data. Interaction services include webpage browsing and location-based services. Background services: do not require real-time transmission but require integrity and accuracy of data. An example of background services is the e-mail service.
RAN Services
Page 9
NodeB Overview
Being a base station in the UMTS, a NodeB can transmit RF signals to a UE or receive RF signals from a UE to implement wireless coverage. A NodeB is connected to an RNC through an Iub interface.
Page 10
RNC Overview
Physically, an RNC can be divided into the hardware and software; logically, an RNC can be divided into the switching sub-system and service processing system. The hardware of an RNC is composed of a switching cabinet, service cabinet, Local Maintenance Terminal (LMT), and alarm console. Besides ports for inputting power and clock signals, an RNC provides ports for communicating with NodeBs, Serving GPRS Support Nodes (SGSNs), Mobile Switching Center (MSCs), other RNCs, and the M2000.The software system of an RNC is composed of several pieces of software which supports the operation of the entire system. The RNC software adopts a distributed structure design, including the foreground host software and BAM software, which can communicate with each other. The switching sub-system and service processing sub-system form the host system (also called foreground administration module). The operation and maintenance sub-system includes the background administration module (BAM) and LMT.
Page 11
IP RAN
Page 12
What Is an IP RAN?
On an IP RAN, Iub interfaces can transmit traffic based on IP. At present, Iu and Iur/Iub earth interfaces of RANs based on WCDMA R99 and R4 perform ATM transmission. In addition, RNCs and NodeBs are tightly coupled. Consequently, both the CapEx and OpEx are high. To effectively protect carriers' investment, reduce CapEx, and achieve smooth evolution of 3G networks, IP will be introduced for RANs in the WCDMA R5 phase. The IP RAN solution aims to fix these issues. In summary. Summarily, on an IP RAN, IP replaces ATM as the transmission technique.
Page 13
Why IP RAN?
Air Interface Technology
3G(R99/R4) UL: 384 Kbps DL: 384 Kbps 3G+HSxPA(R6/R7) UL: 5.76 Mbps DL: 14.4 Mbps 3G+E-HSPA(R8?) UL: 12.5 Mbps? DL: 25 Mbps?
20-100 Mbps 10-50 Mbps 3-20 Mbps 64-384 Kbps 384 K5 Mbps
Service Bandwidt h
64-144 Kbps
Page 14
Why IP RAN?
Being the mainstream of datacom networks, IP datacom networks are of large scales and provide a great variety of access modes. By introducing the IP RAN function, carriers can efficiently use the resources of IP networks and perform Iub-based networking.
Following the network evolution trend and protecting carriers' investment IP transmission is the prevailing technology of datacom networks and is the direction for the further development of datacom networks. Introducing the IP RAN technology, you can follow the network evolution trend and protect your investment.
Page 15
NodeB
Ethernet/IP/MPLS
RNC RNC
TDM PWE3
Page 16
Contents
IP RAN Overview Key Technologies of IP RAN
Page 17
Page 18
PWE3
Introduction to PWE3 TDM to PWE3 ATM to PWE3 Eth to PWE3 Applications of PWE3 PWE3 for PTN devices PTN planning rules
Page 19
What is PWE3
PWE3
Pseudo Wire Emulation Edge-to-Edge
CE
PE PW1 PW3
AC PE PW2
PE
CE
CE
Page 20
AC
CE1
PE1
Tunnel Tunnel
PE2
AC
CE2
Provid er Edge 2
PWE3
Introduction to PWE3 TDM to PWE3 ATM to PWE3 ETH to PWE3 Applications of PWE3 PWE3 for PTN devices PTN planning rules
Page 22
Page 23
SAToP
SAToP: is short for Structure Agnostic TDM over PSN
Payload
Ch0
E1
Ch31
Ch1
E1 data
Header
PTN
Ch31
Ch1
Ch0
E1 data
Header
Page 24
Features of SAToP
The features of SAToP are as follows: 1. Does not need to protect the integrity of the structure, or explain or control the channels. 2. Applicable to PSNs of higher transmission performance. 3. Does not need to distinguish channels and disrupt TDM signaling.
Page 25
SAToP Encapsulation
Three optional PW external tunnel encapsulation modes are listed in RFC 4553:
IP/UDP mode, L2TPv3 mode, and MPLS mode. In IP/UDP and L2TPv3 modes, a SAToP PW can be carried on an IPv4/IPv6 PSN. If the PSN is an MPLS network, the carrying mechanism in MPLS mode is adopted. At present, TDM emulation on PTN devices supports the MPLS mode.
Page 26
Ch31
PTN
Ch31
Ch1
Ch0
Header
Page 27
Features of CESoPSN
The features of CESoPSN are as follows: 1. When services are sent to PSN, TDM structure needs to be protected. 2. The transmission of sensible structure can be applied to PSN network with lower performance. The mode can improve the reliability of the transmission.
Page 28
CESoPSN Encapsulation
Three optional PW external tunnel encapsulation modes are available for CESoPSN: IP/UDP mode, L2TPv3 mode, and MPLS mode. Different from that of SAToP, the TDM data borne by PW through CESoPSN adopts a frame structure. Domain M is added to the PW control field in the PW packet to indicate the detection of AC-side signaling. Huawei TDM transparent transmission devices support CESoPSN of the MPLS mode.
Page 29
At present, the TDM circuit emulation boards of Huawei PTN devices allow you to set the jitter buffer capacity through commands.
Page 30
Analysis of data delay Encapsulation Delay Encapsulation delay occurs when TDM service flows are encapsulated into PW packets. Service Processing Delay Service processing delay refers to the delay when the device processes packets, including packet legality check, packet filtering, check and calculation, packet encapsulation, packet receiving, and packet sending. This delay is related to the service processing capacity of devices, and is therefore, remains unchanged.
Network Transmission Delay
Page 31
Page 32
PWE3
Introduction to PWE3 TDM to PWE3 ATM to PWE3 ETH to PWE3 Applications of PWE3
Page 33
Page 34
Encapsulation Mode
N-to-one ATM cell encapsulation mode This mode is a standard-defined encapsulation mode and allows one or more ATM connections to be mapped to one PW. In this mode, the CW is optional.
0000 ATM payload48bytes VPI VCI ATM payload48bytes PTI C Tunnel Label PW Label Length Flags rsv VPI EXP S EXP S Sequnce Number VCI TTL TTL PTI C
Page 35
Encapsulation Mode
One-to-one ATM cell encapsulation mode
In this mode, one PW can bear one VPC/VCC. One or more cells can be encapsulated to improve bandwidth usage. VPC VCC
0 1 2 3 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
PSN Transport Header in PWE3 Pseudo Wire Header in PWE3 Sequence Number VCI
M V RES PTI C
Payload48 octets
M V RES PTI C
VCI
Payload48 octets
Page 36
Page 37
PWE3
Introduction to PWE3 TDM to PWE3 ATM to PWE3 ETH to PWE3 Applications of PWE3
Page 38
PSN
Page 39
0000
Reserved
Sequence Number
ETH Payload
Page 40
PWE3
Introduction to PWE3 TDM to PWE3 ATM to PWE3 ETH to PWE3 Applications of PWE3 PWE3 for PTN devices PTN planning rules
Page 41
Network Interface
CESoPSN SAToP
MAC
Line Interface
Abis TDM E1/ch STM-1
1+1/1:1 APS
2G BTS
TS# 1-9
E1 E1 E1
---PoC3
STM-1
----
PSN
PoC1 BSC
MSP
E1/POS/GE/ch STM1
Tunnel
--
Idle TS suppression
Page 42
Network Interface
Line Interface
ATM STM-1
3G Node B
E1 E1 E1
1+1/1:1 APS
STM-1
PSN
PoC3
E1 E1 E1
PoC1
RNC
E1/POS/GE Tunnel
Legend EF AF3
3G Node B
BE
IMA is short for Inverse Multiplexing for ATM. As shown in the above figure, the sender schedules and distributes a high speed ATM cell stream to multiple low speed physical links for transmission, and then the receiver schedules and recombines them into one cell stream and submits the cell stream to the ATM layer.
Page 43
Network Interface
Line Interface
3G Node B
PSN
PoC3 PoC1
GE
RNC
E1/POS/GE Tunnel
Legend EF AF3 BE
Page 44
PWE3
Introduction to PWE3 TDM to PWE3 ATM to PWE3 ETH to PWE3 Applications of PWE3 PWE3 for PTN devices PTN planning rules
Page 45
Page 46
Page 47
PWE3
Introduction to PWE3
TDM to PWE3
ATM to PWE3 ETH to PWE3
Applications of PWE3
PWE3 for PTN devices PTN planning rules
Page 48
Page 49
Page 50
Clock
Brief Introduction TOP Clock Synchronization at the Ethernet Physical Layer IEEE 1588v2 Clock Planning
Page 51
Basic Concepts
What Is Clock Synchronization
Clock synchronization: refers to a strict relationship between signals based on a constant frequency offset or phase offset, in which signals are sent or received at an average rate in an epoch. That is, the difference of phases between signals is a constant value.
Page 52
With the fast growth in data services, PSNs are widely applied. The PSN, however, was developed to transfer asynchronous data. If you want to transmit TDM, IPTV, and 3G services on PSNs, you have to considers the high synchronization requirements of these services. This leads to the integration of packet switching technologies and the conventional TDM system. It is required that PSNs should implement clock synchronization.
Page 53
Precision Requirements
Clock1 Clock2
The frequency variance between Clock 1 and Clock 2 must be less than 50 ppb; the clock variance between Clock 1 and Clock 2 must be less than 3 us.
Page 54
Clock
Brief Introduction TOP Clock Synchronization at the Ethernet Physical Layer IEEE 1588v2 Clock Planning
Page 55
TOP is a clock recover technique in which local clock information in a certain encapsulation format is transmitted through a packet. The receiver can recover the clock from the received packet. In this manner, the clock is not affected during the transmission over a PSN. The device that supports TOP can implement clock synchronization on an entire PSN and on a synchronous PSN connected to an asynchronous PSN.
Page 56
TOP Technologies
Recovering clock through the timing information in a packet
TOP Client
Timing packet
queue
PSN
Time Stamp
Frequency recovery
Page 57
TOP Technologies
TOP supports the following operation modes:
1. Adaptive
2. Differential
Page 58
Application of TOP
TOP Server
TOP Packets
Conventional PSN
TOP Client
TOP Packets
TOP Client
TOP allows you to synchronize the clocks on the devices at the two ends of a PSN.
Page 59
TOP Technology
Advantages Supports PSN transparent transmission; the intermediate devices do not have to support TOP; can be applied flexibility. Many chip vendors support TOP; Huawei has developed TOP technologies. Limitations
The clock recovery precision depends on the performance of the PSN. The clock is likely to be affected by network delay, packet loss, and disordering. High QoS has to be ensured.
No standard for TOP has ever been published. Device compatibility is limited. In addition, clock synchronization is not supported.
Page 60
Clock
Brief Introduction TOP Clock Synchronization at the Ethernet Physical Layer IEEE 1588v2 Clock Planning
Page 61
similar to SDH. Instead of being transmitted over the packet cost, this
technique uses a special type of packet to transmit the Synchronous Status Message (SSM).
Page 62
PHY
Page 63
SSM
PRC
PSN
Page 64
Page 65
Clock
Brief Introduction TOP Clock Synchronization at the Ethernet Physical Layer IEEE 1588v2 Clock Planning
Page 66
IEEE 1588v2
Why IEEE 1588v2
The techniques of clock synchronization at the Ethernet Physical Layer and TOP can implement only frequency synchronization instead of clock synchronization. What is IEEE 1588v2 IEEE 1588 is a precision clock synchronization standard for the network measuring and control system. IEEE 1588 is based on Precision Time Protocol (PTP) and can achieve a clock precision of milliseconds. This standard aims to unify dependently running clocks in the measurement and control system.
Page 67
IEEE 1588v2
The key points of IEEE 1588 are as follows:
Page 68
IEEE 1588v2
Three models are defined in the network architecture of the IEEE 1588: Original Clock (OC) Boundary Clock (BC)
Page 69
Principle of IEEE1588v2
Adopting the handshake mode and using precise timestamps to achieve time synchronization
Page 70
TC TC 1588 Master
TC TC 1588 Slave
PSN
RNC
Implementing simultaneous synchronization of frequency and clock between NodeBs and RNCs
Page 71
IEEE 1588v2
Advantages
Can implementing clock synchronization The clock synchronization quality is high, and the effect of PSNs is limited. A standard has been released to support this technology. Devices of various vendors can interwork with one another.
Limitations
- All the devices along clock links need to support IEEE 1588. - The protocol has been finalized. This technique has not been commercially
Page 72
Page 73
Ethernet Synchronizati on
TOP
IEEE1588 V2
There is little impact from the PSN. Each node on the network needs to support IEEE 1588.
Page 74
Clock
Brief Introduction TOP Clock Synchronization at the Ethernet Physical Layer IEEE 1588v2 Clock Planning
Page 75
Page 78
Page 79
For a intersectant ring, you can configure master BITS on one intersectant point as the benchmark clock for the network; configure slave BITS on another intersectant point for switchover.
Page 80
Page 81
When accessing the ATM service, you are recommended to adopt the default service class in the default template 1. That is, the forwarding class of the CBR service is EF; the forwarding class of the rt-VBR service is AF3; the forwarding class of the nrt-VBR service is AF2; the forwarding class of the UBR service is BE.
For the PTN devices on the border nodes in the DS domain, the recommenced mapping for PHB is as follows: For the service flows from non-DS domains, you are recommended to use complex traffic classification for PHB mapping on the V-UNI. For the service flows from other domains, you are recommended to use simple traffic classification for PHB mapping on the V-UNI. On the intermediate nodes of the DS domain, perform forwarding based on PHB and performs QoS configuration. The nodes in a DS domain need to use the same simple classification rule. For user services without configured bandwidth, you need to set the forwarding class to BE, and the discarding priority is not limited (green by default). Congestion avoidance mechanism: policy and shaping For V-UNI, you are recommenced to set the CAR to limit the access services. When the rate of service flows of the same user or CQ queues on interfaces, the maximum rate variance must be within 100 times.
Page 82
- Bandwidth allocation for the V-UNIs in a V-UNI group must meet the following rules:
The sum of CIRs of all V-UNIs cannot exceed the CIR of the V-UNI Group. The PIR of any V-UNI cannot exceed the PIR of the V-UNI Group. Bandwidth allocation for the PWs of a TE-Tunnel must meet the following rules:
- The sum of CIRs of all PWs cannot exceed the rate of the TE tunnel.
- The PIR of a PW cannot exceed the rate of the TE tunnel. Congestion avoidance mechanisms: RED and WRED You are recommended to adopt WRED rather than dropping at the queue tail as the congestion avoidance measure for V-UNI, PW, QinQ, and CQ (port queue). DO not change the default WRED threshold.
Page 83
Page 84
OAM
MPLS OAM Ethernet interface OAM Ethernet service OAM ATM OAM
Page 85
verification
- Forward Defect Indication (FDI) and Backward Defect Indication (BDI): for forward and backward defect indication - LSP ping: for on-demand detection of MPLS LSP connectivity
- LSP TraceRoute: for on-demand tracing of MPLS LSPS and fault location
- PM and LSP detection: detection of delay, jitter, and packet loss rate
OAM packets can detect the connectivity of service channels. Different sites communicate with each other through APS packets and perform switchover. The switchover time reaches the carrier class of less than 50 ms.
Page 86
Functions of Ethernet service OAM The major function of Ethernet Service OAM is to manage and maintain end-toend Ethernet virtual links. Ethernet Service OAM involves the following operations: (1) Fault Management
OAM packets are distinguished by Ethernet Type and passes the same path with service packets.
Page 88
Page 89
Terms
BITSBuilding Integrated Timing Supply System BSC Base Station Controller BTSbase transceiver station CSCircuit Switched IMAInverse Multiplexing on ATM Iuban interface between an RNC and a NodeB NodeB3G BTS PSPacket Switched PTN Packet Transport Network RANRadio Access Network RNCRadio Network Controller SSMSynchronization Status Message TDMTime Division Multiplex(ing)
Page 90
Page 91