Telecommunication Callback Server Push Protocol Inversion

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Web-based telecommunication capabilities are not applicable to free developers as they require a client device to act as a Web server for callback processing, which is not feasible for most mobile terminals lacking Web server capabilities.

Innovation Solution

Converting the standard callback protocol to an asynchronous 'server push' protocol, where the telecommunication capability providing server pushes callback messages to the client, allowing the client to determine and execute the necessary functions without needing to act as a Web server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the standard callback protocol is used where the telecommunication capability providing server calls the client's Web service address, then callback processing can be achieved for SP servers with Web server capabilities, but the solution becomes inapplicable to free developers whose client devices lack Web server capabilities

Engineering Contradiction:

Improveapplicability to free developersVSAvoidWeb server capability requirement

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent inverts the traditional callback direction: instead of the server calling the client (standard callback), the server pushes messages to the client (server push). This reversal eliminates the need for the client to have Web server capabilities, making the solution applicable to free developers using mobile terminals while maintaining callback functionality.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The patent changes the communication mode parameter from synchronous callback (requiring Web server) to asynchronous server push (no Web server needed). By transforming the protocol from standard callback to server push protocol, the technical solution adapts to clients without Web server capabilities while preserving the essential callback message delivery function.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If a client device acts as a Web server to receive callback calls, then callback processing is enabled, but this requirement cannot be met by most mobile terminals

Engineering Contradiction:

Improvecallback processing capabilityVSAvoidclient device requirement

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent reverses the roles: the server that traditionally calls the client now pushes messages to the client. This inversion removes the burden of Web server implementation from the client device, making mobile terminals capable of receiving callback messages without requiring complex Web server functionality.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces a server push mechanism as an intermediary approach. Instead of direct server-to-client callbacks requiring Web servers, the system uses asynchronous message pushing through the server, which mediates the communication and delivers callback information to clients without requiring them to act as Web servers.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If the telecommunication capability providing server calls the callback interface of the SP server, then message processing can be implemented, but this approach fails when the client cannot act as a Web server

Engineering Contradiction:

Improvemessage processing capabilityVSAvoidcompatibility with client devices

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent changes the communication protocol parameter from synchronous callback to asynchronous server push. This parameter change enables message processing functionality while improving compatibility with diverse client devices, particularly mobile terminals that cannot function as Web servers.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent inverts the message delivery approach: instead of the server calling the client's callback interface (which requires Web server), the server pushes messages to the client (which works without Web server). This inversion maintains message processing capability while expanding device compatibility.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentEP2620872B1Method and device for callback processing in telecommunication capacity opening

Publication Date: 2021.04.07 HUAWEI TECH CO LTD

Figure 1
Figure 2
Figure 3

AI summary

The present invention discloses a method for callback processing in telecommunication capability opening, a telecommunication capability opening server, a client, and a telecommunication capability opening service system. The method includes: receiving a telecommunication capability application programming interface (API) call request sent by a client, where the telecommunication capability API call request includes a callback information parameter; performing callback processing according to the telecommunication capability API call request, and generating a callback message according to the callback information parameter; and pushing the callback message to the client. The method may also include: initiating a telecommunication capability API call request to a telecommunication capability opening server, where the telecommunication capability API call request includes a callback information parameter; receiving a callback message pushed by the telecommunication capability opening server, and parsing the callback message; and determining, according to a parsing result, a function that callback processing needs, and calling the function.