Service Control Device Traffic Identification Handover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless communication, when a user equipment hands over between service control devices, the target service control device lacks flow identification information, leading to difficulties in identifying traffic types, which burdens the device and can result in failed traffic type identification, affecting bandwidth control and network security.

Innovation Solution

A method where the source service control device obtains flow identification information for a service flow and synchronizes it to the target service control device during handover, enabling the target device to identify the traffic type using the synchronized information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If association identification method is used for traffic type identification, then traffic type can be identified when user equipment is connected to source service control device, but traffic type identification fails when user equipment hands over to target service control device

Engineering Contradiction:
Improvetraffic type identification reliabilityVSAvoidadaptability to handover between service control devices
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The source service control device performs preliminary action by obtaining and caching flow identification information before handover occurs. This cached information is then transferred to the target service control device, enabling the target device to identify traffic types without needing to perform new detection after handover.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Flow identification information acts as an intermediary that bridges the source service control device and target service control device. This information is transferred between devices during handover, allowing the target device to inherit the traffic identification capabilities of the source device without direct communication between them.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If target service control device performs traffic type identification from scratch after handover, then it can identify traffic types independently, but this brings burden to the device and may lead to identification failure

Engineering Contradiction:
Improveindependence in traffic type identificationVSAvoidcomplexity of traffic type identification process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The target service control device obtains a copy of the flow identification information that was originally obtained by the source service control device. This copying approach allows the target device to inherit identification capabilities without performing complex detection procedures, reducing device burden while maintaining identification independence.

Inventive Principle:
Principle #26Copying

3Productivity

If flow identification information is cached in storage device for association identification, then traffic type identification is efficient, but this information is not available after handover between service control devices

Engineering Contradiction:
Improvetraffic type identification efficiencyVSAvoidloss of flow identification information during handover
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The source service control device performs preliminary action by obtaining and caching flow identification information before handover occurs. This cached information is then transferred to the target service control device, enabling the target device to identify traffic types without needing to perform new detection after handover.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The flow identification information is transferred from source to target service control device during handover, ensuring continuity of the identification capability. This allows the useful action of traffic type identification to continue uninterrupted across device transitions, maintaining both efficiency and information availability.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS9872207B2Method, device, and system for identifying traffic type across devices
Publication Date: 2018.01.16 XFUSION DIGITAL TECH CO LTD
  • US9872207B2 patent drawing
  • US9872207B2 patent drawing
  • US9872207B2 patent drawing

AI summary

A method, a device, and a system for identifying a traffic type across devices are provided, where the method includes: obtaining, by a source service control device, flow identification information of a service flow transmitted between a user equipment and a network; and synchronizing the obtained flow identification information to a target service control device when detecting that the user equipment is handed over from the source service control device to the target service control device to transmit the service flow with the network, so that the target service control device identifies, according to the flow identification information, the traffic type of the service flow transmitted between the user equipment and the network. Thus an operator is facilitated to implement network service control such as bandwidth control and virus prevention efficiently without changing an existing architecture.