WO2022088747A1 - 业务数据传输方法、通信网络、业务接收设备及存储介质 - Google Patents

业务数据传输方法、通信网络、业务接收设备及存储介质 Download PDF

Info

Publication number
WO2022088747A1
WO2022088747A1 PCT/CN2021/104916 CN2021104916W WO2022088747A1 WO 2022088747 A1 WO2022088747 A1 WO 2022088747A1 CN 2021104916 W CN2021104916 W CN 2021104916W WO 2022088747 A1 WO2022088747 A1 WO 2022088747A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
mac address
receiving device
service receiving
devices
Prior art date
Application number
PCT/CN2021/104916
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 EP21884486.8A priority Critical patent/EP4216509A4/en
Publication of WO2022088747A1 publication Critical patent/WO2022088747A1/zh
Priority to US18/307,163 priority patent/US20230262369A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0003—Details
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/76—Routing in software-defined topologies, e.g. routing between virtual machines

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a service data transmission method, a communication network, a service receiving device, and a storage medium.
  • the first port of the service sending device has a first internet protocol (Internet protocol, IP) address.
  • the second port of the service receiving device has a second IP address.
  • IP internet protocol
  • the service sending device needs to obtain a media access control (media access control, MAC) address of the second port.
  • the specific process is as follows: the service sending device broadcasts the ARP request in the network segment of the first IP address through an address resolution protocol (ARP). The request carries the second IP address.
  • ARP address resolution protocol
  • the service receiving device receives the ARP request through the second port with the second IP address, and sends the MAC address of the second port to the service sending device.
  • the ARP request from the service sending device can only reach the port on the same network segment as the first IP address.
  • the service receiving device cannot receive the above-mentioned ARP request through the second port, and therefore will not send the MAC address of the second port to the service sending device.
  • the service sending device cannot obtain the MAC address of the second port, and the service data cannot be successfully sent.
  • each pair of service receiving devices and service sending devices In order to successfully send service data, it is necessary to ensure that each pair of service receiving devices and service sending devices have a first IP address and a second IP address in the same network segment.
  • each service sending device needs to have multiple first IP addresses, and thus needs to have multiple first ports.
  • Each service receiving device needs to have multiple second IP addresses, and thus needs to have multiple second ports.
  • Each device has multiple ports, and the communication network structure is complex.
  • the embodiments of the present application provide a service data transmission method, a communication network, a service receiving device, and a storage medium, which are used to simplify the communication network structure and reduce the complexity of the communication network structure.
  • a first aspect of the embodiments of the present application provides a service data transmission method.
  • the method is applied to a communication network.
  • the communication network includes n service receiving devices and m service sending devices, where both n and m are integers greater than or equal to 1.
  • the method includes: any service receiving device among the n service receiving devices, which is referred to as the first service receiving device in the embodiment of the present application.
  • the first service receiving device broadcasts the MAC address of the first service receiving device to any service sending device that has a connection relationship with it. Specifically, the first service receiving device broadcasts the first MAC address to each of the m service sending devices.
  • the MAC address of the first service receiving device is also referred to as the first MAC address.
  • each service sending device configures local routing information according to the first MAC address. At least one service sending device among the m service sending devices sends service data and the first MAC address to the first service receiving device according to the configured local routing information.
  • the service sending device can receive the MAC address of the service receiving device.
  • the service sending device configures local routing information according to the MAC address of the service receiving device.
  • the service sending device can successfully send the service data according to the local routing information.
  • the service sending device obtains the MAC address of the service receiving device, or the service sending device sends service data to the service receiving device it is not restricted by the network segments of the IP addresses of the service sending device and the service receiving device.
  • Each service sending device or service receiving device does not need to have multiple ports in different network segments, and the structure of the communication network is simpler. Planners also do not need to ensure that each pair of service sending devices and service receiving devices have ports on the same network segment, which makes planning more convenient.
  • the service receiving device sends the first MAC address to each of the m service sending devices through the first data frame.
  • the first data frame includes a first field.
  • the first field is used to carry the first MAC address.
  • the first MAC address is transmitted through the first field in the first data frame.
  • the location of the first MAC address is defined in a specific field. Does not occupy non-specific fields, reducing the impact on other communication methods in the communication network.
  • the communication network is an optical transport network (optical transport network, OTN).
  • OTN optical transport network
  • An OTN frame includes a payload area and an overhead area.
  • the payload area is used to transmit service data
  • the overhead area is used to transmit data other than service data.
  • the MAC address corresponding to the service receiving device in the payload area needs to be obtained.
  • the service receiving device sends the OTN frame as the first data frame to the service sending device.
  • the first field of the overhead area of the OTN frame bears the MAC address corresponding to the service receiving device in the payload area, that is, the first MAC address.
  • the service receiving device has a connection relationship with the service sending device, data can be sent from the service receiving device to the service sending device through the overhead area of the OTN frame. Even if the port of the service receiving device is in the IP address corresponding to the payload area and the IP address corresponding to the port of the service sending device in the payload area is in a different network segment, the service sending device can still receive the data in the payload area of the service receiving device through the overhead area.
  • the corresponding MAC address of the zone The transmission of the MAC address of the service receiving device is no longer limited by the network segment of the port IP address.
  • the IP address of the port can be set freely, which eases the difficulty of planning the IP address by the planner.
  • the first field includes at least one of a GCC0 field, a GCC1 field, or a GCC2 field.
  • the transmission of the first MAC address may be implemented through an extended protocol.
  • the first field is used to carry the packet of the extended protocol.
  • the message of the extended protocol is used to indicate the first MAC address.
  • the message of the extended protocol includes the first data block.
  • the first data block is used to indicate the first MAC address.
  • the transmission of the first MAC address is implemented by extending an existing protocol.
  • the change to the existing communication network is small, and the cost of realizing the change of the communication network structure is small.
  • the extended protocol includes a path computation element communication protocol (path computation element communication protocol, PCEP) or a border gateway protocol (border gateway protocol). protocol, BGP).
  • PCEP path computation element communication protocol
  • border gateway protocol border gateway protocol
  • protocol BGP
  • the relay device when there are multiple service receiving devices in the communication network , the number of messages used to transmit the MAC address of the service receiving device in the communication network can be reduced through the relay device.
  • the relay device receives n MAC addresses from n service receiving devices.
  • the n MAC addresses are different from each other, and the n MAC addresses are in one-to-one correspondence with the MAC addresses of the n service receiving devices.
  • the xth service receiving device is any one of the n service receiving devices.
  • the xth service receiving device sends the xth MAC address to the transit device.
  • the xth MAC address is the MAC address of the xth service receiving device. x is any integer between greater than or equal to 1 and less than or equal to the n.
  • the relay device After receiving the n MAC addresses sent by the n service receiving devices, the relay device forwards the relay message to each service sending device.
  • Each transit message includes n MAC addresses, and the n MAC addresses are in one-to-one correspondence with the n receiving devices.
  • Each service sending device configures local routing information according to n MAC addresses.
  • the local routing information corresponds to n service receiving devices. Specifically, each service sending device configures local routing information related to the xth service receiving device according to the xth MAC address.
  • n service receiving devices send the MAC addresses of the service receiving devices to m service sending devices, and a total of m*n messages need to be sent.
  • n service receiving devices send the MAC addresses of the service receiving devices to m service sending devices, and a total of m+n messages need to be sent.
  • both m and n are integers greater than 1, m*n>m+n.
  • the relay device sends the second data frame to each of the m service transmission devices.
  • the second data frame includes a second field.
  • the second field is used to indicate the MAC address of each of the n service receiving devices.
  • the MAC address of each service receiving device is transmitted through the second field in the second data frame.
  • the location of the MAC address of each service receiving device is defined in a specific field. Does not occupy non-specific fields, reducing the impact on other communication methods in the communication network.
  • the communication network is OTN.
  • the relay device sends the OTN frame as the second data frame to each service sending device.
  • the second field is located in the overhead area of the OTN frame.
  • the second field carries the MAC address corresponding to the service receiving device in the payload area, that is, the first MAC address.
  • the transit device may be a software-defined network SDN controller, a server or a At least one of the network elements.
  • the relay device sends n MAC addresses to a specific service sending device .
  • the transit device stores the mapping relationship between the service receiving device and the service sending device.
  • the relay device sends n MAC addresses to the service sending device that has a mapping relationship with the service receiving device.
  • the relay device does not send the MAC addresses of the n service receiving devices to the service sending device that has no mapping relationship with the service receiving device, which plays a role of screening the service sending devices.
  • the relay device sends the MAC addresses of n service receiving devices to a specific service sending device, thereby reducing the number of messages in the communication network and saving the bandwidth of the communication network.
  • the MAC address of the service receiving device and the service The device identification of the receiving device is sent together.
  • the service sending device configures local routing information according to the device ID and MAC address. Specifically, the service sending device receives the xth MAC address and the xth device identifier from the xth service receiving device. The service sending device fills the xth device identifier and the xth MAC address into the ARP table. In order to send service data to the xth service receiving device, the service sending device queries the routing table to obtain the xth device identifier, and then queries the ARP table to obtain the xth MAC address.
  • the MAC address and the device identifier of the service receiving device are filled into the ARP table of the service sending device.
  • the MAC address of the service receiving device is queried through the device identification, ARP table and routing table, and the ARP technology used in most communication networks is followed.
  • the change to the existing communication network is small, and the cost of realizing the change of the communication network structure is small.
  • the device identifier of the service receiving device is the IP address of the service receiving device, which is used to identify the service receiving device.
  • the service receiving device is identified by the IP address of the device, rather than the IP addresses of multiple ports to identify the service receiving device.
  • the sending device only needs to configure routing information based on one device IP address of the service receiving device, and does not need to configure routing information for multiple ports of the same service receiving device.
  • the same service receiving device in the communication network does not need multiple ports, and the communication network structure is simpler.
  • the service sending device configures routing information through the IP address. By replacing the IP addresses of multiple ports with the IP address of one device, the configuration of routing information by the service sending device is also simpler. The number of messages including the IP address of the service receiving device or the port IP address of the service receiving device sent in the communication network is reduced, and the bandwidth of the communication network is saved.
  • a second aspect of the embodiment of the present application provides a data transmission method, the method includes: any service receiving device among n service receiving devices, which is referred to as a first service receiving device in the embodiment of the present application.
  • the first service receiving device broadcasts the MAC address of the first service receiving device to any service sending device that has a connection relationship with it. Specifically, the first service receiving device broadcasts the MAC address of the first service receiving device to each of the m sending devices.
  • the MAC address of the first service receiving device is also referred to as the first MAC address.
  • the first MAC address is used to configure local routing information for each sending device.
  • the first service receiving device receives service data and the first MAC address from at least one service sending device.
  • the at least one service sending device is at least one of the m service sending devices.
  • the service data and the first MAC address are sent according to the configured local routing information.
  • the first service receiving device sends the first MAC address to each of the m service sending devices through the first data frame.
  • the first data frame includes a first field. The first field is used to carry the first MAC address.
  • the communication network may specifically be an optical transport network OTN.
  • OTN is used to transmit OTN frames.
  • An OTN frame includes a payload area and an overhead area.
  • the payload area is used to transmit service data
  • the overhead area is used to transmit data other than service data.
  • the receiving device may send an OTN frame to the sending device, and the overhead area of the OTN frame carries the MAC address corresponding to the receiving device in the payload area.
  • the first service receiving device is a device in the optical transport network OTN.
  • the service receiving device can send and receive OTN frames.
  • An OTN frame includes a payload area and an overhead area.
  • the payload area is used to transmit service data
  • the overhead area is used to transmit data other than service data.
  • the MAC address corresponding to the service receiving device in the payload area needs to be obtained.
  • the service receiving device sends the OTN frame as the first data frame to the service sending device.
  • the first field of the overhead area of the OTN frame bears the MAC address corresponding to the service receiving device in the payload area, that is, the first MAC address.
  • the first field includes at least one of a GCC0 field, a GCC1 field, or a GCC2 field.
  • the transmission of the first MAC address may be implemented through an extended protocol.
  • the first field is used to carry the packet of the extended protocol.
  • the message of the extended protocol is used to indicate the first MAC address.
  • the message of the extended protocol includes the first data block.
  • the first data block is used to indicate the first MAC address.
  • the extended protocol includes a path computation element communication protocol (path computation element communication protocol, PCEP) or a border gateway protocol (border gateway protocol). protocol, BGP).
  • PCEP path computation element communication protocol
  • border gateway protocol border gateway protocol
  • protocol BGP
  • the number of service receiving devices when the number of service receiving devices is multiple , the number of messages sent by the service receiving device to the MAC address can be reduced through the relay device. Specifically, if the number of service receiving devices is n, n is an integer greater than or equal to 2.
  • the n service receiving devices send n MAC addresses to the transit device.
  • the n MAC addresses are different from each other, and the n MAC addresses are in one-to-one correspondence with the MAC addresses of the n service receiving devices.
  • the n MAC addresses are used for forwarding to each of the m service sending devices.
  • the xth service receiving device is any one of the n service receiving devices.
  • x is any integer between greater than or equal to 1 and less than or equal to the n.
  • the xth service receiving device sends the xth MAC address to the transit device.
  • the xth MAC address is the MAC address of the xth service receiving device.
  • the xMAC address is used for forwarding by the transit device to the service sending device, so that the service sending device configures local routing information according to the xMAC address.
  • the transit device may specifically be at least one of a software-defined network SDN controller, a server, or a network element.
  • the relay device sends n MAC addresses to a specific service sending device.
  • the transit device stores the mapping relationship between the service receiving device and the service sending device.
  • the relay device sends n MAC addresses to the service sending device that has a mapping relationship with the service receiving device.
  • the MAC address of the service receiving device and the service receiving The device ID of the device is sent along with it.
  • the device ID and MAC address are used to configure local routing information on the service sending device.
  • the device identifier of the service receiving device is the IP address of the service receiving device, which is used to identify the service receiving device.
  • a third aspect of the embodiments of the present application provides a data transmission method, the method comprising:
  • Each service sending device in the m service sending devices receives the first MAC address from the first service receiving device.
  • the first MAC address is the MAC address of the first service receiving device.
  • the first service receiving device is any one of n service receiving devices.
  • the service receiving device is any device that has a connection relationship with the service sending device.
  • each service sending device configures local routing information according to the first MAC address.
  • At least one service sending device in the m service sending devices sends service data and the first MAC address to the first service receiving device according to the configured local routing information.
  • each service sending device in the m service sending devices receives the first MAC address from the service receiving device through the first data frame.
  • the first data frame includes a first field. The first field is used to carry the first MAC address.
  • the service sending device is a device in the optical transport network OTN.
  • the service sending device can send and receive OTN frames.
  • An OTN frame includes a payload area and an overhead area.
  • the payload area is used to transmit service data
  • the overhead area is used to transmit data other than service data.
  • the MAC address corresponding to the service receiving device in the payload area needs to be obtained.
  • the service sending device receives the OTN frame as the first data frame from the service receiving device.
  • the first field of the overhead area of the OTN frame carries the MAC address corresponding to the service receiving device in the payload area, that is, the first MAC address.
  • the first field includes at least one of a GCC0 field, a GCC1 field, or a GCC2 field.
  • the transmission of the first MAC address may be implemented through an extended protocol.
  • the first field is used to carry the packet of the extended protocol.
  • the message of the extended protocol is used to indicate the first MAC address.
  • the message of the extended protocol includes the first data block.
  • the first data block is used to indicate the first MAC address.
  • the extended protocol includes a path computation element communication protocol (path computation element communication protocol, PCEP) or a border gateway protocol (border gateway protocol). protocol, BGP).
  • PCEP path computation element communication protocol
  • border gateway protocol border gateway protocol
  • protocol BGP
  • each service sending device in the m service sending devices receives a relay message from the relay device. If the number n of service receiving devices is an integer greater than or equal to 2.
  • Each transit message includes n MAC addresses, and the n MAC addresses are in one-to-one correspondence with the n receiving devices.
  • Each service sending device configures local routing information according to n MAC addresses. The local routing information corresponds to n service receiving devices. Specifically, each service sending device configures local routing information related to the xth service receiving device according to the xth MAC address.
  • each of the m service transmission devices receives the second data frame from the transit device.
  • the second data frame includes a second field.
  • the second field is used to indicate the MAC address of each of the n service receiving devices.
  • the service sending device is a device in the OTN.
  • Each service sending device receives the OTN frame as the second data frame from the transit device.
  • the second field is located in the overhead area of the OTN frame.
  • the second field carries the MAC address corresponding to the service receiving device in the payload area, that is, the first MAC address.
  • the transit device may be a software-defined network SDN controller, a server or At least one of the network elements.
  • the service sending device is specific. Specifically, the transit device stores the mapping relationship between the service receiving device and the service sending device. Only the service sending device that has a mapping relationship with the service receiving device can receive n MAC addresses from the transit device.
  • the MAC address of the receiving device is the same as that of the receiving device. received together with the device ID.
  • the service sending device configures local routing information according to the device ID and MAC address. Specifically, the service sending device receives the xth MAC address and the xth device identifier from the xth receiving device. The service sending device fills the xth device identifier and the xth MAC address into the ARP table. In order to send service data to the xth receiving device, the service sending device queries the routing table to obtain the xth device identifier, and then queries the ARP table to obtain the xth MAC address.
  • the device identifier of the service receiving device is the IP address of the service receiving device, which is used to identify the service receiving device.
  • a fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the method described in the foregoing first aspect is performed.
  • a fifth aspect of the embodiments of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the method described in the foregoing second aspect is performed.
  • a sixth aspect of an embodiment of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the program, the method described in the third aspect is performed.
  • a seventh aspect of the embodiments of the present application provides a computer program product.
  • the computer program product When the computer program product is executed on a computer, the computer executes the method described in the foregoing first aspect.
  • An eighth aspect of the embodiments of the present application provides a computer program product.
  • the computer program product When the computer program product is executed on a computer, the computer executes the method described in the foregoing second aspect.
  • a ninth aspect of the embodiments of the present application provides a computer program product.
  • the computer program product When the computer program product is executed on a computer, the computer executes the method described in the third aspect.
  • the service sending device can receive the MAC address of the service receiving device.
  • the service sending device configures local routing information according to the MAC address of the service receiving device.
  • the service sending device can successfully send the service data according to the local routing information.
  • the service sending device obtains the MAC address of the service receiving device, or the service sending device sends service data to the service receiving device it is not restricted by the network segments of the IP addresses of the service sending device and the service receiving device.
  • Each service sending device or service receiving device does not need to have multiple ports in different network segments, and the structure of the communication network is simpler. Planners also do not need to ensure that each pair of service sending devices and service receiving devices have ports on the same network segment, which makes planning more convenient.
  • Figure 1 is an architecture diagram of a communication network
  • FIG. 1 is an architecture diagram of an optical transport network OTN
  • FIG. 3 is an OTN architecture diagram in an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a data transmission method in an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a format of an expanded BGP protocol message in the embodiment of the present application.
  • FIG. 6 is an architectural diagram of a communication network in an embodiment of the application.
  • FIG. 7 is a schematic flowchart of a data transmission method in an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication network in an embodiment of the application.
  • FIG. 9 is a schematic structural diagram of a service receiving device in an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of a service sending device in an embodiment of the present application.
  • the embodiment of the present application provides a service data transmission method, which is used to simplify the communication network structure, so as to reduce the complexity of the communication network structure.
  • FIG. 1 provides an architecture diagram of a communication network.
  • the communication network has multiple service sending devices and multiple service receiving devices.
  • each of the service sending device 1 to the service sending device m has n ports.
  • the n ports correspond to n IP addresses in different network segments.
  • Each of the service receiving device 1 to the service receiving device n has m ports.
  • the m ports correspond to m IP addresses in different network segments.
  • each service sending device has 3 ports, and each service receiving device has 2 ports.
  • the service sending device 1 has three ports whose IP addresses are IP1, IP2, and IP3 respectively.
  • the service receiving device 1 has two ports whose IP addresses are IP1' and IP4' respectively.
  • the service data can be transmitted.
  • each service sending device in the service sending device 1 to the service sending device m can send a service message to each service receiving device in the service receiving device 1 to the service receiving device n.
  • the service sending device 1 in FIG. 1 can send service data to the service receiving device 1 through the port 1 and the port 1'.
  • the service sending device in FIG. 1 can also be used as a service receiving device for receiving service messages from other devices in the communication network.
  • the service sending device 1 acts as a service receiving device, it can receive service messages from the service receiving device 1 through the port 1 and the port 1'.
  • Service sending devices can also send data to each other.
  • service sending device 1 can also receive service messages from service sending device 2 through port z and port z'.
  • each device has only one port. But in practical application, there are the following problems. On the one hand, when all ports are on the same network segment, there will be too many ARP requests when broadcasting ARP requests. As a result, the bandwidth of the communication network is excessively occupied. On the other hand, different devices belong to different users. Different users have different requirements for the network segment of the device port. Therefore, in a communication network, most devices have multiple ports.
  • the communication network includes the Optical Transport Network OTN.
  • FIG. 2 is a network architecture diagram of an OTN.
  • the data transmission between the user network edge device (customer edge, CE) and the cloud virtual machine (virtual personal computer, VPC) can be realized by OTN.
  • the OTN includes the customer premise equipment (customer premise equipment, CPE) connected to the CE.
  • CE receives and sends service data through CPE.
  • the OTN also includes the cloud premise equipment (PE) connected to the cloud VPC.
  • the cloud VPC receives and sends business data through the cloud PE.
  • the cloud PE is also called cloud PE
  • the cloud VPC is also called VPC.
  • CE1 is used as the source device of service data
  • the cloud VPC1 is used as the receiving device of service data
  • the source device is a device that is connected to the service sending device and provides service data to the service sending device.
  • the receiving device is a device connected to the service receiving device and receiving service data from the service receiving device.
  • CE1 is only an example of the source device, and does not limit the source device.
  • the source device can also be a cloud VPC.
  • Cloud VPC1 is only an example of the source device and the sink device, and does not limit the source device and the sink device.
  • the service receiving device may also be a CE.
  • a service sending device For a service sending device, to send service data to multiple service receiving devices, it needs to have multiple IP addresses in different network segments. It also needs to have multiple ports. The same is true for service receiving equipment. For each pair of service receiving device and service sending device, the port of the service sending device and the port of the service receiving device need to have IP addresses in the same network segment. From the perspective of the communication network, each device has multiple ports, and the communication network structure is complex. From the perspective of planners, it is necessary to ensure that the port of the service sending device and the port of the service receiving device have IP addresses on the same network segment, which makes planning difficult.
  • an embodiment of the present application provides a method for transmitting service data, which realizes the transmission of service data by broadcasting the MAC address of the service receiving device to the service sending device.
  • the service receiving device accesses the communication network or the topology of the communication network changes, the service receiving device actively sends the MAC address of the service receiving device to all service sending devices that have a connection relationship with it. All service sending devices save the MAC address of the service receiving device and can send service data to the service receiving device.
  • the broadcast in the embodiment of the present application refers to an action of sending the same data to a device.
  • the number of devices can be more than one or more than two.
  • broadcasting is an action of sending a MAC address to a service sending device.
  • the MAC address is the MAC address of the service receiving device.
  • the number of service sending devices may be more than one or more than two.
  • the communication network includes m service sending devices and n service receiving devices.
  • the service receiving device is used for receiving service data
  • the service sending device is used for sending service data.
  • m and n are integers greater than or equal to 1, and m may also be an integer greater than or equal to 2.
  • the data transmission method provided in the embodiment of the present application can be applied to the optical transport network OTN.
  • the data transmission method provided in the embodiments of the present application can also be applied to other communication networks.
  • an automatically switched optical network automated optical network, ASON
  • a packet transport network packet transport network, PTN
  • the embodiments of the present application take that the method is applied to OTN as an example for introduction.
  • the embodiments of the present application can implement the above method by extending the existing point-to-point reliable transmission protocol.
  • the extended point-to-point reliable transmission protocol is also referred to as an extended protocol.
  • FIG. 3 is an OTN architecture diagram provided in an embodiment of the present application. Since the method provided by the embodiment of the present application does not need to use the IP address of the port, the port of the device does not need to appear in the network architecture of FIG. 3 . Compared with the communication network architecture shown in FIG. 1 or FIG. 2 , the communication network architecture of FIG. 3 does not need to set the port of the device. The communication network architecture of FIG. 3 is simpler, and the complexity of the communication network structure is low. Based on the network architecture shown in FIG. 3 , the method shown in FIG. 4 can be implemented.
  • the service receiving device may be a CPE in the OTN
  • the service sending device may be a cloud PE in the OTN.
  • the service receiving device may be a cloud PE
  • the service sending device may be a CPE.
  • the service receiving device may be the first CPE
  • the service sending device may be the second CPE.
  • the service receiving device may be the first cloud PE
  • the service sending device may be the second cloud PE.
  • the CPE is used as a service receiving device
  • the cloud PE is used as a service sending device.
  • the embodiments of the present application are only examples of the service receiving device and the service sending device, and do not limit the service receiving device and the service sending device.
  • the first service receiving device broadcasts the first MAC address to m service sending devices.
  • the service receiving device can send and receive OTN frames through OTN.
  • the OTN frame includes an overhead area and a payload area.
  • the payload area is used to carry service data.
  • the overhead area also called control overhead, is used to carry routing information of service data and routing information of devices. Data transfer for control overhead is not constrained by the IP address and MAC address of the device.
  • the service receiving device can send data to all devices that have a connection relationship with the service receiving device by controlling the overhead.
  • a device that has a connection relationship with a service receiving device and can send service data to the service receiving device is called a service sending device.
  • the network includes n service receiving devices and m service sending devices, both m and n are integers greater than or equal to 1.
  • the first service receiving device is any one of n service receiving devices.
  • all service receiving devices are described by taking the cloud PE1 as an example.
  • the cloud PE1 does not limit the service receiving device.
  • the cloud PE1 can broadcast the first data frame to any CPE that has a connection relationship with it.
  • the first data frame is used to carry the MAC address of the cloud PE1.
  • the number of CPEs is m
  • the m CPEs represent all service sending devices that are connected to the cloud PE1 in the communication network.
  • the first data frame is an OTN frame.
  • the first data frame may be a data frame corresponding to the communication network, which is not limited here.
  • the MAC address of the service receiving device is also referred to as the first MAC address.
  • the broadcast of the first MAC address may be implemented through a message of the extended protocol.
  • the message of the extended protocol represented by the BGP message includes a first data block, and the first data block is used to indicate the first MAC address.
  • the message of the extended protocol may be carried in the first field of the first data frame.
  • the first MAC address is used for the service sending device to configure local routing information related to the service receiving device.
  • the packets of extended protocols may also be packets of other extended protocols. For example, a PCEP message, etc., which are not specifically limited here.
  • A if A carries B, it means that A is a location for placing B, but A may not be able to completely accommodate B. So A can be one or more. As long as A can place the content of B, it is a bearer.
  • the first field is used to carry BGP packets. Then the content of a BGP packet can be placed in multiple first fields, and each first field is used to place a part of the content of the BGP packet.
  • the first field when the first data frame is an OTN frame, the first field may be GCC0 in the overhead area of the OTN frame, and the first field may also be other fields in the overhead area of the OTN frame, such as GCC1 or GCC2, which is not specifically limited here.
  • the first data frame is a data frame of another communication network
  • the first field is correspondingly a certain field of the data frame of other communication network, which is not specifically limited here.
  • BGP packets support carrying path attributes (path attributes) objects. It includes the routing destination address and the NEXT_HOP used to represent the next hop IP address. Specifically applied to the scenario shown in FIG. 2 , if the path attribute is the routing destination address, the content of the corresponding path attribute is the IP address of the VPC. If the path attribute is NEXT_HOP, the content of the path attribute is the IP address of the first port of the receiving device.
  • path attributes path attributes
  • NEXT_HOP used to represent the next hop IP address.
  • BGP packets do not support carrying MAC addresses.
  • the BGP protocol also does not specify a specific data block for indicating a MAC address.
  • the embodiment of the present application specifies that the first data block of the extended protocol packet is used to indicate the MAC address of the service receiving device through the extended protocol. Thereby, the transmission of the MAC address of the service receiving device is realized.
  • NEXT_HOP_MAC is used to indicate the MAC address of the next hop.
  • NEXT_HOP_MAC appears together with the NEXT_HOP attribute in BGP packets.
  • NEXT_HOP_MAC is the first data block.
  • the BGP packets that appear in the methods shown in the embodiments of the present application are all extended BGP packets.
  • the content of the path attribute of the path attribute NEXT_HOP in the packet is filled with the IP address of the cloud PE1, and the content of the path attribute of the path attribute NEXT_HOP_MAC is filled with the MAC address of the cloud PE1.
  • the IP address here refers to the device identifier of the cloud PE1, which is also referred to as the first IP address.
  • the device ID is used to identify the receiving device.
  • the MAC address here refers to the MAC address of the cloud PE1, which is also referred to as the first MAC address.
  • the first MAC address is the MAC address of the receiving device.
  • the field used to fill in the first MAC address in the packet of the extended protocol may also be referred to as the second field.
  • the first IP address may be the ID number of the receiving device itself, or may be other device identifiers used to identify the receiving device.
  • a manually configured identification number which is not specifically limited here.
  • the format of the expanded BGP packet may be as described in FIG. 5 , which is a schematic diagram of the format of an expanded BGP protocol packet provided by an embodiment of the present application.
  • Attr.Flags in Figure 5 represents the flag bit of the path attribute.
  • Type Code indicates the type of path attribute, where Type Code3 is NEXT_HOP, and Type Code41 is NEXT_HOP_MAC.
  • Prefix Length indicates the length of the route destination address prefix.
  • Prefix indicates the value of the route destination address prefix.
  • the packet format shown in FIG. 5 is only an example, and does not limit the extended BGP packet and the extended protocol packet.
  • Each service sending device in the m service sending devices configures local routing information according to the first MAC address.
  • the service sending device may include CPE1 and CPE2 in FIG. 3
  • the service receiving device may include cloud PE1 , cloud PE2 and cloud PE3 in FIG. 3 .
  • each of the m CPEs configures local routing information related to the cloud PE1, that is, saves the mapping relationship between the first MAC address and the first IP address.
  • each CPE may store the mapping relationship between the first IP address and the first MAC address in the BGP packet in the ARP table of the CPE. That is, the first IP address and the first MAC address are filled in the ARP table.
  • the local routing information related to the cloud PE1 may also exist in other forms.
  • the mapping relationship between the first MAC address and the routing destination address that is, the mapping relationship between the first MAC address and the IP address of the VPC1 is stored locally, which is not specifically limited here.
  • the VPC1 is a device connected to the cloud PE1 for receiving service data.
  • the ARP table is stored in the memory of the CPE instead of the cache. Therefore, once the mapping relationship between the first IP address and the first MAC address is saved, it will not be overwritten by new data in the CPE cache.
  • the CPE can obtain the first MAC address only according to the mapping relationship stored in the memory, and does not need to obtain the first MAC address by other methods. For example, methods such as broadcasting ARP requests.
  • the first MAC address is obtained by querying the ARP table stored in the memory, and this method has a high success rate for obtaining the first MAC address.
  • the CPE may also save the mapping relationship between the first IP address in the BGP packet and the routing destination address in the routing table of the CPE, that is, fill the routing table with the first IP address and the routing destination address. middle.
  • the mapping relationship between the first IP address and the routing destination address in the routing table may also be obtained in other ways. For example, manual configuration, etc., are not specifically limited here.
  • this step further includes: the service sending device receives the service data and the IP address of the cloud VPC.
  • the service sending device receives the service data and the IP address of the cloud VPC.
  • the CPE1 connected to CE1 can receive the aforementioned service data from CE1 and the IP address of the cloud VPC1, indicating that the service The recipient of the data is cloud VPC1.
  • this step may further include: the service sending device determines the first MAC address.
  • CPE1 can use the IP address of cloud VPC1 as the routing destination address, and query the routing table to obtain the IP address of cloud PE1 corresponding to the IP address of cloud VPC1, that is, the above-mentioned first IP address.
  • the CPE1 then queries the above-mentioned ARP table stored in the memory to obtain the first MAC address corresponding to the first IP address.
  • the first MAC address is the MAC address of the cloud PE1.
  • the CPE can directly determine the first MAC address according to the mapping relationship and the IP address of the VPC, which is not specifically limited here.
  • At least one service sending device among the m service sending devices sends service data and a first MAC address to the first service receiving device according to the local routing information.
  • the service sending device may include CPE1 and CPE2 in FIG. 3
  • the service receiving device may include cloud PE1 , cloud PE2 and cloud PE3 in FIG. 3 .
  • the CPE1 After acquiring the first MAC address, the CPE1 sends the service data and the first MAC address to the cloud PE1. Specifically, CPE1 may fill the service data obtained from CE1 in the payload area of the OTN frame. In the control overhead of the OTN frame, the routing destination address and the next-hop MAC address are filled.
  • the object corresponding to the routing destination address in the control overhead may be filled with the IP address of the cloud VPC1. Fill in the object corresponding to the next-hop IP address in the control overhead as the first IP address. Fill in the object corresponding to the next-hop MAC address in the control overhead as the first MAC address.
  • CPE1 sends the OTN frame to cloud PE1.
  • this step may further include: the service receiving device transmits the service data to the cloud VPC.
  • the cloud PE1 receives the OTN frame, and verifies that the first MAC address carried in the control overhead of the OTN frame is the MAC address of the cloud PE1, thereby confirming that the OTN frame is sent to itself.
  • the cloud PE1 determines that the receiver of the OTN frame is the cloud VPC1 through the IP address of the VPC1 carried in the control overhead of the OTN frame, so as to transmit the service data to the cloud VPC1.
  • the number of service receiving devices is not limited to one, but may be multiple.
  • the cloud PE1 For the corresponding relationship and actions performed by each receiving device, refer to the cloud PE1, and details are not repeated here.
  • all m service sending devices configured with local routing information can send service messages to service receiving devices.
  • service messages For the process of sending a service message to the service receiving device by any one of the m service sending devices, refer to the process of sending by the CPE1, which will not be repeated here.
  • the service sending device can receive the MAC address of the service receiving device.
  • the service sending device configures local routing information according to the MAC address of the service receiving device.
  • the service sending device can successfully send service data according to the local routing information stored locally. Whether the service sending device obtains the MAC address of the service receiving device, or the service sending device sends service data to the service receiving device, it is not restricted by the network segments of the IP addresses of the service sending device and the service receiving device.
  • Each service sending device and service receiving device does not need to have multiple ports in different network segments, and the structure of the communication network is simpler. Planners also do not need to ensure that each pair of service sending devices and service receiving devices have ports on the same network segment, which makes planning more convenient.
  • the service receiving device can be directly identified by the IP address of the service receiving device. It is no longer necessary for planners to plan the port IP address of each service receiving device, which reduces the operation steps of personnel in the communication network and improves the automation of the communication network.
  • the service sending device stores the MAC address of the service receiving device locally.
  • the service sending device sends service data to the service receiving device
  • the MAC address of the service receiving device can be obtained directly from the local, and does not need to be obtained from other devices.
  • the bandwidth of the communication network is saved, and the delay is reduced at the same time.
  • the extension to the BGP message is also applicable to the PCEP protocol, and the newly added path attribute objects are all NEXT_HOP_MAC.
  • the usage of the expanded PCEP message is the same as the usage of the expanded BGP message in the embodiment shown in FIG. 4 , and details are not repeated here.
  • the embodiments of the present application only take the OTN architecture shown in FIG. 3 and the method shown in FIG. 4 as examples.
  • the service data transmission method provided in the embodiment of the present application is not limited to the OTN network, but can also be applied to other communication networks.
  • ASON or PTN, etc. which are not specifically limited here.
  • the MAC address of the service receiving device can be transmitted through the transit device. Thereby reducing the number of messages in the communication network.
  • the relay device is used to reduce the number of messages of the MAC address of the transmission service receiving device in the communication network.
  • the transit device may specifically be a software defined network (software defined network, SDN) controller.
  • the transit device may also be other devices, such as a server or a network element, which is not specifically limited here.
  • the embodiments of the present application only take the SDN controller as an example, and do not limit the transfer device.
  • FIG. 6 is an architectural diagram of a communication network provided in an embodiment of the present application.
  • the architecture reduces the number of messages transmitting the first MAC address in the communication network by means of a transit device.
  • the communication network includes m CPEs and n cloud PEs. Both m and n are integers greater than 1. Based on the network architecture shown in FIG. 6 , the method shown in FIG. 7 can be implemented.
  • CPE and the cloud PE in the embodiments of the present application are only examples of service sending devices and service receiving devices, and do not limit them.
  • service sending device and the service receiving device refer to the embodiment shown in FIG. 4 for details, and details are not repeated here.
  • FIG. 7 is a schematic flowchart of a data transmission method provided by the present application. Please refer to FIG. 7. Based on the communication network architecture shown in FIG. 6, a data transmission method provided by an embodiment of the present application includes:
  • cloud PEs send a first data frame carrying a first MAC address to an SDN controller.
  • each cloud PE in the n cloud PEs sends the first data frame carrying the first MAC address to the SDN controller.
  • the first data frame sent by each service receiving device carries the MAC address of the service receiving device, that is, the first MAC address. That is, the SDN controller will receive n MAC addresses from n cloud PEs.
  • the n MAC addresses are different from each other, and the n MAC addresses are in one-to-one correspondence with the n cloud PEs.
  • the xth cloud PE among the n cloud PEs sends the first data frame to the SDN controller.
  • the frame carries the MAC address and IP address of the xth cloud PE, and the IP address of the VPC connected to the xth cloud PE.
  • the xth cloud PE is any one of the n cloud PEs.
  • the transmission of the first MAC address may be implemented through a packet of an extended protocol represented by the BGP protocol.
  • the BGP protocol For details, refer to step 401 in the embodiment shown in FIG. 4 , which will not be repeated here.
  • the message including the MAC address of the service receiving device may also be referred to as a routing message.
  • cloud PE1 sends a routing message including MAC1, IP1, and VPC1 to the SDN controller, where MAC1 is the MAC address of cloud PE1, IP1 is the IP address of cloud PE1, and VPC1 is the IP address of VPC1.
  • the SDN controller broadcasts a relay message to m CPEs.
  • the SDN controller After receiving the MAC address and IP address of the xth cloud PE and the IP address of the VPC connected to the xth cloud PE sent by the n cloud PEs, the SDN controller broadcasts a relay message to each of the m CPEs.
  • Each transit message includes the MAC addresses and IP addresses of the n cloud PEs and the IP addresses of the VPCs connected to the n cloud PEs.
  • the MAC address and IP address of the xth cloud PE and the IP address of the VPC connected to the xth cloud PE are carried in the BGP packet.
  • x is an integer from 1 to n.
  • the relay message may be sent through an OTN frame.
  • the OTN frame at this time may also be referred to as a second data frame.
  • the second data frame is used to carry the MAC addresses of the n receiving devices.
  • step 401 For the relationship between the second data frame and the BGP message, refer to the relationship between the first data frame and the BGP message in step 401 of the embodiment shown in FIG. 4 , which will not be repeated here.
  • the specific locations of the MAC address, IP address of the xth cloud PE, and the IP address of the VPC connected to the xth cloud PE in the BGP message refer to the description of step 401 in the implementation example in FIG. 4 , which will not be repeated here.
  • Each CPE configures local routing information related to the n cloud PEs.
  • Each CPE is configured with local routing information related to n cloud PEs. Specifically, each CPE configures routing information related to the xth cloud PE according to the MAC address and IP address of the xth cloud PE and the IP address of the VPC connected to the xth cloud PE.
  • x is an integer from 1 to n.
  • the CPE1 receives the service data and the IP address of the cloud VPC.
  • At least one of the n CPEs receives service data and the IP address of the cloud VPC, and the cloud VPC is connected to one of the m cloud PEs.
  • CPE1 receives service data and the IP address of VPC1, and VPC1 is connected to cloud PE1.
  • CPE1 represents any of m CPEs.
  • Cloud PE1 represents any one of n cloud PEs. The embodiments of this application only take the CPE1 and the cloud PE1 as examples, and do not limit the service sending device and the service receiving device.
  • the CPE1 determines the MAC address of the cloud PE1.
  • the CPE1 After receiving the IP address of the VPC1, the CPE1 can obtain the MAC address of the cloud PE1 according to the routing information related to the cloud PE1 configured in step 703.
  • the routing information related to the cloud PE1 configured in step 703.
  • the CPE1 sends an OTN frame carrying the service data and the MAC address of the cloud PE1 to the cloud PE1.
  • CPE1 After obtaining the MAC address of cloud PE1, CPE1 sends an OTN frame carrying service data and the MAC address of cloud PE1 to cloud PE1.
  • OTN frame carrying service data and the MAC address of cloud PE1 to cloud PE1.
  • the cloud PE1 transmits the service data to the cloud VPC1.
  • Cloud PE1 receives the OTN frame. Verify that the MAC address carried in the control overhead of the OTN frame is the MAC address of cloud PE1, thus confirming that the OTN frame is sent to itself.
  • the cloud PE1 determines that the receiver of the OTN frame is the cloud VPC1 connected to the cloud PE1 by using the IP address of the VPC1 carried in the control overhead of the OTN frame, so as to transmit the service data to the cloud VPC1.
  • n service receiving devices send the MAC addresses of the service receiving devices to m service sending devices, and a total of m*n messages need to be sent.
  • n service receiving devices send the MAC addresses of the service receiving devices to m service sending devices, and a total of m+n messages need to be sent.
  • both m and n are integers greater than 1, m*n>m+n.
  • a structure of the communication network includes:
  • n service receiving devices 801 and m service sending devices 802 There are n service receiving devices 801 and m service sending devices 802, where n and m are both integers greater than or equal to 1.
  • the n service receiving devices 801 include a first service receiving device 8011 , and the first service receiving device 8011 is any one of the n service receiving devices 801 .
  • the first service receiving device 8011 is configured to broadcast a first MAC address to the m service sending devices 802, where the first MAC address is the MAC address of the first service receiving device 8011.
  • Each of the m service sending devices 802 is configured to configure local routing information according to the first MAC address.
  • At least one service sending device among the m service sending devices 802 is configured to send the service data and the first MAC address to the first service receiving device 8011 according to the local routing information.
  • the first service receiving device 8011 is configured to send a first data frame to each service sending device, where the first data frame includes a first field, and the first field is used to carry the first data frame.
  • a MAC address is used to carry the first data frame.
  • the first data frame is an OTN frame
  • the first field is located in an overhead area of the OTN frame.
  • the first field is used to carry a packet of an extended protocol
  • the packet of the extended protocol is used to indicate the first MAC address
  • the communication network further includes a relay device 803 .
  • the relay device 803 is configured to receive n MAC addresses from the n service receiving devices 801 , and the n MAC addresses are in one-to-one correspondence with the n service receiving devices. forwarding the n MAC addresses to each service sending device;
  • Each service sending device of the m service sending devices 802 is configured to configure local routing information according to the n MAC addresses, where the local routing information corresponds to the n service receiving devices.
  • the relay device 803 is configured to send a second data frame to each service sending device, where the second data frame includes a second field, and the second field is used to indicate that the n services are received MAC address of each service receiving device in the device.
  • the transit device 803 includes at least one of a software-defined network SDN controller, a server, or a network element.
  • the first service receiving device 8011 is configured to broadcast the first MAC address and the device identification of the first service receiving device to the m service sending devices;
  • Each of the m service sending devices 802 is configured to configure local routing information according to the first MAC address and the device identifier.
  • the communication network shown in FIG. 8 is used to execute the method in the embodiment shown in the foregoing FIG. 4 or FIG. 6 .
  • FIG. 9 is a schematic structural diagram of a service receiving device provided by an embodiment of the present application.
  • the service receiving device 900 may include one or more central processing units (central processing units, CPU) 901 and memory 905 .
  • the memory 905 stores one or more application programs or data.
  • the memory 905 may be volatile storage or persistent storage.
  • the program stored in the memory 905 may include one or more modules, and each module may include a series of instruction operations on the service receiving device.
  • the central processing unit 901 may be configured to communicate with the memory 905 to execute a series of instruction operations in the memory 905 on the service receiving device 900 .
  • the service receiving device 900 may also include one or more power supplies 902, one or more wired or wireless network interfaces 903, one or more transceiver interfaces 904, and/or, one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • one or more operating systems such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • the service receiving device 900 may perform the operations performed by the service receiving device in the embodiment shown in FIG. 4 , FIG. 6 or FIG. 7 , and details are not repeated here.
  • FIG. 10 is a schematic structural diagram of a service sending device provided by an embodiment of the present application.
  • the service sending device 1000 may include one or more central processing units (central processing units, CPU) 1001 and a memory 1005.
  • the memory 1005 stores one or more application programs or data.
  • the memory 1005 may be volatile storage or persistent storage.
  • the program stored in the memory 1005 may include one or more modules, and each module may include a series of instruction operations in the service sending device.
  • the central processing unit 1001 may be configured to communicate with the memory 1005 to execute a series of instruction operations in the memory 1005 on the service sending device 1000 .
  • the service sending device 1000 may also include one or more power supplies 1002, one or more wired or wireless network interfaces 1003, one or more transceiver interfaces 1004, and/or, one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • one or more operating systems such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • the service sending device 1000 may perform the operations performed by the service sending device in the embodiment shown in FIG. 4 , FIG. 6 or FIG. 7 , and details are not repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例公开了一种业务数据传输方法，用于简化通信网络结构，方便规划人员对通信网络的规划。本申请实施例的方法包括：业务接收设备主动向多个与其有连接关系的业务发送设备发送业务接收设备的MAC地址，每个业务发送设备根据该MAC地址配置本地路由信息。业务接收设备的MAC地址不需要根据ARP请求获取，避免了ARP请求带来的对设备端口IP地址的限制。可以用一个设备的IP地址代替该设备的多个端口的IP地址，简化了通信网络。

Description

业务数据传输方法、通信网络、业务接收设备及存储介质
本申请要求于2020年10月31日提交中国国家知识产权局、申请号为202011197165.4、申请名称为“业务数据传输方法、通信网络、业务接收设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种业务数据传输方法、通信网络、业务接收设备及存储介质。
背景技术
在通信网络中，业务发送设备的第一端口具有第一网际互连协议(internet protocol，IP)地址。业务接收设备的第二端口具有第二IP地址。业务发送设备为向业务接收设备发送业务数据，需要获取第二端口的媒体存取控制(media access control，MAC)地址。具体过程如下：业务发送设备通过地址解析协议(address resolution protocol，ARP)，在第一IP地址的网段内广播ARP请求。请求中携带第二IP地址。业务接收设备通过具有第二IP地址的第二端口接收该ARP请求，并将第二端口的MAC地址发送给业务发送设备。
来自业务发送设备的ARP请求只能到达与第一IP地址同网段的端口。当第一端口和第二端口处于不同网段时，业务接收设备无法通过第二端口接收上述ARP请求，也就不会向业务发送设备发送第二端口的MAC地址。此时业务发送设备就无法获取第二端口的MAC地址，业务数据无法成功发送。
为了实现业务数据的成功发送，需要确保每对业务接收设备与业务发送设备之间具有处于同网段的第一IP地址和第二IP地址。当业务发送设备有多个，业务接收设备有多个时，每个业务发送设备需要具有多个第一IP地址，也就需要具有多个第一端口。每个业务接收设备需要具有多个第二IP地址，也就需要具有多个第二端口。每个设备都具有多个端口，通信网络结构复杂。
发明内容
本申请实施例提供了一种业务数据传输方法、通信网络、业务接收设备以及存储介质，用于简化通信网络结构，以降低通信网络结构的复杂度。
本申请实施例第一方面提供了一种业务数据传输方法。该方法应用于通信网络。该通信网络包括n个业务接收设备和m个业务发送设备，n和m均为大于或等于1的整数。该方法包括：n个业务接收设备中的任一个业务接收设备，本申请实施例中称为第一业务接收设备。第一业务接收设备向任一与其具有连接关系的业务发送设备广播第一业务接收设备的MAC地址。具体的，第一业务接收设备向m个业务发送设备中的每个业务发送设备广播第一MAC地址。在本申请实施例中，第一业务接收设备的MAC地址也称为第一MAC地址。每个业务发送设备接收到第一MAC地址后，根据第一MAC地址配置本地路由信息。m个业务发送设备中的至少一个业务发送设备，根据配置好的本地路由信息，向第一业务接收设备发送业务数据和第一MAC地址。
在本申请实施例中，业务发送设备只要与业务接收设备具有连接关系，就能接收到业务接收设备的MAC地址。业务发送设备根据业务接收设备的MAC地址配置本地路由信息。业务发送设备根据本地路由信息，就能实现业务数据的成功发送。无论是业务发送设备获取业务接收设备的MAC地址，还是业务发送设备向业务接收设备发送业务数据，都不受到业务发送设备与业务接收设备IP地址的网段的限制。每个业务发送设备或业务接收设备不需要具有多个处于不同网段的端口，通信网络的结构更简单。规划人员也不需要确保每对业务发送设备和业务接收设备之间具有处于同网段的端口，规划更方便。
结合第一方面，本申请实施例第一方面的第一种实施方式中，业务接收设备通过第一数据帧向m个业务发送设备中的每个业务发送设备发送第一MAC地址。第一数据帧包括第一字段。第一字段用于承载第一MAC地址。
在本申请实施例中，通过第一数据帧中的第一字段传输第一MAC地址。将第一MAC地址的位置限定在特定的字段中。不占用非特定的字段，降低对通信网络中其他通信方法的影响。
结合第一方面的第一种实施方式，本申请实施例第一方面的第二种实施方式中，通信网络是光传送网(optical transport network，OTN)。OTN用于传输OTN帧。OTN帧包括净荷区和开销区。净荷区用于传输业务数据，开销区用于传输除业务数据外的数据。为传输业务数据，需要获取业务接收设备在净荷区对应的MAC地址。业务接收设备向业务发送设备发送作为第一数据帧的OTN帧。在OTN帧开销区的第一字段中承载业务接收设备在净荷区对应的MAC地址，即第一MAC地址。
在本申请实施例中，只要业务接收设备与业务发送设备有连接关系，数据就能通过OTN帧的开销区从业务接收设备发送到业务发送设备。即使业务接收设备的端口在净荷区对应的IP地址，与业务发送设备的端口在净荷区对应的IP地址处于不同网段，业务发送设备也能通过开销区接收到业务接收设备在净荷区对应的MAC地址。业务接收设备MAC地址的传输不再受限于端口IP地址的网段。端口的IP地址可自由设置，减轻了规划人员规划IP地址的难度。
结合第一方面的第二种实施方式，本申请实施例第一方面的第三种实施方式中，第一字段包括GCC0字段、GCC1字段或GCC2字段中的至少一个。
结合第一方面的第二种实施方式或第三种实施方式，本申请实施例第一方面的第四种实施方式中，可以通过扩展协议实现第一MAC地址的传输。具体的，第一字段用于承载扩展协议的报文。扩展协议的报文用于指示第一MAC地址。具体的，扩展协议的报文中包括第一数据分块。第一数据分块用于指示第一MAC地址。
在本申请实施例中，通过扩展已有的协议实现对第一MAC地址的传输。对已有通信网络的变动小，实现通信网络结构变更所付出的代价小。
结合第一方面的第四种实施方式，本申请实施例第一方面的第五种实施方式中，扩展协议包括路径计算单元通信协议(path computation element communication protocol，PCEP)或边界网关协议(border gateway protocol，BGP)。
结合第一方面、第一方面的第一种至第五种实施方式中的任一种，本申请实施例第一 方面的第六种实施方式中，当通信网络中存在多个业务接收设备时，可以通过中转设备减少通信网络中用于传输业务接收设备MAC地址的消息数量。具体的，中转设备接收来自n个业务接收设备的n个MAC地址。n个MAC地址是各不相同的，n个MAC地址与n个业务接收设备的MAC地址一一对应。例如，第x业务接收设备为n个业务接收设备中的任一个业务接收设备。第x业务接收设备向中转设备发送第xMAC地址。第xMAC地址为第x业务接收设备的MAC地址。x为位于大于或等于1且小于或等于所述n之间的任一整数。中转设备接收到n个业务接收设备发送的n个MAC地址后，向每个业务发送设备转发中转消息。每条中转消息中包括n个MAC地址，n个MAC地址与n个接收设备一一对应。每个业务发送设备根据n个MAC地址配置本地路由信息。本地路由信息对应于n个业务接收设备。具体的，每个业务发送设备根据第xMAC地址，配置与第x业务接收设备相关的本地路由信息。
在本申请实施例中，若没有中转设备，n个业务接收设备向m个业务发送设备发送业务接收设备的MAC地址，一共需要发送m*n条消息。通过中转设备，n个业务接收设备向m个业务发送设备发送业务接收设备的MAC地址，一共需要发送m+n条消息。当m和n均为大于1的整数时，m*n>m+n。通过中转设备发送业务接收设备的MAC地址，可以减少通信网络中消息的数量，节省通信网络带宽。
结合第一方面的第六种实施方式，本申请实施例第一方面的第七种实施方式中，中转设备向m个业务发送设备中的每个业务发送设备发送第二数据帧。第二数据帧包括第二字段。第二字段用于指示n个业务接收设备中每个业务接收设备的MAC地址。
在本申请实施例中，通过第二数据帧中的第二字段传输每个业务接收设备的MAC地址。将每个业务接收设备的MAC地址的位置限定在特定的字段中。不占用非特定的字段，降低对通信网络中其他通信方法的影响。
结合第一方面的第七种实施方式，第一方面的第八种实施方式中，通信网络是OTN。中转设备向每个业务发送设备发送作为第二数据帧的OTN帧。第二字段位于OTN帧的开销区。在第二字段中承载业务接收设备在净荷区对应的MAC地址，即第一MAC地址。
结合第一方面的第六种实施方式至第八种实施方式中的任一种，本申请实施例第一方面的第九种实施方式中，中转设备可以是软件定义网络SDN控制器、服务器或网元中的至少一项。
结合第一方面的第六种实施方式至第九种实施方式中的任一种，本申请实施例第一方面的第十种实施方式中，中转设备向特定的业务发送设备发送n个MAC地址。具体的，中转设备存有业务接收设备与业务发送设备之间的映射关系。中转设备向与业务接收设备之间存在映射关系的业务发送设备发送n个MAC地址。
在本申请实施例中，中转设备不向与业务接收设备之间没有映射关系的业务发送设备发送n个业务接收设备的MAC地址，起到了筛选业务发送设备的作用。中转设备向特定的业务发送设备发送n个业务接收设备的MAC地址，从而减少通信网络中消息的数量，节省通信网络带宽。
结合第一方面、第一方面的第一种实施方式至第十种实施方式中的任一种，本申请实施例第一方面的第十一种实施方式中，业务接收设备的MAC地址与业务接收设备的设备标 识一同发送。业务发送设备根据该设备标识和MAC地址，配置本地路由信息。具体的，业务发送设备接收来自第x业务接收设备的第xMAC地址和第x设备标识。业务发送设备将第x设备标识和第xMAC地址填入ARP表中。业务发送设备为了向第x业务接收设备发送业务数据，查询路由表获取第x设备标识，再查询ARP表获取第xMAC地址。
在本申请实施例中，将业务接收设备的MAC地址和设备标识填入业务发送设备的ARP表。通过设备标识和ARP表、路由表来查询业务接收设备的MAC地址，沿用了大部分通信网络所使用的ARP技术。对已有通信网络的变动小，实现通信网络结构变更所付出的代价小。
结合第一方面的第十一种实施方式，本申请实施例第一方面的第十二种实施方式中，业务接收设备的设备标识是业务接收设备的IP地址，用于标识业务接收设备。
在本申请实施例中，通过设备的IP地址来标识业务接收设备，而不是用多个端口的IP地址来标识业务接收设备。发送设备只要基于业务接收设备的一个设备IP地址来配置路由信息即可，不需要对同一业务接收设备的多个端口配置路由信息。通信网络中同一业务接收设备不需要多个端口，通信网络结构更简单。业务发送设备通过IP地址配置路由信息。由一个设备的IP地址代替多个端口的IP地址，业务发送设备对路由信息的配置也更简单。通信网络中发送的包含业务接收设备IP地址或业务接收设备端口IP地址的消息的数量减少，节省通信网络带宽。
本申请实施例第二方面提供了一种数据传输方法，该方法包括：n个业务接收设备中的任一个业务接收设备，本申请实施例中称为第一业务接收设备。第一业务接收设备向任一与其具有连接关系的业务发送设备广播第一业务接收设备的MAC地址。具体的，第一业务接收设备向m个发送设备中的每个业务发送设备广播第一业务接收设备的MAC地址。在本申请实施例中，第一业务接收设备的MAC地址也称为第一MAC地址。第一MAC地址用于每个发送设备配置本地路由信息。第一业务接收设备接收来自至少一个业务发送设备的业务数据和第一MAC地址。至少一个业务发送设备为m个业务发送设备中的至少一个。业务数据和第一MAC地址为根据配置好的本地路由信息发送的。
本方面所示的有益效果，请详见第一方面所示，具体不做赘述。
结合第二方面，本申请实施例第二方面的第一种实施方式中，第一业务接收设备通过第一数据帧向m个业务发送设备中的每个业务发送设备发送第一MAC地址。第一数据帧包括第一字段。第一字段用于承载第一MAC地址。
通信网络具体可以是光传送网OTN。OTN用于传输OTN帧。OTN帧包括净荷区和开销区。净荷区用于传输业务数据，开销区用于传输除业务数据外的数据。为传输业务数据，需要获取接收设备在净荷区对应的MAC地址。接收设备可以向发送设备发送OTN帧，在该OTN帧的开销区中携带接收设备在净荷区对应的MAC地址。
结合第二方面的第一种实施方式，本申请实施例第二方面的第二种实施方式中，第一业务接收设备为光传送网OTN中的设备。业务接收设备可发送和接收OTN帧。OTN帧包括净荷区和开销区。净荷区用于传输业务数据，开销区用于传输除业务数据外的数据。为传输业务数据，需要获取业务接收设备在净荷区对应的MAC地址。业务接收设备向业务发送 设备发送作为第一数据帧的OTN帧。在OTN帧开销区的第一字段中承载业务接收设备在净荷区对应的MAC地址，即第一MAC地址。
结合第二方面的第二种实施方式，本申请实施例第二方面的第三种实施方式中，第一字段包括GCC0字段、GCC1字段或GCC2字段中的至少一个。
结合第二方面的第二种实施方式或第三种实施方式，本申请实施例第一方面的第四种实施方式中，可以通过扩展协议实现第一MAC地址的传输。具体的，第一字段用于承载扩展协议的报文。扩展协议的报文用于指示第一MAC地址。具体的，扩展协议的报文中包括第一数据分块。第一数据分块用于指示第一MAC地址。
结合第二方面的第四种实施方式，本申请实施例第二方面的第五种实施方式中，扩展协议包括路径计算单元通信协议(path computation element communication protocol，PCEP)或边界网关协议(border gateway protocol，BGP)。
结合第二方面、第二方面的第一种实施方式至第五种实施方式中的任一种，本申请实施例第二方面的第六种实施方式中，当业务接收设备的数量为多个时，可以通过中转设备减少业务接收设备发送MAC地址的消息数量。具体的，若业务接收设备的数量为n，n为大于或等于2的整数。n个业务接收设备向中转设备发送n个MAC地址。n个MAC地址是各不相同的，n个MAC地址与n个业务接收设备的MAC地址一一对应。n个MAC地址用于向m个业务发送设备中的每个业务发送设备转发。例如，第x业务接收设备为该n个业务接收设备中的任一个业务接收设备。x为位于大于或等于1且小于或等于所述n之间的任一整数。第x业务接收设备向中转设备发送第xMAC地址。第xMAC地址为第x业务接收设备的MAC地址。第xMAC地址用于中转设备向业务发送设备转发，以使得业务发送设备根据该第xMAC地址配置本地路由信息。
结合第二方面的第六种实施方式，本申请实施例第二方面的第七种实施方式中，中转设备具体可以是软件定义网络SDN控制器、服务器或网元中的至少一项。
结合第二方面的第六种实施方式或第七种实施方式，本申请实施例第一方面的第八种实施方式中，中转设备向特定的业务发送设备发送n个MAC地址。具体的，中转设备存有业务接收设备与业务发送设备之间的映射关系。中转设备向与业务接收设备之间存在映射关系的业务发送设备发送n个MAC地址。
结合第二方面、第二方面的第一种实施方式至第八种实施方式中的任一种，本申请实施例第二方面的第九种实施方式中，业务接收设备的MAC地址与业务接收设备的设备标识一同发送。设备标识和MAC地址用于业务发送设备配置本地路由信息。
结合第二方面的第九种实施方式，本申请实施例第二方面的第十种实施方式中，业务接收设备的设备标识是业务接收设备的IP地址，用于标识业务接收设备。
本申请实施例第三方面提供了一种数据传输方法，该方法包括：
m个业务发送设备中的每个业务发送设备接收来自第一业务接收设备的第一MAC地址。第一MAC地址为第一业务接收设备的MAC地址。第一业务接收设备为n个业务接收设备中的任一个。业务接收设备为与业务发送设备有连接关系的任一设备。每个业务发送设备接收到第一MAC地址后，根据第一MAC地址配置本地路由信息。m个业务发送设备中的至少 一个业务发送设备，根据配置好的本地路由信息，向第一业务接收设备发送业务数据和第一MAC地址。
本方面所示的有益效果，请详见第一方面所示，具体不做赘述。
结合第三方面，本申请实施例第三方面的第一种实施方式中，m个业务发送设备中的每个业务发送设备通过第一数据帧接收来自业务接收设备的第一MAC地址。第一数据帧包括第一字段。第一字段用于承载第一MAC地址。
结合第三方面的第一种实施方式，本申请实施例第三方面的第二种实施方式中，业务发送设备为光传送网OTN中的设备。业务发送设备可以发送和接收OTN帧。OTN帧包括净荷区和开销区。净荷区用于传输业务数据，开销区用于传输除业务数据外的数据。为传输业务数据，需要获取业务接收设备在净荷区对应的MAC地址。业务发送设备接收来自业务接收设备的作为第一数据帧的OTN帧。OTN帧开销区的第一字段中承载业务接收设备在净荷区对应的MAC地址，即第一MAC地址。
结合第三方面的第二种实施方式，本申请实施例第三方面的第三种实施方式中，第一字段包括GCC0字段、GCC1字段或GCC2字段中的至少一个。
结合第三方面的第二种实施方式或第三种实施方式，本申请实施例第三方面的第四种实施方式中，可以通过扩展协议实现第一MAC地址的传输。具体的，第一字段用于承载扩展协议的报文。扩展协议的报文用于指示第一MAC地址。具体的，扩展协议的报文中包括第一数据分块。第一数据分块用于指示第一MAC地址。
结合第三方面的第四种实施方式，本申请实施例第三方面的第五种实施方式中，扩展协议包括路径计算单元通信协议(path computation element communication protocol，PCEP)或边界网关协议(border gateway protocol，BGP)。
结合第三方面、第三方面的第一种实施方式至第五种实施方式中的任一种，本申请实施例第三方面的第六种实施方式中，业务接收设备的数量为多个时，可以通过中转设备减少通信网络中用于传输业务接收设备MAC地址的消息数量。具体的，m个业务发送设备中的每个业务发送设备，接收来自中转设备的中转消息。若业务接收设备的数量n为大于或等于2的整数。每条中转消息中包括n个MAC地址，n个MAC地址与n个接收设备一一对应。每个业务发送设备根据n个MAC地址配置本地路由信息。本地路由信息对应于n个业务接收设备。具体的，每个业务发送设备根据第xMAC地址，配置与第x业务接收设备相关的本地路由信息。
结合第三方面的第六种实施方式，本申请实施例第三方面的第七种实施方式中，m个业务发送设备中的每个业务发送设备接收来自中转设备的第二数据帧。第二数据帧包括第二字段。第二字段用于指示n个业务接收设备中每个业务接收设备的MAC地址。
结合第三方面的第七种实施方式，第三方面的第八种实施方式中，业务发送设备为OTN中的设备。每个业务发送设备接收来自中转设备的作为第二数据帧的OTN帧。第二字段位于OTN帧的开销区。在第二字段中承载业务接收设备在净荷区对应的MAC地址，即第一MAC地址。
结合第三方面的第六种实施方式至第八种实施方式中的任一种，本申请实施例第三方 面的第九种实施方式中，中转设备可以是软件定义网络SDN控制器、服务器或网元中的至少一项。
结合第三方面的第六种实施方式至第九种实施方式中的任一种，本申请实施例第三方面的第十种实施方式中，业务发送设备为特定的。具体的，中转设备存有业务接收设备与业务发送设备之间的映射关系。只有与业务接收设备之间存在映射关系的业务发送设备，才能接收到来自中转设备的n个MAC地址。
结合第三方面、第三方面的第一种实施方式至第十种实施方式中的任一种，本申请实施例第三方面的第十一种实施方式中，接收设备的MAC地址与接收设备的设备标识一同接收。业务发送设备根据该设备标识和MAC地址，配置本地路由信息。具体的，业务发送设备接收来自第x接收设备的第xMAC地址和第x设备标识。业务发送设备将第x设备标识和第xMAC地址填入ARP表中。业务发送设备为了向第x接收设备发送业务数据，查询路由表获取第x设备标识，再查询ARP表获取第xMAC地址。
结合第三方面的第十一种实施方式，本申请实施例第三方面的第十二种实施方式中，业务接收设备的设备标识是业务接收设备的IP地址，用于标识业务接收设备。
本申请实施例第四方面提供了一种计算机可读存储介质，该计算机可读存储介质中保存有程序，当所述计算机执行所述程序时，执行前述第一方面所述的方法。
本申请实施例第五方面提供了一种计算机可读存储介质，该计算机可读存储介质中保存有程序，当所述计算机执行所述程序时，执行前述第二方面所述的方法。
本申请实施例第六方面提供了一种计算机可读存储介质，该计算机可读存储介质中保存有程序，当所述计算机执行所述程序时，执行前述第三方面所述的方法。
本申请实施例第七方面提供了一种计算机程序产品，当该计算机程序产品在计算机上执行时，所述计算机执行前述第一方面所述的方法。
本申请实施例第八方面提供了一种计算机程序产品，当该计算机程序产品在计算机上执行时，所述计算机执行前述第二方面所述的方法。
本申请实施例第九方面提供了一种计算机程序产品，当该计算机程序产品在计算机上执行时，所述计算机执行前述第三方面所述的方法。
在本申请实施例中，业务发送设备只要与业务接收设备具有连接关系，就能接收到业务接收设备的MAC地址。业务发送设备根据业务接收设备的MAC地址配置本地路由信息。业务发送设备根据本地路由信息，就能实现业务数据的成功发送。无论是业务发送设备获取业务接收设备的MAC地址，还是业务发送设备向业务接收设备发送业务数据，都不受到业务发送设备与业务接收设备IP地址的网段的限制。每个业务发送设备或业务接收设备不需要具有多个处于不同网段的端口，通信网络的结构更简单。规划人员也不需要确保每对业务发送设备和业务接收设备之间具有处于同网段的端口，规划更方便。
附图说明
图1为通信网络的架构图；
图2为光传送网OTN的架构图；
图3为本申请实施例中一个OTN架构图；
图4为本申请实施例中数据传输方法一个流程示意图；
图5为本申请实施例中扩展后BGP协议报文一个格式示意图；
图6为本申请实施例中通信网络一个架构图；
图7为本申请实施例中数据传输方法一个流程示意图；
图8为本申请实施例中通信网络一个结构示意图；
图9为本申请实施例中业务接收设备一个结构示意图；
图10为本申请实施例中业务发送设备一个结构示意图。
具体实施方式
本申请实施例提供了一种业务数据传输方法，用于简化通信网络结构，以降低通信网络结构的复杂度。
请参阅图1，图1提供了一种通信网络的架构图。该通信网络具有多个业务发送设备和多个业务接收设备。在该通信网络中，业务发送设备1至业务发送设备m中的每个业务发送设备，都具有n个端口。该n个端口对应n个处于不同网段的IP地址。业务接收设备1至业务接收设备n中的每个业务接收设备，都具有m个端口。该m个端口对应m个处于不同网段的IP地址。
当m＝2，n＝3时，每个业务发送设备都具有3个端口，每个业务接收设备都具有2个端口。例如业务发送设备1，具有IP地址分别为IP1、IP2、IP3的三个端口。业务接收设备1，具有IP地址分别为IP1’、IP4’的两个端口。
只要业务发送设备与业务接收设备的端口之间，具有处于同网段的IP地址，就可以实现业务数据的传输。
基于该架构，业务发送设备1至业务发送设备m中的每个业务发送设备，都能向业务接收设备1至业务接收设备n中的每个业务接收设备发送业务消息。例如图1中的业务发送设备1，可以通过端口1和端口1’向业务接收设备1发送业务数据。
值得注意的是，业务发送设备与业务接收设备的关系并不是如图中所示固定不变的。图1中的业务发送设备也可作为业务接收设备，用于接收来自该通信网络中其他设备的业务消息。例如，当业务发送设备1作为业务接收设备时，可以通过端口1和端口1’，接收来自业务接收设备1的业务消息。业务发送设备之间也可以互相发送数据，例如业务发送设备1也可以通过端口z和端口z’，接收来自业务发送设备2的业务消息。
值得注意的是，图1中的m＝2，n＝3，仅是对业务发送设备和业务接收设备数量的举例。m和n可以为任何正整数，具体此处不作限定。
若通信网络中所有设备的所有端口都处于同一网段，那么每个设备就只有一个端口。但在实际应用中，存在以下问题。一方面，所有端口处于同一网段会造成广播ARP请求时，ARP请求的数量过多。从而导致对通信网络带宽的占用过多。另一方面，不同的设备归属于不同的用户。不同用户对设备端口的网段，其要求也不一样。因此，在通信网络中，绝大部分设备都具有多个端口。
通信网络包括光传送网OTN。请参阅图2，图2为一种OTN的网络架构图。用户网络边缘设备(customer edge，CE)与云端虚拟机(virtual personal computer，VPC)之间的 数据传输，可以由OTN来实现。OTN中包括与CE连接的用户前置设备(customer premise equipment，CPE)。CE通过CPE接收和发送业务数据。OTN中还包括与云端VPC连接的云端前置设备(premise equipment，PE)。云端VPC通过云端PE接收和发送业务数据。在本申请实施例中，云端PE也称为云PE，云端VPC也称为VPC。
以CE1到云端VPC1的业务数据传输为例。CE1为了向VPC1传输的业务数据，需要通过与CE1连接的CPE1和与VPC1连接的云PE1实现。此时CP1为业务发送设备，云PE1为业务接收设备。CPE1通过端口1、端口2和端口3广播ARP请求，获取云PE端口的MAC地址。由于ARP请求受限于端口IP地址的网段，CPE1和云PE1只能通过具有同网段IP地址的端口1和端口1’实现业务数据的传输。
在本申请实施例中，CE1作为业务数据的来源设备，云端VPC1作为业务数据的接收设备。来源设备为与业务发送设备连接的，向业务发送设备提供业务数据的设备。接收设备为与业务接收设备连接的，接收来自业务接收设备的业务数据的设备。CE1仅是对来源设备的举例，并不造成对来源设备的限定。例如，来源设备也可以是云端VPC。和云端VPC1仅是对来源设备和接收设备的举例，并不造成对来源设备和接收设备的限定。例如，业务接收设备也可以是CE。
对于一个业务发送设备来说，要向多个业务接收设备发送业务数据，就需要具有多个处于不同网段的IP地址。也就需要具有多个端口。业务接收设备同理。对于每对业务接收设备和业务发送设备来说，业务发送设备的端口和业务接收设备的端口，需要具有处于同网段的IP地址。从通信网络的角度来看，每个设备具有多个端口，通信网络结构复杂。从规划人员的角度来看，需要确保业务发送设备的端口和业务接收设备的端口，具有处于同网段的IP地址，规划难度高。
为了解决上述问题，本申请实施例提供了一种业务数据的传输方法，通过向业务发送设备广播业务接收设备的MAC地址来实现业务数据的传输。在业务接收设备接入通信网络或通信网络拓扑发生变化时，业务接收设备就向与其具有连接关系的所有业务发送设备主动发送该业务接收设备的MAC地址。所有的业务发送设备保存该业务接收设备的MAC地址，就能向该业务接收设备发送业务数据。
值得注意的是，本申请实施例中的广播，指的是向设备发送同一数据的动作。设备的数量可以是一个以上或两个以上。具体在本申请实施例中，广播就是指向业务发送设备发送MAC地址的动作。MAC地址为业务接收设备的MAC地址。业务发送设备的数量可以是一个以上或两个以上。
本申请实施例中，通信网络中包括m个业务发送设备和n个业务接收设备。业务接收设备用于接收业务数据，业务发送设备用于发送业务数据。m和n均为大于或等于1的整数，m也可以为大于或等于2的整数。
本申请实施例提供的数据传输方法，可以应用于光传送网OTN。除了OTN，本申请实施例提供的数据传输方法也可应用于其他通信网络。例如自动交换光网络(automatically switched optical network，ASON)或分组传输网(packet transport network，PTN)等，此处不作限定。本申请实施例以该方法应用于OTN为例进行介绍。
本申请实施例可通过扩展已有的点到点可靠传输协议实现上述方法。在本申请实施例中，扩展后的点到点可靠传输协议，也称为扩展协议。
图3为本申请实施例中提供的一种OTN架构图。由于本申请实施例提供的方法，不需要用到端口的IP地址，因此图3的网络架构中不需要出现设备的端口。相比于图1或图2所示的通信网络架构，图3的通信网络架构不需要设置设备的端口。图3的通信网络架构结构更简单，通信网络结构的复杂度低。基于图3所示的网络架构，可以实现图4所示的方法。
本申请实施例中，业务接收设备可以是OTN中的CPE，业务发送设备可以是OTN中的云PE。或者也可以业务接收设备是云PE，业务发送设备是CPE。或者也可以业务接收设备是第一CPE，业务发送设备是第二CPE。或者也可以业务接收设备是第一云PE，业务发送设备是第二云PE。具体此处不做限定。
在本申请实施例中，将CPE作为业务接收设备，将云PE作为业务发送设备。本申请实施例仅是对业务接收设备和业务发送设备的举例，并不造成对业务接收设备和业务发送设备的限定。
接下来以通信网络为OTN，扩展协议为边界网关协议BGP举例。请参阅图4，基于图3所示的OTN架构，本申请实施例提供的一种数据传输方法，其流程包括：
401、第一业务接收设备向m个业务发送设备广播第一MAC地址。
业务接收设备可以通过OTN发送和接收OTN帧。OTN帧包括开销区和净荷区。净荷区用于承载业务数据。开销区也称为控制开销，用于承载业务数据的路由信息和设备的路由信息。控制开销的数据传输不受设备的IP地址和MAC地址的制约。业务接收设备可以通过控制开销，向所有与该业务接收设备具有连接关系的设备发送数据。在本申请实施例中，与业务接收设备具有连接关系，且能向业务接收设备发送业务数据的设备，称为业务发送设备。具体的，若网络中包括n个业务接收设备和m个业务发送设备，m和n均为大于或等于1的整数。第一业务接收设备为n个业务接收设备中的任一个。接下来以云PE1作为第一业务接收设备，说明本申请实施例所述的方法。
在本实施例中，以云PE1为例，说明所有业务接收设备。云PE1并不造成对业务接收设备的限定。
在云PE1刚接入通信网络或通信网络拓扑发生变化的情况下，云PE1可以向任一与其具有连接关系的CPE，广播第一数据帧。第一数据帧用于承载云PE1的MAC地址。
具体的，CPE的数量为m，m个CPE代表通信网络中与云PE1有连接关系的所有业务发送设备。
在本实施例中，第一数据帧为OTN帧。当本申请实施例的方法应用于其他通信网络时，第一数据帧可以是对应于该通信网络的数据帧，此处不作限定。
在本申请实施例中，业务接收设备的MAC地址也称为第一MAC地址。
在本申请实施例中，可以通过扩展协议的报文实现对第一MAC地址的广播。具体的，以BGP报文为代表的扩展协议的报文中，包括第一数据分块，第一数据分块用于指示第一MAC地址。扩展协议的报文可以承载于第一数据帧的第一字段。第一MAC地址用于业务发 送设备配置与业务接收设备相关的本地路由信息。除了BGP报文，扩展协议的报文还可以是其他扩展协议的报文。例如PCEP报文等，具体此处不作限定。
在本申请实施例中，若A承载B，表示A为用于放置B的一个位置，但A并不一定能完全容纳B。因此A可以是一个或多个。只要A能放置B的内容，即为承载。例如，第一字段用于承载BGP报文。那么一个BGP报文的内容可以放置于多个第一字段内，每个第一字段用于放置BGP报文的一部分内容。
具体的，当第一数据帧为OTN帧时，第一字段可以是OTN帧开销区的GCC0，第一字段也可以是OTN帧开销区的其他字段，例如GCC1或GCC2，具体此处不作限定。当第一数据帧为其他通信网络的数据帧时，第一字段相应的为其他通信网络数据帧的某字段，具体此处不作限定。
请参阅表1，在已有的BGP协议中，BGP报文支持携带路径属性(path attributes)对象。其中就包括路由目的地址和用于表示下一跳IP地址的NEXT_HOP。具体应用于图2所示的场景中，若路径属性为路由目的地址，则对应的路径属性内容是VPC的IP地址。若路径属性为NEXT_HOP，则路径属性内容是接收设备第一端口的IP地址。
表1已有的BGP报文
路径属性对象 路径属性内容
路由目的地址 VPC的IP地址
NEXT_HOP 第一端口的IP地址
在已有的BGP协议中，BGP报文不支持携带MAC地址。BGP协议也没有规定特定的数据分块用于指示MAC地址。本申请实施例通过扩展协议，规定扩展协议报文的第一数据分块用于指示业务接收设备的MAC地址。从而实现对业务接收设备MAC地址的传输。
请参阅表2，本申请实施例将扩展BGP协议。在扩展的BGP报文中新增一种路径属性，此新增路径属性为NEXT_HOP_MAC，用于表示下一跳的MAC地址。NEXT_HOP_MAC在BGP报文中与NEXT_HOP属性一并出现。在本申请实施例中，NEXT_HOP_MAC即为第一数据分块。
表2本申请实施例扩展的BGP报文
路径属性对象 路径属性内容
路由目的地址 VPC的IP地址
NEXT_HOP 第一IP地址
NEXT_HOP_MAC 第一MAC地址
本申请实施例所示的方法中出现的BGP报文，均为扩展后的BGP报文。
具体的，在云PE1发送BGP报文时，将报文中路径属性NEXT_HOP的路径属性内容填充为云PE1的IP地址，路径属性NEXT_HOP_MAC的路径属性内容填充为云PE1的MAC地址。此处的IP地址指的是云PE1的设备标识，也称为第一IP地址。设备标识用于标识接收设备。此处的MAC地址指的是云PE1的MAC地址，也称为第一MAC地址。第一MAC地址是接收设备的MAC地址。在本申请实施例中，扩展协议的报文中用于填充第一MAC地址的字段也可称为第二字段。
在本申请实施例中，第一IP地址可以是接收设备自身的ID号，也可以是其他用于标 识接收设备的设备标识。例如人工配置的标识号，具体此处不作限定。
扩展后的BGP报文的格式可以如图5所述，图5为本申请实施例提供的一种扩展后BGP协议报文的格式示意图。图5中的Attr.Flags表示路径属性的标志位。Type Code表示路径属性的种类，其中Type Code3是NEXT_HOP,Type Code41是NEXT_HOP_MAC。Prefix Length表示路由目的地址前缀的长度。Prefix表示路由目的地址前缀的值。
图5所示的报文格式仅是举例，并不造成对扩展后BGP报文以及扩展协议报文的限定。
402、m个业务发送设备中的每个业务发送设备，根据第一MAC地址配置本地路由信息。
在本实施例中，所述业务发送设备可以包括图3中的CPE1和CPE2，业务接收设备可以包括图3中的云PE1、云PE2以及云PE3。
示例地，接收到云PE1发送的BGP报文后，m个CPE中的每个CPE配置与云PE1相关的本地路由信息，即保存第一MAC地址与第一IP地址之间的映射关系。具体的，每个CPE可以将BGP报文中的第一IP地址与第一MAC地址之间的映射关系保存在该CPE的ARP表中。也即是将第一IP地址和第一MAC地址填充在ARP表中。与云PE1相关的本地路由信息，也可以以其他形式存在。例如第一MAC地址与路由目的地址之间的映射关系，也即是将第一MAC地址与VPC1的IP地址之间的映射关系，保存在本地，具体此处不做限定。其中，VPC1为与云PE1连接的用于接收业务数据的设备。
在本申请实施例中，ARP表保存在CPE的内存当中，而不是缓存中。因此第一IP地址与第一MAC地址的映射关系一旦被保存，就不会被CPE缓存中的新数据所覆盖。在这一步之后，CPE只要根据保存在内存中的该映射关系就可获取第一MAC地址，不再需要通过其他方法获取。例如广播ARP请求等方法。通过查询保存在内存中的ARP表，获取第一MAC地址，该方法获取第一MAC地址的成功率高。
可选的，CPE还可以将BGP报文中的第一IP地址与路由目的地址之间的映射关系保存在CPE的路由表中，也即是将第一IP地址和路由目的地址填充在路由表中。在本申请实施例中，除了通过扩展协议的报文，路由表中第一IP地址与路由目的地址之间的映射关系也可以通过其他方式获取。例如手工配置等，具体此处不做限定。
作为一个示例，本步骤还包括：业务发送设备接收业务数据和云端VPC的IP地址。具体地，当某一CE需要向云端VPC发送业务数据,例如CE1需要向云端VPC1发送业务数据时，与CE1连接的CPE1可以接收到来自CE1的前述业务数据和云端VPC1的IP地址，表示该业务数据的接收方为云端VPC1。
值得注意的是，本申请实施例仅以CE1和云端VPC1为例，并不造成对业务数据来源和目的地的限定。
作为一个示例，在接收到业务接收设备发送的MAC地址后，本步骤还可以包括：业务发送设备确定第一MAC地址。
例如，获取云端VPC1的IP地址后，CPE1可以将云端VPC1的IP地址作为路由目的地址，查询路由表获取云端VPC1的IP地址所对应的云PE1的IP地址，也即是上述第一IP地址。
CPE1再查询上述保存在内存中的ARP表，获取第一IP地址所对应的第一MAC地址。 在本实施例中第一MAC地址即为云PE1的MAC地址。
若前述步骤302中CPE配置的路由信息为第一MAC地址与VPC之间的映射关系，则CPE可直接根据该映射关系和VPC的IP地址确定第一MAC地址，具体此处不做限定。
403、m个业务发送设备中的至少一个业务发送设备，根据本地路由信息向第一业务接收设备发送业务数据和第一MAC地址。
在本实施例中，所述业务发送设备可以包括图3中的CPE1和CPE2，业务接收设备可以包括图3中的云PE1、云PE2以及云PE3。
示例地，获取第一MAC地址之后，CPE1向云PE1发送业务数据和第一MAC地址。具体的，CPE1可以将从CE1处获取的业务数据填充在OTN帧的净荷区中。再在该OTN帧的控制开销中，填充路由目的地址和下一跳MAC地址。
具体的，可以将控制开销中路由目的地址对应的对象填充为云端VPC1的IP地址。将控制开销中下一跳IP地址对应的对象填充为第一IP地址。将控制开销中下一跳MAC地址对应的对象填充为第一MAC地址。
CPE1向云PE1发送该OTN帧。
作为一个示例，在接收到业务接收设备发送的MAC地址后，本步骤还可以包括：业务接收设备将业务数据传输给云端VPC。
例如，云PE1接收到OTN帧，校验该OTN帧控制开销中携带的第一MAC地址为云PE1的MAC地址，从而确认该OTN帧是发送给自己的。
云PE1再通过该OTN帧控制开销中携带的VPC1的IP地址，确定该OTN帧的接收方为云端VPC1，从而将业务数据传输给云端VPC1。
在本申请实施例中，业务接收设备的数量不限定为1个，可以是多个。每个接收设备所具有的对应关系和执行的动作参见云PE1，此处不再赘述。
在本申请实施例中，m个配置了本地路由信息的业务发送设备，均可向业务接收设备发送业务消息。m个业务发送设备中的任一个，向业务接收设备发送业务消息的过程，参见CPE1发送的过程，此处不再赘述。
在本申请实施例中，业务发送设备只要与业务接收设备具有连接关系，就能接收到业务接收设备的MAC地址。业务发送设备根据业务接收设备的MAC地址配置本地路由信息。业务发送设备根据保存在本地的本地路由信息，就能实现业务数据的成功发送。无论是业务发送设备获取业务接收设备的MAC地址，还是业务发送设备向业务接收设备发送业务数据，都不受到业务发送设备与业务接收设备IP地址的网段的限制。每个业务发送设备和业务接收设备不需要具有多个处于不同网段的端口，通信网络的结构更简单。规划人员也不需要确保每对业务发送设备和业务接收设备之间具有处于同网段的端口，规划更方便。
同时，可以直接用业务接收设备的IP地址标识业务接收设备。不再需要规划人员规划每个业务接收设备的端口IP地址，减少了人员在通信网络中的操作步骤，提升了通信网络的自动性。
在本申请实施例中，业务发送设备将业务接收设备的MAC地址保存在本地。在业务发送设备向业务接收设备发送业务数据的情况下，可直接从本地获取业务接收设备的MAC地 址，不需要向其它设备获取。节省了通信网络带宽，同时减小了时延。
在图4所示实施例中，对BGP报文的扩展同样适用于PCEP协议，新增的路径属性对象均为NEXT_HOP_MAC。对扩展后PCEP报文的用法，与图4所示实施例中对扩展后BGP报文的用法相同，此处不再赘述。
值得注意的是，本申请实施例仅以图3所示的OTN架构和图4所示的方法为例。本申请实施例提供的业务数据传输方法并不局限于OTN网络中，还可应用于其他通信网络。例如ASON或PTN等，具体此处不作限定。
当通信网络中存在多个业务发送设备与多个业务接收设备时，可通过中转设备传送业务接收设备的MAC地址。从而减小通信网络中的消息数量。
在本申请实施例中，中转设备用于减少通信网络中传输业务接收设备MAC地址的消息数量。中转设备具体可以是软件定义网络(software defined network，SDN)控制器。中转设备还可以是其他设备，例如服务器或网元等，具体此处不作限定。本申请实施例仅以SDN控制器为例，并不造成对中转设备的限定。
图6为本申请实施例中提供的一种通信网络架构图。该架构通过中转设备减少通信网络中传输第一MAC地址的消息的数量。该通信网络中包括m个CPE和n个云PE。m和n均为大于1的整数。基于图6所示的网络架构，可以实现图7所示的方法。
值得注意的是，本申请实施例中CPE和云PE仅是对业务发送设备和业务接收设备的举例，并不造成限定。业务发送设备和业务接收设备的可能，具体参见图4所示实施例，此处不再赘述。
图7为本申请提供的一种数据传输方法的流程示意图。请参阅图7，基于图6所示的通信网络架构，本申请实施例提供的一种数据传输方法，其流程包括：
701、n个云PE向SDN控制器发送携带第一MAC地址的第一数据帧。
在n个云PE刚接入通信网络或通信网络拓扑发生变化的情况下，n个云PE中的每一个云PE向SDN控制器发送携带第一MAC地址的第一数据帧。每个业务接收设备发送的第一数据帧中，都承载该业务接收设备的MAC地址，即第一MAC地址。也就是说，SDN控制器会接收到来自n个云PE的n个MAC地址。n个MAC地址互不相同，n个MAC地址与n个云PE是一一对应的。例如n个云PE中的第x云PE，向SDN控制器发送第一数据帧。帧中携带第x云PE的MAC地址、IP地址和与第x云PE连接的VPC的IP地址。第x云PE为n个云PE中的任一个。
具体的，第一MAC地址的传输可以通过以BGP协议为代表的扩展协议的报文实现。具体参见图4所示实施例的步骤401，此处不再赘述。
在本申请实施例中，包括业务接收设备MAC地址的消息也可称为路由消息。以云PE1为例，云PE1向SDN控制器发送包括MAC1、IP1和VPC1的路由消息，其中MAC1为云PE1的MAC地址，IP1为云PE1的IP地址，VPC1为VPC1的IP地址。
702、SDN控制器向m个CPE广播中转消息。
SDN控制器接收到n个云PE发送的第x云PE的MAC地址、IP地址和与第x云PE连接的VPC的IP地址后，向m个CPE中的每个广播中转消息。每条中转消息中包括n个云PE 的MAC地址、IP地址和与n个云PE连接的VPC的IP地址。具体的，第x云PE的MAC地址、IP地址和与第x云PE连接的VPC的IP地址承载于BGP报文中。x为从1到n的整数。
具体的，在本申请实施例中，中转消息可以通过OTN帧发送。此时的OTN帧也可称为第二数据帧。第二数据帧用于承载n个接收设备的MAC地址。
第二数据帧与BGP报文的关系，参见图4所示实施例的步骤401中第一数据帧与BGP报文的关系，此处不再赘述。第x云PE的MAC地址、IP地址和与第x云PE连接的VPC的IP地址在BGP报文中的具体位置，参见图4所实施示例中步骤401的说明，此处不再赘述。
703、每个CPE配置与n个云PE相关的本地路由信息。
每个CPE配置与n个云PE相关的本地路由信息。具体的，每个CPE根据第x云PE的MAC地址、IP地址和与第x云PE连接的VPC的IP地址，配置与第x云PE相关的路由信息。x为从1到n的整数。
配置路由信息的具体过程，参见图4所示实施例，此处不再赘述。
704、CPE1接收业务数据和云端VPC的IP地址。
n个CPE中的至少一个，接收业务数据和云端VPC的IP地址，该云端VPC与m个云PE中的某一个相连接。例如，CPE1接收到业务数据和VPC1的IP地址，VPC1与云PE1连接。CPE1代表m个CPE中的任一个。云PE1代表n个云PE中的任一个。本申请实施例仅以CPE1和云PE1为例，并不造成对业务发送设备和业务接收设备的限定。
705、CPE1确定云PE1的MAC地址。
CPE1接收到VPC1的IP地址，就可以根据步骤703中配置的与云PE1相关的路由信息，获取云PE1的MAC地址。获取云PE1的MAC地址的具体过程，参见图4所示实施例，此处不再赘述。
706、CPE1向云PE1发送携带业务数据和云PE1的MAC地址的OTN帧。
获取云PE1的MAC地址后，CPE1向云PE1发送携带业务数据和云PE1的MAC地址的OTN帧。业务数据和MAC地址在OTN帧中的具体位置，参见图4所示实施例，此处不再赘述。
707、云PE1将业务数据传输给云端VPC1。
云PE1接收到OTN帧。校验OTN帧控制开销中携带的MAC地址为云PE1的MAC地址，从而确认该OTN帧是发送给自己的。
云PE1再通过该OTN帧控制开销中携带的VPC1的IP地址，确定该OTN帧的接收方为与云PE1连接的云端VPC1，从而将业务数据传输给云端VPC1。
在本申请实施例中，若没有中转设备，n个业务接收设备向m个业务发送设备发送业务接收设备的MAC地址，一共需要发送m*n条消息。通过中转设备，n个业务接收设备向m个业务发送设备发送业务接收设备的MAC地址，一共需要发送m+n条消息。当m和n均为大于1的整数时，m*n>m+n。通过中转设备发送业务接收设备的MAC地址，可以减少通信网络中消息的数量，节省通信网络带宽。
下面对本申请实施例中的通信网络进行描述，请参阅图8，本申请实施例中，通信网络一种结构包括：
n个业务接收设备801和m个业务发送设备802，n、m均为大于或等于1的整数。
n个业务接收设备801包括第一业务接收设备8011，第一业务接收设备8011为所述n个业务接收设备801中的任一个。
第一业务接收设备8011用于，向所述m个业务发送设备802广播第一MAC地址，所述第一MAC地址为所述第一业务接收设备8011的MAC地址。
m个业务发送设备802中的每个业务发送设备用于，根据所述第一MAC地址配置本地路由信息。
m个业务发送设备802中的至少一个业务发送设备用于，根据所述本地路由信息，向所述第一业务接收设备8011发送所述业务数据和所述第一MAC地址。
在一个示例中，第一业务接收设备8011用于，向所述每个业务发送设备发送第一数据帧，所述第一数据帧包括第一字段，所述第一字段用于承载所述第一MAC地址。
在一个示例中，所述第一数据帧为OTN帧，所述第一字段位于所述OTN帧的开销区。
在一个示例中，所述第一字段用于承载扩展协议的报文，所述扩展协议的报文用于指示所述第一MAC地址。
在一个示例中，所述通信网络还包括中转设备803。
中转设备803用于，接收来自所述n个业务接收设备801的n个MAC地址，所述n个MAC地址与所述n个业务接收设备一一对应。向所述每个业务发送设备转发所述n个MAC地址；
m个业务发送设备802的每个业务发送设备用于，根据所述n个MAC地址配置本地路由信息，所述本地路由信息对应于所述n个业务接收设备。
在一个示例中，中转设备803用于，向所述每个业务发送设备发送第二数据帧，所述第二数据帧包括第二字段，所述第二字段用于指示所述n个业务接收设备中每个业务接收设备的MAC地址。
在一个示例中，中转设备803包括软件定义网络SDN控制器、服务器或网元中的至少一项。
在一个示例中，第一业务接收设备8011用于，向所述m个业务发送设备广播所述第一MAC地址和所述第一业务接收设备的设备标识；
m个业务发送设备802中的每个所述业务发送设备用于，根据所述第一MAC地址和所述设备标识配置本地路由信息。
图8所示通信网络用于执行前述图4或图6所示实施例中的方法。
下面对本申请实施例中的业务接收设备进行描述。图9是本申请实施例提供的一种业务接收设备结构示意图。该业务接收设备900可以包括一个或一个以上中央处理器(central processing units，CPU)901和存储器905。该存储器905中存储有一个或一个以上的应用程序或数据。
其中，存储器905可以是易失性存储或持久存储。存储在存储器905的程序可以包括一个或一个以上模块，每个模块可以包括对业务接收设备中的一系列指令操作。更进一步地，中央处理器901可以设置为与存储器905通信，在业务接收设备900上执行存储器905 中的一系列指令操作。
业务接收设备900还可以包括一个或一个以上电源902，一个或一个以上有线或无线网络接口903，一个或一个以上收发器接口904，和/或，一个或一个以上操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM等。
该业务接收设备900可以执行前述图4、图6或图7所示实施例中业务接收设备所执行的操作，具体此处不再赘述。
下面对本申请实施例中的业务发送设备进行描述。图10是本申请实施例提供的一种业务发送设备结构示意图。该业务发送设备1000可以包括一个或一个以上中央处理器(central processing units，CPU)1001和存储器1005。该存储器1005中存储有一个或一个以上的应用程序或数据。
其中，存储器1005可以是易失性存储或持久存储。存储在存储器1005的程序可以包括一个或一个以上模块，每个模块可以包括对业务发送设备中的一系列指令操作。更进一步地，中央处理器1001可以设置为与存储器1005通信，在业务发送设备1000上执行存储器1005中的一系列指令操作。
业务发送设备1000还可以包括一个或一个以上电源1002，一个或一个以上有线或无线网络接口1003，一个或一个以上收发器接口1004，和/或，一个或一个以上操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM等。
该业务发送设备1000可以执行前述图4、图6或图7所示实施例中业务发送设备所执行的操作，具体此处不再赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可 以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，read-only memory)、随机存取存储器(RAM，random access memory)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (24)

  1. 一种业务数据传输方法，其特征在于，所述方法用于通信网络，所述通信网络包括n个业务接收设备和m个业务发送设备，所述n、m均为大于或等于1的整数，所述方法包括：
    第一业务接收设备向所述m个业务发送设备广播第一MAC地址，所述第一业务接收设备为所述n个业务接收设备中的任一个，所述第一MAC地址为所述第一业务接收设备的MAC地址；
    所述m个业务发送设备中的每个业务发送设备根据所述第一MAC地址配置本地路由信息；
    所述m个业务发送设备中的至少一个业务发送设备根据所述本地路由信息，向所述第一业务接收设备发送所述业务数据和所述第一MAC地址。
  2. 根据权利要求1所述的方法，其特征在于，所述第一业务接收设备向所述m个业务发送设备广播第一MAC地址，包括：
    所述第一业务接收设备向所述每个业务发送设备发送第一数据帧，所述第一数据帧包括第一字段，所述第一字段用于承载所述第一MAC地址。
  3. 根据权利要求2所述的方法，其特征在于，所述第一数据帧为OTN帧，所述第一字段位于所述OTN帧的开销区。
  4. 根据权利要求3所述的方法，其特征在于，所述第一字段用于承载所述第一MAC地址，包括：
    所述第一字段用于承载扩展协议的报文，所述扩展协议的报文用于指示所述第一MAC地址。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述通信网络还包括中转设备，所述第一业务接收设备向所述m个业务发送设备广播第一MAC地址包括：
    所述中转设备接收来自所述n个业务接收设备的n个MAC地址，所述n个MAC地址与所述n个业务接收设备一一对应；
    所述中转设备向所述每个业务发送设备转发所述n个MAC地址；
    所述每个业务发送设备根据所述n个MAC地址配置本地路由信息。
  6. 根据权利要求5所述的方法，其特征在于，所述中转设备向所述每个业务发送设备转发所述n个MAC地址，包括：
    所述中转设备向所述每个业务发送设备发送第二数据帧，所述第二数据帧包括第二字段，所述第二字段用于指示所述n个业务接收设备中每个业务接收设备的MAC地址。
  7. 根据权利要求5或6所述的方法，其特征在于，所述中转设备包括软件定义网络SDN控制器、服务器或网元中的至少一项。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述第一业务接收设备向所述m个业务发送设备广播第一MAC地址，包括：
    所述第一业务接收设备向所述m个业务发送设备广播所述第一MAC地址和所述第一业务接收设备的设备标识；
    所述每个业务发送设备根据所述第一MAC地址配置本地路由信息，包括：
    所述每个所述业务发送设备根据所述第一MAC地址和所述设备标识配置本地路由信息。
  9. 一种业务数据传输方法，其特征在于，所述方法包括：
    第一业务接收设备向所述m个业务发送设备广播第一MAC地址，所述第一业务接收设备为所述n个业务接收设备中的任一个，所述第一MAC地址为所述第一业务接收设备的MAC地址，所述第一MAC地址用于所述m个业务发送设备中的每个业务发送设备配置本地路由信息；
    所述第一业务接收设备接收业务数据和所述第一MAC地址，所述业务数据和所述第一MAC地址由所述m个业务发送设备中的至少一个业务发送设备根据所述本地路由信息发送。
  10. 根据权利要求9所述的方法，其特征在于，所述第一业务接收设备向所述m个业务发送设备广播第一MAC地址，包括：
    所述第一业务接收设备向所述每个业务发送设备发送第一数据帧，所述第一数据帧包括第一字段，所述第一字段用于承载所述第一MAC地址。
  11. 根据权利要求10所述的方法，其特征在于，所述第一数据帧为OTN帧，所述第一字段位于所述OTN帧的开销区。
  12. 根据权利要求11所述的方法，其特征在于，所述第一字段用于承载所述第一MAC地址，包括：
    所述第一字段用于承载扩展协议的报文，所述扩展协议的报文用于指示所述第一MAC地址。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述第一业务接收设备向所述m个业务发送设备广播第一MAC地址包括：
    所述n个业务接收设备向中转设备发送n个MAC地址，所述n个MAC地址与所述n个业务接收设备一一对应，所述n个MAC地址用于向所述每个业务发送设备转发。
  14. 根据权利要求9至13中任一项所述的方法，其特征在于，所述第一业务接收设备向所述m个业务发送设备广播第一MAC地址，包括：
    所述第一业务接收设备向所述m个业务发送设备广播所述第一MAC地址和所述第一业务接收设备的设备标识，所述第一MAC地址和所述设备标识用于所述每个业务发送设备配置本地路由信息。
  15. 一种通信网络，其特征在于，所述通信网络包括n个业务接收设备和m个业务发送设备，所述n、m均为大于或等于1的整数，第一业务接收设备为所述n个业务接收设备中的任一个；
    所述第一业务接收设备用于，向所述m个业务发送设备广播第一MAC地址，所述第一MAC地址为所述第一业务接收设备的MAC地址；
    所述m个业务发送设备中的每个业务发送设备用于，根据所述第一MAC地址配置本地路由信息；
    所述m个业务发送设备中的至少一个业务发送设备用于，根据所述本地路由信息，向 所述第一业务接收设备发送所述业务数据和所述第一MAC地址。
  16. 根据权利要求15所述的通信网络，其特征在于，所述第一业务接收设备用于，向所述每个业务发送设备发送第一数据帧，所述第一数据帧包括第一字段，所述第一字段用于承载所述第一MAC地址。
  17. 根据权利要求16所述的通信网络，其特征在于，所述第一数据帧为OTN帧，所述第一字段位于所述OTN帧的开销区。
  18. 根据权利要求17所述的通信网络，其特征在于，所述第一字段用于承载所述第一MAC地址，包括：
    所述第一字段用于承载扩展协议的报文，所述扩展协议的报文用于指示所述第一MAC地址。
  19. 根据权利要求15至18中任一项所述的通信网络，其特征在于，所述通信网络还包括中转设备，所述中转设备用于，接收来自所述n个业务接收设备的n个MAC地址，所述n个MAC地址与所述n个业务接收设备一一对应；
    向所述每个业务发送设备转发所述n个MAC地址；
    所述每个业务发送设备用于，根据所述n个MAC地址配置本地路由信息。
  20. 根据权利要求19所述的通信网络，其特征在于，所述中转设备用于，向所述每个业务发送设备发送第二数据帧，所述第二数据帧包括第二字段，所述第二字段用于指示所述n个业务接收设备中每个业务接收设备的MAC地址。
  21. 根据权利要求18或19所述的通信网络，其特征在于，所述中转设备包括软件定义网络SDN控制器、服务器或网元中的至少一项。
  22. 根据权利要求15至21中任一项所述的通信网络，其特征在于，所述第一业务接收设备用于，向所述m个业务发送设备广播所述第一MAC地址和所述第一业务接收设备的设备标识；
    所述每个所述业务发送设备用于，根据所述第一MAC地址和所述设备标识配置本地路由信息。
  23. 一种接收设备，其特征在于，包括处理器、存储器、收发器以及总线；
    所述处理器、存储器、收发器与所述总线相连；
    所述处理器用于执行权利要求9至14中任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中保存有程序，当所述计算机执行所述程序时，执行如权利要求1至14中任一项所述的方法。
PCT/CN2021/104916 2020-10-31 2021-07-07 业务数据传输方法、通信网络、业务接收设备及存储介质 WO2022088747A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21884486.8A EP4216509A4 (en) 2020-10-31 2021-07-07 SERVICE DATA TRANSMISSION METHOD, COMMUNICATIONS NETWORK, SERVICE RECEIVING DEVICE AND STORAGE MEDIUM
US18/307,163 US20230262369A1 (en) 2020-10-31 2023-04-26 Service data transmission method, communication network, service receiving device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011197165.4A CN114531424B (zh) 2020-10-31 2020-10-31 业务数据传输方法、通信网络、业务接收设备及存储介质
CN202011197165.4 2020-10-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/307,163 Continuation US20230262369A1 (en) 2020-10-31 2023-04-26 Service data transmission method, communication network, service receiving device, and storage medium

Publications (1)

Publication Number Publication Date
WO2022088747A1 true WO2022088747A1 (zh) 2022-05-05

Family

ID=81381858

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/104916 WO2022088747A1 (zh) 2020-10-31 2021-07-07 业务数据传输方法、通信网络、业务接收设备及存储介质

Country Status (4)

Country Link
US (1) US20230262369A1 (zh)
EP (1) EP4216509A4 (zh)
CN (1) CN114531424B (zh)
WO (1) WO2022088747A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101051889A (zh) * 2007-03-23 2007-10-10 中兴通讯股份有限公司 实现网络控制器间业务数据一致的方法及系统
US20140198646A1 (en) * 2013-01-14 2014-07-17 Dell Products L.P. Sender device based pause system
CN105451222A (zh) * 2014-07-31 2016-03-30 华为技术有限公司 一种终端建立连接的方法、装置及系统
US20170134272A1 (en) * 2015-11-09 2017-05-11 Nec Corporation Communication device and communication method
CN108134646A (zh) * 2016-12-01 2018-06-08 深圳市中兴微电子技术有限公司 一种光传输单元帧的传输方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7096257B2 (en) * 2000-06-15 2006-08-22 Forster Energy Llc Automatic assignment of addresses to nodes in a network
US8594100B2 (en) * 2010-03-31 2013-11-26 International Business Machines Corporation Data frame forwarding using a distributed virtual bridge
CN103929461B (zh) * 2013-08-12 2018-03-20 新华三技术有限公司 堆叠系统中的mac地址信息同步方法及装置
CN105915400A (zh) * 2016-06-28 2016-08-31 北京神州绿盟信息安全科技股份有限公司 一种数据流切换方法及系统
CN106357542B (zh) * 2016-10-12 2019-10-18 华为技术有限公司 提供组播业务的方法和软件定义网络控制器
WO2019071369A1 (zh) * 2017-10-09 2019-04-18 华为技术有限公司 光网络中数据传输方法及光网络设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101051889A (zh) * 2007-03-23 2007-10-10 中兴通讯股份有限公司 实现网络控制器间业务数据一致的方法及系统
US20140198646A1 (en) * 2013-01-14 2014-07-17 Dell Products L.P. Sender device based pause system
CN105451222A (zh) * 2014-07-31 2016-03-30 华为技术有限公司 一种终端建立连接的方法、装置及系统
US20170134272A1 (en) * 2015-11-09 2017-05-11 Nec Corporation Communication device and communication method
CN108134646A (zh) * 2016-12-01 2018-06-08 深圳市中兴微电子技术有限公司 一种光传输单元帧的传输方法及装置

Also Published As

Publication number Publication date
CN114531424A (zh) 2022-05-24
CN114531424B (zh) 2023-11-10
EP4216509A4 (en) 2023-09-06
EP4216509A1 (en) 2023-07-26
US20230262369A1 (en) 2023-08-17

Similar Documents

Publication Publication Date Title
CN112165725B (zh) 报文处理的方法及设备
US7782854B2 (en) Network switching apparatus, route management server, network interface apparatus, control method therefor, computer program for route management server, and computer-readable storage medium
KR100811890B1 (ko) 인터넷 시스템에서 서비스 플로우를 보장하는 애니캐스트라우팅 방법 및 장치
US10164910B2 (en) Method and apparatus for an information-centric MAC layer
US20080075078A1 (en) Frame Transfer System
US7673061B2 (en) Method and apparatus for neighborhood discovery across disparate point-to-point networks
US20060280138A1 (en) Wireless access point repeater
TWI491231B (zh) 網型網路之代理機制
US20210289436A1 (en) Data Processing Method, Controller, and Forwarding Device
US20090225660A1 (en) Communication device and operation management method
WO2007112645A1 (fr) Procédé et système de mise en oeuvre d'un réseau privé virtuel mobile
WO2014082414A1 (zh) 业务转发的方法及设备
CN108206783A (zh) 一种软件定义网络系统中地址配置方法及其装置
US20220200820A1 (en) Packet Sending Method and Apparatus
US20040202185A1 (en) Multiple virtual local area network support for shared network adapters
KR100299144B1 (ko) 비동기전송모드와 이더넷 네트워크 상에서 레이어-2 스위치를이용한 레이어-3 아이.피 스위칭 장치 및 방법
WO2021147357A1 (zh) 路由信息的发布方法、装置及系统
US20230318974A1 (en) BIER Packet Forwarding Method, Device, and System
US20160112311A1 (en) Enhanced connectivity to end devices via access points of wireless local area networks (wlan)
WO2022088747A1 (zh) 业务数据传输方法、通信网络、业务接收设备及存储介质
US20230006917A1 (en) Route Determining Method and Apparatus and Network Device
US20220263794A1 (en) Method, apparatus, and system for generating forwarding information
CN112994928B (zh) 一种虚拟机的管理方法、装置及系统
JP3464375B2 (ja) 通信データ処理方法及びそのネットワーク間接続装置
US6882646B2 (en) IP network over a partially meshed frame relay network

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021884486

Country of ref document: EP

Effective date: 20230421

NENP Non-entry into the national phase

Ref country code: DE