Contributions Tardives |
|
Numéro
|
Titre
|
Source
|
AI/Question
|
Date
|
|
[ 468 ]
|
Gap Analysis about "Framework of IPv6 Multi-homing for NGN" between ITU-T and other SDOs
|
ETRI
|
Q9/13
|
2006-01-05 |
|
[ 467 ]
|
Considerations for IPv6 Multi-homing in NGN Environments
|
ETRI
|
Q9/13
|
2006-01-05 |
|
[ 466 ]
|
Enhancement of Living List #2 of Q.3/13 (NGN Architecture Framework for Streaming Services)
|
ETRI
|
Q3/13
|
2006-01-05 |
|
[ 465 ]
|
Authoritative Directory Interoperability FAQ
|
VeriSign, Inc.
|
Q2/13
|
2006-01-05 |
|
[ 464 ]
|
A proposal to initiate the study of FMC service scenario by using PSTN as the fixed access network for UMTS network
|
China Telecom
|
Q6/13
|
2006-01-05 |
|
[ 463 ]
|
Proposal for the study on SIP based Real-time Conversational Voice Services
|
China Telecom
|
Q8/13, Q2/13
|
2006-01-05 |
|
[ 462 ]
|
Some proposals to UPT Service Scenarios over NGN
|
China Telecom
|
Q8/13, Q6/13, Q2/13
|
2006-01-05 |
|
[ 461 ]
|
Proposal for the study on Organization of NGN transport user profile data
|
China Telecom
|
Q3/13
|
2006-01-05 |
|
[ 460 ]
|
Proposal for the study on Organization of NGN service user profile data
|
China Telecom
|
Q3/13
|
2006-01-05 |
|
[ 459 ]
|
Proposal for adding FMC service requirements in "Y.FCM Req"
|
China Telecom
|
Q6/13
|
2006-01-05 |
|
[ 458 ]
|
Proposal for adding basic call control scenario in call server based PES
|
China Telecom
|
Q7/13
|
2006-01-05 |
|
[ 457 ]
|
Proposed changes for the mapping of functional entities to network elements
|
China Telecom
|
Q7/13
|
2006-01-05 |
|
[ 456 ]
|
A proposal for revising the definition of Call Server
|
China Telecom
|
Q7/13
|
2006-01-05 |
|
[ 455 ]
|
Proposed Text for Ub Reference Point in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 454 ]
|
Proposed Modification for Rq' Reference Point in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 453 ]
|
Proposed Modification for Go' Reference Point in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 452 ]
|
Proposed Clarification and Modification for ANF and ENF in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 451 ]
|
Initial draft Recommendation on NGN service requirements for ID-based applications (Y.idservreqs)
|
ETRI
|
Q2/13
|
2006-01-05 |
|
[ 450 ]
|
Initial draft Recommendation on functional requirements and architecture of the NGN for ID-based applications and services (Y.idarch)
|
ETRI
|
Q3/13
|
2006-01-05 |
|
[ 449 ]
|
Revised initial draft Recommendation Y.mpserv - "Multi-play service scenario deployment model"
|
Telekomunikacja Polska (Poland)
|
Q8/13, Q2/13
|
2006-01-05 |
|
[ 448 ]
|
Proposal to request SG 11 to begin work on signalling aspects of flow aware technology for the timely support of emerging requirements
|
BT Group
|
Q4/13, Q3/13
|
2006-01-05 |
|
[ 447 ]
|
IP QoS Signaling Concepts and Requirements for Flow Aware Services
|
BT Group
|
Q4/13, Q3/13
|
2006-01-05 |
|
[ 446 ]
|
Editorial proposal on TR-RACF
|
Fujitsu
|
Q4/13
|
2006-01-05 |
|
[ 445 ]
|
Proposal of updating Y.1711 for Transport MPLS
|
Fujitsu
|
Q5/13
|
2006-01-05 |
|
[ 444 ]
|
Modifications to Security Requirements for NGN Release 1
|
France Telecom
|
Q15/13
|
2006-01-05 |
|
[ 443 ]
|
Principles for NGN security architecture design
|
France Telecom
|
Q15/13
|
2006-01-05 |
|
[ 442 ]
|
NAPT control and NAT traversal description enhancement of TR-RACF
|
Oki Electric Industry Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 441 ]
|
Clarification of TR-RACF open issues for release 1
|
OKI Electric Industry Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 440 ]
|
Resource reservation and modification request at Rq' in TR-RACF
|
OKI
|
Q4/13
|
2006-01-05 |
|
[ 439 ]
|
Proposed modification of the unified document structure of service scenarios and deployment models
|
OKI
|
Q8/13
|
2006-01-05 |
|
[ 438 ]
|
Editorial Proposals for TR-RACF open issues
|
OKI
|
Q4/13
|
2006-01-05 |
|
[ 437 ]
|
RACF Functional Architecture
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 436 ]
|
RACF architecture - Re reference point
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 435 ]
|
RACF and Signalling protocols
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 434 ]
|
Terminology in TR-RACF and FRA
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 433 ]
|
Use of Mobile IPv6 in NGN environment
|
Huawei Technologies Co., Ltd.
|
Q9/13
|
2006-01-05 |
|
[ 432 ]
|
Updated proposal for Ranged Allocation Example in G.FEPO
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 431 ]
|
Resource modification procedure in TR-123.qos
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 430 ]
|
Proposed revisions to TR-123.qos
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 429 ]
|
Proposed Modification for Rq Reference Point in RACF
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 428 ]
|
Proposed Modification for Rp Reference Point in RACF
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 427 ]
|
Propose new function of CS-based PSTN/ISDN Emulation Component
|
Huawei Technologies Co., Ltd.
|
Q7/13
|
2006-01-05 |
|
[ 426 ]
|
Proposals for MPLS based Network QoS negotiation procedures
|
Huawei Technologies Co., Ltd.
|
Q2/13
|
2006-01-05 |
|
[ 425 ]
|
Proposals for MPLS based Network Fast Handover mechanism
|
Huawei Technologies Co., Ltd.
|
Q2/13
|
2006-01-04 |
|
[ 424 ]
|
Proposals for harmonizing the style of definitions for hose and pipe
|
Huawei Technologies Co., Ltd.
|
Q2/13
|
2006-01-04 |
|
[ 423 ]
|
Proposal of addition of network adapter to "Draft FGNGN-CSF Version 2" document
|
Huawei Technologies Co., Ltd.
|
Q8/13
|
2006-01-05 |
|
[ 422 ]
|
Proposal for section 7.2.4 of Y.csem
|
Huawei Technologies Co., Ltd.
|
Q7/13
|
2006-01-05 |
|
[ 421 ]
|
Proposal for Sections 7.2.2 & 7.2.4 in Y.NGN-PIEA
|
Huawei Technologies Co., Ltd.
|
Q3/13
|
2006-01-05 |
|
[ 420 ]
|
Proposal for point to multi-points performance metrics
|
Huawei Technologies Co., Ltd.
|
Q5/13
|
2006-01-05 |
|
[ 419 ]
|
Proposal for Objectives of FMC Y.FMC_Req
|
MII, China
|
Q6/13
|
2006-01-05 |
Resultats:263 documents Résultats :
Précédent -
1 -
2 -
3 -
4 -
5 -
6
- Suivant
|
Téléchargement de multiples documents: Formats et langues à prendre en compte (si disponibles):