TCAP Notes(1)

  

1. When the Transaction sublayer is used to support the dialogue, these primitives(E.g. TC-Begin)

map onto TR-primitives with the same generic name(TR-Begin), as there is a one-to-one relationship between a dialogue and a transaction.

2. Each of the previous primitives(e.g.TR-Begin) causes any component(s) previously passed on the interface for the referenced dialogue to be delivered to the remote end (except for a TC-END with prearranged end).

3.Four classes of operations are considered:

– Class 1 – Both success and failure are reported.

– Class 2 – Only failure is reported.

– Class 3 – Only success is reported.

–     Class 4 – Neither success, nor failure is reported.

4.

i) a dialogue begins;

ii) a dialogue confirmation;

iii) a dialogue continues: full-duplex exchange of components is possible;

iv) a dialogue ends:

v)exception reporting and message return

5. This subclause describes the parameters used with the primitives associated with dialogue handling in component sublayer.

-"Abort Reason":

- Address parameters:

- "Application context Name:

- "Components Present:

-"Dialogue ID":

-"P-ABORT":

- "Quality of Service":

- "Termination":

- "User Information":

- "Report C ause":

6. Three scenarios are provided to TC-users to end a dialogue:

– prearranged end;

– basic end;

– abort by the TC-user.

7. This subclause describes the parameters used with the primitives associated with component handling in sublayer.

-"Class"

-"Dialogue ID":

-"Invoke ID":

-"Linked ID":

-"Error":

-"Last Component":

-"Operation"

-"Problem Code":

-"Timeout"

8.component handling

-Operation invocation              -------TC-INVOKE

- Report of success                   ------- TC-RESULT-L/TC-RESULT-NL

-Report of failure                       -------TC-U-ERROR

- Reject by the TC-user             ------ TC-U-REJECT(remote TC-user)

- Cancel of an operation

                       -------- The Component sublayer uses the cancel facility to inform the TC-user that the timer associated with a class 1, 2 or 3 operation has expired; the TC-L-CANCEL indication primitive is used for this purpose.

                       --------- The TC-user uses the TC-U-CANCEL request primitive to inform the local Component sublayer of a cancel decision. No component is sent.

 

- Reset of an operation invocation------ TC-TIMER-RESET

9. Abnormal situations

- Reject of a component by the Component sublayer

-- TC-R-REJECT/TC-R-REJECT

- Dialogue abort

                           -- TC-P-ABORT

10. Overview of the Transaction sublayer primitives

Definition of the parameters

                   - "Quality of Service":

                   - "Destination Address":

                   - "Originating Address":

                   - "P-Abort":

                   - "Transaction ID":

                   - "User Data":

                   - "Report Cause":

11 ． Component element:

3.7

problem code : The Problem code element contains the reason for the rejection of a

component, and one such element is present in a Reject component.

 Four problem code elements are

defined, namely:

 

3.7.1 general problem :

3.7.1.1 unrecognized component :

3.7.1.2 mistyped component :

3.7.1.3 badly structured component :

 

3.7.2 invoke problem :

3.7.2.1 duplicate invoke ID :

3.7.2.2 unrecognized operation :

3.7.2.3 mistyped parameter

3.7.2.4 resource limitation :

3.7.2.5 initiating release :

3.7.2.6 unrecognized linked ID

3.7.2.7 linked response unexpected

3.7.2.8 unexpected linked operation

 

3.7.3 return result problem

3.7.3.1 unrecognized invoke ID

3.7.3.2 return result unexpected

3.7.3.3 mistyped parameter

 

3.7.4 return error problem

3.7.4.1 unrecognized invoke ID

3.7.4.2 return error unexpected

3.7.4.3 unrecognized error

3.7.4.4 unexpected error

3.7.4.5 mistyped paramete