Content for TR 29.820 Word version: 17.0.0
6 Solutions
6.1 Solution#1: Header Enrichment for HTTPS
6.2 Solution#2: UE IP address/prefix allocation by SMF in SMF Set
6.3 Solution #3: Enabling SMF to map network slice information into Network Instance
6.4 Solution #4: Enabling UP function to buffer downlink data as the preferred option
6.5 Solution #5: Enabling UP function to construct End Marker as the preferred option
6.6 Solution #6: Enforce traffic redirection in the UP function as the only option
6.7 Solution#7: Recommending the support of features relating to the core part of the PFCP protocol
6.8 Solution #8: L2TP Tunnel and Session Setup by UP Function
6.9 Solution#9: Enabling UPF to support multiple network slices
6.10 Solution #10: UP Controlled UE IP Portion
6.11 Solution #11: UE IP address allocation by DHCP or AAA Server in 5GC
6.12 Solution #12: UE IP address/prefix allocation by SMF self management
6.13 Solution #13: Per Slice UP Resource Allocation and Usage Report
6 Solutions p. 17
6.1 Solution#1: Header Enrichment for HTTPS p. 17
6.1.1 Description p. 17
6.1.2 Impacts on services, entities and interfaces p. 18
6.1.3 Pros p. 18
6.1.4 Cons p. 18
6.2 Solution#2: UE IP address/prefix allocation by SMF in SMF Set p. 18
6.2.1 Description p. 18
6.2.1.1 General p. 18
6.2.1.2 SMF recover p. 19
6.2.1.3 Session release p. 19
6.2.1.4 SMF added/removed to/from SMF set p. 19
6.2.2 Signalling flow p. 20
6.2.2.1 General p. 20
6.2.2.2 SMF recover p. 20
6.2.2.3 Session release p. 20
6.2.2.4 SMF added/removed to/from SMF set p. 21
6.2.3 Impacts on services, entities and interfaces p. 22
6.2.4 Pros p. 22
6.2.5 Cons p. 22
6.3 Solution #3: Enabling SMF to map network slice information into Network Instance p. 22
6.3.1 Description p. 22
6.3.2 Signalling flow p. 23
6.3.3 Impacts on services, entities and interfaces p. 24
6.4 Solution #4: Enabling UP function to buffer downlink data as the preferred option p. 24
6.5 Solution #5: Enabling UP function to construct End Marker as the preferred option p. 24
6.6 Solution #6: Enforce traffic redirection in the UP function as the only option p. 25
6.7 Solution#7: Recommending the support of features relating to the core part of the PFCP protocol p. 26
6.7.1 Description p. 26
6.7.2 Impacts on services, entities and interfaces p. 26
6.7.3 Pros p. 26
6.7.4 Cons p. 26
6.8 Solution #8: L2TP Tunnel and Session Setup by UP Function p. 27
6.8.1 Description p. 27
6.8.2 Protocol impact over N4/Sxb p. 27
6.8.2.1 L2TP Support Negotiation p. 27
6.8.2.2 L2TP Tunnel/Session Setup p. 28
6.8.2.3 L2TP Session/Tunnel Release p. 30
6.8.3 Impacts on services, entities and interfaces p. 31
6.8.4 End to End Signalling Flow p. 31
6.8.5 Security Considerations for L2TP Tunnel and Session Management p. 34
6.9 Solution#9: Enabling UPF to support multiple network slices p. 35
6.10 Solution #10: UP Controlled UE IP Portion p. 37
6.10.1 Description p. 37
6.10.2 Impacts on services, entities and interfaces p. 37
6.10.3 Pros p. 37
6.10.4 Cons p. 38
6.11 Solution #11: UE IP address allocation by DHCP or AAA Server in 5GC p. 38
6.11.1 Description p. 38
6.11.2 Impacts on services, entities and interfaces p. 39
6.11.3 Pros p. 39
6.11.4 Cons p. 39
6.12 Solution #12: UE IP address/prefix allocation by SMF self management p. 40
6.12.1 Description p. 40
6.12.1.1 General p. 40
6.12.1.2 SMF recover p. 40
6.12.1.3 Session release p. 40
6.12.1.4 SMF added/removed to/from SMF set p. 40
6.12.2 Impacts on services, entities and interfaces p. 40
6.12.3 Pros p. 41
6.12.4 Cons p. 41
6.13 Solution #13: Per Slice UP Resource Allocation and Usage Report p. 41
6.13.1 Description p. 41
6.13.2 Impacts on services, entities and interfaces p. 42
6.13.3 Pros p. 42
6.13.4 Cons p. 42
