Home

Results 51 - 60 of 213,962 for functional. Search took 8.634 seconds.  
Sort by date/Sort by relevance
ITU-T Y.3011 Management Functions The functions or operations related to the management of the network functions and resources. (...) ITU-T Y.2011 Network function A processing function in a network. It includes but is not limited to network nodes functionality, e.g. session management, mobility management, switching, routing functions, which has defined functional behavior and interfaces. (...) ITU-T Y.3011 Virtualized Network Function A network function whose functional software is decoupled from hardware and runs on a virtual machine(s).
Language:English
Score: 475380.1 - https://www.itu.int/en/ITU-T/f...2030_Terms_and_Definitions.pdf
Data Source: un
Divider page to introduce new topic Malcolm Webb Partner, MGF Webb New Zealand GSR 08: Session 3GSR 08: Session 3 Breaking Up is Hard to Do:Breaking Up is Hard to Do: The Emergence of The Emergence of Functional SeparationFunctional Separation as a Regulatory Remedyas a Regulatory Remedy ACCESSACCESS WHOLESALEWHOLESALE RETAILRETAIL CUSTOMERSCUSTOMERS RETAIL COMPETITORS RETAIL BUSINESS DIVISION WHOLESALE DIVISION Access services based on physical assets Access services based on electronic assets OpenreachOpenreach: Asset Ownership: Asset Ownership PSTN & ADSL ServicePSTN & ADSL Service CP Core Node LLUC Space BTW Core Node Backplate of NTE Line Card Openreach is also responsible for all duct, access fibre and copper & fibre backhaul Customer Premises Main Distribution Frame Secondary Connection Point Distribution Point (DP) Backhaul Products Copper Cables Local Telephone ExchangeCore Node Primary Connection Point (Cabinet) openreach Reasons forReasons for Functional SeparationFunctional Separation Discriminatory behaviour by the incumbent – particularly non-price discrimination Existing remedies may not be effective in controlling discriminatory behaviour 3 Key Features of3 Key Features of Functional SeparationFunctional Separation The “virtual” separation of the incumbent’s business The “equivalence” or “equivalence of inputs” (EoI) obligation Monitoring of the incumbent, to ensure compliance with the separation and equivalence obligations, and effective enforcement Functional Separation: Functional Separation: Key IssuesKey Issues Transition to fibre-based next-generation access networks Difficulty in achieving stability in the asset base Service quality Impact on investment incentives Functional Separation in Functional Separation in Developing CountriesDeveloping Countries An independent and reasonably competent bureaucracy that can implement separation, monitor compliance and enforce non-compliance A reasonably strong incumbent operator, that can bear the costs and continue to operate effectively A reasonable expectation that the incumbent will be cooperative Checklist: Alternatives to Alternatives to Functional SeparationFunctional Separation Use blunter regulatory instruments Go straight to structural separation www.itu.int/gsr08www.itu.int/gsr08 Thank you! (...) info@mgfwebb.cominfo@mgfwebb.com PO Box 105PO Box 105--426426 Auckland CityAuckland City New ZealandNew Zealand Phone: +64 9 970 4100Phone: +64 9 970 4100 Fax: +64 9 970 4102Fax: +64 9 970 4102 Openreach: Asset Ownership 3 Key Features ofFunctional Separation Functional Separation: Key Issues Functional Separation in Developing Countries Alternatives to Functional Separation
Language:English
Score: 475309.4 - https://www.itu.int/ITU-D/treg...esentations/Session_3_Webb.pdf
Data Source: un
Microsoft PowerPoint - ts1-p2.ppt ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 International Telecommunication Union Resource and Admission Control in Resource and Admission Control in NGNNGN Ning Li Co-editor of Y.RACF Huawei Technologies ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 2 Outline o Works on RACF in ITU-T o Key features of RACF o RACF implementation requirements o RACF implementation scenarios o Example E2E QoS solution o RAC solution for ADSL/LAN access o RAC solution for UMTS access RAC ---- Resource and Admission Control ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 3 Works on RACF in ITU-T SCF-- Service Control Functions; NACF-- Network Attachment Control Functions; PD-FE -- Policy Decision Functional Entity RACF -- Resource and Admission Control Functions; TRC-FE -- Transport Resource Control Functional Entity; PE-FE -- Policy Enforcement Functional Entity (PE-FE); TRE-FE -- Transport Resource Enforcement Functional Entity The functional architecture of RACF as defined in ITU RACF document ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 4 Key Features of RACF o Key Features of RAC: • Resource arbitrator • Service-driven QoS control, traffic control, NAPT control and FW inspection mode selection • Incremental implementation • Unified Rs to the service layer • Unified Rw interface going down to network edge devices • Compliance checking of the traffic and QoS against subscribed bandwidth and QoS ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 5 RACF Implementation Req’s The early stage implementation of RACF requires the current network to support the Rs, Rw and the PE-FE functions. (...) Implementation Scenario 1 RACFRACF Core Networks Access Networks CPN Network Attachment Control Functions PE-FEPE-FE PE-FE Rs Rs Rw Ru Rw Rt Rc CPE PE-FE Rw Rc TRC-FE RpRt Rw Service Stratum Transport Stratum PD-FE Service Control Functions Rd PD-FE TRC-FE RACFRACF Core Networks Access Networks CPN Network Attachment Control Functions PE-FEPE-FE PE-FE Rs Rs Rw Ru Rw Rt Rc CPE PE-FE Rw Rc TRC-FE RpRt Rw Service Stratum Transport Stratum PD-FE Service Control Functions Rd PD-FE TRC-FE ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 7 Scenario 2:The access and the core belong to different administrative domains, and the SCF interacts with either of the RACFs at the two sides. (...) Implementation Scenario 2 RACFRACF Core Networks Access Networks CPN Network Attachment Control Functions PE-FEPE-FE PE-FE Rs Rw Ru Rw Rt Rc CPE PE-FE Rw Rc TRC-FE RpRt Rw Service Stratum Transport Stratum PD-FE Service Control Functions Rd PD-FE TRC-FE Ri RACFRACF Core Networks Access Networks CPN Network Attachment Control Functions PE-FEPE-FE PE-FE Rs Rw Ru Rw Rt Rc CPE PE-FE Rw Rc TRC-FE RpRt Rw Service Stratum Transport Stratum PD-FE Service Control Functions Rd PD-FE TRC-FE Ri ITU-T/ITU-D Workshop "Standardization and Development of Next Generation Networks" Dar es Salaam, 3-5 October 2006 8 Scenario 3: The access and the core belong to the same administrative domain.
Language:English
Score: 475286.04 - https://www.itu.int/ITU-T/work...00610/presentations/ts1-p2.pdf
Data Source: un
In any case it is clear that there is no will within the H.245 group to address the level of functionality currently available to a T.130 based solution neither is there sufficient capability in the current H.245 to support T.130 functions. (...) Where there is Generic AVC functionality of common interest to both standards groups, that functionality must not be developed in isolation within either group. (...) This joint responsibility agreement should not however be used to restrict functionality not required by the other standard. A decision as to which functionality should be mandatory can be a topic for further discussion.
Language:English
Score: 475099.56 - https://www.itu.int/wftp3/av-a...e/1997-2000/9709_Sun/TD-10.doc
Data Source: un
To provide a national perspective on globalization based on a Global Value Chain (GVC) model Focus on a specific GVC with major trading partners to highlight the multi-country supply chain of goods, value-adding services & institutional arrangements Flexible implementation approach: GVC-specific SUTs and GVC specific institutional sector accounts (either national or multi-country) The GVC Accounting Framework 8 • GVC satellite accounts measure specific aspects of GVCs that are otherwise hidden in the macro-economic accounts. • GVC-specific Supply and Use Tables and GVC-specific Institutional Sector Accounts are comparable across countries using standardized GVC specific products and industry classifications and sector classifications. • Business functions are mapped to the international classifications of products and economic activities; e.g., in the automotive GVC, the core business function is manufacture of motor vehicles. • Participating firms are classified as: Lead firm - the firm that „controls‟ the chain Affiliated Supplier o Controlled [Subsidiary (controlled)] o Non-controlled [Associates (influenced)] Non-affiliated supplier Classifications used 9 Business Functions GVC participating firms GVC products by GVC industry • A business line represents a sequence of business functions controlled by the lead firm • Can be mapped to the reference classification of products and economic activities GVC institutional sectors GVC functional breakdown • Firms are classified according to their role in the GVC (whether lead firm, affiliated or non-affiliated supplier) • A standardized list of product codes and descriptions for industry-specific GVCs • Can be mapped to HS for traded products and CPC for the SUT framework • An extension to the institutional sector framework is largely made to accommodate concepts from FDI • Enhances the standard BOP/IIP functional classification to include a separate category distinct from foreign direct investment – namely other inter- company financing 1. (...) Identify the GVC industries and products and business functions. 7. Map the GVC industries and business functions to ISIC and map the GVC products to CPC codes. 12 Practice for compiling GVC satellite accounts Business Functions 13 • A sequence of business production processes or business functions bring a product from its conception to its final consumers. • They are controlled by the lead firm in a GVC. • They can be divided into core functions and support functions and are undertaken by the lead, affiliate and non- affiliate firms in the GVC. • Core business functions are activities that yields income, normally primary activity of the enterprise. • Support business functions are ancillary supporting activities that facilitate the core business functions • Outputs of support business functions are not themselves intended directly for the market or for third parties • Support business functions can include: • transportation, distribution and logistics • marketing, sales and after-sales services • ICT services • administrative and management services • engineering and related technical services • Research & development Location and upgrading of business functions 14 This can allow for the identification of opportunities for upgrading by gaining competitiveness in higher value-added products through skill, capital and process upgrading. How business functions are generally located about generation of value added in a GVC: Integration into a GVC-specific SUT 15 8.
Language:English
Score: 475069.1 - https://www.cepal.org/sites/de...g-gvcs-unsd-guatemala-2019.pdf
Data Source: un
MKMD (X.750:10/1996) -- Module MKMD (X.750:10/1996) -- See also ITU-T X.750 (1996) Technical Cor. 1 (02/2000) -- See also the index of all ASN.1 assignments needed in this document MKMD {joint-iso-itu-t(2) ms(9) function(2) part16(16) asn1Modules(2) 5} DEFINITIONS IMPLICIT TAGS ::= BEGIN dmiAttribute OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) smi(3) part2(2) attribute(7)} dmiNotification OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) smi(3) part2(2) notification(10)} mkmDirectoryAttributeType OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) standardSpecificExtension(0) directoryAttributeTypes(4)} mkmDirectoryObjectClass OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) standardSpecificExtension(0) directoryObjectClasses(6)} mkmDirectoryNameForm OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) standardSpecificExtension(0) directoryNameForms(7)} mkmMObjectClass OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) managedObjectClass(3)} mkmPackage OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) package(4)} mkmParameter OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) parameter(5)} mkmNameBinding OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) nameBinding(6)} mkmAttribute OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) attribute(7)} mkmAction OBJECT IDENTIFIER ::= {joint-iso-itu-t(2) ms(9) function(2) part16(16) action(9)} END -- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
Language:English
Score: 474944.04 - https://www.itu.int/wftp3/Publ...fl/itu-t/x/x750/1996/MKMD.html
Data Source: un
This inevitably results in competition between the two sets of functions for both resources and managerial attention, to the detriment of both sets of functions. Strategy and policy-related functions, for e ample, usually have a longer-term perspective. (...) In this manner, the proposed structure also ensures that there is no duplication of functions. It also strengthens accountability and internal control by placing compliance functions and execution functions in separate departments.
Language:English
Score: 474638.53 - https://www.un.org/en/ga/fifth..._of_Eff_HR%20placement_CdC.pdf
Data Source: un
These functional entities can be implemented in different equipments or gathered. In any case, exchanges of data occur between these entities. 1.1 The Home Location Function (HLF) This functional entity is a data base in charge of the management of mobile subscribers. (...) The AuF communicates only with its associated HLF and Gatekeeper over an interface denoted in H.323 Annex H. 1.4 The Interworking Function (IWF) The Interworking Function (IWF) is a functional entity associated with the Gatekeeper/Gateway The IWF provides the functionality necessary to allow interworking between a H.323 Network and the PLMN and the fixed networks (ISDN, PSTN and PDNs).
Language:English
Score: 473998.63 - https://www.itu.int/wftp3/av-a...bilityDefn_Geneva_02072000.doc
Data Source: un
-- Module Identifiers-and-Expressions (T.415:03/1993) Identifiers-and-Expressions {2 8 1 5 7} DEFINITIONS ::= BEGIN EXPORTS Content-Portion-Identifier, Object-or-Class-Identifier, Style-Identifier, Protected-Part-Identifier, Category-Name, Resource-Name, Binding-Name, Construction-Expression, Object-Id-Expression, Numeric-Expression, String-Expression; IMPORTS Layout-Object-Type FROM Layout-Descriptors -- see 7.9 Logical-Object-Type FROM Logical-Descriptors; -- see 7.10 Content-Portion-Identifier ::= [APPLICATION 0] IMPLICIT PrintableString -- only digits and space are used in the present version -- of this Specification; other characters are reserved for extensions Object-or-Class-Identifier ::= [APPLICATION 1] IMPLICIT PrintableString -- only digits and space are used in the present version -- of this Specification; other characters are reserved for extensions; -- a 'null' value is represented by an empty string Style-Identifier ::= [APPLICATION 5] IMPLICIT PrintableString -- only digits and space are used in the present version -- of this Specification; other characters are reserved for extensions; -- a 'null' value is represented by an empty string Protected-Part-Identifier ::= [APPLICATION 7] IMPLICIT PrintableString -- only digits and space are used in the present version -- of this Specification; other characters are reserved for extensions; -- a 'null' value is represented by an empty string Category-Name ::= PrintableString -- a 'null' value is represented by an empty string Resource-Name ::= PrintableString Binding-Name ::= PrintableString Construction-Expression ::= CHOICE { construction-type Construction-Type, single-term-construction [3] Construction-Term } Construction-Type ::= CHOICE { sequence-construction [0] IMPLICIT Term-Sequence, aggregate-construction [1] IMPLICIT Term-Sequence, choice-construction [2] IMPLICIT Term-Sequence } Term-Sequence ::= SEQUENCE OF Construction-Term Construction-Term ::= CHOICE { required-construction-factor [0] Construction-Factor, optional-construction-factor [1] Construction-Factor, repetitive-construction-factor [2] Construction-Factor, optional-repetitive-factor [3] Construction-Factor } Construction-Factor ::= CHOICE { object-class-identifier Object-or-Class-Identifier, construction-type Construction-Type } Object-Id-Expression ::= CHOICE { current-object-function [0] IMPLICIT NULL, preceding-object-function [1] Object-Id-Expression, superior-object-function [3] Object-Id-Expression, current-instance-function [4] Current-Instance-Function } Numeric-Expression ::= CHOICE { numeric-literal [0] IMPLICIT INTEGER, increment-application [1] Numeric-Expression, decrement-application [2] Numeric-Expression, ordinal-application [3] CHOICE {identifier Object-or-Class-Identifier, expression Object-Id-Expression}, binding-reference [4] IMPLICIT Binding-Reference } Binding-Reference ::= SET { object-reference CHOICE {identifier Object-or-Class-Identifier, expression Binding-Selection-Function}, binding-identifier Binding-Name } Binding-Selection-Function ::= CHOICE { current-object-function [0] IMPLICIT NULL, preceding-function [1] Object-Id-Expression, superior-function [3] Object-Id-Expression, current-instance-function [4] Current-Instance-Function } Current-Instance-Function ::= SEQUENCE { first-parameter CHOICE {identifier [0] IMPLICIT Object-or-Class-Identifier, layout-object-type [1] IMPLICIT Layout-Object-Type, logical-object-type [2] IMPLICIT Logical-Object-Type}, second-parameter CHOICE {identifier Object-or-Class-Identifier, expression Object-Id-Expression} } String-Expression ::= SEQUENCE OF Atomic-String-Expression Atomic-String-Expression ::= CHOICE { string-literal [0] IMPLICIT OCTET STRING, binding-reference [2] IMPLICIT Binding-Reference, make-string-application [3] Numeric-Expression, upper-alpha-application [4] Numeric-Expression, lower-alpha-application [5] Numeric-Expression, upper-roman-application [6] Numeric-Expression, lower-roman-application [7] Numeric-Expression } END -- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
Language:English
Score: 473975.5 - https://www.itu.int/wftp3/Publ...dentifiers-and-Expressions.asn
Data Source: un
. • UNDP and UNEP have supported the Ministry of Finance in Mozambique since 2005 to integrate environment and climate change in the planning and budget systems • This has been done through the Poverty & Environment Initiative PEI and the SUNRED project Environment and CC budget tracking (programmatic codes) • Mozambique presently has both programmatic codes and functional codes for environment and climate change investments • The present programmatic codes were developed in 2015 (MCA39 – 43) • The functional code 05 (environment protection) is also used by the same institutions • Limitations: • Its only government institutions with an environment mandate that use these codes • Tracking the budget will only reveals what these institutions have budgeted and invested and not what other sector institutions might have invested. (...) Subfunctions of 05 (environment protection) Environment and CC budget tracking (functional code 05xxxx) Allocation in percentage to environment & CC of the total state budget • From 2016 – 2020 there were a total of 169 actions in the GoM’s Social and Economic Plans. • About 20% were implemented by the Ministry for Land, Environment and Rural Development • The rest were implemented by different sector ministries • The sector institutions do not use the functional or programmatic codes on environment & CC • Therefore, about the budget for about 80% of the actions planned is not captured in a budget tracking exercise Distribution of 169 Env & CC actions in the Social and Economic Plans 2016 – 2020 Ministry of Economy and Finance – Current activities • The Ministry of Economy and Finance is finalizing a new Planning and Budgeting system (SPO)which will be applied nationally from central level to districts and municipalities • The SPO identifies about 50 programs and about 200 sub- programs. • With support from UNDP-UNEP SUNRED II MEF has carried out a consultancy to identify • Solutions for integration of the functional code 05xxxx into the SPO and • Institutions that ought to use the 05xxxx to be able to capture close to 100% of the State budget to environment & climate change Advantages of using the functional code 05 (environment protection) • Formulation of policies and public expenditure analyses that are comparable internationally; • Analise the fiscal policy in Mozambique; • Possibility of quantifying the Government’s actions and • Assess the efficiency of the Government’s programs in relation to allocating funds to a certain function. (...) Integration into the Planning and Budgeting Sub-programme • Programme : MCA43 - DRR • Action : Areas in risk of climate disasters mapped • Programmatic coding : MCA43 -2-MAE xx • Function : 08211 • Auxiliary function : 05211 • Currency : MZN • Amount, function : 3000 • Amount, auxiliary function :2000 • Total amount : 5000 Recommendations for improving environment & CC budget tracking THANK YOU Environment and climate budget tracking in the sub-programme for planning and budgeting, Ministry of Economy and Finance, Mozambique, Environment and CC in Mozambique’s planning and budget systems Environment and CC budget tracking (programmatic codes) Environment and CC budget tracking (functional code 05xxxx) Allocation in percentage to environment & CC of the total state budget Distribution of 169 Env & CC actions in the Social and Economic Plans 2016 – 2020 Ministry of Economy and Finance – Current activities Advantages of using the functional code 05 (environment protection) Recommendations for improving environment & CC budget tracking THANK YOU
Language:English
Score: 473891.6 - https://www.undrr.org/media/48662/download
Data Source: un