Linkage policy implementation method and apparatus, open platform board, and device

US9413592B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9413592-B2
Application numberUS-201313962603-A
CountryUS
Kind codeB2
Filing dateAug 8, 2013
Priority dateApr 14, 2011
Publication dateAug 9, 2016
Grant dateAug 9, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Embodiments of the present invention disclose a linkage policy implementation method, which includes: receiving, by a linkage proxy module, a linkage policy request delivered by a third-party application service; calling a corresponding protocol converter according to a protocol identifier in the linkage policy request, and performing protocol conversion for the linkage policy request to convert it into a linkage policy request in a set protocol format; and sending the protocol-converted linkage policy request to a linkage client to instruct the linkage client to parse the linkage policy request based on the set protocol and execute linkage policy configuration. With the present invention, a linkage proxy is set to execute protocol conversion of various protocols. Therefore, the cost of the linkage client would not be increased for supporting multiple protocols; and when third-party applications are increased or decreased, it is unnecessary to reconfigure the linkage client.

First claim

Opening claim text (preview).

What is claimed is: 1. A linkage policy implementation method applied in a device configured with a main control board and an open platform board, wherein the open platform board comprising a linkage proxy module, the linkage policy implementation method performed by the linkage proxy module, comprising: receiving an application registration request delivered by a third-party application service; obtaining a protocol identifier according to the application registration request; obtaining a corresponding protocol converter identifier according to the obtained protocol identifier, and adding the obtained protocol identifier and the corresponding protocol converter identifier to a protocol converter global table; receiving a first linkage policy request delivered by the third-party application service, wherein the first linkage policy request is in a format of a first protocol, the first protocol format that is currently used by the third-party application service; calling a corresponding protocol converter according to a first protocol identifier in the first linkage policy request, and performing a protocol conversion for the first linkage policy request to convert the first linkage policy request into a second linkage policy request in a format of a second protocol, wherein the second protocol format that is currently used by the main control board; and sending the protocol-converted second linkage policy request to a linkage client integrated in the main control board, to instruct the linkage client to parse the second linkage policy request based on the second protocol format and execute linkage policy configuration; wherein sending the protocol-converted second linkage policy request to the linkage client to instruct the linkage client to parse the second linkage policy request based on the second protocol format and execute the linkage policy configuration comprises: adding the application identifier to the protocol-converted second linkage policy request, wherein the application identifier corresponds to the third-party application service; sending the second linkage policy request carrying the corresponding application identifier to the linkage client to instruct the linkage client to parse the second linkage policy request based on the second protocol format and execute the linkage policy configuration; receiving a linkage policy response generated by the linkage client for executing the linkage policy configuration; and calling, according to the corresponding application identifier comprised in the linkage policy response, the corresponding protocol converter to perform the protocol conversion for the linkage policy response, and returning the corresponding protocol-converted linkage policy response to the corresponding third-party application service. 2. The linkage policy implementation method according to claim 1 , wherein after the linkage proxy module receives the application registration request delivered by the third-party application service, the method further comprises: generating the corresponding application identifier for the third-party application service delivering the application registration request, and correspondingly storing the generated corresponding application identifier, the obtained protocol identifier and the corresponding protocol converter identifier in the protocol converter global table. 3. The linkage policy implementation method according to claim 1 , wherein the corresponding protocol converter identifier is a protocol converter program pointer. 4. The linkage policy implementation method according to claim 1 , wherein the receiving the first linkage policy request delivered by the third-party application service comprises: receiving, through a third-party interface corresponding to a different format of the first protocol format, the first linkage policy request delivered by the third-party application service. 5. The linkage policy implementation method according to claim 4 , wherein the calling, by the linkage proxy module, the corresponding protocol converter according to the first protocol identifier in the first linkage policy request comprises: collecting an interface type in the first linkage policy request, and using the interface type as the first protocol identifier; and querying, according to the collected interface type, the protocol converter global table for the corresponding protocol converter for calling. 6. The linkage policy implementation method according to claim 1 , wherein the first linkage policy request is an event registration request, and before the linkage proxy module sends the protocol-converted second linkage policy request to the linkage client, the method further comprises: parsing the first linkage policy request to obtain an event of interest, and recording the obtained event of interest corresponding to the corresponding application identifier; and after sending the protocol-converted second linkage policy request to the linkage client to instruct the linkage client to parse the second linkage policy request based on the second protocol format and execute the linkage policy configuration, the method further comprises: when receiving the recorded event of interest reported by the linkage client, constructing an event notification message according to the recorded event of interest; and calling, according to a mapping between the recorded event of interest and the corresponding application identifier, and according to the corresponding application identifier, the corresponding protocol converter to perform the protocol conversion for the constructed event notification message, and returning the protocol-converted event notification message to the corresponding third-party application service to trigger the third-party application service to execute a callback function. 7. The linkage policy implementation method according to claim 6 , the method further comprises: when the linkage proxy module receives an event deregistration request, wherein the event deregistration request comprises the recorded event of interests, clearing the recorded event of interest corresponding to the corresponding application identifier. 8. A linkage proxy module, comprising: one or more processors coupled to a memory; wherein the memory storing processor-executable instructions, and the processor-executable instructions when executed causes the one or more processors to perform a process that comprises: receiving an application registration request delivered by a third-party application service; obtaining a protocol identifier according to the application registration request; obtaining a corresponding protocol converter identifier according to the obtained protocol identifier, and adding the obtained protocol identifier and the corresponding protocol converter identifier to a protocol converter global table; receiving a first linkage policy request delivered by the third-party application service, wherein the first linkage policy request is in a format of a first protocol, the first protocol format that is currently used by the third-party application service; calling a corresponding protocol converter according to a first protocol identifier in the first linkage policy request, and performing a protocol conversion for the first linkage policy request to convert the first linkage policy request into a second linkage policy request in a format of a second protocol, wherein the second protocol format that is currently used by the main control board; sending the protocol-converted second linkage policy request to a linkage client integrated in the main control board, to instruct the linkage client to parse the second linkage policy request based on the second protocol and execute a

Assignees

Inventors

Classifications

  • H04L69/08Primary

    Protocols for interworking; Protocol conversion · CPC title

  • Policy-based network configuration management · CPC title

  • Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title

  • using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title

  • Mapping or translating multiple network management protocols · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9413592B2 cover?
Embodiments of the present invention disclose a linkage policy implementation method, which includes: receiving, by a linkage proxy module, a linkage policy request delivered by a third-party application service; calling a corresponding protocol converter according to a protocol identifier in the linkage policy request, and performing protocol conversion for the linkage policy request to conver…
Who is the assignee on this patent?
Huawei Tech Co Ltd
What technology area does this patent fall under?
Primary CPC classification H04L69/08. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 09 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).