hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 2 References | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 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... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 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... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 3 Definition of terms, symbols and abbreviations | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 305 200-2-2 [2] and the following apply: Access Gateway (AG): gateway that interworks a significant number of analogue lines to a packet network downstream: relative location in the fixed access network in the direction of Network Termination Point fi... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI EN 305 200-2-2 [2] apply. |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 305 200-2-2 [2] and the following apply: AG Access Gateway ATM Automated Teller Machine FTTdp Fiber To The distribution point FWA Fixed Wireless Access FXS Foreign eXchange Station LL Leased Line MEC Multi-access Edge Computing MIB Management ... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4 Global KPIs of ETSI EN 305 200-2-2 | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.1 Fixed broadband access networks | The network schematic used in the present document is shown in Figure 1 (taken from of ETSI EN 305 200-2-2 [2]). Figure 1: Fixed access network implementations Within the Fixed Access Network (FAN), the term Network Distribution Node (NDN) is employed to describe a variety of aggregations of Network Telecommunications ... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2 KPIs for energy management | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.1 Global KPI (KPIEM) for fixed access networks | From ETSI EN 305 200-2-2 [2], KPIEM is a combination of two separate KPIs, in a common assessment period, as follows: 1) the Objective KPI for task effectiveness expressed as KPITE (see clause 4.2.2.2); 2) the Objective KPI for renewable energy contribution expressed as KPIREN (see clause 4.2.2.3); and both of these Ob... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2 Objective KPIs | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.1 Energy consumption (KPIEC) | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.1.1 General | The present document supports the evaluation of the energy consumption required to provide a given level of service as a primary objective. From ETSI EN 305 200-2-2 [2], KPIEC, for a given assessment period, is defined mathematically as: = ∑ + ∑ where, for the assessment period: i = index of OS... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.1.2 CP-powered equipment within the calculation of KPIEC | 4.2.2.1.2.1 General The presence of CP-powered equipment within the fixed access network requires an amendment of the formula for KPIEC of clause 4.2.2.2.1 as follows: = ∑ + ∑ + with: = ∑ where, for the assessment period: k = index of AG, FTTdp and ONT equipment P = total number of ... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.1.3 Measurement (and estimation) of total energy consumption | As indicated above KPIEC (as either KPIEC-measured or KPIEC-estimated) is the arithmetic sum of the consumption of all the NTE of the fixed access network, together with the energy consumed by their supporting infrastructure where all the NTE is under common governance. The supporting infrastructure considers powering;... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.2 Task effectiveness (KPITE) | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.2.1 General | The present document supports the evaluation of the task effectiveness as a primary objective. KPITE is a measure of the data volume transported across the fixed access network per unit of energy consumed by the entire network. An improvement of KPITE reflects a reduction of the overall energy consumption required to d... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.2.2 Measurement of data volumes | The measurement of the total data volume transported across the fixed network could be made at different probing points, from each NDN, up to the core network. Nevertheless, measuring at each NDN is quite complex both due to the quantity of equipment involved and the lack of such probing points in legacy equipment. Pra... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.3 Renewable energy (KPIREN) | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.3.1 General | From ETSI EN 305 200-2-2 [2], KPIREN , for a given assessment period, is defined mathematically as: 1 1 N M C R C R OS OS NDN NDN i i j j i j KPIEC KPIREN × + × = = = where, for the assessment period: i = index of OS j = index of NDN sites N = total number of OS M = total number of NDN sites i OS C = energy consump... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 4.2.2.3.2 Measurement of renewable energy consumption | ETSI EN 305 200-2-2 [2] and the present document support the use of renewable energy as a primary objective. KPIREN is the ratio of energy consumption from renewable sources to the total energy consumption of clause 4.2.2.1. It is a dimensionless number. Only the sources contributing to KPIEC will be taken into account... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5 Collection of data | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.1 General | The data collection provides the input for KPI calculation. Data are obtained from different sources at the sites or equipment comprising the fixed access network as described in clause 4. This clause describes the origin of the data and the way they could be collected. It is not within the scope of the present documen... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2 Estimation of energy consumption and renewable content | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2.1 Energy consumption | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2.1.1 Overview | The estimation of the energy consumption is given by the KPIEC indicator. For a fixed access network, composed of thousands of remote sites, the KPIEC for global access network will be the arithmetic sum of all KPIEC, estimated or measured, for each site (OS or NDN). This is the same for the objective KPIREN. For examp... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2.1.2 Energy bills | Most sites connected to the grid are equipped with a meter provided by the electricity supplier. This meter allows the supplier to collect (manually or automatically) the energy consumed during a certain period (typically monthly). The collected information on the consumption are used by the supplier to invoice the cus... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2.1.3 Meters installed by the operator (smart metering) | Some operators, for various reasons, have deployed their own meters on some, or all, of their sites, together with a software platform to analyse data and produce detailed reporting. This solution, even if it is the best to know clearly where energy is consumed, is very costly because it needs to deploy, instead of pri... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2.1.4 Energy consumption provided by the equipment | Certain equipment such as servers and even NTEs, is now able to collect internally information on its own energy consumption and store this information in a Management Information Base (MIB). NOTE: Older equipment does not implement such features and this option is of limited value for legacy installations. The MIB can... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2.1.5 Network and location sharing | Fixed infrastructure sharing means the process by which operators share their infrastructure to deliver a fixed service to end users. In the case of the fixed access network, a challenge will be to be to split the consumption between several stakeholders, knowing that part of the network and the sites could be shared w... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.2.2 Renewable energy | Two different methods are possible to collect data for renewable energy: • measure the total of energy generated from renewable sources in a site; • measure the renewable energy consumption of the site (which may differ form that produced at the site). 5.3 Data related to traffic For KPITE, (related to measure the data... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.4 Clarification of data | There are two different types of data which are basic to KPITE calculation: • energy consumption: all data containing information on the energy consumed or any energy generated by renewable sources; • data-traffic: all data containing information on the volumes of information (uplink and downlink) exchanged on the netw... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 5.5 Treatment of data types | Each type of data refers to one or more objectives indicators (KPIEC, KPITE, KPIREN). The data will have to be identified to provide the appropriate information for the calculation method of the KPIs: • data related to energy consumption as input for KPIEC; • data related to renewable energy generated as input for KPIR... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 6 Trend analysis | |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 6.1 Overview | Fixed access networks have developed significantly over recent years and offer data-oriented services that include, in addition to voice communications, multimedia communication, online gaming, high-quality video streaming, and many other future services needing increasing bandwidth and generating substantial growth of... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 6.2 Renewable energy sources | Fixed access network sites could be supplied in part or in full using the renewable energy. Different ways to generate renewable energy are presented in Annex A. Currently, the most important part of renewable energy in fixed access network is the use of solar photovoltaic panels for energy generation. This has the adv... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 6.3 Intelligent management | The fixed access network should operate in an "energy aware" way, so to minimize its energy consumption while delivering the service requested by the customer. During the periods of lower customer traffic it should apply, as far as possible, applicable standby and sleep modes so to aim at an energy consumption behaviou... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 6.4 Summary of possible actions to improve KPIEM | Table 1 summarizes the different techniques to improve KPIEM by the reduction of energy consumption. Table 1: Techniques for improvement of KPIEM Approach Energy savings Advantages Considerations Use of ICT equipment having wide temperature and humidity operating range Up to 30 %. Significant savings when fresh air coo... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 6.5 Reporting of trend data | KPIEM represented by the combination of KPITE or KPIREN is a measure of the energy management across an entire fixed access network. Operators can demonstrate their commitment to improving the energy management by highlighting trends in the measured values of KPITE or KPIREN. However, certain operational decisions can ... |
b9795efe25281bc46e92bb406f342429 | 105 200-2-2 | 7 Reporting templates | As specified in the ETSI EN 305 200-2-2 [2] the following values shall be reported for the sites within the fixed access network for which the KPIEM has been determined using the template of Table 2: • TKPI: the period of time over which Objective KPIs are assessed; • TREPEAT; the time between which the Objective and G... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 1 Scope | The present document describes the end-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points. oneM2M functional architecture focuses on the Service Layer aspects and takes Underlying Network-independent view of the end-to-end services. The Underlying... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 2 References | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 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 reference document (including any amendments) applies. Referenced documents which ar... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 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 reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 3 Definitions and abbreviations | For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 [i.29] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TS 118 111 [i.29]. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access control attributes: set of parameters of the Originator, target resource, and environment against which there could be rules evaluated to control access NOTE: An example of Access Control Attributes of Originator is a role. Exam... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 3.2 Abbreviations and Acronyms | For the purposes of the present document, the following abbreviations and acronyms apply: 2G Second Generation 3GPP 3rd Generation Partnership Project 3GPP2 3rd Generation Partnership Project 2 A/AAAA IPv4/IPv6 DNS records that are used to map hostnames to an IP address AAA Authentication, Authorization, Accounting AAA... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 4 Conventions | The keywords "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.28]. To improve readability: • The information elements of oneM2M Request/Response messages will be referred to as parameters. Parameter abbreviations w... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5 Architecture Model | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.1 General Concepts | Figure 5.1-1 depicts the oneM2M Layered Model for supporting end-to-end (E2E) M2M Services. This layered model comprises three layers: Application Layer, Common Services Layer and the underlying Network Services Layer. Application Layer Common Services Layer Network Services Layer Figure 5.1-1: oneM2M Layered Model |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2 Architecture Reference Model | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2.1 Functional Architecture | Figure 5.2.1-1 illustrates the oneM2M functional architecture. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 19 AE AE Mca Mca Mca Mcc Mcn Mcn CSE CSE NSE NSE Field Domain Infrastructure Domain To Infrastructure Domain of other Service Provider Mcc’ Figure 5.2.1-1: oneM2M Functional Architecture NOTE 1: Other reference points a... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2.2 Reference Points | A reference point consists of one or more interfaces of any kind. The following reference points are supported by the Common Services Entity (CSE). The "Mc(-) nomenclature is based on the mnemonic "M2M communications". NOTE: Information exchange between two M2M Entities assumes the usage of the transport and connectivi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2.2.1 Mca Reference Point | Communication flows between an Application Entity (AE) and a Common Services Entity (CSE) cross the Mca reference point. These flows enable the AE to use the services supported by the CSE, and for the CSE to communicate with the AE. NOTE: The AE and the CSE may or may not be co-located within the same physical entity. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2.2.2 Mcc Reference Point | Communication flows between two Common Services Entities (CSEs) cross the Mcc reference point. These flows enable a CSE to use the services supported by another CSE. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2.2.3 Mcn Reference Point | Communication flows between a Common Services Entity (CSE) and the Network Services Entity (NSE) cross the Mcn reference point. These flows enable a CSE to use the supported services (other than transport and connectivity services) provided by the NSE. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2.2.4 Mcc' Reference Point | Communication flows between two Common Services Entities (CSEs) in Infrastructure Nodes (IN) that are oneM2M compliant and that resides in different M2M SP domains cross the Mcc' reference point. These flows enable a CSE of an IN residing in the Infrastructure Domain of an M2M Service Provider to communicate with a CSE... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 5.2.2.5 Other Reference Points | • See clause 12.2.1 for Mch reference point. • See clause 6.2.4 for Mc, Mp, Ms and Ia reference points. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 21 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6 oneM2M Architecture Aspects | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.1 Configurations supported by oneM2M Architecture | The possible configurations of inter-connecting the various entities supported within the oneM2M system are illustrated in figure 6.1-1. The illustration does not constrain the multiplicity of the entities nor require that all relationships shown are present. Figure 6.1-1: Configurations supported by oneM2M Architectur... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2 Common Services Functions | This clause describes the services provided by the Common Services Layer in the M2M System. Such services reside within a CSE and are referred to as Common Services Functions (CSFs). The CSFs provide services to the AEs via the Mca reference point and to other CSEs via the Mcc reference point. CSEs interact with the NS... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.1 Application and Service Layer Management | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.1.1 General Concepts | The Application and Service Layer Management (ASM) CSF provides management of the AEs and CSEs on the ADNs, ASNs, MNs and INs. This includes capabilities to configure, troubleshoot and upgrade the functions of the CSE, as well as to upgrade the AEs. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 24 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.1.2 Detailed Descriptions | The ASM CSF provides management capabilities for CSEs and AEs. Figure 6.2.1.2-1: Management Layers and Function The ASM CSF utilizes the functions provided by the Device Management (DMG) CSF for interaction with the Management Server. The management functions include: • Configuration Function (CF): This function enable... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.1.2.1 Software Management Function | The Software Management Function (SMF) provides the capability to manage software components (e.g. Software Package, Software Module) for AEs and CSEs. The ASM CSF provides the capability to manage the lifecycle of the Software Packages for a CSE or an AE. AE Software Packages may be deployed on any Node that supports ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.2 Communication Management and Delivery Handling | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.2.1 General Concepts | The Communication Management and Delivery Handling (CMDH) CSF provides communications with other CSEs, AEs and NSEs. The CMDH CSF decides at what time to use which communication connection for delivering communications (e.g. CSE-to-CSE communications) and, when needed and allowed, to buffer communication requests so th... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.2.2 Detailed Descriptions | The service that AEs or CSEs can request from the CMDH CSF is to transport some data to a specific target (CSE or AE), according to given delivery parameters while staying within the constraints of provisioned communication management and delivery handling policies. The content of the data provided by the Originator do... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.3 Data Management and Repository | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.3.1 General Concepts | One of the purposes of CSEs is to enable AEs to exchange data with each other. The Data Management and Repository (DMR) CSF is responsible for providing data storage and mediation functions. It includes the capability of collecting data for the purpose of aggregating large amounts of data, converting this data into a s... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.3.2 Detailed Descriptions | The DMR CSF provides the capability to store data such as Application data, subscriber information, location information, device information, semantic information, communication status, access permission, etc. The data stored by the DMR CSF enables management of the data and provides the foundation of Big Data. The fol... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4 Device Management | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.1 General Concepts | The Device Management (DMG) CSF provides management of device capabilities on MNs (e.g. M2M Gateways), ASNs and ADNs (e.g. M2M Devices), as well as devices that reside within an M2M Area Network. Application Entities (AE) can manage the device capabilities on those Nodes by using the services provided by the DMG CSF al... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.1.1 Device Management Architecture | In order to manage the CSE and device capabilities of the MNs, ASNs and ADNs, the DMG can utilize existing device management technologies (e.g. TR-069 [i.3], OMA-DM [i.4], and LWM2M [i.5]) in addition to management of Management Resources across the Mcc reference point. When the device management technology is used to ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.1.2 Management Server Interaction | 6.2.4.1.2.1 Overview The DMG CSF in the IN has the capability to utilize Management Servers from existing device management technologies (e.g. TR-069 [i.3], OMA DM [i.4], LWM2M [i.5]) to implement the Device Management functions. The IN-DMG-MA communicates with the Management Server using the ms interface that is provi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.1.3 Management Client Interaction | 6.2.4.1.3.1 Overview The DMG CSF in the MN or ASN can use the Management Client from existing management technologies (e.g. TR-069 [i.3], OMA DM [i.4], LWM2M [i.5]) to implement the Device Management functions. The MN-DMG- MA or ASN-DMG-MA communicates with the Management Client using the la interface (e.g. DM-7, 8, 9 ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.1.4 Device Management Resource Lifecycle | 6.2.4.1.4.1 Resource Attributes from Device Management Resources The lifecycle of a Device Management Resource is implemented using the resource management information defined in clause 9.1 through clause 9.5 and the corresponding procedures to Create, Retrieve, Update and Delete the resources are defined in clause 10.... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.2 Detailed Descriptions | The DMG CSF provides capabilities for the purpose of managing M2M Devices/Gateways as well as devices in M2M Area Networks. Figure 6.2.4.2-1: Device Management Entities and Functions ETSI ETSI TS 118 101 V1.0.0 (2015-02) 31 Such capabilities include: • Device Configuration Function (DCF): This function includes the con... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.2.1 Device Configuration Function | The Device Configuration Function (DCF) provides the configuration of device capabilities that are necessary to support M2M Services and AEs in M2M Devices, M2M Gateways or devices in an M2M Area Network. These device configuration capabilities include: • Discovery of a device's management objects and attributes. • Abi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.2.2 Device Diagnostics and Monitoring Function | The Device Diagnostics and Monitoring Function (DDMF) permits the troubleshooting of device capabilities that are necessary to support M2M Services and AEs in M2M Devices, M2M Gateways or devices in an M2M Area Network. These device diagnostic and monitoring capabilities include: • Configuration of diagnostics and moni... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.2.3 Device Firmware Management Function | The Device Firmware Management Function (DFMF) provides lifecycle management for firmware associated with a device. Device firmware is comprised of firmware modules and artefacts (e.g. configuration files) that are maintained on a device. A device can maintain more than one firmware image and the capability to manage i... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.4.2.4 Device Topology Management Function | The Device Topology Management Function (DTMF) is a function that is specific to M2M Gateways where an M2M Gateway maintains zero or more M2M Area Networks. These device topology management capabilities include: • Configuration of the topology of the M2M Area Network. • Retrieval of information related to the devices a... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.5 Discovery | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.5.1 General Concepts | The Discovery (DIS) CSF searches information about applications and services as contained in attributes and resources. The result of a discovery request from an Originator depends upon the filter criteria and is subject to access control policy allowed by M2M Service Subscription. An Originator could be an AE or anothe... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.5.2 Detailed Descriptions | The DIS CSF uses the Originator provided filter criteria (e.g. a combination of keywords, identifiers, location and semantic information) that can limit the scope of information returned to the Originator. The discovery request indicates the address of the resource where the discovery is to be performed. Upon receiving... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.6 Group Management | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.6.1 General Concepts | The Group Management (GMG) CSF is responsible for handling group related requests. The request is sent to manage a group and its membership as well as for the bulk operations supported by the group. When adding or removing members to/from a group, it is necessary to validate whether the group member complies with the p... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.6.2 Detailed Descriptions | The GMG CSF enables the M2M System to perform bulk operations on multiple devices, applications or resources that are part of a group. In addition, the GMG CSF supports bulk operations to multiple resources of interest and aggregates the results. It facilitates access control based on grouping. When needed and availabl... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.7 Location | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.7.1 General Concepts | The Location (LOC) CSF allows AEs to obtain geographical location information of Nodes (e.g. ASN, MN) for location-based services. Such location information requests can be from an AE residing on either a local Node or a remote Node. NOTE: Geographical location information can include more than simply the longitude and... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.7.2 Detailed Descriptions | The LOC CSF obtains and manages geographical location information based on requests from AEs residing on either a local Node or a remote Node. The LOC CSF interacts with any of the following: • a location server in the Underlying Network; • a GPS module in an M2M device; or • information for inferring location stored i... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.8 Network Service Exposure, Service Execution and Triggering | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.8.1 General Concepts | The Network Service Exposure, Service Execution and Triggering (NSSE) CSF manages communications with the Underlying Networks for accessing network service functions over the Mcn reference point. The NSSE CSF uses the available/supported methods for service "requests" on behalf of AEs. The NSSE CSF shields other CSFs a... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.8.2 Detailed Descriptions | The NSSE CSF manages communication with the Underlying Networks for obtaining network service functions on behalf of other CSFs, remote CSEs or AEs. The NSSE CSF uses the Mcn reference point for communicating with the Underlying Networks. The M2M System allows the Underlying Networks to control network service procedur... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.9 Registration | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.9.1 General Concepts | The Registration (REG) CSF processes a request from an AE or another CSE to register with a Registrar CSE in order to allow the registered entities to use the services offered by the Registrar CSE. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 35 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.9.2 Detailed Descriptions | Registration is the process of delivering AE or CSE information to another CSE in order to use M2M Services. An AE on an ASN, an MN or an IN performs registration locally with the corresponding CSE in order to use M2M services offered by that CSE. An AE on an ADN performs registration with the CSE on an MN or an IN in ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.10 Security | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.10.1 General Concepts | The Security (SEC) CSF comprises the following functionalities: • Sensitive data handling; • Security administration; • Security association establishment; • Access control including identification, authentication and authorization; • Identity management. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 36 Sensitive data handling... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.