hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.19.1 Key Issue mapping | This solution is proposed to address Key Issue #3: EC Traffic Routing between local part of DN and central part of DN. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.19.2 Description | As proposed in key issue, the following two cases should be considered to support EC Traffic Routing between local part of DN and central part of DN:
- UL traffic related to an application first routed over EC to Application Server(s) for local-processing, and then further forwarded to a remote Application Server(s) in... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.19.3 Procedures | Figure 6.19.3-1 illustrates the procedure for AF influence on traffic routing between local DN and central DN.
Figure 6.19.3-1: AF influence on traffic routing between local DN and central DN
1. The AF sends the request to NEF by invoking Nnef_TrafficInfluence_Update service. The AF request contains the traffic descrip... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.19.4 Impacts on services, entities and interfaces | AF:
- AF request enhancement to contain potential post-processing locations of applications and potential prior-processing locations of applications.
PCF:
- PCC policy enhancement to contain DNAI(s) for prior-processing and DNAI(s) for post-processing.
SMF:
- creates a single PDU Session to local DN and central DN, and... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.20 Solution #20: EC Traffic Routing between local part of DN and central part of DN via PDU session | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.20.1 Key Issue mapping | The following solution corresponds to the key issue #3 on EC Traffic Routing between local part of DN and central part of DN. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.20.2 Description | This solution is applicable for both Session Breakout Connection Model and Distributed Anchor Point Model.
As described in clause 5.3, the UL traffic is first routed over EC to Application Server(s) for local-processing, and then further forwarded to a central AS(s), and the DL traffic is first routed over central part... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.20.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.20.3.1 EC traffic Routing for UL traffic | Figure 6.20.3.1-1: EC traffic routing for UL traffic
1. [Optional] The AF request in step 1 in Figure 4.3.6.2-1 of TS 23.502 [3] is used to request the traffic routing between local part of DN and central part of DN. The AF request may include order of traffic routing (e.g. indicates the specific IP address for first r... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.20.3.2 EC Traffic Routing for DL traffic | Figure 6.20.3.2-1: EC traffic routing for DL traffic
1. [Optional] The AF request in step 1 in Figure 4.3.6.2-1 of TS 23.502 [3] is used to request the traffic routing between local part of DN and central part of DN. The AF request may include order of traffic routing (e.g. indicates the specific IP address for first r... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.20.4 Impacts on services, entities and interfaces | AF:
- Requests the order of traffic routing and indicates if application identifier or traffic filtering information (e.g. IP 5 Tuple) is matched, then first routing the UL/DL traffic to the specific IP address (i.e. EAS IP address).
SMF:
- SMF configures the UPF (i.e. UL CL/BP, PSA UPF) with traffic filters to enable ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21 Solution #21: Solution to traffic routing between local and central part of DN via tunnel(s) | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.1 Description | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.1.1 Overall architecture of the solution | The architecture provides connectivity between the local and central parts of the DN ("L-DN" and "C-DN" as depicted in Figure 6.21.1-1), so that traffic can be exchanged between different parts of the DN e.g. between a L-DN part and the C-DN part. This allows EASs in different parts of a DN to communicate with each oth... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.1.2 AF control of the connectivity between different DN parts | The solution updates EDI in Table 6.2.3.4-1 of TS 23.548 [5] with following information:
- an indicator whether the DNAI is to be considered as local or central;
- an indicator whether connectivity to central DNAI(s) is needed;
- tunnelling mechanisms at N6 supported by the EAS, and other relevant information.
For the ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.2 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.2.1 Procedure to establish the tunnel between different DN parts using EDI | Based on the AF control of the connectivity between different DN parts as defined in clause 6.21.1.2, the 5GS establishes the tunnel between the different parts of the DN as described in this clause.
When SMF receives DNAI information requiring setting up connectivity between different DN parts, the SMF:
1. selects a L... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.2.2 Procedure to establish the tunnel between different DN parts using request by AF | Figure 6.21.3-1: Request tunnel over 5GC
1. AF/EAS requests 5GC to set up a tunnel between 2 DNAIs. One could also imagine that the EAS/AF only gives IP address ranges of EAS and AS, or even FQDNs of these. If not DNAIs are provided, NEF needs to translate the provided info to DNAIs. The AF/EAS provides which tunnellin... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.2.3 QoS handling of the tunnel between different DN parts | The QoS requirement of the tunnel is independent from any UE's PDU session, the QoS requirement is defined per DNAI or per application (identified by Application ID). The EDI in Table 6.2.3.4-1 of TS 23.548 [5] is updated to contain the QoS requirement on a DNAI or application basis.
To guarantee the QoS requirement of... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.21.3 Impacts on existing nodes and functionality | Impacted nodes and functionality are listed as follows:
AF:
- provides information to 5GC requesting application data forwarding between two parts of the DN (L-DN and a C-DN) via information described in clause 6.21.1.2 along with the QoS requirements in clause 6.21.2.2.
SMF:
- select PSA UPFs (L-PSA UPF and C-PSA UPF)... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.22 Solution #22: Establishment of connectivity between the local DN and central part of DN based on OAM | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.22.1 Key Issue mapping | The solution applies to Key Issue #3: EC Traffic Routing between local part of DN and central part of DN. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.22.2 Description | Raw data collected by devices is expected to be processed locally (e.g. to remove privacy aspects, or reduce the volume of raw data) and then sent to central application servers for further data processing. On the other hand, the processed data by the central servers may be distributed to the local servers, for example... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.22.3 Procedures | Figure 6.22.3-1: Procedure for connectivity between the local DN and central part of DN
1. UPF invokes Nnrf_NFManagement_NFRegister to request NRF to register UPF profile when UPF becomes operative for the first time. The request includes parameters that indicates DNAI(s) hosted by the UPF and supported Transit Gateway... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.22.4 Impacts on services, entities and interfaces | UPF:
- Support transit gateway functionality that enables to route traffic between local and central parts of DN(s).
NRF:
- Support NF profile for UPF with transit gateway support. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.23 Solution #23: Traffic steering between different parts of a DN | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.23.1 Key Issue mapping | Key issue #3. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.23.2 Description. | This solution addresses a scenario where the traffic steering between different parts of a DN for a given UE.
This solution considers the following cases (i) UL traffic first routed EAS in the local part of DN for local-processing (source IP: UE, destination IP: EAS IP-UE, which is given to UE), and then further forwar... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.23.3 Procedures | The procedure is based on the existing procedure described in clause 4.3.6.2 of TS 23.502 [3] with additional parameters sent via the AF request and its corresponding SMF behaviour.
Figure 6.23.3-1: UP path configuration for traffic steering between different parts of a DN
1. The AF decides to send AF traffic influence... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.23.4 Impacts on services, entities and interfaces | NEF:
- exposes an API for AF to provide information for local consecutive steering (including local consecutive steering indication, steering order (UL, DL, or both) local consecutive steering target application target DNAIs/FQDN/IP address, and inter AS latency requirement as local steering requirement information).
P... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.24 Solution #24: Support traffic routing between local-DN and central-DN via the existing UP path of the PDU session and IP replacement | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.24.1 Key Issue mapping | This solution is proposed to solve KI#3. It is the merged solution on using the PDU session to convey the traffic between local DN to central DN the existing UP path of the PDU Session. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.24.2 General Description | This solution resolves KI#3 about traffic routing between L-DN and central DN based on the scenario that the application traffic is required to be processed at different locations.
Based on AF traffic influence request information, the 5GC determines to enable the traffic routing between L-DN and central DN via the tun... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.24.3 Procedures | Figure 6.24.2-1: High level procedure for supporting traffic routing between local DN and central DN via PDU session
Traffic from UE to EAS via the existing procedure
0. The UE establishes a PDU Session as described in clause 4.3.2.2.1 of TS 23.502 [3]. The UE does the DNS query and finds the EAS. The UL CL/BP is inser... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.24.4 Impacts on services, entities and interfaces | SMF (applies for all three options):
- Generate traffic routing rule on ULCL/BP and PDR, FAR on L-PSA/PSA based on AF influence as described above.
- Inform AF the routing path has been configured.
NOTE: Details of the traffic routing rule, PDR, FAR are different for three options and described in UPF impacts.
L-PSA:
-... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.25 Solution #25: EC Traffic Routing between local part of DN and central part of DN with UE IP address within IP header | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.25.1 Key Issue mapping | This solution is for KI #3 EC Traffic Routing between local part of DN and central part of DN. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.25.2 Description | According to KI #3, UL traffic may need to be firstly steered to EAS for first-step processing then to the central AS.DL traffic may need to be firstly steered to EAS then to the UE. However, there may be no direct connectivity between the local DN and central DN.
In this solution, it is proposed the traffic routing as... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.25.3 Procedures | Figure 6.25.3-1: EC Traffic Routing between local part of DN and central part of DN with UE IP address in packet
0. PDU Session Establishment procedure, as described in clause 4.3.2.2.1 of TS 23.502 [3].
1. The SMF inserts ULCL/BP and L-PSA, as described in clause 4.3.5.4 of TS 23.502 [3].
2. The AF sends a request to ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.25.4 Impacts on services, entities and interfaces | SMF:
- Configuring the ULCL UPF, local PSA UPF, central PSA UPF to support the UL/DL traffic processing between local DN and central DN. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.26 Solution #26: Solution on Enhancements for EAS (re)discovery and UPF (re)selection with reducing impact on central 5GC NFs | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.26.1 Description | This solution addresses KI#1.
This solution is in particular based on the below main architectural aspects:
- Use URSP to enable UE, while in certain location, initiate a PDU Session establishment with certain DNN, S-NSSAI.
- Ensures a "local" SMF is selected as part of initial PDU session establishment. AMF is configu... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.26.2 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.26.2.1 Distributed Anchor Point and Multiple PDU Session models | Procedures defined in clause 6.2.2 of TS 23.548 [5] on SSC Mode 2/3 and in clause 4.3.5 of TS 23.502 [3] are used for Distributed Anchor Point and Multiple PDU Session models. An example procedure is given as follows:
Figure 6.26.2.1-1: "Local" SMF selection as part of PDU session establishment
1. UE Registration, as i... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.26.2.2 Session Breakout model | For Session Breakout model, I-SMF is inserted. I-SMF receives local offloading policy information, as described in Solution #5 in clause 6.5. I-SMF retrieves EDI to configure EASDF and DNS message handling locally.
Figure 6.26.2.2-1: PDU Session Establishment with supporting local offloading control
1. The steps from 1... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.26.4 Impacts on services, entities and interfaces | SMF (for Session Breakout):
- Receiving local offloading policies from PCF.
- Providing local offloading policy(ies) to I-SMF.
I-SMF (for Session Breakout):
- Receiving local offloading policy information from SMF
- Retrieves EDI for offloading information
- configures EASDF, and DNS message handling.
PCF (for Session ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 7 Overall Evaluation | Editor's note: This clause will provide evaluation of different solutions. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 7.1 Evaluation for KI#1 | There are 7 solution related to KI#1, i.e. solution #1-#7. The solution can be categorized into 4 groups:
- Group 1: I-SMF based offloading solution.
- Group 2: L-SMF based offloading solution.
- Group 3: Two PDU sessions based solution.
- Group 4: EDI provisioned solution.
G1: I-SMF based offloading solution
I-SMF bas... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 7.2 Evaluation for KI#2 | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 7.3 Evaluation for KI#3 | There are 9 solutions (Sol#17, 18, 19, 20, 21, 22, 23, 24, 25) in the TR for KI#3. These 9 solutions can be classified into 3 categories from Traffic forwarding perspective:
₋ CAT-A: Traffic forwarding by reusing the established User Plane path of the PDU Session (Sol#17, 18, 19, 20, 23, 24, 25);
₋ CAT-B: Traffic forwa... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 8 Conclusions | Editor's note: This clause will list conclusions that have been agreed during the course of the study item activities. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 8.1 Conclusion for KI#1 | The following principles are concluded for the normative work.
For Distributed Anchor Point and Multiple PDU Session models, the existing mechanisms shall be used.
For Session Breakout model the following applies:
- I-SMF based approach shall be considered to reduce impact on central 5GC NFs.
- I-SMF selection shall be... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 8.2 Conclusion for KI#2 | The following principles are concluded for normative work:
- SMF can select local PSA UPF considering N6 delay, when available.
- SMF can collect N6 delay measurement from candidate UPF per pair of 5GC N6 termination point (i.e. UPF) and the measurement endpoint at application side (e.g. EAS/Designated IP (range)) as f... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 8.3 Conclusion for KI#3 | Conclusion: - It’s concluded not to pursue normative work for this key issue. Annex A: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2024-01 SA2#160-Ah Hoc-e - - - - Initial TR skeleton. 0.0.0 2024-06 SP#104 SP-240616 - - - MCC editorial update for presentation to TSG SA#104 for... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 1 Scope | The scope of this Technical Report is to:
- study and identify potential architecture and system level enhancements for the 5G system to support the operation of the DualSteer Device that is capable of traffic steering and switching of user data for different services across two 3GPP access networks. The study addresse... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 3 Definitions of terms and abbreviations | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Non-Integrated Non-3GPP Access: a type of non-3GPP access network that provides direct IP connectivi... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
NIN3A Non-Integrated Non-3GPP Access |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 4 Architectural Assumptions and Requirements | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 4.1 Architectural Assumptions | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 4.1.1 Architectural Assumptions for DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 4.1.2 Architectural Assumptions for ATSSS_Ph4 | The following general assumptions apply:
- The Rel-18 ATSSS as specified in TS 23.501 [3], TS 23.502 [4], and TS 23.503 [5] are regarded as the baseline for this study.
The following assumptions apply to alternative architecture and system level enhancements for ATSSS that do not require the existing non-3GPP interwork... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 4.2 Architectural Requirements | Editor's note: This clause will document any architectural requirements for the study. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 4.2.1 Architectural Requirements for DualSteer | Editor's note: This clause will document any DualSteer architectural requirements for the study. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 4.2.2 Architectural Requirements for ATSSS_Ph4 | - New ATSSS capabilities shall either be able to co-exist with the existing ATSSS capabilities or any dependencies between new and existing capabilities shall be explicitly defined.
- The benefit and drawback of new solutions compared to existing TNGF and N3IWF shall be analyzed before any conclusion on WT#3.
NOTE: Coo... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5 Key Issues | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1 Key Issues for DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.1 Key Issue #1.1: Subscription aspects to support DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.1.1 Description | This key issue will study the enhancements of subscription aspects to support DualSteer including the following:
- Whether and how the 5G System identifies and associates the two subscriptions/SUPIs for DualSteer.
- Whether it is needed and what enhancements are required in the policy subscription data to support gener... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.2 Key Issue #1.2: Registration and mobility management for DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.2.1 Description | This Key Issue will study the overall registration and mobility management impacts to support DualSteer including the following:
- Whether and what enhancements are needed in functions and procedures of registration, deregistration and mobility management for supporting DualSteer. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.3 Key Issue #1.3: Session management aspects for DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.3.1 Description | This key issue will study the following potential session management enhancements to support DualSteer:
- Whether and how to enhance session management functions and procedures for DualSteer traffic steering of a new service to a 3GPP access network and/or the DualSteer traffic switching across two 3GPP access networks... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.4 Key Issue #1.4: Policy enhancements for DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.1.4.1 Description | This key issue aims to study whether and how to define the policies by the HPLMN to support DualSteer traffic steering and/or DualSteer traffic switching:
- Whether and what policies need to be provided by the HPLMN to guide the DualSteer device to decide to connect to an additional PLMN/PNI-NPN, or an additional 3GPP ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.2 Key Issues for ATSSS_Ph4 | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.2.1 Key Issue #2.1: MPQUIC steering functionality to steer, switch and split non-UDP traffic | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.2.1.1 Description | Currently MPQUIC steering functionality can support steering, switching, and splitting of UDP traffic based on IETF protocols, using UDP proxying over HTTP. For TCP traffic, ATSSS has been relying on the use of the "MPTCP steering functionality" that was specified in Rel-16. The associated proxy functionalities (MPQUIC... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.2.2 Key Issue #2.2: Simplified ATSSS architecture over non-3GPP access | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 5.2.2.1 Description | The current ATSSS architecture requires that non-3GPP access is provided via the trusted or untrusted non-3GPP access procedures. This means that to enable ATSSS either a TNGF or an N3IWF is deployed. This key issue studies whether and how to define a functional architecture and procedures for steering, switching, and ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6 Solutions | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of DualSteer Solutions to Key Issues
Key Issues for DualSteer
Solution#
Key Issue #1.1
Key Issue #1.2
Key Issue #1.3
Key Issue #1.4
#1.1
X
X
X
X
#1.2
X
X
X
X
#1.3
X
X
X
X
#1.4
X
X
X
X
#1.5
X
X
X
X
#1.6
X
X
X
#1.7
X
#1.8
X
X
#1.9
X
X
#1.10
X
#1.11
X
#1.12
X
#1.13
X
X
#1.14
X
X
#1.15
X
X
#1.16
X
#1.1... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1 Solutions for DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1 Solution #1.1: Supporting dual-steer connection re-using certain ATSSS functionality | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.1 Overall Description | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.1.1 Introduction | The proposed solution is based on the following principles:
- The impact to AMF is either none or minimal. This enables the DS functionality when only the HPLMN supports the DS functionality and the VPLMN can either remain unchanged or need to make minimal enhancements to the AMF. This solution describes two alternativ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.1.2 Architectures | This solution is based on providing a common anchor (UPF) and SMF inside the 5GC for the DS traffic from both 3GPP access networks. Non-roaming and roaming architectures are shown below.
Figure 6.1.1.1.2-1: Non-roaming dual steering architecture
Figure 6.1.1.1.2-2: Dual steering architecture with roaming in one access
... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.1.3 Registration | Alt 1: No AMF impact: It has no impact on the registration procedure.
Alt 2: Limited AMF impact: The AMF may indicate (visited) network's support for DS PDU session in the initial Registration Accept message to UE. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.1.4 Policy | URSP Rules: To support establishment of DS PDU session, the URSP rules are extended. Specifically, the Access Type preference in Route Selection Descriptor is extended to include a Dual Steering indication.
PCC rules: Considering that data splitting is not supported, the allowed steering modes are Active-Standby and Sm... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.1.5 Subscription and UE context data in UDM/UDR | The connection between the two SUPIs is maintained in UDM. For this purpose, a new field, DS SUPI, is added in the Session Management Subscription Data for both SUPI1 (containing SUPI2) and SUPI2 (containing SUPI1). In addition, for alternative 2, the same field is also added to the Access and Mobility Subscription Dat... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.1.6 Session management | This solution is based on creating a DS PDU session that is anchored in a common UPF and managed by a common SMF. To achieve this:
- Two separate PDU session Establishment requests are sent by the UE (one for each SUPI).
- In the PDU session Establishment requests, Ues provides a new parameter (DS Correlation ID) to en... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.2 Procedures | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.2.1 Session management | Based on the impact on AMF two alternatives are considered for creating DS PDU session.
Note: in this clause we consider two separate UDMs to manage the subscription data of SUPI1 and SUPI2, however, since both UDMs belong to the HPLMN, it can be assumed that the subscription data of both SUPIs are managed in a single ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.2.2 Interworking with EPS | To enable interworking with EPS the same mechanism as in Figure 6.1.1.2.1-1 are followed with the following differences:
If the DS device first establishes a PDU Session for SUPI1 in a 3GPP access network in 5GS:
- In addition to registering the PDU Session for SUPI1 in step 8 of Figure 6.1.1.2.1-1, SMF1+PGW-C1 registe... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.1.3 Impacts on services, entities and interfaces | DS device: Registering with two separate SUPIs; supporting steering and switching across two PDU session associated with two SUPIs; providing a unique DS correlation ID in the N1 SM container in the PDU Session Establishment requests for both SUPIs.
AMF: No impact for Alt1. For Alt2: Selecting SMF with DS capability, S... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.2 Solution #1.2: Alternative SUPI in UE subscription | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.2.1 Description | This solution is for key issue #1.1, #1.2, #1.3 and #1.4.
This solution focuses on a DualSteer Device containing two separated Ues and supporting simultaneous data transmission over two network.
Editor's note: How to support non-simultaneous transmission (e.g. DualSteer Device containing inside UE or due to operator po... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.2.2 Procedures | The following is the high level procedure for DualSteer.
Figure 6.1.2.2-1: Examples on DualSteer Procedures
0. The UDM is configured with the association between SUPI1 and SUPI2 as described in clause 6.1.2.1. For SUPI1 subscription, SUPI2 is added as Alternative SUPI. For SUPI2 subscription, SUPI1 is added as Alternat... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.2.3 Impacts on services, entities and interfaces | UDM:
- enhanced to support Alternative SUPI for each UE subscription.
- enhanced to provide the SM context of SUPI towards the serving AMF of the associated SUPI.
AMF:
- enhanced to select same SMF for secondary PDU session.
- selects the SMF supporting DualSteer based on DualSteer request indication.
SMF:
- enhanced t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.