Contribuciones
[ AI/Cuestión: Q11/15 ]  |
|
Número
|
Título
|
Origen
|
AI/Cuestión
|
Fecha
|
|
[ 257 ]
|
Proposed change in Draft Annex to G.709 for transcoding via 512B/513B
|
NTT
|
Q11/15
|
2008-11-21 |
|
[ 250 ]
|
Proposed text for ODU3ye/OTU3ye in supplement
|
Japan
|
Q11/15
|
2008-11-21 |
|
[ 249 ]
|
Corrigendum for G.709 correcting small mistake and inconsistency with G.798
|
Alcatel Lucent Germany
|
Q9/15, Q11/15
|
2008-11-21 |
|
[ 245 ]
|
Consideration of OTU4 FEC requirements
|
Alcatel Lucent
|
Q11/15
|
2008-11-21 |
|
[ 244 ]
|
Proposal for adding timing transparency to GFP (G.7041) mapping and its variant as given in G.Sup43 Clause 7.3 for 10GBase-R
|
Alcatel - Lucent Germany
|
Q11/15
|
2008-11-21 |
|
[ 243 ]
|
Considerations about Implementation friendly justification procressing of mapping of data into ODU4
|
Alcatel - Lucent Germany
|
Q11/15
|
2008-11-21 |
|
[ 221 ]
|
Proposal on ODU3y supporting a mix of LO ODU signal types
|
China Telecom, CATR, MII China
|
Q11/15
|
2008-11-21 |
|
[ 220 ]
|
Amendment 2 to Recommendation X.85/Y.1321 on the assignment of a set new SAPI value
|
MII, China
|
Q11/15
|
2008-11-21 |
|
[ 219 ]
|
Adding OH bytes in OCh and OMS in order to make physical parameter monitoring (G.709)
|
MII, China
|
Q11/15
|
2008-11-21 |
|
[ 213 ]
|
Proposal on carrying multiple services on ODU3y
|
China Mobile, China Telecom, China Unicom, BUPT
|
Q11/15
|
2008-11-21 |
|
[ 187 ]
|
Evolution of OTN Hierarchy
|
Ericsson
|
Q11/15
|
2008-11-21 |
|
[ 181 ]
|
Rationale for using asynchronous mapping ODU0 into ODU1, ODU2, ODU3
|
Alcatel-Lucent
|
Q11/15
|
2008-11-21 |
|
[ 160 ]
|
Telecom Italia requirements for Next Generation Transport Network
|
Telecom Italia
|
Q11/15
|
2008-11-21 |
|
[ 146 ]
|
Analysis of TTT+GMP vs GFP-T as 1GE into OPU0 mapping method
|
Huawei Technologies Co., Ltd.
|
Q11/15
|
2008-11-20 |
|
[ 138 ]
|
ODU3ye/OTU3ye supplement supporting only 4 x ODU2e
|
NTT
|
Q11/15
|
2008-11-20 |
|
[ 137 ]
|
Bit rate of OTU3ye in G.supODU3ye
|
NTT
|
Q11/15
|
2008-11-20 |
|
[ 125 ]
|
Proposed re-structure G.sup43 for 4xODU2e/ODU3y
|
Fujitsu
|
Q11/15
|
2008-11-20 |
|
[ 124 ]
|
Proposed work plan and comments on G.709v2 draft
|
Fujitsu
|
Q11/15
|
2008-11-20 |
|
[ 123 ]
|
Consideration on interoperability of OTN and proposed multiplexing and mapping structure for G.709
|
Fujitsu
|
Q11/15
|
2008-11-20 |
|
[ 122 ]
|
Documentation of H-ODU3y and H-ODU2e in a Supplement
|
Deutsche Telekom
|
Q11/15
|
2008-11-20 |
|
[ 121 ]
|
H-ODU4 structure and ODUk VCAT versus flexible L-ODUs
|
Deutsche Telekom
|
Q11/15
|
2008-11-20 |
|
[ 120 ]
|
Illustration of the multiplex hierarchy in Recommendation G.709
|
Deutsche Telekom
|
Q11/15
|
2008-11-20 |
|
[ 118 ]
|
Proposed standardisation plan for G.709 extensions
|
Deutsche Telekom
|
Q11/15
|
2008-11-20 |
|
[ 117 ]
|
Proposed new Recommendation for Ethernet CBR over OTN
|
Deutsche Telekom
|
Q11/15
|
2008-11-20 |
|
[ 116 ]
|
Enhanced OTN Mapping
|
Cortina Systems, Ciena Corporation, Cisco Systems
|
Q11/15
|
2008-11-20 |
|
[ 112 ]
|
Structure for Evolution of G.709
|
United States
|
Q11/15
|
2008-11-20 |
|
[ 110 ]
|
Standardization of G.709 Bit Rate Compliant Transparent Transport of 10GBase-R Clients in G.7041 and G.709
|
AT&T, Lucent, Ciena, PMC-Sierra
|
Q11/15
|
2008-11-20 |
|
[ 107 ]
|
Proposals to extend G.709
|
Huawei Technologies Co., Ltd.
|
Q11/15
|
2008-11-20 |
|
[ 103 ]
|
Correction to OPUk-16v frame structure in G.709
|
Korea (Republic of)
|
Q11/15
|
2008-11-20 |
|
[ 95 ]
|
OPUk GMP proposal
|
Huawei Technologies Co., Ltd.
|
Q11/15
|
2008-11-20 |
|
[ 78 ]
|
Proposed definition of ODU3e
|
Tellabs Oy
|
Q11/15
|
2008-11-19 |
|
[ 75 ]
|
STM-16 Jitter and Wander Accumulation over OTN Cross-Connect Network Elements
|
Huawei Technologies Co., Ltd.
|
Q13/15, Q11/15
|
2008-11-19 |
|
[ 74 ]
|
Initial Results for Ethernet Client Jitter and Wander Accumulation over OTN Islands
|
Huawei Technologies Co., Ltd.
|
Q13/15, Q11/15
|
2008-11-19 |
|
[ 73 ]
|
Initial Results for High-Definition Serial Digital Interface Video Client Jitter Accumulation over OTN Islands
|
Huawei Technologies Co., Ltd.
|
Q13/15, Q11/15
|
2008-11-19 |
|
[ 72 ]
|
ODUk VCAT/AMP or ODUf/GMP
|
Huawei Technologies Co., Ltd.
|
Q11/15
|
2008-11-19 |
|
[ 71 ]
|
From SDH centric, line and ring WDM based to multi-service, multi-domain OTN evolution
|
Huawei Technologies Co., Ltd.
|
Q11/15
|
2008-11-19 |
|
[ 69 ]
|
Timing Domains and Timing-Related Processes in an OTN Network Element
|
Huawei Technologies Co., Ltd.
|
Q13/15, Q11/15
|
2008-11-19 |
|
[ 65 ]
|
ODU3y specification proposal
|
Huawei, CMCC
|
Q11/15
|
2008-11-19 |
|
[ 52 ]
|
Proposed Annex/Appendix for G.709 to specify mapping for 64B/66B encoded clients
|
Lucent Technologies
|
Q11/15
|
2008-11-18 |
|
[ 51 ]
|
Mapping of ODU2e into OPU3
|
Lucent Technologies, PMC-Sierra
|
Q11/15
|
2008-11-18 |
|
[ 38 ]
|
Considerations of an OTN hierarchy based on LO/HO principles of Rec. G.872
|
Ciena Corporation
|
Q12/15, Q11/15
|
2008-11-18 |
|
[ 36 ]
|
Recommended approach for capturing Ethernet mappings into G.709 supplements
|
PMC-Sierra, Verizon
|
Q11/15
|
2008-11-18 |
|
[ 35 ]
|
Mapping/Multiplexing LO-ODUs into HO-ODUs
|
PMC-Sierra
|
Q11/15
|
2008-11-18 |
|
[ 34 ]
|
Proposed ODU0 structure and multiplexing
|
PMC-Sierra, Lucent Technologies, AT&T & Ciena Corp
|
Q11/15
|
2008-11-19 |
|
[ 33 ]
|
Proposed Gbit/s Ethernet mapping into ODU0 structure and mappings
|
PMC-Sierra
|
Q11/15
|
2008-11-18 |
|
[ 32 ]
|
Proposed count byte definition for the Generic Mapping Procedure (GMP)
|
PMC-Sierra
|
Q11/15
|
2008-11-18 |
|
[ 16 ]
|
Simplification of the OTN hierarchy
|
Nortel Networks (Canada)
|
Q9/15, Q14/15, Q13/15, Q12/15, Q11/15
|
2008-11-17 |
|
[ 14 ]
|
10GE LAN interface for OTN
|
Nortel Networks (Canada)
|
Q9/15, Q13/15, Q12/15, Q11/15
|
2008-11-17 |
|
[ 13 ]
|
Impact of adding ODU2e and ODU3y to the OTN hierarchy
|
Nortel Networks (Canada)
|
Q9/15, Q12/15, Q11/15
|
2008-11-17 |
|
[ 12 ]
|
Evolution of the OTN
|
Nortel Networks (Canada)
|
Q9/15, Q14/15, Q13/15, Q12/15, Q11/15
|
2008-11-17 |
Resultados :200 documentos
Resultados :
Anterior -
1 -
2 -
3 -
4
|
Telecarga de múltiples documentos: Formatos e idiomas que hay que tener en cuenta (si están disponibles):
