WO2017036247A1 - 网络系统和网络通信的方法 - Google Patents

网络系统和网络通信的方法 Download PDF

Info

Publication number
WO2017036247A1
WO2017036247A1 PCT/CN2016/088655 CN2016088655W WO2017036247A1 WO 2017036247 A1 WO2017036247 A1 WO 2017036247A1 CN 2016088655 W CN2016088655 W CN 2016088655W WO 2017036247 A1 WO2017036247 A1 WO 2017036247A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge node
node
party server
server
network
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.)
Ceased
Application number
PCT/CN2016/088655
Other languages
English (en)
French (fr)
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP16840676.7A priority Critical patent/EP3337134B1/en
Publication of WO2017036247A1 publication Critical patent/WO2017036247A1/zh
Priority to US15/907,162 priority patent/US10785780B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/256—NAT traversal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • 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/163—In-band adaptation of TCP data exchange; In-band control procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2596—Translation of addresses of the same type other than IP, e.g. translation from MAC to MAC addresses
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents

Definitions

  • Embodiments of the present invention relate to the field of communications and, more particularly, to methods of network systems and network communications.
  • CDN Content Delivery Network
  • IP Internet Protocol
  • the content distribution network can distribute the content in the source server to the service node of the distributed deployment.
  • the user request can be automatically referred to the global optimal service node according to the specified policy, and the node is close to the user.
  • Provide services
  • the service node is generally deployed in the Internet Data Center (IDC) room of the metropolitan area network. Therefore, the mobile network user has a longer delay in accessing the service node and a poor user experience.
  • IDC Internet Data Center
  • the embodiment of the invention provides a network system and a network communication method, which can reduce the delay of the user accessing the service node and improve the user experience.
  • a network system for content distribution, including: a third party server and an edge node of a network protocol IP transmission network located between a radio access network or the radio access network and a wireless core network, The edge node is used to control the transmission of the user equipment to the central server.
  • the TCP packet corresponding to the TCP connection is directed to the third-party server.
  • the third-party server includes an application server or a cache server, and is configured to store the distribution data of the central server and respond to the TCP packet according to the distribution data.
  • the method further includes: a central node located in the wireless core network, where the edge node is further configured to register the TCP connection with the central node, so that The central node learns that the third party server has served the user equipment at the edge node.
  • the edge node is specifically configured to determine an IP address that needs to be booted and stored; and the IP that is booted according to the requirement The address is replaced by the destination address of the TCP packet to replace the DNAT, so that the TCP packet is directed to the third-party server.
  • the edge node is configured to resolve a DNS response message corresponding to the domain name system DNS request message sent by the user equipment. , get the IP address that needs to be booted.
  • the edge node is specifically configured to obtain the IP address that needs to be booted from the network management system.
  • the edge node is specifically configured to obtain the IP address that needs to be booted from the central node.
  • the edge node is configured to receive a DNS request message sent by the user equipment, and send the DNS to the user equipment.
  • the DNS response message carries the IP address of the third party server.
  • the central node when the user equipment is from the edge node When the first base station cell is handed over to the second base station cell, the central node is further configured to copy, encapsulate, and forward the uplink TCP packet sent by the user equipment to the edge node, so that the edge node learns that the user equipment has been Switching from the first base station cell to the second base station cell; the edge node is further configured to: after decapsulating the copied and encapsulated uplink TCP packet, according to the IP address that needs to be booted The uplink TCP packet is forwarded to the third-party server; the downlink TCP packet received from the third-party server is copied, encapsulated, and forwarded to the central node after the source address is replaced with the SNAT; the central node is also used for After the copied and encapsulated downlink TCP packet is decapsulated, the packet is forwarded to the user equipment.
  • the central node when the user equipment is handed over from the first base station cell that includes the edge node to the second base station cell, The central node is further configured to copy, encapsulate, and forward the uplink TCP packet sent by the user equipment to the edge node, so that the edge node learns that the user equipment has switched from the first base station cell to the second base station cell.
  • the edge node is further configured to: after decapsulating the copied and encapsulated uplink TCP packet, forwarding the uplink TCP packet to the third-party server; and replicating the downlink TCP packet received from the third-party server Encapsulating and forwarding to the central node; the central node is further configured to decapsulate the copied and encapsulated downlink TCP packet and forward the packet to the user equipment.
  • the first edge node when the second base station cell deploys the first edge node, the first edge node is configured according to the first edge node Whether the uplink TCP packet is a newly established TCP connection determines whether the uplink TCP packet is directed to a third-party server corresponding to the second base station cell.
  • the central node is further configured to use the edge The location information of the node, and the data is distributed to the third-party server.
  • the edge node is further used
  • the traffic usage of the third-party server and the user equipment is reported to the central node; the central node is further configured to perform charging processing according to the reported traffic usage, so that the charging system performs charging.
  • the third-party server It is also used to obtain data corresponding to the IP address that needs to be booted from the central server.
  • a method for network communication includes a wireless access network or a third party server and an edge node of a network protocol IP transmission network between the wireless access network and the wireless core network, the method comprising: the edge node corresponding to a transmission control protocol TCP connection of the user equipment to the central server
  • the TCP packet is directed to the third-party server; the third-party server stores the distribution data of the central server and responds to the TCP packet according to the distribution data, and the third-party server includes an application server or a cache server.
  • the network system further includes a central node located in the wireless core network
  • the method further includes: the edge node registering the TCP connection with the central node, In order for the central node to know that the third party server has served the user equipment at the edge node.
  • the edge node directs the user equipment to the TCP packet corresponding to the transmission control protocol TCP connection of the central server to the
  • the third-party server includes: the edge node determines an IP address to be booted and stores the IP address, and replaces the TCPT with the destination address according to the IP address that needs to be booted, so as to guide the TCP packet to the third party. server.
  • the edge node determines an IP address that needs to be booted, and the method includes: the edge node parsing the domain name system sent by the user equipment The DNS response message corresponding to the DNS request message obtains the IP address to be booted.
  • the edge node determines an IP address that needs to be booted, including: the edge node acquiring the required guidance from the network management system IP address.
  • the edge node determines an IP address that needs to be booted, including: the edge node acquiring the required guidance from the central node IP address.
  • the edge node directs the user equipment to the TCP packet corresponding to the transmission control protocol TCP connection of the central server to Before the third-party server, the method further includes: the edge node receiving the user setting The DNS request message is sent; the DNS response message is sent to the user equipment, and the DNS response message carries the IP address of the third party server.
  • the method when the user equipment is from the edge node When the first base station cell is handed over to the second base station cell, the method further includes: the central node is further configured to copy, encapsulate, and forward the uplink TCP packet sent by the user equipment to the edge node, so as to facilitate the edge node.
  • the edge node is further configured to: after decapsulating the copied and encapsulated uplink TCP packet, according to the IP address that needs to be booted
  • the uplink TCP packet is forwarded to the third-party server; the downlink TCP packet received from the third-party server is copied, encapsulated, and forwarded to the central node; the central node is further used for copying and encapsulating the packet.
  • the downlink TCP packet is unsealed, it is forwarded to the user equipment.
  • the method further includes: the central node is further configured to: copy, encapsulate, and forward the uplink TCP packet sent by the user equipment to the edge node, so that the edge node learns that the user equipment has been switched from the first base station cell to the The second base station cell; the edge node is further configured to: after the unpacked and encapsulated uplink TCP packet is decapsulated, forward the uplink TCP packet to the third-party server; and receive the downlink from the third-party server After the source address is replaced with the SNAT, the TCP packet is copied, encapsulated, and forwarded to the central node.
  • the central node is also used to decapsulate the copied and encapsulated downlink TCP packet and forward it to the user equipment.
  • the method further includes: The first edge node determines whether the uplink TCP packet is directed to the third-party server corresponding to the second base station cell according to whether the uplink TCP packet is a newly established TCP connection.
  • the method further includes: the central node according to the The location information of the edge node, and data distribution to the third party server.
  • the method further includes: the edge node
  • the traffic usage of the third-party server interacting with the user equipment is reported to the central node; the central node performs charging processing according to the reported traffic usage, so that the charging system performs charging.
  • the method further includes :
  • the third-party server obtains data corresponding to the IP address to be booted from the central server.
  • the cache server or the application server is sunk from the IDC room located in the metropolitan area network to the local radio access network or the IP transmission network between the radio access network and the wireless core network, and the edge nodes are deployed.
  • the TCP packet of the central server is directed to the cache server or the application server to implement traffic scheduling. In this way, the transmission delay of the radio access network to the packet core network is reduced, thereby improving the user experience.
  • FIG. 1 is a schematic structural diagram of a content distribution network to which the present invention is applicable.
  • FIG. 2 is a schematic structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a network system according to another embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a process of traffic guidance according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a process of traffic guidance according to another embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a process for a user equipment to perform cell handover of a base station according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a process of data distribution according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a process of charging processing according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of a method for network communication according to an embodiment of the present invention.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access system General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) System, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), or Worldwide Interoperability for Microwave Access (WiMAX) communication system.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WiMA Worldwide Interoperability for Microwave Access
  • a radio access network refers to a fixed user accessing a switch in whole or in part in a wireless manner.
  • a switch accessed by a radio access network refers to a public switched telephone network (PSTN).
  • PSTN public switched telephone network
  • the switch can also be a switch of Integrated Services Digital Network (ISDN).
  • ISDN Integrated Services Digital Network
  • the wireless access network is the ground infrastructure that provides 3G wireless communication services, including high-speed mobile devices to the Internet.
  • the radio access network may be a UTRAN (Universal Terrestrial Radio Access Network), a GERAN (GSM EDGE Radio Access Network), or an E-UTRAN (Evolved Universal Terrestrial Radio Access Network).
  • the evolved universal terrestrial radio access network, the mobility management network element may be a Mobility Management Entity (MME) or a Serving GPRS Support Node (SGSN).
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • a radio access network may include different network elements in different systems.
  • the network elements of the radio access network in LTE and LTE-A include an eNB (eNodeB, an evolved base station), and the network elements of the radio access network in the WCDMA include an RNC (Radio Network Controller) and a NodeB, and wireless
  • the network element in the local area network includes an access point (AP).
  • AP access point
  • WiMax Worldwide Interoperability for Microwave Access
  • the related modules in the base station system may be different, and the embodiment of the present application is not limited.
  • the Core Nerwork is used to connect call requests or data requests to different networks.
  • the core network device may be a General Packet Radio Service (GPRS) Service GPRS Support Node (SGSN).
  • GPRS General Packet Radio Service
  • SGSN General Packet Radio Service Support Node
  • FIG. 1 is a schematic structural diagram of a content distribution network to which the present invention is applicable.
  • the content distribution network shown in FIG. 1 includes an origin server 101, at least one service node 102, and at least one user equipment.
  • the source server 101 is a server that provides content, and may be a web server or the like.
  • the source server 101 distributes the content to at least one service node 102.
  • Each service node 102 can provide services to different user devices.
  • the four user devices shown in FIG. 1 can be served by three service nodes 102.
  • FIG. 2 is a schematic structural diagram of a network system according to an embodiment of the present invention.
  • the network system is used for content distribution, and the network system of Figure 2 includes:
  • the corresponding TCP packet is directed to the third-party server, and the third-party server includes an application server or a cache server for storing the distribution data of the central server and responding to the TCP packet according to the distribution data.
  • the cache server or the application server is sunk from the IDC room located in the metropolitan area network to the local radio access network or the IP transmission network between the radio access network and the wireless core network, and the edge nodes are deployed.
  • the TCP packet of the central server is directed to the cache server or the application server to implement traffic scheduling. In this way, the transmission delay of the radio access network to the packet core network is reduced, thereby improving the user body. Test.
  • the central server can be the source server, which is used to distribute data to third-party servers.
  • the network system can include multiple third party servers.
  • the third party server can include a cache server or an application server.
  • the cache server can be a CDN service node. When it is a cache server (for example, a CDN service node), the center server distributes the content to the cache server; if it is an application server, the center server distributes the application to the application server. It should be understood that both content distribution and application distribution can be distributed for data.
  • the network system shown in FIG. 2 may further include a user equipment, a packet core network, a central server, and the like.
  • the number of third-party servers shown in FIG. 2 may be plural. The entire flow of the network system is described in detail below. It should also be understood that only the embodiment in which the edge node and the third party server are located in the radio access network is shown in FIG. 2, and the edge node and the third party server may also be located in the IP transmission network between the radio access network and the wireless core network. in.
  • the CDN service node in the existing CDN solution is generally located in the metropolitan area network, and since the radio access network generally does not provide the public network IP, the user request cannot be scheduled through the public network IP. Therefore, the CDN service node cannot be deployed in the radio access network.
  • the CDN service node is sunk to the IP transmission network between the radio access network or the radio access network and the wireless core network, and the edge node is deployed to complete the guiding mechanism.
  • the edge node function can be implemented by a software program to complete functions such as a boot mechanism. It should be understood that the process of guiding in the protocol may be referred to as Local Breakout. In the embodiment of the present invention, the process of Local Breakout is uniformly written and guided.
  • Figure 2 shows the scenario where the edge node and the third-party server are located in the radio access network. It should be understood that the edge node and the third party server may also be located in an IP transport network between the radio access network and the wireless core network. As shown in FIG. 2, multiple third-party servers can be deployed in the radio access network. It should be understood that the present invention is only illustrative of one of a plurality of third party servers.
  • An edge node may also be referred to as a Mobile Content Delivery Network edge (MCDN-edge).
  • MCDN-edge Mobile Content Delivery Network edge
  • the network system can introduce traffic to a locally deployed third-party server through DNAT, or can introduce traffic to a locally deployed third-party server through DNS hijacking.
  • the introducing the traffic into the locally deployed third-party server by using the DNAT includes: the edge node 202 can determine the IP address that needs to be booted and store the data; and perform the purpose of the TCP packet according to the IP address that needs to be booted. The address replaces the DNAT to facilitate directing TCP messages to a third-party server.
  • the domain name needs to be sent, and the domain name is parsed by the DNS server to obtain the destination IP address corresponding to the domain name.
  • the destination IP address is the IP address that needs to be booted in the embodiment of the present invention. It should be understood that the data corresponding to the destination IP address may be pre-placed in the third-party server, and the application service may also be provided.
  • the edge node in the embodiment of the present invention replaces the destination IP address of the uplink TCP packet sent by the user equipment, so that the TCP packet is converted from the IP address originally booted to the central server to the IP address that is directed to the third-party server, so that the third party The server provides services to user devices.
  • the edge node may determine the IP address that needs to be booted by parsing the DNS response message.
  • the process that the edge node 202 can determine the IP address that needs to be booted includes: the edge node 202 can obtain the IP address that needs to be booted by parsing the DNS response message corresponding to the domain name system DNS request message sent by the user equipment.
  • the edge node 202 may also obtain an IP address that needs to be booted from the network management system.
  • a third-party server can be called APP-Edge, and an edge node can be called MCDN-Edge.
  • the process of obtaining an IP address by the edge node by parsing the DNS response message corresponding to the DNS request message may be as follows:
  • the private network IP that the third party server provides locally and the domain name and public network IP processed by the third party server (APP-Edge) are pre-configured on the edge node.
  • the process of the UE initiating the DNS request message may include: the UE sends the DNS Request of the domain name to the DNS server through the edge node, and the DNS server passes the edge node. A corresponding DNS response message (DNS Response) is returned to the UE.
  • DNS Response DNS Response
  • the edge node parses the DNS response message and saves the IP address that needs to be booted.
  • the edge node 102 may also introduce traffic into a locally deployed third-party server through DNS hijacking.
  • the edge node 202 may receive a DNS request message for processing a domain name by a third-party server (APP-Edge) sent by the user equipment; and send a DNS response message to the user equipment, where the DNS response message carries an IP address of the third-party server.
  • APP-Edge third-party server
  • the UE sends a DNS Request for the domain name to the DNS server;
  • MCDN-Edge hijacks the DNS Request and constructs a DNS Response, which includes the IP address of the APP-Edge.
  • the domain name to be drained and its corresponding third-party server private network IP are pre-configured on the edge node (MCDN-Edge).
  • the MCDN-Edge intercepts, directly constructs a DNS response message, and returns the private network IP of the third-party server corresponding to the domain name.
  • time to live (Time To Live, TTL) of the DNS needs to be set to a small value, for example, after the UE fails to cache the DNS result and the UE switches to the base station that does not deploy the edge node/third-party server. Can be set to 1 second.
  • FIG. 3 is a schematic structural diagram of a network system according to another embodiment of the present invention.
  • the same devices in FIG. 3 as those in FIG. 2 can be numbered the same, and the network system shown in FIG. 3 further includes:
  • the edge node 202 can also register a TCP connection with the central node, so that the central node 203 knows that the third party server 201 has served the user equipment at the edge node.
  • the cache server or the application server is sunk from the IDC room located in the metropolitan area network to the local radio access network or the IP transmission network between the radio access network and the wireless core network, and the edge nodes are deployed.
  • the TCP packet of the central server is directed to the cache server or the application server to implement traffic scheduling. In this way, the transmission delay of the radio access network to the packet core network is reduced, thereby improving the user body. Test.
  • the edge node and the central node can cooperate with the mobility problem caused by the base station handover of the user equipment to ensure the continuity and integrity of the user service.
  • data return, data distribution and billing functions can be completed.
  • the third-party server does not need to be modified and implemented sinking, which reduces the overall transmission delay of the user service access and improves the user experience.
  • the server device includes a central server.
  • the central node may be a distribution center node (MCDN-Core) for the application and is a sink node of the system.
  • the MCDN-Core can be deployed on the Gateway GPRS Support Node (GGSN) and the Gi/SGi port on the Packet Data Network Gateway (PGW) side, and is responsible for the mobility management and charging of the UE for base station handover. And communication agents, etc.
  • the radio access network and the edge node can use the GTP-U message in the General Packet Radio Service Tunneling Protocol (GTP), and the edge node and the third-party server (APP-Edge) can be adopted.
  • GTP General Packet Radio Service Tunneling Protocol
  • APP-Edge the edge node and the third-party server
  • IP messages, edge nodes and central nodes can use out-of-band communication.
  • Out of band communication refers to the transmission of data entirely through different channels. For example, protocols typically do not apply to the same channels as normal data, but instead use additional channels to transfer important data.
  • the third-party server deployed at the edge node implements information interaction with the central server through the out-of-band channel.
  • the third-party server may also obtain data corresponding to the IP address to be booted from the central server.
  • the third-party server can exchange information with the central server through the out-of-band channel provided by the central node, so that the data corresponding to the IP address to be booted can be obtained from the central server.
  • the third-party server does not have a public network IP, and cannot directly communicate with the central server on the external network.
  • the third-party server setting center node is a protocol for sessions traversal across firewall securely (SOCKS) or a hypertext transfer protocol/hypertext transfer protocol server (Hypertext Transfer Protocol/ Hypertext Transport Protocol Server (HTTP/HTTPS) proxy, through the out-of-band channel, interacts with the central server to implement data return.
  • SOCKS firewall securely
  • HTTP/HTTPS Hypertext Transfer Protocol/ Hypertext Transport Protocol Server
  • the edge node may perform message forwarding between the user equipment and the third party server.
  • the message can be a TCP packet corresponding to the TCP connection.
  • FIG. 4 is a schematic flowchart of a process of traffic guidance according to an embodiment of the present invention.
  • the third-party server can be called APP-Edge
  • the edge node can be called MCDN-Edge
  • the central node can be called MCDN-Core.
  • the process shown in Figure 4 includes:
  • the UE initiates a DNS request process.
  • the private network IP that the third party server provides locally and the domain name and public network IP processed by the APP-Edge are pre-configured on the edge node.
  • the process of the UE initiating the DNS request in the 401 includes: the UE sends a DNS request message (DNS Request) to the DNS server (DNS Server) through the edge node; the DNS server returns a DNS response message (DNS Response) through the edge node.
  • DNS Request a DNS request message
  • DNS Server DNS server
  • DNS Response a DNS response message
  • the edge node parses the DNS response message and saves the IP address that needs to be booted.
  • the UE initiates a TCP connection.
  • the UE may send an uplink TCP SYN packet to the edge node to initiate a TCP connection.
  • the edge node detects that the destination IP of the TCP SYN packet is in the service range of the third server, and records the TCP session.
  • the edge node registers a TCP session with the central node.
  • MCDN-Edge registers the IP quintuple (source IP/source port/destination IP/destination port/TCP protocol) of the TCP session with the MCDN-Core through the outband channel.
  • the registration process may also use an in-band channel.
  • the MCDN-Edge copies and forwards the UE uplink TCP SYN packet of the TCP session to the wireless core network, and adds two identification information in the TCP header field (for example, the Opt ion field):
  • MCDN-Edge ID used to identify the current MCDN-Edge number. Based on this number, MCDN-Core can know the MCDN-Edge where the current session is located. If the subsequent UE is small When the zone is switched, mobility management can be implemented through the out-of-band channel and the MCDN-Edge multiple interactions.
  • the central node saves the TCP session.
  • the MCDN-Core knows that the TCP session has been served at the MCDN-Edge.
  • the edge node replaces the DNAT with the destination address of the TCP packet.
  • the edge node sends the replaced TCP packet to the third-party server.
  • the TCP packet is the uplink TCP SYN packet sent by the UE, and the edge node is replaced.
  • the destination IP address of the TCP packet is the IP address to be booted.
  • the edge node translates the IP address to be booted into the IP address of the third-party server.
  • the UE actually requests the service from the third-party server. Since the third-party server implementation has already distributed the data, the service can be provided directly to the UE.
  • TCP establishes message forwarding.
  • the UE and the third-party server perform TCP connection message forwarding through the edge node.
  • the third-party server sends a downlink TCP SYN ACK packet to the MCDN-Edge; the MCDN-Edge forwards the downlink TCP SYN ACK packet to the UE; the UE sends the MCDN to the MCDN-Edge.
  • - Edge sends an upstream TCP ACK message; MCDN-Edge forwards the upstream TCP ACK message to the APP-Edge.
  • the UE performs data interaction with a third-party server.
  • the UE and the third party server perform data interaction through the edge node.
  • the third-party server acquires data corresponding to the IP address to be booted from the central server.
  • the information may be exchanged through the out-of-band channel provided by the central node and the central server to obtain corresponding data.
  • the UE and the third-party server close the TCP connection through the edge node.
  • the edge node requests cancellation from the central node.
  • the central node deletes the TCP session.
  • FIG. 5 is a schematic flowchart of a process of traffic guidance according to another embodiment of the present invention.
  • the three-party server can be an APP-Edge
  • the edge node can be an MCDN-Edge
  • the central node can be an MCDN-Core.
  • the process shown in Figure 5 includes:
  • the UE sends a DNS request message to the DNS server.
  • the domain name of the domain name to be drained and the private network IP of the corresponding third party server are pre-configured on the edge node. Specifically, after the UE sends a DNS request message to the DNS server, the edge node will hijack the DNS request message.
  • the edge node constructs a DNS response message according to the DNS request message, where the DNS response message includes an IP address of the third-party server.
  • the edge node sends a DNS response message to the UE.
  • the MCDN-Edge detects that the domain name of the DNS request is the service domain name of the APP-Edge, and constructs a DNS response message, and returns the private network IP of the third-party server corresponding to the domain name.
  • the UE initiates a TCP connection.
  • the UE may send an uplink TCP SYN packet to the edge node to initiate a TCP connection.
  • the edge node detects that the destination IP of the TCP SYN packet is the IP of the third-party server, and records the TCP session.
  • the edge node registers a TCP session with the central node.
  • MCDN-Edge registers the IP quintuple (source IP/source port/destination IP/destination port/TCP protocol) of the TCP session with the MCDN-Core through the outband channel.
  • the registration process may also use an in-band channel.
  • the MCDN-Edge copies and forwards the UE uplink TCP SYN packet of the TCP session to the wireless core network, and adds two identification information in the TCP header field (for example, the Option field):
  • MCDN-Edge ID used to identify the current MCDN-Edge number. Based on this number, MCDN-Core can know the MCDN-Edge where the current session is located. If the subsequent UE performs cell handover, mobility management may be implemented through multiple channels of the outband channel and the MCDN-Edge.
  • the central node saves the TCP session.
  • the MCDN-Core knows that the TCP session has been served at the MCDN-Edge.
  • the edge node sends the TCP packet to the third-party server.
  • the UE and the third-party server perform TCP connection message forwarding through the edge node.
  • the MCDN-Edge sends the replaced uplink TCP SYN packet to the APP-Edge; the third-party server sends the downlink TCP SYN ACK packet to the MCDN-Edge; the MCDN-Edge forwards the downlink TCP SYN ACK packet to the UE; Sends an upstream TCP ACK packet to the MCDN-Edge.
  • the MCDN-Edge forwards the upstream TCP ACK packet to the APP-Edge.
  • the UE and the third-party server perform data interaction through the edge node.
  • the third-party server acquires data corresponding to the IP address to be booted from the central server.
  • the information may be exchanged through the out-of-band channel provided by the central node and the central server to obtain corresponding data.
  • the UE and the third-party server close the TCP connection through the edge node.
  • the edge node requests cancellation from the central node.
  • the central node deletes the TCP session.
  • FIG. 6 is a schematic flowchart of a process for a user equipment to perform cell handover of a base station according to an embodiment of the present invention.
  • the cell may configure the edge node or may not configure the edge node.
  • the process of introducing traffic to a locally deployed third-party server can either resolve the DNS response message or by hijacking the DNS request message.
  • the process of cell handover may be different.
  • the central node may further copy, encapsulate, and forward the uplink TCP packet sent by the user equipment to the edge node, if the traffic is forwarded to the third-party server.
  • the edge node can learn that the user equipment has been handed over from the first base station cell to the second base station cell.
  • the edge node can also perform the uplink TCP packet according to the IP address to be forwarded after the IP address of the encapsulated uplink TCP packet is decapsulated.
  • the DNAT is forwarded to the third-party server; the downlink TCP packet received from the third-party server is copied, encapsulated, and forwarded to the central node; the central node can also decapsulate the duplicated and encapsulated downlink TCP packet and forward it to the user. device.
  • the central node may further copy, encapsulate, and forward the uplink TCP packet sent by the user equipment to the edge node by using the hijacking DNS request message to import the traffic to the locally deployed third-party server.
  • the edge node learns that the user equipment has been handed over from the first base station cell to the second base station cell; the edge node can also decapsulate the uplink TCP packet after the copying and encapsulation, and then forward the uplink TCP packet to the third-party server;
  • the downlink TCP packets received from the third-party server are copied, encapsulated, and forwarded to the central node.
  • the central node can also decapsulate the duplicated and encapsulated downlink TCP packets and forward them to the user equipment.
  • the first edge node determines whether the uplink TCP packet is directed to the second base station cell according to whether the uplink TCP packet is a newly established TCP connection.
  • Third-party server when the second base station cell deploys the first edge node, the first edge node determines whether the uplink TCP packet is directed to the second base station cell according to whether the uplink TCP packet is a newly established TCP connection.
  • Third-party server when the second base station cell deploys the first edge node, determines whether the uplink TCP packet is directed to the second base station cell according to whether the uplink TCP packet is a newly established TCP connection. Third-party server.
  • FIG. 6 shows a case where the base station cell after the handover includes the edge node when the user equipment performs the base station cell handover.
  • the third party server may be referred to as APP-Edge, and the third party server includes third party server 1 (APP-Edge 1) and third party server 2 (APP-Edge 2).
  • the edge node can be MCDN-Edge, and the edge node includes edge node 1 (MCDN-Edge 1) and edge node 2 (MCDN-Edge 2).
  • the central node can be MCDN-Core.
  • the third party server 1 and the edge node 1 may be deployed in a radio access network of the first base station cell or an IP transmission network of the radio access network and the wireless core network, and the third party server 2 and the edge node 2 may be deployed in the second base station.
  • the process shown in Figure 6 includes:
  • the edge node 1 registers a TCP session with the central node.
  • the UE is served by the third party server 1 of the first base station cell before the UE handover.
  • the UE moves to the second base station cell to cause handover.
  • the uplink TCP packet of the UE will go through the MCDN-Edge 2 where the cell is located after the handover.
  • the edge node 2 determines whether the TCP packet is consistent with the third-party server 2.
  • the judgment condition is:
  • the IP to be drained is the IP of the APP-Edge 2 service, which is TCP SYN (indicating that a new TCP session will be established); or
  • the IP to be diverted is the IP of the APP-Edge 2 service, which is an uplink TCP packet other than the TCP SYN.
  • the MCDN-Edge 2 has recorded the session information.
  • the central node detects that the TCP packet is registered, and learns that the UE has a handover.
  • the MCDN-Core receives the uplink TCP packet of the previously registered TCP session. If no cell handover occurs, the TCP packet will not be received. Therefore, after receiving the uplink TCP packet, it can be concluded that the UE has already performed cell handover.
  • the central node copies and forwards the received uplink TCP packet to the edge node 1 that registers the TCP session by using an outband message.
  • Edge node 1 (MCDN-Edge 1) will sense that the UE has a cell handover.
  • the edge node 1 performs the destination address replacement on the copied uplink TCP packet.
  • the method shown in FIG. 5 corresponds to an embodiment of diverting by parsing a DNS response message. If the DNS request message is used for trafficking, the process of destination address replacement 606 is not required. In 607, the TCP packet is directly sent to the third party server 1.
  • the edge node 1 sends the replaced uplink TCP packet to the third-party server 1.
  • the third-party server 1 sends a downlink TCP packet to the edge node 1.
  • the edge node 1 receives the downlink TCP packet, and learns that the UE has a cell handover.
  • edge node 1 replaces the downlink TCP packet with the source address, the edge node 1 copies, encapsulates, and sends the packet to the central node by using an outband message.
  • the central node sends the downlink TCP packet to the UE.
  • the central node may send a downlink TCP packet to the edge node 2; the edge node 2 forwards the downlink TCP packet to the UE.
  • the UE continues the original TCP session and sends an uplink TCP packet.
  • the UE may send an uplink TCP packet to the edge node 2; the edge node 2 forwards the packet to the central node to the uplink TCP packet.
  • the embodiment of the present invention may repeat steps 604-611.
  • edge node 2 in the process in FIG. 6 is the first edge node of the second cell where the UE is switched.
  • FIG. 6 described above describes the case where the switched second base station cell includes the edge node 2. If the switched second base station cell does not include the edge node 2, the process is only missing step 603 compared to the process shown in FIG. 6, and the remaining steps are the same. To avoid repetition, it will not be described in detail here.
  • FIG. 7 is a schematic flowchart of a process of data distribution according to an embodiment of the present invention.
  • the central node may perform data distribution on the third-party server according to the location information of the edge node.
  • APP-HQ central server
  • APP-Edge third-party server
  • MCDN-Core central node
  • the edge node registers with the central node (MCDN-Core), and the MCDN-Core can know the MCDN-Edge number, geographical location and cell classification of the access. According to the geographical location, you can set the province, city, district, and district type (such as school, airport, commercial center, etc.) corresponding to the MCDN-Edge service range.
  • the third party server may be an APP-Edge
  • the edge node may be an MCDN-Edge
  • the central node may be an MCDN-Core.
  • the process shown in Figure 7 includes:
  • the central node determines geographic location information of the edge node according to the registration request of the edge node.
  • the central node determines the address location information, that is, the corresponding province, city, district, county, cell type, and the like may be set according to the geographic location.
  • the Internet content provider CP sends a domain name hosting request to the central node.
  • the target city or the target cell type may be selected.
  • the central node authenticates the CP.
  • the central node selects the target edge node according to the request of the CP (for example, the target city and/or the target cell type), and selectively sends the domain name hosting request to the corresponding edge node.
  • the target edge node for example, the target city and/or the target cell type
  • the central node sends a domain name hosting request to the edge node.
  • the edge node performs traffic guidance.
  • the central node returns a domain name hosting response to the CP.
  • the CP sends a content injection/update/delete request to the central node.
  • the central node authenticates the CP, and selects to send a content injection/update/delete request to the department. Part or all of the wireless access network.
  • the central node returns a content injection/update/delete response to the CP.
  • the central node sends a content injection/update/delete request to the third-party server through the edge node.
  • the third-party server performs corresponding processing according to the content injection/update/delete request.
  • the third party server receives the content injection/update/delete request, and if it is a content deletion request, deletes the local URL content; if it is a content injection/update request, it is provided by MCDN-Core.
  • the SOCKS or HTTP/HTTP proxy server initiates a request to acquire content from the source station.
  • the third-party server sends an injection/update content request to the CP through the central node, and the CP sends an injection/update content response to the third-party server through the central node.
  • the third party server saves the injected or updated content.
  • FIG. 8 is a schematic flowchart of a process of charging processing according to an embodiment of the present invention.
  • the edge node may report the traffic usage of the third-party server and the user equipment to the central node; the central node may perform charging processing according to the reported traffic usage, so as to facilitate charging.
  • the system performs billing.
  • the third party server may be an APP-Edge
  • the edge node may be an MCDN-Edge
  • the central node may be an MCDN-Core.
  • the process shown in FIG. 7 is a process of charging a UE.
  • the process shown in Figure 7 includes:
  • the UE initiates an activation PDP request to the GGSN/PGW.
  • GGSN/PGW activates the PDP of the UE.
  • the GGSN/PGW sends the dial-up user remote authentication service charging start request message to the central node.
  • the central node returns a dialing user remote authentication service charging start response message to the GGSN/PGW.
  • the GGSN/PGW returns a PDP activation response to the UE.
  • the central node acquires PDP session information of the UE.
  • the central node may obtain the PDP of the UE from the dial-up user remote authentication service charging start response message.
  • Session information includes a UE IP, a mobile phone number (MSISDN), an APN, a bearer type, and the like;
  • the third-party server provides services for the UE.
  • the edge node may send an uplink service flow to the third-party server; the third-party server sends the downlink service flow to the edge node.
  • the edge node accumulates traffic usage of the third party server and the UE.
  • the edge node sends a traffic report request to the central node.
  • the edge node may periodically report traffic to the central node by using an out-of-band message.
  • the central node performs charging processing according to the traffic reported by the edge node.
  • the central node obtains the corresponding MSISDN through the UE IP according to the traffic reported by the edge node, and performs charging processing.
  • the central node can return the accounting processing result to the edge node through the out-of-band message.
  • the central node may send a charging request to the charging system, and the charging system returns a charging response to the central node.
  • the central node sends a traffic report response to the edge node.
  • the edge node performs control processing according to the charging processing result.
  • the process of performing control processing by the edge node may include:
  • the data is sent to the terminal; if the accounting process fails, the data is sent to the UE.
  • the embodiment of the present invention can also perform charging on a third-party server.
  • the central node can grasp the return source traffic of the edge node, and perform backward charging for the third-party server for the part of the traffic; the central node can also grasp the traffic delivered by the edge node to the UE, and perform backward charging on the third-party server for the part of the traffic. .
  • FIG. 9 is a schematic flowchart of a method for network communication according to an embodiment of the present invention.
  • the method can be performed by a network system.
  • the network system to which the method is applied includes a third-party server and an edge node of a network protocol IP transmission network between the radio access network or the radio access network and the wireless core network, and the method shown in FIG. 9 may include:
  • the edge node associates the user equipment with a transmission control protocol TCP connection of the central server. TCP packets are directed to a third-party server;
  • the third-party server stores the distribution data of the central server and responds to the TCP packet according to the distribution data.
  • the third-party server includes an application server or a cache server.
  • the cache server or the application server is sunk from the IDC room located in the metropolitan area network to the local radio access network or the IP transmission network between the radio access network and the wireless core network, and the edge nodes are deployed.
  • the TCP packet of the central server is directed to the cache server or the application server to implement traffic scheduling. In this way, the transmission delay of the radio access network to the packet core network is reduced, thereby improving the user experience.
  • the network system further includes a central node located in the wireless core network, and the method further includes:
  • the edge node registers a TCP connection with the central node, so that the central node learns that the third-party server has served the user equipment at the edge node.
  • the edge node may determine and store the IP address that needs to be booted; replace the DNAT with the destination address according to the IP address that needs to be booted, so as to report the TCP.
  • the text is directed to a third-party server.
  • the edge node determines the IP address that needs to be booted, and the edge node may parse the DNS response message corresponding to the domain name system DNS request message sent by the user equipment to obtain an IP address that needs to be booted.
  • determining, at the edge node, an IP address that needs to be booted includes: the edge node may obtain an IP address that needs to be booted from the network management system.
  • determining, at the edge node, an IP address that needs to be booted includes: the edge node acquiring an IP address that needs to be booted from the central node.
  • the edge node may receive the DNS request message sent by the user equipment; and send the DNS response to the user equipment.
  • the DNS response message carries the IP address of the third-party server.
  • the edge node when the edge node is to analyze the DNS response message, the traffic is introduced.
  • the method shown in FIG. 9 further includes: a central node, which is further configured to copy, encapsulate, and forward the uplink TCP packet sent by the user equipment to the edge node, so as to facilitate the edge.
  • the node learns that the user equipment has been handed over from the first base station cell to the second base station cell; the edge node is further configured to perform the DNAT of the uplink TCP packet according to the IP address to be encapsulated after the duplicated and encapsulated uplink TCP packet is decapsulated.
  • the downstream TCP packet received from the third-party server is copied, encapsulated, and forwarded to the central node; the central node is also used to resolve the copied and encapsulated downlink TCP packets. After being sealed, it is forwarded to the user device.
  • the method shown in FIG. 9 further includes: a central node, and is further configured to The uplink TCP packet sent by the user equipment is copied, encapsulated, and forwarded to the edge node, so that the edge node learns that the user equipment has been handed over from the first base station cell to the second base station cell; the edge node is also used for copying and encapsulating.
  • the uplink TCP packet After the uplink TCP packet is decapsulated, the uplink TCP packet is forwarded to the third-party server; the downlink TCP packet received from the third-party server is copied, encapsulated, and forwarded to the central node; the central node is also used for copying and encapsulating. After the downlink TCP packet is unsealed, it is forwarded to the user equipment.
  • the method shown in FIG. 9 further includes: when the second base station cell deploys the first edge node, the first edge node determines the uplink TCP report according to whether the uplink TCP packet is a newly established TCP connection. Whether the text is directed to a third-party server corresponding to the second base station cell.
  • the method shown in FIG. 9 further includes: the central node may perform data distribution on the third-party server according to the location information of the edge node.
  • the method shown in FIG. 9 further includes: the edge node may report the traffic usage of the third-party server and the user equipment to the central node; the central node may perform the traffic usage according to the reported traffic usage. Billing processing to facilitate billing system billing.
  • the method shown in FIG. 9 further includes: the third-party server may acquire data corresponding to the IP address that needs to be booted from the central server.
  • the cache server or the application server is sunk from the IDC room located in the metropolitan area network to the local radio access network or the IP transmission network between the radio access network and the wireless core network, and the edge is deployed.
  • the node directs TCP packets for the central server to the cache server or application server to implement traffic scheduling. In this way, the transmission delay of the radio access network to the packet core network is reduced, thereby improving the user experience.
  • the edge node and the central node can cooperate with the mobility problem caused by the base station handover of the user equipment to ensure the continuity and integrity of the user service.
  • data return, data distribution and billing functions can be completed.
  • the third-party server does not need to be modified and implemented sinking, which reduces the overall transmission delay of the user service access and improves the user experience.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed systems, devices, and methods 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.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • 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 objectives of the embodiments of the present invention.
  • 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.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • Any connection may suitably be a computer readable medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例提供了一种网络系统和网络通信的方法，包括：位于无线接入网或无线接入网与无线核心网之间的IP传输网的第三方服务器和边缘节点，边缘节点将用户设备针对中心服务器的TCP连接对应的TCP报文引导到第三方服务器，第三方服务器包括应用服务器或缓存服务器，用于存储中心服务器的分发数据并根据分发数据对TCP报文进行响应。本发明实施例将缓存服务器或应用服务器从城域网的IDC机房下沉到本地的无线接入网或无线接入网与无线核心网之间的IP传输网，并部署边缘节点将针对中心服务器的TCP报文引导到缓存服务器或应用服务器，实现流量调度。这样，减少了无线接入网到分组核心网的传输时延，从而提高了用户体验。

Description

网络系统和网络通信的方法
本申请要求于2015年8月28日提交中国专利局、申请号为201510543193.X，发明名称为“网络系统和网络通信的方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信领域，并且更具体地，涉及网络系统和网络通信的方法。
背景技术
内容分发网络(Content Delivery Network，CDN)是构建在基础网络协议(Internet Protocol，IP)承载网络之上，面向多种业务需求的内容递送和流量分配网络。CDN的目的是通过在现有的互联网(Internet)中增加一层新的网络架构，将网站的应用内容发布到最接近用户设备的网络“边缘”，使得用户设备可以就近取得所需的内容，而不需要到应用服务器中获取，可以解决Internet网络拥挤的状况，提高用户设备访问网站的响应速度。
内容分发网络能够将源服务器中的内容分发至分布式部署的服务节点中，通过应用流量调度技术，可按照指定的策略将用户请求自动指到全局最优的服务节点，由该节点就近为用户提供服务。但是，现有的CDN方案中，服务节点一般部署在城域网的互联网数据中心(Internet Data Center，IDC)机房，因此，移动网络用户访问服务节点的时延较长，用户体验较差。
发明内容
本发明实施例提供一种网络系统和网络通信的方法，能够减少用户访问服务节点的时延，提高用户体验。
第一方面，提供了一种网络系统，用于进行内容分发，包括：位于无线接入网或该无线接入网与无线核心网之间的网络协议IP传输网的第三方服务器和边缘节点，其中，该边缘节点用于将用户设备针对中心服务器的传输控制协 议TCP连接对应的TCP报文引导到该第三方服务器，该第三方服务器包括应用服务器或缓存服务器，用于存储该中心服务器的分发数据并根据该分发数据对该TCP报文进行响应。
结合第一方面，在第一方面的第一种可能的实现方式中，还包括：位于该无线核心网的中心节点，其中，该边缘节点，还用于向该中心节点注册该TCP连接，以便于该中心节点获知该第三方服务器已经在该边缘节点处为该用户设备提供服务。
结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，该边缘节点，具体用于确定需要引导的IP地址并进行存储；根据该需要引导的IP地址，将该TCP报文进行目的地址替换DNAT，以便于将该TCP报文引导到该第三方服务器。
结合第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，该边缘节点，具体用于解析该用户设备发送的域名系统DNS请求消息对应的DNS响应消息，得到该需要引导的IP地址。
结合第一方面的第二种可能的实现方式，在第一方面的第四种可能的实现方式中，该边缘节点，具体用于从网管系统获取该需要引导的IP地址。
结合第一方面的第二种可能的实现方式，在第一方面的第五种可能的实现方式中，该边缘节点，具体用于从该中心节点获取该需要引导的IP地址。
结合第一方面的第一种可能的实现方式，在第一方面的第六种可能的实现方式中，该边缘节点，具体用于接收该用户设备发送的DNS请求消息；向该用户设备发送DNS响应消息，该DNS响应消息携带该第三方服务器的IP地址。
结合第一方面的第二种至第五种可能的实现方式中的任一种可能的实现方式，在第一方面的第七种可能的实现方式中，当该用户设备从包括该边缘节点的第一基站小区切换到第二基站小区时，该中心节点，还用于将该用户设备发送的上行TCP报文进行复制、封装并转发到该边缘节点，以便于该边缘节点获知该用户设备已经从该第一基站小区切换到该第二基站小区；该边缘节点，还用于将该复制、封装后的上行TCP报文解封后，根据该需要引导的IP地址将该 上行TCP报文进行DNAT并转发给该第三方服务器；将从该第三方服务器接收的下行TCP报文进行源地址替换SNAT后，复制、封装并转发到该中心节点；该中心节点，还用于将该复制、封装后的下行TCP报文解封后，转发到该用户设备。
结合第一方面的第六种可能的实现方式，在第一方面的第八种可能的实现方式中，当该用户设备从包括该边缘节点的第一基站小区切换到第二基站小区时，该中心节点，还用于将该用户设备发送的上行TCP报文进行复制、封装并转发到该边缘节点，以便于该边缘节点获知该用户设备已经从该第一基站小区切换到该第二基站小区；该边缘节点，还用于将该复制、封装后的上行TCP报文解封后，将该上行TCP报文转发给该第三方服务器；将从该第三方服务器接收的下行TCP报文进行复制、封装并转发到该中心节点；该中心节点，还用于将该复制、封装后的下行TCP报文解封后，转发到该用户设备。
结合第一方面的第七种或第八种可能的实现方式，在第一方面的第九种可能的实现方式中，当该第二基站小区部署第一边缘节点时，该第一边缘节点根据该上行TCP报文是否为新建的TCP连接判断该上行TCP报文是否引导到该第二基站小区对应的第三方服务器。
结合第一方面的第一种至第九种可能的实现方式中的任一种可能的实现方式，在第一方面的第十种可能的实现方式中，该中心节点，还用于根据该边缘节点的位置信息，对该第三方服务器进行数据分发。
结合第一方面或第一方面第一种至第十种可能的实现方式中的任一种可能的实现方式，在第一方面的第十一种可能的实现方式中，该边缘节点，还用于将该第三方服务器与该用户设备交互的流量使用量向该中心节点上报；该中心节点，还用于根据该上报的流量使用量，进行计费处理，以便于计费系统进行计费。
结合第一方面或第一方面第一种至第十一种可能的实现方式中的任一种可能的实现方式，在第一方面的第十二种可能的实现方式中，该第三方服务器，还用于从该中心服务器获取该需要引导的IP地址对应的数据。
第二方面，提供了一种网络通信的方法，该方法应用的网络系统包括位于 无线接入网或该无线接入网与无线核心网之间的网络协议IP传输网的第三方服务器和边缘节点，该方法包括：该边缘节点将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到该第三方服务器；该第三方服务器存储该中心服务器的分发数据并根据该分发数据对该TCP报文进行响应，该第三方服务器包括应用服务器或缓存服务器。
结合第二方面，在第二方面的第一种可能的实现方式中，该网络系统还包括位于该无线核心网的中心节点，该方法还包括：该边缘节点向该中心节点注册该TCP连接，以便于该中心节点获知该第三方服务器已经在该边缘节点处为该用户设备提供服务。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，该边缘节点将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到该第三方服务器，包括：该边缘节点确定需要引导的IP地址并进行存储；根据该需要引导的IP地址，将该TCP报文进行目的地址替换DNAT，以便于将该TCP报文引导到该第三方服务器。
结合第二方面的第二种可能的实现方式，在第二方面的第三种可能的实现方式中，该边缘节点确定需要引导的IP地址，包括：该边缘节点解析该用户设备发送的域名系统DNS请求消息对应的DNS响应消息，得到该需要引导的IP地址。
结合第二方面的第二种可能的实现方式，在第二方面的第四种可能的实现方式中，该边缘节点确定需要引导的IP地址，包括：该边缘节点从网管系统获取该需要引导的IP地址。
结合第二方面的第二种可能的实现方式，在第二方面的第五种可能的实现方式中，该边缘节点确定需要引导的IP地址，包括：该边缘节点从该中心节点获取该需要引导的IP地址。
结合第二方面的第一种可能的实现方式，在第二方面的第六种可能的实现方式中，在该边缘节点将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到该第三方服务器之前，还包括：该边缘节点接收该用户设 备发送的DNS请求消息；向该用户设备发送DNS响应消息，该DNS响应消息携带该第三方服务器的IP地址。
结合第二方面的第二种至第五种可能的实现方式中的任一种可能的实现方式，在第二方面的第七种可能的实现方式中，当该用户设备从包括该边缘节点的第一基站小区切换到第二基站小区时，该方法还包括：该中心节点，还用于将该用户设备发送的上行TCP报文进行复制、封装并转发到该边缘节点，以便于该边缘节点获知该用户设备已经从该第一基站小区切换到该第二基站小区；该边缘节点，还用于将该复制、封装后的上行TCP报文解封后，根据该需要引导的IP地址将该上行TCP报文进行DNAT并转发给该第三方服务器；将从该第三方服务器接收的下行TCP报文进行复制、封装并转发到该中心节点；该中心节点，还用于将该复制、封装后的下行TCP报文解封后，转发到该用户设备。
结合第二方面的第六种可能的实现方式，在第二方面的第八种可能的实现方式中，当该用户设备从包括该边缘节点的第一基站小区切换到第二基站小区时，该方法还包括：该中心节点，还用于将该用户设备发送的上行TCP报文进行复制、封装并转发到该边缘节点，以便于该边缘节点获知该用户设备已经从该第一基站小区切换到该第二基站小区；该边缘节点，还用于将该复制、封装后的上行TCP报文解封后，将该上行TCP报文转发给该第三方服务器；将从该第三方服务器接收的下行TCP报文进行源地址替换SNAT后，复制、封装并转发到该中心节点；该中心节点，还用于将该复制、封装后的下行TCP报文解封后，转发到该用户设备。
结合第二方面的第七种或第八种可能的实现方式，在第二方面的第九种可能的实现方式中，当该第二基站小区部署第一边缘节点时，该方法还包括：该第一边缘节点根据该上行TCP报文是否为新建的TCP连接判断该上行TCP报文是否引导到该第二基站小区对应的第三方服务器。
结合第二方面的第一种至第九种可能的实现方式中的任一种可能的实现方式，在第二方面的第十种可能的实现方式中，该方法还包括：该中心节点根据该边缘节点的位置信息，对该第三方服务器进行数据分发。
结合第二方面的第一种至第十种可能的实现方式中的任一种可能的实现方式，在第二方面的第十一种可能的实现方式中，该方法还包括：该边缘节点将该第三方服务器与该用户设备交互的流量使用量向该中心节点上报；该中心节点根据该上报的流量使用量，进行计费处理，以便于计费系统进行计费。
结合第二方面或第二方面的第一种至第十一种可能的实现方式中的任一种可能的实现方式，在第二方面的第十二种可能的实现方式中，该方法还包括：该第三方服务器从该中心服务器获取该需要引导的IP地址对应的数据。
本发明实施例中将缓存服务器或应用服务器从位于城域网的IDC机房下沉到本地的无线接入网或无线接入网与无线核心网之间的IP传输网，并部署边缘节点将针对中心服务器的TCP报文引导到缓存服务器或应用服务器，实现流量调度。这样，减少了无线接入网到分组核心网的传输时延，从而提高了用户体验。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明可应用的内容分发网络的示意结构图。
图2是本发明一个实施例的网络系统的示意结构图。
图3是本发明另一实施例的网络系统的示意性结构图。
图4为本发明一个实施例的流量引导的过程的示意性流程图。
图5为本发明另一实施例的流量引导的过程的示意性流程图。
图6是本发明一个实施例的用户设备进行基站小区切换的过程的示意性流程图。
图7是本发明一个实施例的数据分发的过程的示意性流程图。
图8是本发明一个实施例的计费处理的过程的示意性流程图。
图9是本发明一个实施例的网络通信的方法的示意性流程图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明的一部分实施例，而不是全部实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都应属于本发明保护的范围。
应理解，本发明实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(GSM，Global System of Mobile communication)系统、码分多址(CDMA，Code Division Multiple Access)系统、宽带码分多址(WCDMA Wideband Code Division Multiple Access)系统、通用分组无线业务(GPRS，General Packet Radio Service)、长期演进(LTE，Long Term Evolut ion)系统、LTE频分双工(FDD，Frequency Division Duplex)系统、LTE时分双工(TDD，Time Division Duplex)、通用移动通信系统(UMTS，Universal Mobile Telecommunication System，)或全球互联微波接入(WiMAX，Worldwide Interoperability for Microwave Access)通信系统等。
无线接入网(Radio Access Network，RAN)是指固定用户全部或部分以无线的方式接入到交换机，通常无线接入网所接入的交换机是指公共交换电话网络(Public Switched Telephone Network，PSTN)的交换机，也可以是综合业务数字网(Integrated Services Digital Network，ISDN)的交换机。无线接入网是地面的基础设施，为3G无线通信服务，包括高速移动的设备接入到Internet。无线接入网可以为UTRAN(Universal Terrestrial Radio Access Network，通用陆地无线接入网络)、GERAN(GSM EDGE Radio Access Network，GSM/EDGE无线接入网络)或E-UTRAN(Evolved Universal Terrestrial Radio Access Network，演进通用陆地无线接入网络)，移动管理网元可以是移动性管理实体(Mobility Management Entity，MME)或者GPRS服务支撑节点(Serving GPRS Support Node，SGSN)。
无线接入网在不同的系统中可包括不同的网元。例如，LTE和LTE-A中无线接入网的网元包括eNB(eNodeB，演进型基站)，WCDMA中无线接入网络的网元包括RNC(Radio Network Controller，无线网络控制器)和NodeB，无线局域网中的网元包括访问接入点(Access Point，AP)，类似地，WiMax(Worldwide Interoperability for Microwave Access，全球微波互联接入)等其它无线网络也可以使用与本申请实施例类似的方案，只是基站系统中的相关模块可能有所不同，本申请实施例并不限定。
无线核心网(Core Nerwork，CN)用于将呼叫请求或数据请求连接到不同的网络上。核心网设备可以是通用无线分组业务(General Packet Radio Service，GPRS)业务支持节点(Service GPRS Support Node，SGSN)。
图1是本发明可应用的内容分发网络的示意结构图。图1所示的内容分发网络包括源服务器101，至少一个服务节点102和至少一个用户设备。源服务器101为提供内容的服务器，可以为Web服务器等。
源服务器101将内容分发到至少一个服务节点102。每个服务节点102可以向不同的用户设备提供服务。如图1示出的四个用户设备可以由三个服节点102提供服务。
图2是本发明一个实施例的网络系统的示意结构图。该网络系统用于内容分发，图2的网络系统包括：
位于无线接入网或无线接入网与无线核心网之间的网络协议IP传输网的第三方服务器201和边缘节点202，其中，边缘节点用于将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到第三方服务器，第三方服务器包括应用服务器或缓存服务器，用于存储中心服务器的分发数据并根据分发数据对TCP报文进行响应。
本发明实施例中将缓存服务器或应用服务器从位于城域网的IDC机房下沉到本地的无线接入网或无线接入网与无线核心网之间的IP传输网，并部署边缘节点将针对中心服务器的TCP报文引导到缓存服务器或应用服务器，实现流量调度。这样，减少了无线接入网到分组核心网的传输时延，从而提高了用户体 验。
中心服务器可以为源服务器，中心服务器用于将数据分发到第三方服务器。网络系统可以包括多个第三方服务器。第三方服务器可以包括缓存服务器或应用服务器。缓存服务器可以为CDN服务节点。当为缓存服务器(例如CDN服务节点)，则中心服务器将内容分发到该缓存服务器；若为应用服务器，则中心服务器将应用分发到该应用服务器。应理解，内容分发和应用分发都可以为数据分发。
应理解，图2中仅仅示出了本发明实施例的发明点相关的部分，图2所示的网络系统还可以包括用户设备，分组核心网和中心服务器等。图2所示的第三方服务器的个数可以为多个。下文将对网络系统的整个流程进行详细描述。还应理解，图2中仅仅示出了边缘节点和第三方服务器位于无线接入网这一实施例，边缘节点和第三方服务器还可以位于无线接入网与无线核心网之间的IP传输网中。
由于现有CDN方案中的CDN服务节点一般位于城域网，而且，由于无线接入网一般不提供公网IP，用户请求无法通过公网IP进行调度。因此，CDN服务节点无法部署在无线接入网。本发明实施例中将CDN服务节点下沉到无线接入网或无线接入网与无线核心网之间的IP传输网，同时部署边缘节点来完成引导机制。
边缘节点功能可以由软件程序实现，用来完成引导机制等功能。应理解，协议中引导的过程可以称为本地引流(Local Breakout)，本发明实施例中将Local Breakout的过程统一写作引导。图2所示为边缘节点和第三方服务器位于无线接入网的场景。应理解，边缘节点和第三方服务器还可以位于无线接入网和无线核心网之间的IP传输网络。如图2所示，无线接入网中可以部署多个第三方服务器。应理解，本发明仅仅对多个第三方服务器中的一个第三方服务器进行阐述。
边缘节点也可以称为移动内容分发网络边缘节点(Mobile Content Delivery Network edge，MCDN-edge)。
应理解，该网络系统可以通过DNAT将流量引入本地部署的第三方服务器，也可以通过DNS劫持将流量引入本地部署的第三方服务器。
可选地，作为另一实施例，通过DNAT将流量引入本地部署的第三方服务器包括：边缘节点202可以确定需要引导的IP地址并进行存储；根据需要引导的IP地址，将TCP报文进行目的地址替换DNAT，以便于将TCP报文引导到第三方服务器。
具体地，例如，若用户设备想要访问百度网页，需要发送域名，由DNS服务器进行解析该域名，得到该域名对应的目的IP地址。该目的IP地址即为本发明实施例中需要引导的IP地址。应理解，第三方服务器中可以预先放置该目的IP地址对应的数据，也能提供应用服务。本发明实施例中的边缘节点对用户设备发送的上行TCP报文进行目的IP地址替换，使得TCP报文由原先引导到中心服务器的IP地址转换为引导到第三方服务器的IP地址，使得第三方服务器为用户设备提供服务。
可选地，作为一个实施例，边缘节点可以通过解析DNS响应消息确定需要引导的IP地址。
具体地，边缘节点202可以确定需要引导的IP地址的过程包括：边缘节点202可以通过解析用户设备发送的域名系统DNS请求消息对应DNS响应消息，得到需要引导的IP地址。
可选地，作为另一实施例，边缘节点202也可以通过从网管系统获取需要引导的IP地址。
第三方服务器可以称为APP-Edge，边缘节点可以称为MCDN-Edge。边缘节点通过解析DNS请求消息对应的DNS响应消息得到IP地址的过程可以如下：
1)UE发起DNS请求消息；
应理解，在边缘节点上预先配置第三方服务器在本地提供服务的私网IP以及该第三方服务器(APP-Edge)处理的域名和公网IP。
还应理解，UE发起DNS请求消息的过程可以包括：UE通过边缘节点向DNS服务器(DNS Server)发送该域名的DNS Request，DNS Server通过边缘节点 向UE返回对应的DNS响应消息(DNS Response)。
2)边缘节点解析该DNS响应消息，并保存需要引导的IP地址。
可选地，作为另一实施例，边缘节点102还可以通过DNS劫持将流量引入本地部署的第三方服务器。
具体地，边缘节点202可以接收用户设备发送的第三方服务器(APP-Edge)处理域名的DNS请求消息；向用户设备发送DNS响应消息，DNS响应消息携带第三方服务器的IP地址。
边缘节点通过劫持DNS请求消息得到IP地址的过程可以如下：
1)UE向DNS服务器发送该域名的DNS Request；
2)MCDN-Edge劫持DNS Request，构造DNS Response，该DNS Response中包括APP-Edge的IP地址。
应理解，在边缘节点(MCDN-Edge)上预先配置需要引流的域名及其对应的第三方服务器私网IP。当UE发起DNS请求消息时，MCDN-Edge进行拦截，直接构造DNS响应消息，返回该域名对应的第三方服务器私网IP。
3)向UE发送DNS Response。
应理解，为避免UE缓存DNS结果后，UE切换到未部署边缘节点/第三方服务器的基站后导致业务访问失败，DNS的生存时间(Time To Live，TTL)需要设置为较小的值，例如可以设置为1秒。
图3是本发明另一实施例的网络系统的示意性结构图。图3中与图2相同的装置可以采用相同的编号，图3所示的网络系统还包括：
位于无线核心网的中心节点203，其中，边缘节点202，还可以向中心节点注册TCP连接，以便于中心节点203获知第三方服务器201已经在边缘节点处为用户设备提供服务。
本发明实施例中将缓存服务器或应用服务器从位于城域网的IDC机房下沉到本地的无线接入网或无线接入网与无线核心网之间的IP传输网，并部署边缘节点将针对中心服务器的TCP报文引导到缓存服务器或应用服务器，实现流量调度。这样，减少了无线接入网到分组核心网的传输时延，从而提高了用户体 验。
另外，在无线核心网部署中心节点，边缘节点和中心节点能够配合完成用户设备发生基站切换导致的移动性问题，保证用户业务的连续性和完整性。同时能够完成数据回源、数据分发和计费功能。这样，第三方服务器不需要修改并实现下沉，减少了用户业务访问的整体传输时延，提高了用户体验。
应理解，图3中还包括用户设备UE，分组核心网和服务器设备。其中服务器设备包括中心服务器。
还应理解，中心节点可以为应用分发网络中心节点(MCDN-Core)，是系统的汇聚节点。MCDN-Core可以部署于网关GPRS支撑节点(Geteway GPRS Support Node，GGSN)和分组数据网网关(Packet Data Network Gateway，PGW)侧的Gi/SGi口，负责UE进行基站切换的移动性管理、计费以及通信代理等。
具体地，无线接入网和边缘节点(MCDN-Edge)可以采用GPRS隧道协议(General Packet Radio Service Tunneling Protocol，GTP)中的GTP-U消息，边缘节点和第三方服务器(APP-Edge)可以采用IP消息，边缘节点和中心节点(MCDN-Core)可以采用带外通信。带外(Out of band)通信是指完全通过不同的信道来传输数据。例如，协议通常不适用与普通数据相同的通道，而是使用另外的通道来传输重要的数据。具体地，部署在边缘节点的第三方服务器通过带外通道与中心服务器实现信息交互。
可选地，作为另一实施例，若第三方服务器中不包括需要引导的IP地址对应的数据时，该第三方服务器还可以从中心服务器获取需要引导的IP地址对应的数据。
具体地，第三方服务器可以通过中心节点提供的带外通道与中心服务器进行信息交互，从而可以从中心服务器获取需要引导的IP地址对应的数据。
本发明实施例中第三方服务器没有公网IP，无法直接和外网上的中心服务器直接通信。第三方服务器设置中心节点为防火墙安全会话转换协议(Protocol for sessions traversal across firewall securely，SOCKS)代理或者超文本传输协议/超文本传送协议服务器(Hypertext Transfer Protocol/ Hypertext Transport Protocol Server，HTTP/HTTPS)代理，通过带外通道，与中心服务器实现信息交互，实现了数据回源。
可选地，作为另一实施例，在流量引导的过程中，边缘节点可以在用户设备和第三方服务器之间进行消息转发。该消息可以为TCP连接对应的TCP报文。
下面将结合图4详细描述通过解析DNS请求消息获取需要引导的IP地址并进行流量引导的过程。图4为本发明一个实施例的流量引导的过程的示意性流程图。第三方服务器可以称为APP-Edge，边缘节点可以称为MCDN-Edge，中心节点可以称为MCDN-Core。图4所示的过程包括：
401，UE发起DNS请求过程；
应理解，在边缘节点上预先配置第三方服务器在本地提供服务的私网IP以及该APP-Edge处理的域名和公网IP。
具体地，401中UE发起DNS请求过程包括：UE通过边缘节点向DNS服务器(DNS Server)发送DNS请求消息(DNS Request)；DNS Server通过边缘节点返回DNS响应消息(DNS Response)。
402，边缘节点解析该DNS响应消息，并保存需要引导的IP地址。
403，UE发起TCP连接。
具体地，UE可以向边缘节点发送上行TCP SYN报文来发起TCP连接。
404，边缘节点检测到TCP SYN报文的目的IP在第三服务器的服务范围，则记录该TCP会话。
405，边缘节点向中心节点注册TCP会话。
具体地，MCDN-Edge将TCP会话的IP五元组(源IP/源端口/目的IP/目的端口/TCP协议)通过带外通道向MCDN-Core注册。
可选地，作为另一实施例，该注册过程也可以使用带内通道。MCDN-Edge将TCP会话的UE上行TCP SYN报文复制并转发到无线核心网，并在TCP头部字段中(例如Opt ion字段)添加两个标识信息：
边缘节点标识信息(MCDN-Edge ID)：用于标识当前的MCDN-Edge编号，MCDN-Core根据该编号可以获知当前会话所在的MCDN-Edge。若后续UE进行小 区切换时，可以通过带外通道和该MCDN-Edge多个交互实现移动性管理。
本地过程(Local Process)：用于标识该TCP连接已经由MCDN-Edge分流到APP-Edge处理，MCDN-Core识别后不会将该TCP报文转发到中心服务器。
406，中心节点保存TCP会话。
具体地，MCDN-Core获知该TCP会话已经在MCDN-Edge处提供服务。
407，边缘节点将TCP报文进行目的地址替换DNAT。
408，边缘节点向第三方服务器发送替换后的TCP报文。
应理解，TCP报文即为UE发送的上行TCP SYN报文，边缘节点进行替换。TCP报文的目的IP即为需要引导的IP地址，边缘节点将该需要引导的IP地址转换为第三方服务器的IP地址，则UE实际上是向第三方服务器请求服务。由于第三方服务器实现已经分发好数据，则可以直接向UE提供服务。
409，TCP建连消息转发。
具体地，UE和第三方服务器通过边缘节点进行TCP建连消息转发。MCDN-Edge向APP-Edge发送替换后的上行TCP SYN报文后，第三方服务器向MCDN-Edge发送下行TCP SYN ACK报文；MCDN-Edge将下行TCP SYN ACK报文转发给UE；UE向MCDN-Edge发送上行TCP ACK报文；MCDN-Edge将上行TCP ACK报文转发给APP-Edge。
410，UE和第三方服务器进行数据交互。
具体地，UE和第三方服务器通过边缘节点进行数据交互。
411，第三方服务器从中心服务器获取需要引导的IP地址对应的数据。
可选地，若第三方服务器本地没有需要引导的IP地址对应的数据时，可以通过中心节点提供的带外通道和中心服务器进行信息交互，获取对应的数据。
412，UE和第三方服务器通过边缘节点关闭TCP连接。
413，边缘节点向中心节点请求取消注册。
414，中心节点删除TCP会话。
下面将结合图5详细描述通过DNS劫持获取需要引导的IP地址并进行流量引导的过程。图5为本发明另一实施例的流量引导的过程的示意性流程图。第 三方服务器可以为APP-Edge，边缘节点可以为MCDN-Edge，中心节点可以为MCDN-Core。图5所示的过程包括：
501，UE向DNS服务器发送DNS请求消息；
应理解，在边缘节点上预先配置需要引流的域名及其对应的第三方服务器的私网IP。具体地，UE向DNS服务器发送DNS请求消息后，边缘节点将会劫持该DNS请求消息。
502，边缘节点根据DNS请求消息构造DNS响应消息，DNS响应消息包括第三方服务器的IP地址。
503，边缘节点向UE发送DNS响应消息。
具体地，MCDN-Edge检测到DNS请求的域名是APP-Edge的服务域名，则构造DNS响应消息，返回该域名对应的第三方服务器私网IP。
504，UE发起TCP连接。
具体地，UE可以向边缘节点发送上行TCP SYN报文来发起TCP连接。
505，边缘节点检测到TCP SYN报文的目的IP是第三方服务器的IP，则记录该TCP会话。
506，边缘节点向中心节点注册TCP会话。
具体地，MCDN-Edge将TCP会话的IP五元组(源IP/源端口/目的IP/目的端口/TCP协议)通过带外通道向MCDN-Core注册。
可选地，作为另一实施例，该注册过程也可以使用带内通道。MCDN-Edge将TCP会话的UE上行TCP SYN报文复制并转发到无线核心网，并在TCP头部字段中(例如Option字段)添加两个标识信息：
边缘节点标识信息(MCDN-Edge ID)：用于标识当前的MCDN-Edge编号，MCDN-Core根据该编号可以获知当前会话所在的MCDN-Edge。若后续UE进行小区切换时，可以通过带外通道和该MCDN-Edge多个交互实现移动性管理。
本地过程(Local Process)：用于标识该TCP连接已经由MCDN-Edge分流到APP-Edge处理，MCDN-Core识别后不会将该TCP报文转发到中心服务器。
507，中心节点保存TCP会话。
具体地，MCDN-Core获知该TCP会话已经在MCDN-Edge处提供服务。
508，边缘节点将TCP报文发送到第三方服务器。
509，UE和第三方服务器通过边缘节点进行TCP建连消息转发。
具体地，MCDN-Edge向APP-Edge发送替换后的上行TCP SYN报文；第三方服务器向MCDN-Edge发送下行TCP SYN ACK报文；MCDN-Edge将下行TCP SYN ACK报文转发给UE；UE向MCDN-Edge发送上行TCP ACK报文；MCDN-Edge将上行TCP ACK报文转发给APP-Edge。
510，UE和第三方服务器通过边缘节点进行数据交互。
511，第三方服务器从中心服务器获取需要引导的IP地址对应的数据。
可选地，若第三方服务器本地没有需要引导的IP地址对应的数据时，可以通过中心节点提供的带外通道和中心服务器进行信息交互，获取对应的数据。
512，UE和第三方服务器通过边缘节点关闭TCP连接。
513，边缘节点向中心节点请求取消注册。
514，中心节点删除TCP会话。
图6是本发明一个实施例的用户设备进行基站小区切换的过程的示意性流程图。
应理解，用户设备在切换到另一个基站小区后，该小区可以配置边缘节点，也可以不配置边缘节点。将流量引入本地部署的第三方服务器的过程可以通过解析DNS响应消息，也可以通过劫持DNS请求消息。对于这两个实施例，小区切换的过程可以不相同。
可选地，作为另一实施例，若通过解析DNS响应消息将流量引入本地部署的第三方服务器时，中心节点还可以将用户设备发送的上行TCP报文进行复制、封装并转发到边缘节点，以便于边缘节点获知用户设备已经从第一基站小区切换到第二基站小区；边缘节点还可以将复制、封装后的上行TCP报文解封后，根据需要引导的IP地址将上行TCP报文进行DNAT并转发给第三方服务器；将从第三方服务器接收的下行TCP报文进行复制、封装并转发到中心节点；中心节点还可以将复制、封装后的下行TCP报文解封后，转发到用户设备。
可选地，作为另一实施例，若通过劫持DNS请求消息将流量引入本地部署的第三方服务器时，中心节点还可以将用户设备发送的上行TCP报文进行复制、封装并转发到边缘节点，以便于边缘节点获知用户设备已经从第一基站小区切换到第二基站小区；边缘节点还可以将复制、封装后的上行TCP报文解封后，将上行TCP报文转发给第三方服务器；将从第三方服务器接收的下行TCP报文进行复制、封装并转发到中心节点；中心节点还可以将复制、封装后的下行TCP报文解封后，转发到用户设备。
可选地，作为另一实施例，当第二基站小区部署第一边缘节点时，第一边缘节点根据上行TCP报文是否为新建的TCP连接判断上行TCP报文是否引导到第二基站小区对应的第三方服务器。
图6所示为用户设备进行基站小区切换时，切换后的基站小区包括边缘节点的情况。第三方服务器可以称为APP-Edge，第三方服务器包括第三方服务器1(APP-Edge 1)和第三方服务器2(APP-Edge 2)。边缘节点可以为MCDN-Edge，边缘节点包括边缘节点1(MCDN-Edge 1)和边缘节点2(MCDN-Edge 2)。中心节点可以为MCDN-Core。其中，第三方服务器1和边缘节点1可以部署在第一基站小区的无线接入网或者无线接入网与无线核心网的IP传输网，第三方服务器2和边缘节点2可以部署在第二基站小区的无线接入网或者无线接入网与无线核心网的IP传输网。
图6所示的过程包括：
601，边缘节点1向中心节点注册TCP会话。
应理解，UE切换前由第一基站小区的第三方服务器1提供服务。
602，UE移动到第二基站小区导致切换。
具体地，UE的上行TCP报文将经过切换后小区所在的MCDN-Edge 2。
603，边缘节点2判断TCP报文是否符合引流到第三方服务器2。
具体地，该判断条件为：
a、需要引流的IP为APP-Edge 2服务的IP，是TCP SYN(表示将建立新的TCP会话)；或者
b、需要引流的IP为APP-Edge 2服务的IP，是TCP SYN之外的上行TCP报文，MCDN-Edge 2已记录该会话信息。
604，中心节点检测到TCP报文已注册，获知UE发生切换。
具体地，MCDN-Core收到之前已注册的TCP会话的上行TCP报文，如果未发生小区切换，将不会收到该TCP报文。因此收到上行TCP报文后，就可以得出UE已经发生了小区切换。
605，中心节点通过带外消息将收到的上行TCP报文复制并转发到注册该TCP会话的边缘节点1。
边缘节点1(MCDN-Edge 1)将感知UE发生了小区切换。
606，边缘节点1将复制的上行TCP报文进行目的地址替换。
应理解，图5所示的方法对应于通过解析DNS响应消息进行引流的实施例，若通过劫持DNS请求消息进行引流，则不需要进行606这一目的地址替换的过程。在607中，直接将TCP报文发送给第三方服务器1。
607，边缘节点1将替换后的上行TCP报文发送给第三方服务器1。
608，第三方服务器1向边缘节点1发送下行TCP报文。
具体地，边缘节点1接收到下行TCP报文，获知UE发生小区切换，
609，边缘节点1将下行TCP报文进行源地址替换后，复制、封装并通过带外消息发送到中心节点。
610，中心节点将下行TCP报文发送给UE。
具体地，中心节点可以向边缘节点2发送下行TCP报文；边缘节点2将下行TCP报文转发给UE。
611，UE继续原有的TCP会话，发送上行TCP报文。
具体地，UE可以向边缘节点2发送上行TCP报文；边缘节点2向中心节点转发给上行TCP报文。
在此之后，本发明实施例可以重复步骤604-611。
应理解，图6中的过程中的边缘节点2即为UE切换后所在的第二小区的第一边缘节点。上述图6描述的为切换后的第二基站小区包括边缘节点2的情况。 若切换后的第二基站小区不包括边缘节点2时，该过程与图6所示的过程相比，仅仅缺少了步骤603，其余步骤相同。为避免重复，此处不再详细描述。
图7是本发明一个实施例的数据分发的过程的示意性流程图。
可选地，作为另一实施例，中心节点可以根据边缘节点的位置信息，对第三方服务器进行数据分发。
具体地，当公网上的中心服务器(APP-HQ)需要主动分发内容到内网的第三方服务器(APP-Edge)时，通过中心节点(MCDN-Core)统一分发。
边缘节点(MCDN-Edge)向中心节点(MCDN-Core)注册，MCDN-Core可以知道所接入的MCDN-Edge编号、所处地理位置和小区分类等信息。根据地理位置，可以设置该MCDN-Edge服务范围对应的省份、城市、区县、小区类型(如学校、机场、商业中心等)。
应理解，第三方服务器可以为APP-Edge，边缘节点可以为MCDN-Edge，中心节点可以为MCDN-Core。图7所示的过程包括：
701，中心节点根据边缘节点的注册请求，确定边缘节点的地理位置信息。
具体地，中心节点确定地址位置信息，即可以根据该地理位置设置其对应的省份、城市、区县、小区类型等。
702，互联网内容提供商CP向中心节点发送域名托管请求。
具体地，CP发送域名托管请求的同时，可以选择目标城市或目标小区类型等。
703，中心节点对CP进行鉴权。
具体地，中心节点根据CP的请求(例如目标城市和/或目标小区类型)，筛选出目标边缘节点，选择性将域名托管请求发送到对应的边缘节点。
704，中心节点将域名托管请求发送到边缘节点。
705，边缘节点进行流量引导。
706，中心节点向CP返回域名托管响应。
707，CP向中心节点发送内容注入/更新/删除请求。
708，中心节点对CP进行鉴权，选择将内容注入/更新/删除请求发送到部 分或全部的无线接入网。
709，中心节点向CP返回内容注入/更新/删除响应。
710，中心节点通过边缘节点向第三方服务器发送内容注入/更新/删除请求。
711，第三方服务器根据内容注入/更新/删除请求进行相应处理。
具体地，第三方服务器(APP-Edge)收到内容注入/更新/删除请求，如果是内容删除请求，则删除本地上该URL内容；如果是内容注入/更新请求，则通过MCDN-Core提供的SOCKS或HTTP/HTTP代理服务器向源站发起获取内容的请求。
第三方服务器通过中心节点向CP发送注入/更新内容请求，CP通过中心节点向第三方服务器发送注入/更新内容响应。
712，第三方服务器保存注入或更新的内容。
图8是本发明一个实施例的计费处理的过程的示意性流程图。
可选地，作为另一实施例，边缘节点可以将第三方服务器与用户设备交互的流量使用量向中心节点上报；中心节点，可以根据上报的流量使用量，进行计费处理，以便于计费系统进行计费。
应理解，第三方服务器可以为APP-Edge，边缘节点可以为MCDN-Edge，中心节点可以为MCDN-Core。图7所示的过程为对UE进行计费的过程。图7所示的过程包括：
801，UE向GGSN/PGW发起激活PDP请求。
802，GGSN/PGW激活该UE的PDP。
803，GGSN/PGW将拨号用户远程认证服务计费开始请求消息发送给中心节点。
804，中心节点向GGSN/PGW返回拨号用户远程认证服务计费开始响应消息。
805，GGSN/PGW向UE返回PDP激活响应。
806，中心节点获取UE的PDP会话信息。
中心节点可以从拨号用户远程认证服务计费开始响应消息中获取UE的PDP 会话信息。具体地，该PDP会话信息包括UE IP、手机号码(MSISDN)、APN、承载类型等；
807，第三方服务器为UE提供服务。
具体地，边缘节点可以向第三方服务器发送上行业务流；第三方服务器向边缘节点发送下行业务流。
808，边缘节点累计第三方服务器与UE交互的流量使用量。
809，边缘节点向中心节点发送流量上报请求。
具体地，边缘节点可以通过带外消息向中心节点周期性上报流量。
810，中心节点根据边缘节点上报的流量进行计费处理。
具体地，中心节点根据边缘节点上报的流量，通过UE IP得到对应的MSISDN，进行计费处理。中心节点可以通过带外消息，将计费处理结果返回给边缘节点。中心节点可以向计费系统发送计费请求，计费系统向中心节点返回计费响应。
811，中心节点向边缘节点发送流量上报响应。
812，边缘节点根据计费处理结果，进行控制处理。
具体地，边缘节点进行控制处理的过程可以包括：
若计费处理成功，则继续下发数据给终端；计费处理失败，则停止下发数据给UE。
另外，本发明实施例还可以对第三方服务器进行计费。中心节点可以掌握边缘节点的回源流量，针对这部分流量对第三方服务器进行后向收费；中心节点还可以掌握边缘节点对UE下发的流量，针对这部分流量对第三方服务器进行后向收费。
图9是本发明一个实施例的网络通信的方法的示意性流程图。该方法可以由网络系统执行。该方法应用的网络系统包括位于无线接入网或无线接入网与无线核心网之间的网络协议IP传输网的第三方服务器和边缘节点，图9所示的方法可以包括：
910，边缘节点将用户设备针对中心服务器的传输控制协议TCP连接对应的 TCP报文引导到第三方服务器；
920，第三方服务器存储中心服务器的分发数据并根据分发数据对TCP报文进行响应，第三方服务器包括应用服务器或缓存服务器。
本发明实施例中将缓存服务器或应用服务器从位于城域网的IDC机房下沉到本地的无线接入网或无线接入网与无线核心网之间的IP传输网，并部署边缘节点将针对中心服务器的TCP报文引导到缓存服务器或应用服务器，实现流量调度。这样，减少了无线接入网到分组核心网的传输时延，从而提高了用户体验。
可选地，作为另一实施例，网络系统还包括位于无线核心网的中心节点，方法还包括：
930，边缘节点向中心节点注册TCP连接，以便于中心节点获知第三方服务器已经在边缘节点处为用户设备提供服务。
可选地，作为另一实施例，在步骤910中，边缘节点可以确定需要引导的IP地址并进行存储；根据需要引导的IP地址，将TCP报文进行目的地址替换DNAT，以便于将TCP报文引导到第三方服务器。
可选地，作为另一实施例，在边缘节点确定需要引导的IP地址，包括：边缘节点可以解析用户设备发送的域名系统DNS请求消息对应的DNS响应消息，得到需要引导的IP地址。
可选地，作为另一实施例，在边缘节点确定需要引导的IP地址，包括：边缘节点可以从网管系统获取需要引导的IP地址。
可选地，作为另一实施例，在边缘节点确定需要引导的IP地址，包括：边缘节点从中心节点获取需要引导的IP地址。
可选地，作为另一实施例，在步骤910中，若通过NDS劫持的方法将流量引入本地部署的第三方服务器时，边缘节点可以接收用户设备发送的DNS请求消息；向用户设备发送DNS响应消息，DNS响应消息携带第三方服务器的IP地址。
可选地，作为另一实施例，当边缘节点是通过解析DNS响应消息将流量引 入本地部署的第三方服务器这一实施例时，图9所示的方法还包括：中心节点，还用于将用户设备发送的上行TCP报文进行复制、封装并转发到边缘节点，以便于边缘节点获知用户设备已经从第一基站小区切换到第二基站小区；边缘节点，还用于将复制、封装后的上行TCP报文解封后，根据需要引导的IP地址将上行TCP报文进行DNAT并转发给第三方服务器；将从第三方服务器接收的下行TCP报文进行源地址替换后，复制、封装并转发到中心节点；中心节点，还用于将复制、封装后的下行TCP报文解封后，转发到用户设备。
可选地，作为另一实施例，当边缘节点是通过劫持DNS请求消息将流量引入本地部署的第三方服务器这一实施例时，图9所示的方法还包括：中心节点，还用于将用户设备发送的上行TCP报文进行复制、封装并转发到边缘节点，以便于边缘节点获知用户设备已经从第一基站小区切换到第二基站小区；边缘节点，还用于将复制、封装后的上行TCP报文解封后，将上行TCP报文转发给第三方服务器；将从第三方服务器接收的下行TCP报文进行复制、封装并转发到中心节点；中心节点，还用于将复制、封装后的下行TCP报文解封后，转发到用户设备。
可选地，作为另一实施例，图9所示的方法还包括：当第二基站小区部署第一边缘节点时，第一边缘节点根据上行TCP报文是否为新建的TCP连接判断上行TCP报文是否引导到第二基站小区对应的第三方服务器。
可选地，作为另一实施例，图9所示的方法还包括：中心节点可以根据边缘节点的位置信息，对第三方服务器进行数据分发。
可选地，作为另一实施例，图9所示的方法还包括：边缘节点可以将第三方服务器与用户设备交互的流量使用量向中心节点上报；中心节点可以根据上报的流量使用量，进行计费处理，以便于计费系统进行计费。
可选地，作为另一实施例，图9所示的方法还包括：第三方服务器可以从中心服务器获取需要引导的IP地址对应的数据。
本发明实施例中将缓存服务器或应用服务器从位于城域网的IDC机房下沉到本地的无线接入网或无线接入网与无线核心网之间的IP传输网，并部署边缘 节点将针对中心服务器的TCP报文引导到缓存服务器或应用服务器，实现流量调度。这样，减少了无线接入网到分组核心网的传输时延，从而提高了用户体验。
另外，在无线核心网部署中心节点，边缘节点和中心节点能够配合完成用户设备发生基站切换导致的移动性问题，保证用户业务的连续性和完整性。同时能够完成数据回源、数据分发和计费功能。这样，第三方服务器不需要修改并实现下沉，减少了用户业务访问的整体传输时延，提高了用户体验。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本发明的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本发明实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范 围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本发明实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。此外。任何连接可以适当的成为计算机可读介质。
总之，以上所述仅为本发明技术方案的较佳实施例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (26)

  1. 一种网络系统，用于进行内容分发，其特征在于，包括：
    位于无线接入网或所述无线接入网与无线核心网之间的网络协议IP传输网的第三方服务器和边缘节点，其中，所述边缘节点用于将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到所述第三方服务器，所述第三方服务器包括应用服务器或缓存服务器，用于存储所述中心服务器的分发数据并根据所述分发数据对所述TCP报文进行响应。
  2. 根据权利要求1所述的网络系统，其特征在于，还包括：
    位于所述无线核心网的中心节点，其中，所述边缘节点，还用于向所述中心节点注册所述TCP连接，以便于所述中心节点获知所述第三方服务器已经在所述边缘节点处为所述用户设备提供服务。
  3. 根据权利要求2所述的网络系统，其特征在于，所述边缘节点，具体用于
    确定需要引导的IP地址并进行存储；
    根据所述需要引导的IP地址，将所述TCP报文进行目的地址替换DNAT，以便于将所述TCP报文引导到所述第三方服务器。
  4. 根据权利要求3所述的网络系统，其特征在于，所述边缘节点，具体用于解析所述用户设备发送的域名系统DNS请求消息对应的DNS响应消息，得到所述需要引导的IP地址。
  5. 根据权利要求3所述的网络系统，其特征在于，所述边缘节点，具体用于从网管系统获取所述需要引导的IP地址。
  6. 根据权利要求3所述的网络系统，其特征在于，所述边缘节点，具体用于从所述中心节点获取所述需要引导的IP地址。
  7. 根据权利要求2所述的网络系统，其特征在于，所述边缘节点，具体用于
    接收所述用户设备发送的DNS请求消息；
    向所述用户设备发送DNS响应消息，所述DNS响应消息携带所述第三方服务器的IP地址。
  8. 根据权利要求3-6中任一项所述的网络系统，其特征在于，当所述用户设备从包括所述边缘节点的第一基站小区切换到第二基站小区时，
    所述中心节点，还用于将所述用户设备发送的上行TCP报文进行复制、封装并转发到所述边缘节点，以便于所述边缘节点获知所述用户设备已经从所述第一基站小区切换到所述第二基站小区；
    所述边缘节点，还用于将所述复制、封装后的上行TCP报文解封后，根据所述需要引导的IP地址将所述上行TCP报文进行DNAT并转发给所述第三方服务器；将从所述第三方服务器接收的下行TCP报文进行源地址替换SNAT后，复制、封装并转发到所述中心节点；
    所述中心节点，还用于将所述复制、封装后的下行TCP报文解封后，转发到所述用户设备。
  9. 根据权利要求7所述的网络系统，其特征在于，当所述用户设备从包括所述边缘节点的第一基站小区切换到第二基站小区时，
    所述中心节点，还用于将所述用户设备发送的上行TCP报文进行复制、封装并转发到所述边缘节点，以便于所述边缘节点获知所述用户设备已经从所述第一基站小区切换到所述第二基站小区；
    所述边缘节点，还用于将所述复制、封装后的上行TCP报文解封后，将所述上行TCP报文转发给所述第三方服务器；将从所述第三方服务器接收的下行TCP报文进行复制、封装并转发到所述中心节点；
    所述中心节点，还用于将所述复制、封装后的下行TCP报文解封后，转发到所述用户设备。
  10. 根据权利要求8或9所述的网络系统，其特征在于，
    当所述第二基站小区部署第一边缘节点时，所述第一边缘节点根据所述上行TCP报文是否为新建的TCP连接判断所述上行TCP报文是否引导到所述第二基站小区对应的第三方服务器。
  11. 根据权利要求2-10中任一项所述的网络系统，其特征在于，所述中心节点，还用于根据所述边缘节点的位置信息，对所述第三方服务器进行数据分发。
  12. 根据权利要求2-11中任一项所述的网络系统，其特征在于，所述边缘节点，还用于将所述第三方服务器与所述用户设备交互的流量使用量向所述中心节点上报；
    所述中心节点，还用于根据所述上报的流量使用量，进行计费处理，以便于计费系统进行计费。
  13. 根据权利要求1-12中任一项所述的网络系统，其特征在于，所述第三方服务器，还用于从所述中心服务器获取所述需要引导的IP地址对应的数据。
  14. 一种网络通信的方法，其特征在于，所述方法应用的网络系统包括位于无线接入网或所述无线接入网与无线核心网之间的网络协议IP传输网的第三方服务器和边缘节点，所述方法包括：
    所述边缘节点将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到所述第三方服务器；
    所述第三方服务器存储所述中心服务器的分发数据并根据所述分发数据对所述TCP报文进行响应，所述第三方服务器包括应用服务器或缓存服务器。
  15. 根据权利要求14所述的方法，其特征在于，所述网络系统还包括位于所述无线核心网的中心节点，所述方法还包括：
    所述边缘节点向所述中心节点注册所述TCP连接，以便于所述中心节点获知所述第三方服务器已经在所述边缘节点处为所述用户设备提供服务。
  16. 根据权利要求15所述的方法，其特征在于，所述边缘节点将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到所述第三方服务器，包括：
    所述边缘节点确定需要引导的IP地址并进行存储；
    根据所述需要引导的IP地址，将所述TCP报文进行目的地址替换DNAT，以便于将所述TCP报文引导到所述第三方服务器。
  17. 根据权利要求16所述的方法，其特征在于，所述边缘节点确定需要引导的IP地址，包括：
    所述边缘节点解析所述用户设备发送的域名系统DNS请求消息对应的DNS响应消息，得到所述需要引导的IP地址。
  18. 根据权利要求16所述的方法，其特征在于，所述边缘节点确定需要引导的IP地址，包括：
    所述边缘节点从网管系统获取所述需要引导的IP地址。
  19. 根据权利要求16所述的方法，其特征在于，所述边缘节点确定需要引导的IP地址，包括：
    所述边缘节点从所述中心节点获取所述需要引导的IP地址。
  20. 根据权利要求15所述的方法，其特征在于，在所述边缘节点将用户设备针对中心服务器的传输控制协议TCP连接对应的TCP报文引导到所述第三方服务器之前，还包括：
    所述边缘节点接收所述用户设备发送的DNS请求消息；
    向所述用户设备发送DNS响应消息，所述DNS响应消息携带所述第三方服务器的IP地址。
  21. 根据权利要求16-19中任一项所述的方法，其特征在于，当所述用户设备从包括所述边缘节点的第一基站小区切换到第二基站小区时，所述方法还包括：
    所述中心节点，还用于将所述用户设备发送的上行TCP报文进行复制、封装并转发到所述边缘节点，以便于所述边缘节点获知所述用户设备已经从所述第一基站小区切换到所述第二基站小区；
    所述边缘节点，还用于将所述复制、封装后的上行TCP报文解封后，根据所述需要引导的IP地址将所述上行TCP报文进行DNAT并转发给所述第三方服务器；将从所述第三方服务器接收的下行TCP报文进行复制、封装并转发到所述中心节点；
    所述中心节点，还用于将所述复制、封装后的下行TCP报文解封后，转发 到所述用户设备。
  22. 根据权利要求20所述的方法，其特征在于，当所述用户设备从包括所述边缘节点的第一基站小区切换到第二基站小区时，所述方法还包括：
    所述中心节点，还用于将所述用户设备发送的上行TCP报文进行复制、封装并转发到所述边缘节点，以便于所述边缘节点获知所述用户设备已经从所述第一基站小区切换到所述第二基站小区；
    所述边缘节点，还用于将所述复制、封装后的上行TCP报文解封后，将所述上行TCP报文转发给所述第三方服务器；将从所述第三方服务器接收的下行TCP报文进行源地址替换SNAT后，复制、封装并转发到所述中心节点；
    所述中心节点，还用于将所述复制、封装后的下行TCP报文解封后，转发到所述用户设备。
  23. 根据权利要求21或22所述的方法，其特征在于，当所述第二基站小区部署第一边缘节点时，所述方法还包括：
    所述第一边缘节点根据所述上行TCP报文是否为新建的TCP连接判断所述上行TCP报文是否引导到所述第二基站小区对应的第三方服务器。
  24. 根据权利要求15-23中任一项所述的方法，其特征在于，所述方法还包括：
    所述中心节点根据所述边缘节点的位置信息，对所述第三方服务器进行数据分发。
  25. 根据权利要求15-24中任一项所述的方法，其特征在于，所述方法还包括：
    所述边缘节点将所述第三方服务器与所述用户设备交互的流量使用量向所述中心节点上报；
    所述中心节点根据所述上报的流量使用量，进行计费处理，以便于计费系统进行计费。
  26. 根据权利要求14-25中任一项所述的方法，其特征在于，所述方法还包括：
    所述第三方服务器从所述中心服务器获取所述需要引导的IP地址对应的数据。
PCT/CN2016/088655 2015-08-28 2016-07-05 网络系统和网络通信的方法 Ceased WO2017036247A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16840676.7A EP3337134B1 (en) 2015-08-28 2016-07-05 Network system and network communication method
US15/907,162 US10785780B2 (en) 2015-08-28 2018-02-27 Network system and network communication method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510543193.X 2015-08-28
CN201510543193.XA CN106488504B (zh) 2015-08-28 2015-08-28 网络系统和网络通信的方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/907,162 Continuation US10785780B2 (en) 2015-08-28 2018-02-27 Network system and network communication method

Publications (1)

Publication Number Publication Date
WO2017036247A1 true WO2017036247A1 (zh) 2017-03-09

Family

ID=58186633

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088655 Ceased WO2017036247A1 (zh) 2015-08-28 2016-07-05 网络系统和网络通信的方法

Country Status (4)

Country Link
US (1) US10785780B2 (zh)
EP (1) EP3337134B1 (zh)
CN (2) CN111163133B (zh)
WO (1) WO2017036247A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107222499A (zh) * 2017-07-04 2017-09-29 四川云物益邦科技有限公司 基于离线存储技术的文件管理方法
WO2019174208A1 (zh) * 2018-03-15 2019-09-19 北京大米科技有限公司 基于tcp的通信方法、客户端、中心节点和通信系统

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10826820B2 (en) 2017-05-09 2020-11-03 Cisco Technology, Inc. Routing network traffic based on DNS
KR102364802B1 (ko) 2017-06-23 2022-02-17 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 연속성 구현 방법, 장치 및 서비스 연속성 구현 시스템
CN110896410B (zh) * 2018-11-15 2022-03-18 腾讯科技（深圳）有限公司 视频数据的上传方法、装置、计算机可读介质及电子设备
US11128545B2 (en) 2018-12-13 2021-09-21 Verizon Patent And Licensing Inc. Intelligent prioritized mobility of low-latency applications
WO2021031127A1 (zh) 2019-08-20 2021-02-25 华为技术有限公司 一种获取信息的方法及装置
CN113132437B (zh) * 2019-12-31 2024-01-23 中兴通讯股份有限公司 Cdn调度方法、系统、设备和存储介质
CN114124817B (zh) * 2020-03-15 2023-03-14 腾讯科技（深圳）有限公司 基于边缘计算的通信方法、装置、介质及电子设备
CN113301103B (zh) * 2021-02-05 2024-03-12 阿里巴巴集团控股有限公司 数据处理系统、方法及装置
CN114205417B (zh) * 2021-11-16 2024-05-31 上海翀远智能科技有限公司 一种信息处理方法、装置、电子设备及存储介质
CN114466008B (zh) * 2021-12-22 2023-10-13 天翼云科技有限公司 一种云边通信系统、方法、装置、电子设备及存储介质
CN118802755A (zh) * 2024-03-01 2024-10-18 中国移动通信集团浙江有限公司 流量调度方法、装置、电子设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103095597A (zh) * 2011-10-28 2013-05-08 华为技术有限公司 一种用于负载均衡的方法和装置
CN103457993A (zh) * 2012-06-01 2013-12-18 Sk电信有限公司 本地缓存装置和提供内容缓存服务的方法
CN103455439A (zh) * 2012-06-01 2013-12-18 Sk电信有限公司 本地缓存装置以及用于提供内容缓存服务的系统和方法
KR20140144321A (ko) * 2013-06-10 2014-12-18 에스케이텔레콤 주식회사 통신 네트워크에서 컨텐츠 전달 방법 및 이를 위한 장치

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8204082B2 (en) * 2000-06-23 2012-06-19 Cloudshield Technologies, Inc. Transparent provisioning of services over a network
US7356015B2 (en) * 2003-05-02 2008-04-08 Steven Blumenthal Data handoff method between wireless local area network and wireless wide area network
CN1665238B (zh) * 2004-03-04 2010-04-21 华为技术有限公司 下一代网络的组网系统
CN101039315B (zh) * 2006-03-16 2012-01-25 华为技术有限公司 与业务无关的接入网会话控制系统及方法
JP5092374B2 (ja) * 2006-12-01 2012-12-05 富士通株式会社 データセンタ及びデータ転送方法
CN101001197A (zh) * 2006-12-31 2007-07-18 华为技术有限公司 媒体流传输方法、系统及相关设备
US9167478B2 (en) * 2009-06-26 2015-10-20 Telefonaktiebolaget Lm Ericsson (Publ) Method for efficient utilisation of the throughput capacity of an eNB by using a cache
US8856281B2 (en) * 2010-03-22 2014-10-07 At&T Intellectual Property I, L.P. Internet protocol version 6 content routing
US20110320592A1 (en) * 2010-06-24 2011-12-29 Kemmerer Jr Frederick Charles Methods, systems, and computer readable media for content delivery using deep packet inspection
CN101938483A (zh) * 2010-09-03 2011-01-05 中兴通讯股份有限公司 一种直播内容分发方法和系统
CN102143204A (zh) * 2010-11-26 2011-08-03 华为技术有限公司 一种内容分发网络中实现超文本传输协议重定向的方法、装置及系统
KR101662018B1 (ko) * 2012-04-30 2016-10-04 에스케이텔레콤 주식회사 핸드오버를 고려한 모바일 컨텐츠 제공 방법 및 이를 위한 장치
CN103581248A (zh) * 2012-07-31 2014-02-12 中兴通讯股份有限公司 内容分发网络cdn服务的提供方法及装置
CN103581258B (zh) * 2012-08-03 2017-11-03 中国移动通信集团公司 网络数据缓存的方法和系统
CN103875227B (zh) * 2012-09-12 2017-11-24 华为技术有限公司 业务数据缓存处理方法、设备和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103095597A (zh) * 2011-10-28 2013-05-08 华为技术有限公司 一种用于负载均衡的方法和装置
CN103457993A (zh) * 2012-06-01 2013-12-18 Sk电信有限公司 本地缓存装置和提供内容缓存服务的方法
CN103455439A (zh) * 2012-06-01 2013-12-18 Sk电信有限公司 本地缓存装置以及用于提供内容缓存服务的系统和方法
KR20140144321A (ko) * 2013-06-10 2014-12-18 에스케이텔레콤 주식회사 통신 네트워크에서 컨텐츠 전달 방법 및 이를 위한 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3337134A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107222499A (zh) * 2017-07-04 2017-09-29 四川云物益邦科技有限公司 基于离线存储技术的文件管理方法
WO2019174208A1 (zh) * 2018-03-15 2019-09-19 北京大米科技有限公司 基于tcp的通信方法、客户端、中心节点和通信系统

Also Published As

Publication number Publication date
CN111163133A (zh) 2020-05-15
CN106488504B (zh) 2019-12-24
EP3337134A1 (en) 2018-06-20
US10785780B2 (en) 2020-09-22
EP3337134B1 (en) 2021-09-15
CN111163133B (zh) 2022-03-11
US20180192429A1 (en) 2018-07-05
CN106488504A (zh) 2017-03-08
EP3337134A4 (en) 2018-06-20

Similar Documents

Publication Publication Date Title
WO2017036247A1 (zh) 网络系统和网络通信的方法
CN103430516B (zh) 业务提供系统、方法、移动边缘应用服务器及支持节点
US10608842B2 (en) GTP-U downlink packet sending method and apparatus
CN103477665B (zh) 在移动通信网络中发送用户面业务的方法和装置
US9078173B2 (en) Method for handover from circuit switched domain to packet switched domain, device, and communications system
US9693263B2 (en) Method and system for data flow management of user equipment in a tunneling packet data network
WO2019185062A1 (zh) 一种通信方法及装置
WO2017201722A1 (zh) 一种通信控制的方法及相关网元
US20160212778A1 (en) Method and System for Data Flow Management of User Equipment in a Tunneling Packet Data Network
US10447503B2 (en) Method and system for data flow management of user equipment in a tunneling packet data network
CN107925611A (zh) 用于移动cdn的深度分组检视指示
CN106470465B (zh) Wifi语音业务发起方法、lte通信设备、终端及通信系统
WO2015188357A1 (zh) 一种控制承载切换的设备和控制方法
KR20190140045A (ko) 사용자 평면 링크 설립 방법, 기지국 및 이동성 관리 장치
JP6722305B2 (ja) Ｓ８ｈｒにおけるモビリティについての合法的傍受のためのｉｍｓ関連情報の転送
US9167498B2 (en) Caching over an interface between a radio access network and a core network
CN107926066A (zh) 一种业务流的传输方法及装置
WO2009127120A1 (zh) 切换过程中跟踪用户的方法、装置及系统
EP3454588B1 (en) Method and device for transmitting messages
JP2025510617A (ja) 情報を設定する方法と装置及び通信システム

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: 16840676

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016840676

Country of ref document: EP