Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TS 33.180
Word version: 18.1.0
1…
4…
4.3.4
4.3.5
5…
5.1.3
5.1.4…
5.2…
5.2.3
5.2.4
5.2.5
5.2.6…
5.3…
5.4…
6…
7…
7.3…
8…
9…
9.4…
10…
A…
B…
C…
D…
E…
F…
J…
L…
8
MCData
8.1
Overview
8.2
Key Management
8.3
One-to-one communications
8.4
Group communications
8.5
MCData payload protection
8.6
MCData message store security
...
8
MCData
p. 89
8.1
Overview
p. 89
8.2
Key Management
p. 90
8.3
One-to-one communications
p. 91
8.4
Group communications
p. 92
8.5
MCData payload protection
p. 92
8.5.1
General
p. 92
8.5.2
Prequisites
p. 92
8.5.2.1
Prequisites for protected payloads
p. 92
8.5.2.2
Prequisites for authenticated payloads
p. 92
8.5.3
Key derivation for protected payloads
p. 93
8.5.4
Payload protection
p. 93
8.5.4.1
Format of protected payloads
p. 93
8.5.4.2
Encryption of protected payloads
p. 93
8.5.5
Payload authentication
p. 94
8.6
MCData message store security
|R17|
p. 95
8.6.0
Functional model
p. 95
8.6.1
MCData message store reference points
p. 96
8.6.1.1
Reference point MCData-7 (between the Message store client and MCData message store)
p. 96
8.6.1.2
Reference point MCData-8 (between the MCData message store and MCData server)
p. 96
8.6.1.3
Reference point MCData-cap-n (between the MCData server and the MCData client)
p. 96