Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

TR 22.841
Study on Upper layer Traffic Steering, Switching and Split over dual 3GPP access

V19.0.0 (Wzip) 2023/12 55 p.

Rapporteur:: Mr. Pica, Francesco
Qualcomm Germany

full Table of Contents for TR 22.841 Word version: 19.0.0

1 Scope p. 8

The scope of this TR is to document use cases, gap analysis and potential service requirements related to 5GS support of enhanced mechanisms for steering, splitting and switching of user data, pertaining to a UE data session, across two 3GPP networks. The following scenarios are covered, where only one single PLMN subscription is assumed:

Single PLMN;
PLMN and NPN;
two PLMNs.

The two 3GPP networks may use same or different RAT, i.e. NR plus NR or E-UTRA, where NR RAT can be terrestrial or satellite NR access (including different staellite orbits, e.g., GEO/MEO/LEO).

For the PLMN plus PLMN / NPN scenarios, the two networks can be managed by the same operator or by different operators (assumed to have a business agreement among them). In both cases, it is assumed that a single PLMN subscription is used to access both networks (including the NPN).

Simultaneous connectivity over two 3GPP networks presumes UE support of proper capabilities (e.g., dual radio).

It is assumed that there are no impacts to normal inter-PLMN roaming scenarios.

Dual subscription scenarios are not in scope of this TR.

2 References p. 8

3 Definitions of terms, symbols and abbreviations p. 8

3.1 Terms p. 8

3.2 Abbreviations p. 9

4 Overview p. 9

5 Use cases p. 10

5.1 Use case on dual 5G satellite access in maritime scenario p. 10

5.1.1 Description p. 10

5.1.2 Pre-conditions p. 10

5.1.3 Service Flows p. 10

5.1.4 Post-conditions p. 11

5.1.5 Existing features partly or fully covering the use case functionality p. 11

5.1.6 Potential New Requirements needed to support the use case p. 11

5.2 Use case on Inter PLMN Mobility Scenario p. 12

5.2.1 Description p. 12

5.2.2 Pre-conditions p. 12

5.2.3 Service Flows p. 12

5.2.4 Post-conditions p. 13

5.2.5 Existing features partly or fully covering the use case functionality p. 13

5.2.6 Potential New Requirements needed to support the use case p. 13

5.3 Use case on Inter-PLMN or PLMN-SNPN scenario p. 13

5.3.1 Description p. 13

5.3.2 Pre-conditions p. 14

5.3.3 Service Flows p. 14

5.3.4 Post-conditions p. 14

5.3.5 Existing features partly or fully covering the use case functionality p. 15

5.3.6 Potential New Requirements needed to support the use case p. 15

5.4 Use case on Inter-PLMN scenario - TN and NTN p. 15

5.4.1 Description p. 15

5.4.2 Pre-conditions p. 16

5.4.3 Service Flows p. 16

5.4.4 Post-conditions p. 17

5.4.5 Existing features partly or fully covering the use case functionality p. 17

5.4.6 Potential New Requirements needed to support the use case p. 18

5.5 Use case on NTN-based dual 3GPP access p. 18

5.5.1 Description p. 18

5.5.2 Pre-conditions p. 20

5.5.3 Service Flows p. 21

5.5.4 Post-conditions p. 21

5.5.5 Existing features partly or fully covering the use case functionality p. 21

5.5.6 Potential New Requirements needed to support the use case p. 21

5.6 Use case on UE using Terrestrial and Satellite Access p. 22

5.6.1 Description p. 22

5.6.2 Pre-conditions p. 22

5.6.3 Service Flows p. 22

5.6.4 Post-conditions p. 23

5.6.5 Existing features partly or fully covering use case functionality p. 23

5.6.6 Potential New Requirements needed to support the use case p. 23

5.7 Use case on intra-PLMN scenario for XR gaming p. 23

5.7.1 Description p. 23

5.7.2 Pre-conditions p. 24

5.7.3 Service Flows p. 24

5.7.4 Post-conditions p. 25

5.7.5 Existing features partly or fully covering the use case functionality p. 25

5.7.6 Potential New Requirements needed to support the use case p. 25

5.8 Use Case on intra-PLMN traffic redundancy p. 25

5.8.1 Description p. 25

5.8.2 Pre-conditions p. 26

5.8.3 Service Flows p. 26

5.8.4 Post-conditions p. 26

5.8.5 Existing features partly or fully covering the use case functionality p. 27

5.8.6 Potential New Requirements needed to support the use case p. 27

5.9 Use case on dual steering through Satellite and UAV p. 27

5.9.1 Description p. 27

5.9.2 Pre-conditions p. 28

5.9.3 Service Flows p. 29

5.9.4 Post-conditions p. 29

5.9.5 Existing features partly or fully covering the use case functionality p. 29

5.9.6 Potential New Requirements needed to support the use case p. 29

5.10 Use case on NTN and TN Inter-PLMN Multi-access in a Maritime scenario p. 29

5.10.1 Description p. 29

5.10.2 Pre-conditions p. 30

5.10.3 Service Flows p. 31

5.10.4 Post-conditions p. 31

5.10.5 Existing features partly or fully covering the use case functionality p. 32

5.10.6 Potential New Requirements needed to support the use case p. 32

5.11 Use case on inter PLMN scenario for XR service p. 32

5.11.1 Description p. 32

5.11.2 Pre-conditions p. 33

5.11.3 Service Flows p. 33

5.11.4 Post-conditions p. 34

5.11.5 Existing features partly or fully covering the use case functionality p. 34

5.11.6 Potential New Requirements needed to support the use case p. 34

5.12 Use case on different VPLMN scenarios p. 35

5.12.1 Description p. 35

5.12.2 Pre-conditions p. 36

5.12.3 Service Flows p. 36

5.12.4 Post-conditions p. 36

5.12.5 Existing features partly or fully covering the use case functionality p. 36

5.12.6 Potential New Requirements needed to support the use case p. 37

5.13 Use case on Interworking with non-3GPP access p. 37

5.13.1 Description p. 37

5.13.2 Pre-conditions p. 37

5.13.3 Service Flows p. 38

5.13.4 Post-conditions p. 38

5.13.5 Existing features partly or fully covering the use case functionality p. 39

5.13.6 Potential New Requirements needed to support the use case p. 39

5.14 Use Case on Inter-PLMN scenario - TN and multiple NTN p. 39

5.14.1 Description p. 39

5.14.2 Pre-conditions p. 40

5.14.3 Service Flows p. 40

5.14.4 Post-conditions p. 40

5.14.5 Existing features partly or fully covering the use case functionality p. 40

5.14.6 Potential New Requirements needed to support the use case p. 41

5.15 Use Case on access to local NPN services (inter NPN - PLMN scenario) p. 41

5.15.1 Description p. 41

5.15.2 Pre-conditions p. 42

5.15.3 Service Flow p. 42

5.15.4 Post Conditions p. 43

5.15.5 Existing features partly or fully covering the use case functionality p. 43

5.15.6 Potential new requirements p. 43

5.16 Use Case on set of devices accessing local NPN services (inter NPN - PLMN scenario) p. 44

5.16.1 Description p. 44

5.16.2 Pre-conditions p. 45

5.16.3 Service Flows p. 45

5.16.4 Post-conditions p. 46

5.16.5 Existing features partly or fully covering the use case functionality p. 46

5.16.6 Potential New Requirements needed to support the use case p. 46

5.17 Use Case on Vehicle IoT devices steering via NTN and TN p. 46

5.17.1 Description p. 46

5.17.2 Pre-conditions p. 47

5.17.3 Service Flows p. 47

5.17.4 Post-conditions p. 48

5.17.5 Existing features partly or fully covering the use case functionality p. 48

5.17.6 Potential New Requirements needed to support the use case p. 48

5.18 Use Case on UAV UE connecting to 3GPP TN and NTN access networks p. 48

5.18.1 Description p. 48

5.18.2 Pre-conditions p. 49

5.18.3 Service Flows p. 49

5.18.4 Post-conditions p. 50

5.18.5 Existing 3GPP features partly or fully covering the use case functionality p. 50

5.18.6 Potential New Requirements needed to support the use case p. 50

5.19 Use Case on supplementary downlink data via a second 3GPP access network p. 50

5.19.1 Description p. 50

5.19.2 Pre-conditions p. 51

5.19.3 Service Flows p. 51

5.19.4 Post-conditions p. 51

5.19.5 Existing 3GPP features partly or fully covering the use case functionality p. 52

5.19.6 Potential New Requirements needed to support the use case p. 52

6 Consolidated potential requirements p. 52

6.1 Introduction p. 52

6.2 General p. 53

6.3 Mobility and connectivity changes p. 54

6.4 Charging and other aspects p. 54

7 Conclusion and recommendations p. 54

$ Change history p. 55