| 6.1 | Solution #1: Data delivery enabler service architecture p. 14
| 6.1.1 | Solution description p. 14
| 6.1.1.1 | Functional architecture description p. 14
|
| 6.1.1.2 | Functional entities description p. 17
|
| 6.1.1.3 | Reference points description p. 18
| 6.1.1.3.1 | SEALDD reference points p. 18
|
| 6.1.1.3.2 | 3GPP system reference points used by SEALDD p. 18
|
|
|
| 6.1.2 | Solution evaluation p. 18
|
|
| 6.2 | Solution #2: E2E redundant transmission path establishment p. 18
| 6.2.1 | Architecture enhancements p. 18
|
| 6.2.2 | Solution description p. 20
|
| 6.2.3 | Solution evaluation p. 22
|
|
| 6.3 | Solution #3: Client initiated request for redundant transport p. 23
| 6.3.1 | Solution description p. 23
|
| 6.3.2 | Solution evaluation p. 24
|
|
| 6.4 | Solution #4: Data storage creation p. 24
| 6.4.1 | Solution description p. 24
|
| 6.4.2 | Solution evaluation p. 27
|
|
| 6.5 | Solution #5: SEALDD adaptation in CAPIF p. 27
| 6.5.1 | Solution description p. 27
|
| 6.5.2 | Solution evaluation p. 28
|
|
| 6.6 | Solution #6: SEALDD integrating MSGin5G for message transfer p. 28
| 6.6.1 | Architecture enhancements p. 28
|
| 6.6.2 | Solution description p. 28
|
| 6.6.3 | Solution evaluation p. 30
|
|
| 6.7 | Solution #7: SEALDD server discovery and selection for specific VAL server p. 30
| 6.7.1 | Architecture enhancements p. 30
|
| 6.7.2 | Solution description p. 30
|
| 6.7.3 | Solution evaluation p. 31
|
|
| 6.8 | Solution #8: SEALDD server discovery and selection in EDN p. 32
| 6.8.1 | Architecture enhancements p. 32
|
| 6.8.2 | Solution description p. 32
| 6.8.2.1 | General p. 32
|
| 6.8.2.2 | Procedure p. 32
| 6.8.2.2.1 | General p. 32
|
| 6.8.2.2.2 | VAL server registered to EES with associated SEALDD server address as VAL server endpoint p. 33
|
| 6.8.2.2.3 | EAS registered to EES with associated SEALDD server information p. 33
|
|
|
| 6.8.3 | Solution evaluation p. 34
|
|
| 6.9 | Solution #9: SEALDD interaction for regular application traffic transfer p. 34
| 6.9.1 | Architecture enhancements p. 34
|
| 6.9.2 | Solution description p. 34
|
| 6.9.3 | Solution evaluation p. 36
|
|
| 6.10 | Solution #10: SEALDD server relocation p. 36
| 6.10.1 | Solution description p. 36
| 6.10.1.1 | General p. 36
|
| 6.10.1.2 | SEALDD context transfer without IP replacement p. 37
|
| 6.10.1.3 | SEALDD context transfer with IP replacement p. 38
|
|
| 6.10.2 | Solution evaluation p. 38
|
|
| 6.11 | Solution #11: SEALDD support of UE's service continuity p. 39
| 6.11.1 | Solution description p. 39
|
| 6.11.2 | Solution evaluation p. 41
|
|
| 6.12 | Solution #12: SEALDD enabled data transmission quality measurement p. 41
| 6.12.1 | Architecture enhancements p. 41
|
| 6.12.2 | Solution description p. 41
|
| 6.12.3 | Solution evaluation p. 43
|
|
| 6.13 | Solution #13: SEALDD support for data transmission quality guarantee with redundant transport p. 43
| 6.13.1 | Solution description p. 43
|
| 6.13.2 | Solution evaluation p. 44
|
|
| 6.14 | Solution #14: Data distribution management in SEALDD p. 45
| 6.14.1 | Solution description p. 45
|
| 6.14.2 | Solution evaluation p. 47
|
|
| 6.15 | Solution #15: SEALDD enabled data transmission via N6 Tunnel p. 48
| 6.15.1 | Architecture enhancements p. 48
|
| 6.15.2 | Solution description p. 48
|
| 6.15.3 | Solution evaluation p. 49
|
|
| 6.16 | Solution #16: SEALDD enabled application context transfer p. 49
| 6.16.1 | Architecture enhancements p. 49
|
| 6.16.2 | Solution description p. 49
|
| 6.16.3 | Solution evaluation p. 50
|
|
| 6.17 | Solution #17: E2E redundant transmission path establishment with dual UE - dual UP p. 51
| 6.17.1 | Solution description p. 51
|
| 6.17.2 | Solution evaluation p. 54
|
|
| 6.18 | Solution #18: SEALDD enabled rate control for different VAL users p. 55
| 6.18.1 | Architecture enhancements p. 55
|
| 6.18.2 | Solution description p. 55
|
| 6.18.3 | Solution evaluation p. 56
|
|