IEEE 802. 16-15-0005-01-03R0

802.16.3 lmap

23 Feb 2015

IEEE 802. 16-15-0005-01-03R0

Lmap Overview

• draft-ietf-lmap-framework-12 introductory section:• “There is a desire to be able to coordinate the execution of broadband measurements and

the collection of measurement results across a large-scale set of Measurement Agents (MAs).”

• lmap Use Cases Scenario (draft-ietf-lmap-use-cases-06)• From the LMAP perspective, there is no difference between fixed service and mobile

(cellular) service used for Internet access. Hence, like measurements will take place on both fixed and mobile networks. Fixed services include technologies like Digital Subscriber Line (DSL), Cable, and Carrier Ethernet. Mobile services include all those advertised as 2G, 3G, 4G, and Long-Term Evolution (LTE). A metric defined to measure end-to-end services will execute similarly on all access technologies. Other metrics may be access technology specific. The LMAP architecture covers both IPv4 and IPv6 networks.

• lmap use cases currently do not include Wireless Broadband 802.16

IEEE 802. 16-15-0005-01-03R0

Comparison lmap vs 802.16.3Functional Entities

+-----------+ +-----------+ ^|End user or| |End user or| ||Measurement| |Measurement| Non-LMAP| Peer | | Peer | Scope+-----------+ +-----------+ v ^ ^ \ traffic +-------------+ / ^ \...............|.............|........./ | | Measurement | | +----------------->| Agent | | | +-------------+ | | ^ | | | Instruction | | Report | | (over Control | | (over Control Channel) | | Channel) | +---------------+ | | | | | | | | | | v LMAP | +------------+ +------------+ Scope | | Controller | | Collector | | | +------------+ +------------+ v | ^ ^ | ^ | | | | | | | +-------+ | | | | | v |+------------+ +----------+ +--------+ +----------+ | |Bootstrapper| |Subscriber|--->| data |<---| Results | Out+------------+ |parameter | |analysis| |repository| of |database | | tools | +----------+ Scope +----------+ +--------+ | | v

 Figure 1: Schematic of main elements of an LMAP-based Measurement System

Figure 2: Application of Architectural Reference Model

IEEE 802. 16-15-0005-01-03R0

P802.16.3 vs lmapFunctional Entities

Functional Entity Type Description LmapClient   Central Element of the Architectural Reference Model.

Typically embodied as software executing on user edge device (the Client Device), typically a mobile terminal.In case of passive measurements, the Client will collect performance data characterizing communications to and from the Client Device.In case of active measurements, the Client will initiate communications, for measurement purposes, with the Server.The Client posts measurement data to one or more Data Collectors.In addition, the Client may specify the address of the Public Data Collector that the Public Server can submit experimental results to.

Measurement Agent

Controller   Provides information to Client governing the measurement process. Information includes the measurement triggers (e.g. day/time information as well as other specific triggering details, such as location conditions).Also provides the Client with the Server and Data Collector addresses.Client registers with Controller to indicate its address and availability to conduct measurements.

BootstrapperController

Server Public / Private

Serves as communication termination, also providing a data source and data recipient for active measurements initiated by the Client.Registers with Controller to indicate its address and availability to conduct measurements.

End user or Measurement Peer

Data Collector Public / Private

Receives measurement results from the Client. Collector

Network Parameter Host   The Network Parameter Host is included in the Architectural Reference Model for information only.This Functional Entity is described in other documents

Subscriber parameter database

IEEE 802. 16-15-0005-01-03R0

P802.16.3 vs lmapProcedural Flow

An LMAP system goes through the following phases: a Bootstrapping process before the MA can take part in the other three phases. a Control Protocol, which delivers Instruction Messages from a Controller to a MA (amongst other things). the actual Measurement Tasks, which measure some performance or reliability parameter(s) associated with the

transfer of packets. a Report Protocol, which delivers Reports containing the Measurement Results from a MA to a Collector

802.16.3 system goes through the following phases: REGISTRATION

o Client to Controller registrationo Public/Private Server to Controller registration

CONFIGURATIONo Controller to Client configurationo Controller to Controller configurationo Controller to Server configuration

MEASUREMENT SYNCHRONIZATIONo Client to Controller Commands synchronizationo Public/Private Server to Controller Commands synchronization

MEASUREMENTS UPLOADo Flow control between Client (or Server) and Data Collector.o Measurements upload from Client to Data Collectoro Measurements upload from Public/Private Server to Data Collector

DEREGISTRATIONo Client to Controller Deregistrationo Public/Private Server to Controller Deregistration

IEEE 802. 16-15-0005-01-03R0

P802.16.3 vs lmapInformation Model

LMAP Information Modelrelates to the information stored, received or transmitted by a Measurement Agent as described within the LMAP framework.The information described in these models will be transmitted by protocols using interfaces between the Measurement Agent and such systems according to a Data Model.For clarity the information model is divided into six sections:1. Pre-Configuration Information.

Information pre-configured on the Measurement Agent prior to any communication with other components of the LMAP architecture (i.e., the Controller, Collector and Measurement Peers), specifically detailing how to communicate with a Controller and whether the device is enabled to participate as an MA.2. Configuration Information.Update of the pre-configuration information during the registration of the MA or subsequent communication with the Controller, along with the configuration of further parameters about the MA (rather than the Tasks it should perform) that were not mandatory for the initial communication between the MA and a Controller.3. Instruction Information.Information that is received by the MA from the Controller pertaining to the Tasks that should be executed. This includes the task execution Schedules (other than the Controller communication Schedule supplied as (pre)configuration information) and related information such as the Task Configuration, communication Channels to Collectors and schedule Timing information. It also includes Task Suppression information that is used to over-ride normal Task execution. 4. Logging Information.Information transmitted from the MA to the Controller detailing the results of any configuration operations along with error and status information from the operation of the MA.5. Capability and Status Information.Information on the general status and capabilities of the MA. For example, the set of measurements that are supported on the device.6. Reporting Information.Information transmitted from the MA to one or more Collectors including measurement results and the context in which they were conducted.

Information Model

Data Model802.16.3

Data Model Data Model

Conceptual/abstract modelfor designers and operators

Concrete/detailed modelfor implementors

IEEE 802. 16-15-0005-01-03R0

P802.16.3 vs lmapCooperation

Pro Con

802.16.3 is good fit into lmap information model

Advertise/Widen user base independence issues when adapting/revising 802.16.3

Benefit from ideas of larger community

802.16.3 use cases / mobile-specific considerations may provide additional insight into lmap information model and protocols