Transport - Revision history

Monica at 12:43, 23 August 2013

2013-08-23T12:43:57Z

Monica: /* Addressing */

2013-08-23T12:43:34Z

‎Addressing

Monica: /* Addressing */

2013-08-23T12:43:15Z

‎Addressing

Monica: /* Parameters */

2013-08-23T12:39:08Z

‎Parameters

Monica: /* TCAP */

2013-08-23T12:38:19Z

‎TCAP

Monica: /* SCCP */

2013-08-23T12:37:05Z

‎SCCP

Monica: /* MTP */

2013-08-23T12:35:47Z

‎MTP

Monica: /* SCCP */

2013-08-23T12:33:57Z

‎SCCP

Monica: /* MTP */

2013-08-23T12:33:13Z

‎MTP

Monica at 12:31, 23 August 2013

2013-08-23T12:31:22Z

← Older revision		Revision as of 12:43, 23 August 2013
Line 61:		Line 61:

	A trasaction may be terminated silently (without actually sending a message to the remote), usually after waiting a while for an error notification. To achieve such a result send !!!!!!!!!!!!!		A trasaction may be terminated silently (without actually sending a message to the remote), usually after waiting a while for an error notification. To achieve such a result send !!!!!!!!!!!!!
−
−	~~==Component==~~

	==Addressing==		==Addressing==

@@ Line 69: / Line 69: @@
 * '''SCCP Global Titles'''
-->The calling or Called Party Global Titles are usually populated with the numbers associated with the network entities (HLR, VLR, MSC, etc) exchanging the messages.
+The calling or Called Party Global Titles are usually populated with the numbers associated with the network entities (HLR, VLR, MSC, etc) exchanging the messages.
-->For the '''sendAuthenticationInfo''' and '''updateLocation''' operations the IMSI of the SIM card is used as Called (for request) or Calling (for response) Party Address.
 * '''TCAP Dialog user information'''
-->Some operations add User Information in the TCAP dialog. These allow addressing the mobile stations by their IMSI while SCCP is used to route the message to the network entity (MSC, VLR, HLR) where the user is roaming or registered.
+Some operations add User Information in the TCAP dialog. These allow addressing the mobile stations by their IMSI while SCCP is used to route the message to the network entity (MSC, VLR, HLR) where the user is roaming or registered.
 * '''Parameters embedded in requests'''
-->Most messages include specific parameters to identify the network elements. The message as a whole is routed by SCCP GT but internally the systems are using these parameters for database access or forwarding the information.
+Most messages include specific parameters to identify the network elements. The message as a whole is routed by SCCP GT but internally the systems are using these parameters for database access or forwarding the information.
 All these types of addressing may be present in a single message.

← Older revision		Revision as of 12:43, 23 August 2013
Line 65:		Line 65:

	==Addressing==		==Addressing==
		+
		+	There are several types of addresses that are used to specify at which server and / or mobile station is a message to be delivered. The exact usage depends on the context of the operation that creates the TCAP dialog.
		+
		+	* '''SCCP Global Titles'''
		+	->The calling or Called Party Global Titles are usually populated with the numbers associated with the network entities (HLR, VLR, MSC, etc) exchanging the messages.
		+	->For the '''sendAuthenticationInfo''' and '''updateLocation''' operations the IMSI of the SIM card is used as Called (for request) or Calling (for response) Party Address.
		+
		+	* '''TCAP Dialog user information'''
		+	->Some operations add User Information in the TCAP dialog. These allow addressing the mobile stations by their IMSI while SCCP is used to route the message to the network entity (MSC, VLR, HLR) where the user is roaming or registered.
		+
		+	* '''Parameters embedded in requests'''
		+	->Most messages include specific parameters to identify the network elements. The message as a whole is routed by SCCP GT but internally the systems are using these parameters for database access or forwarding the information.
		+
		+	All these types of addressing may be present in a single message.

@@ Line 53: / Line 53: @@
 ===Parameters===
-* '''request-type''' – Type of the TCAP request, may be one of:
+* '''request-type''' – Type of the TCAP request, may be one of: Begin, Continue, End
-->Begin, Continue, End
 * localTID – Local Transaction ID
 * remoteTID – Remote Transaction ID

@@ Line 49: / Line 49: @@
 ==TCAP==
 ==Component==
 ==Addressing==

@@ Line 29: / Line 29: @@
   	</CallingPartyAddress>
   </sccp>
 ==TCAP==

@@ Line 6: / Line 6: @@
 This section may be missing for error reports created higher in the protocol stack or if the SS7 transport is not MTP.
   <mtp>
-     <LocalPC>101</LocalPC>
+       <LocalPC>101</LocalPC>
-     <RemotePC>5000</RemotePC>
+       <RemotePC>5000</RemotePC>
-     <sls>2</sls>
+       <sls>2</sls>
   </mtp>
 ===Parameters===
-* LocalPC – Point Code on the local side; DPC for inbound messages, OPC for outbound
+* <strike>LocalPC</strike> – Point Code on the local side; DPC for inbound messages, OPC for outbound
 * RemotePC – Point Code on the local side; OPC for inbound messages, DPC for outbound
 * sls – Signaling Link Selection Code

← Older revision		Revision as of 12:33, 23 August 2013
Line 17:		Line 17:

	==SCCP==		==SCCP==
		+	The <sccp> transport describes the SCCP specific parameters. These control how messages are routed to their destination by point code, subsystem or phone number. This section may be missing for error reports created higher in the protocol stack (for example TCAP transaction timeout).
		+
		+	<sccp>
		+	<CalledPartyAddress>
		+	<ssn>5</ssn>
		+	<pointcode>101</pointcode>
		+	<gt nature="international" plan="isdn">492115000000</gt>
		+	</CalledPartyAddress>
		+	<CallingPartyAddress>
		+	<ssn>0</ssn>
		+	</CallingPartyAddress>
		+	</sccp>

	==TCAP==		==TCAP==

← Older revision		Revision as of 12:33, 23 August 2013
Line 2:		Line 2:

	==MTP==		==MTP==
		+	The <mtp> transport section describes message parameters specific to MTP. Normally these parameters are just informative for the applications and on new outbound messages are added automatically.
		+
		+	This section may be missing for error reports created higher in the protocol stack or if the SS7 transport is not MTP.
		+	<mtp>
		+	<LocalPC>101</LocalPC>
		+	<RemotePC>5000</RemotePC>
		+	<sls>2</sls>
		+	</mtp>
		+
		+	===Parameters===
		+	* LocalPC – Point Code on the local side; DPC for inbound messages, OPC for outbound
		+	* RemotePC – Point Code on the local side; OPC for inbound messages, DPC for outbound
		+	* sls – Signaling Link Selection Code

	==SCCP==		==SCCP==

← Older revision		Revision as of 12:31, 23 August 2013
Line 1:		Line 1:
	The transport part of the message contains parameters related to the lower level transports. On receive these parameters are filled from the received message. On send these parameters are used by the transports to properly form and route the message.		The transport part of the message contains parameters related to the lower level transports. On receive these parameters are filled from the received message. On send these parameters are used by the transports to properly form and route the message.
		+
		+	==MTP==
		+
		+	==SCCP==
		+
		+	==TCAP==
		+
		+	==Component==
		+
		+	==Addressing==