Future Networks

<p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="05e50aaeb215a1"><em><span style="color: #333333;"><span style="color: #ff0000;">This version of the document currently provides detailed guidelines for implementation of 5G using Option 3, reflecting the initial launch strategy being adopted by multiple operators. However, as described in</span> <span style="color: #000000;">“</span></span><span style="color: #000000;"><a style="color: #000000;" href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gsma.com%2Ffuturenetworks%2Fwiki%2Foperator-requirements-for-5g-core-connectivity-options&amp;data=02%7C01%7Cdhutton%40gsma.com%7C6a81ff85d9ad4c76072308d6e52f0fa4%7C72a4ff82fec3469daafbac8276216699%7C0%7C0%7C636948387640012415&amp;sdata=%2FsYW81usNwnEW7%2Fw7at73vmShxYAFVcY0EsxtKLTK1o%3D&amp;reserved=0">GSMA Operator Requirements for 5G Core Connectivity Options</a></span><span style="color: #333333;"><span style="color: #000000;">”</span> <span style="color: #ff0000;">there is a need for the industry ecosystem to support all of the 5G core connectivity options (namely Option 2, Option 4, Option 5 and Option 7) in addition to Option 3.  As a result, this document will be updated during 2019 to provide guidelines for all 5G deployment options.</span></span></em></p> <p data-wiki-id="15e50aaeb215a9">&nbsp;</p> <p data-wiki-id="25e50aaeb215ab"><strong>To download this online document as a PDF, Please click below:</strong></p> <p data-wiki-id="35e50aaeb215ac"><a href="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/5G-Implementation-Guidelines-NSA-Option-3-v2.1.pdf" target="_blank" rel="noopener noreferrer">Public version </a></p> <p data-hash="jvgo3q91rjovgoaej1" data-wiki-id="45e50aaeb215ae">&nbsp;</p> <h2 id="1a0c8e89fde55ee5a3fac5f945ce6ce2"></h2> <h2 id="905532e09e998b01c82b866eb8ea7d96"><a name="_Toc3234081"></a>Overview</h2> <p data-wiki-id="55e50aaeb215af">&nbsp;</p> <h2 id="79839120b7a34387786968cadd0350b7"><a name="_Toc3234082"></a>Introduction</h2> <p data-wiki-id="65e50aaeb215b2">5G is becoming a reality as early adopters have already commercialized data-oriented 5G networks in 2018 and are planning to launch consumer mobile 5G in 2019 and beyond. Whilst early adopters do not necessarily require guidance, there are still a majority of the operator community that are yet to launch commercial 5G services. This document intends to provide a checklist for operators that are planning to launch 5G networks in NSA (non-standalone) Option 3 configuration.</p> <p data-wiki-id="75e50aaeb215b4"><strong> </strong></p> <h2 id="6205d8de554f94263ea3c784e41a3187"><a name="_Toc3234083"></a>Scope</h2> <p data-wiki-id="85e50aaeb215b6">This document provides technological, spectrum and regulatory considerations in the deployment.</p> <p data-wiki-id="95e50aaeb215b7">This version of the document currently provides detailed guidelines for implementation of 5G using Option 3, reflecting the initial launch strategy being adopted by multiple operators. However, as described in “<a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gsma.com%2Ffuturenetworks%2Fwiki%2Foperator-requirements-for-5g-core-connectivity-options&amp;data=02%7C01%7Cdhutton%40gsma.com%7C6a81ff85d9ad4c76072308d6e52f0fa4%7C72a4ff82fec3469daafbac8276216699%7C0%7C0%7C636948387640012415&amp;sdata=%2FsYW81usNwnEW7%2Fw7at73vmShxYAFVcY0EsxtKLTK1o%3D&amp;reserved=0">GSMA Operator Requirements for 5G Core Connectivity Options</a>” there is a need for the industry ecosystem to support all of the 5G core connectivity options (namely Option 2, Option 4, Option 5 and Option 7) in addition to Option 3.  As a result, this document will be updated during 2019 to provide guidelines for all 5G deployment options.</p> <p data-wiki-id="105e50aaeb215b8"><em>Editor’s note: The topics listed in this document is not exhaustive and is open to suggestion/contribution by any company. Please contact </em><a href="mailto:futurenetworks@gsma.com"><em>futurenetworks@gsma.com</em></a></p> <p data-wiki-id="115e50aaeb215ba"><em>Editor’s note: Section 2.9 (Security) and 2.11 (NetNeutrality/Regulatory Requirements) are for GSMA members only. For membership inquiries, please see the <a href="https://www.gsma.com/membership/">GSMA website</a>.</em></p> <h2 id="58d49cdcd79c2b6cd90f05d4680cddb9"><a name="_Toc3234084"></a>Acknowledgements</h2> <p data-wiki-id="125e50aaeb215bb">Special thanks to the following GSMA Checklist for Non-Standalone 5G Deployment taskforce members for their contribution and review of this document:</p> <ul> <li>AT&amp;T Mobility</li> <li>EE Limited</li> <li>Ericsson</li> <li>Huawei Technologies Co. Ltd.</li> <li>Hutchison 3G UK Limited</li> <li>KDDI</li> <li>LG Electronics Inc.</li> <li>MediaTek Inc.</li> <li>Nokia</li> <li>NTT DOCOMO</li> <li>Softbank Corp.</li> <li>Syniverse Technologies, Inc.</li> <li>Telecom Italia SpA</li> <li>Telefónica S.A.</li> <li>Telia Finland Oyj</li> <li>United States Cellular Corporation</li> <li>Utimaco TS GmbH</li> <li>Verizon Wireless</li> <li>Vodafone Group</li> <li>ZTE Corporation</li> </ul> <p data-wiki-id="135e50aaeb215bd">&nbsp;</p> <h3><a name="_Toc3234085"></a></h3> <h1 id="38969b90b16c43456e74d78addcfc9f7"><a name="_Toc3234088"></a><strong>1. Commercialisation of 5G</strong></h1> <h2 id="17032d4919d97a7ddf459eeeeab256f9"><a name="_Toc3234089"></a>1.1 Fixed Wireless Access</h2> <p data-wiki-id="145e50aaeb215be">FWA (Fixed wireless access) refers to a wireless link that provides connectivity to objects that are stationary or nomadic (i.e. almost no movement when connectivity is used). This concept has already been frequently used as a substitute to wireline connection in the last mile. Therefore, it is often compared with other last-mile connectivity solutions such as FTTx (Fibre-to-the-x) and xDSL (x Digital Subscriber Line). 5G, in all its deployment options, enables the FWA to be a competitive substitute to FTTx with its superior radio capabilities and therefore offers business opportunities for the mobile operators</p> <p data-wiki-id="155e50aaeb215bf">For mobile operators, the FWA provides cost-effective network deployment solution. As the wireless links are cheaper to set up and operate, the network cost in the last mile will be significantly reduced with FWA compared to the case of FTTx. This means that the broadband connectivity will be economically feasible with FWA that would otherwise have been infeasible. With FWA, mobile operators can enjoy the following business opportunities.</p> <ul> <li>Broadband demand currently underserved: with cheaper connectivity solution, traditionally unconnected homes that were considered economically infeasible can be connected, creating an additional broadband revenue stream.</li> <li>Fixed market that can be upgraded to broadband: in places where xDSL or copper lines are hard to be replaced, FWA can offer broadband upgrade and therefore provide upselling opportunities for existing fixed internet customers.</li> <li>Time-limited demand: it is economically infeasible to deploy wireline connection to suit demand that is time-limited (e.g., seasonal, holiday, etc.). FWA, on the other hand, can provide a cost-effective and easy connectivity solution to such demands.</li> <li>Internet of Things: cheaper connectivity solution enables cost-effective connectivity for Internet of Things applications, which tend to require cheap connectivity with less stringent requirements than that of the mobile broadband.</li> </ul> <p data-wiki-id="165e50aaeb215c0">In addition to the monetary benefits, the mobile operators will be able to provide social benefits to the nation by bridging the digital divide gap between unconnected and connected. Furthermore, the broadband connectivity will enable advanced services such as e-learning and e-government, contributing to the better welfare of society.</p> <p data-wiki-id="175e50aaeb215c2">&nbsp;</p> <h2 id="0db6c507ba639a6aca6d7edd8afcecb7"><a name="_Toc3234090"></a>1.2 Enhanced Mobile Broadband</h2> <p data-wiki-id="185e50aaeb215c3">Enhanced mobile broadband refers to the extension of the data demand that was addressed by traditional mobile broadband. 5G will provide enhance data speeds and experience with its superior radio. Although this is not a new business opportunity, the growth of data demand persists with increasing uptake of multimedia contents (e.g., video) and some markets (e.g., North East Asia and North America that will experience over 20 Exabytes per month mobile data traffic in 2023: see Figure 1) have urgent need to address the demand data growth.</p> <p data-wiki-id="195e50aaeb215c4">As a proven business case, enhanced mobile broadband is the priority use case in 5G deployment. Over 70% of CEOs surveyed by GSMA in October 2016 have confirmed such. Although connectivity yields low margin, it offers a stable revenue stream that will be able to bankroll the deployment of 5G to suit 5G use cases other than mobile broadband. Furthermore, as mobile broadband is the key value proposition that is offered by the operator, excelling in enhanced mobile broadband will differentiate the early adopter from its competitors. Therefore, although being a traditional business case, enhanced mobile broadband will be an integral part of 5G commercialisation.</p> <p style="text-align: center;" data-wiki-id="205e50aaeb215c5">Figure 1: Global Mobile Data Traffic (Source: Ericsson)</p> <p data-wiki-id="215e50aaeb215c7"><img class="alignnone wp-image-19007 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-1.png" alt="" width="1175" height="553" /></p> <h1 id="eb7ab6a5ffdc39e6149fecbcf21794c1"><a name="_Toc509847325"></a><a name="_Toc506990889"></a><a name="_Toc504483019"></a><a name="_Toc3234091"></a>2. Prerequisite for initial 5G NSA Option 3 launch</h1> <p data-wiki-id="225e50aaeb215c8">&nbsp;</p> <h2 id="ac3ad95941e89bc0e792d266c2e7e9b1"><a name="_Toc3234092"></a>2.1 Introduction</h2> <p data-wiki-id="235e50aaeb215c9">5G can be deployed in five different deployment options, where SA (standalone) options consist of only one generation of radio access technology and NSA options consist of two generations of radio access technologies (4G LTE and 5G). The early deployments will be adopting either non-standalone option 3 or standalone option 2 as the standardisation of these two options has already been completed.</p> <p data-wiki-id="245e50aaeb215ca">Non-standalone option 3 is where the radio access network is composed of eNBs (eNode Bs) as the master node and gNBs (gNode Bs) as the secondary node (see the left side of Figure 2). The radio access network is connected to EPC (Evolved Packet Core). The NSA option 3, as it leverages existing 4G deployment, can be brought to market quickly with minor modification to the 4G network. This option also supports legacy 4G devices and the 5G devices only need to support NR (New Radio) protocols so the device can also be developed quickly. On the other hand, NSA option 3 does not introduce 5GC and therefore may not be optimised for new 5G use cases beyond mobile broadband. In addition, depending on how 5G devices are developed, the EPC may need to be retained longer than in the case of having EPS (Evolved Packet System) for 4G alone (instead of supporting NSA Option 3).</p> <p data-wiki-id="255e50aaeb215cb">Standalone option 2 is where radio access network consists of only gNBs (gNode Bs) and connects to 5GC (5G Core), and the 5GC interworks with EPC (see right side of Figure 2). SA option 2 has no impact on LTE radio and can fully support all 5G use cases by enabling network slicing via cloud-native service-based architecture. On the other hand, this option requires both NR and 5GC, making time-to-market slower and deployment cost higher than that of NSA option 3. Furthermore, the devices would need to support NR and core network protocols so it would take more time to develop devices. Finally, as the standalone 5G System would need to interwork with EPS to ensure service continuity depending on coverage, the interworking between EPC and 5GC may be necessary.</p> <p style="text-align: center;" data-wiki-id="265e50aaeb215cc">Figure 2: High-level architecture of NSA Option 3x and SA Option 2</p> <p data-wiki-id="275e50aaeb215ce"><img class="alignnone size-full wp-image-21193" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-2-1.png" alt="" width="1132" height="514" /></p> <h2 id="61bdbd758ccbf455c69c6537127bcaae"><a name="_Toc3234093"></a>2.2 Spectrum</h2> <h3><a name="_Toc3234094"></a>2.2.1 Bands earmarked for 5G and their possible utilisation</h3> <p data-wiki-id="285e50aaeb215cf">Availability of a suitable amount of spectrum is the most important prerequisite to launch 5G. While globally harmonised bands will be allocated formally at WRC-19, several countries and regions have already identified candidate bands and in some cases already allocated them.</p> <p data-wiki-id="295e50aaeb215d0">When 5G deployment is driven by providing enhanced mobile broadband, the S and C bands, communications bands extending from 2GHz to 4GHz and 4GHz to 8GHz respectively, accommodate the 3.4GHz to 4.2 GHz frequency range which seems to be the most suitable option. These bands have been identified in many countries as primary bands for 5G and as Figure 3 shows, global harmonisation seems feasible in the lower part of such bands thus unlocking economies of scale in devices.</p> <p data-wiki-id="305e50aaeb215d1">Another band that has been gaining popularity for use in 5G is the so-called millimetre wave band that includes spectrum spanning from 24GHz to 29.5GHz as well as spectrum in the 37GHz to 43.5GHz. The very fast attenuation of the radio signal at these frequencies has cast doubts on the potential of using this spectrum to provide wide area coverage especially in the uplink direction where MIMO and beamforming may not be as effective as in the downlink, however field trials and simulations indicate that there is a key role to be played by mmWave in 5G.</p> <p data-wiki-id="315e50aaeb215d3">28GHz for example, is the band used for many of the Fixed Wireless Access trials and commercial launches and radio cells operating in mmWave are suitable for creating a thick capacity layer where needed (hotspots) as well as for many enterprise scenarios.</p> <p data-wiki-id="325e50aaeb215d4">The main attractiveness of mmWave, as Figure 4 shows, is the availability of very large bandwidth and the strong potential for global harmonization.</p> <p style="text-align: center;" data-wiki-id="335e50aaeb215d5">Figure 3: Spectrum in the S and C bands earmarked for use in 5G in selected countries</p> <p data-wiki-id="345e50aaeb215d6"><img class="alignnone size-full wp-image-21194" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-3-1.png" alt="" width="1104" height="574" /></p> <p style="text-align: center;" data-wiki-id="355e50aaeb215d7">Figure 4: Spectrum allocation in mmWave for selected countries</p> <p data-wiki-id="365e50aaeb215d8"><img class="alignnone size-full wp-image-21195" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-4-1.png" alt="" width="1096" height="571" /></p> <h3><a name="_Toc3234095"></a>2.2.2 Amount of spectrum needed</h3> <p data-wiki-id="375e50aaeb215da">It should be observed that the ITU IMT-2020 requirements, especially with regards to maximum throughput are based on the assumption of using 100MHz channels. From an analysis of the results of recent spectrum auctions in the 3.5 GHz spectrum, it was observed that only in few cases (e.g. Hungary 2016, United Kingdom 2018) operators will have that amount of spectrum available. The consequence is that the actual throughput that can be extracted from the 5G system will be inferior to the IMT-2020 requirement. It is important that operators are in the position to deliver 5G at a lower cost per Gbyte, therefore allocation of at least 100MHz is vital for such use cases.</p> <p data-wiki-id="385e50aaeb215db">&nbsp;</p> <h2 id="d979eacdad9e880f594deea2fbb24b98"><a name="_Toc3234096"></a>2.3 4G Radio network updates</h2> <h3><a name="_Toc3234097"></a>2.3.1 Number of sites needed</h3> <p data-wiki-id="395e50aaeb215dc">Thanks to the possibility of utilising advanced antenna techniques such as MIMO and beamforming, simulations have shown the feasibility of matching the downlink coverage provided by LTE 1800 MHz with 5G radio base stations operating at 3.5 GHz: the same cell grid can, therefore, be reused for the initial rollout. In the uplink direction, MIMO and beamforming are unpractical due to the limited real estate in the device, therefore if the uplink was to use the same frequencies as downlink, the size of the cell would “shrink” to the maximum range in the uplink.</p> <p data-wiki-id="405e50aaeb215dd">To overcome this problem it has been proposed to utilise lower band spectrum such as the 1800 MHz spectrum for the uplink data. In the first step, this is done using option 3 EN-DC, where the uplink data is transmitted on the FDD-band using LTE. To optimize the coverage further, both NR uplink control and user data channels can be transmitted on the FDD-band. This can be done using either NR-NR Carrier Aggregation (CA) or Supplementary uplink (SUL). Both these techniques allow the uplink transmission to be switched between the FDD-band and the 3.5 GHz band. The key difference is that NR CA also provides NR on the FDD-band downlink, using 3GPP-specified LTE-NR spectrum sharing, if needed. This provides opportunity to aggregate NR bandwidth as well as better operation of the NR uplink. For early device chipset implementations, NR CA seems to be more widely supported than SUL.</p> <p data-wiki-id="415e50aaeb215de">Note: In general it is possible to use CA in conjunction with DC. That is CCs can be aggregated (in E-UTRA and/or NR) and then DC is applied.</p> <h3><a name="_Toc3234098"></a>2.3.2 LTE upgrade to support EN-DC (Option 3)</h3> <p data-wiki-id="425e50aaeb215e0">For a successful deployment of EN-DC the 4G network needs to support dual connectivity between E-UTRAN (LTE) and NR. This enhancement allows a device to consume radio resources provided by both 4G and 5G. Typically the 4G radio will be used to carry control signalling while NR and/or LTE will be used for user data. Three variants of the NSA solution have been defined each producing a different impact on the LTE network.</p> <p data-wiki-id="435e50aaeb215e1">Option 3 uses the MN (Master Node) terminated MCG (Master Cell Group) bearer for signalling. There are a few variants for data bearer configuration within Option 3. The industry main-stream is to use an SN-terminated split bearer (sometimes referred to as “Option 3x”).  This variant has low impact on EPC and enables data to route directly to the NR gNB to avoid excessive user plane load on the existing LTE eNB, which was designed for 4G LTE traffic load and not additional NR traffic load. As service continuity after the loss of 5G radio coverage is more graceful in this variant, it also minimizes excessive signalling traffic between RAN and core.</p> <p data-wiki-id="445e50aaeb215e2"><em> </em></p> <h2 id="95b7d1652b6b677cfacd9b4d8c2d0508"><a name="_Toc3234099"></a>2.4 4G Core network updates</h2> <p data-wiki-id="455e50aaeb215ef">4G Core network updating considerations mainly include option 3/3a/3x networking comparison, 4G core network upgrade strategy, network function upgrading.</p> <h3><a name="_Toc3234100"></a>2.4.1 Option 3/3a/3x Networking Comparison</h3> <p data-wiki-id="465e50aaeb215f0">The standardised NSA EPC networking architecture includes Option 3, Option 3a, and Option 3x.</p> <p data-wiki-id="475e50aaeb215f2">In the Option 3 networking mode, the X2 interface traffic between eNB and gNB has NSA user plane traffic. This traffic is huge. The core network needs to increase the bandwidth of the S1-U interface to meet the LTE/NSA transmission requirements.</p> <p data-wiki-id="485e50aaeb215f3">In the Option 3a networking mode, there is only control plane traffic in the X2 interface. So the X2 traffic is very small.</p> <p data-wiki-id="495e50aaeb215f4">In the Option 3x networking mode, there is a little LTE user plane traffic in the X2 interface.</p> <p data-wiki-id="505e50aaeb215f5">From the perspective of the impact on the existing network, the Option 3x is relatively small and has become the mainstream choice for NSA networking. By using 4G as the anchor point of the control plane, it can meet good service continuity and support rapid network construction in the initial stage of 5G deployment.</p> <p style="text-align: center;" data-wiki-id="515e50aaeb215f6">Figure 5: NSA Option 3/3a/3x Networking Mode</p> <p data-wiki-id="525e50aaeb215f8"><img class="alignnone size-full wp-image-21196" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-5-1.png" alt="" width="1163" height="370" /></p> <p data-wiki-id="535e50aaeb215f9"><span style="color: #000000; font-size: 1.4em;">2.4.2 Impact Analysis on 4G Core Network Elements</span></p> <p data-wiki-id="545e50aaeb215fa">Dual Connectivity used for Master eNodeB to connect to Secondary eNodeB has been standardized in the 4G network. NSA Option 3/3a/3x has adopted the 4G Dual Connectivity process.</p> <p data-wiki-id="555e50aaeb215fb">The impact on 4G core network elements supports the NSA, which is shown in Table 1.</p> <p data-wiki-id="565e50aaeb215fc">Table 1: Update requirement</p> <table> <tbody> <tr> <td><strong>NE</strong></td> <td><strong>Upgrade Requirement</strong></td> </tr> <tr> <td>MME</td> <td> <ul> <li>Support high bandwidth with extended QoS</li> <li>Support 5G subscription access control (DCNR, Secondary RAT)</li> <li>Support reporting Secondary RAT traffic</li> <li>Support adding the DNS FQDN information with the NC-NR tag and querying the NSA S-GW information</li> </ul> </td> </tr> <tr> <td>DNS</td> <td> <ul> <li>Match the DNS FQDN with the NC-NR tag and return the NSA S-GW information (no upgrade requirement)</li> </ul> </td> </tr> <tr> <td>SGW/PGW</td> <td> <ul> <li>Support high bandwidth with extended QoS</li> <li>Support 5G subscription access control (DCNR, Secondary RAT)</li> <li>Support reporting Secondary RAT traffic</li> </ul> </td> </tr> <tr> <td>CG/OCS</td> <td> <ul> <li>CDR supports high bandwidth with extended QoS field portability</li> <li>CDR supports Secondary RAT field portability</li> <li>CDR adds 5G traffic report Secondary RAT Usage Reports</li> </ul> </td> </tr> <tr> <td>HSS</td> <td> <ul> <li>ARD access restriction data adds 5G NR access restriction</li> <li>AMBR maximum guaranteed bandwidth adds the maximum uplink/downlink bandwidth</li> <li>Extended-Max-Requested-BW-UL</li> <li>Extended-Max-Requested-BW-DL</li> </ul> </td> </tr> <tr> <td>PCRF</td> <td> <ul> <li>A new QoS extended bandwidth AVP is added to the Gx interface:</li> <li>Extended-Max-Requested-BW-DL and Extended-Max-Requested-BW-UL AVP</li> <li>Extended-GBR-DL and Extended-GBR-UL AVP</li> <li>Extended-APN-AMBR-DL and Extended-APN-AMBR-UL AVP</li> </ul> </td> </tr> </tbody> </table> <p data-wiki-id="575e50aaeb215fd">To support NSA, the 4G core network needs to do a small software upgrade to add or expand several parameters. There is no need to make any modifications to the hardware. The overall process including handover is not different from that of 4G network.</p> <p data-wiki-id="585e50aaeb21601">&nbsp;</p> <h3><a name="_Toc3234102"></a>2.4.3 4G Core Network Upgrading Strategy</h3> <p data-wiki-id="595e50aaeb21605">EPC types include physical EPC based on dedicated hardware and virtualized EPC based on COTS (Commercial Off The Shelf) hardware. There are two typical scenarios for EPC upgrade to support 5G deployment.</p> <p data-wiki-id="605e50aaeb21606">Scenario A:</p> <ul> <li>Physical EPC is upgraded to support NSA.</li> <li>Capacity expansion is based on physical EPC.</li> </ul> <p data-wiki-id="615e50aaeb21607">Scenario B:</p> <ul> <li>Build a new virtualized EPC network to support NSA independently.</li> <li>Interoperability is made between the new virtualized EPC and the physical EPC.</li> <li>Capacity expansion is based on the virtualized EPC.</li> </ul> <p style="text-align: center;" data-wiki-id="625e50aaeb21608">Figure 6: EPC Upgrading for NSA Deployment</p> <p data-wiki-id="635e50aaeb2160a"><img class="alignnone wp-image-19016 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-6.png" alt="" width="1117" height="348" /></p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="645e50aaeb2160b">Scenario A is the easiest way, but it has also brought a big drawback. When evolving to 5G SA, this physical EPC based on dedicated hardware cannot be used in a virtualized environment. This scenario depends on the capabilities of the existing network equipment vendors. Compared to scenario A, scenario B can be smoothly evolved to the target network through the expansion of virtualized EPC.</p> <h2 id="8cb93af06277b80cf7b9805cf9960882"><a name="_Toc3234103"></a>2.5 5G deployment</h2> <p class="NormalParagraph" data-wiki-id="655e50aaeb2160c">5G network deployment considerations mainly include target network planning, Massive MIMO order selection, coverage optimization especially in uplink, time slot synchronization configuration, NSA and SA strategy and network deployment steps.</p> <p class="NormalParagraph" data-wiki-id="665e50aaeb2160d">ITU-defined 5G applications include three types: eMBB, mMTC and uRLLC. At the current stage, based on the 3GPP R15 standard, 5G network focuses on eMBB service, so 5G target network needs to meet the typical eMBB service experience requirements.</p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="675e50aaeb2160e">3GPP has defined the performance requirements for high data rates and traffic densities as the following table in 3GPP TS 22.261 [7], and 50Mbps at downlink is the basic requirement of eMBB service experience (see Table 2)</p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="685e50aaeb21610">From a business perspective, 4K/8K video and VR are eMBB typical services. As shown in the following table, these services require a downlink throughput of 50 to 100 Mbps and an uplink rate of 3 to 5 Mbps (see Table 3).</p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="695e50aaeb21611">For the 5G network deployment in early stage, downlink 100Mbps and uplink 5Mbps are required to meet the service experience requirements.</p> <p data-wiki-id="705e50aaeb21612">Table 2: Performance requirements for high data rates and traffic densities</p> <table width="100%"> <tbody> <tr> <td width="14%">Scenario</td> <td width="17%">Experienced data rate (DL)</td> <td width="17%">Experienced data rate (UL)</td> <td width="17%">Area traffic capacity (DL)</td> <td width="17%">Area traffic capacity (UL)</td> <td width="17%">Overall user density</td> </tr> <tr> <td width="14%">Urban</td> <td width="17%">50 Mbps</td> <td width="17%">25 Mbps</td> <td width="17%">100 Gbps/km<sup>2</sup></td> <td width="17%">50 Gbps/km<sup>2</sup></td> <td width="17%">10 000/km<sup>2</sup></td> </tr> <tr> <td width="14%">Rural</td> <td width="17%">50 Mbps</td> <td width="17%">25 Mbps</td> <td width="17%">1 Gbps/km<sup>2</sup></td> <td width="17%">500 Mbps/km<sup>2</sup></td> <td width="17%">100/km<sup>2</sup></td> </tr> <tr> <td width="14%">Indoor hotspot</td> <td width="17%">1 Gbps</td> <td width="17%">500 Mbps</td> <td width="17%">15 Tbps/km<sup>2</sup></td> <td width="17%">2 Tbps/km<sup>2</sup></td> <td width="17%">250 000/km<sup>2</sup></td> </tr> <tr> <td width="14%">Dense urban</td> <td width="17%">300 Mbps</td> <td width="17%">50 Mbps</td> <td width="17%">750 Gbps/km<sup>2</sup></td> <td width="17%">125 Gbps/km<sup>2</sup></td> <td width="17%">25 000/km<sup>2</sup></td> </tr> <tr> <td width="14%">High-speed vehicle</td> <td width="17%">50 Mbps</td> <td width="17%">25 Mbps</td> <td width="17%">[100] Gbps/km<sup>2</sup></td> <td width="17%">[50] Gbps/km<sup>2</sup></td> <td width="17%">4 000/km<sup>2</sup></td> </tr> </tbody> </table> <p data-wiki-id="715e50aaeb21613">Table 3: Service requirements (Source: Huawei)</p> <table width="100%"> <tbody> <tr> <td width="30%">Service</td> <td width="23%">Resolution</td> <td width="24%">2D</td> <td width="22%">3D</td> </tr> <tr> <td rowspan="3" width="30%">Smart phone/ Surveillance</td> <td width="23%">720P</td> <td width="24%">~1.5Mbps</td> <td width="22%"></td> </tr> <tr> <td width="23%">1080P</td> <td width="24%">~4Mbps</td> <td width="22%"></td> </tr> <tr> <td width="23%">2K</td> <td width="24%">~10Mbps</td> <td width="22%"></td> </tr> <tr> <td width="30%">4K/ Basic VR/AR</td> <td width="23%">4K</td> <td width="24%">~25Mbps</td> <td width="22%"><strong><em>~50Mbps</em></strong></td> </tr> <tr> <td width="30%">8K/Immersive VR/AR</td> <td width="23%">8K</td> <td width="24%">~50Mbps</td> <td width="22%"><strong>~100Mbps</strong></td> </tr> </tbody> </table> <h3><a name="_Toc3234104"></a>2.5.1 Massive MIMO Selection</h3> <p data-wiki-id="725e50aaeb21614">Massive MIMO can improve both coverage and capacity and is a key technical solution for 5G network. But the deployment of Massive MIMO requires three considerations including performance requirements, installation requirements, and TCO saving.</p> <p data-wiki-id="735e50aaeb21616">In the initial stage of 5G, from the perspective of coverage and capacity maximization, it is recommended that 5G and 4G co-site deployment to ensure continuous coverage and reduce planning and optimization costs.</p> <p data-wiki-id="745e50aaeb21623">Engineering constraint is also an important aspect to consider. In some scenarios, there are limits to the weight and volume of the Massive MIMO unit. For example, in South Korea, the engineering department requires AAU weight not to exceed 25kg, and the installation of equipment over 40kg requires the use of Crane in the Netherlands, which costs 1K Euro per 6 hours. In this scenario, 32T is an option for deploying 5G networks.</p> <p data-wiki-id="755e50aaeb21626">In high-rise scenarios, 2D beamforming will provide benefits compared to 1D beamforming, see Figure 7, and therefore 64T or 32T may have performance advantages compared to 16T. In urban and suburban areas, the user spread in the vertical dimension is normally so small that vertical beamforming will not provide any substantial advantages. Therefore 16T will have similar performance as 64T or 32T in many such scenarios.</p> <p style="text-align: center;" data-wiki-id="765e50aaeb21627">Figure 7: Comparison between 64T/32T and 16T</p> <p data-wiki-id="775e50aaeb21628"><img class="alignnone wp-image-19019 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-9.png" alt="" width="971" height="510" /></p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="785e50aaeb2162a">5G network deployment needs to fully consider performance, cost, space and weight limitation, etc. The most cost effective configuration, 64T, 32T or 16T may be different for different deployment scenarios due to the different performance benefits in the scenarios, respectively. 64T/32T tends to perform better in dense-urban high-rise scenarios and hence may be more cost efficient, whereas 32T or 16T tend to be more cost efficient in urban and suburban scenarios.</p> <p data-wiki-id="795e50aaeb2162b">2T2R/4T4R/8T8R solution should be considered as a basic configuration for 5G deployment, deploying 16T16R/32T32R/64T64R to meet capacity requirements in those sites that need capacity upgrades and are heavy loaded.</p> <h3><a name="_Toc3234105"></a>2.5.2 Coverage Enhancement</h3> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="805e50aaeb2162c">C-band is the primary band for 5G network and it has the large bandwidth making it perfect for 5G eMBB services. Downlink coverage is better than uplink coverage on C-band spectrum due to the large downlink transmit power of the gNodeB and to disproportion in uplink and downlink timeslot allocations of NR. The application of technologies such as beamforming and cell-specific reference signal (CRS)-free reduces downlink interference and further increases the difference between C-band uplink and downlink coverage. As shown in Figure 8, taking the downlink 50Mbps and the uplink 5Mbps as an example, the C-band uplink and downlink coverage differs by 16.2dB.</p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="815e50aaeb2162d">The C-Band downlink can achieve the similar coverage as the LTE 1800MHz, but there is limitation in the uplink coverage and becomes 5G deployment bottleneck which will affect the user experience. As shown in Figure 9, the difference between C-Band and LTE 1800MHz uplink coverage is 7.6 dB for 2R and 10.4dB for 4R.</p> <p data-wiki-id="825e50aaeb2162e">Table 4: Comparison between 64T, 32T and 16T</p> <table width="100%"> <tbody> <tr> <td width="27%">To Cover Same Area</td> <td width="24%">64T</td> <td width="24%">32T</td> <td width="24%">16T</td> </tr> <tr> <td width="27%">Require Site Number</td> <td width="24%">1</td> <td width="24%">1.18X</td> <td width="24%">1.48X</td> </tr> <tr> <td width="27%">CAPEX</td> <td width="24%">1</td> <td width="24%">0.95X</td> <td width="24%">1.11X</td> </tr> <tr> <td width="27%">OPEX</td> <td width="24%">1</td> <td width="24%">1.55X</td> <td width="24%">2.83X</td> </tr> </tbody> </table> <p style="text-align: center;" data-wiki-id="835e50aaeb2162f">Figure 8: Uplink and Downlink Coverage difference of C-Band</p> <p data-wiki-id="845e50aaeb21631"><img class="alignnone wp-image-19020 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-10.png" alt="" width="832" height="297" /></p> <p style="text-align: center;" data-wiki-id="855e50aaeb21632">Figure 9: Uplink Coverage difference between C-Band and LTE 1800MHz</p> <p data-wiki-id="865e50aaeb21633"><img class="alignnone wp-image-19034 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-11-1.png" alt="" width="998" height="322" /></p> <p data-wiki-id="875e50aaeb21634">3GPP Release 15 introduces two mechanisms to handle the limited uplink coverage on the higher bands, namely NR Carrier Aggregation (CA) and supplementary uplink (SUL). The use of these mechanisms effectively utilize idle sub-3 GHz band resources, improve the uplink coverage of C-band, and enable the provisioning of 5G services in a wider area. Both solutions, NR CA and SUL, offer transport of UL user data using sub-3GHz band NR radio resources. NR CA provides the added benefit of also providing sub-3GHz DL user data support. Based on the SUL, the feature Uplink and Downlink Decoupling defines new paired spectrums, where C-band is used for the downlink and a sub-3 GHz band (for example, 1.8 GHz) for the uplink, thereby improving uplink coverage. Figure 10 shows how UL and DL Decoupling works.</p> <p data-wiki-id="885e50aaeb21635">Field tests show that combining DL on C-band with UL on sub-3 GHz  can improve both uplink and downlink experience by 6 times (see Figure 11).</p> <p style="text-align: center;" data-wiki-id="895e50aaeb21637">Figure 10: Combining DL on C-band with UL on sub-3GHz band</p> <p data-wiki-id="905e50aaeb21638"><img class="alignnone wp-image-19035 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-12-1.png" alt="" width="1115" height="663" /></p> <p style="text-align: center;" data-wiki-id="915e50aaeb2163c">Figure 11: Field Test Result</p> <p style="text-align: center;" data-wiki-id="925e50aaeb2163d"><img class="alignnone wp-image-19023 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-13.png" alt="" width="872" height="467" /></p> <p style="text-align: center;" data-wiki-id="935e50aaeb2163e">Figure 12: Interference and Guardband with non-synchronization time slot</p> <p data-wiki-id="945e50aaeb2163f"><img class="alignnone wp-image-19024 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-14.png" alt="" width="1174" height="186" /></p> <p style="text-align: center;" data-wiki-id="955e50aaeb21640">Figure 13: 4:1 and 8:2 time slot configuration<img class="alignnone size-full wp-image-21209" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/MODFIG15.png" alt="" width="1003" height="466" /></p> <h3><a name="_Toc3234106"></a>2.5.3 Synchronisation Configuration</h3> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="965e50aaeb21642">The TDD system has the same TX/RX frequency bands, the TX signal of the asynchronous system directly interferes with RX frequency band. If 5G macro-cell networks are not synchronized, more than 25 MHz additional guard band together with additional transceiver filters would be required. Thus, synchronization of 5G network becomes the best way to avoid interference. In this way, efficient spectrum usage is ensured – no additional guard band is required – and network equipment cost can be reduced (see Figure 12).</p> <p class="NormalParagraph" data-wiki-id="975e50aaeb21643">For operators in the same country and region, it is recommended to use the unique synchronisation configuration in the adjacent frequency bands to avoid interference.</p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="985e50aaeb21644"><span lang="EN-GB">In the scenario without C-Band TDD LTE, a 3:1 or 4:1 configuration can be used. In the scenario with C-Band TDD LTE, two NR 8:2 configurations are possible to match existing TD-LTE network making spectrum fully utilized, one with the same frame start as LTE and the other with a frame start offset compared to LTE (see Figure 13).</span></p> <h3><a name="_Toc3234107"></a>2.5.4 NSA and SA Strategy</h3> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="995e50aaeb21645">3GPP defines NSA and SA architectures and the two architectures have been concluded. Option 3x for NSA and Option 2 for SA has become an industry consensus.</p> <p class="NormalParagraph" style="text-align: left;" align="left" data-wiki-id="1005e50aaeb21647">SA is the target architecture, but the NSA ecosystem leads the SA for 6 months. The NSA can quickly deploy 5G network to support eMBB services and can be software upgraded to SA in the future. Key factors of NSA / SA architecture selection listed in Table 5.</p> <p data-wiki-id="1015e50aaeb21648">A network that migrates from NSA to SA will typically support multiple Options simultaneously, by selecting the most suitable configuration for each device.</p> <p style="text-align: center;" data-wiki-id="1025e50aaeb21649">Figure 14: Option 3x for NSA and Option 2 for SA</p> <p data-wiki-id="1035e50aaeb2164a"><img class="alignnone size-full wp-image-21198" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-16-1.png" alt="" width="861" height="379" /></p> <p data-wiki-id="1045e50aaeb2164b">Table 5: Comparison between NSA Option 3 and SA Option 2</p> <table width="100%"> <tbody> <tr> <td width="20%"></td> <td width="46%">Option 3x</td> <td width="33%">Option 2</td> </tr> <tr> <td rowspan="2" width="20%">Standard</td> <td width="46%">17 Q4</td> <td width="33%">18 Q2</td> </tr> <tr> <td colspan="2" width="79%">Option 3x support 5G initial fast deployment, Option 2 0.5~1 year late</td> </tr> <tr> <td width="20%">Data Experience</td> <td colspan="2" width="79%">Option 3x: Smooth mobility without a need for frequent inter RAT handover <span style="font-family: inherit;">or inter RAT reselection (unless wide 5G coverage), better peak rate (unless LTE-NR spectrum sharing/reframing)</span></td> </tr> <tr> <td rowspan="2" width="20%">Coverage</td> <td width="46%">DC /NR-CA or DC / SUL</td> <td width="33%">NR CA (or SUL)</td> </tr> <tr> <td colspan="2" width="79%">EN-DC provides coverage and service continuity for NSA, NR-CA (and possibly SUL) optimizes coverage for both NSA &amp; SA, and provides service continuity for SA</td> </tr> <tr> <td rowspan="2" width="20%">Voice</td> <td width="46%">VoLTE</td> <td width="33%">EPS fallback (initially) or VoNR (target)</td> </tr> <tr> <td colspan="2" width="79%">Suitable solution with the experience at same level</td> </tr> <tr> <td width="20%">Service Readiness</td> <td width="46%">eMBB</td> <td width="33%">eMBB/uRLLC</td> </tr> <tr> <td rowspan="2" width="20%">Deployment complexity</td> <td width="46%">DC</td> <td width="33%">NR CA / LTE-NR spectrum sharing  (SUL)</td> </tr> <tr> <td colspan="2" width="79%">NSA with mandatory DC needs LTE upgrade; SUL which extends SA Coverage need LTE upgrade, complexity at same level</td> </tr> <tr> <td rowspan="2" width="20%">Relevance with existing LTE</td> <td width="46%">DC</td> <td width="33%">LTE-NR spectrum sharing, SUL / Refarming</td> </tr> <tr> <td colspan="2" width="79%">DC, SUL are both relevant to LTE; Coordination after Refarming Legacy LTE is important, NSA/SA are both closely relevant to legacy LTE.</td> </tr> </tbody> </table> <h3><a name="_Toc3234108"></a>2.5.5 5G Network Deployment Strategy in initial stage</h3> <p data-wiki-id="1055e50aaeb2164d">Compared with 4G, the capacity of 5G network is larger, which can greatly enhance the user experience. In addition, operators need to consider 5G network deployment from high value scenarios, users, and services to enhance brand and user experience.</p> <p data-wiki-id="1065e50aaeb21650">That means that operators will focus on core urban areas, hotspots, and high value areas to rapidly deploy 5G networks and provide services with traffic and brand demand.</p> <ul> <li>High-value scenarios and areas include CBD, universities, governments, hospitals, airports, subways, etc.</li> <li>High-value users include three type users: high package, high traffic volume an high value terminal.</li> <li>Besides eMBB services such as video and VR, operators focus on industry incubation, evaluate the earliest mature areas including connected drones, industrial internet, telemedicine and so on and work with innovative partners.</li> </ul> <p data-wiki-id="1075e50aaeb21654">&nbsp;</p> <p style="text-align: center;" data-wiki-id="1085e50aaeb21655">Figure 15: 3 Areas for Initial 5G Deployment</p> <p data-wiki-id="1095e50aaeb21656"><img class="alignnone wp-image-19027 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-17.png" alt="" width="772" height="540" /></p> <h2 id="2cba0e9c6a1efdc93a318f6efefd0671"><a name="_Toc3234109"></a>2.6 Transmission / backhaul</h2> <p data-wiki-id="1105e50aaeb21657">Fronthaul implementation is considered as a key element in order to manage mobile data growth, reduced latency required by 5G use cases and provide scalability in terms of RAN densification, micro cells deployment and future evolutions towards Cloud RAN.</p> <p data-wiki-id="1115e50aaeb21659">Regarding interfaces to be adopted, eCPRI and O-RAN seem to be the main candidate for RRU and CU/DU connection for the 5G scenario, with a bandwidth granularity of 25 Gbit/s. Even though CPRI is currently proposed for 4G Fronthaul deployment, the aim should be to adopt a single interface, eCPRI, for both 4G and 5G networks with defined requirements in term of Jitter/latency.</p> <p data-wiki-id="1125e50aaeb2165a">It is still to be investigated the opportunity to deploy also Midhaul segment, e.g. by mean of aggregation rings between Distributed Unit (DU) and Centralized Unit (CU).</p> <p data-wiki-id="1135e50aaeb2165b">Given the fact that 5G networks are mainly based on TDD multiplexing, accurate Phase synchronization is mandatory. The implementation of a GPS receiver on each radio system represents a potential solution, even though this approach comes with high deployment cost and reliability or security issues. Another solution is based on PTP ITU profiles implementation in Partial Timing Support or Full Timing Support.</p> <p data-wiki-id="1145e50aaeb2166a">IPSec deployment in 5G transport network will have to consider potential Edge Computing implementation. In fact, the shift of Virtualized Functions at the edge of the network will imply to not use IPSec or terminate IPsec tunnels at Edge POP level.</p> <p data-wiki-id="1155e50aaeb2166c">&nbsp;</p> <h2 id="71d6bca8f120629e7a520cc9d0693ec5"><a name="_Toc3234110"></a>2.7 Devices</h2> <p data-wiki-id="1165e50aaeb2166d">The device deployment needs to follow the related Network deployment option.</p> <p data-wiki-id="1175e50aaeb2166e">A device that needs to work within a Network implementing NSA option, it shall support all protocols requested by NSA implementation and could support all protocols requested by SA implementation.</p> <p data-wiki-id="1185e50aaeb2166f">A device that needs to work within a Network implementing SA option, it shall support all protocols requested by SA implementation and could support all protocols requested by NSA implementation.</p> <p data-wiki-id="1195e50aaeb21671">As true for Network deployment also for device deployment the support to the NSA option, with the eNBs (eNode Bs) as the master node, could be faster than the whole SA deployment.</p> <p data-wiki-id="1205e50aaeb21672">The above NSA option permits the devices to avoid supporting also 5G core network protocols at first stage.</p> <p data-wiki-id="1215e50aaeb21673">While for Network deployment supporting SA options the device needs to support whole 5G core network protocols with higher deployment cost and time.</p> <p data-wiki-id="1225e50aaeb21674">Based on the experience for 3G and 4G technologies also for 5G technologies we expect progressive deployment and support of whole 5G functionalities in order to find a way to average the time-to-market with the new services support.</p> <p data-wiki-id="1235e50aaeb21679">Same approach is valid for devices also when we consider the support to the different frequency bands.</p> <p data-wiki-id="1245e50aaeb2167a">On one side the support to the sub-6GHz band can create affordable challenge to the device manufacturers permitting a faster time-to-market; on the other side this band is not optimised for new 5G use cases except the mobile broadband.</p> <p data-wiki-id="1255e50aaeb2167b">Instead the so called mmWave bands are the optimised bands to support the whole 5G services and use cases; but due to the very fast attenuation of the radio signal and the difficulties to manage so high frequencies their support can create big challenges to device manufacturers requesting more time and higher cost compared with only Sub6GHz support.</p> <p data-wiki-id="1265e50aaeb2167c">Based on above aspects the test-set related to the 5G devices should be customized based on device functionalities support, considering different sub-set related to NSA, SA, Sub6GHz, mmWave, VoNR.</p> <p data-wiki-id="1275e50aaeb2167e">&nbsp;</p> <h2 id="38421ed7358d8e434241355a60eab58d"><a name="_Toc3234111"></a>2.8 Network Sharing</h2> <p data-wiki-id="1285e50aaeb2167f">Mobile networks operate on a network infrastructure, which is not only limited to electronic components, but also includes passive elements such as physical sites and towers that are required to operate network. As network have been densified from previous generations to 4G, sharing of network infrastructure is becoming more popular. This is expected to continue in the 5G era where networks will be densified even more. Network sharing comes in many forms, but it is mostly classified according to the technological components that are being shared (see Figure 16).</p> <p data-wiki-id="1295e50aaeb21680">Passive infrastructure sharing is where non-electronic infrastructure at a cell site, such as power supply and management system, and physical elements such backhaul transport networks are shared. This form can be further classified into site sharing, where physical sites of base stations are shared, and shared backhaul, where transport networks from radio controller to base stations are shared.</p> <p data-wiki-id="1305e50aaeb21681">Active infrastructure sharing is sharing of electronic infrastructure of the network including radio access network (consists of antennas/transceivers, base station, backhaul networks and controllers) and core network (servers and core network functionalities). This form can be further classified into MORAN (Multi-Operator Radio Access Network), where radio access networks is shared and dedicated spectrum is used by each sharing operator, MOCN (Multi-Operator Core Network), where radio access networks and spectrum are shared, and core network sharing, where servers and core network functionalities are shared.</p> <p data-wiki-id="1315e50aaeb21685">Note that passive infrastructure sharing is the simplest and can be implemented per sites, which enables operators to easily share sites and maintain their strategic competitiveness depending on the sites shared. Operation is also easier with this form of sharing because network equipment remains separated. However, the cost saving potential of sharing is limited relative to other forms of sharing.</p> <p data-wiki-id="1325e50aaeb21686">MORAN and MOCN enables greater cost sharing potential than passive sharing, and they can be implemented per sites and enables strategic differentiation. However, operation of network equipment needs to be shared (or at least issues must be shared with participants) and therefore increases the complexity of sharing relative to site sharing. Core network is complicated to operate and to maintain strategic differentiation. It is important to note that core network sharing has not been popular and only few cases have been suspected to be so.</p> <p style="text-align: center;" data-wiki-id="1335e50aaeb21687">Figure 16: Classification of network infrastructure sharing</p> <p data-wiki-id="1345e50aaeb21689"><img class="alignnone wp-image-19028 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-18.png" alt="" width="1223" height="473" /></p> <h3><a name="_Toc3234112"></a>2.8.1 Benefits of Sharing</h3> <p data-wiki-id="1355e50aaeb2168a">BEREC [2] published a document where the following benefits are listed:</p> <ul> <li>Cost Savings benefits:</li> <li>passive sharing cost savings: [16%-35%] CAPEX, [16%-35%] OPEX;</li> <li>active sharing (excl. spectrum) cost savings: [33%-35%] CAPEX, [25%-33%] OPEX;</li> <li>active sharing (incl. spectrum) cost savings: [33%-45%] CAPEX, [30%-33%] OPEX;</li> <li>core network sharing: core network sharing cost savings are limited.</li> <li>Environmental benefits – reduces energy consumption, mitigate citizens’ concern over radiation</li> <li>Customer experience – sharing can lead to better quality of the services, better coverage, higher data speed.</li> <li>Coverage obligation can be met</li> </ul> <p data-wiki-id="1365e50aaeb216a9">The reduced cost can be diverted to other services and innovation, maximizing the potential of the capital resources of the mobile operator. Furthermore, network infrastructure sharing resolves difficulties in acquiring sites for the access network, where sharing operators can jointly cooperate to acquire sites. Consequently, the cost of 5G deployment can be reduced with sharing of costs/difficulties associated with sites. The technical enablers in the 5G era such as SDN (Software Defined Networking) and NFV (Network Function Virtualization) also makes the network more accommodating to the network infrastructure sharing.</p> <p data-wiki-id="1375e50aaeb216ab">&nbsp;</p> <h3><a name="_Toc3234113"></a>2.8.2 Obligations and challenges</h3> <p data-wiki-id="1385e50aaeb216ac">Network infrastructure sharing may lead to hindrance in competition among mobile network operators. When the network infrastructure is shared, it is inherently difficult to differentiate or corroborate own network infrastructure to compete against the sharing partners. Whilst it is possible to compete on the basis of services, the regulatory obligation of mobile networks tends to focus on the network connectivity and consequently the infrastructure. This concern can be minimized if the sharing is limited to the scope of passive infrastructure. As active components can be differentiated while optimising the cost of passive infrastructure, competition among sharing operators can still be active.</p> <p data-wiki-id="1395e50aaeb216b1">Furthermore, it is very challenging to consolidate existing network infrastructure to share. An existing network is a result of planning and operations phases based on specific operator requirements, and consolidating existing networks is likely to be difficult if any of the requirements conflict. As NSA option 3 leverages existing LTE network infrastructure, it may also be challenging to implement network infrastructure sharing, unless it is limited to new NR base stations. The sharing of network infrastructure may be more feasible with SA option 2, where both radio access and core networks will be newly deployed, given that the operators will collaborate from the planning phase.</p> <p data-hash="jtyi1okm5796lai09yf" data-wiki-id="1405e50aaeb216b2">&nbsp;</p> <h2 id="85e6d294689ceec6414a5e53c49b7688"></h2> <p data-wiki-id="1415e50aaeb216b3">&nbsp;</p> <h2 id="691b7370df351894b376df6416d68b5f">2.10 Testing</h2> <p data-wiki-id="1425e50aaeb216b4">In deploying NSA 5G network, the items in Table 6 need to be tested to ensure reliable and functional 5G network.</p> <p data-wiki-id="1435e50aaeb216b6">Table 6: Test items for NSA Deployments</p> <table> <tbody> <tr> <td width="302">Content</td> <td width="473">Item</td> <td width="766">Function</td> </tr> <tr> <td rowspan="5" width="302">LTE/NR DC</td> <td width="473">LTE/NR Interface</td> <td width="766">To test X2 interface</td> </tr> <tr> <td width="473">MN terminated MCG Bearer</td> <td width="766">To test MN terminated MCG bearer functionality</td> </tr> <tr> <td width="473">SN terminated SCG Bearer</td> <td width="766">To test SN terminated SCG bearer functionality</td> </tr> <tr> <td width="473">MN terminated split Bearer</td> <td width="766">To test MN terminated split bearer functionality</td> </tr> <tr> <td width="473">SN terminated split Bearer</td> <td width="766">To test SN terminated split bearer functionality</td> </tr> <tr> <td rowspan="3" width="302">LTE/NR DC mobility management</td> <td width="473">SN Addition</td> <td width="766">To test SgNB addition functionality</td> </tr> <tr> <td width="473">SN Re-configuration</td> <td width="766">To test SgNB re-configuration functionality</td> </tr> <tr> <td width="473">LTE/NR DC Handover</td> <td width="766">To test LTE/NR DC handover functionality</td> </tr> <tr> <td rowspan="2" width="302">Data split algorithm</td> <td width="473">DL Data Split Algorithm</td> <td width="766">To test DL data split algorithm</td> </tr> <tr> <td width="473">UL Data Split Algorithm</td> <td width="766">To test UL data split algorithm</td> </tr> <tr> <td rowspan="4" width="302">Performance</td> <td width="473">Single UE DL Throughput</td> <td width="766">To test single UE DL throughput</td> </tr> <tr> <td width="473">Single UE UL Throughput</td> <td width="766">To test single UE UL throughput</td> </tr> <tr> <td width="473">Cell DL Peak Throughput</td> <td width="766">To test cell DL throughput</td> </tr> <tr> <td width="473">Cell UL Peak Throughput</td> <td width="766">To test cell UL throughput</td> </tr> <tr> <td rowspan="2" width="302">Latency</td> <td width="473">Control Plane Latency</td> <td width="766">To test control plane latency</td> </tr> <tr> <td width="473">User Plane Latency</td> <td width="766">To test user plane latency</td> </tr> <tr> <td rowspan="3" width="302">Massive MIMO</td> <td width="473">SU-MIMO DL</td> <td width="766">To test SU-MIMO DL functionality (2 steams)</td> </tr> <tr> <td width="473">MU-MIMO DL</td> <td width="766">To test MU-MIMO DL functionality (16/24 steams)</td> </tr> <tr> <td width="473">MU-MIMO UL</td> <td width="766">To test MU-MIMO UL functionality (8/16 steams)</td> </tr> </tbody> </table> <p data-hash="jtyhyumnuu4epox5vlf" data-wiki-id="1445e50aaeb216b7">&nbsp;</p> <h2 id="0a444a63cec7bced92e13f5f3b599f26">2.12 Features</h2> <p data-wiki-id="1455e50aaeb216b8">NSA Option 3 5G networks provide the features as described in Table 7.</p> <p style="text-align: center;" data-wiki-id="1465e50aaeb216ba">Table 7: Features supported by NSA Deployments (Option 3)</p> <table> <tbody> <tr> <td width="84">Content</td> <td width="230">Item</td> </tr> <tr> <td width="84">NSA Network Architectures</td> <td width="230">Option3/3a/3x</td> </tr> <tr> <td rowspan="5" width="84">Connection Management</td> <td width="230">System Information Broadcasting</td> </tr> <tr> <td width="230">Synchronization</td> </tr> <tr> <td width="230">Random Access Procedure</td> </tr> <tr> <td width="230">Radio Access Bearer Management</td> </tr> <tr> <td width="230">Interface Management (S1-U/X2/Xn/F1)</td> </tr> <tr> <td rowspan="5" width="84">Mobility Management</td> <td width="230">SN Change Procedure in NSA</td> </tr> <tr> <td width="230">Intra-MN Hand Over without SN Change in NSA</td> </tr> <tr> <td width="230">Intra-MN Hand Over with SN Add/Release/Change in NSA</td> </tr> <tr> <td width="230">Inter-MN Hand Over without SN Change in NSA</td> </tr> <tr> <td width="230">Inter-MN Hand Over with SN Add/Release/Change in NSA</td> </tr> <tr> <td rowspan="3" width="84">Radio Resource Management</td> <td width="230">Radio Admission Control</td> </tr> <tr> <td width="230">Congestion Control</td> </tr> <tr> <td width="230">Load Control</td> </tr> <tr> <td rowspan="3" width="84">QoS Management</td> <td width="230">MBR/AMBR</td> </tr> <tr> <td width="230">MBR for non-GBR services</td> </tr> <tr> <td width="230">Legacy Standard QCI</td> </tr> <tr> <td rowspan="4" width="84">User Plane Process</td> <td width="230">MAC PDU and Functions</td> </tr> <tr> <td width="230">RLC PDU and Functions</td> </tr> <tr> <td width="230">PDCP PDU and Functions</td> </tr> <tr> <td width="230">Robust Header Compression (RoHC)</td> </tr> <tr> <td rowspan="3" width="84">RAN Split and Cloud RAN</td> <td width="230">eCPRI</td> </tr> <tr> <td width="230">Integrated Management and Control</td> </tr> <tr> <td width="230">Network Function Virtualization</td> </tr> <tr> <td rowspan="9" width="84">Radio Part</td> <td width="230">Basic Physical Layer Support</td> </tr> <tr> <td width="230">SC-OFDM</td> </tr> <tr> <td width="230">Basic Modulation Schemes (BPSK/QPSK/16QAM/64QAM/256QAM)</td> </tr> <tr> <td width="230">Subcarrier Spacing(15/30/60/120KHz)</td> </tr> <tr> <td width="230">PRACH with Long/Short Sequence</td> </tr> <tr> <td width="230">Long PUCCH/Short PUCCH</td> </tr> <tr> <td width="230">Slot Format Configuration</td> </tr> <tr> <td width="230">Dynamic Scheduling</td> </tr> <tr> <td width="230">UL/DL HARQ</td> </tr> </tbody> </table> <p data-wiki-id="1475e50aaeb216bb">&nbsp;</p> <h2 id="6fb92cd1e59b0cebe54c76cd91010097">2.13 Migration to virtualized network/Network Transformation</h2> <p data-wiki-id="1485e50aaeb216bc">5G core networks will be designed with the assumption that the network will be fully virtualized and cloud native. In addition, 3GPP has standardized CUPS technology that decouples control and user plane of the 4G core network. This means that the operators would need to consider stable migration from their legacy 4G network consisting of proprietary equipment to a virtualized network.</p> <p data-wiki-id="1495e50aaeb216be">In addition to transitioning to the new paradigm of core networks in 5G, virtualized networks possess promising advantages in terms of costs, time to market and fostering service innovation. Before adopting fully virtualized network of 5G core network, operators can familiarize themselves with the new paradigm by migrating their legacy 4G networks to a virtual one. However, the migration to virtual network is not free from hurdles and needs careful considerations.</p> <p data-wiki-id="1505e50aaeb216bf">GSMA Future Networks Programme conducted <a href="https://www.gsma.com/futurenetworks/5g/migration-from-physical-to-virtual-network-functions-best-practices-and-lessons-learned/">case studies of leading operators that have virtualized their 4G core networks and IMS (IP Multimedia Subsystem)</a> [12]. These leading operators all point out that there are many challenges and risks in migrating a legacy network to a fully virtualized network. First, ensuring carrier grade SLA (Service Level Agreement) on IT platform is a great challenge, for example five 9s availability. This also leads to potential lock-in to specific IT vendors as only few vendors would be able to provide telco-grade solutions. There is also challenge in enlarged base of stakeholders and resulting integration of products. Finally, the cost can increase if VNF (Virtual Network Function) and VI (Virtualized Infrastructure) managers are proprietary.</p> <p data-wiki-id="1515e50aaeb216c0">Fortunately, the experience of the operators can help other mobile operators in the migration journey to fully virtualized network. In initial stages of virtualisation, single vendor approach may have advantages as it avoids complicated troubleshooting and cross layer fault detection. Such integration savings can also be realised lowering the Total Cost of Ownership. Second, an end-to-end design of the network can help achieve the telco-grade quality as industry standards for virtualised components are generally below telco-grade and hence end-to-end approach helps to overcome it. Third, the operator organisation needs to reflect the shift in operations and management paradigm associated with virtualized network, as the current organization fit for legacy operations and management would not be appropriate. In relation to this point, operators may benefit from becoming integrators of the equipment used in their networks and train staff accordingly, as virtualized network is analogous to an integrated system for specific purposes.</p> <p data-wiki-id="1525e50aaeb216c1">&nbsp;</p> <h2 id="f1c45801ad6df8a69eea31139cdb541a">2.14 Roaming</h2> <p data-wiki-id="1535e50aaeb216c2">5G NSA Option 3 will not introduce any changes to the existing roaming architecture and procedures. It is up to the VPLMN operator to allow inbound roamers to use 5GS NSA Option 3 or to only allow SA/LTE (Option 1).</p> <p style="text-align: center;" data-wiki-id="1545e50aaeb216c3">Figure 18: Roaming architecture</p> <p data-wiki-id="1555e50aaeb216c7"><img class="alignnone wp-image-19030 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-20.png" alt="" width="737" height="523" /></p> <p data-wiki-id="1565e50aaeb216c8">&nbsp;</p> <h2 id="9e5ea0dcd3016b3e59e209ac5aaa4f37">2.15 Services (IMS – Voice)</h2> <p data-wiki-id="1575e50aaeb216c9">One of the important aspects of migration to 5G is the support of voice and related services (e.g. SMS, conversational video). In what follows, however, the focus will be on IMS based services for voice via 3GPP based 5G access network. Non-IMS based voice is out of scope here. Note that the reasoning for IMS based voice (“VoIMS”) can apply for IMS based SMS (“SMSoIP”) and IMS based conversational video (“VioIMS”). VoIMS refers here to the generic IMS based voice solution; it includes the support of IMS based Emergency Services. VoIMS support over WLAN (“VoWiFi”) and its interworking with VoIMS over 5G access is also out of scope.</p> <p data-wiki-id="1585e50aaeb216cb">The initial configuration corresponds to the use of VoIMS over LTE / EPC (“VoLTE” per IR.92 [1]). It refers to the usage over legacy LTE system (EPS) - so called 3GPP architectural SA/LTE (“Option 1”) - which can also be used by NSA/EN-DC (“Option 3”) (see Figure 19).</p> <h3>2.15.1 Roaming with VoIMS</h3> <p data-wiki-id="1595e50aaeb216cc">Roaming support for VoIMS is is an important feature and is essentially based on IMS Roaming in a 4G or 5G environment.  The principle of IMS and in particular VoIMS roaming in a 4G environment has been defined in IR.65 [3].</p> <p data-wiki-id="1605e50aaeb216cd">The Home Routed solution is usually the path for data / Internet roaming (e.g. for 3G and 4G) but has been used in 4G for (Vo)IMS roaming because it offers a quicker and easier deployment solution independent of the VPMN despite some constraints and additional standardisation effort that was required (e.g. for Lawful Interception).</p> <p data-wiki-id="1615e50aaeb216dc">Figure 19: Potential VoIMS variants according to SA / NSA architectural options</p> <p data-wiki-id="1625e50aaeb216dd"><img class="alignnone wp-image-19031 size-full" src="https://www.gsma.com/futurenetworks/wp-content/uploads/2019/03/Figure-21.png" alt="" width="780" height="643" /></p> <h2 id="48d2712012dd773f349bf8b9996d3522">2.16 Outlook</h2> <p data-wiki-id="1635e50aaeb216df">The document will be open for contributions/suggestions and will keep evolving to provide support for more deployment options and considerations. Currently, the following topics are planned for further development.</p> <ul> <li style="list-style-type: none;"> <ul> <li>Use cases beyond mobile broadband: IoT, URLLC</li> <li>Support for other deployment options (SA Options 2/5, NSA Options 4/5/7)</li> <li>Migration to other deployment options</li> <li>IMS service support in other deployment options</li> <li>VoIMS continuity under 4G and 5G</li> <li>Support of SMS</li> </ul> </li> </ul> <ul> <li>Non-IMS based services</li> <li>4G/5G interworking</li> <li>Further details on E-UTRAN upgrade to support EN-DC: impact on E-UTRAN, enhanced dual connectivity, new QCI values, etc.</li> <li>Regulatory requirement</li> <li>Roaming in 5G networks</li> </ul> <p data-wiki-id="1645e50aaeb216e0">Please contact <a href="mailto:futurenetworks@gsma.com">futurenetworks@gsma.com</a> if you would like to contribute or suggest topic to be covered by this document.</p> <p data-wiki-id="1655e50aaeb216e1">&nbsp;</p> <h3>Abbreviations</h3> <table> <thead> <tr> <td width="206"><strong>Term</strong></td> <td width="1297"><strong>Description</strong></td> </tr> </thead> <tbody> <tr> <td width="206">2D</td> <td width="1297">2 Dimensions</td> </tr> <tr> <td width="206">3D</td> <td width="1297">3 Dimensions</td> </tr> <tr> <td width="206">3GPP</td> <td width="1297">3<sup>rd</sup> Generation Partnership Project</td> </tr> <tr> <td width="206">5GC</td> <td width="1297">5G Core</td> </tr> <tr> <td width="206">AMBR</td> <td width="1297">Aggregate Maximum Bit Rate</td> </tr> <tr> <td width="206">AMF</td> <td width="1297">Access and Mobility Management Function</td> </tr> <tr> <td width="206">AN</td> <td width="1297">Access Network</td> </tr> <tr> <td width="206">APN</td> <td width="1297">Access Point Name</td> </tr> <tr> <td width="206">AR</td> <td width="1297">Augmented Reality</td> </tr> <tr> <td width="206">ARD</td> <td width="1297">Access Restriction Data</td> </tr> <tr> <td width="206">AVP</td> <td width="1297">Attribute-Value pairs</td> </tr> <tr> <td width="206">BEREC</td> <td width="1297">The Body of European Regulators for Electronic Communications</td> </tr> <tr> <td width="206">BPSK</td> <td width="1297">Binary Phase Shift Keying</td> </tr> <tr> <td width="206">BW</td> <td width="1297">Bandwidth</td> </tr> <tr> <td width="206">CA</td> <td width="1297">Carrier Aggregation</td> </tr> <tr> <td width="206">CC</td> <td width="1297">Component Carrier</td> </tr> <tr> <td width="206">CDR</td> <td width="1297">Charging Data Record</td> </tr> <tr> <td width="206">COTS</td> <td width="1297">Commercial Off The Shelf</td> </tr> <tr> <td width="206">CRS</td> <td width="1297">Cell-specific Reference Signal</td> </tr> <tr> <td width="206">CU</td> <td width="1297">Centralized Unit</td> </tr> <tr> <td width="206">CUPS</td> <td width="1297">Control and User Plane Separation</td> </tr> <tr> <td width="206">DC</td> <td width="1297">Dual Connectivity</td> </tr> <tr> <td width="206">DCNR</td> <td width="1297">Dual Connectivity with NR</td> </tr> <tr> <td width="206">DL</td> <td width="1297">Downlink</td> </tr> <tr> <td width="206">DNS</td> <td width="1297">Domain Name System</td> </tr> <tr> <td width="206">DSL</td> <td width="1297">Digital Subscriber Line</td> </tr> <tr> <td width="206">DU</td> <td width="1297">Distributed Unit</td> </tr> <tr> <td width="206">eCPRI</td> <td width="1297">Enhanced Common Public Radio Interface</td> </tr> <tr> <td width="206">eLTE</td> <td width="1297">Enhanced LTE</td> </tr> <tr> <td width="206">eMBB</td> <td width="1297">Enhanced Mobile Broadband</td> </tr> <tr> <td width="206">eNB</td> <td width="1297">eNode B</td> </tr> <tr> <td width="206">EN-DC</td> <td width="1297">E-UTRAN New Radio – Dual Connectivity</td> </tr> <tr> <td width="206">EPC</td> <td width="1297">Evolved Packet Core</td> </tr> <tr> <td width="206">EPS</td> <td width="1297">Evolved Packet System</td> </tr> <tr> <td width="206">eSRVCC</td> <td width="1297">enhanced Single Radio Voice Call Continuity</td> </tr> <tr> <td width="206">E-UTRAN</td> <td width="1297">Evolved-Universal Terrestrial Radio Access</td> </tr> <tr> <td width="206">FQDN</td> <td width="1297">Fully Qualified Domain Name</td> </tr> <tr> <td width="206">FTTX</td> <td width="1297">Fiber To The X</td> </tr> <tr> <td width="206">FWA</td> <td width="1297">Fixed Wireless Access</td> </tr> <tr> <td width="206">GBR</td> <td width="1297">Guaranteed Bit Rate</td> </tr> <tr> <td width="206">gNB</td> <td width="1297">gNode B</td> </tr> <tr> <td width="206">GW</td> <td width="1297">Gateway</td> </tr> <tr> <td width="206">HARQ</td> <td width="1297">Hybrid Automatic Repeat Request</td> </tr> <tr> <td width="206">HE</td> <td width="1297">Home Environment</td> </tr> <tr> <td width="206">HPLMN</td> <td width="1297">Home Public Land Mobile Network</td> </tr> <tr> <td width="206">HSS</td> <td width="1297">Home Subscriber Server</td> </tr> <tr> <td width="206">IMS</td> <td width="1297">IP Multimedia Subsystem</td> </tr> <tr> <td width="206">IMT-2020</td> <td width="1297">International Mobile Telecommunication system with a target date set for 2020</td> </tr> <tr> <td width="206">IP</td> <td width="1297">Internet Protocol</td> </tr> <tr> <td width="206">IT</td> <td width="1297">Information Technology</td> </tr> <tr> <td width="206">ITU-R</td> <td width="1297">International Telecommunication Union Radiocommunication Sector</td> </tr> <tr> <td width="206">LTE</td> <td width="1297">Long Term Evolution&lt;&nbsp;</p> <p data-wiki-id="1665e50aaeb216e2">&nbsp;</p> <p data-wiki-id="1675e50aaeb216e4">&nbsp;</td> </tr> </tbody> </table>

Edit article

Send article

Welcome to the GSMA Future Networks Online Document Hub