System and device for enabling any network functionality client or server in a html5 application

Patent metadata

Field	Value
Publication number	US-2016205185-A1
Application number	US-201615049328-A
Country	US
Kind code	A1
Filing date	Feb 22, 2016
Priority date	Aug 23, 2013
Publication date	Jul 14, 2016
Grant date	—

Abstract

The disclosure relates to a system, comprises a Network Entity running as a HTML5 Application (NEHA), a HTTP server, a network entity (NE), and a mirror network entity (MNE), wherein the NNE is a mirror instance of the NE, a desired network protocol is run between the MNE and the NE, the NEHA is configured for communicating with the NE through the MNE; and the NNE is configured for communicating with the NE using the desired network protocol.

First claim

What is claimed is:

1 . A Network Entity running as a HTML5 Application (NEHA) for use in a system comprising a HTTP server, a network entity (NE) and a mirror network entity (MNE), wherein the MNE is a mirror instance of the NE and a desired network protocol is run between the MNE and the NE, the NEHA comprising:
a first sender configured for sending a first request to the HTTP server for requesting the MNE, wherein the first request indicates the desired network protocol; a first receiver configured for receiving a first response indicating the MNE from the HTTP server; a processing logic configured for creating the first request and processing the first response; and a communicating unit configured for communicating with the NE through the MNE.

2 . The NEHA of claim 1 , wherein the communicating unit comprises:
a second sender configured for sending a message to the MNE; a second receiver configured for receiving a message from the MNE; and wherein the processing logic is further configured for processing the message received from the MNE and creating the message sent to the MNE.

3 . The NEHA of claim 2 , wherein when the NEHA is a client entity for requesting a first service, the NE is a server entity providing the first service, and wherein the message sent to the MNE is a second request for requesting the first service and the message received from the MNE is a second response providing the first service.

4 . The NEHA of claim 3 , wherein:
the desired network protocol comprises network protocols not supported by HTML5, wherein the network protocols not supported by HTML5 comprise Internet Group Management Protocol (IGMP), Internet Protocol Television (IPTV) group protocols, and File Transfer Protocol (FTP); a HTTP protocol is run between the NEHA and the HTTP server, accordingly the first request and the first response are of the HTTP protocol; and wherein the MNE is indicated by a network identity comprising an IP address plus a port number.

5 . The NEHA of claim 2 , wherein when the NEHA is a server entity for providing a second service, the NE is a client entity requesting the second service, and wherein the message received from the MNE is a third request for requesting the second service and the message sent to the MNE is a third response providing the second service.

6 . The NEHA of claim 5 , wherein the desired network protocol comprises at least one of: HTTP, auto discovery and control network protocol, and media auto discovery and control network protocol.

7 . The NEHA of claim 1 , further comprising:
a connection establishing unit coupled to the communicating unit and configured for establishing a persistent connection between the NEHA and the MNE, wherein the message sent to the MNE and the message received from the MNE are transferred over the persistent connection.

8 . The NEHA of claim 1 , wherein a first network protocol is run between the NEHA and the MNE.

9 . The NEHA of claim 8 , wherein the first network protocol comprises at least one of the desired network protocol and a private protocol.

10 . A system comprising:
a Network Entity running as a HTML5 Application (NEHA), a HTTP server, a network entity (NE), and a mirror network entity (MNE), wherein the MNE is a mirror instance of the NE and a desired network protocol is run between the MNE and the NE; wherein the HTTP server is configured for receiving a first request for requesting the MNE from the NEHA, the first request comprising the desired network protocol, and configured for sending a first response indicating the MNE to the NEHA; wherein the NEHA is configured for communicating with the NE through the MNE; and wherein the MNE is configured for communicating with the NE using the desired network protocol.

11 . The system of claim 10 , wherein:
when the NEHA is a client entity, the NE is a server entity; the NEHA is configured for sending a second request for requesting a first service to the MNE and for receiving a second response providing the first service from the MNE; and the MNE is configured for sending a fourth request to the NE for requesting the first service upon the second request received from the NEHA, and for receiving a fourth response providing the first service from the NE, and for sending the second response to the NEHA based on the fourth response.

12 . The system of claim 11 , wherein the NINE is further configured for caching the fourth response, when a latter another request requesting the first service and indicating the desired network protocol is received, the MNE is configured for responding the latter another request directly based on the stored fourth response.

13 . The system of claim 10 , wherein:
when the NEHA is a server entity, the NE is a client entity; the MNE is configured for receiving a fifth request for requesting a second service from the NE, for sending a third request for requesting the second service to the NEHA based on the fifth request, and for sending a fifth response providing the second service to the NE based on a third response providing the second service received from the NEHA; and the NEHA is configured for receiving the third request from the MNE, and for sending the third response to the MNE based on the third request.

14 . The system of claim 13 , wherein the MNE is further configured for caching the third response, when a latter another request requesting the second service, the MNE is configured for responding the latter another request directly based on the stored third response.

15 . The system of claim 1 , wherein the MNE is further configured for communicating with the NEHA using the first network protocol, and, for converting a message sent by the NEHA from the first network protocol to the desired network protocol and for converting a message to-be-sent to the NEHA from the desired network protocol to the first network protocol, when the first network protocol and the desired network protocol are different.

Assignees

• Huawei Tech Co Ltd

Inventors

• Gampel Eran
• Molkho Adi
• Shraga Eyal
• Senderovich Amnon

Classifications

• H04L69/08

  Protocols for interworking; Protocol conversion · CPC title

• H04L67/1095 Primary

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L61/2007

  Electricity · mapped topic

• H04L61/5007

  Internet protocol [IP] addresses · CPC title