Nothing Special   »   [go: up one dir, main page]

US20150200997A1 - Communication system utilizing http - Google Patents

Communication system utilizing http Download PDF

Info

Publication number
US20150200997A1
US20150200997A1 US14/669,622 US201514669622A US2015200997A1 US 20150200997 A1 US20150200997 A1 US 20150200997A1 US 201514669622 A US201514669622 A US 201514669622A US 2015200997 A1 US2015200997 A1 US 2015200997A1
Authority
US
United States
Prior art keywords
data
communication
communication link
http
operable
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/669,622
Other languages
English (en)
Inventor
Tuomas Mikael RÄRKKÄINEN
Valtteri Hakkarainen
Ossi Kalevo
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Gurulogic Microsystems Oy
Original Assignee
Gurulogic Microsystems Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Gurulogic Microsystems Oy filed Critical Gurulogic Microsystems Oy
Assigned to GURULOGIC MICROSYSTEMS OY reassignment GURULOGIC MICROSYSTEMS OY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HAKKARAINEN, VALTTERI, KALEVO, OSSI, KARKKAINEN, TUOMAS MIKAEL
Publication of US20150200997A1 publication Critical patent/US20150200997A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the present disclosure relates to communication systems, for example to communication systems which utilize Real-Time Hypertext Transfer Protocol (HTTP) for communicating various types of digital data, for example graphics data, image data, video data, audio data and similar.
  • HTTP Real-Time Hypertext Transfer Protocol
  • the present disclosure is also concerned with methods of operating aforesaid communication systems for communicating various types of data.
  • the present disclosure is also concerned with software products recorded on machine-readable data storage media, wherein the software products are executable upon computing hardware for implementing aforesaid methods.
  • HTTP Hypertext Transfer Protocol
  • the Protocol is an application protocol for distributed, collaborative hypermedia information systems.
  • HTTP is a multi-linear set of objects which are operable to build a network using logical links to define the network; the links are often referred to as being “hyperlinks” which define a network relationship between nodes.
  • HTTP is operable to function as a request-response protocol, for example in a client-serving model as implemented for the Internet.
  • a web browser is optionally used to implement a client, and a software application executing upon a server may host a web site.
  • a given client submits a HTTP request message to the server, which responds by providing resources such as HTML files and other content, or performs data processing functions on behalf of the client, or even returns a response message to the client.
  • the aforesaid web browser is susceptible to being implemented in various ways, for example as a user agent, as a web crawler or any other software executable upon computing hardware that accesses, consumes or displays Internet-derived data content.
  • HTTP is designed to permit immediate network elements to enable communications between clients and servers.
  • High-traffic web-sites of the Internet often employ web cache servers that are operable to deliver content on behalf of upstream servers to improve response times for data and/or service delivery.
  • HTTP proxy servers at private network boundaries are beneficially used to facilitate communication for clients without a globally routable Internet address, namely by relaying messages via external servers.
  • HTTP resources are identified and located on a given network by using Uniform Resource Identifiers (URI's), also referred to as Uniform Resource Locators (URL's).
  • URI's and hyperlinks are expressed in Hypertext Markup Language (HTML) that is capable of forming webs of mutually interlinked hypertext documents.
  • An HTTP session is implemented by way of a sequence of network request-response transactions.
  • an HTTP client initiates a request by establishing a Transmission Control Protocol (TCP) connection to a particular port on a server.
  • An HTTP server listens for the client's request message and responds by sending back a status line, for example “HTTP/1.1 200 OK” together with an associated message.
  • a body of this associated message is often the requested resource, although an error message may alternatively be returned.
  • HTTP defines methods, conveniently referred to as “verbs”, for indicating a desired action to be performed in respect of an identified resource.
  • the resource is, for example, a data file or an output from an executable object residing on one or more servers. Examples of HTTP methods, also known as HTTP “verbs”, are provided in Table 1.
  • HTTP methods HTTP “verbs”) “Verb” Details GET Requests a representation of a specified resource, wherein requests using “GET” should only retrieve data HEAD Requests a response which is identical to that obtainable from GET, but devoid of any response body; “HEAD” is often employed for retrieving meta-data in an efficient manner POST Requests that a given server accepts an entity enclosed in the request as a new sub-ordinate of a given web resource identified by a URL PUT Requests that an enclosed entity be stored in respect of a supplied URI (URL). If the URI refers to an already existing resource, that resource is modified.
  • URI refers to an already existing resource, that resource is modified.
  • HTTP is based upon requests, see Table 1, that are transmitted and, on response to these requests, HTML pages or binary data such as images or audio streams/files are commonly served in response to receiving the requests.
  • Bi-directional communication via the Internet is known from Voice-over-Internet-Protocol (VoIP) and also from Internet-based video conferencing, for example as contemporarily provided using Skype software and similar; “Skype” is a registered trademark.
  • VoIP Voice-over-Internet-Protocol
  • Skype is a registered trademark.
  • the present disclosure seeks to provide a communication system which is capable of providing two-way data communication via an HTTP communication network in an improved manner.
  • the present disclosure seeks to provide an improved method of operating a communication system for providing two-way data communication via an HTTP communication network.
  • a communication system which is operable to support HTTP-based communication, wherein the communication system is operable to establish a two-way real-time communication link between two nodes of the system by employing a combination of GET and POST methods associated with HTTP, and wherein data exchange via the communication link is implemented in a chunked manner and/or as a series of multipart data blocks, wherein a maximum segment size (MSS) for data chunks and/or multipart data blocks communicated through the communication link is optimized as a function of a communication network capability supporting the communication link.
  • MSS maximum segment size
  • the communication system is of advantage in that it is capable of providing real-time two-way communication with reduced latency.
  • the CONNECT method is capable of being used in three different types of scenario:
  • the communication link includes a reception connection and a transmission connection for providing the two-way communication, and wherein the connections are maintained open until an empty chunk and/or an empty multipart data block is received.
  • the communication link is operable to employ encryption of data communicated therethrough.
  • the communication link is operable to provide communication of at least one of: graphics data, image data, video data, audio data, unstructured data.
  • a method of establishing a communication link via a communication system which is operable to support HTTP-based communication wherein the method includes:
  • the communication link includes a reception connection and a transmission connection for providing the two-way communication, and wherein the connections are maintained open until an empty chunk and/or an empty multipart data block is received.
  • the communication link is operable to employ encryption of data communicated therethrough.
  • the communication link is operable to provide communication of at least one of: graphics data, image data, video data, audio data, unstructured data.
  • non-transitory computer-readable storage medium for establishing a communication link via a communication system which is operable to support HTTP-based communication, comprising computer program code which when executed by a data processing system, causes the data-processing system to:
  • the computer program code is expressed in HTTP and is executable upon a server of a communication network operating according to HTTP.
  • the present invention is of advantage in that the communication system is capable of providing two-way, full-duplex communication, either unencrypted or encrypted, by utilizing known HTTP transfer protocol in such a way that extra configurations are not necessary in software or hardware firewalls and/or in anti-virus software applications executing in the communication system.
  • the present invention is of advantage in that it improves the functionality and reliability of communication applications, and thus simplifies technical maintenance issues associated with the system, for example data security settings.
  • FIG. 1 is an illustration of a communication network operable to employ HTTP
  • FIG. 2 is an illustration of a set of steps of a method of the disclosure.
  • FIG. 3 is an illustration of an alternative set of steps of a method of the disclosure.
  • an underlined number is employed to represent an item over which the underlined number is positioned or an item to which the underlined number is adjacent.
  • a non-underlined number relates to an item identified by a line linking the non-underlined number to the item.
  • the non-underlined number is used to identify a general item at which the arrow is pointing.
  • HTTP is not designed to enable real-time two-way communication between first and second nodes 10 A, 10 B, wherein a given client is able simultaneously to transmit real-time data and to receive real-time in such a manner that:
  • Embodiments of the present disclosure are capable of addressing functionalities (i) to (iv) by employing the following features:
  • HTTP is used for Internet sessions, wherein the GET and POST methods are employed in a mutually independent manner.
  • the GET method is used for requesting HTML content from a web-server which is operable to function as a host for a web-browser client, wherein connections for the GET method remain open until all response data is delivered from the host to the client.
  • a connection procedure is employed which is the same as the POST method, see Table 1, except that data is delivered from the client to the host.
  • connection can be initialised both with the GET method and with the POST method. It is not relevant for the method pursuant to the disclosure which method is used to open the connection.
  • communication is executed in such a manner that a given socket is used in a half-duplex manner, which distinguishes the embodiments from known approaches, for example aforesaid WebSockets.
  • transmission and/or reception of data is more efficient than in a full-duplex connection, because network interface cards do not need to switch their input/output (I/O) states between reception and transmission.
  • I/O input/output
  • Such switching employed in known technical art consumes system resources and correspondingly decreases potential communication speed.
  • the embodiments pursuant to this disclosure comply entirely with the HTTP standard, and do not try to lure the server to forcefully keep open, but instead comply fully with the definition of transfer encoding in the HTTP standard, thus yielding improved communication performance.
  • a socket is utilized after an initialisation of HTTP GET and POST methods only, either in a reception mode or in a transmission mode.
  • a network adapter used only needs to operate in a half-duplex state only, thereby saving network infrastructure and device resources, because the connection operates solely in either a transmitting mode or a reception mode after negotiated HTTP GET and/or POST method headers until a finish of the connection occurs.
  • firewalls and routers namely hubs and switches, receive less switching load and thus will not break as fast as known contemporary full-duplex communication approaches that use only one full-duplex connection.
  • embodiments described hereinafter are much more resource-efficient than aforesaid WebSockets, for example.
  • Aforementioned known WebSockets can easily be analysed by firewalls as belonging to an unidentified connection type and thus be disconnected, thereby preventing or restricting their usage, irrespective of whether or not an associated connection is tunnelled or not.
  • a GET or POST connection functions according to the HTTP protocol, and thus firewalls cannot restrict or prevent communication utilizing these methods.
  • the system pursuant to this disclosure optionally also utilize the tunnelled connection.
  • UDP protocol which is estimated to be substantially three times faster than TCP
  • P2P peer-to-peer
  • Embodiments described herewith are differentiated from known HTTP implementations, in that known HTTP implementations are devoid of any link between GET and POST methods; in contradistinction, embodiments described herein employ GET and POST methods merged together in a novel manner for providing a real-time full-duplex data communication.
  • the mentioned full-duplex data communication is implemented by using one reception connection and one transmission connection.
  • One reception connection or one transmission connection can use one half-duplex connection mode or one full-duplex connection mode.
  • UDP User Datagram Protocol
  • TCP Transport Control Protocol
  • IP Internet Protocol
  • NAT network address translation
  • UDP in the system 5
  • MSS capacity measured in bytes in both IPv4 and IPv6 communication networks, for example used for implementing the system 5 is larger, because UDP headers are smaller than corresponding TCP headers.
  • TCP for both GET and POST connections
  • TCP for both GET and POST connections
  • UDP User Datagram Protocol
  • the data in the transmitting or receiving end can also change from the circuit switched to IP-based data and correspondingly from IP-based to circuit switched data, without departing from the scope of the invention.
  • STEP 1 a client to a data connection generates a unique stream identification (ID), wherein the ID is employed to pair GET and POST methods together, so that a server employed to implement the data connection is aware that the pair of GET and POST methods belong to the same client.
  • ID employed will be elucidated in greater detail later. However, it will be appreciated that GET and POST methods do not limit the present invention when the unique stream identification (ID) is used to combine transmission and reception connections.
  • the principal purpose of the Stream ID is to bind the transmission and reception connections of the client together at the server. This means that the server can then discard harmful, erroneous and/or unidentified connections before their processing continues.
  • Such functionality makes it possible to protect the server and to reduce/prune the server load caused by unidentified connection requests and unnecessary computing. In other words, this enables the system to conserve resources, which provides a benefit of saving energy and decreasing the number of servers that are needed in the server facilities, especially in load balancing systems.
  • STEP 2 (S 2 ): the client then establishes two TCP/IP connections to the server, for example at its default port “ 80 ”, after which the client transmits a header associated with a CONNECT method.
  • the CONNECT method converts the requested data connection into a transparent TCP/IP tunnel, for example usually to facilitate TLS and SSL-encrypted communication (HTTP) through an unencrypted proxy as aforementioned.
  • various forms of encryption are optionally employed, for example SSL 1.0, SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2 or similar types of encryption.
  • the aforesaid tunnel is beneficially transparent for ensuring secure communication between different “ecosystems”.
  • Such a transparent tunnel connection as employed for implementing embodiments of the disclosure is capable of preventing hacker, hostile software, anti-virus software, firewall software or other devices and/or software that are operable to monitor and analyze data traffic from interfering with data that is communicated via the tunnel connection.
  • STEP 3 depending upon the receiving or transmitting connection employed for the communication tunnel, the header of the GET method or the POST method continues to be transmitted and received.
  • the header contains necessary information for a given communication session provided by the communication tunnel.
  • the header beneficially employs a convention form of data structure, although the header includes following parameters:
  • the header can contain information related to authentication of the sender and/or recipient.
  • this information can be provided in the GET or POST URL.
  • MSS Maximum Segment Size
  • Such network optimization is, for example, implemented by requesting a Maximum Transfer Unit (MTU) value from networks coupling connected client devices to the server. It is thereby feasible to identify a weakest communication link in the communication network, and thereafter setting the Maximum Segment Size (MSS) for transmissions to a client device associated with the weakest link at a rate which can be accommodated by the weakest link.
  • MTU Maximum Transfer Unit
  • MSS Maximum Segment Size
  • the MSS value is optionally communicated by the server to other client devices of the system.
  • Step A the system determines a weakest data link coupling the server to the client devices; for example, the MTU value for a given data link is 1500 Bytes. When this MTU value is subtracted by the number of TCP header Bytes, namely 40 Bytes, 1460 Bytes are available. These 1460 Bytes correspond to the MSS.
  • Step B the system determines a MSS for a given session by employing the MSS of the weakest identified link.
  • Step C optionally, a Nagle algorithm employed in the system is disabled in order to prevent congestion control within the system, namely achieved by setting the TCP_NODELAY option on a socket of the system, which disables the Nagle algorithm.
  • Such disablement of the Nagle algorithm is desirable, because the Nagle algorithm waits before a certain amount of Bytes of data have been added to a transmission queue before a corresponding data packet is sent.
  • the system is capable of sending a data packet of size determined solely by the system, as aforementioned.
  • STEP 4 (S 4 ): once the HTTP request header has been transmitted, and a corresponding successful response has been received from the server, duplex data reception and transmission are then commenced. There has thereby been successfully made two connections with the server, namely a reception connection and a transmission connection; these connections are maintained in an open state until an empty data chunk or an empty multipart data block is received.
  • Example 1 there is provided HTTP code which is operable when executed to create a simple tunnelled reception connection between the client and the server, wherein a peer with an IP address 192.168.0.101 connects to a host with an IP address 192.168.0.100.
  • HTTP code which is operable when executed to create a simple tunnelled reception connection between the client and the server, wherein a peer with an IP address 192.168.0.101 connects to a host with an IP address 192.168.0.100.
  • Example 2 there is provided HTTP code which is operable when executed to create a simple tunnelled transmission connection between the client and the server, wherein a peer with an IP address 192.168.0.101 is connected with the host that has a corresponding IP address 192.168.0.100.
  • HTTP code which is operable when executed to create a simple tunnelled transmission connection between the client and the server, wherein a peer with an IP address 192.168.0.101 is connected with the host that has a corresponding IP address 192.168.0.100.
  • Equation 1 Equation 1
  • the beginning of the chunk header consists of the length of the actual chunk data, for example in hexadecimal notation, and of the end of one or more line characters, which are usually both Carriage Return (CR) and Line Feed (Lf).
  • the end of the chunk is similar to the end of line characters, which complete the chunk.
  • the STEP 3 (S 3 ), namely establishing a connection tunnel by utilizing the CONNECT method, is optionally omitted as provided in FIG. 3 .
  • the connection tunnel is omitted when there is not a requirement for the tunnel.
  • the connection tunnel can be constructed only for the GET connection or the POST connection, namely an asymmetrical tunnel communication arrangement between a plurality of nodes; optionally, the communication tunnel is used only for GET or POST connections.
  • Example 3 MSS optimization depends solely upon a given payload provided by a given data chunk, because corresponding http chunk headers have already been stripped off at that point in the processing, whereas the payload of the data block is 100%.
  • MSS optimization is principally based upon a concept as follows:
  • the maximum transmission unit (MTU) is an individual transmission burst and, as such, the largest protocol data unit that the layer can pass onwards, for example 1500 Bytes, and the MSS (maximum segment size) has a data size which is equal to MTU minus the protocol headers.
  • MTU maximum transmission unit
  • the MSS maximum segment size
  • the MSS carries exactly the amount of data in Bytes that the weakest link of the network in question can transmit. Therefore, no splitting of data into smaller packets occurs when technology pursuant to the application is used, which increases the speed and reliability of data transmission, which in turn results in less collisions and packet losses, for example in a WiFi network.
  • MSS optimization is as follows:
  • ICMP-pings are sent to test the network; it is detected that communication between the CLIENT 1 and the CLIENT 2 is prevented if MTU>600. Therefore, the MTU is set to 600 Bytes, which means that the MSS is 560 Bytes, after the 40 Bytes of TCP header have been omitted, namely taken into account. It will be appreciated that the headers in the UDP protocol are smaller, so if UDP is used, the payload will be correspondingly larger.
  • CLIENT 1 then transmits to CLIENT 2 a 3000-Byte packet which is split into 6 parts.
  • Packet 1 560 Bytes are transmitted, of which the payload is 553 Bytes.
  • Packet 2 560 Bytes are transmitted, of which the payload is 553 Bytes.
  • Packet 3 560 Bytes are transmitted, of which the payload is 553 Bytes.
  • Packet 4 560 Bytes are transmitted, of which the payload is 553 Bytes.
  • Packet 6 560 Bytes are transmitted, of which the payload is 235 Bytes.
  • the packet were transmitted directly without splitting, namely as one 3000 Byte packet, then it would have been divided, namely fragmented, by devices of operators along the network, which would have taken time and which might potentially have caused problems, and possibly it would have been necessary to retransmit lost packets, all of which would have resulted in the transmitter having to wait before transmitting new packets, due to a lag caused by an unstable network of the recipient.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
US14/669,622 2013-04-23 2015-03-26 Communication system utilizing http Abandoned US20150200997A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
GB1307340.8 2013-04-23
GB1307340.8A GB2513344B (en) 2013-04-23 2013-04-23 Communication system utilizing HTTP
PCT/EP2014/001052 WO2014173521A1 (en) 2013-04-23 2014-04-21 Two-way real-time communication system utilizing http

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/001052 Continuation WO2014173521A1 (en) 2013-04-23 2014-04-21 Two-way real-time communication system utilizing http

Publications (1)

Publication Number Publication Date
US20150200997A1 true US20150200997A1 (en) 2015-07-16

Family

ID=48537693

Family Applications (2)

Application Number Title Priority Date Filing Date
US14/669,622 Abandoned US20150200997A1 (en) 2013-04-23 2015-03-26 Communication system utilizing http
US14/684,955 Active US9787770B2 (en) 2013-04-23 2015-04-13 Communication system utilizing HTTP

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/684,955 Active US9787770B2 (en) 2013-04-23 2015-04-13 Communication system utilizing HTTP

Country Status (9)

Country Link
US (2) US20150200997A1 (ja)
EP (1) EP2989774B1 (ja)
JP (2) JP6444988B2 (ja)
KR (1) KR101655715B1 (ja)
CN (1) CN105340242B (ja)
BR (1) BR112015026903A2 (ja)
GB (1) GB2513344B (ja)
RU (1) RU2635220C2 (ja)
WO (1) WO2014173521A1 (ja)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110999257A (zh) * 2017-08-04 2020-04-10 诺基亚技术有限公司 用于服务器通知的递送的传送方法选择

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107294913B (zh) * 2016-03-31 2021-08-27 阿里巴巴集团控股有限公司 基于http的安全通信方法、服务端及客户端
US10334052B2 (en) 2016-10-28 2019-06-25 Caterpillar Inc. System and method for communicating negotiated groups of parameters
JP7203297B2 (ja) * 2017-09-27 2023-01-13 有限会社シモウサ・システムズ エンドツーエンド暗号化通信システム
CN108011850B (zh) * 2017-12-18 2021-08-17 北京百度网讯科技有限公司 数据包的重组方法及装置、计算机设备及可读介质
WO2021201305A1 (ko) * 2020-03-30 2021-10-07 엘지전자 주식회사 차량을 위한 통신 프로토콜을 변경하는 방법 및 장치
CN113285931B (zh) * 2021-05-12 2022-10-11 阿波罗智联(北京)科技有限公司 流媒体的传输方法、流媒体服务器及流媒体系统

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6412009B1 (en) * 1999-03-15 2002-06-25 Wall Data Incorporated Method and system for providing a persistent HTTP tunnel
JP3478200B2 (ja) * 1999-09-17 2003-12-15 日本電気株式会社 サーバ・クライアント間双方向通信システム
US7522631B1 (en) * 1999-10-26 2009-04-21 Qualcomm, Incorporated Method and apparatus for efficient data transmission control in a wireless voice-over-data communication system
US7324228B2 (en) * 2000-02-25 2008-01-29 Hewlett-Packard Development Company, L.P. System and method for downloading and for printing data from an external content source
US20020184383A1 (en) 2001-05-29 2002-12-05 Docomo Communications Laboratories Usa, Inc. Live mobile camera system with a communication protocol and a server cluster
EP1461708A1 (en) * 2001-08-24 2004-09-29 Reality Fusion, Inc. System and method for group video teleconferencing with variable bandwidth
JP2003244194A (ja) * 2002-02-18 2003-08-29 Mitsubishi Electric Corp データ暗号装置及び暗号通信処理方法及びデータ中継装置
JP2003304248A (ja) * 2002-04-09 2003-10-24 Nippon Telegr & Teleph Corp <Ntt> データ転送方法及び装置
DE10260926B4 (de) * 2002-12-20 2005-12-01 Hewlett-Packard Development Co., L.P., Houston Kommunikationsverfahren
US7447369B2 (en) * 2003-03-07 2008-11-04 Ricoh Co., Ltd. Communication of compressed digital images
US20050071485A1 (en) * 2003-09-26 2005-03-31 Arun Ramagopal System and method for identifying a network resource
FR2869490B1 (fr) * 2004-04-26 2006-06-23 Michel Gouget Procede d'acces a un syteme informatique protege, application a la tele-administration et a la realisation de proxies
US7561696B2 (en) * 2005-07-12 2009-07-14 Microsoft Corporation Delivering policy updates for protected content
US8151323B2 (en) * 2006-04-12 2012-04-03 Citrix Systems, Inc. Systems and methods for providing levels of access and action control via an SSL VPN appliance
JP2008108116A (ja) * 2006-10-26 2008-05-08 Nec Corp 双方向通信システム、サーバ装置、中継装置、双方向通信方法及びプログラム
KR20100014507A (ko) * 2007-03-22 2010-02-10 텔레폰악티에볼라겟엘엠에릭슨(펍) 사용자 장비에서 링크 최대 전송 단위를 구성하는 방법
JP4864792B2 (ja) * 2007-03-29 2012-02-01 京セラ株式会社 無線通信端末の制御方法および無線通信端末
US7995478B2 (en) * 2007-05-30 2011-08-09 Sony Computer Entertainment Inc. Network communication with path MTU size discovery
KR20090010416A (ko) * 2007-07-23 2009-01-30 삼성전자주식회사 Ｐｐｐ 연결의 패킷 크기 최적화 시스템 및 그 방법
US8782772B2 (en) * 2007-09-28 2014-07-15 Microsoft Corporation Multi-session secure tunnel
KR101405952B1 (ko) * 2007-12-05 2014-06-12 엘지전자 주식회사 데이터 블록 전송방법
JP2010004416A (ja) * 2008-06-23 2010-01-07 Fujitsu Ltd 移動無線装置
KR101010409B1 (ko) 2008-09-01 2011-01-24 주식회사 세아네트웍스 터널링 기반 네트워크에서 ｉｐ 패킷 전송 방법 및 장치
KR101636258B1 (ko) * 2009-03-20 2016-07-05 삼성전자 주식회사 이동통신시스템에서 네트워크의 ｒａｃｈ 관련 시스템 자원자동적 최적화 방법
US9178648B2 (en) * 2010-01-06 2015-11-03 Alcatel Lucent Method to improve voice over IP capacity for user equipment employing variable rate vocoders
WO2012161652A1 (en) * 2011-05-26 2012-11-29 Agency For Science, Technology And Research Methods for transmitting and receiving a digital signal, transmitter and receiver
CN102594826B (zh) * 2012-02-24 2014-12-10 清华大学 一种适用于电力系统终端设备的实时数据压缩通信方法
US8755404B2 (en) * 2012-04-25 2014-06-17 Gainspan Corporation Facilitating communication between resource-constrained devices and wireless communication terminals
US9268651B1 (en) * 2012-10-31 2016-02-23 Amazon Technologies, Inc. Efficient recovery of storage gateway cached volumes

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110999257A (zh) * 2017-08-04 2020-04-10 诺基亚技术有限公司 用于服务器通知的递送的传送方法选择

Also Published As

Publication number Publication date
RU2635220C2 (ru) 2017-11-09
CN105340242A (zh) 2016-02-17
KR101655715B1 (ko) 2016-09-07
GB2513344B (en) 2017-03-15
BR112015026903A2 (pt) 2017-07-25
CN105340242B (zh) 2019-08-16
JP2017118545A (ja) 2017-06-29
KR20150136141A (ko) 2015-12-04
EP2989774A1 (en) 2016-03-02
GB2513344A (en) 2014-10-29
WO2014173521A1 (en) 2014-10-30
US9787770B2 (en) 2017-10-10
US20150222703A1 (en) 2015-08-06
RU2015143010A (ru) 2017-05-26
JP6444988B2 (ja) 2018-12-26
JP2016522478A (ja) 2016-07-28
GB201307340D0 (en) 2013-05-29
EP2989774B1 (en) 2018-04-04

Similar Documents

Publication Publication Date Title
US9787770B2 (en) Communication system utilizing HTTP
US9590821B2 (en) Communication system for transmitting data under a tunnel protocol between at least two data computers via a wide area network and a method for running such a communication system
US9027129B1 (en) Techniques for protecting against denial of service attacks
US10135956B2 (en) Hardware-based packet forwarding for the transport layer
EP1892887B1 (en) Communication method between communication devices and communication apparatus
KR102452752B1 (ko) 전송 제어 방법 및 장치
US9319439B2 (en) Secured wireless session initiate framework
JP2017118545A5 (ja)
EP2741463B1 (en) Data packet transmission method
US11394582B2 (en) Multi-part TCP connection over VPN
CN102088460B (zh) 受限网络中流媒体数据的传输方法、设备和系统
KR102077883B1 (ko) 데이터 통신 시스템 및 방법
EP3820088A1 (en) Method and network device for multi-path communication
US10205804B2 (en) Methods and systems for enhanced support of TCP options in a TCP spoofed system
US11050587B1 (en) Multi-part TCP connection over VPN
US7203757B2 (en) Device, method and program for protocol translation
WO2014198229A1 (zh) 报文处理方法、设备和系统
CN113794715A (zh) 一种虚拟点对点网络数据发送、接收、应答方法及其系统
CN114978643B (zh) 一种通信方法、网络设备及存储介质
Rajput et al. Comparing stream control and datagram congestion control with traditional transmission control protocol
KR102263755B1 (ko) 엔드포인트의 트래픽에 대한 포워딩 시스템 및 방법
CN116010077A (zh) 一种家庭智能网关多核cpu处理器的控制方法及装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: GURULOGIC MICROSYSTEMS OY, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KARKKAINEN, TUOMAS MIKAEL;HAKKARAINEN, VALTTERI;KALEVO, OSSI;SIGNING DATES FROM 20150316 TO 20150323;REEL/FRAME:035265/0024

STCB Information on status: application discontinuation

Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION