WO2018223645A1 - 一种数据分流方法和网关 - Google Patents

一种数据分流方法和网关 Download PDF

Info

Publication number
WO2018223645A1
WO2018223645A1 PCT/CN2017/115714 CN2017115714W WO2018223645A1 WO 2018223645 A1 WO2018223645 A1 WO 2018223645A1 CN 2017115714 W CN2017115714 W CN 2017115714W WO 2018223645 A1 WO2018223645 A1 WO 2018223645A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
data
gateway
header
local server
Prior art date
Application number
PCT/CN2017/115714
Other languages
English (en)
French (fr)
Inventor
郑自永
胡呈欣
衷柳生
关文祥
Original Assignee
京信通信系统（中国）有限公司
京信通信系统（广州）有限公司
京信通信技术(广州)有限公司
天津京信通信系统有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京信通信系统（中国）有限公司, 京信通信系统（广州）有限公司, 京信通信技术(广州)有限公司, 天津京信通信系统有限公司 filed Critical 京信通信系统（中国）有限公司
Priority to US16/620,679 priority Critical patent/US11317322B2/en
Publication of WO2018223645A1 publication Critical patent/WO2018223645A1/zh

Links

Images

Classifications

    • 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/08—Load balancing or load distribution
    • H04W28/0827—Triggering entity
    • H04W28/0835—Access entity, e.g. eNB
    • 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/08—Load balancing or load distribution
    • 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/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • 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/10—Flow control between communication endpoints

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a data offloading method and a gateway.
  • LTE Long Term Evolution
  • IP Internet access
  • IPPA Local IP Access
  • SIPTO IP traffic offload
  • the embodiment of the present application provides a data offloading method and a gateway, which implement data shunting and alleviate the pressure of the core network.
  • the embodiment of the present application provides a data offloading method, which is applicable to a long-term evolution LTE system including a base station, a gateway, a core network, and a local server.
  • the base station and the core network establish a link through a gateway, and the base station and the local server establish a link through the gateway.
  • the method includes: the gateway receives the first data packet sent by the base station; wherein the first data packet includes the first data; and the gateway determines that the first data packet is a non-long-term evolution voice VoLTE data packet: The data is sent to the local server.
  • the embodiment of the present application provides a gateway for data offloading, which is applicable to a long-term evolution LTE system including a base station, a gateway, a core network, and a local server.
  • the base station and the core network establish a link through the gateway, and the base station and the local server pass the The gateway establishes a link, the gateway includes: a receiving unit, configured to receive a first data packet sent by the base station, where the first data packet includes a first terminal identifier, first data, and a processing unit, configured to determine whether the first data packet is a non-long-term evolution voice VoLTE data packet; a sending unit, configured to: when determining that the first data packet is a non-long-term evolution voice VoLTE data packet: send the first data to a local server.
  • an embodiment of the present application provides a gateway, including: a transceiver, a processor, a memory, and a communication interface, wherein the transceiver, the processor, the memory, and the communication interface pass through a bus a transceiver, configured to receive a first data packet sent by a base station; and in a case where the first data packet is determined to be a non-long-term evolution voice VoLTE data packet: sending the first data to the a local server; wherein the first data packet includes first data; the processor is configured to read a program in the memory, and perform the following method: determining whether the first data packet is non-long-term evolution A voice VoLTE data packet; the memory for storing one or more executable programs, and storing data used by the processor when performing an operation.
  • an embodiment of the present application provides a non-transitory computer readable storage medium, where the non-transitory computer readable storage medium stores computer instructions, where the computer instructions are used to cause the computer to perform the first aspect or the A method in any of the possible embodiments on the one hand.
  • an embodiment of the present application provides a computer program product, where the computer program product includes a calculation program stored on a non-transitory computer readable storage medium, the computer program includes program instructions, when the program instruction is When executed by a computer, the computer is caused to perform the method of any of the first aspect or the first aspect of the first aspect.
  • the LTE system includes a base station, a gateway, a core network, and a local server, and the base station and the core network establish a link through the gateway, and the base station and the local server establish a link through the gateway; the gateway receives the first data packet sent by the base station;
  • the first data packet includes the first data;
  • the gateway determines that the first data packet is a Voice over Long Term Evolution (VoLTE) data packet: the first data is sent to the local server.
  • VoIP Voice over Long Term Evolution
  • FIG. 1 is a schematic structural diagram of a data offloading system according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for data offloading according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of opening a full data local offload interaction between a terminal and a local server according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of closing a full data local offload interaction between a terminal and a local server according to an embodiment of the present disclosure
  • FIG. 5 is an example of an uplink and downlink data packet encapsulation format provided by an embodiment of the present application
  • FIG. 6 is a schematic flowchart of a method for uplink data offloading according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a method for downlink data offloading according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of a gateway for data offloading according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a gateway according to an embodiment of the present application.
  • FIG. 1 exemplarily shows a schematic diagram of a data offloading system architecture applicable to an embodiment of the present application.
  • the data offloading system includes a core network, a local server, a gateway, and a base station, and the base station and the core network establish a link through the gateway, and the base station and the local server pass the gateway.
  • the gateway manages a plurality of base stations, each of which manages a plurality of terminals; as shown in FIG. 1, the system architecture 100 includes an Internet 101, a core network 102, a local server 103, a gateway 104, a base station 105, a base station 106, and a base station 107.
  • the gateway 104 is connected to the base station 105, the base station 106, and the base station 107, respectively; on the other hand, the gateway 104 is connected to the core network 102 and the local server 103, respectively; the core network 102 and the local server 103 are connected to the Internet 101.
  • the gateway 104 receives the first data packet sent by the base station, and may send the first data packet to the core network 102 or the local server 103. If the first data packet is a VoLTE data packet, the gateway 104 uses the first data packet. The first data packet is sent to the core network 102. If the first data packet is a non-VoLTE data packet, the gateway 104 sends the first data packet to the local server 103.
  • the gateway 104 receives the second data packet sent by the local server 103, and then sends the second data packet to the base station, and sends the second data packet to the terminal corresponding to the terminal identifier included in the second data packet. .
  • the gateway 104 receives the data packet transmitted by the core network 102 and transmits the data packet to the base station.
  • the terminal controls the data offloading and link selection of the gateway by installing an application software matched with the HTTPS service in the local server;
  • the base station is responsible for providing coverage for the terminal and connecting the gateway with the local server;
  • the gateway is responsible for the specific operation of the data offloading
  • the local server provides HTTPS service for terminal application software, message interaction control, and the local server and the gateway jointly control the UE "whether or not the data is distributed", and the local server provides the NAT function in addition to the direct access interaction of the terminal.
  • FIG. 2 is a schematic flowchart diagram of a data offloading method provided by an embodiment of the present application.
  • a data offloading method provided by an embodiment of the present application is applicable to a long-term evolution LTE system including a base station, a gateway, a core network, and a local server, and the base station and the core network pass The gateway establishes a link, and the base station and the local server establish a link through the gateway.
  • the method includes the following steps:
  • Step S201 The gateway receives the first data packet sent by the base station, where the first data packet includes the first data.
  • Step S202 In the case that the gateway determines that the first data packet is a voice VoLTE data packet on a non-long term evolution: the first data is sent to the local server.
  • the first data packet is an uplink data packet sent by the terminal to the base station, where the first data included in the first data packet may be VoLTE data or non-VoLTE data.
  • step S202 there are multiple methods for determining whether the first data packet is a VoLTE data packet.
  • the embodiment of the present application provides an optional solution: if the first data packet is received, the scale of the bearer path is received. When the value (QoS Class Identifier, QCI for short) is any one of 1, 2, and 5, the first data packet is a VoLTE data packet; if the QCI is not any one of 1, 2, and 5, then One packet is a non-VoLTE packet.
  • the gateway receives the first data packet sent by the base station, where the first data packet includes the first terminal identifier and the first data, and the gateway determines that the first data packet is a non-VoLTE data packet:
  • the first data in the first data packet is sent to the local server; the method provided in this embodiment of the present application can implement the offloading of the non-VoLTE data, in the method of the first data packet sent to the core network in the prior art. , thereby alleviating the pressure on the core network.
  • the gateway sends the first data to the local server in two cases:
  • the gateway determines that the first data packet is a non-VoLTE data packet: sending the first data to the local server, including: the gateway determines that the first data packet is a non-VoLTE data packet, and the gateway is enabled.
  • the first data is sent to the local server.
  • the second case is: the first data packet further includes a destination IP address; and the gateway determines that the first data packet is a non-VoLTE data packet: sending the first data to the local server, including: the gateway determining the first data
  • the packet is a non-VoLTE packet, and the gateway sends the first data to the local server if it determines that the destination IP address matches the IP address of the local server.
  • the gateway offloads the non-VoLTE data to the local server.
  • the IP address of the local server is 192.168.26.100
  • the destination IP address in the first packet is 192.168.26.100
  • the gateway will be the first in the first data packet.
  • a data is forced to be offloaded to the local server. In this way, the data packets that need to be processed through the core network are reduced, and the pressure on the core network is reduced.
  • FIG. 3 exemplarily shows a schematic diagram of turning on full data local offload interaction between the terminal and the local server provided by the embodiment of the present application.
  • the steps to enable full data local offload are as follows:
  • Step S301 The terminal sends a full data offload message to the gateway.
  • Step S302 The gateway forwards the all-data offloading message (Ping) to the local server;
  • Step S303 The local server sends a first request message to the gateway.
  • the first request message may be a local server performing a ping operation on a terminal, and the packet size of the Ping operation is 72 bytes. ;
  • Step S304 If the gateway receives the first request message with a size of 72 bytes, then the full data local offload is enabled;
  • Step S305 After the gateway starts the full data local offloading, the first response message is sent to the local server.
  • the first response message is a response message of the Ping operation. If the gateway starts the full data local offload, the gateway sends the first message to the local server.
  • the response message is 72 bytes;
  • Step S306 After receiving the first response message, the local server sends a full data offloading start message (Https) to the gateway if the first response message is 72 bytes.
  • Https full data offloading start message
  • Step S307 The gateway sends a full data offloading start message to the terminal.
  • the all-data offloading message in the above steps S301 and S302 adopts a local area network communication manner, and the full data offloading start message in steps S306 and S307 adopts an HTTPS encryption mode.
  • FIG. 3 exemplarily shows a schematic diagram of closing the full data local offload interaction between the terminal and the local server provided by the embodiment of the present application.
  • the steps to turn off full data local offloading are as follows:
  • Step S401 The terminal sends a closed full data offload message to the gateway.
  • Step S402 The gateway forwards the closed full data offload message (Ping) to the local server;
  • Step S403 The local server sends a second request message to the gateway, where the second request message may be a local server performing a ping operation on a terminal, and the packet size of the ping operation is 2 bytes as a control protocol for turning off the full offloading;
  • Step S404 If the gateway receives the second request message as 2 bytes, the full data offload is closed.
  • Step S405 After the gateway closes the full data offloading, the second response message is sent to the local server.
  • the second response message is a response message of the Ping operation. If the gateway turns off the full data local offload, the second response sent by the gateway to the local server.
  • the message is 2 bytes;
  • Step S406 The local server receives the second response message, and if the second response message is 2 bytes, sends a full data offload close message (Https) to the gateway;
  • Step S407 The gateway sends a full data offload close message to the terminal.
  • the closed full data offload message in the above steps S401 and S402 adopts a local area network communication manner
  • the full data offload close message in steps S406 and S407 adopts an HTTPS encryption manner.
  • the gateway and the local server use a partial direct communication security mode for the traffic distribution control. If the gateway finds that the local server performs a Ping operation on the terminal, the gateway responds instead of the terminal and performs corresponding Shunt control, in which 72 bytes is used to turn on full data off, and 2 bytes is to close the control of full data offload; and the size of the Ping operation is not limited to 72 bytes, and 2 bytes are closed.
  • the control convention of full data offloading for example, can also be 120 bytes for opening and 36 bytes for closing the full data offload control convention.
  • one of the modes is: installing application software on the terminal, and implementing whether to enable full data offloading with the local server;
  • the terminal terminal can independently select the traditional LTE networking mode or the gateway localized networking mode, and simultaneously the gateway and the local server.
  • the internal control of “whether or not full data offloading” is internalized, alleviating the pressure on the core network, and diversifying the way operators open their own capability platforms, providing operators with a new network transmission support for broadening the market.
  • the method further includes: the gateway sending the first data to the core network by determining that the first data packet meets any one of the preset conditions, where the preset condition includes :
  • the first data packet is a non-VoLTE data packet
  • the destination IP address does not match the IP address of the local server
  • the gateway is in the closed state of the full data local offloading state
  • the first data packet is a VoLTE data packet.
  • the first data packet is a VoLTE data packet, that is, when the QCI is any one of 1, 2, and 5, that is, the first data is voice data, regardless of whether the gateway is in the local data sharing manner.
  • the state sends the first data to the core network for processing; if the first data packet is a non-VoLTE data packet, and the destination IP address does not match the IP address of the local server, and the gateway is in the closed state of full data localization,
  • the first data is sent to the core network.
  • sending the first data to the core network includes: the gateway updates the Ethernet Ethernet header and the tunnel IP header in the first data packet, and obtains a data packet to be sent, and the Send the packet to the core network.
  • the first data packet further includes an IP header, a UDP header, a GTP-U header, and a first terminal identifier.
  • the method further includes: the gateway recording the tunnel IP included in the first data packet. Corresponding relationship between the header and the tunnel UDP header and the GTP-U header and the first terminal identifier, and adding the corresponding relationship to the first set; the gateway encapsulating the first data and the first terminal identifier to obtain the first to-be-sent data packet; the gateway A pending packet is sent to the local server.
  • the first data packet includes an Ethernet header, an IP header, a UDP header, a GTP-U header, a first terminal identifier, and first data, where the IP header, the UDP header, the GTP-U header, and the first terminal
  • the identifiers are one-to-one correspondence; after the gateway receives the first data packet, there are two cases:
  • the gateway determines that the first data packet is a VoLTE data packet, and after the VoLTE data packet is encapsulated, obtains the first data and the first terminal identifier; and then encapsulates the first data and the first terminal identifier into a new Ethernet header,
  • the IP header, UDP header, and GTP-U header are sent to the core network.
  • the gateway determines that the first data packet is a non-VoLTE data packet, and after the non-VoLTE data packet is encapsulated, the first terminal identifier and the first data are obtained, and the IP header, the UDP header, and the GTP in the first data packet are recorded. a correspondence between the U header and the first terminal identifier; and transmitting the first terminal identifier and the first Ethernet header to the first data, and sending the new Ethernet header to the local server.
  • the gateway receives the first data packet sent by the base station, and records the correspondence between the IP header, the UDP header, the GTP-U header, and the first terminal identifier in the first data packet, so that the gateway receives the local server to send.
  • the IP header, the UDP header, and the GTP-U header corresponding to the terminal identifier in the second data packet are determined, and then sent to the terminal that performs data interaction with the local server, and thus, the downlink data obtained from the Internet is obtained.
  • the pressure on the core network is reduced by sending it to the gateway through the local server.
  • the method for data offloading further includes: the gateway receiving the second data packet sent by the local server; wherein the second data packet includes the terminal identifier to be queried and the second data; the gateway determines the A tunnel IP header, a tunnel UDP header, and a GTP-U header corresponding to the terminal identifier that matches the to-be-queried terminal identifier are determined in the same manner as the terminal identifier that matches the to-be-queried terminal identifier; the gateway matches the to-be-queried terminal identifier.
  • the tunnel ID corresponding to the tunnel IP header, the tunnel UDP header, and the GTP-U header encapsulates the second data to obtain a second to-be-sent data packet; the gateway sends the second to-be-sent data packet to the base station.
  • the data included in the second data packet is downlink data
  • the to-be-queried terminal identifier is an identifier corresponding to the terminal that the second data needs to reach; the gateway receives multiple first data packets sent by multiple terminals. Therefore, after the gateway receives the second data packet, it is required to determine to send the second data to the corresponding terminal according to the to-be-queried terminal identifier included in the second data packet.
  • the gateway receives two first data packets sent by the base station, namely: data packet 1, terminal identifier is UE 1 ; data packet 2, terminal identifier is UE 2 ; wherein, the tunnel IP header corresponding to UE 1
  • the tunnel UDP header and GTPU header are IP 1 , UDP 1 and GTPU 1 respectively
  • the tunnel IP header, tunnel UDP header and GTPU header corresponding to UE 2 are IP 2 , UDP 2 and GTPU 2 respectively
  • the gateway receives the second data packet
  • the terminal identifier to be queried includes the UE 2
  • the gateway encapsulates the second data in the second data packet with the tunnel IP header, the tunnel UDP header, and the GTPU header corresponding to the UE 2 as IP 2 , UDP 2, and GTPU 2, respectively.
  • the terminal transmits to the UE 2 via a base station.
  • the embodiment of the present application sends part of the downlink data to the gateway through the local server, thereby reducing data traffic through the core network and reducing the pressure on the core network.
  • FIG. 5 exemplarily shows an example of the uplink and downlink data packet encapsulation format provided by the embodiment of the present application.
  • the data transmission link in the LTE system includes two links: a link composed of a base station, a gateway, a core network, and an Internet, and a link 2 is a chain composed of a base station, a gateway, a local server, and the Internet. road.
  • the uplink data transmission is performed by the base station to the Internet, and specifically includes:
  • the base station sends an uplink data packet 501 to the gateway, and the encapsulation format is: an Ethernet header, an S1 tunnel IP header, an S1 tunnel UDP header, a GTP-U header, and a terminal IP packet, wherein the uplink data packet 501 is the foregoing implementation.
  • the terminal IP packet includes the first data and the first terminal identifier;
  • the gateway After receiving the uplink data packet 501, the gateway determines to send data to the core network or the local server;
  • the Ethernet header and the S1 tunnel IP header in the uplink data packet 501 are updated to obtain an uplink data packet 502.
  • the encapsulation format is: an Ethernet header, an S1 tunnel IP header, an S1 tunnel UDP header, and a GTP- U header, terminal IP packet; and sending the uplink data packet 502 to the core network;
  • the gateway sends data to the local server, record the correspondence between the S1 tunnel IP header, the S1 tunnel UDP header, the GTP-U header, and the first terminal identifier in the uplink data packet 501, and join the first set;
  • the S1 tunnel IP header, the S1 tunnel UDP header, and the GTP-U header in the 501 are removed, and the Ethernet header is updated, and the uplink data packet 504 is obtained.
  • the encapsulation format is: an Ethernet header, a terminal IP packet, and an uplink packet 504. Send to the local server;
  • the core network After receiving the uplink data packet 502, the core network removes the S1 tunnel IP header, the S1 tunnel UDP header, and the GTP-U header, and updates the Ethernet header to obtain an uplink data packet 503.
  • the encapsulation format is: Ethernet. Head and terminal IP packets; sending uplink data packets 503 to the Internet;
  • the local server After receiving the uplink data packet 504, the local server updates the Ethernet header therein to obtain an uplink data packet 505, and the encapsulation format is: an Ethernet header and a terminal IP packet; and an uplink data packet 505 is sent to the Internet.
  • the downlink data transmission is directed by the Internet to the base station, and specifically includes:
  • the Internet sends a downlink data packet to the core network or the local server; if it is in the direction of the core network, the downlink data packet 506 is sent, and the encapsulation format is: an Ethernet header and a terminal IP packet; if it is in the direction of the core network, the downlink data packet is sent 508.
  • the encapsulation format is: Ethernet header, terminal IP packet;
  • the core network receives the downlink data packet 506, adds the S1 tunnel IP header, the S1 tunnel UDP header, and the GTP-U header, and updates the Ethernet header to obtain the downlink data packet 507.
  • the encapsulation format is: Ethernet header, S1 tunnel. IP header, S1 tunnel UDP header, GTP-U header, terminal IP packet; sending downlink data packet 507 to the gateway;
  • the local server receives the downlink data packet 508, updates the Ethernet header therein, and obtains the downlink data packet 509, and the encapsulation format is: an Ethernet header and a terminal IP packet; and a downlink data packet 509 is sent to the gateway;
  • the gateway When the gateway receives the downlink data packet 507 sent by the core network, after updating the Ethernet header and the S1 tunnel IP header, the gateway obtains the downlink data packet 510; when the gateway receives the downlink data packet 509 sent by the local server, according to the terminal IP
  • the S1 tunnel IP header, the S1 tunnel UDP header, and the GTP corresponding to the terminal identifier that matches the to-be-queried terminal identifier are found in the first set of the terminal identifier to be queried.
  • the encapsulated terminal IP packet obtains the downlink data packet 510, and the encapsulation format is: Ethernet header, S1 tunnel IP header, S1 tunnel UDP header, GTP-U header, terminal IP packet; the gateway sends the downlink data packet 510 to the base station. .
  • FIG. 6 is a schematic flowchart showing a method for performing uplink data offloading according to an embodiment of the present application. Based on the system architecture shown in FIG. 1 , as shown in FIG. 6 , another data splitting provided by the embodiment of the present application is provided.
  • the method is applicable to a Long Term Evolution (LTE) system including a base station, a gateway, a core network, and a local server.
  • LTE Long Term Evolution
  • the base station and the core network establish a link by using the gateway, and the base station and the local server establish a link by using the gateway.
  • the method includes the following steps:
  • Step S601 The gateway receives the first data packet sent by the base station, where the first data packet includes a first terminal identifier and first data.
  • Step S602 The gateway determines whether the first data packet is a VoLTE data packet; if yes, step S608 is performed; if not, step S603 is performed;
  • Step S603 The gateway determines whether the destination IP address in the first data packet matches the IP address of the local server; if yes, step S605 is performed; if not, step S604 is performed;
  • Step S604 Whether the gateway is in the full data local offload state; if yes, step S605 is performed; if not, step S608 is performed;
  • Step S605 The gateway records the correspondence between the tunnel IP header, the tunnel UDP header, and the GTP-U header and the first terminal identifier included in the first data packet, and adds the corresponding relationship to the first set.
  • Step S606 The gateway removes the tunnel IP header, the tunnel UDP header, and the GTP-U header in the first data packet, and encapsulates the first data and the first terminal identifier to obtain the first to-be-sent data packet.
  • Step S607 The gateway sends the first to-be-sent data packet to the local server.
  • Step S608 The gateway sends the first data to the core network.
  • FIG. 7 is a schematic flow chart of a method for downlink data offloading provided by an embodiment of the present application. Based on the system architecture shown in FIG. 1 , as shown in FIG. 7 , another data splitting provided by the embodiment of the present application is provided.
  • the method is applicable to a Long Term Evolution (LTE) system including a base station, a gateway, a core network, and a local server.
  • LTE Long Term Evolution
  • the base station and the core network establish a link by using the gateway, and the base station and the local server establish a link by using the gateway.
  • the method includes the following steps:
  • Step S701 The gateway receives the second data packet sent by the local server, where the second data packet includes the terminal identifier to be queried and the second data.
  • Step S702 The gateway queries the first set whether there is a terminal identifier that matches the to-be-queried terminal identifier; if yes, step S703 is performed; if not, step S706 is performed;
  • Step S703 Determine a tunnel IP header, a tunnel UDP header, and a GTP-U header corresponding to the terminal identifier that matches the to-be-queried terminal identifier.
  • Step S704 The gateway encapsulates the second data according to the tunnel IP header, the tunnel UDP header, and the GTP-U header corresponding to the terminal identifier that matches the to-be-queried terminal identifier, to obtain the second to-be-sent data packet.
  • Step S705 The gateway sends the second to-be-sent data packet to the base station.
  • Step S706 Discarding the second data packet.
  • the gateway determines that the first data packet is a non-VoLTE data packet: when the gateway is in the full data offload state, the first data is sent to the local server. In this way, the offloading of the non-VoLTE data in the uplink data is implemented, thereby alleviating the pressure of the core network; and the gateway receives the second data packet sent by the local server, so that the non-VoLTE data in the downlink data does not pass through the core network, through the local server. Sending to the gateway reduces the data traffic through the core network and alleviates the pressure on the core network.
  • the gateway gateway offloading technology and the local server data stream are supported and matched, and the gateway/local server/terminal is merged together to make the terminal
  • the link through the LTE system becomes terminal controllable, alleviates the pressure on the core network, opens the link selection capability on the core network side, and enriches the existing service mode.
  • the flexible and controllable traffic distribution system and gateway of this application are operators. Broadening the market offers a whole new approach.
  • FIG. 8 is a schematic structural diagram of a gateway for data offloading provided by an embodiment of the present application.
  • a gateway for data offloading provided by an embodiment of the present application is applicable to a long term evolution LTE system including a base station, a gateway, a core network, and a local server, where the base station and the core network are established by using the gateway. Linking, the base station and the local server establish a link through the gateway, and the gateway for data offloading is used to execute the foregoing method flow.
  • the gateway 800 for data offloading includes a receiving unit 801, and processing. Unit 802 and transmitting unit 803; wherein:
  • the receiving unit 801 is configured to receive a first data packet sent by the base station, where the first data packet includes first data;
  • the processing unit 802 is configured to determine whether the first data packet is a voice VoLTE data packet on a non-long term evolution
  • the sending unit 803 is configured to: when determining that the first data packet is a voice VoLTE data packet on a non-long term evolution: send the first data to the local server.
  • the sending unit 803 is configured to: when the processing unit 802 determines that the first data packet is a non-VoLTE data packet, and the gateway is in an all-data local off-state state, The first data is sent to the local server.
  • the first data packet further includes a destination IP address
  • the sending unit 803 is configured to: at the processing unit 802, determine that the first data packet is a non-VoLTE data packet, and the destination IP address The first data is sent to the local server if the address matches the IP address of the local server.
  • the processing unit 802 is further configured to: determine whether the first data packet meets any one of a preset condition, and the sending unit 803 is further configured to: determine that the first data packet meets a preset condition
  • the first data is sent to the core network, where the preset condition includes: the first data packet is a non-VoLTE data packet, and the destination IP address is related to the local server The IP address does not match, and the gateway is in a closed full data local offload state; the first data packet is a VoLTE data packet.
  • the first data packet further includes an IP header, a UDP header, a GTP-U header, and a first terminal identifier
  • the processing unit 802 is further configured to: record the foregoing included in the first data packet Corresponding relationship between the tunnel IP header, the tunnel UDP header, and the GTP-U header and the first terminal identifier, and adding the corresponding relationship to the first set; encapsulating the first data and the first terminal
  • the sending unit 803 is further configured to: send the first to-be-sent data packet to the local server.
  • the receiving unit 801 is further configured to: receive a second data packet sent by the local server, where the second data packet includes a terminal identifier to be queried and second data; and the processing unit 802, And in the case that the terminal identifier corresponding to the terminal identifier to be queried in the first set is determined, the tunnel IP header and the tunnel UDP header corresponding to the terminal identifier that matches the to-be-queried terminal identifier are determined.
  • the sending unit 803 is further configured to: send the second to-be-sent data packet to the base station.
  • the gateway receives the first data packet sent by the base station, where the first data packet includes the first data, and the gateway determines that the first data packet is a non-VoLTE data packet. : Send the first data to the local server. In this way, the offloading of non-VoLTE data can be achieved, thereby alleviating the pressure on the core network.
  • FIG. 9 is a schematic structural diagram of a gateway provided by the present application.
  • the gateway 900 includes a transceiver 901, a processor 902, a memory 903, and a communication interface 904; wherein the transceiver 901, the processor 902, the memory 903, and the communication interface 904 are connected to one another via a bus 905.
  • the memory 903 is used to store programs.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 903 may be a volatile memory, such as a random-access memory (RAM), or a non-volatile memory, such as a flash memory.
  • RAM random-access memory
  • non-volatile memory such as a flash memory.
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 903 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof:
  • Operation instructions include various operation instructions for implementing various operations.
  • Operating system Includes a variety of system programs for implementing various basic services and handling hardware-based tasks.
  • the bus 905 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the communication interface 904 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a WLAN interface.
  • the processor 902 can be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and an NP. It can also be a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL) or any combination.
  • the transceiver 901 is configured to receive a first data packet sent by the base station, where the first data packet is determined to be a non-long term evolution voice VoLTE data packet: sending the first data to the local a server; wherein the first data packet includes first data; the processor 902, configured to read a program in the memory 903, and perform the following method: determining whether the first data packet is non-long-term evolution The voice VoLTE data packet; the memory 903 is configured to store one or more executable programs, and may store data used by the processor 902 when performing an operation.
  • the gateway receives the first data packet sent by the base station, where the first data packet includes the first data, and in the case that the first data packet is determined to be a non-VoLTE data packet, the first data is sent to the local device. server. In this way, the offloading of non-VoLTE data can be achieved, thereby alleviating the pressure on the core network.
  • the transceiver 901 is specifically configured to send the first data to the first data packet when the first data packet is determined to be a non-VoLTE data packet, and the gateway is in a state where the full data local offload state is enabled.
  • the local server is specifically configured to send the first data to the first data packet when the first data packet is determined to be a non-VoLTE data packet, and the gateway is in a state where the full data local offload state is enabled.
  • the local server is specifically configured to send the first data to the first data packet when the first data packet is determined to be a non-VoLTE data packet, and the gateway is in a state where the full data local offload state is enabled.
  • the local server is specifically configured to send the first data to the first data packet when the first data packet is determined to be a non-VoLTE data packet, and the gateway is in a state where the full data local offload state is enabled.
  • the local server is specifically configured to send the first data to the first data packet when the first data packet is
  • the first data packet further includes a destination IP address
  • the transceiver 901 is configured to: determine that the first data packet is a non-VoLTE data packet, and determine the destination IP address and location In the case that the IP addresses of the local servers match, the first data is sent to the local server.
  • the processor 902 is further configured to determine whether the first data packet meets any one of a preset condition
  • the transceiver 901 is further configured to: when determining that the first data packet is satisfied And sending, by the any one of the preset conditions, the first data to the core network, where the preset condition includes: the first data packet is a non-VoLTE data packet, and the destination IP address is The IP address of the local server does not match, and the gateway is in a closed full data local offload state; the first data packet is a VoLTE data packet.
  • the first data packet further includes an IP header, a UDP header, a GTP-U header, and a first terminal identifier
  • the processor 902 is further configured to: record the foregoing included in the first data packet Corresponding relationship between the tunnel IP header, the tunnel UDP header, and the GTP-U header and the first terminal identifier, and adding the corresponding relationship to the first set; encapsulating the first data and the first terminal
  • the identifier is obtained by the first to be sent data packet, and the transceiver 901 is further configured to: send the first to-be-sent data packet to the local server.
  • the transceiver 901 is further configured to: receive a second data packet sent by the local server, and send a second to-be-sent data packet to the base station; where the second data packet includes a to-be-queried The terminal identifier and the second data; the processor 902 is further configured to: determine, when the terminal identifier in the first set that matches the to-be-queried terminal identifier, the identifier of the terminal to be queried a tunnel IP header, a tunnel UDP header, and a GTP-U header corresponding to the matching terminal identifier; a tunnel IP header, a tunnel UDP header, and a GTP-U header corresponding to the terminal identifier matching the to-be-queried terminal identifier, and a The second data is obtained, and the second to-be-sent data packet is obtained.
  • embodiments of the present application can be provided as a method, system, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例涉及通信技术领域，尤其涉及一种数据分流方法和网关，用于实现数据分流，缓解核心网压力。本申请实施例提供的一种数据分流方法，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，基站和核心网通过网关建立链接，基站和本地服务器通过网关建立链接，方法包括：网关接收基站发送的第一数据包；其中，第一数据包包括第一数据；网关在确定第一数据包为非长期演进上的语音VoLTE数据包的情况下：将第一数据发送至本地服务器；从而实现了非VoLTE数据的分流，进而缓解了核心网压力。

Description

一种数据分流方法和网关
本申请要求在2017年6月9日提交中华人民共和国知识产权局、申请号为201710432932.7，发明名称为“一种数据分流方法和网关”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种数据分流方法和网关。
背景技术
随着长期演进(Long Term Evolution，简称LTE)技术的发展，用户对于网络服务需求越来越多，用户数量的增加和用户数据传输速率的提高，对核心网络的网元提出了更高的需求。为了减少LTE系统中核心网的负载，提出了在数据传输过程中对数据业务进行分流的技术。
现有技术中，采用了本地互联网互联协议(Internet Protocol，简称IP)存取(Local IP Access，简称LIPA)与选择IP流量卸除(Selected IP Traffic Offload，简称SIPTO)方法，将部分数据业务的直接从基站分流出去，不经由核心网。这种方法需要增加一个本地网关，通过建立直接通道连接基站；该本地网关的作用是将访问本地服务器的数据，由基站直接分流到本地网关，而不经由核心网传递数据。但是，这种方式需要在现有的系统中增加新的网元，增加了成本，而且实现的难度大。
因此，亟需一种数据分流方法，实现数据分流，缓解核心网压力。
发明内容
本申请实施例提供一种数据分流方法和网关，实现数据分流，缓解核心网压力。
第一方面，本申请实施例提供一种数据分流方法，适用于包括基站、网 关、核心网、本地服务器的长期演进LTE系统，基站和核心网通过网关建立链接，基站和本地服务器通过网关建立链接，该方法包括：网关接收基站发送的第一数据包；其中，第一数据包包括第一数据；网关在确定第一数据包为非长期演进上的语音VoLTE数据包的情况下：将第一数据发送至本地服务器。
第二方面，本申请实施例提供一种用于数据分流的网关，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，基站和核心网通过网关建立链接，基站和本地服务器通过网关建立链接，该网关包括：接收单元，用于接收基站发送的第一数据包；其中，第一数据包包括第一终端标识、第一数据；处理单元，用于确定第一数据包是否为非长期演进上的语音VoLTE数据包；发送单元，用于在确定第一数据包为非长期演进上的语音VoLTE数据包的情况下：将第一数据发送至本地服务器。
第三方面，本申请实施例提供一种网关，包括：收发器、处理器、存储器和通信接口，其中，所述收发器、所述处理器、所述存储器和所述通信接口之间通过总线连接；所述收发器，用于接收基站发送的第一数据包；在确定所述第一数据包为非长期演进上的语音VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器；其中，所述第一数据包包括第一数据；所述处理器，用于读取所述存储器中的程序，执行以下方法：确定所述第一数据包是否为非长期演进上的语音VoLTE数据包；所述存储器，用于存储一个或多个可执行程序，可以存储所述处理器在执行操作时所使用的数据。
第四方面，本申请实施例提供一种非暂态计算机可读存储介质，所述非暂态计算机可读存储介质存储计算机指令，所述计算机指令用于使所述计算机执行第一方面或第一方面的任意可能的实施方式中的方法。
第五方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行第一方面或第一方面的任意可能的实施方式中的方法。
本申请实施例中，由于包括基站、网关、核心网、本地服务器的LTE系统，基站和核心网通过网关建立链接，基站和本地服务器通过网关建立链接；网关接收基站发送的第一数据包；其中，第一数据包包括第一数据；网关在确定第一数据包为非长期演进上的语音(Voice over Long Term Evolution，简称VoLTE)数据包的情况下：将第一数据发送至本地服务器。如此，在第一数据包为非VoLTE数据包的情况下，将第一数据包中的第一数据发送至本地服务器，可以实现非VoLTE数据的分流，进而缓解了核心网压力。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简要介绍。
图1为本申请实施例提供的一种数据分流系统架构示意图；
图2为本申请实施例提供的一种数据分流的方法流程示意图；
图3为本申请实施例提供的终端和本地服务器之间开启全数据本地分流交互的示意图；
图4为本申请实施例提供的终端和本地服务器之间关闭全数据本地分流交互的示意图；
图5为本申请实施例提供的上下行数据包封装格式示例；
图6为本申请实施例提供的一种上行数据分流的方法流程示意图；
图7为本申请实施例提供的一种下行数据分流的方法流程示意图；
图8为本申请实施例提供的一种用于数据分流的网关结构示意图；
图9为本申请实施例提供的一种网关的结构示意图。
具体实施方式
为了使本申请的目的、技术方案及有益效果更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
图1示例性示出了本申请实施例适用的一种数据分流系统架构示意图，数据分流系统包括核心网、本地服务器、网关和基站，基站和核心网通过网关建立链接，基站和本地服务器通过网关建立链接，网关管理多个基站，每个基站管理多个终端；如图1所示，该系统架构100包括互联网101、核心网102、本地服务器103、网关104、基站105、基站106和基站107，其中，一方面，网关104分别连接基站105、基站106和基站107；另一方面，网关104分别连接核心网102和本地服务器103；核心网102和本地服务器103连接互联网101。
本申请实施例中，网关104接收基站发送的第一数据包，可以发送至核心网102或本地服务器103；其中，若该第一数据包为VoLTE数据包，则网关104将该第一数据包发送至核心网102；若该第一数据包为非VoLTE数据包，则网关104将该第一数据包发送本地服务器103。
本申请实施例中，一方面，网关104接收本地服务器103发送的第二数据包，则将该第二数据包发送至基站，通过基站发送至该第二数据包中包括的终端标识对应的终端。另一方面，网关104接收核心网102发送的数据包，并将该数据包发送至基站。
本申请实施例中，终端通过安装与本地服务器内HTTPS服务相配套的应用软件控制网关的数据分流与链路选择；基站负责为终端提供覆盖并连接网关与本地服务器；网关负责数据分流具体操作与“是否全分流”的控制；本地服务器提供面向终端应用软件的HTTPS服务、消息交互控制，本地服务器与网关联合控制UE“是否全数据分流”，本地服务器承接终端直接访问交互以外，还提供NAT功能，为分流而至的数据报文提供NAT转化联网服务。
图2示例性示出了本申请实施例提供的一种数据分流方法流程示意图。
基于图1所示的系统架构，如图2所示，本申请实施例提供的一种数据分流方法，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，基站和核心网通过网关建立链接，基站和本地服务器通过网关建立链接，该方法包括以下步骤：
步骤S201：网关接收基站发送的第一数据包；其中，第一数据包包括第一数据；
步骤S202：网关在确定第一数据包为非长期演进上的语音VoLTE数据包的情况下：将第一数据发送至本地服务器。
上述实施例中，步骤S201中，第一数据包为终端向基站发送的上行数据包，其中，第一数据包中包括的第一数据可以为VoLTE数据，也可以为非VoLTE数据。
上述实施例中，步骤S202中，确定第一数据包是否为VoLTE数据包的方法有多种，本申请实施例提供一种可选的方案：若收到第一数据包的承载通路的标度值(QoS Class Identifier，简称QCI)为1、2和5中的任一个值时，则第一数据包为VoLTE数据包；若QCI不为1、2和5中的任一个值时，则第一数据包为非VoLTE数据包。
本申请实施例中，由于网关接收基站发送的第一数据包；其中，第一数据包包括第一终端标识、第一数据；网关在确定第一数据包为非VoLTE数据包的情况下：将第一数据包中的第一数据发送至本地服务器；相对于现有技术中的将第一数据包中的第一数据发送至核心网，本申请实施例提供的方法可以实现非VoLTE数据的分流，进而缓解了核心网压力。
基于上述实施例中的步骤S202，网关将第一数据发送至本地服务器包括两种情况：
第一种情况为：网关在确定第一数据包为非VoLTE数据包的情况下：将第一数据发送至本地服务器，包括：网关在确定第一数据包为非VoLTE数据包、且网关处于开启全数据本地分流状态的情况下，将第一数据发送至本地服务器。如此，网关处于开启全数据本地分流状态时，对接收到的所有非VoLTE数据包，强制分流至本地服务器；相对于现有技术中的仅仅对访问VPN服务器的部分数据流进行分流的方法，本申请实现对非VoLTE数据的全数据本地分流，也就是说，本申请实施例提供的方案相对于现有技术数据分流更彻底，可以减轻核心网的压力。
第二种情况为：第一数据包中还包括目的IP地址；网关在确定第一数据包为非VoLTE数据包的情况下：将第一数据发送至本地服务器，包括：网关在确定第一数据包为非VoLTE数据包，且网关在确定目的IP地址与本地服务器的IP地址匹配的情况下，将第一数据发送至本地服务器。如此，网关对访问本地服务器的非VoLTE数据分流，比如，本地服务器的IP地址为：192.168.26.100，第一数据包中的目的IP地址为192.168.26.100，则网关将第一数据包中的第一数据强制分流至本地服务器。如此，减少了需要经由核心网处理的数据包，减少了核心网的压力。
本申请实施例中，网关是否处于开启全数据本地分流状态，通过终端和本地服务器之间采用HTTPS加密方式的安全通信，确定是否开启全数据本地分流。
为了更清楚的说明如何开启全数据本地分流，图3示例性示出了本申请实施例提供的终端和本地服务器之间开启全数据本地分流交互的示意图。如图3所示，开启全数据本地分流的步骤如下：
步骤S301：终端向网关发送开启全数据分流消息；
步骤S302：网关向本地服务器转发开启全数据分流消息(Ping)；
步骤S303：本地服务器向网关发送第一请求消息；其中，第一请求消息可以为本地服务器对某个终端执行Ping操作，以Ping操作的报文大小72字节为开启全数据本地分流的控制约定；
步骤S304：若网关接收到第一请求消息为72字节大小，则开启全数据本地分流；
步骤S305：网关开启全数据本地分流之后，向本地服务器发送第一应答消息；其中，第一应答消息为Ping操作的应答消息，若网关开启全数据本地分流，则网关向本地服务器发送的第一应答消息为72字节；
步骤S306：本地服务器接收到第一应答消息之后，若第一应答消息为72字节，则向网关发送全数据分流开启消息(Https)；
步骤S307：网关向终端发送全数据分流开启消息；
上述步骤S301、S302中的开启全数据分流消息采用局域网通信的方式，步骤S306、S307中的全数据分流开启消息采用HTTPS加密的方式。
为了更清楚的说明如何关闭全数据本地分流，图3示例性示出了本申请实施例提供的终端和本地服务器之间关闭全数据本地分流交互的示意图。如图4所示，关闭全数据本地分流的步骤如下：
步骤S401：终端向网关发送关闭全数据分流消息；
步骤S402：网关向本地服务器转发关闭全数据分流消息(Ping)；
步骤S403：本地服务器向网关发送第二请求消息；其中，第二请求消息可以为本地服务器对某个终端执行Ping操作，以Ping操作的报文大小2字节为关闭全分流的控制约定；
步骤S404：若网关接收到第二请求消息为2字节大小，则关闭全数据分流；
步骤S405：网关关闭全数据分流之后，向本地服务器发送第二应答消息；其中，第二应答消息为Ping操作的应答消息，若网关关闭全数据本地分流，则网关向本地服务器发送的第二应答消息为2字节；
步骤S406：本地服务器接收到第二应答消息，若第二应答消息为2字节,则向网关发送全数据分流关闭消息(Https)；
步骤S407：网关向终端发送全数据分流关闭消息；
上述步骤S401、S402中的关闭全数据分流消息采用局域网通信的方式，步骤S406、S407中的全数据分流关闭消息采用HTTPS加密的方式。
需要说明的是，上述实施例中，网关与本地服务器关于分流控制采用局部直连通信的安全方式，若网关一旦发现本地服务器对某终端执行Ping操作，则代替此终端作回应、并执行相应的分流控制，其中，以72字节为开启全数据分流、2字节为关闭全数据分流的控制约定；而Ping操作的报文大小并不局限于以72字节为开启、2字节为关闭全数据分流的控制约定，比如，也可以为120字节为开启、36字节为关闭全数据分流的控制约定。
可选地，本申请实施例中实现终端和本地服务器的交互方式有多种，其 中一种方式为：在终端上安装应用软件，用于实现和本地服务器的是否开启全数据分流；本申请实施例中，根据传统LTE系统，借助网关/本地服务器/终端联合控制，依靠网关灵活的分流控制技术，最终实现客户终端自主选择传统LTE联网方式或者网关本地分流的联网方式，同时将网关与本地服务器关于“是否全数据分流”的控制内部完全化，缓解核心网络压力的同时，也多元化运营商开放自身能力平台的方式，为运营商拓宽市场提供一种全新的网络传输支撑。
可选地，网关接收基站发送的第一数据包之后，还包括：网关在确定第一数据包满足预设条件中的任一项，将第一数据发送至核心网；其中，预设条件包括：
条件一，第一数据包为非VoLTE数据包、且目的IP地址与本地服务器的IP地址不匹配、且网关处于关闭全数据本地分流状态；
条件二，第一数据包为VoLTE数据包。
上述实施例中，若第一数据包为VoLTE数据包，即QCI为1、2和5中的任一个值时，也就是说，第一数据为语音数据，无论网关是否处于开启全数据本地分流状态，都将第一数据发送至核心网处理；若第一数据包为非VoLTE数据包、且其中的目的IP地址与本地服务器的IP地址不匹配、且网关处于关闭全数据本地分流状态，将第一数据发送至核心网；本申请实施例中，将第一数据发送至核心网包括：网关更新第一数据包中的以太网Ethernet头、隧道IP头，得到待发送数据包，并将待发送数据包发送至核心网。
可选地，第一数据包还包括IP头、UDP头、GTP-U头和第一终端标识；将第一数据发送至本地服务器之前，还包括：网关记录第一数据包中包括的隧道IP头、隧道UDP头和GTP-U头与第一终端标识的对应关系，并将对应关系加入第一集合；网关封装第一数据和第一终端标识，得到第一待发送数据包；网关将第一待发送数据包发送至本地服务器。
本申请实施例中，第一数据包包括Ethernet头、IP头、UDP头、GTP-U头、第一终端标识和第一数据，其中，IP头、UDP头、GTP-U头与第一终端 标识一一对应；网关接收到第一数据包之后，存在两种情况：
情况一，网关确定第一数据包为VoLTE数据包，则将该VoLTE数据包接封装之后，得到第一数据和第一终端标识；然后将第一数据和第一终端标识封装新的Ethernet头、IP头、UDP头、GTP-U头，再发送至核心网。
情况二，网关确定第一数据包为非VoLTE数据包，则将该非VoLTE数据包接封装之后，得到第一终端标识和第一数据，记录第一数据包中的IP头、UDP头、GTP-U头与第一终端标识的对应关系；并将第一终端标识和第一数据封装上新的Ethernet头，发送至本地服务器。
本申请实施例中，网关接收基站发送的第一数据包，记录第一数据包中的IP头、UDP头、GTP-U头与第一终端标识的对应关系，以便于网关接收到本地服务器发送的第二数据包时，确定出第二数据包中的终端标识对应的IP头、UDP头、GTP-U头，进而发送至与本地服务器进行数据交互的终端，如此，从互联网获得的下行数据通过本地服务器发送至网关，减小了核心网的压力。
可选地，本申请实施例提供的数据分流的方法还包括：网关接收本地服务器发送的第二数据包；其中，第二数据包包括待查询终端标识和第二数据；网关在网关确定出第一集合中与待查询终端标识匹配的终端标识的情况下，确定出与待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头；网关根据与待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头，封装第二数据，得到第二待发送数据包；网关将第二待发送数据包发送至基站。
本申请实施例中，第二数据包中包括的数据为下行数据，待查询终端标识为第二数据需要到达的终端对应的标识；由于网关会收到多个终端发送的多个第一数据包，所以在网关接收到第二数据包之后，需要根据第二数据包中包括的待查询终端标识，以确定将第二数据发送至相应的终端。
举个例子，网关接收到基站发送的2个第一数据包，分别为：数据包一，终端标识为UE 1；数据包二，终端标识为UE 2；其中，UE 1对应的隧道IP头、 隧道UDP头、GTPU头分别为IP 1、UDP 1和GTPU 1；UE 2对应的隧道IP头、隧道UDP头、GTPU头分别为IP 2、UDP 2和GTPU 2；网关接收到第二数据包，其中包括的待查询终端标识为UE 2，则网关将该第二数据包中的第二数据封装上UE 2对应的隧道IP头、隧道UDP头、GTPU头分别为IP 2、UDP 2和GTPU 2，得到第二待发送数据包；并将封装后的第二待发送数据包发送至基站，通过基站发送至终端UE 2。如此，本申请实施例将部分下行数据通过本地服务器发送至网关，进而减少了通过核心网的数据流量，减轻了核心网的压力。
为了更清楚的介绍基站、网关、核心网和本地服务器之间的数据包的格式，图5示例性示出了本申请实施例提供的上下行数据包封装格式示例。
本申请实施例中，LTE系统中的数据传输链路包括两个：链路一为基站、网关、核心网和互联网组成的链路，链路二为基站、网关、本地服务器和互联网组成的链路。
如图5所示，上行数据传输由基站向互联网方向，具体包括：
(1)由基站向网关发送上行数据包501，其封装格式为：Ethernet头、S1隧道IP头、S1隧道UDP头、GTP-U头、终端IP包，其中，上行数据包501即为上述实施例中的第一数据包，终端IP包中包括第一数据和第一终端标识；
(2)网关接收到上行数据包501之后，判断是向核心网或本地服务器发送数据；
若网关向核心网发送数据，则更新上行数据包501中的Ethernet头、S1隧道IP头，得到上行数据包502，其封装格式为：Ethernet头、S1隧道IP头、S1隧道UDP头、GTP-U头、终端IP包；并将上行数据包502发送至核心网；
若网关向本地服务器发送数据，则记录上行数据包501中的S1隧道IP头、S1隧道UDP头、GTP-U头与第一终端标识的对应关系，加入第一集合中；并将上行数据包501中的S1隧道IP头、S1隧道UDP头、GTP-U头拆除，更新其中的Ethernet头，得道上行数据包504，其封装格式为：Ethernet 头、终端IP包；并将上行数据包504发送至本地服务器；
(3)核心网接收到上行数据包502之后，拆除其中的S1隧道IP头、S1隧道UDP头、GTP-U头，并更新其中的Ethernet头，得到上行数据包503，其封装格式为：Ethernet头、终端IP包；向互联网发送上行数据包503；
(4)本地服务器接收到上行数据包504之后，更新其中的Ethernet头，得到上行数据包505，其封装格式为：Ethernet头、终端IP包；向互联网发送上行数据包505。
相应地，如图5所示，下行数据传输由互联网向基站方向，具体包括：
(1)互联网向核心网或本地服务器发送下行数据包；若是向核心网方向，发送下行数据包506，其封装格式为：Ethernet头、终端IP包；若是向核心网方向，发送下行数据包508，其封装格式为：Ethernet头、终端IP包；
(2)核心网接收到下行数据包506，添加S1隧道IP头、S1隧道UDP头、GTP-U头，更新其中的Ethernet头，得到下行数据包507，其封装格式为：Ethernet头、S1隧道IP头、S1隧道UDP头、GTP-U头、终端IP包；向网关发送下行数据包507；
(3)本地服务器接收到下行数据包508，更新其中的Ethernet头，得到下行数据包509，其封装格式为：Ethernet头、终端IP包；向网关发送下行数据包509；
(4)网关接收到核心网发送的下行数据包507时，更新其中的Ethernet头、S1隧道IP头之后，得到下行数据包510；网关接收到本地服务器发送的下行数据包509时，根据终端IP包中包括的待查询终端标识，在第一集合中查找与待查询终端标识匹配的终端标识，并确定出与待查询终端标识匹配的终端标识对应的S1隧道IP头、S1隧道UDP头、GTP-U头，封装终端IP包得到下行数据包510，其封装格式为：Ethernet头、S1隧道IP头、S1隧道UDP头、GTP-U头、终端IP包；网关将下行数据包510发送至基站。
为了更清楚的介绍上述方法流程，本申请实施例提供以下示例。
图6示例性示出了本申请实施例提供的一种上行数据分流的方法流程示 意图，基于图1所示的系统架构，如图6所示，本申请实施例提供的另一种数据分流的方法，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，所述基站和所述核心网通过所述网关建立链接，所述基站和所述本地服务器通过所述网关建立链接，该方法包括以下步骤：
步骤S601：所述网关接收所述基站发送的第一数据包；其中，所述第一数据包包括第一终端标识、第一数据；
步骤S602：所述网关确定第一数据包是否为VoLTE数据包；若是，则执行步骤S608；若否，则执行步骤S603；
步骤S603：所述网关确定第一数据包中的目的IP地址是否与所述本地服务器的IP地址匹配；若是，则执行步骤S605；若否，则执行步骤S604；
步骤S604：网关是否处于开启全数据本地分流状态；若是，则执行步骤S605；若否，则执行步骤S608；
步骤S605：网关记录第一数据包中包括的隧道IP头、隧道UDP头和GTP-U头与第一终端标识的对应关系，并将对应关系加入第一集合；
步骤S606：网关拆除第一数据包中的隧道IP头、隧道UDP头和GTP-U头，封装第一数据和第一终端标识，得到第一待发送数据包；
步骤S607：网关将第一待发送数据包发送至本地服务器；
步骤S608：网关将第一数据发送至核心网。
图7示例性示出了本申请实施例提供的一种下行数据分流的方法流程示意图，基于图1所示的系统架构，如图7所示，本申请实施例提供的另一种数据分流的方法，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，所述基站和所述核心网通过所述网关建立链接，所述基站和所述本地服务器通过所述网关建立链接，该方法包括以下步骤：
步骤S701：网关接收本地服务器发送的第二数据包；其中，第二数据包包括待查询终端标识和第二数据；
步骤S702：网关在第一集合中查询是否存在与待查询终端标识匹配的终端标识；若是，则执行步骤S703；若否，则执行步骤S706；
步骤S703：确定出与待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头；
步骤S704：网关根据与待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头，封装第二数据，得到第二待发送数据包；
步骤S705：网关将第二待发送数据包发送至基站；
步骤S706：丢弃该第二数据包。
从上述图6和图7的方法流程可以看出：网关在确定第一数据包为非VoLTE数据包的情况下：在网关处于开启全数据分流状态时，将第一数据发送至本地服务器。如此，实现了上行数据中非VoLTE数据的分流，进而缓解了核心网压力；而且，网关接收本地服务器发送的第二数据包，如此下行数据中的非VoLTE数据也不经由核心网，通过本地服务器发送至网关，减少了通过核心网的数据流量，缓解了核心网的压力；本申请实施例融合网关分流技术与本地服务器数据流承接及配套方案，将网关/本地服务器/终端融合一起，使终端通过LTE系统上网的链路变为终端可控化，缓解核心网压力、开放核心网侧的链路选择能力、丰富了既有服务模式；本申请灵活可控的分流系统及网关，为运营商拓宽市场提供一种全新的方案。
图8示例性示出了本申请实施例提供的一种用于数据分流的网关的结构示意图。
基于相同构思，本申请实施例提供的一种用于数据分流的网关，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，所述基站和所述核心网通过所述网关建立链接，所述基站和所述本地服务器通过所述网关建立链接，用于数据分流的网关用于执行上述方法流程，如图8所示，该用于数据分流的网关800包括接收单元801、处理单元802和发送单元803；其中：
接收单元801，用于接收所述基站发送的第一数据包；其中，所述第一数据包包括第一数据；
处理单元802，用于确定所述第一数据包是否为非长期演进上的语音 VoLTE数据包；
发送单元803，用于在确定所述第一数据包为非长期演进上的语音VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器。
可选地，所述发送单元803，用于：在所述处理单元802确定所述第一数据包为非VoLTE数据包、且所述网关处于开启全数据本地分流状态的情况下，将所述第一数据发送至所述本地服务器。
可选地，所述第一数据包中还包括目的IP地址；所述发送单元803，用于：在所述处理单元802确定所述第一数据包为非VoLTE数据包、且所述目的IP地址与所述本地服务器的IP地址匹配的情况下，将所述第一数据发送至所述本地服务器。所述处理单元802，还用于：确定所述第一数据包是否满足预设条件中的任一项；所述发送单元803，还用于：在确定所述第一数据包满足预设条件中的任一项，将所述第一数据发送至所述核心网；其中，所述预设条件包括：第一数据包为非VoLTE数据包、且所述目的IP地址与所述本地服务器的IP地址不匹配、且所述网关处于关闭全数据本地分流状态；所述第一数据包为VoLTE数据包。
可选地，所述第一数据包还包括IP头、UDP头、GTP-U头和第一终端标识；所述处理单元802，还用于：记录所述第一数据包中包括的所述隧道IP头、所述隧道UDP头和所述GTP-U头与所述第一终端标识的对应关系，并将所述对应关系加入第一集合；封装所述第一数据和所述第一终端标识，得到第一待发送数据包；所述发送单元803，还用于：将所述第一待发送数据包发送至所述本地服务器。
可选地，所述接收单元801，还用于：接收所述本地服务器发送的第二数据包；其中，所述第二数据包包括待查询终端标识和第二数据；所述处理单元802，还用于：在确定出所述第一集合中与所述待查询终端标识匹配的终端标识的情况下，确定出与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头；根据所述与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头，封装所述第二数据，得 到第二待发送数据包；所述发送单元803，还用于：将所述第二待发送数据包发送至所述基站。
从上述内容可以看出：本申请实施例中，由于网关接收基站发送的第一数据包；其中，第一数据包包括第一数据；网关在确定第一数据包为非VoLTE数据包的情况下：将第一数据发送至本地服务器。如此，可以实现非VoLTE数据的分流，进而缓解了核心网压力。
应理解，以上各个单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。
基于相同构思，本申请提供一种网关，可用于执行上述数据分流的方法流程。图9为本申请提供的一种网关的结构示意图。该网关900包括收发器901、处理器902、存储器903和通信接口904；其中，收发器901、处理器902、存储器903和通信接口904通过总线905相互连接。
其中，存储器903用于存储程序。具体地，程序可以包括程序代码，程序代码包括计算机操作指令。存储器903可以为易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，简称RAM)；也可以为非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，简称HDD)或固态硬盘(solid-state drive，简称SSD)；还可以为上述任一种或任多种易失性存储器和非易失性存储器的组合。
存储器903存储了如下的元素，可执行模块或者数据结构，或者它们的子集，或者它们的扩展集：
操作指令：包括各种操作指令，用于实现各种操作。
操作系统：包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。
总线905可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture， 简称EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信接口904可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为WLAN接口。
处理器902可以是中央处理器(central processing unit，简称CPU)，网络处理器(network processor，简称NP)或者CPU和NP的组合。还可以是硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，简称ASIC)，可编程逻辑器件(programmable logic device，简称PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，简称CPLD)，现场可编程逻辑门阵列(field-programmable gate array，简称FPGA)，通用阵列逻辑(generic array logic，简称GAL)或其任意组合。
所述收发器901，用于接收基站发送的第一数据包；在确定所述第一数据包为非长期演进上的语音VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器；其中，所述第一数据包包括第一数据；所述处理器902，用于读取所述存储器903中的程序，执行以下方法：确定所述第一数据包是否为非长期演进上的语音VoLTE数据包；所述存储器903，用于存储一个或多个可执行程序，可以存储所述处理器902在执行操作时所使用的数据。
本申请实施例中，由于网关接收基站发送的第一数据包；其中，第一数据包包括第一数据；在确定第一数据包为非VoLTE数据包的情况下：将第一数据发送至本地服务器。如此，可以实现非VoLTE数据的分流，进而缓解了核心网压力。
可选的，所述收发器901具体用于：在确定所述第一数据包为非VoLTE数据包，且所述网关处于开启全数据本地分流状态的情况下，将所述第一数 据发送至所述本地服务器。
可选的，所述第一数据包中还包括目的IP地址；所述收发器901具体用于：在确定所述第一数据包为非VoLTE数据包，且在确定所述目的IP地址与所述本地服务器的IP地址匹配的情况下，将所述第一数据发送至所述本地服务器。
可选的，所述处理器902，还用于确定所述第一数据包是否满足预设条件中的任一项；所述收发器901，还用于：在确定所述第一数据包满足预设条件中的任一项，将所述第一数据发送至所述核心网；其中，所述预设条件包括：第一数据包为非VoLTE数据包、且所述目的IP地址与所述本地服务器的IP地址不匹配、且所述网关处于关闭全数据本地分流状态；所述第一数据包为VoLTE数据包。
可选的，所述第一数据包还包括IP头、UDP头、GTP-U头和第一终端标识；所述处理器902，还用于：记录所述第一数据包中包括的所述隧道IP头、所述隧道UDP头和所述GTP-U头与所述第一终端标识的对应关系，并将所述对应关系加入第一集合；封装所述第一数据和所述第一终端标识，得到第一待发送数据包；所述收发器901，还用于：将所述第一待发送数据包发送至所述本地服务器。
可选的，所述收发器901，还用于：接收所述本地服务器发送的第二数据包；将第二待发送数据包发送至所述基站；其中，所述第二数据包包括待查询终端标识和第二数据；所述处理器902，还用于：在确定出所述第一集合中与所述待查询终端标识匹配的终端标识的情况下，确定出与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头；根据所述与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头，封装所述第二数据，得到第二待发送数据包。
本领域内的技术人员应明白，本申请实施例可提供为方法、系统、或计算机程序产品。因此，本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在 一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (20)

  1. 一种数据分流方法，其特征在于，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，所述基站和所述核心网通过所述网关建立链接，所述基站和所述本地服务器通过所述网关建立链接，所述方法包括：
    所述网关接收所述基站发送的第一数据包；其中，所述第一数据包包括第一数据；
    所述网关在确定所述第一数据包为非长期演进上的语音VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器。
  2. 如权利要求1所述的方法，其特征在于，所述网关在确定所述第一数据包为非VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器，包括：
    所述网关在确定所述第一数据包为非VoLTE数据包，且所述网关处于开启全数据本地分流状态的情况下，将所述第一数据发送至所述本地服务器。
  3. 如权利要求1所述的方法，其特征在于，所述第一数据包中还包括目的IP地址；
    所述网关在确定所述第一数据包为非VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器，包括：
    所述网关在确定所述第一数据包为非VoLTE数据包，且所述网关在确定所述目的IP地址与所述本地服务器的IP地址匹配的情况下，将所述第一数据发送至所述本地服务器。
  4. 如权利要求3所述的方法，其特征在于，所述网关接收所述基站发送的第一数据包之后，还包括：
    所述网关在确定所述第一数据包满足预设条件中的任一项，将所述第一数据发送至所述核心网；
    其中，所述预设条件包括：
    第一数据包为非VoLTE数据包、且所述目的IP地址与所述本地服务器的 IP地址不匹配、且所述网关处于关闭全数据本地分流状态；
    所述第一数据包为VoLTE数据包。
  5. 如权利要求1至4任一权利要求所述的方法，其特征在于，所述第一数据包还包括IP头、UDP头、GTP-U头和第一终端标识；
    所述将所述第一数据发送至所述本地服务器之前，还包括：
    所述网关记录所述第一数据包中包括的所述隧道IP头、所述隧道UDP头和所述GTP-U头与所述第一终端标识的对应关系，并将所述对应关系加入第一集合；
    所述网关封装所述第一数据和所述第一终端标识，得到第一待发送数据包；
    所述网关将所述第一待发送数据包发送至所述本地服务器。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    所述网关接收所述本地服务器发送的第二数据包；其中，所述第二数据包包括待查询终端标识和第二数据；
    所述网关在确定出所述第一集合中与所述待查询终端标识匹配的终端标识的情况下，确定出与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头；
    所述网关根据所述与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头，封装所述第二数据，得到第二待发送数据包；
    所述网关将所述第二待发送数据包发送至所述基站。
  7. 一种用于数据分流的网关，其特征在于，适用于包括基站、网关、核心网、本地服务器的长期演进LTE系统，所述基站和所述核心网通过所述网关建立链接，所述基站和所述本地服务器通过所述网关建立链接，所述网关包括：
    接收单元，用于接收所述基站发送的第一数据包；其中，所述第一数据 包包括第一数据；
    处理单元，用于确定所述第一数据包是否为非长期演进上的语音VoLTE数据包；
    发送单元，用于在确定所述第一数据包为非长期演进上的语音VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器。
  8. 如权利要求7所述的网关，其特征在于，所述发送单元，用于：
    在所述处理单元确定所述第一数据包为非VoLTE数据包、且所述网关处于开启全数据本地分流状态的情况下，将所述第一数据发送至所述本地服务器。
  9. 如权利要求7所述的网关，其特征在于，所述第一数据包中还包括目的IP地址；
    所述发送单元，用于：
    在所述处理单元确定所述第一数据包为非VoLTE数据包、且所述目的IP地址与所述本地服务器的IP地址匹配的情况下，将所述第一数据发送至所述本地服务器。
  10. 如权利要求9所述的网关，其特征在于，所述处理单元，还用于：
    确定所述第一数据包是否满足预设条件中的任一项；
    所述发送单元，还用于：
    在确定所述第一数据包满足预设条件中的任一项，将所述第一数据发送至所述核心网；
    其中，所述预设条件包括：
    第一数据包为非VoLTE数据包、且所述目的IP地址与所述本地服务器的IP地址不匹配、且所述网关处于关闭全数据本地分流状态；
    所述第一数据包为VoLTE数据包。
  11. 如权利要求7至10任一权利要求所述的网关，其特征在于，所述第一数据包还包括IP头、UDP头、GTP-U头和第一终端标识；
    所述处理单元，还用于：
    记录所述第一数据包中包括的所述隧道IP头、所述隧道UDP头和所述GTP-U头与所述第一终端标识的对应关系，并将所述对应关系加入第一集合；
    封装所述第一数据和所述第一终端标识，得到第一待发送数据包；
    所述发送单元，还用于：
    将所述第一待发送数据包发送至所述本地服务器。
  12. 如权利要求11所述的网关，其特征在于，所述接收单元，还用于：
    接收所述本地服务器发送的第二数据包；其中，所述第二数据包包括待查询终端标识和第二数据；
    所述处理单元，还用于：
    在确定出所述第一集合中与所述待查询终端标识匹配的终端标识的情况下，确定出与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头；
    根据所述与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头，封装所述第二数据，得到第二待发送数据包；
    所述发送单元，还用于：
    将所述第二待发送数据包发送至所述基站。
  13. 一种网关，其特征在于，包括：收发器、处理器、存储器和通信接口，其中，所述收发器、所述处理器、所述存储器和所述通信接口之间通过总线连接；
    所述收发器，用于接收基站发送的第一数据包；在确定所述第一数据包为非长期演进上的语音VoLTE数据包的情况下：将所述第一数据发送至所述本地服务器；其中，所述第一数据包包括第一数据；
    所述处理器，用于读取所述存储器中的程序，执行以下方法：确定所述第一数据包是否为非长期演进上的语音VoLTE数据包；
    所述存储器，用于存储一个或多个可执行程序，可以存储所述处理器在执行操作时所使用的数据。
  14. 如权利要求13所述的网关，其特征在于，所述收发器具体用于：
    在确定所述第一数据包为非VoLTE数据包，且所述网关处于开启全数据本地分流状态的情况下，将所述第一数据发送至所述本地服务器。
  15. 如权利要求13所述的网关，其特征在于，所述第一数据包中还包括目的IP地址；
    所述收发器具体用于：
    在确定所述第一数据包为非VoLTE数据包，且在确定所述目的IP地址与所述本地服务器的IP地址匹配的情况下，将所述第一数据发送至所述本地服务器。
  16. 如权利要求15所述的网关，其特征在于，所述处理器，还用于确定所述第一数据包是否满足预设条件中的任一项；
    所述收发器，还用于：
    在确定所述第一数据包满足预设条件中的任一项，将所述第一数据发送至所述核心网；
    其中，所述预设条件包括：
    第一数据包为非VoLTE数据包、且所述目的IP地址与所述本地服务器的IP地址不匹配、且所述网关处于关闭全数据本地分流状态；
    所述第一数据包为VoLTE数据包。
  17. 如权利要求13至16任一权利要求所述的网关，其特征在于，所述第一数据包还包括IP头、UDP头、GTP-U头和第一终端标识；
    所述处理器，还用于：
    记录所述第一数据包中包括的所述隧道IP头、所述隧道UDP头和所述GTP-U头与所述第一终端标识的对应关系，并将所述对应关系加入第一集合；
    封装所述第一数据和所述第一终端标识，得到第一待发送数据包；
    所述收发器，还用于：
    将所述第一待发送数据包发送至所述本地服务器。
  18. 如权利要求17所述的网关，其特征在于，所述收发器，还用于：
    接收所述本地服务器发送的第二数据包；将第二待发送数据包发送至所述基站；其中，所述第二数据包包括待查询终端标识和第二数据；
    所述处理器，还用于：
    在确定出所述第一集合中与所述待查询终端标识匹配的终端标识的情况下，确定出与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头；
    根据所述与所述待查询终端标识匹配的终端标识对应的隧道IP头、隧道UDP头和GTP-U头，封装所述第二数据，得到第二待发送数据包。
  19. 一种非暂态计算机可读存储介质，其特征在于，所述非暂态计算机可读存储介质存储计算机指令，所述计算机指令用于使所述计算机执行权利要求1～7任一权利要求所述方法。
  20. 一种计算机程序产品，其特征在于，所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序，所述计算机程序包括程序指令，当所述程序指令被计算机执行时，使所述计算机执行权利要求1～7任一权利要求所述方法。
PCT/CN2017/115714 2017-06-09 2017-12-12 一种数据分流方法和网关 WO2018223645A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/620,679 US11317322B2 (en) 2017-06-09 2017-12-12 Data offloading method and gateway

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710432932.7A CN107333295B (zh) 2017-06-09 2017-06-09 一种数据分流方法和网关
CN201710432932.7 2017-06-09

Publications (1)

Publication Number Publication Date
WO2018223645A1 true WO2018223645A1 (zh) 2018-12-13

Family

ID=60195152

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/115714 WO2018223645A1 (zh) 2017-06-09 2017-12-12 一种数据分流方法和网关

Country Status (3)

Country Link
US (1) US11317322B2 (zh)
CN (1) CN107333295B (zh)
WO (1) WO2018223645A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107333295B (zh) 2017-06-09 2021-04-06 京信通信系统（中国）有限公司 一种数据分流方法和网关
US11755609B2 (en) * 2021-04-20 2023-09-12 Dell Products L.P. Automatically detecting data offloading methods using data bucketing and machine learning techniques
CN116017581A (zh) * 2022-12-14 2023-04-25 深圳千通科技有限公司 5g流量分流方法、装置及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102740283A (zh) * 2012-06-20 2012-10-17 北京傲天动联技术有限公司 Lte系统中的网关设备及其数据分流方法
CN103763738A (zh) * 2014-01-17 2014-04-30 电信科学技术研究院 一种业务分流的方法、系统和设备
CN103796246A (zh) * 2012-10-31 2014-05-14 中兴通讯股份有限公司 数据的分流方法、装置及系统
CN105050116A (zh) * 2015-07-13 2015-11-11 北京佰才邦技术有限公司 移动通信系统中的业务处理方法及接入网设备
WO2016180459A1 (en) * 2015-05-11 2016-11-17 Nokia Solutions And Networks Oy Sending multiple g-pdus with a single udp datagram
CN107333295A (zh) * 2017-06-09 2017-11-07 京信通信系统（中国）有限公司 一种数据分流方法和网关

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102547861B (zh) * 2010-12-08 2016-04-13 中兴通讯股份有限公司 数据分流方法及本地网关
US20150103772A1 (en) * 2012-05-16 2015-04-16 Telefonaktiebolaget L M Ericsson (Publ) Routing of Traffic in a Multi-Domain Network
JP6507641B2 (ja) * 2012-11-16 2019-05-08 日本電気株式会社 ネットワークシステムと方法と装置並びにプログラム
CN103841024B (zh) * 2012-11-27 2017-07-21 中国电信股份有限公司 一种家庭网关实现数据分流的方法和家庭网关
JP5958315B2 (ja) * 2012-12-07 2016-07-27 富士通株式会社 ネットワークシステム、オフロード装置、及びネットワークシステムにおけるトラヒックの制御方法
CN103641024A (zh) 2013-12-05 2014-03-19 常熟市诚达港务机械设备厂 新型提升机
US10263903B2 (en) * 2014-02-05 2019-04-16 Ibasis, Inc. Method and apparatus for managing communication flow in an inter-network system
US9277559B2 (en) * 2014-04-11 2016-03-01 Verizon Patent And Licensing Inc. Sharing radio resources among devices of different device classes
US20150304898A1 (en) * 2014-04-21 2015-10-22 Qualcomm Incorporated Systems, methods and apparatus for controlling offloadability of public data network connections to wireless local area networks and detach from cellular networks
US9961587B2 (en) * 2014-06-26 2018-05-01 Gilat Satellite Networks Ltd. Methods and apparatus for optimizing tunneled traffic
WO2016072900A1 (en) * 2014-11-07 2016-05-12 Telefonaktiebolaget L M Ericsson (Publ) Methods, network nodes and user equipments for controlling ip flow mobility in a communication network
US10122547B2 (en) * 2015-08-14 2018-11-06 Nec Corporation Enabling high-bandwidth, responsive mobile applications in LTE networks
US11044203B2 (en) * 2016-01-19 2021-06-22 Cisco Technology, Inc. System and method for hosting mobile packet core and value-added services using a software defined network and service chains

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102740283A (zh) * 2012-06-20 2012-10-17 北京傲天动联技术有限公司 Lte系统中的网关设备及其数据分流方法
CN103796246A (zh) * 2012-10-31 2014-05-14 中兴通讯股份有限公司 数据的分流方法、装置及系统
CN103763738A (zh) * 2014-01-17 2014-04-30 电信科学技术研究院 一种业务分流的方法、系统和设备
WO2016180459A1 (en) * 2015-05-11 2016-11-17 Nokia Solutions And Networks Oy Sending multiple g-pdus with a single udp datagram
CN105050116A (zh) * 2015-07-13 2015-11-11 北京佰才邦技术有限公司 移动通信系统中的业务处理方法及接入网设备
CN107333295A (zh) * 2017-06-09 2017-11-07 京信通信系统（中国）有限公司 一种数据分流方法和网关

Also Published As

Publication number Publication date
CN107333295A (zh) 2017-11-07
US20210144587A1 (en) 2021-05-13
US11317322B2 (en) 2022-04-26
CN107333295B (zh) 2021-04-06

Similar Documents

Publication Publication Date Title
JP6882255B2 (ja) ネットワークセキュリティアーキテクチャ
US10524173B2 (en) System and method to facilitate sharing bearer information in a network environment
US8565076B2 (en) Destination learning and mobility detection in transit network device in LTE and UMTS radio access networks
US10798638B2 (en) Apparatus and method for controller and slice-based security gateway for 5G
WO2020199896A1 (zh) 一种业务流路由控制方法、装置及系统
CN110100425B (zh) 用于促进网络环境中的无状态服务网关操作的系统和方法
WO2014117376A1 (zh) 可定制的移动宽带网络系统和定制移动宽带网络的方法
KR102469973B1 (ko) 통신 방법 및 장치
US9072041B2 (en) Architecture for cellular networks
WO2014101062A1 (zh) 用户面数据传输方法、移动管理网元、演进型基站及系统
US11019546B2 (en) Switching of uplink user plane termination point of a serving gateway for a bearer in dual connectivity operation
US20180167418A1 (en) Apparatus and method for lawful interception
WO2018223645A1 (zh) 一种数据分流方法和网关
US10694558B2 (en) System, method and apparatus for small cell gateway selective data path offload
CN106856455B (zh) 一种gtpu用户面数据转发的方法和装置
KR102397750B1 (ko) 앵커리스 백홀의 지원을 위한 gtp 터널
JP7012727B2 (ja) パケット交換方法及び関連装置
WO2014121606A1 (zh) 业务处理方法和相关设备
EP2854356B1 (en) Method and device for multi-link fusion
EP3167687B1 (en) Network node and method for co-located epdg and pgw functions
WO2015028058A1 (en) Method, apparatus and computer program product for determining maximum segment size
PH12016501945B1 (en) Residential local break out in a communication system
TWI616113B (zh) 用於多重無線存取技術服務之閘道器、系統及方法
US10856344B2 (en) Method and an apparatus for reducing connection set-up time in a communications network
WO2015176208A1 (zh) 数据包转发处理方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17912827

Country of ref document: EP

Kind code of ref document: A1