Home

Results 11 - 20 of 340,061 for direction. Search took 1.767 seconds.  
Sort by date/Sort by relevance
Introduction The current CD still handles direct mode from the viewpoint of the conventional B (bi-directional) picture. (...) Two motion vectors in forward direction 2.1.4 Two motion vectors in backward direction (Figure 1. (...) In this contribution, the motion vector of direct mode taking backward direction is predicted from three neighboring macroblocks.
Language:English
Score: 428026.46 - https://www.itu.int/wftp3/av-a...002_07_Klagenfurt/JVT-D056.doc
Data Source: un
-- Module Common-Information-Operations (H.450.12:07/2001) Common-Information-Operations {itu-t recommendation h 450 12 version1(0) common-information-operations(0)} DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS OPERATION, ERROR FROM Remote-Operations-Information-Objects {joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} EXTENSION, Extension{} FROM Manufacturer-specific-service-extension-definition {itu-t recommendation h 450 1 version1(0) msi-definition(18)} MixedExtension, undefined FROM Call-Hold-Operations {itu-t recommendation h 450 4 version1(0) call-hold-operations(0)}; H323CommonInformationOperations OPERATION ::= {cmnRequest | cmnInform} cmnRequest OPERATION ::= { ARGUMENT DummyArg OPTIONAL TRUE RESULT CmnArg ERRORS {undefined} CODE local:84 } cmnInform OPERATION ::= { ARGUMENT CmnArg RETURN RESULT FALSE ALWAYS RESPONDS FALSE CODE local:85 } CmnArg ::= SEQUENCE { featureList FeatureList OPTIONAL, featureValues FeatureValues OPTIONAL, featureControl FeatureControl OPTIONAL, extension SEQUENCE SIZE (0..255) OF MixedExtension OPTIONAL, ... } DummyArg ::= SEQUENCE { extensionArg SEQUENCE SIZE (0..255) OF MixedExtension OPTIONAL } FeatureList ::= SEQUENCE { -- indicates capabilities of the endpoint sending the FeatureList ssCFreRoutingSupported NULL OPTIONAL, -- Call Forwarding rerouting -- supported meaningful only in -- forward direction during call -- establishment ssCTreRoutingSupported NULL OPTIONAL, -- Call Transfer rerouting -- supported meaningful both in -- forward & backward direction -- during call establishment ssCCBSPossible NULL OPTIONAL, -- CCBS possible meaningful only -- in backward direction before -- receipt of ALERTING/CONNECT ssCCNRPossible NULL OPTIONAL, -- CCNR possible meaningful only -- in backward direction before -- receipt of CONNECT ssCOSupported NULL OPTIONAL, -- Call Offer supported -- meaningful only in backward -- direction during call -- establishment -- Call Intrusion ssCIForcedReleaseSupported NULL OPTIONAL, -- meaningful only in -- backward direction ssCIIsolationSupported NULL OPTIONAL, -- meaningful only in -- backward direction ssCIWaitOnBusySupported NULL OPTIONAL, -- meaningful only in -- backward direction ssCISilentMonitoringSupported NULL OPTIONAL, -- meaningful only in -- backward direction ssCIConferenceSupported NULL OPTIONAL, -- meaningful only in -- backward direction -- Call Hold ssCHFarHoldSupported NULL OPTIONAL, -- meaningful in both -- directions -- Message Waiting Callback ssMWICallbackSupported NULL OPTIONAL, -- meaningful in backward -- direction -- meaningful both in -- forward & backward -- direction during call -- establishment -- Call Park ssCPCallParkSupported NULL OPTIONAL, -- meaningful in both -- directions ... } FeatureValues ::= SEQUENCE { partyCategory PartyCategory OPTIONAL, ssCIprotectionLevel SSCIProtectionLevel OPTIONAL, -- Supplementary Service Call Intrusion Protection level -- meaningful both in forward and backward direction; inclusion -- indicates support of SS-CI as an unwanted endpoint (forward -- direction) or as a Terminating Endpoint (backward direction), -- as well as the applicable protection level. ... } PartyCategory ::= ENUMERATED {unknown, extension, attendant, emergExt, ... } SSCIProtectionLevel ::= INTEGER(0..3) FeatureControl ::= SEQUENCE { ssCHDoNotHold NULL OPTIONAL, -- meaningful in both directions -- Sending endpoint shall not be held ssCTDoNotTransfer NULL OPTIONAL, -- meaningful in both directions -- sending endpoint shall not be transferred ssMWICallbackCall NULL OPTIONAL, -- meaningful only in SETUP -- indicating a callback call ssCISilentMonitorPermitted NULL OPTIONAL, -- unwanted endpoint -- allows for -- silent monitoring -- meaningful in forward and backward direction ... } END -- of Common-Information-Operations -- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
Language:English
Score: 427033.54 - https://www.itu.int/wftp3/Publ...mon-Information-Operations.asn
Data Source: un
Introduction In Geneva, the method to reduce the bandwidth to access to external SDRAM to get MVs for direct temporal mode as adopted for HDTV. However, it was not adopted for SDTV yet. (...) And the performance of two direct mode with adopted restriction was evaluated for HDTV 2. (...) (Remarks: Empty column will be filled by the meeting.) 3.1 SDTV(625) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 35.44 40.49 40.95 4544.47 32 32.51 39.14 39.47 2709.72 36 29.54 37.69 37.94 1450.16 40 26.98 36.56 36.66 741.84 Direct Temporal+RC 28 35.43 40.49 40.95 4543.47 32 32.51 39.14 39.48 2709.61 36 29.54 37.69 37.94 1450.62 40 26.98 36.56 36.66 741.84 Direct Spatial 28 35.38 40.48 40.93 4410.19 32 32.44 39.12 39.43 2617.31 36 29.41 37.65 37.87 1393.78 40 26.81 36.51 36.56 715.55 Table 1: Comparison of Direct Mode (Src5) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 34.81 40.28 40.58 5421.69 32 31.96 38.83 38.98 2914.63 36 29.19 37.29 37.19 1318.59 40 26.93 36.00 35.99 599.86 Direct Temporal+RC 28 34.81 40.27 40.58 5413.23 32 31.96 38.83 38.98 2908.88 36 29.19 37.29 37.19 1317.76 40 26.92 36.00 36.00 599.77 Direct Spatial 28 34.71 40.24 40.54 5305.12 32 31.81 38.77 38.92 2845.06 36 28.97 37.24 37.16 1248.87 40 26.77 35.96 35.98 559.46 Table 2: Comparison of Direct Mode (Src6) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 34.56 39.13 40.34 5610.23 32 31.80 37.79 38.93 3325.33 36 29.19 36.37 37.38 1844.75 40 26.85 35.33 36.21 997.86 Direct Temporal+RC 28 34.56 39.13 40.34 5608.78 32 31.80 37.79 38.93 3325.26 36 29.19 36.37 37.38 1845.16 40 26.85 35.33 36.21 998.01 Direct Spatial 28 34.49 39.11 40.33 5517.30 32 31.68 37.76 38.90 3251.83 36 29.01 36.34 37.34 1789.57 40 Table 3: Comparison of Direct Mode (Src9) 3.2 SDTV (525) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 33.08 35.49 35.70 4365.63 32 30.14 33.82 33.90 2393.90 36 27.28 32.11 32.07 1306.38 40 24.63 30.96 30.78 750.03 Direct Temporal+RC 28 33.09 35.49 35.70 4374.32 32 30.15 33.82 33.90 2401.32 36 27.28 32.11 32.07 1310.58 40 24.63 30.96 30.78 751.00 Direct Spatial 28 32.99 35.47 35.65 4156.86 32 30.04 33.82 33.86 2264.49 36 27.19 32.12 32.05 1242.95 40 24.51 30.97 30.77 709.88 Table 4: Comparison of Direct Mode (Src15) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 35.54 39.15 40.13 3146.03 32 33.06 37.64 38.93 1857.28 36 30.71 36.05 37.71 1052.72 40 28.72 34.66 36.82 606.74 Direct Temporal+RC 28 35.54 39.15 40.13 3146.33 32 33.06 37.64 38.93 1857.34 36 30.71 36.05 37.71 1052.75 40 28.72 34.66 36.82 606.82 Direct Spatial 28 35.45 39.12 40.12 3068.31 32 32.90 37.58 38.91 1791.58 36 30.50 35.92 37.68 1001.77 40 28.48 34.42 36.75 564.41 Table 5: Comparison of Direct Mode (Src19) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 34.09 36.31 37.37 3488.07 32 31.27 34.75 36.24 1861.70 36 28.59 33.25 35.11 973.56 40 26.14 32.17 34.29 528.94 Direct Temporal+RC 28 34.09 36.31 37.37 3490.54 32 31.27 34.75 36.24 1863.82 36 28.59 33.25 35.11 974.83 40 26.14 32.17 34.29 529.46 Direct Spatial 28 33.98 36.25 37.35 3358.12 32 31.14 34.69 36.22 1770.13 36 28.48 33.23 35.10 929.12 40 26.00 32.20 34.31 504.07 Table 6: Comparison of Direct Mode (Src22) 3.3 HDTV (720p) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 32 36 40 Direct Temporal+RC 28 36.57 41.19 42.78 2108.30 32 34.47 40.06 41.76 1041.25 36 32.60 38.86 40.51 544.53 40 30.76 37.95 39.61 305.09 Direct Spatial 28 36.57 41.22 42.80 2085.01 32 34.44 40.08 41.77 1050.62 36 32.53 38.87 40.52 549.02 40 30.71 37.96 39.61 304.93 Table 6: Comparison of Direct Mode (BigShips: 720p Frame mode) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 32 36 40 Direct Temporal+RC 28 38.64 44.66 44.70 1679.66 32 36.98 43.31 43.16 867.33 36 35.32 41.63 41.29 478.77 40 33.49 40.26 39.92 280.37 Direct Spatial 28 38.60 44.64 44.70 1623.43 32 38.91 43.27 43.14 851.02 36 40 Table 6: Comparison of Direct Mode (Crew: 720p Frame mode) 3.4 SDTV (625: MBAFF) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 35.49 40.61 41.09 4329.32 32 32.60 39.28 39.64 2573.08 36 29.71 37.83 38.08 1374.93 40 Direct Temporal+RC 28 35.49 40.61 41.08 4329.29 32 36 40 Direct Spatial 28 32 36 40 Table 7: Comparison of Direct Mode (Src5: MBAFF) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 34.79 40.26 40.60 5107.34 32 31.95 38.83 38.98 2690.42 36 29.25 37.33 37.23 1236.63 40 Direct Temporal+RC 28 34.80 40.27 40.59 5098.34 32 31.95 38.83 38.98 2695.19 36 40 Direct Spatial 28 32 36 40 Table 8: Comparison of Direct Mode (Src6: MBAFF) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 34.55 39.07 40.26 5497.53 32 36 40 Direct Temporal+RC 28 32 36 40 Direct Spatial 28 32 36 40 Table 8: Comparison of Direct Mode (Src9: MBAFF) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 33.35 36.01 36.24 4012.75 32 36 40 Direct Temporal+RC 28 33.35 36.01 36.25 4015.76 32 30.45 34.36 34.47 2199.21 36 27.63 32.69 32.68 1205.23 40 Direct Spatial 28 33.27 35.98 36.21 3841.40 32 30.39 34.35 34.44 2113.84 36 27.60 32.69 32.66 1176.61 40 24.95 31.56 31.42 684.87 Table 8: Comparison of Direct Mode (Src15: MBAFF) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 32 36 40 Direct Temporal+RC 28 35.51 39.10 40.09 3079.30 32 32.99 37.55 38.87 1795.87 36 30.61 35.91 37.66 992.89 40 28.60 34.49 36.77 557.16 Direct Spatial 28 35.45 39.09 40.10 3015.34 32 32.88 37.52 38.86 1744.17 36 30.46 35.82 37.64 956.68 40 28.42 34.33 36.71 529.47 Table 8: Comparison of Direct Mode (Src19: MBAFF) QP SNRY (db) SNR Cb (db) SNR Cr (db) Bitrate (kbps) Direct Temporal 28 32 36 40 Direct Temporal+RC 28 34.44 36.94 37.99 2997.12 32 31.81 35.54 36.94 1588.15 36 40 Direct Spatial 28 32 36 40 Table 8: Comparison of Direct Mode (Src22: MBAFF) BDSNR (db) BD Bitrate (%) Src5 Src6 Src9 Src15 Src 19 Src22 Table 11: BD SNR & BD Bitrate (Temporal+RC over Temporal) BDSNR (db) BD Bitrate (%) Src5 Src6 Src9 Src15 0.163 -3.344 Src 19 Src22 Table 11: BD SNR & BD Bitrate (Spatial over Temporal) Comparison of Direct Mode (Src6, Field Coding) Bit Rate (kbps) 0 1000 2000 3000 4000 5000 6000 PSNR (db) 26.0 26.5 27.0 27.5 28.0 28.5 29.0 29.5 30.0 30.5 31.0 31.5 32.0 32.5 33.0 33.5 34.0 34.5 35.0 35.5 Temporal RC Spatial Temporal (JM50) Comparison of Direct Mode (Src15, Field Coding) Bit Rate (kbps) 0 1000 2000 3000 4000 5000 PSNR (db) 24.0 24.5 25.0 25.5 26.0 26.5 27.0 27.5 28.0 28.5 29.0 29.5 30.0 30.5 31.0 31.5 32.0 32.5 33.0 33.5 34.0 Temporal RC Spatial Temporal (JM50) EMBED SigmaPlotGraphicObject.5 Comparison of Direct Mode (Src19, Field Coding) Bit Rate (kbps) 0 500 1000 1500 2000 2500 3000 3500 PSNR (db) 28.0 28.5 29.0 29.5 30.0 30.5 31.0 31.5 32.0 32.5 33.0 33.5 34.0 34.5 35.0 35.5 36.0 Temporal RC Spatial Temporal (JM50) Comparison of Direct Mode (Src22, Field Coding) Bit Rate (kbps) 0 500 1000 1500 2000 2500 3000 3500 4000 PSNR (db) 25.5 26.0 26.5 27.0 27.5 28.0 28.5 29.0 29.5 30.0 30.5 31.0 31.5 32.0 32.5 33.0 33.5 34.0 34.5 Temporal RC Spatial Temporal (JM50) 4.
Language:English
Score: 426721.44 - https://www.itu.int/wftp3/av-a...ite/2002_12_Awaji/JVT-F065.doc
Data Source: un
Microsoft PowerPoint - HU Sofia Regulatory.ppt ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Regulatory framework for 3G mobile communications in the EU Jean Piquemal Special Advisor Information Society Department ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France The new regulatory package Services Directive (90/388/EEC)Services Directive (90/388/EEC) extended to: Satellite (94/46/EC)extended to: Satellite (94/46/EC) Cable (95/51/EC)Cable (95/51/EC) Mobile (96/2/EC)Mobile (96/2/EC) Full Competition (96/19/EC)Full Competition (96/19/EC) Cable Ownership (1999/64/EC)Cable Ownership (1999/64/EC) ONP Framework Directive (90/387/EECONP Framework Directive (90/387/EEC amended by 97/51/EC)amended by 97/51/EC) Licensing Directive (97/13/EC)Licensing Directive (97/13/EC) GSM Directive (87/372/EEC)GSM Directive (87/372/EEC) ERMES Directive (90/544/EC)ERMES Directive (90/544/EC) DECT Directive (91/287/EEC)DECT Directive (91/287/EEC) SS--PCS Decision (97/710/EC)PCS Decision (97/710/EC) UMTS Decision (99/128/EC)UMTS Decision (99/128/EC) European Emergency Number Decision (91/396/EC)European Emergency Number Decision (91/396/EC) International Access Code Decision (92/264/EEC)International Access Code Decision (92/264/EEC) ONP Leased Lines Directive (92/44/EECONP Leased Lines Directive (92/44/EEC amended by 97/51/EC)amended by 97/51/EC) TV Standards Directive (95/47/EC)TV Standards Directive (95/47/EC) Interconnection Directive (97/33/ ECInterconnection Directive (97/33/ EC amended by 98/61/EC)amended by 98/61/EC) Voice Telephony Directive (98/10/EC)Voice Telephony Directive (98/10/EC) TelecomsTelecoms Data Protection Directive (97/66/EC)Data Protection Directive (97/66/EC) Liberalisation DirectiveLiberalisation Directive Framework DirectiveFramework Directive Authorisation DirectiveAuthorisation Directive Access & InterconnectionAccess & Interconnection Directive Directive Universal Service & Users’ Universal Service & Users’ Rights DirectiveRights Directive Data Protection DirectiveData Protection Directive Spectrum DecisionSpectrum Decision ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France New regulatory framework • Licensing Directive replaced by new Authorisation Directive, to be transposed into national law and applicable in all Member States as from 24 July 2003 • UMTS Decision will expire on 22 January 2003 pursuant to the ‘sunset clause’ described in Art. 14 • The European Commission has not proposed an extension of the UMTS Decision to the European Parliament and Council ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Timeline: new regulatory package Entry into force on 24 April 2002 Application in all Member States as from 24 July 2003 Member States transpose, but do not apply NRAs carry out market analyses 15 months ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France New Committees and Groups • Communications Committee – Established by the Framework Directive – Advisory and regulatory roles • Radio Spectrum Committee – Established by the Spectrum Decision – Advisory and regulatory roles • European Regulators Group – Created by a separate Commission Decision (29 July 2002 ) – Aim: seek consistent application of rules in all Member States • Radio Spectrum Policy Group – Created by a separate Commission Decision (26 July 2002) – Advisory role ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France UMTS Decision: purpose Decision No 128/1999/EC of 14 December 1998 • Art 1: The aim of this decision shall be to facilitate the rapid and coordinated introduction of compatible UMTS networks and services in the Community on the basis of internal market principles and in accordance with commercial demand ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France UMTS Decision: actions • Art 3.1: Member States shall take all actions necessary in order to allow the coordinated and progressive introduction of UMTS services on their territory by 1st January 2002 at the latest and in particular shall establish an authorisation system for UMTS no later than 1st January 2000 • Art 3.3: Member States shall ensure that the provision of UMTS is organised in frequency bands harmonised by CEPT and pursuant to European standards approved or developed by ETSI. (...) Fourteen of these licenses were secured by new entrants Not all 3G licenses offered in Belgium, France, Greece, Ireland and Luxembourg have been assigned ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Licensing Directive Directive 97/13/EC of 10 April 1997 • Art.10.1: Member States may limit the number of individual licences for any category of telecom services and for the establishment and/or operation of telecommunications infrastructure, only to the extent required to ensure the efficient use of radio frequencies … • Art.10.3: Member States shall grant such individual licences on the basis of selection criteria which must be objective, non- discriminatory, detailed, transparent and proportionate. Any such selection must give due weight to the need to facilitate the development of competition and to maximize benefits for users ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Licensing Directive (continued) • The Licensing Directive and the UMTS Decision provided the legal basis for the 3G licensing process ….. but it was up to the national administrations and regulatory authorities to establish their own licensing approach • Recital 2: … recognizes as a key factor for this regulatory framework in the Union the establishment, in accordance with the principle of subsidiarity, of common principles for general authorisations and individual licensing regimes in the Member States … ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Timing of 3G licensing in the EU15 99 00 01 02 AFIN E B DK S FD EL IRL I LUX NL P UK There has been a significant change of financial environment and market conditions over the 3G licensing period 11 ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Community legislation set out principles, but did not impose specific licensing methods Differences in payment approaches Both auctions and comparative bidding (beauty contest) are compatible with EU legislation Method of 3G licensing in the EU 15Method of 3G licensing in the EU 15 4 8 3 comparative bidding auction without payment with payment ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Method for 3G licensing • The Licensing Directive set out principles, but did not impose specific licensing methods • Auctions and comparative bidding (beauty contest) were compatible with EU legislation – Auctions in eight Member States – Comparative bidding in seven Member States • Schedule of payments and the form of bidding have differed among Member States ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Regulatory fragmentation method of licensing: beauty contest vs. auctions timing of licensing number of licenses; new entrants license duration (15-20 years) deployment obligations sharing / access conditions (national roaming) spectrum assignment: 10 or 15 MHz FDD + 5 MHz TDD cost of licenses ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Outstanding issues • 3G licensing issues and radio spectrum aspects e.g. additional IMT-2000 frequency bands in the 2500- 2690 MHz range will continue to be relevant beyond the expiry date of the UMTS Decision • Outstanding issues will be dealt with in the context of the new regulatory framework within the recently established Committees and Groups ITU-BDT Seminar on Network Evolution, Sofia, Bulgaria, 21-24 January 2003Ministry of Industry - France Accession and candidate countries • Poland, Slovenia, Czech Republic and Slovakia: have issued 3G licenses • Estonia and Latvia: preparing to invite bids for 3G licenses in the near future • Hungary, Lithuania, Cyprus and Malta: have not yet decided on a course of action • Romania: preparing to invite bids for 3G licenses in the near future • Bulgaria and Turkey: have not yet decided on a course of action
Language:English
Score: 426528.5 - https://www.itu.int/ITU-D/tech.../3-3_Part2-HU%20Regulatory.pdf
Data Source: un
Common-Information-Operations (H.450.12:07/2001) -- Module Common-Information-Operations (H.450.12:07/2001) -- See also ITU-T H.450.12 (07/2001) -- See also the index of all ASN.1 assignments needed in this document Common-Information-Operations {itu-t recommendation h 450 12 version1(0) common-information-operations(0)} DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS OPERATION, ERROR FROM Remote-Operations-Information-Objects {joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} EXTENSION, Extension{} FROM Manufacturer-specific-service-extension-definition {itu-t recommendation h 450 1 version1(0) msi-definition(18)} MixedExtension, undefined FROM Call-Hold-Operations {itu-t recommendation h 450 4 version1(0) call-hold-operations(0)}; H323CommonInformationOperations OPERATION ::= { cmnRequest | cmnInform } cmnRequest OPERATION ::= { ARGUMENT DummyArg OPTIONAL TRUE RESULT CmnArg ERRORS { undefined } CODE local:84 } cmnInform OPERATION ::= { ARGUMENT CmnArg RETURN RESULT FALSE ALWAYS RESPONDS FALSE CODE local:85 } CmnArg ::= SEQUENCE { featureList FeatureList OPTIONAL , featureValues FeatureValues OPTIONAL , featureControl FeatureControl OPTIONAL , extension SEQUENCE SIZE (0..255) OF MixedExtension OPTIONAL , ... } DummyArg ::= SEQUENCE { extensionArg SEQUENCE SIZE (0..255) OF MixedExtension OPTIONAL } FeatureList ::= SEQUENCE { -- indicates capabilities of the endpoint sending the FeatureList ssCFreRoutingSupported NULL OPTIONAL , -- Call Forwarding rerouting -- supported meaningful only in -- forward direction during call -- establishment ssCTreRoutingSupported NULL OPTIONAL , -- Call Transfer rerouting -- supported meaningful both in -- forward & backward direction -- during call establishment ssCCBSPossible NULL OPTIONAL , -- CCBS possible meaningful only -- in backward direction before -- receipt of ALERTING/CONNECT ssCCNRPossible NULL OPTIONAL , -- CCNR possible meaningful only -- in backward direction before -- receipt of CONNECT ssCOSupported NULL OPTIONAL , -- Call Offer supported -- meaningful only in backward -- direction during call -- establishment -- Call Intrusion ssCIForcedReleaseSupported NULL OPTIONAL , -- meaningful only in -- backward direction ssCIIsolationSupported NULL OPTIONAL , -- meaningful only in -- backward direction ssCIWaitOnBusySupported NULL OPTIONAL , -- meaningful only in -- backward direction ssCISilentMonitoringSupported NULL OPTIONAL , -- meaningful only in -- backward direction ssCIConferenceSupported NULL OPTIONAL , -- meaningful only in -- backward direction -- Call Hold ssCHFarHoldSupported NULL OPTIONAL , -- meaningful in both -- directions -- Message Waiting Callback ssMWICallbackSupported NULL OPTIONAL , -- meaningful in backward -- direction -- meaningful both in -- forward & backward -- direction during call -- establishment -- Call Park ssCPCallParkSupported NULL OPTIONAL , -- meaningful in both -- directions ... } FeatureValues ::= SEQUENCE { partyCategory PartyCategory OPTIONAL , ssCIprotectionLevel SSCIProtectionLevel OPTIONAL , -- Supplementary Service Call Intrusion Protection level -- meaningful both in forward and backward direction; inclusion -- indicates support of SS-CI as an unwanted endpoint (forward -- direction) or as a Terminating Endpoint (backward direction), -- as well as the applicable protection level. ... } PartyCategory ::= ENUMERATED {unknown, extension, attendant, emergExt, ... } SSCIProtectionLevel ::= INTEGER (0..3) FeatureControl ::= SEQUENCE { ssCHDoNotHold NULL OPTIONAL , -- meaningful in both directions -- Sending endpoint shall not be held ssCTDoNotTransfer NULL OPTIONAL , -- meaningful in both directions -- sending endpoint shall not be transferred ssMWICallbackCall NULL OPTIONAL , -- meaningful only in SETUP -- indicating a callback call ssCISilentMonitorPermitted NULL OPTIONAL , -- unwanted endpoint -- allows for -- silent monitoring -- meaningful in forward and backward direction ... } END -- of Common-Information-Operations -- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
Language:English
Score: 426469.8 - https://www.itu.int/wftp3/Publ...on-Information-Operations.html
Data Source: un
Member States had to adopt these Directives into their own laws by July 24, 2003. Framework Directive. (...) These obligations are carried over from the current regulatory framework. Universal Service Directive. The Universal Service Directive replaces the existing directive on voice telephony and universal services. The Directive also contains rules on number portability, carrier selection and carrier pre-selection which are currently in the Interconnection Directive.
Language:English
Score: 426034.77 - https://www.itu.int/ITU-D/tech...%201/NairobiAbstract_1_2_3.pdf
Data Source: un
Convention Effective ratifications: Further information Convention No. 161 33 effective ratifications (0 denunciations)  Last ratification: 2016 (Côte d’Ivoire)  Ratification by dates: 1986-1996: 15 ratifications; 1997-2016: 18 ratifications 16 Ibid, p. 21. 17Ibid, pp.21-22. 18 Ibid, p. 21. 19 Meeting of Experts on Workers’ Health Surveillance, MEHS/1997/3. http://staging.ilo.org/public/libdoc/ilo/1997/97B09_222_engl.pdf Third meeting of the SRM tripartite working group (25-29 September 2017) TECHNICAL NOTE 1 7  Ratification by region: Europe and Central Asia: 19 ratifications;20 Africa: 7 ratifications;21 Americas: 7 ratifications.22 (2) Information concerning the implementation of Convention No. 161 Currently, there are 34 pending comments by the Committee of Experts in relation to the application of Convention No. 161 by member States, including 11 observations made by employers’ and workers’ organizations.23 The major recurrent issues in Committee of Experts comments concerning the application of Convention No. 161 include:  National policy: including its formulation, implementation and periodic review (Article 2);24 the progressive development of occupational health services for all workers (Article 3);25 and the role of the most representative organizations of employers and workers (Article 4);26  Functions of services (Article 5), including the identification and assessment of risks in the workplace;27 and participation in the analysis of occupational accidents and diseases;28  Organization of occupational health services, including bipartite cooperation in implementation (Article 8);29 20 Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Czech Republic, Finland, Germany, Hungary, Luxembourg, Montenegro, Poland, San Marino, Serbia, Slovakia, Slovenia, Sweden, The former Yugoslav Republic of Macedonia, Turkey, and Ukraine. 21 Benin, Burkina Faso, Côte d'Ivoire, Gabon, Niger, Seychelles, and Zimbabwe. 22 Antigua and Barbuda, Brazil, Chile, Colombia, Guatemala, Mexico, and Uruguay. 23 Burkina Faso, direct request published in 2016; Colombia, direct request published in 2016; Croatia, direct request published in 2017; Czech Republic, direct request published in 2017; Finland, direct request published in 2017; Germany, direct request published in 2017; Guatemala, direct request published in 2016; Poland, direct request published in 2015; Serbia, direct request published in 2016; Sweden, direct request published in 2015; and Turkey, observation and direct request published in 2017. 24 Turkey, observation published in 2017. 25 For example, Benin, direct request published in 2017; Bulgaria, direct request published in 2016; Burkina Faso, direct request published in 2016; Colombia, direct request published in 2016; Finland, direct request published in 2017; Guatemala, direct request published in 2016; Niger, direct request published in 2017; Poland, direct request published in 2015; Serbia, direct request published in 2016; Turkey, observation and direct request published in 2017; and Ukraine, direct request published in 2016. 26 For example, Colombia, direct request published in 2016; Guatemala, direct request published in 2016; Niger, direct request published in 2017; Serbia, direct request published in 2016; Turkey, observation and direct request published in 2017; and Ukraine, direct request published in 2016. 27 For example, Benin, direct request published in 2017; Burkina Faso, direct request published in 2016; and Czech Republic, direct request published in 2017. 28 Benin, direct request published in 2017; Bulgaria, direct request published in 2016; Burkina Faso, direct request published in 2016. 29 Bulgaria, direct request published in 2016; Niger, direct request published in 2017; Luxembourg, direct request published in 2015; Montenegro, direct request published in 2015; Seychelles, direct request published in 2015; Slovenia, direct request published in 2015; Turkey, observation and direct request published in 2017; Ukraine, direct request published in 2016; and Zimbabwe, direct request published in 2015. (...) Without a national policy and a general vision of OSH for which reliable data is necessary, the 30 For example, Bulgaria, direct request published in 2016; Burkina Faso, direct request published in 2016; Colombia, direct request published in 2016; Niger, direct request published in 2017; Turkey, observation and direct request published in 2017; Ukraine, direct request published in 2016. 31 Benin, direct request published in 2017; Bulgaria, direct request published in 2016; Burkina Faso, direct request published in 2016; Colombia, direct request published in 2016; Seychelles, direct request published in 2015; The former Republic of Macedonia, direct request published in 2015; Ukraine, direct request published in 2016; and Zimbabwe, direct request published in 2015. 32 Burkina Faso, direct request published in 2016; Niger, direct request published in 2017; Turkey, observation and direct request published in 2017; and Zimbabwe, direct request published in 2015. 33 Bulgaria, direct request published in 2016; Burkina Faso, direct request published in 2016; Colombia, direct request published in 2016; Serbia, direct request published in 2016; Ukraine, direct request published in 2016; Montenegro, direct request published in 2015; Slovenia, direct request published in 2015; The former Republic of Macedonia, direct request published in 2015; and Zimbabwe, direct request published in 2015. 34 Burkina Faso, direct request published in 2016; Niger, direct request published in 2017; Turkey, observation and direct request published in 2017; and Zimbabwe, direct request published in 2015. 35 See ILO: Report of the Committee set up to examine the representation made by the Inter-Union Assembly of Workers-National Convention of Workers (PIT-CNT) and its affiliated organization, the National Single Trade Union in Construction and Similar Activities (SUNCA) under article 24 of the ILO Constitution alleging non- observance by Uruguay of the Safety Provisions (Building) Convention, 1937 (No. 62), the Labour Inspection Convention, 1947 (No. 81), the Labour Administration Convention, 1978 (No. 150), the Occupational Safety and Health Convention, 1981 (No. 155), and the Occupational Health Services Convention, 1985 (No. 161), Governing Body, 267th Session, Geneva, Nov. 1996, GB.267/15/4. http://www.ilo.org/dyn/normlex/en/f?
Language:English
Score: 425883.6 - www.ilo.org/wcmsp5/grou...enericdocument/wcms_569988.pdf
Data Source: un
The number of casualties will depend not only on weather conditions such as wind speed and direction but also on population density and on the effectiveness of arrangements for evacuation. (...) Third meeting of the SRM tripartite working group (25-29 September 2017) TECHNICAL NOTE 6 6 (2) Information concerning the implementation of Convention No. 174 Currently, there are 18 pending comments by the Committee of Experts in relation to the application of Convention No. 174, concerning 17 of the 18 ratifying member States.11 The following main themes recur with regard to the implementation of Convention No. 174:  Insufficient information on compliance with the obligation of exporting states to provide information to importing states on the prohibition of the use of hazardous substances, technologies or processes as a potential source of a major accident (Article 22);12  National policy, including its formulation, implementation and periodic review (Article 4);13  System for the identification of major hazard installations (Article 5);14  Protection of confidential information (Article 6);15  Responsibilities of employers in relation to a documented system of major hazard control (Article 9);16 the provision of safety reports (Articles 10 and 11);17 and notification of major installations;18  Responsibilities of competent authorities in relation to off-site emergency preparedness (Articles 15 and 16)19 and siting policies (Article 17);20 11 Finland is the only ratifying State for which no comment is pending. 12 Belgium, direct request published in 2011; India, direct request published in 2016; Russian Federation, direct request published in 2016; Saudi Arabia, direct request published in 2015; Ukraine, direct request published in 2016; and Zimbabwe, direct request published in 2015. 13 Albania, direct request published in 2016; Bosnia and Herzegovina, direct request published in 2013; Brazil direct request published in 2016; Colombia, observation and direct request published in 2014; India, direct request published in 2016; Netherlands, direct request published in 2015; Saudi Arabia, direct request published in 2015; Slovenia, direct request published in 2015; Ukraine, direct request published in 2016. 14 Brazil, direct request published in 2016; Colombia, observation and direct request published in 2014; Estonia, direct request published in 2011; Russian Federation, direct request published in 2016; Saudi Arabia, direct request published in 2015; Ukraine, direct request published in 2016; Zimbabwe, direct request published in 2015. 15 Brazil, direct request published in 2016; Colombia, observation and direct request published in 2014; Estonia, direct request published in 2011; Saudi Arabia, direct request published in 2015; Ukraine, direct request published in 2016. 16 Armenia, direct request published in 2014; Brazil, direct request published in 2016; Colombia, observation and direct request published in 2014; Russian Federation, direct request published in 2016; Ukraine, direct request published in 2016; Zimbabwe, direct request published in 2015. 17 Armenia, direct request published in 2014; Colombia, observation and direct request published in 2014; Saudi Arabia, direct request published in 2015; Slovenia, direct request published in 2015; Ukraine, direct request published in 2016; Zimbabwe, direct request published in 2015. 18 Colombia, observation and direct request published in 2014; Russian Federation, direct request published in 2016; Saudi Arabia, direct request published in 2015; Zimbabwe, direct request published in 2015. 19 Armenia, direct request published in 2014; Netherlands, direct request published in 2015; Russian Federation, direct request published in 2016; Saudi Arabia, direct request published in 2015; Zimbabwe, direct request published in 2015. 20 Brazil, direct request published in 2016; Colombia, observation and direct request published in 2014; Netherlands, direct request published in 2015; Russian Federation, direct request published in 2016; Zimbabwe, direct request published in 2015. (...) Consequently, a proposal was made to examine ways to fulfill this obligation in practice and to consider a partial revision of the Convention in relation to this particular issue to remove obstacles to ratification and application in practice.23  The Rotterdam Convention on the Prior Informed Consent Procedure for Certain Hazardous Chemicals and Pesticides in International Trade, 1998 contains more far- reaching information and other requirements of exporting states in relation to hazardous chemicals and pesticides (such as labelling), and requires the designation of national authorities to act on the behalf of Governments in the performance of the administrative functions required by the Convention.24  Conventions Nos 174 and 170 both deal with chemicals, requiring a certain amount of consistency between the instruments. 21 Colombia, observation and direct request published in 2014; Estonia, direct request published in 2011; India, direct request published in 2016; Russian Federation, direct request published in 2016; Saudi Arabia, direct request published in 2015; Ukraine, direct request published in 2016; Zimbabwe, direct request published in 2015. 22 For example, Article 11 requires employers to review, update and amend safety reports concerning the control of major hazards, “when developments in technical knowledge or in the assessment of hazards make this appropriate.” 23 ILO: ILO standards-related activities in the area of OSH: An in-depth study for discussion, Report VI, International Labour Conference, 91st Session, Geneva, 2003, paras. 39, 158, 167 and 168. 24 The Rotterdam Convention on the Prior Informed Consent Procedure for Certain Hazardous Chemicals and Pesticides in International Trade, 1998 (entered into force in 2004, last revised in 2015). http://www.pic.int/TheConvention/Overview/tabid/1044/language/en-US/Default.aspx http://www.pic.int/TheConvention/Overview/tabid/1044/language/en-US/Default.aspx http://www.ilo.org/public/english/standards/relm/ilc/ilc91/pdf/rep-vi.pdf http://www.ilo.org/public/english/standards/relm/ilc/ilc91/pdf/rep-vi.pdf http://www.pic.int/TheConvention/Overview/TextoftheConvention/tabid/1048/language/en-US/Default.aspx http://www.pic.int/TheConvention/Overview/TextoftheConvention/tabid/1048/language/en-US/Default.aspx Third meeting of the SRM tripartite working group (25-29 September 2017) TECHNICAL NOTE 6 8 Possible action to be considered in relation to Convention No. 174 and Recommendation No. 181 Convention No. 174 and Recommendation No. 181 reflect the modern policy-oriented and risk- assessment approach to OSH, recognising the role of employers and workers in managing OSH systems in the enterprise,25 and first established by Convention No. 155 in 1981 and reaffirmed more recently with the adoption of Convention No 187.
Language:English
Score: 425861.6 - www.ilo.org/wcmsp5/grou...enericdocument/wcms_569993.pdf
Data Source: un
Videomux mode in bi-directional video communication Separate logical channel mode in bi-directional video communication Separate logical channel mode in uni-directional video communication Videomux mode in bi-directional video communication The logical channels for the video communication are opened as bi-directional logical channels with H.223 AL3. (...) EMBED Word.Picture.6 Figure 1 Scenario-1 Separate logical Channel Mode in bi-directional Video Communication The logical channels for the video communication, LC1 and LC2, are first opened as bi-directional logical channels with H.223 AL3. (...) In the case where H.263 Annex N video backchannel messages are carried on a separate logical channel, the procedure to set up the logical channel for the video backward channel messages is different depending on whether the video communication is uni-directional or bi-directional. In case of bi-directional video communication, the logical channels for original video data shall first be opened as bi-directional logical channels which should support H.223 AL3.
Language:English
Score: 425640.04 - https://www.itu.int/wftp3/av-a...video-site/9706_Por/q15a29.doc
Data Source: un
Direction of the Central Bank of Russia No. 591-U of June 28, 1999 introduced amendments to Item 1 of the present Direction See previous text of the Item 1. (...) The purchase order drawn up in compliance with the requirements of Direction of the Bank of Russia No. 383-U of October 20, 1998 and Item 3 of the present Direction should contain a provision for the obligatory transfer of the sum specified in Item 3.2 of the present Direction to the deposit account and also a provision for the return of the specified sum according to the procedure specified in Item 3.3 of the present Direction. 5. The present Direction shall come into effect from the moment of its signing and shall be published in the "Vestnik Banka Rossii" journal.
Language:English
Score: 425543.6 - https://www.wto.org/english/th...c_e/rus_e/WTACCRUS48_LEG_2.pdf
Data Source: un