CORA ASR Gateway 24.0/ASOG 49 Release

1
CORA ASR Gateway 24.0/ASOG 49 Release

• September 2014

2
ASOG 49/CORA ASR Gateway 24.0

• CenturyLink will implement the ASOG Version 49
  Industry Standard changes to the ASR forms and
  fields effective on September 20, 2014.
• These changes were decided upon at an industry
  level with participating members of the OBF
  Committees. For detailed information about the
  changes, refer to the ATIS website
  http//www.atis.org/
• In support of the release, CenturyLink will
  implement upfront validations in the CORA
  (CenturyLink Online Request Application) ASR
  Gateway impacting all ASRs being transmitted
  through CORA electronically via the web-based
  CORA GUI, or through direct connections, such as
  NDM or UOM interfaces.

3
ASOG Changes

• ASOG 49

4
ASOG Issues included in this Release

• 3482 ASOG Create New Product Specific Practice
  for Ethernet Switched Port Ordering
• 3500 ASOG Update LAG field in ASR Practice 001
  to allow disconnect of entire LAG group
• 3501 - ASOG Add Autonomous System Number (ASN),
  Virtual Private Network Activity (VPN-ACT) and
  Virtual Private Network Identifier (VPN-ID)
  fields to UNI Mapping Detail Section of Practice
  016 (EVC)
• 3502 - ASOG Modify EVCSP fields Data
  Characteristics

5
ASOG 49 New Form

• New Form
• SES (Switched Ethernet Services) Service specific
  form includes all fields needed for the ordering
  of Switched Ethernet Service. Fields specific to
  this product previously residing on the Transport
  or End User forms are moving to this new form.
•  

6
ASOG 49 New Fields

• New Fields
• ESP (Ethernet Service Point) Added to the SES and
  Confirmation forms. Identifies the Ethernet
  switching point, terminating equipment or
  terminating location, in CLLI code format, at the
  UNI/ENNI termination.
• ASN (Autonomous System Number) Added to the EVC
  form. Indicates the unique number identifying the
  customer Internet network ordering the Border
  Gateway Protocol (BGP) service.
• VPN-ACT (Virtual Private Network Activity) Added
  to the EVC form. Identifies the activity
  requested for the VPN-ID.
• VPN-ID (Virtual Private Network Identification)
  Added to the EVC form. Indicates a unique
  identifier for the virtual private network that
  creates a secure network connection over a public
  network.

7
ASOG 49 Modified Fields

• Modified Fields
• ASR Form
• Add SEI (Switched Ethernet Indicator) moved from
  Transport End User forms
• LAG (Link Aggregation Group) will be updated with
  an ACT entry of D
• QSA (Quantity Service Address) modified usage
  rule
• Transport Form
• Removed the following fields BI, BUM, ES, IPAI,
  IP ADDRESS, PROFE, PROFI, SBDW, SEI, and SUBNET
  MASK. These will be added to the SES (Switched
  Ethernet Services) form.
• End User Form
• Removed the following fields BI, BUM, ES, IPAI,
  IP ADDRESS, PROFE, PROFI, SBDW, SEI, and SUBNET
  MASK. These will be added to the SES (Switched
  Ethernet Services) form.
• EVC Form
• EVCSP (Ethernet Virtual Connection Switch Point)
  modified data characteristics

8
CORA 24.0 Edits and Enhancements

• CORA 24.0

9
CORA 24.0 New Validations

• EVCSP (Ethernet Virtual Connection Switch Point)
  is being modified specific to CTL as
• To only allow 11 character CLLI codes.
• LAG (Link Aggregation Group) is being modified
  as
• Prohibited when the ACT field is not "N", "C", or
  "D" and the REQTYP is not "E" or "S". An entry
  of "N" or "E" is prohibited if the QTY field is
  populated with a value greater than 8. An entry
  of N or E is only valid when the SPEC field is
  MOENN, BGPLU, G8032 and MCLAG.
• ASN (Autonomous System Number) is being added
  with the following requirement
• If the ASN is populated the VPN-ID field is
  required.
• VPN-ID (Virtual Private Network Identifier) is
  being added with the following requirement
• Required when ordering EVC SPEC BGPLU and ASN
  is populated and all of the associated S-VLAN
  fields are not populated. When ordering VPN-ID
  the range must be 0 (zero) to 4294967295 this is
  the only valid range.

10
CORA 24.0Changed Validations

• EVC SVLAN (Service Virtual Local Area Network)
• At least the first occurrence of the SVLAN field
  is required when the associated UACT field is C,
  the associated NCI code contains a "V" in the 7th
  position and the 9th position is a T. (EXAMPLE
  NCI 02VLN.VxT)
• If the SVLAN is not populated, the UACT is "C",
  the 7th position of the NCI is "V" and the 9th
  position is a T, present a new edit Required
  when the associated UACT field is "C" and the
  associated NCI code specifies an S-VLAN based
  map.
• Any entry in SVLAN is prohibited when the 7th
  position of the NCI field is not "V and the 9th
  position is a T.
• If any SVLAN is populated, and the 7th position
  of the NCI field is not "V" and the 9th position
  is a T, present a new edit Prohibited when the
  associated NCI code does not specify an S-VLAN
  based map.
• SVLAN is prohibited when VPN-ID is populated.

11
CORA 24.0 REQTYP for Ring

• Remove the REQTYP edit for Ring as indicated
  below
• The circuit ID in the ASR ECCKT field begins
  with "HN
•  
• ACT C, D, M, or R
• REQTYP R

12
CORA 24.0 GUI Modifications

• Service Type field will be modified
• Remove EVC - Combo - End User (E) and EVC - Combo
  - Transport (S).
• Replace with EVC - Combo (E,S). REQTYP E
  requires a SALI form. REQTYP S prohibits the SALI
  form. SES - Switched Ethernet Services (E, S).
• Note customer would select REQTYP of E or S
  manually. REQTYP E requires a SALI form. REQTYP S
  prohibits the SALI form.

13
CORA 24.0 GUI Modifications

• Reports Tab
• Remove EVC - Combo - End User and EVC - Combo
  Transport.
• Replace with EVC Combo - Switched Ethernet in
  the "Service Type" pull down.

14
CORA 24.0 GUI Modifications

• Reports Tab New
• In the Select Service Type pull down a new
  option of Switched Eternet form (with E or S as
  REQTYP) will be available.

15
CORA 24.0 GUI Modifications

• Restructure Function
• If a customer requests a Combo (SES EVC) and
  wants to change to SES or EVC only, this change
  would only apply prior to ASR being submitted.
• SALI SANO
• When the REQTYP is E and the SEI field Y, the
  customer is required to populate the SALI.SANO
  and SALI.SASN fields. The entry in the SI field
  must be a "C" if populated.
• SALI SPOT
• When the REQTYP is E and the SEI field Y, the
  customer is required to populate the SALI.SI and
  SALI.SPOT fields. The entry in the SPOT field
  must be a valid 8 or 11 CLLI code.

16
CORA 24.0 GUI Modifications

• SALI (Service Address Location Information) for
  SES (Switched Ethernet Services) field will be
  modified
• For REQTYP E a tab will be labeled as Priloc
  SALI.
• Replace with EVC - Combo (E,S) Note customer
  will be required to select REQTYP of E or S
  manually. REQTYP E requires a SALI form. REQTYP S
  prohibits the SALI form. SES - Switched Ethernet
  Services (E, S).