1 / 7

802.16.3 lmap

802.16.3 lmap. 23 Feb 2015. Lmap Overview. Current lmap Use Cases Scenario (From draft-ietf-lmap-use-cases-05.pdf)

twyla
Download Presentation

802.16.3 lmap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 802.16.3 lmap 23 Feb 2015

  2. 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. Comparison lmap vs 802.16.3Functional Entities +-----------+ +-----------+ ^ |End useror| |End useror| | |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 2: Application of Architectural Reference Model Figure 1: Schematic of main elements of an LMAP-based Measurement System

  4. P802.16.3 vs lmapFunctional Entities

  5. 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 • Client to Controller registration • Public/Private Server to Controller registration • CONFIGURATION • Controller to Client configuration • Controller to Controller configuration • Controller to Server configuration • MEASUREMENT SYNCHRONIZATION • Client to Controller Commands synchronization • Public/Private Server to Controller Commands synchronization • MEASUREMENTS UPLOAD • Flow control between Client (or Server) and Data Collector. • Measurements upload from Client to Data Collector • Measurements upload from Public/Private Server to Data Collector • DEREGISTRATION • Client to Controller Deregistration • Public/Private Server to Controller Deregistration

  6. P802.16.3 vs lmapInformation 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: • 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. P802.16.3 vs lmapCooperation

More Related