Home

Results 1 - 10 of 1,275,088 for required generating. Search took 5.373 seconds.  
Sort by date/Sort by relevance
 Page 53 - Cloud computing: From paradigm to operation           Basic HTML Version Table of Contents View Full Version Page 53 - Cloud computing: From paradigm to operation P. 53 Framework and requirements for cloud computing 1 Table II.1 – Edition plan of this Recommendation Scope Edition 1 Edition2 Edition3 General requirements for cloud computing O Extended Extended General requirements for IaaS O Extended Extended General requirements for NaaS O Extended Extended General requirements for DaaS O Extended Extended General requirements for PaaS O Extended General requirements for CaaS O Extended General requirements for BDaaS O Extended General requirements for SaaS O General requirements for Inter-cloud O Extended Extended General requirements for end-to-end cloud O Extended Extended resource management General requirements for cloud infrastructure O Extended Extended General requirements for Trusted cloud service O Extended Others general requirements O Security consideration O Extended Extended Use case Generic use cases O Extended Extended IaaS general use case O Extended Extended NaaS general use case O Extended Extended DaaS general use case O Extended Extended PaaS general use case O Extended CaaS general use case O Extended BDaaS use case O Extended SaaS general use case O Inter-cloud general use case O Extended Extended End-to-end cloud resource O Extended Extended management use case Cloud infrastructure use case O Extended Extended Trusted cloud service use case O Extended Other use cases O NOTE – The mark "O" indicates initial requirements and use cases are prepared, "extended" indicates additional requirements and use cases will be provided. 45     48     49     50     51     52     53     54     55     56     57     58          
Language:English
Score: 612249.2 - https://www.itu.int/en/publica...n/files/basic-html/page53.html
Data Source: un
 Page 29 - Cloud computing: From paradigm to operation           Basic HTML Version Table of Contents View Full Version Page 29 - Cloud computing: From paradigm to operation P. 29 Framework and requirements for cloud computing 1 Table of Contents 1 Scope 2 References 3 Definitions 3.1 Terms defined elsewhere 3.2 Terms defined in this Recommendation 4 Abbreviations and acronyms 5 Conventions 6 General requirements for cloud computing 7 General requirements for IaaS 8 General requirements for NaaS 9 General requirements for DaaS 10 General requirements for PaaS 11 General requirements for CaaS 12 General requirements for BDaaS 13 General requirements for inter-cloud computing 14 General requirements for end-to-end cloud resource management 15 General requirements for cloud infrastructure 16 General requirements for trusted cloud services 17 Security considerations Appendix I – Use cases of cloud computing I.1 Generic use case I.2 IaaS general use case I.3 NaaS general use case I.4 DaaS general use case I.5 PaaS general use case I.6 CaaS general use case I.7 BDaaS general use case I.8 Inter-cloud computing use case I.9 End-to-end cloud resource management use case I.10 Cloud infrastructure use case I.11 Trusted cloud service use case Appendix II – Methodology and edition plan of this Recommendation 21     24     25     26     27     28     29     30     31     32     33     34          
Language:English
Score: 608502.15 - https://www.itu.int/en/publica...n/files/basic-html/page29.html
Data Source: un
ITU-T Study Group 16 (Study Period 2005-2008)   عربي   |   中文   |   Español   |   Français   |   Русский     Advanced Search   Home : ITU-T Home     Third generation of ITU-T Multimedia Systems and Terminals Call for Proposals on Requirements for the third generation of ITU-T Multimedia Systems and Terminals ITU-T Study Group 16 designed H.320, H.321, and H.322 (the first generation of Multimedia Systems and Terminals) through 1992, followed by H.323, H.324, and H.310 (the second generation) in 1996. (...) However, before deciding whether or not starting such a work in SG 16, a clear set of requirements regarding such new generation Multimedia System and Terminals is needed. (...) The Responses solicited by this Call for Requirements should address: The requirements for the third generation of ITU-T multimedia systems and terminals, with special focus on how such a system and terminals would be used on the NGN.
Language:English
Score: 598228.56 - https://www.itu.int/ITU-T/2005.../com16/ams/cfp3rd20050602.html
Data Source: un
Post-conditions (optional) In contrast to the pre-condition, the post-conditions describe conditions or use cases that will be carried out after the operation of a currently described use case. Requirements The title of requirements derived from the use case. 8.4 General requirements A general requirements-related Recommendation describes the technical area as a whole. The objective of a general requirements related Recommendation is to provide high level requirements of the technical areas a whole. (...) The roles/sub roles defined in the Ecosystem (related Recommendation) are normally used to describe the general requirements. The general requirements of a technical area are derived from related general use case(s)/scenario(s). 8.5 Service requirements A service requirements-related Recommendation describes technical requirements from the service perspective.
Language:English
Score: 597234.23 - https://www.itu.int/en/ITU-T/s...20/13/Documents/guidelines.pdf
Data Source: un
Call for Proposals on Requirements for the third generation of ITU-T Multimedia Systems and Terminals ITU-T Study Group 16 designed H.320, H.321, and H.322 (the first generation of Multimedia Systems and Terminals) through 1992, followed by H.323, H.324, and H.310 (the second generation) in 1996. (...) However, before deciding whether or not starting such a work in SG 16, a clear set of requirements regarding such new generation Multimedia System and Terminals is needed. (...) The Responses solicited by this Call for Requirements should address: · The requirements for the third generation of ITU-T multimedia systems and terminals, with special focus on how such a system and terminals would be used on the NGN.
Language:English
Score: 597105 - https://www.itu.int/ITU-T/2005...16/ams/docs/cfp3rd20050602.doc
Data Source: un
The requirement is analyzed only against the other flexible requirements present in the file which are subject to incompatibilities (received and/or generated by the FLEX requirement under consideration). (...) In the case where the NFS received and generated by another FLEX requirement is ≤ the acceptable NFS value, the requirement is identified in green. (...) In the example below, only NMB is affected by the requirement from AFS. If AFS coordinates it requirement with NMB, the coordination information has precedence over the level of NFS generated to the stations from NMB.
Language:English
Score: 596229.1 - https://www.itu.int/en/ITU-R/t...ting%20Optimization%20tool.pdf
Data Source: un
 Page 37 - Cloud computing: From paradigm to operation           Basic HTML Version Table of Contents View Full Version Page 37 - Cloud computing: From paradigm to operation P. 37 Framework and requirements for cloud computing 1 14 General requirements for end-to-end cloud resource management The general requirements for end-to-end cloud resource management derived from the use cases in clause I.9 are as follows: – Manageability for a single cloud service: It is required that the CSP be able to collect management, telemetry and diagnostics and/or status information from the cloud computing systems used for providing cloud services and report the information to the CSC; – Manageability for multiple cloud services: It is recommended that multiple CSPs work together to offer comprehensive status awareness and management information to expand across multiple cloud data centres as composite cloud services are built from multiple services implemented by multiple cloud service providers, requiring the need for multi-cloud, end-to-end management data. NOTE – For more information on end-to-end cloud computing management, refer to [ITU-T Y.3520] and [ITU-T Y.3521]. 15 General requirements for cloud infrastructure The general requirements for cloud infrastructure derived from the use cases in clause I.10 are as follows: – Resource abstraction and control: It is required for cloud infrastructure to provide resource abstraction and control capability to cloud services; – Resource provisioning: It is required for cloud infrastructure to provide collaboratively processing, storage and network resources to cloud services and supporting functions. NOTE – Functional requirements for cloud computing infrastructure are provided in [ITU-T Y.3510]. 16 General requirements for trusted cloud services The general requirements for trusted cloud services are derived from the use case in clause I.11.
Language:English
Score: 596224.95 - https://www.itu.int/en/publica...n/files/basic-html/page37.html
Data Source: un
The requirement is analyzed only against the other flexible requirements present in the file which are subject to incompatibilities (received and/or generated by the FLEX requirement under consideration). (...) In the case where the NFS received and generated by another FLEX requirement is ≤ the acceptable NFS value, the requirement is identified in green. 9 Example: In the extract below, we can assume that our wanted requirement from AFS cannot be assigned the same frequency as requirement ARIAMSVLEI from NMB. 5. (...) In the example below, only NMB is affected by the requirement from AFS. If AFS coordinates it requirement with NMB, the coordination information has precedence over the level of NFS generated to the stations from NMB.
Language:English
Score: 596011.3 - https://www.itu.int/en/ITU-R/t...GE84%20Optimization%20tool.pdf
Data Source: un
Packing Group III — Packagings must meet the Packing Group II performance requirements. . . . A-3 DGP-WG/20-WP/12 Appendix B Packing Instructions 448 – 449 Cargo aircraft only General requirements . . . (...) Packing Instructions 672 – 677 Cargo aircraft only General requirements . . . COMBINATION PACKAGINGS SINGLE PACKAGINGS Packing instruction Packing group Inner packaging (see 6;3.2) Inner packaging quantity (per receptacle) Total quantity per package . . . (...) Packing Group III — Packagings must meet the Packing Group II performance requirements. . . . DGP-WG/20-WP/12 Appendix A-8 Packing Instructions 862 – 864 Cargo aircraft only General requirements . . .
Language:English
Score: 594457.4 - https://www.icao.int/safety/Da.../WG20/DGPWG.20.WP.012.2.en.pdf
Data Source: un
LMF o Handover Management Framework (Stage 2) - Rec. HMF o FMC general requirements from NGN point of view - Rec. (...) Home Networking) are out of scope • Specific functions to control user gateways may not be supported in R1 ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 32 Basic components : Release 1 Requirements for User Equipment o NGN is expected to support a large variety of user equipment o Both direct and indirect (e.g. via IP PBX) connectivity between terminals and NGN shall be supported o NGN Release 1 does not mandate specific requirements for user equipment, except for • Requirements for access arrangements • Compatibility with NGN authentication, control and transport protocol stacks • Attachment of user equipment enabling interface adaptation to varying user requirements (including accessibility needs) is not precluded o R2 will probably consider user equipment requirements • Ongoing studies in SG13 (Y.CMTP), SG16 (Next Gen MultiMedia terminal) etc. ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 33 Basic components : Release 1 Requirements for Interconnection with peer networks (1) o Interconnection at the Network Node Interface (NNI) • Between multiple NGNs • Between NGN and other networks o Two types of Interconnection • Connectivity-oriented Interconnection (CoIx) is required — Simple IP connectivity, irrespective of interoperability levels — No service awareness, specific requirements not necessarily assured • Service-oriented Interconnection (SoIx) is not precluded — Services may offered with defined levels of interoperability ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 34 Basic components : Release 1 Requirements for Interconnection with peer networks (2) Interoperability inside/between NGN o Required for appropriate components in single NGN o Not precluded between NGNs deploying identical sets of capabilities Interworking with non-NGN networks o Interworking required (doesn’t imply all services can be interworked) o Interworking capabilities - provided as list of objectives o Supported network types • PSTN/ISDN • Circuit-based networks: same requirements than PSTN/ISDN — PLMN, Cable networks, Broadcast networks — Circuit-based Enterprise networks via PSTN/ISDN or PIE gateway • IP-based networks : interconnection not excluded ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 35 Interconnection between NGNs: complex topic requiring further work o Practicable Interconnection arrangements for seamless service operations are critical for NGN success o GSMA is considering to extend the GRX backbone to IMS • Will NGN share the same backbone than IMS ?
Language:English
Score: 594090.53 - https://www.itu.int/ITU-T/work...00610/presentations/kns-p1.pdf
Data Source: un