Technology with commercial intent
The first development came during a meeting of the GSMA’s 6G Task Force (6GTF) to share activities with a wider audience, beyond the GSMA’s membership community. The 6GTF’s workplan contains seven work streams. Six of these are technical while the seventh is a reporting activity to update the industry on developments within 3GPP.
In response to commercial realities, all technical workstreams include a component that addresses monetization opportunities. AI, IoT, and sensing are recurring themes in the 6gTF’s activity plan. In addition to monetization, one noteworthy development was the need for a 6G data framework. For the time being, there is a pre-standardization discussion that introduces the concept of a data plane, separate from existing control and user planes.
Infrastructure for accessibility
Data accessibility is the second important story. This one involves Swisscom’s CTIO who spoke about the operational and energy-saving opportunities from AI and digital twin technologies. He commented that, “Although AI is already having a notable positive impact on operations, the operator has realised that AI cannot scale without a strong data platform that allows engineers to query the current network state in seconds directly from a real-time data stream.”
Although telcos possess an abundance of network data, turning that data into knowledge remains a challenge. Swisscom is therefore building a data model that ingests source data and adds context to make it useable across the organisation by anyone using natural language prompts. It bears repeating that network data originates in connected assets and is another form of IoT data.
Add meaning to data
The third development involves the EU funded HEDGE-IoT project which aims to digitize the energy grid. One of the project’s pilots involves a business park in the Netherlands where IoT data allows interdependent stakeholders to become more flexible and coordinated in their energy use. As an added benefit, information sharing and anomaly detection also improve grid resilience. Two aspects of the project stand out. One involves data annotation; instead of handling a data measurement with a value of 27, for example, richer communications are possible from annotated data that says the system received a measurement of 27 degrees Celsius, for a given part of a building ‘X’, in location ‘Y’ on the business park.
The second aspect is about data sharing across organizational boundaries to improve decision-making. Trust is important in these situations because businesses will want to control how much they share while minimizing data storage on a competitor’s infrastructure. HEDGE-IoT applies a decentralized architecture with API connectors operated by each stakeholder. These connectors interpret user requests to find and retrieve data that has been annotated with meaning, like using an old-fashioned phone directory. Equipment vendors are alive to these developments and ready to include APIs and semantic descriptors as part of their product offerings.
Data Setting the Direction
The lead up to the 6G era is strongly associated with native-AI and digital twins, both of which depend on quality data. Relative to the challenge of connecting sensors and devices, expect to see greater emphasis on making IoT data easy to share and meaningful to use, especially as vendors incorporate data capabilities into their connected devices.
.png)
3 May 2026 update
ReplyDeleteThe Semantic Web
A new form of Web content that is meaningful to computers will unleash a revolution of new possibilities. By Tim Berners-Lee, James Hendler and Ora Lassila
https://www.scientificamerican.com/issue/sa/2001/05-01/
https://www.w3.org/2000/Talks/0906-xmlweb-tbl/text.htm
Deletehttps://www.w3.org/2000/Talks/0906-xmlweb-tbl/slide1-1.html
4 May 2026 update
ReplyDelete4 May 2026 update
Machine-to-Machine communications (M2M); Study on Semantic support for M2M Data
Benefits of Semantic Annotation
By providing means to understand M2M data, the available business models can be greatly enhanced. For example, through offering additional semantic information about the data, platform provider can enable (and potentially charge
for) the discovery of devices and data by semantic specification. Another possible business that can be provided would be to provide derived information from the provided raw data through intelligent processing, e.g. analysing the data,
aggregating data across many different data sources, or to provide interpreted data as an additional service.
Support for semantically annotated M2M data and related advanced operations like discovery or resolution from real-world entities to sensors/resources and vice versa will for example enable the following:
• re-use of M2M data by many applications - data can be "brokered" by the M2M Service Provider;
• "write-once run-anywhere" applications (which automatically adapt to the specific device installation);
• simplified configuration of M2M applications and more intelligent adaptation to changing situations;
• easy adaptation in case of failures/changes of the available sensor sets;
• easy creation of generic tools (e.g. for visualization, data processing).
Such 'intelligent' applications will require some notion and modelling of the 'real world' in which they provide services. For example M2M applications are not interested in sensors and actuators themselves, but in what is being sensed by the sensors, or acted upon by actuators. The relevant level of abstraction for M2M data pooling should thus not be confined to individual sensors and actuators. It should rise to the level of physical entities that are being sensed by sensors and acted upon by actuators. Depending on the environment, these entities may be appliances, people, cars, rooms of a building, or more generally self-contained subsystems of a larger system that makes up the target environment. These entities are generic, intrinsic to the environment and not tied to a specific M2M application. They can be legacy appliances or completely passive "things" that need not be directly connected through a network interface, or not even to be identified through a universal identification scheme (such as RFID/EPC global).
However, in the context of ETSI M2M only those entities need to be considered, that that can interact with the ETSI M2M System. For example a "room" entity can be sensed by the sensors in that room.
https://www.etsi.org/deliver/etsi_tr/101500_101599/101584/02.01.01_60/tr_101584v020101p.pdf