ETSI
Draft ETSI TS 102 690 V0.10.3 (2011
• Provides a mapping between the Name of a M2M Device or an M2M Gateway or a group of M2M
Devices/M2M Gateways and a set of information
o set of routable network addresses of the M2M Device or M2M Gateway (e.g. in case of GPRS
network, a M2M Device or M2M Gateway can have 2 addresses : an IP address and a MSISDN)
when the M2M Device is behind a M2M Gateway, the routable network address may be the
M2M Gateway's address.
When the name corresponds to a group of M2M Devices or M2M Gateways the mapping
provides a table containing network addresses for each M2M Device or M2M Gateway.
o Reachability status of an M2M Device or M2M Gateway
o The next planned wake-up time and wake-up duration, if available
• Uses a mechanism (to be defined later) for having the mapping table updated when a M2M device or
M2M gateway is becoming reachable
• Receives requests from other capabilities to be notified when, e.g.
o a specific M2M device becomes reachable
o a device may acquire a new address as a result of mobility
o changes occurs on a set of M2M Device Applications registration information
o etc.
• Provides addressing material and reachability status to the other capabilities, by taking into account the
planned wake-up time and duration
• Allows to create, delete and list a group of M2M Devices or M2M Gateways. Each group of M2M
Devices/Gateways will be identified through a Name.
• Maintains the Device Application Repository:
o By storing in the Device Application Repository the M2M Device Application registration
information of M2M Devices and keeps this information up to date.
o By providing a query interface to properly authenticated and authorized entities residing in the
Network and Application domain for them to be able to retrieve M2M Device Applications
registration information
o By providing, upon request, this information to any entity residing in the Network and Application
domains, assuming the requesting entity is authenticated and authorized to perform such a query.
Editor's note: the below bullet does not mandate this feature to be applicable to all devices. It is FFS if the
content is to be stored in NRAR: contributions are invited. Similar feature will be added in NAE for
network applications.
o By storing in the Device Application Repository the M2M Device's data that can be read by the
authenticated and authorized M2M Network Applications.
o By providing a subscription/notification mechanism that allows an authenticated and authorized M2M
Network Application to be warned upon M2M Device's data update.
• Editor's note: The following bullet is FFS
o Checks NA, GA, and/or DA credentials before providing access to NRAR functions.
5.2.4 Network Communication Selection (NCS) Capability
The Network Communication Service Selection (NCS) Capability :
• Provides network selection when the M2M Device or M2M Gateway can be reached through several network
via several subscriptions.
• Provides the Communication Service selection when a M2M Device or M2M Gateway has several network
addresses.
• Takes into account the Requested Service Class for the purpose of Network and Communication Service
selection.
• Provides alternative Network or Communication Service selection after a communication failure using a first
selected Network or Communication Service.