De lancering van de KPN Innovation Playground en de Netwerk Exposure features SCEF en NEF.

2. SCEF/NEF APIs
and use cases
Unlock the network
SCEF: Service Capability Exposure Function (4G)
NEF: Network Exposure Function (5G)
API: Application Programming Interface
A key enabler to expose IoT and other network
capabilities towards Application Server Providers in a
secure and controlled way
Theo Quirijnen, Cloud Core Sales Support Manager,
Ericsson

3. Massive IoT Critical IoTBroadband IoT Industrial automation IoT
Low cost devices
Small data volumes
Extreme coverage
Industrial protocols
Time sensitive networking
Precise indoor positioning
High data rates
Large data volumes
Low latency (best effort)
Ultra-low latency
High reliability
very high availability
Massive IoT with
NB-IoT & LTE-M
Critical IoT introduction with
5G NR & enhanced with 5GC
Broadband IoT with LTE
Industrial automation IoT introduction
with 5G NR & 5GC
Broadband IoT enhanced
with 5G NR & 5GC
Massive IoT evolution with
NB-IoT & LTE-M
4G networks
5G networks
(public/non-public)
Industry Digitalization with Cellular IoT
One 5G network with four multi-purpose IoT connectivity segments
Entertainment
Railways
Automotive
Manufacturing
Utilities
Mining
Forestry
Agriculture
Public safety
Ports
Smart city
Construction
Healthcare
Education
Oil & gas
Transportation
Media production
Warehousing
Four Multi-purpose IoT Segments

4. How does SCEF/NEF Exposure help you?
Cellular
Connectivity SCEF/NEF
Exposure
Layer
● Enables new use cases
● Provides information that
the devices cannot offer
● Hides the network and
device complexity
● Adds security
● Provides standardized
(3GPP) and customized APIs
● Allows you to modify the
behavior of the devices

5. Main APIs and added value
• 3GPP T8 APIs:
1. Non-IP/IP Data Delivery*
2. Monitoring Events (e.g. location,
reachability)*
3. MSISDN-less communication*
4. Network Parameter configuration
5. Set up session with required Quality of
Service
6. Changing the chargeable party
7. Resource management for Background
Data Transfer
8. Device Triggering (expected 2021)
●Added value:
● Support low cost devices to enable many
more use cases
● Solves the constraints inherent to the
devices
● Hide network and device complexity
● RESTful interface for easier access and
shorter time to market
● High Latency communication, no need
to know the device status
● Security
● Authentication & Authorization
*Planned availability for test expected Q3 2020

6. Use case: Asset tracking
Market Segment: Massive IoT
Business model: B2B
Industry Segment: Transport, delivery
Scenario:
Operator can provide a new service API to enable logistics companies
and consumers to have a continuous monitoring of the status and
location of critical assets (e.g. food crate during transportation, pet
collars) in a secure way.
Service API: Asset tracking
• Non-IP / IP Data Delivery via the same API
• Event Monitoring API (e.g. for the location, reachability)
• Replace MSISDN with external ID for additional security
• Future optional functionalities:
- Device triggering to change behavior next time the device wakes
up
- Device Management
Server
Asset
position
Asset status
Asset status
MAP
1
2
3

7. Use case: Smart metering
Market Segment: Massive IoT
Business model: B2B
Industry Segment: Utility companies
Scenario:
Meter data is collected periodically to track utility usage. The data is
non time sensitive and transmitted usually monthly, up to several
times per hour. The amount of devices is large, the amount of data to
be transmitted small.
Service API: Smart Metering
• Non-IP / IP Data Delivery via the same API
• Event Monitoring API (e.g. for the location, fraud detection)
• Replace MSISDN with external ID for additional security
• Future optional functionalities:
- Device triggering to change behavior next time the device wakes
up
- Device Management
Application Function
of Utility company
Network
Connected
utility meter
Connected
utility meter
Connected
utility meter

8. Future use case: Mobile gaming/HQ Video
Market Segment: Mobile Broadband
Business model: B2B
Industry Segment: Gaming/Content industry
Scenario:
Operators can provide a QoS API to enable OTT applications with
access to high QoS during busy hours e.g. Gaming apps, Content
providers, OTT Video/VoIP apps (Skype, LINE, WeChat), Business
applications (bank, exchange, shopping).
The quality of experience of the end users is enhanced.
Massive data
communication
Car manufacturer
server
Service API: Gaming/Content service optimization
• Request change of QoS to enhance Quality of Experience
• Event Monitoring (Location, geofencing)
• Change chargeable party, gaming provider pays operator, gamer
pays game provider and is not charged by operator for extra QoS
Video Streaming
Application Server
High quality
video
experience
Standard
Video
Experience
End user
AR enabled

9. Future use case: Background Data Transfer
Market Segment: Mobile Broadband
Business model: B2B
Industry Segment: Car Manufacturer/ Fleet Owners
Scenario:
Operators can provide a new Service API to enable a group of
connected cars (e.g. trucks) to automatically up/download massive
amount of car’s maintenance data when they are in a specific
location area and during a specific time window.
Service API: Background data transfer for massive data
• Negotiation API to agree upon a time and location for a group of
vehicles to be allowed to transmit their data
• Event Monitoring API for the location
• Pricing can be based on # GBs depending on time and location
• Change chargeable party (e.g. car manufacturer and car owner
use the same connection, but car owner does not pay for the
data)
Massive data
communication
Time
Location area
Car manufacturer
server

10. Frans Lutz
Sr. Product Specialist Wireless, IoT & Networking
frans.lutz@alcom.nl
www.linkedin.com/in/frans-lutz
Cellular modules with SCEF

11. Alcom Electronics in the Benelux
• Independent technical distributor
• 35+ years expertise in semiconductor, modules and
wireless solutions
• 50+ people in Netherlands and Belgium
• Technical salesforce and engineering support
Alcom electronics bv
Rivium 1e straat 52
2909 LE Capelle aan den IJssel
Netherlands
Tel.: +31 (0)10 288 25 00
info@alcom.nl
Alcom electronics nv/sa
Singel 3
2550 Kontich
Belgium
Tel.: +32 (0)3 458 30 33
info@alcom.be

12. SCEF
Service Capability Exposure Function
• SCEF provides a means to securely expose and discover the services
and capabilities provided by the network interface
• SCEF can be deployed in both NB-IOT and LTE-M
• SCEF is optional in LTE-M network (Rel 13)
• SCEF is part of Rel 13 and is supported by different chip set vendors

13. Advantage for the cellular module
• Simplified data transfer between cellular module and application
server. Hides the network interfaces and protocols.
• Reducing hardware cost due to simplified communication.
• Reducing overall power consumption from the cellular module and
microcontroller.
• Adding new features to applications (example: reachability, location,
loss of connectivity, communication failure, roaming status,
availability after failure)

14. How is SCEF used
Application
microcontroller
Cellular Module
Radio/Core
Network
Service
Capability Server
Application
Server
Mobile OperatorLTE-M
NBIOT
Serial/USB
AT-Commands
API
Expose available features
To Cellular module and
Application ServerNote : Simplified presentation of communication

15. NIDD
Non-IP Data Delivery
• Non-IP PDN (Packet Data Network) type is a solution to transport
traffic over Control Plane. This allows devices to consume as little
power as possible
• To use this select “PDN-Type=Non-IP” (possible values are IPv4,
IPv4v6, IPv6 or Non-IP)
• Delivery of Non-IP Data to the Service Capabilty Server / Application
Server is done using SCEF or Point-to-Point (PtP) Sgi tunnel
• NIDD is not the same as SCEF, NIDD is using SCEF for the delivery

16. Leading chipset manufacturers for LPWA

17. Cellular modules supporting
SCEF on LTE-M
▪ HL7800 LTE-M/NBIoT
▪ HL7802 LTE-M/NBIoT
Future release
▪ RC5100
▪ RC5102
▪ BG96 LTE-M/NBIoT
Future release
▪ BG95
▪ BG77
▪ BC69
▪ BG600L-M3

18. and API access to those networks
IoT Networks Network API availability
Dedicated IoT network introductions

19. Commercial product manager IoT Networks @KPN
Han de Glint

20. Time
5G introduction in NL
• 5 Fieldlabs in NL
• Validate 5G use cases
• Partnerships
• July 2020 launch 5G
• 90% coverage 5 largest cities
• Commercial launch new services
for higher availability of
connectivity
• NEF (predecessor SCEF) available
in test for developers
First steps taken, many to follow
• Additional 5G features
• First customer roll outs
• Commercial availability 5G
network API’s
• NEF/SCEF adoption by
operators, roaming

21. Enough about us..
What we aim for to happen:
• That you are having fun using the SCEF.
• Tell us about what your experience.
• What functions your using
• What applications your developing
• We are curious what this will bring us

22. Thanks Jasper, Theo, Frans. Special thanks to Ericsson
And thanks to you all for attending!

23. BACK UP VRAGEN
VOOR Theo:
-Hoe ziet de toekomst van network exposure eruit? Wat worden de nieuwe
mogelijkheden?
VOOR FRANS
VOOR HAN