| |
|
|
|
|
| |
||||
| |
![]() |
|||
| |
||||
|
|
MetraTech History The team thus decided to create a radical, new approach. They set the design bar high: to develop a protocol that would enable services with completely different data profiles and business models to be defined on-the-fly and without coding. MSIX to XML to SOA HTML, a derivative of SGML, was simple, extensible, and made use of natural-language identifiers. HTTP enabled trouble-free network connectivity. Shouldn’t it be possible, they concluded, to derive an HTML-like protocol from SGML that enabled network elements and applications to connect to Business Support Systems (BSS) in a similarly seamless fashion? In 1996, the team developed the Metered Services Information eXchange (MSIX) protocol. It was derived from SGML and used natural-language identifiers to dynamically define and submit service usage. Using HTTP/SSL for network connectivity and security, MSIX transactions could be safely and seamlessly transmitted across corporate networks or the Internet. The team submitted MSIX to the IETF in 1998, and it was embraced by IP-centric technologists. However, the majority of people with whom we shared it with at that time viewed it as a “stupid idea.” It should be noted that in 1998 the W3C released the first draft of XML, which was also derived from SGML and is substantially similar to MSIX. Recently, Service-Oriented Architecture (SOA) has become the Holy Grail of the OSS/BSS market and this is exactly what the MetraNet has been doing since 1996. Applied Imagination™ Existing product solutions, while claiming to be flexible, are essentially hardwired, resulting in massive costs and significant risks when implementing a customer requirement that the vendor has not explicitly designed its system to support. To solve this fundamental problem, MetraNet was architected to support the invention of new services via a dynamic, metadata-driven engine that provides a custom system without coding or compromising. Since XML was becoming the business language of the Internet and MetraNet’s APIs were XML-based, we chose XML as our metadata implementation technology. MetraNet, now in version 5.0, is completely metadata-driven. Using MetraNet, a product manager is able to invent a service and enter the Service Definition into a web page. Then, MetraNet will do the rest – dynamically generating a database schema, a workflow, a set of web GUIs, and SOA-compliant APIs in a matter of minutes. These dynamic services have been used for a wide-range of OSS/BSS operations including: rating usage events, supporting advice of charge inquires, calculating revenue shares and commissions, creating accounts, provisioning satellite TV viewing rights, IN-based SIM card activation, etc.
Figure 1: Billing Market Evolution
Stupid Network and Stupid BSS In summary his thesis argues that the IN is intelligent and therein lies its problem: The IN tells the data what to do. IP, on the other hand, lets the data tell the network what to do. Thus, Isenberg coined the term “Stupid Network” to describe IP. It is this data-up (“stupid”) rather than network-down (“intelligent”) philosophy that has enabled IP to change the world as we know it. It is also why IP, by definition, is at the core of all SOA and IMS (IP Multimedia Subsystem) solutions. Isenberg correctly predicted that the “Stupid Network” would lead to services that were “mixed and interspersed at will,” a precursor to IMS Composite Applications. Third-generation BSS products are conceptually similar to the IN. They are flexible within their defined context, but they have a top-down (“intelligent”) view of the world and run into significant issues when attempting to support requirements for which the system was not explicitly designed. A fourth generation BSS platform, on the other hand, is conceptually similar to IP. It has a data-up (“stupid”) view of the world resulting in a “tell me what to do” rather than a “I know what you want to do” philosophy. This is accomplished through the pervasive use of metadata which is used to create dynamic SOA-compliant services and the underlying BSS infrastructure (e.g. database schema, workflows, rules, web GUIs and APIs) to support those services. Thus, “IP is to networks as metadata is to BSS.” A “Stupid BSS” enables service providers to apply the creative services and business model that the “Stupid Network” and IMS promise, namely Applied Creativity. Market Need For example:
Market Recognition
Conclusion Business realities and intense competition continue to validate MetraTech’s innovative, metadata-driven approach to billing and partner management. MetraNet is the platform of choice for companies that demand agility and excellence without compromise. Were our early critics right about our approach? Ironically, yes – in the same way that most dismissed the notion that IP would replace the IN. It was a “stupid” approach, but they completely missed the point. Although other BSS providers have wrapped their third-generation platforms with XML, they have only put a modern veneer on an architecture that tells the data what to do rather than the other way around.
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| © 1998 - MetraTech Corp. All rights reserved. Terms and Conditions | Privacy Policy |