Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 26.850  Word version:  16.0.0

Top   Top   Up   Prev   None
1…   5… 
5 IoT device analysis  5.0 General  5.1 Classes of constrained devices  5.2 3GPP device categories  5.3 Device classification for MBMS IoT reception  6 MBMS for NB-IoT device categories  6.1 MBMS User Service Announcement Profile  6.2 MBMS IoT profiles for file download delivery method  7 Solutions  7.1 Overview of CoAP  7.2 Overview of LwM2M  7.3 Solutions for File Repair using CoAP  7.4 Binary data formats  7.5 Solution for announcement during wake-up periods  7.6 Solution for announcement with critical data delivery  7.7 Solution for reception report procedures  7.8 Solution for service announcement procedures  7.9 ASN.1 PER binary FDT instance definition  8 Conclusions  $ Change history 

 

5  IoT device analysis  p. 9

5.0  General  p. 9

5.1  Classes of constrained devices  p. 9

5.2  3GPP device categories  p. 10

5.3  Device classification for MBMS IoT reception  p. 10

6  MBMS for NB-IoT device categories  p. 11

6.1  MBMS User Service Announcement Profile  p. 11

6.2  MBMS IoT profiles for file download delivery method  p. 11

6.2.0  Introduction  p. 11

6.2.1  Common FDT-Instance and File attributes for MBMS IoT profiles  p. 12

6.2.2  FDT-Instance specific Elements and Attributes for MBMS IoT profiles  p. 12

6.2.3  FDT File specific Elements and Attributes for MBMS IoT profiles  p. 12

6.2.4  3GPP-defined FDT extensions for MBMS IoT profiles  p. 13

7  Solutions  p. 14

7.1  Overview of CoAP  p. 14

7.1.0  General  p. 14

7.1.1  Comparison to HTTP  p. 15

7.1.2  Logical Architecture Model  p. 15

7.1.2.0  General  p. 15

7.1.2.1  CoAP Messaging Model  p. 15

7.1.2.2  Methods and Response Codes  p. 16

7.1.3  Message Format  p. 17

7.1.4  Options  p. 18

7.1.5  Caching  p. 19

7.1.6  Proxying  p. 19

7.1.7  Security and DTLS  p. 19

7.1.8  Block-wise transfers  p. 19

7.1.8.0  General  p. 19

7.1.8.1  Structure of a Block Option  p. 20

7.2  Overview of LwM2M  p. 21

7.3  Solutions for File Repair using CoAP  p. 23

7.3.0  General  p. 23

7.3.1  Byte-Range Request based File Repair  p. 24

7.3.1.0  General  p. 24

7.3.1.1  Option 1: use Uri-Query option in CoAP  p. 24

7.3.1.2  Option 2: define a new CoAP option Range  p. 25

7.3.2  Block Request based File Repair  p. 27

7.3.2.0  General  p. 27

7.3.2.1  Option 3: Block request for repair data after broadcast transmission of source and repair symbols  p. 27

7.3.2.2  Option 4: Block request for repair data after broadcast transmission of only repair symbols  p. 29

7.3.2.3  Comparison of Block Request based File Repair Options  p. 30

7.3.3  Solution evaluation  p. 30

7.4  Binary data formats  p. 31

7.4.0  General  p. 31

7.4.1  Efficient Extensible Interchange or Efficient XML Exchange (EXI)  p. 31

7.4.2  Well-known binary formats  p. 32

7.4.3  Ad-hoc binary format  p. 33

7.4.4  Key-Length-Value (KLV) format  p. 36

7.4.5  Performance comparison of binary data formats  p. 36

7.4.5.1  General considerations  p. 36

7.4.5.2  Performance comparison  p. 37

7.4.5.3  Summary  p. 40

7.4.5.4  Recommendation  p. 40

7.5  Solution for announcement during wake-up periods  p. 40

7.6  Solution for announcement with critical data delivery  p. 41

7.7  Solution for reception report procedures  p. 42

7.8  Solution for service announcement procedures  p. 44

7.8.1  Unicast delivery of service announcement using CoAP  p. 44

7.8.2  Service announcement profiles for IoT devices  p. 44

7.9  ASN.1 PER binary FDT instance definition  p. 53

8  Conclusions  p. 54

$  Change history  p. 56

Up   Top