hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3 Response Header Formats | The response header is composed of a response line optionally followed by headers that encode the response parameters. The response line starts with the response code, which is a three-digit numeric value. The code is followed by a white space, the transaction identifier, and optional commentary preceded by a white spa... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.1 CreateConnection | In the case of a CreateConnection message, the response line is followed by a Connection-Id parameter with a successful response (code 200). A LocalConnectionDescriptor is furthermore transmitted with a positive response. The LocalConnectionDescriptor is encoded as a "session description", as defined in clause 8.4. It ... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.2 ModifyConnection | In the case of a successful ModifyConnection message, the response line is followed by a LocalConnectionDescriptor, if the modification resulted in a modification of the session parameters (e.g. changing only the mode of a connection does not alter the session parameters). The LocalConnectionDescriptor is encoded as a ... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.3 DeleteConnection | Depending on the variant of the DeleteConnection message, the response line may be followed by a Connection Parameters parameter line, as defined in clause 8.2.2.5. 250 1210 OK P: PS=1245, OS=62345, PR=780, OR=45123, PL=10, JI=27, LA=48 |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.4 NotificationRequest | A NotificationRequest response does not include any additional response parameters. |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.5 Notify | A Notify response does not include any additional response parameters. |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.6 AuditEndpoint | In the case of an AuditEndPoint the response line may be followed by information for each of the parameters requested—each parameter will appear on a separate line. Parameters for which no value currently exists will still be provided. Each local endpoint name "expanded" by a wildcard character will appear on a separat... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.7 AuditConnection | In the case of an AuditConnection, the response may be followed by information for each of the parameters requested. Parameters for which no value currently exists will still be provided. Connection descriptors will always appear last and each will be preceded by an empty line, as for example: 200 1203 OK C: A3C47F2145... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.3.8 RestartInProgress | The response to a RestartInProgress may include the name of another Media Gateway Controller to contact, for instance when the Media Gateway Controller redirects the endpoint to another Media Gateway Controller as in: 521 1204 Redirect N: MGC-1@whatever.net |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4 Session Description Encoding | The session description is encoded in conformance with the session description protocol (SDP), however, trunking gateways may make certain simplifying assumptions about the session description as specified in the following. It should be noted, that session descriptions are case sensitive per [4]. SDP usage depends on t... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.1 Use of SDP | In a trunking gateway, we only have to describe sessions that use exactly one MIME media type at a given point in time; either "audio" (for voice or voice-band data) or "image" (for T.38 fax calls). The parameters of SDP that are relevant for both the "audio" and "image" based media types are specified in clause 8.4.2.... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.1 Protocol Version (v=) | v= <version> v= 0 Send: must be provided in accordance with [4] (i.e. v=0), Receive: must be provided in accordance with [4]. Origin (o=) The origin field consists (o=) of 6 sub-fields in [4]: o= <username> <session-ID> <version> <network-type> <address-type> <address> o= - 2987933615 2987933615 IN IP4 126.16.64.4 User... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.2 Session Name (s=) | s= <session-name> s= - Send: Hyphen must be used as Session name. Receive: This field must be ignored. |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.3 Session and Media Information (i=) | i= <session-description> Send: For TGCP, the field must not be used. Receive: This field must be ignored. |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.4 URI (u=) | u= <URI> Send: For TGCP, the field must not be used. Receive: This field must be ignored. |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.5 E-Mail Address and Phone Number (e=, p=) | e= <e-mail-address> p= <phone-number> Send: For TGCP, the field must not be used. Receive: This field must be ignored. |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.6 Connection Data (c=) | The connection data consists of 3 sub-fields: c= <network-type> <address-type> <connection-address> c= IN IP4 10.10.111.11 Network Type: Send: Type 'IN' must be used. Receive: Type "IN" must be present. Address Type: Send: Type "IP4" must be used Receive: Type "IP4" must be present. Connection Address: Send: This field... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.7 Bandwidth (b=) | b= <modifier> : <bandwidth-value> b= AS : 64 Send: Bandwidth information is optional in SDP but it should always be included. If this field is not used, the Gate Controller might not authorize the appropriate bandwidth. When an rtpmap or a non well-known codec is used, the bandwidth information must be used. (A non wel... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.8 Time, Repeat Times and Time Zones (t=, r=, z=) | t= <start-time> <stop-time> t= 36124033 0 r= <repeat-interval> <active-duration> <list-of-offsets-from-start-time> z= <adjustment-time> <offset> Send: Time must be present; start time may be zero, but should be the current time, and stop time should be zero. Repeat Times, and Time Zones should not be used, if they are ... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.2.9 Attributes (a=) | a= <attribute> : <value> a= mptime: <alternative 1> <alternative 2> …a = X-pc-bridge: <number-ports> a= <attribute> a= recvonly a= sendrecv a= sendonly a= ptime a=pmft: <modem-fax-transport>t Send: One or more of the "a" attribute lines specified below may be included. Receive: One or more of the "a" attribute lines sp... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.3 SDP Audio Service Use | The following SDP parameters are applied at the media level and are specific to Audio Service Use. Audio Service Use includes VBD mode as defined in V.152 [27]. IPCablecom endpoints must not send any of these parameters within an image media descriptor (see clause 8.4.4). If, however, the endpoint receives an SDP with ... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.3.1 Encryption Keys | k= <method> k= <method> : <encryption-keys> Security services for IPCablecom are defined by IPCablecom Security [12]. The security services specified for RTP and RTCP do not comply with those of [2], [3], and [4]. In the interest of interoperability with non-IPCablecom devices, the "k" parameter will therefore not be u... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.3.2 Attributes (a=) | a= <attribute> : <value> a= rtpmap : <payload type> <encoding name>/<clock rate> [/<encoding parameters>] a= rtpmap : 0 PCMU / 8000 a=fmtp:<format> <format specific parameters> a= X-pc-codecs: <alternative 1> <alternative 2> a= X-pc-secret: <method>:<encryption key>[pad] a = X-pc-csuites-rtp: <alternative 1> <alternati... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.3.3 Media Announcements (m=) | Media Announcements (m=) consists of the following sub-fields: m= <media> <port> <transport> <format> [<format>] m= audio 3456 RTP/AVP 0 97 Media: Send: The 'audio' media type must be used. Receive: The type received must be 'audio' Port: Send: must be filled in accordance with [4]. The port specified is the receive po... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.4 SDP Image Service Use for T.38 | The following SDP parameters are applied at the media level and are specific to Image Service Use for T.38. IPCablecom endpoints must not send any of these parameters within an audio media descriptor (see clause 8.4.3). If, however, the endpoint receives an SDP with attribute parameters specific to audio only within an... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.4.1 Encryption Keys: | k= <method> k= <method> : <encryption-keys> There are currently no security services defined for the "image/t38" media type. Send: must not be used. Receive: This field should be ignored. ETSI ETSI TS 103 161-13 V1.1.1 (2011-10) 88 |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.4.2 Attributes (a=) | a= <attribute> : <value> a=T38FaxVersion: <version> a=T38MaxBitrate: <bitrate> a=T38FaxRateManagement: <faxratemanagement> a=T38FaxMaxBuffer: <maxbuffer> a=T38FaxMaxDatagram: <maxsize> a=T38FaxUdpEC: <ECmethod> a=T38FaxFillBitRemoval a=T38FaxTranscodingMMR a=T38FaxTranscodingJBIG Send: One or more of the "a" attribute ... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.4.4.3 Media Announcements (m=) | Media Announcements (m=) consists of 4 sub-fields: m= <media> <port> <transport> <fmt list> "m= image 3456 udptl t38" ETSI ETSI TS 103 161-13 V1.1.1 (2011-10) 90 Media: Send: The 'image' media type must be used for UDPTL-based T.38. Receive: The type received must be 'image' for UDPTL-based T.38. Port: Send: must be fi... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.5 Transmission Over UDP | |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.5.1 Reliable Message Delivery | MGCP messages are transmitted over UDP. Commands are sent to one of the IP addresses defined in the Domain Name System (DNS) for the specified endpoint or Media Gateway Controller. The responses are sent back to the source address of the command. However, it should be noted that the response may, in fact, come from ano... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.5.2 Retransmission Strategy | The present document avoids specifying any static values for the retransmission timers since these values are typically network-dependent. Normally, the retransmission timers should estimate the timer by measuring the time spent between sending a command and the return of a response. Trunking gateways must implement a ... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.5.3 Maximum Datagram Size, Fragmentation and Reassembly | TGCP messages being transmitted over UDP rely on IP for fragmentation and reassembly of large datagrams. The maximum theoretical size of an IP datagram is 65 535 bytes. With a 20-byte IP header and an 8-byte UDP header, this leaves us with a maximum theoretical TGCP message size of 65 507 bytes when using UDP. However,... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.6 Piggy-Backing | There are cases when a Call Agent will want to send several messages at the same time to one or more endpoints in a gateway and vice versa. When several messages have to be sent in the same UDP packets, they are separated by a line of text that contains a single dot, as in for example: 200 2005 OK DLCX 1210 ds/ds1-1/1@... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.7 Transaction identifiers and three ways handshake | Transaction identifiers are integer numbers in the range from 1 to 999 999 999. Media Gateway Controllers may decide to use a specific number space for each of the gateways that they manage, or to use the same number space for all gateways that belong to some arbitrary group. Media Gateway Controllers may decide to sha... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 8.8 Provisional Responses | In some cases, transaction completion times may be significantly longer than otherwise. TGCP uses UDP as the transport protocol and reliability is achieved by selective time-out based retransmissions where the time-out is based on an estimate of the sum of the network roundtrip time and transaction completion time. Sig... |
e24dc05fc9943606cbfab85caeca5aef | 103 161-13 | 9 Security | If unauthorized entities could use the MGCP, they would be able to set up unauthorized calls or interfere with authorized calls. Security is not provided as an integral part of MGCP. Instead MGCP assumes the existence of a lower layer providing the actual security. Security requirements and solutions for TGCP are provi... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 1 Scope | The present document aims to: • harmonize the LCAs of ICT Equipment, Networks and Services; • increase the quality of the LCA by adding ICT specific requirements to those of ISO 14040 [1] and ISO 14044 [2]; • facilitate communication of LCAs of ICT Equipment, Networks and Services; • increase the credibility of LCAs of... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 14040 (2006): "Environmental management -- Life cycle assessment -- Principles and framework". [2] ISO 14044 (2006): "Environmental management -- Life cycle assessment -- Requirements and guidelines". |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 102 706 (V1.1.1): "Environmental Engineering (EE) Energy Efficiency of Wireless Access Network Equipment". [i.2] European Commission Joint Res... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 3 Definitions and abbreviations | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO 14040 [1], ISO 14044 [2], the ILCD Handbook, Table 1 [i.2] and the following apply. active area: area of the display or touch panel which is useful for touch or viewing black box module: device, system or object which can be viewed solely ... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3G Third generation telecom networks 4G Fourth generation telecom networks BGA Ball Grid Array BOD Biochemical Oxygen Demand BOM Bill of Materials BSC Base Station Control site CAS Chemical Abstracts Service CATV Cable Access Television CC Cli... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 4 General Description | This is a clause about compliance and comparisons. First it is recommended to study ISO 14040 [1], Section 4.1. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 4.1 Compliance to the present document | The present document contains requirements (denoted as mandatory or by the use of the word shall), recommendations (denoted by the use of the word should), and options (denoted as optional or by the use of the word may). Recommendations and options are summarized in clause 8. Full compliance towards the present documen... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 4.2 Comparisons of results | It is important to realise that comparisons of results (absolute and relative values) between LCAs are beyond the scope of the present document, as such comparisons would require that the assumptions and context of each LCA are exactly equivalent. LCA can be performed and presented by different individuals/organization... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5 Methodological framework | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.1 General requirements | When performing an ICT related LCA, the requirements of the present document apply as well as those of ISO 14040 [1] and ISO 14044 [2]. I.e. all three standards have to be taken into account. ETSI ETSI TS 103 199 V1.1.1 (2011-11) 15 |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.1.1 Life cycle stages | The following life cycle stages (also shown in Figure 2) in the present document apply to ICT Equipment, Networks and Services and shall be assessed as applicable in LCAs based on the present document: a) Equipment Raw material acquisition which is composed by: - Raw material extraction. - Raw material processing. b) P... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.1.2 Handling of software | From the perspective of the present document software shall be considered as well as hardware. Any ICT Equipment or Network or Services uses both hardware and software which both impacts, e.g. the production and use stages. For the production stage software development impacts the amount of persons involved in the deve... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.1.3 Operating Lifetime | Operating lifetime is critical for the interpretation of the results of LCAs and shall therefore always be reported when presenting LCA results. Operating lifetime estimates and assumptions shall also be clearly described in the reporting. Operating lifetime can only be defined for equipment, i.e. ICT and Support Equip... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2 Goal and Scope definition | During the LCA scoping phase the building blocks of the ICT Equipment, Networks or Services shall be identified. NOTE: These building blocks are preferably identified from functional block diagrams provided, e.g. by system engineers/architects. Schematically three main levels of targeted product systems exist: • Equipm... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.1 Functional unit | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.1.1 General | The functional unit requires inclusion of the relevant quantifiable properties and the technical/functional performance of the system. This means that the operational lifetime of all included ICT Equipment shall be specified and also the number of users/subscribers supported by the Network and the traffic profile shall... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.1.2 ICT equipment | The functional unit shall be chosen in the context of goal and scope of the LCA and shall be further clarified by system boundary and cut-off rules. ICT Equipment LCA results may be further used as basis for Networks and Services LCA. To comply with the present document, the following functional unit shall be applied w... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.1.3 Networks | For the purpose of the present document, the following functional unit shall be applied where applicable: • Annual Network use. For relevant LCA results realistic use scenarios shall be captured. Additionally, other more specific functional units may be applied as well based on the scope and purpose of the LCA, for ins... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.1.4 Services | For the purpose of the present document, the following functional unit shall be applied where applicable: • Annual Service use. For relevant LCA results realistic use scenarios shall be captured. Additionally, other more specific functional units may be applied as well based on the scope and purpose of the LCA. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2 System boundaries | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.1 General | NOTE 1: Section 4.2.3.3 in ISO 14044 [2] applies as well. The system boundaries define the life cycle stages and processes belonging to the analysed product system, i.e. are required for providing its function as defined by its functional unit. Consequently, the system boundaries here define the life cycle stages and t... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.1.1 The use of unit processes | Each life cycle stage (A to D) is further refined into activities, referred to as unit processes, which represent the basic physical flows (materials and energy) of the life cycle. A unit process typically represents a facility where a product is produced, but it can also represent, e.g. an office or a store - or even ... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.2 ICT equipment | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.2.1 General | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.2.2 Equipment Raw materials acquisition | Equipment Raw Material Acquisition (A) starts with the extraction (A1) of natural resources (e.g. iron ore, crude oil, etc.) and ends with the transport of Raw Materials from Raw materials processing (A2) to Part Production facilities. A2 deals with the processing of extracted Raw Materials (e.g. iron ore pellets) into... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.2.3 Production | The Production (B) starts with the Parts Production, and ends with the transport of ICT Equipment and Support Equipment to Use (C). The system boundary for Production, shown in Figure 5, includes ICT Equipment Production and Support Equipment Production. NOTE 1: Detailed flow chart figure s of, e.g. transports are deci... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.2.4 Use | The Use stage starts with the Installation of ICT Equipment and Support Equipment and ends with the de-installation just before the transport to EoLT. As shown in Figure 6, the use stage includes ICT Equipment Use (C1), Support Equipment Use (C2), Operator activities (C3), and Service provider activities (C4). (C1) and... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.2.5 End-of-life treatment (EoLT) | EoLT starts with the transport of de-installed ICT Equipment and/or Support Equipment to Storage/Disassembly/Dismantling/Shredding facilities, and ends with the waste treatment of ICT Equipment and Support Equipment. NOTE: The first destination for the de-installed ICT Equipment depends on the goal and scope of the spe... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.3 Networks | A Network is an ICT based infrastructure which offers the possibility to transfer voice and/or data between different access points, usually referred to as nodes, and further on to the end-users (represented, e.g. by a telephone or PC). Ultimately the total Network may be studied, taking into account both wireline and ... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.2.4 Services | The operation of a Network could be described as the operation of several services working in parallel, among them the basic primary subscription service allowing transfer of voice and data, but also different applications. Thus, to calculate the impact of a Service, it is necessary to assess the Network, as outlined i... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.3 Cut-off rules | NOTE: Section 4.2.3.3.3 in ISO 14044 [2] applies as well. Cut-offs shall be avoided as far as possible. An alternative to cut-off is often to model unavailable data based on known data. However, if cut-offs are performed, careful considerations are required. ISO 14044 [2], section 4.2.3.3 gives general guidance, especi... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.4 Data Quality Requirements | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.4.1 General | In LCA context data refers to activity data, emission factors and, in some cases, direct GHG emissions. In general the practitioner used shall reduce bias and uncertainty as far as practicable by using the best quality data achievable. Also, high accuracy and preciseness is preferred. In addition data which is more spe... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.2.4.2 Specific requirements on data and data sources | In general data age and technology are especially important in LCAs for ICT Equipment, Networks and Services due to the fast technology evolution and the growth in network traffic. e.g. for data traffic, up-to-date figures shall always be used, e.g. for allocation between Services, as data traffic grows considerably ye... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3 Life Cycle Inventory (LCI) | NOTE: ISO 14044 [2], Section 4.3.1 applied as well. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.1 Data collection | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.1.1 General | NOTE: ISO 14044 [2], Section 4.3.2 applies as well. Practically, when working with certain LCA tool and LCI database, e.g. Transports and Travel (G1) and energy supplies (G2-G4) could be included in larger data sets, whereas other LCA tools/LCI databases provide transports/energy supply separately. The LCA practitioner... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.1.2 Energy consumption during use stage | The best way to determine the energy consumption is to measure a large number of products in real live operating environments over a long period of time (e.g. a year to capture all aspects of different use behaviour, climate etc.). Many network Equipment are installed in sites with energy meters. If data from such meas... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.2 Data calculation | NOTE 1: ISO 14044 [2], Section 4.3.3 applies as well. Several operational steps are needed for data calculation. These are described in ISO 14044 [2], sections 4.3.3.2 to 4.3.3.4 and 4.3.4 and ILCD Handbook [i.2], Section 7.10. All calculation procedures shall be explicitly documented and the assumptions made shall be ... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3 Allocation of data | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.1 General | NOTE: ISO 14044 [2], Sections 4.3.3 and 4.3.4 apply as well. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.1.1 Allocation rules for generic processes | Data for generic processes (G1 to G7) shall be allocated as a whole (i.e. for the full lifecycle for the generic process) to the associated life cycle stage of the product system. However all Raw Material Acquisition (G5) shall be allocated to the life cycle stage Raw Material Acquisition (A). 5.3.3.1.2 Allocation rule... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.1.3 Allocation rules for facility data | Facility data for production facilities shall preferably be allocated to product systems based on relevant physical data (i.e. area × layer for printed circuit boards, good die area for ICs, weight for other components according to Table B.1). If information regarding physical parameters is insufficient economical allo... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.1.4 Allocation rules for transports | Transports shall be allocated based on chargeable weight or volume whichever limits the transport capacity. Empty return trips need also to be considered if applicable. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.1.5 Allocation rules for recycling | The impacts of Raw Material Recycling (G7) shall be allocated between life cycles, in practice between Raw Material Acquisition (A1-A2) and EoLT (D), according to the following principles: • All elementary flows and consequently all environmental impacts of Landfill shall be fully allocated to the life cycle that puts ... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.2 ICT equipment | See clause 5.3.3.1. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.3 Network | Support activities and, when applicable, Support Equipment which is shared between several nodes or all Network equipment need not be allocated to the different ICT Equipment but can be presented without being distributed. End-user equipment (e.g. PCs, smart phones) which is accessing more than one Network (e.g. 3G, WL... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.3.3.4 Services | The following allocation principle of Network data to a Service shall be used: • Data for End-users equipment: - to be allocated based on active use time of the Service. • Data for CPE: - to be allocated based on active use time of the Service or data traffic or data rate/allocated bandwidth. • Data for access networks... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.4 Life Cycle Impact Assessment (LCIA) | NOTE 1: ISO 14044 [2] Section 4.4 and ILCD Handbook [i.2], Sections 6.7 and 8) apply as well. The Life Cycle Impact Assessment (LCIA) handles the translation of the environmental loadings of the life cycle inventory (LCI) to potential and real environmental impacts. In the LCA it shall be ensured that the inventory ele... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.5 Life Cycle Interpretation | NOTE: ISO 14044 [2], Section 4.5 applies as well. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.5.1 General | In the life cycle interpretation, the results of the LCA are evaluated in order to answer questions raised in the goal definition (clause 5.2). The steps of the interpretation shall ensure the robustness of the conclusions from the LCA. During the iterative steps of the LCA the interpretation phase serves to improve th... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.5.2 Uncertainty | The uncertainty of the results of an LCA shall be assessed in accordance with ISO 14044 [2]: to the extent needed to understand the results. Also the sources of uncertainty and methodological choices made shall be assessed and disclosed. For more information regarding uncertainty categories and important uncertainty so... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 5.5.3 Sensitivity analysis | Especially when modelled data are used, different scenarios should be assessed to establish a range of potential outcomes to limit the uncertainty. For requirements on sensitivity analysis refers to ISO 14044 [2], section 4.5.5.3. 5.6 Comparative LCA between ICT and reference product systems To be able to quantify the ... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6 Reporting | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.1 General | The reporting of ICT product systems shall fulfil the reporting rules as defined by ISO 14040 [1] and ISO 14044 [2]. In addition the rules outlined in this clause and what is stated in Annex F shall be followed for reporting of studies claiming compliance with the present document. ETSI ETSI TS 103 199 V1.1.1 (2011-11)... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2 ICT equipment | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.1 Total result | For each impact category studied, diagrams corresponding to Figures 9a and 9b shall be reported for the corresponding category indicator result. It is allowed to present Raw Material Acquisition, Production, and End-of-life treatment together should there be LCA tools/LCI databases limitations preventing a split betwee... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.2 System boundaries | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.2.1 Life cycle stages, unit processes and generic processes | Any deviation to Table 1 and clause 5.2.2 with respect to mandatory life cycle stages/unit processes shall be clearly stated and motivated. Also handling of optional stages/activities shall be clearly reported as well as electricity mix applied, and handling of support activities and transports. Especially for transpor... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.2.3 Raw material acquisition | The use of raw materials shall be transparently reported as outlined below. The most important metals from recycling point of view shall always be included. Other materials can be shown as well but such reporting is optional. For appropriate reporting format refer to Annex F, Table F.5. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.2.4 Production | Parts production Compliance to Annex B, Table B.1 shall be reported according to below and any deviation shall be described and motivated. ETSI ETSI TS 103 199 V1.1.1 (2011-11) 41 For appropriate reporting format refer to Annex F, Table F.6. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.2.5 Use | ICT equipment use The basis for the energy consumption figures for the ICT equipment use stage shall be reported together with the annual value of the energy consumption. For many products (especially end-user equipment), periods off idling and power off are important to model the usage profile. It is therefore mandato... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.