WO2014071605A1 - 处理报文的方法、转发面装置及网络设备 - Google Patents

处理报文的方法、转发面装置及网络设备 Download PDF

Info

Publication number
WO2014071605A1
WO2014071605A1 PCT/CN2012/084368 CN2012084368W WO2014071605A1 WO 2014071605 A1 WO2014071605 A1 WO 2014071605A1 CN 2012084368 W CN2012084368 W CN 2012084368W WO 2014071605 A1 WO2014071605 A1 WO 2014071605A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
packet
identifier
user
forwarding
Prior art date
Application number
PCT/CN2012/084368
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 CN201280002721.5A priority Critical patent/CN104040966B/zh
Priority to EP12888170.3A priority patent/EP2908480B1/en
Priority to PCT/CN2012/084368 priority patent/WO2014071605A1/zh
Publication of WO2014071605A1 publication Critical patent/WO2014071605A1/zh
Priority to US14/707,752 priority patent/US10044574B2/en
Priority to US16/042,710 priority patent/US10771356B2/en
Priority to US16/984,731 priority patent/US11552863B2/en
Priority to US18/146,777 priority patent/US11902116B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5077Network service management, e.g. ensuring proper service fulfilment according to agreements wherein the managed service relates to simple transport services, i.e. providing only network infrastructure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34Signalling channels for network management communication
    • H04L41/342Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • H04L45/745Address table lookup; Address filtering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0227Filtering policies
    • H04L63/0263Rule management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/38Flow based routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/64Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • the present invention relates to network technologies, and in particular, to a method for processing a message, a forwarding plane device, and a network device. Background technique
  • a controller can generate a forwarding table and send the forwarding table to a broadband remote access server (BRAS) or a service router (SR).
  • BRAS broadband remote access server
  • SR service router
  • the BRAS or SR may forward the received message according to the forwarding table.
  • the prior art management of the business is not flexible enough.
  • the embodiments of the present invention provide a method, an apparatus, a forwarding plane device, and a network device for processing a message, which are used to improve flexibility in managing a service.
  • the first aspect provides a method for processing a packet, including: a forwarding plane device receiving a first packet sent by a user, where the first packet includes an identifier of the user, and the forwarding plane device includes a forwarding Publish
  • the forwarding plane device determines the identifier of the service according to the correspondence between the identifier of the user and the identifier of the service, and the identifier of the user in the first packet.
  • the forwarding plane device encapsulates the identifier of the service in the first packet to generate a second packet; the forwarding plane device sends the second packet to a network device, where the second packet is used And causing the network device to manage the service according to the identifier of the service in the second packet.
  • the managing, by the network device, the service according to the identifier of the service in the second packet includes:
  • the network device performs operations corresponding to the service on the second packet according to the identifier of the service in the second packet, where the network device is a first server capable of executing the service; or
  • the network device forwards the second packet to the second server capable of performing the service according to the identifier of the service in the second packet; or
  • the network device generates a forwarding table entry according to the identifier of the service in the second packet, and sends the forwarding table entry to the forwarding plane device, where the matching domain in the forwarding table entry includes An identifier of the user, the forwarding table entry is configured to enable the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry, and generate an updated forwarding table, where
  • the forwarding plane device is capable of performing an operation corresponding to the service on the packet including the identifier of the user according to the updated forwarding table, where the network device is a control plane device corresponding to the forwarding plane device.
  • the method further includes:
  • the forwarding plane device performs a user management operation on the user according to the identifier of the user in the first packet.
  • a method for processing a message including:
  • the forwarding plane device receives the first packet sent by the user, where the first packet includes the identifier of the user, and the forwarding plane device includes a forwarding table.
  • the forwarding plane device forwards the first packet to the network device, where the first packet is used to enable the network device to perform a correspondence between the identifier of the user and the identifier of the service, and the first packet.
  • the identifier of the user determines an identifier of the service, and manages the service according to the identifier of the service.
  • the managing the service according to the identifier of the service includes:
  • the network device performs operations corresponding to the service on the first packet according to the identifier of the service, where the network device is a first server capable of executing the service; or
  • the network device encapsulates the identifier of the service with the first packet to generate a second packet
  • the network device generates a forwarding table entry according to the identifier of the service, and sends the forwarding table entry to the forwarding plane device, where the matching domain in the forwarding table entry includes the identifier of the user, and the forwarding a publishing entry for causing the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry and generate an updated forwarding table, wherein the forwarding plane device is capable of updating according to the
  • the subsequent forwarding table performs operations corresponding to the service on the packet including the identifier of the user, and the network device is a control plane device corresponding to the forwarding plane device.
  • the method further includes: The forwarding plane device performs a user management operation on the user according to the identifier of the user in the first packet.
  • a method for processing a message including:
  • the forwarding plane device Receiving, by the network device, the second packet sent by the forwarding plane device, where the second packet is obtained by: the forwarding plane device receiving the first packet sent by the user, where the first packet includes the user Identifying, the forwarding plane device includes a forwarding table;
  • the forwarding plane device encapsulates the identifier of the service in the first packet, and generates the second packet.
  • the network device manages the service according to the identifier of the service in the second packet.
  • the managing, by the network device, the service according to the identifier of the service in the second packet includes:
  • the network device performs operations corresponding to the service on the second packet according to the identifier of the service in the second packet, where the network device is a first server capable of executing the service; or
  • the network device forwards the second packet to a second server capable of performing the service according to the identifier of the service in the second packet;
  • the network device generates a forwarding table entry according to the identifier of the service in the second packet, and sends the forwarding table entry to the forwarding plane device, where the matching domain in the forwarding table entry includes An identifier of the user, the forwarding table entry is configured to enable the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry, and generate an updated forwarding table, where The forwarding plane device can perform the operation corresponding to the service on the packet including the identifier of the user according to the updated forwarding table, where the network device is a control plane device corresponding to the forwarding plane device.
  • a method for processing a message including:
  • the forwarding device Receiving, by the network device, the first packet that is forwarded by the forwarding device, where the first packet is obtained by: the forwarding device receiving the first packet sent by the user, where the first packet includes the The identifier of the user, where the forwarding plane device includes a forwarding table;
  • the network device Determining, by the network device, an identifier of the service according to a correspondence between the identifier of the user and an identifier of the service, and an identifier of the user in the first packet;
  • the network device manages the service according to the identifier of the service.
  • the managing, by the network device, the service according to the identifier of the service includes:
  • the network device performs operations corresponding to the service on the first packet according to the identifier of the service, where the network device is a first server capable of executing the service; or
  • the network device encapsulates the identifier of the service with the first packet to generate a second packet
  • the network device generates a forwarding table entry according to the identifier of the service, and sends the forwarding table entry to the forwarding plane device, where the matching domain in the forwarding table entry includes the identifier of the user, and the forwarding a publishing entry for causing the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry and generate an updated forwarding table, wherein the forwarding plane device is capable of updating according to the
  • the subsequent forwarding table performs an operation corresponding to the service on the packet including the identifier of the user, where the network device is a control plane device corresponding to the forwarding plane device.
  • a forwarding plane device including:
  • a receiving unit configured to receive a first packet sent by a user, where the first packet includes an identifier of the user, and the forwarding plane device includes a forwarding table;
  • a determining unit configured to determine an identifier of the service according to a correspondence between the identifier of the user and an identifier of the service, and an identifier of the user in the first packet received by the receiving unit;
  • a generating unit configured to encapsulate, in the first packet, an identifier of the service determined by the determining unit, to generate a second packet
  • a sending unit configured to send, by the network device, the second packet generated by the generating unit, where the second packet is used to enable the network device to manage according to the identifier of the service in the second packet The business.
  • the method includes:
  • an operation unit configured to perform a user management operation on the user according to the identifier of the user in the first packet received by the receiving unit.
  • a forwarding plane device including:
  • a receiving unit configured to receive a packet sent by a user, where the packet includes an identifier of the user, where the forwarding plane device includes a forwarding table;
  • a forwarding unit configured to forward, to the network device, the packet that is received by the receiving unit, where the packet is used to enable the network device to perform a correspondence between the identifier of the user and an identifier of the service, and the packet Said
  • the identity of the user determines an identity of the service, and manages the service according to the identity of the service.
  • the method further includes:
  • an operation unit configured to perform a user management operation on the user according to the identifier of the user in the packet received by the receiving unit.
  • a network device including:
  • a receiving unit configured to receive a second packet sent by the forwarding plane device, where the second packet is obtained by:
  • the forwarding plane device receives the first packet sent by the user, where the first packet includes the identifier of the user, and the forwarding plane device includes a forwarding table.
  • the forwarding plane device determines the identifier of the service according to the correspondence between the identifier of the user and the identifier of the service, and the identifier of the user in the first packet, and encapsulates the identifier in the first packet. Defining the identifier of the service, and obtaining the second packet;
  • a management unit configured to manage the service according to the identifier of the service in the second packet.
  • the management unit is configured to perform an operation corresponding to the service on the second packet according to the identifier of the service in the second packet, where
  • the network device is a first server capable of performing the service;
  • the management unit is configured to forward the second packet to a second server capable of performing the service according to the identifier of the service in the second packet;
  • the management unit is configured to generate a forwarding table entry according to the identifier of the service in the second packet, and send the forwarding table entry to the forwarding plane device, where the matching domain in the forwarding table entry Including the identifier of the user, the forwarding table entry is used to enable the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry, and generate an updated forwarding table.
  • the forwarding plane device can perform an operation corresponding to the service on the packet including the identifier of the user according to the updated forwarding table, where the network device is a control plane device corresponding to the forwarding plane device.
  • a network device including:
  • the receiving unit is configured to receive the first packet forwarded by the forwarding plane device, where the first packet is obtained by:
  • the forwarding plane device receives the first packet sent by the user, where the first packet includes the identifier of the user, and the forwarding plane device includes a forwarding table.
  • a determining unit configured to determine an identifier of the service according to a correspondence between the identifier of the user and an identifier of the service, and an identifier of the user in the first packet;
  • a management unit configured to manage the service according to the identifier of the service determined by the determining unit.
  • the management unit is configured to perform an operation corresponding to the service on the packet according to the identifier of the service, where the network device is capable of performing the service.
  • the management unit is specifically configured to encapsulate the identifier of the service with the first packet to generate a second packet;
  • the management unit is configured to generate a forwarding table entry according to the identifier of the service, and send the forwarding table entry to the forwarding plane device, where a matching domain in the forwarding table entry includes an identifier of the user,
  • the forwarding table entry is configured to enable the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry and generate an updated forwarding table, where the forwarding plane device can be configured according to the forwarding table
  • the updated forwarding table performs operations corresponding to the service on the packet including the identifier of the user, where the network device is a control plane device corresponding to the forwarding plane device.
  • the forwarding plane device encapsulates the first packet to generate a second packet.
  • the second message contains the identifier of the service.
  • the forwarding plane device forwards the second packet to the network device, so that the network device can manage the service according to the identifier of the service in the second packet.
  • FIG. 1 is a flowchart of a method for processing a message according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for processing a message according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a forwarding plane device according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a forwarding plane device according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a forwarding plane device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a forwarding plane device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a network device according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of a network device according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 11 is a flowchart of a method for processing a message according to an embodiment of the present invention.
  • FIG. 12 is a flowchart of a method for processing a message according to an embodiment of the present invention.
  • FIG. 13 is a flowchart of a method for processing a message according to an embodiment of the present invention.
  • FIG. 14 is a schematic diagram of an application example of a method for processing a packet according to an embodiment of the present disclosure
  • FIG. 15 is a schematic diagram of an application example of a method for processing a packet according to an embodiment of the present disclosure
  • FIG. 16 is a schematic diagram of an application example of a method for processing a message according to an embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • FIG. 1 is a flowchart of a method for processing a message according to an embodiment of the present invention. Referring to Figure 1, the method includes:
  • the forwarding plane device receives the first packet sent by the user, where the first packet includes the identifier of the user, and the forwarding plane device includes a forwarding table.
  • the forwarding plane device is a device for forwarding traffic.
  • the forwarding plane device may be a broadband remote access server (BRAS).
  • the user may be a device located in a local area network.
  • the user may be a personal computer located on a home network.
  • the personal computer can access the Internet (Internet) through Point-to-Point Protocol over Ethernet (PPPoE).
  • the first packet may be an Internet Protocol (IP) message.
  • IPv4 Internet Protocol version 4
  • IPv6 Internet Protocol version 6, IPv6.
  • IPv6 Internet Protocol version 6
  • the identifier of the user may be a media access control (Media Access Control) protocol address of the user, or may be an Internet Protocol address of the user.
  • the identifier of the user may also be a combination of the MAC protocol address of the user and the virtual local area network (VLAN) identifier of the user.
  • the forwarding table may be a flow table or a packet forwarding table.
  • the forwarding plane device can have two forwarding modes, one is a stream forwarding mode, and the other is a packet forwarding mode.
  • Flow forwarding means that the forwarding plane device forwards the packet according to the flow table.
  • the number of fields used to determine whether a packet matches the entry of the flow table in one entry of the flow table is two or more.
  • the number of fields used in an entry of the flow table to determine whether the packet matches the entry of the flow table may be five.
  • the five fields can be an Internet Protocol address, a destination IP address, a source port (Port), a destination port, and a protocol (PiOt 0C0 l).
  • the field used to determine whether the packet matches the entry of the flow table may be in the open system interconnection model.
  • the field of the Data Link layer of the Open Systems Interconnection model can also be the field of the IP layer of the OSI model.
  • Packet forwarding means that the forwarding plane device forwards the packet according to the packet forwarding table.
  • the number of fields used in an entry in the packet forwarding table to determine whether the packet matches the entry of the packet forwarding table is one.
  • the field in the packet forwarding table used to determine whether the packet matches the entry of the packet forwarding table may be a destination IP address or a destination MAC protocol address.
  • the packet forwarding table may be a MAC table or a routing table.
  • the forwarding plane device can be a switch or a router.
  • the forwarding plane device may be an OpenFlow switch (OpenFlow)
  • OpenFlow Switch For the OpenFlow Switch, refer to the OpenFlow Switch Specification 1.0 (OpenFlow Switch Specification 1.0) published by the Open Networking Foundation (ONF) of the Standard Setting Organization (SSO).
  • ONF Open Networking Foundation
  • SSO Standard Setting Organization
  • the forwarding plane device determines the identifier of the service according to the correspondence between the identifier of the user and the identifier of the service, and the identifier of the user in the first packet.
  • the service refers to processing the received message according to the field in the received message.
  • the field in the message may be the information of the second layer to the seventh layer defined by the OSI model.
  • the service may be a network address translation (NAT) service, a carrier grade network address translation (CGN) service, an internet protocol security (IPSEC) service, and a video service.
  • NAT network address translation
  • CGN carrier grade network address translation
  • IPSEC internet protocol security
  • video service may be a network address translation (NAT) service, a carrier grade network address translation (CGN) service, an internet protocol security (IPSEC) service, and a video service.
  • firewall business uniform resource locator (Uniform / Universal Resource Locator, URL) Filters traffic, peer-to-peer (P2P) traffic visualization services.
  • the video service may be Frame Relay (FR), Resolution Enhancement Technology (RET), Multiple Document Interface (MDI), or Content Delivery Network (CDN).
  • FR Frame Relay
  • RET Resolution Enhancement Technology
  • MDI Multiple Document Interface
  • CDN Content Delivery Network
  • the service may be a forwarding service or a committed access rate (committed access rate,
  • the forwarding service may be a Layer 2 forwarding service, a Layer 3 forwarding service, a multiprotocol label switching (MPLS) forwarding service, or a virtual private network (VPN) forwarding service.
  • MPLS multiprotocol label switching
  • VPN virtual private network
  • the correspondence may be saved in an authentication, authorization, and accounting (AAA) server.
  • AAA authentication, authorization, and accounting
  • the forwarding plane device may obtain the correspondence from the AAA server.
  • the forwarding plane device may obtain the corresponding relationship from the AAA server by using a Remote Authentication Dial In User Service (Radius) protocol.
  • Radius Remote Authentication Dial In User Service
  • the identifier of the service is used to identify the service.
  • the forwarding plane device encapsulates the identifier of the service in the first packet to generate a second packet, where the second packet includes an identifier of the service.
  • the identifier of the service may be carried in the payload of the second packet, or may be carried in the packet header of the second packet.
  • the forwarding plane device forwards the second packet to the network device, where the second packet is used to enable the network device to manage the service according to the identifier of the service in the second packet.
  • the network device may be a control plane device corresponding to the forwarding plane device.
  • the network device may also be a device for forwarding traffic.
  • the network device can be a router.
  • the network device may also be a service server capable of processing the service.
  • the forwarding plane device encapsulates the first packet to generate the second packet.
  • the second packet includes an identifier of the service.
  • the forwarding plane device forwards the second packet to the network device, so that the network device can manage the service according to the identifier of the service in the second packet.
  • the network device that manages the service according to the identifier of the service in the second packet may include: the network device according to the second packet The identifier of the service performs the foregoing on the second packet The operation corresponding to the service, the network device is a first server capable of executing the service.
  • the first server may be a CGN device.
  • the service is a committed access rate (CAR) service
  • the first server may be a router capable of performing operations corresponding to the CAR service.
  • CAR committed access rate
  • the first server may be a switch capable of performing operations corresponding to the video enhanced service.
  • the network device that manages the service according to the identifier of the service in the second packet may include:
  • the network device forwards the second packet to the second server that can perform the service according to the identifier of the service in the second packet.
  • the network device is a device capable of forwarding traffic.
  • the network device can be a router.
  • the network device may also be a neighbor forwarding plane device of the forwarding plane device.
  • the network device can be a control plane device or a neighbor control plane device of the control plane device.
  • the network device manages the service according to the identifier of the service in the second packet, including:
  • the network device generates a forwarding entry according to the identifier of the service in the second packet, and sends the forwarding entry to the forwarding plane device, where the matching domain in the forwarding entry includes the user
  • the forwarding table item is configured to enable the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding entry and generate an updated forwarding table, where the forwarding plane device can be configured according to the forwarding table And the updated forwarding table performs an operation corresponding to the service on the packet that includes the identifier of the user, where the network device is a control plane device corresponding to the forwarding plane device.
  • the service may be a forwarding service.
  • the network device can be a control plane device.
  • the network device may be an OpenFlow Controller.
  • OpenFlow Controller For the open flow controller, please refer to the Open Flow Exchanger Specification Version 1.0 released by ONF.
  • the forwarding plane device can communicate with the network device through a control channel.
  • the control channel may be a secure channel (Secure Channel) in which the open flow switch interacts with the open flow controller.
  • Secure Channel Secure Channel
  • the security channel refer to the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the method may further include: the forwarding plane device according to the foregoing in the first packet.
  • the user's identity performs a user management operation on the user.
  • the user management may be to manage the online process of the user. For example, the user management may be to assign an IP address to the user, authenticate the user, or authorize the user.
  • an embodiment of the present invention provides a method for processing a message.
  • the method includes:
  • the forwarding plane device receives the first packet sent by the user, where the first packet includes the identifier of the user, and the forwarding plane device includes a forwarding table.
  • the forwarding plane device is a device for forwarding traffic.
  • the forwarding plane device can be a BRAS.
  • the user may be a device located in a local area network.
  • the user can be a personal computer located on a home network.
  • the personal computer can access the Internet through PPPoE.
  • the first packet may be an IP packet.
  • the Internet protocol can be either IPv4 or IPv6.
  • the identifier of the user is used to identify the user.
  • the identifier of the user may be the MAC protocol address of the user or the Internet Protocol address of the user.
  • the identifier of the user may also be a combination of the MAC protocol address of the user and the VLAN identifier of the user.
  • the forwarding table may be a flow table or a packet forwarding table.
  • the forwarding plane device can have two forwarding modes, one is a stream forwarding mode, and the other is a packet forwarding mode.
  • Flow forwarding means that the forwarding plane device forwards the packet according to the flow table.
  • the number of fields used to determine whether a packet matches the entry of the flow table in one entry of the flow table is two or more.
  • the number of fields in an entry of the flow table used to determine whether the packet matches the entry of the flow table may be five.
  • the five fields can be Internet Protocol Address, Destination IP Address, Source Port, Destination Port, and Protocol.
  • the field used to determine whether the message matches the entry of the flow table may be a field of the Data Link layer of the OSI model, or may be a field of the IP layer of the OSI model.
  • Packet forwarding means that the forwarding plane device forwards the packet according to the packet forwarding table. Used in an entry in the packet forwarding table The number of fields that determine whether the packet matches the entry of the packet forwarding table is one.
  • the field in the packet forwarding table for determining whether the packet matches the entry of the packet forwarding table may be a destination IP address or a destination MAC protocol address.
  • the packet forwarding table can be a MAC table or a routing table.
  • the forwarding plane device can be a switch or a router.
  • the forwarding plane device may be an open flow switch.
  • OpenFlow switch please refer to the OpenFlow Switch Specification Version 1.0 released by the standards development organization Open Network Foundation.
  • the forwarding plane device forwards the first packet to a network device, where the first packet is used to enable the network device to perform a correspondence between the identifier of the user and an identifier of the service, and the first packet.
  • the identifier of the user in the text determines an identifier of the service, and manages the service according to the identifier of the service.
  • the service refers to processing the received message according to the field in the received message.
  • the field in the message may be the information of the second layer to the seventh layer defined by the OSI model.
  • the service may be a NAT service, a CGN service, an IPSEC service, a video service, a firewall service, a URL filtering service, or a P2P traffic visualization service.
  • the video service may be a frame relay, a resolution enhancement technology, a multi-document interface, or a content distribution network.
  • the service may be a forwarding service or a CAR service. If the service is a forwarding service, the forwarding service may be a Layer 2 forwarding service, a Layer 3 forwarding service, an MPLS forwarding service, or a VPN forwarding service.
  • the correspondence may be saved in the AAA server.
  • the network device can be from the
  • the AAA server acquires the correspondence.
  • the network device may obtain the correspondence from the AAA server by using a Radius protocol.
  • the identifier of the service is used to identify the service.
  • the network device may be a control plane device corresponding to the forwarding plane device.
  • the network device may also be a device for forwarding traffic.
  • the network device can be a router.
  • the network device may also be a service server capable of processing the service. It can be seen from the foregoing technical solution that the forwarding plane device forwards the received first packet to the network device, so that the network device can be based on the user in the first packet.
  • the identifier identifies the identity of the service, and manages the service according to the identity of the service.
  • the managing the service according to the identifier of the service may include: performing, by the network device, the service corresponding to the first packet according to the identifier of the service
  • the operation is that the network device is a first server capable of executing the service.
  • the first server may be a CGN device.
  • the first server may be a router capable of performing operations corresponding to the CAR service.
  • the first server may be a switch capable of performing operations corresponding to the video enhanced service.
  • the managing the service according to the identifier of the service may include: the network device encapsulating the identifier of the service into the first packet, and generating a second report.
  • the network device forwards the second packet to the second server, where the second server is capable of performing the service.
  • the second server may be a CGN device.
  • the second server may be a router capable of performing operations corresponding to the CAR service.
  • the second server may be a switch capable of performing operations corresponding to the video enhanced service.
  • the managing the service according to the identifier of the service may include: the network device generating a forwarding table entry according to the identifier of the service, and sending the forwarding table entry to the forwarding plane device Transmitting the forwarding table entry, the matching field in the forwarding table entry includes an identifier of the user, and the forwarding table entry is used to enable the forwarding plane device to forward the forwarding table entry according to the forwarding table entry
  • the forwarding table in the polygon device is updated to generate an updated forwarding table, and the forwarding plane device can perform the operation corresponding to the service on the packet including the identifier of the user according to the updated forwarding table.
  • the network device is a control plane device corresponding to the forwarding plane device.
  • the network device can be a control plane device.
  • the network device may be an open flow controller.
  • OpenFlow controller refer to the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the forwarding plane device can communicate with the network device through a control channel.
  • the control channel may be a secure channel through which the open flow switch interacts with the open flow controller.
  • the security channel refer to the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the method may further include: the forwarding plane device according to the foregoing in the first packet.
  • the user's identity performs a user management operation on the user.
  • the user management may be to manage the online process of the user.
  • the user management may be to assign an IP address to the user, authenticate the user, or authorize the user.
  • the forwarding plane device performs a user management operation on the user, and the forwarding plane device does not perform a service management operation on the user. Therefore, the above technical solution realizes separation of user management and business management.
  • FIG. 3 is a flowchart of a method for processing a message according to an embodiment of the present invention. Referring to FIG. 3, the method includes:
  • the network device receives the second packet sent by the forwarding plane device, where the second packet is obtained by the following method: the forwarding plane device receives the first packet sent by the user, where the first packet includes An identifier of the user, where the forwarding plane device includes a forwarding table; the forwarding plane device determines, according to the correspondence between the identifier of the user and the identifier of the service, and the identifier of the user in the first packet. An identifier of the service; the forwarding plane device encapsulates the identifier of the service in the first packet, and generates the second packet; the forwarding plane device sends the second packet to the network device .
  • the forwarding plane device is a device for forwarding traffic.
  • the forwarding plane device can be a BRAS.
  • the user may be a device located in a local area network.
  • the user may be a personal computer located on a home network.
  • the personal computer can access the Internet through PPPoE.
  • the first packet may be an IP packet.
  • the Internet protocol may be IPv4 or IPv6.
  • the identifier of the user is used to identify the user.
  • the identifier of the user may be the MAC protocol address of the user, or may be an Internet Protocol address of the user.
  • the identifier of the user may also be a combination of the MAC protocol address of the user and the VLAN identifier of the user.
  • the forwarding table may be a flow table or a packet forwarding table.
  • the forwarding plane device can have two forwarding modes, one is a stream forwarding mode, and the other is a packet forwarding mode.
  • Flow forwarding means that the forwarding plane device forwards the packet according to the flow table.
  • the number of fields used to determine whether a packet matches the entry of the flow table in one entry of the flow table is two or more.
  • the number of fields used in an entry of the flow table to determine whether the packet matches the entry of the flow table may be five.
  • the five fields can be an internet protocol address, a destination IP address, a source port, a destination port, and a protocol.
  • the field for determining whether the message matches the entry of the flow table may be a field in the data link layer of the OSI model, or may be a field in the IP layer of the OSI model.
  • Packet forwarding means that the forwarding plane device forwards the packet according to the packet forwarding table.
  • the number of fields used in an entry in the packet forwarding table to determine whether the packet matches the entry of the packet forwarding table is one.
  • the field in the packet forwarding table used to determine whether the packet matches the entry of the packet forwarding table may be a destination IP address or a destination MAC protocol address.
  • the packet forwarding table may be a MAC table or a routing table.
  • the forwarding plane device can be a switch or a router.
  • the forwarding plane device may be an open flow switch.
  • OpenFlow switch please refer to the OpenFlow Switch Specification Version 1.0 released by the standards development organization Open Network Foundation.
  • the service refers to processing the received message according to the field in the received message.
  • the field in the message may be the information of the second layer to the seventh layer defined by the OSI model.
  • the service may be a NAT service, a CGN service, an IPSEC service, a video service, a firewall service, a URL filtering service, or a P2P traffic visualization service.
  • the video service may be a frame relay, a resolution enhancement technology, a multi-document interface, or a content distribution network.
  • the service may be a forwarding service or a CAR service. If the service is a forwarding service, the forwarding service may be a Layer 2 forwarding service, a Layer 3 forwarding service, an MPLS forwarding service, or a VPN forwarding service.
  • the correspondence may be saved in the AAA server.
  • the forwarding plane device may obtain the correspondence from the AAA server.
  • the forwarding plane device may obtain the correspondence from the AAA server by using a Radius protocol.
  • the identifier of the service is used to identify the service.
  • the second message includes an identifier of the service.
  • the identifier of the service may be carried in the payload of the second packet, or may be carried in the packet header of the second packet.
  • the network device manages the service according to the identifier of the service in the second packet.
  • the network device may be a control plane device corresponding to the forwarding plane device.
  • the network device may also be a device for forwarding traffic.
  • the network device can be a router.
  • the network device may also be a service server capable of processing the service.
  • the forwarding plane device encapsulates the first packet to generate the second packet.
  • the second packet includes an identifier of the service.
  • the forwarding plane device forwards the second packet to the network device, so that the network device can manage the service according to the identifier of the service in the second packet.
  • the network device managing the service according to the identifier of the service in the second packet includes:
  • the network device performs an operation corresponding to the service on the second packet according to the identifier of the service in the second packet, where the network device is a first server capable of performing the service.
  • the first server may be a CGN device.
  • the first server may be a router capable of performing operations corresponding to the CAR service.
  • the first server may be a switch capable of performing operations corresponding to the video enhanced service.
  • the network device managing the service according to the identifier of the service in the second packet includes:
  • the network device forwards the second packet to the second server that can perform the service according to the identifier of the service in the second packet.
  • the network device is a device capable of forwarding traffic.
  • the network device can be a router.
  • the network device may also be a neighbor forwarding plane device of the forwarding plane device.
  • the network device can be a control plane device or a neighbor control plane device of the control plane device.
  • the network device managing the service according to the identifier of the service in the second packet includes:
  • the network device generates a forwarding table entry according to the identifier of the service in the second packet, and sends the forwarding table entry to the forwarding plane device, where the matching domain in the forwarding table entry includes An identifier of the user, the forwarding table entry is configured to enable the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry, and generate an updated forwarding table, where The forwarding plane device can perform the operation corresponding to the service on the packet including the identifier of the user according to the updated forwarding table, where the network device is a control plane device corresponding to the forwarding plane device.
  • the service may be a forwarding service.
  • the network device can be a control plane device.
  • the network device may be an open flow control Device.
  • OpenFlow controller refer to the OpenFlow Switch Specification Version 1.0 released by the ONF.
  • the forwarding plane device can communicate with the network device through a control channel.
  • the control channel may be a secure channel through which the OpenFlow switch interacts with the OpenFlow controller.
  • security channel refer to the OpenFlow Switch Specification Version 1.0 released by the ONF.
  • FIG. 4 is a flowchart of a method for processing a message according to an embodiment of the present invention. Referring to FIG. 4, the method includes:
  • the network device receives the first packet that is forwarded by the forwarding device, where the first packet is obtained by the following method: the forwarding device receives the first packet sent by the user, where the first packet is sent.
  • the identifier of the user is included, and the forwarding plane device includes a forwarding table; and the forwarding plane device forwards the first packet to the control plane device.
  • the forwarding plane device is a device for forwarding traffic.
  • the forwarding plane device can be a BRAS.
  • the user may be a device located in a local area network.
  • the user can be a personal computer located on a home network.
  • the personal computer can access the Internet through PPPoE.
  • the first packet may be an IP packet.
  • the Internet protocol can be either IPv4 or IPv6.
  • the identifier of the user is used to identify the user.
  • the identifier of the user may be the MAC protocol address of the user or the Internet Protocol address of the user.
  • the identifier of the user may also be a combination of the MAC protocol address of the user and the VLAN identifier of the user.
  • the forwarding table may be a flow table or a packet forwarding table.
  • the forwarding plane device can have two forwarding modes, one is a stream forwarding mode, and the other is a packet forwarding mode.
  • Flow forwarding means that the forwarding plane device forwards the packet according to the flow table.
  • the number of fields used to determine whether a packet matches the entry of the flow table in one entry of the flow table is two or more.
  • the number of fields in an entry of the flow table used to determine whether the packet matches the entry of the flow table may be five.
  • the five fields can be Internet Protocol Address, Destination IP Address, Source Port, Destination Port, and Protocol.
  • the field used to determine whether the message matches the entry of the flow table may be a field at the data link layer of the OSI model or a field at the IP layer of the OSI model.
  • Packet forwarding means that the forwarding plane device forwards the packet according to the packet forwarding table. Used in an entry in the packet forwarding table The number of fields that determine whether the packet matches the entry of the packet forwarding table is one.
  • the field in the packet forwarding table for determining whether the packet matches the entry of the packet forwarding table may be a destination IP address or a destination MAC protocol address.
  • the packet forwarding table can be a MAC table or a routing table.
  • the forwarding plane device can be a switch or a router.
  • the forwarding plane device may be an open flow switch.
  • OpenFlow switch please refer to the OpenFlow Switch Specification Version 1.0 released by the standards development organization Open Network Foundation.
  • the network device determines the identifier of the service according to the correspondence between the identifier of the user and the identifier of the service, and the identifier of the user in the first packet.
  • the network device manages the service according to the identifier of the service.
  • the service refers to processing the received message according to the field in the received message.
  • the field in the message may be the information of the second layer to the seventh layer defined by the OSI model.
  • the service may be a NAT service, a CGN service, an IPSEC service, a video service, a firewall service, a URL filtering service, or a P2P traffic visualization service.
  • the video service may be a frame relay, a resolution enhancement technology, a multi-document interface, or a content distribution network.
  • the service may be a forwarding service or a CAR service. If the service is a forwarding service, the forwarding service may be a Layer 2 forwarding service, a Layer 3 forwarding service, an MPLS forwarding service, or a VPN forwarding service.
  • the correspondence may be saved in the AAA server.
  • the network device may obtain the correspondence from the AAA server.
  • the network device may obtain the correspondence from the AAA server by using a Radius protocol.
  • the identifier of the service is used to identify the service.
  • the network device may be a control plane device corresponding to the forwarding plane device.
  • the network device may also be a device for forwarding traffic.
  • the network device can be a router.
  • the network device may also be a service server capable of processing the service. It can be seen from the foregoing technical solution that the forwarding plane device forwards the received first packet to the network device, so that the network device can be based on the user in the first packet.
  • the identifier identifies the identity of the service, and manages the service according to the identity of the service.
  • the managing, by the network device, the service according to the identifier of the service includes:
  • the network device performs operations corresponding to the service on the first packet according to the identifier of the service, where the network device is a first server capable of executing the service.
  • the first server may be a CGN device.
  • the first server may be a router capable of performing operations corresponding to the CAR service.
  • the first server may be a switch capable of performing operations corresponding to the video enhanced service.
  • the network device manages the service according to the identifier of the service, including:
  • the network device encapsulates the identifier of the service with the first packet to generate a second packet; the network device forwards the second packet to a second server, where the second server is capable of performing the service .
  • the second server may be a CGN device.
  • the second server may be a router capable of performing operations corresponding to the CAR service.
  • the second server may be a switch capable of performing operations corresponding to the video enhanced service.
  • the network device manages the service according to the identifier of the service, including:
  • the network device generates a forwarding table entry according to the identifier of the service, and sends the forwarding table entry to the forwarding plane device, where the matching domain in the forwarding table entry includes the identifier of the user, and the forwarding a publishing entry for causing the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry and generate an updated forwarding table, wherein the forwarding plane device is capable of updating according to the
  • the subsequent forwarding table performs an operation corresponding to the service on the packet including the identifier of the user, where the network device is a control plane device corresponding to the forwarding plane device.
  • the network device can be a control plane device.
  • the network device may be an open flow controller.
  • OpenFlow controller refer to the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the forwarding plane device can communicate with the network device through a control channel.
  • the control channel may be a secure channel through which the OpenFlow switch interacts with the OpenFlow controller.
  • For the safety channel please refer to the specific The OpenFlow Switch Specification Version 1.0 released by ONF.
  • FIG. 5 is a forwarding plane device according to an embodiment of the present invention.
  • the forwarding plane device can perform the method shown in FIG. Referring to FIG. 5, the apparatus includes: a receiving unit 51, a determining unit 52, a generating unit 53, and a transmitting unit 54.
  • the receiving unit 51 is configured to receive a first packet sent by the user, where the first packet includes an identifier of the user, and the forwarding plane device includes a forwarding table.
  • the receiving unit 51 can be a receiver.
  • the determining unit 52 is configured to determine, according to the correspondence between the identifier of the user and the identifier of the service, and the identifier of the user in the first packet received by the receiving unit 51.
  • the determining unit 52 can be a network processor (P).
  • the generating unit 53 is configured to encapsulate the identifier of the service determined by the determining unit 52 in the first packet, and generate a second packet.
  • the generating unit 53 can be the P.
  • the sending unit 54 is configured to send, by the network device, the second packet generated by the generating unit 53, where the second packet is used to enable the network device to be according to the second packet.
  • the identity of the business manages the business.
  • the transmitting unit 54 can be a transmitter.
  • the apparatus shown in FIG. 5 may further include: an operation unit 61, configured to perform a user management operation on the user according to the identifier of the user in the first packet received by the receiving unit 51. . See Figure 6 for the operating unit 61.
  • FIG. 6 is a schematic structural diagram of a forwarding plane device according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a forwarding plane device according to an embodiment of the present invention.
  • the forwarding plane device can perform the method shown in Fig. 2.
  • the forwarding plane device includes: a receiving unit 71 and a forwarding unit 72.
  • the receiving unit 71 is configured to receive a packet sent by the user, where the packet includes an identifier of the user, and the forwarding plane device includes a forwarding table.
  • the receiving unit 71 can be a receiver.
  • the forwarding unit 72 is configured to forward, to the network device, the packet received by the receiving unit 71, where the packet is used to enable the network device to perform a correspondence between the identifier of the user and the identifier of the service, and the The identifier of the user in the message determines an identifier of the service, and manages the service according to the identifier of the service.
  • the forwarding unit 72 can be a repeater.
  • an operation unit 81 may be further included, according to the receiving unit.
  • FIG. 8 is a schematic structural diagram of a forwarding plane device according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • the network device can perform the method shown in FIG. Referring to FIG. 9, the network device includes: a receiving unit 91 and a management unit 92.
  • the receiving unit 91 is configured to receive a second packet sent by the forwarding plane device, where the second packet is obtained by: the forwarding plane device receiving the first packet sent by the user, where the first packet is sent.
  • the forwarding plane device includes a forwarding table, and the forwarding plane device is configured according to the correspondence between the identifier of the user and the identifier of the service, and the identifier of the user in the first packet. Determining the identifier of the service, and encapsulating the identifier of the service in the first packet to obtain the second packet; the forwarding plane device sending the second packet to the network device.
  • the receiving unit 91 can be a receiver.
  • the management unit 92 is configured to manage the service according to the identifier of the service in the second packet received by the receiving unit 91.
  • the management unit 92 can be P.
  • the management unit 92 may be configured to perform an operation corresponding to the service on the second packet according to the identifier of the service in the second packet, where the network device is the first one capable of performing the service. server.
  • the management unit 92 may be configured to forward, according to the identifier of the service in the second packet, the second server to the second server capable of performing the service. Message.
  • the management unit 92 may be configured to generate a forwarding table entry according to the identifier of the service in the second packet, and send the to the forwarding device. Forwarding a table entry, the matching field in the forwarding table entry includes an identifier of the user, and the forwarding table entry is used to enable the forwarding plane device to be in the forwarding plane device according to the forwarding table entry
  • the forwarding table is updated to generate an updated forwarding table, and the forwarding plane device is capable of performing an operation corresponding to the service on the packet including the identifier of the user according to the updated forwarding table, the network
  • the device is a control plane device corresponding to the forwarding surface device.
  • FIG. 10 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • the network device can perform the method shown in Figure 4.
  • the network device includes: a receiving unit 10, a determining unit 11 and a management unit 12.
  • the receiving unit 10 is configured to receive a first packet that is forwarded by the forwarding device, where the first packet is obtained by: the forwarding device receiving the first packet sent by the user, where the first packet is sent Include the identifier of the user, the forwarding plane device includes a forwarding table; and the forwarding plane device forwards the to the network device First message.
  • the determining unit 11 is configured to determine an identifier of the service according to a correspondence between the identifier of the user and an identifier of the service, and an identifier of the user in the first packet.
  • the management unit 12 is configured to manage the service according to the identifier of the service determined by the determining unit 11.
  • the management unit 12 is specifically configured to perform operations corresponding to the service on the packet according to the identifier of the service, where the network device is capable of performing the service.
  • the first server is specifically configured to perform operations corresponding to the service on the packet according to the identifier of the service, where the network device is capable of performing the service.
  • the management unit 12 is specifically configured to: encapsulate the identifier of the service into the first packet, and generate a second packet.
  • the management unit 12 is specifically configured to generate a forwarding table entry according to the identifier of the service, and send the forwarding table entry to the forwarding plane device, where the forwarding The matching field in the publication entry includes the identifier of the user, and the forwarding table entry is configured to enable the forwarding plane device to update the forwarding table in the forwarding plane device according to the forwarding table entry and Generating an updated forwarding table, wherein the forwarding plane device is configured to perform an operation corresponding to the service on the packet including the identifier of the user according to the updated forwarding table, where the network device is configured by the forwarding plane device Control surface device.
  • FIG. 11 is a flowchart of a method for processing a message according to an embodiment of the present invention.
  • the user successfully registers the service in the AAA server in advance.
  • the network device is a control plane device. Referring to Figure 11, the method includes:
  • Step 111 Receive a data packet sent by the user, where the data packet includes a user identifier.
  • the forwarding plane device may receive the data packet sent by the user, or may send the data packet to the receiving user through the convergence layer network.
  • the data packet includes the user identifier.
  • the data packet may include other parameters, such as a service identifier.
  • the forwarding plane device may be a broadband remote access server (BRAS), but the BRAS is separate from the user management and service management; of course, the forwarding plane device may also be a router, etc.; It can be other devices with a forwarding function, which is not limited in this embodiment.
  • BRAS broadband remote access server
  • PCI packet control information
  • the control plane device performs service processing on the PCI-added data packet according to the user identifier.
  • Protocol Control Information is a part of the protocol data unit, including addresses, controls, flags, and other optional information, and is a service provided by the provider of the peer-to-peer service.
  • the forwarding plane device After the forwarding plane device receives the data packet, it first determines whether the data packet matches the flow table according to the quintuple element of the packet, where the flow table is sent by the control plane device in advance.
  • the packet control information PCI is added to the data packet, and the data packet after the PCI is added is offloaded to the control plane device, so as to be controlled.
  • the device performs service processing on the data packet according to the user identifier; that is, the data packet is processed correspondingly according to the service registered by the user.
  • the data packet is forwarded according to the address of the flow table.
  • the user identifier may include: a user's Internet Protocol (IP) address, a media access control (MAC) address, a P/or, a MAC address, and a virtual local area network (VLAN). ), but not limited to this.
  • FIG. 11 is a fourth flowchart of a method for processing a message according to an embodiment of the present invention.
  • the method may further include: when receiving a data packet sent by a user, Verify that the user is legal, including:
  • step 122 Verify that the user is legal, if it is legal, go to step 123; otherwise, go to step 125; where, because the relationship between the user and the service registered by the user is saved in the AAA server, the device on the forwarding plane receives the user.
  • the user can be authenticated by the AAA server after receiving the data packet sent by the user. If the user is authenticated, the user is a valid user and has successfully registered. Then, step 123 is performed; if the user is not authenticated, the user is an illegal user, and the data packet sent by the user is discarded.
  • the AAA server in this embodiment may be deployed independently or integrated in the forwarding plane device, which is not limited in this embodiment.
  • Step 123 Determine whether the data packet matches the flow table.
  • step 124 If the data packet does not match, go to step 124. If yes, go to step 126. If yes, determine whether the data packet matches the corresponding entry in the flow table. It can be matched according to the quintuple elements of the message. The process of the specific matching is well known to those skilled in the art, and details are not described herein.
  • the user identifier includes: a user's IP address, a media intervention control MAC address, or a MAC address + a virtual local area network VLAN.
  • the forwarding plane device After receiving the data packet sent by the user, the forwarding plane device first verifies the legality of the user, and if the user is legal, determines whether the data packet matches the entry in the flow table, and then The data packet that does not match the entry is offloaded to the control plane device, and the control plane device performs corresponding service processing on the data packet according to the user identifier. At the same time, because the user management and the processing of the service are separated, the data packet can carry the user identifier or the service identifier.
  • Such a forwarding device can focus on user management, while business processing can be run on a control plane device, such as a service server. That is to say, various services originally running on multiple forwarding plane devices (such as BRAS) can now be centralized on a control plane device (such as a service server cluster or data center) to reduce access.
  • a control plane device such as a service server cluster or data center
  • the method may further include: acquiring an association relationship between the user, the service identifier, and the service; The process is added to the PCI of the data packet.
  • the process of obtaining the data packet may be obtained from the AAA server.
  • the device that offloads the data packet of the PCI to the control plane device is specifically configured to: offload the data packet after adding the service identifier to the control plane device.
  • the service identifier includes: a layer of a virtual local area network ID, a multi-layer virtual local area network ID (such as QinQ, etc.) or a package ID; or the service identifier indicates a service (such as an Internet service, a voice service, etc.), or each One bit represents a service.
  • the method may further include: acquiring a customized package ID; and recording the package ID In the package field of the user table;
  • the method of adding the service identifier to the PCI of the data packet is exemplified by two cases, but is not limited thereto: a case where the forwarding plane device performs multi-protocol label switching MPLS encapsulation on the data packet; Determining whether the MPLS label value in the encapsulated data packet is the same as one of the pre-stored MPLS labels, and if yes, performing a matching operation of the user table; if the user entry in the user table is successfully matched, extracting the a package field value in the user entry; adding the package field value to the PCI of the data packet, where the package field value is a package ID;
  • the forwarding plane device performs IP encapsulation on the data packet, and determines whether the IP value in the encapsulated data packet is the same as one of the pre-stored IP values. If the same, perform matching of the user table. If the user entry in the user table is successfully matched, the package field value in the user entry is extracted; the package field value is added to the PCI of the data packet, where the package field The value is the package ID.
  • the method before receiving the data packet sent by the user, may further include: after detecting that the user goes online, the forwarding plane device sends a request for the user to apply for an IP address to the control plane device. And sending the IP address to the user after receiving the response including the IP address by the control plane device; so that the user subsequently initiates the data packet, that is, the data packet sent by the subsequent user.
  • the IP address is included in the file.
  • the data packet that does not match the entry is offloaded to the control plane device, and is processed by the control plane device, which reduces the traffic pressure of the user access side network (such as the aggregation network).
  • the control plane device which reduces the traffic pressure of the user access side network (such as the aggregation network).
  • the data packet can carry the user identifier or the service identifier.
  • the forwarding plane device e.g., BRAS device
  • the business process can be run on a control plane device such as a service server. That is to say, various services originally running on multiple forwarding plane devices (such as BRAS) can now be centralized on a control plane device (such as a service server cluster or data center) to reduce access.
  • the traffic pressure of the aggregation network can be centralized on a control plane device (such as a service server cluster or data center) to reduce access.
  • FIG. 13 is a flowchart of a method for processing a packet according to an embodiment of the present invention.
  • the network device is still an example of a control plane device, where the method includes: The receiving, by the forwarding device, the data packet that is offloaded, where the data packet includes the user identifier and the packet control information PCI;
  • control plane device receives the data packet that is offloaded by the forwarding plane device, and parses the data packet to obtain a user identifier included in the data packet.
  • the packet control information PCI is added to the data packet.
  • control plane device determines, by the user identifier, which user the data packet belongs to, and learns the service registered by the user, and performs corresponding service processing on the data packet.
  • the control plane device learns the service registered by the user through the user identifier, and invokes the service to process the data packet.
  • the method may further include: acquiring a user corresponding to the user identifier, and a relationship between the user and a registered service; Specifically, the relationship between the user and the registered service may be obtained through a COA (Change of Authorization) message, but is not limited thereto.
  • COA Change of Authorization
  • the performing service processing on the data packet according to the user identifier includes: invoking a service registered by the user to perform service processing on the data packet.
  • the user identification package may include: a user's IP address, a media intervention control MAC address, and/or a MAC address + a virtual local area network VLAN; but is not limited thereto.
  • the control plane device first determines which user the data packet belongs to by the user identifier, and then, through the COA message, learns the service registered by the user from the AAA server, and invokes the service to perform service processing on the data packet.
  • the AAA server can also actively send the user and the registered service to the control plane device through the COA message. For example, when the user goes online, goes offline, or changes the subscription service, the AAA server can notify the control plane device (such as the VAS server) through the COA message, and the control plane device (such as the VAS server) updates the relationship between the service and the user.
  • the method may further include: the control plane device may actively or passively acquire the changed relationship between the user and the registered service from the AAA server; and update the relationship between the stored user and the registered service.
  • the priority of the service identifier is greater than the user identifier
  • the service processing of the data packet according to the user registration service corresponding to the user identifier is specifically
  • the service corresponding to the service identifier is invoked to perform service processing on the data packet.
  • the service identifier may include: a layer of a virtual local area network ID, a multi-layer virtual local area network ID or a package ID; or the service identifier represents a service, or each bit represents a service. But it is not limited to this. That is, as long as the PCI in the data packet includes the service identifier, the control plane device does not need to learn the service registered by the user from the AAA server, but directly invokes the service corresponding to the service identifier to process the data packet.
  • the invoking the service corresponding to the service identifier to perform the service processing on the data packet includes: acquiring a corresponding service identifier in the data packet; determining a specific service corresponding to the service identifier; Identify the specific service and perform service processing on the data packet.
  • the method may further include: the control plane device receiving, by the forwarding device, a request for requesting an IP address for the user; and transmitting, to the forwarding device Send a response that includes an IP address.
  • FIG. 14 is a schematic diagram of a first application example of a method for offloading service data according to an embodiment of the present invention.
  • a data packet includes a user identifier as an example, and the forwarding plane device is BRAS/ SR
  • a network device uses a VAS server as an example, but is not limited thereto.
  • the data packet is taken as an example, but is not limited thereto.
  • the specific implementation process is as follows:
  • the user first registers the service with the AAA server. After the registration is successful, the AAA server stores the relationship between the user and its registered service.
  • one or more users to initiate a data packet to the BRAS/SR, where the data packet includes a user identifier; wherein the user identifier usually uses a user IP address; It can also be a MAC address or a MAC+VLAN as a user identifier; these identifiers are all part of the packet header, so the offloaded data packet naturally includes this information.
  • step (3) After receiving the data packet, the BRAS/SR verifies whether the user is legal through the AAA server. The manner of verification is well known to those skilled in the art, and details are not described herein. Performing step (4) directly on the data packet sent by the legitimate user;
  • the BRAS/SR first determines whether the data packet matches the flow table sent by the upper-layer device (such as a VAS server). If not, the packet control information is added to the data packet. The data packet after the PCI is added is offloaded to the VAS server, that is, the label (5). If it matches, the data packet is forwarded according to the flow table, that is, the label (6).
  • the specific processing procedure of the data packet by the BRAS/SR is as follows, and is not described here.
  • the VAS server After receiving the data packet of the BRAS/SR offload, the VAS server performs service processing on the data packet according to the user identifier; (7) After receiving the data packet, the VAS server first acquires the user and the service relationship through the AAA server; thereby knowing which service processes are used to process the data packet of the user;
  • the VAS server invokes the service registered by the user to perform service processing on the data packet; for example, if the service registered by the user 1 includes: service 1, service 2, and service 3, the service registered by the user 2 includes: 1. Business 2 and Business 3, etc.
  • the VAS server receives the data message in the offloaded network; first obtains the user and the service relationship through the AAA server, so as to know which services are managed by the VAS server to process the data message of the user; when the BRAS/SR sends the data message ( When the data stream is directed to the VAS server, the VAS server parses the user identifier carried in the data packet, and determines which user the data packet belongs to by the user identifier, so that the corresponding service is invoked to process the data packet.
  • the AAA server can notify the VAS server through the COA message, and the VAS server updates the relationship between the service and the user.
  • FIG. 15 is a schematic diagram of a second application example of a method for offloading service data according to an embodiment of the present invention.
  • a service identifier is included in a data packet as an example, but in an actual application.
  • the data includes the user identifier and the service identifier.
  • the priority of the service identifier is higher than the user identifier.
  • the forwarding plane device uses the BRAS/SR as an example.
  • the network device uses the VAS server as an example, but is not limited thereto.
  • the specific implementation process is as follows: (1) The user first registers the service with the AAA server. After the registration is successful, the AAA server stores the relationship between the user and the registered service.
  • One or more users to initiate a data packet to the BRAS/SR, where the data packet includes a service identifier, where the service identifier may be a layer of a virtual local area network. ID (vlanid), a multi-layer virtual local area network ID (such as QinQ) or a package ID; or, the service identifier may also be a service or a service set, or each bit of the service identifier represents a service.
  • ID virtual local area network
  • QinQ multi-layer virtual local area network ID
  • package ID or, the service identifier may also be a service or a service set, or each bit of the service identifier represents a service.
  • the association relationship between the user and the service identifier and the service is obtained, and the relationship can be obtained from the AAA. Obtained on the server, or it can be managed by the BRAS/SR itself;
  • the BRAS/SR When the BRAS/SR receives the data packet sent by the user, it first determines whether the data packet matches the flow table sent by the upper-layer device (such as a VAS server, etc.), if it does not match. Adding the packet control information PCI to the data packet, adding a service identifier to the PCI, and offloading the data packet after adding the service identifier to the VAS server, that is, the label (5); Matching, forwarding the data packet according to the flow table, that is, label (6); That is, in the process, when the data packet of the legal user enters the BRAS/SR, the BRAS/SR will put the data packet that does not match the flow table with the service identifier, and offload the data packet marked with the service identifier. Go to the VAS server for processing.
  • the upper-layer device such as a VAS server, etc.
  • the VAS server in the receipt of the data packet, identifies the service identifier of the data packet, and distributes the data packet to each according to the service identifier according to the relationship between the service identifier and the specific service maintained by the VAS server.
  • the business is processed accordingly.
  • the service corresponding to the service identifier 1 includes the service 1, the service 2, and the service 3.
  • the services corresponding to the service identifier 2 include: service 2, service 3, and service 4.
  • the following describes the process of representing a service identifier by using a vlanid, multiple vlanids, and a package ID; 1) if a vlanid is used to represent the service identifier
  • the vlanid carried by the offloaded packet can be directly used as the service identifier. This method does not need to add a field as the service identifier. If the user needs to change the service (package), only the vlanid needs to be changed. simple.
  • the portal server sets a vlanid to the local online device (or software), indicating that the user uses the vlan.
  • the vlanid is carried in the data packet subsequently sent by the user.
  • the BRAS/SR can also be configured on the interface by using the user-vlan any-other mode. After the user is authenticated and authorized, the user will carry the vlanid.
  • vlanids such as QinQ
  • the implementation process is the same as that of a vlan. The difference is as follows: You can use the outer vlanid as the service identifier or the inner vlan as the service identifier. Or a combination of the two as a business identifier.
  • the implementation needs to add a field for saving the package ID value at the head of the offloaded data packet: This method needs to modify the flow table logic and the P microcode, and the process is:
  • the P microcode increases the shunt enable register flag; the user table in the P microcode adds a package ID field; and increases the register that stores the same MPLS tag value as the flow table logic.
  • the portal server After the user selects the service package through the Portal server or other management tools, the portal server records the package ID and the user association relationship to the AAA server. 4. After the user goes online, the AAA server performs authentication and authorization. At this time, the AAA server sends the customized package ID to the BRAS/SR. The BRAS/SR records the package ID to the user table of the forwarding plane NP microcode.
  • the data packet enters the flow table logic, and the flow table logically queries the flow table, and encapsulates the data packet that does not hit the flow table. That is, the PCI header and the MPLS encapsulation are added, and the encapsulated data packet is sent to the P microcode, and the P microcode determines that the offloading is enabled.
  • the P-new process is performed, that is, the offset data packet is sent to the original packet header (that is, the packet header when entering the flow table logic), and the user table matching operation is performed, if it matches the corresponding user entry in the user table; Extract the corresponding package field value (ie, the package ID value) in the entry; fill the package field value into the package field in the PCI header in the data packet; if the MPLS label value of the data packet and the label in the register One of the values is different, and is implemented according to the existing process of the P-microcode.
  • the existing process of the P-microcode is well-known to those skilled in the art, and details are not described herein.
  • the encapsulation of the data packet may be performed by using an IP encapsulation manner, which is similar to the MPLS encapsulation method.
  • IP encapsulation manner which is similar to the MPLS encapsulation method.
  • FIG. 16 is a schematic diagram of a third application example of a method for offloading service data according to an embodiment of the present invention.
  • the third embodiment is similar to the first embodiment except that the DHCP service function is provided by the VAS server.
  • the router such as the BRAS/SR
  • the router After the router (such as the BRAS/SR) receives the online request from the user, it authenticates to the AAA server. If the authentication succeeds, and then applies for an IP address to the VAS server. After the IP address is applied successfully, the VAS server sends a message including the IP address to the AAA.
  • the server records the IP address and user relationship of the AAA server.
  • the VAS server also sends the IP address to the router, and the router sends the IP address to the user.
  • the user can send a data packet to the router (such as the BRAS/SR), where the data packet carries the IP address.
  • the router such as the BRAS/SR
  • the process of receiving the data packet by the router is the same as that of the embodiment. For details, refer to the first embodiment, and details are not described herein again.
  • the user management device can be deployed in the aggregation layer, close to the user, and the traffic between the users can be terminated in the user management device, and the access aggregation network is reduced. Traffic pressure; and, when the user and the service are decoupled, the user management device can be deployed on the aggregation layer access side.
  • the user information is not perceived, and the workload for the user to be aware of the user information is reduced.
  • the service is processed by the server and can be deployed in a centralized manner and independently upgraded without affecting the online experience of the user.
  • the embodiments of the present invention have the following advantages compared with the prior art: 1. Separate service deployment and user management, simplify management: In other words, the prior art requires user management and service processing on the same device (such as BRAS or SR device).
  • the embodiment of the invention can separate user management and business processing.
  • the data packet can carry the user identifier or / service identifier. This allows the BRAS device to focus on user management, while business processing can run on the business server.
  • the various services that were originally running on multiple BRASs can now be centralized in a single service server cluster or data center.
  • the operator can quickly deploy the value-added service: that is, the technology of the present invention can make the service independent of the user management deployment, so that after the new value-added service is developed, the user deployment part can be completely changed, that is, the BRAS device is not upgraded. . Simply change the service processing on the business server, and you can deploy new services online without affecting the operation of the old business.
  • Network evolution can reduce user management location and meet high-speed bandwidth requirements: That is, user management can be moved from the current BRAS router location, ie, the network aggregation layer, to the user, after user management and service deployment are separated. Access layer location. This layer is closer to the user, making bandwidth management for users more flexible and efficient.
  • the disclosed systems, devices, and methods may In other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit may be only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined. Either can be integrated into another system, or some features can be ignored, or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a mobile hard disk, a read only memory (abbreviated as ROM in English, a full name of Read-Only Memory in English), a random access memory (abbreviated as RAM in English, a full name called Random Access Memory in English), and magnetic
  • ROM read only memory
  • RAM random access memory
  • magnetic A variety of media that can store program code, such as a disc or a disc.

Abstract

一种处理报文的方法、转发面装置及网络设备,处理报文的方法包括:转发面装置接收用户发送的第一报文,第一报文中包括用户的标识,转发面装置中包含转发表;转发面装置根据用户的标识与业务的标识的对应关系以及第一报文中的用户的标识确定业务的标识;转发面装置在第一报文中封装业务的标识,生成第二报文;转发面装置向网络设备发送第二报文,第二报文用于使网络设备根据第二报文中的业务的标识管理业务。上述技术方案提高了对业务进行管理的灵活性。

Description

处理报文的方法、 转发面装置及网络设备
技术领域
本发明涉及网络技术, 特别涉及处理报文的方法、 转发面装置及网络设备。 背景技术
随着网络技术的发展, 在现有软件定义的网络 (SDN, software define network) 中, 已经实现了控制与转发的分离。举例来说, 控制器(controller)可以生成转发表, 并将所述转发表下发到宽带远程接入服务器(BRAS, broadband remote access server) 或业务路由器 (SR, Service Router) 上。 BRAS或 SR可以根据所述转发表对接收到 的报文进行转发。 现有技术对业务进行管理不够灵活。 发明内容 本发明实施例提供了处理报文的方法、装置、转发面装置及网络设备, 用于提高 对业务进行管理的灵活性。
为了实现上述目的, 本发明实施例公开了如下技术方案:
第一方面, 提供了一种处理报文的方法, 包括: 转发面装置接收用户发送的第一 报文, 所述第一报文中包括所述用户的标识, 所述转发面装置中包含转发表;
所述转发面装置根据所述用户的标识与业务的标识的对应关系以及所述第一报 文中的所述用户的标识确定所述业务的标识;
所述转发面装置在所述第一报文中封装所述业务的标识, 生成第二报文; 所述转发面装置向网络设备发送所述第二报文,所述第二报文用于使所述网络设 备根据所述第二报文中的所述业务的标识管理所述业务。
在第一方面的第一种可能的实现方式中,所述网络设备根据所述第二报文中的 所述业务的标识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识对所述第二报文执行所述 业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器; 或者
所述网络设备根据所述第二报文中的所述业务的标识向能够执行所述业务的第 二服务器转发所述第二报文; 或者 所述网络设备根据所述第二报文中的所述业务的标识生成转发表表项并向所述 转发面装置发送所述转发表表项, 所述转发表表项中的匹配域包括所述用户的标识, 所述转发表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置中的 所述转发表进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后的 转发表对包含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为与所 述转发面装置对应的控制面装置。
结合第一方面或第一方面第一种可能的实现方式, 在第二种可能的实现方式 中, 所述转发面装置接收用户发送的第一报文之后, 所述方法还包括:
所述转发面装置根据所述第一报文中的所述用户的标识对所述用户执行用户管 理操作。
第二方面, 提供了一种处理报文的方法, 包括:
转发面装置接收用户发送的第一报文,所述第一报文中包括所述用户的标识,所 述转发面装置中包含转发表;
所述转发面装置向网络设备转发所述第一报文,所述第一报文用于使所述网络设 备根据所述用户的标识与业务的标识的对应关系以及所述第一报文中的所述用户的 标识确定所述业务的标识, 并根据所述业务的标识管理所述业务。
在第二方面的第一种可能的实现方式中,所述根据所述业务的标识管理所述业 务包括:
所述网络设备根据所述业务的标识对所述第一报文执行所述业务对应的操作,所 述网络设备为能够执行所述业务的第一服务器; 或者
所述网络设备向所述第一报文封装所述业务的标识, 生成第二报文;
所述网络设备向第二服务器转发所述第二报文,所述第二服务器能够执行所述业 务; 或者
所述网络设备根据所述业务的标识生成转发表表项并向所述转发面装置发送所 述转发表表项,所述转发表表项中的匹配域包括所述用户的标识,所述转发表表项用 于使所述转发面装置根据所述转发表表项对所述转发面装置中的所述转发表进行更 新并生成更新后的转发表,所述转发面装置能够根据所述更新后的转发表对包含所述 用户的标识的报文执行所述业务对应的操作,所述网络设备为与所述转发面装置对应 的控制面装置。
结合第二方面或第二方面第一种可能的实现方式, 在第二种可能的实现方式 中, 所述转发面装置接收用户发送的第一报文之后, 所述方法还包括: 所述转发面装置根据所述第一报文中的所述用户的标识对所述用户执行用户管 理操作。
第三方面, 提供了一种处理报文的方法, 包括:
网络设备接收转发面装置发送的第二报文, 所述第二报文通过如下途径得到: 所述转发面装置接收用户发送的第一报文, 所述第一报文中包括所述用 户的标识, 所述转发面装置中包含转发表;
所述转发面装置根据所述用户的标识与业务的标识的对应关系以及所述 第一报文中的所述用户的标识确定所述业务的标识;
所述转发面装置在所述第一报文中封装所述业务的标识, 生成所述第二 报文;
所述转发面装置向所述网络设备发送所述第二报文;
所述网络设备根据所述第二报文中的所述业务的标识管理所述业务。
在第三方面的第一可能的实现方式种, 所述网络设备根据所述第二报文中的所 述业务的标识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识对所述第二报文执行所述 业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器; 或者
所述网络设备根据所述第二报文中的所述业务的标识向能够执行所述业务的第 二服务器转发所述第二报文; 或者
所述网络设备根据所述第二报文中的所述业务的标识生成转发表表项并向所述 转发面装置发送所述转发表表项, 所述转发表表项中的匹配域包括所述用户的标识, 所述转发表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置中的 所述转发表进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后的 转发表对包含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为所述 转发面装置对应的控制面装置。
第四方面, 提供了一种处理报文的方法, 包括:
网络设备接收转发面装置转发的第一报文, 所述第一报文通过如下途径得到: 所述转发面装置接收用户发送的所述第一报文, 所述第一报文中包括所 述用户的标识, 所述转发面装置中包含转发表;
所述转发面装置向所述控制面装置转发所述第一报文;
所述网络设备根据所述用户的标识与业务的标识的对应关系以及所述第一报文 中的所述用户的标识确定所述业务的标识; 所述网络设备根据所述业务的标识管理所述业务。
在第四方面的第一可能的实现方式中, 所述网络设备根据所述业务的标识管理 所述业务包括:
所述网络设备根据所述业务的标识对所述第一报文执行所述业务对应的操作,所 述网络设备为能够执行所述业务的第一服务器; 或者
所述网络设备向所述第一报文封装所述业务的标识, 生成第二报文;
所述网络设备向第二服务器转发所述第二报文,所述第二服务器能够执行所述业 务; 或者
所述网络设备根据所述业务的标识生成转发表表项并向所述转发面装置发送所 述转发表表项,所述转发表表项中的匹配域包括所述用户的标识,所述转发表表项用 于使所述转发面装置根据所述转发表表项对所述转发面装置中的所述转发表进行更 新并生成更新后的转发表,所述转发面装置能够根据所述更新后的转发表对包含所述 用户的标识的报文执行所述业务对应的操作,所述网络设备为所述转发面装置对应的 控制面装置。
第五方面, 提供了一种转发面装置, 包括:
接收单元,用于接收用户发送的第一报文,所述第一报文中包括所述用户的标识, 所述转发面装置中包含转发表;
确定单元,用于根据所述用户的标识与业务的标识的对应关系以及所述接收单元 接收的所述第一报文中的所述用户的标识确定所述业务的标识;
生成单元,用于在所述第一报文中封装所述确定单元确定的所述业务的标识, 生 成第二报文;
发送单元,用于向网络设备发送所述生成单元生成的所述第二报文,所述第二报 文用于使所述网络设备根据所述第二报文中的所述业务的标识管理所述业务。
在第五方面的第一可能的实现方式中, 包括:
操作单元,用于根据所述接收单元接收到的所述第一报文中的所述用户的标识对 所述用户执行用户管理操作。
第六方面, 提供了一种转发面装置, 包括:
接收单元, 用于接收用户发送的报文, 所述报文中包括所述用户的标识, 所述转 发面装置中包含转发表;
转发单元,用于向网络设备转发所述接收单元接收的所述报文,所述报文用于使 所述网络设备根据所述用户的标识与业务的标识的对应关系以及所述报文中的所述 用户的标识确定所述业务的标识, 并根据所述业务的标识管理所述业务。
在第六方面的第一可能的实现方式中, 还包括:
操作单元,用于根据所述接收单元接收到的所述报文中的所述用户的标识对所述 用户执行用户管理操作。
第七方面, 提供了一种网络设备, 包括:
接收单元, 用于接收转发面装置发送的第二报文, 所述第二报文通过如下途径得 到:
所述转发面装置接收用户发送的第一报文, 所述第一报文中包括所述用 户的标识, 所述转发面装置中包含转发表;
所述转发面装置根据所述用户的标识与业务的标识的对应关系以及所述 第一报文中的所述用户的标识确定所述业务的标识, 并在所述第一报文中封 装所述业务的标识, 得到所述第二报文;
所述转发面装置向所述网络设备发送所述第二报文;
管理单元, 用于根据所述第二报文中的所述业务的标识管理所述业务。
在第七方面的第一可能的实现方式中, 所述管理单元用于根据所述第二报文中 的所述业务的标识对所述第二报文执行所述业务对应的操作,所述网络设备为能够执 行所述业务的第一服务器; 或者
所述管理单元用于根据所述第二报文中的所述业务的标识向能够执行所述业务 的第二服务器转发所述第二报文; 或者
所述管理单元用于根据所述第二报文中的所述业务的标识生成转发表表项并向 所述转发面装置发送所述转发表表项,所述转发表表项中的匹配域包括所述用户的标 识,所述转发表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置中 的所述转发表进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后 的转发表对包含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为所 述转发面装置对应的控制面装置。
第八方面, 提供了一种网络设备, 包括:
接收单元, 用于接收转发面装置转发的第一报文, 所述第一报文通过如下途径得 到:
所述转发面装置接收用户发送的第一报文, 所述第一报文中包括所述用 户的标识, 所述转发面装置中包含转发表;
所述转发面装置向所述网络设备转发所述第一报文; 确定单元,用于根据所述用户的标识与业务的标识的对应关系以及所述第一报文 中的所述用户的标识确定所述业务的标识;
管理单元, 用于根据所述确定单元确定的所述业务的标识管理所述业务。
在第八方面的第一可能的实现方式中, 所述管理单元具体用于根据所述业务的 标识对所述报文执行所述业务对应的操作,所述网络设备为能够执行所述业务的第一 服务器; 或者
所述管理单元具体用于向所述第一报文封装所述业务的标识, 生成第二报文; 或 者
所述管理单元具体用于根据所述业务的标识生成转发表表项并向所述转发面装 置发送所述转发表表项,所述转发表表项中的匹配域包括所述用户的标识,所述转发 表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置中的所述转发 表进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后的转发表对 包含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为所述转发面装 置对应的控制面装置。
从上述技术方案可以看出, 转发面装置对第一报文进行封装, 生成第二报文。所 述第二报文中包含了业务的标识。所述转发面装置向网络设备转发所述第二报文, 从 而使得所述网络设备能够根据所述第二报文中的所述业务的标识管理所述业务。上述 技术方案可以用于提高对业务进行管理的灵活性。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现 有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅 是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前 提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例提供的一种处理报文的方法的流程图;
图 2为本发明实施例提供的一种处理报文的方法的流程图;
图 3为本发明实施例提供的一种转发面装置的结构示意图;
图 4为本发明实施例提供的一种转发面装置的结构示意图;
图 5为本发明实施例提供的一种转发面装置的结构示意图;
图 6为本发明实施例提供的一种转发面装置的结构示意图;
图 7为本发明实施例提供的一种网络设备的结构示意图; 图 8为本发明实施例提供的一种网络设备的结构示意图;
图 9为本发明实施例提供的一种网络设备的结构示意图;
图 10为本发明实施例提供的一种网络设备的结构示意图;
图 11为本发明实施例提供的一种处理报文的方法的流程图;
图 12为本发明实施例提供的一种处理报文的方法的流程图;
图 13为本发明实施例提供的一种处理报文的方法的流程图;
图 14为本发明实施例提供的处理报文的方法的应用实例的示意图;
图 15为本发明实施例提供的处理报文的方法的应用实例的示意图;
图 16为本发明实施例提供的处理报文的方法的应用实例的示意图。 具体实施方式 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完 整的描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。 基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的 所有其他实施例, 都属于本发明保护的范围。 图 1为本发明实施例提供的一种处理报文的方法的流程图。 参见图 1, 所述方法 包括:
101: 转发面装置接收用户发送的第一报文, 所述第一报文中包括所述用户的标 识, 所述转发面装置中包含转发表。 所述转发面装置为用于对流量进行转发的装置。举例来说,所述转发面装置可以 是宽带远程接入服务器 (broadband remote access server, BRAS)。 所述用户可以是位于局域网的设备。举例来说,所述用户可以是位于家庭网络的 个人电脑。 所述个人电脑可以通过以太网承载的点对点协议 (Point-to-Point Protocol over Ethernet, PPPoE) 接入因特网 ( Internet )。 所述第一报文可以是因特网协议 (Internet Protocol, IP) 报文。 举例来说, 所述 因特网协议可以是因特网协议第四版(Internet Protocol version 4, IPv4), 也可以是因 特网协议第六版 ( Internet Protocol version 6, IPv6 )。 所述用户的标识用于对所述用户进行标识。举例来说,所述用户的标识可以是所 述用户的媒体接入控制(Media Access Control)协议地址, 也可以是所述用户的因特 网协议地址。所述用户的标识也可以是所述用户的 MAC协议地址与所述用户的虚拟 局域网 (virtual local area network, VLAN) 标识的结合。 举例来说, 所述转发表可以是流表, 也可以是包转发表。 转发面装置可以具有两种转发模式, 一种是流转发模式, 另一种是包转发模式。 流转发是指转发面装置根据流表对报文进行转发。流表的一个表项中用于判断报 文是否与流表的表项匹配的字段的个数为 2个或者 2个以上。举例来说,流表的一个 表项中用于判断报文是否与流表的表项匹配的字段的个数可以是 5个。 5个字段可以 分别是因特网协议地址、 目的 IP地址、源端口(Port)、 目的端口以及协议(PiOt0C0l)。 举例来说,用于判断报文是否与流表的表项匹配的字段可以是处于开放系统互连模型
(Open Systems Interconnection model, OSI model) 的数据链路 (Data Link) 层的字 段, 也可以是处于 OSI model的 IP层的字段。
包转发是指转发面装置根据包转发表对报文进行转发。包转发表的一个表项中用 于判断报文是否与包转发表的表项匹配的字段的个数为 1个。举例来说,包转发表的 表项中用于判断报文是否与包转发表的表项匹配的字段可以目的 IP地址, 也可以是 目的 MAC协议地址。 本领域的技术人员可以理解, 包转发表可以是 MAC表, 也可 以是路由表。
本领域的技术人员可以理解, 所述转发面装置可以是交换机或者路由器。
如果所述转发面装置是交换机,所述转发面装置可以是开放流交换机(OpenFlow
Switch)。关于所述开放流交换机,请参考标准制定组织(Standard Setting Organization, SSO) 开放网络基础 (Open Networking Foundation, ONF) 发布的 《开放流交换机规 范》 版本 1.0 (OpenFlow Switch Specification 1.0)。
102、 所述转发面装置根据所述用户的标识与业务的标识的对应关系以及所述第 一报文中的所述用户的标识确定所述业务的标识。
所述业务是指根据接收到的报文中的字段对接收到的报文进行处理。其中,报文 中的字段可以为 OSI model定义的第二层至第七层的信息。
举例来说, 所述业务可以是网络地址转换 (Network Address Translation, NAT) 业务、 运营商级网络地址翻译 (Carrier Grade NAT, CGN) 业务、 互联网协议安全 (Internet Protocol Security, IPSEC)业务、 视频业务、 防火墙业务、 统一资源定位符 ( Uniform / Universal Resource Locator, URL)过滤业务、点对点(Peer-to-Peer, P2P) 流量可视化业务。 其中, 视频业务可以是帧中继 (Frame Relay, FR)、 分辨率增强技 术 ( Resolution Enhancement Technology, RET )、 多文档界面 ( Multiple Document Interface, MDI) 或者内容分发网络 ( Content Delivery Network, CDN)。
举例来说, 所述业务可以是转发业务或者承诺接入速率 (committed access rate,
CAR)业务。 如果所述业务是转发业务, 所述转发业务可以是二层转发业务、三层转 发业务、 多协议标签交换 (multiprotocol label switching, MPLS) 转发业务或者虚拟 专用网 (virtual private network, VPN) 转发业务。
举例来说, 认证、 授权禾口计费 ( Authentication, Authorization and Accounting, AAA)服务器中可以保存所述对应关系。所述转发面装置可以从所述 AAA服务器获 取所述对应关系。 例如, 所述转发面装置可以通过远程用户拨号认证 (Remote Authentication Dial In User Service, Radius)协议从所述 AAA服务器获取所述对应关 系。
所述业务的标识用于对所述业务进行标识。
103、 所述转发面装置在所述第一报文中封装所述业务的标识, 生成第二报文; 所述第二报文包含所述业务的标识。所述业务的标识可以承载在所述第二报文的 净荷中, 也可以承载在所述第二报文的报文头中。
104、 所述转发面装置向网络设备转发所述第二报文, 所述第二报文用于使所述 网络设备根据所述第二报文中的所述业务的标识管理所述业务。
所述网络设备可以是所述转发面装置对应的控制面装置。所述网络设备也可以是 用于对流量进行转发的装置。例如, 所述网络设备可以是路由器。所述网络设备也可 以是能够对所述业务进行处理的业务服务器。 从上述技术方案可以看出,所述转发面装置对所述第一报文进行封装, 生成所述 第二报文。所述第二报文中包含了所述业务的标识。所述转发面装置向所述网络设备 转发所述第二报文,从而使得所述网络设备能够根据所述第二报文中的所述业务的标 识管理所述业务。 上述技术方案可以用于提高对业务进行管理的灵活性。 可选的, 图 1所示的方法中,所述网络设备根据所述第二报文中的所述业务的标 识管理所述业务可以包括: 所述网络设备根据所述第二报文中的所述业务的标识对所述第二报文执行所述 业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器。
举例来说, 如果所述业务为 NAT业务, 所述第一服务器可以是 CGN设备。 举例来说, 如果所述业务为承诺接入速率 (committed access rate, CAR) 业务, 所述第一服务器可以是能够执行 CAR业务对应的操作的路由器。
举例来说, 如果所述业务为视频增强业务,所述第一服务器可以是能够执行视频 增强业务对应的操作的交换机。
可选的, 图 1所示的方法中,所述网络设备根据所述第二报文中的所述业务的标 识管理所述业务可以包括:
所述网络设备根据所述第二报文中的所述业务的标识向能够执行所述业务的第 二服务器转发所述第二报文。
所述网络设备是能够对流量进行转发的装置。举例来说,所述网络设备可以是路 由器。所述网络设备也可以是所述转发面装置的邻居转发面装置。所述网络设备可以 是控制面装置, 或者是控制面装置的邻居控制面装置。
可选的, 图 1所示的方法中,所述网络设备根据所述第二报文中的所述业务的标 识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识生成转发表项并向所述转 发面装置发送所述转发表项,所述转发表项中的匹配域包括所述用户的标识,所述转 发表项用于使所述转发面装置根据所述转发表项对所述转发面装置中的所述转发表 进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后的转发表对包 含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为与所述转发面装 置对应的控制面装置。
在上述技术方案中, 所述业务可以为转发业务。
所述网络设备可以是控制面装置。具体实现时,所述网络设备可以是开放流控制 器 (OpenFlow Controller )。 关于所述开放流控制器, 请参考 ONF发布的 《开放流交 换机规范》 版本 1.0。
所述转发面装置可以通过控制通道与所述网络设备通信。所述控制通道可以是开 放流交换机与开放流控制器进行交互的安全通道(Secure Channel )。 关于所述安全通 道, 具体请参考 ONF发布的 《开放流交换机规范》 版本 1.0。
可选的, 图 1所示的方法中, 所述转发面装置接收用户发送的第一报文之后, 所 述方法还可以包括:所述转发面装置根据所述第一报文中的所述用户的标识对所述用 户执行用户管理操作。 所述用户管理可以是对所述用户的上线过程进行管理。举例来说,所述用户管理 可以是为所述用户分配 IP地址、 对所述用户进行认证或者对所述用户进行授权。
上述技术方案中,所述转发面装置对所述用户执行用户管理操作,所述转发面装 置不对所述用户执行业务管理操作。因此, 上述技术方案实现了用户管理和业务管理 的分离。 参阅图 2, 本发明实施例提供了一种处理报文的方法。 所述方法包括:
201: 转发面装置接收用户发送的第一报文, 所述第一报文中包括所述用户的标 识, 所述转发面装置中包含转发表。 所述转发面装置为用于对流量进行转发的装置。举例来说,所述转发面装置可以 是 BRAS。 所述用户可以是位于局域网的设备。举例来说,所述用户可以是位于家庭网络的 个人电脑。 所述个人电脑可以通过 PPPoE接入 Internet。 所述第一报文可以是 IP报文。 举例来说, 所述因特网协议可以是 IPv4, 也可以 是 IPv6。 所述用户的标识用于对所述用户进行标识。举例来说,所述用户的标识可以是所 述用户的 MAC协议地址, 也可以是所述用户的因特网协议地址。 所述用户的标识也 可以是所述用户的 MAC协议地址与所述用户的 VLAN标识的结合。 举例来说, 所述转发表可以是流表, 也可以是包转发表。 转发面装置可以具有两种转发模式, 一种是流转发模式, 另一种是包转发模式。 流转发是指转发面装置根据流表对报文进行转发。流表的一个表项中用于判断报 文是否与流表的表项匹配的字段的个数为 2个或者 2个以上。举例来说,流表的一个 表项中用于判断报文是否与流表的表项匹配的字段的个数可以是 5个。 5个字段可以 分别是因特网协议地址、 目的 IP地址、 源端口、 目的端口以及协议。 举例来说, 用 于判断报文是否与流表的表项匹配的字段可以是 OSI model的 Data Link层的字段, 也可以是处于 OSI model的 IP层的字段。
包转发是指转发面装置根据包转发表对报文进行转发。包转发表的一个表项中用 于判断报文是否与包转发表的表项匹配的字段的个数为 1个。举例来说,包转发表的 表项中用于判断报文是否与包转发表的表项匹配的字段可以目的 IP地址, 也可以是 目的 MAC协议地址。 本领域的技术人员可以理解, 包转发表可以是 MAC表, 也可 以是路由表。
本领域的技术人员可以理解, 所述转发面装置可以是交换机或者路由器。
如果所述转发面装置是交换机,所述转发面装置可以是开放流交换机。关于所述 开放流交换机, 请参考标准制定组织开放网络基础发布的《开放流交换机规范》版本 1.0。
202: 所述转发面装置向网络设备转发所述第一报文, 所述第一报文用于使所述 网络设备根据所述用户的标识与业务的标识的对应关系以及所述第一报文中的所述 用户的标识确定所述业务的标识, 并根据所述业务的标识管理所述业务。
所述业务是指根据接收到的报文中的字段对接收到的报文进行处理。其中,报文 中的字段可以为 OSI model定义的第二层至第七层的信息。
举例来说, 所述业务可以是 NAT业务、 CGN业务、 IPSEC业务、 视频业务、 防 火墙业务、 URL过滤业务、 P2P流量可视化业务。 其中, 视频业务可以是帧中继、 分 辨率增强技术、 多文档界面或者内容分发网络。
举例来说,所述业务可以是转发业务或者 CAR业务。如果所述业务是转发业务, 所述转发业务可以是二层转发业务、 三层转发业务、 MPLS转发业务或者 VPN转发 业务。
举例来说, AAA服务器中可以保存所述对应关系。 所述网络设备可以从所述
AAA服务器获取所述对应关系。 例如, 所述网络设备可以通过 Radius协议从所述 AAA服务器获取所述对应关系。
所述业务的标识用于对所述业务进行标识。
所述网络设备可以是所述转发面装置对应的控制面装置。所述网络设备也可以是 用于对流量进行转发的装置。例如, 所述网络设备可以是路由器。所述网络设备也可 以是能够对所述业务进行处理的业务服务器。 从上述技术方案可以看出,所述转发面装置将接收到的所述第一报文转发给所述 网络设备,从而使得所述网络设备能够根据所述第一报文中的所述用户的标识确定所 述业务的标识, 并根据所述业务的标识管理所述业务。上述技术方案解决了现有技术 中对业务进行管理不够灵活的技术问题。 可选的,在图 2所示的方法中,所述根据所述业务的标识管理所述业务可以包括: 所述网络设备根据所述业务的标识对所述第一报文执行所述业务对应的操作,所 述网络设备为能够执行所述业务的第一服务器。
举例来说, 如果所述业务为 NAT业务, 所述第一服务器可以是 CGN设备。 举例来说, 如果所述业务为 CAR业务, 所述第一服务器可以是能够执行 CAR 业务对应的操作的路由器。
举例来说, 如果所述业务为视频增强业务,所述第一服务器可以是能够执行视频 增强业务对应的操作的交换机。
可选的,在图 2所示的方法中,所述根据所述业务的标识管理所述业务可以包括: 所述网络设备向所述第一报文封装所述业务的标识, 生成第二报文; 所述网络设备向 第二服务器转发所述第二报文, 所述第二服务器能够执行所述业务。
举例来说, 如果所述业务为 NAT业务, 所述第二服务器可以是 CGN设备。 举例来说, 如果所述业务为 CAR业务, 所述第二服务器可以是能够执行 CAR 业务对应的操作的路由器。
举例来说, 如果所述业务为视频增强业务,所述第二服务器可以是能够执行视频 增强业务对应的操作的交换机。
可选的,在图 2所示的方法中,所述根据所述业务的标识管理所述业务可以包括: 所述网络设备根据所述业务的标识生成转发表表项并向所述转发面装置发送所述转 发表表项,所述转发表表项中的匹配域包括所述用户的标识,所述转发表表项用于使 所述转发面装置根据所述转发表表项对所述转发面装置中的所述转发表进行更新并 生成更新后的转发表,所述转发面装置能够根据所述更新后的转发表对包含所述用户 的标识的报文执行所述业务对应的操作,所述网络设备为与所述转发面装置对应的控 制面装置。
所述网络设备可以是控制面装置。具体实现时,所述网络设备可以是开放流控制 器。 关于所述开放流控制器, 请参考 ONF发布的 《开放流交换机规范》 版本 1.0。
所述转发面装置可以通过控制通道与所述网络设备通信。所述控制通道可以是开 放流交换机与开放流控制器进行交互的安全通道。 关于所述安全通道, 具体请参考 ONF发布的 《开放流交换机规范》 版本 1.0。
可选的, 在图 2所示方法中, 所述转发面装置接收用户发送的第一报文之后, 所 述方法还可以包括:所述转发面装置根据所述第一报文中的所述用户的标识对所述用 户执行用户管理操作。 所述用户管理可以是对所述用户的上线过程进行管理。举例来说,所述用户管理 可以是为所述用户分配 IP地址、 对所述用户进行认证或者对所述用户进行授权。
上述技术方案中,所述转发面装置对所述用户执行用户管理操作,所述转发面装 置不对所述用户执行业务管理操作。因此, 上述技术方案实现了用户管理和业务管理 的分离。
图 3为本发明实施例提供的一种处理报文的方法的流程图。 参见图 3, 所述方法 包括:
301: 网络设备接收转发面装置发送的第二报文, 所述第二报文通过如下途径得 至 IJ :所述转发面装置接收用户发送的第一报文,所述第一报文中包括所述用户的标识, 所述转发面装置中包含转发表;所述转发面装置根据所述用户的标识与业务的标识的 对应关系以及所述第一报文中的所述用户的标识确定所述业务的标识;所述转发面装 置在所述第一报文中封装所述业务的标识, 生成所述第二报文; 所述转发面装置向所 述网络设备发送所述第二报文。
所述转发面装置为用于对流量进行转发的装置。举例来说,所述转发面装置可以 是 BRAS。 所述用户可以是位于局域网的设备。举例来说,所述用户可以是位于家庭网络的 个人电脑。 所述个人电脑可以通过 PPPoE接入 Internet。 所述第一报文可以是 IP报文。 举例来说, 所述因特网协议可以是 IPv4, 也可以 是 IPv6。 所述用户的标识用于对所述用户进行标识。举例来说,所述用户的标识可以是所 述用户的 MAC协议地址, 也可以是所述用户的因特网协议地址。 所述用户的标识也 可以是所述用户的 MAC协议地址与所述用户的 VLAN标识的结合。 举例来说, 所述转发表可以是流表, 也可以是包转发表。 转发面装置可以具有两种转发模式, 一种是流转发模式, 另一种是包转发模式。 流转发是指转发面装置根据流表对报文进行转发。流表的一个表项中用于判断报 文是否与流表的表项匹配的字段的个数为 2个或者 2个以上。举例来说,流表的一个 表项中用于判断报文是否与流表的表项匹配的字段的个数可以是 5个。 5个字段可以 分别是因特网协议地址、 目的 IP地址、 源端口、 目的端口以及协议。 举例来说, 用 于判断报文是否与流表的表项匹配的字段可以是处于 OSI model 的数据链路层的字 段, 也可以是处于 OSI model的 IP层的字段。
包转发是指转发面装置根据包转发表对报文进行转发。包转发表的一个表项中用 于判断报文是否与包转发表的表项匹配的字段的个数为 1个。举例来说,包转发表的 表项中用于判断报文是否与包转发表的表项匹配的字段可以目的 IP地址, 也可以是 目的 MAC协议地址。 本领域的技术人员可以理解, 包转发表可以是 MAC表, 也可 以是路由表。
本领域的技术人员可以理解, 所述转发面装置可以是交换机或者路由器。
如果所述转发面装置是交换机,所述转发面装置可以是开放流交换机。关于所述 开放流交换机, 请参考标准制定组织开放网络基础发布的《开放流交换机规范》版本 1.0。
所述业务是指根据接收到的报文中的字段对接收到的报文进行处理。其中,报文 中的字段可以为 OSI model定义的第二层至第七层的信息。
举例来说, 所述业务可以是 NAT业务、 CGN业务、 IPSEC业务、 视频业务、 防 火墙业务、 URL过滤业务、 P2P流量可视化业务。 其中, 视频业务可以是帧中继、 分 辨率增强技术、 多文档界面或者内容分发网络。
举例来说,所述业务可以是转发业务或者 CAR业务。如果所述业务是转发业务, 所述转发业务可以是二层转发业务、 三层转发业务、 MPLS转发业务或者 VPN转发 业务。 举例来说, AAA服务器中可以保存所述对应关系。所述转发面装置可以从所述 AAA服务器获取所述对应关系。 例如, 所述转发面装置可以通过 Radius协议从所述 AAA服务器获取所述对应关系。
所述业务的标识用于对所述业务进行标识。
所述第二报文包含所述业务的标识。所述业务的标识可以承载在所述第二报文的 净荷中, 也可以承载在所述第二报文的报文头中。
302: 所述网络设备根据所述第二报文中的所述业务的标识管理所述业务。
所述网络设备可以是所述转发面装置对应的控制面装置。所述网络设备也可以是 用于对流量进行转发的装置。例如, 所述网络设备可以是路由器。所述网络设备也可 以是能够对所述业务进行处理的业务服务器。 从上述技术方案可以看出,所述转发面装置对所述第一报文进行封装, 生成所述 第二报文。所述第二报文中包含了所述业务的标识。所述转发面装置向所述网络设备 转发所述第二报文,从而使得所述网络设备能够根据所述第二报文中的所述业务的标 识管理所述业务。 上述技术方案可以用于提高对业务进行管理的灵活性。 可选的,在图 3所示的方法中,所述网络设备根据所述第二报文中的所述业务的 标识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识对所述第二报文执行所述 业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器。
举例来说, 如果所述业务为 NAT业务, 所述第一服务器可以是 CGN设备。 举例来说, 如果所述业务为 CAR业务, 所述第一服务器可以是能够执行 CAR 业务对应的操作的路由器。
举例来说, 如果所述业务为视频增强业务,所述第一服务器可以是能够执行视频 增强业务对应的操作的交换机。
可选的,在图 3所示的方法中,所述网络设备根据所述第二报文中的所述业务的 标识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识向能够执行所述业务的第 二服务器转发所述第二报文。
所述网络设备是能够对流量进行转发的装置。举例来说,所述网络设备可以是路 由器。所述网络设备也可以是所述转发面装置的邻居转发面装置。所述网络设备可以 是控制面装置, 或者是控制面装置的邻居控制面装置。
可选的,在图 3所示的方法中,所述网络设备根据所述第二报文中的所述业务的 标识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识生成转发表表项并向所述 转发面装置发送所述转发表表项, 所述转发表表项中的匹配域包括所述用户的标识, 所述转发表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置中的 所述转发表进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后的 转发表对包含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为所述 转发面装置对应的控制面装置。
在上述技术方案中, 所述业务可以为转发业务。
所述网络设备可以是控制面装置。具体实现时,所述网络设备可以是开放流控制 器。 关于所述开放流控制器, 请参考 ONF发布的 《开放流交换机规范》 版本 1.0。 所述转发面装置可以通过控制通道与所述网络设备通信。所述控制通道可以是开 放流交换机与开放流控制器进行交互的安全通道。 关于所述安全通道, 具体请参考 ONF发布的 《开放流交换机规范》 版本 1.0。
图 4为本发明实施例提供的一种处理报文的方法的流程图。 参见图 4, 所述方法 包括:
401: 网络设备接收转发面装置转发的第一报文, 所述第一报文通过如下途径得 至 IJ : 所述转发面装置接收用户发送的所述第一报文,所述第一报文中包括所述用户的 标识,所述转发面装置中包含转发表; 所述转发面装置向所述控制面装置转发所述第 一报文。
所述转发面装置为用于对流量进行转发的装置。举例来说,所述转发面装置可以 是 BRAS。 所述用户可以是位于局域网的设备。举例来说,所述用户可以是位于家庭网络的 个人电脑。 所述个人电脑可以通过 PPPoE接入 Internet。 所述第一报文可以是 IP报文。 举例来说, 所述因特网协议可以是 IPv4, 也可以 是 IPv6。 所述用户的标识用于对所述用户进行标识。举例来说,所述用户的标识可以是所 述用户的 MAC协议地址, 也可以是所述用户的因特网协议地址。 所述用户的标识也 可以是所述用户的 MAC协议地址与所述用户的 VLAN标识的结合。 举例来说, 所述转发表可以是流表, 也可以是包转发表。 转发面装置可以具有两种转发模式, 一种是流转发模式, 另一种是包转发模式。 流转发是指转发面装置根据流表对报文进行转发。流表的一个表项中用于判断报 文是否与流表的表项匹配的字段的个数为 2个或者 2个以上。举例来说,流表的一个 表项中用于判断报文是否与流表的表项匹配的字段的个数可以是 5个。 5个字段可以 分别是因特网协议地址、 目的 IP地址、 源端口、 目的端口以及协议。 举例来说, 用 于判断报文是否与流表的表项匹配的字段可以是处于 OSI model 的数据链路层的字 段, 也可以是处于 OSI model的 IP层的字段。
包转发是指转发面装置根据包转发表对报文进行转发。包转发表的一个表项中用 于判断报文是否与包转发表的表项匹配的字段的个数为 1个。举例来说,包转发表的 表项中用于判断报文是否与包转发表的表项匹配的字段可以目的 IP地址, 也可以是 目的 MAC协议地址。 本领域的技术人员可以理解, 包转发表可以是 MAC表, 也可 以是路由表。
本领域的技术人员可以理解, 所述转发面装置可以是交换机或者路由器。
如果所述转发面装置是交换机, 所述转发面装置可以是开放流交换机。关于所述 开放流交换机, 请参考标准制定组织开放网络基础发布的《开放流交换机规范》版本 1.0。
402: 所述网络设备根据所述用户的标识与业务的标识的对应关系以及所述第一 报文中的所述用户的标识确定所述业务的标识。
403: 所述网络设备根据所述业务的标识管理所述业务。
所述业务是指根据接收到的报文中的字段对接收到的报文进行处理。其中,报文 中的字段可以为 OSI model定义的第二层至第七层的信息。
举例来说, 所述业务可以是 NAT业务、 CGN业务、 IPSEC业务、 视频业务、 防 火墙业务、 URL过滤业务、 P2P流量可视化业务。 其中, 视频业务可以是帧中继、 分 辨率增强技术、 多文档界面或者内容分发网络。
举例来说,所述业务可以是转发业务或者 CAR业务。如果所述业务是转发业务, 所述转发业务可以是二层转发业务、 三层转发业务、 MPLS转发业务或者 VPN转发 业务。
举例来说, AAA服务器中可以保存所述对应关系。所述网络设备可以从所述 AAA 服务器获取所述对应关系。例如, 所述网络设备可以通过 Radius协议从所述 AAA服 务器获取所述对应关系。
所述业务的标识用于对所述业务进行标识。
所述网络设备可以是所述转发面装置对应的控制面装置。所述网络设备也可以是 用于对流量进行转发的装置。例如, 所述网络设备可以是路由器。所述网络设备也可 以是能够对所述业务进行处理的业务服务器。 从上述技术方案可以看出,所述转发面装置将接收到的所述第一报文转发给所述 网络设备,从而使得所述网络设备能够根据所述第一报文中的所述用户的标识确定所 述业务的标识, 并根据所述业务的标识管理所述业务。上述技术方案解决了现有技术 中对业务进行管理不够灵活的技术问题。 可选的,在图 4所示方法中,所述网络设备根据所述业务的标识管理所述业务包 括:
所述网络设备根据所述业务的标识对所述第一报文执行所述业务对应的操作,所 述网络设备为能够执行所述业务的第一服务器。
举例来说, 如果所述业务为 NAT业务, 所述第一服务器可以是 CGN设备。 举例来说, 如果所述业务为 CAR业务, 所述第一服务器可以是能够执行 CAR 业务对应的操作的路由器。
举例来说, 如果所述业务为视频增强业务,所述第一服务器可以是能够执行视频 增强业务对应的操作的交换机。
可选的,在图 4所示方法中,所述网络设备根据所述业务的标识管理所述业务包 括:
所述网络设备向所述第一报文封装所述业务的标识, 生成第二报文; 所述网络设备向第二服务器转发所述第二报文,所述第二服务器能够执行所述业 务。
举例来说, 如果所述业务为 NAT业务, 所述第二服务器可以是 CGN设备。 举例来说, 如果所述业务为 CAR业务, 所述第二服务器可以是能够执行 CAR 业务对应的操作的路由器。
举例来说, 如果所述业务为视频增强业务,所述第二服务器可以是能够执行视频 增强业务对应的操作的交换机。
可选的,在图 4所示方法中,所述网络设备根据所述业务的标识管理所述业务包 括:
所述网络设备根据所述业务的标识生成转发表表项并向所述转发面装置发送所 述转发表表项,所述转发表表项中的匹配域包括所述用户的标识,所述转发表表项用 于使所述转发面装置根据所述转发表表项对所述转发面装置中的所述转发表进行更 新并生成更新后的转发表,所述转发面装置能够根据所述更新后的转发表对包含所述 用户的标识的报文执行所述业务对应的操作,所述网络设备为所述转发面装置对应的 控制面装置。
所述网络设备可以是控制面装置。具体实现时,所述网络设备可以是开放流控制 器。 关于所述开放流控制器, 请参考 ONF发布的 《开放流交换机规范》 版本 1.0。
所述转发面装置可以通过控制通道与所述网络设备通信。所述控制通道可以是开 放流交换机与开放流控制器进行交互的安全通道。 关于所述安全通道, 具体请参考 ONF发布的 《开放流交换机规范》 版本 1.0。
图 5为本发明实施例提供的一种转发面装置。所述转发面装置可以执行图 1所示 的方法。 参见图 5, 所述装置包括: 接收单元 51, 确定单元 52, 生成单元 53和发送 单元 54。
所述接收单元 51, 用于接收用户发送的第一报文, 所述第一报文中包括所述用 户的标识, 所述转发面装置中包含转发表。
举例来说, 所述接收单元 51可以是接收器。
所述确定单元 52, 用于根据所述用户的标识与业务的标识的对应关系以及所述 接收单元 51接收的所述第一报文中的所述用户的标识确定所述业务的标识。
举例来说, 所述确定单元 52可以是网络处理器 (network processor, P)。
所述生成单元 53, 用于在所述第一报文中封装所述确定单元 52确定的所述业务 的标识, 生成第二报文。
举例来说, 所述生成单元 53可以是所述 P。
所述发送单元 54, 用于向网络设备发送所述生成单元 53生成的所述第二报文, 所述第二报文用于使所述网络设备根据所述第二报文中的所述业务的标识管理所述 业务。
举例来说, 所述发送单元 54可以是发送器。
可选的, 图 5所述装置中还可以包括: 操作单元 61, 用于根据所述接收单元 51 接收到的所述第一报文中的所述用户的标识对所述用户执行用户管理操作。关于操作 单元 61, 可以参见图 6。 图 6为本发明实施例提供的一种转发面装置的结构示意图。
图 7为本发明实施例提供的一种转发面装置的结构示意图。所述转发面装置可以 执行图 2所示的方法。 所述转发面装置包括: 接收单元 71和转发单元 72。
所述接收单元 71, 用于接收用户发送的报文, 所述报文中包括所述用户的标识, 所述转发面装置中包含转发表。
举例来说, 所述接收单元 71可以是接收器。
所述转发单元 72, 用于向网络设备转发所述接收单元 71接收的所述报文, 所述 报文用于使所述网络设备根据所述用户的标识与业务的标识的对应关系以及所述报 文中的所述用户的标识确定所述业务的标识, 并根据所述业务的标识管理所述业务。
举例来说, 所述转发单元 72可以是转发器。
可选的, 图 7所示的装置中, 还可以包括操作单元 81, 用于根据所述接收单元
71 接收到的所述报文中的所述用户的标识对所述用户执行用户管理操作。 关于操作 单元 81, 具体可以参见图 8。 图 8为本发明实施例提供的一种转发面装置的结构示意 图。
图 9为本发明实施例提供的一种网络设备的结构示意图。所述网络设备可以执行 图 3所示的方法。 参见图 9, 所述网络设备包括: 接收单元 91和管理单元 92。
所述接收单元 91, 用于接收转发面装置发送的第二报文, 所述第二报文通过如 下途径得到: 所述转发面装置接收用户发送的第一报文,所述第一报文中包括所述用 户的标识,所述转发面装置中包含转发表; 所述转发面装置根据所述用户的标识与业 务的标识的对应关系以及所述第一报文中的所述用户的标识确定所述业务的标识,并 在所述第一报文中封装所述业务的标识,得到所述第二报文; 所述转发面装置向所述 网络设备发送所述第二报文。
举例来说, 所述接收单元 91可以是接收器。
所述管理单元 92, 用于根据所述接收单元 91接收的第二报文中的所述业务的标 识管理所述业务。
举例来说, 所述管理单元 92可以是 P。
可选的, 图 9所示的网络设备中,
所述管理单元 92可以用于根据所述第二报文中的所述业务的标识对所述第二报 文执行所述业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器。
可选的, 图 9所示的网络设备中, 所述管理单元 92可以用于根据所述第二报文 中的所述业务的标识向能够执行所述业务的第二服务器转发所述第二报文。
可选的, 图 9所示的网络设备中, 所述管理单元 92可以用于根据所述第二报文 中的所述业务的标识生成转发表表项并向所述转发面装置发送所述转发表表项,所述 转发表表项中的匹配域包括所述用户的标识,所述转发表表项用于使所述转发面装置 根据所述转发表表项对所述转发面装置中的所述转发表进行更新并生成更新后的转 发表,所述转发面装置能够根据所述更新后的转发表对包含所述用户的标识的报文执 行所述业务对应的操作, 所述网络设备为所述转发面装置对应的控制面装置。
图 10为本发明实施例提供的一种网络设备的结构示意图。 所述网络设备可以执 行图 4所示的方法。 参见图 10, 所述网络设备包括: 接收单元 10, 确定单元 11和管 理单元 12。
所述接收单元 10, 用于接收转发面装置转发的第一报文, 所述第一报文通过如 下途径得到: 所述转发面装置接收用户发送的第一报文,所述第一报文中包括所述用 户的标识,所述转发面装置中包含转发表; 所述转发面装置向所述网络设备转发所述 第一报文。
所述确定单元 11, 用于根据所述用户的标识与业务的标识的对应关系以及所述 第一报文中的所述用户的标识确定所述业务的标识。
所述管理单元 12, 用于根据所述确定单元 11确定的所述业务的标识管理所述业 务。
可选的, 图 10所示的网络设备中,所述管理单元 12具体用于根据所述业务的标 识对所述报文执行所述业务对应的操作,所述网络设备为能够执行所述业务的第一服 务器。
可选的, 图 10所示的网络设备中,所述管理单元 12具体用于向所述第一报文封 装所述业务的标识, 生成第二报文。
可选的, 图 10所示的网络设备中,所述管理单元 12具体用于根据所述业务的标 识生成转发表表项并向所述转发面装置发送所述转发表表项,所述转发表表项中的匹 配域包括所述用户的标识,所述转发表表项用于使所述转发面装置根据所述转发表表 项对所述转发面装置中的所述转发表进行更新并生成更新后的转发表,所述转发面装 置能够根据所述更新后的转发表对包含所述用户的标识的报文执行所述业务对应的 操作, 所述网络设备为所述转发面装置对应的控制面装置。
图 11 为本发明实施例提供的一种处理报文的方法的流程图。 用户预先在 AAA 服务器成功注册业务。 所述网络设备为控制面装置。 参见图 11, 所述方法包括:
111: 接收用户发送的数据报文, 所述数据报文中包括用户标识; 该实施例中,转发面装置可以接收用户发送的数据报文, 也可以通过汇聚层网络 向接收用户发送的数据报文, 通常情况下, 该数据报文中包括用户标识, 当然, 还可 以包括其他参数, 比如业务标识等。 其中, 所述转发面装置可以是宽带远程接入服务器 (BRAS, broadband remote access server), 但 BRAS对用户的管理和业务管理是分离的; 当然, 所述转发面装置 也可以是路由器等; 还可以是其他具有转发功能的设备, 本实施例不作限制。
112: 如果所述数据报文与流表不匹配, 在所述数据报文中添加报文控制信息 (PCI, packet control information), 并将添加 PCI后的所述数据报文分流到控制面装 置, 以便于控制面装置按照所述用户标识对所述添加 PCI的数据报文进行业务处理。 协议控制信息 PCI : Protocol Control Information,属于协议数据单元中的一部分, 包括地址、 控制、 标志和其它任选信息, 是由对等层服务的提供者提供的一种服务。 在该实施例中, 当转发面装置接收到数据报文后,先按照报文的五元组元素判断 该数据报文是否与流表相匹配,其中,所述流表是控制面装置预先发送给转发面装置 的; 如果数据报文与流表不匹配, 在所述数据报文中添加报文控制信息 PCI, 并将添 加 PCI后的所述数据报文分流到控制面装置,以便于控制面装置按照所述用户标识对 所述数据报文进行业务处理;也就是按照对应用户注册的业务对该数据报文进行相应 处理。当然,如果数据报文与流表相匹配,则按照所述流表的地址转发所述数据报文。 其中, 所述用户标识可以包括: 用户的互联网协议(IP, Internet Protocol)地址、 媒体介入控制 (MAC, Media Access Control) 地址, 禾 P/或, MAC地址 +虚拟局域网 (VLAN, Virtual Local Area Network), 但并不限于此。 本发明实施例中,将匹配不到流表的数据报文分流到控制面装置, 由控制面装置 处理, 从而将用户管理和业务控制分流不同的设备上处理,减小了对接入网的流量压 力, 简化了管理。 还请参阅图 12,图 11为本发明实施例提供的一种处理报文的方法的第四流程图, 所述在图 11的基础上, 还可以包括: 在接收用户发送的数据报文时, 验证所述用户 是否合法, 具体包括:
121: 接收用户发送的数据报文, 所述数据报文中包括用户标识;
122: 验证所述用户是否合法, 如果合法, 执行步骤 123 ; 否则, 执行步骤 125; 其中, 由于用户与该用户注册的业务之间的关系保存在 AAA服务器中, 在转发 面装置在接收到用户发送的数据报文时, 也可以在接收到用户发送的数据报文后,先 通过 AAA服务器对该用户是否合法进行认证, 如果通过认证, 则说明该用户是合法 用户, 已成功注册的用户; 然后, 再执行步骤 123 ; 如果没有通过认证, 则说明该用 户为非法用户, 则丢弃该用户发送的数据报文。 在该实施例中的 AAA服务器, 可以独立部署, 也可以集成在转发面装置中, 本 实施例不作限制。 123: 判断所述数据报文是否与流表匹配, 如果不匹配, 执行步骤 124; 如果匹 配, 执行步骤 126; 其中,判断该数据报文是否匹配到流表中对应的表项,其判断依据可以按照报文 的五元组元素来匹配,具体的匹配的过程,对于本领域技术人员来说, 已是熟知技术, 在此不再赘述。
124: 在所述数据报文中添加报文控制信息 PCI, 并将添加 PCI后的所述数据报 文分流到控制面装置,以便于控制面装置按照所述用户标识对所述添加 PCI的数据报 文进行业务处理; 其中, 所述用户标识包括: 用户的 IP地址、媒体介入控制 MAC地址, 或, MAC 地址 +虚拟局域网 VLAN。
125: 丢弃所述数据报文;
126: 按照所述流表转发所述数据报文; 即按照匹配到流表中的目的地址转发所 述数据报文。 本发明实施例中,转发面装置在接收用户发送的数据报文后,先验证所述用户的 合法性, 如果用户合法, 再判断所述数据报文是否匹配到流表中的表项, 然后, 将匹 配不到表项的数据报文分流到控制面装置,由控制面装置按照用户标识对数据报文进 行对应的业务处理。 同时, 由于将用户管理和业务的处理处理分离, 由于数据报文可 以携带用户标识或业务标识。这样转发面装置(比如 BRAS设备)就可以聚焦于用户 管理, 而业务处理可以在控制面装置(比如业务服务器)上运行。 也就是说, 原来在 多台转发面装置(比如 BRAS)上运行的各类业务, 现在可以集中到一个控制面装置 (比如业务服务器集群或数据中心)上来运行了, 从而减小了对接入汇聚网的流量压 力。 进一步, 由于将用户管理设备部署在汇聚层, 降低了用户管理的位置, 满足高速 增长带宽的需求。 可选的, 在上述实施例中, 将添加 PCI后的数据报文分流到控制面装置之前, 所 述方法还可以包括: 获取所述用户、业务标识及业务的关联关系; 将所述业务标识添 加在所述数据报文的 PCI中; 其中, 获取的过程可以从 AAA服务器上获取; 也可以 从转发面装置中获取, 本实施例不作限制。 所述将添加 PCI的数据报文分流到控制面装置具体为:将添加业务标识后的数据 报文分流到控制面装置。 其中, 所述业务标识包括: 一层虚拟局域网 ID、 多层虚拟 局域网 ID (比如 QinQ等) 或套餐 ID; 或者, 所述业务标识表示一种业务 (比如上 网业务、 语音业务等), 或者每一比特代表一种业务。
可选的, 当所述业务标识为套餐 ID时, 在所述数据报文的 PCI中添加所述业务 标识之前, 所述方法还可以包括: 获取用户定制的套餐 ID; 将所述套餐 ID记录在用 户表的套餐字段中;
所述在数据报文的 PCI中添加所述业务标识以两种情况为例, 但并不限于此: 一种情况是:转发面装置对所述数据报文进行多协议标记交换 MPLS封装; 并判 断封装后的所述数据报文中的 MPLS标签值与预存的 MPLS标签之一是否相同, 如 果相同, 执行用户表的匹配操作; 如果成功匹配到用户表中的用户表项, 提取出所述 用户表项中的套餐字段值; 将所述套餐字段值添加到所述数据报文的 PCI中, 其中, 所述套餐字段值为套餐 ID;
另一种情况为: 转发面装置对所述数据报文进行 IP封装; 判断封装后的所述数 据报文中的 IP值与预存的 IP值之一是否相同, 如果相同, 执行用户表的匹配操作; 如果成功匹配到用户表中的用户表项,提取出所述用户表项中的套餐字段值; 将所述 套餐字段值添加到所述数据报文的 PCI中, 其中, 所述套餐字段值为套餐 ID。
可选的,上述实施例中,在接收用户发送的数据报文之前,所述方法还可以包括: 转发面装置在检测到用户上线后, 向控制面装置发送为所述用户申请 IP地址的请求; 以及在接收到所述控制面装置发送包括 IP地址的响应后, 将所述 IP地址发送给所述 用户; 以便于所述用户后续发起所述数据报文, 即后续用户发送的数据报文中包括所 述 IP地址。
本发明实施例中,将匹配不到表项的数据报文分流到控制面装置, 由控制面装置 处理, 降低了用户接入侧网络(比如汇聚网络) 的流量压力。 同时, 由于将用户管理 和业务的处理分离,由于数据报文可以携带用户标识或业务标识。这样转发面装置(比 如 BRAS设备)就可以聚焦于用户管理, 而业务处理可以在控制面装置(比如业务服 务器)上运行。 也就是说, 原来在多台转发面装置(比如 BRAS)上运行的各类业务, 现在可以集中到一个控制面装置(比如业务服务器集群或数据中心)上来运行了, 从 而减小了对接入汇聚网的流量压力。
还请参阅图 13, 图 13为本发明实施例提供的一种处理报文的方法的第五流程, 所述网络设备仍以控制面装置为例, 所述方法包括: 131: 接收转发面装置分流的数据报文, 所述数据报文中包括用户标识和报文控 制信息 PCI;
在该实施例中, 控制面装置(比如增值服务器等)接收到所述转发面装置分流的 数据报文, 对所述数据报文进行解析, 得到该数据报文中包括的用户标识。 其中, 在 转发面装置分流数据报文时, 在所述数据报文中添加了报文控制信息 PCI。
132: 按照所述用户标识对所述数据报文进行业务处理。
在该步骤中,控制面装置通过用户标识判断该数据报文属于哪个用户, 并获知所 述用户注册的业务, 并对所述数据报文进行相应的业务处理。
在本发明实施例中,控制面装置在接收到数据报文后,通过用户标识获知用户注 册的业务, 并调用该业务对所述数据报文进行处理。
可选的, 上述实施例中, 在接收到转发面装置分流的所述数据报文后, 所述方法 还可以包括: 获取所述用户标识对应的用户, 以及所述用户与注册业务的关系; 具体 可以通过授权变更消息 (COA, Change of Authorization)消息来获取用户与注册业务的 关系, 但并不限于此。
所述按照用户标识对所述数据报文进行业务处理具体包括:调用所述用户注册的 业务对所述数据报文进行业务处理。 其中, 所述用户标识包可以括: 用户的 IP地址、 媒体介入控制 MAC地址, 和 /或, MAC地址 +虚拟局域网 VLAN; 但并不限于此。
也就是说, 控制面装置先通过用户标识判断数据报文属于哪个用户, 然后, 可以 通过 COA消息从 AAA服务器中获知所述用户注册的业务, 并调用所述业务对数据 报文进行业务处理。当然, AAA服务器也可以主动通过 COA消息将所述用户与注册 的业务主动发送给控制面装置。 比如用户上线、 下线、 订阅业务发生变化时, AAA 服务器可以通过 COA消息通告控制面装置 (比如 VAS服务器), 控制面装置 (比如 VAS服务器) 更新业务和用户的关系。
可选的, 上述实施例中, 所述方法还可以包括: 控制面装置可以主动或被动从 AAA服务器中获取变化的用户与注册业务的关系; 并更新已存储的用户与注册业务 的关系。
可选的,如果所述数据报文的 PCI中包括业务标识,所述业务标识的优先级大于 用户标识;所述按照用户标识对应的用户的注册业务对所述数据报文进行业务处理具 体为: 调用所述业务标识对应的业务对所述数据报文进行业务处理。其中, 所述业务 标识可以包括: 一层虚拟局域网 ID、 多层虚拟局域网 ID或套餐 ID; 或者, 所述业 务标识表示一种业务, 或者每一比特代表一种业务。 但并不限于此。 也就是说, 只要所述数据报文中的 PCI 中包括业务标识, 控制面装置不需要向 AAA服务器获知用户注册的业务, 而是直接调用业务标识对应的业务对所述数据报 文进行处理。
其中, 所述调用所述业务标识对应的业务对所述数据报文进行业务处理具体包 括: 获取所述数据报文中对应的业务标识; 确定所述业务标识对应的具体业务; 调用 所述业务标识对应的具体业务, 对所述数据报文进行业务处理。
可选的, 上述实施例中, 在接收到所述数据报文前, 所述方法还可以包括: 控制 面装置接收到转发面装置发送为用户申请 IP地址的请求; 并向所述转发面装置发送 包括 IP地址的响应。
为例便于本领域技术人员的理解, 下面以具体的实例来说明。
实施例一
请参阅图 14, 图 14为本发明实施例提供的分流业务数据的方法的第一应用实例 的示意图,在该实施例中, 以数据报文中包括用户标识为例,转发面装置以 BRAS/SR 为例, 网络设备以 VAS服务器为例, 但并不限于此。 本实施例中报文以数据报文为 例, 但并不限于此, 其具体实现过程为:
( 1 ) 用户先向 AAA服务器注册业务, 注册成功后, AAA服务器上存储用户与 其注册业务的关系;
(2) 一个或多个用户 (本实施例以一个用户为例) 向 BRAS/SR发起数据报文, 所述数据报文中包括用户标识; 其中, 所述用户标识通常使用用户 IP地址; 当然, 也可以是 MAC地址或 MAC+VLAN作为用户标识;这些标识都是报文头的组成部分, 因此分流的数据报文天然通常情况下会包括这些信息。
(3 )所述 BRAS/SR在接收到所述数据报文后, 会通过 AAA服务器验证所述用 户是否合法, 其验证的方式对本领域技术人员来说已是熟知技术, 在此不再赘述; 对 合法的用户发送的数据报文直接执行步骤 (4);
(4) BRAS/SR先判断所述数据报文是否与接收到上层设备 (比如 VAS服务器 等) 发送的流表相匹配, 如果不匹配, 则在所述数据报文中添加报文控制信息 PCI, 并将添加 PCI后的所述数据报文分流到 VAS服务器, 即标号 (5 ), 如果匹配, 按照 所述流表转发所述数据报文, 即标号 (6)。 其中, BRAS/SR对数据报文的具体处理 过程, 详见上述, 在此不再赘述。
( 5 ) VAS服务器在接收到 BRAS/SR分流的数据报文后, 按照所述用户标识对 所述数据报文进行业务处理; (7) VAS服务器在接收到所述数据报文后, 先通过 AAA服务器获取用户和业 务关系; 从而获知由哪些业务流程来处理该用户的数据报文;
( 8) VAS服务器调用所述用户注册的业务对所述数据报文进行业务处理; 比如, 如果用户 1注册的业务包括: 业务 1、 业务 2和业务 3等, 用户 2注册的 业务包括: 业务 1、 业务 2和业务 3等。
在该实施例中, VAS服务器在接收到分流的数据报文中; 先通过 AAA服务器获 取用户和业务关系, 从而获知其管理哪些业务处理用户的数据报文; 当 BRAS/SR将 数据报文 (数据流) 引到 VAS服务器时, VAS服务器解析获得数据报文中携带的用 户标识,通过用户标识来判断此数据报文属于哪个用户, 从而调用相应业务对此数据 报文进行处理。
在上述实施例一中, 用户上线、 下线或订阅的业务发生变化时, AAA服务器可 以通过 COA消息通告 VAS服务器, VAS服务器更新业务和用户的关系。
实施例二
请参阅图 15, 图 15为本发明实施例提供的分流业务数据的方法的第二应用实例 的示意图, 在该实施例中, 以数据报文中包括业务标识为例, 但是, 在实际应用中, 数据包括用户标识和业务标识,其业务标识的优先级高于用户标识为例,转发面装置 以 BRAS/SR为例,网络设备以 VAS服务器为例,但并不限于此。其具体实现过程为: ( 1 ) 用户先向 AAA服务器注册业务, 注册成功后, AAA服务器上存储用户与 其注册业务的关系;
(2) 一个或多个用户 (本实施例以多个用户为例) 向 BRAS/SR发起数据报文, 所述数据报文中包括业务标识; 其中, 所述业务标识可以是一层虚拟局域网 ID (vlanid)、 多层虚拟局域网 ID (比如 QinQ) 或套餐 ID; 或者, 所述业务标识也可 以是一种业务或业务集合, 或者业务标识的每个比特位表示一种业务。
(3 )所述 BRAS/SR接收到所述用户发送的数据报文前, 如果 BRAS/SR在检测 到用户上线时, 获得该用户和业务标识及业务的关联关系, 这种关系即可以从 AAA 服务器上获取, 也可以由 BRAS/SR自己管理;
(4) 所述 BRAS/SR在接收到所述用户发送的数据报文时, 先判断所述数据报 文是否与接收到上层设备 (比如 VAS服务器等) 发送的流表相匹配, 如果不匹配, 则在所述数据报文中添加报文控制信息 PCI, 以及在所述 PCI中添加业务标识, 并将 添加业务标识后的所述数据报文分流到 VAS服务器, 即标号 (5 ); 如果匹配, 按照 所述流表转发所述数据报文, 即标号 (6); 也就是说, 在该过程中, 当合法用户的数据报文进入 BRAS/SR时, BRAS/SR会 将与流表不匹配的数据报文打上业务标识,并将打上业务标识的数据报文分流到 VAS 服务器处理。
(7) VAS服务器在接收到所述数据报文中, 识别所述数据报文的业务标识, 并 按照其维护的业务标识与具体业务的关系,按照所述业务标识将数据报文分发给各个 业务进行相应的处理。 比如,业务标识 1对应的业务包括业务 1、业务 2和业务 3等, 业务标识 2对应的业务包括: 业务 2、 业务 3和业务 4等。
下面分别说明用一个 vlanid、 多个 vlanid、 套餐 ID来表示业务标识的过程; 1 ) 如果用一个 vlanid来表示业务标识
在该实施例中,可以直接以分流报文所携带的 vlanid作为业务标识,这种方式不 用专门增加字段来作为业务标识; 如果用户需要更改业务(套餐),只需要更改 vlanid 就可以实现, 操作简单。
另外, 在该实施例中, 如果用户通过门户 (Portal) 服务器或其他管理工具选择 好业务 (或套餐) 后, Portal服务器会给本地上线设备 (或软件) 设置一个 vlanid, 表明用户以此 vlan来上线; 而该用户后续发起的数据报文中携带该 vlanid。
当然, BRAS/SR也可以在接口下配置 user- vlan any-other方式上线; 用户经过认 证、 授权后上线, 用户报文会携带 vlanid;
需要说明的是, 当用户更改业务(或套餐) 时, 只需客户端软件(或靠近客户端 设备) 变更 vlanid, 即可。
2) 如果用多个 vlanid (比如 QinQ) 来表示业务标识, 其实现过程同理一个 vlan 上线, 其不同之处为: 既可以把外层 vlanid作为业务标识, 也可以把内层 vlan作为 业务标识; 或是二者组合作为业务标识。
3 ) 如果用套餐 ID来表示业务标识:
该实现方式需要在分流的数据报文的头部增加一个保存套餐 ID值的字段: 这种 方式需要修改流表逻辑及 P微码, 其过程为:
1、 在需要分流的数据报文的 PCI(packet control information)头部预留出套餐 ID 字段, 比如 2个字节, 3个字节等;
2、 P微码增加分流使能寄存器标志位; P微码中的用户表增加套餐 ID字段; 增加存储和流表逻辑相同的 MPLS标签值的寄存器。
3、用户通过 Portal服务器或其他管理工具选择好业务套餐后, Portal服务器把套 餐 ID和用户关联关系记录到 AAA服务器中; 4、 当用户上线后, 先通过 AAA服务器进行认证授权, 这时 AAA服务器将用户 定制的套餐 ID下发给 BRAS/SR; BRAS/SR将套餐 ID记录到转发面 NP微码的用户 表中。
5、 数据报文进入流表逻辑, 流表逻辑查询流表, 并对没有命中流表的数据报文 进行封装。 即增加 PCI头部及 MPLS封装, 并将封装后的数据报文发送给 P微码, P微码判断分流使能,如果数据报文的 MPLS标签值和寄存器里的标签值之一相同, 则走 P新流程, 即偏移数据报文到原始报文头部(即进入流表逻辑时的报文头部), 执行用户表匹配操作, 如果匹配到用户表中相应的用户表项; 则取出表项中相应的套 餐字段值(即套餐 ID值);将所述套餐字段值填写到数据报文中 PCI头部中的套餐字 段上; 如果数据报文的 MPLS标签值和寄存器里的标签值之一不相同, 按照 P微码 的现有流程实现; 其中, P微码的现有流程对于本领域技术人员来说已是熟知技术, 在此不再赘述。
另外, 本发明实施例中, 对数据报文的封装, 还可以使用 IP封装的方式处理流 程, 其与 MPLS封装方式相似, 具体详见上述, 在此不再赘述。
实施例三
请参阅图 16, 图 16为本发明实施例提供的分流业务数据的方法的第三应用实例 的示意图,该实施例三与实施例一类似,其不同之处在于, 由 VAS服务器提供 DHCP 服务功能。 当路由器(比如 BRAS/SR)收到用户上线请求后, 向 AAA服务器进行认 证, 如果认证通过, 然后向 VAS服务器申请 IP地址, IP地址申请成功后, VAS服务 器将包括 IP地址的消息发送给 AAA服务器,将 AAA服务器记录 IP地址和用户的关 系。 VAS服务器也将所述 IP地址发送给路由器,路由器再将所述 IP地址发送给用户; 之后, 用户可以向路由器 (比如 BRAS/SR) 发送数据报文中, 所述数据报文携带该 IP地址, 而路由器 (比如 BRAS/SR) 在接收到所述数据报文的处理过程与实施例一 同, 具体详见上述实施例一, 在此不再赘述。
由上述实施例中可知, 当用户管理和业务解耦到不同设备后,用户管理设备可以 在汇聚层里部署, 靠近用户, 用户间的流量可以在用户管理设备终结, 减小对接入汇 聚网的流量压力; 以及, 当用户和业务解耦后, 用户管理设备可以部署在汇聚层接入 侧。往上层面就不用感知到用户信息, 减少业务开通需要感知用户信息的工作量; 以 及, 当用户和业务分离后, 业务由服务器处理, 可以集中部署和独立升级, 不影响用 户在线使用体验。
由上述实施例可知, 本发明实施例与现有技术相比, 具有下述优点: 1、 实现业务部署和用户管理分离, 简化管理: 也就是说, 现有技术要求用户管 理和业务处理在同一台设备(比如 BRAS或 SR设备)上。 本发明实施例可以使用户 管理和业务处理分离。 由于数据报文可以携带用户标识或 /业务标识。 这样 BRAS设 备就可以聚焦于用户管理, 而业务处理可以在业务服务器上运行。特别的, 原来在多 台 BRAS上运行的各类业务,现在可以集中到一个业务服务器集群或数据中心上来运 行了。
2、 使运营商可以快速部署增值业务: 也就是说, 由于本发明技术可以使业务独 立于用户管理部署,这样新的增值业务开发出来后,可以完全不用改变用户部署部分, 即不用升级 BRAS设备。只需在业务服务器上改变服务处理即可,而且是可以在线部 署新业务, 不会影响老业务的运行。
3、 使网络演进可以实现降低用户管理位置, 满足高速增长的带宽需求: 也就是 说, 由于用户管理和业务部署分离后, 用户管理可以从现在 BRAS路由器位置, 即网 络汇聚层, 下移到用户接入层位置。这一层更加接近用户, 使得对用户的带宽管理更 加灵活有效。
需要说明的是, 在本文中, 诸如第一和第二等之类的关系术语仅仅用来将一 个实体或者操作与另一个实体或操作区分开来, 而不一定要求或者暗示这些实体 或操作之间存在任何这种实际的关系或者顺序。 而且, 术语 "包括" 、 "包含" 或者其任何其他变体意在涵盖非排他性的包含, 从而使得包括一系列要素的过 程、 方法、 物品或者设备不仅包括那些要素, 而且还包括没有明确列出的其他要 素, 或者是还包括为这种过程、 方法、 物品或者设备所固有的要素。 在没有更多 限制的情况下, 由语句 "包括一个…… " 限定的要素, 并不排除在包括所述要素 的过程、 方法、 物品或者设备中还存在另外的相同要素。 本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单 元及算法步骤, 能够以电子硬件、 或者计算机软件和电子硬件的结合来实现。这些功 能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专 业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实 现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、 装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中, 应该理解到, 所揭露的系统、 装置和方法, 可 以通过其它的方式实现。 例如, 以上所描述的装置实施例仅仅是示意性的, 例如, 所 述单元的划分, 可以仅仅为一种逻辑功能划分, 实际实现时可以有另外的划分方式, 例如多个单元或组件可以结合或者可以集成到另一个系统, 或一些特征可以忽略, 或 不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过 一些接口, 装置或单元的间接耦合或通信连接, 可以是电性, 机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显 示的部件可以是或者也可以不是物理单元, 即可以位于一个地方, 或者也可以分布到 多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例 方案的目的。
另外, 在本发明各个实施例中的各功能单元可以集成在一个处理单元中, 也可以 是各个单元单独物理存在, 也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以 存储在一个计算机可读取存储介质中。基于这样的理解,本发明的技术方案本质上或 者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现 出来, 该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机 设备(可以是个人计算机, 服务器, 或者网络设备等)执行本发明各个实施例所述方 法的全部或部分步骤。 而前述的存储介质包括: U盘、 移动硬盘、 只读存储器(英文 缩写为 ROM,英文全称为 Read-Only Memory )、随机存取存储器(英文缩写为 RAM, 英文全称为 Random Access Memory )、 磁碟或者光盘等各种可以存储程序代码的介 质。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范围并不局限于此, 任 何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易想到变化或替换, 都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应所述以权利要求的保 护范围为准。

Claims

权 利 要 求
1、 一种处理报文的方法, 其特征在于, 包括:
转发面装置接收用户发送的第一报文, 所述第一报文中包括所述用户的标 识, 所述转发面装置中包含转发表;
所述转发面装置根据所述用户的标识与业务的标识的对应关系以及所述第 一报文中的所述用户的标识确定所述业务的标识;
所述转发面装置在所述第一报文中封装所述业务的标识, 生成第二报文; 所述转发面装置向网络设备发送所述第二报文,所述第二报文用于使所述网 络设备根据所述第二报文中的所述业务的标识管理所述业务。
2、 根据权利要求 1所述的方法, 其特征在于, 所述网络设备根据所述第二 报文中的所述业务的标识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识对所述第二报文执行 所述业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器; 或者 所述网络设备根据所述第二报文中的所述业务的标识向能够执行所述业务 的第二服务器转发所述第二报文; 或者
所述网络设备根据所述第二报文中的所述业务的标识生成转发表表项并向 所述转发面装置发送所述转发表表项,所述转发表表项中的匹配域包括所述用户 的标识,所述转发表表项用于使所述转发面装置根据所述转发表表项对所述转发 面装置中的所述转发表进行更新并生成更新后的转发表,所述转发面装置能够根 据所述更新后的转发表对包含所述用户的标识的报文执行所述业务对应的操作, 所述网络设备为与所述转发面装置对应的控制面装置。
3、 根据权利要求 1或 2所述的方法, 其特征在于, 所述转发面装置接收用 户发送的第一报文之后, 所述方法还包括:
所述转发面装置根据所述第一报文中的所述用户的标识对所述用户执行用 户管理操作。
4、 一种处理报文的方法, 其特征在于, 包括:
转发面装置接收用户发送的第一报文, 所述第一报文中包括所述用户的标 识, 所述转发面装置中包含转发表; 所述转发面装置向网络设备转发所述第一报文,所述第一报文用于使所述网 络设备根据所述用户的标识与业务的标识的对应关系以及所述第一报文中的所 述用户的标识确定所述业务的标识, 并根据所述业务的标识管理所述业务。
5、 根据权利要求 4所述的方法, 其特征在于, 所述根据所述业务的标识管 理所述业务包括:
所述网络设备根据所述业务的标识对所述第一报文执行所述业务对应的操 作, 所述网络设备为能够执行所述业务的第一服务器; 或者
所述网络设备向所述第一报文封装所述业务的标识, 生成第二报文; 所述网络设备向第二服务器转发所述第二报文,所述第二服务器能够执行所 述业务; 或者
所述网络设备根据所述业务的标识生成转发表表项并向所述转发面装置发 送所述转发表表项, 所述转发表表项中的匹配域包括所述用户的标识, 所述转发 表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置中的所述 转发表进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后的 转发表对包含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为 与所述转发面装置对应的控制面装置。
6、 根据权利要求 4或 5所述的方法, 其特征在于, 所述转发面装置接收用 户发送的第一报文之后, 所述方法还包括:
所述转发面装置根据所述第一报文中的所述用户的标识对所述用户执行用 户管理操作。
7、 一种处理报文的方法, 其特征在于, 包括:
网络设备接收转发面装置发送的第二报文, 所述第二报文通过如下途径得 到:
所述转发面装置接收用户发送的第一报文, 所述第一报文中包括所 述用户的标识, 所述转发面装置中包含转发表;
所述转发面装置根据所述用户的标识与业务的标识的对应关系以及 所述第一报文中的所述用户的标识确定所述业务的标识;
所述转发面装置在所述第一报文中封装所述业务的标识, 生成所述 第二报文;
所述转发面装置向所述网络设备发送所述第二报文; 所述网络设备根据所述第二报文中的所述业务的标识管理所述业务。
8、 根据权利要求 7所述的方法, 其特征在于, 所述网络设备根据所述第二 报文中的所述业务的标识管理所述业务包括:
所述网络设备根据所述第二报文中的所述业务的标识对所述第二报文执行 所述业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器; 或者 所述网络设备根据所述第二报文中的所述业务的标识向能够执行所述业务 的第二服务器转发所述第二报文; 或者
所述网络设备根据所述第二报文中的所述业务的标识生成转发表表项并向 所述转发面装置发送所述转发表表项,所述转发表表项中的匹配域包括所述用户 的标识,所述转发表表项用于使所述转发面装置根据所述转发表表项对所述转发 面装置中的所述转发表进行更新并生成更新后的转发表,所述转发面装置能够根 据所述更新后的转发表对包含所述用户的标识的报文执行所述业务对应的操作, 所述网络设备为所述转发面装置对应的控制面装置。
9、 一种处理报文的方法, 其特征在于, 包括:
网络设备接收转发面装置转发的第一报文, 所述第一报文通过如下途径得 到:
所述转发面装置接收用户发送的所述第一报文, 所述第一报文中包 括所述用户的标识, 所述转发面装置中包含转发表;
所述转发面装置向所述控制面装置转发所述第一报文; 所述网络设备根据所述用户的标识与业务的标识的对应关系以及所述第一 报文中的所述用户的标识确定所述业务的标识;
所述网络设备根据所述业务的标识管理所述业务。
10、根据权利要求 9所述的方法, 其特征在于, 所述网络设备根据所述业务 的标识管理所述业务包括:
所述网络设备根据所述业务的标识对所述第一报文执行所述业务对应的操 作, 所述网络设备为能够执行所述业务的第一服务器; 或者 所述网络设备向所述第一报文封装所述业务的标识, 生成第二报文; 所述网络设备向第二服务器转发所述第二报文,所述第二服务器能够执行所 述业务; 或者
所述网络设备根据所述业务的标识生成转发表表项并向所述转发面装置发 送所述转发表表项, 所述转发表表项中的匹配域包括所述用户的标识, 所述转发 表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置中的所述 转发表进行更新并生成更新后的转发表,所述转发面装置能够根据所述更新后的 转发表对包含所述用户的标识的报文执行所述业务对应的操作,所述网络设备为 所述转发面装置对应的控制面装置。
11、 一种转发面装置, 其特征在于, 包括:
接收单元, 用于接收用户发送的第一报文, 所述第一报文中包括所述用户的 标识, 所述转发面装置中包含转发表;
确定单元,用于根据所述用户的标识与业务的标识的对应关系以及所述接收 单元接收的所述第一报文中的所述用户的标识确定所述业务的标识;
生成单元, 用于在所述第一报文中封装所述确定单元确定的所述业务的标 识, 生成第二报文;
发送单元, 用于向网络设备发送所述生成单元生成的所述第二报文, 所述第 二报文用于使所述网络设备根据所述第二报文中的所述业务的标识管理所述业 务。
12、 根据权利要求 11所述的转发面装置, 其特征在于, 还包括: 操作单元,用于根据所述接收单元接收到的所述第一报文中的所述用户的标 识对所述用户执行用户管理操作。
13、 一种转发面装置, 其特征在于, 包括:
接收单元, 用于接收用户发送的报文, 所述报文中包括所述用户的标识, 所 述转发面装置中包含转发表;
转发单元, 用于向网络设备转发所述接收单元接收的所述报文, 所述报文用 于使所述网络设备根据所述用户的标识与业务的标识的对应关系以及所述报文 中的所述用户的标识确定所述业务的标识, 并根据所述业务的标识管理所述业 务。
14、 根据权利要求 13所述的转发面装置, 其特征在于, 包括:
操作单元,用于根据所述接收单元接收到的所述报文中的所述用户的标识对 所述用户执行用户管理操作。
15、 一种网络设备, 其特征在于, 包括:
接收单元, 用于接收转发面装置发送的第二报文, 所述第二报文通过如下途 径得到:
所述转发面装置接收用户发送的第一报文, 所述第一报文中包括所 述用户的标识, 所述转发面装置中包含转发表;
所述转发面装置根据所述用户的标识与业务的标识的对应关系以及 所述第一报文中的所述用户的标识确定所述业务的标识, 并在所述第一 报文中封装所述业务的标识, 得到所述第二报文;
所述转发面装置向所述网络设备发送所述第二报文; 管理单元, 用于根据所述第二报文中的所述业务的标识管理所述业务。
16、 根据权利要求 15所述的网络设备, 其特征在于,
所述管理单元用于根据所述第二报文中的所述业务的标识对所述第二报文 执行所述业务对应的操作, 所述网络设备为能够执行所述业务的第一服务器; 或 者
所述管理单元用于根据所述第二报文中的所述业务的标识向能够执行所述 业务的第二服务器转发所述第二报文; 或者
所述管理单元用于根据所述第二报文中的所述业务的标识生成转发表表项 并向所述转发面装置发送所述转发表表项,所述转发表表项中的匹配域包括所述 用户的标识,所述转发表表项用于使所述转发面装置根据所述转发表表项对所述 转发面装置中的所述转发表进行更新并生成更新后的转发表,所述转发面装置能 够根据所述更新后的转发表对包含所述用户的标识的报文执行所述业务对应的 操作, 所述网络设备为所述转发面装置对应的控制面装置。
17、 一种网络设备, 其特征在于, 包括: 接收单元, 用于接收转发面装置转发的第一报文, 所述第一报文通过如下途 径得到:
所述转发面装置接收用户发送的第一报文, 所述第一报文中包括所 述用户的标识, 所述转发面装置中包含转发表;
所述转发面装置向所述网络设备转发所述第一报文; 确定单元,用于根据所述用户的标识与业务的标识的对应关系以及所述第一 报文中的所述用户的标识确定所述业务的标识;
管理单元, 用于根据所述确定单元确定的所述业务的标识管理所述业务。
18、 根据权利要求 17所述的网络设备, 其特征在于,
所述管理单元具体用于根据所述业务的标识对所述报文执行所述业务对应 的操作, 所述网络设备为能够执行所述业务的第一服务器; 或者
所述管理单元具体用于向所述第一报文封装所述业务的标识, 生成第二报 文; 或者
所述管理单元具体用于根据所述业务的标识生成转发表表项并向所述转发 面装置发送所述转发表表项, 所述转发表表项中的匹配域包括所述用户的标识, 所述转发表表项用于使所述转发面装置根据所述转发表表项对所述转发面装置 中的所述转发表进行更新并生成更新后的转发表,所述转发面装置能够根据所述 更新后的转发表对包含所述用户的标识的报文执行所述业务对应的操作,所述网 络设备为所述转发面装置对应的控制面装置。
PCT/CN2012/084368 2012-11-09 2012-11-09 处理报文的方法、转发面装置及网络设备 WO2014071605A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN201280002721.5A CN104040966B (zh) 2012-11-09 2012-11-09 处理报文的方法、转发面装置及网络设备
EP12888170.3A EP2908480B1 (en) 2012-11-09 2012-11-09 Method, forwarding-plane apparatus, and network device for processing packet
PCT/CN2012/084368 WO2014071605A1 (zh) 2012-11-09 2012-11-09 处理报文的方法、转发面装置及网络设备
US14/707,752 US10044574B2 (en) 2012-11-09 2015-05-08 Packet processing method, forwarding plane device and network device
US16/042,710 US10771356B2 (en) 2012-11-09 2018-07-23 Packet processing method, forwarding plane device and network device
US16/984,731 US11552863B2 (en) 2012-11-09 2020-08-04 Packet processing method, forwarding plane device and network device
US18/146,777 US11902116B2 (en) 2012-11-09 2022-12-27 Packet processing method, forwarding plane device and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/084368 WO2014071605A1 (zh) 2012-11-09 2012-11-09 处理报文的方法、转发面装置及网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/707,752 Continuation US10044574B2 (en) 2012-11-09 2015-05-08 Packet processing method, forwarding plane device and network device

Publications (1)

Publication Number Publication Date
WO2014071605A1 true WO2014071605A1 (zh) 2014-05-15

Family

ID=50683940

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/084368 WO2014071605A1 (zh) 2012-11-09 2012-11-09 处理报文的方法、转发面装置及网络设备

Country Status (4)

Country Link
US (4) US10044574B2 (zh)
EP (1) EP2908480B1 (zh)
CN (1) CN104040966B (zh)
WO (1) WO2014071605A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105556906A (zh) * 2014-05-30 2016-05-04 华为技术有限公司 一种网络地址转换方法及装置
WO2017071399A1 (zh) * 2015-10-29 2017-05-04 中国移动通信集团公司 一种业务数据的传输方法、装置、控制设备及通信系统
CN110896371A (zh) * 2016-02-14 2020-03-20 华为技术有限公司 一种虚拟网络设备及相关方法
WO2020135574A1 (zh) * 2018-12-28 2020-07-02 中兴通讯股份有限公司 报文处理方法、装置、控制面设备和计算机存储介质
CN112671661A (zh) * 2020-12-24 2021-04-16 广州市网优优信息技术开发有限公司 物联网数据传输方法及系统
CN115150216A (zh) * 2021-03-31 2022-10-04 中国电信股份有限公司 流量转发系统、方法和vBRAS的控制面设备
US11575427B2 (en) 2018-09-21 2023-02-07 Zte Corporation Configuration signaling execution control method and apparatus, and device, system and storage medium
US20230344702A1 (en) * 2020-12-29 2023-10-26 Huawei Technologies Co., Ltd. Master/backup negotiation method and device

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103685586B (zh) * 2012-09-07 2018-09-04 中兴通讯股份有限公司 一种实现地址共享的方法、装置和系统
CN105264841B (zh) * 2013-06-26 2018-03-13 华为技术有限公司 报文转发系统、设备和方法
CN105099913B (zh) * 2014-04-21 2018-07-20 新华三技术有限公司 一种报文转发方法及设备
WO2016026798A1 (en) * 2014-08-18 2016-02-25 Nokia Solutions And Networks Oy Group communication service enabler security
CN104883302B (zh) * 2015-03-18 2018-11-09 华为技术有限公司 一种数据包转发的方法、装置及系统
CN106302841A (zh) * 2015-05-18 2017-01-04 中兴通讯股份有限公司 一种运营商级网络地址转换的方法及装置
CN114205926B (zh) * 2015-09-29 2024-01-16 株式会社宙连 控制装置和存储介质
CN105392171B (zh) * 2015-10-29 2018-11-06 京信通信系统(中国)有限公司 一种报文转发方法及其转发设备
CN105763465B (zh) * 2016-01-29 2019-01-22 新华三技术有限公司 一种分布式组合流量控制方法及装置
CN107786613B (zh) * 2016-08-30 2020-05-12 新华三技术有限公司 宽带远程接入服务器bras转发实现方法和装置
CN107995124B (zh) * 2016-10-26 2020-10-09 新华三技术有限公司 流量调度方法及装置
CN108270690B (zh) * 2016-12-30 2021-12-24 北京华为数字技术有限公司 控制报文流量的方法和装置
CN108259632B (zh) * 2017-05-24 2020-02-11 新华三技术有限公司 一种cgn实现方法及装置
CN109428792B (zh) * 2017-08-29 2021-12-14 中兴通讯股份有限公司 一种用户宽带接入处理的方法及装置、设备
CN107770012A (zh) * 2017-10-23 2018-03-06 中国联合网络通信集团有限公司 一种宽带接入方法、装置及虚拟宽带远程接入服务器系统
CN109922005B (zh) * 2017-12-13 2022-08-19 中兴通讯股份有限公司 一种负载分担方法、装置和系统、计算机可读存储介质
CN113055191B (zh) * 2019-12-27 2023-08-01 中兴通讯股份有限公司 一种转发方法、装置、宽带远程接入服务器的转发面
WO2021190029A1 (zh) * 2020-03-24 2021-09-30 中兴通讯股份有限公司 实现运营商级网络地址转换的方法、装置和系统
CN113542188B (zh) * 2020-04-13 2023-04-18 华为技术有限公司 报文检测的方法以及第一网络设备
US11411873B1 (en) * 2020-11-24 2022-08-09 Juniper Networks, Inc. Proactive and on-demand destination next hop information sharing mechanism between a forwarding plane and a service plane
CN115250187B (zh) * 2021-04-27 2023-06-23 中盈优创资讯科技有限公司 一种提高NetFlow中继设备快速过滤的方法及装置
CN113473465B (zh) * 2021-07-13 2023-04-28 蒋溢 基于无线融合网络分流的专网细粒度访问控制方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060423A (zh) * 2006-05-29 2007-10-24 华为技术有限公司 接入网多边缘选择方法及系统
CN101729308A (zh) * 2009-06-01 2010-06-09 中兴通讯股份有限公司 一种策略控制的方法和装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735169B1 (en) * 1999-07-02 2004-05-11 Cisco Technology, Inc. Cascading multiple services on a forwarding agent
US20050086328A1 (en) * 2003-10-17 2005-04-21 Landram Fredrick J. Self configuring mobile device and system
US8050275B1 (en) * 2003-11-18 2011-11-01 Cisco Technology, Inc. System and method for offering quality of service in a network environment
CN100454849C (zh) * 2005-08-05 2009-01-21 华为技术有限公司 下一代网络中的故障检测方法
GB2443229B (en) * 2006-08-23 2009-10-14 Cramer Systems Ltd Capacity management for data networks
US8090877B2 (en) * 2008-01-26 2012-01-03 Citrix Systems, Inc. Systems and methods for fine grain policy driven cookie proxying
US8339959B1 (en) * 2008-05-20 2012-12-25 Juniper Networks, Inc. Streamlined packet forwarding using dynamic filters for routing and security in a shared forwarding plane
CN101436998A (zh) * 2008-12-16 2009-05-20 华为技术有限公司 报文转发路径获取方法和报文转发装置
JP5081847B2 (ja) * 2009-02-20 2012-11-28 株式会社日立製作所 マルチプロセッサによるパケット処理装置およびパケット処理方法
CN102217251B (zh) * 2009-09-21 2013-09-11 华为技术有限公司 一种数据转发方法、数据处理方法、系统以及相关设备
US8549117B2 (en) * 2009-11-05 2013-10-01 Telefonaktiebolaget L M Ericsson (Publ) Method for address translator traversal in 3GPP networks
EP2469945A1 (en) * 2010-12-23 2012-06-27 British Telecommunications public limited company WLAN location services
JP5618886B2 (ja) * 2011-03-31 2014-11-05 株式会社日立製作所 ネットワークシステムおよび計算機振り分け装置、計算機振り分け方法
US9178846B1 (en) * 2011-11-04 2015-11-03 Juniper Networks, Inc. Deterministic network address and port translation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060423A (zh) * 2006-05-29 2007-10-24 华为技术有限公司 接入网多边缘选择方法及系统
CN101729308A (zh) * 2009-06-01 2010-06-09 中兴通讯股份有限公司 一种策略控制的方法和装置

Non-Patent Citations (1)

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

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105556906A (zh) * 2014-05-30 2016-05-04 华为技术有限公司 一种网络地址转换方法及装置
WO2017071399A1 (zh) * 2015-10-29 2017-05-04 中国移动通信集团公司 一种业务数据的传输方法、装置、控制设备及通信系统
CN110896371A (zh) * 2016-02-14 2020-03-20 华为技术有限公司 一种虚拟网络设备及相关方法
US11381507B2 (en) 2016-02-14 2022-07-05 Huawei Technologies Co., Ltd. Virtual network device and related method
CN110896371B (zh) * 2016-02-14 2022-07-26 华为技术有限公司 一种虚拟网络设备及相关方法
US11575427B2 (en) 2018-09-21 2023-02-07 Zte Corporation Configuration signaling execution control method and apparatus, and device, system and storage medium
WO2020135574A1 (zh) * 2018-12-28 2020-07-02 中兴通讯股份有限公司 报文处理方法、装置、控制面设备和计算机存储介质
US11575592B2 (en) 2018-12-28 2023-02-07 Zte Corporation Message processing method and apparatus, control-plane device, and computer storage medium
CN112671661A (zh) * 2020-12-24 2021-04-16 广州市网优优信息技术开发有限公司 物联网数据传输方法及系统
US20230344702A1 (en) * 2020-12-29 2023-10-26 Huawei Technologies Co., Ltd. Master/backup negotiation method and device
CN115150216A (zh) * 2021-03-31 2022-10-04 中国电信股份有限公司 流量转发系统、方法和vBRAS的控制面设备
CN115150216B (zh) * 2021-03-31 2024-03-19 中国电信股份有限公司 流量转发系统、方法和vBRAS的控制面设备

Also Published As

Publication number Publication date
EP2908480A1 (en) 2015-08-19
US10771356B2 (en) 2020-09-08
US20210021490A1 (en) 2021-01-21
US10044574B2 (en) 2018-08-07
EP2908480A4 (en) 2015-11-18
US11902116B2 (en) 2024-02-13
CN104040966B (zh) 2017-04-26
CN104040966A (zh) 2014-09-10
US20180331921A1 (en) 2018-11-15
US11552863B2 (en) 2023-01-10
US20230216754A1 (en) 2023-07-06
EP2908480B1 (en) 2017-10-25
US20150244590A1 (en) 2015-08-27

Similar Documents

Publication Publication Date Title
US11552863B2 (en) Packet processing method, forwarding plane device and network device
US9621372B2 (en) Title-enabled networking
CN112583647B (zh) 用于针对有线和无线节点的公共控制协议的方法和设备
EP2866389B1 (en) Method and device thereof for automatically finding and configuring virtual network
US7036143B1 (en) Methods and apparatus for virtual private network based mobility
US8830834B2 (en) Overlay-based packet steering
US8619779B2 (en) Scalable architecture for enterprise extension in a cloud topology
CN107196813B (zh) 用于自组织二层企业网络架构的方法和装置
US20160381015A1 (en) Authentication for VLAN Tunnel Endpoint (VTEP)
US20100217882A1 (en) Method, system and apparatus for accessing a Layer-3 session
US20150150073A1 (en) Smart Virtual Private Network
US9210223B2 (en) Providing differentiated network services and priorities to VPN routers/clients
WO2013056585A1 (zh) 一种虚拟私云接入认证方法及相关装置
WO2013113171A1 (zh) 流识别的方法、设备和系统
WO2017016473A1 (zh) 用于进行隧道检测的方法、装置及系统
EP3664403B1 (en) User authentication of bras under architecture of mutually separated forwarding and control
CN107733764B (zh) 虚拟可扩展局域网隧道的建立方法、系统以及相关设备
WO2016058463A1 (zh) 业务功能链中协议报文的处理方法、系统及业务功能节点
CN109922005B (zh) 一种负载分担方法、装置和系统、计算机可读存储介质
CN106911817B (zh) 一种通告PPPoE服务端MAC地址变化的方法和装置
WO2018068768A1 (zh) 宽带业务控制方法及装置
CN107995085B (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: 12888170

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2012888170

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2012888170

Country of ref document: EP