Contributions  |
|
Numéro
|
Titre
|
Source
|
AI/Question
|
Date
|
|
[ 1253 ]
|
Input to clause 6.2.4 Authentication and Key Agreement (AKA) of the draft Recommendation Y.NGN IdM Mechanisms
|
Lucent Technologies
|
Q15/13
|
2008-08-27 |
|
[ 1252 ]
|
Proposal for additional text on traffic conditioning
|
Huawei
|
Q4/13
|
2008-08-26 |
|
[ 1251 ]
|
Proposal for additional text in the scope of Y.IPTV-TM
|
Huawei
|
Q4/13
|
2008-08-26 |
|
[ 1250 ]
|
High level requirements of traffic management for the support of IPTV services
|
Huawei
|
Q4/13
|
2008-08-26 |
|
[ 1249 ]
|
Proposal for structural change of Y.IPTV-TM
|
Huawei
|
Q4/13
|
2008-08-26 |
|
[ 1248 ]
|
New sub clause on traffic classification in Y.IPTV-TM
|
Huawei
|
Q4/13
|
2008-08-26 |
|
[ 1247 ]
|
Proposal for new sub clause on management plane mechanisms
|
Huawei
|
Q4/13
|
2008-08-26 |
|
[ 1246 ]
|
Y.NGN-FRA : Proposed text for Annex C (IPTV)
|
France Telecom
|
Q3/13
|
2008-08-26 |
|
[ 1245 ]
|
Y.NGN-FRA : Proposed new clauses in clause 9.3.4 ("Application support functions and service support functions")
|
France Telecom
|
Q3/13
|
2008-08-26 |
|
[ 1244 ]
|
Y.NGN-FRA : Proposed new clause 9.3.3.2 ("Content delivery functional entities")
|
France Telecom
|
Q3/13
|
2008-08-26 |
|
[ 1243 ]
|
Proposed to add the nomadism scenario in Y.RACF (Y.2111)
|
ZTE Corp.
|
Q4/13
|
2008-08-26 |
|
[ 1242 ]
|
Proposed to add the description for resource control scenarios for nomadism
|
ZTE Corp.
|
Q4/13
|
2008-08-26 |
|
[ 1241 ]
|
Proposal for Transport Separation of IP into identifier and locator Execution Function for Y.FAipsplit
|
ZTE Corp.
|
Q3/13
|
2008-08-26 |
|
[ 1240 ]
|
Proposal for the information flow of the Y.FAipsplit
|
ZTE Corp.
|
Q3/13
|
2008-08-26 |
|
[ 1239 ]
|
Proposal for the high level functions of Y.FAipsplit
|
ZTE Corp.
|
Q3/13
|
2008-08-26 |
|
[ 1238 ]
|
Proposal for the architecture model of Y.FAipsplit
|
ZTE Corp.
|
Q3/13
|
2008-08-26 |
|
[ 1237 ]
|
Proposal for new work Item of Y.FAipsplit, " Functional Architecture of ipsplit in NGN "
|
ZTE Corp.
|
Q3/13
|
2008-08-26 |
|
[ 1236 ]
|
Call Centre Service Scenario and Deployment Model over NGN
|
China Telecom, ZTE Corp.
|
Q8/13
|
2008-08-26 |
|
[ 1235 ]
|
Propose Security Considerations in Y.MMCF
|
ZTE Corp.
|
Q15/13, Q3/13
|
2008-08-26 |
|
[ 1234 ]
|
Y.NGN-FRA : Proposed text for clause 7.2.1.2 ("Content delivery functions")
|
France Telecom
|
Q3/13
|
2008-08-26 |
|
[ 1233 ]
|
Changes to Figure 3 of Y.2012
|
France Telecom
|
Q3/13
|
2008-08-26 |
|
[ 1232 ]
|
Functional architecture aspects of IPTV network control - Comments
|
France Telecom
|
Q3/13
|
2008-08-26 |
|
[ 1231 ]
|
Proposal of an IPTV Brokerage Service Scenario
|
Korea (Rep. of)
|
Q8/13
|
2008-08-26 |
|
[ 1230 ]
|
Considerations on Identification Framework for IPTV Services
|
Korea (Rep. of)
|
Q2/13
|
2008-08-26 |
|
[ 1229 ]
|
Proposal for terms and definitions section of Y. IdMFramework [2]
|
NEC Corp.
|
Q15/13
|
2008-08-26 |
|
[ 1228 ]
|
Proposal for terms and definitions section of Y. IdMFramework
|
NEC Corp.
|
Q15/13
|
2008-08-26 |
|
[ 1227 ]
|
Proposed modifications on appendices of Y.mpls-mob
|
ETRI
|
Q2/13
|
2008-08-26 |
|
[ 1226 ]
|
Proposal for adding functional descriptions of communications between RACF and MPM in RACF document
|
KDDI Corp. (KDDI R&D Labs)
|
Q4/13
|
2008-08-26 |
|
[ 1225 ]
|
Modifications on inter-operator communications (clause 10) in Y.RACF rev. 1
|
KDDI Corp.
|
Q4/13
|
2008-08-26 |
|
[ 1224 ]
|
Basic signalling procedures in resource control protocol no.7 (Ri interface) ver. 1
|
KDDI Corp.
|
Q5/11
|
2008-08-26 |
|
[ 1223 ]
|
Revised draft ITU-T Recommendation Q.3307.1 ? Resource control protocol no.7 (rcp7 )- Protocol at the interface between inter-domain Policy Decision Physical Entities (PD-PEs) (Ri interface)
|
KDDI Corp.
|
Q5/11
|
2008-08-26 |
|
[ 1222 ]
|
Consideration of topology hiding at Ri reference point
|
KDDI Corp.
|
Q5/11
|
2008-08-26 |
|
[ 1221 ]
|
Proposal for a new draft recommendation Y.IPTVBrokeringScenario ?3rd Party IPTV Service Brokering Scenarios?
|
ETRI
|
Q8/13
|
2008-08-26 |
|
[ 1220 ]
|
Proposal of changing the texts on draft Recommendation Y.cwbs
|
ETRI
|
Q8/13
|
2008-08-26 |
|
[ 1219 ]
|
Proposal for update texts of requirements in clause 6 on Y.cwbs
|
ETRI
|
Q8/13
|
2008-08-26 |
|
[ 1218 ]
|
Proposal for revised texts of service scenario in clause 8 on Y.cwbs
|
ETRI
|
Q8/13
|
2008-08-26 |
|
[ 1217 ]
|
Request for review of draft Rec.Y.mpls-mob ?MPLS-based mobility capabilities for NGN Services?
|
ETRI
|
Q3/13
|
2008-08-26 |
|
[ 1216 ]
|
Proposal for editorial enhancements of Y.mpls-mob
|
ETRI
|
Q2/13
|
2008-08-26 |
|
[ 1215 ]
|
Comments on terminologies in Y.mpls-mob
|
ETRI
|
Q2/13
|
2008-08-26 |
|
[ 1214 ]
|
Propose to update section of convergence level in Q.FMC-IMS
|
China Mobile
|
Q6/13, Q5/19
|
2008-08-26 |
|
[ 1213 ]
|
Propose to modify the Annex B of Q.FMC-IMS
|
China Mobile
|
Q6/13, Q5/19
|
2008-08-26 |
|
[ 1212 ]
|
Proposal to modify the security procedures of clause 7.1 of draft Y.MMCF
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1211 ]
|
Proposal to modify clause 6.2.4 of draft Rec. Y.MMCF
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1210 ]
|
Proposal for split mode for further study
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1209 ]
|
Proposal for Information Flows for network exit
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1208 ]
|
Proposal for information flow for handover
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1207 ]
|
Proposal for clarification of functionality description of MLMF
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1206 ]
|
Proposal for clarification on functionality of HCF ,HEF and L2HF
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1205 ]
|
Overview of mobility handover procedures
|
China Mobile, Huawei
|
Q3/13
|
2008-08-26 |
|
[ 1204 ]
|
Withdrawn by the author
|
China Mobile
|
Q6/13, Q5/19
|
2008-08-26 |
Resultats:1303 documents
Résultats :
Précédent -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8 -
9 -
10 -
11 -
12 -
13 -
14 -
15 -
16 -
17 -
18 -
19 -
20 -
21 -
22 -
23 -
24 -
25 -
26 -
27
- Suivant
|
Téléchargement de multiples documents: Formats et langues à prendre en compte (si disponibles):
