Wholesale: Products & Services

Archived System CR SCR111714-1IG Detail

The CORA ASR Gateway application is being updated to support changes for ASOG 50, including ASOG, Mech Spec and UOM-ASR Schema changes as mandated by OBF. Details of the ASOG 50 industry changes can be found at: http://www.atis.org/. New or changed fields and forms being added to the ASOG form package are as follows:

• MUXLOC usage rules for multiple circuit occurrences updated on FG A, Trunking, Transport and EUSA to note MUXLOC applies to all CFAs on the ASR

• SMUXLOC usage rules for multiple circuit occurrences updated on Trunking, Transport and EUSA to not SMUXLOC applies to all SCFAs on the ASR

• L2CP (Layer Two Control Protocol) Removed from EVC form

• LC2PP (Layer Two Control Protocol Peering) Identifies a set of peering protocols that are used for various control purposes that allow the Ethernet network to effectively process information for subscribers who choose to deploy 802.1Q bridges. Added to the SES, Transport and End User forms

• L2CP-ADDR (Layer Two Control Protocol Address) Identifies the discard/pass action for all non-peered layer two control protocols. Added to the SES, Transport and End User forms

• BUM-FD (Broadcast, Unicast and Multicast Frame Delivery) Identifies the service frame delivery disposition for Broadcast, Unicast and Multicast service frames outside of the provider’s specified throttling defaults for those providers who bill and/or provision at the port level. Added to the EVC form.

• CEV-P (CE-VLAN Identification Preservation) Identifies if the VLAN ID portion of the Customer Edge VLAN Tag is preserved. Added to the EVC form.

• CEV-CP (CE-VLAN Class of Service Preservation) Identifies if the VLAN Class of Service (CoS) portion of the Customer Edge VLAN Tag is preserved. Added to the EVC form.

• MSFS (Maximum Service Frame Size) Indicates the Maximum Service Frame Size allowed (in bytes) for the EVC. Added to the EVC form.

• SM (Synchronous Mode) Indicates if the bits transmitted from the provider network to the customer edge will need a clock reference based synchronous Ethernet UNI. Added to the ACI and SES form.

• UNI-MSFS (UNI Maximum Service Frame Size) Indicates the Maximum Service Frame Size (in bytes) allowed at the UNI. Added to the ACI, EUSA, Transport, SES forms.

• Bandwidth Profile on EVC form at LREF level

- BCF-I (Bandwidth Coupling Flag – Ingress) Identifies when color-aware markings should be enabled for customer marked EIR traffic to use available CIR Bandwidth.

- CBS-I (Committed Burst Size – Ingress) Identifies the Bandwidth Profile parameter that limits the maximum number of bytes available for a burst of Service Frames sent at the UNI/ENNI that will be delivered by the service provider based on the level of service performance.

- CIR-I (Committed Information Rate - Ingress) Identifies the average rate (bits per second) up to which service frames are delivered as defined in the provider’s service level specification.

- CMI-I (Color Mode Identifier – Ingress) Identifies when the provider configuration will use the specific customer Class of Service (CoS) markings when applying the Bandwidth Profile CIR/EIR.

- EBS-I (Excess Burst Size – Ingress) Identifies the Bandwidth Profile parameter that limits the maximum number of bytes available for a burst of Service Frames associated with the EIR-I sent at the UNI/ENNI that will be delivered by the service provider based on the level of service performance.

- EIR-I (Excess Information Rate – Ingress) Identifies the average rate (bits per second) up to which service frames may be delivered but will not be guaranteed per the provider’s service level specification.

• SR new valid value of M added on EUSA form

• ACIC new usage note added making the field prohibited on the TQ form when WST is populated

• CIC new usage note added making the field prohibited on the TQ form when placing Wireless service request populating the WST

• BI definition notes updated, usage notes changed and new of ‘A’ added on ACI and SES forms

• HVP (High Voltage Protection) new field added to SES form

• WKTEL updated definition note to include land line on SALI form

Company Specific Edits:

New CORA Pre-Order Validations - None

New CORA GUI and ASR Gateway Validations:

• Add HVP field to the Switched Ethernet Services Form - When the valid entry is “Y”, the provider will contact the customer for the necessary detail. This field is conditional. Prohibited when ACT is D on the ASR form, otherwise optional.

• Add L2CPP, L2CP-ADDR, UNI-MFS fields to the Transport Form – CenturyLink specific validation - This field is not used and is prohibited.

• Add UNI-MFS and SM fields to the ACI Form - CenturyLink specific validation - This field is not used and is prohibited.

• Add L2CPP, L2CP-ADDR, UNI-MFS, and SM fields to the SES Form – CenturyLink specific validation - This field is not used and is prohibited.

• Add L2CPP, L2CP-ADDR, UNI-MFS fields to the EUSA Form – CenturyLink specific validation - This field is not used and is prohibited.

• Add CEV-P, CEV-CP, and BUM fields to the EVC form - CenturyLink specific validation - This field is not used and is prohibited.

• Add CIR-I, CBS-I, EIR-I, EBS-I, CMI-I, AND BCF-I to the EVC form at LREF level - CenturyLink specific validation - This field is not used and is prohibited. LREF-related elements associated with OBF Issue 3508 are not supported at this time.

CORA GUI Changes:

• ASR SEI Validation Rule Change

- From: Reject if SEI is Y and first position of REQTYP is not S or E and 3rd and 4th positions of SES.SECNCI, EUS.SECNCI or TRANS.SECNCI are not CX.

-To: Reject if SEI is Y and first position of REQTYP is not S or E and 3rd and 4th positions of SES.SECNCI is not CX and ACT is not D.

• TransMuxloc Validation for SCFA

- Validate SMUXLOC is populated with 8 or 11 character CLLI code and must match ALOC or ZLOC CLLI code in SCFA.

- Add the following edit: If SECLOC=E, SPOT field on SALI form is required and must match ALOC or ZLOC 8 character CLLI code of SCFA. Not valid for REQTYPE=M.

• TRK.SMUXLOC Validation Rule

- Old Edit: Reject when ASR.ACT is not N, SCFA does not start with NEW, TRK.SMUXLOC is not found in TRK.SCFAReports Tab create new tab

- New Edit: Reject when ASR.ACT is not N or D, SCFA does not start with NEW, TRK.SMUXLOC is not found in TRK.SCFA

• SES.GTEL Validation

- Usage NOTE 1: Required when the GCON field is populated, otherwise prohibited

- New Business Rule: GCON prohibited when GETO = W (W: Bill to Carrier)

CORA GUI and ASR Gateway

Conversion:

CORA GUI Report enhancements: None

ASR Gateway Notifications/Responses: None

Proposed Implementation Date:

March 23, 2015

Status History

Project Meetings

3/18/2015 Monthly Systems CMP Meeting Mark Coyne – CenturyLink stated the CORA release is scheduled for implementation March 23, 2015.

2/18/2015 Monthly Systems CMP Meeting Mark Coyne – CenturyLink said the Draft Tech specs were sent on January 9, 2015. A Technical walkthrough was held Monday, January 19, 2015 and the Final Tech specs were sent February 6, 2015. The CORA GUI notice is scheduled for February 23, 2015. The CORA Release is scheduled for implementation March 23, 2015.

1/21/2015 Monthly Systems CMP Meeting Mark Coyne – CenturyLink said the Draft Tech specs were sent on January 9, 2015. A Technical walkthrough was held Monday, January 19, 2015. The CORA Release is scheduled for implementation March 23, 2015.

12/17/2014 Monthly Systems CMP Meeting Mark Coyne – CenturyLink said the Draft Tech specs are due on January 9, 2015. A Technical walkthrough is scheduled for Monday, January 19, 2015 at 10 am MT. The Release is scheduled for implementation March 23, 2015.

11/19/2014 Monthly Systems CMP Meeting Mark Coyne – CenturyLink relayed we have a CenturyLink walk-on CR to be presented. The CR is not in the monthly package but is posted separately to the calendar.

Bill West – CenturyLink presented this new walkon CR associated with the ASOG 50 Industry Guidelines and the CORA Release 25.0. He reviewed the ASOG 50 Industry Changes as listed in the CR Description. Bill said the proposed implementation date is March 23, 2015. Bill asked if there were any questions on the ASOG changes. There were none. Sue Morlan – CenturyLink then reviewed the CORA Company Specific Edits and the CORA GUI changes as listed in the CR Description. Sue asked if there were any questions.

Lynn Denton – Windstream asked when these CR/release changes would be documented and distributed.

Sue Morlan – CenturyLink said she thought there will be a customer walkthrough in February 2015 but a Release notice would provide the specific dates.

NOTE – CMP CALL FOLLOWUP: The technical specifications timeline for the CORA Release 25.0 is: - Draft Technical Specifications Issued January 9, 2015 - Final Technical Specifications Issued February 6, 2015 - Draft ASR CORA GUI Documentation Issued February 23, 2015 - Final ASR CORA GUI Documentation Issued March 2, 2015 - Release Production Date March 23, 2015 The specific date when the customer walkthrough will be held in January 2015 has not yet been determined. More detailed information for this CORA release is available on the CenturyLink OSS Release Calendar on the Wholesale web site at http://www.centurylink.com/wholesale/cmp/teammeetings.html.

CenturyLink Response