Applying Thoughts

"Sometimes I Win, Other times I learn. but I never lose."
Showing posts with label Telecommunication. Show all posts
Showing posts with label Telecommunication. Show all posts

April 25, 2014

ConceptWave Setup & Debug

ConceptWave contains a set of services and tools that helps to build, deploy and manage metadata-based solutions. A J2EE Application Server is required for metadata deployment.

Applications are metadata-based, which is developed in Velocity Studio, an IDE. It can run the metadata, which is capable of serving the web interface of the application without any external application server. An Oracle DB is required to run the application.

·        ConceptWave Installation and Configuration
•Install JDK:
JDK 1.5 or JDK 1.6 or higher
•Oracle Express Edition
        Any version 10+
·     Debugging Skills of ConceptWave
   Step 1. Right-Click the script,click on the menu of Debug Script.
   Step 2. Initialize the input parameter’s value.

      Step 3. debug

Debugging Framework

Step 1.
Debugging Framework

Step 2. Start up the JSDebugger

Step 3. Set the break point.•Another way of set the break point. Click the menu of More Windows

Step 4: Select the script which you want to debug, then click the ”Select” button.

April 13, 2014

BSS vs OSS

OSS stands for Operational Support Systems.
BSS stands for Business Support Systems.

What are Operational Support Systems?
Software (occasionally hardware) applications that support back-office activities which operate on telecom’s network, provision and maintain customer services.
OSS is traditionally used by network planners, service designers, operations, architects, support, and engineering teams in the service provider. Increasingly product managers and senior staff under the CTO or COO may also use or rely on OSS to some extent.
What are Business Support Systems?
Software applications that support front office activities such as customer interactions. Billing, order management, customer relationship management, call centre automation, are all BSS applications.
BSS may also encompass the customer-facing veneer of OSS application such as trouble-ticketing and service assurance – these are back-office activities but initiated directly by contact with the customer.
This basic relationship between OSS and BSS, where OSS is passed service orders and supplies service assurance information to the BSS layer is often referred to as ‘Orders Down, Faults Up’.

above. Super simple relationship between OSS and BSS

Is the integration between OSS and BSS clear?
In the past, OSS/BSS had a clearer separation. A common job like capturing a customer order and provisioning it required a simple BSS-to-OSS interface. “Deliver product X to customer Y”. BSS would capture the order, set-up the billing and pass the order to OSS for fulfillment.
Now, networks and services are more complicated, more flexible, and telcos offer a range of differentiated products. OSS and BSS must liaise over what could be ordered by the customer, based on what service they already had, based on the network they would use, based on current available resources, based on how far they were from the telephone exchange… and so on. Offering a customer a service is now a negotiation between the commercial products managed by BSS and the ability of OSS (and the local network) to deliver certain products.

As a result, a number of systems now straddle OSS/BSS:
·         Service Assurance systems are now integrated across OSS/BSS in order to track service performance and ensure customer service-level agreements (SLA) are met. Service Assurance may also pro-actively identify network failures, initiating resolution action and notifying high-priority customers.

·         Service Catalogs (a.k.a. Product Catalogs) give the telco one place to list products offered to customers and define what network resources can be used to deliver the service. Service Catalogs offer product managers a tool that joins-up the service offering and fulfillment processes across BSS and OSS.

·         Service Management applications allow greater interaction between OSS and BSS processes when the service order and fulfillment process is complex. If a service order comprises multiple technical resources, which are delivered by multiple OSS systems, Service Management is responsible for orchestrating the fulfilment process and keeping the customer-facing team informed about progress, changes or deliver issues.

For more information, please refer to below links:

September 13, 2013

mHealth (aka mobile health)

Mobile eHealth or mHealth broadly encompasses the use of mobile telecommunication and multimedia technologies as they are integrated within increasingly mobile and wireless health care delivery systems.The field broadly encompasses the use of mobile telecommunication and multimedia technologies in health care delivery.
The term mHealth was coined by Professor Robert Istepanian as use of "emerging mobile communications and network technologies for healthcare". 

A definition used at the 2010 mHealth Summit of the Foundation for the National Institutes of Health (FNIH) was "the delivery of healthcare services via mobile communication devices".


mHealth (aka mobile health) is a term used for the practice of medicine and public health, supported by mobile devices. The term is most commonly used in reference to using mobile communication devices. The mHealth field has emerged as a sub-segment of eHealth, the use of information and communication technology (ICT). mHealth applications include the use of mobile devices in collecting community and clinical health data, delivery of healthcare information to practitioners, researchers, and patients, real-time monitoring of patient vital signs, and direct provision of care (via mobile telemedicine). 

Many of these technologies, while having some application to low- and middle-income nations, are developing primarily in high-income countries. However, with broad advocacy campaigns for free and open source software (FOSS), applications are beginning to be tailored for and make inroads in low- and middle-income countries. Some other mHealth technologies include:

1. Patient monitoring devices
2. Mobile telemedicine/telecare devices
3. MP3 players for mLearning
4. Laptop computers
5. Microcomputers
6. Data collection software
7. Mobile Operating System Technology


Mhealth has two service components:


1) CHM (Converged Health Management) will support capturing of health data from patients for one or more medical conditions by utilizing specialized, remotely available mobile biometric devices. The collected health data would then be analyzed and correlated with other available health data to suggest ways to improve management of the specific condition and overall health. In addition, informational messages would be sent with the intent to promote healthy habits by positively influencing patients’ behavior and choices.


2) VV (Virtual Visit) will provide a virtual face-to-face environment for delivery of health services by healthcare professionals, when an actual face-to-face interaction between patient and physician is not possible or is cost prohibitive

Some of the emerging trends in mHealth


1. Emergency response systems (e.g., road traffic accidents, emergency obstetric care)
2. Human resources coordination, management, and supervision
3. Mobile synchronous (voice) and asynchronous (SMS) telemedicine diagnostic and decision support to remote clinicians
4. Clinician-focused, evidence-based formulary, database and decision support information available at the point-of-care
5. Pharmaceutical Supply Chain Integrity & Patient Safety Systems (e.g. Sproxil and mPedigree)
6. Clinical care and remote patient monitoring
7. Health extension services
8. Health services monitoring and reporting
9. Health-related mLearning for the general pub
 


The global healthcare services market is forecast to reach $3 trillion by 2015, according to research from Global Industry Analysts. Investment in sectors such as home healthcare, healthcare IT and telehealth are expected to continue fuelling market expansion. Due to the world’s aging population, the demand for home healthcare is likely to continue climbing over the years to come.

The M2M mHealth Market Revenue will reach $138 billion by 2020
BOSTON, July 18, 2013 /PRNewswire
Source- http://www.prnewswire.com/news-releases/strategy-analytics-verizon-partner-program-highlights-increased-mobile-operator-focus-on-mhealth-solutions-216051861.html


http://www.mhealthnews.com/