Page History
Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Panel |
---|
The following explanation expands on the use case where a distinct EVPL service is implemented between each RAN BS and RAN NC with the following configurations:
Table 1 (at right) shows an example of how Carrier Ethernet services can be delivered in the mobile backhaul according to the assumptions made for the present use case. This use case may also take into consideration additional factors that result in four possible options, each using a different service frame format at the RAN BS UNI-C:
Options B, C and D may ease the configuration of the RAN BS because they are agnostic to the CE-VLAN ID value used to identify Service Frames in the mobile backhaul. Table 2 shows an example of the CE-VLAN ID / EVC mapping for each option and the configuration both at the RAN BS UNI-N and at the RAN NC UNI-N. The symbol * indicates the CE-VLAN ID value used at the UNI for both untagged and priority tagged frames. The CoS ID Preservation attribute should be enabled for each option in order to simplify configuration. Note that the CoS ID per <EVC> model can also be supported by this use case if the assumption to use a single EVP Line per RAN BS that supports multiple services is removed. According to this new assumption each RAN BS can support multiple EVP Lines whereby mobile traffic classes may be grouped into different EVCs. Each EVP Line is mapped to a unique CE-VLAN ID and so each CE-VLAN ID identifies a specific set of services between the RAN NC and a specific RAN BS.
→ Back to the Mobile Backhaul Application |
Panel | ||||
---|---|---|---|---|
| ||||
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Panel | ||
---|---|---|
| ||
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Panel | ||||
---|---|---|---|---|
| ||||
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Panel | ||
---|---|---|
| ||
Panel | ||||
---|---|---|---|---|
| ||||
Larry Samberg |
Panel | ||
---|---|---|
| ||