Telephony Service Creation Environment for SIP Message Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telephony service development requires separate processes for generating call control and dialog services in different target languages, leading to increased development time and costs, and existing solutions lack efficient methods for transforming Session Initiation Protocol (SIP) messages between different formats.

Innovation Solution

A graphical user interface and service creation environment that allows users to select and couple call control and dialog elements, transforming them from intermediate languages into target languages using rules, and customizing SIP messages to facilitate interoperability across different formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If separate development processes are used for generating call control and dialog services in different target languages, then each service can be developed with specific language features, but development time and costs increase

Engineering Contradiction:
Improveease of service developmentVSAvoiddevelopment time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent combines call control service generation and dialog service generation into a single integrated development environment. The service creation environment accepts a unified service definition that simultaneously specifies both call control logic and dialog logic, eliminating the need for separate development processes for each service type while maintaining the ability to generate target code in different languages as needed.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The service creation environment is designed as a universal platform that can generate multiple types of services (call control and dialog services) from a single service definition. The system supports multiple target languages and can produce different types of service modules according to the unified definition, making the development process adaptable and multi-functional rather than requiring separate specialized tools for each service type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If separate development processes are used for generating call control and dialog services in different target languages, then each service can be optimized for its target language, but development costs increase

Engineering Contradiction:
Improvelanguage-specific optimizationVSAvoiddevelopment process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the service definition into distinct components (call control logic and dialog logic) within a unified service definition structure. This allows the service creation environment to process and optimize each component appropriately for its target language while maintaining overall service integration, reducing development process complexity compared to completely separate development workflows.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service creation environment acts as an intermediary that receives a unified service definition and transforms it into language-specific service modules. This intermediary processing layer enables language-specific optimization to occur automatically during the transformation process, eliminating the need for manual separate development processes while preserving adaptability to different target languages.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If existing methods are used for transforming SIP messages between different formats, then message transformation can be achieved, but the process is inefficient and lacks standardization

Engineering Contradiction:
Improvemessage format compatibilityVSAvoidmessage transformation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a standardized transformation framework that systematically transforms SIP messages between different formats by changing message parameters according to predefined rules. The service definition specifies transformation parameters that map source message formats to target message formats, enabling efficient and consistent format conversion without ad-hoc processing for each message type.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP1886467B1Generating and transforming call control elements, dialog elements, and session initiation protocol messages for telephony service applications
Publication Date: 2010.08.04 SONUS NETWORKS INC
  • EP1886467B1 patent drawingFigure 1
  • EP1886467B1 patent drawingFigure 2~3
  • EP1886467B1 patent drawingFigure 4

AI summary

Described are methods, systems, and apparatus, including computer program products for, in one example, generating call control and dialog elements for telephony service applications using a graphical user interface. A graphical user interface is provided. A module is generated, using the graphical user interface, for telephony applications. The module comprises a call control element and a dialog element. In another example, call control and dialog elements for telephony service applications are transformed from an intermediate language into a target language. The module is stored in an intermediate design file based on one or more intermediate languages. At least a portion of the intermediate design file is transformed into one or more target design files based on one or more target languages. In another example, a session initiation protocol message is transformed from a first format into a second format. A set of one or more instructions is associated with a rule. A session initiation protocol message is received. The first set of one or more instructions are determined to be applicable or not to the session initiation protocol message. The session initiation protocol message is transformed, using the first set of one or more instructions, into a target session initiation protocol message based on a second format.