ISUP:Information element usage - Revision history

Ktrueman: added 2nd table

2009-09-10T19:25:08Z

added 2nd table

Ktrueman: /* IE inclusion in different messages */ added first table

2009-09-10T19:21:13Z

IE inclusion in different messages: added first table

Ktrueman: added 2nd section; need to add tables

2009-08-24T21:43:51Z

added 2nd section; need to add tables

Ktrueman: initial content with pruning

2009-08-24T21:41:46Z

initial content with pruning

New page

Within every notification or request message (other than a configuration message), the host application will have to read or insert data structures called “information elements” (or IEs). These data structures contain mandatory or optional information required by the [[ISUP]] layer and/or the remote ISUP layer to properly process the required operation (such as issuing a voice call).

The [[SS7]] ISUP specifications define approximately one hundred different IEs that are used differently according to the variant or type of message. As a common example, the “called party number” IE contains the phone number of the party the host application wants to connect to. Therefore, this IE is inserted in the [[IAM]] message to inform the remote ISUP layer about the targeted end-user.

'''NOTE:''' ITU-T information elements are described more in detail in specification document Q.763.

'''NOTE:''' IE encoding, although similar between specifications (i.e. ANSI and ITU), may still differ slightly and requires that the user have access to the specification documents he plans to use. Since those are copyright-protected documents, TelcoBridges cannot make those directly available.

@@ Line 13: / Line 13: @@
 == IE inclusion in different messages ==
 Depending on which messages are sent to / received from the SS7 network, the host application should expect specific IEs to be inserted or processed.  The following two tables show in which messages IEs can be used or are to be expected. Some IEs are mandatory, which means that a request toward the stack will fail if they are not present. On the other hand, it does mean that optional IEs are not required but that it may depend on the variant that is being used or on the local network implementation. This is why the host application designer needs to verify with national or international authority for the proper IEs.
@@ Line 81: / Line 84: @@
 User-to-User indicators	O					O	O	O	O		O											O	O
 User-to-user information	O					O	O	O	O		O																	O		M
 </tab>

← Older revision		Revision as of 19:21, 10 September 2009
Line 13:		Line 13:
	== IE inclusion in different messages ==		== IE inclusion in different messages ==
	Depending on which messages are sent to / received from the SS7 network, the host application should expect specific IEs to be inserted or processed. The following two tables show in which messages IEs can be used or are to be expected. Some IEs are mandatory, which means that a request toward the stack will fail if they are not present. On the other hand, it does mean that optional IEs are not required but that it may depend on the variant that is being used or on the local network implementation. This is why the host application designer needs to verify with national or international authority for the proper IEs.		Depending on which messages are sent to / received from the SS7 network, the host application should expect specific IEs to be inserted or processed. The following two tables show in which messages IEs can be used or are to be expected. Some IEs are mandatory, which means that a request toward the stack will fail if they are not present. On the other hand, it does mean that optional IEs are not required but that it may depend on the variant that is being used or on the local network implementation. This is why the host application designer needs to verify with national or international authority for the proper IEs.
		+
		+
		+	----
		+
		+
		+	'''ISUP mandatory/optional IEs (ITU)'''
		+	<tab border=1>
		+	Information elements IAM SAM IN IN COT ACM CO CP ANM FOT RE RL CC BLO BLA SU CF CG CGB CQ CQ FAA FR FAC ID IR NR SG PAM US UPA
		+	RS UBL UBA RE CG CGU GR FAR UP
		+	LPA OL UCI GR
		+	Access delivery information O O O O O
		+	Access transport O O O O O O O O O
		+	Automatic congestion level O
		+	Backward call indicators M M O O
		+	Call diversion information O O
		+	Call history information O O
		+	Call reference O O O O O O O O O O
		+	Called party number M
		+	Calling party number O O O
		+	Calling party’s category M O
		+	Cause indicators O O M O M M
		+	Circuit group supervision message type ind. M M
		+	Circuit state indicator M
		+	CUG interlock code O
		+	Connected number O O
		+	Connection request O O O
		+	Continuity indicators M
		+	Echo control information O O O O
		+	Event information O O O O O O O O O O O O O O O O O O O O O O
		+	Facility indicator M
		+	Forward call indicator M
		+	Generic digit O O
		+	Generic notification ind. O O O O O O
		+	Generic number O O O O O
		+	Generic reference O
		+	Information indicators M
		+	Information request indicators M
		+	Location number O
		+	Message compatibility information O O O O O
		+	MCID response indicator O
		+	MCID request indicators O
		+	MLPP precedence O
		+	Nature of connection indicators M
		+	Network specific facility O O O O O O O O
		+	Optional backward call indicators O O O O
		+	Optional forward call indicators O
		+	Original called number O
		+	Originating ISC point code O
		+	Parameter compatibility information O O O O O O O O O O O O O O
		+	Propagation delay counter O
		+	Range and status M M M M
		+	Redirection information O O
		+	Redirecting number O
		+	Redirection number O O O O O
		+	Redirection number restricted O O O O O
		+	Remote operations O O O O O O
		+	Service activation O O O O O O
		+	Signaling point code O
		+	Subsequent number M
		+	Suspend/resume indicators M
		+	Transit network selection O
		+	Transmission medium requirement M
		+	Transmission medium requirement prime O
		+	Transmission medium used O O O O
		+	User service information O
		+	User service information prime O
		+	User-to-User indicators O O O O O O O O
		+	User-to-user information O O O O O O O M
		+	</tab>

← Older revision		Revision as of 21:43, 24 August 2009
Line 9:		Line 9:

	'''NOTE:''' IE encoding, although similar between specifications (i.e. ANSI and ITU), may still differ slightly and requires that the user have access to the specification documents he plans to use. Since those are copyright-protected documents, TelcoBridges cannot make those directly available.		'''NOTE:''' IE encoding, although similar between specifications (i.e. ANSI and ITU), may still differ slightly and requires that the user have access to the specification documents he plans to use. Since those are copyright-protected documents, TelcoBridges cannot make those directly available.
		+
		+
		+	== IE inclusion in different messages ==
		+	Depending on which messages are sent to / received from the SS7 network, the host application should expect specific IEs to be inserted or processed. The following two tables show in which messages IEs can be used or are to be expected. Some IEs are mandatory, which means that a request toward the stack will fail if they are not present. On the other hand, it does mean that optional IEs are not required but that it may depend on the variant that is being used or on the local network implementation. This is why the host application designer needs to verify with national or international authority for the proper IEs.