Home

Results 1 - 10 of 258,361 for functionality. Search took 2.494 seconds.  
Sort by date/Sort by relevance
For example, the function may initiate re-allocation of specific physical resource(s) using physical resource configuration functions. 9.3 Physical resource discovery function Physical resource discovery function detects new physical resources and reports them to virtual resource discovery function of virtual resource management functions. 10 Virtual resource management functions Virtual resource management functions manage, control, and monitor virtual resources in collaboration with physical resource management functions, LINP management functions, and LINP operator functions. They include virtual resource configuration functions, virtual resource monitoring and fault management function, and, optionally, virtual resource discovery function. (...) The allocation function allocates specific virtual link resources and virtual node resources to an LINP upon receiving request from resource coordination function of LINP management functions; − De-allocation function.
Language:English
Score: 579955.9 - https://www.itu.int/en/publica.../files/basic-html/page134.html
Data Source: un
The tunnel/packet routing/switch information and tunnel parameters are transferred from control function to forwarding function. The charging function could be realized on control function, forwarding function or both, which depends on the implementations. The separation of the GW's control function and forwarding function could improve the deployment flexibility, such as centralized control function and distributed forwarding function deployment, without changing the interfaces to other legacy functions. Scenario 1: flexible deployment of separated control function and forwarding function Descriptions When the GW is separated into control function and forwarding function, the control function is centralized and deployed with other mobile packet core control function such as mobility management function, and policy function.
Language:English
Score: 579694.73 - https://www.itu.int/en/publica.../files/basic-html/page243.html
Data Source: un
 Page 838 - Cloud computing: From paradigm to operation           Basic HTML Version Table of Contents View Full Version Page 838 - Cloud computing: From paradigm to operation P. 838 5 Intercloud and interoperability The inter-cloud functions identified in clause 7 are mapped to functional components in [ITU-T Y.3502]. No new functional components are defined. However, functions of some functional components are extended for inter-cloud as follows. – Business support systems • Service subscription management functional component is extended with service subscription management function for inter-cloud as described in clause 7.1.1. • Billing functional component is extended with billing function for inter-cloud as described in clause 7.1.2. – Operational support systems • Service catalogue functional component is extended with service catalogue function for inter- cloud as described in clause 7.2.1. • Provisioning functional component is extended with service provisioning function for inter- cloud as described in clause 7.2.2. • Monitoring and reporting functional component is extended with monitoring and reporting function for inter-cloud as described in clause 7.2.3. • Service policy management functional component is extended with service policy management function for inter-cloud as described in clause 7.2.4. • Service automation functional component is extended with service automation function for inter-cloud as described in clause 7.2.5. • Service level management functional component is extended with service level management function for inter-cloud as described in clause 7.2.6. • Incident and problem management functional component is extended with incident and problem management function for inter-cloud as described in clause 7.2.7. • Peer service management functional components is extended with peer service management function for inter-cloud as described in clause 7.2.8. – Peer service integration • Peer service integration functional component is extended with peer CSP management function as described in clause 7.3.1. • Peer service integration functional component is extended with inter-cloud service negotiation as described in clause 7.3.2. • Peer service integration functional component is extended with inter-cloud service discovery function as described in clause 7.3.3. • Peer service integration functional component is extended with inter-cloud service selection function as described in clause 7.3.4. • Peer service integration functional component is extended with inter-cloud service reservation function as described in clause 7.3.5. • Peer service integration functional component is extended with inter-cloud service release function as described in clause 7.3.6. • Peer service integration functional component is extended with inter-cloud capabilities adaptation function as described in clause 7.3.7. – Security systems • Authentication and identity management functional component is extended with authentication and identity management function for inter-cloud as described in clause7.4.1. • Authorization and security policy management functional component is extended with authorization and security policy management function for inter-cloud as described in clause 7.4.2. 830     833     834     835     836     837     838     839     840     841     842     843          
Language:English
Score: 579678.5 - https://www.itu.int/en/publica.../files/basic-html/page838.html
Data Source: un
 Page 56 - 5G Basics - Core Network Aspects           Basic HTML Version Table of Contents View Full Version Page 56 - 5G Basics - Core Network Aspects P. 56 1 Core network aspects 8.2.1 Data capability Data capability has functional blocks as follows:  Forwarding function: This functional block contains NDO name based forwarding function, request aggregation function, and packet forwarding loop avoidance function.  Cache function: This functional block includes storage to cache NDOs and its accompanying control function.  NDO repository: NDO repository is the storage to hold original contents. Additionally, application specific functional blocks may be placed in the data capability. 8.2.2 Control capability Control capability has functional blocks as follows:  Routing function: Routing functional block is composed of NDO registration function, NDO location resolution function, advertisement function for the availability of NDOs, and network selection function for messages to reach an NDO.  Mobility support function: Mobility support function includes consumer mobility function, NDO mobility function, and network mobility function.  Forwarding information base: Forwarding information base is the storage to hold information to determine the direction of forwarding and is to be used by forwarding function.  Publish/subscribe function: This functional block includes publication and subscription functions. Additionally, application specific functional blocks may be placed in the control capability. 8.2.3 Security capability Security capability has functional blocks as follows:  Access control function: Access control function is a mechanism to secure data confidentiality that NDO is accessible only by the authorized consumers.  NDO authentication function: NDO authentication function is a mechanism to secure data authenticity that NDO is claimed to be true by an authorized entity.  NDO integrity function: NDO integrity function is a mechanism to examine and confirm the integrity of NDO that NDO is ensured to be the same as the source. 8.2.4 Management capability Management capability is the function block to provide network management functions.
Language:English
Score: 579496.14 - https://www.itu.int/en/publica...s/files/basic-html/page56.html
Data Source: un
The cloud infrastructure function set include cloud physical element functions and a cloud hypervisor function above them. Cloud physical element functions provide the basic functions of computing and storage. Cloud hypervisor function provides the functionality to manage cloud physical elements, and provide virtualization functions above them.
Language:English
Score: 579485.74 - https://www.itu.int/en/publica.../files/basic-html/page464.html
Data Source: un
 Page 135 - 5G Basics - Core Network Aspects           Basic HTML Version Table of Contents View Full Version Page 135 - 5G Basics - Core Network Aspects P. 135 Core network aspects 1 11 LINP management functions LINP management functions manage, control, and monitor LINPs, in collaboration with virtual resource management functions, LINP operator functions, and service deployment functions. They include resource orchestration function, LINP configuration functions, LINP monitoring and fault detection function, and authorization functions. 11.1 Resource coordination function Resource coordination function chooses specific virtual resources among available ones to constitute a LINP, and create a mapping between them. (...) When that happens, the function notifies the detected events to virtual resource management functions to deal with the problem. 11.4 Authorization functions Authorization functions provide the following: − LINP operator authorization: LINP operation authorization function authorizes LINP operators to access LINPs.
Language:English
Score: 579290 - https://www.itu.int/en/publica.../files/basic-html/page135.html
Data Source: un
Page 563 - Unleashing the potenti al of the Internet of Things           Basic HTML Version Table of Contents View Full Version Page 563 - Unleashing the potenti al of the Internet of Things P. 563 Unleashing the potential of the Internet of Things 5 I.4 Mapping table of the requirements and the existing NGN functions Clause I.2 defines the existing NGN capabilities to satisfy the requirements of [ITU-T Y.2221]. This clause allocates proper functions of NGN which are defined in [ITU-T Y.2012] to support the capabilities. Requirements Corresponding functions Profile management for service • Application support functions and service support functions registration and discovery (ASF&SSF) Quality of service: Application traffic • Transport functions control – Access network functions – Edge functions • Core transport functions Quality of service: Differentiated QoS • Transport functions and data prioritization – Access network functions – Edge functions – Core transport functions • Transport control functions – Resource and admission control functions (RACF) Connectivity • Transport control functions – Network attachment control functions (NACF) Location management • Transport control functions – Network attachment control functions (NACF) Mobility • Transport functions – Access network functions – Mobility management and control functions (MMCF) Security • Management functions (security key management) • End-user functions (data security) • Application support functions and service support functions (ASF&SSF) Identification, authentication and • Transport control functions authorization – Network attachment control functions (NACF) • Service control and content delivery functions (SC&CDF) – Service control functions (SCF) • Application support functions and service support functions (ASF&SSF) Accounting and charging • Management functions (accounting management) – Charging and accounting functions (CAF) Rec.
Language:English
Score: 579271 - https://www.itu.int/en/publica.../files/basic-html/page563.html
Data Source: un
Page 563 - 2015 Security in Telecommunications and Information Technology           Basic HTML Version Table of Contents View Full Version Page 563 - 2015 Security in Telecommunications and Information Technology P. 563 Unleashing the potential of the Internet of Things 5 I.4 Mapping table of the requirements and the existing NGN functions Clause I.2 defines the existing NGN capabilities to satisfy the requirements of [ITU-T Y.2221]. This clause allocates proper functions of NGN which are defined in [ITU-T Y.2012] to support the capabilities. Requirements Corresponding functions Profile management for service • Application support functions and service support functions registration and discovery (ASF&SSF) Quality of service: Application traffic • Transport functions control – Access network functions – Edge functions • Core transport functions Quality of service: Differentiated QoS • Transport functions and data prioritization – Access network functions – Edge functions – Core transport functions • Transport control functions – Resource and admission control functions (RACF) Connectivity • Transport control functions – Network attachment control functions (NACF) Location management • Transport control functions – Network attachment control functions (NACF) Mobility • Transport functions – Access network functions – Mobility management and control functions (MMCF) Security • Management functions (security key management) • End-user functions (data security) • Application support functions and service support functions (ASF&SSF) Identification, authentication and • Transport control functions authorization – Network attachment control functions (NACF) • Service control and content delivery functions (SC&CDF) – Service control functions (SCF) • Application support functions and service support functions (ASF&SSF) Accounting and charging • Management functions (accounting management) – Charging and accounting functions (CAF) Rec.
Language:English
Score: 578788.04 - https://www.itu.int/wftp3/Publ.../files/basic-html/page563.html
Data Source: un
 Page 601 - Cloud computing: From paradigm to operation           Basic HTML Version Table of Contents View Full Version Page 601 - Cloud computing: From paradigm to operation P. 601 XaaS 3 • operational support systems functional component-monitoring and reporting: monitoring and controlling virtual desktop resource function (see clause 7.3.1) • operational support systems functional component-service policy management: operational policy management for DaaS function (see clause 7.3.4) • operational support systems functional component-platform and virtualisation management: virtual desktop resource allocation and distribution function (see clause 7.3.3) • operational support systems functional component-incident and problem management: high availability for DaaS function (see clause 7.3.5), power management of virtual desktop resource function (see clause 7.3.6) • business support systems functional component-account management: user account and profile management function (see clause 7.3.2) There are four DaaS functions that are not mapped to any functional components in [ITU-T Y.3502]; they can be located in the layering framework as follows: – User layer: • connection negotiation function (see clause 7.4.2), client peripheral connection function (see clause 7.4.3), service continuity for user environment function (see clause 7.4.4) – Multi-layer functions: • operational support systems functional component: provisioning and allocation of virtual desktop function (see clause 7.2.4) The detailed mapping is in Appendix II. Since there are no reference points among functional components in [ITU-T Y.3502], it is necessary to adopt the grouping of DaaS functions in order to specify their reference points for convenience. Clause 9 explains the reference points based on four groups of DaaS functions as in Figure 7-1, i.e., client support functions, virtual desktop connection and delivery functions, virtual desktop resource management functions, and virtualization infrastructure functions. 9 DaaS functional architecture 9.1 Client support functions The client support functions (CS-FS) have four functions including: connection negotiation function (CN-F), client peripheral connection function (CPC-F), service connection function (SC-F), and service continuity for user environment function (SCUE-F) as shown in Figure 9-1.
Language:English
Score: 578569.9 - https://www.itu.int/en/publica.../files/basic-html/page601.html
Data Source: un
The IoT Security and Privacy Protection functional entity crosses all functional layers. NOTE 2 – The functional entities described in this Recommendation located in the service support and application support layer are only related with the generic support capabilities specified in [ITU-T Y.2060]. 7.2.2 Functional entities of an implementation view The Transport functional entity illustrated in Figure 7-2 includes the access network functions, edge functions, core transport functions, gateway functions, and media handling functions as specified in [ITU-T Y.2012]. The Transport Control functional entity illustrated in Figure 7-2 includes resource and admission control functions (RACF), network attachment control functions (NACF), and mobility management and control functions (MMCF) as specified in [ITU-T Y.2012]. (...) The Management and Identity Management functional entity illustrated in Figure 7-2 includes management functions and identity management functions as specified in [ITU-T Y.2012].
Language:English
Score: 578115.33 - https://www.itu.int/wftp3/Publ.../files/basic-html/page488.html
Data Source: un