Signaling System No.7 Protocol Architecture And Sevices part 68

Chia sẻ: Dasdsadqwe Dsadasdsadsa | Ngày: | Loại File: PDF | Số trang:7

Thêm vào BST

Báo xấu

64
lượt xem 4
download

Download Vui lòng tải xuống để xem tài liệu đầy đủ

Appendix D. TCAP Messages and Components The tables in this appendix summarize Transaction Capabilities Application Part (TCAP) messages and components

Chủ đề:

Bình luận(0) Đăng nhập để gửi bình luận!

Lưu

Nội dung Text: Signaling System No.7 Protocol Architecture And Sevices part 68

< Day Day Up > < Day Day Up > Appendix D. TCAP Messages and Components The tables in this appendix summarize Transaction Capabilities Application Part (TCAP) messages and components, and explain the purpose of each. For an introduction to TCAP, refer to Chapter 10, "Transaction Capabilities Application Part (TCAP)." Table D-1 shows the TCAP messages used in ITU-T networks. Table D-1. ITU TCAP Message Reference Binary Message Purpose Code Name 0110 Unidirectional Used to send components to another TCAP user 0001 without establishing a transaction. No Transaction ID is allocated. No response is expected when this message is received. 0110 Begin Initiates a transaction. 0010 The transaction ID is allocated and included in all messages that are associated with the transaction. A TCAP user can respond with an End or Continue message. 0110 End Ends an existing transaction. The Transaction ID is 0100 released when this message is received. 0110 Continue Sent when a transaction has been established and 0101 further information exchange is needed. A Transaction ID is allocated and used in all messages associated with the transaction. The Continue message includes both an Origination Transaction ID and a Destination Transaction ID. A TCAP user can respond with an End or Continue message.
0110 Abort Indicates that an abnormal condition has occurred. The 0111 transaction is ended and all associated Transaction IDs are released. The abort might be initiated by the TCAP user (U-Abort) or the protocol itself (P-Abort). Table D-2 shows the TCAP messages used in ANSI networks. Table D-2. TCAP Message Reference (ANSI) Binary Message Name Purpose Code 1110 Unidirectional Used to send components to another TCAP user 0001 without establishing a transaction. No Transaction ID is allocated. No response is expected when this message is received. 1110 Query With Initiates a transaction and allows the receiving TCAP 0010 Permission user to end the transaction. A Transaction ID is allocated and included in all messages associated with the transaction. The normal response from a TCAP user is a Conversation or Response message. 1110 Query Without Initiates a transaction but does not allow the 0011 Permission receiving TCAP user to end the transaction. A Transaction ID is allocated and included in all messages associated with the transaction. The normal response from a TCAP user is a Conversation message. 1110 Response Ends an existing transaction. The Transaction ID is 0100 released when this message is received. 1110 Conversation Sent when a transaction has been established and 0101 With Permission further information exchange is needed. The receiving TCAP user is allowed to end the transaction. A Transaction ID is allocated when the first Conversation message is sent and is used in subsequent messages associated with the transaction. The Conversation With Permission message includes
both an Origination Transaction ID and a Destination Transaction ID. The normal response from a TCAP user is a Conversation or Response message. 1110 Conversation Sent when a transaction has been established and 0110 Without further exchange of information is needed. The Permission receiving TCAP user is not allowed to end the transaction. A Transaction ID is allocated when the first Conversation message is sent and is used in subsequent messages associated with the transaction. The Conversation With Permission message includes both an Origination Transaction ID and a Destination Transaction ID. The normal response from a TCAP user is a Conversation message. 1111 Abort Indicates that an abnormal condition has occurred. 0110 The transaction is ended and all associated Transaction IDs are released. The abort might be initiated by the TCAP user (U-Abort) or the protocol itself (P-Abort). Table D-3 shows the TCAP components used in ITU and ANSI networks. Table D-3. TCAP Component Type Reference (ITU/ANSI) ITU ANSI Binary Binary Component Code Code Type Purpose 10100 11101 Invoke Invokes an operation at a remote node. 001 001 This is a request to have an action, such as translating a number or creating a connection performed. 10100 11101 Return Result Returns the result of a successfully 010 01 0 (Last) invoked operation. No subsequent components are to be sent. 10100 11101 Return Error Indicates that an error has occurred at the 011 011 application or user level.
10100 11101 Reject Indicates that an error has occurred at the 100 100 protocol level. 11101 Invoke (Not Invokes an operation at a remote node. 101 Last) Further responding components are expected. Applies only to ANSI Networks. 10100 11101 Return Result Returns the result of a successfully 111 110 (Not Last) invoked operation. Subsequent components are sent. < Day Day Up > < Day Day Up > Appendix D. TCAP Messages and Components The tables in this appendix summarize Transaction Capabilities Application Part (TCAP) messages and components, and explain the purpose of each. For an introduction to TCAP, refer to Chapter 10, "Transaction Capabilities Application Part (TCAP)." Table D-1 shows the TCAP messages used in ITU-T networks. Table D-1. ITU TCAP Message Reference Binary Message Purpose Code Name 0110 Unidirectional Used to send components to another TCAP user 0001 without establishing a transaction. No Transaction ID is allocated. No response is expected when this message is received. 0110 Begin Initiates a transaction. 0010 The transaction ID is allocated and included in all messages that are associated with the transaction. A TCAP user can respond with an End or Continue message.
0110 End Ends an existing transaction. The Transaction ID is 0100 released when this message is received. 0110 Continue Sent when a transaction has been established and 0101 further information exchange is needed. A Transaction ID is allocated and used in all messages associated with the transaction. The Continue message includes both an Origination Transaction ID and a Destination Transaction ID. A TCAP user can respond with an End or Continue message. 0110 Abort Indicates that an abnormal condition has occurred. The 0111 transaction is ended and all associated Transaction IDs are released. The abort might be initiated by the TCAP user (U-Abort) or the protocol itself (P-Abort). Table D-2 shows the TCAP messages used in ANSI networks. Table D-2. TCAP Message Reference (ANSI) Binary Message Name Purpose Code 1110 Unidirectional Used to send components to another TCAP user 0001 without establishing a transaction. No Transaction ID is allocated. No response is expected when this message is received. 1110 Query With Initiates a transaction and allows the receiving TCAP 0010 Permission user to end the transaction. A Transaction ID is allocated and included in all messages associated with the transaction. The normal response from a TCAP user is a Conversation or Response message. 1110 Query Without Initiates a transaction but does not allow the 0011 Permission receiving TCAP user to end the transaction. A Transaction ID is allocated and included in all messages associated with the transaction. The normal response from a TCAP user is a Conversation message.
1110 Response Ends an existing transaction. The Transaction ID is 0100 released when this message is received. 1110 Conversation Sent when a transaction has been established and 0101 With Permission further information exchange is needed. The receiving TCAP user is allowed to end the transaction. A Transaction ID is allocated when the first Conversation message is sent and is used in subsequent messages associated with the transaction. The Conversation With Permission message includes both an Origination Transaction ID and a Destination Transaction ID. The normal response from a TCAP user is a Conversation or Response message. 1110 Conversation Sent when a transaction has been established and 0110 Without further exchange of information is needed. The Permission receiving TCAP user is not allowed to end the transaction. A Transaction ID is allocated when the first Conversation message is sent and is used in subsequent messages associated with the transaction. The Conversation With Permission message includes both an Origination Transaction ID and a Destination Transaction ID. The normal response from a TCAP user is a Conversation message. 1111 Abort Indicates that an abnormal condition has occurred. 0110 The transaction is ended and all associated Transaction IDs are released. The abort might be initiated by the TCAP user (U-Abort) or the protocol itself (P-Abort). Table D-3 shows the TCAP components used in ITU and ANSI networks. Table D-3. TCAP Component Type Reference (ITU/ANSI) ITU ANSI Binary Binary Component Code Code Type Purpose 10100 11101 Invoke Invokes an operation at a remote node.
001 001 This is a request to have an action, such as translating a number or creating a connection performed. 10100 11101 Return Result Returns the result of a successfully 010 01 0 (Last) invoked operation. No subsequent components are to be sent. 10100 11101 Return Error Indicates that an error has occurred at the 011 011 application or user level. 10100 11101 Reject Indicates that an error has occurred at the 100 100 protocol level. 11101 Invoke (Not Invokes an operation at a remote node. 101 Last) Further responding components are expected. Applies only to ANSI Networks. 10100 11101 Return Result Returns the result of a successfully 111 110 (Not Last) invoked operation. Subsequent components are sent.