Showing posts with label OMA. Show all posts
Showing posts with label OMA. Show all posts

Tuesday 17 November 2020

5G Non IP Data Delivery and Lightweight M2M (LwM2M) over NIDD

Earlier this year, MediaTek had announced that its MT2625 NB-IoT chip has been validated for LwM2M over NIDD on SoftBank Corp.’s cellular network across Japan. This achievement marks the first global commercial readiness of LwM2M over NIDD; a secure, ultra-efficient IoT communications technique that is being adopted by operators worldwide. The benefits of LwM2M over NIDD include security improvements, cost-efficient scalability and reduced power consumption.

LwM2M over NIDD is a combination of the communication technology "NIDD (Non-IP Data Delivery)" that does not use an IP address in LTE communication NB-IoT for IoT and the device management protocol "LwM2M (Lightweight M2M)" advocated by the Open Mobile Alliance. It's been a while since I wrote about Open Mobile Alliance on this blog. OMA SpecWorks is the successor brand to the Open Mobile Alliance. You can read all about it here.


OMA SpecWorks’ LightweightM2M is a device management protocol designed for sensor networks and the demands of a machine-to-machine (M2M) environment. With LwM2M, OMA  SpecWorks has responded to demand in the market for a common standard for managing lightweight and low power devices on a variety of networks necessary to realize the potential of IoT. The LwM2M protocol, designed for remote management of M2M devices and related service enablement, features a modern architectural design based on REST, defines an extensible resource and data model and builds on an efficient secure data transfer standard called the Constrained Application Protocol (CoAP). LwM2M has been specified by a group of industry experts at the OMA SpecWorks Device Management Working Group and is based on protocol and security standards from the IETF.

You can get all the LwM2M resources here and the basic specs of 'Lightweight M2M 1.1: Managing Non-IP Devices in Cellular IoT Networks' here.
The 5G Americas whitepaper 'Wireless Technology Evolution Towards 5G: 3GPP Release 13 to Release 15 and Beyond' details how Current Architecture for 3GPP Systems for IOT Service Provision and Connectivity to External Application Servers. It also talks about Rel-13 Cellular IoT EPS Optimizations which provide improved support of small data transfer over control plane and user plane. Control Plane CIoT EPS Optimization transports user data (measurements, ID, status, etc.) via MME by encapsulating user data in NAS PDUs and reduces the total number of control plane messages when handling a short data transaction. Control Plane CIoT EPS optimization, designed for small infrequent data packets, can also be used for larger data bursts depending in UE Radio capability.

User data transported using the Control Plane CIoT EPS Optimization, has special characteristics, as different mobility anchor and termination nodes.

Therefore, the Preferred Network Behavior signaling must include information on:
  • Whether Control Plane CIoT EPS optimization is supported
  • Whether User Plane CIoT EPS optimization is supported
  • Whether Control Plane CIoT EPS optimization is preferred or whether User Plane CIoT EPS optimization is preferred
These optimizations have enabled:
  • Non-IP Data Delivery (NIDD) for both: mobile originated and mobile terminated communications, by using SCEF (Service Capability Exposure Function) or SGi tunneling. However, it has to be taken into account that Non-IP PDUs may be lost and its sequence is not guaranteed
  • For IP data, the UE and MME may perform header compression based on Robust Header Compression (ROHC) framework
  • NB-IoT UE can attach but not activate any PDN connection
  • High latency communication handled by the buffering of downlink data (in the Serving GW or the MME)
  • SMS transfer
  • EPS Attach, TA Update and EPS Detach procedures for NB-IoT only UEs, with SMS service request
  • Procedures for connection suspend and resume are added
  • Support for transfer of user plane data without the need for using the Service Request procedure to establish Access Stratum context in the serving eNodeB and UE
When selecting an MME for a UE that is using the NB-IoT RAT, and/or for a UE that signals support for CIoT EPS Optimizations in RRC signaling, the eNodeB’s MME selection algorithm shall select an MME taking into account its Release 13 NAS signaling protocol.

Mpirical has a nice short video explaining 5G Non IP Data Delivery. It is embedded below.

IoT has not taken off as expected and prophesised for years. While the OMASpecWorks is doing some fantastic work by defining simplified approach for IoT deployment, its current member list doesn't have enough operators to drive the uptake required for its spec adoption. They would argue that it doesn't matter how many members there are as the NIDD approach is completely optional and over-the-top. Let's wait and see how it progresses.

Related Posts:

Tuesday 12 July 2011

Couple of presentations on GNSS and LCS

I came across couple of presentations from International Conference on Localization and GNSS, held in Tampere, Finland, June 29-30, 2011

This first presentation by Lauri Wirola of Nokia gives good summary of standardized positioning technologies in use today. It also lists the difference between control plane and user plane positioning. The 3GPP based positioning from Rel 5 to Rel 8 has been listed. Overall a very interesting presentation.

The second presentation by Ignacio Fernández Hernández of the European Commission, gives an overview of the EU satnav programmes (Galileo, EGNOS) and current R&D status; Present some numbers and findings of the overall GNSS R&D panorama in EU and abroad; Present some trends and challenges in location technologies for the following years. Another interesting presentation I think.


Monday 27 October 2008

Customisable services on their way

According to a survey in Mformation:

80 percent of respondents to the survey indicated that they would use mobile services more if greater personalization were possible. 67 percent of mobile subscribers stated they would be willing to pay a premium to personalize their mobile devices and the applications and services on them. In fact, 86 percent of people said this would enrich their mobile experience. The research also revealed that over two thirds (68%) of mobile users find buying a phone frustrating when they know that there are applications and services on it that they will never use. This clearly demonstrates that greater personalization offers an opportunity to unlock pent-up demand.
The research also found the following results:
  • Revenue-generating mobile data services such as mobile email (43%), Internet (51%) and picture messaging (46%) are gaining ground as the most frequently used applications.
  • There are still a large number of people who never or rarely use these applications (email – 57 %, Internet – 49%, picture messaging – 54%).
  • More than half of people who don’t currently have access to these applications would use them if they were made available in a simple and compelling manner (email – 62%, Internet – 58%, picture messaging – 68%).

94 percent of consumers are already attempting to personalize their phones with items like specific ringtones or accessories. However, 89 percent said that they would like a higher level of personalization through the ability to pick and mix applications, services, and other characteristics of the handset such as form factors and designs. Moreover, 81 percent would switch to a provider that offered greater choice for customization.

Now, a forthcoming update to the Open Mobile Alliance Device Management (OMA DM) standard for mobile phones will make it easier for users to personalise their handset, for which there is enormous potential demand

Matt Bancroft, Mformation vice president, said that operators have a strong role to play in making this happen, and stand to gain as many respondents indicated that they would switch carrier and be prepared to pay extra for the ability to customise their handset.

Bancroft suggested that the OMA DM extensions, due to be ratified in 2009, will enable users of feature phones to customise their handset as much as high-end smartphone users already can.

"In essence, the update adds a new managed object defined for delivery, installation, activation and management of applications," he said.

The new extension, called Software Component Management Object, is already available as a pre-ratified version in Mformation's management tools for mobile operators, according to Bancroft.

"It also means profound things for software developers. A billion and a half mobile phones are sold each year, so there will be a much broader market for applications in the next 12-18 months once this standard becomes available," he said.

Tuesday 26 June 2007

OMA seeks to ease mobile TV pain


The Open Mobile Alliance's recently-unveiled BCAST Enabler specification is designed to create a 'write once, run anywhere' environment' for broadcasters and other content providers. The spec - if widely adopted - could have significant implications for the concept of mobile TV 'roaming'.
In theory, it means broadcasters will be able to deploy their programming across the whole gamut of broadcast mobile TV platforms - DVB-H, DVB-SH, DMB, DAB-IP, ATSC-M/H etc - with little or no tweaking.
Because it works with any IP-based content delivery technology BCAST Enabler can also be used for the delivery of programming across cellular systems like 3GPP MBMS, 3GPP2 BCMCS and mobile unicast streaming systems, such as 3G streaming.

What benefits will OMA BCAST offer broadcasters and broadcast network operators?
• The specification enables broadcast-only mode for delivering services. It also allows broadcast-only terminals and free-to-air content with service and content protection capability.

• The specification is agnostic to access network meaning that the same service offering can be delivered over broadcast channel, interaction channel or both. Being agnostic to underlying architecture allows integration of the broadcast offering with operators or independent delivery over the interaction channel, which is controlled by broadcaster.

• Service interactivity is well specified and caters for broad range of services including interactive and direct feedback from viewers. Also, the service interactivity is not bound to the cellular channel – WLAN or a similar network can also be used. The use of the interaction channel allows personalization of services and service guides.

• The Service Guide enables the broadcaster to associate broadcast
programming with on-demand content. In addition, it supports both broadcast and on-demand delivery of the Service Guide itself.

What benefits will OMA BCAST offer terminal manufacturers?

• The Mobile TV Enabler specifies features for a common TV & video service layer that are currently not addressed by other specifications but still needed to ensure interoperability for large-scale terminal availability.

• Enables economies of scale by leveraging same technologies for both
broadcast and interactive channels. This means vendors can build an
economically viable terminal base that can be used by operators/carriers or broadcasters or jointly by both.