{"id":440106,"date":"2024-10-20T08:12:59","date_gmt":"2024-10-20T08:12:59","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-13757-82023\/"},"modified":"2024-10-26T15:21:58","modified_gmt":"2024-10-26T15:21:58","slug":"bs-en-13757-82023","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-13757-82023\/","title":{"rendered":"BS EN 13757-8:2023"},"content":{"rendered":"
This document describes the functionalities and specifies the requirements of an adaptation layer to be applied when transporting M-Bus upper layers using a wireless communication protocol other than wireless M-Bus. These alternative radio technologies developed outside CEN\/TC 294 can be based on Internet Protocol or not and operate either in licensed or unlicensed frequency bands.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | European foreword <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 4 Abbreviations and symbols 4.1 Abbreviations <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 4.2 Symbols 5 Network architecture 5.1 Overview <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | Figure 1 \u2014 LPWAN network architecture overview 5.2 General description of network entities 5.2.1 Head End System 5.2.2 Core network 5.2.2.1 Network manager <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 5.2.2.2 Security server 5.2.3 Gateway 5.2.4 End device <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | Figure 2\u2014 End device LPWAN identifier and application address relations 6 General layer structure 6.1 Overview <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | Table 1 \u2014 General layer structure 6.2 Encapsulation schemes 6.2.1 M-Bus over non-IP based communication technologies <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | Table 2 \u2014 M-Bus over non-IP LPWAN encapsulation 6.2.2 M-Bus over IP based communication technologies Table 3 \u2014 M-Bus over IP-based LPWAN encapsulation <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 7 Adaptation layer description 7.1 Adaptation layer structure Table 4 \u2014 CI-fields of MBAL Table 5 \u2014 Structure of M-Bus Adaption layer with CI-field CFh 7.2 Adaptation layer services 7.2.1 MBAL Control field (MBAL-CL) 7.2.1.1 Structure of MBAL Control field <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | Table 6 \u2014 MBAL Control field in uplink Table 7 \u2014 MBAL Control field in downlink 7.2.1.2 Subfield Version Table 8 \u2014 MBAL-CL Version subfield 7.2.1.3 Subfield Access (uplink) <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | Table 9 \u2014 MBAL-CL Access subfield 7.2.1.4 Subfield Latency (downlink) Table 10 \u2014 MBAL-CL Latency subfield 7.2.1.5 Subfield Function code <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Table 11 \u2014 MBAL-CL Function code subfield (uplink) <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | Table 12 \u2014 MBAL-CL Function code subfield (downlink) 7.2.2 Other MBAL fields <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Annex A (informative) Overview of LPWAN technologies A.1 LPWAN features for metering communication A.2 Segregation matrix Table A.1 \u2014 LPWAN technologies comparison matrix <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Annex B (informative) MBAL implementation examples B.1 MBAL for alarm data pulling scenario Figure B.1 \u2014 M-Bus alarm data pulling using MBAL B.2 MBAL for user data push and pull <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure B.2 \u2014 M-Bus user data push and pull using MBAL B.3 Confirmed User Data transmission Figure B.3 \u2014 Confirmed user data transmission with MBAL <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Annex C (informative) Adaptation mechanism for Cat. NB (NB-IoT) and Cat. M1 (LTE-M) C.1 Cat. M1 and Cat. NB brief description C.2 Cat. M1 and Cat. NB characteristics Table C.1 \u2014 Comparison of Cat. M1 and Cat. NB as defined in 3GPP Release 13\/14 [8] C.3 Cat. M1 and Cat. NB network architecture C.3.1 General introduction <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | C.3.2 Architecture overview Figure C.1 \u2014 Simple architecture overview for an LTE network C.3.3 CIoT main features and access methods C.3.3.1 CIoT EPS optimizations <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | C.3.3.2 Power saving mode Figure C.2 \u2014 PSM and TAU mechanisms chronogram illustration C.3.3.3 Extended discontinuous reception <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Figure C.3 \u2014 eDRX feature chronogram illustration C.4 M-Bus over CIoT C.4.1 Overview C.4.2 Basic M-Bus over CIoT mechanism C.4.2.1 Overview <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Table C.2 \u2014 Basic M-Bus over CIoT protocol stack using DoNAS C.4.2.2 Basic M-Bus over CIoT Table C.3 \u2014 MBAL with CI-field in UDP Payload C.4.3 Advanced M-Bus over CIoT C.4.3.1 M-Bus over CIoT model using transfer level security <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Table C.4 \u2014 Protocol stack used for lightweight IP based communication including COSE security C.4.3.2 Connection establishment C.4.3.2.1 General <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Figure C.4 \u2014 Unsolicited end-to-end data example Figure C.5 \u2014 Unsolicited data transfer attacked with hostile response attempt <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Figure C.6 \u2014 Two-way communication sequence CoAP elements C.4.3.2.2 Introduction <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | C.4.3.2.3 Port number C.4.3.2.4 Datagram format Table C.5 \u2014 CoAP datagram format C.4.3.2.5 Header Table C.6 \u2014 CoAP message format (from [5]) <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Table C.7 \u2014 Mandatory CoAP header parameters <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Table C.8 \u2014 Option parameters for enabling the content C.4.3.2.6 Payload C.4.3.2.6.1 General C.4.3.2.6.2 COSE\/CBOR C.4.3.2.6.3 Payload organization Table C.9 \u2014 The CoAP payload <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table C.10 \u2014 The CoAP payload (COSE_Encrypt0 formatted) consists of organized CBOR objects C.4.3.2.6.4 Protected and unprotected header C.4.3.2.6.5 Protected header parameters Table C.11 \u2014 Protected header parameters C.4.3.2.6.6 Unprotected header parameters <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Table C.12 \u2014 Unprotected header parameters Table C.13 \u2014 kid COSE header parameters as a CBOR map <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | C.4.3.3 CBOR defined MBAL and payload content C.4.3.3.1 General C.4.3.3.2 Message content Table C.14 \u2014 Overview of currently supported protocol identifications and protocol revisions C.4.3.3.3 CBOR payload content C.4.3.3.3.1 General <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table C.15 \u2014 Payload components C.4.3.3.3.2 MBAL field Table C.16 \u2014 MBAL Component Table C.17 \u2014 MBAL subfield CBOR elements <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | C.4.3.4 Examples of implementation C.4.3.4.1 Security – COSE Content encryption\/authentication Table C.18 \u2014 CCM authenticated encryption algorithm overview <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table C.19 \u2014 IV example for an M-Bus device C.4.3.4.2 Services and parameters <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | C.4.3.4.3 Communication sequences \/ scenarios C.4.3.4.3.1 General C.4.3.4.3.2 Uni-directional end-to-end examples <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure C.7 \u2014 Uni-directional unsolicited messages from end device without CoAP reliability <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure C.8 \u2014 Unsolicited messages from end device with CoAP reliability <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure C.9 \u2014 Install scenario without HES acknowledgement (CNF-IR) C.4.3.4.3.3 Two-way examples <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure C.10 \u2014 SND-UD2\/RSP-UD scenario. CoAP reliability exploited <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure C.11 \u2014 SND-UD2\/RSP-UD scenario (continued) <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Annex D (informative) Adaptation mechanism for LoRaWAN D.1 LoRaWAN brief description D.2 LoRaWAN network architecture D.2.1 Overview D.2.2 Application server <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | D.2.3 End device D.2.4 Gateways D.2.5 Core network D.2.5.1 Network server D.2.5.2 Join server <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Figure D.1 \u2014 LoRaWAN network architecture and over the air activation mechanism D.3 LoRaWAN security services description <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | D.4 LoRaWAN main features D.5 LoRaWAN frame structure overview Table D.1 \u2014 LoRaWAN frame structure overview <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table D.2 \u2014 LoRaWAN frame control byte structure D.6 M-Bus over LoRaWAN D.6.1 M-Bus upper layers encapsulation in LoRaWAN <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table D.3 \u2014 M-Bus over LoRaWAN frame structure D.6.2 LoRaWAN and MBAL co-operation D.6.2.1 End device access and operation classes <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table D.4 \u2014 End device access mapped to LoRaWAN Class D.6.2.2 Acknowledgement D.6.2.3 Pending downlinks D.6.3 Implementation examples D.6.3.1 Overview <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | D.6.3.2 M-Bus over LoRaWAN installation procedure Figure D.2 \u2014 M-Bus over LoRaWAN installation procedure D.6.3.3 M-Bus over LoRaWAN for alarm data pulling <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Figure D.3 \u2014 M-Bus over LoRaWAN for alarm data pulling using MBAL D.6.3.4 M-Bus over LoRaWAN for User data push and pull <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Figure D.4 \u2014 M-Bus over LoRaWAN for user data push and pull <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Annex E (informative) Adaptation mechanism for TS-UNB E.1 TS-UNB\/MIOTY brief description E.2 MIOTY network architecture E.2.1 Overview Figure E.1 \u2014 Network architecture according to ETSI LTN with TS-UNB air interface <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | E.2.2 Service center E.2.3 End-point E.2.4 Base station E.3 MIOTY principles E.3.1 Device classes E.3.2 Scheduling and acknowledgement <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Figure E.2 \u2014 Uplink\/Downlink scheduling and acknowledgement E.4 MIOTY frame structure overview <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table E.1 \u2014 MIOTY frame structure E.5 M-Bus over MIOTY E.5.1 Encapsulation of M-Bus <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table E.2 \u2014 MPF values for M-Bus Table E.3 \u2014 M-Bus Data Payload E.5.2 MIOTY and MBAL co-operation E.5.2.1 End-point access and device classes <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Table E.4 \u2014 End-point access mapped to device class E.5.2.2 End-point latency E.5.2.3 Acknowledgement E.5.3 Implementation example E.5.3.1 General <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | E.5.3.2 M-Bus over MIOTY command workflow Figure E.3 \u2014 Command workflow for M-Bus over MIOTY <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Annex F (informative) Adaptation mechanism for Wize F.1 Wize brief description F.2 Wize services <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | F.3 Wize network architecture F.3.1 Overview Figure F.1 \u2014 Wize LPWAN network general architecture F.3.2 Uplink broadcast <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | F.3.3 Downlink unicast F.3.4 Downlink broadcast F.3.5 Wize message types and message flow Table F.1 \u2014 Wize protocol message types and flow <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Figure F.2 \u2014 Wize message flow <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | F.3.6 Wize security services and management <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Figure F.3 \u2014 Wize protocol security services overview F.3.7 Wize Data Link Layer (DLL) Table F.2 \u2014 Wize DLL Table F.3 \u2014 L6 frame of the Wize protocol <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | F.4 M-Bus over Wize F.4.1 Overview Table F.4 \u2014 Protocol layer structure for transporting M-Bus over Wize Table F.5 \u2014 M-Bus over Wize using MBAL encapsulation overview F.4.2 MBAL with CI-field <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table F.6 \u2014 MBAL-CL function code mapping to Wize DLL <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication systems for meters – Adaptation layer<\/b><\/p>\n |