No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OSN 9800 V100 Configuration Guide 03

This document introduces service configuration process for OSN 9800.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Ethernet Services

Ethernet Services

MEF and IETF have separately defined Ethernet service models at Layer 2.

In essence, the Ethernet service models defined by MEF and IETF are the same although they have different names. The product support all the service models listed in Table 3-1. This table also presents the mappings between the service models, transport tunnels, and service multiplexing methods.

Table 3-1 Ethernet service models
MEF Model IETF Model Transport Tunnel (Network Side) Service Multiplexing Method (Access Side)
E-Line - Physically isolated/VLAN Physically isolated
VPWS MPLS
- Physically isolated/VLAN VLAN
VPWS MPLS
E-LAN - Physically isolated Physically isolated
- Physically isolated/VLAN VLAN
VPLS MPLS

E-Line/E-LAN

MEF defines two types of Layer 2 Ethernet services: E-Line service using point-to-point Ethernet virtual connection (EVC) and E-LAN service using multipoint-to-multipoint EVC.

Table 3-2 lists the E-Line and E-LAN services supported by the OptiX OSN 9800.

Table 3-2 E-Line and E-LAN services

Service

Service Type

E-Line Service

ETH PWE3 services

E-Line Services Carried by PWs

Native ETH services

Point-to-point transparently transmitted E-Line service

VLAN-based E-Line services

E-Line Services Carried by QinQ Links

E-LAN Service

ETH PWE3 services

E-LAN Services Carried by PWs

Native ETH services

E-LAN Services Carried by Ports

E-LAN Services Carried by QinQ Links

E-Line Service

Any Ethernet service that is based on a point-to-point EVC shall be designated as an Ethernet Line (E-Line) service type, as shown in Figure 3-1.

Figure 3-1 E-Line Service
Table 3-3 shows different E-Line services and related carrier technologies.
Table 3-3 E-Line Service

E-Line Service

Carrier technologies

Schematic Diagram

E-Line Services Carried by PWs

MPLS



Point-to-point transparently transmitted E-Line service

Port carrier (physical isolation)



VLAN-based E-Line services

VLAN



E-Line Services Carried by QinQ Links

VLAN

E-LAN Service

Any Ethernet service that is based on a Multipoint-to-Multipoint Ethernet Virtual Connection (EVC) shall be designated as an Ethernet Line (E-LAN) Service type, as shown in Figure 3-2.

Figure 3-2 E-LAN Service

The E-LAN services that the product support are:
  • E-LAN Services Carried by PWs
  • E-LAN Services Carried by QinQ Links
  • E-LAN Services Carried by Ports

Table 3-4 shows the different E-LAN services and related carrier technologies.

Table 3-4 E-LAN Service

E-LAN Service

Carrier technologies

Schematic Diagram

E-LAN Services Carried by PWs

MPLS



E-LAN Services Carried by QinQ Links

VLAN



E-LAN Services Carried by Ports

Port carrier (physical isolation)



VPWS/VPLS

Layer 2 virtual private network (L2VPN) defined by IETF includes the virtual private wire service (VPWS) and virtual private LAN service (VPLS). VPWS is used to provide point-to-point service at Layer 2 and VPLS is used to simulate a local area network (LAN) in a wide area network (WAN).

VPWS

VPWS is a Layer 2 virtual private network (VPN) technology for point-to-point transmission. It performs one-to-one mapping between a received attachment circuit (AC) and a pseudo wire (PW). By binding ACs and PWs in the <AC, PW, AC> format to form a virtual circuit, VPWS achieves transparent transmission of Layer 2 services between users. Figure 3-3 shows the application of VPWS.

Figure 3-3 Application of VPWS

VPLS

VPLS is a Layer 2 VPN technology for simulating LANs. Using VPLS, each L2VPN considers an NE as a virtual switching instance (VSI), and this VSI is used to achieve mapping between multiple ACs and PWs, and connect multiple Ethernet LANs so that the LANs work as if they are one LAN.

VPLS is an important technology for MANs. It can connect multiple Ethernet-powered enterprise networks. As shown in Figure 3-4, VPLS provides LAN services across the WAN for customer A.
Figure 3-4 Application of VPLS

CES/CEP Services

The CES/CEP helps to solve the problem of insufficient optical fiber resources in the access ring and allows TDM services to be transparently transmitted across the pure packet mode.

Emulation Mode

CES/CEP services support the following emulation modes:
  • Structure-Agnostic TDM over Packet (SAToP): In this mode, SAToP emulation is performed for SDH VC-12 signals. Emulation services in this mode are also called CES services.
  • Structure-aware TDM Circuit Emulation Service over Packet Switched Network (CESoPSN): In this mode, CESoPSN emulation is performed for SDH VC-12 signals. Emulation services in this mode are also called CES services. Compared with the SAToP mode, the CESoPSN mode is more bandwidth-efficient because it supports idle timeslot compression.
  • Circuit Emulation over Packet (CEP): In this mode, CEP emulation is performed for SDH VC-4 signals. Emulation services in this mode are also called CEP services.

Application Scenario

Figure 3-5 describes the typical application of CES/CEP services. CES/CEP services are classified into remote services (UNI-NNI) and local services (UNI-UNI).
  • Remote service (UNI-NNI): The native TDM services between the NodeB and the RNC are transmitted over a PSN. PE1 emulates the native TDM services from the NodeB into CES/CEP services (CESoPSN mode is used as an example in the following figure). Then, the CES/CEP services are transmitted to PE2 over the PSN. Finally, PE2 restores the CES/CEP services to the native TDM services, which are then transmitted to the RNC.
  • Local service (UNI-UNI): The NodeB and RNC are interconnected using PE1. PE1 receives native TDM services from NodeB and transparently transmits the services to the RNC on the UNI side.
Figure 3-5 Typical application of CES/CEP services

Translation
Download
Updated: 2019-09-05

Document ID: EDOC1100033663

Views: 19425

Downloads: 682

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next