Signaling System No.7 Protocol Architecture And Sevices part 38

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

0
27
lượt xem
3
download

Signaling System No.7 Protocol Architecture And Sevices part 38

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

ANSI Protocol Message Contents The following sections describe the set of ANSI messages, the fields included in each, and specify the mandatory and optional fields for each message type. The message types specified by ANSI include

Chủ đề:
Lưu

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

  1. ANSI Protocol Message Contents The following sections describe the set of ANSI messages, the fields included in each, and specify the mandatory and optional fields for each message type. The message types specified by ANSI include: • Unidirectional • Query • Conversation • Response • Protocol abort • User abort • Dialogue portion In the messages, fields marked as "Mandatory*" must be present, but their contents can be empty. Unidirectional Message The Unidirectional Message is sent when no reply is expected. Table 10-14 lists the message contents. Table 10-14. Unidirectional Message Fields Unidirectional Message Fields Mandatory/Optional Package Type Identifier Mandatory Total Message Length Transaction ID Identifier Mandatory Transaction ID Length (Set to 0) Dialogue Portion Optional Component Sequence Identifier Mandatory Component Sequence Length Components
  2. Query With/Without Permission The Query Message is used to initiate a transaction. There are two types of Query messages: Query with Permission and Query without Permission. The Query with Permission message gives the receiving node permission to end the transaction at any time. The Query without Permission message does not give the receiving node permission to end the transaction. After receiving this message, the transaction remains established until the originator ends it or sends a subsequent message giving the receiving node permission to end the transaction. Table 10-15 lists the message contents. Table 10-15. Query Message Fields Query With/Without Permission Message Fields Mandatory/Optional Package Type Identifier Mandatory Total Message Length Transaction ID Identifier Mandatory Transaction ID Length Originating Transaction ID Dialogue Portion Optional Component Sequence Identifier Optional Component Sequence Length Components Conversation With/Without Permission The Conversation Message is used to exchange additional information for a previously established transaction. There are two types of Conversation Messages: Conversation with Permission and Conversation without Permission Message.
  3. The Conversation with Permission Message gives the receiving node permission to end the transaction at any time. The Conversation without Permission message does not give the receiving node permission to end the transaction. After receiving this message, the transaction remains established until the originator ends it or sends a subsequent message giving the receiving node permission to end the transaction. Table 10-16 lists the message contents. Table 10-16. Conversation Message Fields Conversation With/Without Permission Message Fields Mandatory/Optional Package Type Identifier Mandatory Total Message Length Transaction ID Identifier Mandatory Transaction ID Length Originating Transaction ID Responding Transaction ID Dialogue Portion Optional Component Sequence Identifier Optional Component Sequence Length Components Response Message The Response Message is sent to end a transaction. Table 10-17 lists the message contents. Table 10-17. Response Message Fields
  4. Response Message Fields Mandatory/Optional Package Type Identifier Mandatory Total Message Length Transaction ID Identifier Mandatory Transaction ID Length Responding Transaction ID Dialogue Portion Optional Component Sequence Identifier Optional Component Sequence Length Components Protocol Abort (P-Abort) Message The Protocol Abort (P-Abort) Message is sent to terminate a previously established transaction. A P-Abort is initiated because of an error at the TCAP protocol layer. Table 10-18 lists the message contents. Table 10-18. Abort Message Fields Abort (P-Abort) Message Fields Mandatory/Optional Message Type Mandatory Total Message Length Transaction ID Identifier Mandatory Transaction ID Length Transaction ID P-Abort Cause Identifier Mandatory
  5. P-Abort Cause Length P-Abort Cause User Abort (U-Abort) Message The User Abort (U-Abort) Message is sent to terminate a previously established transaction. A U-Abort is initiated at the Application Layer based on application logic. Table 10-19 lists the message contents. Table 10-19. User Abort Message Fields Abort (U-Abort) Message Fields Mandatory/Optional Message Type Mandatory Total Message Length Transaction ID Identifier Mandator Transaction ID Length Transaction ID Dialogue Portion Optional U-Abort Information Identifier Mandatory U-Abort Information Length U-Abort Information  
Đồng bộ tài khoản