Descriptions
The Message Transfer Part provides a reliable transfer and delivery of signaling information across signaling networks. It is divided into three levels:
•MTP Level 1 defines the physical, electrical, and functional characteristics for the signaling data link.
•MTP Level 2 provides the reliability aspects of MTP including error monitoring and recovery.
•MTP Level 3 provides the link, route, and traffic management aspects of MTP.
The MTP software and boards support ITU-T, ANSI, and Chinese variants of the protocol, enabling applications to be widely deployed.
MTP provides the means to:
•Interface with the SS7 network
•Detect and correct errors to messages sent on signaling links
•Manage links and routes, thus mitigating failures and congestion within the network should they occur
MTP provides routing services for SCCP and ISUP on a point-to-point basis. In addition, MTP supports TCAP, which depends upon SCCP, as well as the protocols such CAP and GSM MAP that are supported by TCAP.
The UltraWAVE MTP modules support the relevant addressing (point code) scheme required by ITU-T, ANSI, and China. In addition, it supports:
•4 networks: National, National Spare, International, International Spare
•14-bit / 24-bit originating point code
•1024 signaling links
•512 linksets
•1024 routing sets (destination point code) per network
•16 links per linkset
Signaling Point Code (SPC) in the SS7 network is uniquely identified by a numeric point code. Point codes are carried in signaling messages exchanged between signaling points to identify the origination (Originating Point Code) and destination (Destination Point Code) of each message. Each signaling point in a signaling network is allocated to a code plan that is unambiguous within a domain (International, International Spare, National, National Spare), in accordance with the Network Indicator (NI). Signaling points in the same domain are specified to a fixed length, either 14-bit or 24-bit. Message routing is the process of selecting, for each signaling message to be sent, the signaling linkset to be used. It is based on analysis of the predetermined routing data at the signalling point concerned. •ACN: The Application Context Name enables the version negotiation for the MAP messages, which make the system more compatible with the other networks by means of flexible message version adjustment. The adjustable version includes Version 1, Version 2 and Version 3.
|
Telecommunication network served by a common channel signaling is composed of a number of switching and processing nodes interconnected by transmission links. To communicate using SS7, each of these nodes must act as a signalling point within the SS7 network. In addition, there will be a need to interconnect these signalling points by means of signalling data links, such that SS7 information may be conveyed between them. •SLC: The selection of outgoing link is based on information in the DPC and Signaling Link Code field. The Signaling Link Code is used to: -Ensure message sequencing. Any two messages sent with the same SLC will always arrive at the destination in the same order in which they were originally sent. -Allow equal load sharing of traffic among all available links. In theory, if a user part sends messages at regular intervals and assigns the SLC values in a round-robin fashion, the traffic level should be equal among all links (within the combined linkset) to that destination. •Sigtran: The Sigtran protocol deliveries traditional switched circuit signaling on IP network, with an emphasis on SS7 over IP. •M2UA: The M2UA protocol is the layer between SCTP and MTP3 that separates the physical SS7 termination from the actual signaling point within the network. M2UA serves several purposes. The first purpose is to provide a mechanism for the transport of SS7 MTP2 user signaling (e.g., MTP3 messages) over IP using SCTP. The second purpose is to allow remote placement of SS7 link terminations and back haul SS7 traffic to a centralized point in the network.
|
A number of parallel signaling links constitute a linkset.
|
The Signaling Gateway provides interworking between the UltraWAVE MSC and the IP-based network elements. It is implemented as an embedded component of MTP3.
|
Each signaling point in the SS7 network is identified with a unique address called a point code. Point codes are carried in signaling messages exchanged between signaling points to identify the source and destination of each message. The point code is a hierarchical address that consists of a network identification which identifies a signaling network. In the ITU definition, there are four signaling networks and each signaling network can have a unique Originating Point Code. The Flexible Point Codes Function of the UltraWAVE system is an extension of the upper definition; it allows each signaling network to have multiple point codes. That means several Originating Point Codes may exist in the same signaling network. This function is based on the achievement of binding OPCs on linksets and routes. The UltraWAVE system supports up to 512 linkset, each linkset should be assigned to a signaling network and have an individual OPC. When the OPC of the linkset is ignored, the linkset will take the OPC of its signaling network as an alternative. The OPC of the linkset takes priority over the OPC of its signaling network. Each linkset has its own route to define a particular destination and its accompany alternate linkset. Just like the linkset, a route should be assigned to a signaling network and have an individual OPC. When the OPC of the route is ignored, the route will take the OPC of its signaling network as an alternative. The OPC of the route takes priority over the OPC of its signaling network.
|
MTP3 Parameter Dictionary
Parameter |
Definition |
Range |
System |
-- |
-- |
•TCP Port |
Specify a TCP port for the SCCP-Lite protocol. •Default = 5000 |
-- |
Int Network Int S Network Nat Network Nat S Network |
Parameter configuration for the International network. The other three networks have the same parameter structure. |
International International Spare National National Spare |
•OPC |
Assign a default Point Code to the local MSC. This OPC is applicable only to the specific signaling network. |
ITU = 1 - 16383 ANSI = 1 - 16777215 |
•Point Code Length |
Specify the length of Point Code using in the international signaling network. |
•14-bit •24-bit |
•Point Code Type |
Specify the protocol stack using in the international signaling network. It can be ITU or ANSI. |
•ITU •ANSI |
> Routing |
-- |
Max 1024 items |
•Title |
Routing destination name for identification purpose only. |
-- |
•DPC |
Decimal Point Code of the routing destination node. |
ITU = 1 - 16383 ANSI = 1 - 16777215 |
•OPC |
Specify a virtual Point Code to the local MSC. This OPC will be transmitted between the local MSC and the destination node. From the destination node's perspective, it's the unique Point Code of the local MSC. The compulsory OPC makes the system more compatible with other networks by means of supporting multiple point codes. Set 0 to use the default OPC for this routing entry. |
|
•Normal Linkset |
Specify the primary linkset to the routing entry for signaling addressing. |
0 - 511 |
•Alternative Linkset |
Specify a secondary linkset to the routing entry for signaling addressing when the primary linkset is unavailable. |
|
•M3UA Routing Context |
Define routing context to identify M3UA traffic transmitted between the local MSC and the destination node. The routing context must be unique for each M3UA application defined. |
0 - 16777215 |
Linkset |
-- |
Max 512 items |
•Title |
Linkset destination name for identification purpose only. |
-- |
•Admin State |
(Read Only) Control the operation of the managed linkset by lock and unlock commands. |
•Locked •Unlocked |
•Status |
(Read Only) The current status of the serving linkset. |
•Online •Offline |
•Network Indicator |
Identify the Network Indicator of this linkset. |
•National •National Spare •International •International Spare |
•DPC |
Decimal Point Code of the linkset destination node. |
ITU = 1 - 16383 ANSI = 1 - 16777215 |
•OPC |
Specify a virtual Point Code to the local MSC. This OPC will be transmitted between the local MSC and the destination node. From the destination node's perspective, it's the unique Point Code of the local MSC. The compulsory OPC makes the system more compatible with other networks by means of supporting multiple point codes. Set 0 to use the default OPC of the specific signaling network. |
|
•Loopback Option |
Enable to loop all data on this linkset from transmit side back to receive side. Enable it on the linksets connected between two MSS platforms. |
•Enable •Disable |
Link |
-- |
Max 1024 items |
•Title |
Link destination name for identification purpose only. |
-- |
•Admin State |
(Read Only) Control the operation of the managed link by lock and unlock commands. |
•Locked •Unlocked |
•Status |
(Read Only) The current status of the serving link. |
•Online •Offline |
•Signaling Type |
Specify the signaling type of this link. •ECP = 8KE1 Control Protocol defined for circuit switch applications. •M2UA = Signaling transport over MTP2 User Adaptation Layer. •M3UA = Signaling transport over MTP3 User Adaptation Layer. •IUA = Signaling transport over ISDN User Adaptation Layer. •MTP3-Lite = Protocol defined for IPA BSS or AMG connections. |
•ECP •M2UA •M3UA •IUA •MTP3-Lite |
•Linkset ID |
Specify the index number of the associated linkset to this link. |
0 - 511 |
•SLC |
Signaling Link Code ranges from 0 to 15. The SLC must be unique for each link within the same linkset. |
0 - 15 |
•Host IP |
Specify the primary management server of this link. Enter the IP address of MSC-0 or MSC-1. |
Dotted decimal format |
•Alternative Host IP |
Specify a secondary management server of this link just in case the primary server is unavailable. Enter the IP address of MSC-1 or MSC-0. |
|
•SG ID |
Specify the index number of the relevant signaling gateway to this link. |
0 - 255 |
•M2UA IID |
Specify M2UA Interface Identifier (IID) to this link. The IID must be unique for each link connected to the same signaling gateway. |
0 - 15 |
•Application Mode |
(For MTP3-Lite) Specify the application mode of the local MSC when connecting to the IPA BSS or AMG. |
•Server •Client |
•Remote IP |
(For MTP3-Lite) IP address of the connected IPA BSS or AMG. |
Dotted decimal format |
•Inactivity Timeout |
(For MTP3-Lite) Specify the allowable interval of time without receiving a heartbeat from IPA BSS or AMG. Unit is second. |
0 - 255 seconds |
•Allowed Timeout Times |
(For MTP3-Lite) Define the maximum number of allowed inactivity timeout. |
0 - 255 |
SG |
-- |
Max 256 items |
•Admin State |
(Read Only) Control the operation of the managed SG entry by lock and unlock commands. |
•Locked •Unlocked |
•Application Mode |
Specify the application mode of the connected signaling gateway. |
•Server •Client |
•ACK Option |
Enable or disable ACK message delivery on this SG entry. |
•Allow •Forbid |
•Signaling Type |
Specify the signaling type of this signaling gateway. •M2UA = Signaling transport over MTP2 User Adaptation Layer.< •M3UA = Signaling transport over MTP3 User Adaptation Layer. •IUA = Signaling transport over ISDN User Adaptation Layer. |
•M2UA •M2UA •IUA |
•Remote IP |
IP address of the signaling gateway destination. |
Dotted decimal format |
Return to
2.1.1.22