Telecom Application Solutions

Integrated Service Platform (ISP Solution) Such architecture provide fundamental platform for application customization and new application.
Mainly the platform consists of 5 elements:
Core Running Environment: provide open message based distribution frame as the backbone bus for all application module and other functional modules;

Application/Service and Service Logic Execution Environment: provide different customized application/services and the corresponding service logic entity. Actually, service logic in application side is the same as Service Logic Execution Environment, and the only different is that: SLEE element takes the abstraction of common service logic elements for purpose of easy deployment and re-use. Library in SLEE is expandable and upgradeable.

Network Adaptation Module: provide access way to different network element. They are expandable and upgradeable to provide more access ways through telecom network. The module converts the information from different network elements to unique message that can be exchanged and processed by other modules over message bus.

Portals: provide access ways through IP network such as Internet/WAP/GPRS. It can incorporate different Portals as Portlets and form one unified Portal for single sing-on and other purpose. Anyway, depending on different requirements, several category portal can be deployed for different user group, such as: O&M Portal, Content Management Portal, User Portal etc.

Charging Module: it is an optional module that depends on the actual requirement. If needed, it provides different charging modes for different kinds of traffic and application, such as: transaction, session and others. It also incorporates one charging gateway to provide adaptation to charging elements from network side, mainly two categories: CDR mechanism for postpaid charging and real-time mechanism for prepaid charging. Even if the charging function is invalid, the corresponding service data is still recorded and statistics is generated for settlement and other purpose.

Content Management System (CMS)

Content becomes the most important services once 3G network provide more bandwidth for end users. And a lot of operators start to build centralized Service Delivery Platform (SDP) and even centralized Content Management System (CMS) to speed up the time to market for different media and contents. But depending on the actual marketing situation, dedicated and distributed Content Management Platform for Content/Application Provider side is still good choice for easy management and control.

The design of CMS considers the integrated design with operator’s SDP, and some functional module can be independent ones incorporated inside CMS or integrated with ones inside operator’s SDP, mainly: DRM, Content Adaptation Engine, Device Management and Data, Portal channels.

The incumbent part of CMS includes 3 parts:

Content Creator: centralized management interface for content administrator or use to create content based on the material on hand and different service model. Each content item must be granted with certain attributes for further deployment and usage.

Content Gateway/Service Plug-In: content can be local data or from foreign system (3rd Party), or even from real-time service Plug-In module. To achieve this design, the universal addressing mechanism is deployed with XML attributes for each valid content resource. Corresponding to each valid address of content item, different content gateway is invoked based on the content attributes, such as: Content GW to Local DB, Content GW to remote DB (Pull Mode), Content GW to Service Plug-In to acquire the output with/without input message, etc. And Content GW is design in duplex mode, that means: foreign system from 3rd Party side can also send Pull content request and CMS system will Push the corresponding content to them with certain authentication procedure.

Content Portal: It just provide unified interface to different administrator and user to management and use the CMS. If no user portal is deployed and integrated by SDP side, user portal can also be built up for access of end users through IP channel. Rendering function is provided for mobile Portal like WAP Portal.

There are another three modules that can be integrated with existing SDP or can be part of CMS:

DRM: Digital Right Management module provides tools to label the content with DRM tags. API should be provided if SDP DRM is deployed.

Content Adaptation Engine: Content Adaptation Engine provides Transcoding engine to accommodate different requirements on different terminals. It works for picture, audio, video or text encoding. Content Adaptation works in accordance with Device Management module so that any adaptation is done based on the profile of subscriber’s current terminals.

Device Management: especially for mobile network, diversity of mobile device is always a challenge. To delivery the proper content in a proper way, CMS must choose or adapt the content to cater for the proper device capability of end users.

Mobile Value Added Service Platform (VAS)

Based on our open & flexible architecture and framework, we offer rich value-added services, including voice and data service such as VAS platform, prepaid service, calling card service, missed call service, roaming service, SMS/MMS gateway, SMS/MMS VAS platform, Enterprise SMS/MMS system, Call Center, VoIP system, etc,. We also provide Entertainment and Games applications. These services span the entire development lifecycle from original requirements collecting, system design, requirement analysis, development and deployment.

We have expertise in building mobile value-added service, Handset and PDA applications. We provide our customers with excellent products and services. These products and services are focused on mobile operator, mobile service provider and enterprise user.

Multi-Channel Access Portal System (MAPS)

Multi-Channel access portal means user portal for subscriber to preview/request/subscriber the services. At present, we can provide three kinds of user Portals: Web Portal, WAP Portal and VXML based Voice Portal. The Portal can also incorporate the existing different Portals as Portlet to form the unified Portal.