6 - Standards for Access Service Request

Abstract

Selling carrier Ethernet (CE) services to off-net customers over peering carrier Ethernet networks (CENs) requires service providing operators to purchase E-access service from access providing operators. This purchase order known as access service request (ASR) constitutes a business-to-business (B2B) transaction. To ensure that there is no confusion about what is being requested, standardization of these request forms is required. This chapter provides brief descriptions of various access service request forms available from the Ordering and Billing Forum (OBF) which manages these forms and is part of an industry organization called the Alliance for Telecommunications Industry Solutions (ATIS). The chapter then identifies those forms that are specifically used for E-access service with the caveat that operators have some deviations in implementing these forms. Details of fields in those E-access service-specific forms are then provided in this chapter. While describing these fields, the chapter identifies some Common Language codes needed in these ASR forms. These Common Language codes are maintained by an organization called iConnective which owns its trade mark as well. Because MEF specifies attributes and parameters and ASR forms use Common Language codes to order required attributes and parameters, this chapter compares MEF-specified attributes and parameters, and ASR required Common Language codes and identifies areas where further clarification in mapping of attributes and parameters to Common Language codes would help in the implementation of this new and fast-emerging E-access service for peering CENs. The access service request (ASR) is generally preceded by selling activities and succeeded by a long chain of activities that includes ordering, design, order management, provisioning, installation coordination, preservice testing, service turn-up, billing and maintenance including ongoing coordination of testing and trouble resolution for all operator-provided facilities. Automation or mechanization of these activities is highly desirable. Large and complex IT systems called operations and business support systems (OSS/BSS) provide automation or mechanization of these and some more activities. This chapter provides a transition to OSS/BSS systems which is the topic of our Chapter 7.