The purpose of this document is to assist carriers with ordering Virtual Circuit (EVC) Service.
Verizon's Ethernet Virtual Circuit (EVC) provides point-to-point connectivity between Ethernet TLS UNI circuits (UNI to UNI), TLS UNI circuits and ENNI circuits (UNI to ENNI).
The EVC is available for connectivity between ERS UNI circuits only, in four service types (one for Standard, and three for Premier) and a multitude of speeds. The customer must have two UNI circuits or a UNI and an ENNI circuit in effect before the EVC connection can be ordered.
ERS UNI circuits are available in two service types, ERS Standard and ERS Premier. Both the ERS UNI circuit types (Standard or Premier) required at least one separate EVC in order to be functional.
The ERS Standard UNI is offered in three speeds - 10M, 100M, and 1000M (1G); these same speeds are available for the EVC connecting ERS Standard circuits. The ERS Standard UNI can have one EVC connection.
The ERS Premier UNI is offered in four speeds - 10M, 100M,1000M (1G) and 10000M (10G).The EVC for connecting ERS Premier circuits is offered in various bandwidth increments and allows for one, two, or three levels of service (basic, priority data, and real time) under specific conditions. The ERS Premier circuit can have multiple EVC connections.
Service Types
Conditional to service types, the EVC can either be ordered between two UNI circuits or between a UNI and an ENNI of the same "flavor" (Standard to Standard or Premier to Premier). For TLS service, both options are available.
EVC connections are not available nor are they allowed on EMS circuits.
EVC service descriptions and specific conditions are listed below:
ERS Standard is designed for customer applications that do not
require bandwidth or delay guarantees and is the only EVC type
available for ERS Standard UNI circuits.
ERS Basic (ERS-B) is designed for customer applications that do
not require bandwidth or delay guarantees and is available for ERS
Premier UNI circuits.
ERS Priority Data (ERS-PD) is designed for customer applications
requiring a bandwidth guarantee for their point-to-point EVC,but do
not require low delay, and is available for ERS Premier
UNI circuits.
ERS Real Time (ERS-RT) is designed for customer applications
requiring a bandwidth guarantee and low delay for some of their
traffic, and is available for ERS Premier UNI circuits.
NOTE: The total bandwidth of an EVC applied to an ERS Premier
UNI can be composed of one level of service and bandwidth, or a
combination of two or three levels of service listed above
(ERS Basic, ERS Priority Data, and ERS Real Time) and multiple
bandwidths.
The customer is required to identify the type, speed, and level of service of each EVC ordered for the ERS Premier UNI. The speed of the EVC cannot exceed the bandwidth of the lower speed UNI of the connection.
TLS UNI Tagged or Untagged Frames - Ethernet Frames can be formatted Tagged or Untagged. The customer TLS UNI circuits on the EVC ASR form (tagged or untagged) will indicate whether a single bandwidth and level or service or multiple bandwidths and levels of service are permitted in the configuration of each EVC. This indication of tagged or untagged is provided in the NCI Codes provided by the customer on the ASR.
Read more about our Ethernet Solutions.
New Ethernet Virtual Circuit (EVC) Service is offered under a private carriage agreement (Forbearance). Contact your Verizon Account Manager for more information.
Note: When this product is ordered under a private carriage agreement (Forbearance), the Contract ID must be populated in the Promotion Number (PNUM) field on the Access Service Request (ASR) form.
ASR Requirements - Ethernet Virtual Circuit
A complete ASR is essential to properly provision and bill Ethernet Virtual Circuit (EVC) service. The following information pertains to the fields that will impact EVC requests. All fields on the ASR (including those not listed here) must be populated according to the Access Business Rules.
EVC ASRs follow special access rules for an "S" Request Type. Verizon is offering point to point EVC connections. Two EVC forms will be required, one for referencing each TLS UNI/ENNI circuit involved in the mapping connection. The number of EVC forms within the ASR will be determined by the customer population of the NUT field (EXAMPLE: 02, which yields two EVC Forms)
| Access Service Request (ASR) Form | |||
|---|---|---|---|
| Section | Field | Entry | Notes |
| Admin Section | |||
| RTR | Required - Valid values = F or N | All ASR activities | |
| EXP | Not permitted | All ASR activity. | |
| QTY | 1 Required | All ASR activity - quantity of 1 is only valid entry for EVC ASR. | |
| EVCI | A - Generates the EVC Screen Page - Required | All ASR activity. Only valid entry is A for Stand Alone EVC. | |
| ECCKT | Not permitted | All ASR activity. The ECCKT field on the ASR page will not be utilized for EVC activity. | |
| PIU | 100 Required | All ASR activity except D | |
| BAN | Billing Account Number Required. Customer valid entries. a. Populated BAN of TLS UNI circuit of RUID 1 field b. E (existing) |
All ASR activity except D. | |
| SPEC | Not permitted | All ASR activity | |
| Billing Section | |||
| PNUM | Forbearance Contract ID = FORMERLY POPULATED IN CNO. - Required | All activities except D. | |
| VTA | Blank | All activities. There are no term pricing plans for EVC - all EVCs are billed month to month | |
| Remarks Section | RMKS | Customer remarks. | Customer remarks for additional information. |
| Ethernet Virtual Connection (EVC) Form (Form 1) | |||
|---|---|---|---|
| Ethernet Virtual Connection Detail Section | |||
| EVC NUM | Required - Customer EVC number Numeric sequence EXAMPLE: 0001 |
All ASR Activity | |
| NC | Required - See Matrix provided below. | ASR Activity N, C, R | |
| EVCID | Required - EVC CLS Circuit ID | ASR Activity C, R, D | |
| NUT | Required - 02 | ASR Activity N, C, R Only value permitted is 02 | |
| UNI Mapping Detail Section | |||
| UREF | Required - 01 | ASR Activity N, C or R *NOTE: The Quantity of UREFs must equal the Number in the NUT field, the numbering of the UREFs is incremental 01 and 02 | |
| UACT | Required - EVC requested activity Valid entries = N, C, R, D, *K | All ASR Activity * NOTE: Activity of K (cancel) is only allowed on a SUPP. | |
| NCI | Required - See Matrix provided below. | ASR Activity N, C, R NCI Code will reference TLS UNI in RUID 1 field interface mapping on EVC page 1. | |
| EVCSP | Required - TLS UNI Switch CLLI | ASR Activity N, C, R This is the Switch CLLI of TLS UNI in RUID 1 field. | |
| CE-VLAN | Required for ASR Activity C and R, Optional for N activity if customer is requesting a preferred EVC VLAN ID. Identifies the EVC VLAN ID assigned to the EVCID | ASR Activity C, R ASR Activity D.- not required ASR Activity N - This will be sent on FOC to customer. | |
| RUID | Required - Identifies TLS UNI/ENNI Circuit IDs for EVC connection | ASR Activity N, C, R RUID from which the EVC is being mapped is populated on this page - EVC Page 1. | |
| LREF | Required - Identifies the Level of Service Reference Number EXAMPLE: LREF = 1 | ASR Activity N, C, R The data in this entire section of fields of the EVC Form under the UNI Mapping Detail Section will identify the first level of service the customer wishes to apply to the EVC. | |
| LOSACT | Required - Identifies the Activity for this Level of Service | ASR Activity N, C, R. *K * NOTE: Activity of K (cancel) is only allowed on a SUPP. NOTE: Required when the LREF field is populated. | |
| LOS | Required - Identifies the Level of Service Name Valid entries - See the EVC Levels of Service and Bandwidth Combinations Matrix below. |
ASR Activity N, C, R NOTE: Required when the LOSACT field is populated. | |
| BDW | Required - Identifies the bandwidth rate defined by the Level of Service EXAMPLE: 10M Valid entries - See the EVC Levels of Service and Bandwidth Combinations Matrix below. |
ASR Activity N, C, R NOTE: Required when the LREF and LOSACT fields are populated. | |
| REMARKS | Customer remarks. | All ASR Activity - Customer remarks for additional information. | |
| PG_of_ | Provides page numbers contained in the EVC transaction. EXAMPLE: PG 0 0 1 of 0 0 2 |
All ASR Activity - System generated. | |
| Ethernet Virtual Connection (EVC) Form (Form 2) | |||
|---|---|---|---|
| Ethernet Virtual Connection Detail Section | |||
| EVC NUM | Required - Customer EVC number Numeric sequence EXAMPLE: 0001 |
All ASR Activity Data will be repeated from EVC Page 1 | |
| NC | Required - See Matrix provided below. | ASR Activity N, C, R Data will be repeated from EVC Page 1 | |
| EVCID | Required - EVC CLS Circuit ID | ASR Activity C, R, D | |
| NUT | Required - 02 | Data will be repeated from Page 1 of EVC Form Page | |
| UNI Mapping Detail Section | |||
| UREF | Required - 02 | Data will be repeated from Page 1 of EVC Form Page | |
| UACT | Required - EVC requested activity Valid entries = N, C, R, D, *K |
Data will be repeated from Page 1 of EVC Form Page | |
| NCI | Required - See Matrix provided below. | ASR Activity N, C, R.NCI Code will reference TLS UNI/ENNI in RUID 2 field interface mapping on EVC page 2. | |
| EVCSP | Required - TLS UNI/ENNI Switch CLLI | ASR Activity N, C, R.This is the Switch CLLI of TLS UNI/ENNI in RUID 2 field. | |
| CE-VLAN | Required for ASR Activity C and R, Optional for N activity if customer is requesting a preferred EVC VLAN ID. Identifies the EVC VLAN ID assigned to the EVCID | Data will be repeated from Page 1 of EVC Form | |
| RUID | Required - Identifies TLS UNI/ENNI Circuit IDs for EVC connection | ASR Activity N, C, R - RUID to which the EVC is being mapped is populated on this page - EVC Page 2 | |
| LREF | Required - Identifies the Level of Service Reference Number EXAMPLE: LREF = 1 |
Data will be repeated from Page 1 of EVC Screen Page | |
| LOSACT | Required - Identifies the Activity for this Level of Service | Data will be repeated from Page 1 of EVC Screen Page | |
| LOS | Required - Identifies the Level of Service Name. Valid entries - See the EVC Levels of Service and Bandwidth Combinations Matrix below. |
Data will be repeated from Page 1 of EVC Form | |
| BDW | Required - Identifies the bandwidth rate defined by the Level of Service EXAMPLE: 10M Valid entries - See the EVC Levels of Service and Bandwidth Combinations Matrix below. |
Data will be repeated from Page 1 of EVC Form | |
| REMARKS | Customer remarks. | Customer remarks for additional information. | |
| PG_of_ | Provides page numbers contained in the EVC transaction. EXAMPLE:PG 0 0 2 of 0 0 2 |
Identifies the page number and total number of pages contained in this transaction. | |
Network Channel / Network Channel Indicator
NC/NCI CODES FOR EVC
| NC CODE | NCI CODE |
|---|---|
| VLP- | 02VLN.UL3 02VLN.UNT 02VLN.V 02VLN.VP |
FOR ERS Standard UNI to ERS Standard UNI
| UNI #1 (RUID 1) | UNI #2 (RUID 2) | ||
|---|---|---|---|
| NC CODE | NCI CODE | NC CODE | NCI CODE |
| VLP- | 02VLN.UNT | VLP | 02VLN.UNT |
| VLP- | 02VLN.UNT | VLP | 02VLN.V |
| VLP- | 02VLN.V | VLP | 02VLN.V |
| VLP- | 02VLN.V | VLP | 02VLN.UNT |
For ERS Premier UNI to ERS Premier UNI
| UNI #1 (RUID 1) | UNI #2 (RUID 2) | ||
|---|---|---|---|
| NC CODE | NCI CODE | NC CODE | NCI CODE |
| VLP- | 02VLN.UL3 | VLP | 02VLN.UL3 |
| VLP- | 02VLN.UL3 | VLP | 02VLN.VP |
| VLP- | 02VLN.VP | VLP | 02VLN.VP |
| VLP- | 02VLN.VP | VLP | 02VLN.UL3 |
02VLN.UL3 - VALID FOR ERS PREMIER UNI
2 Conductors
Ethernet Virtual Connection (EVC) Termination (EVC/UNI Map Type)
PORT + UNTAGGED FRAMES + DSCP/TOS MAP (This EVC accepts only untagged frames ingressing the UNI, and ALSO supports multiple classes of service distinguished via Layer 3 DSCP/TOS)
02VLN.UNT - VALID FOR ERS STANDARD UNI
2 Conductors
Ethernet Virtual Connection (EVC) Termination (EVC/UNI Map Type)
PORT + UNTAGGED FRAMES MAP (This EVC maps to all untagged frames on a UNI)
02VLN.V - VALID FOR ERS STANDARD UNI
2 Conductors
Ethernet Virtual Connection (EVC) Termination (EVC/UNI Map Type)
PORT + VLAN MAP (This EVC accepts only TAGGED frames with specific CEVLAN ID(s))
02VLN.VP - VALID FOR ERS PREMIER UNI
2 Conductors
Ethernet Virtual Connection (EVC) Termination (EVC/UNI Map Type)
PORT + VLAN + PBIT MAP (This EVC accepts only TAGGED frames with a specific CEVLAN ID(s) and ALSO supports multiple classes of service distinguished via Pbit)
| Service Description | NC Code | CKL 1 NCI | CKL 2 NCI |
|---|---|---|---|
| ERS Standard EVC - One Level of Service permitted | VLP- | ||
| 02VLN.UNT | 02VLN.UNT 02VLN.V | ||
| 02VLN.V | 02VLN.V 02VLN.UNT | ||
| ERS Premier Basic - Multiple Levels of Service | VLP- | ||
| 02VLN.UL3 | 02VLN.UL3 | ||
| 02VLN.VP | 02VLN.VP | ||
| ERS Premier Basic - One Level of Service permitted | VLP- | ||
| 02VLN.UL3 | 02VLN.VP | ||
| 02VLN.VP | 02VLN.UL3 | ||
| ERS Premier Priority Data - Multiple Levels of Service | VLP- | ||
| 02VLN.UL3 | 02VLN.UL3 | ||
| 02VLN.VP | 02VLN.VP | ||
| ERS Premier Priority Data - One Level of Service permitted | VLP- | ||
| 02VLN.UL3 | 02VLN.VP | ||
| 02VLN.VP | 02VLN.UL3 | ||
| ERS Premier Real Time - Multiple Levels of Service | VLP- | ||
| 02VLN.UL3 | 02VLN.UL3 | ||
| 02VLN.VP | 02VLN.VP | ||
| ERS Premier Real Time - One Level of Service permitted | VLP- | ||
| 02VLN.UL3 | 02VLN.VP | ||
| 02VLN.VP | 02VLN.UL3 |
EVC LEVELS OF SERVICE AND BANDWIDTH COMBINATIONS
For each EVC the customer is required to provide level(s) of service for the EVC and specific bandwidth(s) for the EVC.
Below are the valid combinations for EVC ERS Standard and EVC ERS Premier requests.
| Service Description | Level of Service | Bandwidths |
|---|---|---|
| ERS Standard | STANDARD | 10M, 100M, 1000M |
| ERS Premier | BASIC | 1M, 2M, 3M, 4M, 5M, 6M, 7M, 8M, 9M, 10M, 20M, 30M, 40M, 50M, 60M, 70M, 80M, 90M, 100M, 200M, 300M, 400M, 500M, 600M, 700M, 800M, 900M, 1000M |
| ERS Premier | PRIORITY DATA | 1M, 2M, 3M, 4M, 5M, 6M, 7M, 8M, 9M, 10M, 20M, 30M, 40M, 50M, 60M, 70M, 80M, 90M, 100M, 200M, 300M, 400M, 500M, 600M, 700M, 800M |
| ERS Premier | REAL TIME | 1M, 2M, 3M, 4M, 5M, 6M, 7M, 8M, 9M, 10M, 20M, 30M, 40M, 50M, 60M, 70M, 80M, 90M, 100M, 200M |
Service and Product Enhancement Code
Note: the SPEC field is not applicable for Ethernet Virtual Circuit Service.
Variable Term Agreement
Note: there are no Term Pricing Plans for EVC. All EVCs are billed month-to-month
