CN112153087B - Cross-Net communication method for third-party network terminal - Google Patents
Cross-Net communication method for third-party network terminal Download PDFInfo
- Publication number
- CN112153087B CN112153087B CN201910566234.5A CN201910566234A CN112153087B CN 112153087 B CN112153087 B CN 112153087B CN 201910566234 A CN201910566234 A CN 201910566234A CN 112153087 B CN112153087 B CN 112153087B
- Authority
- CN
- China
- Prior art keywords
- network
- communication
- handshake protocol
- pipeline
- net
- 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.)
- Active
Links
- 238000004891 communication Methods 0.000 title claims abstract description 118
- 238000000034 method Methods 0.000 title claims abstract description 23
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 68
- 230000005540 biological transmission Effects 0.000 claims abstract description 55
- 239000003999 initiator Substances 0.000 claims abstract description 36
- 230000003993 interaction Effects 0.000 claims abstract description 5
- 238000009434 installation Methods 0.000 claims abstract description 4
- 230000035515 penetration Effects 0.000 claims description 15
- 238000013507 mapping Methods 0.000 claims description 6
- 230000002159 abnormal effect Effects 0.000 claims description 3
- 230000000712 assembly Effects 0.000 claims description 3
- 238000000429 assembly Methods 0.000 claims description 3
- 239000000284 extract Substances 0.000 claims description 3
- 238000012545 processing Methods 0.000 claims description 3
- 230000005856 abnormality Effects 0.000 claims description 2
- 230000009365 direct transmission Effects 0.000 abstract description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
Images
Classifications
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
-
- 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]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
-
- 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/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a cross-Net communication method of a third-party network terminal, which is characterized in that a cross-Net network communication component is installed at a terminal needing communication, tcp long connection with an upstream server is established after the installation is finished for service interaction, a network action intercepting module in the cross-Net network communication component is injected into the third-party communication component, the network communication action of a third-party communication component initiator is taken over in an api hook mode, a handshake protocol is used, a transmission channel of two communication nodes after a network upstream server is communicated with a Net is communicated, the communication channels of two communication parties are informed to be communicated, and then the third-party communication component carries out normal data exchange. The invention realizes the direct transmission of two network components after Net in a transparent way on the premise of not influencing the function of a third-party communication component, has strong universality and can be seamlessly integrated into various communication components, such as Windows remote desktop, RemoteApp, VNC remote control, SSH remote operation, FTP file management protocol and the like.
Description
Technical Field
The invention relates to the technical field of cross-Net communication, in particular to a cross-Net communication method of a third-party network terminal.
Background
Because the characteristics of the net environment often cannot directly exchange network data, the network communication nodes distributed at different network locations often encounter the problem of cross-net communication. Of course, if the network components developed by the network components can design a set of communication protocols, the relay server located at the upstream of the network forwards the network packet data to perform indirect data communication. But if the communication component is a third party communication component, such as a common Windows remote desktop and a common VNC remote control tool, the communication component can not communicate in the way.
Disclosure of Invention
In order to solve the above problem, the present invention provides a cross-Net communication method for a third-party network terminal.
In order to realize the purpose, the invention adopts the technical scheme that:
a cross-Net communication method of a third-party network terminal comprises the following steps:
the method comprises the following steps: installing a cross-Net network communication component on a terminal needing communication, establishing tcp long connection with an upstream server after the installation is finished, using the tcp long connection for service interaction, and injecting a network action interception module in the cross-Net network communication component into a third-party communication component;
step two: a request initiator of the communication terminal hooks a socket connection interface through an api hook interface, acquires a resource address after intercepting a connection action, and if the resource address is to be connected across Net, the resource address is hung to wait for the completion of handshake of two parties;
step three: a request initiator initiates a handshake request to an upstream server through a first handshake protocol;
step four: after receiving a handshake request sent by a request initiator, an upstream server analyzes the packet content of a first handshake protocol, extracts device identifiers of both parties, then queries service sockets corresponding to the devices of both parties from a cache, packages the service sockets into a second handshake protocol after finding, and pushes the second handshake protocol to both communication parties through a socket;
step five: after receiving a second handshake protocol pushed by the upstream server, the two communication parties respectively establish new data transmission pipelines and are connected with the upstream server, then the contents of the second handshake protocol are encapsulated into a third handshake protocol, and the third handshake protocol is sent to the upstream server through the established data transmission pipelines;
step six: after receiving the third handshake protocol pushed in the step five, the upstream server maps the two data sockets in the cache through the pipeline identifiers, encapsulates the data sockets into a fourth handshake protocol after the mapping is finished, and pushes the fourth handshake protocol to both communication parties;
step seven: the two communication parties receive the fourth handshake protocol in the step six, recover the suspended service flow in the step two after the pipeline is successfully established, and direct the connection of the third-party communication assembly of the request initiator to the third-party communication assembly of the opposite terminal;
step eight: after receiving the network packet transmitted by the third-party communication assembly in a directional manner, the locally-installed Net penetration assembly sends the network packet to an upstream server through the data transmission pipeline established in the fifth step;
step nine: after receiving the data transmitted by the data transmission pipeline, the upstream server searches the cached target socket through the mapping in the sixth step, and directly routes the data to the Net penetration assembly of the opposite end;
step ten: and after receiving the data routed by the upstream server side, the data transmission pipeline of the opposite end directly feeds the data back to the third-party communication assembly to complete the corresponding connection of the third-party communication assemblies of both communication parties.
Preferably, the contents of the first handshake protocol, the second handshake protocol, and the third handshake protocol each include a service-side pipe identifier, a request initiator network pipe identifier, and an opposite-side network pipe identifier, where the service-side pipe identifier is used to pair with an upstream service side; the network pipeline identifier of the request initiator and the network pipeline identifier of the opposite terminal are respectively used for identifying the pipeline identifiers of the network connection of the request initiator and the opposite terminal.
Preferably, the fourth handshake protocol includes a service-side pipeline identifier, a data transmission pipeline establishment state, and a first error report content, where the service-side pipeline identifier is used to pair with an upstream service side; the data transmission pipeline establishing state is used for identifying whether the data transmission pipeline is established successfully or not; the first error content is used for indicating an error prompt that the data transmission pipeline is not successfully established.
Preferably, the communication method further comprises processing an abnormal condition of network connection, if transmission from the Net penetration assembly to the upstream service end is wrong, trying to reconnect with the upstream service end, and repeating the step five after connection is successful; if the connection is still failed, closing the network connection of the third-party communication assembly and informing the third-party communication assembly of network abnormality;
and after receiving the notification of requesting the initiator to close the network connection of the third-party communication component, the third-party communication component of the opposite end notifies the upstream server end through a fifth handshake protocol, and after receiving the network exception message, the upstream server end encapsulates the message into a sixth handshake protocol and routes the message to the two parties, so that the two parties release network pipeline resources, and after the notification is completed, the upstream server end also clears the corresponding cache.
Furthermore, the fifth handshake protocol and the sixth handshake protocol both include a service-side pipeline identifier, a network pipeline identifier of a request initiator, a network pipeline identifier of an opposite terminal, a data transmission pipeline communication state, and second error reporting content, where the service-side pipeline identifier is used to pair with an upstream service side; the network pipeline identification of the request initiator and the network pipeline identification of the opposite terminal are respectively used for identifying the pipeline identifications of the request initiator and the network connection of the opposite terminal; the data transmission pipeline communication state is used for identifying whether the data transmission pipeline is communicated with the Net penetration assembly or not; the second error notification is used for indicating an error prompt that the data transmission pipeline is not communicated with the Net penetration assembly.
Furthermore, the contents of the fifth handshake protocol and the sixth handshake protocol are both in a Json format, and the text encoding modes are both utf-8 encoding.
Furthermore, the contents of the first handshake protocol, the second handshake protocol, the third handshake protocol and the fourth handshake protocol are all in a Json format, and the text encoding modes are all utf-8 encoding.
The invention realizes the direct transmission of two network components after Net in a transparent way on the premise of not influencing the function of a third-party communication component, has strong universality and can be seamlessly integrated into various communication components, such as Windows remote desktop, RemoteApp, VNC remote control, SSH remote operation, FTP file management protocol and the like.
Drawings
The accompanying drawings are included to provide a further understanding of the invention.
In the drawings:
fig. 1 is a work flow diagram of a cross-Net communication method of a third-party network terminal according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Abbreviations and key term definitions:
tcp: a common network interaction protocol belongs to a connection protocol, a tcp protocol guarantees the integrity and reliability of data transmission in the aspect of implementation and is positioned in a transmission layer of a five-layer network architecture.
net environment: the terminal ip in the net environment is usually a subnet ip, and the external part cannot access the terminal ip directly through the network address.
and (3) an api hook, namely, a method for intercepting an api action or changing the behavior of the api by writing a jump instruction in the api head.
Protocol-different network nodes implement a network packet format negotiated for exchanging data, such as http protocol, smtp protocol, dns protocol, arp protocol or proprietary protocol defined by us.
Network byte order: commonly called big-end, the data storage mode is that the low order bits of the data are stored in the high address, and the high order bits are stored in the low address
Host byte order: the data is stored in a way that the lower bits of the data are stored in the lower address and the upper bits are stored in the upper address.
As shown in fig. 1, a cross-Net communication method for a third-party network terminal includes the following steps:
the method comprises the following steps: installing a cross-Net network communication component on a terminal needing communication, establishing tcp long connection with an upstream server after the installation is finished, using the tcp long connection for service interaction, and injecting a network action interception module in the cross-Net network communication component into a third-party communication component, wherein the terminal refers to two computer terminals or other equipment terminals needing communication;
step two: a request initiator of the communication terminal hooks a socket connection interface through an api hook interface, acquires a resource address after a connection action is captured, and hangs the resource address to wait for the completion of handshake of two parties if the resource address is to be connected across Net;
step three: a request initiator initiates a handshake request to an upstream server through a first handshake protocol; the first handshake protocol is a handshake request delivered to an upstream server by a communication request initiator, describes necessary information of a handshake opposite terminal, and has a specific format as follows:
step four: after receiving a handshake request sent by a request initiator, an upstream server analyzes the packet content of a first handshake protocol, extracts equipment identifiers of both parties, namely pipeline identifiers of both parties, then inquires a service socket corresponding to both parties from a cache, packages the service socket into a second handshake protocol after finding the service socket, and pushes the second handshake protocol to both communication parties through a socket; the second handshake protocol is a handshake request pushed from the upstream server to the connecting both ends, the information of the initiator of the protocol content additional request and the pipeline information for pairing are used, the upstream server is used as a data sender, and the specific protocol format is as follows:
step five: after receiving a second handshake protocol pushed by the upstream server, the two communication parties respectively establish new data transmission pipelines and are connected with the upstream server, then the contents of the second handshake protocol are encapsulated into a third handshake protocol, and the third handshake protocol is sent to the upstream server through the established data transmission pipelines; the third handshake protocol is a data transmission pipeline creation request initiated by a data socket connected with two independent ends, and is used for an upstream server to establish communication data transmission pipelines at two ends of Net, and the specific protocol format is as follows:
step six: after receiving the third handshake protocol pushed in the step five, the upstream server maps the two data sockets in the cache through the pipeline identifiers, encapsulates the data sockets into a fourth handshake protocol after the mapping is finished, and pushes the fourth handshake protocol to both communication parties; the fourth handshake protocol is a data transmission pipeline establishment completion notification that is pushed to both communication parties by the upstream server, and is used for notifying both communication parties of completion of establishment of a cross-Net data transmission pipeline, and normal data transmission can be performed, and the specific protocol is as follows:
step seven: the two communication parties receive the fourth handshake protocol in the step six, recover the suspended service flow in the step two after the pipeline is successfully established, and direct the connection of the third-party communication assembly of the request initiator to the third-party communication assembly of the opposite terminal;
step eight: after receiving the network packet directionally transmitted by the third-party communication component, the locally-installed Net penetration component transmits the network packet to an upstream server through the data transmission pipeline established in the fifth step (namely the independent data socket established in the fifth step);
step nine: after receiving the data transmitted by the data transmission pipeline, the upstream server searches the cached target socket through the mapping in the sixth step, and directly routes the data to the Net penetration assembly of the opposite end;
step ten: after receiving the data routed by the upstream server, the data transmission pipeline of the opposite end directly feeds back the data to the third-party communication assembly, so that the corresponding connection of the third-party communication assemblies of both communication parties is completed, and other packets in the process are also processed in the same way.
Through the steps, two network nodes behind Net can perform normal data transmission, and the transmission process is completely transparent to a third-party communication assembly, so that the original service flow is not influenced.
The contents of the first handshake protocol, the second handshake protocol and the third handshake protocol all comprise a service end pipeline identifier, a request initiator network pipeline identifier and an opposite end network pipeline identifier, and the service end pipeline identifier is used for pairing with an upstream service end; the network pipeline identifier of the request initiator and the network pipeline identifier of the opposite terminal are respectively used for identifying the pipeline identifiers of the network connection of the request initiator and the opposite terminal.
The fourth handshake protocol comprises a service end pipeline identifier, a data transmission pipeline establishment state and first error reporting content, wherein the service end pipeline identifier is used for pairing with an upstream service end; the data transmission pipeline establishing state is used for identifying whether the data transmission pipeline is established successfully or not; the first error content is used for indicating an error prompt that the data transmission pipeline is not successfully established.
Processing the abnormal situation of network connection, if transmission from the Net penetration assembly to the upstream service end is wrong, trying to reconnect the upstream service end, repeating the registration action in the fifth step after successful connection, and registering the upstream service end, namely reconnecting the upstream service end; if the connection is still failed, closing the connection socket of the third-party communication assembly and informing the third-party communication assembly of network abnormity;
and after receiving the notification of requesting the initiator to close the network connection of the third-party communication component, the third-party communication component of the opposite end notifies the upstream server end through a fifth handshake protocol, and after receiving the network exception message, the upstream server end encapsulates the message into a sixth handshake protocol and routes the message to the two parties, so that the two parties release network pipeline resources, and after the notification is completed, the upstream server end also clears the corresponding cache.
The fifth handshake protocol is a service disconnection notification sent by a third-party communication component of the opposite end to the upstream server, and is used for reporting the completion of the use of the data transmission pipeline to the upstream server, and the specific protocol format is as follows:
and the sixth handshake protocol is a service disconnection notification pushed by the upstream server to the third-party communication components of both parties of the cross-Net communication, and is used for notifying the opposite end Net that the use of the component data transmission pipeline is completed and releasing tunnel resources.
The fifth handshake protocol and the sixth handshake protocol both comprise a service end pipeline identifier, a network pipeline identifier of a request initiator, a network pipeline identifier of an opposite end, a data transmission pipeline communication state and second error reporting content, wherein the service end pipeline identifier is used for pairing with an upstream service end; the network pipeline identifier of the request initiator and the network pipeline identifier of the opposite terminal are respectively used for identifying the pipeline identifiers of the network connection of the request initiator and the opposite terminal; the data transmission pipeline communication state is used for identifying whether the data transmission pipeline is communicated with the Net penetration assembly or not; the second error notification is used for indicating an error prompt that the data transmission pipeline is not communicated with the Net penetration assembly.
The contents of the first handshake protocol, the second handshake protocol, the third handshake protocol, the fourth handshake protocol, the fifth handshake protocol and the sixth handshake protocol are all in a Json format, and the text coding modes are all utf-8 codes.
The invention takes over the network connection action of both communication parties and suspends the communication parties in an api hook interface mode, then enables a third-party communication component under a net environment to carry out communication handshake through a service positioned at the upstream of a network through a handshake protocol, restores the suspended third-party communication components of both communication parties after the handshake is successful, carries out communication through an established data transmission pipeline, and realizes data exchange of network nodes behind different nets through the forwarding of packets of both parties.
Although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that various changes in the embodiments and/or modifications of the invention can be made, and equivalents and modifications of some features of the invention can be made without departing from the spirit and scope of the invention.
Claims (7)
1. A cross-Net communication method of a third-party network terminal is characterized in that: the method comprises the following steps:
the method comprises the following steps: installing a cross-Net network communication component on a terminal needing communication, establishing tcp long connection with an upstream server after the installation is finished, using the tcp long connection for service interaction, and injecting a network action interception module in the cross-Net network communication component into a third-party communication component;
step two: a request initiator of the communication terminal hooks a socket connection interface through an api hook interface, acquires a resource address after a connection action is captured, and hangs the resource address to wait for the completion of handshake of two parties if the resource address is to be connected across Net;
step three: a request initiator initiates a handshake request to an upstream server through a first handshake protocol;
step four: after receiving a handshake request sent by a request initiator, an upstream server analyzes the packet content of a first handshake protocol, extracts device identifiers of both parties, then queries service sockets corresponding to the devices of both parties from a cache, packages the service sockets into a second handshake protocol after finding, and pushes the second handshake protocol to both communication parties through a socket;
step five: after receiving a second handshake protocol pushed by the upstream server, the two communication parties respectively establish new data transmission pipelines and are connected with the upstream server, then the contents of the second handshake protocol are encapsulated into a third handshake protocol, and the third handshake protocol is sent to the upstream server through the established data transmission pipelines;
step six: after receiving the third handshake protocol pushed in the step five, the upstream server maps the two data sockets in the cache through the pipeline identifiers, encapsulates the data sockets into a fourth handshake protocol after the mapping is finished, and pushes the fourth handshake protocol to both communication parties;
step seven: the two communication parties receive the fourth handshake protocol in the step six, recover the suspended service flow in the step two after the pipeline is successfully established, and direct the connection of the third-party communication assembly of the request initiator to the third-party communication assembly of the opposite terminal;
step eight: after receiving the network packet transmitted by the third-party communication assembly in a directional manner, the locally-installed Net penetration assembly sends the network packet to an upstream server through the data transmission pipeline established in the fifth step;
step nine: after receiving the data transmitted by the data transmission pipeline, the upstream server searches the cached target socket through the mapping in the sixth step, and directly routes the data to the Net penetration assembly of the opposite end;
step ten: and after receiving the data routed by the upstream server side, the data transmission pipeline of the opposite end directly feeds the data back to the third-party communication assembly to complete the corresponding connection of the third-party communication assemblies of both communication parties.
2. The cross-Net communication method of the third-party network terminal according to claim 1, wherein: the contents of the first handshake protocol, the second handshake protocol and the third handshake protocol all comprise a service end pipeline identifier, a request initiator network pipeline identifier and an opposite end network pipeline identifier, and the service end pipeline identifier is used for pairing with an upstream service end; the network pipeline identifier of the request initiator and the network pipeline identifier of the opposite terminal are respectively used for identifying the pipeline identifiers of the network connection of the request initiator and the opposite terminal.
3. The cross-Net communication method of the third-party network terminal according to claim 1, characterized in that: the fourth handshake protocol comprises a service end pipeline identifier, a data transmission pipeline establishment state and first error reporting content, wherein the service end pipeline identifier is used for pairing with an upstream service end; the data transmission pipeline establishing state is used for identifying whether the data transmission pipeline is established successfully; the first error content is used for indicating an error prompt that the data transmission pipeline is not successfully established.
4. The cross-Net communication method of the third-party network terminal according to claim 1, characterized in that: the communication method also comprises the steps of processing the abnormal situation of network connection, if the transmission from the Net penetration assembly to the upstream service end is wrong, trying to reconnect the upstream service end, and repeating the fifth step after the connection is successful; if the connection is still failed, closing the network connection of the third-party communication assembly and informing the third-party communication assembly of network abnormality;
and after receiving the notification of requesting the initiator to close the network connection of the third-party communication component, the third-party communication component of the opposite end notifies the upstream server end through a fifth handshake protocol, and after receiving the network exception message, the upstream server end encapsulates the message into a sixth handshake protocol and routes the message to the two parties, so that the two parties release network pipeline resources, and after the notification is completed, the upstream server end also clears the corresponding cache.
5. The cross-Net communication method of the third party network terminal according to claim 4, wherein: the fifth handshake protocol and the sixth handshake protocol both comprise a service end pipeline identifier, a network pipeline identifier of a request initiator, a network pipeline identifier of an opposite end, a data transmission pipeline communication state and second error reporting content, wherein the service end pipeline identifier is used for pairing with an upstream service end; the network pipeline identifier of the request initiator and the network pipeline identifier of the opposite terminal are respectively used for identifying the pipeline identifiers of the network connection of the request initiator and the opposite terminal; the data transmission pipeline communication state is used for identifying whether the data transmission pipeline is communicated with the Net penetration assembly or not; the second error notification is used for indicating an error prompt that the data transmission pipeline is not communicated with the Net penetration assembly.
6. The cross-Net communication method of the third party network terminal according to claim 5, wherein: the contents of the fifth handshake protocol and the sixth handshake protocol are both in a Json format, and the text coding modes are both utf-8 codes.
7. The cross-Net communication method of the third-party network terminal according to claim 1, characterized in that: the contents of the first handshake protocol, the second handshake protocol, the third handshake protocol and the fourth handshake protocol are all in a Json format, and the text coding modes are all utf-8 codes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910566234.5A CN112153087B (en) | 2019-06-27 | 2019-06-27 | Cross-Net communication method for third-party network terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910566234.5A CN112153087B (en) | 2019-06-27 | 2019-06-27 | Cross-Net communication method for third-party network terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112153087A CN112153087A (en) | 2020-12-29 |
| CN112153087B true CN112153087B (en) | 2022-06-24 |
Family
ID=73868575
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910566234.5A Active CN112153087B (en) | 2019-06-27 | 2019-06-27 | Cross-Net communication method for third-party network terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112153087B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103595701A (en) * | 2012-08-17 | 2014-02-19 | 鸿富锦精密工业（深圳）有限公司 | Gateway, and method for establishing network voice communication by use of same |
| CN105531684A (en) * | 2013-09-06 | 2016-04-27 | 思科技术公司 | Universal PCI EXPRESS port |
| CN107277035A (en) * | 2017-07-05 | 2017-10-20 | 北京信息职业技术学院 | A kind of method for transmitting client-side information in TCP access phases |
| CN108139952A (en) * | 2017-06-14 | 2018-06-08 | 北京小米移动软件有限公司 | Using exchange method, exchange method and device |
| CN109274634A (en) * | 2017-07-18 | 2019-01-25 | 腾讯科技（深圳）有限公司 | Multimedia communication method and device, storage medium |
| CN109361671A (en) * | 2018-10-23 | 2019-02-19 | 华南理工大学 | A streaming media transmission architecture method based on SIP protocol |
-
2019
- 2019-06-27 CN CN201910566234.5A patent/CN112153087B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103595701A (en) * | 2012-08-17 | 2014-02-19 | 鸿富锦精密工业（深圳）有限公司 | Gateway, and method for establishing network voice communication by use of same |
| CN105531684A (en) * | 2013-09-06 | 2016-04-27 | 思科技术公司 | Universal PCI EXPRESS port |
| CN108139952A (en) * | 2017-06-14 | 2018-06-08 | 北京小米移动软件有限公司 | Using exchange method, exchange method and device |
| CN107277035A (en) * | 2017-07-05 | 2017-10-20 | 北京信息职业技术学院 | A kind of method for transmitting client-side information in TCP access phases |
| CN109274634A (en) * | 2017-07-18 | 2019-01-25 | 腾讯科技（深圳）有限公司 | Multimedia communication method and device, storage medium |
| CN109361671A (en) * | 2018-10-23 | 2019-02-19 | 华南理工大学 | A streaming media transmission architecture method based on SIP protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112153087A (en) | 2020-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7533178B2 (en) | Resuming a computing session when rebooting a computing device | |
| CN102571749B (en) | Data transmission system and method using relay server | |
| CN101572709B (en) | Switching method, system, server and client device of socket connection | |
| CN105407008A (en) | Reconnecting method and system for interrupted TCP (Transmission Control Protocol) connection, terminal and server | |
| US11917523B2 (en) | Polymorphic network control system and method supporting mobile access of terminal | |
| CN101729543A (en) | Method for improving performance of mobile SSL VPN by utilizing remote Socks5 technology | |
| EP4162654B1 (en) | Diagnosing intermediary network nodes | |
| CN111431787B (en) | Tunnel establishment method and device and computer readable storage medium | |
| CN101159683A (en) | Method and device for controlling data flow | |
| CN102082678A (en) | Processing method and equipment of port discarding OAM (Operation, Administration and Maintenance) protocol | |
| CN105072148A (en) | Method and device for building connection with terminal | |
| CN112153087B (en) | Cross-Net communication method for third-party network terminal | |
| WO2022042499A1 (en) | Tunnel keepalive method, network device, system and storage medium | |
| CN104636210B (en) | A kind of method and device for realizing Data Exchange | |
| CN111901364A (en) | Firewall penetration method and system | |
| CN101795186B (en) | Linkage disconnecting method, system and equipment | |
| CN105450432A (en) | Method for positioning port connection error and associated equipment | |
| CN115801629B (en) | Bidirectional forwarding detection method and device, electronic equipment and readable storage medium | |
| CN108337162B (en) | System and method for supporting dual-homing protection | |
| KR20180058539A (en) | Separated network bridge system and control method thereof | |
| CN105991348A (en) | TCP (transmission control protocol) connection closing method and device | |
| CN116192863A (en) | Micro-service flow processing method, DPU service grid deployment method and system | |
| CN101510901B (en) | Communication method, communication apparatus and system between distributed equipment | |
| CN109286575A (en) | Message priority configuration method, device and the network equipment | |
| CN115334691A (en) | Method, device and storage medium for network distribution by scanning code |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PP01 | Preservation of patent right | ||
| PP01 | Preservation of patent right |
Effective date of registration: 20231113 Granted publication date: 20220624 |