archive-org.com » ORG » X » XPDR.ORG

Total: 20

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Analytics Layer — XPDR.ORG
    the user experience An RF engineer probably knows at least theoretically but with thousands of such values being reported on a regular basis it is nearly impossible to manually develop a health model for all circumstances that the various statistics convey That is where the Analytics Layer comes in With access to both the values from networked devices and customer feedback automated speed test results customer surveys calls to customer support etc it is possible to draw conclusions by correlating source data with results data to draw conclusions that can be used to improve the self healing process as well as to improve customer education and customer support procedures Besides improving the customer experience all of the same data can be used to produce sophisticated business intelligence knowledge that can be used to determine ways to improve profitability on existing business lines identify opportunities for other service tiers or business lines and collect information on the key benefits that users find particularly valuable so that promotional efforts can focus on those benefits To facilitate this level of analysis the Analytics Layer specifies that collected data should be stored in big data NoSQL datastores e g Cassandra Mongo HBase and processed

    Original URL path: http://www.xpdr.org/analytics-layer/ (2016-04-28)
    Open archived version from archive


  • Escalation Layer — XPDR.ORG
    this problem once and for all by ensuring that problems are escalated transferred and collaboratively resolved by all parties that are involved in the user experience A simple knowledge base is loaded with directives on the routing of customer problems through responsible vendors network service provider device manufacturer application vendor etc Tickets can be manually re routed based on evaluation by each vendor s support tiers And when necessary audited

    Original URL path: http://www.xpdr.org/escalation-layer/ (2016-04-28)
    Open archived version from archive

  • Participate — XPDR.ORG
    Analytics Layer Escalation Layer Participate Contact News XPDR Is Only As Good As Its Members That said XPDR s membership arrangements are still being finalized Please check back here to keep current on the latest status There will be various levels of membership based on the amount your organization plans to participate and the amount of support your organization will need but the basic membership that gains you access to

    Original URL path: http://www.xpdr.org/participate/ (2016-04-28)
    Open archived version from archive

  • Contact — XPDR.ORG
    Is XPDR XPDR Reference Architecture Local Layer Fabric Layer Control Layer Self Healing Layer Analytics Layer Escalation Layer Participate Contact News XPDR org is currently managed by RefractN LLC If you haven t please visit their web page and if

    Original URL path: http://www.xpdr.org/contact/ (2016-04-28)
    Open archived version from archive

  • News — XPDR.ORG
    Architecture Local Layer Fabric Layer Control Layer Self Healing Layer Analytics Layer Escalation Layer Participate Contact News Home About What Is XPDR XPDR Reference Architecture Local Layer Fabric Layer Control Layer Self Healing Layer Analytics Layer Escalation Layer Participate Contact

    Original URL path: http://www.xpdr.org/news-aviator/ (2016-04-28)
    Open archived version from archive

  • XPDR Reference Architecture — XPDR.ORG
    in the decades since As influential as the OSI reference model was it is worth noting that almost no one uses any of the protocols that were developed by those committees to implement that model but the model itself stood the test of time because it accurately predicted the various problem domains that a diverse set of networking technologies would have to navigate and allowed different vendor to tailor their specific solutions to those needs while still interoperating with the technologies other vendors provided at other levels This is the goal of the XPDR reference model It s founding member RefractN has developed specific technologies and protocols minor extensions really of existing industry standards to address current problems dealing with efficient transport of management information and enabling self healing capabilities within intelligent devices But the problem is much broader than simply transporting data and as powerful the idea is to empower devices to take charge of their own health under the tutelage of a hands off central server there are still problems to solve at other layers There may be better solutions at the layers that RefractN has proposed So in the best spirit of OSI s seven layer model we propose the XPDR Reference Model and its own layers each designed to address the specific realms they are defined to cover Several of the layers run end to end across the network from the back office to the local network The Local Layer Covers communications with devices in the home branch office or remote site The Fabric Layer Provides high efficiency low latency reliable communication of a variety of kinds of data with security scalability and complete failover support The Control Layer Responsible for data integrity across the network ensuring that upstream data is reliably delivered to the right

    Original URL path: http://www.xpdr.org/55833bbee4b06d2f27907976 (2016-04-28)
    Open archived version from archive

  • Local Layer — XPDR.ORG
    to be functioning optimally to provide the best user experience The local layer provides an interface between those disparate local environments and the various other components in the architecture that can use their health data to improve the user experience It manages applications and devices in the following areas Home automation and security Video set top boxes game systems Oil and gas instrumentation Remote medical devices And many others The

    Original URL path: http://www.xpdr.org/local-layer (2016-04-28)
    Open archived version from archive

  • Fabric Layer — XPDR.ORG
    TR 069 is based on SOAP a heavy weight human readable format that is network inefficient because of its text encoding and as much as 90 overhead in headers IPDR is binary encoded and has very low protocol overhead SNMP is oriented towards transmitting a single data item at a time Though there are mechanisms to collect more than one data element at a time they require a complete transmission of the requested items at the time of the request IPDR uses templates to define sets of data to be transmitted in bulk and it is only necessary to transmit a single request for all data in a template Both TR 069 and SNMP are server driven While TR 069 allows for scheduled exports of a single set of data IPDR supports periodic transmission of a variety of templates of data XPDR goes above and beyond IPDR which is primarily focused on transferring large quantities of bulk data for multiple devices and provides even more efficiency and capability XPDR separates template negotiation from data transmission IPDR requires that a template describing the data to be transmitted be negotiated on each transmission XPDR negotiates templates out of band ahead of time so that data transfers are immediate without the extra overhead of negotiating templates that rarely change Data encoding goes beyond the standard XDR and recognizes that many data fields are the same from one transmission to another and de dups those data fields so that they don t have to be transmitted repeatedly XPDR s data encoding improves upon XDR again by performing ASN 1 type encoding of numeric values ensuring that they are as short as possible regardless of type declaration The RefractN XPDR implementation supports automatic device exports based on triggers defined in profiles passed down along with

    Original URL path: http://www.xpdr.org/fabric-layer (2016-04-28)
    Open archived version from archive



  •