CN110943897A - PPPoE data message transmission method, device, equipment and storage medium - Google Patents

PPPoE data message transmission method, device, equipment and storage medium Download PDF

Info

Publication number
CN110943897A
CN110943897A CN201910951180.4A CN201910951180A CN110943897A CN 110943897 A CN110943897 A CN 110943897A CN 201910951180 A CN201910951180 A CN 201910951180A CN 110943897 A CN110943897 A CN 110943897A
Authority
CN
China
Prior art keywords
pppoe
flow table
port information
message
data message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201910951180.4A
Other languages
Chinese (zh)
Inventor
尹彬
吴琪
严思韵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhongchang (hangzhou) Information Technology Co Ltd
China Mobile Communications Group Co Ltd
Original Assignee
Zhongchang (hangzhou) Information Technology Co Ltd
China Mobile Communications Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zhongchang (hangzhou) Information Technology Co Ltd, China Mobile Communications Group Co Ltd filed Critical Zhongchang (hangzhou) Information Technology Co Ltd
Priority to CN201910951180.4A priority Critical patent/CN110943897A/en
Publication of CN110943897A publication Critical patent/CN110943897A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854Wide area networks, e.g. public data networks
    • H04L12/2856Access arrangements, e.g. Internet access
    • H04L12/2858Access network architectures
    • H04L12/2859Point-to-point connection between the data network and the subscribers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854Wide area networks, e.g. public data networks
    • H04L12/2856Access arrangements, e.g. Internet access
    • H04L12/2869Operational details of access network equipments
    • H04L12/287Remote access server, e.g. BRAS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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
    • H04L45/7453Address table lookup; Address filtering using hashing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching

Abstract

The embodiment of the invention relates to the technical field of communication, and discloses a PPPoE data message transmission method, which comprises the following steps: acquiring port information of each PPPoE client; reporting the port information to an SDN controller; receiving an IP message and a flow table issued by the SDN controller according to the port information; matching the IP message flow table according to the flow table; and if the matching is successful, converting the IP message into a PPPoE data message according to the flow table, and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table. The embodiment of the invention also provides a PPPoE data message transmission device, equipment and a storage medium. The PPPoE data message transmission method, the PPPoE data message transmission device, the PPPoE data message transmission equipment and the PPPoE data message transmission storage medium provided by the embodiment of the invention can improve the efficiency of transmitting the PPPoE data message by a BRAS system.

Description

PPPoE data message transmission method, device, equipment and storage medium
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for transmitting a PPPoE data packet.
Background
PPPoE (Point-to-Point Protocol Over Ethernet ) is an important user internet Access Protocol in BRAS (Broadband Remote Access Server).
When a plurality of PPPoE users communicate, because the BRAS system can not obtain the information of the user port, a two-layer protocol stack generally needs to be constructed, the port information is learned by using a two-layer switch, and the PPPoE data message can be sent to a corresponding client after the port information is learned, so that the BRAS has the disadvantages of large resource consumption and low efficiency when transmitting the PPPoE data message.
Disclosure of Invention
The embodiment of the invention aims to provide a PPPoE data message transmission method, a device, equipment and a storage medium, so that the efficiency of transmitting the PPPoE data message by a BRAS is improved.
In order to solve the above technical problem, an embodiment of the present invention provides a PPPoE data packet transmission method, including the following steps: acquiring port information of each PPPoE client; reporting the port information to an SDN controller; receiving an IP message and a flow table issued by the SDN controller according to the port information; matching the IP message flow table according to the flow table; and if the matching is successful, converting the IP message into a PPPoE data message according to the flow table, and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table.
The embodiment of the present invention further provides a PPPoE data packet transmission device, including: the port information acquisition module is used for acquiring the port information of each PPPoE client; the port information reporting module is used for reporting the port information to the SDN controller; the flow table issuing receiving module is used for receiving the IP message and receiving a flow table issued by the SDN controller according to the port information; the receiving message matching module is used for matching the IP message with the flow table according to the flow table; and the data message sending module is used for converting the IP message into a PPPoE data message according to the flow table and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table if the matching is successful.
An embodiment of the present invention further provides a network device, including: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executable by the at least one processor to enable the at least one processor to perform the PPPoE data message transmission method.
The embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the PPPoE data message transmission method is implemented.
Compared with the prior art, the method and the device have the advantages that the switch reports the acquired port information to the SDN controller, so that the SDN controller can issue the flow table according to the port information, the switch can convert the received IP message into the PPPoE data message according to the port information in the flow table, and the PPPoE data message is forwarded to the correct PPPoE client. Due to the fact that the switch can directly conduct PPPoE data message transmission processing according to the flow table issued by the SDN controller, a thick and heavy two-layer protocol stack does not need to be built, the BRAS system is light, resource consumption is low, and efficiency is improved.
In addition, reporting the port information to the SDN controller includes: storing the port information of the PPPoE client in an effective load of a user datagram protocol according to a preset format; and reporting the user datagram protocol to the SDN controller. The switch reports the port information of the PPPoE client through a user datagram protocol, only one time of sending is needed when the PPPoE client initiates dialing authentication, and the switch does not need to report regularly or an SDN controller actively inquires, so that the switch is light in weight, and the processing efficiency of the switch can be improved.
In addition, sending the PPPoE data packet to the target PPPoE client corresponding to the port information in the flow table includes: acquiring an output port corresponding to port information of the PPPoE data message in a flow table; and sending the PPPoE data message to the target PPPoE client according to the output port. By acquiring the output port corresponding to the port information of the PPPoE data message in the flow table, the PPPoE data message can be forwarded to the correct PPPoE client according to the acquired output port.
In addition, the flow table includes an IP address of the target PPPoE client; and matching the IP message according to the flow table, wherein the method comprises the following steps: acquiring a destination IP address in the IP message; and matching the target IP address with the IP address of the target PPPoE client in the flow table. By acquiring the destination IP address in the IP message, matching can be realized according to the destination IP address, so that whether the IP message is a PPPoE data message which needs to be forwarded to the PPPoE client side is judged.
In addition, the flow table includes a media access control address of the target PPPoE client; sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table, including: modifying the target medium access control address of the PPPoE data message into a medium access control address of a target PPPoE client in the flow table according to the flow table; and sending the PPPoE data message after the medium access control address is modified to a target PPPoE client corresponding to the port information in the flow table. The target medium access address of the PPPoE data message is modified into the medium access control address of the target PPPoE client in the flow table according to the flow table, so that correct data transmission between the switch and the target PPPoE client can be ensured.
In addition, converting the IP packet into a PPPoE data packet according to the flow table includes: and encapsulating the IP message according to the flow table to obtain a PPPoE data message. The successfully matched IP message is encapsulated through the flow table, and the IP message can be converted into a PPPoE data message, so that the converted message can be sent to a PPPoE client side, and the PPPoE data message can be forwarded.
In addition, acquiring the port information of each PPPoE client includes: acquiring port information and a medium access control address of each PPPoE client according to the dialing information of each PPPoE client; reporting the port information to an SDN controller, including: and reporting the port information and the medium access control address of each PPPoE client to the SDN controller through a user datagram protocol. By acquiring the port information and the medium access control address of each PPPoE client and reporting the port information and the medium access control address to the SDN controller through a user datagram protocol, the SDN controller can acquire the corresponding medium access control address according to the port information, so that the SDN controller can issue a flow table according to the medium access control address and the port information of the PPPoE client, and a switch is ensured to correctly transmit the PPPoE data message to a target PPPoE client.
Drawings
One or more embodiments are illustrated by the corresponding figures in the drawings, which are not meant to be limiting.
FIG. 1 is a schematic diagram of PPPoE communication in the prior art;
fig. 2 is a schematic flow chart of a PPPoE data packet transmission method according to a first embodiment of the present invention;
fig. 3 is another schematic flow chart of a PPPoE data packet transmission method according to the first embodiment of the present invention;
fig. 4 is a schematic diagram of storing port information of a PPPoE client in payload of UDP;
fig. 5 is a block diagram of a PPPoE data packet transfer device according to a second embodiment of the present invention;
fig. 6 is a schematic structural diagram of a network device in a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments.
The first embodiment of the invention relates to a PPPoE data message transmission method, which comprises the steps of obtaining port information of each PPPoE client; reporting the port information to an SDN controller; receiving an IP message and a flow table issued by the SDN controller according to the port information; matching the IP message flow table according to the flow table; and if the matching is successful, converting the IP message into a PPPoE data message according to the flow table, and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table. The switch reports the acquired port information to the SDN controller, so that the SDN controller can issue a flow table according to the port information, and the switch can convert the received IP message into a PPPoE data message according to the port information in the flow table and forward the PPPoE data message to a correct PPPoE client. Because the exchanger carries out the transmission processing of PPPoE data messages according to the flow table, a thick and heavy two-layer protocol stack is not required to be constructed, the resource consumption of the BRAS system is low, and the efficiency is improved.
It should be noted that the execution subject of the PPPoE data packet transmission method provided by the embodiment of the present invention may be, but is not limited to, a switch in a BRAS system, and optionally, the switch is a switch supporting an openflow protocol. The openflow is a network communication protocol. The following description will be made by taking a switch as an example.
Please refer to fig. 1, which is a diagram illustrating PPPoE communication in the prior art. The dashed path labeled 1 represents a message sent from the PPPoE client 2 to the PPPoE client 1, and the dashed path labeled 2 represents a downlink message returned from the network to the PPPoE client 1. For the switch, it is necessary to know the port information of the PPPoE client to forward the two messages to the correct PPPoE client. The traditional method is to use a two-layer switch and a three-layer switch to learn the port information of the PPPoE client, but the scheme needs to construct a two-layer protocol stack, so that the BRAS system becomes thicker and heavier, and the resource consumption is large.
Fig. 2 shows a schematic flow diagram of a PPPoE data packet transmission method according to an embodiment of the present invention, which includes the following steps:
s101: and acquiring port information of each PPPoE client.
The port information of the PPPoE client refers to information of an ingress port of the PPPoE client. Alternatively, the port information of the PPPoE client may be obtained through a process of dialing the PPPoE client.
For example, the PPPoE client initiates dialing to the switch, when the PPPoE client sends a PPPoE control message to the switch, the BRAS system records the ingress port information of the PPPoE client, and the switch acquires the ingress port information of the PPPoE client recorded by the BRAS system.
Alternatively, the switch may obtain information of an ingress port of the PPPoE client by querying the flow table. For example, when the switch receives a message, it determines whether the ethertype of the message is 0x8863, if so, it determines that the received message is a PPPoE control message, and then extracts the information of the ingress port of the PPPoE client.
Because each PPPoE client needs a process of dialing the switch when initiating communication, the switch can acquire the port information of each PPPoE client.
S102: and reporting the port information to the SDN controller.
The SDN controller is a controller in a BRAS system and is mainly used for managing and controlling services and issuing flow table design. Optionally, the BRAS system is a Software Defined Network (SDN) based BRAS system.
Specifically, the switch reports the acquired port information of each PPPoE client to the SDN controller. Optionally, when the switch reports the port information of each PPPoE client to the SDN controller, a message in a preset format agreed with the SDN controller may be reported to the SDN controller, so that when the SDN controller receives the message in the preset format, the port information of each PPPoE client may be extracted correspondingly. The message in the preset format may be specifically set according to actual needs, and is not specifically limited herein.
S103: and receiving the IP message and a flow table issued by the SDN controller according to the port information.
It should be understood that the IP message includes a general IP message and an IP message converted from a PPPoE data message.
Optionally, after the SDN controller obtains the port information of each PPPoE client reported by the switch, a flow table is formed according to the port information of the PPPoE client and sent to the switch. The flow table includes, besides the port information of the PPPoE client, other information that can be matched with the IP packet, so that the switch can determine whether the received IP packet is an IP packet converted from a PPPoE data packet that needs to be forwarded to the PPPoE client according to the issued flow table. The information matched with the IP packet may be, for example, a destination IP address of the packet.
S104: and performing flow table matching on the received IP message according to the flow table.
Specifically, the switch performs flow table matching on the received IP packet according to information matching the IP packet in the flow table, and determines whether the IP packet is an IP packet converted from a PPPoE data packet.
In a specific example, the flow table includes an IP address of a target PPPoE client, where the target PPPoE client refers to a PPPoE client to which a received IP packet is directed. In S104, performing flow table matching on the received IP packet according to the flow table, which may specifically include: and acquiring a destination IP address in the IP message, and matching the destination IP address with the IP address of the target client in the flow table.
Specifically, the switch extracts a destination IP address in the IP packet, matches the extracted destination IP address with an IP address of a target client, and determines whether the extracted destination IP address and the target client are consistent. If the extracted destination IP address is consistent with the IP address of the target client, indicating that the received IP message is the IP message converted from the PPPoE data message; if not, the received IP message is indicated to be a common IP message.
By acquiring the destination IP address in the IP message, matching can be realized according to the destination IP address, so that whether the IP message is a PPPoE data message which needs to be forwarded to the PPPoE client side is judged.
S105: and if the matching is successful, converting the received IP message into a PPPoE data message according to the flow table, and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table.
Specifically, if the matching is successful, it indicates that the received IP packet is an IP packet converted from a PPPoE data packet, and the switch converts the received IP packet into the PPPoE data packet according to the flow table, and sends the converted PPPoE data packet to the target PPPoE client according to the port information in the flow table.
In a specific example, in S105, sending the PPPoE data packet to the target PPPoE client corresponding to the port information in the flow table may include: acquiring an output port corresponding to port information of the PPPoE data message in a flow table; and sending the PPPoE data message to the target PPPoE client according to the output port.
Optionally, the output port corresponding to the port information is located in the action domain of the flow table, and the switch may acquire the output port corresponding to the PPPoE data packet according to the port information in the action domain of the flow table, and forward the PPPoE data packet to a correct PPPoE client, that is, a target PPPoE client, according to the acquired output port.
Because the flow table received by the switch includes the port information of the PPPoE client, and the matching information in the flow table can correspond to the information matched with the IP message one by one, after the matching is successful, the switch converts the IP message into the PPPoE message on one hand, and on the other hand, acquires the output port corresponding to the PPPoE data message according to the port information in the matched flow table, and then sends the PPPoE data message to the target PPPoE client according to the output port.
By acquiring the output port corresponding to the port information of the PPPoE data message in the flow table, the PPPoE data message can be forwarded to the correct PPPoE client according to the acquired output port.
In a specific example, the flow table includes the MAC address of the target PPPoE client; in S105, sending the PPPoE data packet to the target PPPoE client corresponding to the port information in the flow table may include: and modifying the target MAC address of the PPPoE data message into the MAC address of the target PPPoE client in the flow table according to the flow table, and sending the PPPoE data message with the modified MAC address to the target PPPoE client corresponding to the port information in the flow table.
The MAC address of the target PPPoE client in the flow table may be acquired from the authentication server by the SDN controller, and the authentication server may acquire the MAC address in the process of initiating authentication to the authentication server through the PPPoE client. The MAC address of the target PPPoE client in the flow table may also be obtained through other obtaining ways, which is not limited herein.
Optionally, modifying the destination MAC address of the PPPoE data packet may also be implemented by setting an action field in the flow table, and the switch may modify the destination MAC address of the PPPoE data packet to the MAC address of the target PPPoE client in the flow table according to the action field in the flow table.
Specifically, the switch modifies the destination MAC address of the successfully matched PPPoE data packet into the MAC address of the target PPPoE client in the flow table according to the received action field in the flow table, and then sends the PPPoE data packet with the modified MAC address to the target PPPoE client corresponding to the port information in the flow table.
It should be understood that, since the destination MAC address of the IP packet is a virtual MAC address when the switch receives the IP packet, modifying the destination MAC address of the PPPoE data packet into the MAC address of the target PPPoE client in the flow table according to the flow table can ensure correct data transmission between the switch and the target PPPoE client.
Compared with the prior art, the PPPoE data message transmission method provided by the embodiment of the invention has the advantages that the switch reports the acquired port information to the SDN controller, so that the SDN controller can issue the flow table according to the port information, the switch can convert the received IP message into the PPPoE data message according to the flow table, and the PPPoE data message is forwarded to the correct PPPoE client according to the port information in the flow table. Due to the fact that the switch can directly conduct PPPoE data message transmission processing according to the flow table issued by the SDN controller, a thick and heavy two-layer protocol stack does not need to be built, the BRAS system is light, resource consumption is low, and efficiency is improved.
In a specific example, in S105, converting the IP packet into a PPPoE data packet according to the flow table may include: and encapsulating the IP message according to the flow table to obtain a PPPoE data message.
It should be understood that the IP message is different from the PPPoE data message in that the PPPoE data message has one more header than the IP, wherein the header includes a session id (session id), a code type, and a protocol type of the PPPoE client. Alternatively, the information of the header may be obtained from an authentication server, and the authentication server may obtain the information of the header when the PPPoE client initiates authentication to the authentication server.
Optionally, when the PPPoE data packet is sent from the PPPoE client to the network, a decapsulation process is included, that is, a packet header of the PPPoE data packet is removed, so that the PPPoE data packet is converted into an IP packet and then forwarded to the network.
The successfully matched IP message is encapsulated through the flow table, and the IP message can be converted into a PPPoE data message, so that the converted message can be sent to a PPPoE client side, and the PPPoE data message can be forwarded.
In a specific example, as shown in fig. 3, another flow diagram of a PPPoE data packet transmission method according to an embodiment of the present invention specifically includes the following steps:
s201: and acquiring port information of each PPPoE client.
S202: and storing the port information of the PPPoE client in an effective load of a user datagram protocol according to a preset format.
S203: and reporting the user datagram protocol to the SDN controller.
S204: and receiving the IP message and a flow table issued by the SDN controller according to the port information.
S205: and performing flow table matching on the received IP message according to the flow table.
S206: and if the matching is successful, converting the received IP message into a PPPoE data message according to the flow table, and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table.
Wherein, S201, S204, S205 and S206 are the same as above, and are not described again here.
In S202, the preset format may be set according to actual needs, and is not limited specifically here. The preset format is a format agreed by the switch and the SDN controller. Optionally, the preset format may include vendor type, port information, and other information. The manufacturer type is, for example, an identifier of china mobile, china telecom or china unicom, and, for example, the manufacturer type of china mobile is cmhi.
A User Datagram Protocol (UDP) is a simple connectionless Datagram oriented transport layer Protocol, and a switch stores acquired port information of each PPPoE client in a payload (payload) of the UDP. Please refer to fig. 4, which is a diagram illustrating port information of a PPPoE client is stored in a payload of a UDP. Wherein, Vendor is the manufacturer type, and port is the port information of the PPPoE client. There may be other required information between Vendor and port, such as the MAC address of the PPPoE client.
Specifically, the switch stores the acquired port information of the PPPoE client in payload of the UDP, and reports the port information to the SDN controller through the UDP. Optionally, the SDN controller determines according to a vendor type in the preset format, and if the vendor type is consistent with a predefined vendor type, for example, cmhi, extracts port information of the PPPoE client in the UDP, and then issues a flow table according to the port information of the PPPoE client.
It should be noted that the port information of the PPPoE client may also be obtained by setting a mode of regularly reporting by the switch or actively querying by the SDN controller, but regularly reporting or actively querying by the BRAS controller consumes more system and bandwidth resources. The port information of the PPPoE client is reported through UDP, and the port information is only required to be sent once when the PPPoE client initiates dialing authentication, so that the weight is light, and the processing efficiency of the switch can be improved.
In a specific example, in S101, acquiring port information of each PPPoE client may include: acquiring port information and an MAC address of each PPPoE client according to the dialing information of each PPPoE client; in S102, reporting the port information to the SDN controller may include: and reporting the port information and the MAC address of each PPPoE client to the SDN controller through a user datagram protocol.
When each PPPoE client initiates dialing to the switch, the switch can acquire the port information of each PPPoE client and also can acquire the MAC address of the PPPoE client, so that the switch can report the port information and the MAC address of each PPPoE client to the SDN controller at the same time, and during reporting, the port information and the MAC address of each PPPoE client can be simultaneously stored in a User Datagram Protocol (UDP). Alternatively, it may be stored in payload of UDP. After the report of the switch, the SDN controller may obtain port information and an MAC address of each PPPoE client.
Alternatively, the SDN controller may store the port information and MAC address correspondence of each PPPoE client in a HASH table of a database in the BRAS system, with the MAC address as a key and the port information as a value. Therefore, after the SDN controller acquires the MAC address and the IP address of the PPPoE client from the authentication server, the HASH table can be inquired according to the MAC address to obtain corresponding port information, and then the flow table is issued according to the IP address, the port information and the MAC address, so that the switch can forward the PPPoE data message to the correct PPPoE client according to the flow table.
By acquiring the port information and the MAC address of each PPPoE client and reporting the port information and the MAC address to the SDN controller through a user datagram protocol, the SDN controller can acquire the corresponding MAC address according to the port information, so that the SDN controller can issue a flow table according to the MAC address and the port information of the PPPoE client, and a switch is ensured to correctly transmit the PPPoE data message to a target PPPoE client.
The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the steps contain the same logical relationship, which is within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.
A second embodiment of the present invention relates to a PPPoE data packet transmission device, as shown in fig. 5, including: the system comprises a port information acquisition module 301, a port information reporting module 302, a flow distribution table receiving module 303, a received message matching module 304 and a data message sending module 305.
A port information obtaining module 301, configured to obtain port information of each PPPoE client;
a port information reporting module 302, configured to report port information to an SDN controller;
a flow table issuing receiving module 303, configured to send the IP packet and receive a flow table issued by the SDN controller according to the port information;
a received message matching module 304, configured to perform flow table matching on the IP message according to the flow table;
and a data packet sending module 305, configured to, if the matching is successful, convert the IP packet into a PPPoE data packet according to the flow table, and send the PPPoE data packet to a target PPPoE client corresponding to the port information in the flow table.
Further, the port information reporting module 302 is further configured to:
storing the port information of the PPPoE client in an effective load of a user datagram protocol according to a preset format;
and reporting the user datagram protocol to the SDN controller.
Further, the data packet sending module 305 is further configured to:
modifying an output port of the PPPoE data message into a port corresponding to the port information according to the flow table;
and sending the PPPoE data message to the target PPPoE client according to the modified output port.
Further, the flow table includes an IP address of the target PPPoE client, and the received packet matching module 304 is further configured to:
acquiring a destination IP address in the IP message;
and matching the target IP address with the IP address of the target PPPoE client in the flow table.
Further, the flow table includes a media access control address of the target PPPoE client; the data messaging module 305 is further configured to:
modifying the target medium access control address of the PPPoE data message into a medium access control address of a target PPPoE client in the flow table according to the flow table;
and sending the PPPoE data message after the medium access control address is modified to a target PPPoE client corresponding to the port information in the flow table.
Further, the data packet sending module 305 is further configured to:
and encapsulating the IP message according to the flow table to obtain a PPPoE data message.
Further, the port information obtaining module 301 is further configured to: acquiring port information and a medium access control address of each PPPoE client according to the dialing information of each PPPoE client; the port information reporting module 302 is further configured to: and reporting the port information and the medium access control address of each PPPoE client to the SDN controller through a user datagram protocol.
It should be understood that this embodiment is an example of the apparatus corresponding to the first embodiment, and may be implemented in cooperation with the first embodiment. The related technical details mentioned in the first embodiment are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment.
It should be noted that each module referred to in this embodiment is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, and may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, elements that are not so closely related to solving the technical problems proposed by the present invention are not introduced in the present embodiment, but this does not indicate that other elements are not present in the present embodiment.
A third embodiment of the invention relates to a network device, as shown in fig. 6, comprising at least one processor 401; and a memory 402 communicatively coupled to the at least one processor 401; the memory 402 stores instructions executable by the at least one processor 401, and the instructions are executed by the at least one processor 401, so that the at least one processor 401 can execute the PPPoE data packet transmission method.
Where the memory 402 and the processor 401 are coupled by a bus, which may include any number of interconnected buses and bridges that couple one or more of the various circuits of the processor 401 and the memory 402 together. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 401 may be transmitted over a wireless medium via an antenna, which may receive the data and transmit the data to the processor 401.
The processor 401 is responsible for managing the bus and general processing and may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 402 may be used to store data used by processor 401 in performing operations.
A fourth embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program realizes the above-described method embodiments when executed by a processor.
That is, those skilled in the art can understand that all or part of the steps in the method of the foregoing embodiments may be implemented by a program to instruct related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.

Claims (10)

1. A PPPoE data message transmission method is characterized by comprising the following steps:
acquiring port information of each PPPoE client;
reporting the port information to an SDN controller;
receiving an IP message and a flow table issued by the SDN controller according to the port information;
performing flow table matching on the IP message according to the flow table;
and if the matching is successful, converting the IP message into a PPPoE data message according to the flow table, and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table.
2. The PPPoE data packet transmission method according to claim 1, wherein said reporting the port information to the SDN controller comprises:
storing the port information of the PPPoE client in an effective load of a user datagram protocol according to a preset format;
and reporting the user datagram protocol to an SDN controller.
3. The PPPoE data packet transmission method according to claim 1, wherein said sending said PPPoE data packet to a target PPPoE client corresponding to said port information in said flow table comprises:
acquiring an output port corresponding to the port information of the PPPoE data message in the flow table;
and sending the PPPoE data message to a target PPPoE client according to the output port.
4. The PPPoE data packet transmission method according to claim 1, wherein said flow table includes an IP address of said target PPPoE client;
the performing flow table matching on the IP message according to the flow table comprises:
acquiring a destination IP address in the IP message;
and matching the target IP address with the IP address of the target PPPoE client in the flow table.
5. The PPPoE data packet transmission method according to claim 1, wherein said flow table comprises a media access control address of said target PPPoE client;
the sending the PPPoE data packet to the target PPPoE client corresponding to the port information in the flow table includes:
modifying the target medium access control address of the PPPoE data message into the medium access control address of the target PPPoE client in the flow table according to the flow table;
and sending the PPPoE data message after the medium access control address is modified to a target PPPoE client corresponding to the port information in the flow table.
6. The PPPoE data packet transmission method according to claim 1, wherein said converting said IP packet into a PPPoE data packet according to said flow table comprises:
and encapsulating the IP message according to the flow table to obtain a PPPoE data message.
7. The PPPoE data packet transmission method according to any one of claims 1 to 6, wherein said obtaining port information of each PPPoE client comprises:
acquiring port information and a medium access control address of each PPPoE client according to dialing information of each PPPoE client;
reporting the port information to an SDN controller includes:
and reporting the port information and the medium access control address of each PPPoE client to an SDN controller through a user datagram protocol.
8. A PPPoE data message transmission device, comprising:
the port information acquisition module is used for acquiring the port information of each PPPoE client;
a port information reporting module, configured to report the port information to an SDN controller;
the flow table issuing receiving module is used for receiving the IP message and receiving a flow table issued by the SDN controller according to the port information;
the receiving message matching module is used for matching the flow table of the IP message according to the flow table;
and the data message sending module is used for converting the IP message into a PPPoE data message according to the flow table and sending the PPPoE data message to a target PPPoE client corresponding to the port information in the flow table if the matching is successful.
9. A network device, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a PPPoE data message transmission method as recited in any one of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out a PPPoE data message transmission method according to any one of claims 1 to 7.
CN201910951180.4A 2019-10-08 2019-10-08 PPPoE data message transmission method, device, equipment and storage medium Pending CN110943897A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910951180.4A CN110943897A (en) 2019-10-08 2019-10-08 PPPoE data message transmission method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910951180.4A CN110943897A (en) 2019-10-08 2019-10-08 PPPoE data message transmission method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN110943897A true CN110943897A (en) 2020-03-31

Family

ID=69906075

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910951180.4A Pending CN110943897A (en) 2019-10-08 2019-10-08 PPPoE data message transmission method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110943897A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111614565A (en) * 2020-05-19 2020-09-01 青岛海信宽带多媒体技术有限公司 Message forwarding method and gateway

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125191A (en) * 2013-04-23 2014-10-29 华为技术有限公司 Processing method, device and system of point to point protocol over Ethernet
CN105429876A (en) * 2015-11-04 2016-03-23 上海斐讯数据通信技术有限公司 SDN-based data forwarding method
CN106161249A (en) * 2016-06-07 2016-11-23 杭州迪普科技有限公司 The processing method and processing device of PPPoE message
CN107819602A (en) * 2016-09-14 2018-03-20 中国电信股份有限公司 Customer flow distribution method and system
US20200099546A1 (en) * 2017-06-12 2020-03-26 Deutsche Telekom Ag Method and system for establishing a service path in a communications network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125191A (en) * 2013-04-23 2014-10-29 华为技术有限公司 Processing method, device and system of point to point protocol over Ethernet
CN105429876A (en) * 2015-11-04 2016-03-23 上海斐讯数据通信技术有限公司 SDN-based data forwarding method
CN106161249A (en) * 2016-06-07 2016-11-23 杭州迪普科技有限公司 The processing method and processing device of PPPoE message
CN107819602A (en) * 2016-09-14 2018-03-20 中国电信股份有限公司 Customer flow distribution method and system
US20200099546A1 (en) * 2017-06-12 2020-03-26 Deutsche Telekom Ag Method and system for establishing a service path in a communications network

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111614565A (en) * 2020-05-19 2020-09-01 青岛海信宽带多媒体技术有限公司 Message forwarding method and gateway
CN111614565B (en) * 2020-05-19 2022-05-10 青岛海信宽带多媒体技术有限公司 Message forwarding method and gateway

Similar Documents

Publication Publication Date Title
EP3585095B1 (en) Method and device for controlling qos, smf, upf, ue, pcf and an
US8228848B2 (en) Method and apparatus for facilitating push communication across a network boundary
EP3836577B1 (en) Session management method and device for user groups
CN104137518B (en) Internet protocol connection in Service-Oriented Architecture Based bus
US20170244792A1 (en) Power-Line Carrier Terminal Control Apparatus, System, and Method
US11356410B2 (en) Packet transmission method and device, and computer readable storage medium
CN106790675A (en) Load-balancing method, equipment and system in a kind of cluster
EP2813057B1 (en) Method and apparatus for discovering wireless devices
CN110808948B (en) Remote procedure calling method, device and system
CN114556893B (en) System and method for communication between incompatible radio and virtual baseband units
US10182132B2 (en) Method, apparatus and system for communication between OpenFlow device and IP network device
CN112968965B (en) Metadata service method, server and storage medium for NFV network node
GB2592315A (en) Methods and systems for sending packets through a plurality of tunnels
CN110943897A (en) PPPoE data message transmission method, device, equipment and storage medium
CN115622833B (en) Device management method, system, device and medium for cross-terminal communication based on bus
WO2021031092A1 (en) Packet processing method and network device
CN101465783B (en) Connection method, device and connection network bridge for isomery household network appliances
KR101996337B1 (en) Switch processing method, controller, switch, and switch processing system
CN106850871B (en) Method for realizing DHCP server with single physical network card and multiple VLANs
CN116095197A (en) Data transmission method and related device
WO2018068238A1 (en) Cable media converter management method, apparatus and system
EP3562194B1 (en) Method for identifying at least one network slice configuration of a mobile network, communication system, and automation system
CN111654390A (en) Data transmission method, device, terminal equipment and storage medium
KR101396995B1 (en) Method for converting protocol in a gateway, and gateway thereof
CN109768905A (en) A kind of method, system, equipment and the storage medium of PPPoE message transmissions

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20200331

RJ01 Rejection of invention patent application after publication