Contributions  |
|
Numéro
|
Titre
|
Source
|
AI/Question
|
Date
|
|
[ 903 ]
|
A new implementation Architecture for controlling MPLS network
|
ZTE Corporation
|
Q4/13
|
2008-05-04 |
|
[ 902 ]
|
Add the Requirement of Charging Policy Decision
|
ZTE Corporation
,
China Mobile
|
Q4/13
|
2008-05-04 |
|
[ 901 ]
|
Add Charging Trigger Function to the PE-FE
|
ZTE Corporation
|
Q4/13
|
2008-05-04 |
|
[ 900 ]
|
Add Charging Policy Decision Function to the PD-FE
|
ZTE Corporation
,
China Mobile
|
Q4/13
|
2008-05-05 |
|
[ 899 ]
|
Add charging correlation information components to the Rw
|
ZTE Corporation
|
Q4/13
|
2008-05-04 |
|
[ 898 ]
|
Signalling requirement for UE on Gateway Model CRT to the draft of Q.CRBT_CRT
|
ZTE Corporation
|
Q2/11
|
2008-05-04 |
|
[ 897 ]
|
Signalling requirement for UE on Gateway Model CRBT to the draft of Q.CRBT_CRT
|
ZTE Corporation
|
Q2/11
|
2008-05-04 |
|
[ 896 ]
|
Signalling requirement for AS on Gateway Model CRT to the draft of Q.CRBT_CRT
|
ZTE Corporation
|
Q2/11
|
2008-05-04 |
|
[ 895 ]
|
Signalling requirement for AS on Gateway Model CRBT to the draft of Q.CRBT_CRT
|
ZTE Corporation
|
Q2/11
|
2008-05-04 |
|
[ 894 ]
|
Service flows for gateway model CRT to the draft of Q.CRBT_CRT
|
ZTE Corporation
|
Q2/11
|
2008-05-04 |
|
[ 893 ]
|
Service flows for gateway model CRBT to the draft of Q.CRBT_CRT
|
ZTE Corporation
|
Q2/11
|
2008-05-04 |
|
[ 892 ]
|
Proposal to add acceptable QoS information to Rs interface (Q.3321.1)
|
ZTE Corporation
|
Q5/11
|
2008-05-04 |
|
[ 891 ]
|
Proposal to add acceptable QoS information to Ri interface (Q.3307.1)
|
ZTE Corporation
|
Q5/11
|
2008-05-04 |
|
[ 890 ]
|
CRBT service interaction with other networks to the draft of Q.CRBT_CRT
|
ZTE Corporation, Huawei Technologies Co.,Ltd.
|
Q2/11
|
2008-05-04 |
|
[ 889 ]
|
Proposals to add procedures for use of new added AVP on Rs interface
|
P.R. China
|
Q5/11
|
2008-05-04 |
|
[ 888 ]
|
Proposal for adding Service Routing function into Y.ngn-openenv
|
CATR,MII P.R. China
|
Q2/13
|
2008-05-04 |
|
[ 887 ]
|
Proposal for grouping the functions in Y.ngn-openenv
|
CATR,MII P.R. China
|
Q2/13
|
2008-05-04 |
|
[ 886 ]
|
Introduction of Signalling Agent function to the section 6.1"General concepts" in Y.MCFArch
|
CATR,MII P.R. China
|
Q3/13
|
2008-05-04 |
|
[ 885 ]
|
Proposed refinement text for clause 10 "Forwarding" in Y.FPBN-addr
|
CATR,MII P.R. China
|
Q13/13
|
2008-05-04 |
|
[ 884 ]
|
Proposal on the content of the clause 9 "Routing" in Y.FPBN-addr
|
CATR,MII P.R. China
|
Q13/13
|
2008-05-04 |
|
[ 883 ]
|
Proposal on the content of the clause 8 "Mapping and Translation" in Y.FPBN-addr
|
CATR,MII P.R. China
|
Q13/13
|
2008-05-04 |
|
[ 882 ]
|
Proposal on new text of the clause 7.3 "Addressing Objects" in Y.FPBN-addr
|
CATR,MII P.R. China
|
Q13/13
|
2008-05-04 |
|
[ 881 ]
|
Proposal on the content of the clause6 "Introduction" in Y.FPBN-addr
|
CATR,MII P.R.China
|
Q13/13
|
2008-05-05 |
|
[ 880 ]
|
Proposal for Interoperability within an NGN network
|
Ministry of Communications & IT, INDIA
|
Q3/13, Q1/13
|
2008-05-04 |
|
[ 879 ]
|
Device Profile for Profile Management on Y.USN-reqts
|
KT
|
Q2/13
|
2008-05-04 |
|
[ 878 ]
|
Proposed revision of draft Recommendation Y.USN-reqts, "Requirements for support of USN applications and services in NGN environment"
|
ETRI
,
KT
|
Q2/13
|
2008-05-04 |
|
[ 877 ]
|
Proposed Texts for the Functional information flows of Q.LMF
|
Korea
,
ETRI
|
Q6/13, Q2/19
|
2008-05-04 |
|
[ 876 ]
|
Subject confirmation methods of the SAML tokens
|
Lucent Technologies
|
Q15/13
|
2008-05-04 |
|
[ 875 ]
|
Use of the SAML assertions for exchange of the identity and security information in the SOAP messages (contributions towards development of Y.IdM Mechanisms)
|
Lucent Technologies
|
Q15/13
|
2008-05-05 |
|
[ 874 ]
|
Draft outline of the draft Recommendation Identity Management Mechanisms
|
Lucent Technologies
|
Q15/13
|
2008-05-04 |
|
[ 873 ]
|
Generic Bootstrapping Architecture in IdM
|
Lucent Technologies
|
Q15/13
|
2008-05-04 |
|
[ 872 ]
|
Proposed Changes to Y.RACF-DistribMPLS
|
AT&T
,
Verizon
|
Q4/13
|
2008-05-04 |
|
[ 871 ]
|
Proposed Changes to Y.RACF-DistribMPLS on BG-FE and PD-FE
|
ZTE
,
AT&T
|
Q4/13
|
2008-05-04 |
|
[ 870 ]
|
Proposed Changes to Appendices in Q.LMF
|
ETRI
|
Q6/13, Q2/19
|
2008-05-04 |
|
[ 869 ]
|
Functional Information Flow of Location Management Function
|
ETRI
|
Q6/13, Q2/19
|
2008-05-04 |
|
[ 868 ]
|
Functional Architecture of Location Management Function
|
ETRI
|
Q6/13, Q2/19
|
2008-05-04 |
|
[ 867 ]
|
Description on High Level Functions in Location Management Function
|
ETRI
|
Q6/13, Q2/19
|
2008-05-04 |
|
[ 866 ]
|
Clarification of Location Management Function in Q.LMF
|
ETRI
|
Q6/13, Q2/19
|
2008-05-04 |
|
[ 865 ]
|
Reference Points with Mobility Location Management in Y.MCFArch
|
ETRI
|
Q3/13
|
2008-05-04 |
|
[ 864 ]
|
Initial attachment procedure for Y.MCFArch
|
ETRI
|
Q3/13
|
2008-05-04 |
|
[ 863 ]
|
Mobility Extension for Y.NACF R2
|
ETRI
|
Q3/13
|
2008-05-04 |
|
[ 862 ]
|
Separation of High Level Functions from Functional Entities in Y.MCFArch
|
ETRI
|
Q3/13
|
2008-05-04 |
|
[ 861 ]
|
Architecture Reference Model for Y.MCFArch
|
ETRI
|
Q3/13
|
2008-05-04 |
|
[ 860 ]
|
Proposal for addition of a new USN use case in Y.USN-reqts
|
KT
|
Q2/13
|
2008-05-04 |
|
[ 859 ]
|
Proposal for addition of some NGN capabilities for USN applications and Services in Y.USN-reqts
|
KT
|
Q2/13
|
2008-05-04 |
|
[ 858 ]
|
Proposed Signalling flows for CRT service in Annex C of Q.CRBT_CRT
|
KT
|
Q3/11, Q2/11
|
2008-05-04 |
|
[ 857 ]
|
Proposed Signalling flows for CRBT service in Annex C of Q.CRBT_CRT
|
KT
|
Q3/11, Q2/11
|
2008-05-04 |
|
[ 856 ]
|
Proposed texts for Section 7.4 in CRT service
|
KT
|
Q3/11, Q2/11
|
2008-05-04 |
|
[ 855 ]
|
Proposed texts for Section 6.4 in CRBT service
|
KT
|
Q3/11, Q2/11
|
2008-05-04 |
|
[ 854 ]
|
Proposed Section 6.2.3 CRBT service flows on HTTP model
|
KT
|
Q3/11, Q2/11
|
2008-05-04 |
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):
