1. IEEE 802.16-15-0005-00-03R0 802.16.3 lmap 23 Feb 2015

2. IEEE 802.16-15-0005-00-03R0 Lmap Overview Current lmap Use Cases Scenario (From draft-ietf-lmap-use-cases-05.pdf) –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 WLL 802.16.3

3. IEEE 802.16-15-0005-00-03R0 Comparison lmap vs 802.16.3 Functional 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

4. IEEE 802.16-15-0005-00-03R0 P802.16.3 vs lmap Functional Entities Functional EntityTypeDescriptionLmap Client 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. Bootstrapper Controller ServerPublic / 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 CollectorPublic / 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

5. IEEE 802.16-15-0005-00-03R0 P802.16.3 vs lmap Procedural 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 registration o Public/Private Server to Controller registration  CONFIGURATION o Controller to Client configuration o Controller to Controller configuration o Controller to Server configuration  MEASUREMENT SYNCHRONIZATION o Client to Controller Commands synchronization o Public/Private Server to Controller Commands synchronization  MEASUREMENTS UPLOAD o Flow control between Client (or Server) and Data Collector. o Measurements upload from Client to Data Collector o Measurements upload from Public/Private Server to Data Collector  DEREGISTRATION o Client to Controller Deregistration o Public/Private Server to Controller Deregistration

6. IEEE 802.16-15-0005-00-03R0 P802.16.3 vs lmap Information Model LMAP Information Model relates 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.

7. IEEE 802.16-15-0005-00-03R0 P802.16.3 vs lmap Cooperation ProCon 802.16.3 is good fit into lmap information model Advertise/Widen user baseindependence issues when adapting/revising 802.16.3 Benefit from ideas of larger community

8. IEEE 802.16-15-0005-00-03R0 P802.16.3 vs lmap Functional Entities (hidden slide) Functional EntityTypeDescriptionlmap Client The Client is the central element of the Architectural Reference Model. It is typically embodied as software executing on the user edge device (the Client Device), typically a mobile terminal. The measurement process is intended to collect data representative of the performance of the network from the perspective of the user edge device. In the case of passive measurements, the Client will collect performance data characterizing communications to and from the Client Device. In the case of active measurements, the Client will initiate communications, for measurement purposes, with the Server. The Client posts resultant measurement data to one or more Data Collectors. In addition, the Public Server can submit experimental results to the Public Data Collector, using the address specified by the Client. Measurement Agent Controller The Controller provides information to the Client governing the measurement process. This information includes the measurement triggers (which may include day/time information as well as other specific triggering details, such as location conditions). The Controller also provides the Client with the Server and Data Collector addresses. The Client registers with the Controller to indicate its address and availability to conduct measurements. It updates its registration status as needed. Note: Inter-controller communications for configuration sharing may be specified. Controller ServerPublic The Server serves as a communication termination, providing a data source and data recipient for active measurements initiated by the Client. The Public Server registers with the Controller to indicate its address and availability to conduct measurements. It updates its registration status as needed. The address of the Public Server is specified to the Client by the Controller. The results of measurements collected by a wide range of Clients using the Public Server should be readily comparable. Therefore, the characteristics of the Public Server should be well known and consistent, with minimal congestion and minimal variability. The Public Server can submit experimental results to the Public Data Collector, using the address specified by the Client. Note: A drawback to the use of the Public Server is that network operators could prioritize traffic to and from this server so that measurements would overestimate real network performance. End user or Measurement Peer ServerPrivate The Server serves as a communication termination, providing a data source and data recipient for active measurements initiated by the Client. The Private Server is typically hosted in a network of primary interest to the user, so that measurement of communications between the Client and the Private Server are reflective of communications conducted by the Client device outside the measurement scenario. The address of the Private Server is specified to the Client as a result of Client configuration controlled by the user. Note: The tests conducted with the Private server need not be identical to those conducted with the Public server. End user or Measurement Peer Data CollectorPublic The Data Collector receives measurement results from the Client. The Client transmits to the Public Data Collector only results that are intended for public use, with appropriate controls to prevent release of personally identifiable information (PII). In the case of active measurements, such data is limited to that collected from the Public Server. When a Private Data Collector is used, the Private Data Collector may forward public results to the Public Data Collector, in which case the Client need not be responsible for that transmission. Collector Data CollectorPrivate The Data Collector receives measurement results from the Client. The Client transmits to the Private Data Collector results that are intended for private use as well as those intended for public use. When a Private Data Collector is used, the Private Data Collector may forward public results to the Public Data Collector, in which case the Client need not be responsible for that transmission. The address of the Private Data Collector is specified to the Client as a result of Client configuration controlled by the user. Collector Network Parameter Host The Network Parameter Host is not used. Note: The Network Parameter Host is included in the Architectural Reference Model for information only, since such a functional entity is described in other documents ([3],[4],[5]). Those documents are primarily oriented toward fixed networks. In those cases, this entity (also known as a “Network Information Subscription Server” or “Network Parameter Server”) stores information and provides such information about the “nominal” network performance, such as the nominal service characteristics as specified in a network subscription. Such information may be available to a network operator but is generally not publicly available, so accessing this information without violating privacy concerns is problematic. Also, in the mobile case, the active network access provider depends on circumstances; for example, the link may be to a wireless LAN or a roaming cellular provider, so that subscription information may be of little relevance. Furthermore, such information is of little value in the mobile environment generally, since performance is highly dependent on many environmental parameters that vary significantly with respect to nominal performance, and information about these environmental conditions can be obtained directly through observations collected by the Client. Subscriber parameter database