TMCnews Featured Article
Innovate and Bypass Legacy IN Change Requests Using a Service Broker
By TMCnet Special Guest
Michel Arrede, Marketing, Amdocs jNetX
The lack of flexibility in service providers’ proprietary legacy systems has seriously hindered service innovation in the telecom market. But by using a Service Broker to break the barrier between the core network and the applications layer, service providers are now able to combine all their network assets in a new possible way. In other words, by using a Service Broker, service providers can now offer any service to any subscriber.
For a long time, traditional Network Equipment Providers (NEPs) were not in favor of having this separation between the core network and the applications layer and obviously this limited the service innovation. However several Tier 1 services providers have now adopted Service Broker in their network and are heavily benefiting from this new flexibility. There is no more doubt; Tier 1 service providers have a clear need for a Service Broker, and Service Broker is opening the door of service innovation.
The Service Broker sits between the core network and the applications layer and enables the blending of any IN, IMS and Web Services network elements simply by configuring specifics rules, even if proprietary implementations have been deployed in your network.
When the Service Broker receives an IN or IMS message either from the core network or from the applications layer, the Service Broker compares the received message with the provisioned rules. If the rules match, then provisioned actions are applied. Obviously, several rules can be provisioned for a specific message received.
So when a change is required either at your core network level or applications layer, instead of asking for a time consuming and very expensive Change Request, you now have the alternative of implementing this change directly in the Service Broker just by configuring some rules.
Deploying a Service Broker guarantees greater agility, enabling you to rapidly combine your network assets and create value for your customers. At the same time, the Service Broker provides the solution for harmonizing your service plane, centralizing your network infrastructure and replacing proprietary legacy IN systems.
On the business side, the Service Broker helps in two ways. First, you will be able to monetize all your network assets, which will result in revenue growth. And secondly, by removing all the proprietary aspects in your network, you will be able to dramatically reduce operating expenses.
By taking the control of your application roadmap, you will have the ability in your hands to satisfy your subscribers and gain market share against your competitors.
About Amdocs (News - Alert) jNetX Service Broker
The Amdocs jNetX Service Broker enables end users to decide which set of applications they want to use. As an example, prepaid users are now free to subscribe simultaneously to additional services such as Ring Back Tone, Personal Call Management, Parental control, Ring Back When Free, VPN and so on. The result is increased revenues for service providers, reduced cost and considerably improved time to market.
The Amdocs jNetX (News - Alert) Service Broker breaks the technical barriers that prevent multiple services from multiple vendors to be simultaneously subscribed and delivered to the end user. It enables service interaction between a combination of independent:
-- IN services or features (IN Mediation)
-- SIP/IMS services or features (SCIM)
-- Internet/Web Services
The Amdocs jNetX Service Broker is used to consolidate, in real-time, the interaction of services that are running within the Amdocs jNetX Service Broker and/or outside of it (external applications servers). When external applications or features are involved, the Amdocs jNetX Service Broker takes care of the appropriate protocol conversion. As a consequence, service providers can reuse their legacy IN applications in an IMS environment and vice versa and easily bridge IN and IMS services together with Web Services and/or SOA. Additionally the Amdocs jNetX convergent technology enables:
-- The Amdocs jNetX Service Broker to simultaneously communicate with Online or Offline Charging Systems (e.g. over Diameter Ro and Rf), with User Data Repositories (e.g. over Diameter Sh, Radius and LDAP) or with any other network elements that are required.
-- The Amdocs jNetX Service Broker to simultaneously host any communications applications. Amdocs jNetX offers a large portfolio of commercial-off-the-shelf (COTS) communications applications that provide rich communications services, but at the same time enable services providers to replace their existing legacy IN applications (such as VPN, NTS (News - Alert) (News - Alert), etc.) that are well on their way to reaching their respective end of life.
-- Finally, the Amdocs jNetX Service Broker can easily evolve to an Amdocs Prepaid solution or to an Amdocs Convergent Charging solution. The overall goal is to facilitate a smooth replacement of costly and inflexible legacy IN prepaid systems with the new generation of Amdocs Prepaid or Amdocs Convergent Charging systems.
Many service providers that are currently using the Amdocs jNetX Service Broker started by combining IN or SIP services together with their existing and legacy Prepaid IN.
TMCnet publishes expert commentary on various telecommunications, IT, call center, CRM and other technology-related topics. Are you an expert in one of these fields, and interested in having your perspective published on a site that gets several million unique visitors each month? Get in touch.

TMCnet LOGIN
Webinars
