Showing posts with label Technical Details. Show all posts
Showing posts with label Technical Details. Show all posts

Wednesday, 24 January 2024

UE Assistance Information in LTE and 5G

I have been asked about the UE Assistance Information (UAI) RRC message a few times before. Generally I have always pointed people back to the LTE/5G specifications but here is a concise video that the telecoms technology training company Mpirical have shared recently:

If you want to dig further into details then please see the RRC specifications: 36.331 for LTE and 38.331 for 5G. 

Over the years I have added quite a few short tutorials from Mpirical on this blog, do check them out below.

Related Posts

Tuesday, 17 January 2023

Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS)

3GPP Release 17 introduced a new feature called AKMA (Authentication and Key Management for Applications), the goal of which is to enable the authentication and generation of application keys based on 3GPP credentials for all UE types in the 5G System, especially IoT devices, ensuring to bootstrap the security between the UE and the applications in the 5G system.

3GPP TR 21.917 has an excellent summary as follows:

Authentication and key management for applications based on 3GPP credential in 5G (AKMA) is a cellular-network-based delegated authentication system specified for the 5G system, helping establish a secure tunnel between the end user and the application server. Using AKMA, a user can log in to an application service only based on the 3GPP credential which is the permanent key stored in the user’s tamper-resistant smart card UICC. The application service provider can also delegate the task of user authentication to the mobile network operator by using AKMA. 

The AKMA architecture and procedures are specified by SA3 in TS 33.535, with the related study showing how its general principles are derived documented in TR 33.835. The AKMA feature introduces a new Network Function into the 5G system, which is the AKMA Anchor Function (AAnF). Its detailed services and API definitions are specified by CT3 in TS 29.535. Earlier generations of cellular networks include two similar standards specified by SA3, which are generic bootstrapping architecture (GBA) and battery-efficient security for very low throughput machine type communication devices (BEST). Since the AKMA feature is deemed as a successor of these systems, the work is launched by SA3 without the involvement of stage 1.

In the latest issue of 3GPP Highlights Magazine, Suresh Nair, 3GPP Working Group SA3 Chair, Saurabh Khare & Jing Ping (Nokia) has explained the AKMA procedure. The article is also available on 3GPP website here. The article lists the following as AKMA advantages:

  • Since the AKMA framework uses authentication and authorization of the UE leveraging the PLMN credentials stored on the USIM, this becomes as strong as the network primary authentication and subsequent keys derived further to UE and Application Function (AF) interface.
  • The Application Functions can leverage the authentication service provided by the AKMA Anchor Function (AAnF) without additional CAPEX and OPEX.
  • The architecture provides a direct interface between the UE and the AF where a customized application-specific interface can be built, including the key management, key lifetime extension, etc.

The Journal of ICT Standardization has a paper on Authentication Mechanisms in the 5G System. It details AKMA and much more. It's a great place to start for anyone new looking to understand different 5G Authentication Mechanisms. 

Related Posts

Thursday, 29 September 2022

Four Ways 5G Can Improve the Battery Life of User Equipment (UE)

We have looked at different approaches in this blog and the 3G4G website on reducing the power consumption (see related posts below). In a blog post some months back, Huawei highlighted how 5G can improve the battery life of UE. The blog post mentioned four approaches, we have looked at three of them on various blogs. 

The following is from the blog post:

RRC_INACTIVE State

A UE can access network services only if it establishes a radio resource control (RRC) connection with the base station. In legacy RATs, a UE is either in the RRC_CONNECTED state (it has an RRC connection) or the RRC_IDLE state (it does not have an RRC connection). However, transitioning from the RRC_IDLE state to the RRC_CONNECTED state takes a long time, so it cannot meet the low latency requirement of some 5G services. But a UE cannot just stay in the RRC_CONNECTED state because this will consume much more UE power.

To solve this problem, 5G introduces the RRC_INACTIVE state, where the RRC connection is released but the UE context is retained (called RRC Release with Suspend), so an RRC connection can be quickly resumed when needed. This way, a UE in the RRC_INACTIVE state can access low-latency services whenever needed but consume the same amount of power as it does in the RRC_IDLE state.

DRX + WUS

Discontinuous reception (DRX) enables a UE in the RRC_CONNECTED state to periodically, instead of constantly, monitor the physical downlink control channel (PDCCH) to save power. To meet the requirements of different UE services, both short and long DRX cycles can be configured for a UE. However, when to wake up is determined by the predefined cycle, so the UE might wake up unnecessarily when there is no data scheduled.

Is there a way for a UE to wake up only when it needs to? Wake-up Signal (WUS) proposed in Release 16 is the answer. This signal can be sent before the next On Duration period (during which the UE monitors the PDCCH) so that the UE wakes up only when it receives this signal from the network. Because the length of a WUS is shorter than the On Duration Timer, using WUS to wake up a UE saves more power than using only DRX.

BWP Adaptation

In theory, working on a larger bandwidth consumes more UE power. 5G provides large bandwidths, but it is unnecessary for a UE to always work on large bandwidth. For example, if you play online mobile games on a UE, only 10 MHz of bandwidth is needed for 87% of the data transmission time. As such, Bandwidth Part (BWP) is proposed in 5G to enable UEs to work on narrower bandwidths without sacrificing user experience.

BWP adaptation enables the base station to dynamically switch between BWPs based on the UE’s traffic volume. When the traffic volume is large, a UE can work on a wide BWP, and when the traffic volume is small, the UE can work on a narrow one. BWP switching can be performed based on the downlink control information (DCI) and RRC reconfiguration messages. This ensures that a UE always works on a bandwidth that supports the traffic volume but does not consume too much power.

Maximum MIMO Layers Reduction

According to 3GPP specifications, the number of receive and transmit antennas used by a UE cannot be fewer than the maximum number of MIMO layers in the downlink and uplink, respectively. For example, when a maximum of four downlink MIMO layers are configured for a UE, the UE must enable at least four receive antennas to receive data. Therefore, if the maximum number of MIMO layers can be reduced, the UE does not have to activate as many antennas, reducing power consumption.

This can be achieved in 5G because the number of MIMO layers can be re-configured based on assistance information from UEs. After receiving a request to reduce the number of MIMO layers from a UE, the base station configures fewer MIMO layers for the UE through an RRC reconfiguration message. In this way, the UE can deactivate some antennas to save power.

Power consumption in the networks and the devices is a real challenge. While the battery capacity and charging speeds are increasing, it is also important to find ways to optimise the signalling parameters, etc. One such approach can be seen in the tweet above regarding regarding T-Mobile in The Netherlands, selectively switching off a carrier in the night and switching it back when the cell starts loading or in the morning.

We will see lot more innovations and optimisations to dynamically update the technologies, parameters, optimisations to ensure power savings wherever possible.

Related Posts

Saturday, 10 September 2022

CUPS for Flexible U-Plane Processing Based on Traffic Characteristics

I looked at Control and User Plane Separation (CUPS) in a tutorial, nearly five years back here. Since then most focus has been on 5G, not just on my blogs but also from the industry. 

Earlier this year, NTT Docomo's Technical Journal looked at CUPS for Flexible U-Plane Processing Based on Traffic Characteristics. The following is an extract from the article:

At the initial deployment phase of 5th Generation mobile communication systems (5G), the 5G Non-Stand-Alone (NSA) architecture was widely adopted to realize 5G services by connecting 5G base stations to the existing Evolved Packet Core (EPC). As applications based on 5G become more widespread, the need for EPC to achieve higher speed and capacity communications, lower latency communications and simultaneous connection of many terminals than ever has become urgent. Specifically, it is necessary to increase the number of high-capacity gateway devices capable of processing hundreds of Gbps to several Tbps to achieve high-speed, high-capacity communications, to distribute gateway devices near base station facilities to achieve even lower latency communications, and to improve session processing performance for connecting massive numbers of terminals simultaneously.

Conventional single gateway devices have both Control Plane (C-Plane) functions to manage communication sessions and control communications, and User Plane (U-Plane) functions to handle communications traffic. Therefore, if the previously assumed balance between the number of sessions and communications capacity is disrupted, either the C-Plane or the U-Plane will have excess processing capacity. In high-speed, high-capacity communications, the C-Plane has excess processing power, and in multiple terminal simultaneous connections, the U-Plane has excess processing power because the volume of communications is small compared to the number of sessions. If the C-Plane and U-Plane can be scaled independently, these issues can be resolved, and efficient facility design can be expected. In addition, low-latency communications require distributed deployment of the U-Plane function near the base station facilities to reduce propagation delay. However, in the distributed deployment of conventional devices with integrated C-Plane and U-Plane functions, the number of sessions and communication volume are unevenly distributed among the gateway devices, resulting in a decrease in the efficiency of facility utilization. Since there is no need for distributed deployment of C-Plane functions, if the C-Plane and U-Plane functions can be separated and the way they are deployed changed according to their characteristics, the loss of facility utilization efficiency related to C-Plane processing capacity could be greatly reduced.

CUPS is an architecture defined in 3GPP TS 23.214 that separates the Serving GateWay (SGW)/Packet data network GateWay (PGW) configuration of the EPC into the C-Plane and U-Plane. The CUPS architecture is designed so that there is no difference in the interface between the existing architecture and the CUPS architecture - even with CUPS architecture deployed in SGW/PGW, opposing devices such as a Mobility Management Entity (MME), Policy and Charging Rules Function (PCRF), evolved NodeB (eNB)/ next generation NodeB (gNB), and SGWs/PGWs of other networks such as Mobile Virtual Network Operator (MVNO) and roaming are not affected. For C-Plane, SGW Control plane function (SGW-C)/PGW Control plane function (PGW-C), and for U-Plane, SGW User plane function (SGW- U)/PGW User plane function (PGW-U) are equipped with call processing functions. By introducing CUPS, C-Plane/U-Plane capacities can be expanded individually as needed. Combined SGW-C/PGW-C and Combined SGW-U/PGW-U can handle the functions of SGW and PGW in common devices. In the standard specification, in addition to SGW/PGW, the Traffic Detection Function (TDF) can also be separated into TDF-C and TDF-U, but the details are omitted in this article.

From above background, NTT DOCOMO has been planning to deploy Control and User Plane Separation (CUPS) architecture to realize the separation of C-Plane and U-Plane functions as specified in 3rd Generation Partnership Project Technical Specification (3GPP TS) 23.214. Separating the C-Plane and U-Plane functions of gateway devices with CUPS architecture makes it possible to scale the C-Plane and U-Plane independently and balance the centralized deployment of C-Plane functions with the distributed deployment of U- Plane functions, thereby enabling the deployment and development of a flexible and efficient core network. In addition to solving the aforementioned issues, CUPS will also enable independent equipment upgrades for C-Plane and U-Plane functions, and the adoption of U-Plane devices specialized for specific traffic characteristics.

In the user perspective, the introduction of CUPS can be expected to dramatically improve the user experience through the operation of facilities specializing in various requirements, and enable further increases in facilities and lower charges to pursue user benefits by improving the efficiency of core network facilities.

Regarding the CUPS architecture, a source of value for both operators and users, this article includes an overview of the architecture, additional control protocols, U-Plane control schemes based on traffic characteristics, and future developments toward a 5G Stand-Alone (5G SA) architecture.

The article is available here.

Related Posts

Monday, 13 June 2022

Tutorial on 4G/5G Mobile Network Uplink Working and Challenges

People involved with mobile technology know the challenges with uplink for any generation of mobile network. With increasing data rates in 4G and 5G, the issue has become important as most of the speeds are focused on download but upload speeds are quite poor.

People who follow us across our channels know of many of the presentations we share across them from various sources, not just ours. One such presentation by Peter Schmidt looked at the uplink in details. In fact we recommend following him on Twitter if you are interested in technical details and infrastructure.

The details of his talk as follows:

The lecture highlights the influences on the mysterious part of mobile communications - sources of interference in the uplink and their impact on mobile communication as well as practices for detecting sources of RF interference.

The field strength bar graph of a smartphone (the downlink reception field strength) is only half of the truth when assessing a mobile network coverage. The other half is the uplink, which is largely invisible but highly sensitive to interference, the direction from the end device to the base stations. In this lecture, sources of uplink interference, their effects and measurement and analysis options will be explained.

Cellular network uplink is essential for mobile communication, but nobody can really see it. The uplink can be disrupted by jammers, repeaters, and many other RF sources. When it is jammed, mobile communication is limited. I will show what types of interference sources can disrupt the uplink and what impact this has on cellular usage and how interference hunting can be done.

First I explain the necessary level symmetry of the downlink (from the mobile radio base station - eNodeB to the end device) and the uplink (from the end device back to the eNodeB). Since the transmission power of the end device and eNodeB are very different, I explain the technical background to achieving symmetry. In the following I will explain the problems and possibilities when measuring uplink signals on the eNodeB, it is difficult to look inside the receiver. In comparison, the downlink is very easy to measure, you can see the bars on your smartphone or you can use apps that provide detailed field strength information etc. However, the uplink remains largely invisible. However, if this is disturbed on the eNodeB, the field strength bars on the end device say nothing. I will present a way of observing which some end devices bring on board or can be read out of the chipset with APPs. The form in which the uplink can be disrupted, the effects on communication and the search for uplink sources of disruption will complete the presentation. I will also address the problem of 'passive intermodulation' (PIM), a (not) new source of interference in base station antenna systems, its assessment, measurement and avoidance.

The slides are available here. The original lecture was in German, a dubbed video is embedded below:

If you know of some other fantastic resources that we can share with our audience, please feel free to add them in the comments.

Related Posts

Monday, 16 May 2022

Lawful Intelligence and Interception in 5G World with Data and OTT Apps

Not long ago we looked at the 'Impact of 5G on Lawful Interception and Law Enforcement' by SS8. David Anstiss, Senior Solutions Architect at SS8 Networks gave another interesting talk on Evolving Location and Encryption Needs of LEAs in a 5G world at Telecoms Europe Telco to Techco virtual event in March.

In this talk, David provided an insight in​to how 5G is impacting lawful interception and the challenges Law Enforcement Agencies face as they work with Communication Service Providers to gather intelligence and safeguard society. While there is an overlap with the previous talk, in this video David looked at a real world example with WhatsApp. The talk also covered:

  • Real-world problems with 5GC encryption
  • 5G location capabilities and the impact on law enforcement investigations
  • Optimal solutions for both CSPs and LEAs

The video of the talk is embedded below:

Related Posts:

Tuesday, 12 October 2021

Tuesday, 24 August 2021

3GPP's 5G-Advanced Technology Evolution from a Network Perspective Whitepaper


China Mobile, along with a bunch of other organizations including China Unicom, China Telecom, CAICT, Huawei, Nokia, Ericsson, etc., produced a white paper on what technology evolutions will we see as part of 5G-Advanced. This comes not so long after the 3GPP 5G-Advanced Workshop which a blogged about here.

The abstract of the whitepaper says:

The commercialization of 5G networks is accelerating globally. From the perspective of industry development drivers, 5G communications are considered the key to personal consumption experience upgrades and digital industrial transformation. Major economies around the world require 5G to be an essential part of long-term industrial development. 5G will enter thousands of industries in terms of business, and technically, 5G needs to integrate DOICT (DT - Data Technology, OT - Operational Technology, IT - Information Technology and CT - Communication Technology) and other technologies further. Therefore, this white paper proposes that continuous research on the follow-up evolution of 5G networks—5G-Advanced is required, and full consideration of architecture evolution and function enhancement is needed.

This white paper first analyzes the network evolution architecture of 5G-Advanced and expounds on the technical development direction of 5G-Advanced from the three characteristics of Artificial Intelligence, Convergence, and Enablement. Artificial Intelligence represents network AI, including full use of machine learning, digital twins, recognition and intention network, which can enhance the capabilities of network's intelligent operation and maintenance. Convergence includes 5G and industry network convergence, home network convergence and space-air-ground network convergence, in order to realize the integration development. Enablement provides for the enhancement of 5G interactive communication and deterministic communication capabilities. It enhances existing technologies such as network slicing and positioning to better help the digital transformation of the industry.

The paper can be downloaded from China Mobile's website here or from Huawei's website here. A video of the paper launch is embedded below:

Nokia's Antti Toskala wrote a blog piece providing the first real glimpse of 5G-Advanced, here.

Related Posts

Monday, 9 August 2021

Qualcomm Demoes Sub-band Half Duplex (SBHD)


Qualcomm has been busy promoting its advanced 5G solutions these last few months in the run up to Mobile World Congress (MWC). You can find a detailed write-up on their website here as well as a feature which they did with RCR wireless here.

One of the innovations that caught my attention was Sub-band Half-Duplex (SBHD). In the first glance it looks like the Enhanced Interference Mitigation & Traffic Adaptation (eIMTA) solution we discussed long back here.

Their article talks about how their 5G multi-cell over-the-air (OTA) test network can now support subband half-duplex, allowing for more flexible service multiplexing as well as improved latency and coverage. 

While you can get an idea of what SBHD is from the diagram above, here is a video explaining it further.

Let us know what do you think about how important will this feature be in future 5G networks.

Related Posts:

Wednesday, 30 June 2021

Open RAN Terminology and Players


When we made our little Open RAN explainer, couple of years back, we never imagined this day when so many people in the industry will be talking about Open RAN. I have lost track of the virtual events taking place and Open RAN whitepapers that have been made available just in the last month.

One of the whitepapers just released was from NTT Docomo, just in time for MWC 2021. You can see the link in the Tweet

Even after so much information being available, many people still have basic questions about Open RAN and O-RAN. I helped make an Open RAN explainer series and blogged about it here. Just last week, I blogged about the O-RAN explainer series that I am currently working on, here.

There were some other topics that I couldn't cover elsewhere so made some short videos on them for the 3G4G YouTube channel. The first video/presentation explains Open RAN terminology that different people, companies and organizations use. It starts with open interfaces and then looks at radio hardware disaggregation and compute disaggregation. Moving from 2G/3G/4G to 5G, it also explains the Open RAN approach to a decomposed architecture with RAN functional splits.

If you look at the Telecom Infra Project (TIP) OpenRAN group or O-RAN Alliance, the organizations driving the Open RAN vision and mission, you will notice many new small RAN players are joining one or both of them. In addition, you hear about other Open RAN consortiums that again include small innovative vendors that may not be very well known. 

The second video is an opinion piece looking at what is driving these companies to invest in Open RAN and what can they expect as return in future.

As always, all 3G4G videos' slides are available on our SlideShare channel.

Related Posts:

Thursday, 24 June 2021

O-RAN Introduction for Beginners


Having been writing about Open RAN for a while, I thought it was important to make simple beginners tutorials for O-RAN. As my full time job* is with a company that is heavily involved in Open RAN and O-RAN, I had an insiders view for doing this project. 

I am making a series of videos for Parallel Wireless to help the industry become familiar with the technology and terminology. The playlist is embedded below:

Four of these are ready and more will be added as and when I get some time. Here is a summary of the videos available. Some of them also have a corresponding blog that I am linking below.

  1. Introduction to O-RAN Philosophy: This explains the basics of O-RAN and how O-RAN is transforming the mobile networks industry towards open, intelligent, virtualized and fully interoperable RAN.
  2. Introduction to O-RAN Timeline and Releases: This part looks at important timelines from the O-RAN Alliance, understand the O-RAN Software Community (OSC) and the role it plays in O-RAN, and finally, looks at the O-RAN Open-Source Software releases.
  3. Introduction to O-RAN Architecture: This part looks at how the basic OpenRAN architecture is evolving into the O-RAN Alliance based Intelligent, Virtualized and Fully Interoperable RAN. It starts with a high-level ORAN architecture and then delves into details of Service Management and Orchestration (SMO), Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC), Near-RT RIC and O-Cloud.
  4. O-RAN Technical Steering Committee (TSC) & Workgroups: This part looks at O-RAN Technical Steering Committee (TSC) & Workgroups (WGs). The O-RAN TSC decides or gives guidance on O-RAN technical topics and approves O-RAN specifications prior to the Board approval and publication. The TSC consists of Member representatives and the technical workgroup co-chairs, representing both Members and Contributors. Within the TSC, there are 10 work groups, 4 focus groups, Open-Source Community and Minimum Viable Plan Committee. These have all been discussed within the video.
  5. O-RAN Workgroup1: Task Groups and Deliverables: This part looks at O-RAN Workgroup#1 (WG1), its task groups and sub-task groups and finally the deliverables produced by WG1.
  6. O-RAN Alliance Workgroup 2 and Workgroup 3: Specifications and Other Deliverables: This part looks at O-RAN Workgroup#2 (WG2) and Workgroup#3 (WG3) deliverables.

I am hoping that I will be able to do a few more parts and add a lot more information to the basics so a handy resource is available for anyone interested. Feel free to add links, suggestions, etc. in the comments below. 

Related Posts:

*Full Disclosure: I work for Parallel Wireless as a Senior Director, Technology & Innovation Strategy. This blog is maintained in my personal capacity and expresses my own views, not the views of my employer or anyone else. Anyone who knows me well would know this.

Monday, 21 June 2021

3GPP Standards on Edge Computing

A sub-set of 3GPP Market Representation Partners hosted a 2-part webinar series in April 2021 looking at edge computing for industry verticals and on-going standardisation work in 3GPP. The first part write-up is available here. The webinar was attended by a mix of organisations from both verticals and the telecommunication industry, helping to share a common understanding on edge computing. 

The webinar brought together top experts at the 3GPP plenary level, SA2 (Architecture) and SA6 (application enablement and critical communication applications) for a deep-dive into how 5G and related standards can help harmonise and enable technologies like edge computing and artificial intelligence to work together much more efficiently. 

The webinar was co-chaired by Georg Mayer, 3GPP SA Chairman and Stephanie Parker, Trust-IT and Vice-chair of the 5G-IA Pre-Standardisation WG with the John Favaro, Trust-IT and member of the 5G PPP Automotive Working Group. 

The webinar was attended by a mix of organisations from both verticals and the telecommunication industry, helping to share a common understanding on edge computing.

This video embedded below is the recording of the webinar on edge computing held on Thursday 22 April 2021 part 2 - 3GPP Standards on Edge Computing as an educational deep dive to help industry verticals gain a better understanding of an evolving landscape. It gives key insights into 3GPP standardisation work on edge computing with an overview of the main activities taking place within SA (System Aspects and Architecture). Presentations and panel discussions zoom in on the network layer with SA2 Architecture and on the application layer for vertical enablement with SA6 Application Enablement and Critical Communication Applications. The panel discussion with SA TSG, SA2 and SA6 chairmen sheds light on the role of artificial intelligence from both the network and application perspectives, underscoring the vital importance of industry verticals in the standardisation process to meet their specific requirements in 3GPP as a truly global initiative.

PDF of presentations as follows:

Global5G has a summary with main takeaways and poll findings here. The following is from there:

Main Takeaways

  1. 5G will help technologies like edge computing and artificial intelligence to harmonise and enable them to work together much more efficiently.
  2. 3GPP Release 17 is foundational for edge computing but more will come in future releases given its importance in mobile communications and as we gradually move beyond 5G. The webinar was therefore a timely deep-dive into today's landscape. 
  3. Artificial Intelligence and edge computing can both serve as building blocks but in different ways: 
    • Network layer perspectives: AI can further optimise edge computing applications.
    • Application layer persepctives: Edge computing can be a building block for AI, e.g. offloading limited capabilities from the device to the network.
  4. Global initiatives like 3GPP can help reduce regional fragmentation, drive convergence and enable network-compliant rollouts that benefit the ecosystem around the world.
  5. As a global initiative, 3GPP is well placed to build on its strong relationships and collaborations with ETSI MEC and GSMA. 
  6. It is absolutely essential that industry verticals get involved in 3GPP working groups, which is where key activities take place and where their requirements should be channelled. It is also important that verticals understand how their seemingly specific requirements could be relevant to other sectors. Being part of 3GPP is a complex but highly rewarding experience. It does not need to be a life-long commitment.

Poll Findings - Participant Viewpoints

Do you participate in standardization on edge computing?

Interestingly most respondents do not take part in any standardisation initiatives. Hence the webinar series was an opportunity to highlight the many activities taking place and encourage participants to get involved. Those that do take part mostly contribute to 3GPP and other forums (29%) like ETSI (SDO) and industry associations like 5GAA and 5G-ACIA as some of the early movers on edge computing. Beyond 3GPP, a smaller number of respondents (11%) contribute to ETSI and other forums such as 5GAA and GSMA and the same amount (11%) are involved in other forums.

How important do you think coordination on edge computing standardisation is?

Coordination on edge computing standardisation needs to be prioritised with 65% of respondents saying it's vital and another 33% saying it's quite important. Only 1 respondent said it's not needed. An important output via the 5G-IA Pre-Standardisation WG and supported by panellists and organisers (5G-IA, 5GAA, 5G-ACIA and PSCE) would be a user-friendly guide on edge computing standardisation to help stakeholders navigate the landscape. 

Do you see a need for new areas of standardisation for edge computing?

Findings from this poll are particularly interesting as we have a close split between those that think more standardisation work is needed (47%) and those that don't know (43%) with just 10% saying it's not needed. Webinar organisers have come up with two possible explanations. On the one hand, we may be looking at a fragmented landscape that would benefit from more unification, also from an architecture perspective. On the other hand, organisations looking at the landscape may simply be overwhelmed by the dverse activities taking place. They may also have new applications sitting on top of the network but are not sure if they need to be standardised. Practical guidance could go a long way in clarifying this uncertainty. 

Again, a quick guide on edge computing standardisation could be a useful output, highlighting also the good cooperation already taking place as an important step in the right direction. 

You can see Part 1 of this webinar here.

Related Posts

Thursday, 10 June 2021

Nokia veterans Harri Holma and Antti Toskala explain 5G Basics

An online conference on 5G is currently going on. 'Backed by 5G: Technology for Impact', is hosted by Start North as a part of the Aalto University Summer Course 5G Hack the Mall.

It is a two-week online conference which gathers the industry experts, entrepreneurs and policymakers together to discuss, present and question how 5G will affect our society, economy and everyday life. We want you to join the change by offering a chance to learn from the best, to start or strengthen your journey to expertise in 5G. With the support of our partners, you have the possibility to listen and get your questions answered by the global 5G leaders from the leading companies, academia, NGOs and public institutions, which all are daily involved with changing the world and enabling change with the latest technology.

The current conference features couple of Nokia experts who are well known in the industry for their books on the mobile technologies. Dr. Harri Holma, Fellow, Nokia Bell Labs, spoke on "What is Good to Know About 5G Technology Components". His talk is embedded below:


The second talk is by Dr. Antti Toskala, Fellow, Nokia Bell Labs, on Radio Access (5G Physical Layer). His talk is embedded below

Slides are shared to the 5G Summer School participants. If you are keen to get your hands on the slides, please email: hello@startnorth.com. You can watch all the videos from the event on the Start North YouTube channel here.

Related Posts

Monday, 31 May 2021

5G User Plane Redundancy


We looked at the 5G Enhanced URLLC (eURLLC) earlier. One of the ways to improve reliability is to have redundancy in the user plane. This can use different approaches like: 

  • Duplicating N3
  • Adding a secondary gNB using Dual connectivity
  • Introducing another UPF
  • Two anchor UPFs

In fact they are all built on top of each other so you can decide how critical are your user plane redundancy needs. 

I came across this short video from Mpirical embedded below that covers this topic nicely. In case you want to refresh your 5G Core Network architecture, jump to our old tutorial here.

Related Posts:

Tuesday, 6 April 2021

A look at 5G Applications, Application Functions & Application Servers

We often get questions about 5G Service Based Architecture. Luckily, we have a tutorial that we can redirect people to. It's available here and the video just crossed 50K views. One of the questions that people often want to understand, is about the Application Function (AF) and how does it fit in the Applications Architecture.

To explain this, we made a tutorial. The slides and videos are embedded below. In that we have used the examples from our XR, V2X and Private Networks tutorials. All links are available at the bottom of this post.

Video:

Slides:

Related Posts:

Friday, 5 March 2021

How to Identify Network Slices in NG RAN

In my last post I described how NG RAN resources can be divided into network slices. 

Now I would like to show how these network slices and the traffic they carry can be identified. 

The key to this is a parameter from the NG Application Protocol (NGAP) called the Single Network Slice Selection Assistance Information (S-NSSAI). When configuring virtual network functions in NG RAN there are lists of S-NSSAI exchanged, e.g. between gNB-CU CP and AMF during NGAP Setup procedure, to negotiate which network slices have to be supported in general. 

When it comes to connection establishment starting with NGAP Initial Context Setup for each PDU session that is established its individual S-NSSAI is signaled. 

The S-NSSAI - as show in the figure below - consists of two parameters, the Slice/Service Type (SST - 8 bit) and the optional Slice Differentiator (SD - 24 bit). The exact format and numbering ranges are defined in 3GPP 23.003.

3GPP 23.501 defines a set of default values for SST as listed in the following table:

Slice/Service type

SST value

Characteristics

eMBB

 

1

Slice suitable for the handling of 5G enhanced Mobile Broadband.

URLLC

2

Slice suitable for the handling of ultra- reliable low latency communications.

MIoT

3

Slice suitable for the handling of massive IoT.

V2X

4

Slice suitable for the handling of V2X services.

So when looking back at the figure it emerges that for each subscriber represented by an IMSI the SST allows to identify which services are running. 

On the other hand allows to see if in which virtual network the subscriber is active. In my example I have defined that the resources are shared among a Public MNO that I consider the owner of the network hardware and two different private (campus) networks. While IMSI 1 and IMSI 2 are not allowed to use any other network slice the IMSI 3 is allowed to "roam" betweent the public slice and the two private network slices. This explains why a slice-specific authentication functionality as defined in Rel. 16 is necessary. 

Related Posts: