MTP2:Architecture - Revision history

Cboulanger at 02:39, 2 September 2009

2009-09-02T02:39:10Z

← Older revision		Revision as of 21:39, 1 September 2009
Line 27:		Line 27:

	The MTP Level 2 software prevents deadlocks and overload conditions from occurring.		The MTP Level 2 software prevents deadlocks and overload conditions from occurring.


	~~[[category:Needs revising]]~~

Cboulanger at 01:35, 2 September 2009

2009-09-02T01:35:49Z

← Older revision		Revision as of 20:35, 1 September 2009
Line 5:		Line 5:


	MTP2 ~~can be~~ used in conjunction with an above local MTP3 layer ~~and can be used as a standalone and communicates with remote MTP3 layer (host application). See [[MTP2:Connection mode\|MTP2 connection mode]] for more information~~.		MTP2 is used in conjunction with an above local MTP3 layer.


	[[Image:MTP2-layer-hierarchy.jpg\|600px\| ]]		[[Image:MTP2-layer-hierarchy.jpg\|600px\| ]]

Ktrueman: added 2nd graphic and links to other content

2009-08-25T17:28:02Z

added 2nd graphic and links to other content

← Older revision		Revision as of 12:28, 25 August 2009
Line 1:		Line 1:
	[[MTP2 Layer\|MTP Level 2]] defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link. The MTP2 layer is a service provider to the MTP3 Link layer. The MTP2 layer is a service user of [[Web_Portal_Tutorial_Guide#Line_Interfaces\|line interfaces / line ~~services”~~]] as seen in the shown in the figure below.		[[MTP2 Layer\|MTP Level 2]] defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link. The MTP2 layer is a service provider to the MTP3 Link layer. The MTP2 layer is a service user of [[Web_Portal_Tutorial_Guide#Line_Interfaces\|line interfaces / line services]] as seen in the shown in the figure below.


	[[Image:MTP2-architecture.jpg\|700px~~\|MTP2 architecture schematic~~]]		[[Image:MTP2-architecture.jpg\|700px]]


	MTP2 can be used in conjunction with an above local MTP3 layer and can be used as a standalone and communicates with remote MTP3 layer (host application). See ~~the~~ connection mode ~~table in the MTP2 Configuration section~~.		MTP2 can be used in conjunction with an above local MTP3 layer and can be used as a standalone and communicates with remote MTP3 layer (host application). See [[MTP2:Connection mode\|MTP2 connection mode]] for more information.


	[[Image:~~filename~~\|~~thumb\|widthpx~~\| ]]		[[Image:MTP2-layer-hierarchy.jpg\|600px\| ]]


	A MTP2 Link must be associated with one ~~Trunk instance~~. It’s a 1-to-1 association. MTP Level 2 defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link.		A MTP2 Link must be associated with one line interface/service. It’s a 1-to-1 association. MTP Level 2 defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link.


	'''IMPORTANT NOTE:''' It is important to ensure that the received and transmitted clocks of the ~~Trunk~~ were synchronized. This can be useful for removing/limiting undesirable FIB and BSN errors. See section “Clock Configurations” in the TB640 user’s guide.		'''IMPORTANT NOTE:''' It is important to ensure that the received and transmitted clocks of the line interface/service were synchronized. This can be useful for removing/limiting undesirable FIB and BSN errors. (See section “Clock Configurations” in the TB640 user’s guide.)

Ktrueman: clean up

2009-08-25T15:57:39Z

clean up

← Older revision		Revision as of 10:57, 25 August 2009
Line 2:		Line 2:


	[[Image:MTP2-architecture.jpg\|~~800px~~\|MTP2 architecture schematic]]		[[Image:MTP2-architecture.jpg\|700px\|MTP2 architecture schematic]]

Ktrueman: added graphic

2009-08-25T13:58:12Z

added graphic

← Older revision		Revision as of 08:58, 25 August 2009
Line 1:		Line 1:
	A MTP2 ~~Link must be associated with one Trunk instance. It’s a 1 to 1 association.~~ MTP Level 2 defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link.		[[MTP2 Layer\|MTP Level 2]] defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link. The MTP2 layer is a service provider to the MTP3 Link layer. The MTP2 layer is a service user of [[Web_Portal_Tutorial_Guide#Line_Interfaces\|line interfaces / line services”]] as seen in the shown in the figure below.


	'''~~Important note~~:''' It is important to ensure that the received and transmitted clocks of the Trunk were synchronized. This can be useful for removing/limiting undesirable FIB and BSN errors. See section “Clock Configurations” in the TB640 user’s guide.		[[Image:MTP2-architecture.jpg\|800px\|MTP2 architecture schematic]]


			MTP2 can be used in conjunction with an above local MTP3 layer and can be used as a standalone and communicates with remote MTP3 layer (host application). See the connection mode table in the MTP2 Configuration section.


			[[Image:filename\|thumb\|widthpx\| ]]


			A MTP2 Link must be associated with one Trunk instance. It’s a 1-to-1 association. MTP Level 2 defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link.


			'''IMPORTANT NOTE:''' It is important to ensure that the received and transmitted clocks of the Trunk were synchronized. This can be useful for removing/limiting undesirable FIB and BSN errors. See section “Clock Configurations” in the TB640 user’s guide.

Ktrueman: clean up

2009-08-14T21:06:35Z

clean up

← Older revision		Revision as of 16:06, 14 August 2009
Line 2:		Line 2:


	'''Important note:''' It is important to ensure that the received and transmitted ~~clock~~ of the Trunk ~~was~~ synchronized. This can be useful ~~to remove~~ undesirable FIB and BSN ~~error~~. See section “Clock Configurations” in the TB640 user’s guide.		'''Important note:''' It is important to ensure that the received and transmitted clocks of the Trunk were synchronized. This can be useful for removing/limiting undesirable FIB and BSN errors. See section “Clock Configurations” in the TB640 user’s guide.


	== Priorities ==		== Priorities ==

Ktrueman: initial content

2009-08-10T14:28:57Z

initial content

New page

A MTP2 Link must be associated with one Trunk instance. It’s a 1 to 1 association. MTP Level 2 defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link.

'''Important note:''' It is important to ensure that the received and transmitted clock of the Trunk was synchronized. This can be useful to remove undesirable FIB and BSN error. See section “Clock Configurations” in the TB640 user’s guide.

== Priorities ==
No pre-emption of data occurs in the process of being transmitted or requiring retransmission. Only a single congestion priority is supported for ANSI and ITU. For a TTC/NTT link, transmitted data buffers are prioritized based on the priority indicated by [[MTP3 Layer|MTP Level 3]].

== Flow control ==
The MTP Level 2 software regulates data flow when resource utilization (such as buffer pool size or queue length) reaches specifies thresholds. For each threshold, MTP Level 2 performs one of the following actions:
*Informs the layer manager about flow control.
*Sends a link status signal unit with status "B" (busy).
*Sends a flow control indication to the upper layer.

The MTP Level 2 software prevents deadlocks and overload conditions from occurring.

[[category:Needs revising]]