You are on page 1of 34

Introduction to TL1

Luu Vo Sep 2011

Agenda
What is TL1? Protocol Overview TL1 Message Types TL1 Message Structure TL1 Input Message TL1 Output Message TL1 Acknowledgment Message TL1 Autonomous Message TL1 vs. SNMP QnA
Introduction to TL1 2

What is TL1?
Transaction Language 1 (TL1) management protocol in telecommunications  developed by Bellcore in 1984  used to manage optical and broadband access infrastructure in North America cross-vendor, cross-technology, man-machine language  designed as a standard protocol readable by machines as well as humans to replace the diverse ASCII based protocols used by different Network Element (NE) vendors  extensible to incorporate vendor specific commands defined in Telcordia Technologies (formerly Bellcore) Generic Requirements document GR-831-CORE
Introduction to TL1 3

Protocol Overview

Introduction to TL1

TL1 Message Types


TL1 Input Message: command used to operate on the NE, sent by the user or the OSS TL1 Output/Response Message: reply sent by the NE in response to an input message TL1 Acknowledgment Messages: an acknowledgment of the receipt of a TL1 input message, sent if the response message will be delayed by more than 2 seconds TL1 Autonomous Message: asynchronous messages (usually events or alarms) sent by the NE

Introduction to TL1

TL1 Message Structure


TL1 messages follow a fixed structure, and all commands must conform to it Commands themselves are extensible and new commands can be added by NE vendors Common message components  Target identifier (TID) & Source identifier (SID): unique name assigned to each NE. TID is used to route the message to an NE, SID is used to identify the source of an autonomous message.  Access identifier (AID): identifies an entity within an NE  Correlation tag (CTAG) & Autonomous correlation tag (ATAG): numbers used to correlate messages
Introduction to TL1 6

TL1 Input Message

command_code:staging_block:payload_blocks;

Introduction to TL1

TL1 Input Message Command Code


Defines the nature of the task that is to be executed on the NE verb-modifier1-modifier2 Verb: type of action to be taken on the NE Modifiers: optional qualifiers used to identify and describe the object in the NE, which has to be acted upon by the message
Introduction to TL1 8

TL1 Input Message Command Code Verb


# 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Verb ABT ACPT ACT ALW AUD CANC CHG CMPR CONN COPY CPY CRPT CRTE DGN Definition Abort Accept Activate Allow Audit Cancel Change Compare Connect Copy Copy Corrupt Create Diagnose

Introduction to TL1

TL1 Input Message Command Code Verb


# 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Verb DISC DLT ED ENCAP ENT EX EXIT FLTLOC INH INIT MEAS MON OPR RD Definition Disconnect Delete Edit Encapsulation Enter Exercise Exit FaultLocate Inhibit Initialize Measure Monitor Operate Read

Introduction to TL1

10

TL1 Input Message Command Code Verb


# 29 30 31 32 33 34 35 36 37 38 39 40 41 42 Verb REC RECNFGR REPT RLS RMV RST RTRV SCHED SET SND STA STP TEST TRACE Definition Recover Reconfigure Report Release Remove Restore Retrieve Schedule Set Send Start Stop Test Trace

Introduction to TL1

11

TL1 Input Message Staging Block


Identifies the exact resource in the NE, which has to be acted upon by the command :TID:AID:CTAG:generalblock: Target Identifier (TID):  used for identifying the end NE when commands from OSSs are routed through a gateway network element.  TID should be equal to the system identification code (SID) that is returned in a response message from the NE  In direct routing, where commands are sent to an NE directly from the OSS, the TID value will be null.

Introduction to TL1

12

TL1 Input Message Staging Block (Cont.)


Access Identifier (AID):
 one or more simple or compound parameters that uniquely identify the entity, within or associated with the target NE, to be acted upon by the input message used to correlate a response or acknowledgment with the originating input message. information about how the command will be handled by the NE :[[<delayed activation parameters>],[<contingency flag>],[<indirect data retrieval identifier>]]: General block is mandatory in commands that have payload If delayed-activation is not supported then general block may be null (represented by two semi-colons ::)

Correlation tag (CTAG):


    

General Block:

Introduction to TL1

13

TL1 Input Message Payload Block


Any additional information that is required to carryout the command payload_block::=data_block_list; data_block_list::=data_block | data_block_list:data_block zero or more datablocks, separated by colons Every datablock may contain multiple datacomponents, separated by commas Datacomponents may be either positiondefined or name-defined parameters
Introduction to TL1 14

TL1 Input Message - Example

Introduction to TL1

15

TL1 Output Message

header response_id [response_block] terminator

Introduction to TL1

16

TL1 Output Message - Response Header


^^^sid^year-monthday^hour:min:sec SID (the source identifier): name of the NE used for identifying the NE emitting the message year-month-day and hour:min:sec represent the date and time of the message
Introduction to TL1 17

TL1 Output Message - Response ID


identifies the type of output message whether it is a response or an autonomous message M^^ctag^completion_code M - used to differentiate between response and autonomous message ctag - indicates the correlation tag assigned with the input message. completion code - indicates the status of the task - whether it is completed successfully or not.
Introduction to TL1 18

TL1 Output Message - Response ID (Cont.)


Completion code Type Success response code Parameters COMPLD - indicates successful completion of the requested operation. DELAY - indicates successful delayed activation of the requested operation. DENY - indicates failure of the TL1 command and provides an error message with the reason for the failure. PRTL - indicates partially successful response. That is, the requested action can be completed for some of the specified AIDs, but not all. RTRV - indicates that the response is successful, but it is lengthy and is being returned in multiple parts. Final response has a COMPLD response code.

Other response code

Introduction to TL1

19

TL1 Output Message - Response Block


text blocks holding the main body of the output message and the payload quoted lines, unquoted lines, and comments
 unquoted line: list of parameters (either name defined or position defined) separated by mandatory white spaces or optional commas  quoted line: double quoted (") line of machine parsable text  comment allows free form text messages to be generated by the NE for presentation to the OS. The comment must begin with /* and end with */.
Introduction to TL1 20

TL1 Output Message - Terminators


<cr><lf>( ; | > ) semicolon (;) indicates the termination of output messages greater than (>) character indicates more output associated with this response will follow under another header. size of the output message should not exceed 4096 bytes. If it exceeds the specified size, then the output response is split into multiple responses with the same CTAG.
Introduction to TL1 21

TL1 Output Message - Example

Introduction to TL1

22

TL1 Acknowledgment Message

acknowledgment_code ctag terminator

Introduction to TL1

23

TL1 Acknowledgment Message


Acknowledgment code
      IP: In Progress PF: Printout follows (identical to IP) OK: All right NA: No acknowledgment NG: No Good RL: Repeat Later system busy

CTAG: Refers to the correlation tag of the input message to which this acknowledgment is made Terminator: always end with greater than symbol (>) terminator
Introduction to TL1 24

TL1 Autonomous Message

header auto_id [text_block] terminator

Introduction to TL1

25

TL1 Autonomous Message - Header


^^^sid^year-monthday^hour:min:sec SID (Source identifier): name of the NE used for identifying the NE emitting the message. year-month-day and hour:min:sec represent the date and time of the message.
Introduction to TL1 26

TL1 Autonomous Message - Auto ID


alarm_code^atag^verb [-modifier1[modifier2]] Alarm Code:
 severity of the alarm  If multiple alarms are reported, the alarm code will correspond to the alarm with the highest severity  Non-alarmed code is used when the NE reports non-alarmed autonomous messages (e.g., reporting performance data measurements.)

Introduction to TL1

27

TL1 Autonomous Message - Auto ID (Cont.)


Alarm Code (almcde) *C Description Corresponding notification code (ntfcncde) CR

Critical alarm condition

**

Major alarm condition

MJ

*^

Minor alarm condition

MN

A^

Non-alarmed autonomous message

CL, NA

Introduction to TL1

28

TL1 Autonomous Message - Auto ID (Cont.)


ATAG (Autonomous TAG): integer value incremented by one for each message, used for alarm correlation verb-modifier1-modifier2
 Verb: the type of autonomous event that is fired by the NE  Modifiers: additional description about the object

Introduction to TL1

29

TL1 Autonomous Message - Text Block


text blocks holding the main body of the auto message and the payload quoted lines, unquoted lines, and comments
 unquoted line: list of parameters (either name defined or position defined) separated by mandatory white spaces or optional commas  quoted line: double quoted (") line of machine parsable text  comment allows free form text messages to be generated by the NE for presentation to the OS. The comment must begin with /* and end with */.
Introduction to TL1 30

TL1 Autonomous Message Terminators


<cr><lf>( ; | > ) semicolon (;) indicates the termination of output messages greater than (>) character indicates more output associated with this response will follow under another header. size of the output message should not exceed 4096 bytes. If it exceeds the specified size, then the output response is split into multiple responses with the same ATAG.
Introduction to TL1 31

TL1 Autonomous Message Example

Introduction to TL1

32

TL1 vs. SNMP


Function Operations Notification Management Information Model Encoding Acknowledgment Delay Activation Communication type Security TL1 Input Messages. Autonomous Message NA SNMP GET, SET, GET-NEXT, and GET-BULK Trap, Notification, and Inform MIB

plain ASCII text Yes Yes Man-Machine and Machine-Machine language System and resource access control mechanism, persistent connection between OSS and NE for authentication

UDP message (binary) No No Machine-Machine Language SNMPv3 uses USM (User Security Model) and VACM (View based Access Control Mechanism) security model. Authentication is done per message

Introduction to TL1

33

QnA
Questions?

Introduction to TL1

34

You might also like