Content for TR 23.799 Word version: 14.0.0
6.4 Solutions for Key Issue 4: Session management p. 205
6.4.1 Solution 4.1: Session Management functions and relations p. 205
6.4.1.1 Architecture description p. 206
6.4.1.2 Function description p. 207
6.4.1.3 Solution evaluation p. 207
6.4.2 Solution 4.2: Session setup procedures p. 207
6.4.2.1 Architecture description p. 207
6.4.2.2 Function description p. 208
6.4.2.2.1 Session establishment procedure, non-roaming case p. 208
6.4.2.2.2 Session establishment procedure, home-routed roaming case p. 210
6.4.2.3 Solution evaluation p. 211
6.4.3 Solution 4.3: NextGen Session Management with Multiple PDU sessions to the same Data Network p. 211
6.4.3.1 Architecture description p. 211
6.4.3.2 Function Description p. 214
6.4.3.2.1 UE PDU Session Establishment Triggering p. 214
6.4.3.2.2 UP-GW Selection p. 215
6.4.3.2.3 Establishment of a PDU Session p. 216
6.4.3.3 Solution evaluation p. 217
6.4.4 Void
6.4.5 Solution 4.5: Network triggered on-demand SM setup procedure p. 217
6.4.5.1 Architecture description p. 217
6.4.5.2 Function description p. 217
6.4.5.3 Solution evaluation p. 218
6.4.6 Solution 4.6: Common interfaces towards UE, AN and SDM for both MM and SM related procedures p. 219
6.4.6.1 Description p. 219
6.4.7 Solution 4.7: Infrequent small data transfer p. 219
6.4.7.1 Architecture description p. 220
6.4.7.2 Function description p. 221
6.4.7.3 Solution evaluation p. 223
6.4.8 Solution 4.8: for Data transmission with ConnectionLess RAN-Core interface p. 224
6.4.8.1 Solution Overview p. 224
6.4.8.2 Call flows p. 227
6.4.9 Solution 4.9: UP protocol model - Per QoS class tunnel protocol p. 233
6.4.9.1 Architecture description p. 233
6.4.9.2 Function description p. 234
6.4.9.3 Solution evaluation p. 234
6.4.10 Solution 4.10: UP protocol model - Per PDU session tunnel protocol p. 234
6.4.10.1 Architecture description p. 234
6.4.10.2 Function description p. 235
6.4.10.3 Solution evaluation p. 235
6.4.11 Solution 4.11: UP protocol model - Per Node-level tunnel p. 235
6.4.11.1 Architecture description p. 235
6.4.11.2 Function description p. 236
6.4.11.3 Solution evaluation p. 237
6.4.12 Solution 4.12: UP protocol model - SDN-Based Approach p. 237
6.4.12.1 Architecture description p. 237
6.4.12.2 Function description p. 239
6.4.12.3 Solution evaluation p. 239
6.4.13 Solution 4.13: Session Management model for multiple parallel PDU Sessions and for multi-homed PDU Session p. 239
6.4.13.1 Architecture description p. 239
6.4.13.2 Function description p. 241
6.4.13.3 Solution evaluation p. 243
6.4.14 Solution 4.14: Session management with flexible multiple UP GW(s) assignment p. 243
6.4.14.1 Architecture Description p. 243
6.4.14.2 Session establishment with Edge GW and DN-GW selection and configuration p. 245
6.4.14.3 Edge GW relocation p. 245
6.4.15 Solution 4.15: Common interfaces towards UE, AN with MM and SM decoupled p. 246
6.4.15.1 Description p. 246
6.4.15.2 Procedure p. 247
6.4.16 Solution 4.16: the interaction between MM and SM p. 249
6.4.16.1 Architecture Description p. 249
6.4.16.1.1 Overview p. 249
6.4.16.1.2 Interactions between MMF and SMF p. 250
6.4.16.1.3 Subscription data p. 252
6.4.16.2 Function description p. 253
6.4.16.2.1 Set-up of a PDU session p. 253
6.4.16.2.2 The subscription on UE mobility p. 254
6.4.16.2.3 The notification on UE mobility p. 255
6.4.16.3 Solution evaluation p. 256
6.4.17 Void
6.4.18 Solution 4.18: Solution for Infrequent Small Data p. 257
6.4.18.1 Architecture description p. 257
6.4.18.2 Function description p. 257
6.4.18.2.1 Connection Establishment Flow p. 257
6.4.18.2.2 Uplink PDU Transfer Flow p. 258
6.4.18.2.3 Downlink PDU Transfer Flow p. 259
6.4.18.3 Solution evaluation p. 260
6.4.19 Solution 4.19: Infrequent small user data transfer via control plane p. 260
6.4.19.1 Architecture description p. 261
6.4.19.2 Function description p. 261
6.4.19.2.1 Mobile originated data transport via control plane p. 261
6.4.19.2.2 Mobile terminated data transport via control plane p. 262
6.4.19.3 Solution evaluation p. 263
6.4.20 Solution 4.20: Session Management on the PDU session(s) via different accesses p. 263
6.4.20.1 Architecture description p. 263
6.4.20.2 Function description p. 265
6.4.20.3 Solution evaluation p. 266
6.4.21 Solution 4.21: NG3 interface related procedures p. 266
6.4.21.1 Architecture description p. 266
6.4.21.2 Function description p. 267
6.4.21.3 Solution evaluation p. 270
6.4.22 Solution 4.22: Session management per PDU session p. 270
6.4.22.1 Architecture Description p. 270
6.4.22.2 Function description p. 271
6.4.22.3 Solution evaluation p. 274
6.4.23 Solution 4.23: Asynchronous Session Management Model p. 274
6.4.23.1 Architecture description p. 274
6.4.23.2 Function description p. 275
6.4.23.3 Solution evaluation p. 276
6.4.24 Solution 4.24: Session Management with individual CP function per access network p. 276
6.4.24.1 Architecture description p. 276
6.4.24.2 Function description p. 277
6.4.24.3 Solution evaluation p. 278
6.4.25 Solution 4.25: Local Area Data Network p. 278
6.4.25.1 Architecture description p. 278
6.4.25.2 Function description p. 278
6.4.25.3 Solution evaluation p. 279
