Subscriber Record Segmentation for Service Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current HLR systems face challenges in efficiently managing and provisioning a large number of customized applications services for subscribers, as they require a high number of separate COS records, which becomes impractical when operators need to offer numerous service packages and versions.

Innovation Solution

The implementation of a system where each subscriber record includes references to multiple specific COS records for different types of customized application service subscriber information, reducing the need for separate COS records by using a general COS record and type-specific COS records, with the ability to generate a unique subscriber ID from these references.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate COS records are used for each customized application service type, then service customization capability is improved, but device complexity and record management burden increase

Engineering Contradiction:
Improveservice customization capabilityVSAvoidrecord management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the CAMEL subscriber information into two distinct parts: a general COS record containing common service parameters and multiple type-specific COS records containing service-specific parameters. This segmentation allows the system to maintain detailed service customization capability while reducing overall record management complexity through structured organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The general COS record serves as a universal container that holds common service parameters applicable to all CAMEL service types. This multi-functional design eliminates redundancy by allowing the same general record structure to support multiple service types, thereby reducing the total number of records needed while maintaining customization capability.

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

2Adaptability or versatility

If multiple separate COS records are maintained for different service types, then service diversity is improved, but loss of time in provisioning increases

Engineering Contradiction:
Improveservice diversityVSAvoidprovisioning time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing the relationship between the general COS record and multiple type-specific COS records during system configuration. This pre-organized structure allows rapid provisioning of new service packages without requiring time-consuming reconfiguration of individual records, as the system can quickly reference and combine existing record templates.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If a single general COS record is used for all service types, then device complexity is reduced, but service customization capability deteriorates

Engineering Contradiction:
Improverecord structure simplicityVSAvoidservice customization capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent applies segmentation by dividing the COS record into a general part (common to all service types) and multiple type-specific parts (different for each service type). This segmented structure maintains simplicity in the general record while enabling detailed customization through the type-specific records, resolving the contradiction between simplicity and customization capability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10492040B2Subscriber record referencing class of service records
Publication Date: 2019.11.26 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10492040B2 patent drawing
  • US10492040B2 patent drawing
  • US10492040B2 patent drawing

AI summary

A subscriber record may include a plurality of references to a plurality of specific class of service records. Each class of service record may relate to a different type of customized applications service subscriber information.