hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6 AccessRight Management on remote SCL | |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6.1 AccessRight Resource creation | Interoperability Test Description Identifier: TD_M2M_MH_28 Objective: App creates an AccessRight resource via an accesRightCreateRequest on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.11.2 ETSI TS 102 690 [2], clause 9.3.2.10 Pre-test conditions: v... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6.2 AccessRight Retrieve | Interoperability Test Description Identifier: TD_M2M_MH_29 Objective: App retrieves accessRight resource via an accessRightRetrieveRequest (GET) on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.11.3 ETSI TS 102 690 [2], clause 9.3.2.10 Pre-test condi... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6.3 AccessRight Update | Interoperability Test Description Identifier: TD_M2M_MH_30 Objective: App updates attribute in accessRight resource via an accessRightUpdateRequest (PUT) on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.11.4 ETSI TS 102 690 [2], clause 9.3.2.10 Pre-t... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6.4 AccessRight Delete | Interoperability Test Description Identifier: TD_M2M_MH_31 Objective: App de-registers by deleting accessRightresource via an accessRightDeleteRequest on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.11.5 ETSI TS 102 690 [2], clause 9.3.2.10 Pre-test... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6.5 Unauthorized operation (Empty Requesting Entity) | Interoperability Test Description Identifier: TD_M2M_MH_32 Objective: App retrieve request is rejected due to Access Rights on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.11.1 ETSI TS 102 690 [2], clause 9.3.2.10 Pre-test conditions: void Test Sequ... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6.6 Unauthorized operation (Bad Requesting Entity) | Interoperability Test Description Identifier: TD_M2M_MH_33 Objective: App retrieve request is rejected due to Access Rights on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.11.1 ETSI TS 102 690 [2], clause 9.3.2.10 Pre-test conditions: void Test Sequ... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.6.7 Unauthorized operation (Insufficient Access Rights) | Interoperability Test Description Identifier: TD_M2M_MH_34 Objective: App delete request is rejected due to Access Rights on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.11.1 ETSI TS 102 690 [2], clause 9.3.2.10 Pre-test conditions: • Application <a... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.7 Group Management on remote SCL | |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.7.1 Group Resource creation | Interoperability Test Description Identifier: TD_M2M_ MH _35 Objective: App creates a group resource via a groupCreateRequest on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.21.2 ETSI TS 102 690 [2], clause 9.3.2.17 Pre-test conditions: void Test Se... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.7.2 Group Retrieve | Interoperability Test Description Identifier: TD_M2M_MH_36 Objective: App retrieves group resource via a groupRetrieveRequest (GET) on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.21.3 ETSI TS 102 690 [2], clause 9.3.2.17 Pre-test conditions: • App ... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.7.3 Group Update | Interoperability Test Description Identifier: TD_M2M_MH_37 Objective: App updates attribute in group resource via an groupUpdateRequest (PUT) on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.21.4 ETSI TS 102 690 [2], clause 9.3.2.17 Pre-test conditio... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.7.4 Group Delete | Interoperability Test Description Identifier: TD_M2M_MH_38 Objective: App delete group resource via an groupDeleteRequest (DELETE) on remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.21.5 ETSI TS 102 690 [2], clause 9.3.2.17 Pre-test conditions: • App h... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.7.5 Group Operations | Interoperability Test Description Identifier: TD_M2M_MH_39 Objective: App creates multiple contentInstance using group resource on Remote SCL Configuration: M2M_CFG_04, M2M_CFG_04, M2M_CFG_08, M2M_CFG_10 References: ETSI TS 102 921 [1], clause 10.21.2 ETSI TS 102 690 [2], clause 9.3.2.17 Pre-test conditions: • App has ... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.8 Announcement | |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.8.1 Application registration with announcement | Interoperability Test Description Identifier: TD_M2M_MH_41 Objective: App registration with Announcement Configuration: M2M_CFG_06, M2M_CFG_11 References: ETSI TS 102 921 [1], clause 10.9.2 ETSI TS 102 690 [2], clause 9.3.2.28 Pre-test conditions: • GSCL has registered to NSCL Test Sequence: Step Type Description 1 Sti... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.8.2 Application delete with announcement | Interoperability Test Description Identifier: TD_M2M_MH_42 Objective: App application delete with Announcement Configuration: M2M_CFG_06, M2M_CFG_11 References: ETSI TS 102 921 [1], clause 10.9.2 ETSI TS 102 690 [2], clause 9.3.2.28 Pre-test conditions: • GSCL has registered to NSCL • App has created an announceable Ap... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.2.8.3 Application De-Announce Ressources | Interoperability Test Description Identifier: TD_M2M_MH_43 Objective: App application De-Announce ressource Configuration: M2M_CFG_06, M2M_CFG_11 References: ETSI TS 102 921 [1], clause 10.9.2 ETSI TS 102 690 [2], clause 9.3.2.28 Pre-test conditions: • GSCL has registered to NSCL • App has created an announceable Appli... |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.3 End to End configuration testing | |
d1016e52d900f42ab00eef510629339d | 103 315 | 8.3.1 Resource management with re-targeting | Interoperability Test Description Identifier: TD_M2M_E2E_01 Objective: DA/GA adds a contentInstance resource < contentInstance> to the contentInstances resource of a specific container in remote NSCL via a contentInstanceCreateRequest Configuration: M2M_CFG_06, M2M_CFG_11 References: ETSI TS 102 921 [1], clause 10.19.2... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 1 Scope | The Internet of Things (IoT) presents a wide and growing range of communications requirements. Certain of these requirements are addressed by systems which are referred to as 'Low Throughput Networks' (LTN) in ETSI documents. The use cases addressed by LTN systems and the LTN systems characteristics are provided in ETS... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 2 References | |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 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... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 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... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 3 Definitions and abbreviations | |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: LTN family: complete solution within the scope of the LTN standard NOTE: LTN families are not necessarily interoperable. LTN standard: technical specifications developed by ETSI which describe architecture and protocols of LTN systems ... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: BS Base Station DA Device Application DL DownLink EP End-Point IoT Internet of Things IP Internet Protocol LPWAN Low Power Wide Area Network LTN Low Throughput Network NA Network Application RA Registration Authority RP Relay Point SC Service ... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4 LTN architecture description | |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.1 Overall description | LTN systems comprise a radio network and a core network tailored to the connectivity of IoT devices. Figure 4-1 is the overall architecture description of any LTN system. Blue boxes and blue lines are part of the LTN system, whereas grey lines and grey boxes are application specific. ETSI ETSI TS 103 358 V1.1.1 (2018-0... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.2 LTN reference architecture | This clause gives the reference architecture as the basis for all LTN families. It is a high-level decomposition into major components with a characterization of the interaction of the components (definition derived from [i.4]). Figure 4-2 depicts the LTN reference architecture in terms of functional blocks (i.e. the c... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.3 LTN functional blocks | |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.3.1 End-point | An End-Point (EP) is a leaf node of an LTN system that communicates application data between local Device Application (DA) and Network Application (NA). It shall connect to a base station over the A interface. If relay points are supported, it shall connect to a relay point over the A" interface. An EP shall be identif... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.3.2 Relay point | A Relay Point (RP) is an optional node in an LTN system. It shall connect to an EP over A'' interface and to a base station over A' interface. A RP may also communicate application data between local Device Application (DA) and Network Application (NA). A RP shall be identified by a IEEE EUI-64™ globally unique identif... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.3.3 Base station | A Base Station (BS) is a radio hub of an LTN system. It shall connect to a single service centre over interface B. It shall connect to end-points over interface A and relay points over interface A'. Base stations should implement provision for reduced service in case of disconnection from the SC. |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.3.4 Service centre | An LTN system shall have a single Service Centre (SC). The SC may perform the following functions: • forwarding application data packet, both uplink and downlink; • EP authentication, acting as either the other party of the authentication or a relay between the two authenticating parties; • configuration and/or subscri... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.3.5 Registration authority | An LTN system shall include the functionality of a Registration Authority (RA). The RA shall store identifiers and credentials of end-points and/or relay points. It may also store other parameters, such as: • secret key; • class of transmit power; • class of EP; • frequency capability; • owner of the EP and/or RP; • ch... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.4 LTN interfaces | |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.4.1 Interface A | Interface A is the air interface between EPs and BS. It shall be the primary air interface of any LTN system. It shall be a unidirectional or bidirectional interface between EP and BS. Interface A shall support EP mobility. It may carry signalling messages. Interface A shall exhibit the following specific features: • m... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.4.2 Interface A' | Interface A' is the air interface between RP and BS. It shall be a bidirectional or unidirectional interface. |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.4.3 Interface A'' | Interface A" is the air interface between EP and RP. It shall be a bidirectional or unidirectional interface. ETSI ETSI TS 103 358 V1.1.1 (2018-06) 10 |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.4.4 Interface B | Interface B is the interface between a BS and the SC. Data flow over the interface B may include decoded UL radio bursts, user packet for DL transmission, signalling and BS management messages. Interface B shall be secured, using IP-based encryption technology or equivalent. |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.4.5 Interface C | Interface C is the interface between a SC and the RA. Data flow over the interface C may include credentials of end-points and relay points. |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 4.4.6 Interface D | Interface D is the interface between two SC of the same LTN family to support roaming. Interface D is optional; if implemented, it shall use secured IP-based links. |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 5 LTN key characteristics | |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 5.1 Cooperative reception over air interfaces | Cooperative reception is the ability of a single UL transmission to be received simultaneously by several base stations. This feature is implemented with (see Figure 5-1): • overlap of BS radio coverage, which is intentionally included in the radio design of an LTN system; • deduplication of the received UL packets in ... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 5.2 LTN politeness and coexistence | LTN systems shall implement mitigation techniques according to applicable spectrum regulations. If deployed in Europe, LTN devices shall be compliant with ETSI EN 300 220-1 [1] and ETSI EN 300 220-2 [2]. All LTN systems shall be designed to withstand interference from other systems operating in the same SRD frequency b... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 5.3 Options, profiles and families | The overall LTN architecture and the LTN functional blocks detailed in sub-clauses 4 apply to all LTN systems, irrespective of the types of application they serve. Nevertheless, flexibility in the implementation of the radio interface helps LTN to address specific requirements. This flexibility is obtained by means of ... |
d1342b53e36c738a5406ad7ce6cb3988 | 103 358 | 5.4 End-point classes | An LTN system shall support one or more classes of EP as described in Table 5-1. Table 5-1: the four classes of end-points in an LTN system Class Description Purpose Z UL-only: End-point is UL-only; it does not receive DL application messages. Application does not require DL. A Pull-based: EP receiver is only available... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 1 Scope | The present document is part 1 of a multi-part deliverable that define the fourth generation of high-speed data-over- cable systems, commonly referred to as the DOCSIS® 3.1 specifications. This specification was developed for the benefit of the cable industry, and includes contributions by operators and vendors from No... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 2 References | |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 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... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 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... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 3 Definitions, symbols and abbreviations | |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: cable modem: Layer 2 termination device that terminates the network end of a DOCSIS® link headend: central location on the cable network that is responsible for injecting broadcast video and other signals in the downstream direction |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CCAP Converged Cable Access Platform CM Cable Modem CMTS Cable Modem Termination System CPE Customer Premise Equipment DHCP Dynamic Host Configuration Protocol EQAM Edge quadrature amplitude modulation HFC Hybrid Fibre Coax IP Internet Protoco... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 4 Background | |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 4.1 Broadband Access Network | A coaxial-based broadband access network is assumed. This may take the form of either an all-coax or hybrid- fibre/coax network. The generic term "cable network" is used in the present document to cover all cases. A cable network uses a tree-and-branch architecture with analogue transmission. The key functional charact... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 4.2 DOCSIS® Network and System Architecture | The elements that participate in the provisioning of DOCSIS® services are shown in figure 1. Figure 1: The DOCSIS® Network The CM connects to the operator's cable network and to a home network, bridging packets between them. Many CPE devices can connect to the CM's LAN interfaces. CPE devices can be embedded with the C... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 4.3 Service Goals | As cable operators have widely deployed high-speed data services on cable television systems, the demand for bandwidth has increased. To this end, it was decided to add new features to the DOCSIS® specification for the purpose of increasing system and channel capacity, enhancing network security, and deploying new serv... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 4.4 Backward Compatibility | The present document defines the DOCSIS® 3.1 interface. Prior generations of DOCSIS® were commonly referred to as the DOCSIS® 1.0, 1.1, 2.0, and 3.0 interfaces. DOCSIS® 3.1 provides backward-compatibility with equipment built to certain previous versions. DOCSIS® 3.1-compliant CMs interoperate seamlessly with DOCSIS® 3... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 4.5 Reference Architecture | The reference architecture for data-over-cable services and interfaces is shown in figure 3. Figure 3: Data-over-Cable Reference Architecture ETSI ETSI TS 103 311-1 V1.1.1 (2017-02) 9 The lighter shaded areas are related functionality, but are out of the scope of DOCSIS® specifications. Boxes represent functional compo... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 5 Overview of the Multi-part ETSI Standard | |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 5.1 Part 1: General; DOCSIS® 3.1 | The present document. |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 5.2 Part 2: Physical Layer; DOCSIS® 3.1 | There are differences in the cable spectrum planning practices adopted for different regions of the world. For the new PHY layer defined in this specification, there is flexibility to deploy the technology in any spectrum plan; therefore, no special accommodation for different regions of the world is required for this ... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 5.3 Part 3: MAC and Upper Layer Protocols; DOCSIS® 3.1 | Part 3 defines the MAC layer protocols of DOCSIS® 3.1 as well as requirements for upper layer protocols (e.g. IP, DHCP, etc.). DOCSIS® 3.0 introduced new MAC layer features beyond what were present in earlier versions of DOCSIS®. DOCSIS® 3.1 introduces a new PHY layer feature to further increase the peak downstream and... |
5411d23b3860ba70431793f1e072727e | 103 311-1 | 6 Requirements for Compliance | To claim compliance to ETSI TS 103 311, implementations shall comply with the requirements statements in all three parts of the present multi-part deliverable, and in addition shall comply with the DOCSIS® 3.1 Security Specification [3], the DOCSIS® 3.1 CM-OSSI Specification [4] and the DOCSIS® 3.1 CCAP-OSSI Specificat... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 1 Scope | The present document establishes the specifications for the MAMES (Multiple Alert Message Encapsulation over Satellite) Protocol. Starting from an overview of the MAMES objectives and operations, the MAMES Architecture is presented: the MAMES functional entities are identified and the MAMES positioning in a protocol-st... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 2 References | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 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... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 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... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 3 Definitions and abbreviations | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Alert Intermediary System: telecommunications network or node that is located at the user side of the Alert Network and that forwards alert-related (MAMES or non-MAMES) messages Alert Issuer: entity that generates Alert Messages and fo... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: A4A Alert-For-All (Alert4All) ACK Acknowledgement AES Advanced Encryption Standard AES-CBC AES Cipher Block Chaining AES-CTR AES Counter AM Alert Message AMH Alert Message Header ASN.1 Abstract Syntax Notation One CAP Common Alerting Protocol ... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4 MAMES Objectives and Operation | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.1 MAMES Objectives | MAMES main objectives are: • the definition of an encapsulation protocol for Alert Protocol Messages transport over satellite links, as well as over other terrestrial communication links, like GSM, LTE, etc.; • the provision of a flexible and extensible encapsulation scheme; • the encapsulation of a single or a concate... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.2 Overview of MAMES Operation | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.2.1 MAMES Network Entities: MAMES Provider and MAMES Receiver | The objective of this clause is to provide an overview of MAMES basic operation and introduce the MAMES network entities (MAMES Alert Provider and MAMES Alert Receiver). Figure 4.1 illustrates the basic MAMES alerting operation, showing the network hierarchy of the alerting chain, the main involved entities, the links ... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.2.2 MAMES Operative Modes: Direct and Indirect MAMES Alerting | The two MAMES operative modes are described in the following. Although terrestrial communications networks may also be used to transport MAMES-based messages, in the rest of the document the focus is on the SatCom/SatNav systems. The two MAMES operative modes are depicted in Figure 4.2. These are: • Direct MAMES Alerti... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.2.3 The MAMES Agents | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.2.3.1 MAMES Network Reference Model | The MAMES protocol service is implemented by MAMES Agents located in the MAMES network entities. A MAMES Agent is a software module that processes the MAMES Protocol. Two types of MAMES Agents are defined: • the MAMES Alerter-Side Agent; • the MAMES User-Side Agent. The former serves the MAMES Alert Provider and the la... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.2.3.2 MAMES Alerter-Side Agent | The MAMES Alerter-Side Agent is the MAMES Agent serving the MAMES Alert Provider. It is responsible for the initiation of the MAMES Protocol. Its main function is to receive the Alert Protocol Message as a Service Data Unit (SDU) and produce the MAMES Message as Protocol Data Unit (PDU), enabling the correct transmissi... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 4.2.3.3 MAMES User-Side Agent | The MAMES User-Side Agent is the MAMES Agent serving the MAMES Alert Receiver. It is responsible for the termination of the MAMES Protocol. Its main functions are: • parsing of MAMES Message originated by the MAMES Alert Provider, including Alert Protocol Message(s) (if any) decapsulation (forward link); • composition ... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5 MAMES Architecture | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.1 Functional Architecture | The objective of this clause is to provide a high level description of the main MAMES functional entities, which shall be part of the MAMES Agents. A list of the main MAMES functional entities is reported in Table 5.1. For each of them a general description and a specific description based on the MAMES Agents the funct... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2 Protocol Architecture | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2.1 MAMES Positioning in a Protocol-stack Architecture | The objective of this clause is to define the MAMES positioning in a protocol-stack architecture, assuming a generic satellite-based communications network (for terrestrial networks, the satellite-specific entities would have to be replaced by the corresponding terrestrial entities). ETSI ETSI TS 103 337 V1.1.1 (2015-0... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2.2 Protocol Architecture for Direct MAMES Alerting | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2.2.1 Scenario A1 | In Scenario A1 the MAMES Receiver is inside the satellite user segment and MAMES and Alert Protocol terminations are co-located (the Alerting Device and the MAMES Alert Receiver are co-located). Figure 5.2 depicts the Scenario A1 protocol stack architecture. Satellite Network Local or Wide Area Network Lower Layers (Sa... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2.2.2 Scenario A2 | In Scenario A2 the MAMES Receiver is inside the satellite user segment, but the MAMES and Alert Protocol terminations are not co-located. The Alerting Device is outside the satellite user segment and it is connected to the MAMES Receiver via one or more Alert Intermediary Systems. Figure 5.4 depicts the Scenario A2 pro... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2.3 Protocol Architecture for Indirect MAMES Alerting | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2.3.1 Scenario B1 | In Scenario B1 the MAMES Receiver is outside the satellite user segment and MAMES and Alert Protocol terminations are co-located. Figure 5.5 depicts the Scenario B1 protocol stack architecture. ETSI ETSI TS 103 337 V1.1.1 (2015-05) 22 Satellite Network Local or Wide Area Network Alert Issuer Upper Layers Lower Layers (... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 5.2.3.2 Scenario B2 | In Scenario B2 the MAMES Receiver is outside the satellite user segment and the MAMES and Alert Protocol terminations are not co-located. One or more Alert Intermediary Systems are in between the MAMES Alert Provider and the MAMES Alert Receiver (MAMES Message relaying) and between the MAMES Alert Receiver and the Aler... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6 MAMES Messages | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6.1 Overall Structure | The objective of this clause is to provide the definition of the MAMES Messages. Following a hierarchical organization, the MAMES message types are presented in clause 6.2, the headers are defined in clause 6.3 and details on the header fields are reported in clause 6.4. To introduce the definition of the MAMES message... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6.2 MAMES Message Types | |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6.2.1 Overview of MAMES Message Types | Different types of MAMES Message are defined based on the message purpose (e.g. message function) and satellite network transmission constraints (e.g. MAMES Transmission over GNSS Systems). Five types of MAMES Messages are defined. These are: • MAMES ALERT; • MAMES Ultra-short ALERT (Us-ALERT); ETSI ETSI TS 103 337 V1.... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6.2.2 MAMES ALERT | MAMES ALERT Message enables the encapsulation of a single or multiple Alert Protocol Messages that need to be delivered to the Alerting Device. ETSI ETSI TS 103 337 V1.1.1 (2015-05) 26 A MAMES ALERT: • enables the encapsulation of different Alert Protocol Messages including all the Alert Protocol specific messages type... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6.2.3 MAMES Ultra-Short ALERT | The MAMES Ultra-short Message is the shortest MAMES Message defined with the aim to allow the transmission of MAMES Messages over narrowband satellite channels (e.g.: MAMES over GNSS). A MAMES Ultra-short ALERT: • is an extreme solution used in exceptional cases (e.g.: network resources limited contexts, out-of-band si... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6.2.4 MAMES UPDATE | MAMES UPDATE Message is an update at MAMES level. It is an update of a valid previously transmitted MAMES Message (MAMES ALERT or MAMES UPDATE). A MAMES UPDATE: • handles updates at MAMES level enabling the encapsulation of those Alert Protocol Messages that do not include at Alert Protocol level a means to identify a ... |
de05721b3b866b1bb84caad5a903e23a | 103 337 | 6.2.5 MAMES CANCEL | A MAMES CANCEL Message is a cancellation at MAMES level. It declares a valid previously transmitted MAMES Message (MAMES ALERT, MAMES Ultra-short ALERT, MAMES UPDATE) as obsolete. MAMES CANCEL handles MAMES errors enabling a MAMES Alert Provider to notify the MAMES Alert Receiver that a previous sent MAMES Message shal... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.