Home

Results 81 - 90 of 507,829 for extensive selection. Search took 3.48 seconds.  
Sort by date/Sort by relevance
It is targeted at middle-level fishery and environment officers, extension workers, facilitators [...] Ecosystem approach to fisheries management training course (Inland fisheries) Volume 2: Inland fishery case studies Global Year: 2019 This Ecosystem Approach to Fisheries management training course (Inland Fisheries) is designed as a complete training course for the sustainable management of inland fisheries using the ecosystem approach. (...) It is targeted at middle-level fishery and environment officers, extension workers, facilitators [...] Ecosystem approach to fisheries management training course (Inland fisheries) – Volume 4: Training session plans Global Year: 2019 This Ecosystem Approach to Fisheries management training course (Inland Fisheries) is designed as a complete training course for the sustainable management of inland fisheries using the ecosystem approach. It is targeted at middle-level fishery and environment officers, extension workers, facilitators [...] Building capacity for mainstreaming fisheries co-management in Indonesia.
Language:English
Score: 855889.2 - https://www.fao.org/inland-fisheries/tools/training/ru/
Data Source: un
., N − 1 and Z0 = 0, shall be further augmented so that the vector Zi has a Hermitian symmetry: Z i  conj ( Z 2N i ) for  Ni  1 to 2 N  1 10.4.4 Cyclic extension and windowing The cyclic extension provides a guard interval between adjacent symbols. This guard interval is intended to protect against inter-symbol interference. The cyclic extension also adds windowing that is necessary for spectrum shaping. (...) Therefore, the total number of samples transmitted per each symbol period, after cyclic extension and windowing, is 2N+ LCP. The values of β selected for upstream (βus) and downstream (βds) may be different.
Language:English
Score: 855464.5 - https://www.itu.int/en/publica.../files/basic-html/page800.html
Data Source: un
., for test purposes • Solution: • ECN can be used to fill the gap between message content definitions and message encoding • Forces: • Separation of abstract message contents and auxiliary information • Specification of presence and length determinants • Complex message encoding => complex ECN HiperlanHiperlan exampleexample • Purpose of the example: • Show how messages that are originally specified using tables can be specified using ASN.1 and ECN • Real-life Hiperlan protocol: • Existing ASN.1 definitions • Existing tables for message encoding • RLC-RADIO-HANDOVER-COMPLETE-ARG used as an example message Hiperlan Hiperlan -- Message table formMessage table form 8 7 6 5 4 3 2 1 Octet 1 Defined in DLC TS MSB Sequence number Octet 2 Sequence number MSB EXTENSION-TYPE Future use Octet 3 MSB RLC LCH PDU type Octet 4 Future use mac-id-old Octet 5 mac-id-old ap-id-old Octet 6 ap-id-old net-id-old Octet 7 net-id-old Octet 8 mac-id-new Octet 9 cl-id Octet 10 Duc-ext-ind cl-conn-attr-length(L) # of DUC:s Octet 11 # of DUC:s(N) Future use Octet12 (DUC1) direction dlcc-id Octet(12+L) cl-connn-attr Octet Y (DUC1-FW) allocation-type Future use cyclic-prefix fec-used ec-mode Octet ... (...) &encoding-space-size : nbits >} #INT ::= { ENCODING { ENCODING-SPACE SIZE nbits } } Collection of encodingsCollection of encodings • Encoding definitions are collected as an encoding object set Hiperlan-Encodings #ENCODINGS ::= { rlc-radio-handover-complete-arg-encoding | duc-direction-descr-encoding | allocation-type-encoding | arq-data-encoding | fec-encoding | fca-descr-encoding } Hiperlan Hiperlan -- ELMELM • Encodings are applied to top-level types in the ASN.1 module Hiperlan-ELM LINK-DEFINITIONS ::= BEGIN IMPORTS #RLC-RADIO-HANDOVER-COMPLETE-ARG FROM Hiperlan-ASN1 Hiperlan-Encodings FROM Hiperlan-EDM; ENCODE #RLC-RADIO-HANDOVER-COMPLETE-ARG WITH Hiperlan-Encodings COMPLETED BY PER-BASIC-UNALIGNED END HiperlanHiperlan example summaryexample summary • Application of ASN.1 + ECN for Hiperlan is straightforward • ASN.1 definitions shall contain only application-specific definitions • Encoding structures contain also auxiliary fields like length and presence determinants • Encoding objects • specify relations between determinant fields and determined fields • specify special encoding (octet-alignment, padding, spare bits) • The encoding link module applies the encoding objects to the ASN.1 types ECN and specializationECN and specialization • Context: • Protocol messages are defined using ASN.1 • Standard ASN.1 encoding rules (e.g., PER) are used to provide encoding for messages • Problem: • Standard encoding rules do not provide all the needed properties for encoding • Solution: • Use standard encoding rules for the majority of encodings • Use ECN to specialize encoding for wanted properties • Forces: • A kind of specialization vs. a generic property Specialization of CHOICE index encodingSpecialization of CHOICE index encoding • Context: • There is a top-level message container type which encapsulates specific messages and provides identification for them Messages ::= CHOICE { a MessageA, b MessageB, c MessageC } • Problem: • New messages are wanted to be added in the container. • Encoding for the new messages should be similar to the old messages, i.e., no extension container is needed. • The number of new messages is not limited • Solution: • Encode CHOICE index using a Huffman-like encoding Specialization of CHOICE index encodingSpecialization of CHOICE index encoding • The following encoding object specifies that the encoding structure for the Messages type consists of • an "aux-messageId" field, which is used as a message determinant • a "message" field, which contains the selected message messages-encoding #Messages ::= { REPLACE STRUCTURE WITH #Messages-struct{< >} ENCODED BYmessages-struct-encoding{< >} } #Messages-struct{< #OriginalMessages >} ::= #SEQUENCE { aux-msgId #MessageIdentifier, message #OriginalMessages } #MessageIdentifier ::= #INT Specialization of CHOICE index encodingSpecialization of CHOICE index encoding • The following encoding object specifies how the fields are encoded • "aux-msgId" field is encoded as an open-ended integer field • "aux-msgId" acts as a determinant for the "message" field messages-struct-encoding{<#OriginalMessages>} #Messages-struct{<#OriginalMessages>} ::= { ENCODE STRUCTURE { aux-msgId msgId-encoding, message { ALTERNATIVE DETERMINED BY added-field USING aux-msgId } } WITH PER-BASIC-UNALIGNED } msgId-encoding #MessageIdentifier ::= { USE #BITS MAPPING TO BITS { 0 .. 2 TO ‘000’B .. ‘010’B, -- 0 - MessageA, 1 - MessageB, 2 - MessageC 3 TO ‘1’B -- 3 - Extensions, like 10000, 10001, 10010 etc } WITH self-delimiting-bits } Length determinant forLength determinant for SEQUENCEsSEQUENCEs • Context: • There is a group of SEQUENCE types which need to be extensible MessageA ::= SEQUENCE { -- Whatever extensions MessageA-Extensions OPTIONAL } MessageA-Extensions ::= SEQUENCE { -- Extensible } • Problem: • The size of the encoding needs to be smaller than in case of normal PER extensibility • Solution: • Introduce a length determinant for the selected SEQUENCE types • Length of encoding of extensions is delimited by the SEQUENCE length determinant Length determinant forLength determinant for SEQUENCEsSEQUENCEs • The following generic encoding structure is used as a replacement structure for extensible SEQUENCEs #Sequence-with-length-determinant ::= #SEQUENCE • The following sequence-with-length-determinant-encoding #Sequence-with-length-determinant ::= { REPLACE STRUCTURE WITH Seq-with-length-struct{< >} ENCODEB BY seq-with-length-struct-encoding{< >} } #Seq-with-length-struct{< #OrigSequence >} ::= #SEQUENCE { aux-length #INT (0..512), seq #OrigSequence } Length determinant forLength determinant for SEQUENCEsSEQUENCEs • The following parameterized encoding object specifies that • the "aux-length" field is used as a length determinant for the "seq" field • length of "seq" field is measured in bits • otherwise the normal PER rules are used seq-with-length-struct-encoding{< #OrigSeq >} #Seq-with-length-struct{< #OrigSeq >} ::= { ENCODE STRUCTURE { -- aux-length as in PER seq { ENCODING SPACE SIZE variable-with-determinant MULTIPLE OF bit DETERMINED BY added-field USING aux-length } } WITH PER-BASIC-UNALIGNED } Length determinant forLength determinant for SEQUENCEsSEQUENCEs • The generic encoding structure and encoding object are applied for selected SEQUENCE types as follows: RENAMES #SEQUENCE AS #Sequence-with-length-determinant IN #MessageA-Extensions, #MessageB-Extensions, #MessageC-Extensions FROM Example-ASN1; • As a result the property of length determined encoding is associated with the selected SEQUENCE types • Context: • There are integer types which need to have limited extensibility • The maximum number of extensions can be predicted • It is specified what to do when a spare value is received -- Used range in version 1 is 1..224, values 225-256 are spare values. -- If a spare value is received, then the following error procedure shall be initiated... ExtensibleInteger ::= INTEGER (1..256) • Problem: • Minimize the encoding size • Make sure that senders do not send spare values Extension of value sets of INTEGER typesExtension of value sets of INTEGER types Ignore spare valuesIgnore spare values • The following encoding object specifies that • it is not allowed to send spare values but it is allowed to receive them extensibleInteger-encoding #ExtensibleInteger::= { ENCODE-DECODE { USE #INT (1..224) -- no padding bits needed MAPPING ORDERED VALUES WITH per-int-encoding } DECODE-AS-IF per-int-encoding } per-int-encoding #INTEGER ::= { ENCODE WITH PER-BASIC-UNALIGNED } Encoding object setEncoding object set • Collect encoding objects in one encoding object set MyEncodings #ENCODINGS ::= { messages-encoding | sequence-with-length-determinant-encoding | extensibleInteger-encoding } Encoding link moduleEncoding link module Example-ELM LINK-DEFNITIONS ::= BEGIN IMPORTS #Messages, -- Implicit encoding classes #ExtensibleInteger FROM Example-ASN1 #MessageA-Extensions, -- Explicitly renamed encoding classes #MessageB-Extensions, #MessageC-Extensions, MyEncodings -- Encoding object set FROM Example-EDM; ENCODE #Messages, #ExtensibleInteger, #MessageA-Extensions, #MessageB-Extensions, #MessageC-Extensions WITH MyEncodings COMPLETED BY PER-BASIC-UNALIGNED END ECN Presentation SummaryECN Presentation Summary • The basic concepts of ECN are fairly simple • Application area and wanted encoding features affect a lot of how ECN can be applied • Multiple ways to achieve the same goal • What is specified in ASN.1 and what in ECN • Generic ECN vs. specific ECN
Language:English
Score: 855030.1 - https://www.itu.int/en/ITU-T/a...ECN_Introduction_June_2001.pdf
Data Source: un
The selection committee was appointed by TER SC. The Selection Committee was composed of 7 members from Bosnia and Herzegovina, Croatia, Czech Republic, Poland, Serbia, Slovakia and Slovenia. 5. (...) With respect to the possible extension of TER data collection to the selected non-TER countries (Chapter 5.2. of the Report) which the Committee favoured, the position was taken that the final decision on that is up to these non-TER countries and that it should be materialised without additional costs to the TER Project. 14. (...) The selection committee was established composed of 7 members appointed at the session (Ms.
Language:English
Score: 854960.5 - https://unece.org/DAM/trans/do...20/TER/REPORT__45th_TER_SC.pdf
Data Source: un
Confirmed 7/12 5-8 July 2010 Lannion, France France Telecom Orange review the test results of Optimisation/Characterisation of G.711.1 & G.722 SWB extension (mono). review the test results of the Music experiment to evaluate the performance of proposed G.718 decoder-side post-processing for high frequency pitches, progress the Handbook STP, any other issues for which input contributions will be provided. Confirmed 7/12 Week 6-10 December 2010 Lannion, France France Telecom Orange review the test results of Optimisation/Characterisation of G.711.1 & G.722 SWB extension (stereo step1). draft the test plan and review the processing plan of Characterisation phase 2 of G.711.1 & G.722 SWB extension (MS stereo) progress the Handbook STP Confirmed 9/12 (joint meeting with 14/12 & 17/12) 15-17 September 2010 Berlin, Germany DT selection of detectors for P.TCA technical requirement specification of P.AMD discussion and agreement on draft Recommendation P.OLQA Confirmed 13/12 tbd tbd tbd G.OMVAS ToR and test plan G.IPTV-PMPD Other topics as necessary Planned 14/12 (joint meeting with 9/12 & 17/12) 15-17 September 2010 Berlin, Germany DT Review of P.NAMS participating parties Finalize the P.NAMS Test Plan Continue with P.NAMS selection critera Finalize P.NBAMS Requirement Specification Create the draft P.NBAMS Test Plan Draft the P.NBAMS selection criteria Send call for model submission for P.NBAMS Confirmed 17/12 (joint meeting with 9/12 & 14/12) 15-17 September 2010 Berlin, Germany DT As the highest priority, advancing the new Recommendation Y.156sam, on Ethernet Service Activation Test Methodology.
Language:English
Score: 854134.6 - https://www.itu.int/en/ITU-T/s...es/meetings-201006-201012.aspx
Data Source: un
Based on the prepared , the best BS beams are selected sequentially to increase channel capacity. (...) The beam newly turned on in ,max is selected as -th beam and excluded from beam candidates. (...) Finally, the optimal beam beam selection matrix A ⋆ selection matrix = −1, is determined. 46 © International Telecommunication Union, 2021     53     54     55     56     57     58     59     60     61     62     63          
Language:English
Score: 852749 - https://www.itu.int/en/publica...6/files/basic-html/page58.html
Data Source: un
The new procedure allows a sender to indicate the scalability structure it is using, which in turn enables a receiver to optionally select a particular operation point. 1. Introduction Annex G of H.264 [1] defines a scalable coding extension for H.264, referred to as SVC (Scalable Video Coding). (...) In [9] we further elaborated on the issues and proposed specific extensions to H.241. The central focus of the extensions was to provide profile indication support. (...) If such information (“sprop-operation-point-info” or “sprop-scalability-info”) is provided by a sender, a receiver can optionally select a particular operation point. If no such selection takes place, then the sender transmits the full SVC stream.
Language:English
Score: 852543.7 - https://www.itu.int/wftp3/av-a...e/2009-2012/1012_RTP/q1j04.doc
Data Source: un
The telephone number of FAO Headquarters is +39 06 570 + extension. If the extension is not known, dial +39 06 570 51 for the FAO switchboard operator. 24. (...) For more information, dial extension 53127 (Tel. 06-5705-3127). Medical Services 43. (...) The FAO Security Office operates from 08.00 hours to 17.00 hours from Room B062 (extension 55159); after 17.00 hours contact the Security Guards in Building A (extension 53145, 06- 570-53145 from outside FAO Headquarters).
Language:English
Score: 852499.6 - https://www.fao.org/fileadmin/...nts/PGR/ITWG/ITWG4/P4infoE.pdf
Data Source: un
Mr Selvaraju Ramasamy, Head of FAO's Research and Extension Unit , spoke about the status of agricultural extension and advisory services and their role in sustainable soil management. He explained that agricultural extension operates within a broader knowledge system, the agricultural knowledge triangle, which represents research, extension and higher agricultural education, and encouraged the need to create linkages between these institutions to promote learning and the sharing and use of knowledge at the farm level. (...) Ms Bazza presented the next steps and how the Soil Doctors programme will develop: first through the selection of promoters by the GSP, then through the selection of a community and a champion farmer/ Soil Doctor by the selected promoter, and finally through the training of other farmers in their community by the Soil Doctors.
Language:English
Score: 852329.1 - https://www.fao.org/global-soi...ighlights/detail/ar/c/1311932/
Data Source: un
Mr Selvaraju Ramasamy, Head of FAO's Research and Extension Unit , spoke about the status of agricultural extension and advisory services and their role in sustainable soil management. He explained that agricultural extension operates within a broader knowledge system, the agricultural knowledge triangle, which represents research, extension and higher agricultural education, and encouraged the need to create linkages between these institutions to promote learning and the sharing and use of knowledge at the farm level. (...) Ms Bazza presented the next steps and how the Soil Doctors programme will develop: first through the selection of promoters by the GSP, then through the selection of a community and a champion farmer/ Soil Doctor by the selected promoter, and finally through the training of other farmers in their community by the Soil Doctors.
Language:English
Score: 852329.1 - https://www.fao.org/global-soi...ighlights/detail/en/c/1311932/
Data Source: un