8.0 Delayed Activation

Delayed activation is an intrinsic feature of TL1 that helps you to execute commands automatically at predefined date/time. This article speaks about this feature in detail.

8.1 Need for Delayed Activation

For service maintenance and performance analysis, operators run huge tasks in the NE, during lean hours. Provisioning thousand subscribers at a
time is a good example for such tasks. The delayed activation feature comes handy in such situations. It allows operators to specify the date & time of execution in the command. Hence, operators need not sit back for long hours and send all those commands. Instead, they can send commands for automatic execution by specifying the date & time. And the NE executes the commands at the specified date/time without requiring a human operator.

8.2 How delayed activation works

NEs store the TL1 commands (only those with delayed activation) in a message pending buffer. The agent executes these commands at the specified date/time (date/time is specified in each command). It also sends a response message on completion of the operation.

8.3 Delayed activation parameters

[ON=]  - ON represents the ORDER NUMBER. It is a numeric value assigned by you.  The NE to internally identify the delayed input message uses this number.
[DATE=]  - DATE represents the exact date at which the delayed activation should occur. It takes the following format  <yy>- <mm > - <dd>
[TIME=] - TIME represents the exact time at which the delayed activation should occur. It takes the following format:  <hh> - <mm> - <ss>

8.4 How to set the delayed activation parameters in a TL1 command

You have to specify the three delayed activation parameters in the general block.

Syntax of TL1 command:
<commandcode>: <TID>: <AID>:< CTAG>: <general block>:<payload block>;

Delayed activation parameters can be specified in the general block as shown below:
Generalblock::= <ON>,<DATE>,<TIME>,<CF>,<INDRTRV>

Example:
The following command ENT-CRS-STS1:TID:STS-3-2,STS-4-3:44:1, ,, : ; creates a cross connect between two channels, STS-3-2 and STS-4-3. To set the delayed activation parameters for this command, refer the table below

Delayed activation at	Command
23:00 hrs same day	ENT-CRS-STS1:TID:STS-3-2, STS-4-3:44:210198, , 23-00-00, : ;
on dec 06, 2002	ENT-CRS-STS1:TID:STS-3-2, STS-4-3:44:210198,02-12-06 , , : ;
23:00 hrs on dec06th2002	ENT-CRS-STS1:TID:STS-3-2, STS-4-3:44:210198,02-12-06,23-00-00, : ;

where, 210198 indicates ORDER NUMBER, 23:00:00 indicates time, 02-12-06 indicates date.

8.5 How to retrieve pending commands

To retrieve the TL1 commands with delayed activation , which are stored in the NE, the following command can be used
RTRV-DA::[ALL|ORDNUM]:<ctag>::TTYPE ,TTIMEGE, TTIMELE;

The NE will retrieve all the pending delayed activation commands if you specify ALL in the retrieve message. To retrieve specific commands from the NE specify the ORDER NUMBER of those commands in the retrieve message. After retrieval of the commands, you can make necessary changes in that command and re-send if necessary.

8.6 How to activate pending commands

You can activate a pending command manually by sending a TL1 command. The command for activating the pending messages takes the following format.
ACT-DA::[ALL|ORDNUM]:<ctag>::;

By specifying ALL you activate all the pending commands. To activate specific pending commands, specify the exact ORDER NUMBER of the commands.

8.7 How to cancel pending commands

You can delete a pending command using the following command
CANC-DA::[ALL|ORDNUM]:<ctag>::;