Documentos Temporales
(GEN)
[ Origen: ITU-T Study Group 2 ]  |
|
Número
|
Título
|
Origen
|
AI/Cuestión
|
Fecha
|
|
[ 63-GEN ]
|
LS/i/r on work program of ITU-T SG21 on metaverse based on FG-MV deliverables (TSAG-LS46) [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q6/17
|
2025-02-21 |
|
[ 62-GEN ]
|
LS/i on revised text of Question 9/21 on metaverse [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q6/17
|
2025-02-21 |
|
[ 61-GEN ]
|
LS/i/r on the definitions for term smartphone from ITU-T Study Group 17 (SCV-LS8) [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q7/17, Q1/17
|
2025-02-21 |
|
[ 60-GEN ]
|
LS/i/r on Coordination for Identity Management (SG17-LS139) [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q10/17
|
2025-02-21 |
|
[ 59-GEN ]
|
LS/i on initiation of new work item on the draft ITU-T F. CV-FARSI "Functional Architecture and Requirements of connected vehicles supporting satellite internet services" [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q13/17
|
2025-02-21 |
|
[ 58-GEN ]
|
LS/i/r on the progress of the Correspondence Group on AI Security (CG-AISEC) (SG17-LS138) [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q7/17
|
2025-02-21 |
|
[ 57-GEN ]
|
LS/i on new work item ITU-T F.DMMS-Reqs "Functional requirements for data matrix for multimedia services" [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q7/17
|
2025-02-21 |
|
[ 56-GEN ]
|
LS/i on the creation of a new work item F.MDA-RSM "Requirements for sharing management of multimedia data asset" [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q7/17, Q14/17
|
2025-02-21 |
|
[ 55-GEN ]
|
LS/i on initiation of new work item ITU-T H.VADS "Assessment criteria for video authenticity detection services" [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q7/17
|
2025-02-21 |
|
[ 54-GEN ]
|
LS/i on new work item ITU-T F.AICP-IO "Technical specification for artificial intelligence cloud platform - Inference optimization" [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q8/17
|
2025-02-21 |
|
[ 53-GEN ]
|
LS/i on new work item ITU-T F.AICP-HA "Technical specification for artificial intelligence cloud platform - high availability requirements" [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q8/17
|
2025-02-21 |
|
[ 52-GEN ]
|
LS/i on current status of Q5/21 [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q7/17
|
2025-02-21 |
|
[ 51-GEN ]
|
LS/i on security of medical equipment [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q1/17
|
2025-02-21 |
|
[ 50-GEN ]
|
LS/i/r on terms contained in ITU-T SG21 draft Recommendations (reply SCV-LS37) [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q1/17
|
2025-02-21 |
|
[ 49-GEN ]
|
LS/i/r on Invitation to provide inputs to the "Glossary of terms and definitions for machine learning" (JCA-ML-LS10) [from ITU-T SG21]
|
ITU-T Study Group 21
|
Q7/17
|
2025-02-21 |
|
[ 48-GEN ]
|
LS/i on SCV activity in SG2 [from ITU-T SG2]
|
ITU-T Study Group 2
|
Q1/17
|
2025-02-20 |
|
[ 47-GEN ]
|
LS/i/r on definition developed in SG17 (reply to SCV-LS34) [from ITU-T SG2]
|
ITU-T Study Group 2
|
Q1/17
|
2025-02-20 |
|
[ 46-GEN ]
|
LS/i on Provision of handset-derived caller location information for emergency communications [from ITU-T SG2]
|
ITU-T Study Group 2
|
Q11/17
|
2025-02-20 |
|
[ 45-GEN ]
|
LS/i/r on Coordination for Identity Management (reply to SG17-LS139) [from ITU-T SG2]
|
ITU-T Study Group 2
|
Q10/17
|
2025-02-20 |
|
[ 44-GEN ]
|
LS/i/r on the resolution of AAP comments (reply to TSAG-LS44) [from ITU-T SG2]
|
ITU-T Study Group 2
|
Q1/17
|
2025-02-20 |
|
[ 43-GEN ]
|
LS/i on the consent of Recommendation ITU-T M.3411 (ex. M.uiamr), "User identity and access management requirements for telecommunications management network" [from ITU-T SG2]
|
ITU-T Study Group 2
|
Q11/17, Q10/17
|
2025-02-20 |
|
[ 38-GEN ]
|
LS/i/r on distributed ledger technology security (reply to SG17-LS163) [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q14/17
|
2025-02-10 |
|
[ 37-GEN ]
|
LS/i/r on SG17 progress on IoT security (reply to SG17-LS150) [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17
|
2025-02-10 |
|
[ 36-GEN ]
|
LS/i on initiation of new work item on draft Recommendation ITU-T Y.DIoT-data-space "The architecture of blockchain based distributed infrastructure for trusted data space" [ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17, Q14/17
|
2025-02-04 |
|
[ 35-GEN ]
|
LS/i on the agreement of the Supplement ITU-T Y.Suppl.88 (ex Y.Sup-IoT-BC) "Applicability cases of blockchain in the IoT") [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17
|
2025-02-04 |
|
[ 34-GEN ]
|
LS/i/r on Coordination for Identity Management (reply to SG17-LS139) [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17, Q10/17
|
2025-02-04 |
|
[ 33-GEN ]
|
LS/i on Draft Terms of Reference of the Joint Coordination Activities on metaverse standardization [from ITU-T SGs 20 & 21]
|
ITU-T Study Group 20 and ITU-T Study Group 21
|
Q6/17
|
2025-02-03 |
|
[ 32-GEN ]
|
LS/i on Revised Title and Terms of Reference of JCA-IoT and SC&C [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17
|
2025-02-03 |
|
[ 31-GEN ]
|
LS/i on initiation of new work item on draft Recommendation ITU-T Y.DIoT-req-cap, "General requirements and capability framework of decentralized/distributed Internet of things" [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17, Q14/17
|
2025-02-03 |
|
[ 30-GEN ]
|
LS/i on the consent of the draft Recommendation ITU-T Y.4608 (ex Y.IoT-BoT-peer) "Capability and functional architecture of blockchain of things peers" [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q14/17
|
2025-02-03 |
|
[ 29-GEN ]
|
LS/i on the initiation of two new work items related to identity for metaverse [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17, Q11/17, Q10/17
|
2025-02-03 |
|
[ 28-GEN ]
|
LS/i on Joint Correspondence group on Trust (CG-Trust) [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q1/17
|
2025-02-03 |
|
[ 27-GEN ]
|
LS/i on the establishment of a new Question under ITU-T Study Group 20 [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17
|
2025-02-03 |
|
[ 26-GEN ]
|
LS/i on Joint Correspondence Group on Internet of Things Security (CG-IoTSec) [from ITU-T SG20]
|
ITU-T Study Group 20
|
Q6/17
|
2025-02-03 |
Resultados :34 documentos
|
Telecarga de múltiples documentos: Formatos e idiomas que hay que tener en cuenta (si están disponibles):
