Showing posts with label Ericsson. Show all posts
Showing posts with label Ericsson. Show all posts

Monday, 15 July 2024

Disaggregation of 5G Core (5GC) Network

When talking about mobile networks, we generally talk about disaggregation and virtualization of the RAN rather than the core. The 5G Core Network was also designed with disaggregation in mind, supporting service-based architecture (SBA) where Network Functions (NFs) are modular and can be deployed as microservices.

The 5G Core (5GC) is the foundation for Standalone 5G (5G SA) networks where the end users can experience the power of 'real' 5G. A newly published forecast report by Dell’Oro Group pointed out that the Mobile Core Network (MCN) market 5-year cumulative revenue forecast is expected to decline 10 percent (2024-2028). The reduction in the forecast is caused by severe economic headwinds, primarily the high inflation rates, and the slow adoption of 5G SA networks by Mobile Network Operators (MNOs).

While most people think of 5G Core Network as a single entity, in reality it contains many different network functions that can be supplied by different vendors. One way to select the vendors is based on grouping of NFs based on functionality as shown in the picture above. Here we have categorised them into User Plane & Mobility, Subscriber Data Management, Routing & Selection, and Policy & Charging. 

An example of of this disaggregation can be seen in the image above where Telenor worked with partners to build a truly multi-vendor, 5G core environment running on a vendor-neutral platform. According to their announcement

“The main component of 5G-SA is the 5G mobile core, the ‘brain’ of the 5G system. Unfortunately, most 5G core deployments are still single vendor dependent, with strong dependencies on that vendor’s underlying proprietary architecture. This single-vendor dependency can be a killer for innovation. It restricts open collaboration from the broader 5G ecosystem of companies developing new technology, use cases, and services that the market expects,” explains Patrick Waldemar, Vice President and Head of Technology in Telenor Research.

As an industry first, Telenor, along with partners, have established to build a truly multi-vendor, 5G core environment running on a vendor-neutral platform. The multi-vendor environment consists of best of breed Network Functions from Oracle, Casa-Systems, Enea and Kaloom, all running on Red Hat Openshift, the industry’s leading enterprise Kubernetes platform.

“To protect the 5G infrastructure from cyber threats, we deployed Palo Alto Networks Prisma Cloud Compute, and their Next Generation Firewall is also securing Internet connectivity for mobile devices. Red Hat Ansible Automation Platform is being used as a scalable automation system, while Emblasoft is providing automated network testing capabilities. The 5G New Radio (NR) is from Huawei,” says Waldemar.

In their whitepaper on "How to build the best 5G core", Oracle does a very similar grouping of the NFs like the way I have shown at the top and highlights what they supply and which partner NFs they use.

When the mobile operator Orange announced the selection of suppliers for their 5G SA networks in Europe, the press release said the following:

Orange has chosen the following industrial partners:

  • Ericsson’s 5G SA core network for Belgium, Spain, Luxembourg and Poland
  • Nokia’s 5G SA core network for France and Slovakia 
  • Nokia’s Subscriber Data Management for all countries
  • Oracle Communications for 5G core signaling and routing in all countries

I was unable to find out exactly which NFs would be supplied by which vendor but you get an idea.

Finally, I have depicted four scenarios for deployment and which Cloud Native Environment (CNE) would be used. In a single vendor core, the CNE, even though from a third party, could belong to either the vendor themselves (scenario 1) or may be suggested by the operator (scenario 2). 

In case of a multi-vendor deployment, it is very likely that each vendor would use their own CNE (scenario 4) rather than one suggested by the operator or belonging to the lead vendor (scenario 3).

If you have been involved in trial/test/deployment of a multi-vendor 5G Core, would love to hear your feedback on that as well as this post.

Related Posts

Wednesday, 10 August 2022

AI/ML Enhancements in 5G-Advanced for Intelligent Network Automation

Artificial Intelligence (AI) and Machine Learning (ML) has been touted to automate the network and simplify the identification and debug of issues that will arise with increasing network complexity. For this reason 3GPP has many different features that are already present in Release-17 but are expected to evolve further in Release-18. 

I have already covered some of this topics in earlier posts. Ericsson's recent whitepaper '5G Advanced: Evolution towards 6G' also has a good summary on this topic. Here is an extract from that:

Intelligent network automation

With increasing complexity in network design, for example, many different deployment and usage options, conventional approaches will not be able to provide swift solutions in many cases. It is well understood that manually reconfiguring cellular communications systems could be inefficient and costly.

Artificial intelligence (AI) and machine learning (ML) have the capability to solve complex and unstructured network problems by using a large amount of data collected from wireless networks. Thus, there has been a lot of attention lately on utilizing AI/ML-based solutions to improve network performance and hence providing avenues for inserting intelligence in network operations.

AI model design, optimization, and life-cycle management rely heavily on data. A wireless network can collect a large amount of data as part of its normal operations. This provides a good base for designing intelligent network solutions. 5G Advanced addresses how to optimize the standardized interfaces for data collection while leaving the automation functionality, for example, training and inference up to the proprietary implementation to support full flexibility in the automation of the network.

AI/ML for RAN enhancements

Three use cases have been identified in the Release 17 study item related to RAN performance enhancement by using AI/ML techniques. Selected use cases from the Release 17 technical report will be taken into the normative phase in the next releases. The selected use cases are: 1) network energy saving; 2) load balancing; and 3) mobility optimization.

The selected use cases can be supported by enhancements to current NR interfaces, targeting performance improvements using AI/ML functionality in the RAN while maintaining the 5G NR architecture. One of the goals is to ensure vendor incentives in terms of innovation and competitiveness by keeping the AI model implementation specific. As shown in Fig.2 (on the top) an intent-based management approach can be adopted for use cases involving RAN-OAM interactions. The intent will be received by the RAN. The RAN will need to understand the intent and trigger certain functionalities as a result.

AI/ML for physical layer enhancements

It is generally expected that AI/ML functionality can be used to improve the radio performance and/or reduced the complexity/overhead of the radio interface. 3GPP TSG RAN has selected three use cases to study the potential air interface performance improvements through AI/ML techniques, such as beam management, channel state information feedback enhancement, and positioning accuracy enhancements for different scenarios. The AI/ML-based methods may provide benefits compared to traditional methods in the radio interface. The challenge will be to define a unified AI/ML framework for the air interface by adequate AI/ML model characterization using various levels of collaboration between gNB and UE.

AI/ML in 5G core

5G Advanced will provide further enhancements of the architecture for analytics and on ML model life-cycle management, for example, to improve correctness of the models. The advancements in the architecture for analytics and data collection serve as a good foundation for AI/ML-based use cases within the different network functions (NFs). Additional use cases will be studied where NFs make use of analytics with the target to support in their decision making, for example, network data analytics functions (NWDAF)- assisted generation of UE policy for network slicing.

If you are interested in studying this topic further, check out 3GPP TR 37.817: Study on enhancement for data collection for NR and ENDC. Download the latest version from here.

Related Posts

Tuesday, 22 March 2022

Realizing Zero Trust Architecture for 5G Networks

Over the last couple of years, I keep on coming across Zero-Trust Architecture (ZTA). A simple way to explain is that the standard model of security is known as perimeter security model, where everything within the perimeter can be trusted. In zero-trust (ZT) model, no assumptions is made about trustworthiness and hence it is also sometimes known as perimeterless security model.

This short video from IBM clearly explains what ZT means:

This blog post from Palo Alto Networks also clearly explains ZT:

By definition, Zero Trust is a strategic approach to cybersecurity that secures an organization by eliminating implicit trust and continuously validating every stage of a digital interaction. Zero Trust for 5G removes implicit trust regardless of what the situation is, who the user is, where the user is or what application they are trying to access.

The impact of Zero Trust on network security specifically protects the security of sensitive data and critical applications by leveraging network segmentation, preventing lateral movement, providing Layer 7 threat prevention and simplifying granular user-access controls. Where traditional security models operate under the assumption that everything inside an organization’s perimeter can be trusted, the Zero Trust model recognizes that trust is a vulnerability.

In short, Zero Trust for 5G presents an opportunity for service providers, enterprises and organizations to re-think how users, applications and infrastructure are secured in a way that is scalable and sustainable for modern cloud, SDN-based environments and open-sourced 5G networks. Delivering the Zero Trust Enterprise means taking Zero Trust principles, making them actionable and effectively rebuilding security to keep pace with digital transformation. 

A research paper looking at Intelligent ZTA (i-ZTA) provides an interesting approach to security in 5G and beyond. The paper can be downloaded from here. The abstract states:

While network virtualization, software-defined networking (SDN), and service-based architectures (SBA) are key enablers of 5G networks, operating in an untrusted environment has also become a key feature of the networks. Further, seamless connectivity to a high volume of devices in multi-radio access technology (RAT) has broadened the attack surface on information infrastructure. Network assurance in a dynamic untrusted environment calls for revolutionary architectures beyond existing static security frameworks. This paper presents the architectural design of an i-ZTA upon which modern artificial intelligence (AI) algorithms can be developed to provide information security in untrusted networks. We introduce key ZT principles as real-time Monitoring of the security state of network assets, Evaluating the risk of individual access requests, and Deciding on access authorization using a dynamic trust algorithm, called MED components. The envisioned architecture adopts an SBA-based design, similar to the 3GPP specification of 5G networks, by leveraging the open radio access network (O-RAN) architecture with appropriate real-time engines and network interfaces for collecting necessary machine learning data. The i-ZTA is also expected to exploit the multi-access edge computing (MEC) technology of 5G as a key enabler of intelligent MED components for resource-constraint devices.

Ericsson Technology Review covered Zero Trust in 5G Networks in one of their issues. Quoting from the article:

The 3GPP 5G standards define relevant network security features supporting a zero trust approach in the three domains: network access security, network domain security and service-based architecture (SBA) domain security. 

The network access security features provide users with secure access to services through the device (mobile phone or connected IoT device) and protect against attacks on the air interface between the device and the radio node. Network domain security includes features that enable nodes to securely exchange signaling data and user data, for example, between radio and core network functions (NFs).

The 5G SBA is built on web technology and web protocols to enable flexible and scalable deployments using virtualization and container technologies and cloud-based processing platforms. SBA domain security specifies the mechanism for secure communication between NFs within the serving network domain and with other network domains. 

While the new requirements and functionality introduced in the 5G specifications are already aligned with many of the zero trust tenets. It is already evident, however, that further technology development, standardization and implementation are needed in areas such as policy frameworks, security monitoring and trust evaluation to support the adoption of zero trust architecture in new telecom environments that are distributed, open, multi-vendor and/or virtualized.

While various technologies can support organizations in adhering to the guiding principles of zero trust as part of their total active defense strategy, it is important to remember that technology alone will never be sufficient to realize the full potential of zero trust. Successful implementation of a network based on zero trust principles requires the concurrent implementation of information security processes, policies and best practices, as well as the presence of knowledgeable security staff. Regardless of where a CSP is in its transition toward a zero trust architecture, the three pillars of people, processes and technology will continue to be the foundation of a robust security architecture.

Related Posts:

Tuesday, 25 January 2022

3GPP Release-18 Work Moves Into Focus as Release-17 Reaches Maturity

In early December 2021, 3GPP reached a consensus on the scope of 5G NR Release-18. With the 3GPP Rel-17 functional freeze set for March 2022, Release-18 work is moving into focus. This is being billed as a significant milestone marking the beginning of 5G Advanced — the second wave of wireless innovations that will fulfil the 5G vision. Release 18 is expected to build on the solid foundation set by 3GPP Releases 15, 16, and 17, and it sets the longer-term evolution direction of 5G and beyond.

(click on the image to enlarge - PDF here)

The 3GPP Release-18 page has a concise summary of all that you need to know, including the timeline. For anyone interested in going through features one-by-one, start navigating from here, select Rel-18 from the top.

For others who may be more interested in summary rather than a lot of details, here are some good links to navigate:

  • Nokia whitepaper - 5G-Advanced: Expanding 5G for the connected world (link)
  • Paper by Ericsson researcher, Xingqin Lin, 'An Overview of 5G Advanced Evolution in 3GPP Release 18' (link)
  • Marcin DryjaƄski, Rimedo Labs - 3GPP Rel-18: 5G-Advanced RAN Features (link)
  • Bevin Fletcher, FierceWireless: Next 3GPP standard tees up 5G Advanced (link)

As always, Qualcomm has a fantastic summary of 5G evolution and features in 3GPP Release-18 on their page here. The image above nicely shows the evolution of 5G from Release-15 all the way to Release-18. The image below shows a summary of 3GPP Release-18, 5G-Advanced features.

They also hosted a webinar with RCR wireless. The webinar is embedded below.

The slides can be downloaded from GSA website (account required, free to register) here.

Related Posts

Tuesday, 16 November 2021

5G-Advanced Flagship Features

I am starting to get a feeling that people may be becoming overwhelmed with all the new 5G features and standards update. That is why this presentation by Mikael Höök, Director Radio Research at Ericsson, at Brooklyn 6G Summit (B6GS) caught my attention. 

The talk discusses the network infrastructure progress made in the previous two years to better illustrate the advanced 5G timeline to discovering 6G requirements. At the end of the talk, there was a quick summary of the four flagship features that are shown in the picture above. The talk is embedded below, courtesy of IEEE TV

In addition to this talk, October 2021 issue of Ericsson Technology Review covers the topic "5G evolution toward 5G advanced: An overview of 3GPP releases 17 and 18". You can get the PDF here.

I have covered the basics of these flagship features in the following posts:

Please feel free to add your thoughts as comments below.

Related Posts

Thursday, 11 November 2021

Network Slicing using User Equipment Route Selection Policy (URSP)

Google announced that its latest smartphone OS will include support for 5G network slicing. Last week Telecom TV brought this news to my attention. The article explains:

It's a move designed to leverage its expertise in devices in order to give it the edge over its rival hyperscalers.

It comes in two flavours. The first is for enterprise-owned handsets, and routes all data sent and received by a device over the network slices provided by that company's mobile operator. Android 12 gives operators the ability to manage slices using a new dynamic policy control mechanism called User Equipment Route Selection Policy (URSP). URSP enables devices to automatically switch between different network slices according to which application they are using. For example, someone working for a financial institution might require a highly-secure network slice for sending and receiving sensitive corporate data, but will then require a reliable, high-throughput, low-latency slice so they can participate in a video meeting.

The second flavour is implemented in the work profile. For years, enterprises have had the option of creating work profiles on Android devices – irrespective of whether they are owned by the organisation or the individual – to use as a separate repository for enterprise apps and data. When Android 12 comes out next year, enterprises will be able to route data to and from that repository over a network slice.

Google said it has already carried out network slicing tests with both Ericsson and Nokia using test versions of its recently released Pixel 6 smartphone running on the as-yet-unreleased Android 12 OS.

Last week Taiwanese operator Far EasTone (FET) and Ericsson announced they have completed the world’s first proof of concept (PoC) for simultaneously connecting multiple network slices per device running on Android 12 commercial release. The press release said:

The trial, carried out on FET’s 5G standalone (SA) infrastructure built on Ericsson’s radio access network and cloud-native Core network, successfully demonstrated the 5G user equipment slicing policy feature (User Equipment Route Selection Policy, or URSP) on multiple Android devices. This marks a breakthrough in network slicing capabilities on a 5G standalone network and paves the way for further ecosystem development in this important area.

With more 5G networks evolving to standalone architecture around the globe, end-to-end network slicing, which includes Ericsson RAN Slicing to secure Quality of Service (QoS) differentiation, plays a key role in enabling new services for end users, with which multiple virtual 5G networks are created on top of one physical network. The 5G trial, in collaboration with FET, Ericsson and Android, went even further in network slicing capabilities by introducing and demonstrating 5G user equipment (UE) slicing policy (URSP) features that allow devices to simultaneously operate on dynamic policy control and selection between multiple 5G network slices. This enables the steering of applications and services with specific requirements to defined slices without switching devices.

Multiple slices allow devices to have multiple profiles to secure different levels of experience, security, and privacy requirements, based on the needs of the different applications and in correspondence with the user profile.  For instance, a device can have a personal profile with private data from apps or off-work entertainment, and a work profile with enterprises productivity apps. With URSP features, employers can customize the work profile with increased security and enable better use of RAN Slicing with QoS so that enterprise-related apps can work even during network congestion.

Some security-sensitive apps, such as mobile banking, can also benefit from different routing mechanisms of the traffic enabled by URSP. For instance, the banking app would not need to send its traffic to the internet and then to the app server as it does today. Instead, it could go straight to the app server and avoid the routing through internet. With the shortest route by connecting to a defined slice, users could reduce the risk of being attacked by hackers.

In their technical whitepaper on Network Slicing, Samsung explains: 

Along with the concept of network slicing and features in the RAN and Core network, UE Route Selection Policy (URSP) is introduced as a way to manage network slice information for the UE. URSP is a network slice feature enabled by the PCF which informs the network slice status to the UE via the AMF. In 4G network systems, it was near impossible to install new services in the network for a UE. But through the URSP feature, 5G network operators can easily configure new service for a UE. Figure 12 (top of this blog post) shows the difference in network slice selection in 4G and 5G Network. In 5G network, slice selection policy can be configured dynamically through URSP, while slice selection policy is pre-defined and cannot be changed dynamically in 4G network.

URSP contains OSId, AppId, IP descriptors to define the application and Single-Network Slice Selection Assistance Information (S-NSSAI), Data Network Name (DNN), Session and Service Continuity (SSC) mode information for the application and network slice mapping.

The S-NSSAI identifies each network slice service and provides information to properly assign network slice/functions. An S-NSSAI is comprised of:

  • A Slice/Service type (SST), which refers to the expected network slice behavior in terms of features and services;
  • A Slice Differentiator (SD), which is an optional information that complements the Slice/Service type(s) to differentiate amongst multiple network slices of the same Slice/Service type.

3GPP allows the use of the Slice Differentiator (SD) field that can build customized network slices. The SD field can be used to describe services, customer information and priority.

Here is a short video from Mpirical explaining 5G UE Route Selection.

It it worth reminding here that this feature, like many of the other 5G features, is dependent on 5G Core. We hope that the transition to 5G Standalone Networks happens as soon as possible.

Related Posts:

Tuesday, 2 November 2021

Energy Consumption in Mobile Networks and RAN Power Saving Schemes

We just made a tutorial on this topic looking at where most of the power consumption in the mobile network occurs and some of the ways this power consumption can be reduced. 

The chart in the Tweet above (also in the presentation) clearly shows that the energy costs for operators run in many millions. Small power saving schemes can still have a big impact on the total energy reduction, thereby saving huge amounts of energy and costs.

The March issue of ZTE Communications Magazine contains some good articles looking at how to tackle the energy challenges in the network going forward. This recent article by Ericsson is also a good source of information on this topic.

Anyway, the slides and the video of the tutorial is embedded below:

Related Posts:

Wednesday, 20 October 2021

5G NR-Unlicensed (NR-U)

I have been talking about unlicensed LTE since 2013. With all the debate around LTE-U and LAA now non-existent, the technology has evolved with every new release. As can be seen from this picture by Ericsson above, 5G NR-U in Release-16 supports:

  • License-exempt Downlink (DL)
  • License-exempt scheduled Uplink (UL)
  • License-exempt autonomous UK
  • Standalone license-exempt operation

The Release-16 work item summary details the following deployment scenarios for NR-based access to unlicensed spectrum:

  • Scenario A: Carrier aggregation between NR in licensed spectrum (PCell) and NR in shared spectrum (SCell);
    • A.1: SCell is not configured with UL (DL only); 
    • A.2: SCell is configured with UL (DL+UL). 
  • Scenario B: Dual connectivity between LTE in licensed spectrum and NR in shared spectrum (PSCell);
  • Scenario C: NR in shared spectrum (PCell);
  • Scenario D: NR cell in shared spectrum and uplink in licensed spectrum;
  • Scenario E: Dual connectivity between NR in licensed spectrum (PCell) and NR in shared spectrum (PSCell)

5G New Radio Unlicensed: Challenges and Evaluation, available on arXiv here provides a lot of useful information on different kind of operations within the unlicensed band and the challenges of co-existence with Wi-Fi

Finally, Qualcomm has quite a few resources on this topic. Last year, they hosted a webinar on the topic, "How does unlicensed spectrum with NR-U transform what 5G can do for you?". The slides from that are available here and a video of that is available here. RCR Wireless also has this short article from one of the webinar presenters here.

Related Posts

Monday, 4 October 2021

Are there 50 Billion IoT Devices yet?

Detailed post below but if you are after a quick summary, it's in the picture above.

Couple of weeks back someone quoted that there were 50 billion devices last year (2020). After challenging them on the number, they came back to me to say that there were over 13 billion based on GSMA report. While the headline numbers are correct, there are some finer details we need to look at.

It all started back in 2010 when the then CEO of Ericsson announced that there will be 50 Billion IoT Devices by 2020. You could read all about it here and see the presentation here. While it doesn't explicitly say, it was expected that the majority of these will be based on cellular technologies. I also heard the number 500 Billion by 2030, back in 2013.

So the question is how many IoT devices are there today and how many of these are based on mobile cellular technologies?

The headline number provided by the GSMA Mobile Economy report, published just in time for MWC 2021, is 13.1 billion in 2020. It does not provide any further details on what kind of connectivity these devices use. I had to use my special search skills to find the details here.

As you can see, only 1.9 billion of these are based on cellular connections, of which 0.2 billion are based on licensed Low Power Wide Area (licensed LPWA, a.k.a. LTE-M and NB-IoT) connections. 

Ericsson Mobility Report, June 2021, has a much more detailed breakdown regarding the numbers as can be seen in the slide above. As of the end of 2020, there were 12.4 billion IoT devices, of which 10.7 billion were based on Short-range IoT. Short-range IoT is defined as a segment that largely consists of devices connected by unlicensed radio technologies, with a typical range of up to 100 meters, such as Wi-Fi, Bluetooth and Zigbee.

Wide-area IoT, which consists of segment made up of devices using cellular connections or unlicensed low-power technologies like Sigfox and LoRa had 1.7 billion devices. So, the 1.6 billion cellular IoT devices also includes LPWAN technologies like LTE-M and NB-IoT.

I also reached out to IoT experts at analyst firm Analysys Mason. As you can see in the Tweet above, Tom Rebbeck, Partner at Analysys Mason, mentioned 1.6 billion cellular (excluding NB-IoT + LTE-M) and 220 million LPWA (which includes NB-IoT, LTE-M, as well as LoRa, Sigfox etc.) IoT connections.

I also noticed this interesting chart in the tweet above which shows the growth of IoT from Dec 2010 until June 2021. Matt Hatton, Founding Partner of Transforma Insights, kindly clarified that the number as 1.55 billion including NB-IoT and LTE-M.

As you can see, the number of cellular IoT connections are nowhere near 50 billion. Even if we include all kinds of IoT connectivity, according to the most optimistic estimate by Ericsson, there will be just over 26 billion connections by 2026.

Just before concluding, it is worth highlighting that according to all these cellular IoT estimates, over 1 billion of these connections are in China. GSMA's 'The Mobile Economy China 2021' puts the number as 1.34 billion as of 2020, growing to 2.29 billion by 2025. Details on page 9 here.

Hopefully, when someone wants to talk about Internet of Thing numbers in the future, they will do a bit more research or just quote the numbers from this post here.

Related Posts

Tuesday, 27 July 2021

Introduction to 5G Reduced Capability (RedCap) Devices

Back in 2019, we wrote about Release-17 study item called NR-Lite (a.k.a. NR-Light). After the study started, it was renamed as RedCap or Reduced Capability.

We have now made a video tutorial on RedCap to not only explain what it is but also discuss some of the enhancements being discussed for 3GPP Release-18 (5G-Advanced). For anyone wanting to find out the differences between the baseline 5G devices with RedCap, without wanting to go too much in detail, can see the Tweet image for comparison.

The video and the slides of the tutorial are embedded below:

Related Posts:

Monday, 12 April 2021

Positioning in 5G networks



I have written about the 5G positioning techniques not that long back on this blog here and on connectivity technology blog here. With Release-16 now ready for deployment, Huawei has already announced world's first in 5G Indoor Positioning. Their announcement said:

China Mobile Suzhou and Huawei reached a new milestone with the verification of the 5G indoor positioning capability in metro transport scenarios in Suzhou — a major city located along the southeastern edge of Jiangsu Province in eastern China. The verification showed that, even with pRRUs being hidden, a positioning precision of 3 to 5 m can be achieved in 90% of the platform and hall areas. This is the first time that 5G indoor positioning has been verified on live networks in the world, providing valuable experience for the commercial growth of 5G positioning in vertical industries.

Indoor location-based services are in high demand of vertical applications, such as indoor navigation, asset tracking, geofencing, logistics management, and personnel management, which reflects the huge market space of indoor positioning. Currently, indoor positioning technologies are of great variety and most of them need to be deployed and maintained individually, resulting in high end-to-end costs. As a part of the continuous evolution of 5G, positioning has been added to 3GPP Release 16 finalized in mid 2020 to realize indoor positioning by leveraging the ultra-high signal resolution empowered by 5G's high bandwidth, multi-point measurements, and multi-access edge computing (MEC) deployment.

The verification was based on Huawei's 5G digital indoor solution LampSite and leading MEC solution. The LampSite units measure the radio signals of 5G devices and work with MEC to analyze the signal characteristics. Based on the results of the analysis, leading algorithms are used to precisely locate 5G devices.

We wrote about Huawei's Lampsite on Telecoms Infrastructure blog last year here.

A group of Ericsson engineers have written a research paper on 5G positioning recently. It's available on arXiv here. Here is the abstract:

In this paper we describe the recent 3GPP Release 16 specification for positioning in 5G networks. It specifies positioning signals, measurements, procedures, and architecture to meet requirements from a plethora of regulatory, commercial and industrial use cases. 5G thereby significantly extends positioning capabilities compared to what was possible with LTE. The indicative positioning performance is evaluated in agreed representative 3GPP simulation scenarios, showing a 90 percentile accuracy of a few meters down to a few decimeters depending on scenarios and assumptions.

Definitely worth a read if you like hardcore technical papers.

Related Posts:

Monday, 22 February 2021

Reducing 5G Device Power Consumption Using Connected-mode Discontinuous Reception (C-DRX)


Back in 2019, when we were still participating in physical event, I heard Sang-Hoon Park, ESVP, Head of Regional Network O&M Headquarter, KT talk about 'KT’s journey to large-scale 5G rollout' at Total Telecom Congress.

South Korea is blessed with three highly competitive MNOs and due to this, the government asked them to launch their 5G networks at the same time in 2018. I have also blogged about how KT is working on reducing the latency of their network here.

Anyway, as you can see in the picture above, using Connected-mode Discontinuous Reception (C-DRX), KT was able to show huge power saving in the 5G Samsung smartphone. They also made a video embedded below:

KT has some more details from their blog post back in 2019 here. Also some more details on RayCat here. Both the sites are in Korean but you can use Google translate to get more details.

What is KT battery saving technology (C-DRX)?

KT's'battery saving technology' is shortened to'Connected Mode Discontinuous Reception' and is called C-DRX. In simple terms, it is one of the technologies that reduces battery usage by periodically switching the communication function of a smartphone to a low power mode while data is connected.

In CDRX technology, the base station and the terminal share CDRX information through RRC setting and reconfiguration, so when there is no packet transmission/reception by the terminal, the terminal transmission/reception terminal can be turned off to reduce battery consumption, and the CDRX setting is optimized to reduce the user's battery consumption. It is possible to increase the available time for related applications.

In order to reduce the battery consumption of the terminal, it is a technology that controls the PDCCH monitoring activity, which is a downlink control channel related to the terminal identifier, through RRC. The base station controls the CDRX through RRC, and how the communication company optimizes and applies this was a big task. Is the first in Korea to optimize this technology and apply it to the national network.

In simple terms, the smartphone is not using communication, but it turns off the power completely and enters the standby state to reduce power consumption. When not in use, it completely turns off the power wasted in transmitting and receiving even during the standby time, thus extending the user's smartphone usage time.

As can be seen from the picture above, battery saving technology saves battery by completely turning off the communication function when there is no data or voice call. If the network does not have the battery saving technology applied, it is always connected to the communication network and waits even when not in use. Then, the battery is always connected to the communication function and the battery saving technology overcomes this part.

When Qualcomm announced their Industry’s First Mobile Platform with Integrated 5G back in 2019, the press release said:

The new integrated Snapdragon 5G mobile platform features Qualcomm® 5G PowerSave technology to enable smartphones with the battery life users expect today. Qualcomm 5G PowerSave builds on connected-mode discontinuous reception (C-DRX, a feature in 3GPP specifications) along with additional techniques from Qualcomm Technologies to enhance battery life in 5G mobile devices – making it comparable to that of Gigabit LTE devices today. Qualcomm 5G PowerSave is also supported in the Snapdragon X50 and X55 5G modems, which are expected to power the first waves of 5G mobile devices introduced this year.

The picture is from the slide deck here. See links in further reading below to learn more about this feature.

Further Reading:

  • All about Wired and Wireless Technology: LTE Connected Mode DRX (link)
  • Netmanias: Future LTE Designed by SK Telecom: ​(2) Application of C-DRX, July 2017 (link)
  • Ericsson: A technical look at 5G mobile device energy efficiency, Feb 2020 (link)
  • ZTE via IEEE Access: Power Saving Techniques for 5G and Beyond, July 2020 (link)

Related Posts:

Monday, 22 June 2020

Carrier Aggregation (CA) and Dual Connectivity (DC)


This topic keeps coming up every few months with either someone asking me for clarifications or someone asking us to make a video. While I don't think I will mange to get round to making a video sometime soon, there are some excellent resources available that should help a new starter. Here they are in an order I think works best



The first resource that I think also works best is this webinar / training from Award Solutions. It covers this topic well and the image at the top of the post is a god summary for someone who already understands the technology.


It may also help to understand that in the 5G NSA can have 4G carrier aggregation as well as 5G carrier aggregation in addition to dual connectivity.


If you saw the video earlier, you noticed that DC actually came as part of LTE in Release-12. We covered it in our Telecom Infrastructure blog here. NTT Docomo Technical journal had a detailed article on 'Carrier Aggregation Enhancement and Dual Connectivity Promising Higher Throughput and Capacity' that covered DC in a lot more technical detail, albeit from LTE point of view only. The article is available here. A WWRF whitepaper from the same era can also provide more details on LTE Small Cell Enhancement by Dual Connectivity. An archived copy of the paper is available here.

Another fantastic resource is this presentation by Rapeepat Ratasuk and Amitava Ghosh from Mobile Radio Research Lab, Nokia Bell Labs. The presentation is available here and details the MCG (Master Cell Group) Split Bearer and SCG (Secondary Cell Group) Split Bearer, etc. This article from Ericsson also provides more detail on this topic while ShareTechNote takes it one level even deeper with technical details and signalling here and here.

So hopefully this is a good detailed starting point on this topic, until we manage to make a simple video someday.