Hi,
I am supposed to determine general requirements of MSP, for example, we can extract configuration and status of ms protection by studying its standard (ITU-T G.841) and we can determine its requirements from Hw such as defects, KBytes, the request of
switching and bridge. but some requirements of MSP is not mentioned in standard directly, for example when we want to create an MSP module, working and protection ports must have same STM level or when we select a port as a protection or working port we
can not consider this port as another MSP protection application.
is there anyone can guide me to find other requirements like expressed items? thanks in advance,
Elnaz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello Elnaz,

You added:

I am supposed to determine general requirements of MSP,
for example, we can extract configuration and status of
ms protection by studying its standard (ITU-T G.841) and > we can determine its requirements from Hw such as defects,
KBytes, the request of switching and bridge. but some
requirements of MSP is not mentioned in standard directly,
for example when we want to create an MSP module, working
and protection ports must have same STM level or when we
select a port as a protection or working port we can not
consider this port as another MSP protection application.

That knowledge is considered "good engineering practice" of
the systems engineer and the implementer.

It is Multiplex SECTION Protection, so the protected section
will have the same STM-N level N.

MSP is 1+1 protection so one port can only protect one other
port (if it would protect other ports it would be 1:n protection).

is there anyone can guide me to find other requirements
like expressed items?

I hope the above clarifies your concern.

Best regards, Huub.

--
reply to hhelvooort with 2 'o's ================================================================
http://www.van-helvoort.eu/ ================================================================
Always remember that you are unique...just like everyone else...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Monday, December 25, 2017 at 3:29:07 PM UTC+3:30, e.baghe...@gmail.com wrote:

Hi,
I am supposed to determine general requirements of MSP, for example, we can extract configuration and status of ms protection by studying its standard (ITU-T G.841) and we can determine its requirements from Hw such as defects, KBytes, the request of

switching and bridge. but some requirements of MSP is not mentioned in standard directly, for example when we want to create an MSP module, working and protection ports must have same STM level or when we select a port as a protection or working port we
can not consider this port as another MSP protection application.

is there anyone can guide me to find other requirements like expressed items? thanks in advance,
Elnaz

Dear Huub
thank you for your reply,
would you please explain me the difference between section, port, trail, and path!
I know MSP is a protection in port level and SNCP is a protection in path level. for example, when MSP switches, AUGs of the working port will be connected to AUGs of protection port so it just enough to have slot and port information but in SNCP we need
not only port information but path information like AUG number, AU number, time slot number. in SNCP a certain working path can be connected to another protection path.(also in SNCP we need cross-level information(VC-3, VC-4, VC-12,...) and protection
type(SNCP/N OR SNCP/I) for determining its defects).
but I still have some doubt about the information of mine!
thanks in advance,
Elnaz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Elnaz,

You write:

thank you for your reply,

You're welcome.

would you please explain me the difference between section,
port, trail, and path!

These are terms used in different technologies.
Section and trail are SDH terms, port ant path are packet
(Ethernet) terms.

A section is the link between two nodes, in general the
Multiplex Section (MS) and if repeaters are use, divided
into several Regenerator Sections (RS).

A trail is the end-to-end connection through a network
passing multiple nodes and sections. Note that a section
is in fact also a trail between two adjacent nodes.

A port is the end of a connection, in SDH the term Termination
Point (TP) is used.

A path in Ethernet is similar to a connection in SDH.
Because a connection does not have to pass the whole network
it is in general referred to as Sub-Network Connection (SNC).

I know MSP is a protection in port level and SNCP is a protection
in path level.

MSP == Multiplex Section Protection so protection at the section
(MS) layer in the network.

SNCP == Sub-Network Connection Protection so protection at the
connection (VC-n) layer in the network.

for example, when MSP switches, AUGs of the working
port will be connected to AUGs of protection port so it just
enough to have slot and port information

Indeed, MSP provides in fact hardware protection. That is why
the physical ports have to be on different card slots.

but in SNCP we need not only port information but path
information like AUG number, AU number, time slot number.

Correct, because the connection functions in each of the nodes
that are passed have to be provisioned.

in SNCP a certain working path can be connected to another
protection path.

AND both work and protection connection have to follow a
different path through the network to avoid single points of
failure.

(also in SNCP we need cross-level information(VC-3, VC-4, > VC-12,...)

to provision the cross-connects. MSP has no intermediate node.

and protection type(SNCP/N OR SNCP/I) for determining its defects).

MSP has only the physical link defects as input for switching.

Best regards, Huub.



--
reply to hhelvooort with 2 'o's ================================================================
http://www.van-helvoort.eu/ ================================================================
Always remember that you are unique...just like everyone else...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)