Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

STM-1 TU12 numbering scheme

1,403 views
Skip to first unread message

benda...@gmail.com

unread,
Oct 16, 2008, 10:37:59 AM10/16/08
to
Hello Huub et al.,

I was a bit confused about the numbering scheme of TU12 within STM-1.

Foreword: G707 specifies how columns should be numbered (this is
paragraph 7.3.9 and Appendix II ): this KLM to column mapping is clear
to me.

What is not clear, is how TU-12 can be numbered from 1 to 63, and what
is the relation to KLM notation ?
That is, I am searching for a rule which would say:
1st TU12 is KLM (1,1,1)
2nd TU12 is KLM(?,?,?)
and so on up to 63th TU12.

I browsed the recommandation, but I don't feel very confident with my
own interpretation (BTW personal interpretation is a bad sign when
reading a recommandation..;-) ).
My own interpretation has two options:

option 1) The end of paragraph 7.3.13 specifies a kind of order
(Tributary#1 is TU12 1-1-1, Tributary#2 is 1-1-2, and so on). Is this
the rule I am looking for ?

option 2) Table 7-1 specifies a "TS#=timeslot number". Is this the
rule I am looking for ?
Thanks for any help.

Ben

Huub van Helvoort

unread,
Oct 16, 2008, 11:23:19 AM10/16/08
to
Hi Ben,

You wrote:

> I was a bit confused about the numbering scheme of TU12 within STM-1.
>
> Foreword: G707 specifies how columns should be numbered (this is
> paragraph 7.3.9 and Appendix II ): this KLM to column mapping is clear
> to me.
>
> What is not clear, is how TU-12 can be numbered from 1 to 63, and what
> is the relation to KLM notation ?
> That is, I am searching for a rule which would say:
> 1st TU12 is KLM (1,1,1)
> 2nd TU12 is KLM(?,?,?)
> and so on up to 63th TU12.
>
> I browsed the recommandation, but I don't feel very confident with my
> own interpretation (BTW personal interpretation is a bad sign when
> reading a recommandation..;-) ).
> My own interpretation has two options:
>
> option 1) The end of paragraph 7.3.13 specifies a kind of order
> (Tributary#1 is TU12 1-1-1, Tributary#2 is 1-1-2, and so on). Is this
> the rule I am looking for ?

Three TU-12 are mapped into a TUG-2 (this is the K number, seven
TUG-2 are mapped into a TUG-3 (this is the L number) and three TUG-3
are mapped into an AU-4 (the M number). You can use this formula
in section 7.3.12 and the note in 7.3.13.

> option 2) Table 7-1 specifies a "TS#=timeslot number". Is this the
> rule I am looking for ?

Look at figure 7-27 the lower part.

Cheers, Huub.

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

benda...@gmail.com

unread,
Oct 16, 2008, 1:19:05 PM10/16/08
to
Thanks Huub.
So figure 7-27 is clear: I can use the TS# as an index in the table
oc TU12 [1,63].


However, I forgot to mention the TU12 are directly mapped to VC4 (not
through VC3).
So 7.3.12 is not applicable (this applies to VC3) in my case.

I still remain confused about the note in 7.3.13.
Is this applicable to TU12 directly mapped to VC4 (not through
VC3) ?


Ben

benda...@gmail.com

unread,
Oct 16, 2008, 2:06:50 PM10/16/08
to
Hi again Huub,

> Three TU-12 are mapped into a TUG-2 (this is the K number, seven
> TUG-2 are mapped into a TUG-3 (this is the L number) and three TUG-3
> are mapped into an AU-4 (the M number). You can use this formula
> in section 7.3.12 and the note in 7.3.13.

I am confused by this sentence: I thought
- K was the index of TUG-3 in AU-4
- L was the index of TUG-2 in TUG-3
- M was the index of TU-12 in TUG-2 ?
Did I really mis-understood the recommandation ?

Ben

Huub van Helvoort

unread,
Oct 16, 2008, 2:30:22 PM10/16/08
to
Hi Ben,

You replied:

> So figure 7-27 is clear: I can use the TS# as an index in the table
> oc TU12 [1,63].
>
> However, I forgot to mention the TU12 are directly mapped to VC4 (not
> through VC3).

If you look at figure 6-1 you will see that VC-12 is always mapped
via TU-12 - TUG-2 and TUG-3 into a VC-4.

> So 7.3.12 is not applicable (this applies to VC3) in my case.

My mistake, you should look at 7.3.9

> I still remain confused about the note in 7.3.13.
> Is this applicable to TU12 directly mapped to VC4 (not throug

> VC-3)

Indeed.

Huub van Helvoort

unread,
Oct 16, 2008, 2:32:31 PM10/16/08
to
Hi Ben,

You replied:

No I mixed up K and M.
(I should stop responding while in a meeting and trying to
follow the discussion....)

benda...@gmail.com

unread,
Oct 17, 2008, 6:49:06 AM10/17/08
to
On 16 oct, 20:32, Huub van Helvoort <hhelvoo...@chello.nl> wrote:
> Hi Ben,
Hi Huub,

thanks for your reply.

> You replied:
>
> >> Three TU-12 are mapped into a TUG-2 (this is the K number, seven
> >> TUG-2 are mapped into a TUG-3 (this is the L number) and three TUG-3
> >> are mapped into an AU-4 (the M number). You  can use this formula
> >> in section 7.3.12 and the note in 7.3.13.
> > I am confused by this sentence: I thought
> > - K was the index of TUG-3 in AU-4
> > - L was the index of TUG-2 in TUG-3
> > - M was the index of TU-12 in TUG-2 ?
> > Did I really mis-understood the recommandation ?
>
> No I mixed up K and M.
> (I should stop responding while in a meeting and trying to
> follow the discussion....)

Sorry to bother you at that time.. Wasn't it time to go home ? :-)

Back to note in 7.3.13:
Tributary#2 is KLM(1,1,2), but KLM(1,1,2) is timeslot number#22,
right ?
Do most companies rather use "tributary port#" or "time slot#" to
convert KLM to a so kind of "readable" [1-63] index ?
Is there a genrally admitted rule ?
Or does any supplier do what he wants, provided the KLM at frame level
is always OK ?

Ben

Huub van Helvoort

unread,
Oct 17, 2008, 10:39:29 AM10/17/08
to
Hello Ben,

You replied:

> Sorry to bother you at that time.. Wasn't it time to go home ? :-)

The time at the top of the message os from my laptop,
physically I am now in the Boston area (time difference 6 hours),
monday I will be back home again ;-)

> Back to note in 7.3.13:
> Tributary#2 is KLM(1,1,2), but KLM(1,1,2) is timeslot number#22,
> right ?
> Do most companies rather use "tributary port#" or "time slot#" to
> convert KLM to a so kind of "readable" [1-63] index ?
> Is there a genrally admitted rule ?
> Or does any supplier do what he wants, provided the KLM at frame level
> is always OK ?

Most equipment makers use the trib port number 1...63 both in
hardware and on the management system.
This to ensure that if two different vendor equipment is connected
the signal input at trib x is output a t trib x.

benda...@gmail.com

unread,
Oct 17, 2008, 11:19:19 AM10/17/08
to
OK, I understand the consensus is:
Trib#1 <=> KLM(1,1,1)
Trib#2 <=> KLM(1,1,2)
Trib#3 <=> KLM(1,1,3)
Trib#4 <=> KLM(1,2,1)

Thanks very much Huub !

Ben

erg...@gmail.com

unread,
Apr 29, 2014, 9:44:05 AM4/29/14
to
Hallo, here is your answer!

SDH tributary numbering
E1 tributary numbering (timslots) for SDH signals in KLM

K describes TUG-3 group (1-3)
L describes a TUG-2 group inside a TUG-3 (1-7)
M describes a TU-12/VC12/E1 inside a TUG-2 (1-3)


Trib TUG-3 TUG-2 VC-12 (-> E1) KLM
1 1 1 1 1.1.1
2 1 1 2 1.1.2
3 1 1 3 1.1.3
4 1 2 1 1.2.1
5 1 2 2 1.2.2
6 1 2 3 1.2.3
7 1 3 1 1.3.1

Now you can continue with the 8, 9 10, 11...until the 63

bye.

akhil...@gmail.com

unread,
Sep 16, 2014, 1:24:44 PM9/16/14
to
how many klm in 45 mb

Huub van Helvoort

unread,
Oct 28, 2014, 2:52:59 PM10/28/14
to
Hello Akhil,

You wrote:

> how many klm in 45 mb

Your question is very cryptic.
So my answer may not be relevant.

If you mean by 45 mb a VC-3 with badwwidth of 45 Mbit/s
there will fit 21 VC-12 in a VC-3 or 24 VC-11 in a VC-3.

You will find all about KLM numbering in ITU-T recommendation
G.707.

Regards, Huub


--
reply to hhelvooort with 2 'o's
================================================================
0 new messages