[go: up one dir, main page]

WO2016150140A1 - Procédé et système de traitement pour un paquet de commande dans une passerelle basée sur un réseau défini par logiciel (sdn) - Google Patents

Procédé et système de traitement pour un paquet de commande dans une passerelle basée sur un réseau défini par logiciel (sdn) Download PDF

Info

Publication number
WO2016150140A1
WO2016150140A1 PCT/CN2015/091137 CN2015091137W WO2016150140A1 WO 2016150140 A1 WO2016150140 A1 WO 2016150140A1 CN 2015091137 W CN2015091137 W CN 2015091137W WO 2016150140 A1 WO2016150140 A1 WO 2016150140A1
Authority
WO
WIPO (PCT)
Prior art keywords
plane function
gateway
tunnel
forwarding plane
message
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/CN2015/091137
Other languages
English (en)
Chinese (zh)
Inventor
宗在峰
谢振华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2016150140A1 publication Critical patent/WO2016150140A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Definitions

  • This application relates to, but is not limited to, the field of network communications.
  • SDN Software Defined Network
  • the mobile network gateway device or the access gateway device based on the SDN architecture divides the functional module into two functions: a gateway control plane function and a gateway forwarding plane function, wherein the gateway forwarding plane function is only responsible for data forwarding, and all control related processing is performed by the gateway.
  • the control plane function is responsible.
  • the functions of the gateway control plane function mainly include the establishment of the user plane tunnel and the configuration of the tunnel information to the gateway forwarding plane function, so that the gateway forwarding plane function can forward data according to the configuration of the gateway control plane function.
  • gateway control plane functions such as user IP address allocation, multicast group management, and other configuration management related to the user terminal.
  • the allocation of the user's IP address can be performed by using a Dynamic Host Configuration Protocol (DHCP) method (DHCPv4 or DHCPv6).
  • DHCPv4 or DHCPv6 Dynamic Host Configuration Protocol
  • RS/RA Router Request/Router Advertisement Message
  • the IP packets related to the IP address allocation are sent by the user equipment (UE, User Equipment) to the gateway forwarding plane through the forwarding plane.
  • the UE may also send other IP packets related to the control, such as the packets that join the multicast group.
  • the gateway forwarding plane function is a pure forwarding function and does not have the ability to control and manage. Therefore, the gateway forwarding plane function cannot handle these IP packets related to control and management.
  • Mobile network gateways or fixed network access gateways usually serve many users.
  • a port is usually assigned to each access terminal on the side of the gateway forwarding plane function facing the user terminal.
  • This port is a logical link or a physical link that isolates data from or to different access terminals.
  • an access terminal may sometimes establish multiple IP connections.
  • multiple different IP connections of one access terminal have unique logical links corresponding thereto.
  • the logical link is a GPRS (General Packet Radio Service) Channel Protocol-User Plane (GTP-U) tunnel.
  • GTP-U General Packet Radio Service
  • logical links are not limited to GTP-U tunnels. Any identity that distinguishes different IP connections of different access terminals can be used to identify a logical link.
  • Identity information used by the user in the control plane process such as access authentication (authentication identity information such as International Mobile Subscriber Identification Number (IMSI), Temporary Mobile Subscriber Identity (M-TMSI), The Integrated Services Digital Network (ISDN) may be different from the identification information used in the IP control message (the identification information in the IP packet is usually a random number or a MAC address, etc.), when one is a lot
  • the gateway forwarding plane function of the access terminal service sends the IP control packet from the terminal to the gateway control plane function, it is difficult for the gateway control plane function to distinguish the users corresponding to the IP control packets.
  • the gateway forwarding plane function may not match the packet to the correct user terminal.
  • the terminal In order to save air interface resources and save power, according to the mobile network protocol, when the terminal does not send and receive data for a period of time, the terminal enters an idle state. When the terminal enters the idle state, the air interface resources are released, and at the same time, the connection from the base station to the gateway is also released. When the terminal is in the idle state, the gateway needs to initiate a paging process when receiving the data sent to the terminal, thereby triggering the terminal to re-establish the connection to the network.
  • the gateway After the gateway is SDNized, the function of initiating paging belongs to the gateway control plane function.
  • the gateway forwarding plane function initiates paging by triggering the gateway control plane function by the SDN controller (SDN Controller) when determining that the received data has no downlink tunnel information. Since paging occurs frequently in the mobile Internet, in order to trigger paging, the gateway forwarding plane function and the gateway control plane function need to exchange information frequently through the SDN controller.
  • SDN Controller SDN Controller
  • the gateway forwarding plane function may also receive the peer end from the GTP-U tunnel. GTP-U control message.
  • the gateway forwarding plane function sends the GTP-U control packet directly to the SDN controller after confirming that the received packet is a GTP-U control packet, and then sends the gateway to the gateway by the SDN controller.
  • Control surface function A GTP-U tunnel corresponding to each bearer of each terminal has a corresponding GTP-U control packet, which is used for tunnel maintenance, such as tunnel keep-alive.
  • other control-related packets may be forwarded to the gateway control plane function in the system.
  • the SDN architecture needs to be forwarded through the SDN controller. However, forwarding a large number of GTP-U messages and other control messages to the SDN controller through the SDN controller is a huge challenge.
  • This document provides a method and system for processing control packets in an SDN-based gateway, which can solve the problem that the gateway control plane function and the gateway forwarding plane function cannot correctly match the control packets to the user, thereby preventing the SDN controller from forwarding a large number of control packets. To ensure the performance of the SDN controller.
  • a method for processing control packets in an SDN-based gateway comprising: establishing a logical channel for each IP connection between a gateway forwarding plane function and a gateway control plane function, wherein the logical channel is used for a gateway forwarding plane function Forwarding control messages related to the IP connection between the gateway control plane function.
  • control message includes:
  • IP connection-related GPRS channel protocol-user plane GTP-U control message The IP connection-related GPRS channel protocol-user plane GTP-U control message.
  • IP connection-related data packet that triggers paging.
  • the process of establishing a logical channel further includes: the gateway control plane function is configured to set, by using an SDN controller, a forwarding rule table of the control packet for the gateway forwarding plane function.
  • the forwarding rule table includes at least rules and actions, where: the rules are used for identification
  • the rules include:
  • the GTP-U packet type of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the GTP-U destination tunnel ID of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function are the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function.
  • the type of user data packet received by the gateway forwarding plane function including the protocol type and UDP or TCP port number or ICMP type.
  • the user data packet is an IP data packet encapsulated in a tunnel whose tunnel destination is a function of a gateway forwarding plane or an IP data packet without tunnel encapsulation;
  • the action is used to process the GTP-U data packet or the user data packet received by the gateway forwarding plane function, and the action includes: encapsulating the data packet received by the gateway forwarding plane function into the gateway forwarding plane function and the gateway control plane.
  • the gateway control plane function is sent in the logical channel between functions.
  • the action includes tunnel information of a gateway control plane function and local tunnel information of a gateway forwarding plane function.
  • control message includes:
  • IP connection-related GPRS channel protocol-user plane GTP-U control message The IP connection-related GPRS channel protocol-user plane GTP-U control message.
  • IP connection-related data packet that triggers paging.
  • the processing system further includes a second processing module, configured to: set, by the SDN controller, a forwarding rule table of the control packet for the gateway forwarding plane function.
  • the forwarding rule table includes at least a rule and an action, where the rule is used to identify the control packet related to the IP connection, where the rule includes:
  • the GTP-U packet type of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the GTP-U destination tunnel ID of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function are the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function.
  • the type of user data packet received by the gateway forwarding plane function including the protocol type and UDP or TCP port number or ICMP type.
  • the user data packet is an IP data packet encapsulated in a tunnel whose tunnel destination is a function of a gateway forwarding plane or an IP data packet without tunnel encapsulation;
  • the action is used to process the GTP-U data packet or the user data packet received by the gateway forwarding plane function, and the action includes: encapsulating the data packet received by the gateway forwarding plane function into the gateway forwarding plane function and the gateway control plane.
  • the gateway control plane function is sent in the logical channel between functions.
  • the action includes tunnel information of a gateway control plane function and local tunnel information of a gateway forwarding plane function.
  • a computer readable storage medium storing computer executable instructions for performing the method of any of the above.
  • a dedicated logical channel is established for each IP connection between the gateway forwarding plane function and the gateway control plane function, and the dedicated logical channel is used for forwarding control between the gateway forwarding plane function and the gateway control plane function.
  • the control message in all the data received from an IP connection is directed to the dedicated logical channel, so that the gateway forwarding plane function forwards the control message to the gateway control plane function through the dedicated logical channel.
  • the dedicated logical channel In this way, the conflict of the identifier information used in the IP control packet in the related art is avoided by using the dedicated logical channel, thereby avoiding the problem that the gateway control plane function and the gateway forwarding plane function cannot correctly match the control packet to the user.
  • the SDN controller is prevented from forwarding a large number of control messages, ensuring the performance of the SDN controller.
  • FIG. 1 is a schematic structural diagram of a method for processing a control packet in an SDN-based gateway according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of an interface of the gateway forwarding plane function in FIG. 1;
  • FIG. 3 is a flowchart of a method for processing a control packet in an SDN-based gateway according to an embodiment of the present invention
  • Figure 4 is a flow chart of the first embodiment of the present invention.
  • Figure 5 is a flow chart of a second embodiment of the present invention.
  • FIG. 6 is a flowchart of a UE disconnecting a PDN connection or a network detachment according to the first embodiment or the second embodiment of the present invention
  • FIG. 7 is a flowchart of a UE entering an idle state according to a third embodiment of the present invention.
  • FIG. 8 is a flowchart of a process when a gateway forwarding plane function receives downlink data of a UE when the UE is in an idle state according to the third embodiment of the present invention
  • Figure 9 is a flow chart of a fourth embodiment of the present invention.
  • Figure 10 is a flow chart of a fifth embodiment of the present invention.
  • FIG. 11 is a flowchart of a UE disconnecting a PDN connection or a network detachment according to a fourth embodiment or a fifth embodiment of the present invention.
  • Figure 12 is a flow chart of a sixth embodiment of the present invention.
  • FIG. 13 is a flowchart of a UE entering an idle state according to a seventh embodiment of the present invention.
  • FIG. 14 is a flowchart of processing when the access gateway AGW receives downlink data of the UE when the UE is in an idle state according to the seventh embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of a method for processing a control packet in an SDN-based gateway according to an embodiment of the present invention.
  • the gateway control plane function 10 is responsible for establishing a forwarding plane function for the terminal 60, for example, selecting the gateway forwarding plane function 20 accessed by the terminal 60, and establishing an IP connection for the terminal 60.
  • a logical link for example, establishment of a GTP-U tunnel
  • an IP address for the access of the terminal 60
  • the gateway control plane function 10 also configures a forwarding rule table for the gateway forwarding plane function 20.
  • the forwarding rule table determines how the gateway forwarding plane function selects the next hop route for the user IP packet and the encapsulation mode for the next hop route.
  • the gateway control plane function 10 configures the forwarding rule table to the gateway forwarding plane function 20 via the SDN controller 30.
  • the gateway control plane function 10 is also associated with the access control function interface 40 to authorize the terminal 60 to allocate forwarding area resources, obtain user subscription information (for bandwidth control, charging, etc.).
  • the gateway forwarding plane function 20 is responsible for forwarding the user IP data packets.
  • the gateway forwarding plane function 20 can forward the user IP data packet to the gateway control plane function 10, and can also forward the user IP data packet to other next hop routes, such as to the next hop router to the Internet network.
  • the access control function 40 is responsible for controlling the access of the terminal 60, for example, performing access authentication on the terminal 60, determining access attributes (such as bandwidth, etc.) of the terminal 60, and in the mobile network, the access control function 40 It is also responsible for mobility management, including user mobility management in both connected and idle states.
  • Access point 50 is an access device for terminal 60.
  • the access device may be a residential gateway (RG), an access point (AP, Access Point), or another customer premises equipment (CPE, Customer Premise Equipment).
  • the access device may be a Node B (NB), an evolved Node B (eNB), a home base station, or an AP.
  • the gateway control plane function 10 may be a physical entity or a virtual network element running on a virtual machine.
  • the gateway control plane function 10 can also be an application (APP) on the SDN controller 30 that interfaces with the SDN controller 30 through the northbound interface.
  • the gateway forwarding plane function 20 supports the Open Flow protocol for the configuration of flow tables.
  • the gateway forwarding plane function 20 can be a combination of one or more switches or other specialized devices.
  • FIG. 2 is a schematic diagram of an interface of the gateway forwarding plane function 20 of FIG.
  • the gateway forwarding plane function 20 can have at least three interfaces, respectively, with a downstream node 70 (eg, an access point device), a gateway control plane function 10 (such as a gateway control plane device), and an upstream node 80 ( For example, the next hop router or switch is connected, corresponding to interface 1, interface 2 and interface 3 in FIG. 2, respectively.
  • a downstream node 70 eg, an access point device
  • a gateway control plane function 10 such as a gateway control plane device
  • an upstream node 80 For example, the next hop router or switch is connected, corresponding to interface 1, interface 2 and interface 3 in FIG. 2, respectively.
  • Interface 1 is divided into a number of logical ports, each logical port corresponds to an IP connection, each logic The port has a corresponding logical port number.
  • the logical port on interface 1 is a GTP-U tunnel, and each IP connection corresponds to a GTP-U tunnel.
  • the gateway forwarding plane function 20 uses one or a group of tunnel IDs (Tunnel Endpoint Identifier (TEID-U, Tunnel Endpoint Identifier)) and the tunnel IP address identify a logical port.
  • tunnel IDs Tunnel Endpoint Identifier (TEID-U, Tunnel Endpoint Identifier)
  • the gateway forwarding plane function 20 interfaces with the gateway control plane function 10 (i.e., interface 2) to assign a logical port to each IP connection, which may also be identified by the tunnel IP and tunnel ID of the gateway forwarding plane function 20. In other embodiments, it may be identified in other ways.
  • the interface that the gateway forwarding plane function 20 is connected to the upstream node 80 ie, the interface 3) may be a simple Layer 2 port or a tunnel for a virtual private network (VPN) according to the application scenario.
  • VPN virtual private network
  • the upstream node is a router or switch connected to the Internet, or a router or switch connected to a Packet Data Network (PDN) network
  • the interface 3 does not distinguish the IP connection, that is, all from the Internet or
  • the data from the PDN network is mixed and sent to the gateway forwarding plane function 20.
  • the gateway forwarding plane function 20 needs to classify the data packets to determine which logical port of which interface to send out.
  • a method for processing a control packet in an SDN-based gateway includes:
  • Step 11 Establish a logical channel for each IP connection between the gateway forwarding plane function and the gateway control plane function;
  • Step 12 Forward, between the gateway forwarding plane function and the gateway control plane function, the control packet related to the IP connection by using the logical channel.
  • control message includes:
  • IP packet-related data packet that triggers paging.
  • the method further includes: the gateway control plane function sets a forwarding rule table of the control packet for the gateway forwarding plane function by using the SDN controller.
  • the forwarding rule table includes at least rules and actions, where the rules are used to identify control messages related to the IP connection, and the rules include:
  • the GTP-U packet type of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the GTP-U destination tunnel ID of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function are the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function.
  • the type of user data packet received by the gateway forwarding plane function including the protocol type and User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) port number or Internet Control Message Protocol. (ICMP, Internet Control Message Protocol) type,
  • the user data packet is an IP data packet encapsulated in a tunnel whose tunnel destination is a function of a gateway forwarding plane or an IP data packet without tunnel encapsulation;
  • the action is used to process the GTP-U data packet or the user data packet received by the gateway forwarding plane function, and the action includes: encapsulating the data packet received by the gateway forwarding plane function into the gateway forwarding plane function and the gateway control plane.
  • the gateway control plane function is sent in the logical channel between functions.
  • the action further includes tunnel information of the gateway control plane function and local tunnel information of the gateway forwarding plane function.
  • the ingress port of the gateway forwarding plane function uses the local end information of the tunnel, and the egress port of the gateway forwarding plane function uses the tunnel peer information identifier.
  • the ingress port of interface 1 is identified by the IP address of the gateway forwarding interface function interface 1 and the tunnel ID of the logical interface of the gateway forwarding interface function interface 1 (ie TEID-U).
  • the outbound port of the interface 1 is identified by the IP address of the downstream node and the tunnel ID of the downstream node (that is, TEID-U).
  • the IP address of the downstream node on interface 1 The outbound port is identified with the tunnel ID of the downstream node (ie TEID-U). Similarly, on interface 2, the local tunnel ID identifies an ingress port, and the peer IP address and tunnel ID identify an egress port. On interface 3, the ingress port can be a Layer 3 tunnel or a common Layer 2 interface.
  • the forwarding rule table on the gateway forwarding plane function is divided into an uplink and a downlink direction.
  • the uplink The direction refers to the data received from the downstream node to the upstream node or the gateway control plane device;
  • the downstream direction is the data packet sent from the upstream node or the gateway control plane device to the downstream node.
  • the uplink forwarding rule table of the gateway forwarding plane function is shown in Table 1:
  • the entry 1 determines the next hop according to the ingress port and the destination address. If the destination address is multicast, broadcast, anycast, or gateway control plane address, the next hop is selected according to the tunnel ID of interface 1. .
  • the gateway forwarding plane function directly determines the next hop to be forwarded according to the destination IP address of the packet. For example, a packet sent to a server on the Internet determines the appropriate forwarding interface according to the IP address of the packet. It is sent out (where the gateway forwarding plane function may have multiple interfaces 3).
  • the gateway forwarding plane function determines the next hop according to the tunnel ID of interface 1, which is applicable to some special connections, such as VPN.
  • the IP connection established by the terminal is used for VPN
  • the IP connection is established in the terminal.
  • the request will carry a corresponding indication, and the type of the IP connection to be established is indicated by the Access Point Name (APN) in the mobile network.
  • APN Access Point Name
  • the tunnel ID and VPN tunnel of interface 1 are Association, all data from the specific tunnel of interface 1 is forwarded to the specified VPN tunnel.
  • the type of GTP-U is a signaling message, and the next hop is selected according to the tunnel ID of interface 1 for such a data packet.
  • the downstream forwarding rule table of the gateway forwarding plane function is shown in Table 2:
  • the gateway forwarding plane function can directly determine the next hop tunnel information according to the tunnel ID of the interface 2; or query the tunnel information of the interface 1 according to the destination IP in the packet; or combine the interface 3 The destination IP address of the tunnel IP and the packet is queried by the peer IP and the peer tunnel ID.
  • FIG. 4 is a flow chart of the first embodiment of the present invention.
  • a mobile network is taken as an example to describe a process of establishing a tunnel related to an IP connection between a gateway forwarding plane function and a gateway control plane function in the embodiment of the present invention, and a gateway control plane function is a gateway forwarding plane function configuration.
  • the forwarding rule table and the gateway forwarding plane function forward data according to the configuration of the gateway control plane function.
  • the eNB corresponds to the access point in FIG. 1, and the mobility management entity MME corresponds to the access control function in FIG.
  • the embodiment of the invention does not limit the naming of the access control function.
  • the access control function can be named by other names.
  • the functions completed by the access control function include: user access authentication, user mobility management, user IP connection establishment and management.
  • the gateway control plane function and the gateway forwarding plane function constitute a Serving Gateway (SGW, Serving Gateway) and a Packet Data Network Gateway (PGW) of the mobile gateway device in the 4G mobile network.
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • Figure 4 shows a flow chart in conjunction with the PGW and the SGW.
  • the PGW and the SGW may be separate. If the PGW and the SGW are deployed separately, the gateway control plane function in FIG. 4 corresponds to the control plane function of the PGW, and the gateway forwarding plane function corresponds to the PGW forwarding. Face function.
  • Step 101a The UE sends a PDN connection establishment request to the MME.
  • step 101b triggering the MME to establish a PDN connection in the process of the UE attaching to the network (Attach).
  • Step 102 The MME selects a gateway, and sends a session establishment request to the gateway control plane function corresponding to the gateway.
  • the MME may notify the gateway control plane function of the type of the PDN to be established, so that the gateway control plane function selects an appropriate gateway forwarding plane resource for the UE. If the IP address request sent by the UE is received in step 101a or step 101b, the MME also sends the IP address request of the UE to the gateway control plane function.
  • Step 103 The gateway control plane function selects a gateway forwarding plane function resource for the PDN connection to be established according to the PDN type and other information (such as the location information of the UE and the load information of the gateway forwarding plane function) received in step 102.
  • the gateway control plane function allocates the uplink tunnel information to the PDN connection to be established, including the IP address of the uplink tunnel and the TEID-U of the GTP-U tunnel.
  • the gateway control plane function also establishes the gateway control plane function to the gateway for the PDN connection.
  • the tunnel between the functions ie, the logical channel), which includes the tunnel ID of the gateway control plane function and the tunnel ID and tunnel IP corresponding to the tunnel IP and gateway forwarding plane functions.
  • the gateway control plane function assigns an IP address to the PDN connection to be established. If the IP address pool is not managed locally by the gateway control plane function, the gateway control plane function needs to obtain an IP address from the functional entity of the management IP address pool.
  • a commonly used method for obtaining an IP address is that the gateway control plane functions as a DHCP client (Client) to obtain an IP address from a DHCP server (Server).
  • the gateway control plane function generates a forwarding rule table corresponding to the PDN connection, and sends the forwarding rule table to the gateway forwarding plane function, so that the gateway forwarding plane function can forward data according to the forwarding rule table. See Table 1 and Table 2 for the contents of the forwarding rule table.
  • Step 104 The gateway forwarding plane function sends a configuration update response to the gateway control plane function.
  • Step 105 The gateway control plane function sends a session establishment response to the MME.
  • the gateway control plane function sends the uplink tunnel ID and the uplink tunnel IP to the gateway forwarding plane function. Send it to the MME. If the gateway control plane function assigns an IP address or an IPv6 prefix to the UE, the gateway control plane function also sends the IP address or IPv6 prefix assigned to the UE to the MME in the message.
  • Step 106 The MME requests the eNB to allocate radio resources for the newly established PDN connection.
  • the MME brings a Network Attached Server (NAS) message (such as a PDN connection setup response) to the UE.
  • NAS Network Attached Server
  • the MME sends the uplink tunnel ID and the tunnel IP of the gateway forwarding plane function to the eNB.
  • Step 107 The eNB initiates a radio resource control (RRC) reconfiguration process, configures radio resources required for the newly established PDN connection for the UE, and sends the NAS message carried by the MME to the UE.
  • RRC radio resource control
  • Step 108 The eNB sends a bearer allocation response to the MME.
  • the eNB sends the eNB downlink tunnel IP and tunnel ID assigned to the PDN connection to the MME.
  • Step 109 The UE sends a NAS message (such as completion of PDN connection establishment) to the MME.
  • a NAS message such as completion of PDN connection establishment
  • Step 110 The MME sends an update bearer request to the gateway control plane function, where the MME sends the downlink tunnel IP and the tunnel ID of the eNB to the gateway control plane function.
  • Step 111 The gateway control plane function updates the forwarding rule table, and sends an update configuration request to the gateway forwarding plane function, and updates the forwarding rule table of the gateway forwarding plane function.
  • Step 112 The gateway forwarding plane function sends an update configuration response to the gateway control plane function.
  • Step 113 The gateway control plane function sends an update bearer response to the MME.
  • Step 114 After the PDN connection is established, the UE initiates an IP address configuration process. If the UE uses the IPv6 stateless address autoconfiguration protocol to perform address configuration, the UE may send an RS message to the network.
  • Step 115 After receiving the RS message sent by the UE, the gateway forwarding plane function determines, according to the forwarding rule table, that the message is sent to the gateway control plane through the tunnel associated with the PDN connection of the UE.
  • Step 116 If the gateway control plane function receives the RS message of the UE, or the gateway control plane function determines to actively send the address broadcast to the UE, the gateway control plane function sends the RA message to the UE by using the gateway forwarding plane function.
  • the gateway control plane function determines the tunnel from which the data is sent to the gateway forwarding plane function according to the tunnel that receives the RS message or according to the ID of the UE.
  • Step 117 After receiving the RA message from the gateway control plane function, the gateway forwarding plane function receives the RA message.
  • the tunnel ID to the RA message determines from which tunnel the data is sent to the UE.
  • Figure 5 is a flow chart of a second embodiment of the present invention.
  • the UE obtains an IP address in DHCP mode.
  • the steps 201a to 213 in FIG. 5 are the same as the steps 101a to 113 in FIG. 4, and details are not described herein again.
  • Step 214 After the PDN connection is established, the UE initiates an IP address configuration process. If the UE is configured with the DHCPv4 mode, the UE sends a DHCP Discovery broadcast message. If the UE uses DHCPv6 to configure the address, the UE sends a DHCP Solicit message to the All_DHCP_Servers multicast address or the All_DHCP_Relay_Agents_and_Servers multicast address.
  • Step 215 After receiving the DHCP Discovery or DHCP Solicit message sent by the UE, the gateway forwarding plane function determines, according to the forwarding rule table, that the message is sent to the gateway control plane through the tunnel associated with the PDN connection of the UE. The gateway forwarding plane function sends a DHCP Discovery or DHCP Solicit message to the gateway control plane function through the associated tunnel.
  • Step 216 After receiving the DHCP Discovery or DHCP Solicit message, the gateway control plane function sends a response message DHCP Offer (corresponding to DHCPv4 mode) or DHCP advertisement (corresponding to DHCPv6 mode) to the UE through the gateway forwarding plane function.
  • the source address of the message is the gateway.
  • the IP address of the control plane function, and the DHCP server is set as the gateway control plane function.
  • the gateway control plane function sends DHCP messages to the gateway forwarding plane through the management tunnel.
  • Step 217 The gateway forwarding plane function receives the DHCP Offer or the DHCP Advertisement message, determines the next hop tunnel information according to the tunnel ID of the ingress port, and sends the message to the UE through the tunnel.
  • Step 218 The UE sends a DHCP (DHCPv4 or DHCPv6) Request message to the gateway control plane function through the gateway forwarding plane function.
  • DHCP DHCPv4 or DHCPv6
  • Step 219 After receiving the DHCP Request message, the gateway forwarding plane function determines that the destination address is the gateway control plane function, and the gateway forwarding plane function queries the forwarding rule table, and queries the next hop tunnel information according to the ingress port, and the DHCP Request message is sent. Encapsulated into the tunnel and sent to the gateway control plane function.
  • Step 220 The IP address assigned to the UE after the gateway control plane function receives the DHCP Request message.
  • the address and network configuration parameters are encapsulated into a DHCP Reply message, and the DHCP Reply message is sent to the gateway forwarding plane through the corresponding tunnel.
  • Step 221 After receiving the DHCP Reply message, the gateway forwarding plane function determines the next hop tunnel information according to the tunnel ID of the ingress port, and sends the foregoing message to the UE through the tunnel.
  • FIG. 6 is a flowchart of a UE disconnecting a PDN connection or a network detachment according to the first embodiment or the second embodiment of the present invention.
  • the tunnel between the gateway control plane function and the gateway forwarding plane function is removed.
  • Each step shown in Figure 6 is described in detail below:
  • Step 301a The UE sends a PDN connection disconnection request to the MME.
  • step 301b triggering the MME to disconnect the PDN during the process of the UE de-attaching from the network.
  • Step 302 The MME sends a session deletion request to the gateway control plane function of the PDN connection corresponding gateway.
  • Step 303 The gateway control plane function sends a configuration update request to the gateway forwarding plane function by using the SDN controller, and deletes the forwarding table related to the PDN from the gateway forwarding plane function.
  • Step 304 The gateway forwarding plane function sends a configuration update response to the gateway control plane function.
  • Step 305 The gateway control plane function sends a session deletion response to the MME.
  • Step 306 The MME requests the eNB to delete the radio resource corresponding to the PDN connection.
  • Step 307 The eNB initiates an RRC reconfiguration process, deletes the radio resource corresponding to the PDN connection, and sends the NAS message carried by the MME to the UE.
  • Step 308 The eNB sends a bearer deletion response to the MME.
  • Step 309 The UE sends a NAS message (for example, the PDN connection is disconnected) to the MME.
  • a NAS message for example, the PDN connection is disconnected
  • FIG. 7 is a flowchart of a UE entering an idle state (IDLE) according to a third embodiment of the present invention.
  • the gateway forwarding plane function and the tunnel serving the PDN bearer between the eNBs are released, and the downstream flow table corresponding to the PDN connection of the UE in the gateway forwarding plane function needs to be modified to point to the gateway control plane function.
  • the gateway forwarding plane function subsequently receives the downlink data of the UE, the gateway forwarding plane function sends the downlink data of the UE to the gateway control plane function, thereby triggering paging.
  • the gateway forwarding plane function caches data.
  • the gateway forwarding plane function sends the buffered data to the UE.
  • the UE enters the IDLE state to trigger the gateway control plane function to modify the flow table corresponding to the gateway forwarding plane function for the PDN connection of the UE, so that it can be cached. Data, and can send downlink data of the idle UE to the gateway control plane function.
  • Step 401 The eNB determines that the UE enters the IDLE state, and the eNB sends an S1 release request to the MME.
  • Step 402 The MME sends a modify bearer request to the gateway control plane function.
  • Step 403 The gateway control plane function modifies the downlink forwarding table of the gateway forwarding plane function by the SDN controller, so as to buffer the received downlink data of the UE, and send the received downlink data of the UE to the gateway control plane function.
  • the modified stream representation is as follows:
  • MATCH UE IP
  • ACTION Buffer (length, delay)
  • ENCAP_tunnel destination MAC
  • source IP gateway forwarding plane function IP
  • destination tunnel ID destination tunnel ID
  • Step 404 The gateway forwarding plane function sends a response to the gateway control plane function by using the SDN controller.
  • Step 405 The gateway control plane function sends a modify bearer response to the MME.
  • Step 406 Continue the subsequent S1 release process.
  • FIG. 8 is a flowchart of a process when a gateway forwarding plane function receives downlink data of a UE when the UE is in the IDLE state according to the third embodiment of the present invention. The following describes each step shown in Figure 8 as follows:
  • Step 501 The gateway forwarding plane function receives the downlink data packet of the UE.
  • Step 502 The gateway forwarding plane function searches the downlink forwarding table. According to the rules of the downlink forwarding table, the gateway forwarding plane function buffers the downlink data packet, and encapsulates the data and sends the data to the gateway control plane function.
  • Step 503 After receiving the downlink data packet of the UE, the gateway control plane function determines that the data packet is a downlink data packet of the UE according to the destination IP address and the tunnel in which the data packet is received, and the function of the gateway control plane determines to initiate the locating for the UE. Call process.
  • the gateway control plane function sends a paging request to the MME.
  • Step 504 The MME sends a paging request to the eNB.
  • Step 505 The eNB sends a paging message.
  • Step 506 The UE initiates a service request process after receiving the paging message.
  • Step 507 In the service request process, the MME sends a modify bearer request to the gateway control plane function.
  • Step 508 The gateway control plane function modifies the downlink forwarding table of the gateway forwarding plane function by using the SDN controller, deletes the buffer function in the downlink forwarding table corresponding to the UE, and points the downlink tunnel to the eNB.
  • the modified downlink forwarding indicates, for example, the following:
  • Step 509 The gateway forwarding plane function sends a response through the SDN controller.
  • Step 510 The gateway control plane function sends a modify bearer response to the MME.
  • Step 511 The downlink data is sent from the gateway forwarding plane function to the eNB, and then sent to the UE.
  • FIG. 9 is a flow chart of a fourth embodiment of the present invention.
  • the local control function/global control function corresponds to the access control function in FIG. 1
  • NB corresponds to the access point in FIG.
  • an access gateway controller AGW-C
  • an access gateway AGW
  • AGW access gateway
  • GGW-C global gateway controller
  • GGW global gateway
  • the AGW-C acts as the DHCP server or as the default gateway of the UE, and is responsible for assigning an IP address to the UE, but the IP address belongs to the GGW-C/GGW, and the GGW-C passes the control plane.
  • the signaling process sends the IP address assigned to the UE to the AGW-C.
  • a network element-level tunnel is established between the AGW and the GGW.
  • the IP data packet of the user is sent from the AGW to the GGW through the network element-level tunnel, and then sent by the GGW to the external PDN network.
  • a PDN-level tunnel is established between the AGW and the NB.
  • the AGW queries the downlink tunnel information according to the destination IP address of the data packet, and encapsulates the data packet into the corresponding tunnel and sends the data packet to the NB.
  • Step 601a The UE sends a PDN connection establishment request to the LCF/GCF.
  • step 601b triggering the LCF/GCF to establish a PDN connection in the process of attaching the UE to the network (Attach).
  • Step 602 The LCF/GCF selects the AGW-C and sends a session establishment request to the selected AGW-C.
  • the LCF/GCF may notify the AGW-C of the type of PDN to be established, so that the AGW-C selects an appropriate AGW for the UE. If the IP address request sent by the UE is received in step 601a or step 601b, the LCF/GCF also sends the IP address request of the UE to the AGW-C.
  • the AGW-C selects an AGW for the PDN connection to be established according to the received PDN type and other information (such as location information of the UE, load information of the AGW, etc.).
  • the AGW-C allocates the uplink tunnel information to the PDN connection to be established, including the IP address of the uplink tunnel and the TEID-U of the GTP-U tunnel.
  • the AGW-C also establishes a tunnel between the AGW-C and the AGW for the PDN connection.
  • the tunnel includes the tunnel ID of the AGW-C and the tunnel ID and tunnel IP corresponding to the tunnel IP and the AGW.
  • the AGW-C allocates the tunnel information between the AGW and the GGW. If the AGW and the GGW are network-level tunnels, the AGW-C configures the AGW IP address of the tunnel.
  • Step 603 The AGW-C sends a session establishment response to the LCF/GCF.
  • the AGW-C transmits the AGW tunnel information of the tunnel between the AGW and the GGW (such as the AGW tunnel IP address), and the AGW to the AGW of the NB tunnel.
  • the tunnel information is sent to the LCF/GCF.
  • Step 604 The LCF/GCF selects the GGW-C and sends a session establishment request to the GGW-C.
  • the LCF/GCF sends the APN requested by the UE and the AGW tunnel information of the tunnel between the AGW and the GGW obtained in step 603 to the GGW-C.
  • Step 605 The GGW-C allocates an IP address to the PDN connection to be established. If the IP address pool is not managed locally by the GGW-C, the GGW-C needs to obtain an IP address from the functional entity that manages the IP address pool.
  • a commonly used method for obtaining an IP address is that the GGW-C functions as a DHCP client to obtain an IP address from the DHCP server.
  • the GGW-C generates a forwarding rule table corresponding to the PDN connection, and sends the forwarding rule table to the GGW, so that the GGW can forward data according to the forwarding rule table.
  • a forwarding rule table corresponding to the PDN connection
  • IP address of the UE IP address of the AGW tunnel, IP of the GGW tunnel;
  • Upstream direction Destination IP address: Next hop.
  • Step 606 The GGW sends a configuration response to the GGW-C.
  • Step 607 The GGW-C sends a session establishment response to the LCF/GCF.
  • the GGW-C sends the IP address assigned to the UE, and the GGW tunnel information of the tunnel between the GGW and the AGW to the LCF/GCF.
  • Step 608 The LCF/GCF requests the NB to allocate radio resources for the newly established PDN connection.
  • the LCF/GCF brings the NAS message (such as the PDN connection setup response) to the UE.
  • the LCF/GCF sends the upstream tunnel ID and tunnel IP of the AGW to the NB.
  • Step 609 The NB initiates an RRC reconfiguration process, and configures, for the UE, the radio resources required for the newly established PDN connection, and sends the NAS message piggybacked by the LCF/GCF to the UE.
  • Step 610 The NB sends a bearer allocation response to the LCF/GCF.
  • the NB sends the NB downlink tunnel IP and tunnel ID assigned to the PDN connection to the LCF/GCF.
  • Step 611 The UE sends a NAS message (such as completion of PDN connection establishment) to the LCF/GCF.
  • Step 612 The LCF/GCF sends an update session request to the AGW-C, in which the LCF/GCF sends the downlink tunnel IP and tunnel ID of the NB to the AGW-C.
  • Step 613 The AGW-C generates a forwarding rule table for the PDN connection, and sends a configuration update request to the AGW to update the forwarding rule table of the AGW.
  • a forwarding rule table in the AGW see Table 1 and Table 2, for example.
  • Step 614 The AGW sends a configuration update response to the AGW-C.
  • Step 615 The AGW-C sends an update session response to the LCF/GCF.
  • a Per PDN forwarding plane tunnel is established between the UE and the AGW, and the tunnel is used to transmit IP data packets sent from the UE or sent to the UE.
  • the UE initiates an IP address configuration process.
  • Step 616 If the UE uses the IPv6 stateless address autoconfiguration protocol to perform address configuration, the UE sends an RS message to the network.
  • Step 617 After receiving the RS message sent by the UE, the AGW determines that the message needs to be sent to the AGW-C through the tunnel associated with the PDN connection of the UE according to the forwarding rule table.
  • Step 618 If the AGW-C receives the RS message of the UE, or the AGW-C decides to actively give the UE The address broadcast is sent, and the AGW-C sends an RA message to the UE through the AGW. The AGW-C decides from which tunnel to send data to the AGW according to the tunnel that receives the RS message or according to the ID of the UE.
  • Step 619 After receiving the RA message from the AGW-C, the AGW determines, according to the tunnel ID of the received RA message, which tunnel to send data to the UE.
  • Figure 10 is a flow chart of a fifth embodiment of the present invention.
  • the difference between the fifth embodiment shown in FIG. 10 and the fourth embodiment shown in FIG. 9 is that, in FIG. 10, the UE acquires an IP address by using a DHCP method.
  • the steps 701a-715 shown in FIG. 10 are the same as the steps 601a-615 in FIG. 9, and are not described herein again.
  • Step 716 After the PDN connection is established, the UE initiates an IP address configuration process. If the UE is configured with the DHCPv4 mode, the UE sends a DHCP Discovery broadcast message. If the UE uses DHCPv6 to configure the address, the UE sends a DHCP Solicit message to the All_DHCP_Servers multicast address or the All_DHCP_Relay_Agents_and_Servers multicast address.
  • Step 717 After receiving the DHCP Discovery or DHCP Solicit message sent by the UE, the AGW determines that the message needs to be sent to the AGW-C through the tunnel associated with the PDN connection of the UE according to the forwarding rule table. The AGW sends a DHCP Discovery or DHCP Solicit message to the AGW-C through the associated tunnel.
  • Step 718 After receiving the DHCP Discovery or DHCP Solicit message, the AGW-C sends a response message DHCP Offer (corresponding to DHCPv4 mode) or DHCP Advertisement (corresponding to DHCPv6 mode) to the UE.
  • the source address of the message is the IP address of the AGW-C.
  • the AGW-C sends the DHCP message to the AGW through the management tunnel.
  • Step 719 After receiving the DHCP Discovery or DHCP Solicit message, the AGW determines the next hop tunnel information according to the tunnel ID of the ingress port, and sends the message to the UE through the tunnel.
  • Step 720 The UE sends a DHCP Request message to the AGW-C, where the destination address of the data packet is the IP address of the AGW-C.
  • Step 721 The AGW receives the DHCP Request, determines that the destination address is the AGW-C, and the AGW queries the forwarding rule table, and queries the next hop tunnel information according to the ingress port, and encapsulates the DHCP Request message into the tunnel to send to the AGW-C.
  • Step 722 The IP address and network that the AGW-C will assign to the UE after receiving the DHCP request.
  • the configuration parameters are encapsulated into a DHCP Reply message, and the DHCP Reply message is sent to the AGW through the corresponding tunnel.
  • Step 723 After receiving the DHCP Reply message, the AGW determines the next hop tunnel information according to the tunnel ID of the ingress port, and sends the message to the UE through the tunnel.
  • FIG. 11 is a flowchart of a UE disconnecting a PDN connection or a network detachment according to a fourth embodiment or a fifth embodiment of the present invention.
  • the tunnel between the gateway control plane function and the gateway forwarding plane function is removed.
  • Each step shown in Figure 11 is described in detail below:
  • Step 801a The UE sends a PDN connection disconnect request to the LCF/GCF.
  • step 801b triggering the LCF/GCF to disconnect the PDN during the UE's de-attachment from the network.
  • Step 802 The LCF/GCF sends a session deletion request to the AGW-C corresponding to the PDN connection.
  • Step 803 The AGW-C sends an update configuration request to the AGW through the SDN controller, and deletes the forwarding table corresponding to the PDN connection.
  • Step 804 The AGW sends an update configuration response to the AGW-C.
  • Step 805 The AGW-C sends a session deletion response to the LCF/GCF.
  • Step 806 The LCF/GCF sends a session deletion request to the GGW-C corresponding to the PDN connection.
  • Step 807 If the forwarding rule table of the GGW needs to be updated, the GGW-C sends an update configuration request to the GGW, and deletes the forwarding rule table corresponding to the PDN connection.
  • Step 808 The GGW sends an update configuration response to the GGW-C.
  • Step 809 The GGW-C sends a session deletion response to the LCF/GCF.
  • Step 810 The LCF/GCF requests the NB to delete the radio resource corresponding to the PDN connection.
  • the LCF/GCF brings the NAS message (such as the PDN connection deletion response) to the UE.
  • Step 811 The NB initiates an RRC reconfiguration process, where the PDN connection related radio resource is deleted, and the NAS message piggybacked by the LCF/GCF is sent to the UE.
  • Step 812 The NB sends a bearer deletion response to the LCF/GCF.
  • Step 813 The UE sends a NAS message (for example, the PDN connection is disconnected) to the LCF/GCF.
  • a NAS message for example, the PDN connection is disconnected
  • FIG. 12 is a flow chart of a sixth embodiment of the present invention.
  • the eNB corresponds to the access point in FIG. 1
  • the MME corresponds to the access control function in FIG.
  • the eNB sends GTP-U control.
  • the message is sent to the gateway control plane function, and the gateway control plane function processes the GTP-U control message.
  • the steps 901a to 913 shown in FIG. 12 are the same as the steps 101a to 113 in FIG. 4, and details are not described herein again. Steps 914 to 917 in FIG. 12 are described in detail below:
  • Step 914 The eNB sends a GTP-U control message to the gateway forwarding plane function.
  • the GTP-U control message may include an ECHO (Response), an ECHO response, an Error Indication, an End Mark, and the like.
  • Step 915 The gateway forwarding plane function searches for the tunnel IP address and port number of the gateway control plane function corresponding to the port and the local tunnel IP address corresponding to the egress port according to the destination port number of the received GTP-U control packet.
  • the gateway forwarding plane function re-encapsulates the received GTP-U control packet by the outbound port information and sends it to the gateway control plane.
  • Step 916 The gateway control plane function sends a GTP-U control packet to the gateway forwarding plane function.
  • the GTP-U control message may include an ECHO, an Error Indication, an End Mark, and the like.
  • Step 917 The gateway forwarding plane function queries the tunnel IP address and port number of the eNB corresponding to the port and the local tunnel IP address corresponding to the egress port according to the destination port number of the received GTP-U control packet.
  • the gateway forwarding plane function re-encapsulates the received GTP-U control packet by the outbound port information and sends the packet to the eNB.
  • FIG. 13 is a flowchart of a UE entering an IDLE state according to a seventh embodiment of the present invention.
  • the tunnel serving the PDN bearer between the AGW and the NB is released, and the downstream table corresponding to the PDN connection of the UE in the AGW needs to be modified to point to the AGW-C.
  • the AGW subsequently receives the downlink data of the UE, the AGW sends the downlink data of the UE to the AGW-C, thereby triggering the paging.
  • the AGW buffers the data.
  • the AGW sends the buffered data to the UE.
  • FIG. 13 is a flowchart of a UE entering an IDLE state according to a seventh embodiment of the present invention.
  • the UE enters the IDLE state to trigger the AGW-C to modify the flow table corresponding to the AGW for the PDN connection of the UE, so that it can buffer the data, and can send the downlink data of the UE in the idle state to the AGW-C.
  • Step 1001 The NB determines that the UE enters the IDLE state, and the NB sends a UE context release request to the LCF/GCF.
  • Step 1002 The LCF/GCF sends an update session request to the AGW-C.
  • Step 1003 The AGW-C modifies the downlink forwarding table of the AGW by using the SDN controller, and then buffers the received downlink data of the UE, and sends the received downlink data of the UE to the AGW-C.
  • the modified stream representation is as follows:
  • Step 1004 The AGW sends a response to the AGW-C through the SDN controller.
  • Step 1005 The AGW-C sends a modification session response to the LCF/GCF.
  • Step 1006 Continue the subsequent UE context release process.
  • FIG. 14 is a flowchart of processing when the AGW receives downlink data of the UE when the UE is in an idle state according to the seventh embodiment of the present invention. Each step shown in Figure 14 is described below:
  • Step 1101 The AGW receives the downlink data packet of the UE, and the data packet may be from the GGW or directly from the external network.
  • Step 1102 The AGW searches for the downlink forwarding table. According to the rule of the found downlink forwarding table, the AGW buffers the downlink data packet, and encapsulates the data packet and sends the data packet to the AGW-C.
  • Step 1103 After receiving the downlink data packet of the UE, the AGW-C determines that the data packet is a downlink data packet of the UE according to the destination IP address and the tunnel in which the data packet is received, and the AGW-C determines to initiate a paging procedure for the UE. .
  • the AGW-C sends a paging request to the LCF/GCF.
  • Step 1104 The LCF/GCF sends a paging request to the NB.
  • Step 1105 The NB sends a paging message.
  • Step 1106 The UE initiates a service request process after receiving the paging message.
  • Step 1107 In the service request process, the LCF/GCF sends a modify bearer request to the AGW-C.
  • Step 1108 The AGW-C modifies the downlink forwarding table of the AGW through the SDN controller, deletes the cache function in the downlink forwarding table corresponding to the UE, and points the downlink tunnel to the NB.
  • the modified downlink forwarding indicates, for example, the following:
  • Step 1109 The AGW sends a response to the AGW-C through the SDN controller.
  • Step 1110 The AGW-C sends a modified session response to the LCF/GCF.
  • Step 1111 The downlink data is sent from the GGW/AGW to the NB, and then sent to the UE.
  • the access between the access point and the gateway forwarding plane function is tunneled, and the GTP-U tunnel mode is specifically described.
  • the embodiments of the present invention are not limited thereto.
  • the logical link between the access point and the gateway forwarding plane function may also take other forms as long as the logical link can identify different IP connections.
  • methods for distinguishing different IP connections by other means are not described herein again, and those skilled in the art can make corresponding changes as needed.
  • the embodiment of the present invention further provides a processing system for controlling a message in a gateway based on an SDN, which is disposed on a gateway control plane function, and includes a first processing module, configured to: between a gateway forwarding plane function and a gateway control plane function.
  • a logical channel is established for each IP connection, wherein the logical channel is configured to forward a control message related to the IP connection between a gateway forwarding plane function and a gateway control plane function.
  • control message includes:
  • IP connection-related GPRS channel protocol-user plane GTP-U control message The IP connection-related GPRS channel protocol-user plane GTP-U control message.
  • IP connection-related data packet that triggers paging.
  • the processing system further includes a second processing module, configured to: set, by the SDN controller, a forwarding rule table of the control packet for the gateway forwarding plane function.
  • the forwarding rule table includes at least a rule and an action, where the rule is used to identify the control packet related to the IP connection, and the rule includes:
  • the GTP-U packet type of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the GTP-U destination tunnel ID of the GTP-U packet received by the gateway forwarding plane function and/or,
  • the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function are the source IP address and/or destination IP address of the user data packet received by the gateway forwarding plane function.
  • the type of user data packet received by the gateway forwarding plane function including the protocol type and UDP or TCP port number or ICMP type.
  • the user data packet is an IP data packet encapsulated in a tunnel whose tunnel destination is a function of a gateway forwarding plane or an IP data packet without tunnel encapsulation;
  • the action is used to process the GTP-U data packet or the user data packet received by the gateway forwarding plane function, and the action includes: encapsulating the data packet received by the gateway forwarding plane function into the gateway forwarding plane function and the gateway control plane.
  • the gateway control plane function is sent in the logical channel between functions.
  • the action may further include tunnel information of the gateway control plane function and local tunnel information of the gateway forwarding plane function.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • a dedicated logical channel is established for each IP connection between the gateway forwarding plane function and the gateway control plane function, and the dedicated logical channel is used to forward control packets between the gateway forwarding plane function and the gateway control plane function. That is, the control message in all the data received from an IP connection is directed to the dedicated logical channel, so that the gateway forwarding plane function forwards the control message to the gateway control plane function through the dedicated logical channel.
  • the dedicated logical channel In this way, the conflict of the identifier information used in the IP control packet in the related art is avoided by using the dedicated logical channel, thereby avoiding the problem that the gateway control plane function and the gateway forwarding plane function cannot correctly match the control packet to the user.
  • the SDN controller is prevented from forwarding a large number of control messages, ensuring the performance of the SDN controller.

Landscapes

  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé et un système de traitement pour un paquet de commande dans une passerelle basée sur un réseau défini par logiciel (SDN). Le procédé consiste à : établir un canal logique pour chaque connexion IP entre une fonction de plan de transfert de passerelle et une fonction de plan de commande de passerelle, le canal logique étant utilisé pour transférer un paquet de commande associé à la connexion IP entre la fonction de plan de transfert de passerelle et la fonction de plan de commande de passerelle.
PCT/CN2015/091137 2015-03-23 2015-09-29 Procédé et système de traitement pour un paquet de commande dans une passerelle basée sur un réseau défini par logiciel (sdn) Ceased WO2016150140A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510130677.1 2015-03-23
CN201510130677.1A CN106161289A (zh) 2015-03-23 2015-03-23 一种基于sdn的网关中控制报文的处理方法及系统

Publications (1)

Publication Number Publication Date
WO2016150140A1 true WO2016150140A1 (fr) 2016-09-29

Family

ID=56976968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/091137 Ceased WO2016150140A1 (fr) 2015-03-23 2015-09-29 Procédé et système de traitement pour un paquet de commande dans une passerelle basée sur un réseau défini par logiciel (sdn)

Country Status (2)

Country Link
CN (1) CN106161289A (fr)
WO (1) WO2016150140A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109417575A (zh) * 2016-09-30 2019-03-01 华为技术有限公司 一种ip地址分配方法及装置
CN110224942A (zh) * 2018-03-01 2019-09-10 中兴通讯股份有限公司 一种报文处理方法、装置及存储介质
CN113056038A (zh) * 2016-11-04 2021-06-29 华为技术有限公司 删除用户面隧道的方法、网元及系统
US11115350B2 (en) * 2012-06-29 2021-09-07 Huawei Technologies Co., Ltd. Method for processing information, forwarding plane device and control plane device
CN115550109A (zh) * 2021-06-29 2022-12-30 中国移动通信集团重庆有限公司 数据传输的方法、网关、第一业务交换机、设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018103108A1 (fr) * 2016-12-10 2018-06-14 华为技术有限公司 Procédé et dispositif de routage pour un message de données
CN108462594B (zh) * 2017-02-21 2022-03-04 阿里巴巴集团控股有限公司 虚拟专有网络及规则表生成方法、装置及路由方法
CN108989194B (zh) * 2017-05-31 2021-07-09 微软技术许可有限责任公司 分布式IPSec网关
CN109842540B (zh) * 2017-11-28 2022-10-11 上海仪电（集团）有限公司中央研究院 一种基于软件定义网络的二层组播网络互通装置和方法
CN109246025B (zh) * 2018-08-09 2022-02-01 烽火通信科技股份有限公司 基于网络介质的流量控制系统及方法
CN111130816B (zh) * 2019-12-27 2022-06-24 北京东土军悦科技有限公司 一种报文转发处理设备、方法、装置和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103067534A (zh) * 2012-12-26 2013-04-24 中兴通讯股份有限公司 一种NAT实现系统、方法及Openflow交换机
CN103391296A (zh) * 2013-07-29 2013-11-13 北京华为数字技术有限公司 一种控制器、转发器及通道建立方法和系统
WO2014000266A1 (fr) * 2012-06-29 2014-01-03 华为技术有限公司 Procédé de traitement d'informations, appareil de plan de transfert et appareil de plan de commande
CN103975625A (zh) * 2012-06-30 2014-08-06 华为技术有限公司 一种控制和转发解耦架构下的转发面隧道资源的管理方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101175326B (zh) * 2004-12-30 2010-07-07 华为技术有限公司 保证业务QoS的宽带接入网络
CN101242366B (zh) * 2008-02-28 2012-04-18 华为技术有限公司 一种路由器及路由器内管理控制的方法
CN104243299B (zh) * 2013-06-14 2019-07-02 中兴通讯股份有限公司 一种隧道处理方法及系统、控制面设备、转发面设备
CN104301251B (zh) * 2014-09-22 2018-04-27 新华三技术有限公司 一种QoS处理方法、系统及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014000266A1 (fr) * 2012-06-29 2014-01-03 华为技术有限公司 Procédé de traitement d'informations, appareil de plan de transfert et appareil de plan de commande
CN103975625A (zh) * 2012-06-30 2014-08-06 华为技术有限公司 一种控制和转发解耦架构下的转发面隧道资源的管理方法
CN103067534A (zh) * 2012-12-26 2013-04-24 中兴通讯股份有限公司 一种NAT实现系统、方法及Openflow交换机
CN103391296A (zh) * 2013-07-29 2013-11-13 北京华为数字技术有限公司 一种控制器、转发器及通道建立方法和系统

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11115350B2 (en) * 2012-06-29 2021-09-07 Huawei Technologies Co., Ltd. Method for processing information, forwarding plane device and control plane device
CN109417575A (zh) * 2016-09-30 2019-03-01 华为技术有限公司 一种ip地址分配方法及装置
EP3496374A4 (fr) * 2016-09-30 2019-07-17 Huawei Technologies Co., Ltd. Procédé et dispositif d'attribution d'adresse ip
CN113056038A (zh) * 2016-11-04 2021-06-29 华为技术有限公司 删除用户面隧道的方法、网元及系统
CN113056038B (zh) * 2016-11-04 2023-05-16 华为技术有限公司 删除用户面隧道的方法、网元及系统
CN110224942A (zh) * 2018-03-01 2019-09-10 中兴通讯股份有限公司 一种报文处理方法、装置及存储介质
CN110224942B (zh) * 2018-03-01 2023-08-04 中兴通讯股份有限公司 一种报文处理方法、装置及存储介质
CN115550109A (zh) * 2021-06-29 2022-12-30 中国移动通信集团重庆有限公司 数据传输的方法、网关、第一业务交换机、设备

Also Published As

Publication number Publication date
CN106161289A (zh) 2016-11-23

Similar Documents

Publication Publication Date Title
US12245104B2 (en) Multicast service transmission method and device
US11690110B2 (en) Time sensitive network bridge configuration
WO2016150140A1 (fr) Procédé et système de traitement pour un paquet de commande dans une passerelle basée sur un réseau défini par logiciel (sdn)
US8514756B1 (en) Collectively addressing wireless devices
US8520615B2 (en) Breakout gateway for mobile data traffic
US20130007286A1 (en) User session routing between mobile network gateways
JP6489019B2 (ja) 通信システム、通信装置および通信制御方法
KR102126223B1 (ko) 이동통신 코어 망에서의 시그널링 방법 및 그 시스템
WO2011050678A1 (fr) Réseau de communication mis en oeuvre selon une architecture de réseau à séparation du plan de commande et du plan de transport
CN105874756B (zh) 控制信令的传输方法及设备
RU2676533C1 (ru) Способ и устройство назначения ip-адреса
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
JP2020537457A (ja) 通信システムにおけるデータ・ルーティング
US9668176B2 (en) Method for selecting shunt gateway and controller
CN108271433B (zh) 一种数据报文处理方法及控制面网元、用户面网元
CN116233953A (zh) 数据传输方法、装置、设备及存储介质
JP2014531780A (ja) 通信端末、通信方法、通信システムおよびプログラム
WO2012051892A1 (fr) Procédé et système pour la commande de routage de données
WO2011050663A1 (fr) Procédé et système de mise à jour de tunnel dans un système de communication prenant en charge un accès sous protocole internet (ip) local
WO2012088828A1 (fr) Procédé, système et routeur de passerelle d'accès pour maintenance de table
CN103004151A (zh) 本地路由的检测、建立方法、装置以及系统
EP3694252B1 (fr) Procédé et dispositif de commutation de cellule
TWI441549B (zh) 行動通訊網路中本地路由的系統與方法
WO2012130118A1 (fr) Procédé et système de détachement d'utilisateur
KR20150001452A (ko) 분산형 네트워크에서 데이터 패킷 경로 최적화 방법 및 장치

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

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

Country of ref document: EP

Kind code of ref document: A1