hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.6 Luminance mapping table | |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.6.1 Introduction | The variables defined in this clause are piece-wise linear pivot points representative of the square-root of the inverse luminance mapping curve, implemented by the look-up table lutMapY. This look-up table is taken as one input of the SDR-to-HDR reconstruction process. The variables specified in this clause are presen... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.6.2 luminanceMappingNumVal - Number of Luminance Mapping Curve Points | This variable specifies the number of pivot points in the piece-wise linear luminance mapping curve. The value of luminanceMappingNumVal shall be in the bounded range [0 to 33]. |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.6.3 luminanceMappingX - Luminance Mapping x values | This variable indicates the xi values of the luminance mapping curve. It shall be in the bounded range [0 to 1] and in multiples of (1 ÷ 16 383). The value of luminanceMappingX[ i + 1 ] shall be greater than the value of luminanceMappingX[ i ], for i in the range of 0 to luminanceMappingNumVal - 2, inclusive. |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.6.4 luminanceMappingY - Luminance Mapping y values | This variable indicates the yi values of the luminance mapping curve. It shall be in the bounded range [0 to 1] and in multiples of (1 ÷ 16 383). When luminanceMappingX[ 0 ] is greater than 0, an initial linear segment shall be inferred that maps input values ranging from 0 to luminanceMappingX[ 0 ], inclusive, to targ... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.7 Colour correction table | |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.7.1 Introduction | The variables defined in this clause are piece-wise linear pivot points representative of colour correction curve, implemented by the look-up table lutCC. This look-up table is taken as one input of the SDR-to-HDR reconstruction process. The variables specified in this clause are present when payloadMode is set to 1 (i... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.7.2 colourCorrectionNumVal - Number of Colour Correction Curve Points | This variable specifies the number of pivot points in the piece-wise linear colour correction curve. The value of colourCorrectionNumVal shall be in the bounded range [0 to 33]. |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.7.3 colourCorrectionX - Colour Correction x values | This variable indicates the xi values of the colour correction curve. It shall be in the bounded range [0 to 1] and in multiples of (1 ÷ 2 047). The value of colourCorrectionX[ i + 1 ] shall be greater than the value of colourCorrectionX[ i ], for i in the range of 0 to colourCorrectionNumVal - 2, inclusive. ETSI ETSI ... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 6.3.7.4 colourCorrectionY - Colour Correction y values | This variable indicates the yi values of the colour correction curve. It shall be in the bounded range [0 to 1] and in multiples of (1 ÷ 2 047). When colourCorrectionX[ 0 ] is greater than 0, an initial linear segment shall be inferred that maps input values ranging from 0 to colourCorrectionX[ 0 ], inclusive, to targe... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7 HDR signal reconstruction process | |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.1 Input streams | The input stream is composed of a decoded SDR video stream and associated dynamic metadata that are combined to reconstruct an HDR video signal. The dynamic metadata can be conveyed thanks to two mutually exclusive modes: a parameter-based mode (payloadMode 0) and a table-based mode (payloadMode 1). Concerning ITU-T or... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2 Reconstruction process of the HDR stream | |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.1 Introduction | This clause specifies the reconstruction process enabling the generation of an HDR picture from an SDR picture with associated dynamic metadata. This process is defined for full range SDR picture signal (as defined in SMPTE RP 2077 [7]). For SDR picture defined as narrow-range signal, an (unspecified) conversion to ful... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.2 Selecting a reconstruction mode | Clause 7.2.3 describes the processing step to construct luminance mapping and colour correction tables that are used as inputs to the HDR stream reconstruction process. The HDR reconstruction process operates on look-up tables reconstructed from variables (payloadMode 0) specified in clauses 7.2.3.1 and 7.2.3.2 or deri... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3 Luminance mapping and colour correction tables construction | |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1 Luminance mapping table construction from variables (payloadMode 0) | |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.1 Introduction | The luminance mapping table construction for payloadMode 0 derives a 1D look-up table lutMapY from the luminance mapping variables as described in clause 6.2.5. This process takes as inputs: • the HDR picture characteristics variable hdrMasterDisplayMaxLuminance; • the luminance mapping variables tmInputSignalBlackLeve... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.2 Overview of the computation of lutMapY | The look-up table lutMapY[ Ypost1 ], for luma values Ypost1 = 0..( maxSampleVal - 1 ), implements an inverse tone mapping function. The inverse tone mapping process is shown in Figure 4. For any Ypost1 in 0..( maxSampleVal - 1 ), the lutMapY[ Ypost1 ] is derived by applying the following steps: • Ypost1 is converted vi... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.3 Block "To perceptual uniform signal" | This process takes as inputs: • the luma value Ypost1. The process generates as output: • the converted linear-light value Ypus. In the first step, Ypost1, which is a Recommendation ITU-R BT.1886 [11] compatible luma signal, shall be taken to the power γ = 2,4 to yield the linear-light signal Y2. = ... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.4 Block "Adjustment curve" | This process takes as inputs: • the converted linear-light value Ypus ; • the variables tmOutputFineTuningNumVal, tmOutputFineTuningX[ i ] and tmOutputFineTuningY[ i ], for i=0..( tmOutputFineTuningNumVal - 1 ). The process generates as output: • the corrected value Yft . In this block, the input signal Ypus shall be c... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.5 Block "Inverse tone mapping curve" | This process takes as inputs: • the corrected value Yft ; • the variables shadowGain, highlightGain, midToneWidthAdjFactor; • the variable hdrMasterDisplayMaxLuminance. The process generates as output: • the inverse tone-mapped value, in linear-light domain, Yadj . In this block, the input signal Yft shall be converted... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.6 Block "Black/white level adaptation" | This process takes as inputs: • the inverse tone-mapped value, in linear-light domain, Yadj ; • the variables tmInputSignalBlackLevelOffset and tmInputSignalWhiteLevelOffset. The process generates as output: • the stretched value Ybw . In this block, the input signal Yadj shall be adapted by the black and white stretch... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.7 Block "Gain limiter" | This process takes as inputs: • the value Ybw from clause 7.2.3.1.6; • the value Ypus from clause 7.2.3.1.3; • the variable tmInputSignalBlackLevelOffset; • the variable hdrMasterDisplayMaxLuminance in the structure luminance_mapping_variables( ) of the SDR- to-HDR reconstruction metadata (clause 6.2.5). The process ge... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.8 Block "To linear signal" | This process takes as inputs: • the gain limited value Yglim; • the variable hdrMasterDisplayMaxLuminance. The process generates as output: • the linear-light value Yll. In this block the computation of the value Yll, the input signal Yglim shall be converted from the perceptually uniform domain to the linear-light dom... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.1.9 Block "Sqrt" | This process takes as inputs: • the linear-light value Yll ; • the variable hdrDisplayMasterMaxLuminance. ETSI ETSI TS 103 433 V1.1.1 (2016-08) 31 The process generates as output: • the value lutMapY[ Ypost1 ]. LHDR is equal to hdrDisplayMasterMaxLuminance. In this block, the square root of the value Yll is taken in or... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.3 Luminance mapping table retrieval (payloadMode 1) | This process derives, for payload mode 1, a 1D look-up table lutMapY from the luminance mapping variables specified in clause 6.3.6. This process takes as inputs: • the luminance mapping table variables luminanceMappingNumVal, luminanceMappingX[ i ] and luminanceMappingY[ i ]; • the mastering display max luminance hdrM... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.3.4 Colour correction table retrieval (payloadMode 1) | The process derives, for payload mode 1, a 1D look-up table lutCC from the colour correction table as described in clause 6.3.7. This process takes as inputs: • the colour correction table variables colourCorrectionNumVal, colourCorrectionX[ i ] and colourCorrectionY[ i ]. The process generates as output: • the colour ... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.2.4 HDR picture reconstruction from look-up tables and SDR picture | The HDR reconstruction process generates the reconstructed HDR picture from the decoded SDR picture and the luminance mapping and colour correction tables. This process takes as inputs: • an SDR picture made of two-dimensional arrays SDRY, SDRCb, SDRCr of width picWidth and height picHeight, after applying on the decod... |
c86f5e710ab461d7d5499b4a8bbac9c2 | 103 433 | 7.3 Piecewise linear function computation | A piecewise linear function f (x) that is specified by a list of{ xi, yi } pairs shall be computed as specified in this clause. The y = f (x) values that are not in the list of { xi, yi } pairs shall be obtained through interpolation. The default interpolation shall be linear interpolation. The default processing of y ... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 1 Scope | The present document defines a method to improve the coexistence by mitigating the interference between the DSL transceiver and PLT transceiver operating in overlapping frequency band but on different cables. In-home PLT networks operate over the same spectrum as DSL networks. This increases the likelihood of crosstalk... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 2 References | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 3 Definitions and abbreviations | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Arbitration Function (AF): entity that facilitates coordination between the DSL and PLC systems in order to reduce interference on the basis of coordination policy by appropriately configuring parameters of the DSL and PLC devices NOTE... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Arbitraty Function CPE Customer Premises Equipment DMT Discrete MultiTone DSL Digital Subscriber Line DSM Dynamic Spectrum Management EMC ElectroMagnetic Compatibility FDD Frequency Division Duplexing IPTV Internet Protocol TeleVision ITU-T... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 4.1 Introduction | DSL and PLT technologies are based on OFDM transmission and both PLT and DSL modems operate in the frequency range from 2 MHz to 30 MHz, although on different cables. ETSI ETSI TS 103 430 V1.1.1 (2016-05) 8 Figure 1: Interaction between DSL and PLT The cross-channel coupling depends on the type of cables (twisted or un... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 4.2 DSL and PLT Channel Coupling Model | The DSL and PLT channels are usually modelled separately, for our purpose of coexistence of these two transceivers, a MIMO channel model of dimension using matrix H (2 x 2) was introduced to take into account the channel coupling and this is illustrated in figure 2). In this MIMO model, coefficient h1,1 represents the ... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 4.3 Analysis of the PHY layers of PLT and DSL | The physical layer of PLT modem (PHY) is based on windowed OFDM as the basic modulation technique. The physical layer of VDSL2/ modem (PHY) is also based on windowed OFDM. The separation of upstream and downstream transmissions by FDD is defined by the band plans [2]. The VDSL2 signal can potentially use the frequency ... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 5 Reference models | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 5.1 Generalized reference model | The generalized reference model addressing the coexistence mechanism is presented in figure 3. The Arbitration Function (AF) facilitates resource allocation between the PLC network and the xDSL NT. The communication between PLC and AF and the xDSL NT and AF are defined using a generic reference model presented in figur... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 5.2 Details of the interfaces | 1) The defined interfaces of the generic reference model (ΦC, ΦP, and ΦA, figure 3) are logical, which means: - the interface is defined by sets of primitives to be exchanged (see clause 7.5 in Recommendation ITU-T G.9977 [1]); - no L1-layer protocol (physical signals) is specified. 2) The ΦC, ΦP, and ΦA interface prim... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6 General approach | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.1 Overview of PLC the interference mitigation mechanism | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.1.1 Overview | The coexistence mechanism defined in Recommendation ITU-T G.9977 [1] provides mitigation of the PLC interference into xDSL line and mutual optimization of the performance of the xDSL line and PLC network. It facilitates normal initialization and stable steady-state operation of a xDSL line within the QoS requirements d... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.2 Device discovery | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.2.1 Overview | The discovery mechanism provides the AF, the xDSL NT, and the PLC devices a procedure to announce themselves and become aware of the existence of devices that are relevant for the coexistence procedure. The discovery mechanism provides the tools that: • Allow the AF, the xDSL NT and PLC network devices to announce thei... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.3 Device measurement | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.3.1 Overview | The AF is in charge of coordinating the measurement of the interference between xDSL and PLC network devices. For this, AF may request corresponding time windows. As a result of these measurement procedures, AF can obtain measurement data and use it to facilitate coexistence between xDSL NT and PLC network devices, and... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.4 Device configuration | |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.4.1 Overview | The device configuration procedure allows changing transmission parameters of PLC network devices and xDSL line (xDSL NT) necessary to facilitate coexistence between the PLC network and the xDSL and optimize the overall end-to-end service delivery to the customer. The procedure is managed by the AF and performed under ... |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.5 Primitives supporting coexistence protocol | The list of coordination primitives between xDSL NT and PLC network for the logical interfaces ΦP, ΦC, and ΦA is defined in table 7-4 in Recommendation ITU-T G.9977 [1]. |
2c542e38cce00c634dfc60ea8df3cb8b | 103 430 | 6.6 Description of primitives | The primitives exchange across ΦP, ΦC, and ΦA interfaces shall have the following properties: • the exchange contains a set of request - response pairs of messages (except for indication messages); • each primitive may carry one or more primitives; • the type of the primitive is determined by the OPCODE that indicates ... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 1 Scope and purpose of the present document | |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 1.1 Abstract | The present document, originally developed as HGI-RD048v2, contains requirements regarding modular software deployments on the home gateway. These requirements form the HGI's "Open Platform 2.1". Under the Open Platform 2.1 requirements, modular software applications have to run in a dedicated virtual execution environ... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 1.2 Scope and purposes | Service delivery to residential customers beyond triple play requires the integration of home devices and appliances with cloud infrastructures. Such integration often requires new software in the home network, but the variety of available technologies makes this difficult. In order to achieve the next level of service... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 1.3 What is new compared to HGI-RD008 and to RD-048v1? | |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 1.3.1 RD-048v1 compared with RD-008 [i.20] | • Addition of Smarthome related low-level requirements, especially in terms of support of USB based hardware extendibility. • Detailed requirements for system clock synchronization. • Detailed OSGi requirements: Many requirements have been detailed for clarification and precision reasons. • Reference to Broadband Forum... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 1.3.2 RD-048v2 compared with RD-048v1 | • Streamlined text. • Modified figures to reflect text consistency. • Streamlined wording of requirements. • Updated references to OSGi and Java™ JRE version. • Updated Java™ related requirements to Java™ 8 compact1 profile. • Requirements that in RD-048v1 referred to OSGi Service Platform Specification Release 4.2 (Co... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 1.4 Relationship with HGI residential profile | The present document contains requirements over and above those in the HGI Residential Profile [i.1], to support the software module execution environment. All requirements of the HGI Residential Profile still apply. Some of the original functionalities defined in the HGI Residential Profile [i.1] may be suitable for i... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 2 References | |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 3 Definitions and abbreviations | |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Gateway Operator (or just operator): Primary responsibility of the Gateway Operator is to control who is allowed to deploy services to the Service Platform in question i.e. control which Service Deployment Managers are allowed to manag... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACS Auto Configuration Server CWMP CPE Wan Management Protocol RMS Remote Management System |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4 Architecture | |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.1 Roles and entities | This clause defines operational roles and entities for an execution environment on the HG. The HGI roles of "Broadband Service Provider" (BSP) and "Application Service Provider" (ASP) as defined in [i.1] may apply to several of the following roles, but both certainly apply to the "operator" role. For example, a BSP mig... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.2 Entities in the open platform 2.1 - enabled home gateway | Entities in the Open Platform 2.1 enabled Home Gateway are depicted in Figure 2. This is the reference scheme for the Home Gateway Software Architecture [i.3]. The HG consists of the core functions (HG_Core) plus one or more HG Execution Environments (HG_EE), each of them including a Service Platform (HG_SP) and softwa... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.3 Home gateway software architecture | This clause describes the software architecture for the integration of a Service Platform into an HG. The architecture is generic in the sense that applies to any chosen Service Platform technology. |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.3.1 Essentials | • An HG_API shall be defined for any specific Service Platform technology. All HGs using that specific technology shall implement the HG_API defined for that technology. • There are no restrictions on how modules are implemented other than those defined by the chosen Service Platform technology. • Any modules intended ... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.3.2 Details | The HG_EE runs on top of the HG_Core. Modules run on top of the Service Platform and are able to communicate with each other to use each other's functions, if they are authorized to do so. Using functions other than those provided by the Service Platform is allowed (e.g. to provide direct access to the HG_Core for vend... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.4 Access to smart home non IP networks | There are three common models to address appliances in non-IP networks (e.g. switches, dimmers, sensors). Some systems allow an external gateway to be attached to the HG and then be accessed over IP-based protocols (such as HTTP) in order to perform actions and queries on appliances connected to the external gateway us... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.5 Remote management | |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.5.1 Essentials | • The remote management protocol for HG_EE is CWMP [i.6] with its related data models TR-181 [i.4] or TR-098 [i.5]. • There is only 1 management entity for any given HG_EE (see role model in Figure 1). • LAN-side management (by e.g. the customer) is not allowed for HG_EE. • Management/configuration of the service aspec... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.5.2 Details | Management of the software configuration of an HG is under the control of a (single) Gateway Operator. This includes the approval of any software before it is installed on to the execution environment. Third party service providers are therefore dependent on the Gateway Operator for the installation of modules to deliv... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 4.5.3 Issues with firmware updates and software module management | If the software execution platform is part of a device's firmware, then a firmware update probably contains an empty execution platform, and therefore it is probably necessary to reinstall all needed modules and configurations. On a large scale, considering millions of devices and hundreds of applications per device, a... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5 Generic requirements | The following clauses contain high-level requirements to make the HG execution environment for software modules reliable, manageable and useable to application developers. Requirements in each section apply to one of: • HG (i.e. may be implemented anywhere in HG). • HG_Core. • HG_EE (i.e. may be implemented anywhere in... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.1 Basic requirements | Requirements in this clause could be implemented in the HG_Core or the HG_EE, or both. ETSI ETSI TS 103 426 V1.1.1 (2016-11) 16 Table 1 N° Requirement OP2.0-1 The HG SHALL have an internal system clock to provide the date and time of day. See note. OP2.0-2 The HG SHALL support synchronisation of its internal system clo... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.2 Reliability and security | Table 3 N° Requirement OP2.0-14 All functions of the HG_Core SHALL remain available if the HG_EE malfunctions or crashes. OP2.0-15 The HG_SP SHOULD ensure that any single module cannot exceed assigned resources (CPU load, runtime memory). OP2.0-16 The HG_SP SHALL be able to log life cycle operations (install, uninstall... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.3 Life cycle management | Life cycle management refers to the management of modules and their existence on the HG. The life cycle actions for a module are installation, uninstallation, update, start and stop. ETSI ETSI TS 103 426 V1.1.1 (2016-11) 17 |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.3.1 General | Table 4 N° Requirement OP2.0-19 When performing lifecycle operations the HG_SP SHALL NOT affect the lifecycle of modules that do not have dependencies on the module operated upon. |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.3.2 Installation | Installing a module means loading a module package to the HG_EE from a management backend, or triggering the HG_SP to download a module package from a URL. Table 5 N° Requirement OP2.0-20 An HG_SP SHALL be able to check the signature integrity of all modules. Signature integrity provides the authorization for a module ... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.3.3 Uninstallation | Uninstalling a module means removing the module from the HG_EE non-volatile memory. Table 6 N° Requirement OP2.0-23 Before uninstalling a module, the HG_SP SHALL inform all dependent modules for example to give them the opportunity for graceful shutdown. OP2.0-24 Before uninstalling a module the HG_SP SHALL initiate th... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.3.4 Update | Updating a module means to replace an existing module on the HG_EE with a more recent version of the module. Table 7 N° Requirement OP2.0-26 The HG_SP SHALL allow updating software modules. OP2.0-27 The HG_SP SHALL re-start a module after update if the module, before being updated, had been running. OP2.0-28 Before upd... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.3.5 Start | Starting a module means assigning system resources to a module and invoking an initialisation operation of the module. Table 8 N° Requirement OP2.0-29 The HG_SP SHALL be able to start a module. OP2.0-30 The HG_SP SHALL inform dependent modules that another module has been started. ETSI ETSI TS 103 426 V1.1.1 (2016-11) ... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.3.6 Stop | Stopping a module means invoking an operation of the module that allows a graceful release of the resources that it was using. Table 9 N° Requirement OP2.0-31 The HG_SP SHALL be able to stop a module. OP2.0-32 Before stopping a module, the HG_SP SHALL inform all depending modules about this. OP2.0-33 After stopping a s... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.4 Remote management | HGI specifies the use of a CWMP-based remote management system to manage the core functions of a Home Gateway. It is therefore appropriate to specify the same system for the lifecycle management of software modules on the HG. Compliance with the TR-181 [i.4] or TR-098 [i.5] BBF data model specifications is assumed in a... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.5 Module dependencies and interaction | A module might need to control the functions or the data resources of other modules. The HG_SP provides the means to ensure consistency on module configuration (no unresolved and stale references). The HG_SP needs to support modules being able to register, advertise, retrieve and invoke interfaces. Table 11 N° Requirem... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.6 Supported protocols stacks | A basic set of protocol stacks is specified, to avoid the need for module-specific implementations. Table 12 N° Requirement OP2.0-49 The HG_SP SHALL provide an API to an HTTP and HTTPS client protocol stack. If technology specific standardized APIs are available these SHALL be used. OP2.0-49a The HG_SP SHALL provide an... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 5.7 HG application programming interface (HG_API) | Table 13 N° Requirement OP2.0-52 The HG SHALL provide an API to support communication between HG_EE modules and the HG_Core. OP2.0-53 The HG_API SHALL provide access to HG_Core functions as specified in the HGI Residential Profile [i.1]. OP2.0-54 The HG_API SHALL provide access to management functions as specified in T... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 6 Technology specific requirements | This clause contains technology specific Service Platform requirements, instantiating the HG_EE and HG_SP requirements when a Java/OSGi solution is adopted. HG_Core requirements are out of scope for clause 6. To implement an HG compliant to HGI Open Platform 2.1 as specified in this clause, the developer will follow th... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 6.1 OSGI service platform | The OSGi Service Platform is a Java™ based HG_SP with the addition of a comprehensive component model. This clause defines a profile of Java™ and OSGi technology. In specifying OSGi specific requirements, the terms used to identify entities in the Open Platform 2.1 enabled Home Gateway defined in clause 4.2 are replace... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 6.1.1 Essentials | • OSGi Dmt Admin Service is used as HG-API, while the vendor-specific implementation of access to management resources is carried out through Data Plugins to Dmt Admin. • Config Admin Service is mandatory, and its implementation is vendor-specific, because it provides persistence and needs to store data on the HG in a ... |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 6.1.2 Architecture | The instantiation of the generic Home Gateway architecture (see [i.9], [i.10], [i.11], [i.12], [i.13], [i.14] and [i.15]), for OSGi technology is depicted in Figure 3. Figure 3: Component view of an OSGi based Home Gateway |
b87a2ecc7924dd85005b1c4be3330723 | 103 426 | 6.1.3 OSGI specific requirements | The following requirements define a Java/OSGi-based execution environment. The rightmost column of table 15, labelled "Reference", shows the corresponding generic requirements, or N/A (not applicable) if no generic counterpart is defined. NOTE: Applications developed under OSGi Service Platform Core R5 will run under O... |
9884ed23a1363b60936cd0865bf31909 | 103 410-7 | 1 Scope | The present document presents SAREF4AUTO, an extension of SAREF for the Automotive Domain. |
9884ed23a1363b60936cd0865bf31909 | 103 410-7 | 2 References | |
9884ed23a1363b60936cd0865bf31909 | 103 410-7 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.