CN217789687U - Transmission system of back source request - Google Patents

Transmission system of back source request Download PDF

Info

Publication number
CN217789687U
CN217789687U CN202220482642.XU CN202220482642U CN217789687U CN 217789687 U CN217789687 U CN 217789687U CN 202220482642 U CN202220482642 U CN 202220482642U CN 217789687 U CN217789687 U CN 217789687U
Authority
CN
China
Prior art keywords
source
network
node
connection
request
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
Application number
CN202220482642.XU
Other languages
Chinese (zh)
Inventor
郭毅立
郑鹏达
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.)
Wangsu Science and Technology Co Ltd
Original Assignee
Wangsu Science and Technology Co Ltd
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 Wangsu Science and Technology Co Ltd filed Critical Wangsu Science and Technology Co Ltd
Priority to CN202220482642.XU priority Critical patent/CN217789687U/en
Application granted granted Critical
Publication of CN217789687U publication Critical patent/CN217789687U/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Abstract

The embodiment of the utility model provides a relate to internet technical field, disclose a transmission system of source returning request, include: a content distribution network, a cloud platform network and a connection network; wherein the connection network connects the content distribution network and the cloud platform network; the content distribution network comprises a source return node, the cloud platform network comprises a source station, and the source return node and the source station are connected through the connection network; the connection network comprises a private network. The utility model discloses a transmission system of source request returns can improve source request transmission security, realize transmission line control back to reduce cost in business.

Description

Transmission system of back source request
Technical Field
The embodiment of the utility model provides a relate to internet technical field, in particular to transmission system of source request returns.
Background
With the development of internet technology, in order to facilitate access, an enterprise generally chooses to deploy a source station in a public Network environment or on a cloud platform, and uses a Content Delivery Network (CDN) technology to realize accelerated transmission of data, so as to jointly realize Network security acceleration service. The cloud platform gathers computing resources from different regions to provide services for users together, the CDN is an intelligent virtual network constructed on the basis of the existing network, and the users can obtain required contents nearby by means of edge servers deployed in various regions and scheduling of the central platform, so that a network acceleration technology is realized.
In the prior art, a CDN node can only access a source station deployed on a public network or a cloud platform through the public network, and when a back-source request is transmitted in the public network, at least the following problems exist:
firstly, potential safety hazards exist in a public network environment, and a back-source request can be intercepted, tampered and disguised, so that the transmission safety of the back-source request is low;
secondly, the public network is generally an operator network, the line quality and the state are not controllable, and the transmission stability is poor;
thirdly, enterprises need to pay additional public network bandwidth cost, which is high in cost.
SUMMERY OF THE UTILITY MODEL
The embodiment of the application mainly aims to provide a transmission system of a source returning request, which can improve the transmission security of the source returning request, realize transmission line control and reduce enterprise cost.
To achieve the above object, an embodiment of the present application provides a transmission system for a back source request, including: a content distribution network, a cloud platform network and a connection network; the connection network is connected with the content distribution network and the cloud platform network; the content distribution network comprises a back source node, the cloud platform network comprises a source station, and the back source node is connected with the source station through a connection network; the connection network comprises a private network.
The transmission system of the source returning request, provided by the application, is connected with the content distribution network and the cloud platform network through the connection network, and the connection network comprises the private network, so that the source returning node and the source station can establish private connection, and the source returning request is sent to the source station through the private connection, so that the source returning request can be transmitted to the source station through an intranet instead of a public network between the content distribution network and the source station, thereby reducing the situations that the source returning request is intercepted, tampered and the like caused by public network transmission, improving the transmission safety of the source returning request, and solving the problems mentioned in the background technology.
In addition, when the back-source node and the source station are deployed in the same machine room, the back-source node and the source station are connected through a special intranet line. In the application, the back-source node bound with the intranet IP address of the source station and the source station are deployed in the same intranet, so that the intranet connection between the back-source node and the source station is higher in safety, and the transmission safety of the back-source request is further guaranteed.
In addition, the virtual transport network includes a first transit node and a second transit node; the first transfer node and the return source node are both deployed in a first local area network and are in communication connection based on the first local area network, and the second transfer node and the source station are both deployed in a second local area network and are in communication connection based on the second local area network. In the application, the source return node and the first transfer node are in communication connection based on the first local area network, the source station and the second transfer node are in communication connection based on the second local area network, and the first transfer node and the second transfer node are nodes in the virtual transmission network, so that the source return node and the source station can establish a virtual network private line connection based on the first local area network, the second local area network and the virtual transmission network, perform virtual network private line transmission of the source return request, and guarantee the transmission security of the source return request.
In addition, the source node is configured with a first IP address and a second IP address, the private network establishes private connection with the intranet IP address of the source station through the first IP address, and the public network establishes public network connection with the public network IP address of the source station through the second IP address. After receiving the source returning request, the source returning node establishes a special connection with the intranet IP address of the source station based on the first IP address and sends the source returning request to the source station through the special connection; when the connection network is unavailable, the source node and the source station are connected through a public network, and the source returning request is sent to the source station through the public network connection. In the application, when the private network is unavailable, the source returning node cannot send the source returning request to the source station through the private connection, and at the moment, the source returning node can still send the source returning request to the source station through establishing public network connection with the source station, so that the source returning request can be sent to the source station certainly.
In addition, the second IP address and the first IP address belong to different address fields respectively, and the source station configures different routing rules for the different address fields respectively in advance; the different routing rules include: sending the response information sent to the first IP address to the back source node through the special connection; and sending the response information sent to the second IP address to the back source node through the public network connection. In the application, because the second IP address and the first IP address belong to different address segments respectively, and the source station configures different routing rules for the different address segments respectively in advance, after receiving the back-source request, the source station can determine a sending path for sending the response information according to the difference of the IP addresses used by the back-source node, thereby ensuring routing consistency.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
Fig. 1 is a first schematic structural diagram of a transmission system for back-source requests according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a transmission system for back-source requests according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram three of a transmission system for back-source requests according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the following describes each embodiment of the present invention in detail with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that in various embodiments of the invention, numerous technical details are set forth in order to provide a better understanding of the present application. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments. The following embodiments are divided for convenience of description, and should not constitute any limitation to the specific implementation manner of the present invention, and the embodiments may be mutually incorporated and referred to without contradiction.
The embodiment of the utility model relates to a transmission system of source request returns, as shown in FIG. 1, include:
a content distribution network 110, a cloud platform network 120, and a connection network 130;
wherein, the connection network 130 connects the content distribution network 110 and the cloud platform network 120;
the content distribution network 110 comprises a back-source node 1101, the cloud platform network comprises a source station 1201, and the back-source node 1101 and the source station 1201 are connected through a connection network 130; the connection network 130 includes a private network 1310.
The transmission system of the source-returning request in this embodiment further enhances a service function of a Content Delivery Network 110 (CDN), that is, a CDN platform, where the CDN is a layer of intelligent virtual Network on the basis of the existing internet, which is formed by deploying node servers at various locations of the Network, and the CDN system can redirect a request of a user to a service node closest to the user according to Network traffic, connection of each node, a load condition, a distance to the user, response time, and other comprehensive information in real time. The method aims to enable the user to obtain the required content nearby, solve the network congestion condition and improve the response speed of the user for accessing the website. In the CDN field, the back-sourcing refers to a process in which a CDN node obtains data from a source station 1201 (i.e., a source station server) to return the data to a user, and the back-sourcing request is a request for obtaining data, which is sent by the CDN node to the source station 1201 in the back-sourcing process.
Because an enterprise generally selects to deploy the source station 1201 in a public network environment or on a cloud platform, a CDN node can only access the source station 1201 deployed on a public network or the cloud platform through the public network, when a back-source request has 1 in a public network transmission process, the public network environment has a potential safety hazard, and the back-source request may be eavesdropped, tampered and disguised, resulting in lower transmission security of the back-source request; 2. the public network is generally an operator network, the line quality and the state are not controllable, and the transmission stability is poor; 3. enterprises need to pay additional public network bandwidth cost, and the cost is high.
In the present application, the transmission system of the back-source request uses the connection network 130 to connect the content distribution network 110 and the cloud platform network 120, the content distribution network 110 includes the back-source node 1101, the cloud platform network 120 includes the source station 1201, the back-source node 1101 and the source station 1201 are connected through the connection network 130, and the connection network 130 includes the private network 1310, so that the back-source node 1101 may establish a private connection with the source station 1201, such as an intranet connection and a virtual network private line connection, and send the back-source request to the source station 1201 through the private connection, and thus, the back-source request may be transmitted to the source station 1201 through the private network 1310 instead of being transmitted through a public network between the content distribution network 110 and the source station 1201, thereby reducing the situations of eavesdropping and tampering of the back-source request caused by the public network transmission, improving the security of the transmission of the back-source request, and, as the back-source request is transmitted through the intranet, the enterprise does not need to pay the public network bandwidth cost, which may save the transmission cost.
The implementation details of the transmission system of the source return request of the present embodiment are specifically described below, and the following description is only provided for facilitating understanding of the implementation details, and is not necessary for implementing the present embodiment.
The content distribution network 110 includes a back source node 1101, and further includes an edge node 1102, the source station 1201 is deployed on a cloud platform of a cloud service provider, wherein the back source node 1101 is connected to the source station 1201 through a connection network 130, a user equipment sending a back source request is connected to the back source node 1101 through the edge node 1102, the connection network 130 includes an intranet private line 1301 or a virtual transmission network 1302, when the back source node 1101 and the source station 1201 are located in the same local area network, the private network 1310 is an intranet private line 1311, that is, the back source node 1101 is connected to the source station 1201 through the intranet private line 1311, and when the back source node 1101 and the source station 1201 are located in different local area networks, the private network 1310 is a virtual transmission network 1312, that is, the back source node 1101 is connected to the source station 1201 through the virtual transmission network 1312.
The edge node 1102 is configured to receive a source returning request from the user equipment, determine whether an intranet IP address is available when an intranet IP address exists in a source station 1201 which requests access from a source returning request, and forward the source returning request to the source returning node 1101 if the intranet IP address is available. Specifically, the edge node 1102 prestores a source station 1201 that needs to provide a service and a public network address thereof, and if the source station 1201 also has an intranet IP address, the edge node 1102 also stores the intranet IP address in association with the corresponding source station 1201 and the public network address thereof. When the user equipment sends a request back to the source station 1201, the CDN scheduling service may select a corresponding edge node 1102 for the user according to the location information of the user, so as to provide a network service. After receiving the back-to-source request, the edge node 1102 analyzes the back-to-source request, determines a source station 1201 to be accessed by a user according to information of the back-to-source request, and determines whether an intranet IP address exists in the source station 1201 according to a local record; if the source station 1201 has an intranet IP address, the edge node 1102 determines whether the intranet IP address is available; if the source station 1201 does not have an intranet IP address, an optimal source returning path is selected inside the CDN network according to the public network address of the source station 1201, and the source returning request is finally sent to the source station 1201 through the public network.
In an implementation, the edge node 1102 may determine whether an intranet IP address is available based on pre-stored address detection results. Each return source node 1101 in the CDN network of this embodiment may periodically perform connectivity detection on the bound intranet IP address, determine whether the intranet IP address of the source station 1201 is available, and synchronize a detection result to the edge node 1102 in the CDN network. In one example, the back-source node 1101 uploads the probe result to a core server, which synchronizes the probe result of the whole network to the edge node 1102 of the CDN network. The edge node 1102 updates the state of the locally stored intranet IP address by the received detection result. In this way, the edge node 1102 can directly and quickly determine whether the intranet IP address is available according to the intranet IP address state stored locally, thereby reducing the time required for the edge node 1102 to process the return request.
The back-to-source node 1101 is configured to, after receiving the back-to-source request, establish a dedicated connection with the source station 1201 based on the first IP address and the intranet IP address, and send the back-to-source request to the source station 1201 through the dedicated connection. After receiving the back-source request, the back-source node 1101 determines whether the intranet IP address of the source station 1201 is available, and if the intranet IP address of the source station 1201 is available, the edge node 1102 forwards the back-source request to the back-source node 1101 bound to the intranet IP address.
Specifically, the back-source node 1101 may send a back-source request to the source station 1201 through the dedicated connection immediately after the dedicated connection is successfully established, and attempt to establish the dedicated connection to the source station 1201 again after the dedicated connection is unsuccessfully established until the dedicated connection is successfully established. In a preferred embodiment, after the establishment of the dedicated connection fails, the source station 1201 tries to establish the dedicated connection again within the range of the configured retry connection establishment times until the establishment of the dedicated connection is successful, and if the retry connection establishment time is out, the establishment of the dedicated connection is determined to have failed. By setting the retry times, the probability of successful intranet connection establishment can be improved, so that the source returning request can be transmitted from the special connection as far as possible, and meanwhile, the source returning rate is prevented from being influenced by too many retry times.
In one example, connecting network 130 also includes a public network through which source station 1201 and back-source node 1101 may be connected when private network 1310 is unavailable.
In an example, as shown in fig. 2, the CDN network 210 (i.e., CDN platform) includes a back source node 2101 and an edge node 2102, the edge node 2102 is connected to the user equipment 20, and the CDN back source node 2101 and the source station 2201 are deployed in the same computer room, so that the CDN back source node 2101 and the source station 2201 are located in the same intranet (i.e., local area network 230) and connected by an intranet dedicated line through a network device. The source node 2101 may establish an intranet connection with an intranet IP address of the source station 2201 via the first IP address, where the intranet connection may be established via a Transmission Control Protocol (TCP), or a User Datagram Protocol (UDP). After this intranet connection is successfully created, back-source node 2101 may send a back-source request to source station 2201 over this intranet connection.
In this embodiment, since the source returning node 2101 bound to the intranet IP address of the source station 2201 is deployed in the same intranet as the source station 2201, the intranet connection between the source returning node 2101 and the source station 2201 has higher security, thereby further ensuring the transmission security of the source returning request.
Further, the private intranet line may be formed based on a switch, the switch is connected to the back-source node 2101 and the source station 2201, and the back-source node 2101 implements communication with the source station 2201 through the switch, so that a back-source request sent by the back-source node 2101 is forwarded to the source station 2201 through the switch. The switches may include a CDN switch 23111 (i.e., CDN SW) and a cloud platform switch 23112, that is, the back source node 2101 and the source site 2201 may be connected by the switches. For example, a Client Premise Equipment (CPE) is disposed on the switch to configure the connection of the lan.
In one example, the back-source node 2101 sends a back-source request to the source station 2201 via an intranet connection with the back-source node 2101, and then receives a response message returned by the source station 2201 via the intranet connection.
In this embodiment, the source station 2201 returns response information to the source node 2101 through the intranet connection between the source station 2201 and the source node 2101, which can ensure the data security of the response information and the routing consistency.
In one example, the connection network 230 further includes a public network 2320 (i.e., a public network), and the connection between the source node 2101 and the source station 2201 may also be via the public network. If the intranet connection is failed to be established, the return source node 2101 establishes a public network connection with the public network IP address of the source station 2201 based on the second IP address, and sends a source request back through the public network connection. That is, when configuring information, the source station 2201 needs to configure two IP addresses for it, one is an intranet IP address and one is a public IP address, and when configuring information, the source node 2101 also needs to configure two IP addresses for it, one is dedicated to establishing connection with the intranet IP address of the source station 2201, that is, a first IP address, one is dedicated to establishing connection with the public IP address of the source station 2201, that is, a second IP address, the private network 2310 establishes connection with the intranet IP address of the source station 2201 through the first IP address, and the public network establishes connection with the public IP address of the source station 2201 through the second IP address.
In this embodiment, when the private network 2310 is unavailable, for example, TCP connection establishment fails, the source returning node 2101 cannot send the source returning request to the source station 2201 through an intranet connection, at this time, the source returning node 2101 may establish a public network connection with a public network address of the source station 2201 based on the second IP address, and may still send the source returning request to the source station 2201, which ensures that the source returning request can be sent to the source station 2201 certainly, and avoids that the source returning request cannot obtain a response in time.
Further, after the source return node 2101 sends the source return request to the source station 2201 via the public network connection, the source return node 2101 correspondingly receives the response information returned by the source station 2201 via the public network connection.
In this embodiment, the response information returned by the source station 2201 is received through the public network connection, so that even when the establishment of the intranet connection fails, the return source node 2101 can be ensured to receive the response information of the source station 2201, and the request sent through the public network receives the response through the public network, and the request sent by the intranet receives the response through the intranet, thereby ensuring the routing consistency.
Further, the second IP address and the first IP address belong to different address segments, respectively, and the source station 2201 may configure different routing rules for the address segments to which the second IP address and the first IP address belong in advance, where the different routing rules include: the response information sent to the address field where the first IP address is located is sent to the back-to-source node 2101 via the intranet connection, and the response information sent to the address field where the second IP address is located is sent to the back-to-source node 2101 via the public network connection.
In this embodiment, since the second IP address and the first IP address belong to different address segments, and the source station 2201 configures different routing rules for the different address segments in advance, after receiving the back-source request, the source station 2201 may determine a sending path for sending the response information according to the difference of the IP addresses used by the back-source node 2101, thereby ensuring routing consistency.
In an example, as shown in fig. 3, a CDN edge node 3102 is connected to a user equipment 30, and a CDN back source node 3101 and a CDN back source station 3201 are deployed in different rooms, so that the back source node 3101 and the CDN back source station 3201 cannot be connected through an intranet dedicated line, and therefore, the back source node 3101 and the CDN back source station 3201 need to be connected through a virtual transport network, where the virtual transport network 3320 includes a first transit node 3301 and a second transit node 3302, the first transit node 3301 and the back source node 3101 are both deployed in a first local area network 3100 and are connected in communication based on the first local area network 3100, and the second transit node 3302 and the CDN back source station 3201 are both deployed in a second local area network 3200 and are connected in communication based on the second local area network 3200. A switch 3103 in the first local area network 3100 is connected back to the source node 3101 and the first transit node 3301, respectively, a switch 3203 in the second local area network 3200 is connected to the source station 3201 and the second transit node 3302, respectively, and the first transit node 3301 and the second transit node 3302 are connected by a virtual network private line, which is a private connection established based on a virtual transport network 3320 (e.g., an SDWAN network). The back-source request is sent by the back-source node 3101, forwarded to the first transit node 3301 through the switch 3103 in the first local area network 3100, forwarded to the second transit node 3302 by the first transit node 3301 based on the virtual network private line, forwarded to the switch 3202 in the second local area network 3200 by the second transit node 3302, and finally forwarded to the source station 3201 by the switch in the second local area network 3200.
In this embodiment, the source node 3101 and the source station 3201 are based on the first local area network 3100, the source station 3201 and the second transit node 3302 are based on the second local area network 3200, and the first transit node 3301 and the second transit node 3302 are nodes in the virtual transmission network, so that the source node 3101 and the source station 3201 are based on the first local area network 3100, the second local area network 3200, and the virtual transmission network, and can establish a dedicated connection, perform dedicated network transmission of the source return request, and ensure transmission security of the source return request.
In one example, the first transit node 3301 and the second transit node 3302 may be deployed on a switch with a Customer Premise Equipment ("CPE") disposed thereon to configure connections of the virtual transport network.
In one example, the Virtual transport Network may be a Multi-Protocol Label Switching Virtual Private Network ("MPLS-VPN"), a Software Defined Wide Area Network ("SD-WAN"), or the like.
Taking SD-WAN as an example, after receiving the request to return to the source, the return-to-source node 3101 establishes a virtual network dedicated line connection with the source station 3201 based on the SD-WAN based on the first IP address and the intranet IP address of the source station 3201, and sends the request to return to the source station 3201 through the virtual network dedicated line. The first IP address is an IP address corresponding to the first local area network 3100, and the intranet IP address of the source station 3201 is an IP address corresponding to the second local area network 3200.
The source returning node 3101 may send a source returning request to the source station 3201 through the private virtual network line immediately after the private virtual network line is successfully established, and try to establish the private virtual network line to the source station 3201 again after the private virtual network line is unsuccessfully established until the private virtual network line is successfully established. In a preferred embodiment, after the virtual dedicated network line is failed to be established, the source station 3201 is tried to establish the virtual dedicated network line again within the range of the configured retry connection establishment times until the virtual dedicated network line is successfully established, and if the virtual dedicated network line is out of the range of the retry connection establishment times, the virtual dedicated network line is determined to be failed to be established. By setting the retry times, the probability of successful intranet connection establishment can be improved, so that the source returning request can be transmitted from a virtual network private line as far as possible, and meanwhile, the source returning rate is prevented from being influenced by too many retry times.
When the private network is unavailable and the establishment of the private connection fails, for example, the TCP connection is failed to be established, the back-to-source node 3101 cannot send the back-to-source request to the source station 3201 through the virtual network dedicated line, at this time, the back-to-source node 3101 may establish the public network connection with the public network address of the source station 3201 based on the second IP address, and still may send the back-to-source request to the source station 3201, which ensures that the back-to-source request can be sent to the source station 3201 certainly, and avoids that the back-to-source request cannot obtain a response in time. That is, the source station 3201 needs to be configured with two IP addresses, one is an internal network IP address and one is a public network IP address, and the return source node 3101 needs to be configured with two IP addresses, one dedicated for establishing a connection with the internal network IP address of the source station 3201, that is, the first IP address, and one dedicated for establishing a connection with the public network IP address of the source station 3201, that is, the second IP address, during information configuration.
In this embodiment, when the private network is unavailable, the back-source node 3101 cannot send the back-source request to the source station 3201 through the private connection, and at this time, the back-source node 3101 can still send the back-source request to the source station 3201 by establishing the public network connection with the source station 3201, so as to ensure that the back-source request can be sent to the source station 3201 certainly.
In one example, the back-source node 3101 receives the response information returned by the source station 3201 through the virtual network private line after sending the back-source request to the source station 3201 through the virtual network private line with the back-source node 3101.
Further, the back-to-source node 3101 receives the response information returned by the source station 3201 through the public network connection after sending the back-to-source request to the source station 3201 through the public network connection.
It will be understood by those skilled in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and detail may be made therein without departing from the spirit and scope of the invention in practice.

Claims (7)

1. A system for transmitting a request back to a source, comprising:
a content distribution network, a cloud platform network and a connection network;
wherein the connection network connects the content distribution network and the cloud platform network;
the content distribution network comprises a source return node, the cloud platform network comprises a source station, and the source return node and the source station are connected through the connection network; the connection network comprises a private network.
2. The system for transmitting a return request according to claim 1, wherein the private network comprises an intranet private line;
and when the source returning node and the source station are deployed in the same machine room, the source returning node and the source station are connected through the intranet private line.
3. The transmission system of back-source requests according to claim 2, wherein said back-source node and said source station are connected through a switch.
4. The transmission system of claim 1, wherein the private network comprises a virtual transport network;
the virtual transmission network comprises a first transfer node and a second transfer node;
the first transfer node and the back source node are deployed in a first local area network and are in communication connection based on the first local area network, and the second transfer node and the source station are deployed in a second local area network and are in communication connection based on the second local area network.
5. The system according to claim 4, wherein the first transit node and the second transit node are connected based on a virtual network dedicated line.
6. The transmission system of the request back to source of claim 4, wherein the first transit node and the second transit node are deployed on a switch.
7. The system according to claim 1, wherein the content distribution network further comprises an edge node, and the user equipment sending the back-source request and the back-source node are connected through the edge node.
CN202220482642.XU 2022-03-07 2022-03-07 Transmission system of back source request Active CN217789687U (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202220482642.XU CN217789687U (en) 2022-03-07 2022-03-07 Transmission system of back source request

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202220482642.XU CN217789687U (en) 2022-03-07 2022-03-07 Transmission system of back source request

Publications (1)

Publication Number Publication Date
CN217789687U true CN217789687U (en) 2022-11-11

Family

ID=83905305

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202220482642.XU Active CN217789687U (en) 2022-03-07 2022-03-07 Transmission system of back source request

Country Status (1)

Country Link
CN (1) CN217789687U (en)

Similar Documents

Publication Publication Date Title
US11451510B2 (en) Method and apparatus for processing service request
US8549286B2 (en) Method and system for forwarding data between private networks
US5410543A (en) Method for connecting a mobile computer to a computer network by using an address server
US8909743B2 (en) Dynamic session maintenance for mobile computing devices
EP4009593A1 (en) Data transmission method and apparatus, network card and storage medium
EP2922246B1 (en) Method and data center network for cross-service zone communication
CN113596191B (en) Data processing method, network element equipment and readable storage medium
CN111612466B (en) Consensus and resource transmission method, device and storage medium
EP2252093B1 (en) Method for enabling mobility of client devices in large scale unified networks
CN107517189B (en) Method and equipment for WLAN user access authentication and configuration information issuing
US8175091B2 (en) Communication system
US10462048B2 (en) Virtual cluster establishment method and network device
CN104160680A (en) Spoofing technique for transparent proxy caching
CN113364741A (en) Application access method and proxy server
EP4246936A1 (en) Data processing method, function device and readable storage medium
CN114629912B (en) Communication transmission method and device based on MEC
US7248891B2 (en) Method of managing a communication with multi-server service providing means
CN217789687U (en) Transmission system of back source request
KR100597405B1 (en) System and method for relaying data by use of socket applicaton program
CN110336793A (en) A kind of Intranet access method and relevant apparatus
JP5726302B2 (en) Secret or protected access to a network of nodes distributed across a communication architecture using a topology server
US20160381147A1 (en) Information transmission method and apparatus
US8036218B2 (en) Technique for achieving connectivity between telecommunication stations
CN114726859A (en) Return request transmission method, electronic device and storage medium
CN104618450A (en) Wireless Local Area Networks (WLAN) Web caching system and method

Legal Events

Date Code Title Description
GR01 Patent grant
GR01 Patent grant