Contribuciones |
|
Número
|
Título
|
Origen
|
AI/Cuestión
|
Fecha
|
|
[ 851 ]
|
Proposed text for ITU-T Y.3501 Edition 2
|
Orange
,
ORANGE POLSKA S.A.
|
Q17/13
|
2015-04-07 |
|
[ 850 ]
(Rev.1-2) |
Establishing liaisons with open source SDN related initiatives
|
Orange
,
Orange Polska S.A.
|
Q14/13
|
2015-04-07 |
|
[ 849 ]
(Rev.1) |
Proposed introduction text for Y.AMC
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q14/13
|
2015-04-07 |
|
[ 848 ]
|
Proposed functional requirements for resource layer (Y.SDN-REQ)
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q14/13
|
2015-04-07 |
|
[ 847 ]
|
Proposed functional requirements for control layer (Y.SDN-REQ)
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q14/13
|
2015-04-07 |
|
[ 846 ]
|
Proposed functional components of SDN control layer in Y.SDN-ARCH
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q14/13
|
2015-04-07 |
|
[ 845 ]
|
Proposed text of ITU-T Y.3510 Edition 2
|
Orange
,
Orange Polska S.A.
|
Q18/13
|
2015-04-07 |
|
[ 844 ]
|
Proposed text for network resources and abstraction in Y.SDN-ARCH
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q14/13
|
2015-04-07 |
|
[ 843 ]
|
Revisions of ITU-T Y.3501, Y.3510 and Y.3520
|
Orange
,
ORANGE POLSKA S.A.
|
Q19/13, Q18/13, Q17/13
|
2015-04-07 |
|
[ 842 ]
(Rev.1) |
Proposed revised high-level architecture for Y.AMC
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q14/13
|
2015-04-07 |
|
[ 841 ]
(Rev.1) |
Proposed definition of AMC (Autonomic Management and Control) in Y.AMC
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q14/13
|
2015-04-07 |
|
[ 840 ]
(Rev.1) |
Proposed reference point for Y.VNC
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q6/13
|
2015-04-07 |
|
[ 839 ]
(Rev.1) |
Proposed modification of the reference point Vt for Y.VNC
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q6/13
|
2015-04-07 |
|
[ 838 ]
(Rev.1) |
Proposal for principle on derivation of NaaS functionality in Y.CCNaaS-arch
|
China Unicom
|
Q18/13
|
2015-04-07 |
|
[ 837 ]
|
Identification of a set of requirements for the IoT from Africa
|
Uganda Communications Commission (UCC)
|
Q3/13, Q2/13, Q11/13, Q1/13
|
2015-04-07 |
|
[ 836 ]
(Rev.1) |
Proposed modification of the high-level architecture for Y.VNC
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q6/13
|
2015-04-07 |
|
[ 835 ]
(Rev.1) |
Proposal for analysis and description of functionality for interworking of different connectivity solutions in Y.CCNaaS-arch
|
China Unicom
|
Q18/13
|
2015-04-07 |
|
[ 834 ]
(Rev.1-2) |
Proposed architecture for middle-box management in draft recommendation Y.SDN-arch
|
SK Telecom
|
Q14/13
|
2015-04-07 |
|
[ 833 ]
(Rev.1) |
Proposal for DevOps description in Y.CCNaaS-arch
|
China Unicom
|
Q18/13
|
2015-04-07 |
|
[ 832 ]
(Rev.1) |
Propose to launch IMT-2020 network standardization work in the form of GSI.
|
China Mobile Communications Corporation
,
China Telecommunications Corporation
|
QALL/13
|
2015-04-07 |
|
[ 831 ]
(Rev.1) |
Proposal for cloud computing impacts on end-to-end management in Y.e2ecm/M.occm
|
China Unicom
|
Q19/13
|
2015-04-07 |
|
[ 830 ]
(Rev.1) |
Major issues discussion for the combined work item Y.e2ecm/M.occm
|
China Unicom
|
Q19/13
|
2015-04-07 |
|
[ 829 ]
|
Recommendation plan for Smartwork (Y.fsn)
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q1/13
|
2015-04-07 |
|
[ 828 ]
(Rev.1) |
Proposal for initiation of Y.3501 revision
|
China Unicom
|
Q17/13
|
2015-04-07 |
|
[ 827 ]
|
An update of definition VCNE Package to Y. NGNe-VCN-Reqts
|
Nokia Solutions and Networks Gmbh & Co. KG
,
China Mobile
|
Q2/13
|
2015-04-07 |
|
[ 826 ]
|
Proposal for add explanation in Section 6.3.2 in Y.dsncdf
|
China Unicom
|
Q12/13
|
2015-04-07 |
|
[ 825 ]
(Rev.1) |
Proposal to the draft Recommendation Y.trusted-env "The basic principles of a trusted environment in ICT infrastructure"
|
Ministry of Telecom and Mass Communications of the Russian Feder
|
Q16/13
|
2015-04-07 |
|
[ 824 ]
(Rev.1) |
Proposal for initiating a new work item "The use of the Internet of Things for study of global processes of the earth"
|
Ministry of Telecom and Mass Communications of the Russian Feder
|
Q2/13
|
2015-04-07 |
|
[ 823 ]
(Rev.1) |
Proposal to the draft Recommendation Y.I?N-Reqts "Requirements and capabilities for Information Control Networks and related applications"
|
Ministry of Telecom and Mass Communications of the Russian Feder
|
Q2/13
|
2015-04-07 |
|
[ 822 ]
(Rev.1) |
Proposal for Initiating a New Work Item to Study the Voice and Video Call Continuity over LTE, Wi-Fi and 2G/3G
|
China Mobile Communications Corporation
|
Q10/13
|
2015-04-07 |
|
[ 821 ]
(Rev.1) |
Proposal for adding description of the scenarios of Voice and Video Call Continuity over LTE, Wi-Fi and 2G3G
|
China Mobile Communications Corporation
|
Q3/13
|
2015-04-07 |
|
[ 820 ]
|
Propose to initiate a new work item on scenarios and requirements of identity protection service
|
China Unicom
|
Q2/13
|
2015-04-07 |
|
[ 819 ]
(Rev.1) |
Proposal for adding description of the overview of solution of Voice and Video Call Continuity over LTE Wi-Fi and 2G3G
|
China Mobile Communications Corporation
|
Q3/13
|
2015-04-07 |
|
[ 818 ]
(Rev.1) |
Proposal for adding description and procedures of PS to CS SRVCC solution of Voice and Video Call Continuity over LTE Wi-Fi and 2G3G
|
China Mobile Communications Corporation
|
Q3/13
|
2015-04-07 |
|
[ 817 ]
(Rev.1) |
Proposal for adding description and procedures of CS to PS SRVCC solution of Voice and Video Call Continuity over LTE Wi-Fi and 2G3G
|
China Mobile Communications Corporation
|
Q3/13
|
2015-04-07 |
|
[ 816 ]
(Rev.1) |
Propose to update the basic scheme for Freedata service scenarios
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 815 ]
(Rev.1) |
Propose to update identification methods for Freedata service
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 814 ]
(Rev.1) |
Propose to replace 'technical scheme' to 'network functional entities'
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 813 ]
(Rev.1) |
Propose to replace 'APP Provider' to '3rd Party' in Freedata service
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 812 ]
(Rev.1) |
Propose to add the definition of 'basic scheme' in Freedata service scenarios
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 811 ]
(Rev.1) |
Propose to add requirements of functional restrictions for network entities
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 810 ]
(Rev.1) |
Propose to add description of security risks in Freedata service in NGN evolution
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 809 ]
(Rev.1) |
Propose to update the problem statement
|
China Mobile Communications Corporation
|
Q14/13
|
2015-04-07 |
|
[ 808 ]
(Rev.1) |
Propose to update the overview, keywords and scope in VCN requirement
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 807 ]
(Rev.1) |
Propose to update the figure in appendix I of VCN requirement
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 806 ]
|
Update to the reference of Y. NGNe-VCN-Reqts according to the latest status of ETSI NFV ISG
|
Nokia Solutions and Networks Gmbh & Co. KG
,
China Mobile
|
Q2/13
|
2015-04-07 |
|
[ 805 ]
(Rev.1) |
Proposal to revise Q17/13 Description
|
Electronics and Telecommunications Research Institute (ETRI)
,
ORANGE POLSKA S.A.
,
Orange
|
Q17/13
|
2015-04-07 |
|
[ 804 ]
(Rev.1) |
Propose to update the description of VCN system in VCN requirement
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 803 ]
(Rev.1) |
Propose to update the content of VCN requirement
|
China Mobile Communications Corporation
|
Q2/13
|
2015-04-07 |
|
[ 802 ]
(Rev.1) |
Propose to update requirement of SAME
|
China Mobile Communications Corporation
|
Q14/13
|
2015-04-07 |
Resultados :225 documentos Resultados :
Anterior -
1 -
2 -
3 -
4 -
5
- Siguiente
|
Telecarga de múltiples documentos: Formatos e idiomas que hay que tener en cuenta (si están disponibles):