Professional Documents
Culture Documents
On
5G User Registration for Dual
Access & Dual Connectivity
March 1, 2019 0
Preface
The content of this document is about technical aspect of
Table of Contents
5G technology. Challenges of 5G data speed and
resolution is detailed within proposed architecture.
This document attempts the case for new work that need to be
developed for 5G User to improves end user’s reachability
outlining the poor radio coverage issue with respect to voice
and video services (by IP Multimedia Services- IMS).
This White Paper Document is intent for technical readers just
for the technical information basis. Proposal not to be
Whitepaper-5G-User-Registration-for-Dual-Access-Connectivity taken
March, 2019 as1
tested field trial, but can be meant for lab validation.
Table of Contents
Table of Contents............................................................................................................................................. 1
1. Abstract .................................................................................................................................................. 3
2. Introduction ............................................................................................................................................ 6
2.1 5G System Architecture................................................................................................................... 6
2.2 Quality of Service (QoS) for 5G Services .......................................................................................... 8
2.3 Dual Connectivity ............................................................................................................................ 8
3. Challenges ............................................................................................................................................... 9
4. Solution Architect: 5G-User Registration for Out-of-Coverage Scenario ................................................ 10
4.1 Solution for Proposal .................................................................................................................... 10
5. Solution Architect for User Defined FILTER of 5G System ...................................................................... 14
6. Solution Architect for Dual Access for Degrade in Radio Condition ....................................................... 16
6.1 Solution for Proposal .................................................................................................................... 16
7. Solution Architect for Dual Connectivity (DC) with Master-gNB Degrade Radio Condition .................... 18
7.1 Solution for Proposal .................................................................................................................... 18
8. Solution Architect for Wi-Fi Converge Issue .......................................................................................... 20
8.1 Solution for Proposal .................................................................................................................... 20
9. Conclusion............................................................................................................................................. 22
10. References ........................................................................................................................................ 23
11. Team ................................................................................................................................................. 24
12. Contacts ............................................................................................................................................ 25
In this document, 5G System architecture is fine-tuned with a solution to a multi-access mechanism enabling
uninterrupted services to enhance user experience. Overall, how to increase the user reachability is documented
with their data delivery mechanisms are evaluated to serve them in better all possible scenario.
User data is delivered to user's end device via network slicing functionality of 5G system. As compared to earlier
technologies with user’s single point of registration, in the 5G System multi-registration procedure have
accelerated further for network resource sharing and user data sharing. 5G User’s accessibility while roaming to
other network generation like 4G or 2G are not in the scope of this document.
User data of 5G System is delivered to user from service or data network via interface N6 and N3 to UE. For the
clarity in the current document proposal, multiple node/function like UDSF, NRF, and interfaces N9, N14 are not
shown.
UE access to the Network Function (NF) and services via non-3GPP such access like WLAN or Wi-Fi. The N3IWF
interface connect UE with 5G core network via N2 and N3 interface.
The 5G System architecture consists of the following Network Functions. The functional description of
these network functions is specified.
include the following functionality to support non-3GPP access networks: Support of N2 interface with N3IWF
for Mobility, Security Authentication and other signalling.
The functionality of N3IWF in the case of untrusted non-3GPP access termination of N2 and N3 interfaces to 5G
Core Network for control-plane and user-plane respectively and other signalling.
Session Management e.g., Establishment, modification and release of sessions, including tunnel maintain
between UPF and AN node, UE IP address allocation and management, Downlink Data Notification and other
signalling.
Access subscription information relevant for policy decisions in Unified Data Repository (UDR).
The Application Function (AF) interacts with the 3GPP Core Network to provide services like traffic routing, Policy
framework for policy control and others.
Anchor point for Intra-/Inter-RAT mobility, External PDU Session point of interconnect to Data Network, Packet
routing & forwarding, Packet inspection, etc.
Support authentications for 3GPP access and untrusted non-3GPP access as specified in TS 33.501.
Generation of 3GPP AKA Authentication Credentials, User Identification Handling, Access authorization based
on subscription data, Subscription management, SMS management, etc.
Internet Broad band IP services, rich multimedia services like voice, video, fax, messaging etc. – service provides
are defined Service Network for 5G Architecture.
Supports selecting of the Network Slice instances to serve the UE, determining the AMF set to be used to serve
the UE.
QFI is defined as QoS Flow ID is an identity to QoS flow in the 5G System. All data traffic within a PDU session
are labelled or identified by QFI, it implies same QFI labelled data flow will receive same traffic forwarding
treatment like scheduling, priority etc. Data flow is via N3 (N3 and N9) interface, being encapsulated end-to-
end. This flow is controlled by SMF, who provides QoS profile during session establishment to RAN and provides
the PDR to the UPF.
Please Note that like 4G System, default QoS flow is applied to each PDU session and retains till lifetime span of
connectivity. In case of non-3GPP access QFI is delivered to N3IWF entity (or NG-RAN) for every time User Plane
of the PDU session is established, modified or activated.
Dual Connectivity (DC) concept developed for 3GPP access, functional support the network to make use of
additional radio resource to achieve required throughput in downlink and uplink of user data. This was
introduced in 4G System support 5G data speed by addition of dual connectivity of UE with eNBs, master eNB
and Secondary eNBs and /or eNodeB in congestion with gNB. This is achieved by addition of Secondary eNodeB
to the Master-eNodeB. The Master-eNBs has full control to add, delete and HO (Handover) of eNodeB as and
when needed.
In this document, user access to voice and video service are discussed. Proposal made to maintain user
registration state for each access type of user at Service Network in various scenarios and challenges. Henceforth
to achieve stable 5G Service delivery is a great amount of challenges too involved.
• 5G System has been evolved to serve the user in more efficient way of meeting higher download and upload
of user data, 5G User accessing the network via wireline and wireless, in addition to this Residential Gateway
and IoT support are also defined. Access and user’s experience are challenging for poor radio coverage (for
both Wi-Fi and RAN) and the proposal in this document addresses the problem of poor coverage on either
3GPP or non-3GPP access with UE in dual-access mode. This document attempts the case for a new work
that needs to be developed for 5G User to improve faster download and upload of user's data in a scenario
of dual-access outlining the poor radio coverage issues.
• This document also outlines the faster user data mechanism accompanying 3GPP access of 5G User device
via bearer offloading in case of a poor coverage.
• This document also outlines the faster user data mechanism accompanying non-3GPP access of 5G User
device via split bearer in case of a poor coverage.
User registered may goes out of access network coverage at the time of serve being delivered. The User hunts
for another access network will fails. A considerable amount of delay is incurred on this hunting procedure. This
document outlines this problem by proposing a solution for this by dual-registration concept.
Since UE of 5G System is capable of dual access, implies UE can simultaneously have active connections with
both 3GPP and non-3GPP access at same time. In turn, this implies UE is reachable via both access types at the
same time.
Let us consider a simple case where the 5G UE device having dual access capability gets powered-on and both
Wi-Fi and RAN network is available.
3-Another
Access-
Type=YES
4-REGISTRATION
PANI=WLAN; DUAL; IMSI; Call-ID=2
TABLE-2
5-200 Ok
Expiry-Time=t2
7-200 Ok
Case: Loss in connectivity with either Access-Type, E.g.: Wi-Fi connection Lost
TABLE-2
1,2- As shown in Figure-3, UE first try to get attached to network via RAN access and followed by sending first
initial (fresh) SIP Registration request to the IMS network. Authentication procedure is not included here for the
Upon successful SIP REGISTRATION stores the UE registration data in the following format in Table-1.
3- Since UE support dual-access, based on availability of another access-type, Wi-Fi, UE try of get access to
network 5G-Core via N3IWF.
4,5- Upon successful Wi-Fi attached procedure was successful, UE also triggers another FRESH REGISTER request
to IMS network. Since RAN access was active, hence the UE MUST send this FRESH REGISTRATION with PANI
header=wlan with option tag=dual, indicating dual registration. The second SIP Registration request triggered
via another access type, in this example Wi-Fi will be again Un-Protected Registration, i.e. different call-ID and
different IPsec, as shown in Table-2.
Additional optional tag with name=dual, need to send during REGISTRATION to the Network. This parameter will
be sent to the IMS network along with PANI [RFC7913] header, in the below format.
The Optional tag=dual, initiates the PCSCF to store two entries of a user's registration data.
6,7- Upon successful of second registration via Wi-Fi access, i.e. Dual-Registration, register status via RAN access-
type need be updated. Hence re-registration (refresh registration) request is sent for PANI=RAN (in this example)
which was sent earlier. Register request sent on RAN access again will have optional tag=dual.
8,9- In case of loss of one of the radio access, an updated for registration status on available access-type will be
sent to the network. This re-register request will update the network registration status table at P-CSCF/SBC.
For example, dual REGISTERED 5G UE lost connectivity on Wi-Fi. Whether or not UE's initiated de-register
request for Wi-Fi access reached IMS network, a re-register request will be sent on RAN access with no optional
tag=dual on PANI header. This indicated loss of Wi-Fi access type and P-CSCF will mark will update the user
registration status stored locally by erasing of Wi-Fi access.
If UE had IMS registration successful over both access types, RAN and Wi-Fi, dual access tag in database of IMS
registrar service indicates that UE is reachable over two access type. Terminating P-CSCF forwards INVITE on
both access type via a parallel forking mechanism. SIP response 183 (Session Progress) received first from either
access type, will be considered successful and response will be processed discarding other forked
request/response. Further bearer creation over successful access-type triggered via diameter AAR/AAA
request/response with policy server
If UE had successful registration with only single access-type, then terminating P-CSCF forward INVITE on
registered access type as a normal procedure.
PCC rules to achieve required throughput. FILTER mechanism to be implemented at UPF user plane data for
dual-access outlining the poor radio coverage issue. 5G-Core System split bearer's FILTER for dual Access.
4G System was designed such that it provides one default bearer for each APN type (Service type). That is UE
after attach procedure with access network, PGW create default data bearer of QCI=9 for data service. Again, if
UE has voice capability, then it triggers new PDN connect request for APN=ims for voice & Video services, for
which P-GW creates QCI=5 bearer as a default bearer.
5G System is designed to support dual access mechanism such that both 3GPP and non-3GPP access at same
time. In this case, the P-GW needed to maintain two default bearers for each APN instead of one, as explained
below.
Please note: How an APN with same name to maintain two defaults bearers or APN name to be modified for
each access type is out of scope of this document. However, details of setup procedure and call flow mechanism
is beyond the scope of this document, draft [3] can be referred.
Take for example IMS registration via SIP protocol, UE will send sip registration for RAN on QCI=5 and for Wi-Fi
on separate QCI=5 Taking an example of voice call, one voice call established over RAN with QCI=1 and another
voice call can be established in parallel over Wi-Fi over separate QCI=1. This dedicated bearer MUST be
implemented with FILTER mechanism for data sharing.
In case of poor radio coverage of RAN, for example, split bearer between RAN and Wi-Fi using this FILTER such
that some part of audio packets is delivered to user via RAN and some via Wi-Fi, thus enhancing the User
experience. The SMF will be splitting the downlink packet in SPLIT mode via FILTER mechanism while maintaining
PCC rule in tagged.
Traffic FILTER mechanism is needed to be implemented between each QCI type for same APN, for only for
DEDICATED bearer, not default bearer. This Filter mechanism will control traffic packet segmentation to be
delivered on each of QCI.
Proposal of Split Bearer for dual access. The solution proposed in this document to solve the problem of degrade
radio condition on the either of the access type at UE and bearer offloading to other access-type. Bearer split
among RAN and Wi-Fi referring to Figure-6. Trigger for split bearer of bearer can originate from other of access
type RAN or Wi-Fi.
• In the example given in Figure-6 and Figure-7, there is degrade in radio condition at RAN access of user. And
at the same time 5G user also have Wi-Fi access registered.
• Based on measurement report from UE, gNB (RAN) take decision for partial Handover. gNB asked for UE-
Capabilities to check availability of other access type.
Measurement Control
Measurement Report
HO Decision
UEAccessCapabilities
UE Wi-Fi Access Report
Partial HO-procedure to
N3IWF + FILTER
• Taking inputs on UE-Capabilities response about the availability of other access type, gNB process for Split
bearer with other access type.
• gNB (RAN) triggers split bearer request for Wi-Fi access to AMF and, also includes User data traffic template
FILTER.
• FILTER: FILTER is a user data delivery template defined by NG-RAN for the 5G-core UPF to implement and
execute, without super imposing on the PCC rule.
• If offload of complete user data traffic is needed, then FILTER value MUST be empty/NULL.
• If split of user data traffic is needed, then FILTER value needs to be populated with suitable data traffic
segregation indication within a template according to which user data traffic is split partially between RAN
and Wi-Fi by UPF on N3 interface.
Proposal of Bearer Offloading Dual-Connectivity with 3GPP access. The solution proposed in this document to
solve the degrade Rf (means Radio Interface) condition at Master-gNB while handover to another Master-gNB
is not possible and UE have better or improved Rf condition with Secondary-gNB (as compared to Master-gNB).
Figure-8 below shows how radio resource control can be handed over from Master-gNB to Secondary-gNB.
Measurement Control
Measurement Report
HO Decision
S-gNB HO Request
Carry SCG config info
New M-gNB
User Data User Data
Proposal for Split Bearer in Dual-Connectivity (DC) in Non-3GPP access Referring to document [20160157293
A1], the solution proposed in this document is to solve the degrade Wi-Fi radio resource connected to UE. N3IWF
/WLC acting as a Wi-Fi aggregation point will deliver user-data via more than one AP (Access Point).
Y1 Y2 N2 N11
Master-AP
N4
N3 N6
UE Y2
Y1
Secondary-AP
As shown in Figure-9 and in Figure-10, in case of Wi-Fi dual connectivity, different from 3GPP standard, N3IWF
have full control to on the delivery of user data by splitting it into multiple Access Points. 'Wi-Fi Aggregation’
functionality of WLC. 5G User being served by multiple Access Points and each of these Access Points has
independent connectivity with N3IWF, which is different from DC functionality of 3GPP.
N3IWF have enhanced aggregation feature of governing single user data on multiple Access Points. That is
N3IWF control user data delivery via two Access Points, namely Master-AP and Secondary-AP. Based on Wi-Fi
radio resource condition, N3IWF SHOULD take decision to split user data delivery via multiple Access-Points.
N3IWF MUST also completely switch all the user data to Secondary-AP and releasing them from Master-AP.
Thereafter Secondary-AP will be referred as Master-AP.
This White Paper is a study of 5G User registration for dual access and dual connectivity. Specifically, the
document put forward 5G User's service delivery in various radio condition and an attempt to solve the
challenges and problem to achieve high throughput at user device.
[2] draft-sfc-sinha-5g-bearer-dc-wifi. Proposal for dual connectivity on Wi-fi access of 5G– June’018.
[3] draft-sfc-sinha-5g-split-bearer-dual-access. Proposal for split bearer between RAN and Wi-Fi on 5G – June’18.
[4] draft-sfc-sinha-5g-ims-dual-reg. Proposal for mechanism of dual registration over RAN and Wi-Fi for IMS
services – June’18.
[6] RFC2119- Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI
10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[8] TS23.501- "3GPP TS23.501, System Architecture for the 5G System (Release 15)", March 2018.
[9] TS36.300 "3GPP TS36.300, Evolved Universal Terrestrial Radio Access(E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description", March 2018.
[12] TR38.801 "Study on new radio access technology: Radio access architecture and interfaces", March 2017.
[13] TR23.793 "Study on Access Traffic Steering, Switch and Splitting support in the 5G system architecture.",
April 2018.
[14] ETSI GR NGP 001 "Next Generation Protocol (NGP); Scenario Definitions”., May 2017.
[15] ETSI GR NGP 004 "Next Generation Protocol (NGP): Evolved Architecture for mobility using. Identity
Oriented Networks.”, January 2018.
The team members are from different industries with different experiences, expertise, and backgrounds. Their
joint supports which are all significant factors to success for study of this White Paper on 5th Generation of
Mobile Communication.
Profile: https://www.linkedin.com/in/sunil-s-14b096145/
Amardeep Sinha
Profile: https://www.linkedin.com/in/amardeep-sinha-0b270b1/
Yogesh Chandeshware
Bachelor’s degree in Telecom and specialist in IMS & VoLTE. Familiar with
Cloud (Open stack) & Virtual network.
Profile: https://www.linkedin.com/in/yogesh-chandeshware-a5360062/
Keywords
5G, Dual Connectivity, Dual Access, Data Flow, User Registration, Mobile Networks, Wireless Technologies
General Disclaimer
This document and the information contained in this document (collectively, the “Information”) is provided by
authors for Information purpose only because authors believe the Information may be useful. This Whitepaper
prepared is based on analysis of secondary information and knowledge available in the public domain and
authors is not liable for errors in secondary information whose accuracy cannot be guaranteed. The information
in this document may contain predictive statements including, without limitation, statements regarding the
future financial and operating results, future product portfolio, new technology, etc. There are a number of
factors that could cause actual results and developments to differ materially from those expressed or implied in
the predictive statements. Therefore, such information is provided for reference purpose only and constitutes
neither an offer nor an acceptance. The Information is provided solely on the basis that each business will be
responsible for making its own assessments of the Information and is advised to verify all representations,
statements and information before using or relying upon any of the Information. Author does not warrant the
accuracy of the Information and is not responsible for any damages arising from the use of or reliance upon the
Information. The information contained herein is for informational purposes only, and is subject to change
without notice.
Copyright
Copyright © 2019. All right reserved. No part of this document may be reproduced or transmitted in any form or
by any means without prior written consent to the authors.