Re: ASP Capabilities value 0x2 of interworking field
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Stanislav, Stanislav Ivanovich wrote: (Tue, 20 Dec 2005 07:44:05) > > > However the essential point is that the AS/RC concepts which is > symmetrical one (at least in SE model) is not suitable to perform the > relay. > > Traditi! onal SS7 networks (MTP and SCCP) are asymmetrical in sense > that they do not care where the message originated but where it has to > be delivered. Yah. SS7 links are uni-directional. > > In xxUA networks AS/RC concept in mandatory SE model both originating > and destination addresses have to be specified and only > these combinations are allowed. This is extremely unfriendly for > relay! No they don't. Any routing key is possible. Dynamic registration does not support all possible routing keys. Provisioned routing keys can take any form. Also note that SUA registration supports multiple and ranges of addresses in a dynamically registered routing key. Not even M3UA restricts its routing keys to a single originating or destination point code. You can have one destination HLR point code and 400 MSC originating point codes if you'd like. Or visa versa. Or 400 of each. > > Thus in traditional networks TFP or SSP messages manage traffic in > only one direction. Even more granularity of traffic is uniquely and > defined by the specifications. > > However in the AS/RC concept in the mandatory SE model one ASP TM > message manages traffic in both directions! ASP TM messages are not used to manage relay. SNMM messages are. --brian -- Brian F. G. Bidulock [email protected] http://www.openss7.org/