There is no shortage of Metaverse papers and articles as it is the latest trend in the long list of technologies promising to change the world. Couple of months back I wrote a post about it in the 6G blog here.
TOMORROW: Hear from leading experts in the field about key questions such as how this technology is evolving, how can it be leveraged to augment business and personal environments, and what socio-technical and ethical questions have to be addressed. https://t.co/NggnJPu4eU pic.twitter.com/kfmYiCdomP
— IEEE Standards Assoc (@IEEESA) July 5, 2022
IEEE hosted a Metaverse Congress with the Kickoff Session 'Demystifying and Defining the Metaverse' this month as can be seen in the Tweet above. The video embedded below covers the following talks:
Some fantastic definitions, explanations, use cases and vision on Metaverse. The final speaker nicely summarised Metaverse as shown in this slide below.
Worth highlighting point 6 that the Metaverse is device independent. I argued about something similar when we try and link everything to 6G (like we linked everything to 5G before). We are just in the beginning phase, a lot of updates and clarifications will come in the next few years before Metaverse starts taking a final shape.
Related Posts:
At DEF CON 31 last year, Tracy Mosley, Vulnerability Researcher at Trenchant presented a talk titled "Nothin’ but a G Thang - The Evolution of Cellular Networks" (background of title). The abstract of the talk says:
In this talk we will walk through each step of cellular evolution, starting at 2G and ending at 5G. The never-ending attack and defend paradigm will be clearly laid out. In order to understand the attack surface, I’ll cover network topology and protocol. For each cellular generation, I will explain known vulnerabilities and some interesting attacks. In response to those vulnerabilities, mitigations for the subsequent cellular generation are put in place. But as we all know, new mitigations mean new opportunities for attackers to get creative. While I will explain most cellular-specific terminology, a familiarity with security concepts will help to better understand this talk. Basic foundations of communications systems, information theory or RF definitely make this talk more enjoyable, but are absolutely not necessary. It’s a dense topic that is highly applicable to those working on anything that touches the cellular network!
The talk is embedded below:
The presentation can be downloaded from here.
Related Posts:
At the Brooklyn 6G Summit (B6GS) 2023, top tier economist Dr. Jeff Shen from BlackRock, presented a talk from the industry perspective of AI (Artificial Intelligence) and investment. Jeff Shen, PhD, Managing Director, is Co-CIO and Co-Head of Systematic Active Equity (SAE) at BlackRock. He is a member of the BlackRock Global Operating Committee, BlackRock Systematic (BSYS) Management Committee and the BlackRock Asian Middle Eastern & Allies Network (AMP) Executive Committee.
How are firms reacting to AI? From 'ICT Industry Trends in the coming decades' by Jeff Shen, BlackRock at #B6GS - I am guessing the peak of mobile mention was the peak 5G hype in 2015/16. Hopefully the industry is now much wiser and won't repeat the 6G hype. pic.twitter.com/xjEiDtmSUZ
— Zahid Ghadialy (@zahidtg) November 5, 2023
In his talk he covered the history of how and where AI has been traditionally used and how the thinking around AI has changed over the last few decades. He then presented his view on if AI is just a fad or it's more than that. To illustrate the fact, he provided an example of how Generative AI market is expected to grow from $40 Billion in 2022 to $1.3 Trillion in 2032.
There are many challenges that AI faces that one should be aware of; namely regulation, cyber threats and ethical concerns. In the US, AI touches the entire economy, from legal to healthcare. In their quarterly reporting, firms are now discussing AI and the larger tech companies are not afraid to grow inorganically in order to get more exposure to the trend.
You can watch the whole of his talk embedded below, courtesy of IEEE Tv.
Related Posts:
Jim Morrish, Founding Partner of Transforma Insights has kindly made an in-depth Edge Computing Tutorial for our channel. Slides and video is embedded below.
In this tutorial Jim covers the following topics:
We would love to know if this answers your questions on this topic. If not, please feel free to post your questions below.
Related Posts:
The Project Coordination Group (PCG) of 3GPP recently approved a new logo for use on specifications for 6G, during their 52nd PCG meeting, hosted by ATIS in Reston, Virginia. As with previous logos, surely people in general will use them not just for 3GPP 6G compliant products, but for all kinds of things.
New 6G logo approved - The Project Coordination Group (PCG) of 3GPP has approved a new logo for use on specifications for 6G, during their 52nd PCG meeting this week. Learn more: https://t.co/sh2yvQtc23 via @3GPPLive#Free6Gtraining #6G #5G #B5G #5GAdvanced #3G4G5G pic.twitter.com/2CtUVBGQgd
— Free 6G Training (@6Gtraining) April 24, 2024
Over the years many people have reached out to me to ask for 3GPP logos, even though they are available publicly. All 3GPP logos, from 3G to 6G is available in the Marcoms directory here. In addition to the logo, each directory also lists guidance for use of the logos. For example, 3GPP does not allow the use of the logo as shown on the left in the image on top of the post while the one on the right is okay.
Surely there isn't an issue for general use but for anyone wishing to use the logos for their products, equipment, documentation or books, they will have to strictly comply with the rules.
Related Posts:
Metaverse means different things for different people. If you explain Metaverse with an example, many people understand but they are generally looking at things from a different point of view. A bit like blind men and an elephant. Similarly when we talk about Metaverse-ready networks, it can mean different things to different people, depending on their background.
Back in Oct 2021, Facebook changed its name to Meta with a vision to bring the metaverse to life and help people connect, find communities and grow businesses. This was followed by a blog post by Dan Rabinovitsj, Vice President, Meta Connectivity, highlighting the high-level requirements for these metaverse-ready networks.
At Fyuz 2022, the Telecom Infra Project (TIP) announced the launch of Metaverse-Ready Networks Project Group primary whose objective is to accelerate the development of solutions and architectures that enhance network readiness to support metaverse experiences. Meta Platforms, Microsoft, Sparkle, T-Mobile and Telefónica are the initial co-chairs of this Project Group.
A blast from the past - I'm listening to a Nokia CTO, Alessandro Bovone, setting out Nokia's view of the future #CWIC2022 pic.twitter.com/DSN96eK2qh
— David Wood (@dw2) November 2, 2022
Cambridge Wireless' CWIC 2022 discussed 'The Hyperconnected Human'. One of the sessions focussed on 'Living in the Metaverse' which I think was just brilliant. The slides are available from the event page and the video is embedded below:
Coming back to metaverse-ready networks, the final day of Fyuz 2022 conference featured 'The Meta Connectivity Summit' produced by Meta.
The main stage featured a lot of interesting panel sessions looking at metaverse use cases and applications, technology ecosystem, operator perspectives as well as a talk by CIO of Softbank. The sessions are embedded below. The breakout sessions were not shared.8.3 milliseconds is the magic number to have a seamless experience in the Metaverse#Metaverse #MetaverseConnectivity #Fyuz22 https://t.co/UsqDEgvBEU
— Zahid Ghadialy (@zahidtg) October 27, 2022
Metaverse is also being used as a catch-all for use cases and applications in 6G. While many of the requirements of Metaverse will be met by 5G and beyond applications, 6G will bring in even more extreme requirements which would justify the investments in the Metaverse-Ready Networks.
Related Posts:
The 5G Core (5GC) supports the application of analytics to provide Intelligent Automation of the network, In Rel-16 the set of use cases that are proposed for the NWDAF has been widely expanded.
In an earlier post, we looked at the ATIS webinar discussing Release-16 & forthcoming features in Rel-17. Puneet Jain, Director of Technical Standards at Intel and 3GPP SA2 Chairman talked briefly about NWDAF. The following is from his talk:
Release-16 provides support for Network Automation and Data Analytics. Network Data Analytics Function (NWDAF) was defined to provide analytics to 5G Core Network Functions (NFs) and to O&M. It consists of several services that were defined in 3GPP Rel-16 and work is now going in Release 17 to further extend them.
In release 16 Slice load level related network data analytics and observed service experience related network data analytics were defined. NF load analytics as well Network Performance analytics was also specified. NWDAF provides either statistics or prediction on the load communication and mobility performance in the area of interest.
Other thing was about the UE related analytics which includes UE mobility analytics, UE communication analytics, Expected UE behavior parameter, Related network data analytics and abnormal behavior related network data analytics.
The NWDAF can also provide user data congestion related analytics. This can be done by one time reporting or continuous reporting in the form of statistics or prediction or both to any other network function.
QoS sustainability analytics, this is where the consumer of QoS sustainability analytics may request NWDAF analytics information regarding the QoS change statistic for a specific period in the past in a certain area or the likelihood of QoS change for a specific period in future, in certain areas.
In Release 17, studies are ongoing for network automation phase 2. This includes some leftover from Release 16 such as UE driven analytics, how to ensure that slice SLA is guaranteed and then also new functionality is being discussed that includes things like support for multiple NWDAF instance in one PLMN including hierarchies, how to enable real-time or near-real-time NWDAF communications, how to enable NWDAF assisted user pane optimization and last which is very interesting is about interaction between NWDAF and AI model and training service owned by the operator.
This article on TM Forum talks about NWDAF deployment challenges and recommendations:
To deploy NWDAF, CSPs may encounter these challenges:
Here are some ways you can overcome these challenges and deploy efficient next-generation analytics with NWDAF:
This is such an important topic that you will hear more about it on this blog and elsewhere.
Related Posts:
Drones, technically Unmanned Aerial Vehicles/Systems or UAVs/UASs, have been a subject of interest for a very long time due to the wide variety of use cases they can offer. In the recent issue of 3GPP Highlights newsletter, Lena Chaponniere, 3GPP Working Group CT1 Vice-Chair has written an article about TSG CT work on UAS Connectivity, Identification and Tracking. Interestingly, the 3GPP abbreviation for UAS is slightly different, Uncrewed Aerial Systems.
Quoting from the newsletter:
One of the defining drivers of 5G is the expansion beyond traditional mobile broadband to provide solutions meeting the needs of vertical industries.
A very good example of 3GPP rising up to this challenge is the work done in Release 17 to use cellular connectivity to support Uncrewed Aerial Systems (UAS), thereby enabling this vertical to benefit from the ubiquitous coverage, high reliability, QoS, robust security, and seamless mobility provided by the 3GPP system.
A key component of this work took place in CT Working Groups, which under the leadership of Sunghoon Kim (CT Work Item rapporteur) and Waqar Zia (rapporteur of new specifications TS 29.255 and TS 29.256) developed the necessary protocols and APIs to meet the service requirements specified in 3GPP SA1 and the architectural enhancements specified in 3GPP SA2, as part of the Release 17 Work Item on ‘ID_UAS’.
The key functions of the 3GPP architecture for ID_UAS are depicted in the following figure:
The work in CT Working Groups focused on specifying support for the following features:
UAV remote identification: The CAA (Civil Aviation Administration)-Level UAV ID was introduced in the 3GPP system. It is a globally unique, electronically and physically readable, and tamper resistant identification which allows the receiving entity to address the correct USS for retrieval of UAV information and can be assigned solely by the USS, via means outside the scope of 3GPP, or assigned by the USS with assistance from 3GPP system, whereby the USS delegates the role of “resolver” of the CAA-Level UAV ID to the UAS NF.
AV USS authentication and authorization (UUAA): The first step for the owner of the UAV is to register the UAV with the USS, via a procedure outside the scope of 3GPP, which can take place offline or using internet connectivity. During this procedure, the CAA-level UAV ID is configured in the UAV and the aviationlevel information (e.g. UAV serial number, pilot information, UAS operator, etc.) is provided to the USS.
The UE at the UAV then registers with the 3GPP system by using existing procedures for 3GPP primary authentication, with the MNO credentials stored in the USIM.
After successful authentication of the UE, the UUAA procedure is performed, to enable the 3GPP Core Network to verify that the UAV has successfully registered with the USS. In 5GS, this procedure can take place during the 3GPP registration, or during the establishment of a PDU session for UAS services.
For the former, CT1 extended the registration procedure in TS 24.501 to enable the UE to indicate its CAA-Level UAV ID into a new container (Service-level-AA container) included in the Registration Request message, which triggers the AMF to initiate UUAA with the USS by invoking the Nnef_Authentication service toward the UAS NF, as specified by CT4 in new specification TS 29.256, and the UAS NF to invoke the Naf_Authentication service toward the USS, as specified by CT3 in new specification TS 29.255.
For the latter, CT1 extended the PDU session establishment procedure in TS 24.501 to enable the UE to indicate its CAA-Level UAV ID via the Service-level-AA container included in the PDU Session Establishment Request message, which triggers the SMF to initiate UUAA with the USS via the UAS NF by invoking the services mentioned above. In order to enable exchanging the authentication messages between the UE and the USS, CT1 specified a new Session Management procedure in TS 24.501, in which the SMF sends a Service-level Authentication Command to the UE in a Downlink NAS Transport message. The UE replies to this command with a Service-level Authentication Complete carried in an Uplink NAS Transport message. In EPS, the UUAA procedure takes place during PDN connection establishment, and the information exchanged to that end between the UAV and the PGW is carried in the Service-level-AA container included in the ePCO
C2 communication over cellular connectivity: C2 communication over cellular connectivity consists of the UAV establishing a user plane connection to receive C2 messages from a UAVC, or to report telemetry data to a UAVC. Authorization for C2 communication by the USS is required and includes authorization for pairing of the UAV with a UAVC, as well as flight authorization for the UAV.
C2 communication authorization may be performed:
To support this, CT1 extended the PDU session establishment and modification procedures in TS 24.501 to enable inclusion of the CAA-level UAV ID and an application layer payload containing information for UAVC pairing and for UAV flight authorization in the Service-level-AA container carried in the PDU Session Establishment Request and PDU Session Modification Request messages. The ePCO Information Element in TS 24.008 was also extended to enable it to include the above-mentioned information.
UAV location reporting and tracking: UAV location reporting and tracking was specified by CT3 and CT4 by re-using the existing Nnef_EventExposure service specified in TS 29.522 with the UAS NF acting as NEF/SCEF and interacting with other network functions (e.g. GMLC and AMF/MME) to support UAV tracking. The following tracking modes were specified:
The PDF of newsletter is available here.
Related Posts:
