ࡱ > e g ` a b c d / f D bjbj > ڇ ڇ 3.
xQ xQ ^ ^ h h h h h h 8 h j h R X yo 2 z p { { { * y 6 ð , \
h C C C ^ ^ { { 8 C ^ { h { C y l e < " 0 R e ( b b X h h C C C C C C R b C C C C C C C C C xQ ] :
Maintenance Ticketing Gateway
CenturyLink
Interface Specification
September 25, 2014
For MTG Software Version 1.7
Versioning
All releases of this document are listed in chronological order.
There is no relationship between the document number and the software release number.
Document ReleaseDateDescription0.1August 5, 2011Early draft.
An official documentation review will be held at a later date to review the details of this document.0.2August 24, 2011The document is ready for official documentation review.1.0September 2, 2011The document is published.
Technical corrections are in Appendix A.
Added notes to last two rows of the table in Section 3, MTG Ticketing System XSD Usage.
Added missing ACKs to diagrams in Section 1.5, Customer-CenturyLink MTG Transactions.
Added sentence (Please refer to the MTG Implementation Document for additional required elements by transaction.) to Section 4, Required Data, Per Transaction.
Restructured version numbering system to show this version as release 1.0 and previous versions as point releases/drafts.1.1September 21, 2011Updated tML-TABase.xsd1.2October 8, 2012Updated Section 6.2, Response Normal (Full TestRequestType is 1)1.3 DraftDecember 19, 2012Added clarification to Authentication section(2.3.1) and Response WSDL section(2.4.2).1.3 FinalJanuary 18, 2013Added clarification to Authentication section(2.3.1) and Response WSDL section(2.4.2). For production March 4, 20131.4 DraftFebruary 26, 2013Added clarification to the Authentication section (2.3.1). For production April 20, 20131.4 FinalMarch 15, 2013Added clarification to the Authentication section (2.3.1). For production April 20, 20131.5 DraftApril 19, 2013Added clarification to the TrackID information in section 2.4.4. For June 30, 20131.5 FinalMay 16, 2013Added clarification to the TrackID information in section 2.4.4. For June 30, 20131.6 DraftJune 11, 2014Updated the examples of tML-TA for GMT with the suffix Z in Sections 5.2, 5.8, 5.13.1, 5.13.2, 5.13.3, 5.13.4 and 5.13.5. 1.7 Draft
August 28, 2014Document update in support of the added functionality to perform Client Self Test before creating Design repair ticket. For production date of November 09th, 2014.1.7 FinalSeptember 25, 2014Document update in support of the added functionality to perform Client Self Test before creating Design repair ticket. For production date of November 09th, 2014.1.7 Final UpdateNovember 10, 2014Document is updated with additional Sample SOAP Ack message (Sections 2.5.6, 2.5.7 and 2.5.8), and examples of tML for Client Self Test Request and Responses (Sections 7.1, 7.2 and 7.3).
Copyright and Trademarks
( 2014 CenturyLink, Inc. All Rights Reserved. The CenturyLink mark, pathways logo and certain CenturyLink product names are the property of CenturyLink, Inc. All other marks are the property of their respective owners.
Disclaimer
This document provides an overview of a CenturyLink service. It is intended to assist users in determining the type and structure of information requested and returned by the service.
The information contained herein does not constitute an offer by CenturyLink to provide services, equipments, or materials. Any such services and items will only be provided pursuant to an effective agreement between CenturyLink and the customer.
Contents
TOC \o \f \h \z \u HYPERLINK \l "_Toc403146846" 1 Introduction PAGEREF _Toc403146846 \h 6
HYPERLINK \l "_Toc403146847" 1.1 Using these CenturyLink Business Services PAGEREF _Toc403146847 \h 7
HYPERLINK \l "_Toc403146848" 1.2 Other Documents PAGEREF _Toc403146848 \h 7
HYPERLINK \l "_Toc403146849" 1.3 Implemented Requests, Responses, and Notifications PAGEREF _Toc403146849 \h 7
HYPERLINK \l "_Toc403146850" 1.4 Mapping CenturyLink and Customer Transactions to the ATIS Services PAGEREF _Toc403146850 \h 8
HYPERLINK \l "_Toc403146851" 1.5 Customer-CenturyLink MTG Transactions PAGEREF _Toc403146851 \h 9
HYPERLINK \l "_Toc403146852" 1.5.1 Customer-initiated Create Ticket PAGEREF _Toc403146852 \h 9
HYPERLINK \l "_Toc403146853" 1.5.2 Customer-initiated Update Ticket PAGEREF _Toc403146853 \h 10
HYPERLINK \l "_Toc403146854" 1.5.3 Customer-initiated Cancel Ticket PAGEREF _Toc403146854 \h 10
HYPERLINK \l "_Toc403146855" 1.5.4 Customer-initiated Retrieve Ticket PAGEREF _Toc403146855 \h 11
HYPERLINK \l "_Toc403146856" 1.5.5 CenturyLink-initiated Update Ticket (Status/Log Notes Update) PAGEREF _Toc403146856 \h 11
HYPERLINK \l "_Toc403146857" 1.5.6 CenturyLink-initiated Cleared Ticket (Design Service) PAGEREF _Toc403146857 \h 12
HYPERLINK \l "_Toc403146858" 1.5.7 CenturyLink-initiated Cleared/Closed Ticket (POTS Service) PAGEREF _Toc403146858 \h 13
HYPERLINK \l "_Toc403146859" 2 Communication Protocol PAGEREF _Toc403146859 \h 14
HYPERLINK \l "_Toc403146860" 2.1 Communication Requirements PAGEREF _Toc403146860 \h 14
HYPERLINK \l "_Toc403146861" 2.2 Access Topology PAGEREF _Toc403146861 \h 14
HYPERLINK \l "_Toc403146862" 2.3 Security PAGEREF _Toc403146862 \h 15
HYPERLINK \l "_Toc403146863" 2.3.1 Authentication PAGEREF _Toc403146863 \h 15
HYPERLINK \l "_Toc403146864" 2.3.2 Validation of Ownership (Authorization) PAGEREF _Toc403146864 \h 16
HYPERLINK \l "_Toc403146865" 2.4 WSDL PAGEREF _Toc403146865 \h 16
HYPERLINK \l "_Toc403146866" 2.4.1 Request WSDL PAGEREF _Toc403146866 \h 16
HYPERLINK \l "_Toc403146867" 2.4.2 Response WSDL PAGEREF _Toc403146867 \h 18
HYPERLINK \l "_Toc403146868" 2.4.3 SOAP Interface PAGEREF _Toc403146868 \h 19
HYPERLINK \l "_Toc403146869" 2.4.4 tMLHeader PAGEREF _Toc403146869 \h 19
HYPERLINK \l "_Toc403146870" 2.5 Request/Response PAGEREF _Toc403146870 \h 21
HYPERLINK \l "_Toc403146871" 2.5.1 Sample SOAP Request to CenturyLink Request Web Service PAGEREF _Toc403146871 \h 21
HYPERLINK \l "_Toc403146872" 2.5.2 Sample SOAP ACK Message from CenturyLink PAGEREF _Toc403146872 \h 21
HYPERLINK \l "_Toc403146873" 2.5.3 Sample SOAP Response to Customers Result Web Service PAGEREF _Toc403146873 \h 21
HYPERLINK \l "_Toc403146874" 2.5.4 Sample SOAP ACK Message from Customers Result Web Service PAGEREF _Toc403146874 \h 21
HYPERLINK \l "_Toc403146875" 2.5.5 Sample SOAP Fault Message (NACK) from CenturyLink PAGEREF _Toc403146875 \h 21
HYPERLINK \l "_Toc403146876" 2.5.6 Sample SOAP ACK Message from CenturyLink for Non-Intrusive Client Self Test PAGEREF _Toc403146876 \h 22
HYPERLINK \l "_Toc403146877" 2.5.7 Sample SOAP ACK Message from CenturyLink for Full, Loop Back and Supplemental Intrusive Client Self Test PAGEREF _Toc403146877 \h 22
HYPERLINK \l "_Toc403146878" 2.5.8 Sample SOAP Fault Message (NACK) from CenturyLink for all types of Client Self Tests PAGEREF _Toc403146878 \h 22
HYPERLINK \l "_Toc403146879" 3 MTG Ticketing System XSD Usage PAGEREF _Toc403146879 \h 23
HYPERLINK \l "_Toc403146880" 4 Required Data, Per Transaction PAGEREF _Toc403146880 \h 24
HYPERLINK \l "_Toc403146881" 4.1 RequestTroubleReportCreationRequest PAGEREF _Toc403146881 \h 24
HYPERLINK \l "_Toc403146882" 5 Examples of tML-TA for Trouble Ticketing PAGEREF _Toc403146882 \h 26
HYPERLINK \l "_Toc403146883" 5.1 RequestTroubleReportCreationRequest PAGEREF _Toc403146883 \h 26
HYPERLINK \l "_Toc403146884" 5.2 RequestTroubleReportCreationResponse PAGEREF _Toc403146884 \h 31
HYPERLINK \l "_Toc403146885" 5.3 ModifyAttributesRequest PAGEREF _Toc403146885 \h 32
HYPERLINK \l "_Toc403146886" 5.4 ModifyAttributesResponse PAGEREF _Toc403146886 \h 33
HYPERLINK \l "_Toc403146887" 5.5 CancelTroubleReportRequest PAGEREF _Toc403146887 \h 33
HYPERLINK \l "_Toc403146888" 5.6 CancelTroubleReportResponse PAGEREF _Toc403146888 \h 34
HYPERLINK \l "_Toc403146889" 5.7 RetrieveAttributesByTroubleReportIdRequest PAGEREF _Toc403146889 \h 34
HYPERLINK \l "_Toc403146890" 5.8 RetrieveAttributesByTroubleReportIdResponse PAGEREF _Toc403146890 \h 35
HYPERLINK \l "_Toc403146891" 5.9 VerifyRepairCompletionRequest PAGEREF _Toc403146891 \h 41
HYPERLINK \l "_Toc403146892" 5.10 VerifyRepairCompletionResponse PAGEREF _Toc403146892 \h 42
HYPERLINK \l "_Toc403146893" 5.11 AddTroubleInfoRequest PAGEREF _Toc403146893 \h 42
HYPERLINK \l "_Toc403146894" 5.12 AddTroubleInfoResponse PAGEREF _Toc403146894 \h 43
HYPERLINK \l "_Toc403146895" 5.13 AttributeValueChangeNotification PAGEREF _Toc403146895 \h 43
HYPERLINK \l "_Toc403146896" 5.13.1 Event Notification (Additional Trouble Status Info Added) PAGEREF _Toc403146896 \h 43
HYPERLINK \l "_Toc403146897" 5.13.2 Design Services Cleared Notification PAGEREF _Toc403146897 \h 44
HYPERLINK \l "_Toc403146898" 5.13.3 Design Services Closed Notification PAGEREF _Toc403146898 \h 46
HYPERLINK \l "_Toc403146899" 5.13.4 POTS Cleared Notification PAGEREF _Toc403146899 \h 46
HYPERLINK \l "_Toc403146900" 5.13.5 POTS Closed Notification PAGEREF _Toc403146900 \h 47
HYPERLINK \l "_Toc403146901" 6 Examples of tML for POTS Service Test PAGEREF _Toc403146901 \h 49
HYPERLINK \l "_Toc403146902" 6.1 Request PAGEREF _Toc403146902 \h 49
HYPERLINK \l "_Toc403146903" 6.2 Response Normal (Full TestRequestType is 1) PAGEREF _Toc403146903 \h 49
HYPERLINK \l "_Toc403146904" 6.3 Response Normal (Quick TestRequestType is 2) PAGEREF _Toc403146904 \h 50
HYPERLINK \l "_Toc403146905" 6.4 Response Normal (Central Office TestRequestType is 3) PAGEREF _Toc403146905 \h 51
HYPERLINK \l "_Toc403146906" 6.5 Response Normal (Loop Test TestRequestType is 4) PAGEREF _Toc403146906 \h 52
HYPERLINK \l "_Toc403146907" 7 Examples of tML for Client Self Test PAGEREF _Toc403146907 \h 54
HYPERLINK \l "_Toc403146908" 7.1 Request PAGEREF _Toc403146908 \h 54
HYPERLINK \l "_Toc403146909" 7.2 Response - Normal PAGEREF _Toc403146909 \h 54
HYPERLINK \l "_Toc403146910" 7.3 Response Error Exception PAGEREF _Toc403146910 \h 55
HYPERLINK \l "_Toc403146911" 8 Glossary PAGEREF _Toc403146911 \h 56
HYPERLINK \l "_Toc403146912" Appendix A: Corrections PAGEREF _Toc403146912 \h 57
Introduction
This document is intended for organizations wishing to implement electronic trouble ticketing capabilities with CenturyLink for the exchange of Trouble Ticket information for various CenturyLink products and services purchased by the customer.
CenturyLinks Maintenance Ticketing Gateway (MTG) provides a mechanism to automate communication and the processing of trouble ticket information. This mechanism is available for use by Wholesale customers of legacy Qwest.
MTG provides an electronic bonding facility that enables CenturyLink customers of legacy Qwest to use their own repair/ticketing system to manage troubles on their CenturyLink products and services in legacy Qwest territory. This application is used primarily to mechanically process telephone circuit repair activities including repair ticket generation, MLT (Mechanized Loop Tests) and CST (Client Self Test).
MTG is available for use only in legacy Qwest territories in the following states:
Arizona
Colorado
Idaho
Iowa
MinnesotaMontana
Nebraska
New Mexico
North Dakota
OregonSouth Dakota
Utah
Washington
Wyoming
The CenturyLink MTG Ticketing System is based on:
ATIS Standard XML Schema Interface for Fault Management (Trouble Administration), ATIS-0300003.2010, an industry standard for exchange of trouble ticket information
ATIS- 0300079 tML Transport Profile: This document recommends a Transport Profile Specification to support the Telecommunications Markup Language (tML) Framework. The intent is to facilitate the interchange of XML formatted business transactions between service requestor and service provider. MTG does not implement every detail of the transport profile, but does use many of the asynchronous concepts described within the guidelines.
XML POTS Service Test ATIS-0300002.2009, XML Schema Interface for POTS Service Test. This standard provides an XML schema information model for POTS Service Test based on ATIS-0300262.2007 and an XML schema interface for POTS Service Test function specified in the same ANSI standard.
This service uses Telecommunication Markup Language (tML).
Example tMLs in this document demonstrate requests, responses, and notifications for particular situations.
Using these CenturyLink Business Services
The use of the CenturyLink Maintenance Ticketing Gateway via tML provides an effective mechanism to automate the communication and processing of trouble ticket information. If you determine that your company can support a tML environment, and you would like to conduct business with CenturyLink via the CenturyLink Maintenance Ticketing Gateway (MTG), contact your CenturyLink Service Manager (SM).
This document provides business service overviews, designed to help you in understanding requests, responses, and notifications, and how those data are organized in the XSD request, response (if any), and standalone notifications.
Because this is a web services interface, there are no dedicated circuit requirements for access. Customers must have internal policies and processes in place to support sending and receiving trouble ticket transactions over the public Internet.
Other Documents
Detailed implementation specifics will be provided in the MTG Implementation Document.
Implemented Requests, Responses, and Notifications
The following requests, responses, and notifications are used:
Request/Response
RequestTroubleReportCreation
CancelTroubleReport
VerifyRepairCompletion
ModifyAttributes
RetrieveAttributesByTroubleReportId
AddTroubleInfo
POTSUncontrolledTest
Notifications
AttributeValueChangeNotification
The mapping of CenturyLink/Customer business transactions and the ATIS services shown above is detailed in the mapping section of this specification document.
Mapping CenturyLink and Customer Transactions to the ATIS Services
The table below maps transaction types to ATIS-specified services.
Transaction TypeATIS XSDCustomer Create Ticket ServicesCustomer creates a Trouble Ticket.RequestTroubleReportCreationRequestCenturyLink response that Ticket was created or that an exception occurred.RequestTroubleReportCreationResponseCustomer Update/Cancel Ticket ServicesCustomer updates attributes on ticket (e.g., notes, A loc information, authorizations, escalates, managed access hours).ModifyAttributesRequestCenturyLink acknowledges attributes were updated on ticket or that an exception occurred. ModifyAttributesResponseCustomer updates notes on ticket. (Call Log/Notes update).AddTroubleInfoRequestCenturyLink acknowledges notes were updated on ticket or that an exception occurred. (Call Log/Notes update) AddTroubleInfoResponseCustomer closes ticket.
Customer requests cancellation of ticket.CancelTroubleReportRequestCenturyLink acknowledges ticket cancel request was received ok or that an exception occurred. CancelTroubleReportResponseCustomer Retrieve Ticket ServicesCustomer Retrieve Ticket RequestRetrieveAttributesByTroubleReportIdRequestCenturyLink sends Customer Retrieve Ticket Response details or that an exception occurred.RetrieveAttributesByTroubleReportIdResponseCenturyLink Close Ticket ServicesCenturyLink sends request to close a ticket with cleared status (for Design Services see 1.5.6 information).AttributeValueChangeNotificationFor Design Services, Customer sends verification of issue resolution.VerifyRepairCompletionRequestCenturyLink acknowledges verify request was received ok or that an exception occurred.VerifyRepairCompletionResponseNotification ServicesCenturyLink sends Status Update notification (for POTS see 1.5.7 information).AttributeValueChangeNotificationCenturyLink sends a Ticket Log Update Notification (includes escalation information). AttributeValueChangeNotification
Customer-CenturyLink MTG Transactions
Customer-initiated Create Ticket
SHAPE \* MERGEFORMAT
Customer-initiated Update Ticket
SHAPE \* MERGEFORMAT
Customer-initiated Cancel Ticket
SHAPE \* MERGEFORMAT
Customer-initiated Retrieve Ticket
SHAPE \* MERGEFORMAT
CenturyLink-initiated Update Ticket (Status/Log Notes Update)
SHAPE \* MERGEFORMAT
CenturyLink-initiated Cleared Ticket (Design Service)
SHAPE \* MERGEFORMAT
CenturyLink-initiated Cleared/Closed Ticket (POTS Service)
SHAPE \* MERGEFORMAT
Communication Protocol
The CenturyLink MTG Ticketing System uses an asynchronous request/response model based on an implementation of the Alliance for Telecommunications Industry Solutions (ATIS) tML Transport Profile.
This interface has been designed to send and receive electronic transactions using SOAP over HTTP(s).
A partner sends a request to the CenturyLink Request Listener web service. CenturyLink will then validate that the request passes authentication and the XSD schema check, and return an acknowledgement or SOAPFault to the customer. This means the requester is not required to stay connected to the provider while a potentially lengthy request is processed. This approach allows for better error recovery (often without involving the business customer) and provides a more secure and robust interaction.
When a response to a customer request or an attribute value change notification for an existing ticket is ready for delivery, CenturyLink will attempt to push (send) the result to the customer. If the send fails because a customers system is not available due to planned maintenance outage or any other unexpected system or communication failure, CenturyLink will attempt one retry. If that retry fails, the payload of the failed transaction will not be delivered to the customer. The customer can later retrieve currentor latestticket attributes.
When communication is restored and verified, the customer may follow late bonding procedures described in the MTG Implementation Document to electronically bond any tickets created in CenturyLink during the outage period.
Communication Requirements
In order to transmit and receive data, CenturyLink customers must build their own XML client interface.
CenturyLink customers must have an XML Server Interface. The application is solely business to business (B2B).
CenturyLink customers must provide their own Internet access.
CenturyLink customers must abide by the CenturyLink XML Schema design.
Access Topology
The following diagram is an overview of the access topology into the CenturyLink XML Interface for electronic bonding trouble administration.
EMBED Visio.Drawing.11
Figure 1: CenturyLink Maintenance Ticketing Gateway
Security
Authentication
CenturyLink customers must have a Digital Certificate to make use of CenturyLink XML API.
MTG uses two-way Secure Socket Layer/Transport Layer Security (SSL/TLS) communication. The SOAP header is not used for transport security.
Please follow the X.509v3 standard.
For inbound transactions, the customer must send the CenturyLink-provided digital certificate.
For outbound transactions, CenturyLink will send the customer-provided digital certificate for client authentication.
CenturyLink has an additional option available to include partner provided username, password in plain text format under WSSE security header/ Usernametoken section inside SOAP header in the CenturyLink outbound request. With this option, the customer-provided digital certificate for client authentication is not required.
MTGs current implementation (both as client and server) is compliant with RFC 5746 and allows secure renegotiations. However, on outbound communication from MTG to Partner, if the partner server doesn't support secure renegotiations, MTG client has an option to turn off session reuse upon partners request.
Validation of Ownership (Authorization)
Create Request
The CenturyLink MTG gateway validates that a serviceId (circuit/TN) entered belongs to the Manager (i.e., customer) via MCN or ACNA/RSID comparison.
All Other Requests (After Successful Create Request)
The CenturyLink MTG gateway validates that a trouble report entered belongs to the Manager (i.e., customer).
WSDL
CenturyLink exposes two asynchronous WSDLs (document/literal wrapped SOAP Binding) for Request and Response / Attribute Value Change Notification (AVCN) messages compliant with SOAP 1.1 specifications.
CenturyLink uses XML Namespace to avoid name conflicts between tML definitions and application-specific definitions.
CenturyLink Implemented Web Services:
Process Report
Required Customer Implemented Web Services:
Process Result
Request WSDL
The Request WSDL exposes the operation named processReport.
The processReport operation accepts a String parameter (the SOAP request body contains the tML Request compliant with the tML-TA.xsd).
When message processing is successful, the CenturyLink hosted web service generates a synchronous acknowledgment, which means that the XML request was well formed and is a tML-TA compliant message.
Any exceptions in receiving the message will be communicated back to the customer as SOAPFaults.
Response WSDL
The Response WSDL must be implemented by the customer to be able to receive CenturyLink Response or AttributeValueChangeNotification transactions.
This WSDL exposes the operation name processResult.
The processResult accepts a String parameter (containing the Response or AttributeValueChangeNotification XML compliant with the tML-TA.xsd). This operation will be invoked by CenturyLink when sending Responses or AttributeValueChangeNotifications.
In SOAP Response to Customers Result Web Service, CenturyLink will send the payload wrapped in a CDATA section inside the resultString element.
SOAP Interface
The SOAP request body contains the tML Request. The SOAP response body contains the tML response or a fault message.
A SOAPFault will be generated whenever a schema validation error, data storage error, or other internal error occurs. The generated SOAPFault will include an Exception Description element that provides diagnostic information.
If a SOAPFault is received by the customer when invoking an operation it means request transaction was not processed by CenturyLink and it is the customers responsibility to resend the message, if appropriate.
tMLHeader
The tMLHeader is a required part of the payload for all request and responses to the CenturyLink MTG. The tML header is a part of the TCIF tML Transport Profile (per the tML Header Component of the tML Transport Profile (ATIS-0300079)), and is used to allow a customer to correlate asynchronous responses and trouble tickets with status updates.
The tMLHeader will include the following information.
Note: These formats are suggested implementations based on ATIS-0300079. The customer is responsible for the uniqueness of the CorrelationID and TrackID.
CorrelationID will be used to correlate a particular request or response with the acknowledgement. It is also used to specify the result to be retrieved. The CorrelationID must be unique for each request. Maximum size is 64 alphanumeric. Below is a suggested format of this field:
FROM field (up to 10 characters) (This is the UserId. Indicates where the request originates.)
TO field (up to 10 characters, after the FROM field) (This is CTL. Indicates the identity of the destination service provider.)
Send Timestamp field (maximum 30 characters) (Note: Time zone information is specified in this format see tML Header Schema Definition).
Static CorrelationID abbreviation String :CI: (4 characters)
Unique Number generated by originator (maximum 10 characters, recommended for uniqueness)
TrackID will be used to correlate multiple messages for a particular business transaction lifecycle, including requests, responses and acknowledgements. The TrackID is unique and persistent for the life of the ticket. MTG will allow the re-use of trackId, only if MTG fails to create and return TicketId in MTG response to the create ticket request. MTG will also allow the re-use of trackID on MLT and CST requests that failed to process in MTG. Maximum size is 64 alphanumeric. Below is a suggested format of this field:
FROM field (up to 10 characters) (This is the UserId. Indicates where the request originates.)
TO field (up to 10 characters, after the FROM field) (This is CTL. Indicates the identity of the destination service provider.)
Send Timestamp field (30 characters) (Note: Time zone information is specified in this format see tML Header Schema Definition).
Static TrackID abbreviation String :TI: (4 characters)
Unique Number generated by originator (10 characters)
Request/Response
Sample SOAP Request to CenturyLink Request Web Service
tML TA Request goes here...
Sample SOAP ACK Message from CenturyLink
Sample SOAP Response to Customers Result Web Service
tML TA Result in CDATA goes here...
Sample SOAP ACK Message from Customers Result Web Service
Sample SOAP Fault Message (NACK) from CenturyLink
SOAP-ENV:ClientValidation ErrorDetailed error message here
Sample SOAP ACK Message from CenturyLink for Non-Intrusive Client Self Test
Sample SOAP ACK Message from CenturyLink for Full, Loop Back and Supplemental Intrusive Client Self Test
Warning this is an Intrusive Test. The circuit will be taken out of service for the duration of the test
Sample SOAP Fault Message (NACK) from CenturyLink for all types of Client Self Tests
SOAP-ENV:ClientValidation ErrorDetailed error message here
MTG Ticketing System XSD Usage
The four XSDs shown in the table below are in the embedded files below.
Note: Not all elements contained in the XSDs are supported in the MTG implementation. Please see MTG Implementation document for details.
Schema NameDescriptionNotestML-TA.xsdIndustry schema that defines TML TA interface.CenturyLink adds complex elements to the ATIS specification.tML-TABase.xsdAn industry schema that defines TML TA base elements.CenturyLink adds complex elements to the ATIS specification.tML-ServiceTest.xsdIndustry schema that defines POTS Service Test interface.Used for MLT (Mechanized Loop Tests).tML-ServiceTestBase.xsdIndustry schema that defines the POTS Service Test base elements.PotsTestRequestType of 6 (StopTone) not supported.tML-ServiceTest.xsdSchema that defines ClientSelfTest interface.Used for CST (Client Self Test).tML-ServiceTestBase.xsdSchema that defines ClientSelfTest base elements.Used for CST (Client Self Test).
EMBED Package
EMBED Package
EMBED Package
EMBED Package
Required Data, Per Transaction
Please refer to the MTG Implementation Document for additional required elements by transaction.
Most of the elements in the XSDs are optional from an XSD validation standpoint. However, CenturyLink will require some optional elements to be populated.
See XSD for other required elements along with the elements shown below.
Create Request
ManagedObjectInstance Standard Relative Distinguish Name (RDN) string values that identify networkId, accountName, and serviceId.
TroubleReportFormatId and data per 4.1 TRFD table.
All Other Requests (After Successful Create Request)
TargetObjectName Standard Relative Distinguish Name (RDN) string values that identify networkId, accountName, and troubleReportId.
RequestTroubleReportCreationRequest
The following table shows required sections and elements based on the TRFD TroubleReportFormatId element value on the create request.
Bold = elementsNon-bold = sections
Blank = Not required/applicable
TRFD1: Services with a premise address.
TRFD2: Services without a premise address.
TRFD3: Resold POTS.
ATIS Create Request Element or SectionTRFD 1TRFD 2TRFD 3RequestTroubleReportCreationRequest/
ManagedObjectInstance/Must be presentMust be presentMust be presentRequestTroubleReportCreationRequest/
TroubleType/Must be presentMust be presentMust be presentRequestTroubleReportCreationRequest/
AdditionalTroubleInfoList/Must be presentMust be presentMust be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
ALocationAccessAddress/
Must be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
ALocationAccessHours/
Must be present
Must be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
ALocationAccessPerson/
Must be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
AuthorizationList/
Must be present
Must be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
CustomerTroubleTickNum
Must be present
Must be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
EscalationList/RequestTroubleReportCreationRequest/
AdditionalCreateInfo/
ManagedObjectAccessHours/
Must be present
Must be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
ManagerContactPerson/
Must be present
Must be present
Must be presentRequestTroubleReportCreationRequest/
AdditionalCreateInfo/
TroubleReportFormatId
Must be present
Must be present
Must be present
Examples of tML-TA for Trouble Ticketing
Note: The examples below are not an exhaustive set of attributes that could be included in each transaction. Please see the tML-TA.xsd, tML-TABase.xsd, and MTG Implementation document for details.
RequestTroubleReportCreationRequest
TELCO-INCCTL2011-04-26T16:50:31.097-05:001:CI:1234567890TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321TELCO-INCRESELLER1.2.320.10015.0.6.55networkId4679accountNameTELCO-INCserviceId26/HCGS/123456//MS1230Fail to loop Smartjack-5-Bit1Main Office931 14th StreetDenverCO80202truefalsefalsefalsefalsefalsefalse08:00:0023:59:00falsetruefalsefalsefalsefalsefalse00:00:0023:59:00falsefalsetruefalsefalsefalsefalse00:00:0023:59:00falsefalsefalsetruefalsefalsefalse00:00:0023:59:00falsefalsefalsefalsetruefalsefalse00:00:0023:59:00falsefalsefalsefalsefalsetruefalse00:00:0023:59:00falsefalsefalsefalsefalsefalsetrue00:00:0023:59:00TELCO-INC NOC30355512122falsefalsefalsetruefalsefalsefalsefalsefalsefalseSMITH J30355512342falsefalsefalsefalsefalsetruefalsefalsefalsefalseSMITH J30355512342011-04-27T18:51:42-05:00CUSTICK12345612011-04-26T16:50:31-05:00SMITH J30355512340truefalsefalsefalsefalsefalsefalse08:00:0023:59:00falsetruefalsefalsefalsefalsefalse00:00:0023:59:00falsefalsetruefalsefalsefalsefalse00:00:0023:59:00falsefalsefalsetruefalsefalsefalse00:00:0023:59:00falsefalsefalsefalsetruefalsefalse00:00:0023:59:00falsefalsefalsefalsefalsetruefalse00:00:0023:59:00falsefalsefalsefalsefalsefalsetrue00:00:0023:59:00SMITH J303555123401000
RequestTroubleReportCreationResponse
TELCO-INCCTL2011-04-26T16:50:31.097-05:001:CI:1234567890TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCserviceId26/HCGS/123456//MS2011-04-26T16:52:57ZDE123456122011-04-26T16:52:57ZCTL30355512342011-04-28T16:08:57Z
ModifyAttributesRequest
TELCO-INCCTL2011-04-27T10:50:31.097-05:001:CI:1234512345TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321TELCO-INCRESELLERnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE123456Please provide status
ModifyAttributesResponse
TELCO-INCCTL2011-04-27T10:50:31.097-05:001:CI:1234512345TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCtroubleReportIdDE123456
CancelTroubleReportRequest
TELCO-INCCTL2011-04-29T15:50:31.097-05:001:CI:1234599999TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321TELCO-INCRESELLERnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE123456trueThis trouble report is no longer validMy Name3035551234931 14th StreetDenverCO80202
CancelTroubleReportResponse
TELCO-INCCTL2011-04-29T15:50:31.097-05:001:CI:1234599999TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCtroubleReportIdDE123456
RetrieveAttributesByTroubleReportIdRequest
TELCO-INCCTL2011-04-29T17:50:31.097-05:001:CI:1234512345TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321TELCO-INCRESELLERnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE123456truetruetruetruetruetruetruetruetruetruetruetruetruetruetruetruetruetruetrue
RetrieveAttributesByTroubleReportIdResponse
TELCO-INCCTL2011-04-29T17:50:31.097-05:001:CI:1234512345TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCtroubleReportIdDE123456INTEGRATION TESTING5-9-11 retesting an external log updatetruefalsefalsefalsefalsefalsefalse08:00:0023:59:00falsetruefalsefalsefalsefalsefalse00:00:0023:59:00falsefalsetruefalsefalsefalsefalse00:00:0023:59:00falsefalsefalsetruefalsefalsefalse00:00:0023:59:00falsefalsefalsefalsetruefalsefalse00:00:0023:59:00falsefalsefalsefalsefalsetruefalse00:00:0023:59:00falsefalsefalsefalsefalsefalsetrue00:00:0023:59:00Main Office931 14th StreetDenverCO80202TELCO-INC NOC30355512122falsefalsefalsetruefalsefalsefalsefalsefalsefalseSMITH J30355512342falsefalsefalsefalsefalsetruefalsefalsefalsefalseSMITH J30355512342011-04-27T18:51:42ZCUSTICK12345612011-04-26T16:50:31ZSMITH J30355512340truefalsefalsefalsefalsefalsefalse08:00:0023:59:00falsetruefalsefalsefalsefalsefalse00:00:0023:59:00falsefalsetruefalsefalsefalsefalse00:00:0023:59:00falsefalsefalsetruefalsefalsefalse00:00:0023:59:00falsefalsefalsefalsetruefalsefalse00:00:0023:59:00falsefalsefalsefalsefalsetruefalse00:00:0023:59:00falsefalsefalsefalsefalsefalsetrue00:00:0023:59:00networkId4679accountNameTELCO-INCserviceId26/HCGS/123456//MSAPIUSER30355512342011-05-09T10:14:35ZDE1234561122011-05-09T10:15:14Z1230
VerifyRepairCompletionRequest
TELCO-INCCTL2011-04-28T15:50:31.097-05:001:CI:5432112345TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321TELCO-INCRESELLERnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE1234561verified fixSmith J3035551234
VerifyRepairCompletionResponse
TELCO-INCCTL2011-04-28T15:50:31.097-05:001:CI:5432112345TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCtroubleReportIdDE123456
AddTroubleInfoRequest
TELCO-INCCTL2011-05-01T18:50:31.097-05:001:CI:1234598765TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321TELCO-INCRESELLERnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE123456Please provide status
AddTroubleInfoResponse
TELCO-INCCTL2011-05-01T18:50:31.097-05:001:CI:1234598765TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCtroubleReportIdDE123456
AttributeValueChangeNotification
Event Notification (Additional Trouble Status Info Added)
TELCO-INCCTL2011-04-29T14:55:31.097-05:001:CI:5432154321TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321101002011-04-29T14:30:06ZnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE123456TECHNICIAN HAS BEEN DISPATCHED ON YOUR TICKET.ETA : 45MIN
Design Services Cleared Notification
TELCO-INCCTL2011-04-29T12:50:31.097-05:001:CI:5432154321TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321100462011-04-29T12:48:06ZnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE123456033000truefalsefalsefalsefalsefalsetruefalsefalsefalsefalse043000truefalsefalsefalsefalsefalsefalsefalsetruefalsefalseTrouble Cleared Awaiting Customer Verification.CenturyLink requests authorization to close ticket.true2130002011-04-29T12:48:06Z63262011-04-29T12:48:06Z
Design Services Closed Notification
TELCO-INCCTL2011-04-29T14:55:31.097-05:001:CI:5432154321 TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321102992011-04-29T12:48:06ZnetworkId4679accountNameTELCO-INCtroubleReportIdDE123456DE123456Trouble ticket closed.4272011-04-29T14:55:25Z
POTS Cleared Notification
TELCO-INCCTL2011-04-28T12:45:31.097-05:001:CI:5432154321TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321102502011-04-28T12:45:30ZnetworkId4679accountNameTELCO-INCtroubleReportId06543210654321Trouble ticket cleared.3252011-04-28T12:45:30Z
POTS Closed Notification
TELCO-INCCTL2011-04-29T20:50:31.097-05:001:CI:5432154321TELCO-INCCTL2011-04-26T16:50:31.097-05:001:TI:0987654321100562011-04-29T20:48:06ZnetworkId4679accountNameTELCO-INCtroubleReportId06543210654321Trouble ticket closed.Disposition Code: 1001. Definition: CenturyLink Toll Cable Cut/Damaged. Cause Code: 600. Definition: Unknowntrue2130002011-04-28T12:45:30Z294272011-04-29T20:48:06Z
Examples of tML for POTS Service Test
Note: The examples below are not an exhaustive set of attributes that could be included in each transaction. Please see the tML-ServiceTest.xsd, tML-ServiceTestBase.xsd, and MTG Implementation document for details.
Request
TELCO-INCCTL2011-05-20T18:50:31.097-05:001:CI:1234598765TELCO-INCCTL2011-05-20T16:50:31.097-05:001:TI:0987654321TELCO-INCRESELLER1networkId4679accountNameTELCO-INCserviceId7035556778
Response Normal (Full TestRequestType is 1)
TELCO-INCCTL2011-05-20T18:50:31.097-05:001:CI:1234598765TELCO-INCCTL2011-05-20T16:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCserviceId7035556778This is a summary...1010005020010210001000200OKNot OK992015
Response Normal (Quick TestRequestType is 2)
TELCO-INCCTL2011-05-20T17:45:31.097-05:001:CI:1234598765TELCO-INCCTL2011-05-20T15:45:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCserviceId7035556778This is a summary...181235000350001099103992019700
Response Normal (Central Office TestRequestType is 3)
TELCO-INCCTL2011-05-20T22:35:31.097-05:001:CI:1234598765TELCO-INCCTL2011-05-20T20:30:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCserviceId7035556778This is a summary...1010005020010210001000200OKNot OK992015
Response Normal (Loop Test TestRequestType is 4)
TELCO-INCCTL2011-05-20T07:22:31.097-05:001:CI:1234598765TELCO-INCCTL2011-05-20T05:11:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCserviceId7035556778This is a summary...1450350003500099586OKNot OK996519800
Examples of tML for Client Self Test
Note: The examples below are not an exhaustive set of attributes that could be included in each transaction. Please see the tML-ServiceTest.xsd, tML-ServiceTestBase.xsd, and MTG Implementation document for details.
Request
TELCO-INCCTL2014-08-28T18:50:31.097-05:001:CI:1234598765TELCO-INCCTL2014-08-28T18:50:31.097-05:001:TI:0987654321CEMRRESELLER1networkId4679accountNameTELCO-INCserviceId26/HCGS/123456//MSfalse
Response - Normal
TELCO-INCCTL2014-08-28T18:50:31.097-05:001:CI:1234598765TELCO-INCCTL2014-08-28T18:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCserviceId26/HCGS/123456//MSW-3bagygNTANo test access available - Please open a ticket.CHNHMNBJ2014-08-05T12:58:01.662Z
Response Error Exception
TELCO-INCCTL2014-08-28T18:50:31.097-05:001:CI:1234598765TELCO-INCCTL2014-08-28T18:50:31.097-05:001:TI:0987654321networkId4679accountNameTELCO-INCserviceId26/HCGS/123456//MSMTG1000
Cannot access INTAS Service
Glossary
ATISAlliance for Telecommunications Industry Solutions: A standards body for the Telecommunications Industry. http://www.atis.org.CSTClient Self TestMTGCenturyLink Maintenance Ticketing Gateway: CenturyLinks business-to-business Electronic Ticketing trouble administration gateway.TCIFTelecommunications Industry ForumtML-TATelecommunications Markup Language-Trouble Administration: The ATIS XSD/XML standard for trouble administration.TMOCATIS Telecom Management and Operations Committee (formerly, T1M1).TRFDTrouble Report Format Definition
Appendix A: Corrections
Shown below are corrections for the September 2, 2011 release of this document. These are changes from the review document of August 24, 2011.
SectionChange5.1 Request Trouble Report Creation RequestAdded missing closing bracket to:
5.6 CancelTroubleReportResponseBeginning at the eleventh line of the WSDL, removed the following:
TELCO-INCRESELLER5.2 RequestTroubleReportCreationResponseCommittmentTime, with two ts in Committment, has been corrected to CommitmentTime. For example:
5.12 AddTroubleInfoResponseRemove white space from parent tags:
5.7 RetrieveAttributesByTroubleReportIdRequestAdded the following (missing) end tag:
5.5 CancelTroubleReportRequestAdded the missing "/tML-TA:" after opening bracket:
trueSection 6 Examples of tML for POTS Service TestAll POTS examples have been replacedSection 5.13 AttributeValueChangeNotificationReplaced sections 5.13.1 to 5.13.5
STYLEREF "service name" \* MERGEFORMAT Maintenance Ticketing Gateway Specification STYLEREF "category name" \* MERGEFORMAT CenturyLink
STYLEREF "category name" \* MERGEFORMAT CenturyLink STYLEREF "service name" \* MERGEFORMAT Maintenance Ticketing Gateway Specification
- Internal Use Only - PAGE 2 ( 2014 CenturyLink, Inc. All Rights Reserved. September 25, 2014
- Internal Use Only -
September 25, 2014 ( 2014 CenturyLink, Inc. All Rights Reserved. PAGE 3
Internal Use Only -Disclose and distribute only to CenturyLink employees and authorized persons working for CenturyLink. Disclosure outside of CenturyLink is prohibited without authorization.
( 2014 CenturyLink, Inc. All Rights Reserved.
RequestTroubleReportCreationRequest
Receive and acknowledge request.
Submit Create Ticket request.
CenturyLink processing.
Receive Create Ticket notification.
Submit Create Ticket notification.
RequestTroubleReportCreationResponse
ACK/NACK (HTTP Response Message)
ACK/NACK (HTTP Response Message)
Receive and acknowledge request.
Submit Update Ticket request.
CenturyLink processing.
Receive Update Ticket notification.
Submit Update Ticket notification.
ACK/NACK (HTTP Response Message)
ModifyAttributesResponse
ModifyAttributesRequest
ACK/NACK (HTTP Response Message)
CancelTroubleReportRequest
Receive and acknowledge request.
Submit Cancel Ticket request.
ACK/NACK (HTTP Response Message)
CenturyLink processing.
Receive Cancel Ticket notification.
Submit Cancel Ticket notification.
ACK/NACK (HTTP Response Message)
CancelTroubleReportResponse
Receive and acknowledge request.
Submit Retrieve Ticket request.
CenturyLink processing.
Receive Retrieve Ticket notification.
Submit Retrieve Ticket notification.
RetrieveAttributesByTroubleReportIdResponse
ACK/NACK (HTTP Response Message)
RetrieveAttributesByTroubleReportIdRequest
ACK/NACK (HTTP Response Message)
Submit Update Ticket (status / log notes update) notification.
Receive Update Ticket (priority / log notes update) notification.
ACK/NACK (HTTP Response Message)
AttributeValueChangeNotification
Receive Cleared Ticket notification.
Submit verification of issue resolution
AttributeValueChangeNotification
VerifyRepairCompletionRequest
Process request
Receive verification response
VerifyRepairCompletionResponse
Submit verification response
Receive Closed Ticket notification.
Submit Closed Ticket notification.
AttributeValueChangeNotification
After 24 hours of no response, no dispute, or immediately upon acceptance, the ticket may be closed.
Cleared state (3), status (26), status time, activity duration, close out narrative, trouble found, maintenance service charge, and outage duration, restored time.
Closed state (4), status (27), status time, additional trouble status info.
Submit Cleared Ticket notification.
ACK/NACK (HTTP Response Message)
ACK/NACK (HTTP Response Message)
ACK/NACK (HTTP Response Message)
ACK/NACK (HTTP Response Message)
Receive Cleared Ticket notification.
AttributeValueChangeNotification
Receive Closed Ticket notification.
Submit Closed Ticket notification.
AttributeValueChangeNotification
Cleared state (3), status (25), status time, additional trouble status info.
Closed state (4), status (27), status time, close out narrative, trouble found, maintenance service charge, outage duration, restored time.
Submit Cleared Ticket notification.
ACK/NACK (HTTP Response Message)
ACK/NACK (HTTP Response Message)
E F I U Z [ \ ] v w y D K L R `
2
7
?
A
8 > H 뭦뛗Ƈ h hO h)7 h6 h) h{ h|w h{? hz h hz hw hz hl hz h9( hz h$\
hP h' h+j hpt )j hK hK B*UmH nH ph uhz j hb hK UmH nH u3 - E G H I ] z . 3 ? - $If ( gdz E W K Q I ? @ D S ` P J A A A > $If gdz > $If kdV $$If l F
% b 0 4 4
l ap ytH
u o f o > $If gdz > $If kd. $$If l F
% b 0 4 4
l aytH
+
F
o
! A u o f f f f f f ] > $If gd(? > $If gdz > $If kd $$If l F
% b 0 4 4
l aytH A B F Y p s m d d > $If gdz > $If kdH $$If l F
% b 0 4 4
l aytH p q u u o f f > $If gdz > $If kdٜ $$If l F
% b 0 4 4
l aytH @
u o f ] > $If gd) > $If gdz > $If kdf $$If l F
% b 0 4 4
l aytH @
A
K
\
u o f ] > $If gd) > $If gdz > $If kd $$If l F
% b 0 4 4
l aytH
G u o f ] > $If gd+j > $If gdz > $If kd $$If l F
% b 0 4 4
l aytH G H R a u o f ] > $If gd+j > $If gdz > $If kd
$$If l F
% b 0 4 4
l aytH ( u o f ] > $If gd+j > $If gdz > $If kd $$If l F
% b 0 4 4
l aytH ' ) ( * 6 I J ^ _ ` ~ νzvz hF j hF Uhz mH nH uj h UmH nH u h' j hz aJ hz htq hpt hH hH hpt h hpt aJ hpt hpt H*hpt hpt h` hpt h` H*hpt h` h7 h(? hi h hS h$\
(( ) 3 @ u o f ] > $If gd+j > $If gdz > $If kd' $$If l F
% b 0 4 4
l aytH ) u o f ] > $If gd7 > $If gdz > $If kd $$If l F
% b 0 4 4
l aytH ) * 4 5 E u l c l Z > $If gdT $If gd, > $If gd, kdA $$If l F
% b 0 4 4
l aytH u l l c > $If gdT > $If gd, kdΡ $$If l F
% b 0 4 4
l aytH u l l c > $If gdH > $If gd, kd[ $$If l F
% b 0 4 4
l aytH H ? I u p k f d b b d ` ^ ( gdz ( gdz > gdz kd $$If l F
% b 0 4 4
l aytH
= > A B Q R S m n o p q r s t οέοٗοοٗοoοٗ #jo h UmH nH u#j h UmH nH uhF j hF Uj hF UmH nH u #ju h UmH nH uj h UmH nH uh%xD mH nH u .hK h%xD 5CJ OJ PJ QJ aJ mH nH u hPu h%xD 0J= mH nH u + s s F
e k 2 } ( ( ! ! '" A t
Q R S m n o p q r s t ôâôôÂôôpô#j h UmH nH u#ji h UmH nH uj hF UmH nH u #j h UmH nH uj h UmH nH uh%xD mH nH u .hK h%xD 5CJ OJ PJ QJ aJ mH nH u hPu h%xD 0J= mH nH uj hF UhF , $ % & @ A B C D E F G e f k l 7 8 = > ` a b | ǽǰǽǽǣǽǽǖǽǽ j] h U j h U jc h U j h U h%xD hPu h%xD 0J= hK h%xD CJ OJ PJ QJ aJ hPu h%xD 0J= OJ QJ hF j hF U 6| } ~
( ) . / d e f
) * ܺ˱ܺ˱ܺ˱ jQ h U jԨ h U jW h U hPu h%xD 0J= hPu h%xD 0J= OJ QJ hF hK h%xD CJ OJ PJ QJ aJ j hF U h%xD j h U jڧ h U6* + , B C D ^ _ ` b c d e f οέοٗοοٗοoοٗ #jȪ h UmH nH u#jK h UmH nH uhF j hF Uj hF UmH nH u #jΩ h UmH nH uj h UmH nH uh%xD mH nH u .hK h%xD 5CJ OJ PJ QJ aJ mH nH u hPu h%xD 0J= mH nH u + ; < ? @ H I J d e f h i j k l ôâôvmh^hQ^h^v j« h U j h U h%xD hPu h%xD 0J= hK h%xD CJ OJ PJ QJ aJ hPu h%xD 0J= OJ QJ j hF UmH nH u #jE h UmH nH uj h UmH nH uh%xD mH nH u .hK h%xD 5CJ OJ PJ QJ aJ mH nH u hPu h%xD 0J= mH nH uj hF UhF + , - / 0 1 2 3 Q R U V Z [ \ v w x z { | } ~ ˴p^ppP j hF UmH nH u #j h UmH nH uj h UmH nH uh%xD mH nH u .hK h%xD 5CJ OJ PJ QJ aJ mH nH u hPu h%xD 0J= mH nH uhF j? h U j h U h%xD hPu h%xD 0J= hK h%xD CJ OJ PJ QJ aJ hPu h%xD 0J= OJ QJ j hF U ! " # % & ' ( ) G H M N \ ] ^ x y z | } ~ ԽʵԤʵԗʵԊ j h U j3 h U j h U hF j hF Uj9 h U j h U h%xD hPu h%xD 0J= hK h%xD CJ OJ PJ QJ aJ hPu h%xD 0J= OJ QJ 6 ! " # % & ' ( ) G H M N ˳˨ylc^^Q^ j h U h%xD hPu h%xD 0J= hPu h%xD 0J= OJ QJ j hF UmH nH u #j- h UmH nH uj h UmH nH uh%xD mH nH u .hK h%xD 5CJ OJ PJ QJ aJ mH nH u hPu h%xD 0J= mH nH uhF hK h%xD CJ OJ PJ QJ aJ j hF Uj h U 7 8 = > s t u ! ! ! ! ! ! ! ! 8! 9! >! ?! p! q! r! ! ǽǰǽǽǣǽǽǖǽǽ j! h U j h U j' h U j h U h%xD hPu h%xD 0J= hPu h%xD 0J= OJ QJ hF hK h%xD CJ OJ PJ QJ aJ j hF U 8! ! ! ! ! ! ! ! ! ! ! ! " " " " !" "" $" %" &" '" (" F" G" L" M" " " " " " " " " " " " " " " " R# S# T# n# o# p# r# s# t# u# v# # # ܺ˱ܺ˱ܺ˱ j h U j h U j h U hPu h%xD 0J= hPu h%xD 0J= OJ QJ hF hK h%xD CJ OJ PJ QJ aJ j hF U h%xD j h U j h U6'" " u# # ;$ $ % |% % E&