Personal tools

5G Connectivity Types

(5G Three Connectivity Types - IEEE Xplore)

Three 5G Connectivity Types


From a functional point of view, the most logical approach is to build a set of dedicated networks each adapted to serve one type of business customer. These dedicated networks would permit the implementation of tailor-made functionality and network operation specific to the needs of each business customer, rather than a one-size-fits-all approach as witnessed in the current and previous mobile generations which would not be economically viable.

These three primary 5G New Radio (NR) use cases are defined by the 3GPP as part of its SMARTER (Study on New Services and Markets Technology Enablers) project. The objective behind SMARTER was to develop high level use cases and identify what features and functionality 5G would need to deliver to enable them. It began in 2015 and resulted in over 70 use cases, initially grouped into five categories which has since been trimmed to three. They are characterised by the performance attributes the particular use cases will require, although there is some overlap.

The three sets of primary 5G New Radio (NR) use cases are as follows:

  • Enhanced Mobile Broadband (eMBB): data-driven use cases requiring high data rates across a wide coverage area.
  • Ultra Reliable Low Latency Communications (URLLC): strict requirements on latency and reliability for mission critical communications, such as remote surgery, autonomous vehicles or the Tactile Internet.
  • Massive Machine Type Communications (mMTC): need to support a very large number of devices in a small area, which may only send data sporadically, such as Internet of Things (IoT) use cases.

eMBB supports stable connections with very high peak data rates, as well as moderate rates for cell-edge users; mMTC supports a massive number of Internet of Things (IoT) devices, which are only sporadically active and send small data payloads; URLLC supports low-latency transmissions of small payloads with very high reliability from a limited set of terminals, which are active according to patterns typically specified by outside events, such as alarms.


[More to come ...]


Document Actions