WO2017049971A1 - Procédé d'émission de paquet et passerelle - Google Patents

Procédé d'émission de paquet et passerelle Download PDF

Info

Publication number
WO2017049971A1
WO2017049971A1 PCT/CN2016/086551 CN2016086551W WO2017049971A1 WO 2017049971 A1 WO2017049971 A1 WO 2017049971A1 CN 2016086551 W CN2016086551 W CN 2016086551W WO 2017049971 A1 WO2017049971 A1 WO 2017049971A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
upgrade
user equipment
upgrade information
protocol
Prior art date
Application number
PCT/CN2016/086551
Other languages
English (en)
Chinese (zh)
Inventor
蔡仕江
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2017049971A1 publication Critical patent/WO2017049971A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Definitions

  • the present invention relates to the field of communications, and in particular, to a message sending method and a gateway.
  • hypertext is compared to traditional text. Traditional texts, whether textbooks or computer text files, are linear. Readers must read pages one by one in order to read them. The reader has no choice. Unlike hypertext, hypertext is not a linear structure, but a nonlinear mesh structure. When reading, readers don't have to read down in a sequential manner when reading linear articles, but instead selectively read the parts of interest.
  • HTTP1.x uses multiple quintuples to connect to the server to obtain data.
  • the gateway performs DPI (English: Deep packet inspection, Chinese: deep packet inspection) analysis to obtain accurate accounting information of the user. .
  • DPI Korean: Deep packet inspection, Chinese: deep packet inspection
  • the GET in different stream IDs matches the corresponding rules, and it is precisely because this quintuple has many streams of different service data, the same message.
  • the gateway is not practical based on the quintuple and requires a comprehensive upgrade of the base stream ID.
  • HTTP 2.0 brings upgrades to server and gateway device synchronization. Especially when the server also supports HTTP2.0, the gateway is passive, because many versions of the current network may still be earlier versions, and HTTP2.0 is not fully supported. Currently, it takes a lot of time to use the online device version upgrade to support HTTP2.0. Manpower and time period.
  • the invention provides a message sending method and a gateway, which are used to solve the problem of upgrading the device version brought by the HTTP2.0 upgrade.
  • a first aspect of the present invention provides a packet sending method, including:
  • the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and a setting.
  • the gateway parses and identifies the upgrade information
  • the gateway modifies the key fields in the upgrade information separately, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with HTTP1.x. Confirmation message of the agreement.
  • the modifying, by the gateway, the keyword segments in the upgrade information separately includes:
  • the gateway inverts the character strings corresponding to the key fields respectively.
  • the modifying, by the gateway, the keyword segments in the upgrade information separately includes:
  • the gateway deletes the key field.
  • the gateway analysis and identification specifically includes:
  • the gateway records the key segment and performs deep packet detection DPI analysis.
  • a second aspect of the present invention provides a gateway, including:
  • An obtaining unit configured to obtain a packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, Upgrade fields and set fields;
  • HTTP2.0 Hypertext Transfer Protocol
  • An identification unit configured to parse and identify the upgrade information
  • a modifying unit configured to modify the key fields in the upgrade information separately, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with the HTTP1 A confirmation message for the .x protocol.
  • the modifying unit is specifically configured to invert a character string corresponding to the key field.
  • the modifying unit is specifically configured to delete the key field.
  • the The key segment is recorded, and DPI analysis is performed for deep packet inspection.
  • the gateway obtains the packet sent by the user equipment, and the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, and the upgrade information
  • the key field includes: a connection field, an upgrade field, and a setting field; the gateway parses and identifies the upgrade information; the gateway separately modifies the key fields in the upgrade information, so that the server side
  • the received message is identified as a message of the HTTP 1.x protocol and then acknowledges the HTTP1.x protocol confirmation message to the user equipment. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.
  • FIG. 1 is a schematic flowchart diagram of an embodiment of a packet sending method according to the present invention
  • FIG. 2 is a schematic flowchart diagram of another embodiment of a method for sending a packet according to the present invention.
  • FIG. 3 is a schematic flowchart diagram of another embodiment of a packet sending method according to the present invention.
  • FIG. 4 is a schematic structural diagram of an embodiment of a gateway provided by the present invention.
  • FIG. 5 is a schematic structural diagram of another embodiment of a gateway provided by the present invention.
  • first, second, etc. may be used in the embodiments of the present invention to describe each Users or terminals, but users or terminals should not be limited to these terms. These terms are only used to distinguish users or terminals from each other.
  • first user may also be referred to as a second user without departing from the scope of the embodiments of the present invention.
  • second user may also be referred to as a first user; similarly, the second user may also be This is not limited by the embodiment of the present invention.
  • the working process of HTTP is a typical client/server working mode, the client is the WWW browser, and the server is the WWW server.
  • the HTTP working process uses the request/response handshake method: 1 the client connects, the two parties establish a TCP connection; 2 the client makes the request; 3 the server processes the request, returns the response; 4 the server closes the connection.
  • HTTP itself is both simple and efficient in handling large numbers of requests. After the client connects to the server, the information that the client must pass is just the request method and path. Because HTTP is simple, the HTTP server program is small and simple. Therefore, the communication speed via HTTP is very fast, and the time overhead is much smaller than other protocols.
  • HTTP is a connectionless protocol. It means limiting each connection to only one request, the client submits a request after connecting to the server, and disconnects immediately after the client receives the response. With this connectionless protocol, the server won't wait for it when there is no request, and the server will not hold the original request after completing a request.
  • Using a connectionless protocol is like writing a letter. Once you write a good letter, it will be fine. The other party has a new message and another letter. Keeping the connection agreement is similar to making a call. The two sides took turns to talk about a lot of words before they hang up. The phone line is always occupied during the conversation. For connectionless protocols, the server side is easier to implement and can take advantage of online resources.
  • HTTP is a stateless protocol: each request, the content, status, and completion of the response are not retained as historical data for use in the next phase. It is both an advantage and a disadvantage. On the one hand, because there is no state, the protocol has no ability to remember things. If subsequent transaction processing requires prior processing For information, then this information must be saved outside the agreement. A lack of state means that the required front information must be reproduced, which inevitably leads to more information being transmitted per connection. On the other hand, it is precisely because of the lack of state that HTTP is less cumbersome, running faster, and the server responds faster.
  • a content negotiation mechanism is required to enable the web server to pick out the resource entity with the most appropriate form of expression that satisfies the user's requirements. Because many times the source server or the intermediate server providing the cache does not have a unified optimal resource form standard, and the client browser does not necessarily have the ability to handle all entity types.
  • HTTP has good scalability, and it transmits more than just hypertext data. Based on this, the application developer's research and development requirements can easily increase the request method and response state, and run it in the user-customized system.
  • the expanded server can respond to the original standard browser, and can also distinguish the dedicated client program developed by the user and respond accordingly.
  • the HTTP protocol has gone through three phases of 0.9, 1.0, and 1.1.
  • Added meta information add a piece of information, that is, information information, in front of the main data. It enables the server to provide information about the transfer of data. For example, what type of object is being transferred, in which language it is written, and so on;
  • identity authentication a simple "question-answer" basic access authorization method. The process is to first send an identity authentication request to the client by the server, and then the customer sends a confirmation message;
  • Cache mechanism Temporarily save the contents of the previous client request and the response of the web server corresponding to the request in the memory or physical memory of the machine, so that it can be utilized when processing a new client request.
  • HTTP 2.0 Hypertext Transfer Protocol 2.0
  • HTTP 2.0 is the next generation HTTP protocol. It was developed by the IETF's Hypertext Transfer Protocol Bis (httpbis) working group. It is the first update since the release of http1.1 in 1999. HTTP 2.0 conducted its first collaborative collaboration test in August 2013. HTTP/2.0 provides HTTP semantically optimized transport.
  • An HTTP/2.0 connection is made through a TCP connection (application-level protocol [TCP] running above).
  • the client is the TCP connection initiator.
  • the client can initiate an HTTP2.0 negotiation upgrade. If the server supports the HTTP2.0 protocol, the server will answer the HTTPOK 100OK confirmation, otherwise it will directly answer the 100OK confirmation of HTTP1.x.
  • the client can also directly initiate an HTTP 2.0 request message, and the server must respond to the HTTP 2.0 request.
  • the present invention provides a packet sending method, which is mainly executed by a gateway; 1.
  • An embodiment of a message sending method provided by the present invention includes:
  • the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and an upgrade field. , setting the field;
  • HTTP2.0 Hypertext Transfer Protocol
  • the user equipment initiates a TCP connection, establishes a TCP connection with the server, and the gateway acquires a packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment,
  • the upgrade information includes the following key fields: connection field Connection, upgrade field Upgrade, and setting field HTTP2-Setting.
  • the gateway parses and identifies the upgrade information.
  • the gateway identifies the key field in the upgrade information, records the keyword information, and performs DPI and content charging.
  • the gateway separately modifies the key fields in the upgrade information, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with the HTTP1. A confirmation message for the .x protocol.
  • the gateway separately modifies the key fields in the upgrade information, for example, respectively, the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field are reversed or the sequence of the strings is scrambled; or Delete the Connection, Upgrade, and HTTP2-Setting fields. If you choose to delete the device, you need to add the deleted key fields to the HTTP header field before the server responds to the HTTP1.x acknowledgment message from the user device to ensure TCP. The correctness of the sequence.
  • the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a field, an upgrade field, and a setting field; the gateway parses the upgrade information; the gateway separately modifies the key fields in the upgrade information, so that the server identifies the received message A message confirming the HTTP 1.x protocol is sent to the user equipment after the message of the HTTP 1.x protocol. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.
  • HTTP2.0 Hypertext Transfer Protocol
  • another embodiment of a packet sending method provided by the present invention includes:
  • the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field. , setting the field;
  • the gateway parses and identifies the upgrade information.
  • Steps 201 and 202 refer to the related descriptions in steps 101 and 102, and details are not described herein again.
  • the gateway reverses the character string corresponding to the key field, so that the server identifies the received message as the HTTP1.x protocol message and then responds to the user equipment with HTTP1.
  • a confirmation message for the x protocol is
  • the gateway inverts the character strings corresponding to the key fields respectively, for example, respectively, the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field are reversed; for example, the system is passing HTTP.
  • the Upgrade request is modified to ensure the correctness of the data transfer.
  • the HTTP to HTTP 2.0 upgrade header field is in the following format:
  • HTTP2-Settings ⁇ base64url encoding of HTTP/2SETTINGS payload>
  • the gateway UGW needs to identify the Connection, Upgrade, and HTTP2-Setting fields in the above example and reverse it:
  • sgnitteS-2PTTH ⁇ base64url encoding of HTTP/2SETTINGS payload>
  • the string order of the Connection, Upgrade, and HTTP2-Setting fields can be disturbed, or a few letters can be added/reduced, and the same effect can be achieved.
  • the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: Field, upgrade field, setting field; the gateway parsing identifies the liter Level information; the gateway inverts the character string corresponding to the key field, respectively, so that the server recognizes the received message as an HTTP1.x protocol message and then responds to the user equipment with HTTP1. A confirmation message for the .x protocol. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.
  • HTTP2.0 Hypertext Transfer Protocol
  • another embodiment of a packet sending method provided by the present invention includes:
  • the gateway obtains a packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and an upgrade field. , setting the field;
  • HTTP2.0 Hypertext Transfer Protocol
  • the gateway parses and identifies the upgrade information.
  • Steps 301 and 302 refer to the related descriptions in steps 101 and 102, and details are not described herein again.
  • the gateway deletes the key field, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with an acknowledgement message of the HTTP1.x protocol.
  • the gateway deletes the key field, for example, deletes the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field; for example, the system ensures the correctness of data transmission after modifying the HTTP Upgrade request.
  • the HTTP to HTTP 2.0 upgrade header field is in the following format:
  • HTTP2-Settings ⁇ base64url encoding of HTTP/2SETTINGS payload>
  • the gateway UGW needs to identify the Connection, Upgrade, and HTTP2-Setting fields in the above example and delete it:
  • the TCP layer needs to maintain the serial numbers on the left and right sides:
  • the gateway UGW modifies the HTTP request header field initiated by the user equipment UE, the TCP sequence will follow The change, therefore, the gateway UGW needs to ensure the correctness of the TCP sequence to avoid protocol-level errors.
  • the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a field, an upgrade field, and a setting field; the gateway parses the upgrade information; the gateway deletes the key field, so that the server identifies the received message as an HTTP1.x protocol message. The acknowledgment message of the HTTP1.x protocol is then replied to the user equipment. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.
  • HTTP2.0 Hypertext Transfer Protocol
  • the user equipment initiates a TCP connection, establishes a TCP connection with the server, and the gateway obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, and the upgrade information includes the following information.
  • Key field Connection field Connection, upgrade field Upgrade, setting field HTTP2-Setting.
  • the gateway identifies the key fields in the upgrade information, records the keyword information, and performs DPI and content charging.
  • the gateway inverts the character string corresponding to the key field, so that the server recognizes the received message as a packet of the HTTP 1.x protocol, and then responds to the user equipment with the HTTP 1.x protocol. Confirmation message.
  • the Connection, Upgrade, and HTTP2-Setting fields in the HTTP header field are reversed respectively; for example, the system ensures the correctness of data transmission by modifying the HTTP Upgrade request, and the HTTP to HTTP 2.0 upgrade header field is in the following format. :
  • HTTP2-Settings ⁇ base64url encoding of HTTP/2SETTINGS payload>
  • the gateway UGW needs to identify the Connection, Upgrade, and HTTP2-Setting fields in the above example. Points and reverses it:
  • sgnitteS-2PTTH ⁇ base64url encoding of HTTP/2SETTINGS payload>
  • the packet is sent to the server.
  • the server identifies the received packet as the HTTP1.x protocol packet and then responds to the user equipment with HTTP1.
  • the confirmation message of the x protocol ie HTTP1.x 200OK.
  • the gateway includes:
  • the obtaining unit 401 is configured to obtain a packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key field: a connection field. , upgrade fields, set fields;
  • the identifying unit 402 is configured to parse and identify the upgrade information
  • the modifying unit 403 is configured to modify the key fields in the upgrade information to enable the server to identify the received message as a packet of the HTTP 1.x protocol and then respond to the user equipment. A confirmation message for the HTTP1.x protocol.
  • the obtaining unit 401 obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key segments. a connection field, an upgrade field, and a setting field; the identification unit 402 parses and identifies the upgrade information; the modifying unit 403 separately modifies the key fields in the upgrade information, so that the server receives the report.
  • the message is identified as a message of the HTTP 1.x protocol
  • the user device is replied to the HTTP1.x protocol confirmation message. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.
  • the modifying unit The 403 is specifically configured to invert the character string corresponding to the key field, so that the server identifies the received message as an HTTP1.x protocol message and then responds to the user equipment with the HTTP1.x. Confirmation message of the agreement.
  • the modifying unit 403 is specifically configured to delete the key field, so that the server identifies the received message as HTTP1.
  • the message of the x protocol is replied to the user equipment with an acknowledgement message of the HTTP 1.x protocol.
  • the identifying unit 402 is specifically configured to record the key segment and perform deep packet detection DPI analysis.
  • FIG. 4 illustrates the specific structure of the gateway from the perspective of the functional unit.
  • the specific structure of the gateway is described from the hardware point of view below with reference to the embodiment shown in FIG. 5:
  • the gateway includes a receiver 501, a transmitter 502, a processor 503, and a memory 504.
  • Memory 504 can include read only memory and random access memory and provides instructions and data to processor 503.
  • a portion of the memory 504 can also include a non-volatile random access memory.
  • Memory 504 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:
  • Operation instructions include various operation instructions for implementing various operations.
  • Operating system Includes a variety of system programs for implementing various basic services and handling hardware-based tasks.
  • the gateway according to an embodiment of the present invention may have more or less components than those shown in FIG. 5, may combine two or more components, or may have different component configurations or settings, and each component may include one Hardware, software, or a combination of hardware and software, including multiple signal processing and/or application specific integrated circuits.
  • the processor 503 is configured to perform the following operations:
  • the packet carries the upgrade information of the Hypertext Transfer Protocol (HTTP2.0) of the user equipment, where the upgrade information includes the following key fields: a connection field, an upgrade field, and a setting field. ;
  • HTTP2.0 Hypertext Transfer Protocol
  • the received message is identified as a message of the HTTP 1.x protocol and then acknowledges the HTTP1.x protocol confirmation message to the user equipment.
  • the processor 503 obtains the packet sent by the user equipment, where the packet carries the upgrade information of the hypertext transfer protocol HTTP2.0 protocol of the user equipment, where the upgrade information includes the following key segments. a connection field, an upgrade field, and a setting field; the processor 503 parses and identifies the upgrade information, and separately modifies the key fields in the upgrade information, so that the server identifies the received message.
  • a message confirming the HTTP 1.x protocol is sent to the user equipment after the message of the HTTP 1.x protocol. Therefore, the information that the user equipment wants to upgrade to HTTP2.0 is dropped back to HTTP1.x, so that the user equipment can not perceive and still continue the service, and can allow the user to continue the service and control the user flow.
  • the processor 503 is specifically configured to:
  • the character string corresponding to the key segment is inverted, so that the server recognizes the received message as an HTTP1.x protocol message and then acknowledges the HTTP1.x protocol confirmation message to the user equipment. .
  • the processor 503 is specifically configured to:
  • the key segment is deleted, so that the server recognizes the received message as a packet of the HTTP 1.x protocol, and then responds to the user equipment with an acknowledgement message of the HTTP 1.x protocol.
  • the processor 503 is specifically configured to:
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • Another point that is shown or discussed between each other The coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé d'émission de paquet et une passerelle pour résoudre un problème dans lequel un équipement doit être mis à niveau pour prendre en charge un protocole de transfert hypertexte 2.0 (HTTP 2.0). Le procédé consiste : à acquérir, par une passerelle, un paquet émis par un équipement utilisateur, le paquet transportant des informations de mise à niveau pour mettre à niveau l'équipement utilisateur afin que ce dernier prenne en charge le HTTP 2.0, et les informations de mise à niveau comprenant les champs clés suivants : un champ de connexion, un champ de mise à niveau et un champ de réglage ; à analyser et à identifier, par la passerelle, les informations de mise à niveau ; à modifier, par la passerelle, les champs clés dans les informations de mise à niveau, respectivement, et après l'identification, par une extrémité de serveur, du paquet reçu en tant que paquet associé à HTTP 1.x, à répondre, à l'équipement utilisateur, avec un message de confirmation HTTP 1.x.
PCT/CN2016/086551 2015-09-22 2016-06-21 Procédé d'émission de paquet et passerelle WO2017049971A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510608336.0A CN105245446B (zh) 2015-09-22 2015-09-22 一种报文发送方法及网关
CN201510608336.0 2015-09-22

Publications (1)

Publication Number Publication Date
WO2017049971A1 true WO2017049971A1 (fr) 2017-03-30

Family

ID=55042954

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/086551 WO2017049971A1 (fr) 2015-09-22 2016-06-21 Procédé d'émission de paquet et passerelle

Country Status (2)

Country Link
CN (1) CN105245446B (fr)
WO (1) WO2017049971A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112448933A (zh) * 2019-09-02 2021-03-05 浙江宇视科技有限公司 一种自适应兼容平台互联域间协议的方法和系统
CN114338272A (zh) * 2021-12-30 2022-04-12 上海集度汽车有限公司 通信控制方法、装置、车辆及可读存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105245446B (zh) * 2015-09-22 2019-02-19 上海华为技术有限公司 一种报文发送方法及网关

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546800A (zh) * 2012-01-06 2012-07-04 华为技术有限公司 一种网关握手、通信方法、网关及Web通信系统
CN102694754A (zh) * 2012-06-07 2012-09-26 广州睿哲网络科技有限公司 实现IPv4/IPv6网站内容互通的应用网关技术及系统
US20120300777A1 (en) * 2011-05-25 2012-11-29 Ravikumar Chandrasekaran Supporting multiple iec-101/iec-104 masters on an iec-101/iec-104 translation gateway
CN105245446A (zh) * 2015-09-22 2016-01-13 上海华为技术有限公司 一种报文发送方法及网关

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101505307B (zh) * 2009-03-09 2012-02-01 华为技术有限公司 面向服务构架的消息处理方法、网络节点及系统
CN103227788B (zh) * 2013-04-17 2016-02-03 广州市和声信息技术有限公司 实现网页应用程序与sip设备进行通信的方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120300777A1 (en) * 2011-05-25 2012-11-29 Ravikumar Chandrasekaran Supporting multiple iec-101/iec-104 masters on an iec-101/iec-104 translation gateway
CN102546800A (zh) * 2012-01-06 2012-07-04 华为技术有限公司 一种网关握手、通信方法、网关及Web通信系统
CN102694754A (zh) * 2012-06-07 2012-09-26 广州睿哲网络科技有限公司 实现IPv4/IPv6网站内容互通的应用网关技术及系统
CN105245446A (zh) * 2015-09-22 2016-01-13 上海华为技术有限公司 一种报文发送方法及网关

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112448933A (zh) * 2019-09-02 2021-03-05 浙江宇视科技有限公司 一种自适应兼容平台互联域间协议的方法和系统
CN112448933B (zh) * 2019-09-02 2022-12-23 浙江宇视科技有限公司 一种自适应兼容平台互联域间协议的方法和系统
CN114338272A (zh) * 2021-12-30 2022-04-12 上海集度汽车有限公司 通信控制方法、装置、车辆及可读存储介质

Also Published As

Publication number Publication date
CN105245446B (zh) 2019-02-19
CN105245446A (zh) 2016-01-13

Similar Documents

Publication Publication Date Title
US8898260B2 (en) Automatic multimedia upload for publishing data and multimedia content
EP3275162B1 (fr) Systèmes et techniques pour une communication internet
US8332476B2 (en) Social network virtual private network
US10225354B2 (en) Proximity session mobility
US20160149964A1 (en) Apparatus and method for communications involving a legacy device
WO2017167132A1 (fr) Procédé et appareil servant à mettre en œuvre une messagerie instantanée
CN107463453B (zh) 同一终端不同应用间通信的方法、装置、设备和存储介质
US20130191518A1 (en) Method and apparatus for automatic service discovery and connectivity
US9686506B2 (en) Method, apparatus, system, and storage medium for video call and video call control
JP2014209343A (ja) ドラッグアンドドロップすることを可能にするためのシステム及び方法
EP2745467A1 (fr) Procédé permettant de contrôler le flux et d'assurer une communication fiable dans un environnement collaboratif
JP5940216B2 (ja) ベアラ非依存プロトコルを伴うソケット管理の方法
WO2014127675A1 (fr) Méthode, dispositif et terminal de partage d'informations
WO2017114190A1 (fr) Procédé et dispositif de traitement de téléchargement de fichier
WO2017049971A1 (fr) Procédé d'émission de paquet et passerelle
WO2013174265A1 (fr) Procédé et dispositif de transmission de données
CN108156223A (zh) 一种基于websocket的消息精准推送系统及方法
EP2813051B1 (fr) Partage dynamique d'un service web
WO2017054510A1 (fr) Système, appareil et procédé de communication de données dans un processus de communication
WO2016180220A1 (fr) Procédé et appareil d'établissement de conversation
JP2016066265A (ja) 情報処理装置、通信システム及びプログラム
WO2023011057A1 (fr) Procédé et appareil de communication
WO2012159291A1 (fr) Procédé pour identifier le type d'un terminal et dispositif de réseau d'accès sans fil
JP2007035053A (ja) 異なる端末器間のセッション保持方法
US9900372B2 (en) Techniques to detect and react to proxy interference

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16847853

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16847853

Country of ref document: EP

Kind code of ref document: A1